CN115061591A

CN115061591A - Edge false touch detection method, electronic device and computer-readable storage medium

Info

Publication number: CN115061591A
Application number: CN202111076872.2A
Authority: CN
Inventors: 韩帅; 蒋冬; 冀焕霞; 樊亮
Original assignee: Xi'an Honor Device Co.,Ltd.
Current assignee: Xi'an Honor Device Co.,Ltd.
Priority date: 2021-09-14
Filing date: 2021-09-14
Publication date: 2022-09-16

Abstract

The embodiment of the application provides a method for detecting edge false touch, electronic equipment and a computer readable storage medium, wherein the method comprises the following steps: acquiring data of a touch event to be detected, wherein the touch event comprises a press-down event and a lift-up event, and the data of the touch event comprises first data of the press-down event and second data of the lift-up event; and determining whether the touch event to be detected is one of a plurality of preset types of edge false touch events according to a preset edge false touch area of the electronic equipment and the first data and the second data of the touch event to be detected. The method for detecting the edge false touch provided by the embodiment of the application can detect the edge false touch fault and can identify the type of the edge false touch fault.

Description

Edge false touch detection method, electronic device and computer-readable storage medium

Technical Field

The present application relates to the field of touch technologies, and in particular, to a method for detecting edge false touches, an electronic device, and a computer-readable storage medium.

Background

With the rapid development of electronic technologies, touch technologies are widely applied to various electronic devices. For example, a touch panel is integrated in a display screen of a device such as a mobile phone, a tablet computer, a wearable device, and a teaching all-in-one machine, so that the device has a touch function while displaying. In addition, the equipment such as notebook computer is provided with a touch panel, and can also realize the touch function.

When the electronic equipment with the touch function is applied, edge false touch is easy to occur. Especially, under the condition that the electronic equipment screen is higher and higher in occupied area and the frame is smaller and smaller, the problem of edge mistaken touch is particularly prominent. Therefore, the algorithm for preventing the edge from being touched by mistake is more and more demanding. In the case of an edge false touch prevention algorithm, whether in an algorithm design stage, an algorithm test stage, an algorithm application stage, or an algorithm improvement stage, an edge false touch fault needs to be identified and detected.

Disclosure of Invention

The application provides a method for detecting edge false touch, an electronic device and a computer readable storage medium, which can detect edge false touch faults.

In a first aspect, the present application provides a method for detecting an edge miss-touch, including:

acquiring data of a touch event to be detected, wherein the touch event comprises a press-down event and a lift-up event, and the data of the touch event comprises first data of the press-down event and second data of the lift-up event; and determining whether the touch event to be detected is one of a plurality of preset types of edge false touch events according to a preset edge false touch area of the electronic equipment and the first data and the second data of the touch event to be detected.

Optionally, if the touch event to be detected belongs to one of the edge false touch events of the plurality of preset types, a fault of edge false touch can be prompted.

Optionally, if the touch event to be detected does not belong to any one of the edge false touch events of the plurality of preset types, it is determined that the touch event to be detected does not belong to the edge false touch event.

In the method for detecting edge false touches provided by the first aspect, whether the touch event to be detected is one of a plurality of preset types of edge false touches is determined according to the set edge false touch area of the electronic device and the first data and the second data of the touch event to be detected by obtaining the first data and the second data of the touch event to be detected. The method can determine whether the touch event to be detected is an edge error touch event, and is convenient for subsequent analysis or processing; meanwhile, the method provided by the embodiment can determine the type of the edge false touch, and the detection result of the edge false touch event is more accurate, so that the subsequent analysis or processing is more accurate, and the effectiveness of solving the edge false touch problem is improved.

With reference to the first aspect, in some implementation manners of the first aspect, determining whether the touch event to be detected is one of a plurality of preset types of edge false touch events according to a preset edge false touch area of the electronic device and first data and second data of the touch event to be detected includes:

determining a touch position and a touch distance of the touch event to be detected according to the first data and the second data of the touch event to be detected; the touch distance is used for representing the distance between the position of a press-down event and the position of a lift-up event in a preset direction in the touch event; and determining whether the touch event to be detected is one of a plurality of preset types of edge false touch events according to the preset edge false touch area, the touch position and the touch distance of the touch event to be detected.

With reference to the first aspect and the foregoing implementation manner, the method further includes:

determining the touch duration of the touch event to be detected according to the first data and the second data of the touch event to be detected; the touch duration is used for representing the time difference between the occurrence moment of the lift-up event and the occurrence moment of the press-down event in the touch event;

determining whether the touch event to be detected is one of a plurality of preset types of edge false touch events according to a preset edge false touch area, and the touch position and the touch distance of the touch event to be detected, including:

and determining whether the touch event to be detected is one of a plurality of preset types of edge false touch events according to the preset edge false touch area, the touch position, the touch distance and the touch duration of the touch event to be detected.

In one possible implementation, the edge false touch events of a plurality of preset types include: an edge long press false touch event, an edge slide false touch event, a corner fast click false touch event, and an edge continuous click false touch event.

The edge long press false touch event, the edge sliding false touch event, the corner fast click false touch event and the edge continuous click false touch event are all edge false touch types encountered in the actual using process of a user. In the implementation mode, the real experience of a user in the process of using the terminal is fully considered, the edge long press error touch event in the touch event can be intelligently detected, the edge long press error touch event is matched with the edge error touch fault type in the actual use of the user, the follow-up analysis, processing and improvement on the data of the edge long press error touch event are facilitated, and the user experience is improved.

In a possible implementation manner, the preset edge mis-touch area includes a first preset area, and according to the preset edge mis-touch area and the touch position, the touch distance, and the touch duration of the touch event to be detected, it is determined whether the touch event to be detected is one of a plurality of preset types of edge mis-touch events, including:

if the touch position of the touch event to be detected belongs to a first preset area, the touch distance of the touch event to be detected is smaller than or equal to a first preset distance, and the touch duration of the touch event to be detected is larger than or equal to a preset long press duration, determining that the touch event to be detected is an edge long press mis-touch event.

Optionally, the first preset area may be an area with an X coordinate of 0pixel to 5pixel and an area with an X coordinate of width-6pixel to width-1pixel, where width is a pixel width of a display screen of the electronic device.

Alternatively, the first preset distance may be 30 pixels.

Optionally, the preset long press time may be 1500 ms.

In the implementation mode, whether the touch position, the touch distance and the touch duration of the touch event to be detected are matched with the parameter condition of the edge long press false touch event or not is determined, so that whether the touch event to be detected is the edge long press false touch event or not is determined. The characteristics of the edge long press false touch event can be quantitatively embodied by the first preset area, the first preset distance and the preset long press duration, so that in the implementation mode, by determining that the touch position of the touch event to be detected belongs to the first preset area, the touch distance of the touch event to be detected is smaller than or equal to the first preset distance, and the touch duration of the touch event to be detected is larger than or equal to the preset long press duration, the edge long press false touch event can be accurately detected, and the accuracy of edge long press false touch fault detection is improved.

In one possible implementation, the touch position includes a position of a press-down event and a position of a lift-up event in the touch event; the method for detecting the touch position of the touch event belongs to a first preset area and comprises the following steps:

the position of a press-down event and the position of a lift-up event in a touch event to be detected both belong to a first preset area.

In a possible implementation, the method further includes:

if the touch event to be detected is an edge long press false touch event, then: obtaining a first number of false touch events within a first time period; the first time period refers to a time period between the occurrence moment of a press-down event and the occurrence moment of a lift-up event in the touch event to be detected; acquiring a second number of touch events in a first time period; and if the second quantity is greater than the first quantity, determining that the touch event to be detected is an edge long press false touch event which can be sensed by a user.

Alternatively, the first number may be determined by obtaining the number of event identifications of edge false touch events within the first time period.

Alternatively, the second number may be determined by obtaining the number of event identifications within the first time period.

In the implementation mode, under the condition that the edge long press event is determined to be the edge long press false touch event, whether the touch event is the user-perceivable edge long press false touch event is determined, and the touch event is further matched with the edge false touch fault in actual use of a user, so that the user experience is truly reflected, the subsequent targeted analysis, processing and improvement are facilitated, and the user experience is further improved.

In a possible implementation manner, the preset edge mis-touch area includes a second preset area, and according to the preset edge mis-touch area and the touch position, the touch distance, and the touch duration of the touch event to be detected, it is determined whether the touch event to be detected is one of a plurality of preset types of edge mis-touch events, including:

if the touch position of the touch event to be detected belongs to a second preset area, the touch distance of the touch event to be detected is greater than the first preset distance and less than or equal to a second preset distance, and the touch duration of the touch event to be detected is greater than or equal to a preset sliding duration, determining that the touch event to be detected is an edge sliding mis-touch event.

Alternatively, the second preset area may be the same as the first preset area.

Alternatively, the second preset distance may be 700 pixels.

Optionally, the preset sliding time period may be equal to the preset long pressing time period, which is 1500 ms.

In the implementation manner, whether the touch position, the touch distance and the touch duration of the touch event to be detected are matched with the parameter conditions of the edge sliding false touch event or not is determined, so that whether the touch event to be detected is the edge sliding false touch event or not is determined. The second preset area, the second preset distance and the preset sliding time length can quantitatively embody the characteristics of the edge sliding false touch event, therefore, in the implementation manner, by determining that the touch position of the touch event to be detected belongs to the second preset area, the touch distance of the touch event to be detected is greater than the first preset distance and less than or equal to the second preset distance, and the touch time length of the touch event to be detected is greater than or equal to the preset sliding time length, the edge sliding false touch event can be accurately detected, and the accuracy of edge sliding false touch fault detection is improved.

In a possible implementation, the method further includes:

if the touch event to be detected is an edge sliding error touch event, then: obtaining a first number of false touch events within a first time period; the first time period is a time period between the occurrence time of a press-down event and the occurrence time of a lift-up event in the touch event to be detected; acquiring a second number of touch events in a first time period; and if the second quantity is greater than the first quantity, determining that the touch event to be detected is an edge sliding false touch event which can be sensed by the user.

In the implementation mode, under the condition that the touch event to be detected is determined to be the edge sliding mis-touch event, whether the touch event is the user-perceivable edge sliding mis-touch event is determined, and the edge sliding mis-touch event is further matched with the edge mis-touch fault in the actual use of the user, so that the user experience is truly reflected, the follow-up targeted analysis, processing and improvement are facilitated, and the user experience is further improved.

In a possible implementation manner, the preset edge mis-touch area includes a third preset area, and according to the preset edge mis-touch area and the touch position, the touch distance, and the touch duration of the touch event to be detected, it is determined whether the touch event to be detected is one of a plurality of preset types of edge mis-touch events, including:

if the touch position of the touch event to be detected belongs to a third preset area, the touch distance of the touch event to be detected is smaller than or equal to a third preset distance, and the touch duration of the touch event to be detected is smaller than or equal to a preset quick click duration, determining that the touch event to be detected is a corner quick click mistaken touch event.

Optionally, the third preset area may be an area with an X coordinate of 0pixel to 1pixel and a Y coordinate of length-150pixel to length-1pixel, and an area with an X coordinate of length-2 pixel to width-1pixel and a Y coordinate of length-150pixel to length-1pixel, where width is a pixel width of a display screen of the electronic device and length is a pixel length of the display screen of the electronic device.

Alternatively, the third preset distance may be 0 pixel.

Optionally, the preset quick click duration may be 150 ms.

In the implementation manner, whether the touch position, the touch distance and the touch duration of the touch event to be detected are matched with the parameter conditions of the corner quick-click mistaken-touch event or not is determined, so that whether the touch event to be detected is the corner quick-click mistaken-touch event or not is determined. Therefore, in the implementation manner, by determining that the touch position of the touch event to be detected belongs to the third preset region, the touch distance of the touch event to be detected is less than or equal to the third preset distance, and the touch duration of the touch event to be detected is less than or equal to the preset quick click duration, the corner quick click false touch event can be accurately detected, and the accuracy of corner quick click false touch fault detection is improved.

In one possible implementation manner, the multiple preset types of edge false touch events include edge continuous click false touch events, and the preset edge false touch area includes a fourth preset area; determining whether the touch event to be detected is one of a plurality of preset types of edge false touch events according to a preset edge false touch area, and the touch position and the touch distance of the touch event to be detected, including:

if the touch position of the touch event to be detected belongs to a fourth preset area and the touch distance of the touch event to be detected is smaller than or equal to a second preset distance, acquiring data of m touch events which are continuous in time with the touch event to be detected after the touch event to be detected; m is a positive integer;

respectively determining touch positions and touch distances of the m touch events according to the data of the m touch events;

if the touch positions of the m touch events belong to a fourth preset area, the touch distances of the m touch events are smaller than or equal to a second preset distance, and the duration of the continuous events is larger than or equal to a preset continuous clicking duration, determining that the touch events to be detected and the m touch events are edge continuous clicking mis-touch events; the continuous event duration refers to a time difference between the occurrence time of the lift-up event in the last touch event of the m touch events and the occurrence time of the press-down event in the touch events to be detected.

Optionally, the fourth preset area may be the same as the first preset area and the second preset area.

Alternatively, the second preset distance may be 700 pixels.

Alternatively, m may be 3.

Optionally, the preset continuous click time may be 3000 ms.

In the implementation manner, whether the touch event to be detected and the m touch events to be detected and the edge continuously click the mistaken touch event or not is determined according to the data of the touch event to be detected and the data of the m touch events to be detected and the data of the touch event to be detected, which are continuous in time after the touch event to be detected and the touch event to be detected. Therefore, in the implementation manner, by determining that the touch positions of the touch event to be detected and the m touch events belong to the fourth preset region, the touch distances of the touch event to be detected and the m touch events are both smaller than or equal to the second preset distance, and the duration of the continuous event is greater than or equal to the preset continuous click duration, the edge continuous click false touch event can be accurately detected, and the accuracy of edge continuous click false touch fault detection is improved.

In a possible implementation, the method further includes:

if the touch event to be detected and the m touch events are edge continuous click mistaken touch events, then: acquiring a third number of false touch events within a second time period; the second time period is a time period between the occurrence time of a press-down event in the touch events to be detected and the occurrence time of a lift-up event in the last touch event of the m touch events; acquiring a second number of touch events in a second time period; and if the second quantity is greater than the third quantity, determining that the touch events to be detected and the m touch events are edge continuous clicking mistaken touch events which can be perceived by the user.

Alternatively, the third number may be determined by acquiring the number of event identifications of the edge false touch event in the second time period.

In the implementation mode, under the condition that the touch event to be detected and the m touch events are determined to be edge continuous clicking mistaken touch events, whether the edge continuous clicking mistaken touch events are the user-perceivable edge continuous clicking mistaken touch events is determined, the edge continuous clicking mistaken touch events are further matched with the edge mistaken touch fault types generated in the actual use of a user, the user experience is truly reflected, therefore, the follow-up targeted analysis, processing and improvement are facilitated, and the user experience is further improved.

In one possible implementation, the first data includes a hit coordinate of a press-down event, and the second data includes a hit coordinate of a lift-up event; determining a touch position and a touch distance of the touch event to be detected according to the first data and the second data of the touch event to be detected, including:

determining the touch position of the touch event to be detected according to the report point coordinates of the press event and the report point coordinates of the lift event in the touch event to be detected; determining an absolute value of a difference value of the report point coordinate of the lifting event and the report point coordinate of the pressing event in the preset direction in the touch event to be detected, and obtaining the touch distance of the touch event to be detected.

In the implementation mode, the touch position and the touch distance of the touch event to be detected can be simply and accurately determined by pressing the report point coordinates of the event and lifting the report point coordinates of the event, and the operation efficiency of the algorithm is improved.

In a second aspect, the present application provides an edge miss-touch detection apparatus having the functionality of the first aspect described above and possible implementations of the first aspect described above. The functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above-described functions. Such as an acquisition module or unit, a detection module or unit, etc.

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

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

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

Further optionally, the chip further comprises a communication interface.

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

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

It is to be understood that, for the beneficial effects of the second, third, fourth, fifth and sixth aspects, reference may be made to the description of the first aspect, and details are not repeated here.

Drawings

FIG. 1 is a schematic diagram of an example of a scenario of an edge false touch fault according to an embodiment of the present disclosure;

FIG. 2 is a block diagram of an exemplary software architecture of an electronic device according to an embodiment of the present disclosure;

fig. 3 is a schematic view illustrating a touch control process of an electronic device according to an embodiment of the present disclosure;

FIG. 4 is a schematic diagram illustrating an example of a detection process of an edge miss-touch according to an embodiment of the present disclosure;

FIG. 5 is a flowchart illustrating an example of a method for detecting an edge miss-touch according to an embodiment of the present disclosure;

FIG. 6 is a diagram illustrating an example of first data provided by an embodiment of the present application;

FIG. 7 is a diagram illustrating an example of second data provided by an embodiment of the present application;

fig. 8 is a schematic diagram of a screen coordinate system and a preset edge miss-touch area of a mobile phone according to an embodiment of the present disclosure;

FIG. 9 is a flowchart illustrating an example of a method for detecting an edge miss-touch according to an embodiment of the present disclosure;

fig. 10 is a schematic diagram of a screen coordinate system and a first predetermined area of a mobile phone according to an embodiment of the present application;

FIG. 11 is a schematic diagram of another example of a fault of edge miss-touch according to an embodiment of the present disclosure;

fig. 12 is a schematic diagram illustrating a hit of a touch event corresponding to an edge long press false touch scene that is perceivable by a user according to an embodiment of the present application;

FIG. 13 is a flowchart illustrating an example of a method for detecting an edge miss-touch according to an embodiment of the present disclosure;

fig. 14 is a schematic diagram illustrating an example of a hit of a touch event corresponding to a user-perceivable edge sliding miss-touch scene according to an embodiment of the present disclosure;

FIG. 15 is a flowchart illustrating an example of a method for detecting an edge miss-touch according to an embodiment of the present disclosure;

fig. 16 is a schematic diagram of an exemplary screen coordinate system and a third predetermined area of a mobile phone according to an embodiment of the disclosure;

FIG. 17 is a flowchart illustrating an example of a method for detecting an edge miss-touch according to an embodiment of the present disclosure;

FIG. 18 is a diagram illustrating an example of a user-perceivable edge continuously clicking a hit point of a touch event corresponding to a false touch scene according to an embodiment of the present disclosure;

FIG. 19 is a schematic structural diagram of an example of a detection apparatus for edge miss-touch according to an embodiment of the present disclosure;

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

Detailed Description

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

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

Touch Panel (TP), also called Touch panel, refers to a panel capable of realizing Touch input. The touch panel can be used alone to realize a touch function, and is applied to electronic devices such as a notebook computer. The touch panel can also be used in cooperation with the display panel to form a touch display screen (also called a touch screen or a touch screen), which can realize both a display function and a touch function, and is applied to electronic devices such as mobile phones, tablet computers, wearable devices and teaching integrated machines.

No matter which electronic device is applied, the touch panel may have an edge error touch fault in the using process. Taking the touch panel applied to the mobile phone as an example for explanation:

fig. 1 is a schematic view of a scenario of an edge miss-touch fault according to an embodiment of the present disclosure. As shown in fig. 1, when a user holds a mobile phone, a finger may touch an edge of a touch screen, and a touch panel of the touch screen recognizes a touch operation and executes the corresponding operation, which may cause that when another hand of the user executes a normal touch operation, the touch panel cannot recognize an input of the normal touch operation, and thus the user cannot realize an intended operation.

For the error touch fault of the edge, an edge error touch prevention algorithm is generally adopted for processing so as to avoid the influence of the error touch of the edge on the normal operation of a user. However, whether in the design phase, test phase, application phase, or improvement phase of the edge anti-false touch algorithm, there is a need to identify and detect edge false touch events. The embodiment of the application aims to provide a method for detecting edge false touch, which is used for identifying and detecting an edge false touch event.

For convenience of understanding, before describing the method for detecting edge false touch provided in the embodiment of the present application, a software structure of an electronic device with a touch function and a process of the electronic device implementing the touch function are described first.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The user performs a touch operation through the touch panel 201. The touch operation includes, but is not limited to, a touch operation, a click operation, a slide operation, a long press operation (also referred to as a long press operation), and the like. The touch panel 201 receives a touch operation of a user, generates a touch signal, and reports the generated touch signal to the touch signal processing module 202 of the kernel layer. The touch signal processing module 202 receives the touch signal, performs encapsulation processing on the touch signal, and outputs the encapsulated touch signal to the touch data generation module 203 of the kernel layer. Optionally, the touch signal processing module 202 may report the encapsulated touch signal to the touch data generating module 203 through an I2C interface, an MIPI interface, or an SPI interface. The touch data generation module 203 performs normalization processing, data calibration, and other processing on the touch signal, and further generates data (input.c) of a touch event. It is understood that a user performs a touch operation to generate one or more touch events. One touch event corresponds to the operation of a touch object (e.g., a finger or a stylus), and one touch event corresponds to a set of data. For example, the user performs a slide-up operation on the screen, possibly with one finger or with multiple fingers. And generating a touch event corresponding to a group of data by the operation of each finger on the screen.

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

It can be understood that after the touch data generating module 203 generates the data of the touch event, the data of the touch event can 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 generation module 203 generates data of one touch event, the touch data generation module 203 sends the data of the touch event to the log generation module 207, and the log generation module 207 writes part or all of the data of the touch event into a log file. The log file may be stored in a memory of the electronic device or may be transmitted to another electronic device, for example, to a server.

The method for detecting edge false touch provided by the embodiment of the application is used for processing the data of the touch event generated by the electronic equipment with the structure shown in fig. 2 and 3 so as to detect the edge false touch fault. Specifically, the method provided in the embodiment of the present application is used for processing the data (input.c) of the touch event generated by the touch data generating module 203 shown in the embodiment of fig. 3.

It should be noted that the method for detecting edge false touch provided by the embodiment of the present application may be applied to an electronic device. The electronic device may be the electronic device having the touch function, that is, capable of generating data of a touch event, such as a terminal device; other electronic devices, such as servers, communicatively connected to the electronic device generating the data of the touch event are also possible. The terminal device may be a mobile phone, a tablet computer, a wearable device, an in-vehicle device, an Augmented Reality (AR)/Virtual Reality (VR) device, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a Personal Digital Assistant (PDA), and other devices having a touch function. When the method provided by the embodiment of the application is applied to the terminal device, optionally, the terminal device can acquire the data of the touch event from the kernel layer in real time and process the data of the touch event so as to detect the edge false touch event. Optionally, the generated data of the touch event may also be stored in a memory in the form of an operation log, and the terminal device may acquire 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 and can also be a physical server. Optionally, the electronic device generating the data of the touch event may upload the generated data of the touch event to a server in the form of an operation log, and the server processes the data of the touch event to detect an edge false touch event.

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

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

s401, a user executes touch operation through the touch panel.

S402, the touch panel receives touch operation of a user and generates a touch signal.

And S403, the touch panel reports the generated touch signal to the touch signal processing module.

S404, the touch signal processing module receives the touch signal and packages the touch signal.

S405, the touch signal processing module sends the packaged touch signal to the touch data generation module.

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

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

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

That is, the log generation module writes part or all of the data of each touch event into the log file.

And S409, the log generation module sends the log file to the communication module.

S4010, the communication module sends the log file to a server.

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

S4011, the server receives the log file sent by the communication module, and detects an edge false touch fault according to the data of the touch event in the log file.

In the following embodiment, based on the structures and the flows shown in fig. 2 to fig. 4, with reference to the accompanying drawings and application scenarios, a specific process of detecting an edge false touch fault by a server according to data of a touch event in a log file will be described.

Fig. 5 is a schematic flowchart of an example of a method for detecting edge miss-touch according to an embodiment of the present application, and as shown in fig. 5, the method includes:

s501, data of a touch event to be detected are obtained, wherein the touch event comprises a press-down event and a lift-up event, and the data of the touch event comprises first data of the press-down event and second data of the lift-up event.

The server may store data of a plurality of touch events. The server may process data of the multiple touch events one by one, and detect whether each touch event is an edge miss-touch event, that is, perform each step in the embodiment of the present application on the data of the multiple touch events one by one. The touch event currently being processed is referred to as a touch event to be detected.

Optionally, in this embodiment, each touch event includes a press-DOWN (DOWN) event and a lift-UP (UP) event. The pressing event corresponds to a pressing operation of a finger or a stylus pen of the user, namely the finger or the stylus pen of the user is in contact with the screen. The lift-off event corresponds to a lift-off operation of a user's finger, stylus pen, or the like, that is, the user's finger, stylus pen, or the like leaves the screen.

Accordingly, the data of each touch event may include data of a press-down event (hereinafter, referred to as first data) and data of a lift-up event (hereinafter, referred to as second data). The first data may include hit coordinates (including abscissa and ordinate, i.e., X and Y coordinates) of the hit event, a hit time of the hit event, an event identification, and the like. The event identifier may also be referred to as an event number, a Tracking ID, or the like, and is used to represent a unique identity of the touch event. One touch event corresponds to one event identifier, and a press-down event and a lift-up event in one touch event correspond to the same event identifier. In other words, one touch event corresponds to a pair of press/lift events, and the event identifiers are the same one press event and one lift event as a pair of press/lift events.

The second data may include the hit coordinates (including abscissa and ordinate, i.e., X and Y coordinates) of the lift event, the time of the hit of the lift event, the event identification, and the like.

It can be understood that one touch event corresponds to one event identifier, that is, the event identifier in the first data and the event identifier in the second data of the same touch event are the same. In addition, as described above, one touch event includes one press-down event and one lift-up event, i.e., one touch event includes a pair of press-down/lift-up events. The event identification is the same one press down event and one lift up event as a pair of press down/lift up events.

Optionally, the first data and the second data may further include other data such as a report rate, which is not limited in this embodiment of the application.

For example, fig. 6 is a schematic diagram of an example of first data (i.e., data of a press-down event) provided in the embodiment of the present application. As shown in FIG. 6, "BTN _ TOUCH DOWN" as shown at 604 characterizes the set of data as the first data. The first data includes hit coordinates for a press event: x-coordinate 601 and Y-coordinate 602. The first data further includes an event identifier 603, a time point 605 when the event is pressed, a point rate 606, and the like.

For example, fig. 7 is a schematic diagram of an example of the second data (i.e., data of a lift-off event) provided in the embodiment of the present application. As shown in FIG. 7, "BTN _ TOUCH UP" shown at 704 characterizes the set of data as second data. The second data includes the breakpoint coordinates of the lift event: x-coordinate 701 and Y-coordinate 702. The second data further includes an event identifier 703, a time of a tick for a lift event 705, a tick rate 706, and the like.

S502, determining whether the touch event to be detected is one of a plurality of preset types of edge false touch events according to a preset edge false touch area of the terminal device and the first data and the second data of the touch event to be detected.

And the preset edge mis-touch area of the terminal equipment is used for screening edge mis-touch events from the touch position. The touch position refers to an occurrence position of a touch event, namely a position where a user contacts a screen of the terminal device. That is, the touch position of the touch event is located in the predetermined edge mis-touch area, and the touch event may be an edge mis-touch event. If the touch position of the touch event is located outside the preset edge touch area, the touch event does not belong to an edge false touch event.

The preset edge mis-touch area can be set according to actual requirements. For example, taking a mobile phone as an example, fig. 8 is a schematic diagram of a screen coordinate system and a preset edge miss-touch area of the mobile phone according to an embodiment of the present disclosure. As shown in fig. 8, let the width direction of the mobile phone be the X coordinate direction, the length direction of the mobile phone be the Y coordinate direction, and the upper left corner of the screen when holding the mobile phone is the coordinate 0 point. Optionally, the X coordinate, the Y coordinate, and the preset edge miss-touch area may be measured by taking pixel points as units. And if the pixel width and the pixel length of the mobile phone display screen are respectively set as width and length, the range of the X coordinate is 0pixel to width-1pixel, and the range of the Y coordinate is 0pixel to length-1 pixel. For example, the resolution of the mobile phone is 2400 × 1080, that is, the display screen of the mobile phone is divided into 1080 pixels in the X coordinate direction and 2400 pixels in the Y coordinate direction, then the pixel width of the mobile phone is 1080 pixels, and the pixel length of the mobile phone is 2400 pixels. The X-coordinate ranges from 0pixel to 1079pixel and the Y-coordinate ranges from 0pixel to 2399 pixel.

The predetermined edge miss-touch area may be, for example, an area with X coordinate of 0 to X and Y coordinate of Y to length-Y-1, such as the area 801 in fig. 8. Alternatively, the default edge miss-touch area may be an area with X coordinate from width-X-1 to width-1 and Y coordinate from Y to length-Y-1, such as area 802 in FIG. 8. Of course, the default edge miss-touch area may include both the area 801 and the area 802.

There may be various types of edge false touches depending on the actual operation of the user. In this embodiment, a plurality of types of edge false touch events may be predefined, and a determination condition of each type of edge false touch event may be defined. The server determines whether the touch event to be detected belongs to one of a plurality of preset types of edge false touch events according to the first data and the second data of the touch event to be detected and the preset edge false touch area of the terminal device based on the judgment condition of each type of edge false touch event.

If the touch event to be detected belongs to an edge false touch event of a certain preset type, the server can prompt the edge false touch fault, and extract and store the data of the touch event to be detected and the edge false touch type to be detected, so as to be used for subsequent analysis or processing, for example, research and development personnel can analyze the reason of the edge false touch generated by the terminal equipment, analyze the product stability of the terminal equipment, improve the false touch prevention algorithm of the terminal equipment, and the like. Optionally, after determining that the touch event to be detected belongs to an edge false touch event of a certain preset type, the server may further obtain other data related to the touch event to be detected, for example, Transparent page Pages (THP) data, for subsequent analysis or processing. The data specifically acquired by the server may be determined according to the purpose of the detection result of the edge miss-touch.

If the touch event to be detected does not belong to any one of the edge false touch events of the plurality of preset types, the determination that the touch event to be detected does not belong to the edge false touch event is made, and the data of the touch event to be detected in the server can be deleted and released.

In this embodiment, by acquiring the first data and the second data of the touch event to be detected, whether the touch event to be detected is one of a plurality of preset types of edge false touch events is determined according to the set edge false touch region of the terminal device and the first data and the second data of the touch event to be detected. The method provided by the embodiment can determine whether the touch event to be detected is an edge false touch event, so that the subsequent analysis or processing is facilitated. Meanwhile, the method provided by the embodiment can determine the type of the edge false touch, and the detection result of the edge false touch event is more accurate, so that the subsequent analysis or processing is more accurate, and the effectiveness of solving the edge false touch problem is improved.

In one embodiment, the plurality of preset types of edge mis-touch events may include edge long press mis-touch events, edge slide mis-touch events, corner quick click mis-touch events, and edge continuous click mis-touch events. The edge long press false touch event is also called an edge long press false touch event, and means that a user presses the screen in a preset edge false touch area of the screen for a time longer than a preset time. The edge sliding error touch event refers to that a user slides or reciprocates in a certain direction in a preset edge error touch area of a screen. The corner fast-clicking false-touch event refers to that a user quickly clicks (presses and then quickly lifts) at a corner of a screen, for example, when the user holds a mobile phone in a forward left direction, a left thumb clicks the screen at the lower right corner of the screen, or a left thumb clicks the screen at the lower left corner of the screen. The edge continuous clicking false touch event is also called an edge adjacent position continuous lifting and pressing false touch event, and means that a user performs clicking operation for multiple times near a certain position in a preset edge false touch area of a screen.

It can be understood that after the server acquires the first data and the second data of the touch event to be detected, the server firstly determines parameters required for judging the type of the edge false touch event according to the first data and the second data respectively; and then matching the determined parameters with the parameter conditions of the edge false touch events of various types respectively, if the determined parameters are successfully matched with the parameter conditions of the edge false touch events of a certain type, determining that the touch event to be detected belongs to the edge false touch event of the type, otherwise, determining that the touch event does not belong to the edge false touch event of the type. And if the touch event to be detected does not belong to any one of the preset types of edge false touch events, determining that the touch event to be detected does not belong to the edge false touch event.

Optionally, the parameters required to determine different types of edge false touch events may be different. As a possible implementation manner, the parameters required for determining whether the touch event to be detected is an edge long press false touch event, an edge sliding false touch event, and a corner quick click false touch event may include: touch position, touch distance and touch duration.

The touch position may include a position of a press-down event and a position of a lift-up event. The location of a press event may be characterized by the strike coordinates of a press event and the location of a lift event may be characterized by the strike coordinates of a lift event.

The touch distance is used for representing the distance between the position of the press-down event and the position of the lift-up event in the preset direction in the touch event. In some embodiments, the preset direction may be, for example, a longitudinal coordinate direction of the terminal device, and the touch distance may be an absolute value of a difference between a longitudinal coordinate of the lift event and a longitudinal coordinate of the press event, that is: touch distance ═ y _up -y _down L. In other embodiments, when the screen of the terminal device (e.g., a smart watch) is circular, the predetermined direction may be a predetermined arc, and the touch distance may be a distance along the predetermined arc between a lift event and a press event.

The touch duration is used for representing the time difference between the occurrence time of the lift-up event and the occurrence time of the press-down event in the touch event. Specifically, the touch duration may be obtained by calculating a difference between a click reporting time of a lift event and a click reporting time of a press event in the touch event, that is: touch duration t _up -t _down 。

The following describes the determination processes of the edge long press false touch event, the edge sliding false touch event, and the corner quick click false touch event, respectively, with reference to the drawings.

Fig. 9 is a schematic flowchart of an example of a method for detecting an edge miss-touch according to an embodiment of the present disclosure. As shown in fig. 9, the method for determining whether the touch event to be detected belongs to the edge long press false touch event includes:

s901, judging whether the touch position of the touch event to be detected belongs to a first preset area.

Optionally, the server may determine whether both the lift event and the press event in the to-be-detected touch event belong to a first preset area. Specifically, the server may determine whether the report point coordinate of the lift event and the report point coordinate of the press event in the touch event to be detected both belong to a first preset area; if so, determining that the touch position of the touch event to be detected belongs to a first preset area, and executing a step S902; if not, determining that the touch position of the touch event to be detected does not belong to the first preset area, and executing step S905.

For example, fig. 10 is a schematic diagram of a screen coordinate system and a first preset area of a mobile phone according to an embodiment of the present application. As shown in fig. 10, alternatively, the first preset area may be, for example, an area with X coordinates of 0pixel to 5 pixels, as shown by an area 1001 in fig. 10, and an area with X coordinates of width-6pixel to width-1pixel, as shown by an area 1002 in fig. 10. Namely: the server judges whether the rising event point coordinates and the rising event point coordinates in the touch events to be detected belong to a data set [0, 1, 2, 3, 4, 5] or a data set [ width-6, width-5, width-4, width-3, width-2, width-1], unit pixel.

S902, judging whether the touch distance of the touch event to be detected is smaller than or equal to a first preset distance.

Alternatively, the first preset distance may be, for example, 30 pixels. Specifically, the server judges whether the touch distance of the touch event to be detected meets the condition that y is less than or equal to 0pixel _up -y _down | is less than or equal to 30 pixels; if yes, go to step S903; if not, go to step S905.

S903, judging whether the touch duration of the touch event to be detected is larger than or equal to the preset long pressing duration.

The preset long pressing time can be set according to actual requirements. Alternatively, the preset long press time may be 1500ms, for example. Specifically, the server determines whether the touch duration of the touch event to be detected satisfies t _up -t _down More than or equal to 1500 ms; if yes, go to step S904; if not, go to step S905.

And S904, determining that the touch event to be detected is an edge long press mistaken touch event.

If the touch event to be detected is determined to be an edge long press false touch event, the server may prompt an edge false touch fault, extract and store data of the touch event to be detected and an edge false touch type to which the data belong, take the next touch event as the touch event to be detected, and return to execute step S501 to determine whether the next touch event is one of a plurality of preset types of edge false touch events.

S905, determining that the touch event to be detected is not an edge long press mistaken touch event.

If the touch event to be detected is determined not to be the edge long press false touch event, the server further determines whether the touch event to be detected is the next type of edge false touch event, for example, whether the touch event to be detected is the edge sliding false touch event.

In this embodiment, whether the touch position, the touch distance, and the touch duration of the touch event to be detected are matched with the parameter conditions of the edge long press false touch event is determined to determine whether the touch event to be detected is the edge long press false touch event. The edge long press false touch event is a type of edge false touch which can be encountered during the actual use process of a user. In the embodiment, the real experience of the user in the terminal using process is fully considered, the edge long press false touch event in the touch event can be intelligently detected, the edge long press false touch event is matched with the edge false touch fault type in the actual use of the user, the subsequent analysis, processing and improvement on the data of the edge long press false touch event are facilitated, and the user experience is improved. In addition, the first preset area, the first preset distance and the preset long press duration can quantitatively embody the characteristic of the edge long press false touch event, so in this embodiment, by determining that the touch position of the to-be-detected touch event belongs to the first preset area, the touch distance of the to-be-detected touch event is less than or equal to the first preset distance, and the touch duration of the to-be-detected touch event is greater than or equal to the preset long press duration, the edge long press false touch event can be accurately detected, and the accuracy of edge long press false touch fault detection is improved.

In an embodiment, after determining that the touch event to be detected is an edge long press false touch event, it may be further determined whether the touch event to be detected is a user-perceivable edge long press false touch event. The user-perceivable edge long press false touch event means that the user performs other normal operations while the edge long press false touch occurs, and the edge long press false touch event and other edge false touch events affect the normal operations of the user, so that the user can perceive that the edge false touch event occurs.

For example, referring to fig. 11, when the user holds the mobile phone with his left hand, the middle finger and the ring finger of the left hand long press the right edge of the mobile phone, and both touch events corresponding to the middle finger and the ring finger long press operation of the left hand are edge long press false touch events. In this process, the user clicks the application "recorder" with the right index finger. For example, fig. 12 is a schematic diagram illustrating a hit of a touch event on a display screen corresponding to the application scenario illustrated in fig. 11. In fig. 12, 1201 indicates the entry point of the touch event corresponding to the middle finger of the left hand of the user, 1202 indicates the entry point of the touch event corresponding to the ring finger of the left hand of the user, and 1203 indicates the entry point of the touch event corresponding to the index finger of the right hand of the user.

Due to the fact that the fault of edge long press false touch is caused by operation of the middle finger and the ring finger of the left hand, a user clicks the application program to have no response, and further the user perceives that an edge false touch event occurs. In this scenario, the edge long press false touch event corresponding to the long press operation of the middle finger and the ring finger of the left hand is the user-sensible edge long press false touch event.

In one embodiment, whether an edge long press false touch event is a user-perceptible edge long press false touch event may be determined by:

if the touch event to be detected is determined to be an edge long press false touch event, then: acquiring the number of false touch events in a first time period to obtain a first number; the first time period refers to a time period between the occurrence time of a press-down event and the occurrence time of a lift-up event in the touch event to be detected; acquiring the number of touch events in a first time period to obtain a second number; and if the second quantity is greater than the first quantity, determining that the touch event to be detected is an edge long press false touch event which can be sensed by a user.

That is to say, the server determines whether the total number of the touch events in the time period in which the touch event to be detected occurs is greater than the number of the edge false touch events (including the edge long press false touch event and other types of edge false touch events), and if so, determines that the edge long press false touch event is the user-perceivable edge long press false touch event.

Optionally, the first number may be determined by obtaining the number of event identifiers of the edge miss-touch event in the first time period, or may be determined by obtaining a logarithm of a press/lift event in which the edge miss-touch occurs in the first time period. Similarly, the second number may be determined by obtaining the total number of event identifications in the first time period, or by obtaining the total logarithm of press/lift events in the first time period.

In this embodiment, under the condition that it is determined that the edge long press event is the edge long press false touch event, it is determined whether the touch event is the user-perceivable edge long press false touch event, and the edge long press false touch event is further matched with an edge false touch fault occurring in actual use of the user, so that user experience is truly reflected, thereby facilitating subsequent targeted analysis, processing and improvement, and further improving the user experience.

For example, fig. 13 is a schematic flowchart of an example of a method for detecting an edge miss-touch according to an embodiment of the present application. As shown in fig. 13, the method for determining whether the touch event to be detected belongs to the edge sliding false touch event includes:

s1301, judging whether the touch position of the touch event to be detected belongs to a second preset area;

if yes, go to step S1302;

if not, step S1305 is executed.

The specific process of step S1301 is similar to the process of step S901 in fig. 9, and is not described again here.

Optionally, the second preset area may be the same as or different from the first preset area. It is to be understood that, when the second preset area is the same as the first preset area, the server performs step S901, and step S1301 may not be repeated.

S1302, determining whether the touch distance of the touch event to be detected is greater than a first preset distance and less than or equal to a second preset distance.

Alternatively, the second preset distance may be, for example, 700 pixels. Specifically, the server judges whether the touch distance of the touch event to be detected meets 30pixel < | y _up -y _down Less than or equal to 700 pixels; if yes, go to step S1303; if not, step S1305 is executed.

S1303, judging whether the touch duration of the touch event to be detected is greater than or equal to a preset sliding duration.

The preset sliding time length can be set according to actual requirements. Optionally, the preset sliding time length may be equal to the preset long press time length, which is also 1500 ms. Specifically, the server determines whether the touch duration of the touch event to be detected satisfies t _up -t _down More than or equal to 1500 ms; if yes, go to step S1304; if not, step S1305 is executed.

And S1304, determining that the touch event to be detected is an edge sliding error touch event.

If it is determined that the touch event to be detected is an edge sliding false touch event, the server may prompt an edge false touch fault, extract and store data of the touch event to be detected and an edge false touch type to which the data belong, take a next touch event as the touch event to be detected, and return to execute step S501 to determine whether the next touch event is one of a plurality of preset types of edge false touch events.

S1305, determining that the touch event to be detected is not an edge sliding error touch event.

If the touch event to be detected is determined not to be the edge sliding mis-touch event, the server further determines whether the touch event to be detected is the next type of edge mis-touch event, for example, whether the touch event to be detected is a corner quick-click mis-touch event.

In this embodiment, whether the touch position, the touch distance, and the touch duration of the touch event to be detected are matched with the parameter conditions of the edge sliding false touch event is determined to determine whether the touch event to be detected is the edge sliding false touch event. The edge sliding false touch event is a type of edge false touch encountered by a user during actual use. In the embodiment, the real experience of the user in the terminal using process is fully considered, the edge sliding false touch event in the touch event can be intelligently detected, the edge sliding false touch event is matched with the edge false touch fault type in the actual use of the user, the follow-up analysis, processing and improvement on the data of the edge sliding false touch event are facilitated, and the user experience is improved. In addition, the second preset area, the second preset distance, and the preset sliding duration may quantitatively embody the characteristic of the edge sliding false touch event, and therefore, in this embodiment, by determining that the touch position of the touch event to be detected belongs to the second preset area, the touch distance of the touch event to be detected is greater than the first preset distance and is less than or equal to the second preset distance, and the touch duration of the touch event to be detected is greater than or equal to the preset sliding duration, the edge sliding false touch event may be accurately detected, and the accuracy of detecting the edge sliding false touch fault is improved.

In one embodiment, after determining that the touch event to be detected is an edge sliding false touch event, it may be further determined whether the touch event to be detected is an edge sliding false touch event perceivable by a user. The user-perceivable edge sliding mis-touch event means that the user performs other normal operations while the edge sliding mis-touch occurs, and the edge sliding mis-touch event and other edge mis-touch events affect the normal operations of the user, so that the user can perceive that the edge mis-touch event occurs.

For example, in one application scenario, a user holds a mobile phone with his left hand, and the middle finger of the left hand slides at the edge of the right side of the mobile phone, thereby generating an edge slide false touch event. During this process, the user's right index finger slides up. For example, fig. 14 shows a schematic diagram of a hit of a touch event on a display screen corresponding to the application scenario. In fig. 14, 1401 denotes a touch event hit point corresponding to the middle finger of the left hand of the user, and 1402 denotes a touch event hit point corresponding to the right index finger of the right hand of the user.

The error touch fault of edge sliding caused by the sliding of the middle finger of the left hand causes no response of upward sliding of the index finger of the right hand of the user, and further the occurrence of an edge error touch event is sensed. In this scenario, the edge sliding false touch event corresponding to the sliding operation of the middle finger of the left hand is the user-perceivable edge sliding false touch event.

In one embodiment, the method for determining whether the edge sliding false touch event is the user-perceivable edge sliding false touch event is similar to the process for determining the user-perceivable edge long press false touch, and can be implemented by the following steps:

if the touch event to be detected is determined to be an edge sliding error touch event, then:

acquiring the number of false touch events in a first time period to obtain a first number; the first time period refers to a time period between the occurrence time of a press-down event and the occurrence time of a lift-up event in the touch event to be detected; acquiring the number of touch events in a first time period to obtain a second number; and if the second quantity is greater than the first quantity, determining that the touch event to be detected is an edge sliding false touch event which can be sensed by the user.

That is to say, the server determines whether the total number of the touch events in the time period in which the edge sliding false touch event occurs is greater than the total number of the edge false touch events (including the edge sliding false touch event and other edge false touch events), and if so, determines that the edge sliding false touch event is the user-perceivable edge sliding false touch event.

In this embodiment, under the condition that it is determined that the touch event to be detected is the edge sliding false touch event, it is determined whether the touch event is the user-perceivable edge sliding false touch event, and the edge sliding false touch event is further matched with an edge false touch fault occurring in the actual use of the user, so that the user experience is truly reflected, thereby facilitating subsequent targeted analysis, processing and improvement, and further improving the user experience.

For example, fig. 15 is a flowchart illustrating an example of a method for detecting an edge miss-touch according to an embodiment of the present application. As shown in fig. 15, the method for determining whether the touch event to be detected belongs to the corner quick click event includes:

s1501, judging whether the touch position of the touch event to be detected belongs to a third preset area;

if yes, go to step S1502;

if not, step S1505 is executed.

The specific process of step S1501 is similar to the process of step S901 in fig. 9, and is not described herein again.

For example, fig. 16 is a schematic diagram of a screen coordinate system and a third preset area of a mobile phone according to an embodiment of the present application. As shown in fig. 16, optionally, the third preset area may be, for example, an area with X coordinates of 0pixel to 1pixel and Y coordinates of length-150pixel to length-1pixel, as shown in an area 1601 in fig. 16; and regions with X coordinates from width-2pixel to width-1pixel and Y coordinates from length-150pixel to length-1pixel, as shown by region 1602 in FIG. 16. Namely: the server judges whether the rising event report point coordinate and the rising event report point coordinate in the touch event to be detected belong to a data set [0, 1] or a data set [ width-2, width-1] (unit pixel) or not, and judges whether the rising event report point coordinate and the rising event report point coordinate belong to a length-150, length-1] (unit pixel) or not.

S1502, determining whether a touch distance of the to-be-detected touch event is less than or equal to a third preset distance, where the third preset distance is less than the first preset distance.

Alternatively, in one embodiment, the third predetermined distance may be, for example, 1 pixel. Optionally, in another embodiment, the third preset distance may also be 0. That is, step S1502 is substantially the step of determining whether the touch distance of the touch event to be detected is 0, i.e. determining | y _up -y _down Whether | is equal to 0; if yes, go to step S1503; if not, step S1505 is executed.

S1503, whether the touch duration of the touch event to be detected is smaller than or equal to a preset quick click duration is judged.

The preset quick click duration can be set according to actual requirements. Optionally, the preset quick click duration may be 150 ms. Specifically, the server determines whether the touch duration of the touch event to be detected satisfies t _up -t _down Less than or equal to 150 ms; if yes, go to step S1504; if not, step S1505 is executed.

S1504, determining that the touch event to be detected is a corner quick click mistaken touch event.

If it is determined that the touch event to be detected is the corner quick-click false touch event, the server may prompt an edge false touch fault, extract and store data of the touch event to be detected and an edge false touch type to which the data belong, take the next touch event as the touch event to be detected, and return to execute step S501 to determine whether the next touch event is one of a plurality of preset types of edge false touch events.

S1505, determining that the touch event to be detected is not a corner quick click mistaken touch event.

If the touch event to be detected is determined not to be the corner quick-click mistaken-touch event, the server further determines whether the touch event to be detected is the next type of edge mistaken-touch event, for example, whether the touch event to be detected is the edge continuous-click mistaken-touch event.

In this embodiment, whether the touch position, the touch distance, and the touch duration of the touch event to be detected are matched with the parameter condition of the corner fast click false touch event is determined to determine whether the touch event to be detected is the corner fast click false touch event. The corner quick click false touch event is also a type of edge false touch which can be encountered in the actual use process of a user. In the embodiment, the real experience of the user in the terminal using process is fully considered, the corner quick-click mistaken-touch event in the touch event can be intelligently detected, the corner quick-click mistaken-touch event is matched with the edge mistaken-touch fault type in the actual use of the user, the follow-up analysis, processing and improvement on the data of the corner quick-click mistaken-touch event are facilitated, and the user experience is improved. In addition, the third preset area, the third preset distance, and the preset fast click duration may quantitatively embody the characteristic of the corner fast click false touch event, and therefore, in this embodiment, by determining that the touch position of the touch event to be detected belongs to the third preset area, the touch distance of the touch event to be detected is less than or equal to the third preset distance, and the touch duration of the touch event to be detected is less than or equal to the preset fast click duration, the corner fast click false touch event may be accurately detected, and the accuracy of detecting the corner fast click false touch fault is improved.

The following describes a determination process of the edge continuous click miss-touch event with reference to the drawings.

For example, fig. 17 is a flowchart illustrating an example of a method for detecting an edge miss-touch according to an embodiment of the present application. As shown in fig. 17, the method for determining whether the touch event to be detected belongs to the edge continuous click mis-touch event includes:

s1701, judging whether the touch position of the touch event to be detected belongs to a fourth preset area;

if yes, go to step S1702;

if not, go to step S1708.

The specific process of step S1701 is similar to the process of step S901 in fig. 9, and is not described again here.

Optionally, the fourth preset area may be the same as or different from the first preset area and the second preset area. It is to be understood that the server performs step S901 or S1301 when the fourth preset area is the same as the first preset area or the second preset area, and step S1701 may not be repeatedly performed.

S1702, determine whether the touch distance of the touch event to be detected is less than or equal to a second predetermined distance.

Optionally, taking the second preset distance as 700 pixels as an example, specifically, the server determines whether the touch distance of the touch event to be detected satisfies | y | _up -y _down Less than or equal to 700 pixels; if yes, go to step S1703; if not, go to step S1708.

S1703, data of m touch events after the to-be-detected touch event and the to-be-detected touch event are acquired, where m is a positive integer.

The specific value of m can be set according to actual requirements, and m can be 3, for example.

Optionally, the data of m adjacent touch events after the click point reporting time of the lift event can be acquired according to the click point reporting time of the lift event in the touch events to be detected. Each touch event in the m touch events comprises a press-down event and a lift-up event, and the data of each touch event comprises first data of the lift-up event and second data of the press-down event in the touch events.

And S1704, respectively determining the touch positions and the touch distances of the m touch events according to the data of the m touch events.

The specific process of determining the touch positions and touch distances of the m touch events is the same as the specific process of determining the touch positions and touch distances of the touch events to be detected in the above embodiments, and is not repeated here.

S1705, determining whether the touch positions of the m touch events all belong to a fourth preset area, and whether the touch distances of the m touch events are all less than or equal to a second preset distance.

If the touch positions of the m touch events all belong to the fourth preset area and the touch distances of the m touch events are all smaller than or equal to the second preset distance, executing step S1706; otherwise, step S1708 is performed.

Optionally, the server may also perform the relevant processes in steps S1703 to S1705 one by one for the m touch events according to the event identifier. Specifically, it is assumed that the event identifier of the touch event to be detected is n, and after the hit point time of the lift event in the touch event to be detected, the event identifiers of m touch events are n +1, n +2, …, and n + m in sequence. If the server determines that the touch distance of the touch event to be detected is less than or equal to the second preset distance in step 1702, the following steps are performed:

1) acquiring first data and second data of a touch event with an event identifier of n + 1;

2) determining a touch position of the touch event with the event identifier n +1 according to the first data and the second data of the touch event with the event identifier n + 1;

3) determining whether the touch position of the touch event with the event identifier of n +1 belongs to a fourth preset area;

4) if the touch position of the touch event with the event identifier of n +1 does not belong to the fourth preset area, executing step S1708;

5) if the touch position of the touch event with the event identifier of n +1 belongs to a fourth preset area, determining the touch distance of the touch event with the event identifier of n +1 according to the first data and the second data of the touch event with the event identifier of n + 1;

6) determining whether the touch distance of the touch event with the event identifier n +1 is smaller than or equal to a second preset distance;

7) if the touch distance of the touch event with the event identifier n +1 is greater than the second preset distance, executing step S1708;

8) if the touch distance of the touch event with the event identifier n +1 is smaller than or equal to a second preset distance, repeating the processes 1) to 7) to judge the touch event with the event identifier n + 2;

by analogy, touch events with the event identifications of n +3, … and n + m are respectively judged;

9) if the touch event with the event identifier n + m is judged, the result of the step 6) is: if the touch distance of the touch event with the event identifier n + m is smaller than or equal to the second preset distance, determining that the touch positions of the m touch events all belong to the fourth preset area, and the touch distances of the m touch events are smaller than or equal to the second preset distance, and executing step S1706; otherwise, step S1708 is performed.

S1706, judging whether the duration of the continuous event is greater than or equal to a preset continuous click duration; the continuous event duration refers to a time difference between the occurrence time of the lift-up event of the last touch event in the m touch events and the occurrence time of the press-down event in the touch events to be detected.

The preset continuous click duration can be set according to actual requirements. Optionally, the preset continuous click time may be 3000 ms. Namely, the server judges whether the duration of the continuous event is greater than or equal to 3000 ms; if yes, go to step S1707; if not, go to step S1708.

S1707, determining the touch event to be detected and the m touch events as edge continuous clicking mistaken touch events.

If it is determined that the touch event to be detected and the m touch events are edge continuous click false touch events, the server may prompt an edge false touch fault, extract and store data of the touch event to be detected and the m touch events and the edge false touch type to which the data belong, take the next touch event after the m touch events as the touch event to be detected, and return to execute step S501 to determine whether the touch event is one of a plurality of preset types of edge false touch events.

And S1708, determining that the touch event to be detected is not an edge continuous clicking mistaken touch event.

If it is determined that the touch event to be detected is not an edge continuous click mis-touch event and the edge continuous click mis-touch is the last one of the preset edge mis-touch types, the server may use a next touch event (i.e., the touch event with the event identifier n + 1) after the touch event to be detected as the touch event to be detected, and return to the step S501 to determine whether the touch event is one of the preset edge mis-touch events.

As can be seen from the above process, the parameters required for determining whether the touch event to be detected is an edge continuous click mis-touch event may include: the method comprises the steps of obtaining m touch events after a touch event to be detected and after the touch event to be detected, and the duration of the continuous events.

In this embodiment, whether the touch event to be detected and the m touch events are continuously clicked with the edge to generate the false touch event is determined according to the data of the touch event to be detected and the data of the m touch events which are continuous in time after the touch event to be detected and the touch event to be detected. The edge continuous clicking false touch event is a type of edge false touch encountered in the actual using process of a user. In the embodiment, the real experience of the user in the terminal using process is fully considered, the edge continuous clicking false touch event in the touch event can be intelligently detected, the edge continuous clicking false touch event is matched with the edge false touch fault type in the actual use of the user, the follow-up analysis, processing and improvement on the data of the edge continuous clicking false touch event are facilitated, and the user experience is improved. In addition, the fourth preset area, the second preset distance and the preset continuous clicking time length can quantitatively reflect the characteristic of the edge continuous clicking false touch event, and therefore in this embodiment, by determining that the touch positions of the touch event to be detected and the m touch events all belong to the fourth preset area, the touch distances of the touch event to be detected and the m touch events are both smaller than or equal to the second preset distance, and the continuous event time length is greater than or equal to the preset continuous clicking time length, the edge continuous clicking false touch event can be accurately detected, and the accuracy of edge continuous clicking false touch fault detection is improved.

In an embodiment, after determining that the touch event to be detected and the m touch events are edge continuous clicking false touch events, it may be further determined whether the touch event to be detected and the m touch events are user-perceivable edge continuous clicking false touch events. The user-perceivable edge continuous clicking false touch event means that the user performs other normal operations while the edge continuous clicking false touch occurs, and the edge continuous clicking false touch event and other edge false touch events affect the normal operations of the user, so that the user can perceive that the edge false touch event occurs.

For example, in one application scenario, a user holds a mobile phone with his left hand, and the thumb of his left hand is continuously pressed and lifted near a certain position on the left edge of the mobile phone, thereby generating an edge continuous click false touch event. In this process, the index finger of the right hand of the user drags a certain icon to the right and down direction. For example, fig. 18 shows a schematic diagram of a hit of a touch event on a display screen corresponding to the application scenario. In fig. 18, 1801 represents the trace of the touch event corresponding to the thumb of the left hand of the user, and 1802 represents the trace of the touch event corresponding to the index finger of the right hand of the user.

The error touch fault of continuous edge clicking caused by continuous lifting and pressing of the thumb of the left hand causes no response when the index finger of the right hand of the user drags the icon to the right lower direction, and then the error touch event of the edge is sensed. In this scenario, the continuous clicking and mis-touching event corresponding to the continuous lifting and pressing operation of the thumb of the left hand is the user-perceivable continuous clicking and mis-touching event of the edge.

In one implementation, determining whether the edge continuous click false touch event is a user-perceivable edge continuous click false touch event may be implemented by:

if the touch event to be detected is determined to be an edge continuous click mis-touch event, then:

acquiring the number of false touch events in the second time period to obtain a third number; the second time period is a time period between the occurrence moment of a press-down event in the touch events to be detected and the occurrence moment of a lift-up event in the last touch event in the m touch events; acquiring the number of touch events in a second time period to obtain a second number; and if the second quantity is greater than the third quantity, determining that the touch events to be detected and the m touch events are edge continuous clicking mistaken touch events which can be perceived by the user.

That is to say, the server determines whether the total number of the touch events in the time period in which the edge continuous-click false-touch event occurs is greater than the total number of the edge false-touch events (including the edge continuous-click false-touch event and other edge false-touch events), and if so, determines that the edge continuous-click false-touch event is the user-perceivable edge continuous-click false-touch event.

Optionally, the third number may be determined by obtaining the number of event identifiers of the edge miss-touch event in the second time period, or may be determined by obtaining a logarithm of a press/lift event in which the edge miss-touch occurs in the second time period.

In the embodiment, under the condition that the touch event to be detected and the m touch events are determined to be the edge continuous clicking false touch event, whether the edge continuous clicking false touch event is the user-sensible edge continuous clicking false touch event is determined, and the edge continuous clicking false touch event is further matched with the type of the edge false touch fault occurring in the actual use of the user, so that the user experience is truly reflected, the subsequent pertinence analysis, processing and improvement are facilitated, and the user experience is further improved.

It can be understood that in the process of determining whether the touch event to be detected is one of a plurality of preset types of edge false touch events, the determination may be performed in sequence according to the above sequence, that is, first determining whether the touch event is an edge long press false touch event, then determining whether the touch event is an edge sliding false touch event, then determining whether the touch event is a corner fast click false touch event, and finally determining whether the touch event is an edge continuous click false touch event. In some embodiments, the determination may also be performed according to other sequences, which is not limited in this application.

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

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

Fig. 19 is a schematic structural diagram of a device for detecting edge miss-touch according to an embodiment of the present disclosure. As shown in fig. 19, the apparatus for detecting edge miss-touch provided in this embodiment may include:

an obtaining module 1901, configured to obtain data of a touch event to be detected, where the touch event includes a press event and a lift event, and the data of the touch event includes first data of the press event and second data of the lift event;

the detecting module 1902 is configured to determine whether the touch event to be detected is one of a plurality of preset types of edge false touch events according to a preset edge false touch area of the electronic device and the first data and the second data of the touch event to be detected.

In one embodiment, the detection module 1902 is specifically configured to: determining the touch position and the touch distance of the touch event to be detected according to the first data and the second data of the touch event to be detected; the touch distance is used for representing the distance between the position of a press-down event and the position of a lift-up event in a preset direction in the touch event; and determining whether the touch event to be detected is one of the preset types of edge false touch events according to the preset edge false touch area, and the touch position and the touch distance of the touch event to be detected.

In one embodiment, the detection module 1902 is specifically configured to: determining the touch duration of the touch event to be detected according to the first data and the second data of the touch event to be detected; the touch duration is used for representing the time difference between the occurrence moment of the lift-up event and the occurrence moment of the press-down event in the touch event; and determining whether the touch event to be detected is one of the preset types of edge false touch events according to the preset edge false touch area, and the touch position, the touch distance and the touch duration of the touch event to be detected.

In one embodiment, the plurality of preset types of edge mis-touch events include: edge long press false touch events, edge slide false touch events, and corner quick click false touch events.

In an embodiment, the preset edge miss-touch area includes a first preset area, and the detection module 1902 is specifically configured to: if the touch position of the touch event to be detected belongs to the first preset area, the touch distance of the touch event to be detected is smaller than or equal to a first preset distance, and the touch duration of the touch event to be detected is larger than or equal to a preset long press duration, determining that the touch event to be detected is the edge long press mistaken touch event.

In one embodiment, the touch position includes a position of a press-down event and a position of a lift-up event in the touch event; the detection module 1902 is specifically configured to determine that both a position of a press-down event and a position of a lift-up event in the to-be-detected touch event belong to the first preset area.

In one embodiment, the detection module 1902 is further configured to: obtaining a first number of false touch events within a first time period; the first time period is a time period between the occurrence time of a press-down event and the occurrence time of a lift-up event in the to-be-detected touch event; acquiring a second number of touch events in the first time period; and if the second quantity is larger than the first quantity, determining that the touch event to be detected is an edge long press false touch event which can be sensed by a user.

In an embodiment, the preset edge mis-touch area includes a second preset area, and the detection module 1902 is further specifically configured to: if the touch position of the touch event to be detected belongs to the second preset area, the touch distance of the touch event to be detected is greater than the first preset distance and less than or equal to the second preset distance, and the touch duration of the touch event to be detected is greater than or equal to the preset sliding duration, determining that the touch event to be detected is the edge sliding mis-touch event.

In one embodiment, the detection module 1902 is further specifically configured to: obtaining a first number of false touch events within a first time period; the first time period is a time period between the occurrence time of a press-down event and the occurrence time of a lift-up event in the to-be-detected touch event; acquiring a second number of touch events in the first time period; and if the second number is larger than the first number, determining that the touch event to be detected is an edge sliding false touch event which can be perceived by a user.

In an embodiment, the preset edge miss-touch area includes a third preset area, and the detection module 1902 is further specifically configured to: if the touch position of the touch event to be detected belongs to the third preset area, the touch distance of the touch event to be detected is smaller than or equal to a third preset distance, and the touch duration of the touch event to be detected is smaller than or equal to a preset quick click duration, determining that the touch event to be detected is the corner quick click mis-touch event.

In one embodiment, the multiple preset types of edge mis-touch events include edge continuous click mis-touch events, and the preset edge mis-touch area includes a fourth preset area; the detection module 1902 is specifically configured to:

if the touch position of the touch event to be detected belongs to a fourth preset area and the touch distance of the touch event to be detected is smaller than or equal to a second preset distance, acquiring data of m touch events which are continuous in time with the touch event to be detected after the touch event to be detected; m is a positive integer; determining touch positions and touch distances of the m touch events according to the data of the m touch events respectively; if the touch positions of the m touch events belong to the fourth preset area, the touch distances of the m touch events are smaller than or equal to the second preset distance, and the duration of the continuous event is larger than or equal to the preset continuous click duration, determining that the touch event to be detected and the m touch events are edge continuous click mis-touch events; the continuous event duration refers to a time difference between an occurrence time of a lift-up event in the last touch event of the m touch events and an occurrence time of a press-down event in the touch events to be detected.

In one embodiment, the detection module 1902 is further specifically configured to: acquiring a third number of false touch events within a second time period; the second time period is a time period between the occurrence time of a press-down event in the touch events to be detected and the occurrence time of a lift-up event in the last touch event in the m touch events; acquiring a second number of touch events in the second time period; and if the second number is larger than the third number, determining that the touch events to be detected and the m touch events are edge continuous clicking false touch events which can be perceived by a user.

In one embodiment, the first data includes hit coordinates for a press down event and the second data includes hit coordinates for a lift up event; the detection module 1902 is specifically configured to: determining the touch position of the touch event to be detected according to the report point coordinates of the press event and the report point coordinates of the lift event in the touch event to be detected; and determining an absolute value of a difference value of the report point coordinate of the lifting event and the report point coordinate of the pressing event in the preset direction in the touch event to be detected, so as to obtain the touch distance of the touch event to be detected.

The detection apparatus for edge miss-touching provided by this embodiment is used to execute the detection method for edge miss-touching, and the technical principle and the technical effect are similar, and are not described herein again.

Referring to fig. 20, a structure of an electronic device according to an embodiment of the present application is shown. The electronic device may be a terminal device or a server that generates data of a touch event in the above application embodiment. The electronic device includes: a processor 2001, a receiver 2002, a transmitter 2003, a memory 2004, and a bus 2005. The processor 2001 includes one or more processing cores, and the processor 2001 executes applications of various functions and information processing by running software programs and modules. The receiver 2002 and the transmitter 2003 may be implemented as one communication component, which may be a baseband chip. The memory 2004 is coupled to the processor 2001 by a bus 2005. The memory 2004 may be configured to store at least one program instruction, and the processor 2001 may be configured to execute the at least one program instruction to implement the solution of the above-mentioned embodiments. The implementation principle and technical effect are similar to those of the embodiments related to the method, and are not described herein again.

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

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

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

In the embodiments of the present application, the processor may be a general-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. A 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 directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a processor.

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

The memory in the embodiments of the present application may also be circuitry or any other device capable of performing a storage function for storing program instructions and/or data. Embodiments of the present application provide methods in which the methods 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, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, a network appliance, a user device, or other programmable apparatus. The computer instructions may be stored in, or transmitted from, a computer-readable storage medium to another computer-readable storage medium, for example, from one website, computer, server, or data center, over a wired (e.g., coaxial cable, fiber optics, Digital Subscriber Line (DSL), or wireless (e.g., infrared, wireless, microwave, etc.) network, the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device including one or more integrated servers, data centers, etc., the available medium may be magnetic medium (e.g., floppy disk, hard disk, magnetic tape), optical medium (e.g., digital video disc (digital video disc, DWD), or a semiconductor medium (e.g., SSD), etc.

The embodiment of the present application provides a computer program product, which enables a terminal to execute the technical solutions in the above embodiments when the computer program product runs on the terminal. The principle and technical effects are similar to those of the related embodiments, and are not described herein again.

The embodiment of the present application provides a computer-readable storage medium, on which program instructions are stored, and when the program instructions are executed by a terminal, the terminal is enabled to execute the technical solutions of the above embodiments. The principle and technical effects are similar to those of the related embodiments, and are not described herein again. In summary, the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and these modifications or substitutions do not depart from the scope of the technical solutions of the embodiments of the present application.

In addition, an apparatus, which may be specifically a chip, a component or a module, may include a processor and a memory connected to each other; when the device runs, the processor can execute the computer execution instruction stored in the memory, so that the chip can execute the edge false touch detection method in the above method embodiments.

The electronic device, the computer-readable storage medium, the computer program product, or the chip provided in this embodiment are all configured to execute the corresponding method provided above, so that the beneficial effects achieved by the electronic device, the computer-readable storage medium, the computer program product, or the chip may refer to the beneficial effects in the corresponding method provided above, and are not described herein again.

Through the description of the above embodiments, those skilled in the art will understand that, for convenience and simplicity of description, only the division of the above functional modules is used as an example, and in practical applications, the above function distribution may be completed by different functional modules as needed, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, a module or a unit may be divided into only one logic function, and may be implemented in other ways, for example, a plurality of units or components may be combined or integrated into another apparatus, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

Units described as separate parts may or may not be physically separate, and parts displayed as units may be one physical unit or a plurality of physical units, may be located in one place, or may be distributed to a plurality of different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially or partially contributed to by the prior art, or all or part of the technical solutions may be embodied in the form of a software product, where the software product is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps of the methods of the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

In addition, in the above embodiments, the description of each embodiment has an emphasis on each other, and reference may be made to the related description of other embodiments for a part that is not described or illustrated in a certain embodiment. It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. Furthermore, references to "one embodiment" or "some embodiments" or the like described in the specification of the present application mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for detecting an edge miss-touch, the method comprising:

acquiring data of a touch event to be detected, wherein the touch event comprises a press-down event and a lift-up event, and the data of the touch event comprises first data of the press-down event and second data of the lift-up event;

and determining whether the touch event to be detected is one of a plurality of preset types of edge false touch events according to a preset edge false touch area of the electronic equipment and the first data and the second data of the touch event to be detected.

2. The method according to claim 1, wherein the determining whether the touch event to be detected is one of a plurality of preset types of edge mis-touch events according to a preset edge mis-touch area of an electronic device and the first data and the second data of the touch event to be detected comprises:

determining the touch position and the touch distance of the touch event to be detected according to the first data and the second data of the touch event to be detected; the touch distance is used for representing the distance between the position of a press-down event and the position of a lift-up event in a preset direction in the touch event;

and determining whether the touch event to be detected is one of the preset types of edge false touch events according to the preset edge false touch area, and the touch position and the touch distance of the touch event to be detected.

3. The method of claim 2, further comprising:

determining whether the touch event to be detected is one of the preset types of edge false touch events according to the preset edge false touch area, and the touch position and the touch distance of the touch event to be detected, including:

and determining whether the touch event to be detected is one of the preset types of edge false touch events according to the preset edge false touch area, and the touch position, the touch distance and the touch duration of the touch event to be detected.

4. The method of claim 3, wherein the plurality of preset types of edge mis-touch events comprises: edge long press false touch events, edge slide false touch events, and corner quick click false touch events.

5. The method according to claim 4, wherein the preset edge mis-touch area comprises a first preset area, and the determining whether the touch event to be detected is one of the preset types of edge mis-touch events according to the preset edge mis-touch area and the touch position, the touch distance and the touch duration of the touch event to be detected comprises:

if the touch position of the touch event to be detected belongs to the first preset area, the touch distance of the touch event to be detected is smaller than or equal to a first preset distance, and the touch duration of the touch event to be detected is larger than or equal to a preset long press duration, determining that the touch event to be detected is the edge long press mistaken touch event.

6. The method of claim 5, wherein the touch location comprises a location of a press-down event and a location of a lift-up event in the touch event; the method for detecting the touch event includes that the touch position of the touch event to be detected belongs to the first preset area, and includes:

and the position of a press-down event and the position of a lift-up event in the touch event to be detected both belong to the first preset area.

7. The method of claim 5 or 6, further comprising:

obtaining a first number of false touch events within a first time period; the first time period is a time period between the occurrence time of a press-down event and the occurrence time of a lift-up event in the to-be-detected touch event;

acquiring a second number of touch events in the first time period;

and if the second quantity is larger than the first quantity, determining that the touch event to be detected is an edge long press false touch event which can be sensed by a user.

8. The method according to claim 4, wherein the preset edge mis-touch area comprises a second preset area, and the determining whether the touch event to be detected is one of the preset types of edge mis-touch events according to the preset edge mis-touch area and the touch position, the touch distance and the touch duration of the touch event to be detected comprises:

if the touch position of the touch event to be detected belongs to the second preset area, the touch distance of the touch event to be detected is greater than the first preset distance and less than or equal to the second preset distance, and the touch duration of the touch event to be detected is greater than or equal to the preset sliding duration, determining that the touch event to be detected is the edge sliding mis-touch event.

9. The method of claim 8, further comprising:

acquiring a second number of touch events in the first time period;

if the second number is larger than the first number, determining that the touch event to be detected is an edge sliding false touch event which can be sensed by a user.

10. The method according to claim 4, wherein the preset edge mis-touch area comprises a third preset area, and the determining whether the touch event to be detected is one of the preset types of edge mis-touch events according to the preset edge mis-touch area and the touch position, the touch distance and the touch duration of the touch event to be detected comprises:

if the touch position of the touch event to be detected belongs to the third preset area, the touch distance of the touch event to be detected is smaller than or equal to a third preset distance, and the touch duration of the touch event to be detected is smaller than or equal to a preset quick click duration, determining that the touch event to be detected is the corner quick click mis-touch event.

11. The method according to claim 2, wherein the plurality of preset types of edge mis-touch events comprise edge continuous click mis-touch events, and the preset edge mis-touch region comprises a fourth preset region;

determining touch positions and touch distances of the m touch events according to the data of the m touch events respectively;

if the touch positions of the m touch events belong to the fourth preset area, the touch distances of the m touch events are smaller than or equal to the second preset distance, and the duration of the continuous event is larger than or equal to the preset continuous click duration, determining that the touch event to be detected and the m touch events are edge continuous click mis-touch events; the continuous event duration refers to a time difference between an occurrence time of a lift-up event in the last touch event of the m touch events and an occurrence time of a press-down event in the touch events to be detected.

12. The method of claim 11, further comprising:

acquiring a third number of false touch events within a second time period; the second time period is a time period between the occurrence time of a press-down event in the touch events to be detected and the occurrence time of a lift-up event in the last touch event in the m touch events;

acquiring a second number of touch events in the second time period;

and if the second number is larger than the third number, determining that the touch events to be detected and the m touch events are edge continuous clicking false touch events which can be perceived by a user.

13. The method of any of claims 2 to 12, wherein the first data comprises a hit point coordinate of a press down event and the second data comprises a hit point coordinate of a lift up event; the determining the touch position and the touch distance of the touch event to be detected according to the first data and the second data of the touch event to be detected includes:

determining the touch position of the touch event to be detected according to the report point coordinates of the press event and the report point coordinates of the lift event in the touch event to be detected;

and determining an absolute value of a difference value of the report point coordinate of the lifting event and the report point coordinate of the pressing event in the preset direction in the touch event to be detected, so as to obtain the touch distance of the touch event to be detected.

14. 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-13.

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