CN114995675B - Touch control jump point fault detection method, electronic equipment and readable storage medium - Google Patents

Touch control jump point fault detection method, electronic equipment and readable storage medium Download PDF

Info

Publication number
CN114995675B
CN114995675B CN202111166893.3A CN202111166893A CN114995675B CN 114995675 B CN114995675 B CN 114995675B CN 202111166893 A CN202111166893 A CN 202111166893A CN 114995675 B CN114995675 B CN 114995675B
Authority
CN
China
Prior art keywords
touch
point
report
event
touch event
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202111166893.3A
Other languages
Chinese (zh)
Other versions
CN114995675A (en
Inventor
韩帅
樊亮
冀焕霞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Honor Device Co Ltd
Original Assignee
Beijing Honor Device Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Honor Device Co Ltd filed Critical Beijing Honor Device Co Ltd
Priority to CN202111166893.3A priority Critical patent/CN114995675B/en
Publication of CN114995675A publication Critical patent/CN114995675A/en
Application granted granted Critical
Publication of CN114995675B publication Critical patent/CN114995675B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/03—Arrangements for converting the position or the displacement of a member into a coded form
    • G06F3/041—Digitisers, e.g. for touch screens or touch pads, characterised by the transducing means
    • G06F3/0416—Control or interface arrangements specially adapted for digitisers
    • G06F3/0418—Control or interface arrangements specially adapted for digitisers for error correction or compensation, e.g. based on parallax, calibration or alignment
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/03—Arrangements for converting the position or the displacement of a member into a coded form
    • G06F3/041—Digitisers, e.g. for touch screens or touch pads, characterised by the transducing means
    • G06F3/0416—Control or interface arrangements specially adapted for digitisers
    • G06F3/0418—Control or interface arrangements specially adapted for digitisers for error correction or compensation, e.g. based on parallax, calibration or alignment
    • G06F3/04186—Touch location disambiguation

Abstract

The embodiment of the application provides a detection method of touch jump point faults, 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, time and event identifications of a plurality of report points in preset time, the event identifications are used for representing touch events of the report points, the plurality of report points comprise a press report point and a lift report point, and the press report point and the lift report point have action identifications; and determining whether a touch jump point fault of a preset type exists in the preset duration according to the first touch data. The method provided by the invention can detect the touch control jump point fault and identify the type of the touch control jump point fault.

Description

Touch control jump point fault detection method, electronic equipment and readable storage medium
Technical Field
The application relates to the technical field of touch control, in particular to a detection method for touch control jump point faults, electronic equipment and a readable storage medium.
Background
With the rapid development of electronic technology, touch technology is widely applied to various electronic devices. For example, touch panels are integrated in the screens of the mobile phone, the tablet personal computer, the wearable device, the teaching integrated machine and other devices, so that the screen of the device has a touch function while displaying.
The electronic equipment with the touch function has the advantage that touch jumping point faults can occur in a probabilistic manner when the electronic equipment is applied. The touch jump points, also called jump points, abnormal jump points, "ghost hands", "ghost touches" or automatic touches, refer to that the touch panel recognizes a report point and reports a touch event when a user does not perform touch operation on the screen, so that the screen has phenomena such as picture jump, automatic operation application or control. The failure of the touch control jump point of the electronic equipment can cause that a user can not realize expected operation, so that normal use of the user is seriously influenced, and the user experience is poor. Therefore, it is necessary to identify and detect the touch jumping point fault, so as to analyze the cause of the touch jumping point fault, and further solve the touch jumping point fault.
Disclosure of Invention
The application provides a detection method, a detection device, electronic equipment, a chip, a computer readable storage medium and a computer program product for touch control jump point faults, which can identify and detect the touch control jump point faults.
In a first aspect, the present application provides a method for detecting a touch trip point fault, where the method includes:
acquiring first touch data of the electronic equipment, wherein the first touch data comprises coordinates, time and event identifications of a plurality of report points in preset time, the event identifications are used for representing touch events of the report points, the plurality of report points comprise a press report point and a lift report point, and the press report point and the lift report point have action identifications; and determining whether a touch jump point fault of a preset type exists in the preset duration according to the first touch data.
The touch control jumping point fault detection method provided by the first aspect can detect whether the touch control jumping point fault of the preset type exists in the preset time length, so that the generation reason of the touch control jumping point fault is analyzed in the later period, the probability of occurrence of the touch control jumping point fault is solved or reduced, and the user experience is improved; and the whole process does not need manual intervention, so that the intelligent performance is high. In addition, the implementation mode can detect the type of the touch control jump point fault, so that analysis can be performed based on the type of the touch control jump point fault when the reason of the touch control jump point fault is analyzed in the later period, the touch control jump point fault can be more accurately solved.
In a possible implementation manner, the preset type of touch jumping point fault includes at least one of a first direction jumping point fault, a fixed position continuous clicking jumping point fault, a fixed position quick clicking jumping point fault, a full screen random touch jumping point fault, a full screen random simultaneous touch jumping point fault, a continuous touch jumping point fault and a post-touch jumping point fault.
In a possible implementation manner, determining whether a touch jump point fault of a preset type exists in 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 plurality of report points; the complete touch event refers to a touch event that both a pressing report point and a lifting report point are included in the first touch data; and determining whether a touch jump point fault of a preset type exists in the preset duration according to the data of at least one complete touch event in the first touch data.
In a possible implementation manner, the preset type of touch jump point fault includes a first direction jump point fault, and determining whether the preset type of touch jump point fault exists in a preset duration according to data of at least one complete touch event in the first touch data includes:
determining whether the coordinates of a first pressed report point and adjacent pressed report points meet a first coordinate condition according to the coordinates and the time of the pressed report point of 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 refer to press report points adjacent to the first press report point time sequence; the first coordinate condition comprises that the coordinate offset of a first pressed report point and an adjacent pressed report point in a second direction is smaller than or equal to a first offset threshold value, and the second direction is perpendicular to the first direction; if the coordinates of the first pressed report point and the adjacent pressed report points meet the first coordinate condition, determining the first pressed report point as a first target pressed report point; if the number of the first target pressing points in the data of the at least one complete touch event is larger than or equal to the first preset number, determining that a first direction jump point fault exists in the preset time period.
In a possible implementation manner, the preset type of touch jump point fault includes a first direction jump point fault, and determining whether the preset type of touch jump point fault exists in a preset duration according to data of at least one complete touch event in the first touch data includes:
determining whether the coordinates of the first lifting report point and the adjacent lifting report point meet a second coordinate condition according to the coordinates and the time 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 smaller than or equal to a first offset threshold value, and the second direction is perpendicular to the first direction; if the coordinates of the first lifting report point and the adjacent lifting report points meet the 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 the first preset number, determining that a first direction jump point fault exists in the preset time period.
Optionally, the first direction is an abscissa direction in a screen coordinate system of the electronic device, the second direction is an ordinate direction in the screen coordinate system of the electronic device, and the touch jump point fault in the implementation mode is an abscissa direction fault.
The abscissa-direction jump fault is a touch jump fault in actual application of a user, detection of the abscissa-direction jump fault in touch data can be achieved through the two implementation modes, the detection is matched with the type of the touch jump fault generated in actual use of the user, real experience of the user is fully considered, analysis is conveniently conducted according to data of touch events when the jump fault occurs, the abscissa-direction jump fault is more specifically solved, and user experience is further improved. In the two implementations, the position of the touch event is represented by pressing the coordinates of the report point or lifting the coordinates of the report point, so that an algorithm can be simplified, and the efficiency of detecting the fault of the touch jump point can be improved.
Optionally, the first direction is an ordinate direction in a screen coordinate system of the electronic device, the second direction is an abscissa direction in the screen coordinate system of the electronic device, and the touch jump point fault in the implementation mode is an ordinate direction fault.
Similarly, the ordinate-direction jump point fault is a touch jump point fault in actual application of a user, detection of the ordinate-direction jump point fault in touch data can be achieved through the two implementation modes, the type of the touch jump point fault is matched with that of the touch jump point fault generated in actual use of the user, real experience of the user is fully considered, analysis is conveniently carried out according to data of a touch event when the jump point fault occurs, the jump point fault in the ordinate-direction is more specifically solved, and user experience is further improved.
Optionally, the first coordinate condition further includes:
the coordinate offset of the first pressed report point and the adjacent pressed report point in the first direction is smaller than or equal to the second offset threshold.
In the implementation manner, the coordinate offset of the first pressing report point and the coordinate offset of the adjacent pressing report points in the first direction are limited, and the coordinate offset of the first pressing report point and the coordinate offset of the adjacent pressing report point in the second direction are further limited, so that misjudgment of touch control (for example, continuous scribing along a certain direction when the accuracy of reporting the points of a screen is detected) of a user in some special cases as an abscissa-direction touch control jump point fault can be effectively avoided, and the detection accuracy of the first-direction touch control jump point fault is improved.
Alternatively, the first offset threshold may be 6 pixels (pixels) to 10 pixels.
Alternatively, the second offset threshold may be 80 pixel to 120 pixel.
Alternatively, the first preset number may be an integer of 4 to 6.
Alternatively, the preset duration may be 800ms to 1200ms.
In a possible implementation manner, the preset type of touch jump fault includes a fixed-position continuous click jump fault, and determining whether the preset type of touch jump fault exists in a preset duration according to data of at least one complete touch event in the first touch data includes:
determining whether the coordinates of the pressed report point of the first complete touch event and the pressed report point of the adjacent complete touch event meet a third coordinate condition 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 between the first complete touch event and the adjacent complete touch event is smaller than or equal to a preset event interval threshold value;
the first complete touch event is any complete touch event, and the adjacent complete touch event is a complete touch event adjacent to the first complete touch event time sequence after the first complete touch event; the third coordinate condition comprises that the coordinate offset of the pressing report point of the first complete touch event and the coordinate offset of the pressing report point of the adjacent complete touch event in the first direction is smaller than or equal to a third offset threshold value, the coordinate offset in the second direction is smaller than or equal to a fourth offset threshold value, and the first direction is perpendicular to the second direction; the event interval refers to the time difference between the time of lifting 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 in the two touch events;
If the coordinates of the pressed report point of the first complete touch event and the pressed 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 smaller than or equal to a preset event interval threshold value, determining the first complete touch event as a first target event;
if the number of the first target events in the at least one complete touch event is greater than or equal to the second preset number, determining that a fixed-position continuous click jump point fault exists in the preset duration.
In a possible implementation manner, the preset type of touch jump fault includes a fixed-position continuous click jump fault, and determining whether the preset type of touch jump fault exists in a preset duration according to data of at least one complete touch event in the first touch data includes:
according to the coordinates, the time and the event identification of the report point of at least one complete touch event, 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, and determining whether the event interval between the first complete touch event and the adjacent complete touch event is smaller than or equal to a preset event interval threshold;
The first complete touch event is any complete touch event, and the adjacent complete touch event is a complete touch event adjacent to the first complete touch event 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 smaller than or equal to a third offset threshold value, the coordinate offset in the second direction is smaller than or equal to a fourth offset threshold value, and the first direction is perpendicular to the second direction; the event interval refers to the time difference between the time of lifting 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 in 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 smaller than or equal to a preset event interval threshold value, determining the first complete touch event as a second target event;
if the number of the second target events in the at least one complete touch event is greater than or equal to the second preset number, determining that a fixed-position continuous click jump point fault exists in the preset duration.
The fixed-position continuous click jump fault is a touch jump fault in actual application of a user, detection of the fixed-position continuous click jump fault in touch data can be achieved through the two implementation modes, the type of the touch jump fault is matched with the type of the touch jump fault generated in actual use of the user, real experience of the user is fully considered, analysis is conveniently carried out according to data of touch events when the jump fault occurs, the problem of the fixed-position continuous click jump fault is solved more specifically, and user experience is further improved. In the two implementations, the position of the touch event is represented by pressing the coordinates of the report point or lifting the coordinates of the report point, so that an algorithm can be simplified, and the efficiency of detecting the fault of the touch jump point can be improved.
Alternatively, the third offset threshold and the fourth offset threshold may each 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 24ms.
Alternatively, the preset duration may be 490ms to 510ms.
In a possible implementation manner, the preset type of touch jump point fault includes a fixed-position quick click jump point fault, and determining whether the preset type of touch jump point fault exists in a preset duration according to data of at least one complete touch event in the first touch data includes:
Determining whether the coordinates of the pressed report point of the first complete touch event and the pressed report point of the adjacent complete touch event meet a fifth coordinate condition 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 smaller than or equal to a preset touch duration threshold;
the first complete touch event is any complete touch event, and the adjacent complete touch event is a complete touch event adjacent to the first complete touch event time sequence after the first complete touch event; the fifth coordinate condition comprises that the coordinate offset of the pressing report point of the first complete touch event and the coordinate offset of the pressing report point of the adjacent complete touch event in the first direction is smaller than or equal to a fifth offset threshold value, the coordinate offset in the second direction is smaller than or equal to a sixth offset threshold value, and the first direction is perpendicular to the second direction; the touch duration is the time difference between the time of lifting the report point and the time of pressing the report point of the touch event;
if the coordinates of the pressed report point of the first complete touch event and the pressed report points of the adjacent complete touch events meet a fifth coordinate condition, and the touch duration of the first complete touch event is smaller than or equal to a preset touch duration threshold, determining the first complete touch event as a third target event;
If the number of the third target events in the at least one complete touch event is greater than or equal to the third preset number, determining that the fixed-position quick click jump fault exists in the preset duration.
In a possible implementation manner, the preset type of touch jump point fault includes a fixed-position fast touch jump point fault, and determining whether the preset type of touch jump point fault exists in a preset duration according to data of at least one complete touch event in the first touch data includes:
according to the coordinates, time and event identification of the report point of at least one complete touch event, 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 sixth coordinate condition, and determining whether the touch duration of the first complete touch event is smaller than or equal to a preset touch duration threshold;
the first complete touch event is any complete touch event, and the adjacent complete touch event is a complete touch event adjacent to the first complete touch event 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 touch event in the first direction is smaller than or equal to a fifth offset threshold value, the coordinate offset in the second direction is smaller than or equal to a sixth offset threshold value, and the first direction is perpendicular to the second direction; the touch duration is the time difference between the time of lifting 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 points of the adjacent complete touch events meet a sixth coordinate condition, and the touch duration of the first complete touch event is smaller than or equal to a 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 the third preset number, determining that a fixed-position quick click jump fault exists in the preset duration.
The fixed-position quick click jump fault is a touch jump fault in actual application of a user, detection of the fixed-position quick click jump fault in touch data can be achieved through the process, the type of the touch jump fault is matched with the type of the touch jump fault generated in actual use of the user, real experience of the user is fully considered, analysis is conveniently carried out according to data of touch events when the jump fault occurs, the quick click jump fault of the fixed position is more specifically solved, and user experience is further improved.
Alternatively, the fifth offset threshold and the sixth offset threshold may each be 128 pixels to 192 pixels.
Alternatively, the third preset number may be an integer of 4 to 6.
Alternatively, the touch duration threshold may be 16ms to 24ms.
Alternatively, the preset duration may be 490ms to 510ms.
In a possible implementation manner, the preset type of touch jump point fault includes a full-screen random touch jump point fault, and determining whether the preset type of touch jump point fault exists in a preset duration according to data of at least one complete touch event in the first touch data includes:
determining whether the coordinates of a first pressed report point and the coordinates of adjacent pressed report points meet a seventh coordinate condition according to the coordinates and the moments of the pressed report points of at least one complete touch event, and determining whether the time difference between the moments of the first pressed report point and the coordinates of the adjacent pressed report points is smaller than or equal to a first time difference threshold;
the first press report point is a press report point of any one complete touch event, and the adjacent press report points refer to press report points adjacent to the first press report point time sequence; the seventh coordinate condition comprises that the coordinate offset of the first pressed report point and the adjacent pressed report point in the first direction is larger than or equal to a seventh offset threshold value, the coordinate offset in the second direction is larger than or equal to an eighth offset threshold value, and the first direction is perpendicular to the second direction;
If the coordinates of the first pressed report point and the adjacent pressed report points meet the seventh coordinate condition, and the time difference between the time of the first pressed report point and the time of the adjacent pressed report points is smaller than or equal to a first time difference threshold value, determining the first pressed report point as a second target pressed report point;
if the number of the second target pressing points in the data of the at least one complete touch event is larger than or equal to the fourth preset number, determining that a full-screen random touch jumping point fault exists in the preset time period.
The full-screen random touch jumping point fault is a touch jumping point fault in actual application of a user, the detection of the full-screen random touch jumping point fault in touch data can be realized through the process, the full-screen random touch jumping point fault is matched with the type of the touch jumping point fault generated in actual use of the user, and the real experience of the user is fully considered, so that analysis is conveniently carried out according to the data of a touch event when the jumping point fault occurs, the full-screen random touch jumping point fault is more specifically solved, and the user experience is further improved.
Alternatively, the seventh offset threshold and the eighth offset threshold may each be 128 pixels to 192 pixels.
Alternatively, the fourth preset number may be an integer of 4 to 6.
Alternatively, the first time difference threshold may be 24ms to 36ms.
Alternatively, the preset duration may be 800ms to 1200ms.
In a possible implementation manner, the preset type of touch jump point fault includes a full-screen random simultaneous touch jump point fault, and determining whether the preset type of touch jump point fault exists in a preset duration according to data of at least one complete touch event in the first touch data includes:
if the number of the complete touch events in the first touch data is greater than or equal to a first number threshold, acquiring all sub-time periods in a time period corresponding to the preset duration according to the time points of the plurality of report points and event identifiers, and acquiring the number of the touch events in each sub-time period; the duration of the sub-time period is smaller than the preset duration;
determining the sub-time periods with the number of touch events being greater than or equal to a second number threshold value in all the sub-time periods as target sub-time periods;
if the number duty ratio of the target sub-time periods in all the sub-time periods is larger than the preset duty ratio, determining that full-screen random simultaneous touch control jump point faults exist in the preset duration.
The full-screen random simultaneous touch jumping fault is a touch jumping fault which occurs in practical application of a user, detection of the full-screen random simultaneous touch jumping fault in touch data can be achieved through the process, the full-screen random simultaneous touch jumping fault is matched with the type of the touch jumping fault which occurs in practical use of the user, real experience of the user is fully considered, analysis is conveniently conducted according to data of touch events when the jumping fault occurs, the full-screen random simultaneous touch jumping fault is more specifically solved, and user experience is further improved.
In a possible implementation manner, acquiring all sub-time periods in a time period corresponding to a preset duration includes:
and respectively taking the time of pressing down the report points in the plurality of report points as the starting point of the sub-time period, and obtaining all the sub-time periods according to the duration of the sub-time period and the time period corresponding to the preset duration. The sub-time period dividing method provided in the implementation manner can enable all divided sub-time periods to comprise all pressed report points in the first touch data, so that traversal of all touch events is realized in the detection process, and accuracy of the touch fault detection result at the same time when the full screen is random is improved.
In a possible implementation manner, all sub-time periods are continuous, and all sub-time periods in a time period corresponding to a preset duration are acquired, including:
dividing the time period corresponding to the preset time period according to the time length of the sub-time period to obtain all the sub-time periods. The sub-time period dividing method provided by the implementation mode can be used for rapidly obtaining all the sub-time periods, and the algorithm efficiency is high.
Alternatively, the sub-period may have a duration of 80ms to 120ms.
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 duty cycle may be 40% to 60%.
Alternatively, the preset duration may be 2400ms to 3600ms.
In a possible implementation manner, the touch jump point fault of the preset type includes a continuous touch jump point fault, and the starting point of the time period corresponding to the preset duration is the moment of the second pressing report point;
according to the data of at least one complete touch event in the first touch data, before determining whether a touch jump point fault of a preset type exists in a preset time period, the method further comprises the following steps:
determining that a second lifting report point which is the same as the event identification of the second pressing report point does not exist in the first touch data;
according to the data of at least one complete touch event in the first touch data, determining whether a touch jump point fault of a preset type exists in a preset duration comprises the following steps:
determining whether coordinates of a pressed report point and a lifted 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 pressed report point and a lifted report point of the first complete touch event in a first direction is smaller than or equal to a ninth offset threshold value, the coordinate offset in a second direction is smaller than or equal to a tenth offset threshold value, and the first direction is perpendicular to the second direction;
If the coordinates of the pressed report point and the lifted 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 of the at least one complete touch event is greater than or equal to a preset ratio threshold, determining that a continuous touch jump point fault exists in a preset duration.
The continuous touch jumping point fault is a touch jumping point fault in actual application of a user, the continuous touch jumping point fault in touch data can be detected through the process, the type of the continuous touch jumping point fault is matched with the type of the touch jumping point fault in actual use of the user, and the real experience of the user is fully considered, so that analysis is conveniently carried out according to the data of a touch event when the jumping point fault occurs, the continuous touch jumping point fault is more specifically solved, and the user experience is further improved.
Alternatively, the ninth offset threshold and the tenth offset threshold may each be 48 pixel to 72 pixel.
Alternatively, the preset duration may be 6400ms to 9600ms.
Alternatively, the preset ratio threshold may be 56% to 84%.
In a possible implementation manner, the preset type of touch jump point fault includes a jump point fault after touch, and the starting point of a time period corresponding to the preset duration is the time of the second pressing report point;
Determining whether a touch jump point fault of a preset type exists in a preset duration according to the first touch data comprises the following steps:
according to the coordinates and the moments of the pressed report points in the first touch data, determining whether the coordinates of the second pressed report point and each other pressed report point meet a ninth coordinate condition, and determining whether the time difference between the moment of the second pressed report point and the moment of each other pressed report point is smaller than or equal to a second time difference threshold;
the other pressing report points refer to pressing report points except the second pressing report point in the first touch data; the ninth coordinate condition comprises that the coordinate offset of the second pressed report point and each other pressed report point in the first direction is larger than or equal to an eleventh offset threshold value, the coordinate offset in the second direction is larger than or equal to a twelfth offset threshold value, and the first direction is perpendicular to the second direction;
if the coordinates of the second pressed reporting point and each other pressed reporting point meet the ninth coordinate condition, and the time difference between the time of the second pressed reporting point and the time of each other pressed reporting point is smaller than or equal to a second time difference threshold value, determining the second pressed reporting point and each other pressed reporting point as a group of multi-point co-touch reporting points;
Acquiring third touch data in a preset time length taking the moment of a third pressing report point as a starting point, taking the third pressing report point as a second pressing report point, and executing first touch data on the third touch data until the second pressing report point and each other pressing report point are not multi-point co-touch report points, and determining the group number of the multi-point co-touch report points; the third pressing report point is a pressing report point adjacent to the second lifting report point time sequence after the second lifting report point, and the second lifting report point is a lifting report point with the same event identification as the second pressing report point;
if the number of groups of the multi-point co-touch report points is greater than or equal to the preset number of groups, determining that the jump point fault exists after touch within the preset duration.
The jump point fault after touch is a touch jump point fault in actual application of a user, detection of the jump point fault after touch in touch data can be achieved through the process, the jump point fault type is matched with the jump point fault type of the touch in actual use of the user, real experience of the user is fully considered, analysis is conveniently carried out according to data of a touch event when the jump point fault occurs, the jump point fault after touch is more specifically solved, and user experience is further improved.
Alternatively, the eleventh offset threshold and the twelfth offset threshold may each be 120 pixel to 180 pixel.
Alternatively, the second time difference threshold may be 40ms to 60ms.
Alternatively, the preset number of groups may be 3 or 4.
Alternatively, the preset duration may be 490ms to 510ms.
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 electronic device behavior in the first aspect and possible implementations of the first aspect. The functions may be realized by hardware, or may be realized by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above. Such as a receiving module or unit, a processing module or unit, etc.
In a third aspect, the present application provides an electronic device, the electronic device comprising: a processor, a memory, and an interface; the processor, the memory and the interface cooperate with each other such that the electronic device performs any one of the methods of the technical solutions of the first aspect.
In a fourth aspect, the present application provides a chip comprising a processor. The processor is configured to read and execute a 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, which when executed by a processor causes the processor to perform any one of the methods of the first aspect.
In a sixth aspect, the present application provides a computer program product comprising: computer program code which, when run on an electronic device, causes the electronic device to perform any one of the methods of the solutions of the first aspect.
Drawings
FIG. 1 is a block diagram of a software architecture of an example electronic device provided in an embodiment of the present application;
fig. 2 is a schematic diagram of a module related to a touch function in an electronic device according to an embodiment of the present application;
fig. 3 is a schematic diagram of a screen coordinate system of an example of a mobile phone according to an embodiment of the present application;
FIG. 4 is a schematic diagram of data of an example of a pressed report point provided in an embodiment of the present application;
FIG. 5 is a schematic diagram of an example of data of a lift-off report according to an embodiment of the present disclosure;
FIG. 6 is a schematic diagram of an example of mobile report data according to an embodiment of the present application;
fig. 7 is a flowchart of a method for detecting a touch trip point fault according to an embodiment of the present application;
FIG. 8 is a schematic diagram of reporting points corresponding to an example of a horizontal jump point fault provided in an embodiment of the present application;
FIG. 9 is a flowchart of a method for detecting an abscissa-direction jump fault according to an embodiment of the present disclosure;
FIG. 10 is a flowchart of another method for detecting a jump point fault in the abscissa direction according to an embodiment of the present application;
FIG. 11 is a schematic illustration of reporting points corresponding to an example of a vertical jump point fault provided in an embodiment of the present application;
FIG. 12 is a schematic illustration of reporting points corresponding to a fixed-position continuous click skip point fault according to an embodiment of the present disclosure;
FIG. 13 is a flowchart illustrating an exemplary method for detecting a fixed-position continuous click jump fault according to an embodiment of the present disclosure;
FIG. 14 is a flowchart of another method for detecting a continuous click jump fault at a fixed location according to an embodiment of the present application;
FIG. 15 is a schematic diagram of a report corresponding to a fixed-position fast click skip point fault according to an embodiment of the present disclosure;
FIG. 16 is a flowchart illustrating an exemplary method for detecting a fixed-position fast click jump fault according to an embodiment of the present disclosure;
FIG. 17 is a flowchart of another method for detecting a fixed-position fast click jump fault according to an embodiment of the present disclosure;
FIG. 18 is a schematic diagram of a report corresponding to a full-screen random touch skip point fault according to an embodiment of the present disclosure;
fig. 19 is a flowchart of a method for detecting a full-screen random touch skip point fault according to an embodiment of the present application;
FIG. 20 is a schematic diagram of a report corresponding to a full-screen random simultaneous touch skip point fault according to an embodiment of the present disclosure;
FIG. 21 is a flowchart of a method for detecting a full-screen random simultaneous touch jump fault according to an embodiment of the present disclosure;
fig. 22 is a schematic diagram of reporting points corresponding to a continuous touch skip point fault according to an embodiment of the present application;
fig. 23 is a flowchart of an example of a method for detecting a continuous touch trip point fault according to an embodiment of the present application;
FIG. 24 is a schematic diagram of a report corresponding to a jump point fault after touch according to an embodiment of the present application;
FIG. 25 is a flowchart illustrating an example of a method for detecting a jump 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. Wherein, in the description of the embodiments of the present application, "/" means or is meant unless otherwise indicated, for example, a/B may represent a or B; "and/or" herein is merely an association relationship describing an association object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In addition, in the description of the embodiments of the present application, "plurality" means two or more than two.
The terms "first," "second," "third," and the like, are used below 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, a feature defining "a first", "a second", or a third "may explicitly or implicitly include one or more such feature.
A Touch Panel (TP), also called a Touch panel, refers to a panel capable of realizing Touch input. The touch panel can be applied alone to realize a touch function, for example, to electronic devices such as a notebook computer. The touch panel can also be matched with the display panel to form a touch display screen (also called a touch screen or a touch screen), so that the display function can be realized, and the touch function can be realized, for example, the touch panel is applied to electronic equipment such as mobile phones, tablet computers, wearable equipment, teaching integrated machines and the like.
Regardless of the electronic device used, the touch panel may have a touch jump fault during use. The touch control jump points, also called jump points, abnormal jump points, touch screen jump points, "ghost hands", "ghost touches" or automatic touches, etc., refer to that the touch control panel recognizes the report point and reports the touch event when the user does not perform touch control operation on the screen, so that the screen has the phenomena of picture jump, automatic operation application or control, etc. The jump point may be caused by various reasons, for example, the electric field of the touch panel is affected, for example, by static electricity, a magnetic field, adhesion of conductive substances, temperature, humidity, physical damage, etc.; for example, the touch panel power supply voltage is unstable.
The failure of the touch jump point can cause that the user cannot execute normal touch operation, and even loss can be caused to the user due to automatic operation of the application or the control on the screen. Therefore, it is necessary to detect the touch jumping point fault, so as to analyze the cause of the touch jumping point fault, and further solve the touch jumping point fault or reduce the probability of the touch jumping point fault. The method provided by the embodiment of the application aims to detect the touch control jump point fault.
It can be appreciated that the method provided by the embodiment of the application can be used for detecting the touch jump point fault of any electronic device with a touch function, including electronic devices such as a notebook computer with a touch panel and the like, and electronic devices with a touch screen. The following embodiments are all described by taking the method for detecting a touch jump point fault of an electronic device with a touch screen as an example.
For easy understanding, before explaining the method for detecting a touch jump point fault provided in the embodiments of the present application, a software architecture of an electronic device with a touch screen and a process of implementing a touch function by the electronic device are first described.
The software system of the electronic device may employ a layered architecture, an event driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. In this embodiment, taking an Android system with a layered architecture as an example, a software structure of the electronic device 100 is illustrated.
Fig. 1 is a block diagram illustrating 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 with distinct roles and branches. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, from top to bottom, an application layer, an application framework layer, an Zhuoyun row (Android run) and system libraries, and a kernel layer, respectively. The application layer may include a series of application packages.
As shown in fig. 1, the application package may include applications for cameras, gallery, calendar, phone calls, maps, navigation, WLAN, bluetooth, music, video, short messages, etc.
The application framework layer provides an application programming interface (application programming interface, API) and programming framework for application programs of the application layer. The application framework layer includes a number of predefined functions.
As shown in FIG. 1, the application framework layer may include a window manager, a content provider, a view system, a telephony manager, a resource manager, a notification manager, and the like.
The window manager is used for managing window programs. The window manager can acquire 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 such data accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebooks, 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, a display interface including a text message notification icon may include a view displaying text and a view displaying a picture.
The telephony manager is for providing communication functions of the electronic device. Such as the management of call status (including on, hung-up, etc.).
The resource manager provides various resources for the application program, such as localization strings, icons, pictures, layout files, video files, and the like.
The notification manager allows the application to display notification information in a status bar, can be used to communicate notification type messages, can automatically disappear after a short dwell, and does not require user interaction. Such as notification manager is used to inform that the download is complete, message alerts, etc. The notification manager may also be a notification in the form of a chart or scroll bar text that appears on the system top status bar, 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, a text message is prompted in a status bar, a prompt tone is emitted, the electronic device vibrates, and an indicator light blinks, etc.
In addition, the application framework layer further comprises related modules of Event reporting and management, such as an Event monitor (Event Hub) module, an input reading (input reader) module, an input distributing (input dispatcher) module and the like.
Android runtimes include core libraries and virtual machines. Android run time is responsible for scheduling and management of the Android system.
The core library consists of 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. The virtual machine executes java files of the application program layer and the application program framework layer as binary files. The virtual machine is used for executing the functions of object life cycle management, stack management, thread management, security and exception management, garbage collection and the like.
The system library may include a plurality of functional modules. For example: surface manager (surface manager), media library (media library), three-dimensional graphics processing library (e.g., openGL ES), 2D graphics engine (e.g., SGL), etc.
The surface manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications.
Media libraries support a variety of commonly used audio, video format playback and recording, still image files, and the like. The media library may support a variety of audio and video encoding formats, such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, etc.
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 generating module, a log (log) generating 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 also includes a hardware layer. The hardware layer may include a motherboard, a touch panel, a touch chip, accessories, and the like. The hardware layer is matched with each layer of the software system to realize the touch function.
Fig. 2 is a schematic diagram of modules involved in a touch function in an electronic device according to an embodiment of the present application. As shown in fig. 2, a structure and a module for implementing a touch function of an electronic device include: a touch panel 201 of a hardware layer, a touch signal processing module 202, a touch data generating module 203 and a log generating module 207 of a kernel layer, an event monitoring module 204, an input reading module 205 and an input distributing module 206 of an 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 jump fault. Alternatively, 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. Touch signals generated due to touch trip faults include, but are not limited to, touch signals generated due to the influence of an electric field of a touch panel, touch signals generated due to the instability of a power supply voltage of the touch panel, and the like.
The touch signal processing module 202 receives the touch signal, encapsulates the touch signal, and outputs the encapsulated touch signal to the touch data generating module 203 of the kernel layer. Optionally, the touch signal processing module 202 may report the touch signal after the encapsulation to the touch data generating module 203 through an integrated circuit (inter-integrated circuit, I2C) interface, a mobile industry processor interface (mobile industry processor interface, MIPI) or a serial peripheral interface (Serial Peripheral Interface, SPI) or the like. The touch data generating module 203 performs normalization processing, data calibration processing, and the like on the touch signal, so as to generate data (input. C) of the touch event. It is understood that the user performs a touch operation to generate one or more touch events. One touch event corresponds to an operation of a touch contact object (such as a finger or a stylus pen, etc.), 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 a plurality of fingers. Each finger is operated on the screen to generate a touch event corresponding to a group of data.
The touch data generating 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 event is distributed to corresponding application programs in the application program layer by the input distribution module 206, and the application programs respond correspondingly.
It may be appreciated that, after the touch data generating module 203 generates the data of the touch event, the data of the touch event may be further sent to the log generating 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 generating module 203 generates data of one touch event, the data of the touch event is sent to the log generating module 207, and part or all of the data of the touch event is written into the log file by the log generating module 207. The log file may be stored in a memory of the electronic device or may be sent to other electronic devices, 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 pressing report point (also called a pressing event) and data of a lifting report point (also called a lifting event). The data of the pressed report point corresponds to the pressing operation of the user, namely, the finger of the user or the handwriting pen is contacted with the screen. The data of the raised report point corresponds to a lifting operation of the user, that is, the user's finger or the stylus or the like leaves the screen. In addition, the data for each touch event may also include data for one or more mobile reporting points (also referred to as mobile points). The data of the mobile report point corresponds to the contact operation or the mobile operation of the user, namely, the contact of the finger or the handwriting pen of the user with the screen or the movement along the screen. It will be appreciated that the mobile reporting point of a touch event is located between the press reporting point and the lift reporting point in time.
The data of the pressing report point, the lifting report point and each moving point comprise 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 for representing the position of the report point in a screen coordinate system of the mobile phone. Fig. 3 is a schematic diagram of a screen coordinate system of an example 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., X-coordinate direction) and an ordinate direction (i.e., 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 the coordinate 0 point when the mobile phone is being held. Correspondingly, the coordinates of the report point may include an X coordinate and a Y coordinate. The X coordinate is used for representing the position of the report 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 report point in the Y coordinate direction in the mobile phone screen coordinate system. Alternatively, the X and Y coordinates of the dots may be characterized in units of pixels (pixels).
The time of reporting the point is used for representing the time point when the reporting the point occurs.
Event identification may also be referred to as event number, tracking ID, etc. 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 pressing report point and the data of the lifting report point also comprise action identifiers. Specifically, the data of the pressing report point includes the pressing action identifier. The pressing action identifier is used for representing that the report point is a pressing report point. The press action identifier may be, for example, "btn_touch DOWN". The lifting action mark is used for representing that the report point is a lifting report point. The pressing action identifier may be, for example, "btn_touch UP".
It can be understood that one touch event corresponds to one event identifier, that is, the event identifiers of the pressing report point, the lifting report point and each mobile report point of the same touch event are the same.
Optionally, the data of the pressing report point, the lifting report point, and each mobile report point may further include other data such as report point rate, which is not limited in any way in the embodiment of the present application.
Fig. 4 is a schematic diagram of data of a pressed report point according to an embodiment of the present application. As shown in fig. 4, the data of the pressed report point includes an X coordinate 401, a Y coordinate 402, an event identifier 403, a pressed action identifier 404, a time 405, a report point rate 406, and the like of the pressed report point.
Fig. 5 is a schematic diagram of an example of lifting report data according to an embodiment of the present application. As shown in fig. 5, the data of the lift-off report point includes an X coordinate 501, a Y coordinate 502, an event identifier 503, a lift-off action identifier 504, a report point time 505, a report point rate 506, and the like of the lift-off report point.
Fig. 6 is a schematic diagram of data of an example mobile report according to an embodiment of the present application. As shown in fig. 6, the data of the mobile report point includes the mobile report point X coordinate 601, the Y coordinate 602, the event identifier 603, the report point time 605, the report point rate 606, and the like.
The method for detecting the touch jumping point fault is used for processing the data of the touch event generated by the electronic equipment with the structure shown in fig. 1 and 2 so as to detect the touch jumping point fault. Specifically, the method provided in the embodiment of the present application is used to process the data (input. C) of the touch event generated by the touch data generating module 203 shown in the embodiment of fig. 2, so as to determine whether there is a touch jump point fault.
It should be noted that, the method for detecting the touch control jump point fault provided by the embodiment of the application can be applied to electronic equipment. The electronic device may be the electronic device having the touch function, that is, capable of generating data of a touch event, for example, a terminal device; other electronic devices, such as servers, communicatively coupled to the electronic device generating the data of the touch event may also be used. The terminal device may be a mobile phone, a tablet computer, a wearable device, a vehicle-mounted device, an Augmented Reality (AR)/Virtual Reality (VR) device, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (personal digital assistant, PDA), or the like. When the method provided by the embodiment of the application is applied to the terminal equipment, optionally, the terminal equipment can acquire the data of the touch event from the kernel layer in real time, and process the data of the touch event to detect the touch jump point fault event. Alternatively, the generated data of the touch event may be stored in the memory in the form of an operation log, etc., and the terminal device may obtain the data of the touch event from the memory and process 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 or a physical server. Optionally, the electronic device that generates the data of the touch event may upload the generated data of the touch event to the server in a form of an operation log, and the server processes the data of the touch event to detect a touch trip fault event.
For convenience of explanation, the following embodiments take the application of the detection method of the touch jump point fault to the server as an example, and take the electronic device generating the data of the touch event as the terminal device, and specifically take the mobile phone as an example for explanation.
First, the whole flow of the method for detecting a touch jump fault (including the process of generating touch event data by a mobile phone and uploading the touch event data to a server) will be described with reference to fig. 1 and 2. It may be understood that, in this embodiment, each module represents a module that implements a certain function, which may be implemented by hardware, or may be implemented by software, or may be implemented by a combination of software and hardware, which is not limited in this application. Referring to fig. 7, the detection flow of the touch skip point fault includes:
s701, generating a touch signal by the touch panel.
As described above, the touch signal may be generated by the touch panel according to the touch operation of the user, or may be generated by the touch jump fault.
S702, the touch panel reports the generated touch signal to the touch signal processing module.
S703, the touch signal processing module receives the touch signal and encapsulates the touch signal.
S704, the touch signal processing module sends the packaged touch signal to the touch data generating module.
And S705, the touch data generation module performs normalization processing, data calibration and other processing on the packaged touch signals to generate data of touch events.
S706, the touch data generation module sends the generated data of the touch event to the log generation module.
S707, the log generating 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 of the touch event in the log file may include data generated due to a touch trip point failure.
S708, the log generating module sends the log file to the communication module.
S709, the communication module sends the log file to the server.
Alternatively, the log generating module may periodically package and send the generated log file to the communication module, where the communication module sends the log file to the server. Optionally, the log generating module may also package the log file and send the package to the server according to the size of the data amount in the log file when the data amount in the log file reaches a preset value.
S710, the server receives the log file sent by the communication module, and detects touch jumping point faults according to the data of the touch events in the log file.
In one embodiment, when the server detects a touch jump point fault according to the data of the touch event in the log file, the server may acquire data packets from the log file one by one, and process the data of the touch event in each data packet respectively, so as to detect whether the touch jump point fault exists in the data packet. For the data packet without touch control jump point fault, the server can delete the data packet to release the memory. For a data packet with touch jumping point faults, the server can prompt the faults and reserve the data of time events in the data packet so as to analyze the generation reasons of the touch jumping point faults according to the data at the later stage, thereby solving the touch jumping point faults or reducing the occurrence probability of the jumping point faults and improving the user experience; and the whole process does not need manual intervention, so that the intelligent performance is high.
Optionally, the server may obtain data of all the report points in the preset duration according to a preset rule, so as to obtain a plurality of data packets, and further process the plurality of data packets respectively.
In one embodiment, the time periods occupied by all the report points in the log file may be divided according to a preset duration, so as to obtain a plurality of continuous time periods. The data of the report points in each of a plurality of continuous time periods is taken as a data packet, so that a plurality of data packets are obtained. For example, the time of the first report point is A1, the time of the last report point is A2 in the log file according to the time sequence, the time periods of A1 to A2 may be divided according to a preset time period Δt to obtain time periods A1 to a1+Δt, time periods a1+Δt to a1+2 Δt, time periods a1+2 Δt to a1+3 Δt … … obtain the data of all report points whose time points are in time periods A1 to a1+Δt, obtain the data packet 1, obtain the data of all report points whose time points are in time periods a1+Δt to a1+2 Δt, obtain the data packet 2, obtain the data of all report points whose time points are in time periods a1+2 Δt to a1+3 Δt, and obtain the data packet 3 … ….
In another embodiment, the time of pressing the report point in the log file may be used as a starting point to obtain the data of all report points in the preset duration, so as to obtain a plurality of data packets. For example, taking the time B1 of the first pressing of the report point in the log file as a starting point, acquiring data of all report points within a preset time period delta t after B1 to obtain a data packet 1, namely acquiring data of all report points with the time of the report point being within a time period B1 to B1+ [ delta ] t to obtain the data packet 1; taking the time B2 of the second pressing report point in the log file as a starting point, acquiring data of all report points in a preset time delta t after B2 to obtain a data packet 2, namely acquiring data of all report points in a time period B2 to B2+ [ delta ] t at the time of the report point to obtain the data packet 2; and so on. Alternatively, the first and second press report points … … may be the first and second … … press report points in the time-ordered press report point list. The data packet obtained by the method in the embodiment is used for carrying out touch control jump point fault detection, so that the traversal of all touch control event data in the log file can be realized, and the result of the touch control jump point fault detection is more accurate.
Of course, the acquisition of the data packet may also be implemented by other methods, which is not limited in this application.
In addition, in the embodiment of the application, according to different expressions of the report points in terms of position, time, quantity and the like when faults occur, touch control jump point faults can be divided into horizontal coordinate direction jump point faults, vertical coordinate direction jump point faults, fixed position continuous click jump point faults, fixed position quick click jump point faults, full screen random touch control jump point faults, full screen random simultaneous touch control jump point faults, continuous touch control jump point faults, touch after-touch jump point faults and the like. According to the method provided by the embodiment of the invention, whether one touch jumping point fault in the multiple types exists in the data packet or not can be determined according to the acquired touch data in each data packet, namely whether one touch jumping point fault in the multiple types exists in the preset duration corresponding to the data packet or not is determined. Therefore, when the reason of the touch jumping point fault is analyzed in the later period, the analysis can be performed based on the type of the touch jumping point fault, the pertinence is better, and the touch jumping point fault can be more accurately solved.
Different types of touch jump faults can be detected by different specific methods. Optionally, for each data packet, a method for detecting a touch skip point fault of each type may be performed separately, so as to determine whether the touch skip point fault of the type 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 may be set according to different types of touch jump faults to be detected.
For convenience of explanation, in the following embodiments, a specific process of each type of touch jump point fault and a detection method thereof will be described by taking a processing procedure of a server to data of a touch event in a certain data packet (hereinafter referred to as first touch data) as an example. The processing procedure of touch data in other data packets is the same as the processing procedure, and the description is not repeated.
First, definitions and concepts referred to in the embodiments of the present application will be described:
the complete touch event refers to a touch event that a press report point, a lift report point and each movement 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 report point and the time of lifting the report point, if the press report point and the lift report point are both included in the first touch data, the touch event can be described as a complete touch event.
The incomplete touch event refers to a touch event that at least one of a press report point, a lift report point and each moving point is not included in the first touch data. Similarly, if any one of the pressing report point or the lifting report point of an event is not included in the first touch data, the touch event can be described as an incomplete touch event.
The coordinate offset in the X coordinate direction refers to the absolute value of the difference between the X coordinates of two points, i.e. |x 1 -x 2 |，x 1 Representing the X coordinate, X of one of the two reporting points 2 Representing the X coordinate of the other.
The coordinate offset in the Y-coordinate direction refers to the absolute value of the difference between the Y-coordinates of two points, i.e. |y 1 -y 2 |，y 1 Representing the Y-coordinate, Y, of one of the two reporting points 2 Representing the Y coordinate of the other.
The touch duration refers to the time difference between the time of lifting the report point and the time of pressing the report point of a touch event, i.e. touch duration=t up -t down ，t up Time t representing lifting report point of certain touch event down The time of the pressing report point of the touch event is shown.
Event interval refers to a time difference between a time of a lifting report point of a previous touch event and a time of a pressing report point of a next touch event in time sequence in two touch events, namely event interval=t down2 -t up1 ，t up1 A time t representing a lifting report point of a previous touch event in time sequence down2 And the time of pressing the report point of the subsequent touch event is represented.
The following describes each type of touch control jump point fault and detection method thereof one by one:
1. fault of jump point in horizontal coordinate direction
The abscissa direction jump point fault is also called an abscissa jump point fault or a fixed line jump point fault, and the like, and refers to a complete touch event distributed along a certain transverse line for multiple times in a short time. Distribution along a certain horizontal line means that the position fluctuation of the complete touch events in the vertical direction is small. The reporting points of the jump point faults in the abscissa direction are shown as the reporting points of the touch events which occur for a plurality of times in the fixed line, the coordinates of the reporting points are close, and the coordinate offset in the ordinate direction is small. In general, the report of the normal touch operation performed by the user does not appear.
In the embodiment of the present application, the position of the touch event may be represented by one or more of coordinates of a pressed report point, pressed coordinates, or a moving point in the touch event. For convenience of description, and to simplify the detection process of the touch jump point fault, in the following embodiment, the position of the touch event is represented by pressing the report point or lifting the coordinate of the report point.
Fig. 8 is a schematic diagram of reporting points corresponding to an example of a point jump fault in the abscissa direction according to an embodiment of the present application. Each point in fig. 8 represents a pressed report point of a complete touch event, and the time of these report points is within a certain period of time, and in this embodiment, the duration of this period of time is 900ms. As can be seen from fig. 8, the individual dots in the diagram are distributed along a horizontal line 801 in the diagram, with less fluctuation in the ordinate direction. That is, a complete touch event with coordinates distributed along the horizontal line 801 occurs multiple times within 900ms, and thus, there is a horizontal jump point fault within the 900ms.
For the abscissa direction jump fault, detection can be performed by the following method.
Fig. 9 is a schematic flow chart of a method for detecting a jump point fault in an 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 first touch data according to event identifications and action identifications of a plurality of report points in a preset time period.
The preset duration is the duration selected when the data packet is acquired in the above embodiment. In an embodiment of detection of the abscissa direction skip point fault, the preset duration may be 800ms to 1200ms.
It can be appreciated that the touch event corresponding to the first touch data may include a complete touch event or a non-complete touch event. The server may search the first touch data for an action identifier and an event identifier, and if there is a pressing report point (i.e. a report point with the pressing action identifier) and a lifting report point (i.e. a report point with the lifting 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 the data of the complete touch event from the first touch data according to the event identifier. The data of each complete touch event comprises the data (coordinates, time, event identification, action identification and the like) of a press report point, a lift report point and each moving point in the touch event.
And the server determines whether the abscissa-direction jump point fault exists in the preset duration according to the data of the at least one complete touch event. Specifically, steps S902 to S907 are as follows.
S902, determining whether coordinates of an nth pressing report point and an adjacent pressing report point in data of at least one complete touch event meet a first coordinate condition; where n=1, 2,3 … … m, 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 time sequence in the press report points of the at least one complete touch event.
Optionally, in this embodiment, the server may obtain the nth pressed report point and the adjacent pressed report points of the nth pressed report point according to the time sequence of each report point of the complete touch event. It should be understood that, among the pressed report points of at least one complete touch event, the 1 st pressed report point and the mth pressed report point include 1 adjacent report point, and the other pressed report points include 2 adjacent pressed report points.
The first coordinate condition is used for representing that the difference between the coordinates of the nth press report point and the adjacent press report point in the vertical coordinate direction is smaller. Optionally, the first coordinate condition may include that a coordinate offset of the nth press report point and the adjacent press report point in the Y-coordinate direction is less than or equal to a first offset threshold. Alternatively, the first offset threshold may be 8 pixel to 12 pixel.
Optionally, as a possible implementation manner, the first coordinate condition may further include that a coordinate offset of the nth pressed report point and the adjacent pressed 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 pixel to 120 pixel. In the implementation manner, the coordinate offset of the nth pressed report point and the adjacent pressed report point in the Y coordinate direction is limited, and the coordinate offset of the nth pressed report point and the adjacent pressed report point in the X coordinate direction is further limited, so that misjudgment of touch control (such as continuous scribing along the horizontal coordinate direction when the accuracy of reporting the points of a screen is detected) of a user in some special cases as a touch control jump point fault in the horizontal coordinate direction can be effectively avoided, and the detection accuracy of the touch control jump point fault in the horizontal coordinate direction is improved.
Taking the first offset threshold as 8 pixel and the second offset threshold as 80 pixel as an example, step S902 is that the server determines whether the coordinates of the nth pressed report point and the adjacent pressed report point satisfy |y simultaneously down（n+1） -y down（n） 80 pixel and x down（n+1） -x down（n） The content of the pixel is less than or equal to 80; wherein y is down（n） Representing the Y-coordinate, Y, of the nth press report point down（n+1） Representing Y coordinates, x of adjacent press report points down（n） X coordinate, X representing the nth press report point down（n+1） Representing the X coordinates of adjacent press-down report points.
If yes, go to step S903;
if not, step S906 is performed.
S903, determining the nth pressing report point as a first target pressing report point.
S904, judging whether the number of the first target pressing report points is larger than or equal to a first preset number.
Alternatively, the first preset number may be an integer of 4 to 6.
If the number of the first target pressing report points is greater than or equal to the first preset number, step S905 is executed;
if the number of the first target pressing points is smaller than the first preset number, step S906 is performed.
S905, determining that the abscissa direction jump point fault exists in the preset time.
S906, judging whether n is equal to m.
That is, it is determined whether each of the pressed report points of all the complete touch events has performed the above-described determination process.
If n is equal to m, execute step S907;
if n is smaller than m, let n=n+1, return to step S902.
S907, determining that the abscissa direction jump point fault does not exist within the preset time period.
Optionally, in an embodiment, before step S902, determining whether the total number of the complete touch events in the first touch data is greater than or equal to the first preset number may be further included, if yes, step S902 is performed, and if not, step S907 is performed. Therefore, the judging process can be simplified, and the algorithm running efficiency is improved.
Through research and analysis, the abscissa-direction jump point fault is a touch jump point fault in actual application of a user, detection of the abscissa-direction jump point fault in touch data can be achieved through the process, the type of the touch jump point fault is matched with that of the touch jump point fault in actual use of the user, real experience of the user is fully considered, analysis is conveniently carried out according to data of a touch event when the jump point fault occurs, the abscissa-direction jump point fault is more specifically solved, and user experience is further improved.
In the method for detecting the jump point fault in the abscissa direction, the position of the touch event is represented by pressing down the coordinates of the report point. In another possible implementation manner, the position of the touch event may also be represented by lifting the report point. Fig. 10 is a schematic flow chart of another method for detecting a jump point fault in the abscissa direction according to the embodiment of the present application, as shown in fig. 10, where the method includes:
s1001, determining at least one complete touch event in the first touch data according to event identifications and action identifications of a plurality of report points in a preset time period.
S1002, determining whether coordinates of an nth lifting report point and an adjacent lifting report point in data of at least one complete touch event meet a second coordinate condition; where n=1, 2,3 … … m, m is the total number of complete touch events in the first touch data.
The adjacent lifting report points refer to lifting report points adjacent to the nth lifting report point time sequence 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 in the vertical coordinate direction is smaller. Optionally, the second coordinate condition may include that a coordinate offset of the nth raised report point and the adjacent raised 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 pixel to 12 pixel.
Optionally, as a possible implementation manner, the first coordinate condition may further include that a coordinate offset of the nth raised report point and the adjacent raised 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 pixel to 120 pixel. Similar to the embodiment shown in fig. 9, in this implementation manner, the coordinate offset of the nth lifting report point and the adjacent lifting report point in the Y coordinate direction is defined, and the coordinate offset of the nth lifting report point and the adjacent lifting report point in the X coordinate direction is further defined, so that misjudgment of touch control of a user under some special conditions as a touch control jump point fault can be effectively avoided, and the detection accuracy of the touch control jump point fault is improved.
Taking the first offset threshold as 8 pixel and the second offset threshold as 80 pixel as an example, step S1002 is that the server determines whether the coordinates of the nth raised report point and the adjacent raised report point are simultaneousSatisfy |y up（n+1） -y up（n） 8 pixel and x up（n+1） -x up（n） The content of the pixel is less than or equal to 80; wherein y is up（n） Representing the Y coordinate, Y of the nth raised report point up（n+1） Representing Y coordinates, x of adjacent lifting report points up（n） X coordinate, X representing the nth raised report point up（n+1） Representing the X coordinates of the adjacent lift-off report points.
If the coordinates of the nth lifting report point and the adjacent lifting report points 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 meet the second coordinate condition, step S1006 is executed.
S1003, determining the nth lifting report point as a target lifting report point.
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 smaller than the first preset number, step S1006 is executed.
S1005, determining that the abscissa direction jump point fault exists in the preset time.
S1006, judging whether n is equal to m.
That is, it is determined whether each of the raised report points of all the complete touch events has performed the above-described determination process.
If n is equal to m, then step S1007 is performed;
if n is smaller than m, let n=n+1, return to step S1002.
S1007, determining that the abscissa direction jump point fault does not exist within the preset time period.
The implementation is similar to the process shown in the embodiment of fig. 9, and specific processes and advantages and the like are not described herein.
2. Jump point fault in ordinate direction
The ordinate-direction jump point fault is also called as an ordinate jump point fault or a fixed-line jump point fault, and the like, and refers to that a complete touch event distributed along a certain column occurs for a plurality of times in a short time. Distribution along a column means that the position of the complete touch events in the abscissa direction fluctuates less. The reporting points of the jump point faults in the ordinate direction are shown as the reporting points of the touch events which occur for a plurality of times in a fixed column, the coordinates of the reporting points are close, and the coordinate offset in the abscissa direction is small. In general, the report of the normal touch operation performed by the user does not appear.
Fig. 11 is a schematic diagram of reporting points corresponding to an example of a vertical jump point fault according to an embodiment of the present application. Each point in fig. 11 represents a pressed report point of a complete touch event, and the time of these report points is within a certain period of time, and in this embodiment, the duration of this period of time is 900ms. As can be seen from fig. 11, the distribution of the individual dots in the figure is distributed along the column 1101 in the figure, with less fluctuation in the abscissa direction. That is, a complete touch event with coordinates distributed along column 1101 occurs multiple times within 900ms, and thus, there is a ordinate direction jump fault within the 900ms.
The method for detecting the jump point fault in the ordinate direction is similar to the method for detecting the jump point fault in the abscissa direction, and the difference is that the coordinate condition of the jump point fault in the ordinate direction is opposite to the threshold value of the coordinate offset in the abscissa direction and the ordinate direction in the first coordinate condition or the second coordinate condition. In contrast to the embodiment shown in fig. 9, in the detection process of the ordinate-direction jump point fault, the coordinate condition of the ordinate-direction jump point fault is that the coordinate offset of the nth press report point and the adjacent press report point in the abscissa direction is smaller than or equal to the first offset threshold (8 pixel to 12 pixel), and the coordinate offset of the nth press report point and the adjacent press report point in the ordinate direction is smaller than or equal to the second offset threshold (80 pixel to 120 pixel).
In addition, in the detection process of the jump point fault in the same horizontal coordinate direction, the position of the touch event can be represented by pressing down the coordinates of the report point, and the position of the touch event can also be represented by lifting up the coordinates of the report point.
Meanwhile, the ordinate-direction jump point fault is also a touch jump point fault in actual application of a user, and the detection of the abscissa-direction jump point fault in touch data is realized by the method provided by the embodiment, the type of the touch jump point fault is matched with the type of the touch jump point fault in actual use of the user, and the actual experience of the user is fully considered, so that analysis is conveniently carried out according to the data of a touch event when the jump point fault occurs, the jump point fault in the ordinate-direction is more specifically solved, and the user experience is further improved.
3. Fixed position continuous click trip fault
The fixed position continuous clicking jump point fault is also called a fixed position continuous lifting pressing jump point fault or a fixed position continuous touch jump point fault, and the like, and means that a plurality of complete touch events occur at a certain fixed position in a short time, the complete touch events are continuous (i.e. one complete touch event is ended, the other complete touch event occurs), and the event interval between two complete touch events adjacent in time sequence is short. The report points of the fault of continuously clicking the jump point at the fixed position are shown as continuously pressing the report points, lifting the report points, pressing the report points and lifting the report points at the fixed position, and like a finger or a handwriting pen, the screen is continuously clicked at the fixed position. However, the frequency of full touch events in such faults 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 absolute fixed position, but rather a small range or area.
Fig. 12 is a schematic diagram of a report corresponding to a fixed-position continuous click skip point fault according to an embodiment of the present application. Each point in fig. 12 represents a pressed report point of a complete touch event, where it is known that the complete touch events are continuous, an event interval between two complete touch events adjacent in time sequence is short, and the time of the report point of the complete touch event is within a certain period of time. In this embodiment, the duration of this period is 495ms. As can be seen from fig. 12, the reporting points in the figure are distributed in the area 1201, and the coordinates of the reporting points fluctuate less in both the abscissa and ordinate directions. That is, a plurality of continuous full touch events occur in the region 1201 within 495ms, and the event interval between two full touch events adjacent in time sequence is short. Thus, there is a fixed-position continuous click skip fault within this 495ms.
For a fixed position continuous click trip fault, detection can be performed by the following method.
Fig. 13 is a schematic flow chart of a method for detecting a fixed-position continuous click jump 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 event identifications and action identifications of a plurality of report points in a preset time period.
The preset duration is the duration selected when the data packet is acquired in the above embodiment. In the embodiment of fixed-position continuous click skip fault detection, the preset duration may be 490ms to 510ms.
The specific process of this step is the same as step S901 in the embodiment shown in fig. 9, and will not be described here again.
S1302, determining whether coordinates of a pressed report point of an nth complete touch event and pressed report points of adjacent complete touch events meet a third coordinate condition in at least one complete touch event; where n=1, 2,3 … … m, 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 that 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 pressed report point of the adjacent full touch event is after the lifted report point of the nth full touch event, and the pressed report point of the adjacent full touch event is adjacent to the lifted report point of the nth full touch event.
Optionally, the server may determine, according to the event identifier and the time of the reporting point of each complete touch event, that the time of pressing the reporting point is after the lifting reporting point of the nth touch event, and that the time of pressing the reporting point is adjacent to the time of lifting the reporting point of the nth complete touch event, thereby determining adjacent complete touch events, and further determining whether the third coordinate condition is satisfied.
The third coordinate condition is used for representing that the coordinate difference between the pressing report point of the nth complete touch event and the pressing report point of the adjacent complete touch event is smaller. Optionally, the third coordinate condition may include that a coordinate offset of a pressed report point of the nth full touch event and a pressed report point of an adjacent full touch event in an X coordinate direction is less than or equal to a third offset threshold, and a coordinate offset in a Y coordinate direction is less than or equal to the 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 pixel to 192 pixel.
Taking 150 pixel as an example, that is, the server determines whether the coordinates of the pressed report point of the nth complete touch event and the pressed report point of the adjacent complete touch event satisfy |x simultaneously n+1（down） -x n（down） 150 pixel and y n+1（down） -y n（down） The content of the pigment is less than or equal to 150 pixel; wherein x is n（down） X coordinate, X representing the pressed report point of the nth complete touch event n+1（down） X coordinate, y representing pressed report point of adjacent complete touch event n（down） Y-coordinate, Y representing the pressed report point of the nth full touch event n+1（down） And representing the Y coordinates of the pressed report points of the adjacent complete touch events.
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.
That is, the server determines whether the time difference between the time of lifting the report point of the nth full touch event and the time of pressing the report point of the adjacent full touch event is less than or equal to the preset event interval threshold.
Alternatively, the preset event interval threshold may be 16ms to 24ms. At a preset event interval thresholdFor example, for 22ms, step S1303 is: judging whether the nth complete touch event and the adjacent complete touch event meet t n+1（down） -t n（up） Not more than 22ms, wherein t n+1（down） Time t representing pressed report point of adjacent complete touch event n（up） And the time of the lifting report point of the nth complete touch event is represented.
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, step S1304 is performed;
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, step S1306 is executed;
if the number of the first target events is smaller than the second preset number, step S1307 is executed.
S1306, determining that a continuous click jump point fault exists in a fixed position within a preset time period.
S1307, determine whether n is equal to m.
That is, it is determined whether each full touch event has performed the above-described determination process.
If n is equal to m, then step S1308 is performed;
if n is smaller than m, let n=n+1, return to step S1302.
S1308, it is determined that the fixed-position continuous click jump fault does not exist in the preset duration.
Optionally, in an embodiment, before step S1302, determining whether the total number of the complete touch events in the first touch data is greater than or equal to the second preset number may be further included, if yes, step S1302 is performed, and if not, step S1308 is performed. Therefore, the judging process can be simplified, and the algorithm running efficiency is improved.
Through research and analysis, the fixed-position continuous click jump fault is a touch jump fault in actual application of a user, detection of the fixed-position continuous click jump fault in touch data can be achieved through the process, the type of the touch jump fault is matched with the type of the touch jump fault generated in actual use of the user, real experience of the user is fully considered, analysis is conveniently carried out according to data of touch events when the jump fault occurs, the fixed-position continuous click jump fault is more specifically solved, and user experience is further improved.
In the method for detecting the fault of the continuous clicking jump point at the fixed position, the position of the touch event is represented by pressing down the coordinates of the report point. In another possible implementation manner, the position of the touch event may also be represented by lifting the report point. Fig. 14 is a schematic flow chart of another method for detecting continuous click jump point faults at fixed positions according to an embodiment of the present application, as shown in fig. 14, where the method includes:
s1401, determining at least one complete touch event in the first touch data according to event identifications and action identifications of a plurality of report points in a preset time period.
S1402, determining whether coordinates of a lifting report point of an nth complete touch event and lifting report points of adjacent complete touch events meet a fourth coordinate condition in at least one complete touch event; where n=1, 2,3 … … m, m is the total number of complete touch events in the first touch data.
The fourth coordinate condition is used for representing that the coordinate 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 a raised report point of the nth full touch event and a raised report point of an adjacent full touch event in an X coordinate direction is less than or equal to a third offset threshold, and a coordinate offset in a Y coordinate direction is less than or equal to the third offset threshold. The third offset threshold and the fourth offset threshold may be the same as those described above with respect to the embodiment of fig. 13.
Taking the third offset threshold and the fourth offset threshold as 150 pixel each,step S1402, namely, the server determines whether the coordinates of the raised report point of the nth full touch event and the raised report point of the adjacent full touch event satisfy |x simultaneously n+1（up） -x n（up） 150 pixel and y n+1（up） -y n（up） The content of the pigment is less than or equal to 150 pixel; wherein x is n（up） X coordinate, X representing the lifting report point of the nth complete touch event n+1（up） X coordinate, y representing lifting report point of adjacent complete touch event n（up） Y-coordinate, Y representing the lifting report point of the nth complete touch event n+1（up） And the Y coordinates of the lifting report points of the adjacent complete touch events are represented.
If yes, step S1403 is executed;
If not, step S1407 is executed.
S1403, 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.
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, step S1404 is executed;
otherwise, step S1407 is performed.
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, step S1406 is executed;
if the number of the second target events is smaller than the second preset number, step S1407 is performed.
S1406, determining that a continuous click jump point fault exists in a fixed position within a preset duration.
S1407, judging whether n is equal to m.
That is, it is determined whether each full touch event has performed the above-described determination process.
If n is equal to m, go to step S1408;
if n is smaller than m, let n=n+1, return to step S1402.
S1408, determining that the fixed-position continuous click point fault does not exist in the preset time period.
The implementation is similar to the process shown in the embodiment of fig. 13, and specific processes and advantages and the like are not described herein.
4. Fixed position quick click trip fault
The fixed position quick click jump fault is also called a fixed position quick lifting press jump fault or a fixed position quick touch jump fault, and the like, and means that a plurality of complete touch events occur in a certain fixed position in a short time, the complete touch events are continuous (namely, one complete touch event is ended, and the other complete touch event occurs), and the touch duration of each complete touch event is short. The report of the fault of the quick click jump point at the fixed position is expressed as that the report is pressed down, lifted up, pressed down and lifted up continuously at the fixed position, and the screen is clicked quickly at the fixed position like a finger or a handwriting pen. However, the frequency of the complete touch event in the fault is higher than the frequency of the normal quick click operation of the user, and the touch duration of the complete touch event is shorter than the touch duration of the normal quick click operation of the user.
Also in this embodiment, the so-called "fixed position" may not be an absolutely fixed position, but a small range or area.
Fig. 15 is an exemplary schematic diagram of a report corresponding to a fixed-position fast click jump fault according to an embodiment of the present application. Each point in fig. 15 represents a pressed report point of a complete touch event, where the complete touch events are known to be continuous, the touch duration of a plurality of complete touch events is relatively small, and the time of the report points of the complete touch events is within a certain time period. In this embodiment, the duration of this period is 495ms. As can be seen from fig. 15, the reporting points in the figure are distributed in the area 1501, and the coordinates of the reporting points fluctuate less in both the abscissa and ordinate directions. That is, a number of fast full touch events occur within region 1501 within 495ms, and thus, there is a fixed location fast click skip fault within 495ms.
For a fixed position quick click trip fault, detection can be performed by the following method.
Fig. 16 is a schematic flow chart of a method for detecting a fixed-position fast click jump 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 event identifications and action identifications of a plurality of report points in a preset time period.
The preset duration is the duration selected when the data packet is acquired in the above embodiment. In the embodiment of fixed-position fast click skip fault detection, the preset duration may be 490ms to 510ms.
This step is the same as step S901 in the embodiment shown in fig. 9, and will not be described here again.
S1602, determining whether coordinates of a pressed report point of an nth complete touch event and pressed report points of adjacent complete touch events meet a fifth coordinate condition in at least one complete touch event; where n=1, 2,3 … … m, m is the total number of complete touch events in the first touch data.
The definition and determination method of the adjacent complete touch event are the same as those of the embodiments shown in fig. 13 and 14, and are not repeated here.
The fifth coordinate condition is used for representing that the coordinate difference between the pressing report point of the nth complete touch event and the pressing report point of the adjacent complete touch event is smaller. Optionally, the fifth coordinate condition may include that a coordinate offset of a pressed report point of the nth full touch event and a pressed report point of an adjacent full touch event in an X coordinate direction is less than or equal to a fifth offset threshold, and a coordinate offset in a Y coordinate direction is less than or equal to a sixth offset threshold. The fifth offset threshold and the sixth offset threshold may or may not be equal. In one embodiment, the fifth offset threshold and the sixth offset threshold are equal and are each 128 pixel to 192 pixel.
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 pressed reporting point of the nth complete touch event and the pressed reporting point of the adjacent complete touch event satisfy the fifth coordinate condition is not repeated here.
If the coordinates of the pressed report point of the nth complete touch event and the pressed report point of the adjacent complete touch event meet the fifth coordinate condition, executing step S1603;
if the coordinates of the pressed report point of the nth full touch event and the pressed report point of the adjacent full touch event do not meet the fifth coordinate condition, step S1607 is performed.
S1603, judging whether the touch duration of the nth complete touch event is smaller than or equal to a preset touch duration threshold.
That is, the server determines whether the time difference between the time of lifting the report point and the time of pressing the report point of the nth complete touch event is less than or equal to a preset touch duration threshold.
Alternatively, the preset touch duration threshold may be 16ms to 24ms. Taking the preset touch duration threshold value of 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 21ms; wherein t is n（up） Time t representing lifting report point of nth complete touch event n（down） And the time of pressing the report point of the nth complete touch event is represented.
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.
S1604, determining the nth complete touch event as a third target event.
S1605, determining whether the number of third target events is greater 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, step S1606 is performed;
if the number of the third target events is smaller than the third preset number, step S1607 is performed.
S1606, determining that a fixed-position quick click point fault exists in the preset time period.
S1607, determine whether n is equal to m.
That is, it is determined whether each full touch event has performed the above-described determination process.
If n is equal to m, executing step S1608;
if n is smaller than m, let n=n+1, return to step S1602.
S1608, determining that the fixed-position quick click point fault does not exist in the preset time period.
Optionally, in an embodiment, before step S1602, determining whether the total number of the complete touch events in the first touch data is greater than or equal to the third preset number may be further included, if yes, step S1602 is executed, and if not, step S1608 is executed. Therefore, the judging process can be simplified, and the algorithm running efficiency is improved.
Through research and analysis, the fixed-position quick click jump fault is a touch jump fault in actual application of a user, detection of the fixed-position quick click jump fault in touch data can be achieved through the process, the type of the touch jump fault is matched with the type of the touch jump fault generated in actual use of the user, real experience of the user is fully considered, analysis is conveniently carried out according to data of a touch event when the jump fault occurs, the fixed-position quick click jump fault is more specifically solved, and user experience is further improved.
In the method for detecting the fast click jump point fault at the fixed position, the position of the touch event is represented by pressing down the coordinates of the report point. In another possible implementation manner, the position of the touch event may also be represented by lifting the report point. Fig. 17 is a schematic flow chart of another method for detecting a fixed-position fast click jump fault according to an embodiment of the present application, as shown in fig. 17, where the method includes:
s1701, determining at least one complete touch event in the first touch data according to event identifications and action identifications of a plurality of report points in a preset time period.
S1702, determining whether coordinates of a lifting report point of an nth complete touch event and lifting report points of adjacent complete touch events meet a sixth coordinate condition in at least one complete touch event; where n=1, 2,3 … … m, m is the total number of complete touch events in the first touch data.
The sixth coordinate condition is used for representing that the coordinate 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 a raised report point of the nth full touch event and a raised report point of an adjacent full touch event in an X coordinate direction is less than or equal to a fifth offset threshold, and a coordinate offset in a 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 pressed report point of the nth complete touch event and the pressed report point of the adjacent complete touch event meet the sixth coordinate condition is not repeated here.
If yes, go to step S1703;
if not, step S1707 is performed.
S1703, judging whether the touch duration of the nth complete touch event is smaller 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.
S1704, determining the nth complete touch event as a fourth target event.
S1705, judging whether the number of the fourth target events is larger 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, executing step S1706;
if the number of the fourth target events is smaller than the third preset number, step S1707 is performed.
S1706, determining that a quick click point fault exists in a preset time period.
S1707, judging whether n is equal to m.
That is, it is determined whether each full touch event has performed the above-described determination process.
If n is equal to m, execute step S1708;
if n is smaller than m, let n=n+1, return to step S1702.
S1708, determining that the quick click jump fault does not exist in the preset time.
The implementation is similar to the process shown in the embodiment of fig. 16, and specific processes and advantages and the like are not described herein.
5. Full screen random touch control jump point fault
The full-screen random touch jump fault is also called full-screen random touch jump 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 time of the complete touch events is relatively close. The reporting points of the full screen random touch are shown as random coordinates of the reporting points, no obvious rule exists, and the event interval between the pressing reporting points of the touch event is smaller. In general, the report of the normal touch operation performed by the user does not appear.
Fig. 18 is an exemplary schematic diagram of a report corresponding to a full-screen random touch skip point fault according to an embodiment of the present application. Each point in fig. 18 represents a pressed report point of a complete touch event, where the intervals between the report points are known to be smaller, and the time points of the report points of the complete touch event are within a certain period of time, and in this embodiment, the duration of the period of time is 900ms. As can be seen from fig. 18, the report points in the graph are randomly distributed, and have no obvious rule. That is, the complete touch events with randomly distributed coordinates occur multiple times within 900ms, and the intervals between the pressing points of the complete touch events are smaller, so that a full-screen random touch skip point fault exists within 900ms.
For the full-screen random touch control jump point fault, detection can be performed by the following method.
Fig. 19 is a schematic flow chart 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 event identifications and action identifications of a plurality of report points in a preset time period.
The preset duration is the duration 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 duration may be 800ms to 1200ms.
This step is the same as step S901 in the embodiment shown in fig. 9, and will not be described here again.
S1902, determining whether coordinates of an nth pressed report point and an adjacent pressed report point in data of at least one complete touch event meet a seventh coordinate condition; where n=1, 2,3 … … m, m is the total number of complete touch events in the first touch data.
The definition and the acquisition method of the adjacent pressed report point are the same as those of the embodiment shown in fig. 9, and are not described herein.
The seventh coordinate condition is used for representing that the difference between the coordinates of the nth pressing report point and the adjacent pressing report point in the vertical coordinate direction is larger, so that the randomness of the coordinates is reflected. Optionally, the seventh coordinate condition may include that the coordinate offset of the nth press report point and the adjacent press report point in the X-coordinate direction is greater than or equal to a seventh offset threshold, and the coordinate offset 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 be equal or different. In one embodiment, the seventh offset threshold and the eighth offset threshold are equal, each 128 pixel to 192 pixel.
Taking the seventh offset threshold and the eighth offset threshold as 180 pixel, step S1902 is to say that the server determines whether the coordinates of the nth pressed report point and the adjacent pressed report point satisfy |x simultaneously down（n+1） -x down（n） 180 pixel and y down（n+1） -y down（n） 180 pixel; wherein x is down（n） X coordinate, X representing the nth press report point down（n+1） Representing the X coordinate, y of adjacent press report points down（n） Represents the nthY coordinates, Y of each press report point down（n+1） Representing the Y coordinates of adjacent press-down report points.
If yes, go to step S1903;
if not, step S1907 is performed.
S1903, judging whether the time difference between the time when the nth point is pressed and the time when the adjacent point is pressed is smaller than or equal to a first time difference threshold value.
Alternatively, the first time difference threshold may be 24ms to 36ms. Taking the first time difference threshold value as 33ms as an example, the server judges whether the time of pressing the reporting point n and the time of pressing the reporting point adjacent meet t down（n+1） -t down（n） Less than or equal to 33ms; wherein t is down（n+1） Indicating the time t of adjacent press report points down（n） Indicating the time of the nth press report.
If yes, go to step S1904;
if not, step S1907 is performed.
S1904, determining the nth pressing report point as a second target pressing report point.
S1905, judging whether the number of the second target pressing report points is larger than or equal to a fourth preset number.
Alternatively, the fourth preset number may be an integer of 4 to 6.
If the number of the second target pressing report points is greater than or equal to the fourth preset number, executing step S1906;
If the number of the second target pressing points is smaller than the fourth preset number, step S1907 is performed.
And S1906, determining that a full-screen random touch jump point fault exists in a preset time period.
S1907, determining whether n is equal to m.
That is, it is determined whether each of the pressed report points of all the complete touch events has performed the above-described determination process.
If n is equal to m, go to step S1908;
if n is smaller than m, let n=n+1, return to step S1902.
S1908, determining that the full-screen random touch control jump point fault does not exist in the preset time.
Optionally, in an embodiment, before step S1902, 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 fourth preset number, if yes, executing step S1902, and if not, executing step S1908. Therefore, the judging process can be simplified, and the algorithm running efficiency is improved.
Through research and analysis, the full-screen random touch jumping point fault is a touch jumping point fault in actual application of a user, detection of the full-screen random touch jumping point fault in touch data can be achieved through the process, the full-screen random touch jumping point fault is matched with the type of the touch jumping point fault generated in actual use of the user, real experience of the user is fully considered, analysis is conveniently conducted according to data of touch events when the jumping point fault occurs, the full-screen random touch jumping point fault is more specifically solved, and user experience is further improved.
6. Full screen random simultaneous touch control jump point fault
The full-screen random simultaneous touch jump point fault is also called full-screen random simultaneous touch jump point fault or full-screen random multi-point touch jump point fault, and the like, and means that a plurality of complete touch events occur in a short time, and 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 case of multiple simultaneous touch events occurs multiple times. The reporting points of the full screen random simultaneous touch are shown as the random coordinates of the reporting points, no obvious rule exists, a plurality of reporting points of complete events exist in a short time, and the situation that a plurality of reporting points occur at the same time (including pressing reporting points, lifting reporting points or moving reporting points) happens repeatedly. In general, the report of the normal touch operation performed by the user does not appear.
It will be appreciated that in this embodiment, the so-called "simultaneous" may not be absolute, but rather a certain small time range or period.
Fig. 20 is a schematic diagram of a report corresponding to a full-screen random simultaneous touch skip point fault according to an embodiment of the present application. Specifically, fig. 20 is a report point in the data of the mobile phone touch event at a certain moment. That is, the timings of the respective dots in fig. 20 are the same. In addition, it is known that the number of complete touch events is greater than 35 in a certain period of time including the time of these points. In this embodiment, the duration of this period is 2900ms. As can be seen from fig. 20, the reporting points in the graph are randomly distributed, and have no obvious rule, and simultaneously, a plurality of reporting points appear at the same time. That is, more than 35 full touch events occur within 2900ms, and more touch events occur simultaneously at the time shown in FIG. 20. Thus, there is a full screen random simultaneous touch skip point fault within this 2900ms.
For the full-screen random simultaneous touch jump point fault, detection can be performed by the following method.
Fig. 21 is a schematic flow chart 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, determining at least one complete touch event in first touch data according to event identifications and action identifications of a plurality of report points in a preset time period.
The preset duration is the duration selected when the data packet is acquired in the above embodiment. In the embodiment of detecting the full-screen random simultaneous touch skip point fault, the preset duration may be 2400ms to 3600ms.
This step is the same as step S901 in the embodiment shown in fig. 9, and will not be described here again.
S2102, determining 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 the complete touch events in the first touch data is greater than the first number threshold, step S2103 is executed;
otherwise, step S2107 is performed.
S2103, acquiring all sub-time periods in a time period corresponding to the preset duration according to the time points of a plurality of report points in the first touch data and event identifiers, and acquiring the number of touch events in each sub-time period; the duration of the sub-time period is less than a 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 simultaneously at the same time in the following steps. The reporting points in the same sub-time period are considered to belong to the same time instant, i.e. the reporting points appear simultaneously. The duration of the sub-time period can be set according to requirements. It can be understood that the smaller the duration of the sub-time period is, the closer the reporting point in the sub-time period is to the 'simultaneous', and the more accurate the result of the obtained full-screen random simultaneous touch fault is. Alternatively, the sub-period may have a duration of 80ms to 120ms. The sub-time period is 80ms to 120ms, so that the calculation process of an algorithm is not too complicated while the accuracy of the result of the full-screen random simultaneous touch fault is ensured, and the detection efficiency is improved.
There are several ways to divide the sub-time periods. In one embodiment, the time period corresponding to the preset time period may be divided according to the time periods of the sub-time periods, so as to obtain a plurality of continuous time periods, that is, all the sub-time periods. The time period corresponding to the preset duration, that is, the time period corresponding to the data packet in the foregoing embodiment. Assuming that the time period corresponding to the preset duration is B1 to b1+ [ delta ] t and the duration of the sub-time period is 100ms, in this embodiment, the sub-time period obtained by dividing includes: b1+100ms, b1+200ms, b1+300ms, b1+400ms … …
In another embodiment, the time of each pressing the report point in the first touch data may be used as the start point of the sub-time period, and all the sub-time periods may be obtained by dividing according to the duration of the sub-time period. For example, in the first touch data, the time when the report point is pressed is respectively: c1, C2, C3, C4 … …, the divided sub-time periods include: the dividing method for the sub-time periods provided by the embodiment of C1+100ms, C2+100ms, C3+100ms and C4+100ms … … can enable all divided sub-time periods to comprise all pressed report points in the first touch data, so that traversal of all touch events is realized in the detection process, and accuracy of full-screen random simultaneous touch fault detection results 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 can screen out the report points with the time in the sub-time period according to the time and the event identification of each report point in the first touch data, and count the number of touch events for the screened report points according to the event identification. It should be noted that, for the selected report points, the report points with the same event identifier are counted only once.
And S2104, determining the sub-time periods with the number of touch events being greater than or equal to a 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-time period as 110ms and the second number threshold as 5 as an example, this step is 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" for each 110ms within the preset duration. If yes, the sub-time period is determined as the target sub-time period.
S2105, determining whether the duty ratio of the number of target sub-periods in all sub-periods is greater than a preset duty ratio.
That is, it is determined whether the duty cycle of the touch events occurring "simultaneously" with at least 5 touch events is greater than a preset duty cycle.
Alternatively, the preset duty cycle may be 40% to 60%.
If the duty ratio of the number of the target sub-periods in all the sub-periods is greater than the preset duty ratio, step S2106 is executed;
if the duty ratio of the number of the target sub-periods in all the sub-periods is less than or equal to the preset duty ratio, step S2107 is executed;
s2106, determining that full-screen random simultaneous touch jump faults exist in a preset time period.
S2107, determining that full-screen random simultaneous touch control jump point faults do not exist in a preset time period.
Through research and analysis, the full-screen random simultaneous touch jumping point fault is a touch jumping point fault in actual application of a user, detection of the full-screen random simultaneous touch jumping point fault in touch data can be achieved through the process, the full-screen random simultaneous touch jumping point fault is matched with the type of the touch jumping point fault generated in actual use of the user, real experience of the user is fully considered, analysis is conveniently conducted according to data of touch events when the jumping point fault occurs, the full-screen random simultaneous touch jumping point fault is more specifically solved, and user experience is further improved.
7. Continuous touch trip point failure
The continuous touch jump fault is also called a long press jump fault or a no-vanishing jump fault, and the like, and means that the touch duration of a certain touch event of touch data is long. The report of the continuous touch jump point fault is expressed as that the report of a touch event is continuously present for a long time.
It can be appreciated that when the mobile phone fails to continuously touch the jump point at the fixed position, normal touch operation performed by the user is affected, for example, the user does not respond when clicking the screen. In this case, the user tries a plurality of times and touches a plurality of times. According to the research, when the continuous touch control jump point fault occurs, the report point generated by the fault and the report point generated by the user touch control can be expressed as follows: the time difference between the pressing report point and the lifting report point of a certain touch event is large, and in the time period corresponding to the time of pressing the report point and the time of lifting the report point of the touch event, one or more other touch events exist, and the coordinate range fluctuation of most of the touch events is small. In general, the report of the normal touch operation performed by the user does not appear.
Fig. 22 is a schematic diagram of reporting points corresponding to a continuous touch skip point fault in an embodiment of the present application. Specifically, fig. 22 is a report of a touch event in a certain period of time. In this embodiment, the duration of this period is 9300ms. Each of 2201, 2202, 2203, and 2204 in the known graph represents a report of a touch event. The report points at 2201 do not include the raised report point of the event, and the touch events at 2202, 2203 and 2204 are complete touch events. As can be seen from fig. 22, the coordinate ranges of the points of the touch events at 2202, 2203 and 2204 in the figure fluctuate less. That is, the touch duration of the touch event corresponding to the report point at 2201 is greater than 9300ms. The fluctuation range of 75% of the touch events in the graph is small in the 9300ms period. Thus, there is a sustained touch skip point failure within this 9300ms.
For continuous touch skip point faults, 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: and taking the moment of pressing a report point (hereinafter referred to as a second pressed report point) in the log file as a starting point to acquire data of all report points in a preset duration, thereby obtaining first touch data. That is, the starting point of the time period corresponding to the first touch data is the time of the second pressing report point, and the duration of the time period is the preset duration.
Fig. 23 is a schematic flow chart of a method for detecting a continuous touch trip 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 with the same event identification as the event identification of the second pressing report point exists in the first touch data according to the event identifications and the action identifications of the report points in the preset time period.
And the second lifting report point is 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 report point is greater than or equal to the preset duration.
The preset duration is the duration selected when the data packet is acquired in the above embodiment. In an embodiment of the detection of the continuous touch trip point fault, the preset duration may be 6400ms to 9600ms.
If the second lifting report point exists in the first touch data, executing step S2302;
if the second lifting report point does not exist in the first touch data, executing step S2309;
s2302, determining at least one complete touch event in the first touch data according to event identifications and action identifications of a plurality of report points in a preset time period.
This step is the same as step S901 in the embodiment shown in fig. 9, and will not be described here again.
S2303, determining whether coordinates of a pressed report point and a lifted report point of an nth complete touch event meet an eighth coordinate condition in at least one complete touch event; where n=1, 2,3 … … m, m is the total number of complete touch events in the first touch data.
The eighth coordinate condition is used for representing that the coordinate difference between the pressed report point and the lifted report point of the nth complete touch event is smaller. Optionally, the eighth coordinate condition may include that a coordinate offset of the press report point and the lift report 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. Alternatively, the ninth offset threshold and the tenth offset threshold may or may not be equal. In a specific embodiment, the ninth offset threshold and the tenth offset threshold are equal, each being 48 pixel to 72 pixel.
Taking the ninth offset threshold and the tenth offset threshold as 68 pixel as examples, that is, the server determines whether the coordinates of the pressed report point and the lifted report point of the nth complete touch event simultaneously satisfy |x n（up） -x n（down） 68 pixel and y n（up） -y n（down） The I is less than or equal to 68 pixel; wherein x is n（up） X coordinate, X representing the lifting report point of the nth complete touch event n（down） X coordinate, y representing the pressed report point of the nth complete touch event n（up） Y-coordinate, Y representing the lifting report point of the nth complete touch event n（down） And the Y coordinate of the pressed report point of the nth complete touch event is represented.
If yes, step S2304 is performed;
if not, step S2308 is performed.
S2304, determining the nth complete touch event as a fifth target event.
S2305, the total number of touch events (hereinafter referred to as total number) in the first touch data is obtained.
S2306, determining whether a ratio of the number of fifth target events to the total number is greater than or equal to a preset ratio threshold.
Alternatively, the preset ratio threshold may be 56% to 84%.
If the ratio of the number of the fifth target events to the total number is greater than or equal to the preset ratio threshold, step S2307 is performed;
if the ratio of the number of the fifth target events to the total number is smaller than the preset ratio threshold, step S2308 is performed.
S2307, determining that continuous touch control jump point faults exist in a preset time period.
S2308, judging whether n is equal to m.
That is, it is determined whether each full touch event has performed the above-described determination process.
If n is equal to m, step S2309 is performed;
If n is smaller than m, let n=n+1, return to step S2303.
S2309, determining that the continuous touch control jump point fault does not exist in the preset time.
It can be understood that, the time of pressing each report point in the log file is taken as a starting point to obtain the data of all the report points in the preset duration, so as to obtain a plurality of data packets, and the processes of S2301 to S2309 are executed on each data packet, so that all the touch events can be traversed, and all the continuous touch jump point faults in the touch data of the log file are determined, so that the accuracy is high.
Through research and analysis, the continuous touch jumping point fault is a touch jumping point fault which occurs in actual application of a user, the detection of the continuous touch jumping point fault in touch data can be realized through the process, the type of the continuous touch jumping point fault is matched with the type of the touch jumping point fault which occurs in actual use of the user, and the actual experience of the user is fully considered, so that the analysis is conveniently carried out according to the data of a touch event when the jumping point fault occurs, the continuous touch jumping point fault is more specifically solved, and the user experience is further improved.
8. Jump point failure after touch
The jump point fault after touch is also called as jump point fault after touch or jump point fault caused by touch, etc., which 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. These touch events, which occur as the user touches, are random in touch duration. Moreover, unlike normal multi-touch by the user, these touch events that occur with the user touch are more distant from the touch events that occur with the user touch and start at a closer time.
According to research, when the jump point fault occurs after touch, the report point can be expressed as: the press report points of the plurality of (at least 2) touch events occur in a group in a short time, and in the group of press report points, the distance between the press report point automatically reported by the screen and the coordinates of the press report point generated by the touch of the user is larger, and the difference between the press report point automatically reported by the screen and the moment of the press report point generated by the touch of the user is smaller. In general, the report of the normal touch operation performed by the user does not appear.
Fig. 24 is an exemplary schematic diagram of a report corresponding to a jump point fault after touch according to an embodiment of the present application. Specifically, a point in fig. 24 represents a pressed report point of a touch event, and the time of the report point of the touch event is known to be in a shorter time period, and in this embodiment, the duration of the time period is 495ms. In addition, at both the known spot 2401 and spot 2402, the difference in time between the spot 2401 and spot 2403 is small. As can be seen, the coordinates of the report point 2402 and the report point 2401 are far, and the coordinates of the report point 2403 and the report point 2401 are far. That is, in 495ms, the dots 2402, 2403 and 2401 appear in groups, and the coordinate distances between the dots 2402, 2403 and 2401 are far, and the difference in time is small. Thus, there is a post-touch skip point fault within the 495ms.
In one embodiment, to ensure the accuracy of the post-touch skip point fault detection result, the post-touch skip point fault may be determined when the above situation occurs multiple times in succession.
The following describes a method for detecting a jump point fault after touch with reference to the accompanying drawings.
In the embodiment shown in fig. 23, the method for acquiring the first touch data in this embodiment is also as follows: and taking the moment of pressing a report point (hereinafter referred to as a second pressed report point) in the log file as a starting point to acquire data of all report points in a preset duration, thereby obtaining first touch data. That is, the starting point of the time period corresponding to the first touch data is the time of the second pressing report point, and the duration of the time period is the preset duration.
Fig. 25 is a schematic flow chart 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 coordinates of a second pressed report point and other pressed report points meet a ninth coordinate condition according to coordinates of the report points in a preset time period; the other pressing report points refer to other pressing report points except the first pressing report point in the first touch data.
The preset duration is the duration selected when the data packet is acquired in the above embodiment. In an embodiment of detection of a jump point failure after touch, the preset duration may be 490ms to 510ms.
The ninth coordinate condition is used to characterize that the second pressed reporting point is a larger distance from the coordinates of each other pressed reporting point. In one embodiment, the ninth coordinate condition may include the first press report point and each of the other press report points having a coordinate offset in the X-coordinate direction that is greater than or equal to an eleventh offset threshold and the Y-coordinate direction having a coordinate offset threshold that is greater than or equal to a twelfth offset threshold. Alternatively, the eleventh offset threshold and the twelfth offset threshold may or may not be equal. In a specific embodiment, the eleventh offset threshold is equal to the twelfth offset threshold, both 120 pixel to 180 pixel.
Taking 140 pixel as the eleventh and twelfth offset thresholds, step S2501 is that the server determines whether the coordinates of the second pressed report point and each other pressed report point satisfy |x simultaneously 2（down） -x s（down） 140 pixel and y 2（down） -y s（down） The content of the pixel is less than or equal to 140 pixels; wherein x is 2（down） X coordinate, X representing second press report point s（down） Representing the X coordinate, y of any other pressed report point 2（down） Representing the Y coordinate, Y of the second press report point s（down） Representing the Y coordinate of any other pressed point.
If yes, go to step S2502;
if not, step S2503 is performed.
S2502, determining whether the time difference between the time of the second pressing report point and the time of each other pressing report point is smaller than or equal to a second time difference threshold according to the time of each report point in the preset time.
Alternatively, the second time difference threshold may be 40ms to 60ms.
If the time difference between the time of the second pressing the report point and the time of each other pressing the report 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 pressing the report point and the time of each other pressing the report point is less than or equal to the second time difference threshold, step S2504 is performed.
S2503, determining that the jump point fault after touch does not exist within a preset time period.
S2504, determining the second pressing report point and each other pressing report point as a group of multi-point co-touch report points.
That is, if the conditions of step S2501 and step S2502 are satisfied once, it is determined that a post-suspected-touch skip point failure occurs.
S2505, judging whether the group number of the multi-point co-touch report points is larger than or equal to a preset group number.
Alternatively, the preset number of groups may be 3 or 4.
If the number of groups of the multi-point co-touch report points is smaller than the preset number of groups, step S2506 is performed.
If the number of groups of the multi-point co-touch report points is greater than or equal to the preset number of groups, step S2508 is performed;
s2506, obtaining third touch data in a preset duration with the time of third pressing the report point as a starting point; the third pressing report point is a pressing report point which is behind the second lifting report point and is adjacent to the second lifting report point in time sequence, and the second lifting report point is a lifting report point with the same event identification as the second pressing report point.
S2507, the step returns to step S2501 by using the third pressed report point as the second pressed report point and the third touch data as the first touch data.
S2508, determining that a jump point fault after touch exists in a preset time period.
Taking the preset group number as 4 as an example, that is, if 4 or more suspected post-touch jump faults occur continuously, determining that the post-touch jump faults occur within a preset time period corresponding to the first touch data and within a preset time period corresponding to the third touch data.
It can be understood that, the time of pressing each report point in the log file is taken as a starting point to obtain the data of all the report points in the preset duration, so as to obtain a plurality of data packets, and the processes from S2501 to S2508 are executed on each data packet, so that all the touch events can be traversed, and all the jump point faults after touch in the touch data of the log file are determined, so that the accuracy is high.
Through research and analysis, the post-touch jump point fault is a touch jump point fault in actual application of a user, detection of the post-touch jump point fault in touch data can be achieved through the process, the type of the post-touch jump point fault is matched with the type of the touch jump point fault in actual use of the user, real experience of the user is fully considered, analysis is conveniently carried out according to data of a touch event when the jump point fault occurs, the post-touch jump point fault is more specifically solved, and user experience is further improved.
The above describes in detail an example of the method for detecting a touch skip point fault provided in the embodiment of the present application. It will be appreciated that the electronic device, in order to achieve the above-described functions, includes corresponding hardware and/or software modules that perform the respective functions. Those of skill in the art will readily appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Those skilled in the art may implement the described functionality using different approaches for each particular application in conjunction with the embodiments, but such implementation is not to be considered as outside the scope of this application.
The embodiment of the present application may divide the functional modules of the electronic device according to the above method examples, for example, may divide each function into each functional module corresponding to each function, for example, a detection unit, a processing unit, a display unit, or the like, or may integrate two or more functions into one module. The integrated modules may be implemented in hardware or in software functional modules. It should be noted that, in the embodiment of the present application, the division of the modules is schematic, which is merely a logic function division, and other division manners may be implemented in actual implementation.
It should be noted that, all relevant contents of each step related to the above method embodiment may be cited to the functional description of the corresponding functional module, which is not described herein.
Referring to fig. 26, a structure of an electronic device provided in an embodiment of the present application is shown, where the electronic device may be a terminal device or a server that generates data of a touch event in the embodiment of the present application. 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 software programs and modules to perform various functional applications and information processing. The receiver 2602 and the transmitter 2603 may be implemented as one communication component, which may be a baseband chip. The memory 2604 is coupled to the processor 2601 by a bus 2605. The memory 2604 may be configured to store at least one program instruction, and the processor 2601 is configured to execute the at least one program instruction to implement the technical solutions of the foregoing embodiments. The implementation principle and technical effects are similar to those of the related embodiments of the method, and are not repeated here.
When the electronic device is started, 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 is required to be transmitted through the antenna, the processor carries out baseband processing on the data to be transmitted and then outputs a baseband signal to a control circuit in the control circuit, and the control circuit carries out radio frequency processing on the baseband signal and then transmits the radio frequency signal outwards in the form of electromagnetic waves through the antenna. When data is transmitted to the electronic equipment, the control circuit receives a radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor, and the processor converts the baseband signal into data and processes the data.
Those skilled in the art will appreciate that for ease of illustration, only one memory and processor is shown in fig. 26. In an actual electronic device, there may be multiple processors and memories. The memory may also be referred to as a storage medium or storage device, etc., and embodiments of the present application are not limited in this regard.
As an alternative implementation, the processor may include a baseband processor, which is mainly used to process the communication data, and a central processor, which is mainly used to execute a software program and process the data of the software program. It will be appreciated by those skilled in the art that the baseband processor and the central processing unit may be integrated into one processor or may be separate processors interconnected by bus technology or the like. Those skilled in the art will appreciate that an electronic device may include multiple baseband processors to accommodate different network formats, and that an electronic device may include multiple central processors to enhance its processing capabilities, with various components of the electronic device being connectable via various buses. The baseband processor may also be referred to as a baseband processing circuit or 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 a memory in the form of a software program, which is executed by the processor to realize the baseband processing function. The memory may be integrated within the processor or separate from the processor. The memory includes a Cache memory that can hold frequently accessed data/instructions.
In the embodiments of the present application, the processor may be a general purpose 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 a method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution.
In the embodiment of the present application, the memory may be a nonvolatile memory, such as a hard disk (HDD) or a solid state drive (SS), or may 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, and is not limited thereto.
The memory in the embodiments of the present application may also be circuitry or any other device capable of implementing a memory function for storing program instructions and/or data. The methods provided in 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. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, a network device, a user device, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, e.g., from one website, computer, server, or data center, by wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL), or wireless (e.g., infrared, wireless, microwave, etc.) means, the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc., that contains an integration of one or more available media, the available media may be magnetic media (e.g., floppy disk, hard disk, tape), optical media (e.g., digital video disc (digital video disc, DWD), or semiconductor media (e.g., SSD), etc.
An embodiment of the present application provides a computer program product, which when executed on an electronic device, causes the electronic device to execute the technical solution in the foregoing embodiment. The principle and technical effects of the present invention are similar to those of the above-described related embodiments, and will not be described in detail herein.
An embodiment of the present application provides a computer readable storage medium, on which program instructions are stored, which when executed by an electronic device, cause the electronic device to execute the technical solution of the foregoing embodiment. The principle and technical effects of the present invention are similar to those of the above-described related embodiments, and will not be described in detail herein.
In summary, the above embodiments are only for illustrating the technical solution of the present application, and are not limited thereto; 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 scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims (25)

1. The method for detecting the touch control jump 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 in preset time, the event identifications are used for representing touch events to which the report points belong, the plurality of report points comprise a press report point and a lift report point, and the press report point and the event identifications of the lift report point of the same touch event are the same; the pressing report point and the lifting report point are provided with action identifiers, the action identifiers of the pressing report point are used for representing that the report point is the pressing report point, and the action identifiers of the lifting report point are used for representing that the report point is the lifting report point;
determining whether a touch jump point fault of a preset type exists in the preset time period according to the first touch data; the touch control jump point faults of the preset type comprise at least one of a first direction jump point fault, a fixed position continuous click jump point fault, a fixed position quick click jump point fault, a full screen random touch control jump point fault, a continuous touch control jump point fault and a full screen random simultaneous touch control jump point fault;
the determining whether a touch jump point fault of a preset type exists in the preset duration according to the 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 plurality of report points; the complete touch event refers to a touch event that both a pressing report point and a lifting report point are included in the first touch data; and determining whether the touch jump point fault of the preset type exists in the preset duration according to the data of the at least one complete touch event in the first touch data.
2. The method of claim 1, wherein the preset type of touch skip point fault includes the first direction skip point fault, and wherein determining whether the preset type of touch skip point fault exists within the preset duration according to the data of the at least one complete touch event in the first touch data includes:
determining whether the coordinates of a first pressed report point and adjacent pressed report points meet a first coordinate condition according to the coordinates and the time of the pressed report points of the at least one complete touch event; the first pressing report point is a pressing report point of any one of the complete touch events, and the adjacent pressing report points refer to pressing report points adjacent to the first pressing report point time sequence; the first coordinate condition comprises that the coordinate offset of the first pressed report point and the adjacent pressed report point in a second direction is smaller than or equal to a first offset threshold value, and the second direction is perpendicular to the first direction;
if the coordinates of the first pressed report point and the adjacent pressed report points meet the first coordinate condition, determining the first pressed report point as a first target pressed report point;
if the number of the first target pressing 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 jump point fault exists in the preset duration.
3. The method of claim 1, wherein the preset type of touch skip point fault includes the first direction skip point fault, and wherein determining whether the preset type of touch skip point fault exists within the preset duration according to the data of the at least one complete touch event in the first touch data includes:
determining whether the coordinates of the first lifting report point and the adjacent lifting report point meet a second coordinate condition 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 of the complete touch events, 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 smaller than or equal to a first offset threshold value, and the second direction is perpendicular to the first direction;
if the coordinates of the first lifting report point and the adjacent lifting report points meet the 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 the at least one complete touch event is greater than or equal to a first preset number, determining that the first direction jump point fault exists in the preset duration.
4. The method of claim 2, wherein the first coordinate condition further comprises:
the coordinate offset of the first pressed report point and the adjacent pressed report point in the first direction is smaller than or equal to a second offset threshold.
5. The method of claim 4, 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.
6. The method of claim 4, wherein the first direction is an ordinate direction in a screen coordinate system of the electronic device and the second direction is an abscissa 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.
7. The method according to any one of claims 2 to 6, wherein the first preset number is an integer from 4 to 6 and the preset time period is from 800ms to 1200ms.
8. The method of claim 1, wherein the preset type of touch skip point fault comprises the fixed position continuous click skip point fault, and the determining whether the preset type of touch skip point fault exists in the preset 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 pressed report point of the first complete touch event and the coordinates of the pressed report point of the adjacent complete touch event meet a third coordinate condition 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 smaller than or equal to a preset event interval threshold value;
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 time sequence after the first complete touch event; the third coordinate condition comprises that the coordinate offset of the pressed report point of the first complete touch event and the pressed report point of the adjacent complete touch event in a first direction is smaller than or equal to a third offset threshold value, the coordinate offset in a second direction is smaller than or equal to a fourth offset threshold value, and the first direction is perpendicular to the second direction; the event interval refers to a time difference between a time of lifting a report point of a previous touch event and a time of pressing a report point of a next touch event in time sequence in the two touch events;
If the coordinates of the pressed report point of the first complete touch event and the pressed report 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;
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 jump point fault exists in the preset duration.
9. The method of claim 1, wherein the preset type of touch skip point fault comprises the fixed position continuous click skip point fault, and the determining whether the preset type of touch skip point fault exists in the preset 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 lifting report point of a first complete touch event and the coordinates of lifting report points of adjacent complete touch events meet a fourth coordinate condition according to the coordinates, time and event identification of report points of 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 smaller than or equal to a preset event interval threshold;
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 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 a first direction is smaller than or equal to a third offset threshold value, the coordinate offset in a second direction is smaller than or equal to a fourth offset threshold value, and the first direction is perpendicular to the second direction; the event interval refers to a time difference between a time of lifting a report point of a previous touch event and a time of pressing a report point of a next touch event in time sequence in 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 smaller than or equal to the preset event interval threshold, determining the first complete touch event as a second target event;
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 jump point fault exists in the preset duration.
10. The method of claim 8 or 9, wherein the third offset threshold and the fourth offset threshold are each 128 pixels to 192 pixels, the second preset number is an integer from 4 to 6, the preset event interval threshold is from 16ms to 24ms, and the preset time period is from 490ms to 510ms.
11. The method of claim 1, wherein the preset type of touch skip point fault comprises the fixed location quick click skip point fault, and the determining whether the preset type of touch skip point fault exists in the preset 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 pressed report point of the first complete touch event and the coordinates of the pressed report point of the adjacent complete touch event meet a fifth coordinate condition 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 smaller than or equal to a preset touch duration threshold;
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 time sequence after the first complete touch event; the fifth coordinate condition comprises that the coordinate offset of the pressed report point of the first complete touch event and the pressed report point of the adjacent complete touch event in a first direction is smaller than or equal to a fifth offset threshold, and the coordinate offset in a second direction is smaller 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 lifting the report point and the time of pressing the report point of the touch event;
if the coordinates of the pressed report point of the first complete touch event and the pressed report point of the adjacent complete touch event meet the fifth coordinate condition, and the touch duration of the first complete touch event is smaller than or equal to the preset touch duration threshold, determining the first complete touch event as a third target event;
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 jump fault exists in the preset duration.
12. The method of claim 1, wherein the touch skip point fault of the preset type includes a fast touch skip point fault of the fixed location, and the determining whether the touch skip point fault of the preset type exists in the preset duration according to the data of the at least one complete touch event in the first touch data 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 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 smaller than or equal to a preset touch duration threshold;
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 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 touch event in a first direction is smaller than or equal to a fifth offset threshold, the coordinate offset in a second direction is smaller than or equal to a sixth offset threshold, and the first direction is perpendicular to the second direction; the touch duration refers to the time difference between the time of lifting 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 smaller 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 jump fault exists in the preset duration.
13. The method of claim 11 or 12, wherein the fifth offset threshold and the sixth offset threshold are each 128 pixels to 192 pixels, the third preset number is an integer from 4 to 6, the touch duration threshold is from 16ms to 24ms, and the preset duration is from 490ms to 510ms.
14. The method of claim 1, wherein the touch skip point fault of the preset type includes the full-screen random touch skip point fault, and the determining whether the touch skip point fault of the preset type exists in the preset duration according to the data of the at least one complete touch event in the first touch data includes:
Determining whether coordinates of a first pressed report point and coordinates of adjacent pressed report points meet a seventh coordinate condition according to coordinates and moments of pressed report points of the at least one complete touch event, and determining whether a time difference between the moments of the first pressed report point and the coordinates of the adjacent pressed report points is smaller than or equal to a first time difference threshold;
the first pressing report point is a pressing report point of any one of the complete touch events, and the adjacent pressing report points refer to pressing report points adjacent to the first pressing report point time sequence; the seventh coordinate condition includes that a coordinate offset of the first pressed report point and the adjacent pressed report point in a first direction is greater than or equal to a seventh offset threshold, and a coordinate offset in a 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 pressed report point and the adjacent pressed report point meet the seventh coordinate condition, and the time difference between the time of the first pressed report point and the time of the adjacent pressed report point is smaller than or equal to the first time difference threshold, determining the first pressed report point as a second target pressed report point;
And if the number of the second target pressing report points in the data of the at least one complete touch event is larger than or equal to a fourth preset number, determining that the full-screen random touch jump point fault exists in the preset duration.
15. The method of claim 14, 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 from 24ms to 36ms, and the predetermined time period is from 800ms to 1200ms.
16. The method of claim 1, wherein the touch skip point fault of the preset type includes the full screen random simultaneous touch skip point fault, and the determining whether the touch skip point fault of the preset type exists in the preset duration according to the data of the at least one complete touch event in the first touch data includes:
if the number of the complete touch events in the first touch data is greater than or equal to a first number threshold, acquiring all sub-time periods in a time period corresponding to the preset duration according to the time points of the plurality of report points and event identifiers, and acquiring the number of the touch events in each sub-time period; the duration of the sub-time period is smaller 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, in all the sub-time periods as target sub-time periods;
if the number duty ratio of the target sub-time periods in all the sub-time periods is larger than a preset duty ratio, determining that the full-screen random simultaneous touch jump point fault exists in the preset duration.
17. The method of claim 16, wherein the obtaining all sub-time periods in the time period corresponding to the preset duration includes:
and respectively taking the time when each report point is pressed down in the plurality of report points as the starting point of a sub-time period, and obtaining all the sub-time periods according to the duration of the sub-time period and the time period corresponding to the preset duration.
18. The method of claim 16, wherein the all sub-time periods are continuous, and the obtaining all sub-time periods in the time period corresponding to the preset duration includes:
dividing the time period corresponding to the preset time period according to the time length of the sub-time period to obtain all the sub-time periods.
19. The method of any one of claims 16 to 18, wherein the sub-time period has a duration of 80ms to 120ms, the first number threshold is an integer of 24 to 36, the second number threshold is an integer of 3 to 5, the preset duty cycle is 40% to 60%, and the preset duration is 2400ms to 3600ms.
20. The method of claim 1, wherein the touch trip point fault of the preset type includes a continuous touch trip point fault, and the start point of the time period corresponding to the preset duration is a time of the second press report point;
the method further includes, before determining whether the preset type of touch jump point fault exists in the preset duration according to the data of the at least one complete touch event in the first touch data:
determining that a second lifting report point which is the same as the event identification of the second pressing report point does not exist in the first touch data;
the determining whether the touch jump point fault of the preset type exists in the preset duration according to the data of the at least one complete touch event in the first touch data includes:
determining whether coordinates of a pressed report point and a lifted 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 the coordinate offset of a pressed report point and a lifted report point of the first complete touch event in a first direction is smaller than or equal to a ninth offset threshold, the coordinate offset in a second direction is smaller than or equal to a tenth offset threshold, and the first direction is perpendicular to the second direction;
If the coordinates of the pressed report point and the lifted 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 in the at least one complete touch event is greater than or equal to a preset ratio threshold, determining that the continuous touch jump point fault exists in the preset duration.
21. The method of claim 20, wherein the ninth offset threshold and the tenth offset threshold are each 48 pixels to 72 pixels, the preset duration is 6400ms to 9600ms, and the preset ratio threshold is 56% to 84%.
22. The method of claim 1, wherein the touch skip point fault of the preset type further comprises a skip point fault after touch, and a start point of a time period corresponding to the preset duration is a time of a second press report point;
the determining whether a touch jump point fault of a preset type exists in the preset duration according to the first touch data includes:
according to the coordinates and the moments of the pressed report points in the first touch data, determining whether the coordinates of the second pressed report point and each other pressed report point meet a ninth coordinate condition, and determining whether the time difference between the moment of the second pressed report point and the moment of each other pressed report point is smaller than or equal to a second time difference threshold;
The other pressing report points refer to pressing report points except the second pressing report point in the first touch data; the ninth coordinate condition includes that the coordinate offset of the second pressed report point and each other pressed report point in the first direction is greater than or equal to an eleventh offset threshold, the coordinate offset in the second direction is greater than or equal to a twelfth offset threshold, and the first direction is perpendicular to the second direction;
if the coordinates of the second pressed reporting point and the other pressed reporting points meet the ninth coordinate condition, and the time difference between the time of the second pressed reporting point and the time of the other pressed reporting points is smaller than or equal to the second time difference threshold, determining the second pressed reporting point and the other pressed reporting points as a group of multipoint co-touch reporting points;
acquiring third touch data in the preset time length taking the moment of a third pressing report point as a starting point, taking the third pressing report point as the second pressing report point, and executing the first touch data on the third touch data until the second pressing report point and each other pressing report point are not multi-point co-touch report points, and determining the group number of the multi-point co-touch report points; the third pressing report point is a pressing report point adjacent to the second lifting report point time sequence after a second lifting report point, and the second lifting report point is a lifting report point with the same event identification as the second pressing report point;
And if the group number of the multi-point co-touch report points is greater than or equal to a preset group number, determining that the jump point fault exists after touch within the preset duration.
23. The method of claim 22, wherein the eleventh offset threshold and the twelfth offset threshold are each 120 pixels to 180 pixels, the second time difference threshold is 40ms to 60ms, the preset group number is 3 or 4, and the preset time period is 490ms to 510ms.
24. 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-23.
25. A computer readable storage medium, characterized in that the computer readable storage medium has stored therein a computer program which, when executed by a processor, causes the processor to perform the method of any of claims 1 to 23.
CN202111166893.3A 2021-09-30 2021-09-30 Touch control jump point fault detection method, electronic equipment and readable storage medium Active CN114995675B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111166893.3A CN114995675B (en) 2021-09-30 2021-09-30 Touch control jump point fault detection method, electronic equipment and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111166893.3A CN114995675B (en) 2021-09-30 2021-09-30 Touch control jump point fault detection method, electronic equipment and readable storage medium

Publications (2)

Publication Number Publication Date
CN114995675A CN114995675A (en) 2022-09-02
CN114995675B true CN114995675B (en) 2023-04-28

Family

ID=83017978

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111166893.3A Active CN114995675B (en) 2021-09-30 2021-09-30 Touch control jump point fault detection method, electronic equipment and readable storage medium

Country Status (1)

Country Link
CN (1) CN114995675B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240143112A1 (en) * 2022-10-28 2024-05-02 Himax Technologies Limited Touch sensing apparatus, electronic device and touch operation recording method thereof

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103970323A (en) * 2013-01-30 2014-08-06 北京汇冠新技术股份有限公司 Method and system for tracking of trajectory of touch screen
CN106775053A (en) * 2016-11-11 2017-05-31 广州视源电子科技股份有限公司 The determination method and device of sensitivity of touch screen

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101691478B1 (en) * 2011-02-09 2016-12-30 삼성전자주식회사 Operation Method based on multiple input And Portable device supporting the same
US20180284977A1 (en) * 2017-03-30 2018-10-04 Acer Incorporated Electronic devices, methods for controlling user interface and methods for sensing touch object
CN112432308B (en) * 2020-11-20 2022-07-08 珠海格力电器股份有限公司 Touch interaction device, control method and device thereof and air conditioning unit

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103970323A (en) * 2013-01-30 2014-08-06 北京汇冠新技术股份有限公司 Method and system for tracking of trajectory of touch screen
CN106775053A (en) * 2016-11-11 2017-05-31 广州视源电子科技股份有限公司 The determination method and device of sensitivity of touch screen

Also Published As

Publication number Publication date
CN114995675A (en) 2022-09-02

Similar Documents

Publication Publication Date Title
CN111737127B (en) Method and apparatus for testing map services
US11789805B2 (en) Detecting, diagnosing, and alerting anomalies in network applications
US11960354B2 (en) Proactive learning of network software problems
US11874884B2 (en) Identifying web elements based on user browsing activity and machine learning
CN109885537B (en) Log display method, system and computer readable storage medium
CN108475182A (en) Data processing method and electric terminal
CN114995675B (en) Touch control jump point fault detection method, electronic equipment and readable storage medium
US10193989B2 (en) Visualization of user behavior
WO2019139725A1 (en) Feature usage prediction using shell application feature telemetry
KR20230007268A (en) Task processing method, task processing device, electronic device, storage media and computer program
CN112817790A (en) Method for simulating user behavior
CN110266555B (en) Method for analyzing website service request
WO2015119970A1 (en) Visual tagging to record interactions
CN114995674B (en) Edge false touch detection method, electronic device and computer readable storage medium
CN112306606A (en) Method and equipment for presenting control style
CN115061591A (en) Edge false touch detection method, electronic device and computer-readable storage medium
US20230065492A1 (en) Method for obtaining browser running data, electronic device, and storage medium
CN103106140A (en) Intelligent display device testing information display method
CN110311806A (en) A kind of mobile applications interface operating lag diagnostic method, system and terminal
CN108459942A (en) A kind of data processing method, device and storage medium
CN105262829B (en) Geographical position monitoring method and system
CN103593290B (en) A kind of method and device testing software stability
CN103547982A (en) Identifying contacts and contact attributes in touch sensor data using spatial and temporal features
CN113378036A (en) Page operation analysis and point burying method, device, equipment and storage medium
CN113534209A (en) Position reporting method and device based on tracker, storage medium and terminal

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant