Edge False Touch Detection Method, Electronic Device, and Computer-Readable Storage Medium

Abstract

An embodiment of the present application provides a method for detecting edge accidental touches, an electronic device, and a computer-readable storage medium. The method includes: obtaining 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; determining whether the touch event to be detected is one of a plurality of preset types of edge accidental touch events according to a preset edge accidental touch area of the electronic device and the first data and the second data of the touch event to be detected. The method for detecting edge accidental touches provided by the embodiment of the present application can detect edge accidental touch faults and can identify the types of edge accidental touch faults.

Description

Technical Field

[0001] The present application relates to the field of touch technology, and particularly to a method for detecting edge false touch, an electronic device, and a computer-readable storage medium. Background Art

[0002] With the rapid development of electronic technology, touch technology has been widely applied to various electronic devices. For example, touch panels are integrated in the display screens of devices such as mobile phones, tablet computers, wearable devices, and teaching all-in-one machines, enabling the devices to have touch functions while displaying. In addition, devices such as notebook computers are provided with touch panels and can also achieve touch functions.

[0003] These electronic devices with touch functions are prone to edge false touch during application. Especially when the screen-to-body ratio of electronic devices is getting higher and the frame is getting smaller, the problem of edge false touch is particularly prominent. Therefore, the requirements for edge anti-false touch algorithms are getting higher and higher. For edge anti-false touch algorithms, whether in the algorithm design stage, algorithm testing stage, algorithm application stage, or algorithm improvement stage, it is necessary to identify and detect edge false touch faults. Summary of the Invention

[0004] The present 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.

[0005] In a first aspect, the present application provides a method for detecting edge false touch, the method comprising:

[0006] Obtaining data of a touch event to be detected, wherein 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; 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 the first data and the second data of the touch event to be detected.

[0007] Optionally, if the touch event to be detected belongs to one of a plurality of preset types of edge false touch events, an edge false touch fault may be prompted.

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

[0009] In the edge accidental touch detection method provided by the first aspect, by obtaining the first data and the second data of the touch event to be detected, it is determined whether the touch event to be detected is one of multiple preset types of edge accidental touch events according to the preset edge accidental touch area of the electronic device and the first data and the second data of the touch event to be detected. This method can determine whether the touch event to be detected is an edge accidental touch event, facilitating subsequent analysis or processing; at the same time, the method provided in this embodiment can determine the type of edge accidental touch, making the detection result of the edge accidental touch event more accurate, so that subsequent analysis or processing is more accurate, improving the effectiveness of solving the edge accidental touch problem.

[0010] Combined with the first aspect, in some implementation manners of the first aspect, determining whether the touch event to be detected is one of multiple preset types of edge accidental touch events according to the preset edge accidental touch area of the electronic device and the first data and the second data of the touch event to be detected includes:

[0011] Determine the touch position and 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; wherein, the touch distance is used to represent the distance between the position of the press event and the position of the lift event in the preset direction in the touch event; according to the preset edge accidental touch area and the touch position and touch distance of the touch event to be detected, determine whether the touch event to be detected is one of multiple preset types of edge accidental touch events.

[0012] Combined with the first aspect and the above implementation manners, the method further includes:

[0013] Determine 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 to represent the time difference between the occurrence time of the lift event and the occurrence time of the press event in the touch event;

[0014] Determine whether the touch event to be detected is one of multiple preset types of edge accidental touch events according to the preset edge accidental touch area and the touch position and touch distance of the touch event to be detected includes:

[0015] Determine whether the touch event to be detected is one of multiple preset types of edge accidental touch events according to the preset edge accidental touch area and the touch position, touch distance and touch duration of the touch event to be detected.

[0016] In a possible implementation manner, the multiple preset types of edge accidental touch events include: edge long press accidental touch event, edge slide accidental touch event, corner quick click accidental touch event, and edge continuous click accidental touch event.

[0017] The edge long - press accidental touch event, edge slide accidental touch event, corner quick - click accidental touch event, and edge continuous - click accidental touch event are all types of edge accidental touches that users may encounter during actual use. In this implementation method, the real experience of users during the use of the terminal is fully considered, and it can intelligently detect the edge long - press accidental touch event in the touch event, which matches the type of edge accidental touch failure that occurs in actual user use, facilitating subsequent analysis, processing, and improvement of the data for the edge long - press accidental touch event, and improving the user experience.

[0018] In a possible implementation method, the preset edge accidental - touch area includes a first preset area. According to the preset edge accidental - touch area, as well as the touch position, touch distance, and touch duration of the touch event to be detected, it is determined whether the touch event to be detected is one of the edge accidental - touch events of multiple preset types, including:

[0019] 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 less than or equal to the first preset distance, and the touch duration of the touch event to be detected is greater than or equal to the preset long - press duration, then it is determined that the touch event to be detected is an edge long - press accidental touch event.

[0020] Optionally, the first preset area can be the area where the X - coordinate is from 0 pixel to 5 pixels, and the area where the X - coordinate is from width - 6 pixels to width - 1 pixel, where width is the pixel width of the display screen of the electronic device.

[0021] Optionally, the first preset distance can be 30 pixels.

[0022] Optionally, the preset long - press duration can be 1500 ms.

[0023] In this implementation method, by determining whether the touch position, touch distance, and touch duration of the touch event to be detected match the parameter conditions of the edge long - press accidental touch event, it is determined whether the touch event to be detected is an edge long - press accidental touch event. The first preset area, the first preset distance, and the preset long - press duration can quantitatively reflect the characteristics of the edge long - press accidental touch event. Therefore, in this implementation method, 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 less than or equal to the first preset distance, and the touch duration of the touch event to be detected is greater than or equal to the preset long - press duration, the edge long - press accidental touch event can be accurately detected, improving the accuracy of the detection of the edge long - press accidental touch failure.

[0024] In a possible implementation method, the touch position includes the position of the press event and the position of the lift event in the touch event; that the touch position of the touch event to be detected belongs to the first preset area includes:

[0025] The positions of the press event and the lift event in the touch event to be detected both belong to the first preset area.

[0026] In a possible implementation, the method further includes:

[0027] If the touch event to be detected is an edge long-press mis-touch event, then: obtain the first quantity of edge mis-touch events within the first time period; the first time period refers to the time period between the occurrence moment of the press event and the occurrence moment of the lift event in the touch event to be detected; obtain the second quantity of touch events within the first time period; if the second quantity is greater than the first quantity, determine that the touch event to be detected is an edge long-press mis-touch event that can be perceived by the user.

[0028] Optionally, the first quantity can be determined by obtaining the quantity of event identifiers of edge mis-touch events within the first time period.

[0029] Optionally, the second quantity can be determined by obtaining the quantity of event identifiers within the first time period.

[0030] In this implementation, when determining that the edge long-press event is an edge long-press mis-touch event, determine whether the touch event is an edge long-press mis-touch event that can be perceived by the user, further match it with the edge mis-touch faults that occur in the actual use of the user, truly reflect the user experience, so as to facilitate subsequent targeted analysis, processing and improvement, and further improve the user experience.

[0031] In a possible implementation, the preset edge mis-touch area includes a second preset area. According to the preset edge mis-touch area, the touch position, touch distance and touch duration of the touch event to be detected, determine whether the touch event to be detected is one of multiple preset types of edge mis-touch events, including:

[0032] 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, determine that the touch event to be detected is an edge sliding mis-touch event.

[0033] Optionally, the second preset area can be the same as the first preset area.

[0034] Optionally, the second preset distance can be 700 pixel.

[0035] Optionally, the preset sliding duration can be equal to the preset long-press duration, which is 1500 ms.

[0036] In this implementation manner, it is determined whether the touch event to be detected is an edge sliding accidental touch event by determining whether the touch position, touch distance, and touch duration of the touch event to be detected match the parameter conditions of the edge sliding accidental touch event. The second preset area, the second preset distance, and the preset sliding duration can quantitatively reflect the characteristics of the edge sliding accidental touch event. Therefore, in this 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 duration of the touch event to be detected is greater than or equal to the preset sliding duration, the edge sliding accidental touch event can be accurately detected, and the accuracy of detecting the edge sliding accidental touch fault can be improved.

[0037] In a possible implementation manner, the method further includes:

[0038] If the touch event to be detected is an edge sliding accidental touch event, then: obtain the first quantity of edge accidental touch events within the first time period; the first time period refers to the time period between the occurrence moment of the press event and the occurrence moment of the lift event in the touch event to be detected; obtain the second quantity of touch events within the first time period; if the second quantity is greater than the first quantity, determine that the touch event to be detected is an edge sliding accidental touch event perceptible to the user.

[0039] In this implementation manner, in the case of determining that the touch event to be detected is an edge sliding accidental touch event, it is determined whether the touch event is an edge sliding accidental touch event perceptible to the user, which further matches the edge accidental touch fault that occurs in the actual use of the user, truly reflects the user experience, and thus facilitates subsequent targeted analysis, processing, and improvement, and further improves the user experience.

[0040] In a possible implementation manner, the preset edge accidental touch area includes a third preset area. According to the preset edge accidental touch area and the touch position, touch distance, and touch duration of the touch event to be detected, it is determined whether the touch event to be detected is one of multiple preset types of edge accidental touch events, including:

[0041] 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 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, determine that the touch event to be detected is a corner quick click accidental touch event.

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

[0043] Optionally, the third preset distance may be 0 pixel.

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

[0045] In this implementation manner, by determining whether the touch position, touch distance, and touch duration of the touch event to be detected match the parameter conditions of the corner quick click mis-touch event, it is determined whether the touch event to be detected is a corner quick click mis-touch event. The third preset area, the third preset distance, and the preset quick click duration can quantitatively reflect the characteristics of the corner quick click mis-touch event. Therefore, in this implementation manner, 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 quick click duration, the corner quick click mis-touch event can be accurately detected, and the accuracy of detecting the corner quick click mis-touch fault can be improved.

[0046] In a possible implementation manner, 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; determining whether the touch event to be detected is one of the multiple preset types of edge mis-touch events according to the preset edge mis-touch area and the touch position and touch distance of the touch event to be detected includes:

[0047] If the touch position of the touch event to be detected belongs to the fourth preset area and the touch distance of the touch event to be detected is less than or equal to the second preset distance, then, obtain the data of m touch events that are temporally continuous with the touch event to be detected after the touch event to be detected; m is a positive integer;

[0048] Determine the touch positions and touch distances of the m touch events respectively according to the data of the m touch events;

[0049] If the touch positions of m touch events all belong to the fourth preset area, the touch distances of the m touch events are all less than or equal to the second preset distance, and the continuous event duration is greater than or equal to the preset continuous click duration, then it is determined that the touch event to be detected and the m touch events are edge continuous click mis-touch events; where the continuous event duration refers to the time difference between the occurrence time of the lift event in the last touch event among the m touch events and the occurrence time of the press event in the touch event to be detected.

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

[0051] Optionally, the second preset distance may be 700 pixel.

[0052] Optionally, m may be 3.

[0053] Optionally, the preset continuous click duration may be 3000 ms.

[0054] In this implementation manner, based on the data of the touch event to be detected and the data of m touch events that are temporally continuous with the touch event to be detected after the touch event to be detected, it is determined whether the touch event to be detected and the m touch events are edge continuous click mis-touch events. The fourth preset area, the second preset distance, and the preset continuous click duration can quantitatively reflect the characteristics of the edge continuous click mis-touch events. Therefore, in this implementation manner, 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 all less than or equal to the second preset distance, and the continuous event duration is greater than or equal to the preset continuous click duration, the edge continuous click mis-touch events can be accurately detected, improving the accuracy of detecting edge continuous click mis-touch faults.

[0055] In a possible implementation manner, the method further includes:

[0056] If the touch event to be detected and the m touch events are edge continuous click mis-touch events, then: obtain the third quantity of edge mis-touch events within the second time period; the second time period refers to the time period between the occurrence time of the press event in the touch event to be detected and the occurrence time of the lift event in the last touch event among the m touch events; obtain the second quantity of touch events within the second time period; if the second quantity is greater than the third quantity, then determine that the touch event to be detected and the m touch events are edge continuous click mis-touch events that can be perceived by the user.

[0057] Optionally, the third quantity may be determined by obtaining the quantity of event identifiers of edge mis-touch events within the second time period.

[0058] In this implementation manner, when it is determined that the touch event to be detected and the m touch events are edge continuous click mis-touch events, it is determined whether the edge continuous click mis-touch event is a user-perceivable edge continuous click mis-touch event, and further matched with the edge mis-touch fault type that occurs during the actual use of the user, so as to truly reflect the user experience, thereby facilitating subsequent targeted analysis, processing, and improvement, and further improving the user experience.

[0059] In a possible implementation manner, the first data includes the reported point coordinates of the press event, and the second data includes the reported point coordinates of the lift event; determining the touch position and 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:

[0060] Determining the touch position of the touch event to be detected according to the reported point coordinates of the press event and the reported point coordinates of the lift event in the touch event to be detected; determining the absolute value of the difference between the reported point coordinates of the lift event and the reported point coordinates of the press event in the touch event to be detected in a preset direction, to obtain the touch distance of the touch event to be detected.

[0061] In this implementation manner, through the reported point coordinates of the press event and the reported point coordinates of the lift event, the touch position and touch distance of the touch event to be detected can be simply and accurately determined, improving the operation efficiency of the algorithm.

[0062] In a second aspect, the present application provides a device for detecting edge mis-touch. The device has the functions in the above first aspect and the possible implementation manners of the first aspect. The functions can 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 functions. For example, an acquisition module or unit, a detection module or unit, etc.

[0063] In a third aspect, the present application provides an electronic device. The electronic device includes: a processor, a memory, and an interface; the processor, the memory, and the interface cooperate with each other to enable the electronic device to execute any one of the methods in the technical solution of the first aspect.

[0064] In a fourth aspect, the present application provides a chip, including a processor. The processor is used to read and execute a computer program stored in the memory to execute the methods in the first aspect and any possible implementation manners thereof.

[0065] Optionally, the chip further includes a memory, and the memory is connected to the processor through a circuit or a wire.

[0066] Further optionally, the chip further includes a communication interface.

[0067] Fifth aspect, the present application provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the processor is caused to execute any one of the methods in the technical solution of the first aspect.

[0068] Sixth aspect, the present application provides a computer program product, which includes: computer program code. When the computer program code runs on an electronic device, the electronic device is caused to execute any one of the methods in the technical solution of the first aspect.

[0069] It can be understood that for the beneficial effects of the above-mentioned second aspect, third aspect, fourth aspect, fifth aspect and sixth aspect, reference can be made to the relevant descriptions in the first aspect above, and details will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0070] Figure 1 It is a schematic diagram of a scenario of an edge accidental touch failure provided by an embodiment of the present application;

[0071] Figure 2 It is a software structure block diagram of an electronic device provided by an embodiment of the present application;

[0072] Figure 3 It is a schematic diagram of a touch control process of an electronic device provided by an embodiment of the present application;

[0073] Figure 4 It is a schematic diagram of a detection process of edge accidental touch provided by an embodiment of the present application;

[0074] Figure 5 It is a schematic diagram of a process of a detection method for edge accidental touch provided by an embodiment of the present application;

[0075] Figure 6 It is a schematic diagram of a first data provided by an embodiment of the present application;

[0076] Figure 7 It is a schematic diagram of a second data provided by an embodiment of the present application;

[0077] Figure 8 It is a schematic diagram of a screen coordinate system of a mobile phone and a preset edge accidental touch area provided by an embodiment of the present application;

[0078] Figure 9 It is a schematic diagram of a process of a detection method for edge accidental touch provided by an embodiment of the present application;

[0079] Figure 10 It is a schematic diagram of a screen coordinate system of a mobile phone and a first preset area provided by an embodiment of the present application;

[0080] Figure 11It is a schematic diagram of another scenario of edge accidental touch failure provided by an embodiment of the present application;

[0081] Figure 12 It is a schematic diagram of the reported points of a touch event corresponding to a scenario of edge long-press accidental touch that can be perceived by a user provided by an embodiment of the present application;

[0082] Figure 13 It is a schematic flowchart of a method for detecting edge accidental touch provided by an embodiment of the present application;

[0083] Figure 14 It is a schematic diagram of the reported points of a touch event corresponding to a scenario of edge sliding accidental touch that can be perceived by a user provided by an embodiment of the present application;

[0084] Figure 15 It is a schematic flowchart of a method for detecting edge accidental touch provided by an embodiment of the present application;

[0085] Figure 16 It is a schematic diagram of the screen coordinate system and the third preset area of a mobile phone provided by an embodiment of the present application;

[0086] Figure 17 It is a schematic flowchart of a method for detecting edge accidental touch provided by an embodiment of the present application;

[0087] Figure 18 It is a schematic diagram of the reported points of a touch event corresponding to a scenario of edge continuous click accidental touch that can be perceived by a user provided by an embodiment of the present application;

[0088] Figure 19 It is a schematic structural diagram of a device for detecting edge accidental touch provided by an embodiment of the present application;

[0089] Figure 20 It is a schematic structural diagram of an electronic device provided by an embodiment of the present application. Detailed implementation manners

[0090] Next, the technical solutions in the embodiments of the present application will be described with reference to the accompanying drawings in the embodiments of the present application. Among them, in the description of the embodiments of the present application, unless otherwise specified, " / " means "or". For example, A / B may mean A or B; herein, "and / or" is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B 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 of" means two or more than two.

[0091] Hereinafter, the terms "first", "second", and "third" are only used for descriptive purposes and should not be construed as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, features defined with "first", "second", and "third" may explicitly or implicitly include one or more of such features.

[0092] A touch panel (TP), also known as a touch screen panel, etc., refers to a panel that can achieve touch input. The touch panel can be used alone to achieve touch functions. For example, it can be applied to electronic devices such as laptops. The touch panel can also be used in conjunction with a display panel to form a touch display screen (also known as a touch screen or a touch panel), which can not only achieve display functions but also touch functions. For example, it can be applied to electronic devices such as mobile phones, tablet computers, wearable devices, and teaching all-in-one machines.

[0093] Regardless of the type of electronic device it is applied to, edge mis-touch faults may occur during the use of the touch panel. Taking the application of the touch panel to a mobile phone as an example for illustration:

[0094] Exemplarily, Figure 1 This is a schematic diagram of the scenario of edge mis-touch fault provided by an embodiment of the present application. As Figure 1 shown, when a user holds a mobile phone, it is possible that a finger touches the edge of the touch screen, and the touch panel of the touch screen recognizes the touch operation and executes the corresponding operation. This will cause the touch panel to fail to recognize the input of a normal touch operation when the user's other hand is performing a normal touch operation, resulting in the user being unable to achieve the expected operation.

[0095] For edge mis-touch faults, edge anti-mis-touch algorithms are generally used for processing to avoid the impact of edge mis-touch on the normal operations of users. However, whether it is the design stage, test stage, application stage, or improvement stage of the edge anti-mis-touch algorithm, it is necessary to identify and detect edge mis-touch events. The embodiments of the present application aim to provide a method for detecting edge mis-touch for identifying and detecting edge mis-touch events.

[0096] For ease of understanding, before describing the method for detecting edge mis-touch provided by the embodiments of the present application, the software structure of an electronic device with touch functions and the process of the electronic device achieving touch functions will be described first.

[0097] The software system of an electronic device can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservices architecture, or a cloud architecture. The embodiments of the present application take the Android system with a layered architecture as an example to exemplarily illustrate the software structure of the electronic device.

[0098] Exemplarily, Figure 2The software architecture block diagram of an electronic device provided by an embodiment of this application. The layered architecture divides the software into several layers, and each layer has a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom, namely the application layer, the application framework layer, the Android runtime and the system libraries, and the kernel layer. The application layer may include a series of application packages.

[0099] As Figure 2 shown, the application packages may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message, etc.

[0100] The application framework layer provides application programming interfaces (APIs) and programming frameworks for the applications in the application layer. The application framework layer includes some predefined functions.

[0101] As Figure 2 shown, the application framework layer may include a window manager, a content provider, a view system, a telephone manager, a resource manager, a notification manager, etc.

[0102] The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc.

[0103] The content provider is used to store and obtain data, and make this data accessible to applications. The data may include video, image, audio, dialed and answered calls, browsing history and bookmarks, phone book, etc.

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

[0105] The telephone manager is used to provide the communication function of the electronic device. For example, the management of call status (including connection, disconnection, etc.).

[0106] The resource manager provides various resources for applications, such as localized strings, icons, pictures, layout files, video files, etc.

[0107] The notification manager enables an application to display notification information in the status bar. It can be used to convey messages of the notification type, and can disappear automatically after a short stay without user interaction. For example, the notification manager is used to inform that a download is completed, a message reminder, etc. The notification manager can also be a notification that appears in the system top status bar in the form of a chart or a scrolling text, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialogue window. For example, it prompts text information in the status bar, emits a prompt tone, the electronic device vibrates, the indicator light flashes, etc.

[0108] In addition, the application framework layer also includes relevant modules for event reporting and management. For example, the event listening (EventHub) module, the input reading (input reader) module, the input dispatching (input dispatcher) module, etc.

[0109] Android runtime includes the core libraries and the virtual machine. Android runtime is responsible for the scheduling and management of the Android system.

[0110] The core libraries include two parts: one part is the functional functions that the Java language needs to call, and the other part is the core libraries of Android.

[0111] The application layer and the application framework layer run in the virtual machine. The virtual machine executes the Java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as the management of object life cycles, stack management, thread management, security and exception management, and garbage collection.

[0112] The system libraries can include multiple functional modules. For example: the surface manager, the media libraries, the 3D graphics processing library (for example: OpenGL ES), the 2D graphics engine (for example: SGL), etc.

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

[0114] The media libraries support the playback and recording of multiple common audio and video formats, as well as static image files, etc. The media libraries can support multiple audio and video coding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0115] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, synthesis, and layer processing, etc.

[0116] The 2D graphics engine is the drawing engine for 2D drawing.

[0117] The kernel layer is the layer between the hardware and the software. The kernel layer includes at least a display driver, a camera driver, an audio driver, and a sensor driver. Additionally, the kernel layer may further include a touch signal processing module, a touch data generation module, a log generation module, and a communication module, etc. Among them, the communication module can be a wired communication module or a wireless communication module.

[0118] Meanwhile, the electronic device further includes a hardware layer. The hardware layer may include a main board, a touch panel, a touch chip, and accessories, etc. The hardware layer cooperates with each layer of the software system to implement the touch function.

[0119] Exemplarily, Figure 3 is a schematic diagram of the touch process of the electronic device provided by an embodiment of the present application. As Figure 3 shown, the structures and modules for the electronic device to implement the touch function include: the touch panel 201 in the hardware layer, the touch signal processing module 202, the touch data generation module 203, and the log generation module 207 in the kernel layer, and the event listening module 204, the input reading module 205, and the input distribution module 206 in the application framework layer, etc.

[0120] The user performs a touch operation through the touch panel 201. The touch operation includes but is not limited to touch operations, click operations, swipe operations, and long press operations (also known as long - hold operations), etc. The touch panel 201 receives the user's touch operation, generates a touch signal, and reports the generated touch signal to the touch signal processing module 202 in 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 in the kernel layer. Optionally, the touch signal processing module 202 may report the encapsulated touch signal to the touch data generation module 203 through an I2C interface, a MIPI interface, or an SPI interface, etc. The touch data generation module 203 performs normalization processing, data calibration, etc. on the touch signal, and then generates the data (input.c) of the touch event. It can be understood that when the user performs a touch operation, one or more touch events are generated. One touch event corresponds to the operation of one touch contact object (such as a finger or a stylus, etc.), and one touch event corresponds to a set of data. For example, when the user performs an upward swipe operation on the screen, it may be a single - finger upward swipe or a multi - finger upward swipe. The operation of each finger on the screen generates a touch event, corresponding to a set of data.

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

[0122] It can be understood that after the touch data generation module 203 generates the data of the touch event, it can further send the data of the touch event to the log generation module 207. The log generation module 207 generates a log file according to the data of the touch event. Optionally, the touch data generation module 203 can send the data of the touch event to the log generation module 207 in real time, so that the log generation module 207 generates a log file; that is to say, every time the touch data generation module 203 generates the data of a touch event, it 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 the log file. The log file can be stored in the memory of the electronic device or sent to other electronic devices, for example, sent to the server.

[0123] The edge false touch detection method provided by the embodiment of the present application is used to process the data of the touch event generated by an electronic device with a structure as Figure 2 and Figure 3 shown to detect the edge false touch fault. Specifically, the method provided by the embodiment of the present application is used to process the data (input.c) of the touch event generated by the touch data generation module 203 shown in the Figure 3 embodiment.

[0124] It should be noted that the edge accidental touch detection method provided in the embodiments of the present application can be applied to an electronic device. The electronic device can be the above-mentioned electronic device with a touch function, that is, an electronic device capable of generating touch event data, such as a terminal device; it can also be other electronic devices communicatively connected to the electronic device that generates touch event data, such as a server. Among them, the terminal device can be a mobile phone, a tablet computer, a wearable device, a vehicle-mounted device, an augmented reality (AR) / virtual reality (VR) device, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), or other devices with a touch function. When the method provided in the embodiments of the present application is applied to a terminal device, optionally, the terminal device can obtain touch event data from the kernel layer in real time, process the touch event data to detect edge accidental touch events. Optionally, the generated touch event data can also be stored in a memory in the form of a running log or the like, and the terminal device can obtain the touch event data from the memory and process the touch event data.

[0125] When the method provided in the embodiments of the present application is applied to a server, the server can be a cloud server or a physical server. Optionally, the electronic device that generates touch event data can upload the generated touch event data to the server in the form of a running log or the like, and the server processes the touch event data to detect edge accidental touch events.

[0126] For the sake of convenience of description, in the following embodiments, the edge accidental touch detection method is applied to a server as an example, and the electronic device that generates touch event data is a terminal device, specifically a mobile phone as an example for description.

[0127] First, in combination with Figure 2 and Figure 3 , the entire process of the edge accidental touch detection method (including the process of the mobile phone generating touch event data and uploading the touch event to the server) will be described. It can be understood that in this embodiment, each module represents a module that implements a certain function, which can be implemented by hardware, software, or a combination of software and hardware. The present application does not make any limitation in this regard. Please refer to Figure 4 , the edge accidental touch detection process includes:

[0128] S401. The user performs a touch operation through the touch panel.

[0129] S402. The touch panel receives the user's touch operation and generates a touch signal.

[0130] S403. The touch panel reports the generated touch signal to the touch signal processing module.

[0131] S404. The touch signal processing module receives the touch signal and performs encapsulation processing on the touch signal.

[0132] S405. The touch signal processing module sends the encapsulated touch signal to the touch data generation module.

[0133] S406. The touch data generation module performs normalization processing, data calibration, etc. on the encapsulated touch signal to generate touch event data.

[0134] S407. The touch data generation module sends the generated touch event data to the log generation module.

[0135] S408. The log generation module generates a log file based on the touch event data.

[0136] That is, the log generation module writes some or all of the data of each touch event into the log file.

[0137] S409. The log generation module sends the log file to the communication module.

[0138] S4010. The communication module sends the log file to the server.

[0139] Optionally, the log generation module can 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 generation module can also, according to the size of the data in the log file, when the data volume in the log file reaches a preset value, package and send the log file to the server.

[0140] S4011. The server receives the log file sent by the communication module and detects edge false touch faults based on the touch event data in the log file.

[0141] The following embodiments will be based on Figures 2 to 4 the shown structure and process, combined with the accompanying drawings and application scenarios, to elaborate on the specific process of the server detecting edge false touch faults based on the touch event data in the log file.

[0142] Figure 5 is a schematic flowchart of a method for detecting edge false touch provided by an embodiment of the present application. As Figure 5 shown, the method includes:

[0143] S501. 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.

[0144] The server may store data of multiple touch events. The server can process the data of multiple touch events one by one to detect whether each touch event is an edge mis-touch event, that is, execute each step in the embodiments of the present application on the data of multiple touch events one by one. Among them, the touch event currently being processed is called the touch event to be detected.

[0145] Optionally, in the embodiments of the present application, each touch event includes a press (DOWN) event and a lift (UP) event. Among them, the press event corresponds to the pressing operation of the user's finger or stylus, etc., that is, the user's finger or stylus contacts the screen. The lift event corresponds to the lifting operation of the user's finger or stylus, etc., that is, the user's finger or stylus leaves the screen.

[0146] Correspondingly, the data of each touch event may include the data of the press event (hereinafter referred to as the first data) and the data of the lift event (hereinafter referred to as the second data). The first data may include the reported point coordinates of the press event (including the abscissa and ordinate, that is, the X coordinate and the Y coordinate), the reported point time of the press event, and the event identifier, etc. Among them, the event identifier may also be referred to as the event number, Tracking ID, etc., and is used to represent the unique identity of the touch event. One touch event corresponds to one event identifier, and the press event and the lift 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 a press event and a lift event with the same event identifier are a pair of press / lift events.

[0147] The second data may include the reported point coordinates of the lift event (including the abscissa and ordinate, that is, the X coordinate and the Y coordinate), the reported point time of the lift event, and the event identifier, etc.

[0148] It can be understood that one touch event corresponds to one event identifier, that is, the event identifier in the first data of the same touch event is the same as the event identifier in the second data. In addition, as described above, one touch event includes a press event and a lift event, that is, one touch event includes a pair of press / lift events. A press event and a lift event with the same event identifier are a pair of press / lift events.

[0149] Optionally, the first data and the second data may also respectively include other data such as the reporting rate, and the embodiments of the present application do not make any limitations on this.

[0150] Exemplarily, Figure 6A schematic diagram of an example of the first data (i.e., the data of the press event) provided by an embodiment of the present application. As Figure 6 shown, "BTN_TOUCH DOWN" shown at 604 indicates that this set of data is the first data. The first data includes the reported point coordinates of the press event: X coordinate 601 and Y coordinate 602. The first data also includes an event identifier 603, the reported point time 605 of the press event, and a reporting rate 606, etc.

[0151] Exemplarily, Figure 7 A schematic diagram of an example of the second data (i.e., the data of the lift event) provided by an embodiment of the present application. As Figure 7 shown, "BTN_TOUCH UP" shown at 704 indicates that this set of data is the second data. The second data includes the reported point coordinates of the lift event: X coordinate 701 and Y coordinate 702. The second data also includes an event identifier 703, the reported point time 705 of the lift event, and a reporting rate 706, etc.

[0152] S502. Determine whether the touch event to be detected is one of multiple preset types of edge false touch events according to the preset edge false touch area of the terminal device and the first data and the second data of the touch event to be detected.

[0153] The preset edge false touch area of the terminal device is used to screen edge false touch events from the touch position. The touch position refers to the occurrence position of the touch event, that is, the position where the user touches the screen of the terminal device. That is to say, if the touch position of the touch event is within the preset edge false touch area, then the touch event may be an edge false touch event. If the touch position of the touch event is outside the preset edge touch area, then the touch event does not belong to the edge false touch event.

[0154] The preset edge false touch area can be set according to actual needs. Exemplarily, taking a mobile phone as an example, Figure 8 A schematic diagram of the screen coordinate system and the preset edge false touch area of a mobile phone provided by an embodiment of the present application. As Figure 8As shown in the figure, assume that the width direction of the mobile phone is the X coordinate direction, the length direction of the mobile phone is the Y coordinate direction, and the upper left corner of the screen is the coordinate 0 point when the mobile phone is held upright. Optionally, the X coordinate, the Y coordinate, and the preset edge accidental touch area can be measured in pixels. Assume that the pixel width of the mobile phone display screen is width, and the pixel length is length. Then the range of the X coordinate is from 0 pixel to width - 1 pixel, and the range of the Y coordinate is from 0 pixel to length - 1 pixel. For example, if the mobile phone resolution 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 direction. Then, the pixel width width of this mobile phone is 1080 pixels, and the pixel length length of this mobile phone is 2400 pixels. The range of the X coordinate is from 0 pixel to 1079 pixels, and the range of the Y coordinate is from 0 pixel to 2399 pixels.

[0155] The preset edge accidental touch area can be, for example, an area where the X coordinate is from 0 to x and the Y coordinate is from y to length - y - 1, such as Figure 8 the area 801 in. Or, the preset edge accidental touch area can also be an area where the X coordinate is from width - x - 1 to width - 1 and the Y coordinate is from y to length - y - 1, such as Figure 8 the area 802 in. Of course, the preset edge accidental touch area can also include both the area 801 and the area 802.

[0156] According to different actual operations of the user, there may be multiple types of edge accidental touches. In this embodiment, multiple types of edge accidental touch events can be predefined, and the judgment conditions for each type of edge accidental touch event can be defined. Based on the judgment conditions for each type of edge accidental touch event, the server determines whether the touch event to be detected belongs to one of the multiple preset types of edge accidental touch events according to the first data, the second data of the touch event to be detected, and the preset edge accidental touch area of the terminal device.

[0157] If the touch event to be detected belongs to a marginal false touch event of a certain preset type, the server can prompt a marginal false touch fault and extract and save the data of the touch event to be detected and the marginal false touch type to which it belongs for subsequent analysis or processing. For example, it can be used by R & D personnel to analyze the reasons for marginal false touches on the terminal device, analyze the product stability of the terminal device, or improve the anti-false touch algorithm of the terminal device. Optionally, after determining that the touch event to be detected belongs to a marginal false touch event of a certain preset type, the server can further obtain other data related to the touch event to be detected, such as Transparent Huge Pages (THP) data, etc., for subsequent analysis or processing. The specific data obtained by the server can be determined according to the use of the detection result of the marginal false touch.

[0158] If the touch event to be detected does not belong to any of the multiple preset types of marginal false touch events, it is determined that the touch event to be detected does not belong to a marginal false touch event, and the data of the touch event to be detected in the server can be deleted and released.

[0159] In this embodiment, by obtaining the first data and the second data of the touch event to be detected, it is determined whether the touch event to be detected is one of the multiple preset types of marginal false touch events according to the preset marginal false touch area of the terminal device and the first data and the second data of the touch event to be detected. The method provided in this embodiment can determine whether the touch event to be detected is a marginal false touch event, which is convenient for subsequent analysis or processing. At the same time, the method provided in this embodiment can determine the type of the marginal false touch, making the detection result of the marginal false touch event more accurate, so that the subsequent analysis or processing is more accurate, and the effectiveness of solving the marginal false touch problem is improved.

[0160] In one embodiment, the multiple preset types of marginal false touch events may include marginal long-press false touch events, marginal swipe false touch events, corner quick click false touch events, and marginal continuous click false touch events. Among them, the marginal long-press false touch event, also known as the marginal long-press false touch event, refers to the user pressing the screen in the preset marginal false touch area of the screen for more than the preset duration. The marginal swipe false touch event refers to the user swiping or reciprocally swiping in a certain direction in the preset marginal false touch area of the screen. The corner quick click false touch event refers to the user quickly clicking (i.e., pressing and then quickly lifting) at the corner position of the screen. For example, when the user holds the mobile phone with the left hand facing forward, the left little finger clicks the screen at the lower right corner of the screen, or the left thumb clicks the screen at the lower left corner of the screen. The marginal continuous click false touch event, also known as the marginal adjacent position continuously lifting and pressing false touch event, refers to the user performing multiple click operations near a certain position in the preset marginal false touch area of the screen.

[0161] It can be understood that after the server obtains the first data and the second data of the touch event to be detected, it first determines the parameters required to judge the type of edge mis-touch event according to the first data and the second data respectively; then, it matches the determined parameters with the parameter conditions of each type of edge mis-touch event respectively. If the determined parameters match the parameter conditions of a certain type of edge mis-touch event, it is determined that the touch event to be detected belongs to this type of edge mis-touch event, otherwise it does not belong to this type of edge mis-touch event. If the touch event to be detected does not belong to any of the preset types of edge mis-touch events, it is determined that the touch event to be detected does not belong to the edge mis-touch event.

[0162] Optionally, the parameters required to judge different types of edge mis-touch events may be different. As a possible implementation, the parameters required to judge whether the touch event to be detected is an edge long-press mis-touch event, an edge swipe mis-touch event, and a corner quick click mis-touch event may include: touch position, touch distance, and touch duration.

[0163] Among them, the touch position may include the position of the press event and the position of the lift event. The position of the press event can be characterized by the reported point coordinates of the press event, and the position of the lift event can be characterized by the reported point coordinates of the lift event.

[0164] The touch distance is used to characterize the distance between the position of the press event and the position of the lift event in the touch event in a preset direction. In some embodiments, the preset direction may be, for example, the vertical coordinate direction of the terminal device, and the touch distance may be the absolute value of the difference between the vertical coordinate of the lift event and the vertical coordinate of the press event, that is: touch distance = |y up -y down |. In some other embodiments, when the screen of the terminal device (such as a smart watch) is circular, the preset direction may be, for example, a preset arc, and the touch distance may be the distance between the lift event and the press event along the preset arc.

[0165] The touch duration is used to characterize the time difference between the occurrence time of the lift event and the occurrence time of the press event in the touch event. Specifically, the touch duration can be obtained by calculating the difference between the reported point time of the lift event and the reported point time of the press event in the touch event, that is: touch duration = t up -t down .

[0166] Next, in conjunction with the accompanying drawings, the judgment processes of the edge long-press mis-touch event, the edge swipe mis-touch event, and the corner quick click mis-touch event will be described respectively.

[0167] Exemplarily, Figure 9 is a schematic flowchart of a method for detecting edge mis-touch provided by an embodiment of the present application. As Figure 9As shown, the method for determining whether a touch event to be detected belongs to an edge long - press mis - touch event includes:

[0168] S901. Determine whether the touch position of the touch event to be detected belongs to a first preset area.

[0169] Optionally, the server can determine whether both the lift event and the press event in the touch event to be detected belong to the first preset area. Specifically, the server can determine whether the reported point coordinates of the lift event and the reported point coordinates of the press event in the touch event to be detected both belong to the first preset area; if so, determine that the touch position of the touch event to be detected belongs to the first preset area, and execute step S902; if not, determine that the touch position of the touch event to be detected does not belong to the first preset area, and execute step S905.

[0170] Exemplarily, Figure 10 is a schematic diagram of the screen coordinate system and the first preset area of a mobile phone provided in an embodiment of the present application. As Figure 10 shown, optionally, the first preset area can be, for example, an area with an X - coordinate from 0 pixel to 5 pixels, as shown by area 1001 in Figure 10 , and an area with an X - coordinate from width - 6 pixels to width - 1 pixel, as shown by area 1002 in Figure 10 . That is: The server determines whether the X - coordinates of the reported point coordinates of the lift event and the reported point coordinates of the lift event in the touch event to be detected both belong to the data set [0, 1, 2, 3, 4, 5] or the data set [width - 6, width - 5, width - 4, width - 3, width - 2, width - 1], with the unit of pixel.

[0171] S902. Determine whether the touch distance of the touch event to be detected is less than or equal to a first preset distance.

[0172] Optionally, the first preset distance can be, for example, 30 pixels. Specifically, the server determines whether the touch distance of the touch event to be detected satisfies 0 pixel ≤ |y up - y down | ≤ 30 pixels; if so, execute step S903; if not, execute step S905.

[0173] S903. Determine whether the touch duration of the touch event to be detected is greater than or equal to a preset long - press duration.

[0174] The preset long - press duration can be set according to actual needs. Optionally, the preset long - press duration can be, for example, 1500 ms. Specifically, the server determines whether the touch duration of the touch event to be detected satisfies t up - t down≥1500 ms; if so, execute step S904; if not, execute step S905.

[0175] S904. Determine that the touch event to be detected is an edge long - press mis - touch event.

[0176] If it is determined that the touch event to be detected is an edge long - press mis - touch event, the server can prompt an edge mis - touch fault, extract and save the data of the touch event to be detected and the corresponding edge mis - touch type, and use the next touch event as the touch event to be detected, then return to execute step S501 to determine whether the next touch event is one of the edge mis - touch events of multiple preset types.

[0177] S905. Determine that the touch event to be detected is not an edge long - press mis - touch event.

[0178] If it is determined that the touch event to be detected is not an edge long - press mis - touch event, the server further determines whether the touch event to be detected is an edge mis - touch event of the next type. For example, it determines whether the touch event to be detected is an edge slide mis - touch event.

[0179] In this embodiment, by determining whether the touch position, touch distance, and touch duration of the touch event to be detected match the parameter conditions of the edge long - press mis - touch event, it is determined whether the touch event to be detected is an edge long - press mis - touch event. The edge long - press mis - touch event is a type of edge mis - touch that users may encounter during actual use. In this embodiment, fully considering the real experience of users during the use of the terminal, it can intelligently detect the edge long - press mis - touch event in the touch event, which matches the type of edge mis - touch fault that occurs in actual user use, facilitating subsequent analysis, processing, and improvement of the data of the edge long - press mis - touch event, and improving the user experience. In addition, the first preset area, the first preset distance, and the preset long - press duration can quantitatively reflect the characteristics of the edge long - press mis - touch event. Therefore, in this embodiment, 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 less than or equal to the first preset distance, and the touch duration of the touch event to be detected is greater than or equal to the preset long - press duration, the edge long - press mis - touch event can be accurately detected, improving the accuracy of detecting the edge long - press mis - touch fault.

[0180] In one embodiment, after determining that the touch event to be detected is an edge long - press mis - touch event, it can further be determined whether the touch event to be detected is a user - perceivable edge long - press mis - touch event. A user - perceivable edge long - press mis - touch event refers to a situation where while an edge long - press mis - touch occurs, the user performs other normal operations, and the edge long - press mis - touch event and other edge mis - touch events affect the user's normal operations, resulting in the user being able to perceive that an edge mis - touch event has occurred.

[0181] For example, referring to Figure 11 , the user holds the mobile phone with the left hand, and the middle finger and ring finger of the left hand long-press the right edge of the mobile phone. The two touch events corresponding to the long-press operation of the middle finger and ring finger of the left hand are both edge long-press mis-touch events. During this process, the user clicks the application "Recorder" with the index finger of the right hand. Exemplarily, Figure 12 shows Figure 11 a schematic diagram of the reported points of touch events on the display screen corresponding to the application scenario shown. Figure 12 In it, 1201 represents the reported point of the touch event corresponding to the middle finger of the user's left hand, 1202 represents the reported point of the touch event corresponding to the ring finger of the user's left hand, and 1203 represents the reported point of the touch event corresponding to the index finger of the user's right hand.

[0182] Due to the edge long-press mis-touch failure caused by the operation of the middle finger and ring finger of the left hand, the user's click on the application is unresponsive, and then it is perceived that an edge mis-touch event has occurred. In this scenario, the edge long-press mis-touch events corresponding to the long-press operations of the middle finger and ring finger of the left hand are edge long-press mis-touch events that can be perceived by the user.

[0183] In one embodiment, the following method can be used to determine whether an edge long-press mis-touch event is an edge long-press mis-touch event that can be perceived by the user:

[0184] If it is determined that the touch event to be detected is an edge long-press mis-touch event, then: obtain the number of edge mis-touch events within the first time period to obtain the first quantity; where the first time period refers to the time period between the occurrence time of the press event and the occurrence time of the lift event in the touch event to be detected; obtain the number of touch events within the first time period to obtain the second quantity; if the second quantity is greater than the first quantity, then determine that the touch event to be detected is an edge long-press mis-touch event that can be perceived by the user.

[0185] That is to say, the server determines whether the total number of touch events within the time period when the touch event to be detected occurs is greater than the number of edge mis-touch events (including edge long-press mis-touch events and other types of edge mis-touch events). If so, then determine that this edge long-press mis-touch event is an edge long-press mis-touch event that can be perceived by the user.

[0186] Optionally, the first quantity can be determined by obtaining the number of event identifiers of edge mis-touch events within the first time period, or the first quantity can be determined by obtaining the number of pairs of press / lift events with edge mis-touch within the first time period. Similarly, the second quantity can be determined by obtaining the total number of event identifiers within the first time period, or the second quantity can be determined by obtaining the total number of pairs of press / lift events within the first time period.

[0187] In this embodiment, when it is determined that the edge long-press event is an edge long-press mis-touch event, it is determined whether the touch event is a user-perceivable edge long-press mis-touch event, and further matched with the edge mis-touch fault that occurs during the actual use of the user, so as to truly reflect the user experience, which is convenient for subsequent targeted analysis, processing and improvement, and further improves the user experience.

[0188] Exemplarily, Figure 13 is a schematic flowchart of a method for detecting edge mis-touch provided by an embodiment of the present application. As Figure 13 shown, the method for determining whether a touch event to be detected belongs to an edge sliding mis-touch event includes:

[0189] S1301. Determine whether the touch position of the touch event to be detected belongs to a second preset area;

[0190] If so, execute step S1302;

[0191] If not, execute step S1305.

[0192] The specific process of step S1301 is similar to the Figure 9 process of S901, and will not be elaborated here.

[0193] Optionally, the second preset area may be the same as or different from the first preset area. It can be understood that when the second preset area is the same as the first preset area, the server has executed step S901, and step S1301 may not be executed repeatedly.

[0194] S1302. Determine 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.

[0195] Optionally, the second preset distance may be 700 pixel, for example. Specifically, the server determines whether the touch distance of the touch event to be detected satisfies 30 pixel < |y up -y down | ≤ 700 pixel; if so, execute step S1303; if not, execute step S1305.

[0196] S1303. Determine whether the touch duration of the touch event to be detected is greater than or equal to a preset sliding duration.

[0197] The preset sliding duration can be set according to actual needs. Optionally, the preset sliding duration may be equal to the preset long-press duration, 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 ≥ 1500 ms; if so, execute step S1304; if not, execute step S1305.

[0198] S1304. Determine that the touch event to be detected is an edge sliding false touch event.

[0199] If it is determined that the touch event to be detected is an edge sliding false touch event, the server can prompt an edge false touch fault, extract and save the data of the touch event to be detected and the corresponding edge false touch type, and use the next touch event as the touch event to be detected, then return to execute step S501 to determine whether the next touch event is one of the edge false touch events of multiple preset types.

[0200] S1305. Determine that the touch event to be detected is not an edge sliding false touch event.

[0201] If it is determined that the touch event to be detected is not an edge sliding 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, it determines whether the touch event to be detected is a corner quick click false touch event.

[0202] In this embodiment, by determining whether the touch position, touch distance, and touch duration of the touch event to be detected match the parameter conditions of the edge sliding false touch event, it is determined whether the touch event to be detected is an edge sliding false touch event. The edge sliding false touch event is a type of edge false touch that users may encounter during actual use. In this embodiment, full consideration is given to the real experience of users during the use of the terminal, and the edge sliding false touch events in the touch events can be intelligently detected, which matches the types of edge false touch faults that occur in actual user use, facilitating subsequent analysis, processing, and improvement of the data of the edge sliding false touch events, and improving the user experience. In addition, the second preset area, the second preset distance, and the preset sliding duration can quantitatively reflect the characteristics of the edge sliding false touch event. 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 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 can be accurately detected, improving the accuracy of detecting the edge sliding false touch fault.

[0203] In one embodiment, after determining that the touch event to be detected is an edge sliding false touch event, it can further be determined whether the touch event to be detected is a user-perceivable edge sliding false touch event. A user-perceivable edge sliding false touch event means that while an edge sliding false touch occurs, the user performs other normal operations, and the edge sliding false touch event and other edge false touch events affect the user's normal operations, resulting in the user being able to perceive that an edge false touch event has occurred.

[0204] For example, in an application scenario, the user holds the mobile phone with the left hand, and the middle finger of the left hand slides on the right edge of the mobile phone, generating an edge sliding accidental touch event. During this process, the index finger of the user's right hand slides upward. Exemplarily, Figure 14 Fig. shows a schematic diagram of the reported points of touch events on the display screen corresponding to this application scenario. Figure 14 In, 1401 represents the reported point of the touch event corresponding to the middle finger of the user's left hand, and 1402 represents the reported point of the touch event corresponding to the index finger of the user's right hand.

[0205] Due to the edge sliding accidental touch failure caused by the sliding of the middle finger of the left hand, the upward sliding of the index finger of the user's right hand has no response, and then it is perceived that an edge accidental touch event has occurred. In this scenario, the edge sliding accidental touch event corresponding to the sliding operation of the middle finger of the left hand is an edge sliding accidental touch event that can be perceived by the user.

[0206] In one embodiment, the method for determining whether an edge sliding accidental touch event is an edge sliding accidental touch event that can be perceived by the user is similar to the process of determining an edge long-press accidental touch that can be perceived by the user, and can be implemented through the following steps:

[0207] If it is determined that the touch event to be detected is an edge sliding accidental touch event, then:

[0208] Obtain the number of edge accidental touch events within the first time period to obtain the first quantity; wherein, the first time period refers to the time period between the occurrence time of the press event and the occurrence time of the lift event in the touch event to be detected; obtain the number of touch events within the first time period to obtain the second quantity; if the second quantity is greater than the first quantity, then determine that the touch event to be detected is an edge sliding accidental touch event that can be perceived by the user.

[0209] That is to say, the server determines whether the total number of touch events within the time period when the edge sliding accidental touch event occurs is greater than the total number of edge accidental touch events (including edge sliding accidental touch events and other edge accidental touch events). If so, it is determined that the edge sliding accidental touch event is an edge sliding accidental touch event that can be perceived by the user.

[0210] In this embodiment, when it is determined that the touch event to be detected is an edge sliding accidental touch event, determining whether the touch event is an edge sliding accidental touch event that can be perceived by the user further matches the edge accidental touch failure that occurs during the actual use of the user, truly reflects the user experience, and thus facilitates subsequent targeted analysis, processing, and improvement, further improving the user experience.

[0211] Exemplarily, Figure 15 is a schematic flowchart of a method for detecting edge accidental touch provided by an embodiment of the present application. As Figure 15 shown, the method for determining whether a touch event to be detected belongs to a corner quick click event includes:

[0212] S1501. Determine whether the touch position of the touch event to be detected belongs to the third preset area;

[0213] If so, execute step S1502;

[0214] If not, execute step S1505.

[0215] The specific process of step S1501 is similar to that of Figure 9 S901 in [], and will not be elaborated here.

[0216] Exemplarily, Figure 16 FIG. is a schematic diagram of the screen coordinate system and the third preset area of a mobile phone provided by an embodiment of the present application. As Figure 16 shown, optionally, the third preset area may be, for example, an area where the X coordinate is from 0 pixel to 1 pixel and the Y coordinate is from length - 150 pixel to length - 1 pixel, as Figure 16 shown by area 1601 in []; and an area where the X coordinate is from width - 2 pixel to width - 1 pixel and the Y coordinate is from length - 150 pixel to length - 1 pixel, as Figure 16 shown by area 1602 in []. That is: the server determines whether the X coordinates of the reported point coordinates of the lift event and the reported point coordinates of the lift event in the touch event to be detected both belong to the data set [0, 1] or the data set [width - 2, width - 1] (unit: pixel), and determines whether the Y coordinate of the reported point coordinates both belongs to [length - 150, length - 1] (unit: pixel).

[0217] S1502. Determine whether the touch distance of the touch event to be detected is less than or equal to the third preset distance, where the third preset distance is less than the first preset distance.

[0218] Optionally, in one embodiment, the third preset distance may be, for example, 1 pixel. Optionally, in another embodiment, the third preset distance may also be 0. That is to say, step S1502 is essentially for the server to determine whether the touch distance of the touch event to be detected is 0, that is, to determine whether |y up - y down | is equal to 0; if so, execute step S1503; if not, execute step S1505.

[0219] S1503. Determine whether the touch duration of the touch event to be detected is less than or equal to the preset quick click duration.

[0220] The preset quick click duration can be set according to actual requirements. Optionally, the preset quick click duration can be 150 ms. Specifically, the server determines whether the touch duration of the touch event to be detected satisfies t up -t down ≤ 150 ms; if so, step S1504 is executed; if not, step S1505 is executed.

[0221] S1504. Determine that the touch event to be detected is a corner quick click false touch event.

[0222] If it is determined that the touch event to be detected is a corner quick click false touch event, the server can prompt an edge false touch fault, extract and save the data of the touch event to be detected and the type of the edge false touch to which it belongs, and use 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 the edge false touch events of multiple preset types.

[0223] S1505. Determine that the touch event to be detected is not a corner quick click false touch event.

[0224] If it is determined that the touch event to be detected is not a corner quick click 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, it determines whether the touch event to be detected is an edge continuous click false touch event.

[0225] In this embodiment, by determining whether the touch position, touch distance, and touch duration of the touch event to be detected match the parameter conditions of the corner quick click false touch event, it is determined whether the touch event to be detected is a corner quick click false touch event. The corner quick click false touch event is also a type of edge false touch that may be encountered in the actual use of users. In this embodiment, the real experience of users during the use of the terminal is fully considered, and the corner quick click false touch event in the touch event can be intelligently detected, which matches the type of edge false touch fault that occurs in the actual use of users, facilitating subsequent analysis, processing, and improvement of the data of the corner quick click false touch event, and improving the user experience. In addition, the third preset area, the third preset distance, and the preset quick click duration can quantitatively reflect the characteristics of the corner quick click false touch event. 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 quick click duration, the corner quick click false touch event can be accurately detected, improving the accuracy of detecting the corner quick click false touch fault.

[0226] Next, in conjunction with the accompanying drawings, the judgment process of the edge continuous click false touch event will be described.

[0227] Exemplarily, Figure 17 is a schematic flow chart of a method for detecting edge accidental touches provided by an embodiment of the present application. As Figure 17 shown, the method for determining whether a touch event to be detected belongs to an edge continuous click accidental touch event includes:

[0228] S1701. Determine whether the touch position of the touch event to be detected belongs to a fourth preset area;

[0229] If so, execute step S1702;

[0230] If not, execute step S1708.

[0231] The specific process of step S1701 is similar to that of Figure 9 S901 in, and will not be elaborated here.

[0232] Optionally, the fourth preset area may be the same as or different from the first preset area and the second preset area. It can be understood that when the fourth preset area is the same as the first preset area or the second preset area, the server has executed step S901 or S1301, and step S1701 may not be executed repeatedly.

[0233] S1702. Determine whether the touch distance of the touch event to be detected is less than or equal to a second preset distance.

[0234] Optionally, taking the second preset distance as 700 pixel as an example, specifically, the server determines whether the touch distance of the touch event to be detected satisfies |y up -y down | ≤ 700 pixel; if so, execute step S1703; if not, execute step S1708.

[0235] S1703. Obtain the data of m touch events that are temporally continuous with the touch event to be detected after the touch event to be detected, where m is a positive integer.

[0236] The specific value of m can be set according to actual needs. For example, m can be 3.

[0237] Optionally, according to the reporting time of the lift event in the touch event to be detected, obtain the data of m touch events adjacent after the reporting time of the lift event. Each of the m touch events includes a press event and a lift event, and the data of each touch event includes the first data of the lift event and the second data of the press event in the touch event.

[0238] S1704. Determine the touch positions and touch distances of the m touch events respectively according to the data of the m touch events.

[0239] The specific process of determining the touch positions and touch distances of m touch events is the same as that of determining the touch positions and touch distances of the touch events to be detected in the above embodiments, and will not be elaborated here.

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

[0241] 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 less than or equal to the second preset distance, then execute step S1706; otherwise, execute step S1708.

[0242] Optionally, the server can also execute the relevant processes of the above steps S1703 to S1705 for each of the m touch events according to the event identifier. Specifically, assume that the event identifier of the touch event to be detected is n, and assume that after the reporting time of the lift event in the touch event to be detected, the event identifiers of the m touch events are n + 1, n + 2,..., n + m in sequence. If the server determines in step 1702 that the touch distance of the touch event to be detected is less than or equal to the second preset distance, then execute the following steps:

[0243] 1) Obtain the first data and the second data of the touch event with the event identifier n + 1;

[0244] 2) Determine the 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;

[0245] 3) Determine whether the touch position of the touch event with the event identifier n + 1 belongs to the fourth preset area;

[0246] 4) If the touch position of the touch event with the event identifier n + 1 does not belong to the fourth preset area, then execute step S1708;

[0247] 5) If the touch position of the touch event with the event identifier n + 1 belongs to the fourth preset area, then determine the touch distance 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;

[0248] 6) Determine whether the touch distance of the touch event with the event identifier n + 1 is less than or equal to the second preset distance;

[0249] 7) If the touch distance of the touch event with the event identifier n + 1 is greater than the second preset distance, then execute step S1708;

[0250] 8) If the touch distance of the touch event with event identifier n + 1 is less than or equal to the second preset distance, then repeat the above processes 1) to 7) to judge the touch event with event identifier n + 2;

[0251] And so on, judge the touch events with event identifiers n + 3,..., n + m respectively;

[0252] 9) If in the judgment of the touch event with event identifier n + m, the result of the above step 6) is: the touch distance of the touch event with event identifier n + m is less than or equal to the second preset distance, then determine 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 all less than or equal to the second preset distance, and execute step S1706; otherwise, execute step S1708.

[0253] S1706. Judge whether the continuous event duration is greater than or equal to the preset continuous click duration; the continuous event duration refers to the time difference between the occurrence time of the lift event of the last touch event among the m touch events and the occurrence time of the press event of the touch event to be detected.

[0254] The preset continuous click duration can be set according to actual needs. Optionally, the preset continuous click duration can be 3000ms. That is, the server judges whether the continuous event duration is greater than or equal to 3000ms; if so, execute step S1707; if not, execute step S1708.

[0255] S1707. Determine that the touch event to be detected and the m touch events are edge continuous click mis-touch events.

[0256] If it is determined that the touch event to be detected and the m touch events are edge continuous click mis-touch events, the server can prompt an edge mis-touch fault, extract and save the data of the touch event to be detected and the m touch events and the corresponding edge mis-touch type, and use the next touch event after the m touch events as the touch event to be detected, and return to execute step S501 to judge whether the touch event is one of the edge mis-touch events of multiple preset types.

[0257] S1708. Determine that the touch event to be detected is not an edge continuous click mis-touch event.

[0258] 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 type among multiple preset edge mis-touch types, the server can use the next touch event after the touch event to be detected (i.e., the touch event with event identifier n + 1 above) as the touch event to be detected, and return to execute step S501 to judge whether the touch event is one of the edge mis-touch events of multiple preset types.

[0259] As can be seen from the above process, the parameters required to determine whether the touch event to be detected is an edge continuous click mis-touch event may include: the touch position, the touch distance, the data of m touch events that are temporally continuous with the touch event to be detected after the touch event to be detected, and the continuous event duration.

[0260] In this embodiment, based on the data of the touch event to be detected and the data of m touch events that are temporally continuous with the touch event to be detected after the touch event to be detected, it is determined whether the touch event to be detected and the m touch events are edge continuous click mis-touch events. The edge continuous click mis-touch event is a type of edge mis-touch that users may encounter during actual use. In this embodiment, the real experience of users during the use of the terminal is fully considered, and the edge continuous click mis-touch events in the touch events can be intelligently detected, which matches the edge mis-touch fault types that occur in the actual use of users, facilitating subsequent analysis, processing, and improvement of the data of the edge continuous click mis-touch events, and improving the user experience. In addition, the fourth preset area, the second preset distance, and the preset continuous click duration can quantitatively reflect the characteristics of the edge continuous click mis-touch event. 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 all less than or equal to the second preset distance, and the continuous event duration is greater than or equal to the preset continuous click duration, the edge continuous click mis-touch event can be accurately detected, improving the accuracy of detecting the edge continuous click mis-touch fault.

[0261] In one embodiment, after determining that the touch event to be detected and the m touch events are edge continuous click mis-touch events, it can be further determined whether the touch event to be detected and the m touch events are user-perceivable edge continuous click mis-touch events. A user-perceivable edge continuous click mis-touch event means that while the edge continuous click mis-touch occurs, the user performs other normal operations, and the edge continuous click mis-touch event and other edge mis-touch events affect the user's normal operations, resulting in the user being able to perceive that an edge mis-touch event has occurred.

[0262] For example, in an application scenario, the user holds the mobile phone with the left hand, and the left thumb continuously lifts and presses near a certain position on the left edge of the mobile phone, generating an edge continuous click mis-touch event. During this process, the user's right index finger drags a certain icon in the lower right direction. Exemplarily, Figure 18 shows a schematic diagram of the touch event reporting points on the display screen corresponding to this application scenario. Figure 18 In it, 1801 represents the reporting point of the touch event corresponding to the user's left thumb, and 1802 represents the reporting point of the touch event corresponding to the user's right index finger.

[0263] Due to the accidental touch failure of continuous edge clicks caused by the continuous lifting and pressing of the left thumb, the user's right index finger fails to respond when dragging an icon in the lower right direction, and then the user perceives that an accidental edge touch event has occurred. In this scenario, the accidental touch event of continuous edge clicks corresponding to the continuous lifting and pressing operation of the left thumb is an accidental touch event of continuous edge clicks that can be perceived by the user.

[0264] In one implementation, determining whether an accidental touch event of continuous edge clicks is an accidental touch event of continuous edge clicks that can be perceived by the user can be achieved through the following process:

[0265] If it is determined that the touch event to be detected is an accidental touch event of continuous edge clicks, then:

[0266] Obtain the number of accidental edge touch events in the second time period to get the third quantity; where the second time period refers to the time period between the occurrence time of the press event in the touch event to be detected and the occurrence time of the lift event in the last touch event among the m touch events; obtain the number of touch events in the second time period to get the second quantity; if the second quantity is greater than the third quantity, then determine that the touch event to be detected and the m touch events are accidental touch events of continuous edge clicks that can be perceived by the user.

[0267] That is to say, the server determines whether the total number of touch events in the time period when the accidental touch event of continuous edge clicks occurs is greater than the total number of accidental edge touch events (including accidental touch events of continuous edge clicks and other accidental edge touch events). If so, it is determined that this accidental touch event of continuous edge clicks is an accidental touch event of continuous edge clicks that can be perceived by the user.

[0268] Optionally, the third quantity can be determined by obtaining the number of event identifiers of accidental edge touch events in the second time period, or the third quantity can be determined by obtaining the number of pairs of press / lift events with accidental edge touches in the second time period.

[0269] In this embodiment, when it is determined that the touch event to be detected and the m touch events are accidental touch events of continuous edge clicks, determining whether this accidental touch event of continuous edge clicks is an accidental touch event of continuous edge clicks that can be perceived by the user is further matched with the type of accidental edge touch failure that occurs during the user's actual use, truly reflecting the user experience, so as to facilitate subsequent targeted analysis, processing, and improvement, and further improve the user experience.

[0270] It can be understood that in the process of determining whether the touch event to be detected is one of the edge mis-touch events of multiple preset types, the above-mentioned order can be used for sequential determination, that is, first determine whether it is an edge long-press mis-touch event, then determine whether it is an edge swipe mis-touch event, then determine whether it is a corner quick click mis-touch event, and finally determine whether it is an edge continuous click mis-touch event. In some embodiments, the determination can also be made in other orders, and the embodiments of the present application do not make any limitations in this regard.

[0271] The above text has introduced in detail the examples of the edge mis-touch detection method provided by the embodiments of the present application. It can be understood that in order for the electronic device to implement the above functions, it includes the corresponding hardware and / or software modules for executing each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of the examples described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the way of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in combination with the embodiments, but such implementation should not be considered to exceed the scope of the present application.

[0272] The embodiments of the present application can divide the electronic device into functional modules according to the above method examples. For example, each function can be correspondingly divided into each functional module, such as a detection unit, a processing unit, a display unit, etc., or two or more functions can be integrated into one module. The above integrated module can be implemented in the form of hardware or in the form of a software functional module. It should be noted that the division of modules in the embodiments of the present application is illustrative, only a logical function division, and there can be other division methods in actual implementation.

[0273] Figure 19 It is a schematic structural diagram of a detection device for edge mis-touch provided by an embodiment of the present application. As Figure 19 shown, the detection device for edge mis-touch provided in this embodiment may include:

[0274] An acquisition module 1901, configured to acquire data of the 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;

[0275] A detection module 1902, configured to determine whether the touch event to be detected is one of the edge mis-touch events of multiple preset types according to a preset edge mis-touch area of the electronic device and the first data and the second data of the touch event to be detected.

[0276] In one embodiment, the detection module 1902 is specifically configured to: determine the touch position and 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; wherein, the touch distance is used to characterize the distance between the position of the press event and the position of the lift event in a preset direction in the touch event; determine whether the touch event to be detected is one of the multiple preset types of edge accidental touch events according to the preset edge accidental touch area and the touch position and touch distance of the touch event to be detected.

[0277] In one embodiment, the detection module 1902 is specifically configured to: determine 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 to characterize the time difference between the occurrence time of the lift event and the occurrence time of the press event in the touch event; determine whether the touch event to be detected is one of the multiple preset types of edge accidental touch events according to the preset edge accidental touch area and the touch position, touch distance and touch duration of the touch event to be detected.

[0278] In one embodiment, the multiple preset types of edge accidental touch events include: edge long press accidental touch event, edge slide accidental touch event, and corner quick click accidental touch event.

[0279] In one embodiment, the preset edge accidental 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 less than or equal to the first preset distance, and the touch duration of the touch event to be detected is greater than or equal to the preset long press duration, then determine that the touch event to be detected is the edge long press accidental touch event.

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

[0281] In one embodiment, the detection module 1902 is further configured to: obtain the first quantity of edge accidental touch events within a first time period; the first time period refers to the time period between the occurrence time of the press event and the occurrence time of the lift event in the touch event to be detected; obtain the second quantity of touch events within the first time period; if the second quantity is greater than the first quantity, then determine that the touch event to be detected is a user-perceivable edge long press accidental touch event.

[0282] In one embodiment, the preset edge accidental 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 a 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, determine that the touch event to be detected is the edge sliding accidental touch event.

[0283] In one embodiment, the detection module 1902 is further specifically configured to: obtain a first quantity of edge accidental touch events within a first time period; the first time period refers to the time period between the occurrence time of the press event and the occurrence time of the lift event in the touch event to be detected; obtain a second quantity of touch events within the first time period; if the second quantity is greater than the first quantity, determine that the touch event to be detected is a user-perceivable edge sliding accidental touch event.

[0284] In one embodiment, the preset edge accidental 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 less than or equal to a third preset distance, and the touch duration of the touch event to be detected is less than or equal to a preset quick click duration, determine that the touch event to be detected is the corner quick click accidental touch event.

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

[0286] if the touch position of the touch event to be detected belongs to the fourth preset area, and the touch distance of the touch event to be detected is less than or equal to the second preset distance, then obtain data of m touch events that are temporally continuous with the touch event to be detected after the touch event to be detected; m is a positive integer; determine the touch positions and touch distances of the m touch events respectively according to the data of the m touch events; if the touch positions of the m touch events all belong to the fourth preset area, the touch distances of the m touch events are all less than or equal to the second preset distance, and the continuous event duration is greater than or equal to a preset continuous click duration, determine that the touch event to be detected and the m touch events are edge continuous click accidental touch events; wherein, the continuous event duration refers to the time difference between the occurrence time of the lift event in the last touch event among the m touch events and the occurrence time of the press event in the touch event to be detected.

[0287] In one embodiment, the detection module 1902 is further specifically configured to: obtain a third quantity of edge accidental touch events within a second time period; the second time period refers to the time period between the occurrence time of the press event in the touch event to be detected and the occurrence time of the lift event in the last touch event among the m touch events; obtain a second quantity of touch events within the second time period; if the second quantity is greater than the third quantity, determine that the touch event to be detected and the m touch events are user-perceivable edge continuous click accidental touch events.

[0288] In one embodiment, the first data includes the reported point coordinates of the press event, and the second data includes the reported point coordinates of the lift event; the detection module 1902 is specifically configured to: determine the touch position of the touch event to be detected according to the reported point coordinates of the press event and the reported point coordinates of the lift event in the touch event to be detected; determine the absolute value of the difference between the reported point coordinates of the lift event and the reported point coordinates of the press event in the touch event to be detected in the preset direction, to obtain the touch distance of the touch event to be detected.

[0289] The edge accidental touch detection device provided in this embodiment is used to execute the above-mentioned edge accidental touch detection method, and the technical principles and technical effects are similar, so details are not described herein again.

[0290] Please refer to Figure 20 , which shows a structure of an electronic device provided in an embodiment of the present application. The electronic device may be the terminal device or the server that generates the data of the 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 various functional applications and information processing by running software programs and modules. The receiver 2002 and the transmitter 2003 may be implemented as a communication component, and the communication component may be a baseband chip. The memory 2004 is connected to the processor 2001 through the bus 2005. The memory 2004 may be used to store at least one program instruction, and the processor 2001 is used to execute at least one program instruction to implement the technical solution of the above embodiment. The implementation principle and technical effect are similar to those of the related embodiment of the above method, so details are not described herein again.

[0291] After the electronic device is powered 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, after the processor performs baseband processing on the data to be sent, it outputs a baseband signal to the control circuit in the control circuit. The control circuit performs radio frequency processing on the baseband signal and then sends the radio frequency signal outwards in the form of electromagnetic waves through the antenna. When data is sent to the electronic device, the control circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor. The processor converts the baseband signal into data and processes the data.

[0292] Those skilled in the art can understand that for the sake of convenience of description, Figure 20 only one memory and one processor are shown. In an actual electronic device, there may be multiple processors and memories. The memory can also be referred to as a storage medium or a storage device, etc., and the embodiments of the present application do not limit this.

[0293] As an optional implementation manner, the processor may include a baseband processor and a central processor. The baseband processor is mainly used to process communication data, and the central processor is mainly used to execute the software program and process the data of the software program. Those skilled in the art can understand that the baseband processor and the central processor can be integrated in one processor, or can be separate processors interconnected through technologies such as a bus. Those skilled in the art can understand that an electronic device can include multiple baseband processors to adapt to different network modes, and an electronic device can include multiple central processors to enhance its processing ability. Each component of the electronic device can be connected through various buses. The baseband processor can also be referred to as a baseband processing circuit or a baseband processing chip. The central processor can also be referred to as a central processing circuit or a central processing chip. The function of processing communication protocols and communication data can be built into the processor, or can be stored in the memory in the form of a software program, and the processor executes the software program to implement the baseband processing function. The memory can be integrated in the processor or can be independent of the processor. The memory includes a cache Cache, which can store frequently accessed data / instructions.

[0294] In the embodiments of the present application, the processor can be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being completed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor.

[0295] In the embodiments of the present application, the memory can be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or can also be a volatile memory, such as a random-access memory (RAM). The memory is any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, not limited thereto.

[0296] The memory in the embodiments of the present application can also be a circuit or any other device capable of implementing a storage function, for storing program instructions and / or data. In the methods provided by the embodiments of the present application, all or part of them can be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that the computer can access or a data storage device such as a server or a data center that includes one or more integrated available media. The available medium can be a magnetic medium (such as a floppy disk, a hard disk, a magnetic tape), an optical medium (such as a digital video disc (DVD)), or a semiconductor medium (such as an SSD), etc.

[0297] The embodiments of the present application provide a computer program product. When the computer program product runs on a terminal, the terminal is enabled to execute the technical solutions in the above embodiments. The implementation principle and technical effects are similar to those of the above related embodiments and will not be elaborated here.

[0298] An embodiment of the present application provides a computer-readable storage medium, on which program instructions are stored. When the program instructions are executed by a terminal, the terminal is caused to execute the technical solutions of the above embodiments. The implementation principle and technical effects are similar to those of the above related embodiments, and will not be elaborated here. In summary, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements on some of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the various embodiments of the present application.

[0299] In addition, an embodiment of the present application further provides a device, which may specifically be a chip, a component or a module. The device may include a processor and a memory connected to each other; wherein, the memory is used to store computer-executable instructions. When the device runs, the processor may execute the computer-executable instructions stored in the memory, so that the chip executes the edge accidental touch detection method in the above method embodiments.

[0300] Among them, the electronic device, computer-readable storage medium, computer program product or chip provided in this embodiment are all used to execute the corresponding method provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method provided above, and will not be elaborated here.

[0301] Through the description of the above embodiments, those skilled in the art can understand that for the convenience and simplicity of description, only the above division of each functional module is used as an example. In actual applications, the above functions can be allocated to different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

[0302] In several embodiments provided by the present application, it should be understood that the disclosed device and method can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of modules or units is only a logical functional division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection may be through some interfaces. The indirect coupling or communication connection of the device or unit may be in an electrical, mechanical or other form.

[0303] The unit described as a separation component may or may not be physically separated. The component shown as a unit may be a single physical unit or multiple physical units, that is, it may be located in one place or distributed to multiple different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0304] In addition, each functional unit in various embodiments of the present application may be integrated in a processing unit, or each unit may exist physically alone, or two or more units may be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

[0305] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiments of the present application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions for causing a device (which can be a single-chip microcomputer, a chip, etc.) or a processor to execute all or part of the steps of the methods of the various embodiments of the present application. The aforementioned storage medium includes: USB flash drives, mobile hard disks, read only memory (ROM), random access memory (RAM), magnetic disks, optical disks, and other various media that can store program codes.

[0306] In addition, it should be noted that in the above embodiments, the descriptions of the various embodiments have their own emphases. For parts not detailed or recorded in a certain embodiment, reference can be made to the relevant descriptions of other embodiments. It should be understood that the magnitudes of the sequence numbers of the steps in the above embodiments do not mean the order of execution is prior or posterior. The execution order of each process should be determined according to its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. In addition, the reference to "one embodiment" or "some embodiments" etc. described in the specification of the present application means that a specific feature, structure, or characteristic described in combination with this embodiment is included in one or more embodiments of the present application. Thus, the statements "in one embodiment", "in some embodiments", "in other some embodiments", "in still other embodiments", etc. that appear in different places in this specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways.

[0307] The above content is only a specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of changes or substitutions, which should all be covered within the protection 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 edge accidental touches, characterized in that, applied to an electronic device, the touch screen of the electronic device includes a preset edge accidental touch area, and the method includes: Obtaining data of a touch event to be detected, wherein 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; Determining a touch position, a touch distance, and a 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; wherein, the touch distance is used to characterize the distance between the position of the press event and the position of the lift event in a preset direction in the touch event, and the touch duration is used to characterize the time difference between the occurrence time of the lift event and the occurrence time of the press event in the touch event; Determining whether the touch event to be detected is one of a plurality of preset types of edge accidental touch events according to the preset edge accidental touch area and the touch position, touch distance, and touch duration of the touch event to be detected; the plurality of preset types of edge accidental touch events include: edge long - press accidental touch event, edge swipe accidental touch event, and corner quick - click accidental touch event; The preset edge accidental touch area includes a first preset area, and determining whether the touch event to be detected is one of the plurality of preset types of edge accidental touch events according to the preset edge accidental touch area and the touch position, touch distance, and touch duration of the touch event to be detected includes: 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 less than or equal to a first preset distance, and the touch duration of the touch event to be detected is greater than or equal to a preset long - press duration, then determining that the touch event to be detected is the edge long - press accidental touch event.

2. The method according to claim 1, characterized in that, The touch position includes the position of the press event and the position of the lift event in the touch event; that the touch position of the touch event to be detected belongs to the first preset area includes: Both the position of the press event and the position of the lift event in the touch event to be detected belong to the first preset area.

3. The method according to claim 1, characterized in that, The method further includes: Obtaining a first quantity of edge accidental touch events within a first time period; the first time period refers to the time period between the occurrence time of the press event and the occurrence time of the lift event in the touch event to be detected; Obtaining a second quantity of touch events within the first time period; If the second quantity is greater than the first quantity, then determining that the touch event to be detected is a user - perceivable edge long - press accidental touch event.

4. The method according to claim 1, characterized in that, The preset edge accidental touch area includes a second preset area, and determining whether the touch event to be detected is one of the plurality of preset types of edge accidental touch events according to the preset edge accidental touch area and the touch position, touch distance, and touch duration of the touch event to be detected includes: 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, then it is determined that the touch event to be detected is the edge sliding false touch event.

5. The method according to claim 4, wherein, the method further includes: obtaining a first quantity of edge false touch events within a first time period; the first time period refers to the time period between the occurrence time of the press event and the occurrence time of the lift event in the touch events to be detected; obtaining a second quantity of touch events within the first time period; if the second quantity is greater than the first quantity, then it is determined that the touch event to be detected is a user-perceivable edge sliding false touch event.

6. The method according to claim 1, wherein, the preset edge false touch area includes a third preset area, and determining whether the touch event to be detected is one of the multiple preset types of edge false touch events according to the preset edge false touch area and the touch position, touch distance and touch duration of the touch event to be detected includes: 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 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, then it is determined that the touch event to be detected is the corner quick click false touch event.

7. The method according to claim 1, wherein, 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 the multiple preset types of edge false touch events according to the preset edge false touch area and the touch position and touch distance of the touch event to be detected includes: if the touch position of the touch event to be detected belongs to the fourth preset area, and the touch distance of the touch event to be detected is less than or equal to the second preset distance, then, obtain data of m touch events that are temporally continuous with the touch event to be detected after the touch event to be detected; m is a positive integer; respectively determining the touch position and touch distance of the m touch events according to the data of the m touch events; if the touch positions of the m touch events all belong to the fourth preset area, the touch distances of the m touch events are all less than or equal to the second preset distance, and the continuous event duration is greater than or equal to the preset continuous click duration, then it is determined that the touch event to be detected and the m touch events are edge continuous click false touch events; wherein, the continuous event duration refers to the time difference between the occurrence time of the lift event in the last touch event among the m touch events and the occurrence time of the press event in the touch event to be detected.

8. The method according to claim 7, wherein, the method further includes: Obtain a third quantity of edge accidental touch events within a second time period; the second time period refers to the time period between the occurrence moment of the press event in the touch event to be detected and the occurrence moment of the lift event in the last touch event among the m touch events; Obtain a second quantity of touch events within the second time period; If the second quantity is greater than the third quantity, determine that the touch event to be detected and the m touch events are edge continuous click accidental touch events that can be perceived by the user.

9. The method according to any one of claims 1 to 8, characterized in that, The first data includes the reported point coordinates of the press event, and the second data includes the reported point coordinates of the lift event; the determining the touch position and 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: Determine the touch position of the touch event to be detected according to the reported point coordinates of the press event and the reported point coordinates of the lift event in the touch event to be detected; Determine the absolute value of the difference between the reported point coordinates of the lift event and the reported point coordinates of the press event in the touch event to be detected in the preset direction, to obtain the touch distance of the touch event to be detected.

10. An electronic device, characterized in that, 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 execute the method according to any one of claims 1 to 9.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the processor is enabled to execute the method according to any one of claims 1 to 9.

Images