CN114995675A

CN114995675A - Method for detecting touch jumping point fault, electronic equipment and readable storage medium

Info

Publication number: CN114995675A
Application number: CN202111166893.3A
Authority: CN
Inventors: 韩帅; 樊亮; 冀焕霞
Original assignee: Beijing Honor Device Co Ltd
Current assignee: Beijing Honor Device Co Ltd
Priority date: 2021-09-30
Filing date: 2021-09-30
Publication date: 2022-09-02
Anticipated expiration: 2041-09-30
Also published as: CN114995675B

Abstract

The embodiment of the application provides a method for detecting a touch jumping point fault, electronic equipment and a readable storage medium, and relates to the technical field of touch control, wherein the method comprises the following steps: acquiring first touch data of the electronic equipment, wherein the first touch data comprises coordinates, moments and event identifications of a plurality of report points in a preset time length, the event identifications are used for representing touch events to which the report points belong, the plurality of report points comprise press report points and lift report points, and the press report points and the lift report points have action identifications; and determining whether a preset type of touch jumping point fault exists within a preset time length according to the first touch data. The method provided by the application can detect the touch jumping point fault and identify the type of the touch jumping point fault.

Description

Method for detecting touch jumping point fault, electronic equipment and readable storage medium

Technical Field

The present application relates to the field of touch technologies, and in particular, to a method for detecting a touch skip point fault, an electronic device, and a readable storage medium.

Background

With the rapid development of electronic technologies, touch technologies are widely applied to various electronic devices. For example, touch panels are integrated in screens of devices such as mobile phones, tablet computers, wearable devices, teaching integrated machines and the like, so that the screens of the devices have a touch function while displaying.

When the electronic device with the touch function is applied, a touch jumping point fault may occur probabilistically. The touch jumping points, also referred to as jumping points, abnormal jumping points, "ghost hands", "ghost touches", or automatic touches, refer to that when a user does not perform a touch operation on a screen, a touch panel recognizes a report point and reports a touch event, so that a screen jumps, and an application or a control is automatically operated. When the electronic equipment has a touch jump point fault, the user cannot realize expected operation, the normal use of the user is seriously influenced, and the user experience is poor. Therefore, it is necessary to identify and detect a touch skip point fault, so as to analyze the cause of the touch skip point fault, and further solve the touch skip point fault.

Disclosure of Invention

The application provides a method and a device for detecting a touch jump point fault, an electronic device, a chip, a computer readable storage medium and a computer program product, which can identify and detect the touch jump point fault.

In a first aspect, the present application provides a method for detecting a touch skip point fault, where the method includes:

acquiring first touch data of the electronic equipment, wherein the first touch data comprises coordinates, moments and event identifications of a plurality of report points in a preset time length, the event identifications are used for representing touch events to which the report points belong, the plurality of report points comprise press report points and lift report points, and the press report points and the lift report points have action identifications; and determining whether a preset type of touch jump point fault exists in a preset time length according to the first touch data.

The method for detecting the touch jumping point fault can detect whether the preset type of touch jumping point fault exists within the preset time length, so that the generation reason of the touch jumping point fault can be analyzed in the later period, the touch jumping point fault is solved or the probability of the occurrence of the jumping point fault is reduced, and the user experience is improved; moreover, the whole process does not need manual intervention and has high intelligence. In addition, the implementation mode can detect the type of the touch jumping point fault, so that when the reason of the touch jumping point fault is analyzed at the later stage, the analysis can be carried out based on the type of the touch jumping point fault, and the touch jumping point fault can be more targeted, so that the touch jumping point fault can be more accurately solved.

In one possible implementation, the preset type of touch-control skip point fault is one of a first-direction skip point fault, a fixed-position continuous-click skip point fault, a fixed-position fast-click skip point fault, a full-screen random touch-control skip point fault, a full-screen random simultaneous touch-control skip point fault, a continuous touch-control skip point fault, or a post-touch skip point fault.

In a possible implementation manner, determining whether a preset type of touch trip point fault exists within a preset duration according to first touch data includes:

determining at least one complete touch event in the first touch data according to the event identifications and the action identifications of the report points; the complete touch event refers to a touch event in which the press report point and the lift report point are both included in the first touch data; and determining whether a preset type of touch jumping point fault exists in a preset time period according to the data of at least one complete touch event in the first touch data.

In a possible implementation manner, determining whether a touch skip point fault of a preset type exists within a preset duration according to data of at least one complete touch event in first touch data, where the touch skip point fault of the preset type is a first direction skip point fault, includes:

determining whether the coordinates of a first press report point and an adjacent press report point meet a first coordinate condition or not according to the coordinates and the time of the press report point of at least one complete touch event; the touch control system comprises a first touch control point, a second touch control point, a third touch control point and a fourth touch control point, wherein the first touch control point is a touch control point of any complete touch control event, and the adjacent touch control points are touch control points adjacent to the first touch control point in time sequence; the first coordinate condition comprises that the coordinate offset of a first press report point and an adjacent press report point in a second direction is less than or equal to a first offset threshold, and the second direction is vertical to the first direction; if the coordinates of the first press report point and the adjacent press report point meet a first coordinate condition, determining the first press report point as a first target press report point; if the number of the first target press report points in the data of at least one complete touch event is greater than or equal to a first preset number, determining that a first direction trip point fault exists in a preset time length.

determining whether the coordinates of the first lifting report point and the adjacent lifting report point meet a second coordinate condition or not according to the coordinates and the moment of the lifting report point of at least one complete touch event; the first lifting report point is a lifting report point of any complete touch event, and the adjacent lifting report points are lifting report points adjacent to the first lifting report point in time sequence; the second coordinate condition comprises that the coordinate offset of the first lifting report point and the adjacent lifting report point in the second direction is less than or equal to a first offset threshold, and the second direction is vertical to the first direction; if the coordinates of the first lifting report point and the adjacent lifting report point meet a second coordinate condition, determining the first lifting report point as a target lifting report point; if the number of the target lifting report points in the data of at least one complete touch event is greater than or equal to a first preset number, determining that a first direction jumping point fault exists in a preset time length.

Optionally, the first direction is an abscissa direction in a screen coordinate system of the electronic device, the second direction is a ordinate direction in the screen coordinate system of the electronic device, and the touch skip point fault in the implementation manner is an abscissa direction fault.

The cross coordinate direction jumping point fault is a touch control jumping point fault occurring in the practical application of a user, the detection of the cross coordinate direction jumping point fault in the touch control data can be realized through the two implementation modes, the detection is matched with the touch control jumping point fault type occurring in the practical application of the user, the real experience of the user is fully considered, and therefore the analysis is convenient to be carried out according to the data of the touch control event when the jumping point fault occurs, the cross coordinate direction jumping point fault is solved in a more targeted mode, and the user experience is further improved. In the two implementation modes, the position of the touch event is represented by pressing down the coordinates of the report points or lifting up the coordinates of the report points, so that the algorithm can be simplified, and the efficiency of detecting the touch jump point fault is improved.

Optionally, the first direction is a vertical coordinate direction in a screen coordinate system of the electronic device, the second direction is a horizontal coordinate direction in the screen coordinate system of the electronic device, and the touch skip point fault in the implementation manner is a vertical coordinate direction fault.

Similarly, a longitudinal coordinate direction jumping point fault is a touch control jumping point fault occurring in the practical application of a user, the detection of the longitudinal coordinate direction jumping point fault in the touch control data can be realized through the two implementation modes, the detection is matched with the type of the touch control jumping point fault occurring in the practical use of the user, and the real experience of the user is fully considered, so that the analysis is convenient to be performed according to the data of the touch control event when the jumping point fault occurs, the longitudinal coordinate direction jumping point fault is solved in a more targeted manner, and the user experience is further improved.

Optionally, the first coordinate condition further includes:

the coordinate offset of the first press point and the adjacent press point in the first direction is less than or equal to the second offset threshold.

In the implementation mode, the coordinate offset of the first press report point and the coordinate offset of the adjacent press report point in the first direction are further limited, and meanwhile, the coordinate offset of the first press report point and the coordinate offset of the adjacent press report point in the second direction are further limited, so that the problem that the touch control of a user under some special conditions (for example, a screen is continuously marked along a certain direction during the touch report accuracy detection) is mistakenly judged as the touch control skip point fault in the abscissa direction can be effectively avoided, and the detection accuracy of the touch control skip point fault in the first direction is improved.

Alternatively, the first offset threshold may be 6 pixels (pixels) to 10 pixels.

Alternatively, the second offset threshold may be 80 pixels to 120 pixels.

Alternatively, the first preset number may be an integer of 4 to 6.

Optionally, the preset time duration may be 800ms to 1200 ms.

In a possible implementation manner, determining whether a preset type of touch skip point fault exists within a preset duration according to data of at least one complete touch event in first touch data, where the preset type of touch skip point fault is a fixed-position continuous click skip point fault, includes:

determining whether the coordinates of the press report point of the first complete touch event and the press report point of the adjacent complete touch event meet a third coordinate condition or not according to the coordinates, the time and the event identification of the report point of at least one complete touch event, and determining whether the event interval of the first complete touch event and the adjacent complete touch event is less than or equal to a preset event interval threshold or not;

the first complete touch event is any complete touch event, and the adjacent complete touch event is a complete touch event which is adjacent to the first complete touch event in time sequence after the first touch event; the third coordinate condition comprises that the coordinate offset of a press report point of the first complete touch event and a press report point of an adjacent complete touch event in the first direction is less than or equal to a third offset threshold, the coordinate offset in the second direction is less than or equal to a fourth offset threshold, and the first direction is vertical to the second direction; the event interval refers to a time difference between a time point of raising a report point of a previous touch event and a time point of pressing a report point of a next touch event in a time sequence in the two touch events;

if the coordinates of the press report point of the first complete touch event and the press report point of the adjacent complete touch event meet a third coordinate condition, and the event interval between the first complete touch event and the adjacent complete touch event is less than or equal to a preset event interval threshold, determining the first complete touch event as a first target event;

and if the number of the first target events in the at least one complete touch event is greater than or equal to a second preset number, determining that a fixed-position continuous click skip point fault exists in a preset time length.

determining whether the coordinates of the lifting report point of the first complete touch event and the lifting report point of the adjacent complete touch event meet a fourth coordinate condition or not according to the coordinates, the time and the event identification of the report point of at least one complete touch event, and determining whether the event interval of the first complete touch event and the adjacent complete touch event is smaller than or equal to a preset event interval threshold or not;

the first complete touch event is any complete touch event, and the adjacent complete touch event is a complete touch event which is adjacent to the first complete touch event in time sequence after the first complete touch event; the fourth coordinate condition comprises that the coordinate offset of the lifting report point of the first complete touch event and the lifting report point of the adjacent complete touch event in the first direction is less than or equal to a third offset threshold, the coordinate offset in the second direction is less than or equal to a fourth offset threshold, and the first direction is vertical to the second direction; the event interval refers to the time difference between the time of raising the report point of the previous touch event and the time of pressing the report point of the next touch event in the time sequence of the two touch events;

if the coordinates of the lifting report point of the first complete touch event and the lifting report point of the adjacent complete touch event meet a fourth coordinate condition, and the event interval between the first complete touch event and the adjacent complete touch event is less than or equal to a preset event interval threshold, determining the first complete touch event as a second target event;

and if the number of the second target events in the at least one complete touch event is greater than or equal to a second preset number, determining that a fixed-position continuous click skip point fault exists in a preset time length.

The fixed-position continuous click skip point fault is a touch control skip point fault occurring in the practical application of a user, the fixed-position continuous click skip point fault in the touch control data can be detected through the two implementation modes, the fixed-position continuous click skip point fault is matched with the touch control skip point fault type occurring in the practical application of the user, the real experience of the user is fully considered, therefore, the analysis is convenient to be carried out according to the data of the touch control event when the skip point fault occurs, the fixed-position continuous click skip point fault is solved in a more targeted manner, and the user experience is further improved. In the two implementation modes, the position of the touch event is represented by pressing down the coordinates of the report point or lifting up the coordinates of the report point, so that the algorithm can be simplified, and the efficiency of detecting the touch jump point fault is improved.

Alternatively, the third offset threshold and the fourth offset threshold may both be 128 pixels to 192 pixels.

Alternatively, the second preset number may be an integer of 4 to 6.

Alternatively, the preset event interval threshold may be 16ms to 24 ms.

Optionally, the preset time duration may be 490ms to 510 ms.

In a possible implementation manner, determining whether a preset type of touch skip point fault exists within a preset duration according to data of at least one complete touch event in first touch data, where the preset type of touch skip point fault is a fixed-position fast-click skip point fault, includes:

determining whether the pressing report point of the first complete touch event and the pressing report point of the adjacent complete touch event meet a fifth coordinate condition or not according to the coordinates, the moment and the event identification of the report point of at least one complete touch event, and determining whether the touch duration of the first complete touch event is less than or equal to a preset touch duration threshold value or not;

the first complete touch event is any complete touch event, and the adjacent complete touch event is a complete touch event which is adjacent to the first complete touch event in time sequence after the first complete touch event; the fifth coordinate condition comprises that the coordinate offset of a press report point of the first complete touch event and a press report point of an adjacent complete event in the first direction is less than or equal to a fifth offset threshold, the coordinate offset in the second direction is less than or equal to a sixth offset threshold, and the first direction is vertical to the second direction; the touch duration refers to the time difference between the time of raising the report point and the time of pressing the report point of the touch event;

if the coordinates of the press report point of the first complete touch event and the press report point of the adjacent complete touch event meet a fifth coordinate condition, and the touch duration of the first complete touch event is less than or equal to a preset touch duration threshold, determining the first complete touch event as a third target event;

and if the number of the third target events in the at least one complete touch event is greater than or equal to a third preset number, determining that a fixed-position quick click trip point fault exists in a preset time.

In a possible implementation manner, determining whether a touch skip point fault of a preset type exists within a preset time period according to data of at least one complete touch event in first touch data when the touch skip point fault of a preset type is a fixed position fast touch skip point fault includes:

determining whether the coordinates of the lifting report point of the first complete touch event and the lifting report point of the adjacent complete touch event meet a sixth coordinate condition or not according to the coordinates, the time and the event identification of the report point of at least one complete touch event, and determining whether the touch duration of the first complete touch event is less than or equal to a preset touch duration threshold or not;

the first complete touch event is any complete touch event, and the adjacent complete touch event is a complete touch event which is adjacent to the first complete touch event in time sequence after the first complete touch event; the sixth coordinate condition comprises that the coordinate offset of the lifting report point of the first complete touch event and the lifting report point of the adjacent complete event in the first direction is less than or equal to a fifth offset threshold, the coordinate offset in the second direction is less than or equal to a sixth offset threshold, and the first direction is vertical to the second direction; the touch duration refers to the time difference between the time of raising the report point and the time of pressing the report point of the touch event;

if the coordinates of the lifting report point of the first complete touch event and the lifting report point of the adjacent complete touch event meet a sixth coordinate condition, and the touch duration of the first complete touch event is less than or equal to a preset touch duration threshold, determining the first complete touch event as a fourth target event;

and if the number of the fourth target events in the at least one complete touch event is greater than or equal to the third preset number, determining that a fixed-position quick click skip point fault exists in the preset time.

The fixed position quick click skip point fault is a touch control skip point fault occurring in the practical application of a user, the fixed position quick click skip point fault in the touch control data can be detected through the process, the fixed position quick click skip point fault is matched with the touch control skip point fault type occurring in the practical application of the user, the real experience of the user is fully considered, and therefore the fixed position quick click skip point fault is conveniently analyzed according to the data of the touch control event when the skip point fault occurs, the fixed position quick click skip point fault is more pertinently solved, and the user experience is further improved.

Alternatively, the fifth offset threshold and the sixth offset threshold may both be 128 pixels to 192 pixels.

Alternatively, the third preset number may be an integer of 4 to 6.

Optionally, the touch duration threshold may be 16ms to 24 ms.

Optionally, the preset time period may be 490ms to 510 ms.

In a possible implementation manner, determining whether a preset type of touch skip point fault exists within a preset time period according to data of at least one complete touch event in first touch data is a full-screen random touch skip point fault, and includes:

determining whether the coordinates of the first press report point and the adjacent press report point meet a seventh coordinate condition or not according to the coordinates and the time of the press report point of at least one complete touch event, and determining whether the time difference between the time of the first press report point and the time of the adjacent press report point is smaller than or equal to a first time difference threshold value or not;

the first press report point is a press report point of any complete touch event, and the adjacent press report points are press report points adjacent to the first press report point in time sequence; the seventh coordinate condition comprises that the coordinate offset of the first press report point and the adjacent press report point in the first direction is greater than or equal to a seventh offset threshold, the coordinate offset in the second direction is greater than or equal to an eighth offset threshold, and the first direction is vertical to the second direction;

if the coordinates of the first press point and the adjacent press point meet a seventh coordinate condition and the time difference between the moment of the first press point and the moment of the adjacent press point is less than or equal to a first time difference threshold value, determining the first press point as a second target press point;

and if the number of the second target touch down report points in the data of at least one complete touch event is greater than or equal to a fourth preset number, determining that a full-screen random touch skip point fault exists within a preset time length.

The full-screen random touch control skip point fault is a touch control skip point fault occurring in the practical application of a user, the full-screen random touch control skip point fault in the touch control data can be detected through the process, the type of the full-screen random touch control skip point fault is matched with the type of the touch control skip point fault occurring in the practical use of the user, the real experience of the user is fully considered, therefore, the analysis is convenient to be carried out according to the data of the touch control event when the skip point fault occurs, the full-screen random touch control skip point fault is solved in a more targeted mode, and the user experience is further improved.

Alternatively, the seventh offset threshold and the eighth offset threshold may both be 128 pixels to 192 pixels.

Optionally, the fourth preset number may be an integer from 4 to 6.

Alternatively, the first time difference threshold may be 24ms to 36 ms.

Optionally, the preset time duration may be 800ms to 1200 ms.

In a possible implementation manner, determining whether a preset type of touch skip point fault exists within a preset time period according to data of at least one complete touch event in first touch data, where the preset type of touch skip point fault is a full-screen random simultaneous touch skip point fault, includes:

if the number of complete touch events in the first touch event data is greater than or equal to a first number threshold, acquiring all sub-time periods in a time period corresponding to a preset time length according to the time of the multiple report points and the event identification, and acquiring the number of touch events in each sub-time period; the duration of the sub-time period is less than the preset duration;

determining the sub-time periods of which the number of touch events is greater than or equal to a second number threshold value in all the sub-time periods as target sub-time periods;

and if the number ratio of the target sub-time periods in all the sub-time periods is greater than the preset ratio, determining that the full-screen random simultaneous touch control skip point fault exists in the preset time length.

The full-screen random simultaneous touch control skip point fault is a touch control skip point fault occurring in the practical application of a user, the full-screen random simultaneous touch control skip point fault in the touch control data can be detected through the process, the type of the touch control skip point fault occurring in the practical application of the user is matched, the real experience of the user is fully considered, therefore, the analysis is convenient to be carried out according to the data of the touch control event when the skip point fault occurs, the full-screen random simultaneous touch control skip point fault is solved in a more targeted mode, and the user experience is further improved.

In a possible implementation manner, acquiring all sub-time periods within a time period corresponding to a preset duration includes:

and respectively taking the time when each report point in the report points is pressed as the starting point of the sub-time period, and obtaining all the sub-time periods according to the time period corresponding to the time length of the sub-time period and the preset time length. According to the method for dividing the sub-time periods, all the divided sub-time periods can include all the press report points in the first touch data, so that traversal of all touch events is realized in the detection process, and the accuracy of the detection result of the touch fault at the same time of the full-screen random is improved.

In a possible implementation manner, the step of obtaining all sub-time periods within a time period corresponding to a preset duration includes:

and dividing the time periods corresponding to the preset time periods according to the time lengths of the sub-time periods to obtain all the sub-time periods. The method for dividing the sub-time periods provided by the implementation mode can quickly acquire all the sub-time periods, and the algorithm efficiency is high.

Optionally, the duration of the sub-period may be 80ms to 120 ms.

Alternatively, the first number threshold may be an integer from 24 to 36.

Alternatively, the second number threshold may be an integer from 3 to 5.

Alternatively, the preset proportion may be 40% to 60%.

Optionally, the preset duration may be 2400ms to 3600 ms.

In one possible implementation manner, the preset type of touch-control skip point fault is a continuous touch-control skip point fault, and the starting point of the time period corresponding to the preset time length is the time of the second press report point;

according to the data of at least one complete touch event in the first touch data, before determining whether a preset type of touch jump point fault exists within a preset time, the method further comprises:

determining that a second lifting report point which is the same as the event identifier of the second pressing report point does not exist in the first touch data;

determining whether a preset type of touch jumping point fault exists within a preset time according to data of at least one complete touch event in the first touch data, wherein the determining comprises the following steps:

determining whether the coordinates of the press report point and the lift report point of the first complete touch event meet an eighth coordinate condition; the first complete touch event is any complete touch event, the eighth coordinate condition comprises that the coordinate offset of a press report point and a lift report point of the first complete touch event in the first direction is less than or equal to a ninth offset threshold, the coordinate offset in the second direction is less than or equal to a tenth offset threshold, and the first direction is vertical to the second direction;

if the coordinates of the press report point and the lift report point of the first complete touch event meet the eighth coordinate condition, determining the first complete touch event as a fifth target event; acquiring the total number of touch events in the first touch data; and if the ratio of the number of the fifth target events to the total number of the fifth target events in the at least one complete touch event is greater than or equal to a preset ratio threshold, determining that a continuous touch skip point fault exists in a preset time length.

The continuous touch control skip point fault is a touch control skip point fault occurring in the practical application of a user, the continuous touch control skip point fault in the touch control data can be detected through the process, the continuous touch control skip point fault is matched with the touch control skip point fault type occurring in the practical application of the user, the real experience of the user is fully considered, therefore, the continuous touch control skip point fault is conveniently analyzed according to the data of the touch control event when the skip point fault occurs, the continuous touch control skip point fault is more pertinently solved, and the user experience is further improved.

Alternatively, the ninth offset threshold and the tenth offset threshold may each be 48 pixels to 72 pixels.

Optionally, the preset time duration may be 6400ms to 9600 ms.

Alternatively, the preset proportional threshold may be 56% to 84%.

In one possible implementation manner, the preset type of touch control trip point fault is a touch back trip point fault, and the starting point of the time period corresponding to the preset time length is the time of the second press report point;

determining whether a preset type of touch jumping point fault exists within a preset time length according to the first touch data, wherein the method comprises the following steps:

determining whether the coordinates of the second press report point and each other press report point meet a ninth coordinate condition or not according to the coordinates and the time of the press report point in the first touch data, and determining whether the time difference between the time of the second press report point and each other press report point is smaller than or equal to a second time difference threshold value or not;

the other press-down points are press-down points in the first touch data except the second press-down point; the ninth coordinate condition comprises that the coordinate offset of the second press report point and each other press report point in the first direction is greater than or equal to an eleventh offset threshold, the coordinate offset of the second press report point in the second direction is greater than or equal to a twelfth offset threshold, and the first direction is vertical to the second direction;

if the coordinates of the second press-down point and each other press-down point meet the ninth coordinate condition, and the time difference between the time of the second press-down point and the time of each other press-down point is smaller than or equal to a second time difference threshold value, determining the second press-down point and each other press-down point as a group of multi-point common-touch report points;

acquiring third touch data within a preset time length by taking the moment of the third press report point as a starting point, taking the third press report point as a second press report point, and executing the first touch data on the third touch data until the second press report point and each other press report point are not multi-point common touch report points, and determining the group number of the multi-point common touch report points; the third press report point is a press report point which is behind the second lift report point and is adjacent to the second lift report point in time sequence, and the second lift report point is a lift report point which has the same event identification as the second press report point;

and if the group number of the multipoint common touch report points is greater than or equal to the preset group number, determining that the post-touch skip point fault exists in the preset time.

The after-touch skip point fault is a touch skip point fault occurring in the practical application of a user, the after-touch skip point fault in the touch data can be detected through the process, the after-touch skip point fault is matched with the type of the touch skip point fault occurring in the practical application of the user, the real experience of the user is fully considered, and therefore the after-touch skip point fault is conveniently analyzed according to the data of the touch event when the skip point fault occurs, the after-touch skip point fault is solved in a more targeted mode, and the user experience is further improved.

Alternatively, the eleventh offset threshold and the twelfth offset threshold may each be 120 pixels to 180 pixels.

Alternatively, the second time difference threshold may be 40ms to 60 ms.

Optionally, the number of preset groups may be 3 or 4.

Optionally, the preset time duration may be 490ms to 510 ms.

In a second aspect, the present application provides an apparatus, which is included in an electronic device, and which has a function of implementing the behavior of the electronic device in the first aspect and the possible implementation manners of the first aspect. The functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above-described functions. Such as a receiving module or unit, a processing module or unit, etc.

In a third aspect, the present application provides an electronic device, comprising: a processor, a memory, and an interface; the processor, the memory and the interface cooperate with each other to enable the electronic device to perform any one of the methods of the first aspect.

In a fourth aspect, the present application provides a chip comprising a processor. The processor is adapted to read and execute the computer program stored in the memory to perform the method of the first aspect and any possible implementation thereof.

Optionally, the chip further comprises a memory, and the memory is connected with the processor through a circuit or a wire.

Further optionally, the chip further comprises a communication interface.

In a fifth aspect, the present application provides a computer-readable storage medium, in which a computer program is stored, and when the computer program is executed by a processor, the processor is enabled to execute any one of the methods in the technical solutions of the first aspect.

In a sixth aspect, the present application provides a computer program product comprising: computer program code for causing an electronic device to perform any of the methods of the first aspect when the computer program code runs on the electronic device.

Drawings

Fig. 1 is a block diagram of a software structure of an example of an electronic device according to an embodiment of the present disclosure;

fig. 2 is a schematic diagram illustrating modules involved in a touch function of an electronic device according to an embodiment of the present disclosure;

FIG. 3 is a schematic diagram of an exemplary screen coordinate system of a mobile phone according to an embodiment of the present disclosure;

FIG. 4 is a diagram illustrating exemplary data for a press-to-report point according to an embodiment of the present disclosure;

FIG. 5 is a diagram illustrating an example of data for raising a report point according to an embodiment of the present disclosure;

FIG. 6 is a diagram illustrating an example of mobile node data according to an embodiment of the present disclosure;

fig. 7 is a schematic flowchart illustrating an exemplary method for detecting a touch skip point fault according to an embodiment of the present disclosure;

fig. 8 is a schematic point reporting diagram corresponding to an example of a trip point fault in the abscissa direction according to the embodiment of the present application;

fig. 9 is a schematic flowchart of an exemplary method for detecting a trip point fault in the abscissa direction according to an embodiment of the present application;

fig. 10 is a schematic flowchart of another exemplary method for detecting a trip point fault in the abscissa direction according to an embodiment of the present application;

fig. 11 is a schematic point reporting diagram corresponding to an example of a trip point fault in the ordinate direction according to the embodiment of the present application;

FIG. 12 is a schematic diagram of an example of reporting points corresponding to a fixed-location continuous click skip point fault according to an embodiment of the present disclosure;

fig. 13 is a schematic flowchart of an example method for detecting a fixed-location continuous click skip fault according to an embodiment of the present application;

FIG. 14 is a schematic flowchart of another example of a method for detecting a fixed-location consecutive click skip fault according to an embodiment of the present disclosure;

fig. 15 is a schematic point reporting diagram corresponding to an example of a fixed-location quick-click trip-point fault according to the embodiment of the present disclosure;

FIG. 16 is a flowchart illustrating an example of a method for detecting a fixed-location quick click skip fault according to an embodiment of the present disclosure;

fig. 17 is a schematic flowchart of another detection method for a fixed-location quick click skip fault according to an embodiment of the present application;

fig. 18 is a schematic point reporting diagram corresponding to an example of a full-screen random touch skip point fault according to the present application;

fig. 19 is a schematic flowchart illustrating an example of a method for detecting a full-screen random touch skip fault according to an embodiment of the present application;

fig. 20 is a schematic point reporting diagram corresponding to a full-screen random simultaneous touch skip point fault according to an embodiment of the present application;

fig. 21 is a schematic flowchart illustrating an example of a method for detecting a full-screen random simultaneous touch skip fault according to an embodiment of the present application;

fig. 22 is a schematic point reporting diagram corresponding to an example of a sustained touch skip point fault according to an embodiment of the present disclosure;

fig. 23 is a schematic flowchart illustrating an example of a method for detecting a sustained touch skip point fault according to an embodiment of the present disclosure;

fig. 24 is a schematic point reporting diagram corresponding to an exemplary post-touch skip point fault according to an embodiment of the present disclosure;

fig. 25 is a schematic flowchart of an exemplary method for detecting a trip point fault after touch according to an embodiment of the present disclosure;

fig. 26 is a schematic structural diagram of an example of an electronic device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. In the description of the embodiments herein, "/" means "or" unless otherwise specified, for example, a/B may mean a or B; "and/or" herein is merely an association describing an associated object, and means that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of the present application, "a plurality" means two or more than two.

In the following, the terms "first", "second" and "third" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, features defined as "first", "second", "third" may explicitly or implicitly include one or more of the features.

Touch Panels (TPs), also called Touch panels, refer to panels capable of performing Touch input. The touch panel can be independently applied to realize a touch function, for example, the touch panel is applied to electronic equipment such as a notebook computer. The touch panel can also be used in combination with a display panel to form a touch display screen (also called a touch screen or a touch screen), which can realize both a display function and a touch function, and is applied to electronic devices such as mobile phones, tablet computers, wearable devices, teaching integrated machines, and the like.

No matter which electronic device is applied, the touch panel may have a touch jumping fault during the use process. The touch jumping points, also called jumping points, abnormal jumping points, touch screen jumping points, "ghost hands", "ghost touches" or automatic touches, refer to the phenomenon that when a user does not perform touch operation on a screen, a touch panel recognizes a report point and reports a touch event, so that a screen jumps, and an automatic operation application or control appears on the screen. The reason for the jumping point may be various, for example, the electric field of the touch panel is affected, for example, by static electricity, magnetic field, adhesion of conductive substance, temperature, humidity, physical damage, etc.; for example, the power supply voltage of the touch panel is unstable.

The touch jump failure may cause the user to fail to perform normal touch operation, and may even cause a loss to the user due to the screen automation application or control. Therefore, it is necessary to detect a touch skip point fault so as to analyze the cause of the touch skip point fault, and further solve the touch skip point fault or reduce the probability of the touch skip point fault. The method provided by the embodiment of the application aims to realize detection of the touch jumping point fault.

It can be understood that the method provided by the embodiment of the present application can be used for detecting a touch trip point fault of any electronic device with a touch function, including electronic devices such as a notebook computer with a touch panel and electronic devices with a touch screen. The following embodiments are all described by taking the method as an example for detecting the touch jumping point fault of the electronic device with the touch screen.

For convenience of understanding, before describing the method for detecting a touch skip point fault provided in the embodiment of the present application, a software architecture of an electronic device with a touch screen and a process of the electronic device implementing a touch function are described first.

The software system of the electronic device may employ a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present application takes an Android system with a layered architecture as an example, and exemplarily illustrates a software structure of the electronic device 100.

Fig. 1 is a block diagram of a software structure of an electronic device according to an embodiment of the present application. The layered architecture divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, an application layer, an application framework layer, an Android runtime (Android runtime) and system library, and a kernel layer from top to bottom. The application layer may include a series of application packages.

As shown in fig. 1, the application package may include camera, gallery, calendar, phone call, map, navigation, WLAN, bluetooth, music, video, short message, etc. applications.

The application framework layer provides an Application Programming Interface (API) and a programming framework for the application program of the application layer. The application framework layer includes a number of predefined functions.

As shown in FIG. 1, the application framework layers may include a window manager, content provider, view system, phone manager, resource manager, notification manager, and the like.

The window manager is used for managing window programs. The window manager can obtain the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.

The content provider is used to store and retrieve data and make it accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

The view system includes visual controls such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, the display interface including the short message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide communication functions of the electronic device. Such as management of call status (including connection, hangup, etc.).

The resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and the like.

The notification manager enables the application to display notification information in the status bar, can be used to convey notification-type messages, can disappear automatically after a brief dwell, and does not require user interaction. Such as a notification manager used to inform download completion, message alerts, etc. The notification manager may also be a notification that appears in the form of a chart or scroll bar text at the top status bar of the system, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, prompting text information in the status bar, sounding a prompt tone, vibrating the electronic device, flashing an indicator light, etc.

In addition, the application framework layer also includes related modules for reporting and managing events, such as an Event monitoring (Event Hub) module, an input reader (input reader) module, an input dispatcher (input dispatcher) module and the like.

The Android runtime comprises a core library and a virtual machine. The Android runtime is responsible for scheduling and managing an Android system.

The core library comprises two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. And executing java files of the application program layer and the application program framework layer into a binary file by the virtual machine. The virtual machine is used for performing the functions of object life cycle management, stack management, thread management, safety and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface managers (surface managers), media libraries (media libraries), three-dimensional graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), and the like.

The surface manager is used to manage the display subsystem and provide a fusion of the 2D and 3D layers for multiple applications.

The media library supports a variety of commonly used audio, video format playback and recording, and still image files, among others. The media library may support a variety of audio-video encoding formats, such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, and the like.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

The 2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver. In addition, the kernel layer may further include a touch signal processing module, a touch data generation module, a log (log) generation module, a communication module, and the like. The communication module may be a wired communication module or a wireless communication module.

In addition, the electronic device further includes a hardware layer. The hardware layer may include a motherboard, a touch panel, a touch chip, an accessory, and the like. The hardware layer is matched with each layer of the software system to realize the touch function.

For example, fig. 2 is a schematic diagram of modules involved in a touch function in an electronic device according to an embodiment of the present disclosure. As shown in fig. 2, the structure and the module of the electronic device for implementing the touch function include: the touch panel 201 of the hardware layer, the touch signal processing module 202, the touch data generating module 203 and the log generating module 207 of the kernel layer, the event monitoring module 204, the input reading module 205 and the input distributing module 206 of the application framework layer, and the like.

The touch panel 201 is configured to generate a touch signal and report the generated touch signal to the touch signal processing module 202 of the kernel layer. The touch signal generated by the touch panel 201 may be a touch signal generated according to a touch operation of a user, or a touch signal generated due to a touch skip point fault. Optionally, the touch operation of the user includes, but is not limited to, a touch operation, a click operation, a slide operation, a long press operation (also referred to as a long press operation), and the like. The touch signal generated due to the touch skip point fault includes, but is not limited to, the generation of the touch signal due to the influence of the electric field of the touch panel, the generation of the touch signal due to the unstable power supply voltage of the touch panel, and the like.

The touch signal processing module 202 receives the touch signal, performs encapsulation processing on the touch signal, and outputs the encapsulated touch signal to the touch data generation module 203 of the kernel layer. Optionally, the touch signal processing module 202 may report the touch signal after the encapsulation processing to the touch data generating module 203 through an integrated circuit (I2C) Interface, a Mobile Industry Processor Interface (MIPI) or a Serial Peripheral Interface (SPI). The touch data generation module 203 performs normalization processing, data calibration, and other processing on the touch signal, and further generates data (input.c) of a touch event. It is understood that a user performs a touch operation to generate one or more touch events. One touch event corresponds to the operation of a touch object (e.g., a finger or a stylus), and one touch event corresponds to a set of data. For example, the user performs a slide-up operation on the screen, possibly with one finger or with multiple fingers. And generating a touch event corresponding to a group of data by the operation of each finger on the screen.

The touch data generation module 203 reports the generated data of the touch event to the event monitoring module 204 and the input reading module 205 of the application architecture layer for processing. After being processed by the event monitoring module 204 and the input reading module 205, the input distribution module 206 distributes the data to the corresponding application program in the application program layer, and the application program makes a corresponding response.

It is to be understood that, after the touch data generation module 203 generates the data of the touch event, the data of the touch event may be further sent to the log generation module 207. The log generation module 207 generates a log file according to the data of the touch event. Optionally, the touch data generating module 203 may send the data of the touch event to the log generating module 207 in real time, so that the log generating module 207 generates a log file; that is, each time the touch data generation module 203 generates data of one touch event, the touch data generation module 203 sends the data of the touch event to the log generation module 207, and the log generation module 207 writes part or all of the data of the touch event into a log file. The log file may be stored in a memory of the electronic device or may be transmitted to another electronic device, for example, to a server.

For ease of understanding, the data of the touch event is described below.

The data of each touch event at least comprises data of a press-down point (also called a press-down event) and data of a lift-up point (also called a lift-up event). The data of the press-down report point corresponds to the press-down operation of the user, that is, the finger or the stylus pen of the user contacts with the screen. The data of the lifted-up hit corresponds to a lifting operation by the user, that is, the user's finger or stylus or the like is off the screen. In addition, the data for each touch event may also include data for one or more mobile nodes (also referred to as mobile nodes). The data of the mobile report point corresponds to the contact operation or the movement operation of the user, namely, the finger or the stylus of the user contacts with the screen or moves along the screen. It is understood that the moving hit of a touch event is between the press hit and the lift hit in time.

The data of the press-down report point, the lift-up report point and each moving point comprises coordinates, time and event identification. The coordinates are used for representing the position of the report point in a preset coordinate system. For a mobile phone, the coordinates are used to represent the position of the newspaper point in the screen coordinate system of the mobile phone. For example, fig. 3 is a schematic diagram of a screen coordinate system of a mobile phone according to an embodiment of the present application. As shown in fig. 3, the screen coordinate system of the mobile phone includes an abscissa direction (i.e., an X coordinate direction) and an ordinate direction (i.e., a Y coordinate direction), the width direction of the mobile phone is the X coordinate direction, the length direction of the mobile phone is the Y coordinate direction, and the upper left corner of the screen is a coordinate 0 point when the mobile phone is held. Correspondingly, the coordinates of the newspaper point may include an X coordinate and a Y coordinate. The X coordinate is used for representing the position of the newspaper point in the X coordinate direction in the mobile phone screen coordinate system, and the Y coordinate is used for representing the position of the newspaper point in the Y coordinate direction in the mobile phone screen coordinate system. Alternatively, the X and Y coordinates of a newspaper point may be characterized in units of pixels (pixels).

The time of reporting is used for representing the time point of reporting.

The event identification may also be referred to as an event number, Tracking ID, or the like. The event identifier of the report point is used for representing the touch event to which the report point belongs.

In addition, the data of the press-down newspaper point and the data of the lift-up newspaper point also comprise an action identifier. Specifically, the data of the press-down point includes a press-down action identifier. The press action identifier is used for representing that the report point is a press report point. Illustratively, the pressing action identifier may be "BTN _ TOUCH DOWN", for example. The data of the lifting report point comprises a lifting action identifier, and the lifting action identifier is used for representing that the report point is the lifting report point. Illustratively, the pressing action identifier may be "BTN _ touchhup", for example.

It can be understood that one touch event corresponds to one event identifier, that is, the event identifiers of the press report point, the lift report point and each mobile report point of the same touch event are the same.

Optionally, the data of the press report point, the lift report point, and each mobile report point may further include other data such as a report point rate, which is not limited in this embodiment of the present application.

For example, fig. 4 is a schematic diagram of an example of data of a press-down point provided in the embodiment of the present application. As shown in fig. 3, the data of the hit point includes an X coordinate 401, a Y coordinate 402, an event identifier 403, a hit action identifier 404, a time 405, a hit rate 406, and the like of the hit point.

For example, fig. 5 is a schematic diagram of an example of data for raising a report point according to an embodiment of the present application. As shown in fig. 5, the data of the lifting waypoint includes an X coordinate 501, a Y coordinate 502, an event identifier 503, a lifting action identifier 504, a waypoint time 505, a waypoint rate 506, and the like of the lifting waypoint.

For example, fig. 6 is a schematic diagram of data of an example mobile node according to an embodiment of the present application. As shown in fig. 6, the data of the mobile report includes X coordinates 601, Y coordinates 602, an event identifier 603, a report time 605, a report rate 606, and the like of the mobile report.

The method for detecting a touch skip point fault provided by the embodiment of the application is used for processing data of a touch event generated by an electronic device with a structure shown in fig. 1 and 2 to detect the touch skip point fault. Specifically, the method provided in the embodiment of the present application is used for processing data (input.c) of a touch event generated by the touch data generation module 203 shown in the embodiment of fig. 2 to determine whether a touch skip point fault exists.

It should be noted that the method for detecting a touch skip point fault provided in the embodiment of the present application may be applied to an electronic device. The electronic device may be the electronic device having a touch function, that is, capable of generating data of a touch event, such as a terminal device; it may also be another electronic device, such as a server, communicatively connected to the electronic device generating the data of the touch event. The terminal device may be a mobile phone, a tablet computer, a wearable device, an in-vehicle device, an Augmented Reality (AR)/Virtual Reality (VR) device, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a Personal Digital Assistant (PDA), or the like. When the method provided by the embodiment of the application is applied to the terminal device, optionally, the terminal device can acquire the data of the touch event from the kernel layer in real time and process the data of the touch event so as to detect the touch skip point fault event. Optionally, the generated data of the touch event may also be stored in a memory in the form of an operation log, and the terminal device acquires the data of the touch event from the memory and processes the data of the touch event.

When the method provided by the embodiment of the application is applied to the server, the server can be a cloud server and can also be a physical server. Optionally, the electronic device generating the data of the touch event may upload the generated data of the touch event to a server in the form of an operation log, and the server processes the data of the touch event to detect a touch skip point fault event.

For convenience of description, the following embodiments all take an example in which the method for detecting a touch skip point fault is applied to a server, and take an electronic device that generates data of a touch event as a terminal device, specifically take a mobile phone as an example for description.

First, with reference to fig. 1 and fig. 2, a whole flow of the method for detecting a touch skip point fault (including a process of generating touch event data by a mobile phone and uploading the touch event data to a server) will be described. It can be understood that, in this embodiment, each module represents a module for implementing a certain function, which may be implemented by hardware, software, or a combination of software and hardware, and this application is not limited in any way. Referring to fig. 7, the detection process of the touch skip point fault includes:

s701, the touch panel generates a touch signal.

As described above, the touch signal generated by the touch panel may be a touch signal generated according to a touch operation of a user, or a touch signal generated due to a touch skip point fault.

S702, the touch panel reports the generated touch signal to the touch signal processing module.

And S703, the touch signal processing module receives the touch signal and packages the touch signal.

S704, the touch signal processing module sends the packaged touch signal to the touch data generating module.

S705, the touch data generation module performs normalization processing, data calibration and other processing on the packaged touch signal to generate data of the touch event.

And S706, the touch data generation module sends the generated data of the touch event to the log generation module.

And S707, the log generation module generates a log file according to the data of the touch event.

That is, the log generation module writes part or all of the data of each touch event into the log file. The data for the touch event in the log file may include data generated due to a touch skip fault.

S708, the log generation module sends the log file to the communication module.

And S709, the communication module sends the log file to a server.

Optionally, the log generating module may periodically package and send the generated log file to the communication module, and the communication module sends the log file to the server. Optionally, the log generating module may also package and send the log file to the server when the data volume in the log file reaches a preset value according to the data volume in the log file.

S710, the server receives the log file sent by the communication module and detects the touch jump point fault according to the data of the touch event in the log file.

In an embodiment, when the server detects a touch skip point fault according to the data of the touch event in the log file, the server may obtain data packets one by one from the log file, and process the data of the touch event in each data packet respectively to detect whether the touch skip point fault exists in the data packet. For a data packet without a touch jumping point fault, the server may delete the data packet to release the memory. For a data packet with a touch control jumping point fault, the server can prompt the fault and keep data of a moment event in the data packet so as to analyze the generation reason of the touch control jumping point fault according to the data at a later stage, thereby solving the touch control jumping point fault or reducing the probability of the occurrence of the jumping point fault and improving the user experience; and the whole process does not need manual intervention and has high intelligence.

Optionally, the server may obtain data of all report points within a preset time according to a preset rule to obtain a plurality of data packets, and then process the plurality of data packets respectively.

In an embodiment, the time periods occupied by all the reporting points in the log file may be divided according to a preset time duration to obtain a plurality of continuous time periods. And taking the data of the report point in each time period in a plurality of continuous time periods as a data packet, thereby obtaining a plurality of data packets. For example, the report points in the log file are sorted according to time, the time of the first report point is a1, and the time of the last report point is a2, the time period from a1 to a2 may be divided according to a preset time length Δ t to obtain time periods from a1 to a1 +/t, a1 +/Δ t to a1+2 Δ t, and a1+2 Δ t to a1+3 Δ t … …, to obtain data of all report points whose time is within a time period from a1 to a1 +/Δ t, to obtain a data packet 1, to obtain data of all report points whose time is within a time period from a1 +/Δ t to a1+2 Δ t, to obtain a data packet 2, to obtain data of all report points whose time is within a time period from a1+2 Δ t to a1+3 Δ t, to obtain a plurality of data packets 3 … ….

In another embodiment, the time when each report point is pressed in the log file may be used as a starting point to obtain data of all report points in a preset time length, so as to obtain a plurality of data packets. For example, with a time B1 of a first press report point in the log file as a starting point, obtaining data of all report points within a preset time duration Δ t after B1 to obtain a data packet 1, that is, obtaining data of all report points at the time of the report point within a time period B1 to B1 +/Δ t to obtain the data packet 1; taking the second time point B2 when the report point is pressed down in the log file as a starting point, acquiring data of all report points within a preset time length delta t after B2 to obtain a data packet 2, namely acquiring data of all report points within a time period from B2 to B2 +/delta t at the time point of acquiring the report point to obtain the data packet 2; and so on. Optionally, the first hit point and the second hit point … … may be first hit points and second hit points … … in a hit point list sorted according to a time sequence. The data packet acquired based on the method in the embodiment is used for touch jump fault detection, so that traversal of all touch event data in the log file can be realized, and the touch jump fault detection result is more accurate.

Of course, the acquisition of the data packet may also be realized by other methods, which is not limited in this application.

In addition, in the embodiment of the present application, according to different expressions of reporting points in the aspects of position, time, number and the like when a fault occurs, the touch skip point fault may be divided into an abscissa direction skip point fault, an ordinate direction skip point fault, a fixed position continuous click skip point fault, a fixed position fast click skip point fault, a full-screen random touch skip point fault, a full-screen random simultaneous touch skip point fault, a continuous touch skip point fault, a post-touch skip point fault and the like. The method provided by the embodiment of the application can determine whether one of the multiple types of touch-control skip point faults exists in the data packet according to the acquired touch-control data in each data packet, that is, whether one of the multiple types of touch-control skip point faults exists in the preset time corresponding to the data packet is determined. Therefore, when the reason of the touch jumping point fault is analyzed at the later stage, the analysis can be carried out based on the type of the touch jumping point fault, and the touch jumping point fault can be more targeted, so that the touch jumping point fault can be more accurately solved.

Different types of touch jump point faults can be detected by different specific methods. Optionally, for each data packet, a detection method of each type of touch skip point fault may be separately executed to determine whether the type of touch skip point fault exists in the data packet. Meanwhile, in the process of acquiring the data packet, the specific value of the preset duration can be selected according to actual requirements. In one embodiment, different preset durations can be set according to different types of touch skip point faults to be detected.

For convenience of description, in the following embodiments, a specific process of each type of touch skip point fault and a detection method thereof is described by taking a processing process of a server on data of a touch event (hereinafter, referred to as first touch data) in a certain data packet as an example. The processing procedure of the touch data in other data packets is the same as the procedure, and the description is not repeated.

The definitions and concepts involved in the embodiments of the present application are explained first:

the complete touch event refers to a touch event in which the press report point, the lift report point, and each moving point are included in the first touch data. It can be understood that, for a touch event, since the time of each moving point is between the time of pressing the touch point and the time of lifting the touch point, if the touch point is included in the first touch data, it can be said that the touch event is a complete touch event.

The incomplete touch event refers to a touch event in which at least one of a press hit, a lift hit, and each move hit is not included in the first touch data. Similarly, if any one of the press-down hit or the lift-up hit of an event is not included in the first touch data, it can be said that the touch event is an incomplete touch event.

The coordinate offset in the X coordinate direction is the absolute value of the difference between the X coordinates of two report points, i.e. | X ₁ -x ₂ |，x ₁ Representing the X coordinate, X, of one of two points ₂ Representing the X coordinate of the other.

The coordinate offset in the Y coordinate direction is the absolute value of the difference between the Y coordinates of two report points, i.e. | Y ₁ -y ₂ |，y ₁ Representing the Y coordinate, Y, of one of the two points ₂ Representing the Y coordinate of the other.

The touch duration refers to a time difference between a time point of raising and a time point of pressing a touch event, that is, the touch duration is t _up -t _down ，t _up The time of lifting the touch event, t _down And indicating the time of the touch event for pressing the report point.

The event interval refers to a time difference between a time point of a previous touch event in time sequence for raising a touch point and a time point of a next touch event in time sequence for pressing the touch point, namely, the event interval is t _down2 -t _up1 ，t _up1 Time, t, representing the point of touch up of the previous touch event in time sequence _down2 And indicating the time of the press report point of the next touch event.

The following description is made for each type of touch skip point fault and the detection method thereof:

1. trip point fault in the abscissa direction

The abscissa direction skip point fault is also called an abscissa skip point fault or a fixed row skip point fault, and the like, and refers to a complete touch event distributed along a certain horizontal row appearing for multiple times in a short time. Distributed along a certain row means that the position fluctuation of the complete touch events in the ordinate direction is small. The report points of the trip point fault in the abscissa direction are represented as report points in which touch events occur for multiple times in a fixed row, the coordinates of the report points are close, and the coordinate offset in the ordinate direction is small. In general, such a performance does not occur when a user performs normal touch operation.

In the embodiment of the present application, the position of the touch event may be represented by one or more of coordinates of a press-down point, a press-down coordinate, or a moving point in the touch event. For convenience of illustration, and to simplify the detection process of the touch skip point fault, in the following embodiments, the position of the touch event is represented by coordinates of a press-down point or a lift-up point.

Fig. 8 is a schematic point report diagram corresponding to an exemplary trip point fault in the abscissa direction according to an embodiment of the present disclosure. Each point in fig. 8 represents a press-down point of a complete touch event, and the time of the press-down points is within a certain time period, in this embodiment, the duration of the time period is 900 ms. As can be seen from fig. 8, the respective pixels in the figure are distributed along the horizontal line 801 in the figure, and the fluctuation in the ordinate direction is small. That is, a complete touch event with coordinates distributed along the horizontal line 801 occurs multiple times within 900ms, and thus, a trip point fault in the horizontal coordinate direction exists within the 900 ms.

For the trip point fault in the abscissa direction, the detection can be performed by the following method.

Fig. 9 is a schematic flowchart of an exemplary method for detecting a trip point fault in the abscissa direction according to an embodiment of the present application, and as shown in fig. 9, the method includes:

s901, determining at least one complete touch event in the first touch data according to the event identifiers and the action identifiers of the multiple report points within a preset time length.

The preset time length is the time length selected when the data packet is acquired in the above embodiment. In an embodiment of detecting the trip point fault in the abscissa direction, the preset time period may be 800ms to 1200 ms.

It is understood that the touch event corresponding to the first touch data may include a complete touch event or an incomplete touch event. The server may search the action identifier and the event identifier in the first touch data, and if there is a press report point (i.e., a report point with a press action identifier) and a lift report point (i.e., a report point with a lift action identifier) with the same event identifier, determine that the touch event corresponding to the event identifier is a complete touch event. The number of full touch events may be 1 or more.

Optionally, the server may extract data of a complete touch event from the first touch data according to the event identifier. The data of each complete touch event includes data (coordinates, time, event identifier, and action identifier) of a press-down touch point, a lift-up touch point, and each moving point in the touch event.

And the server determines whether the jumping point fault in the abscissa direction exists within a preset time length according to the data of the at least one complete touch event. Specifically, steps S902 to S907 are described below.

S902, determining whether the coordinates of the nth touch point and the adjacent touch point in the data of at least one complete touch event meet a first coordinate condition; wherein n is 1, 2, 3 … … m, and m is the total number of complete touch events in the first touch data.

The adjacent press report points refer to press report points adjacent to the nth press report point in the press report points of the at least one complete touch event.

Optionally, in this embodiment, the server may obtain the nth touch down point and the adjacent touch down point of the nth touch down point according to the time sequence of each touch down point of the complete touch event. It should be understood that, of the touch down points of at least one full touch event, the 1 st touch down point and the mth touch down point include 1 adjacent touch down point, and the other touch down points include 2 adjacent touch down points.

The first coordinate condition is used for representing that the difference between the coordinates of the nth press report point and the coordinates of the adjacent press report points is small in the vertical coordinate direction. Alternatively, the first coordinate condition may include that a coordinate offset amount of the nth touch down point and an adjacent touch down point in the Y coordinate direction is less than or equal to a first offset amount threshold. Alternatively, the first offset threshold may be 8 pixels to 12 pixels.

Optionally, as a possible implementation manner, the first coordinate condition may further include that a coordinate offset of the nth touch-down point and an adjacent touch-down point in the X coordinate direction is less than or equal to the second offset threshold. Alternatively, the second offset threshold may be 80 pixels to 120 pixels. In the implementation mode, the coordinate offset of the nth press report point and the coordinate offset of the adjacent press report point in the Y coordinate direction are limited, and the coordinate offsets of the nth press report point and the adjacent press report point in the X coordinate direction are further limited, so that the problem that the touch control of a user under some special conditions (for example, the touch control of the user is continuously marked along the abscissa direction when the touch control accuracy of a screen is detected) is mistakenly judged as the touch control skip point fault in the abscissa direction can be effectively avoided, and the detection accuracy of the touch control skip point fault in the abscissa direction is improved.

The first offset threshold is 8 pixels, and the second offset threshold is80pixel as an example, step S902 is that the server determines whether the coordinates of the nth touch down point and the adjacent touch down point satisfy y _down(n+1) -y _down(n) Less than or equal to 80 pixels and | x _down(n+1) -x _down(n) | is less than or equal to 80 pixels; wherein, y _down(n) Y coordinate, Y, representing the nth touch down point _down(n+1) Y-coordinate, x, representing adjacent press-down points _down(n) X coordinate, X, representing the nth touch down point _down(n+1) Representing the X coordinate of the adjacent press-down point.

If yes, executing step S903;

if not, go to step S906.

S903, the nth press report point is determined as the first target press report point.

S904, whether the number of the first target press report points is larger than or equal to a first preset number is judged.

Alternatively, the first preset number may be an integer of 4 to 6.

If the number of the first target press report points is greater than or equal to the first preset number, executing step S905;

if the number of the first target touch-down points is smaller than the first preset number, step S906 is executed.

S905, determining that a jumping point fault in the horizontal coordinate direction exists in the preset time length.

And S906, judging whether n is equal to m or not.

That is, it is determined whether each of the touch points of all the complete touch events has performed the above determination process.

If n is equal to m, go to step S907;

if n is smaller than m, let n be n +1, and return to step S902.

And S907, determining that no trip point fault in the horizontal coordinate direction exists in the preset time length.

Optionally, in an embodiment, before the step S902, the method may further include determining whether the total number of the complete touch events in the first touch data is greater than or equal to a first preset number, if so, executing the step S902, and if not, executing the step S907. Therefore, the judgment process can be simplified, and the algorithm operation efficiency can be improved.

Through research and analysis, the cross coordinate direction jumping point fault is a touch control jumping point fault occurring in the practical application of a user, the cross coordinate direction jumping point fault in the touch control data can be detected through the process, the type of the touch control jumping point fault occurring in the practical use of the user is matched with that of the touch control jumping point fault occurring in the practical use of the user, and the real experience of the user is fully considered, so that the analysis is conveniently performed according to the data of the touch control event when the jumping point fault occurs, the cross coordinate direction jumping point fault is more pertinently solved, and the user experience is further improved.

In the method for detecting the trip point fault in the horizontal coordinate direction, the position of the touch event is represented by the coordinates of the press report point. In another possible implementation, the location of the touch event may also be characterized by a lift-off hit. Fig. 10 is a schematic flowchart of another exemplary method for detecting a skip point fault in the abscissa direction according to an embodiment of the present application, and as shown in fig. 10, the method includes:

s1001, determining at least one complete touch event in the first touch data according to the event identifications and the action identifications of the report points in the preset time length.

S1002, determining whether the coordinates of the nth raised report point and the adjacent raised report point in the data of at least one complete touch event meet a second coordinate condition; wherein n is 1, 2, 3 … … m, and m is the total number of complete touch events in the first touch data.

The adjacent lifting report points refer to lifting report points which are adjacent to the nth lifting report point in the lifting report points of the at least one complete touch event.

The second coordinate condition is used for representing that the difference between the coordinates of the first lifting report point and the adjacent lifting report point is smaller in the vertical coordinate direction. Optionally, the second coordinate condition may include that a coordinate offset of the nth lifting report point and an adjacent lifting report point in the Y coordinate direction is less than or equal to the first offset threshold. Alternatively, the first offset threshold may be 8 pixels to 12 pixels.

Optionally, as a possible implementation manner, the first coordinate condition may further include that a coordinate offset of the nth lifting report point and an adjacent lifting report point in the X coordinate direction is less than or equal to the second offset threshold. Alternatively, the second offset threshold may be 80 pixels to 120 pixels. Similar to the embodiment shown in fig. 9, in this implementation manner, while limiting the coordinate offset of the nth lifting report point and the coordinate offset of the adjacent lifting report point in the Y coordinate direction, the coordinate offsets of the nth lifting report point and the adjacent lifting report point in the X coordinate direction are further limited, so that it is effectively avoided that a touch of a user under some special conditions is mistakenly determined as a touch skip point fault, and the detection accuracy of the touch skip point fault is improved.

Taking the first offset threshold as 8 pixels and the second offset threshold as 80 pixels as an example, step S1002 means that the server determines whether the coordinates of the nth lifting report point and the adjacent lifting report point satisfy | y |, simultaneously _up(n+1) -y _up(n) Less than or equal to 8 pixels and | x _up(n+1) -x _up(n) | < 80 pixel; wherein, y _up(n) Y-coordinate, Y, representing the nth lifting report _up(n+1) Y-coordinate, x, representing adjacent lift-off points _up(n) X-coordinate, X, representing the nth lifting report _up(n+1) Representing the X coordinate of the adjacent lift off point.

If the coordinates of the nth lifting report point and the adjacent lifting report point meet the second coordinate condition, executing step S1003;

if the coordinates of the nth lifting report point and the adjacent lifting report point do not satisfy the second coordinate condition, step S1006 is executed.

S1003, determining the nth lifting report point as a target lifting report point.

And S1004, judging whether the number of the target lifting report points is larger than or equal to a first preset number.

If the number of the target lifting report points is greater than or equal to the first preset number, executing step S1005;

if the number of the target lifting report points is less than the first preset number, step S1006 is executed.

S1005, determining that the jumping point fault in the horizontal coordinate direction exists in the preset time length.

S1006, judging whether n is equal to m.

That is, it is determined whether each of the lifting report points of all the complete touch events has performed the above determination process.

If n is equal to m, go to step S1007;

if n is smaller than m, let n be n +1, and return to step S1002.

And S1007, determining that no trip point fault in the horizontal coordinate direction exists in the preset time length.

The implementation manner is similar to the process shown in the embodiment of fig. 9, and the specific process, beneficial effects, and the like are not described herein again.

2. Trip point fault in ordinate direction

The vertical coordinate direction trip point fault is also called a vertical coordinate trip point fault or a fixed column trip point fault and the like, and means that a complete touch event distributed along a certain column appears for multiple times in a short time. Distributed along a certain column means that the position of the complete touch events fluctuates little in the abscissa direction. The report points of the jump point fault in the ordinate direction are represented as report points of a touch event which appears in a fixed column for multiple times, the coordinates of the report points are close, and the coordinate offset in the abscissa direction is small. In general, such an indication does not occur when a user performs normal touch operation.

Exemplarily, fig. 11 is a schematic point reporting diagram corresponding to a trip point fault in the ordinate direction provided in the embodiment of the present application. Each point in fig. 11 represents a touch down point of a complete touch event, and the time of the touch down points is within a certain time period, in this embodiment, the time period is 900 ms. As can be seen from fig. 11, the distribution of the respective pixels in the figure is distributed along the column 1101 in the figure, and the fluctuation in the abscissa direction is small. That is, within 900ms, a complete touch event with coordinates distributed along the column 1101 occurs many times, and thus, a trip point fault in the ordinate direction exists within the 900 ms.

The method of detecting a trip point failure in the ordinate direction is similar to the method of detecting a trip point failure in the abscissa direction, but is different in that the coordinate condition of the trip point failure in the ordinate direction is opposite to the threshold values for the coordinate offset amounts in the abscissa direction and the ordinate direction in the first coordinate condition or the second coordinate condition described above. In contrast to the embodiment shown in fig. 9, in the detection process of the ordinate-direction jump fault, the coordinate conditions of the ordinate-direction jump fault are that the coordinate offset of the nth touch down point from the adjacent touch down point in the abscissa direction is less than or equal to the first offset threshold (8 pixels to 12 pixels), and the coordinate offset of the nth touch down point from the adjacent touch down point in the ordinate direction is less than or equal to the second offset threshold (80 pixels to 120 pixels).

In addition, in the method for detecting the trip point fault in the same horizontal coordinate direction, in the process of detecting the trip point fault in the vertical coordinate direction, the position of the touch event can be represented by the coordinate of the press-down report point, and the position of the touch event can also be represented by the coordinate of the lift-up report point.

Meanwhile, a trip point fault in the ordinate direction is also a touch control trip point fault occurring in practical application of a user, the method provided by the embodiment realizes detection of the trip point fault in the abscissa direction in the touch control data, matches with the type of the touch control trip point fault occurring in practical use of the user, and fully considers the real experience of the user, so that analysis is conveniently performed according to data of a touch control event when the trip point fault occurs, the trip point fault in the ordinate direction is solved in a more targeted manner, and the user experience is further improved.

3. Fixed position continuous click skip fault

The fixed-position continuous click skip point fault is also called a fixed-position continuous lift-up and press-down skip point fault or a fixed-position continuous touch skip point fault and the like, and means that a plurality of complete touch events occur at a fixed position within a short time, the complete touch events are continuous (namely one complete touch event is finished, and the other complete touch event occurs), and the event interval between two complete touch events adjacent in time sequence is short. The fixed position continuous clicking of the report point of the skip point fault is represented by continuously pressing the report point, lifting the report point, pressing the report point and lifting the report point at the fixed position, and the like that a finger or a stylus pen and the like continuously clicks a screen at the fixed position. However, the frequency of occurrence of a full touch event in such a failure is higher than the frequency of normal continuous clicking operations by the user.

It will be appreciated that in this embodiment, the so-called "fixed position" may not be an absolutely fixed position, but a small area or region.

Fig. 12 is a schematic view of a report corresponding to a fixed-location continuous click skip point fault according to an embodiment of the present disclosure. Each point in fig. 12 represents a touch down point of a complete touch event, and it is known that the complete touch events are continuous, the event interval of two complete touch events adjacent in time sequence is short, and the touch down time of the complete touch events is within a certain time period. In this embodiment, the duration of the time period is 495 ms. As can be seen from fig. 12, the respective report points in the figure are distributed in the area 1201, and the coordinates of the report points fluctuate less in both the abscissa direction and the ordinate direction. That is, a plurality of consecutive complete touch events occur in the area 1201 within 495ms, and the event interval between two complete touch events adjacent in time sequence is short. Thus, there is a fixed position continuous click skip fault within this 495 ms.

For a fixed-location successive click skip fault, the detection can be performed by the following method.

Exemplarily, fig. 13 is a schematic flowchart of an example of a method for detecting a fixed-location continuous click skip fault according to an embodiment of the present application, and as shown in fig. 13, the method includes:

s1301, determining at least one complete touch event in the first touch data according to the event identifications and the action identifications of the report points in the preset time length.

The preset time length is the time length selected when the data packet is acquired in the above embodiment. In the fixed location continuous click skip fault detection embodiment, the preset duration may be 490ms to 510 ms.

The specific process of this step is the same as step S901 in the embodiment shown in fig. 9, and is not described herein again.

S1302, determining whether the coordinates of a press report point of an nth complete touch event and a press report point of an adjacent complete touch event in at least one complete touch event meet a third coordinate condition; wherein n is 1, 2, 3 … … m, and m is the total number of complete touch events in the first touch data.

The adjacent complete touch event refers to a complete touch event which is after the nth complete touch event and is adjacent to the nth complete touch event in time sequence in the at least one complete touch event. In other words, the press report point of the adjacent complete touch event is behind the lift report point of the nth complete touch event, and the press report point of the adjacent complete touch event is adjacent to the lift report point of the nth complete touch event.

Optionally, the server may determine, according to the event identifier and the time of the report point of each complete touch event, that the time of pressing the report point is after the time of lifting the report point of the nth touch event, and the time of pressing the report point is adjacent to the time of lifting the report point of the nth complete touch event, so as to determine the adjacent complete touch event, and further determine whether the third coordinate condition is satisfied.

The third coordinate condition is used for representing that the difference between the press report point of the nth complete touch event and the press report point of the adjacent complete touch event is smaller. Optionally, the third coordinate condition may include that a coordinate offset of a press point of the nth full touch event and a press point of an adjacent full touch event in the X coordinate direction is less than or equal to a third offset threshold, and a coordinate offset in the Y coordinate direction is less than or equal to a third offset threshold. Optionally, the third offset threshold and the fourth offset threshold may be equal or unequal. In one embodiment, the third offset threshold and the fourth offset threshold are equal and are each 128 pixels to 192 pixels.

Taking the third offset threshold and the fourth offset threshold as 150 pixels as an example, that is, the server determines whether the coordinates of the press-down report of the nth complete touch event and the press-down report of the adjacent complete touch event satisfy | x |, simultaneously _n+1(down) -x _n(down) Less than or equal to 150 pixels and y _n+1(down) -y _n(down) Less than or equal to 150 pixels; wherein x is _n(down) X coordinate, X, of press-down point representing nth full touch event _n+1(down) X-coordinate, y, of press-down points representing adjacent complete touch events _n(down) Y coordinate, Y, of press down point representing nth full touch event _n+1(down) A Y coordinate representing a press-down point of an adjacent full touch event.

If yes, executing step S1303;

if not, step S1307 is executed.

S1303, judging whether the event interval between the nth complete touch event and the adjacent complete touch event is smaller than or equal to a preset event interval threshold value.

That is, the server determines whether a time difference between a time point of raising the touch point of the nth complete touch event and a time point of pressing the touch point of the adjacent complete touch event is less than or equal to a preset event interval threshold.

Alternatively, the preset event interval threshold may be 16ms to 24 ms. Taking the preset event interval threshold as 22ms as an example, step S1303 is: judging whether the nth complete touch event and the adjacent complete touch event meet t _n+1(down) -t _n(up) Less than or equal to 22ms, wherein t is _n+1(down) Time of press touch point, t, representing adjacent complete touch event _n(up) And indicating the moment of the lifting report point of the nth complete touch event.

If the event interval between the nth complete touch event and the adjacent complete touch event is less than or equal to the preset event interval threshold, executing step S1304;

otherwise, step S1307 is executed.

S1304, determining the nth complete touch event as a first target event.

S1305, judging whether the number of the first target events is larger than or equal to a second preset number.

Alternatively, the second preset number may be an integer of 4 to 6.

If the number of the first target events is greater than or equal to the second preset number, executing step S1306;

if the number of the first target events is less than the second preset number, step S1307 is executed.

And S1306, determining that the fixed position continuous click skip point fault exists in the preset time.

S1307, judging whether n is equal to m.

That is, it is determined whether the above determination process is performed for each complete touch event.

If n is equal to m, go to step S1308;

if n is smaller than m, n is set to n +1, and the process returns to step S1302.

S1308, determining that no fixed position continuous click skip point fault exists in the preset time.

Optionally, in an embodiment, before the step S1302, it may further include determining whether the total number of the complete touch events in the first touch data is greater than or equal to a second preset number, if so, executing the step S1302, and if not, executing the step S1308. Therefore, the judgment process can be simplified, and the algorithm operation efficiency can be improved.

Through research and analysis, the fixed-position continuous click skip point fault is a touch control skip point fault occurring in the practical application of a user, the fixed-position continuous click skip point fault in the touch control data can be detected through the process, the fixed-position continuous click skip point fault is matched with the type of the touch control skip point fault occurring in the practical use of the user, the real experience of the user is fully considered, therefore, the analysis is convenient to be carried out according to the data of the touch control event when the skip point fault occurs, the fixed-position continuous click skip point fault is solved in a more targeted manner, and the user experience is further improved.

In the method for detecting the fixed position continuous click skip point fault, the position of the touch event is represented by the coordinates of the press report point. In another possible implementation, the location of the touch event may also be characterized by a lift-off hit. Exemplarily, fig. 14 is a schematic flowchart of another detection method for a fixed-location continuous click skip point fault according to an embodiment of the present application, and as shown in fig. 14, the method includes:

s1401, determining at least one complete touch event in the first touch data according to the event identifiers and the action identifiers of the multiple report points within a preset time length.

S1402, determining whether the coordinates of the lifting report point of the nth complete touch event and the lifting report point of the adjacent complete touch event in at least one complete touch event meet a fourth coordinate condition; wherein n is 1, 2, 3 … … m, and m is the total number of complete touch events in the first touch data.

The fourth coordinate condition is used for representing that the difference between the lifting report point of the nth complete touch event and the lifting report point of the adjacent complete touch event is smaller. Optionally, the fourth coordinate condition may include that a coordinate offset of the lifting report point of the nth complete touch event and the lifting report point of the adjacent complete touch event in the X coordinate direction is less than or equal to a third offset threshold, and a coordinate offset in the Y coordinate direction is less than or equal to the third offset threshold. The values of the third offset threshold and the fourth offset threshold may be the same as those of the embodiment shown in fig. 13.

Taking the third offset threshold and the fourth offset threshold as 150 pixels as an example, step S1402 is to say that the server determines whether the coordinates of the lifting report point of the nth complete touch event and the lifting report point of the adjacent complete touch event satisfy | x | _n+1(up) -x _n(up) Less than or equal to 150 pixels and y _n+1(up) -y _n(up) Less than or equal to 150 pixels; wherein x is _n(up) X coordinate, X, of a lift-off touch point representing the nth full touch event _n+1(up) X coordinate, y, of lift-off points representing adjacent complete touch events _n(up) Y coordinate, Y, of lift-off tick representing nth full touch event _n+1(up) A Y coordinate representing a lift-off touch point of an adjacent complete touch event.

If yes, go to step S1403;

if not, go to step S1407.

S1403, determining whether an event interval between the nth complete touch event and an adjacent complete touch event is less than or equal to a preset event interval threshold.

If the event interval between the nth complete touch event and the adjacent complete touch event is less than or equal to the preset event interval threshold, executing step S1404;

otherwise, step S1407 is executed.

And S1404, determining the nth complete touch event as a second target event.

S1405, judging whether the number of the second target events is larger than or equal to a second preset number.

If the number of the second target events is greater than or equal to the second preset number, executing step S1406;

if the number of the second target events is smaller than the second preset number, step S1407 is executed.

And S1406, determining that the fixed position continuous click skip point fault exists in the preset time.

S1407, judging whether n is equal to m.

If n is equal to m, go to step S1408;

if n is smaller than m, n is made n +1, and the process returns to step S1402.

And S1408, determining that no fixed position continuous click skip point fault exists within the preset time.

The implementation manner is similar to the process shown in the embodiment of fig. 13, and the specific process, beneficial effects, and the like are not described herein again.

4. Fixed position fast click skip fault

The fixed-position fast-click skip point fault is also called a fixed-position fast-lift-press skip point fault or a fixed-position fast-touch skip point fault, and the like, and means that a plurality of complete touch events occur at a fixed position within a short time, the complete touch events are continuous (that is, one complete touch event is finished, and another complete touch event occurs), and the touch duration of each complete touch event is short. The fixed position fast click of the report point of the skip point fault is represented by continuously pressing the report point, lifting the report point, pressing the report point and lifting the report point at the fixed position, like a screen is fast clicked at the fixed position by a finger or a stylus pen and the like. However, the frequency of occurrence of the complete touch event in such a failure is higher than the frequency of the normal fast click operation of the user, and the touch duration of the complete touch event is shorter than the touch duration of the normal fast click operation of the user.

Also, in the present embodiment, the so-called "fixed position" may not be an absolutely fixed position, but a small range or area.

Fig. 15 is a schematic view of a report corresponding to a fixed-location quick click skip point fault according to an embodiment of the present disclosure. Each point in fig. 15 represents a touch down point of a complete touch event, and knowing that the complete touch events are continuous, the touch duration of a plurality of complete touch events is relatively short, and the touch down time of the complete touch events is within a certain time period. In this embodiment, the duration of the time period is 495 ms. As can be seen from fig. 15, the respective pixels in the graph are distributed in the area 1501, and the coordinates of the pixels fluctuate little in both the abscissa direction and the ordinate direction. That is, multiple fast full touch events occur within region 1501 within 495ms, and thus, there is a fixed location fast click trip point failure within 495 ms.

For a fixed location quick click skip fault, detection may be performed by the following method.

Fig. 16 is a schematic flowchart of an example of a method for detecting a fixed-location quick click skip point fault according to an embodiment of the present application, and as shown in fig. 16, the method includes:

s1601, determining at least one complete touch event in the first touch data according to the event identifiers and the action identifiers of the multiple report points within a preset time length.

The preset time length is the time length selected when the data packet is acquired in the above embodiment. In the fixed location quick click skip fault detection embodiment, the predetermined duration may be 490ms to 510 ms.

This step is the same as step S901 in the embodiment shown in fig. 9, and is not described again here.

S1602, determining whether the coordinates of a press report point of an nth complete touch event and a press report point of an adjacent complete touch event in at least one complete touch event meet a fifth coordinate condition; wherein n is 1, 2, 3 … … m, and m is the total number of complete touch events in the first touch data.

The definition of the adjacent complete touch event and the determination method thereof are the same as those in the embodiments shown in fig. 13 and fig. 14, and are not described herein again.

The fifth coordinate condition is used for representing that the difference between the press report point of the nth complete touch event and the press report point of the adjacent complete touch event is smaller. Optionally, the fifth coordinate condition may include that a coordinate offset of a touch down point of the nth full touch event and a touch down point of an adjacent full touch event in the X coordinate direction is less than or equal to a fifth offset threshold, and a coordinate offset in the Y coordinate direction is less than or equal to a sixth offset threshold. The fifth offset threshold and the sixth offset threshold may be equal or unequal. In one embodiment, the fifth offset threshold and the sixth offset threshold are equal and are each 128 pixels to 192 pixels.

That is, the fifth coordinate condition may be the same as the third coordinate condition in the embodiment shown in fig. 13, and the process of determining whether the coordinates of the press report of the nth complete touch event and the press report of the adjacent complete touch event satisfy the fifth coordinate condition is not described herein again.

If the coordinates of the press report point of the nth complete touch event and the press report point of the adjacent complete touch event satisfy the fifth coordinate condition, executing step S1603;

if the coordinates of the press report point of the nth complete touch event and the press report point of the adjacent complete touch event do not satisfy the fifth coordinate condition, step S1607 is executed.

S1603, determining whether the touch duration of the nth complete touch event is less than or equal to a preset touch duration threshold.

That is, the server determines whether a time difference between a time of raising a report point and a time of pressing the report point of the nth complete touch event is less than or equal to a preset touch duration threshold.

Optionally, the preset touch duration threshold may be 16ms to 24 ms. Taking the preset touch duration threshold as 21ms as an example, step S1603 is to determine whether the nth complete touch event satisfies t _n(up) -t _n(down) Less than or equal to 21 ms; wherein, t _n(up) The moment of lifting the report point of the nth complete touch event, t _n(down) And indicating the time of the press point of the nth complete touch event.

If the touch duration of the nth complete touch event is less than or equal to the preset touch duration threshold, executing step S1604;

otherwise, step S1607 is performed.

And S1604, determining the nth complete touch event as a third target event.

S1605, judging whether the number of the third target events is larger than or equal to a third preset number.

Alternatively, the third preset number may be an integer of 4 to 6.

If the number of the third target events is greater than or equal to the third preset number, executing step S1606;

if the number of the third target events is less than the third preset number, step S1607 is executed.

S1606, determining that a fixed position quick click skip point fault exists in the preset time length.

S1607, judging whether n is equal to m or not.

If n is equal to m, go to step S1608;

if n is smaller than m, let n be n +1, and return to step S1602.

S1608, determining that no fixed position quick click trip point fault exists within the preset time length.

Optionally, in an embodiment, before the step S1602, it may further include determining whether the total number of the complete touch events in the first touch data is greater than or equal to a third preset number, if so, performing the step S1602, and if not, performing the step S1608. Therefore, the judgment process can be simplified, and the algorithm operation efficiency can be improved.

Through research and analysis, the fixed-position quick click skip point fault is a touch control skip point fault occurring in the practical application of a user, the fixed-position quick click skip point fault in the touch control data can be detected through the process, the fixed-position quick click skip point fault is matched with the type of the touch control skip point fault occurring in the practical use of the user, the real experience of the user is fully considered, therefore, the fixed-position quick click skip point fault is conveniently analyzed according to the data of the touch control event when the skip point fault occurs, the fixed-position quick click skip point fault is more pertinently solved, and the user experience is further improved.

According to the detection method of the fixed position quick click skip point fault, the position of the touch event is represented by the coordinates of the press report point. In another possible implementation, the location of the touch event may also be characterized by a lift-off hit. Fig. 17 is a schematic flowchart of another fixed-location quick click and skip fault detection method provided in an embodiment of the present application, and as shown in fig. 17, the method includes:

s1701, determining at least one complete touch event in the first touch data according to the event identifier and the action identifier of the plurality of report points within the preset time duration.

S1702, determining whether a coordinate of a lifting report point of an nth complete touch event and a lifting report point of an adjacent complete touch event in the at least one complete touch event satisfies a sixth coordinate condition; wherein n is 1, 2, 3 … … m, and m is the total number of complete touch events in the first touch data.

The sixth coordinate condition is used for representing that the difference between the lifting report point of the nth complete touch event and the lifting report point of the adjacent complete touch event is smaller. Optionally, the sixth coordinate condition may include that a coordinate offset of the lifting report point of the nth complete touch event and the lifting report point of the adjacent complete touch event in the X coordinate direction is less than or equal to a fifth offset threshold, and a coordinate offset in the Y coordinate direction is less than or equal to a sixth offset threshold.

The sixth coordinate condition may be the same as the fifth coordinate condition in the embodiment shown in fig. 16, and the process of determining whether the coordinates of the press-down report point of the nth complete touch event and the press-down report point of the adjacent complete touch event satisfy the sixth coordinate condition is not described herein again.

If yes, go to step S1703;

if not, go to step S1707.

S1703, determining whether the touch duration of the nth complete touch event is less than or equal to a preset touch duration threshold.

If the touch duration of the nth complete touch event is less than or equal to the preset touch duration threshold, executing step S1704;

otherwise, step S1707 is performed.

And S1704, determining the nth complete touch event as a fourth target event.

S1705, determining whether the number of the fourth target events is greater than or equal to a third preset number.

If the number of the fourth target events is greater than or equal to the third preset number, performing step S1706;

if the number of the fourth target events is less than the third preset number, step S1707 is executed.

S1706, determining that a quick click skip point fault exists in the preset time length.

S1707, judging whether n is equal to m.

If n is equal to m, go to step S1708;

if n is smaller than m, let n be n +1, and return to step S1702.

S1708, determining that no quick click skip point fault exists in the preset time.

The implementation manner is similar to the process shown in the embodiment of fig. 16, and the detailed process, beneficial effects, and the like are not described herein again.

5. Full screen random touch trip point fault

The full-screen random touch skip point fault is also called a full-screen random touch skip point fault and the like, and means that a plurality of complete touch events occur in a short time, the positions of the complete touch events are random and have no obvious rule, and the starting times of the complete touch events are relatively close. The touch points of the full-screen random touch show that the coordinates of the touch points are random without obvious rules, and the event interval between the touch events is small. In general, such a performance does not occur when a user performs normal touch operation.

For example, fig. 18 is a schematic point reporting diagram corresponding to an example of a full-screen random touch skip point fault according to an embodiment of the present disclosure. Each point in fig. 18 represents a press-down point of a complete touch event, and it is known that the intervals of the press-down points are small, and the time of the press-down points of the complete touch events is within a certain time period, in this embodiment, the time duration of the time period is 900 ms. As can be seen from FIG. 18, the entries in the graph are randomly distributed without obvious regularity. That is, complete touch events with randomly distributed coordinates occur multiple times within 900ms, and the interval of the touch down points of the complete touch events is small, so that a full-screen random touch skip point fault exists within 900 ms.

For a full-screen random touch skip point fault, the detection can be performed by the following method.

Fig. 19 is a schematic flowchart of an example of a method for detecting a full-screen random touch skip point fault according to an embodiment of the present application, and as shown in fig. 19, the method includes:

s1901, determining at least one complete touch event in the first touch data according to the event identifier and the action identifier of the multiple touch points within a preset duration.

The preset time length is the time length selected when the data packet is acquired in the above embodiment. In an embodiment of detecting a full-screen random touch skip point fault, the preset time may be 800ms to 1200 ms.

S1902, determining whether the coordinates of the nth touch down point and the adjacent touch down point in the data of at least one complete touch event meet a seventh coordinate condition; wherein n is 1, 2, 3 … … m, and m is the total number of complete touch events in the first touch data.

The method for defining and acquiring the adjacent report points is the same as the embodiment shown in fig. 9, and is not repeated herein.

The seventh coordinate condition is used for representing that the difference between the coordinates of the nth press report point and the adjacent press report point is large in the direction of the vertical coordinate, so that the randomness of the coordinates is reflected. Optionally, the seventh coordinate condition may include that a coordinate offset amount of the nth touch down point and an adjacent touch down point in the X coordinate direction is greater than or equal to a seventh offset threshold, and a coordinate offset amount in the Y coordinate direction is greater than or equal to an eighth offset threshold. The seventh offset threshold and the eighth offset threshold may or may not be equal. In one embodiment, the seventh offset threshold and the eighth offset threshold are equal and are each 128 pixels to 192 pixels.

Taking the seventh offset threshold and the eighth offset threshold as 180 pixels, step S1902 is that the server determines whether the coordinates of the nth touch down point and the adjacent touch down point satisfy | x | _down(n+1) -x _down(n) Less than or equal to 180pixel and y _down(n+1) -y _down(n) Less than or equal to 180 pixels; wherein x is _down(n) X coordinate, X, representing the nth touch down point _down(n+1) X-coordinate, y, representing adjacent press-down points _down(n) Y coordinate, Y, representing the nth touch down point _down(n+1) The Y coordinate of the adjacent press-down point is represented.

If yes, go to step S1903;

if not, go to step S1907.

S1903, determine whether the time difference between the nth touch down point and the adjacent touch down point is less than or equal to the first time difference threshold.

Alternatively, the first time difference threshold may be 24ms to 36 ms. Taking the first time difference threshold as 33ms as an example, the server determines whether the time of the nth touch down point and the time of the adjacent touch down point satisfy t _down(n+1) -t _down(n) Less than or equal to 33 ms; wherein, t _down(n+1) Indicating the time of adjacent press-down of a touch-down point, t _down(n) Indicating the time of the nth touch down point.

If yes, go to step S1904;

if not, go to step S1907.

S1904, the nth touch-down point is determined as the second target touch-down point.

S1905, determine whether the number of second target press hits is greater than or equal to a fourth predetermined number.

Optionally, the fourth preset number may be an integer from 4 to 6.

If the number of second target press touch points is greater than or equal to the fourth preset number, go to step S1906;

if the number of second target touch down points is less than the fourth predetermined number, step S1907 is executed.

S1906, determining that a full-screen random touch jumping point fault exists within the preset time.

S1907, judge whether n is equal to m.

If n is equal to m, go to step S1908;

if n is smaller than m, let n be n +1, and return to step S1902.

S1908, determining that no full-screen random touch jumping point fault exists within a preset time length.

Optionally, in an embodiment, before the step S1902, it may further be determined whether the total number of the complete touch events in the first touch data is greater than or equal to a fourth preset number, if so, the step S1902 is executed, and if not, the step S1908 is executed. Therefore, the judgment process can be simplified, and the operation efficiency of the algorithm can be improved.

Through research and analysis, the full-screen random touch control skip point fault is a touch control skip point fault occurring in the practical application of a user, the full-screen random touch control skip point fault in the touch control data can be detected through the process, the type of the full-screen random touch control skip point fault is matched with the type of the touch control skip point fault occurring in the practical use of the user, the real experience of the user is fully considered, therefore, the analysis is convenient to be carried out according to the data of the touch control event when the skip point fault occurs, the full-screen random touch control skip point fault is solved in a more targeted manner, and the user experience is further improved.

6. Full screen random simultaneous touch trip point fault

The full-screen random simultaneous touch skip point fault is also called a full-screen random touch simultaneous skip point fault or a full-screen random multi-point touch skip point fault and the like, and means that a plurality of complete touch events occur in a short time, a plurality of touch events (including complete touch events and incomplete touch events) occur at the same time at a certain moment, and the positions of the touch events occur randomly on a screen without obvious rules; this situation occurs multiple times with multiple touch events occurring simultaneously. The full-screen random simultaneous touch report point shows that the coordinates of the report points are random, no obvious rule exists, a plurality of report points of complete events exist in a short time, and the condition that a plurality of report points simultaneously appear at the same time (including pressing the report points, lifting the report points or moving the report points) occurs for a plurality of times. In general, such a performance does not occur when a user performs normal touch operation.

It should be understood that, in the present embodiment, the term "simultaneously" may not be absolutely simultaneous, but rather a certain small time range or time period.

Fig. 20 is a schematic view of a touch report corresponding to a full-screen random simultaneous touch skip point fault according to an embodiment of the present disclosure. Specifically, fig. 20 shows the report points in the data of the touch event of the mobile phone at a certain time. That is, the time of each report in fig. 20 is the same. In addition, it is known that the number of complete touch events is greater than 35 in a certain time period including the time of the touch points. In this embodiment, the duration of the time period is 2900 ms. As can be seen from fig. 20, the report points in the graph are randomly distributed, and there is no obvious rule, and at the same time, a plurality of report points appear at the same time. That is, within 2900ms, more than 35 full touch events occurred, and, at the time shown in fig. 20, more touch events occurred at the same time. Thus, there is a random simultaneous touch trip point failure at full screen within 2900 ms.

For a full-screen random simultaneous touch skip point fault, the detection can be performed by the following method.

Exemplarily, fig. 21 is a schematic flowchart of a method for detecting a full-screen random simultaneous touch skip point fault according to an embodiment of the present application, and as shown in fig. 21, the method includes:

s2101, at least one complete touch event in the first touch data is determined according to the event identifications and the action identifications of the multiple report points within a preset time length.

The preset time length is the time length selected when the data packet is acquired in the above embodiment. In an embodiment of detecting a full-screen random simultaneous touch trip point fault, the preset duration may be 2400ms to 3600 ms.

S2102, determine whether the number of complete touch events in the first touch data is greater than a first number threshold.

Alternatively, the first number threshold may be an integer from 24 to 36.

If the number of complete touch events in the first touch data is greater than the first number threshold, executing step S2103;

otherwise, step S2107 is executed.

S2103, acquiring all sub-time periods in a time period corresponding to a preset duration according to the time of the report points in the first touch data and the event identification, and acquiring the number of touch events in each sub-time period; the duration of the sub-period is less than the preset duration.

The sub-period refers to a time range determined with reference to a certain time. The sub-time period is used for determining the number of touch events occurring in the time period, and further determining whether a plurality of touch events occur at the same time in the following steps. The report points in the same sub-time period are considered to belong to the same time, namely, the report points appear at the same time. The duration of the sub-period can be set according to requirements. It can be understood that the smaller the duration of the sub-period is, the closer the report point in the sub-period is to the "simultaneous", and the more accurate the obtained result of the full-screen random simultaneous touch fault is. Optionally, the duration of the sub-period may be 80ms to 120 ms. The sub-time period is 80ms to 120ms, so that the accuracy of the result of the touch fault at the same time of the random full-screen touch is ensured, the calculation process of the algorithm is not too complex, and the detection efficiency is improved.

The division of the sub-period may be in various ways. In an embodiment, the time period corresponding to the preset time period may be divided according to the time periods of the sub-time periods to obtain a plurality of continuous time periods, that is, all the sub-time periods. The time period corresponding to the preset time length is also the time period corresponding to the data packet in the above embodiment. Assuming that the time period corresponding to the preset time length is B1-B1 +. DELTA.t, and the time length of the sub-time period is 100ms, in this embodiment, the divided sub-time periods include: b1+100ms, B1+200ms, B1+300ms, B1+400ms … …

In another embodiment, the time of each touch point in the first touch data may be used as a starting point of the sub-period, and all the sub-periods are obtained by dividing according to the duration of the sub-period. For example, in the first touch data, the time when the report point is pressed is: c1, C2, C3, and C4 … …, the divided sub-periods include: the sub-time period dividing method provided by the embodiment of C1+100ms, C2+100ms, C3+100ms, and C4+100ms … … can enable all the divided sub-time periods to include all the touch points in the first touch data, so that traversal of all touch events is realized in the detection process, and the accuracy of the detection result of the touch fault at the same time when the full screen is random is improved.

In this embodiment, the number of touch events includes the number of complete touch events and the number of incomplete touch events. Taking the number of touch events in a certain sub-time period as an example, the server may screen out the touch points whose time is in the sub-time period according to the time of each touch point in the first touch data and the event identifier, and count the number of touch events for the screened touch points according to the event identifier. It should be noted that, for the screened nodes, the nodes with the same event identifier are counted only once.

And S2104, determining the sub-time periods in which the number of touch events is greater than or equal to the second number threshold value in all the sub-time periods as target sub-time periods.

Alternatively, the second number threshold may be an integer from 3 to 5.

Taking the duration of the sub-period as 110ms and the second number threshold as 5 as an example, this step is also to determine whether the number of touch events in each 110ms in the preset duration is greater than or equal to 5. In other words, it is determined whether at least 5 touch events occur "simultaneously" in each 110ms of the preset duration. And if so, determining the sub-time period as a target sub-time period.

S2105, judging whether the ratio of the number of the target sub-time periods in all the sub-time periods is larger than a preset ratio or not.

That is, it is determined whether the ratio of the touch events occurring at least 5 touch events "at the same time" is greater than the preset ratio.

Alternatively, the preset proportion may be 40% to 60%.

If the ratio of the number of the target sub-time periods in all the sub-time periods is greater than the preset ratio, executing step S2106;

if the ratio of the number of the target sub-time periods in all the sub-time periods is less than or equal to the preset ratio, executing step S2107;

s2106, determining that a full-screen random simultaneous touch control skip point fault exists in the preset time.

S2107, determining that no full-screen random simultaneous touch jumping point fault exists within the preset time length.

Through research and analysis, the full-screen random simultaneous touch jumping point fault is a touch jumping point fault occurring in the practical application of a user, the full-screen random simultaneous touch jumping point fault in the touch data can be detected through the process, the type of the touch jumping point fault occurring in the practical use of the user is matched, the real experience of the user is fully considered, and therefore analysis is convenient to be performed according to the data of the touch event when the jumping point fault occurs, the full-screen random simultaneous touch jumping point fault is solved in a more targeted manner, and the user experience is further improved.

7. Sustained touch trip point failure

The continuous touch jumping fault is also called a long press jumping fault or a non-vanishing jumping fault, and the like, which means that the touch duration of a certain touch event in the touch data is very long. The report point of the continuous touch jump point fault shows that the time length of the report point data of a certain touch event is long.

It can be understood that when a fixed-position continuous touch skip point fault occurs in the mobile phone, the normal touch operation performed by the user may be affected, for example, the user does not respond when clicking the screen. In this case, the user may try several times and perform several touches. Research shows that when a continuous touch jumping point fault occurs, the report points generated due to the fault and the report points generated by the user touch can be expressed as follows: the time difference between the press-down point and the lift-up point of a certain touch event is large, another one or more touch events exist in a time period corresponding to the press-down time and the lift-up time of the touch event, and the coordinate range fluctuation of most touch events in the touch events is small. In general, such a performance does not occur when a user performs normal touch operation.

For example, fig. 22 is a schematic point report diagram corresponding to a continuous touch skip point fault according to an embodiment of the present disclosure. Specifically, fig. 22 shows the report points of touch events in a certain time period. In this embodiment, the duration of the time period is 9300 ms. It is understood that 2201, 2202, 2203, and 2204 in the figure each represent the touch event's touch point. Here, the tick at 2201 does not include the lift tick of the event, and the touch events at 2202, 2203, and 2204 are full touch events. As can be seen from fig. 22, the coordinate ranges of the touch points of the

touch events

2202, 2203 and 2204 in the graph fluctuate slightly. That is to say, the touch duration of the touch event corresponding to the report point 2201 is greater than 9300 ms. In the period of 9300ms, the fluctuation range of 75% of touch events in the graph is small. Thus, there is a sustained touch trip point fault within the 9300 ms.

For the sustained touch skip point fault, the detection can be performed by the following method.

It should be noted that, in this embodiment, the method for acquiring the first touch data includes: the method includes the steps that data of all report points in a preset time length are obtained by taking the time when a certain report point (hereinafter referred to as a second report point) is pressed in a log file as a starting point, and first touch data are obtained. That is to say, the starting point of the time period corresponding to the first touch data is the time when the second touch point is pressed, and the duration of the time period is the preset duration.

Exemplarily, fig. 23 is a schematic flowchart of a method for detecting a sustained touch skip point fault according to an embodiment of the present application, and as shown in fig. 23, the method includes:

s2301, determining whether a second lifting report point identical to the event identifier of the second pressing report point exists in the first touch data or not according to the event identifiers and the action identifiers of the plurality of report points within a preset time length.

The second lifting report point is also the lifting report point of the touch event corresponding to the second pressing report point. That is, the server determines whether the touch duration of the touch event of the second press-down point is greater than or equal to a preset duration.

The preset time length is the time length selected when the data packet is acquired in the above embodiment. In an embodiment of detecting the continuous touch skip point fault, the preset time may be 6400ms to 9600 ms.

If the first touch data has the second lift-off report point, executing step S2302;

if the second lift-off report point does not exist in the first touch data, go to step S2309;

s2302, determining at least one complete touch event in the first touch data according to the event identifications and the action identifications of the multiple report points within a preset time length.

S2303, determining whether coordinates of a press-down report point and a lift-up report point of an nth complete touch event in at least one complete touch event meet an eighth coordinate condition; and n is 1, 2, 3 … … m, where m is the total number of complete touch events in the first touch data.

The eighth coordinate condition is used for representing that the difference between the coordinates of the press report point and the lift report point of the nth complete touch event is smaller. Optionally, the eighth coordinate condition may include that a coordinate offset of the press-in touch point and the lift-off touch point of the nth full touch event in the X coordinate direction is less than or equal to a ninth offset threshold, and a coordinate offset in the Y coordinate direction is less than or equal to a tenth offset threshold. Optionally, the ninth offset threshold and the tenth offset threshold may be equal or unequal. In a specific embodiment, the ninth offset threshold and the tenth offset threshold are equal and are each 48 pixels to 72 pixels.

Taking the ninth offset threshold and the tenth offset threshold as 68 pixels, that is, the server determines whether the coordinates of the press-down report point and the lift-up report point of the nth complete touch event satisfy | x |, simultaneously _n(up) -x _n(down) Less than or equal to 68pixel and y _n(up) -y _n(down) Less than or equal to 68 pixel; wherein x is _n(up) X-seat of lifting report point for representing nth complete touch eventLogo, x _n(down) X coordinate, y, of press-down point representing nth full touch event _n(up) Y coordinate, Y, of lift-off tick representing nth full touch event _n(down) And a Y coordinate representing a press-down point of the nth full touch event.

If yes, go to step S2304;

if not, go to step S2308.

S2304, determining the nth complete touch event as a fifth target event.

S2305, obtaining a total number of touch events (hereinafter referred to as total number) in the first touch data.

S2306, determining whether the ratio of the number of the fifth target events to the total number is larger than or equal to a preset ratio threshold.

Alternatively, the preset proportional threshold may be 56% to 84%.

If the ratio of the number of the fifth target events to the total number of the fifth target events is greater than or equal to the preset ratio threshold, executing step S2307;

if the ratio of the number of the fifth target events to the total number of the fifth target events is smaller than the preset ratio threshold, step S2308 is executed.

S2307, determining that the continuous touch jumping point fault exists within the preset time.

S2308, judging whether n is equal to m.

If n is equal to m, go to step S2309;

if n is smaller than m, let n be n +1, and return to step S2303.

S2309, determining that no continuous touch jumping point fault exists within a preset time.

It can be understood that the time when each report point is pressed in the log file is respectively used as a starting point to acquire data of all report points in a preset time length to obtain a plurality of data packets, the processes from S2301 to S2309 are executed on each data packet, all touch events can be traversed, all continuous touch skip point faults in the touch data of the log file are determined, and the accuracy is high.

Through research and analysis, the continuous touch control skip point fault is a touch control skip point fault occurring in the practical application of a user, the continuous touch control skip point fault in the touch control data can be detected through the process, the continuous touch control skip point fault is matched with the touch control skip point fault type occurring in the practical use of the user, the real experience of the user is fully considered, therefore, the continuous touch control skip point fault is conveniently analyzed according to the data of the touch control event when the skip point fault occurs, the continuous touch control skip point fault is more pertinently solved, and the user experience is further improved.

8. Jump point fault after touch

The after-touch skip point fault is also called as a after-touch skip point fault or a touch-induced skip point fault and the like, and means that a user touches a screen, the screen automatically reports a touch event, the user does not touch the screen, and the screen does not report the touch event. The touch events occurring along with the touch of the user have random touch duration. Moreover, unlike the normal multi-touch of the user, the touch events occurring along with the user touch are at a greater distance from the touch events generated by the user touch and have a closer start time.

Research shows that when a jump point fault occurs after touch, point reporting can be represented as follows: the touch event detection method comprises the steps that a plurality of (at least 2) touch event press points appear in a group in a short time, in the group of the press points, the distance between the press points automatically reported by a screen and the coordinates of the press points generated by the touch of a user is large, and the difference between the press points automatically reported by the screen and the time when the press points generated by the touch of the user are small. In general, such a performance does not occur when a user performs normal touch operation.

For example, fig. 24 is a schematic point report diagram corresponding to a post-touch skip point fault according to an embodiment of the present application. Specifically, in fig. 24, one point represents a touch event touch down point, and the touch event touch down point is known to be within a certain short time period, in this embodiment, the time period is 495 ms. Note that, it is known that the time difference between the point 2401 and the point 2403 is small at both the point 2401 and the point 2402. As can be seen from the figure, the distance between the coordinates of point 2402 and point 2401 is longer, and the distance between point 2403 and point 2401 is longer. That is, within 495ms, point 2402, point 2403, and point 2401 appear in a group, and the coordinate distances between point 2402, point 2403, and point 2401 are long, and the time difference is small. Thus, there is a post-touch trip point failure within this 495 ms.

In one embodiment, in order to ensure the accuracy of the detection result of the post-touch skip point fault, the occurrence of the post-touch skip point fault may be determined when the above conditions continuously occur multiple times.

The following describes a method for detecting a jump point fault after touch with reference to the accompanying drawings.

As in the embodiment shown in fig. 23, in this embodiment, the method for acquiring the first touch data also includes: the method includes the steps that data of all report points in a preset time length are obtained by taking the time when a certain report point (hereinafter referred to as a second report point) is pressed in a log file as a starting point, and first touch data are obtained. That is to say, the starting point of the time period corresponding to the first touch data is the time when the second touch point is pressed, and the duration of the time period is the preset duration.

Exemplarily, fig. 25 is a schematic flowchart of a method for detecting a jump-point fault after touch according to an embodiment of the present application, and as shown in fig. 25, the method includes:

s2501, determining whether the coordinates of the second press report point and each other press report point meet a ninth coordinate condition according to the coordinates of each report point in a preset time length; the other press-down points refer to other press-down points in the first touch data except the first press-down point.

The preset time length is the time length selected when the data packet is acquired in the above embodiment. In an embodiment of detecting the jump point fault after the touch, the preset time period may be 490ms to 510 ms.

The ninth coordinate condition is used for representing that the distance between the second press-in point and the coordinates of each other press-in point is larger. In one embodiment, the ninth coordinate condition may include that the coordinate shift amount of the first drop-off point and each of the other drop-off points in the X coordinate direction is greater than or equal to an eleventh shift amount threshold, and the coordinate shift threshold in the Y coordinate direction is greater than or equal to a twelfth shift amount threshold. Optionally, the eleventh offset threshold and the twelfth offset threshold may be equal or not. In a specific embodiment, the eleventh offset threshold and the twelfth offset threshold are equal and are each 120 pixels to 180 pixels.

Taking the eleventh offset threshold and the twelfth offset threshold as 140 pixels, step S2501 means that the server determines whether the coordinates of the second drop-off point and each of the other drop-off points satisfy | x |, simultaneously _2(down) -x _s(down) | is less than or equal to 140 pixels and | y _2(down) -y _s(down) Less than or equal to 140 pixels; wherein x is _2(down) X-coordinate, X, representing a second press-down point _s(down) X-coordinate, y, representing any other press-down point _2(down) Y-coordinate, Y, representing a second click _s(down) The Y coordinate representing any other press-down point.

If yes, go to step S2502;

if not, go to step S2503.

S2502, determining whether the time difference between the time of the second press report point and the time of each other press report point is smaller than or equal to a second time difference threshold value or not according to the time of each report point in the preset time length.

Alternatively, the second time difference threshold may be 40ms to 60 ms.

If the time difference between the time of the second press-down point and the time of each other press-down point is less than or equal to the second time difference threshold, executing step S2503;

if the time difference between the time of the second press-down point and the time of each of the other press-down points is less than or equal to the second time difference threshold, step S2504 is executed.

S2503, determining that no post-touch skip point fault exists within the preset time.

S2504, determining the second press point and each other press point as a group of multi-point common touch points.

That is, when the conditions of step S2501 and step S2502 are satisfied once, it is determined that the one-time pseudo-touch-after-skip point failure has occurred.

S2505, judging whether the number of groups of the multi-point common touch report points is larger than or equal to a preset number of groups.

Optionally, the number of preset groups may be 3 or 4.

If the number of groups of the multi-point common touch report points is less than the preset number of groups, step S2506 is performed.

If the number of groups of the multi-point common touch report points is greater than or equal to the preset number of groups, executing step S2508;

s2506, acquiring third touch data within a preset time length with the moment of pressing a third touch point as a starting point; the third press report point is a press report point which is behind the second lift report point and is adjacent to the second lift report point in time sequence, and the second lift report point is a lift report point which has the same event identification with the second press report point.

S2507, taking the third touch data as the first touch data and the third touch point as the second touch point, and returning to execute step S2501.

S2508, determining that the post-touch skip point fault exists in the preset time.

Taking the preset number of groups as 4 as an example, that is, if suspected post-touch skip point faults occur for 4 times or more continuously, it is determined that the post-touch skip point faults occur within the preset time duration corresponding to the first touch data and within the preset time duration corresponding to the third touch data.

It can be understood that the time when each report point is pressed in the log file is respectively used as a starting point to obtain data of all report points in a preset time length to obtain a plurality of data packets, the processes from S2501 to S2508 are executed on each data packet, all touch events can be traversed, and all post-touch skip point faults in the touch data of the log file are determined, so that the accuracy is high.

Through research and analysis, the after-touch skip point fault is a touch control skip point fault occurring in the practical application of a user, the after-touch skip point fault in the touch control data can be detected through the process, the after-touch skip point fault is matched with the type of the touch control skip point fault occurring in the practical use of the user, and the real experience of the user is fully considered, so that the after-touch skip point fault can be conveniently analyzed according to the data of the touch control event when the skip point fault occurs, the after-touch skip point fault can be more specifically solved, and the user experience can be further improved.

The above details describe an example of a method for detecting a touch skip point fault according to an embodiment of the present application. It will be appreciated that the electronic device, in order to implement the above-described functions, comprises corresponding hardware and/or software modules for performing the respective functions. Those of skill in the art would readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed in hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, with the embodiment described in connection with the particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiment of the present application, the electronic device may be divided into function modules according to the method example, for example, the function modules may be divided into function modules corresponding to the functions, such as a detection unit, a processing unit, a display unit, and the like, or two or more functions may be integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation.

It should be noted that all relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

Please refer to fig. 26, which shows a structure of an electronic device according to an embodiment of the present application, where the electronic device may be a terminal device that generates data of a touch event in the embodiment of the present application, or may be a server. The electronic device includes: a processor 2601, a receiver 2602, a transmitter 2603, a memory 2604, and a bus 2605. The processor 2601 includes one or more processing cores, and the processor 2601 executes applications of various functions and information processing by running software programs and modules. The receiver 2602 and the transmitter 2603 may be implemented as one communication component, which may be a baseband chip. Memory 2604 is coupled to processor 2601 by bus 2605. The memory 2604 may be used for storing at least one program instruction, and the processor 2601 is used for executing the at least one program instruction to implement the technical solutions of the above embodiments. The implementation principle and technical effect are similar to those of the related embodiments of the method, and are not described herein again.

When the electronic device is turned on, the processor can read the software program in the memory, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent through the antenna, the processor carries out baseband processing on the data to be sent and then outputs baseband signals to a control circuit in the control circuit, and the control circuit carries out radio frequency processing on the baseband signals and then sends the radio frequency signals to the outside through the antenna in an electromagnetic wave mode. When data is sent to the electronic equipment, the control circuit receives radio-frequency signals through the antenna, converts the radio-frequency signals into baseband signals and outputs the baseband signals to the processor, and the processor converts the baseband signals into the data and processes the data.

Those skilled in the art will appreciate that fig. 26 shows only one memory and processor for ease of illustration. In a practical electronic device, there may be multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, and the like, which is not limited in this application.

As an alternative implementation manner, the processor may include a baseband processor and a central processing unit, the baseband processor is mainly used for processing communication data, and the central processing unit is mainly used for executing a software program and processing data of the software program. Those skilled in the art will appreciate that the baseband processor and the central processing unit may be integrated into one processor, or may be separate processors, interconnected through bus or other technologies. Those skilled in the art will appreciate that an electronic device may include multiple baseband processors to accommodate different network formats, multiple central processors to enhance its processing capabilities, and various components of the electronic device may be connected by various buses. The baseband processor may also be expressed as a baseband processing circuit or a baseband processing chip. The central processing unit may also be expressed as a central processing circuit or a central processing chip. The function of processing the communication protocol and the communication data may be built in the processor, or may be stored in the memory in the form of a software program, and the software program is executed by the processor to realize the baseband processing function. The memory may be integrated within the processor or may be separate from the processor. The memory includes a Cache, which may store frequently accessed data/instructions.

In the embodiments of the present application, the processor may be a general processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps, and logic blocks disclosed in the embodiments of the present application. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in a processor.

In the embodiment of the present application, the memory may be a nonvolatile memory, such as a Hard Disk Drive (HDD) or a solid-state drive (SS), and may also be a volatile memory (volatile memory), for example, a random-access memory (RAM). The memory is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, not limited thereto.

The memory in the embodiments of the present application may also be circuitry or any other device capable of performing a storage function for storing program instructions and/or data. The methods provided by the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions described in accordance with the embodiments of the application are all or partially generated when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a computer network, a network appliance, a user device, or other programmable apparatus. The computer instructions may be stored in, or transmitted from, a computer-readable storage medium to another computer-readable storage medium, for example, from one website, computer, server, or data center, over a wired (e.g., coaxial cable, fiber optics, Digital Subscriber Line (DSL), or wireless (e.g., infrared, wireless, microwave, etc.) network, the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device including one or more integrated servers, data centers, etc., the available medium may be magnetic medium (e.g., floppy disk, hard disk, magnetic tape), optical medium (e.g., digital video disc (digital video disc, DWD), or a semiconductor medium (e.g., SSD), etc.

The embodiment of the present application provides a computer program product, which, when running on an electronic device, enables the electronic device to execute the technical solutions in the above embodiments. The implementation principle and technical effect are similar to those of the related embodiments, and are not described herein again.

The embodiment of the present application provides a computer-readable storage medium, on which program instructions are stored, and when the program instructions are executed by an electronic device, the electronic device is enabled to execute the technical solutions of the above embodiments. The principle and technical effects are similar to those of the related embodiments, and are not described herein again.

In summary, the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for detecting a touch skip point fault is characterized by comprising the following steps:

acquiring first touch data of electronic equipment, wherein the first touch data comprises coordinates, time and event identifications of a plurality of report points within a preset time length, the event identifications are used for representing touch events to which the report points belong, the report points comprise press report points and lift report points, and the press report points and the lift report points have action identifications;

and determining whether a preset type of touch jumping point fault exists in the preset time according to the first touch data.

2. The method of claim 1, wherein the preset type of touch skip point fault is one of a first direction skip point fault, a fixed position continuous click skip point fault, a fixed position fast click skip point fault, a full screen random touch skip point fault, a continuous touch skip point fault, or a full screen random simultaneous touch skip point fault.

3. The method of claim 2, wherein the determining whether a preset type of touch skip point fault exists within the preset duration according to the first touch data comprises:

determining at least one complete touch event in the first touch data according to the event identifications and the action identifications of the report points; the complete touch event refers to a touch event in which a press report point and a lift report point are both included in the first touch data;

and determining whether a preset type of touch jumping point fault exists in the preset time according to the data of the at least one complete touch event in the first touch data.

4. The method of claim 3, wherein the predetermined type of touch trip point fault is the first direction trip point fault, and the determining whether the predetermined type of touch trip point fault exists within the predetermined duration according to the data of the at least one complete touch event in the first touch data comprises:

determining whether the coordinates of a first press report point and an adjacent press report point meet a first coordinate condition or not according to the coordinates and the time of the press report point of the at least one complete touch event; the first press report point is a press report point of any one complete touch event, and the adjacent press report points are press report points adjacent to the first press report point in time sequence; the first coordinate condition comprises that the coordinate offset of the first press report point and the adjacent press report point in a second direction is less than or equal to a first offset threshold value, and the second direction is vertical to the first direction;

if the coordinates of the first press-in point and the adjacent press-in point meet the first coordinate condition, determining the first press-in point as a first target press-in point;

if the number of the first target press report points in the data of the at least one complete touch event is greater than or equal to a first preset number, determining that the first direction trip point fault exists in the preset duration.

5. The method of claim 3, wherein the predetermined type of touch trip point failure is the first direction trip point failure, and the determining whether the predetermined type of touch trip point failure exists within the predetermined duration according to the data of the at least one complete touch event in the first touch data comprises:

determining whether the coordinates of the first lifting report point and the adjacent lifting report point meet a second coordinate condition or not according to the coordinates and the time of the lifting report point of the at least one complete touch event; the first lifting report point is a lifting report point of any one complete touch event, and the adjacent lifting report points are lifting report points adjacent to the first lifting report point in time sequence; the second coordinate condition comprises that the coordinate offset of the first lifting report point and the adjacent lifting report point in a second direction is less than or equal to a first offset threshold, and the second direction is vertical to the first direction;

if the coordinates of the first lifting report point and the adjacent lifting report point meet the second coordinate condition, determining the first lifting report point as a target lifting report point;

and if the number of the target lifting report points in the data of the at least one complete touch event is greater than or equal to a first preset number, determining that the first direction jumping point fault exists in the preset duration.

6. The method of claim 4, wherein the first coordinate condition further comprises:

and the coordinate offset of the first press-in point and the adjacent press-in point in the first direction is less than or equal to a second offset threshold.

7. The method of claim 6, wherein the first direction is an abscissa direction in a screen coordinate system of the electronic device, and the second direction is an ordinate direction in the screen coordinate system of the electronic device; the first offset threshold is 8 pixels to 12 pixels, and the second offset threshold is 80 pixels to 120 pixels.

8. The method of claim 6, wherein the first direction is a vertical coordinate direction in a screen coordinate system of the electronic device, and the second direction is a horizontal coordinate direction in the screen coordinate system of the electronic device; the first offset threshold is 8 pixels to 12 pixels, and the second offset threshold is 80 pixels to 120 pixels.

9. The method according to any one of claims 4 to 8, wherein the first preset number is an integer from 4 to 6, and the preset duration is from 800ms to 1200 ms.

10. The method of claim 3, wherein the predetermined type of touch skip point fault is the fixed location continuous click skip point fault, and the determining whether the predetermined type of touch skip point fault exists within the predetermined duration according to the data of the at least one complete touch event in the first touch data comprises:

determining whether the coordinates of the press report point of the first complete touch event and the press report point of the adjacent complete touch event meet a third coordinate condition or not according to the coordinates, the time and the event identification of the report point of the at least one complete touch event, and determining whether the event interval of the first complete touch event and the adjacent complete touch event is smaller than or equal to a preset event interval threshold or not;

wherein the first complete touch event is any one of the complete touch events, and the adjacent complete touch event is a complete touch event which is adjacent to the first complete touch event in time sequence after the first touch event; the third coordinate condition comprises that the coordinate offset of the press report point of the first complete touch event and the press report point of the adjacent complete touch event in a first direction is less than or equal to a third offset threshold, the coordinate offset in a second direction is less than or equal to a fourth offset threshold, and the first direction is vertical to the second direction; the event interval refers to a time difference between a time point of raising a report point of a previous touch event and a time point of pressing a report point of a next touch event in a time sequence in the two touch events;

if the coordinates of the touch down point of the first complete touch event and the touch down point of the adjacent complete touch event meet the third coordinate condition, and the event interval between the first complete touch event and the adjacent complete touch event is smaller than or equal to the preset event interval threshold, determining the first complete touch event as a first target event;

and if the number of the first target events in the at least one complete touch event is greater than or equal to a second preset number, determining that the fixed-position continuous click skip point fault exists in the preset duration.

11. The method of claim 3, wherein the predetermined type of touch skip point fault is the fixed location continuous click skip point fault, and the determining whether the predetermined type of touch skip point fault exists within the predetermined duration according to the data of the at least one complete touch event in the first touch data comprises:

determining whether the coordinates of the raised report point of the first complete touch event and the raised report point of the adjacent complete touch event meet a fourth coordinate condition or not according to the coordinates, the time and the event identification of the report point of the at least one complete touch event, and determining whether the event interval between the first complete touch event and the adjacent complete touch event is less than or equal to a preset event interval threshold or not;

wherein the first complete touch event is any one of the complete touch events, and the adjacent complete touch event is a complete touch event adjacent to the first complete touch event in time sequence after the first complete touch event; the fourth coordinate condition comprises that the coordinate offset of the lifting report point of the first complete touch event and the lifting report point of the adjacent complete touch event in the first direction is less than or equal to a third offset threshold, the coordinate offset in the second direction is less than or equal to a fourth offset threshold, and the first direction is vertical to the second direction; the event interval refers to the time difference between the time of raising the report point of the previous touch event and the time of pressing the report point of the next touch event in the time sequence of the two touch events;

if the coordinates of the lifting report point of the first complete touch event and the lifting report point of the adjacent complete touch event meet the fourth coordinate condition, and the event interval between the first complete touch event and the adjacent complete touch event is less than or equal to the preset event interval threshold, determining the first complete touch event as a second target event;

and if the number of the second target events in the at least one complete touch event is greater than or equal to a second preset number, determining that the fixed-position continuous click skip point fault exists in the preset duration.

12. The method according to claim 10 or 11, wherein the third and fourth offset thresholds are each 128-192 pixels, the second predetermined number is an integer from 4 to 6, the predetermined event interval threshold is from 16ms to 24ms, and the predetermined duration is from 490ms to 510 ms.

13. The method of claim 3, wherein the predetermined type of touch trip point fault is the fixed location quick click trip point fault, and the determining whether the predetermined type of touch trip point fault exists within the predetermined duration according to the data of the at least one complete touch event in the first touch data comprises:

determining whether the coordinates of the press report point of the first complete touch event and the press report point of the adjacent complete touch event meet a fifth coordinate condition or not according to the coordinates, the time and the event identification of the report point of the at least one complete touch event, and determining whether the touch duration of the first complete touch event is less than or equal to a preset touch duration threshold or not;

wherein the first complete touch event is any one of the complete touch events, and the adjacent complete touch event is a complete touch event which is adjacent to the first complete touch event in time sequence after the first complete touch event; the fifth coordinate condition comprises that the coordinate offset of the press report point of the first complete touch event and the press report point of the adjacent complete event in a first direction is less than or equal to a fifth offset threshold, the coordinate offset in a second direction is less than or equal to a sixth offset threshold, and the first direction is vertical to the second direction; the touch duration refers to the time difference between the time of raising the report point and the time of pressing the report point of the touch event;

if the coordinates of the press report point of the first complete touch event and the press report point of the adjacent complete touch event meet the fifth coordinate condition, and the touch duration of the first complete touch event is less than or equal to the preset touch duration threshold, determining the first complete touch event as a third target event;

and if the number of the third target events in the at least one complete touch event is greater than or equal to a third preset number, determining that the fixed position quick click skip point fault exists in the preset duration.

14. The method of claim 3, wherein the predetermined type of touch trip point fault is the fixed location fast touch trip point fault, and the determining whether the predetermined type of touch trip point fault exists within the predetermined duration according to the data of the at least one complete touch event in the first touch data comprises:

determining whether the coordinates of the lifting report point of the first complete touch event and the lifting report point of the adjacent complete touch event meet a sixth coordinate condition or not according to the coordinates, the time and the event identification of the report point of the at least one complete touch event, and determining whether the touch duration of the first complete touch event is less than or equal to a preset touch duration threshold or not;

wherein the first complete touch event is any one of the complete touch events, and the adjacent complete touch event is a complete touch event which is adjacent to the first complete touch event in time sequence after the first complete touch event; the sixth coordinate condition includes that a coordinate offset between the lifting report point of the first complete touch event and the lifting report point of the adjacent complete event in a first direction is less than or equal to a fifth offset threshold, and a coordinate offset in a second direction is less than or equal to a sixth offset threshold, wherein the first direction is perpendicular to the second direction; the touch duration refers to the time difference between the time of raising the report point and the time of pressing the report point of the touch event;

if the coordinates of the lifting report point of the first complete touch event and the lifting report point of the adjacent complete touch event meet the sixth coordinate condition, and the touch duration of the first complete touch event is less than or equal to the preset touch duration threshold, determining the first complete touch event as a fourth target event;

if the number of the fourth target events in the at least one complete touch event is greater than or equal to a third preset number, determining that the fixed position quick click skip point fault exists within the preset duration.

15. The method according to claim 13 or 14, wherein the fifth offset threshold and the sixth offset threshold are both 128 pixels to 192 pixels, the third preset number is an integer from 4 to 6, the touch duration threshold is 16ms to 24ms, and the preset duration is 490ms to 510 ms.

16. The method of claim 3, wherein the predetermined type of touch skip point fault is the full-screen random touch skip point fault, and the determining whether the predetermined type of touch skip point fault exists within the predetermined duration according to the data of the at least one complete touch event in the first touch data comprises:

determining whether the coordinates of a first press report point and an adjacent press report point meet a seventh coordinate condition or not according to the coordinates and the time of the press report point of the at least one complete touch event, and determining whether the time difference between the time of the first press report point and the time of the adjacent press report point is less than or equal to a first time difference threshold value or not;

the first press point is a press point of any complete touch event, and the adjacent press points are press points adjacent to the first press point in time sequence; the seventh coordinate condition includes that the coordinate offset of the first press report point and the adjacent press report point in the first direction is greater than or equal to a seventh offset threshold, and the coordinate offset in the second direction is greater than or equal to an eighth offset threshold, and the first direction is perpendicular to the second direction;

if the coordinates of the first press-down point and the adjacent press-down point meet the seventh coordinate condition, and the time difference between the moment of the first press-down point and the moment of the adjacent press-down point is smaller than or equal to the first time difference threshold, determining the first press-down point as a second target press-down point;

and if the number of the second target touch down report points in the data of the at least one complete touch event is greater than or equal to a fourth preset number, determining that the full-screen random touch skip point fault exists within the preset time length.

17. The method of claim 16, wherein the seventh offset threshold and the eighth offset threshold are each 128 pixels to 192 pixels, the fourth predetermined number is an integer from 4 to 6, the first time difference threshold is 24ms to 36ms, and the predetermined duration is 800ms to 1200 ms.

18. The method according to claim 3, wherein the predetermined type of touch skip point fault is the full-screen random simultaneous touch skip point fault, and the determining whether the predetermined type of touch skip point fault exists within the predetermined duration according to the data of the at least one complete touch event in the first touch data comprises:

if the number of the complete touch events in the first touch event data is greater than or equal to a first number threshold, acquiring all sub-time periods in a time period corresponding to the preset time length according to the time of the multiple report points and the event identification, and acquiring the number of the touch events in each sub-time period; the duration of the sub-time period is less than the preset duration;

determining sub-time periods in which the number of touch events is greater than or equal to a second number threshold value in all the sub-time periods as target sub-time periods;

and if the number ratio of the target sub-time periods in all the sub-time periods is greater than a preset ratio, determining that the full-screen random simultaneous touch control skip point fault exists in the preset time length.

19. The method according to claim 18, wherein the obtaining all sub-time periods within the time period corresponding to the preset duration comprises:

and respectively taking the time when each report point in the report points is pressed as the starting point of a sub-time period, and obtaining all the sub-time periods according to the time length of the sub-time period and the time period corresponding to the preset time length.

20. The method according to claim 18, wherein the obtaining all the sub-time periods is continuous, and the obtaining all the sub-time periods in the time period corresponding to the preset duration comprises:

and dividing the time periods corresponding to the preset time periods according to the time lengths of the sub time periods to obtain all the sub time periods.

21. The method according to any one of claims 18 to 20, wherein the sub-period has a duration of 80ms to 120ms, the first quantity threshold is an integer of 24 to 36, the second quantity threshold is an integer of 3 to 5, the predetermined percentage is 40% to 60%, and the predetermined duration is 2400ms to 3600 ms.

22. The method according to claim 3, wherein the preset type of touch-control skip point fault is a continuous touch-control skip point fault, and the starting point of the time period corresponding to the preset duration is the time of the second press report point;

before determining whether a touch skip point fault of a preset type exists in the preset time period according to the data of the at least one complete touch event in the first touch data, the method further includes:

determining whether a preset type of touch jumping point fault exists within the preset duration according to the data of the at least one complete touch event in the first touch data, including:

determining whether the coordinates of the press-down report point and the lift-up report point of the first complete touch event meet an eighth coordinate condition; the first complete touch event is any one of the complete touch events, the eighth coordinate condition includes that coordinate offset of a press touch point and a lift touch point of the first complete touch event in a first direction is less than or equal to a ninth offset threshold, and coordinate offset in a second direction is less than or equal to a tenth offset threshold, and the first direction is perpendicular to the second direction;

if the coordinates of the press report point and the lift report point of the first complete touch event meet the eighth coordinate condition, determining the first complete touch event as a fifth target event;

acquiring the total number of touch events in the first touch data;

if the ratio of the number of the fifth target events to the total number in the at least one complete touch event is greater than or equal to a preset ratio threshold, determining that the continuous touch skip point fault exists in the preset time length.

23. The method of claim 22, wherein the ninth offset threshold and the tenth offset threshold are each 48-72 pixels, the preset duration is 6400-9600 ms, and the preset proportional threshold is 56-84%.

24. The method according to claim 1, wherein the preset type of touch-control trip point fault is a touch-back trip point fault, and the starting point of the time period corresponding to the preset duration is the time of the second press-down trip point;

determining whether a preset type of touch jumping point fault exists within the preset duration according to the first touch data includes:

determining whether the coordinates of the second press-in point and each other press-in point meet a ninth coordinate condition according to the coordinates and the time of the press-in point in the first touch data, and determining whether the time difference between the time of the second press-in point and each other press-in point is smaller than or equal to a second time difference threshold value;

the other press-down points are press-down points in the first touch data except the second press-down point; the ninth coordinate condition comprises that coordinate offset amounts of the second reported point and each of the other reported points in the first direction are greater than or equal to an eleventh offset threshold, and coordinate offset amounts in the second direction are greater than or equal to a twelfth offset threshold, wherein the first direction is perpendicular to the second direction;

if the coordinates of the second press-in point and each of the other press-in points satisfy the ninth coordinate condition, and the time difference between the time of the second press-in point and the time of each of the other press-in points is less than or equal to the second time difference threshold, determining the second press-in point and each of the other press-in points as a group of multi-point common-touch-in points;

acquiring third touch data within the preset duration with the moment of a third press report point as a starting point, taking the third press report point as a second press report point, executing the step of first touch data on the third touch data until the second press report point and each other press report point are not multi-point common touch report points, and determining the number of groups of the multi-point common touch report points; the third press report point is a press report point which is adjacent to a second lifting report point in time sequence after the second lifting report point, and the second lifting report point is a lifting report point with the same event identifier as the second press report point;

and if the group number of the multipoint common touch report points is greater than or equal to a preset group number, determining that the post-touch skip point fault exists in the preset time length.

25. The method of claim 24, wherein the eleventh offset threshold and the twelfth offset threshold are both 120-180 pixels, the second time difference threshold is 40-60 ms, the preset number of groups is 3 or 4, and the preset duration is 490-510 ms.

26. An electronic device, comprising: a processor, a memory, and an interface;

the processor, memory and interface cooperate to cause the electronic device to perform the method of any of claims 1-25.

27. A computer-readable storage medium, in which a computer program is stored which, when executed by a processor, causes the processor to carry out the method of any one of claims 1 to 25.