An input monitoring method, apparatus, and electronic device

Abstract

This application provides an input monitoring method, apparatus, and electronic device. The method includes: monitoring input events of touch points on a touch panel; calculating the input event value of a row / column based on the input events of all touch points in a row / column on the touch panel; and determining whether a touch event is generated out of thin air in the row / column based on the input event value. According to the method of this application, overall monitoring of rows or columns on the touch panel and determining whether a touch event is generated out of thin air in a row or column can greatly improve the accuracy of the determination.

Description

Technical Field

[0001] This application relates to the field of smart terminal technology, and in particular to an input monitoring method, apparatus and electronic device. Background Technology

[0002] In existing technology applications, touch panels are a common user input solution. A touch panel contains multiple touch points. When a user interacts with a touch point (e.g., clicks it), the touch panel generates a touch event corresponding to that point. The touch recognition system identifies the touch point corresponding to the touch event to determine the location of the user's touch input.

[0003] Capacitive touch panels are a common technical solution for touch panel input. They operate by sensing the electrical current emitted by the human body. However, they are easily affected by magnetic fields, voltage, static electricity, conductive media, and physical damage. When affected by these factors, the touch panel may exhibit random touches. That is, the touch panel may collect input signals at locations where the user has not made any touch operations, resulting in artificially generated touch events, known as "ghost touches."

[0004] Because capacitive touch panels are integrated, when "ghost hands" appear in certain areas of the capacitive touch panel, it is impossible to repair only that area; the entire capacitive touch panel must be replaced, which greatly increases the maintenance cost of the device. Summary of the Invention

[0005] To address the problem of how to repair touch events that are generated out of thin air in capacitive touch panels under existing technology, this application provides an input monitoring method, apparatus, and electronic device. This application also provides a computer-readable storage medium.

[0006] The embodiments of this application adopt the following technical solutions:

[0007] Firstly, this application provides an input monitoring method, including:

[0008] Monitor input events at touch points on the touch panel;

[0009] Calculate the input event value of the row / column based on the input events of all touch points in the row / column on the touch panel;

[0010] Determine whether a touch event is generated out of thin air in the row / column based on the input event value.

[0011] In one implementation of the first aspect, calculating the input event value of a row / column based on the input events of all touch points in a row / column on the touch panel includes:

[0012] Calculate the input event value of the row / column in a monitoring cycle based on all input events of all touch points in a row / column on the touch panel in a monitoring cycle.

[0013] In one implementation of the first aspect, calculating the input event value of the row / column in a monitoring cycle based on all input events of all touch points in a row / column on the touch panel in a monitoring cycle includes:

[0014] Calculate the input event value of the touch point for one monitoring cycle, where the value is equal to the sum of the input event values ​​of the touch point obtained each time input event is collected within one monitoring cycle.

[0015] In one implementation of the first aspect, calculating the input event value of the touch point for the monitoring period includes:

[0016] The point weight corresponding to the input event of the touch point is determined based on the input type of the input event of the touch point;

[0017] The input event value of the touch point is calculated based on the point weight corresponding to the input event of the touch point.

[0018] In one implementation of the first aspect, calculating the input event value of a row / column based on the input events of all touch points in a row / column on the touch panel includes:

[0019] Confirm the row weight / column weight of the aforementioned row / column;

[0020] The input event value of the row / column is calculated based on the row weight / column weight.

[0021] In one implementation of the first aspect, confirming the row weight / column weight of the row / column includes:

[0022] The row / column weights are calculated based on the user's touch habits.

[0023] In one implementation of the first aspect, confirming the row weight / column weight of the row / column includes:

[0024] The weights of the rows / columns are adjusted based on the uniformity of the distribution of input events in the row / column.

[0025] In one implementation of the first aspect, determining whether a touch event is generated out of thin air in the row / column based on the input event value includes:

[0026] When the input event value of a row / column in a monitoring cycle is greater than a preset threshold, it is determined that there is a touch event generated out of thin air in the row / column.

[0027] In one implementation of the first aspect, determining whether a touch event is generated out of thin air in the row / column based on the input event value includes:

[0028] When the input event value of a row / column is greater than a preset threshold for N consecutive monitoring cycles, it is determined that there is a touch event generated out of thin air in the row / column, where N is an integer greater than 1.

[0029] In one implementation of the first aspect, the method further includes:

[0030] When a touch event is generated out of thin air in a row / column, the input to that row / column is blocked.

[0031] Secondly, this application provides an input monitoring device, comprising:

[0032] The input event acquisition module is used to acquire input events from touch points on the touch panel;

[0033] The calculation module is used to calculate the input event value of a row / column based on the input events of all touch points in a row / column on the touch panel;

[0034] The recognition module is used to determine whether a touch event generated out of thin air exists in the row / column based on the input event value.

[0035] Thirdly, this application provides an electronic device, which includes a memory for storing computer program instructions and a processor for executing the program instructions, wherein when the computer program instructions are executed by the processor, the electronic device is triggered to perform the method steps as described in the embodiments of this application.

[0036] Fourthly, this application provides a computer-readable storage medium storing a computer program that, when run on a computer, causes the computer to perform the methods of the embodiments of this application.

[0037] The technical solutions proposed in the embodiments of this application can achieve at least the following technical effects:

[0038] According to the method in the embodiments of this application, the overall monitoring of rows or columns on the touch panel can be performed to determine whether there are touch events generated out of thin air in the rows or columns on the touch panel, which can greatly improve the accuracy of the determination. Attached Figure Description

[0039] Figure 1The diagram shows the arrangement of touch points on the touch panel.

[0040] Figure 2 The image shown is a diagram illustrating the appearance of a "ghost hand" on a mobile phone's touchscreen.

[0041] Figure 3 The diagram shows the arrangement of touch points on the touch panel.

[0042] Figure 4 This is a structural block diagram of a user terminal device according to an embodiment of this application;

[0043] Figure 5A This is a structural block diagram of a user terminal device 400 according to an embodiment of this application;

[0044] Figure 5B This is a structural block diagram of a user terminal device 400 according to an embodiment of this application;

[0045] Figure 5C This is a structural block diagram of a user terminal device 400 according to an embodiment of this application;

[0046] Figure 6 The diagram shown is a flowchart of a method according to an embodiment of this application;

[0047] Figure 7 The image shown is a bar chart of input event values ​​according to an embodiment of this application;

[0048] Figure 8 The diagram shown is a flowchart of a method according to an embodiment of this application;

[0049] Figure 9 The diagram shown is a schematic representation of a mobile phone display interface according to an embodiment of this application;

[0050] Figure 10 The diagram shown is a schematic representation of a mobile phone display interface according to an embodiment of this application;

[0051] Figure 11 The diagram shown is a schematic representation of a mobile phone display interface according to an embodiment of this application.

[0052] Figure 12 The diagram shown is a structural block diagram of a device according to an embodiment of this application;

[0053] Figure 13 This is a schematic diagram of the structure of a user terminal device provided in this application.

[0054] Figure 14 This is a schematic diagram of the hardware structure of a user terminal device provided in this application. Detailed Implementation

[0055] The technical solutions of the embodiments of this application are described below with reference to the accompanying drawings. In the description of the embodiments of this application, the terminology used in the following embodiments is for the purpose of describing specific embodiments only and is not intended to be a limitation of this application. As used in the specification and appended claims of this application, the singular expressions “a,” “the,” “the,” “the,” and “this” are intended to also include expressions such as “one or more,” unless the context clearly indicates otherwise. It should also be understood that in the following embodiments of this application, “at least one” and “one or more” refer to one or more (including two). The character “ / ” generally indicates that the preceding and following objects are in an “or” relationship.

[0056] References to "one embodiment" or "some embodiments" in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized. The term "connection" includes direct connections and indirect connections, unless otherwise stated. "First" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated.

[0057] In the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0058] In existing technology applications, when "ghost hand" artifacts appear in certain areas of a capacitive touch panel, it's impossible to perform localized repairs on those areas. If you don't want to replace the entire touch panel and want to continue using the affected area, a feasible solution is to filter the input events generated by the touch panel, identify the input events corresponding to the "ghost hand" artifacts, and block those events. This would prevent the "ghost hand" artifacts from interfering with the user's normal touch input.

[0059] However, under current hardware conditions, filtering input events generated by the touch panel to identify those corresponding to "ghost hands" requires a comprehensive analysis of all input events generated by the touch panel. This not only consumes significant processing resources but also results in a high error rate due to the difficulty of identification. Consequently, it not only fails to prevent "ghost hands" from interfering with the user's normal touch input but also introduces new interference.

[0060] To address the above problems, one embodiment of this application proposes a solution to deal with "ghost hands".

[0061] Specifically, when a "ghost hand" appears on the touch panel, since the cause of the "ghost hand" is usually physical damage to the touch panel, the position of the "ghost hand" is fixed (appearing at the touch point where physical damage occurs), and there will be no "ghost hand" drifting.

[0062] Furthermore, the touch recognition system does not identify user touch operations by analyzing touch events at a single touch point. Instead, it analyzes touch events from multiple touch points on the touch panel (for example, when clicking, a user will not click only one touch point, but multiple touch points at the fingertip simultaneously). Therefore, the absence of touch events from a few touch points will not affect the touch recognition system's ability to correctly recognize user touch input.

[0063] For the reasons mentioned above, if we disregard whether the input of the touch point is caused by the "ghost hand" and instead block all inputs from that touch point (intercepting the input at the "ghost hand" location), then we can avoid the "ghost hand" interfering with the user's normal input without affecting the normal recognition of the user's touch input, without performing input analysis.

[0064] For example, Figure 1 The diagram shows the arrangement of touch points on a touch panel. Figure 1 As shown, each diamond represents a touch point on the touch panel. Touch point A1 has physical damage. Even when the user does not tap touch point A1, it still outputs a touch signal, causing the touch panel to generate a touch event corresponding to touch point A1, resulting in a "ghost hand." In this application scenario, the "ghost hand" always appears at touch point A1. By blocking all inputs to touch point A1, the "ghost hand" can be prevented from interfering with the user's normal input. Meanwhile, the touch recognition system can still correctly recognize the user's touch input through input events from other touch points besides touch point A1.

[0065] Furthermore, to block input from touch points exhibiting "ghost hand" behavior, it is first necessary to identify these touch points. One approach is to determine these touch points by examining touch performance parameters within the screen's response area. Specifically, the examined touch performance parameters include: number of clicks, touch point movement distance, touch duration, and touch intensity.

[0066] For example, a touch point outputs a touch signal when it is clicked to indicate that it has been clicked. A touch point exhibiting "ghost hand" behavior will also output a touch signal even when not clicked. Since users typically do not continuously click a single touch point for an extended period, while touch points exhibiting "ghost hand" behavior will continuously output touch signals, when identifying the number of times a touch point has been clicked based on touch signal output, touch points exhibiting "ghost hand" behavior are often clicked far more frequently than touch points without "ghost hand" behavior.

[0067] Therefore, the number of times a touch point is clicked within a certain time period can be used to determine whether a touch point has experienced a "ghost hand" (it should be noted that a touch point being clicked refers to the touch point being clicked based on the touch signal output by the touch point, including erroneous clicks detected when a touch point experiences a "ghost hand" effect, and does not equal the actual click by the user). Specifically, under normal usage conditions, a threshold number of touch point clicks is set within a preset time period (e.g., 1 minute) (e.g., 500 times). When the number of times a touch point is clicked within a preset time period exceeds the preset number, it is considered that the touch point has experienced a "ghost hand" effect. At this time, the touch point is determined to be an invalid touch point and is blocked. Similarly, if the number of touch signals output by the touch point within a preset time period does not exceed the preset number, the touch point is considered not to have experienced a "ghost hand" effect and is determined to be a valid touch point.

[0068] The aforementioned method of determining whether a touchpoint has a "ghost hand" effect by detecting touch parameters can identify touchpoints with "ghost hands" to a certain extent. However, in practical applications, identifying "ghost hands" based on the number of clicks on a single touchpoint has a significant margin of error. Specifically, touchpoints on a touch panel are typically arranged in a matrix, and each touchpoint is not independently connected to the signal acquisition module. Touchpoint location is achieved by identifying the row and column to which it belongs; that is, the touch panel's signal acquisition module locates touchpoints with input signals by identifying the row and column to which the touchpoint belongs. Therefore, when a touch panel suffers physical damage, it is usually a problem affecting a single row or column. However, if a problem occurs in a single row or column leading to a "ghost hand," at any given moment, the location of the "ghost hand" could be any one or more touchpoints in that affected row or column, not all touchpoints in that affected row or column.

[0069] For example, Figure 2 The image shown illustrates a "ghost hand" effect appearing on a mobile phone's touchscreen. Figure 2 As shown, suppose in an interactive scenario, to enhance the user experience, when a user taps the screen, a dot is displayed at the tap location to respond to the tap. When the touch panel is physically damaged, certain areas of the touch panel will still recognize a tap and display a dot (a "ghost hand") even when the user has not tapped the screen. Figure 2 As shown in the left image, dots are displayed at multiple locations on the screen (210) when the user does not perform any screen tapping operation; as Figure 2 As shown in the right figure, dots are displayed at multiple locations within 220 on the screen.

[0070] Because "ghost hands" appear on any one or more touch points in a row or column where the entire touch panel is malfunctioning, the frequency of "ghost hands" appearing on a specific touch point in that row or column may be lower than the frequency of "ghost hands" appearing on a single touch point malfunctioning on the entire touch panel. Therefore, if the number of times a single touch point malfunctions is used to identify touch points exhibiting "ghost hands," it is possible to miss touch points in rows or columns where the entire touch panel is malfunctioning.

[0071] For example, Figure 3 The diagram shows the arrangement of touch points on a touch panel. A setting determines that a touch point is considered to have experienced a "ghost hand" when the cumulative number of clicks exceeds a preset 500 within one minute. Figure 3As shown, suppose touch point A3 on the touch panel suffers physical damage, resulting in a "ghost hand" effect. Even when the user does not tap touch point A3, it will still output a touch signal. Based on the touch signal output by touch point A3, if it is identified that touch point A3 has been tapped 1200 times within one minute, then according to the preset number of taps (500), it can be determined that touch point A3 has experienced a "ghost hand" effect. Therefore, by blocking the touch signal input from touch point A3, the interference of the "ghost hand" effect on the user's normal input operation can be avoided.

[0072] Suppose that row B3 on the touch panel suffers physical damage, resulting in a "ghost hand" appearing on row B3. Even if the user does not tap row B3, the touch points on row B3 will still output touch signals. However, since row B contains multiple touch points, the frequency of the "ghost hand" appearing on touch point B13 in row B3 is lower than the frequency of the "ghost hand" appearing in row B3. For example, at time T13, touch points B13 and B23 on row B3 exhibit a "ghost hand"; at time T23, touch points B23 and B33 on row B3 exhibit a "ghost hand." For row B3, a "ghost hand" appears at both times T13 and T23, while for touch point B13, a "ghost hand" appears only at time T13. Suppose that based on the touch signal output by touch point B13, it is identified that touch point B13 is clicked 200 times within 1 minute. At this time, according to the preset number of 500, touch point B13 will not be identified as a touch point with a "ghost hand" appearing. The touch signal input of touch point B13 will not be blocked, and the "ghost hand" appearing on touch point B13 will interfere with the user's normal input operation.

[0073] Therefore, in one embodiment of this application, an input monitoring method is proposed. In this method, rows or columns on the touch panel are monitored as a whole to accurately determine whether "ghost hands" appear on the rows or columns of the touch panel.

[0074] For example, Figure 4 This is a structural block diagram of a user terminal device according to an embodiment of this application. Figure 4 As shown, the user terminal device 400 includes a touch panel 401 and a processor 402.

[0075] The touch panel 401 includes multiple touch points arranged in rows / columns and a signal processing chip. The touch panel 401 can be integrated with a display screen to form a touch screen; the touch panel 401 can also be a standalone input device (e.g., an electronic drawing board). When a touch point on the touch panel 401 is clicked, a touch signal corresponding to the clicked touch point is generated. The signal processing chip of the touch panel 401 generates a touch event based on the touch signal (the touch event includes the location of the clicked touch point) and outputs the touch event.

[0076] The processor 402 is connected to the touch panel 401. The processor 402 is loaded with a touch recognition module, which recognizes the user's touch operation behavior based on touch events.

[0077] According to the input monitoring method in this application embodiment, a touch detection module is constructed in the user terminal device 400. The touch detection module monitors the touch events output by the touch panel 401 and detects whether there is "ghost hand" input. When "ghost hand" input exists, the touch event corresponding to the "ghost hand" is blocked before the touch event is input to the touch recognition module (preventing the touch event corresponding to the "ghost hand" from being input to the touch recognition module), thereby avoiding interference from the "ghost hand" in the recognition of the user's touch operation behavior.

[0078] Figure 5A This is a structural block diagram of a user terminal device 400 according to an embodiment of this application. Figure 5A As shown, touch event filtering can be implemented within the system framework of the user terminal device. The user terminal device 400 includes a touch panel 401 and a processor 402. The processor 402 includes a touch detection module 503A and a touch recognition module 504A.

[0079] The touch recognition module 504A is used to identify the user's touch operation behavior based on touch events. The processor 402 is connected to the touch panel 401. The touch detection module 503A loaded in the processor 402 monitors the touch events output by the touch panel 401 to detect the presence of "ghost hand" input. When no "ghost hand" input is found, the touch detection module 503A forwards the touch events output by the touch panel 401 to the touch recognition module 504A. When "ghost hand" input is found, the touch detection module 503A masks the touch events corresponding to the "ghost hand" input from the touch events output by the touch panel 401 and forwards the touch events that do not contain the "ghost hand" input to the touch recognition module 504A.

[0080] Figure 5B This is a structural block diagram of a user terminal device 400 according to an embodiment of this application. Figure 5B As shown, touch event filtering can also be implemented in the touch panel of the user terminal device. The user terminal device 400 includes a touch panel 401 and a processor 402. The touch panel 401 includes a plurality of touch points 503B arranged in rows and columns, a touch signal processing module 504B, and a touch detection module 505B.

[0081] The processor 402 is equipped with a touch recognition module. The processor 402 is connected to the touch panel 401, and the processor 402 receives touch events output by the touch panel 401. The touch recognition module identifies the user's touch operation behavior based on the touch events.

[0082] When a touch point in touch point 503B is clicked, a corresponding touch signal is generated and sent to touch signal processing module 504B. Touch signal processing module 504B generates a corresponding touch event. Touch detection module 505B monitors the touch events output by touch signal processing module 504B to detect the presence of "ghost hand" input. When no "ghost hand" input is found, touch detection module 505B outputs the touch event from touch signal processing module 504B to processor 402. When "ghost hand" input is found, touch detection module 505B masks the touch event corresponding to the "ghost hand" input and outputs the touch event that does not contain the "ghost hand" input to processor 402.

[0083] Figure 5C This is a structural block diagram of a user terminal device 400 according to an embodiment of this application. Figure 5C As shown, touch events can also be filtered through a separate processing chip. The user terminal device 400 includes a touch panel 401, a processor 502C, and a processor 402.

[0084] The touch panel 401 includes multiple touch points 504C arranged in rows and columns, and a touch signal processing module 505C. When a touch point in one of the touch points 504C is clicked, a corresponding touch signal is generated, and the touch signal is sent to the touch signal processing module 505C, which generates a corresponding touch event.

[0085] Processor 402 is connected to touch panel 401, and processor 502C is connected to processor 402. Processor 402 is equipped with a touch recognition module. The touch detection module monitors the touch events output by touch signal processing module 505C to detect the presence of "ghost hand" input. When no "ghost hand" input is present, touch detection module 505B outputs the touch events from touch signal processing module 505C to processor 502C. When "ghost hand" input is present, touch detection module masks the touch events corresponding to the "ghost hand" input and outputs the touch events that do not contain the "ghost hand" input to processor 502C.

[0086] The processor 502C is equipped with a touch recognition module. The processor 502C receives touch events output by the processor 402, and the touch recognition module identifies the user's touch operation behavior based on the touch events.

[0087] The user terminal device 400 in this application embodiment includes, but is not limited to, smartphones, tablets, and wearable electronic devices (such as smartwatches) with touch input functionality. Exemplary embodiments of the user terminal device 400 include, but are not limited to, devices equipped with… Portable electronic devices running Windows, Linux, or other operating systems. The user terminal device 400 described above can also be other portable electronic devices, such as laptops. It should also be understood that in some other embodiments, the user terminal device 400 may not be a portable electronic device, but rather a fixed-mount or desktop electronic device (e.g., a desktop computer).

[0088] Below, in conjunction with Figure 6 This paper will specifically introduce the solutions provided in the embodiments of this application for dealing with "ghost hands". Figure 6 The diagram shown is a flowchart of a method according to an embodiment of this application. The touch detection module of the user terminal device 400 performs the following... Figure 6 Steps S610 to S630 are shown to identify rows / columns of touch points where "ghost hands" exist.

[0089] S610 monitors input events at touch points on the touch panel.

[0090] Prior to S610, the user terminal device 400 could receive an input to trigger the execution of S610; this input could be a user input, such as the user terminal device 400 receiving a touch input or voice input (for example, the user clicks the detection button to instruct the user terminal device 400 to start detecting whether a "ghost hand" exists); the input could also be an instruction generated by a preset task on the user terminal device 400 when the task conditions are met (for example, the user terminal device 400 is preset to detect whether a "ghost hand" exists once a week).

[0091] S620 calculates the input event value of a row / column in a monitoring period based on the input events of all touch points in a row / column on the touch panel within a monitoring period.

[0092] For example, in S620, input events from touch points on the touch panel are collected at a preset frequency. The input event value of a touch point on the touch panel within a monitoring cycle is equal to the sum of the input event values ​​of the touch point acquired each time input event is collected within that monitoring cycle. The input event value of the top row / column of the touch panel within a monitoring cycle is equal to the sum of the input event values ​​of all touch points in the top row / column of the touch panel within that monitoring cycle.

[0093] Furthermore, in one implementation of S620, the input event value of the touch point is calculated based on the input type of the input event (e.g., tap, swipe, air gesture) each time an input event is collected.

[0094] Specifically, a base value B is set (e.g., 1.0). The input event value of a touch point is the product of its weight P and the base value B. The weight P is a fixed value determined based on the input type of the input event (e.g., tap: 0.8, swipe: 0.3, air gesture: 0.0). `i` represents the input event acquisition operation number within the current monitoring period, i = 0 to n, where n is the number of input event acquisition operations within one monitoring period. `j` represents the touch point number in the current row / column, j = 1 to m, where m is the number of touch points in the current row / column. During the i-th input event acquisition, the accumulated input event value of touch point j is:

[0095] Vl i,j =Vl i-1,j +B*P i,j (1)

[0096] The input event value of touch point j in the current row / column within a monitoring cycle is Vl, which is calculated when the input event is collected for the nth time. n,j The input event value R for the current row / column within a monitoring period is:

[0097] R = Vl n,1 +Vl n,2 +…Vl n,m-1 +Vl n,m (2)

[0098] Furthermore, in practical applications, different areas of the touch panel are clicked at varying frequencies when a user performs touch operations. For example, based on the interface design, the middle part of the touch screen (content display area) is clicked more frequently than the surrounding areas (border display area); the top (drop-down menu trigger area) and bottom (back button, main interface button, console button) are clicked more frequently than the left / right sides. This can lead to situations where, within a monitoring period, the input event values ​​of rows / columns with high user click frequency when no "ghost hand" occurs are the same as or similar to the input event values ​​of rows / columns with low user click frequency when a "ghost hand" occurs.

[0099] For example, suppose there is physical damage to row B41 of the touch panel, creating a "ghost hand" effect. Even if the user doesn't tap row B41, the touch points on row B41 will still output touch signals. Within monitoring period Z4, although the user didn't tap row B41, the output signal of row B41 shows that it was tapped 100 times due to the presence of the "ghost hand." Simultaneously, suppose there is no "ghost hand" effect on row B42, but the user taps row B42 consecutively within monitoring period Z4. Within monitoring period Z4, the output signal of row B42 shows that it was tapped 95 times. Thus, within monitoring period Z4, the input event values ​​for rows B41 and B42 are very similar, easily leading to incorrect judgments when using the same threshold to determine the presence of a "ghost hand."

[0100] To address the above situation, in one implementation of S620, a weight Q is assigned to a row / column based on the frequency of clicks (click frequency) in the actual application scenario (the higher the frequency of clicks, the lower the weight). The input event value R of the current row / column within a monitoring period is:

[0101] R = Q * (Vl) n,1 +Vl n,2 +…Vl n,m-1 +Vl n,m (3)

[0102] Furthermore, in one implementation of S620, the row / column weight Q is calculated based on the user's touch habits. Specifically, the initial value Q0 of the row / column weight Q is set to a fixed value (e.g., 1.0), and the initial input event value of touch point j is set to 0. During the i-th input event acquisition, the current input event value of touch point j is:

[0103] Vd i,j =(Vd i-1,j +B*P i ) / twenty four)

[0104] When the input event is collected for the i-th time, the current input event value of the row / column is:

[0105] R i =Q i-1 *(V i,0 +V i,1 +…+V i,m ) / m. (5)

[0106] For the i-th input event capture, we can calculate:

[0107] Q i =(Q i-1 +n*R i / (R1+R2+…+Rn )) / 2. (6)

[0108] The row / column weight Q within a monitoring period is Q. n .

[0109] Furthermore, in one implementation of S620, the row / column weights Q are also corrected based on the uniformity of the input event distribution in the row / column. Specifically, a distribution uniformity parameter Di is introduced, and the row / column weights Q are multiplied by Di to achieve the correction. Di depends on the current input event value Vd of the touch point in the row / column. i,j The larger the variance, the smaller Di is.

[0110] S630 determines whether a "ghost hand" exists in a row or column based on the input event value of the row or column.

[0111] For example, in one implementation of S630, when the input event value of a row / column in a monitoring cycle is greater than a preset threshold, it is determined that the row / column has a "ghost hand".

[0112] Figure 7 The image shown is a bar chart of input event values ​​according to an embodiment of this application. Figure 7 As shown, the horizontally arranged bar chart represents the row numbers (0 to N) of the touch panel's touch points. The height of the bar chart corresponds to the input event value of that row in one monitoring cycle. If the input event value of row (x) is higher than the threshold, then row (x) is determined to have a "ghost hand".

[0113] Figure 8 The diagram shown is a flowchart of a method according to an embodiment of this application. For a touch point in a certain row / column on the touch panel, the following steps are performed: Figure 8 The following steps are shown to determine if a "ghost hand" exists in the row / column:

[0114] S810: Clear monitoring data and start a new monitoring cycle;

[0115] S820 updates the input event values ​​of rows / columns based on the input events of the touch points;

[0116] S830, determines whether the monitoring cycle has been completed;

[0117] If not completed, return to S820;

[0118] If complete, execute S840;

[0119] S840 calculates the input event values ​​for rows / columns within a monitoring period;

[0120] S850 determines whether the input event value of a row / column within a monitoring period is greater than a preset threshold;

[0121] If the value is greater, execute S860;

[0122] S860, determine that a "ghost hand" exists in this row / column;

[0123] If it is less than or equal to, execute S870;

[0124] S860, determine that there is no "ghost hand" in this row / column.

[0125] Furthermore, considering that in certain sudden application scenarios (for example, when a user clicks the touch panel continuously and rapidly within a certain period of time), the user's touch input may also cause the input event value of a row / column within a monitoring cycle to exceed the preset threshold, in order to avoid misjudgment, in one implementation of S630, when the input event value of a row / column is greater than the preset threshold for N consecutive monitoring cycles, it is determined that there is a "ghost hand" in that row / column, where N is an integer greater than 1.

[0126] Furthermore, following S630, the input control system 400 also performs:

[0127] S640: When a row / column contains a "ghost hand" (input error), the input of that row / column is completely blocked to prevent the "ghost hand" from interfering with the user's normal input.

[0128] After S640, once rows or columns are blocked, users can be notified through methods including, but not limited to, dialog boxes, notifications, floating buttons, and prompts. Specifically, the display position of pop-up dialog boxes, floating buttons, etc., will dynamically change according to the rows or columns that need to be blocked.

[0129] Figure 9 The diagram shown is a schematic representation of a mobile phone display interface according to an embodiment of this application. Figure 9 As shown, after identifying the location of the "ghost hand" and blocking the corresponding row / column, the mobile phone outputs notification 901 to the user.

[0130] In another implementation, after S630, upon identifying a row or column with a "ghost hand" (illegible character), S640 may not be executed proactively. Instead, the user can be notified via methods including, but not limited to, dialog boxes, notifications, floating buttons, and prompts, allowing the user to confirm whether to proceed with the blocking operation. Specifically, the display position of the pop-up dialog box, floating button, etc., will dynamically adjust according to the rows or columns to be blocked.

[0131] Figure 10 The diagram shown is a schematic representation of a mobile phone display interface according to an embodiment of this application. Figure 10 As shown, after identifying the location of the "ghost hand", the mobile phone outputs a prompt box 1001 to the user.

[0132] After S640, users can also disable the detection of the block and unblock the corresponding row or column through menus, dialog boxes, floating buttons, etc.

[0133] Figure 11 The diagram shown is a schematic representation of a mobile phone display interface according to an embodiment of this application. Figure 11 As shown, users can enable "Auto Touch Detection" to set the phone to automatically detect "ghost hands" at preset intervals. Users can also set the "Touch Detection Time" to specify the time for automatic "ghost hand" detection. Users can configure the phone's actions when "ghost hands" are detected through "Block Settings." Users can set whether to output notifications after automatically blocking touch input through "Block Notifications." Users can cancel all touch input blocking by pressing the "Unblock" button. Users can immediately begin detecting "ghost hands" by pressing the "Touch Detection" button.

[0134] Furthermore, when multiple rows / columns are muted, you can operate using the volume / power buttons. Alternatively, you can operate using air gestures.

[0135] It is understood that some or all of the steps or operations in the above embodiments are merely examples, and other operations or variations thereof can be performed in the embodiments of this application. Furthermore, the steps may be performed in different orders as presented in the above embodiments, and it is not necessary to perform all the operations in the above embodiments.

[0136] Furthermore, in the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program a digital device themselves to "integrate" it onto a PLD, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog are the most commonly used. Those skilled in the art should understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0137] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0138] In the description of the embodiments of this application, for the sake of convenience, the device is described by dividing it into various modules / units according to its functions. The division of each module / unit is only a logical functional division. When implementing the embodiments of this application, the functions of each module / unit can be implemented in one or more software and / or hardware.

[0139] Specifically, the apparatus proposed in this application can be fully or partially integrated onto a single physical entity, or physically separated. These modules can be implemented entirely in software via processing element calls; entirely in hardware; or partially in software via processing element calls and partially in hardware. For example, the detection module can be a separate processing element or integrated into a chip in the electronic device. The implementation of other modules is similar. Furthermore, these modules can be fully or partially integrated together, or implemented independently. During implementation, each step of the above method or each of the above modules can be completed through integrated logic circuits in the hardware of the processor element or through software instructions.

[0140] For example, these modules can be one or more integrated circuits configured to implement the above methods, such as one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs). Alternatively, these modules can be integrated together as a system-on-a-chip (SOC).

[0141] Based on the above description, according to an embodiment of this application, a monitoring device is also proposed. This device can be applied to a user terminal device 400. Figure 12 The diagram shown is a structural block diagram of a device according to an embodiment of this application. Figure 12 As shown, the device includes:

[0142] The input event acquisition module 1210 is used to acquire input events from touch points on the touch panel.

[0143] The calculation module 1220 is used to calculate the input event value of a row / column in a monitoring period based on the input events of all touch points in a row / column on the touch panel in a monitoring period.

[0144] The identification module 1230 is used to determine whether a row or column has a "ghost hand" based on the input event value of the row / column within a monitoring period;

[0145] The input masking module 1240 is used to mask the input of a row or column as a whole when a "ghost hand" is present, thereby preventing the "ghost hand" from interfering with the user's normal input.

[0146] An embodiment of this application also proposes a user terminal device. Figure 13 This is a schematic diagram of a user terminal device provided in this application. For example, the user terminal device 1300 includes at least one processor, a memory, and a touch panel. The coupling between the processor, memory, and touch panel in this embodiment can be a communication connection, an electrical connection, or other forms. Specifically, the memory is used to store program instructions. The touch panel is used to generate touch events. The processor is used to call the program instructions stored in the memory, causing the user terminal device to execute the steps in the monitoring method provided in this embodiment. It should be understood that this user terminal device can be used to implement the monitoring method provided in this embodiment; related features can be referred to above and will not be repeated here.

[0147] This application provides a computer program product containing instructions that, when run on a user terminal device, cause the user terminal device to execute the steps in the monitoring method provided in the embodiments of this application.

[0148] This application provides a computer-readable storage medium including instructions that, when executed on a user terminal device, cause the user terminal device to perform the steps in the monitoring method provided in the embodiments of this application.

[0149] For example, Figure 14 A schematic diagram of the hardware structure of a user terminal device 1300 provided in an embodiment of this application is shown. Figure 14 As shown, the user terminal device 1300 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0150] It is understood that the structure illustrated in the embodiments of this application does not constitute a specific limitation on the user terminal device 1300. In other embodiments of this application, the user terminal device 1300 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0151] The processor 110 of the user terminal device 1300 can be a device-on-a-chip (SoC), which may include a central processing unit (CPU) and may further include other types of processors. For example, the processor 110 may be a PWM control chip.

[0152] The processor 110 may include, for example, a CPU, DSP, microcontroller, or digital signal processor, and may also include a GPU, embedded neural network processing units (NPU), and image signal processor (ISP). The processor 110 may also include necessary hardware accelerators or logic processing hardware circuitry, such as an ASIC, or one or more integrated circuits for controlling the execution of the program in this application. Furthermore, the processor 110 may have the function of operating one or more software programs, which may be stored in a storage medium.

[0153] Processor 110 may include one or more processing units. For example, processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU). Different processing units may be independent components or integrated into one or more processors. In some embodiments, user terminal device 1300 may also include one or more processors 110. The controller can generate operation control signals based on instruction opcodes and timing signals to control instruction fetching and execution.

[0154] In some embodiments, the processor 110 may include one or more interfaces. These interfaces may include an inter-integrated circuit (I2C) interface, an integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a SIM card interface, and / or a USB interface, etc. The USB interface 130 is a USB standard-compliant interface, specifically a Mini USB interface, a Micro USB interface, a USB Type-C interface, etc. The USB interface 130 can be used to connect a charger to charge the user terminal device 1300, and can also be used for data transfer between the user terminal device 1300 and peripheral devices.

[0155] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this application are merely illustrative and do not constitute a structural limitation on the user terminal device 1300. In other embodiments of this application, the user terminal device 1300 may also adopt different interface connection methods or a combination of multiple interface connection methods as described in the above embodiments.

[0156] The external storage interface 120 can be used to connect an external storage card, such as a Micro SD card, to expand the storage capacity of the user terminal device 1300. The external storage card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external storage card.

[0157] The internal memory 121 of the user terminal device 1300 can be used to store one or more computer programs, which include instructions. The processor 110 can execute the instructions stored in the internal memory 121, thereby causing the user terminal device 1300 to perform the methods provided in some embodiments of this application, as well as various applications and data processing. The internal memory 121 may include a code storage area and a data storage area. The code storage area may store the operating system. The data storage area may store data created during the use of the user terminal device 1300. Furthermore, the internal memory 121 may include high-speed random access memory and may also include non-volatile memory, such as one or more disk storage components, flash memory components, universal flash storage (UFS), etc.

[0158] The internal memory 121 may be a read-only memory (ROM), other types of static storage devices that can store static information and instructions, random access memory (RAM), or other types of dynamic storage devices that can store information and instructions. It may also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices. Alternatively, it may be any computer-readable medium capable of carrying or storing desired program code in the form of instructions or data structures that can be accessed by a computer.

[0159] Processor 110 and internal memory 121 can be combined into a single processing device, or more commonly, they are independent components. Processor 110 is used to execute program code stored in internal memory 121 to implement the methods described in the embodiments of this application. In specific implementations, internal memory 121 can also be integrated into the processor, or it can be independent of the processor.

[0160] The charging management module 140 receives charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 receives charging input from the wired charger via a USB interface 130. In some wireless charging embodiments, the charging module 140 receives wireless charging input via the wireless charging coil of the user terminal device 1300. While charging the battery 142, the charging management module 140 can also supply power to the user terminal device 1300 via the power management module 141.

[0161] The power management module 141 connects the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, and supplies power to the processor 110, internal memory 121, external memory interface 120, mobile communication module 150, and wireless communication module 160. The power management module 141 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance). In some other embodiments, the power management module 141 may also be located within the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be located in the same device.

[0162] The wireless communication function of the user terminal equipment 1300 can be implemented through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor, and baseband processor.

[0163] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in user terminal equipment 1300 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with a tuning switch.

[0164] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the user terminal device 1300. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110.

[0165] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through an audio device (not limited to speaker 170A, receiver 170B, etc.) or displays images or videos through the display screen 194. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 110 and may be housed in the same device as the mobile communication module 150 or other functional modules.

[0166] The wireless communication module 160 can provide solutions for wireless communication applications on the user terminal device 1300, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0167] In some embodiments, antenna 1 of user terminal equipment 1300 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling user terminal equipment 1300 to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc. The GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

[0168] User terminal device 1300 can achieve shooting function through ISP, camera 193, video codec, GPU, display 194 and application processor.

[0169] User terminal device 1300 can implement audio functions, such as music playback and recording, through audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.

[0170] User terminal device 1300 can realize touch input through display screen 194, touch sensor 180K, and processor 110. For example, touch sensor 180K and display screen 194 are integrated into a touch screen. The user's click operation on the touch screen is collected by touch sensor 180K as a touch signal. The touch signal is collected and converted by sensor module 180 and then transmitted to processor 110. Processor 110 identifies and analyzes the touch signal to understand the user's touch operation behavior.

[0171] In one embodiment, Figure 4 The touch panel 401 shown can be implemented by the touch sensor 180K shown in Figure 5, or by the processing chip in the sensor module 180 combined with the touch sensor 180K. The touch detection module can be implemented based on the sensor module 180, or by the processor 100, or by hardware modules other than the sensor module 180 and the processor 100.

[0172] Those skilled in the art will clearly understand that the embodiments of this application can be implemented in hardware, or in a hardware and software manner. When implemented in hardware and software, the above-mentioned functions can be stored in a computer-readable medium. Based on this understanding, the technical solutions of the embodiments of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as flash memory, portable hard disk, read-only memory, random access memory, magnetic disk, or optical disk.

[0173] The above description is merely a specific implementation of the embodiments of this application, but the protection scope of the embodiments of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the embodiments of this application should be covered within the protection scope of the embodiments of this application. Therefore, the protection scope of the embodiments of this application should be determined by the protection scope of the claims.

Claims

1. An input monitoring method characterized by, The method comprises: monitoring input events of touch points on a touch panel; confirming row weight / column weight of a row / column, and correcting the row weight / column weight according to uniformity of distribution of input events in the row / column, wherein the row weight / column weight is related to frequency of user clicking; calculating input event value of the row / column according to input events of all touch points in the row / column on the touch panel and the row weight / column weight of the row / column, wherein; determining whether there is a touch event generated in the row / column according to the input event value.

2. The method of claim 1, wherein, The calculating of the input event value of the row / column according to input events of all touch points in the row / column on the touch panel comprises: calculating input event value of the row / column in a monitoring period according to all input events of all touch points in the row / column on the touch panel in the monitoring period.

3. The method of claim 2, wherein, The calculating of the input event value of the row / column in the monitoring period according to all input events of all touch points in the row / column on the touch panel in the monitoring period comprises: calculating input event value of the touch point in the monitoring period, wherein the input event value of the touch point in the monitoring period is equal to accumulation of input event value of the touch point obtained each time input event is collected in the monitoring period.

4. The method of claim 3, wherein, The calculating of the input event value of the touch point in the monitoring period comprises: confirming point weight corresponding to input event of the touch point according to input type of the input event of the touch point; calculating input event value of the touch point according to the point weight corresponding to the input event of the touch point.

5. The method of claim 1, wherein, The confirming of the row weight / column weight of the row / column comprises: calculating the row weight / column weight according to touch habit of the user.

6. The method according to any one of claims 1-5, characterized in that, The determining of whether there is a touch event generated in the row / column according to the input event value comprises: when input event value of the row / column in a monitoring period is greater than a preset threshold, determining that there is a touch event generated in the row / column.

7. The method according to any one of claims 1-5, characterized in that, The determining of whether there is a touch event generated in the row / column according to the input event value comprises: when input event value of the row / column in N continuous monitoring periods is greater than a preset threshold, determining that there is a touch event generated in the row / column, wherein N is an integer greater than 1.

8. The method according to any one of claims 1-5, characterized in that, The method further comprises: when there is a touch event generated in the row / column, shielding input of the row / column.

9. An input monitoring device, characterized by The method comprises: an input event obtaining module, configured to obtain input events of touch points on a touch panel; a calculating module, configured to confirm row weight / column weight of a row / column, and correct the row weight / column weight according to uniformity of distribution of input events in the row / column, wherein the row weight / column weight is related to frequency of user clicking; and calculate input event value of the row / column according to input events of all touch points in the row / column on the touch panel and the row weight / column weight of the row / column. a recognition module configured to determine, based on the input event value, whether a spurious touch event exists in the row / column.

10. An electronic device, comprising: The electronic device comprises a memory for storing computer program instructions and a processor for executing the program instructions, wherein when the computer program instructions are executed by the processor, the electronic device is triggered to perform the method steps of any one of claims 1-8.

11. A computer readable storage medium, characterized in that, The computer readable storage medium stores a computer program, which, when running on a computer, causes the computer to perform the method of any one of claims 1-8.

Images