Adaptive noise reduction in touch screen devices

CN122963371APending Publication Date: 2026-10-23STMICROELECTRONICS INT NV
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202610521194.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2025-04-22
Filing Date
2026-04-20
Publication Date
2026-10-23

AI Technical Summary

Technical Problem

当噪声水平升高时,可能影响触摸检测精度,可能导致不准确的触摸或错误的触摸检测

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122963371A_ABST
    Figure CN122963371A_ABST
Patent Text Reader

Abstract

The present disclosure relates to adaptive noise reduction in a touch screen device. A method for operating a touch screen device. The method includes performing a noise monitoring scan of the touch screen device, collecting noise data from the noise monitoring scan, determining whether the noise data is greater than a first noise threshold and less than a second noise threshold, and if so, determining whether the noise data is greater than the second noise threshold, the second noise threshold being greater than the first noise threshold, entering a first noise mode to apply a first noise filter in response to the noise data being greater than the first noise threshold and less than the second noise threshold, and entering a second noise mode to apply a second noise filter in response to the noise data being greater than the second noise threshold.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention generally relates to electronic devices, and in certain embodiments, to systems and methods for reducing noise interference in touchscreen devices. Background Technology

[0002] Touchscreens are commonly used in electronic devices such as tablets, smartphones, wearable devices, and computers. Touchscreen devices typically include sensing nodes capable of detecting touch input from a user's finger or stylus. Touch input can be detected by measuring changes in capacitance at the sensing node. These changes in capacitance indicate the presence and location of touch input on the touchscreen. Besides touch input, noise can cause changes in capacitance at the sensing node. Changes in capacitance at the sensing node caused by noise may be mistaken for touch input.

[0003] Noise from various sources such as power supplies, telephone chargers, display components, and other electronic devices can generate electromagnetic noise, which can interfere with accurate touch detection. Increased noise levels can affect touch detection accuracy, potentially leading to inaccurate or erroneous touch detection. Touch controllers can employ various noise filtering techniques to provide reliable touch detection in noisy environments. Summary of the Invention

[0004] One general aspect includes a method of operating a touchscreen device. The method includes: performing a noise monitoring scan on the touchscreen device; collecting noise data from the noise monitoring scan; determining whether the noise data is greater than a first noise threshold and less than a second noise threshold, and if so, determining whether the noise data is greater than the second noise threshold, the second noise threshold being greater than the first noise threshold; entering a first noise mode to apply a first noise filter in response to the noise data being greater than the first noise threshold and less than the second noise threshold; and entering a second noise mode to apply a second noise filter in response to the noise data being greater than the second noise threshold.

[0005] Another general aspect includes a method of operating a touchscreen device. The method includes: performing a first noise monitoring scan on the touchscreen device; collecting first noise data from the first noise monitoring scan; determining that the first noise data is greater than a first noise threshold and less than a second noise threshold, the second noise threshold being greater than the first noise threshold; entering a first noise mode in response to the first noise data being greater than the first noise threshold and less than the second noise threshold; performing a second noise monitoring scan on the touchscreen device; collecting second noise data from the second noise monitoring scan; determining that the second noise data is greater than a second noise threshold; and entering a second noise mode in response to the second noise data exceeding the second noise threshold, the second noise mode including performing two or more mutual scans on the same portion of a frame.

[0006] Another general aspect includes a device comprising: a touchscreen and a touch controller. The touch controller is configured to: perform a noise monitoring scan on the touchscreen; collect noise data from the noise monitoring scan; determine whether the noise data is greater than a first noise threshold and less than a second noise threshold, or determine whether the noise data is greater than the second noise threshold, the second noise threshold being greater than the first noise threshold; operate in a first noise mode to apply a first noise filter in response to the noise data being greater than the first noise threshold and less than the second noise threshold; and operate in a second noise mode to apply a second noise filter in response to the noise data being greater than the second noise threshold.

[0007] Other embodiments and variations are described herein. Attached Figure Description

[0008] To gain a more complete understanding of the invention and its advantages, reference is now made to the following description in conjunction with the accompanying drawings, wherein:

[0009] Figure 1A - Figure 1B A schematic diagram of components of an electronic device according to an embodiment of this application is shown.

[0010] Figure 2 A touch detection process according to an embodiment of this application is illustrated.

[0011] Figure 3 Noise data from a noise monitoring scan is shown according to an embodiment of this application.

[0012] Figure 4 A noise analysis process according to an embodiment of this application is illustrated.

[0013] Figure 5 An exemplary graph illustrating noise and touch signals according to an embodiment of this application is shown.

[0014] Figure 6 A flowchart illustrating adaptive noise management in an electronic device according to an embodiment of this application is shown.

[0015] Figure 7 A flowchart illustrating an embodiment of this application for determining a mutual scanning frequency for touch detection is shown.

[0016] Figure 8 A flowchart illustrating adaptive noise management in an electronic device according to an embodiment of this application is shown.

[0017] Figure 9A and Figure 9B An intensity bitmap is shown according to an embodiment of this application.

[0018] Figure 10A and Figure 10B The output signal according to an embodiment of this application is shown.

[0019] Figure 11 A flowchart illustrating adaptive noise management in an electronic device according to an embodiment of this application is shown. Detailed Implementation

[0020] Touchscreen devices become susceptible to noise interference when unwanted electromagnetic signals interfere with their normal function. Noise interference can originate from a variety of internal and external sources, including, for example, connections to telephone chargers, images on the display, nearby power cords, radio signals, fluorescent bulbs, or other electronic devices. Noise interference can cause touch input processing problems such as mis-received and ghosting touches.

[0021] Known methods for handling noise interference in touchscreen devices typically employ basic filtering techniques. However, conventional filtering techniques are insufficient for extremely noisy environments. For example, a touch controller operating at a fixed scan frequency may experience severe interference when noise sources generate interference at or near frequencies higher than the fixed scan frequency. Therefore, even with basic filtering applied, noise interference can still affect touch performance.

[0022] Furthermore, existing methods typically implement the same noise countermeasures regardless of the severity of the interference, which may affect touch response more than necessary under moderate noise conditions. In cases where less aggressive noise handling is sufficient, a "one-size-fits-all" approach may unnecessarily impact touch response. The lack of adaptation based on actual noise severity can lead to suboptimal trade-offs between noise immunity and touch performance.

[0023] Embodiments of this disclosure provide a touchscreen device with enhanced capabilities to characterize noise conditions. Methods for maintaining touch detection reliability while managing latency and power consumption tradeoffs based on actual noise severity can help address the challenges of characterizing noise conditions.

[0024] Embodiments of this disclosure can enhance touch input processing when noise is detected in a touchscreen device. Embodiments of this disclosure can filter out noise to improve touch response in a touchscreen device. According to various embodiments, techniques and systems for detecting noise and processing touch input on a touchscreen are provided. Various embodiments of this disclosure provide techniques for detecting various noise levels on a touchscreen and applying filters to reduce the impact of noise on touch input processing.

[0025] Figure 1A - Figure 1B A schematic diagram of components of an electronic device according to an embodiment of this application is shown.

[0026] refer to Figure 1A The electronic device 100 may include a touch screen 102, a touch controller 104, and a system-on-a-chip 106. The electronic device 100 may be a smartphone, a GPS device, a tablet computer, a mobile media player, a laptop computer, a gaming system, a personal computer, a wearable device, or any other electronic device that can utilize a touch-sensitive display.

[0027] While aspects of the invention have been described primarily in the context of touchscreen displays in mobile devices and smartphones, it should be understood that these aspects can also be applied to other touch-enabled electronic devices and systems. Specifically, aspects of the invention can be similarly applied to tablet computers, laptop computers, monitors, self-service kiosks, point-of-sale terminals, automotive displays, industrial control panels, gaming devices, and other touch interface implementations.

[0028] Touchscreen 102 may be an organic light-emitting diode (OLED) display, an LED display, or any other type of display. Touchscreen 102 may include a plurality of pixels in a display layer configured to display images. As will be understood by those skilled in the art, the display layer of touchscreen 102 may include a plurality of pixels located at each intersection between data lines and scan lines. Multiple scan lines may extend through rows of touchscreen 102, and data lines may extend through columns of touchscreen 102, in a matrix-like manner. Touchscreen 102 may also include a touch-sensing layer configured to detect touch input performed on touchscreen 102. This will be described in more detail below.

[0029] Touch controller 104 can perform various methods relating to the display. In various embodiments, touch controller 104 can be a processor that analyzes information and executes, for example, a series of executable scripts stored in memory 110. In one or more embodiments, the processor may comprise an application-specific integrated circuit (ASIC) device, a central processing unit (CPU), or any other processing unit known in the art. In various embodiments, touch controller 104 may include multiple separate computing units, such as cores integrated within a processor, or different separate processing chips. Further details regarding how touch controller 104 takes into account water on touchscreen 102 are provided below.

[0030] In various embodiments, the touch controller 104 may include an analog block 108 and a digital block 112. The analog block 108 may include multiple analog circuits configured to measure the capacitance on the touchscreen 102 and convert it into digital values. The digital block 112 may include various digital logic circuits, such as a DAC or a digital control system, configured to obtain digital touch data from the analog block 108, process the digital touch data, and store it in the memory 110.

[0031] Memory 110 can be configured to store data and instructions for touch controller 104, and may include various programs to be executed by touch controller 104. Memory 110 may include a non-transitory computer-readable medium storing instructions to be executed by touch controller 104. Memory 110 may include volatile and non-volatile components to support temporary data storage during the processing and long-term storage of system software and calibration data. Volatile memory (typically RAM) provides fast access to temporary storage of sensor data, intermediate results, and current state information of the gesture recognition system. Non-volatile memory, such as flash memory or EEPROM, can store information such as device firmware, gesture recognition algorithms, and sensor calibration data.

[0032] In various embodiments, the system-on-chip 106 may also be referred to as an application processor and may include processors, interfaces, circuitry, etc., configured to direct input and output data streams to the touchscreen 102 and the associated touch controller 104. The system-on-chip 106 may be configured to receive touch event data from the touch controller 104 and interpret the touch event data based on the user interface or application displayed on the touchscreen 102.

[0033] Additionally, the touch controller 104 can be configured to detect touch input via the touchscreen 102. In other words, the touch controller 104 can be configured to send touch drive signals (TDS) to the touchscreen, receive touch sensing signals (TSS) as a return from the touchscreen, process the TSS to determine touch coordinates, and report them to the on-chip system 106. Then, based on the intensity data collected from the scan, the touchscreen can be used by the touch controller 104 to determine touch coordinates and report them to the on-chip system 106. The on-chip system 106 can then provide output to the touchscreen 102 based on the reported touch coordinates.

[0034] Advantageously, as will be described in more detail below, embodiments of this application disclose a touchscreen device configured to record and analyze multiple touch inputs across multiple frames based on merging criteria, and a method for determining whether to merge the touch inputs for reporting. In other words, multiple touch inputs can be merged and reported as a single touch input, or separated and reported as individual touch inputs.

[0035] Figure 1B A schematic diagram of a touchscreen 102 is shown. In various embodiments, the touchscreen 102 may include a touch sensing layer 116 and a display layer 118. The touch sensing layer 116 and the display layer 118 may be located on the front of the electronic device 100. The touch sensing layer 116 is configured to detect touch input performed on the touchscreen 102.

[0036] The touch sensing layer 116 includes a plurality of TX channels (e.g., driving channels) and RX channels (e.g., sensing channels) arranged in rows and columns across the touchscreen 102. The TX and RX channels form the touch sensing layer. The TX and RX channels may span the entire touchscreen 102 in a grid-like manner operable by a touch controller. In various embodiments, the TX channels may be formed as rows across the touchscreen, and the RX channels 124 may be formed as columns across the touchscreen 102. In other embodiments, the RX channels 124 may be formed in rows on the touchscreen 102, and the TX channels 122 may be formed in columns on the touchscreen 102. In some embodiments, the TX channels 122 and RX channels 124 may overlap.

[0037] The TX and RX channels can be formed by electrically coupling the touchscreen 102 to electrode rows (e.g., TX or RX electrodes) and electrode columns (e.g., TX or RX electrodes) spanning the entire touchscreen 102. In various embodiments, the TX and RX channels have measurable mutual capacitance at their intersections. In some embodiments, the TX and RX channels may have self-capacitance that can be measured relative to ground level.

[0038] Touch controller 104 is coupled to the TX and RX channels forming touch sensing layer 116. TX channel 122 and RX channel 124 create a cross matrix that acts as individual touch sensors. Touch controller 104 sends electrical signals through the TX channels and measures capacitance changes at each intersection through the RX channels. Touch controller detects and locates touch events by analyzing changes in capacitance at touchscreen 102. Touch events can include finger touches, stylus or pen touches, or any contact with touchscreen 102 that changes capacitance in touch sensing layer 116. For convenience, these contacts are referred to herein as touch inputs. Touch controller 104 can process the raw data, determine noise levels, apply noise filters corresponding to the noise levels, and interpret touch inputs, converting them into coordinates and gestures that the device's operating system can understand. This integration between the touch controller and the touch sensing layer enables accurate and responsive touch detection.

[0039] Figure 2 A touch detection process according to an embodiment of this application is illustrated. Touch detection process 200 shows a scan sequence 202 and a processing block 232. (The last sentence appears to be incomplete and possibly refers to a different application.) Figure 1A and Figure 1B describe Figure 2 However, it should be understood that these operations can be performed using other hardware.

[0040] In one or more embodiments, the touch controller 104 performs multiple scanning operations to detect and verify touch input on the electronic device 100. The touch controller 104 executes a scan sequence 202, which includes turning on an analog front-end (AFE) 212, performing self-sensing detection 214, performing self-sensing scans 216, 218, performing a noise monitoring scan 220, and performing a mutual scan 222 before powering off the AFE 224. The scan sequence 202 can be performed for each frame to mitigate noise interference and perform touch detection. The scan sequence 202 can be configured to balance factors such as power consumption, the settling time of analog circuitry, and frame timing requirements.

[0041] Each scan sequence 202 begins with the analog front-end (AFE) circuitry 212 being powered on. In various embodiments, AFE power-on 212 represents the initial phase of each touch scan frame, where the analog circuitry required for touch sensing is powered on and ready for operation. The AFE includes analog circuitry for driving signals to touch sensing electrodes and measuring received touch signals. During AFE power-on 212, various analog components are activated in a controlled sequence. In one or more embodiments, the analog components may include a drive signal generator, a sensing amplifier, an analog filter, and an analog-to-digital converter required for touch detection. The AFE power-on sequence ensures proper initialization of the analog circuitry to achieve stable operating conditions before the start of touch scan operation.

[0042] In one or more embodiments, AFE activation 212 occurs at the beginning of each frame before self-sensing and mutual sensing operations can commence. In various embodiments, the timing of the AFE activation is coordinated with the frame rate 230 to maintain a consistent scan interval. For example, at a 120Hz frame rate, the AFE activation sequence is initiated every 8.3 milliseconds to begin a new scan frame. In other embodiments, the timing of the AFE activation can be adjusted to collect multiple data measurements that may vary the frame rate 230. For example, the frame rate 230 may be adjusted from 120Hz to 90Hz, changing the duration of the AFE activation sequence from 8.3ms to 11.1ms to collect additional data measurements for the frame.

[0043] After AFE is turned on 212, a self-sensing operation can be performed. In various embodiments, a self-sensing operation refers to a sequence of scanning steps performed by the touch controller to detect touch input using self-capacitance measurement. In one or more embodiments, the self-sensing operation includes initiating self-sensing detection 214 (SS Det), performing a self-sensing scan 216 on the driving channel (SS TCH TX), and performing a self-sensing scan 218 on the sensing channel (SS TCH RX). The order of these operations need not be as shown in the figure.

[0044] In one or more embodiments, self-sensing detection 214 initiates a self-sensing sequence by preparing touch controller 104 to measure changes in the self-capacitance of each electrode. In various embodiments, self-sensing detection 214 includes analog circuitry and digital control logic prepared for self-capacitance measurement. Self-sensing detection 214 may also include setting measurement parameters and a reference level for identifying potential touch activity.

[0045] In one or more embodiments, a self-sensing scan 216 on the drive channel includes driving a signal to each drive channel to perform a self-capacitance measurement between the drive electrode and ground. Similarly, a self-sensing scan on the sensing channel 218 includes driving a signal to each sensing channel to perform a self-capacitance measurement between the sensing electrode and ground. Self-capacitance is the capacitance between a single conductor and ground. In the touch sensing layer 116, the self-capacitance of a drive channel or sensing channel can be measured independently of other drive and sensing channels. The touch controller 104 can measure changes in the self-capacitance of each drive or sensing channel. When a touch event occurs, the change in the self-capacitance of the corresponding channel enables the detection of the touch location.

[0046] In one or more embodiments, self-sensing operation can supplement mutual scanning by providing additional touch detection data using different measurement techniques. The combination of self-sensing and mutual scanning measurements can help improve overall touch detection reliability, especially in challenging noisy environments.

[0047] Following self-sensing scans 216 and 218, a noise monitoring scan 220 (i.e., MS MRN) can be performed. The noise monitoring scan 220 detects noise data (MS MRN) on the touchscreen 102. During the noise monitoring scan 220, the touch controller can set all drive channels (i.e., TX channels) to a high-impedance state or ground them, thereby silencing the active touch sensing elements. In this state, the sensing channels (i.e., RX channels) remain active but only "listen" to the environment. Any signal detected on the sensing channels can be classified as noise, which can originate from various sources such as images on the display, power supply, nearby electronic devices, or chargers and USB connections.

[0048] In one or more embodiments, noise monitoring scans 220a, 220b, 220c can be performed for each frame at multiple different frequencies Freq0, Freq1, Freq2. For example, different frequencies Freq0, Freq1, Freq2 can be performed at 333kHz, 308kHz, and 271kHz, respectively. Multi-frequency scanning allows the touch controller 104 to analyze noise characteristics at different operating frequencies. Although the example shows three different frequencies, it should be understood that two or more frequencies can be scanned.

[0049] In various embodiments, when the noise level is severe, the noise monitoring scan frequency can be adjusted to avoid frequencies that may experience severe interference. For example, if the noise level is severe at noise monitoring scan frequencies of 333 kHz, 308 kHz, and 271 kHz, the noise monitoring scan frequency can be adjusted to 320 kHz, 295 kHz, and 258 kHz for subsequent noise monitoring scans.

[0050] Noise data can be collected for each of the different frequencies Freq0, Freq1, and Freq2. In one or more embodiments, the touch controller 104 can create a noise distribution of the noise data for each frame at each noise monitoring frequency. The noise data may include noise intensity representing the amplitude and frequency characteristics of the noise on each sensing channel. Higher noise intensity values ​​may indicate greater noise interference. The noise distribution can be stored by the touch controller 104 for analysis, for example, as follows: Figure 3 As stated above.

[0051] Following noise monitoring scan 220, mutual scan 222 (MS screen) can be performed. Mutual scan can be used to collect intensity data on electronic device 100. Mutual scan achieves touch detection by measuring changes in capacitive coupling between the TX and RX electrodes across the entire touch sensing layer 116. When a finger approaches touchscreen 102, the electric field around the sensing node is affected, reducing the coupling capacitance at the affected sensing node, which can be used to determine the location or coordinates of the touch input. Although mutual scan 222 is typically performed after noise monitoring scan 220, it should be understood that the order can be reversed.

[0052] In one or more embodiments, mutual scanning includes sequentially driving drive channels to scan the touch sensing layer 116 while the sensing channels simultaneously measure signals to collect intensity data measurements in parallel. The touch controller 104 may provide transmission signals of a specific frequency to the drive channels on the touch sensing layer, while the sensing channels receive signals coupled through sensing nodes formed at sensing nodes. Intensity data measurements can indicate the degree of coupling at each sensing node and indicate the presence of touch input. Intensity data measurements can be used to create a two-dimensional intensity bitmap of touch activity.

[0053] In one or more embodiments, mutual scanning 222 can be configured with specific scanning and processing configurations to detect touch inputs that can be adapted based on operating modes and noise conditions. Touch controller 104 can determine the optimal frequency for performing mutual scanning 222 to minimize noise interference while collecting intensity data. For example, noise monitoring scans 220a, 220b, 220c can be performed at multiple frequencies Freq0, Freq1, Freq2, and the frequencies used for noise monitoring scans 220a, 220b, 220c with the lowest noise data can be set as the frequencies used for mutual scanning 222. When the mutual scanning frequency is set to the noise monitoring scan frequency with the lowest noise data, ghosting or inaccurate touches on touchscreen 102 can be reduced. In various embodiments, touch controller 104 can analyze noise data from noise monitoring scan 220 and intensity data measurements from mutual scanning 222 across multiple frames to distinguish continuous touch events from transient noise spikes. In one or more embodiments, mutual scanning 222 may be performed multiple times, such as two or more times, on the same portion of a frame to collect multiple intensity measurements within each frame period. The average of the multiple intensity data measurements can be used to determine the presence of touch input.

[0054] After mutual scanning 222, scan sequence 202 ends by shutting down analog front-end (AFE) circuitry 224 (i.e., turning off AFE power). The AFE can be turned off at the end of each frame to save power until the next frame begins. When scan sequence 202 is complete, touch controller 104 begins processing 232 the noise and intensity data measurements collected from the previous scan sequence 202. When processing 232 for the previous scan sequence 202 is complete, the coordinates of the touch input on touchscreen 102 can be reported to system-on-chip 106 at a set reporting rate 234.

[0055] In one or more embodiments, while the touch controller 104 is processing the previous scan sequence 202, the touch controller 104 can execute the next scan sequence 202. Touch input can be reported to the on-chip system 106 simultaneously with the execution of the next scan sequence 202 and while processing the next scan sequence 232. The touch detection process 200 can be repeated continuously for each subsequent frame.

[0056] The touch detection process 200 can be used to detect the severity of noise interference, apply appropriate noise reduction measures based on the severity, and perform touch detection based on the applied noise reduction measures. The touch detection process 200 (e.g., the scan frequency in the scan sequence 202) can be adapted to eliminate noise interference detected in the touch detection.

[0057] Figure 3Noise data from a noise monitoring scan is shown according to an embodiment of this application. The description will be taken in conjunction with the accompanying drawings. Figure 3 .

[0058] In one or more embodiments, the noise monitoring scan 220 can be performed on each frame at multiple different frequencies Freq0, Freq1, Freq2, such as Figure 2 The noise monitoring scan 220 can detect noise data for each RX channel (i.e., the sensing channel) at each of multiple frequencies Freq0, Freq1, and Freq2 across multiple frames. For example, each noise monitoring scan 220 collects noise lines for the corresponding frequencies Freq0, Freq1, and Freq2 for each frame. Each line or row of noise data includes noise data for M sensing channels. For example, frame #1 collects a line of noise data D0x1, D0x2, D0x3, ..., D0xM from sensing channels Rx1, Rx2, Rx3, ..., RxM in noise monitoring scan 220a of Freq0; frame #1 collects a line of noise data D1x1, D1x2, D1x3, ..., D1xM from RX channels Rx1, Rx2, Rx3, ..., RxM in noise monitoring scan 220b of Freq1; and frame #1 collects a line of noise data D2x1, D2x2, D2x3, ..., D2xM from RX channels Rx1, Rx2, Rx3, ..., RxM in noise monitoring scan 220c of Freq2.

[0059] In one or more embodiments, the touch controller 104 may store noise data in memory 110. In one or more embodiments, noise data collected from noise monitoring scan 220 may be stored in a circular buffer 221. The circular buffer 221 organizes the noise data by the noise monitoring scan frequency and samples of historical noise data measurements over several frames or several sensing channels. When noise data is collected from a new frame, the noise data may replace the oldest noise data in the circular buffer 221, and a scrolling window of N frames or samples of historical noise measurements is maintained for each noise monitoring scan frequency and sensing channel combination.

[0060] refer to Figure 3For each frame, noise monitoring scan 220 is performed at three different noise monitoring scan frequencies Freq0, Freq1, and Freq2. Noise monitoring scan 220 collects noise data from each frame at each noise monitoring scan frequency Freq0, Freq1, and Freq2. Each cell in the circular buffer 221 stores noise data corresponding to the noise monitoring scan frequency, frame, and sensing channel. For example, in the circular buffer 221, D001 represents noise data corresponding to noise monitoring scan frequency Freq0, frame #1, and sensing channel Rx1, and D112 represents noise data corresponding to noise monitoring frequency Freq1, frame #2, and sensing channel Rx2. Each noise data line can be stored frame-by-frame in the circular buffer 221 for each noise monitoring scan frequency. For example, the first data line stored in the circular buffer 221 corresponds to the noise monitoring scan frequency Freq0 of frame #1, the second data line stored corresponds to the noise monitoring scan frequency Freq0 of frame #2, and so on. When the circular buffer 221 is full, the noise data of the latest frame (e.g., frame #17) can overwrite the noise data of frame #1 stored in the circular buffer 221.

[0061] In various embodiments, the circular buffer 221 may maintain 16 frames or samples of historical noise data measurements for each noise monitoring scan frequency. By storing historical noise measurements for each noise monitoring scan frequency, the touch controller 104 can perform statistical analysis of noise patterns in the time and frequency domains. For example, standard deviation calculation across N frames or samples of noise data measurements can allow the touch controller 104 to quantify the noise level and determine the appropriate noise operating mode for touch detection. The touch controller 104 can use standard deviation calculations from multiple sensing channels and frames to determine the severity of current noise interference. Based on the standard deviation calculations, the touch controller 104 can adaptively enter different noise operating modes optimized for changing noise conditions while maintaining touch detection reliability.

[0062] Figure 4 The noise analysis process according to an embodiment of this application is illustrated. It will be described in conjunction with the above-described figures. Figure 4 .

[0063] In one or more embodiments, the touch controller 104 performs a noise analysis process 400 to determine the noise operation mode of the touch detection process 200 based on the severity of noise interference. The noise analysis process 400 begins by performing a noise monitoring scan in step 402 and collects noise data for M sensing channels at each frequency for N frames in step 404, such as... Figure 2 and Figure 3 As described in [the text].

[0064] The noise analysis process 400 proceeds to step 406 to calculate the average value of the collected noise data for each of the M sensing channels at each frequency Freq0, Freq1, and Freq2 across N frames. In other words, the average value of the collected noise data is the average value for each sensing channel at each noise monitoring scan frequency. For example, refer to... Figure 3 The average noise data used for sensing channel Rx1 is calculated based on the noise data D0x1 used for 16 frames: .

[0065] The noise analysis process 400 proceeds to step 408 to calculate the standard deviation of the noise data for each of the M sensing channels at each frequency Freq0, Freq1, and Freq2 across N frames. In other words, the standard deviation of the collected noise data is the standard deviation of each sensing channel at each noise monitoring scan frequency. The standard deviation of the noise data can be calculated using the average value calculated in step 406. The standard deviation of the noise data can be calculated using the following equation: Where f is the noise monitoring scan frequency, D is the noise data stored in the corresponding sensing channel, N is the number of frames or samples, and M is the sensing channel. For example, the standard deviation of the noise data for 16 frames at the noise monitoring scan frequency Freq0 for sensing channel RxM can be calculated using the following equation: .

[0066] The noise analysis process 400 proceeds to step 410 to determine the maximum standard deviation of each noise monitoring scan frequency on the M sensing channels. The maximum standard deviation of each noise monitoring scan frequency can be calculated using the following equation: In one or more embodiments, a maximum standard deviation value is determined for each noise monitoring scan frequency. For example, when noise monitoring scans are performed at three different noise monitoring scan frequencies Freq0, Freq1, and Freq2, the maximum standard deviation is determined for each noise monitoring scan frequency Freq0, Freq1, and Freq2. .

[0067] The noise analysis process 400 proceeds to step 412 to determine the minimum of the maximum standard deviations for each noise monitoring scan frequency (i.e., the minimum standard deviation or minimum standard deviation). For example, the minimum standard deviation can be expressed by the following formula: In one or more embodiments, the minimum standard deviation can be used to determine the noise monitoring scan frequency with the minimum noise data. The noise monitoring scan frequency with the minimum noise data can be set as the mutual scan frequency for the touch detection process 200.

[0068] The noise analysis process 400 proceeds to step 414 to perform a mutual scan on the current frame, to step 416 to collect intensity data from the mutual scan of the current frame, and to step 418 to determine the standard deviation (i.e., current std) of the intensity data for the current frame from the mutual scan. The standard deviation for the current frame is calculated based on the set of frequencies of the mutual scan frequencies for the current frame. For example, the current mutual scan frequency of the current frame can be performed at the noise monitoring scan frequency with the minimum noise data (e.g., Freq1), and then based on... Calculate the standard deviation of the current frame. In one or more embodiments, the standard deviation of the current frame can be used to perform noise reduction measurements based on the severity of noise interference. The severity of noise interference can be used to determine the noise operation mode of the touch detection process 200. In one or more embodiments, the standard deviation of the current frame can be used to dynamically adjust the mutual sampling scan frequency and the hopping threshold used to perform hopping.

[0069] Figure 5 An example diagram illustrating noise and touch signals according to an embodiment of this application is shown. It will be described in conjunction with the above-described drawings. Figure 5 .

[0070] Graph 500 illustrates noise signal 502, touch signal 504, a first noise threshold 506, a second noise threshold 508, and a touch reporting threshold 510. In one or more embodiments, noise signal 502 represents noise interference that may be present during operation of electronic device 100. The relative magnitude of noise signal 502 compared to noise thresholds 506 and 508 can determine which noisy operating mode is activated. When the noise level exceeds certain noise thresholds, touch controller 104 can implement certain noise filtering techniques to maintain reliable touch detection.

[0071] In various embodiments, noise interference can originate from multiple sources both within and around the touchscreen device. For example, grid noise can be coupled into the touchscreen 102 via power connections and ground references. As mentioned above, telephone chargers can generate significant electromagnetic interference, particularly from switching power supplies and AC-DC conversion circuitry. Noise levels can vary depending on the quality of the charger; for example, a lower-quality charger can generate more severe interference. Display components can also introduce another source of noise interference. In various embodiments, display drive signals, backlight circuitry, and other display subsystems can couple electromagnetic noise into nearby touchscreen devices. The likelihood of display-related interference increases with display density and refresh rate.

[0072] In one or more embodiments, noise interference can be measured by observing deviations in capacitance values ​​at the sensing nodes of the touch sensing layer 116. These deviations can manifest as variations in signal strength measurements across different sensing channels and frames. The amplitude and frequency characteristics of the noise signal 502 can vary depending on the noise source and the operating conditions of the interfering components.

[0073] In one or more embodiments, touch signal 504 represents touch input on touchscreen 102 of electronic device 100. Touch signal 504 represents touch input that may originate from a finger touch or an active or passive pen touch. Touch controller 104 performs touch detection by measuring changes in signal amplitude at a capacitive sensing node formed by cross-drive and sensing electrodes in touch sensing layer 116. Changes in capacitance at the sensing node can indicate the presence and location of touch input on touchscreen 102. Touch controller 104 can process touch signal 504 as touch input when the amplitude of touch signal 504 exceeds touch reporting threshold 510.

[0074] In one or more embodiments, the noise signal 502 may have an amplitude exceeding the touch reporting threshold 510. When the noise signal 502 exceeds the touch reporting threshold 510, the touch controller 104 may incorrectly process the noise signal 502 as a touch input, which may result in ghosting touches or erroneous touch detection. The touch controller 104 can perform touch detection in various noise operation modes, which can reduce the impact of noise interference. The touch controller 104 can determine which noise operation mode to apply based on the characteristics of the noise signal 502, reducing the likelihood of processing the corresponding noise signal 502 as a touch input.

[0075] In one or more embodiments, the touch controller 104 may utilize various noise thresholds to determine an appropriate noise pattern for performing touch detection. For example, the touch controller 104 may include a first noise threshold 506 and a second noise threshold 508. In various embodiments, the second noise threshold 508 is a threshold that is higher than the first noise threshold 506. In various embodiments, the first noise threshold 506 may be referred to as a medium noise threshold 506, while the second noise threshold 508 may be referred to as a severe noise threshold 508.

[0076] In one or more embodiments, the first noise threshold 506 may be a threshold for moderate noise, while the second noise threshold 508 may be a threshold for severe noise. The first noise threshold 506 and the second noise threshold 508 may be predetermined thresholds stored in memory. For example, the first noise threshold 506 may be set to 40, and the second noise threshold 508 may be set to 80. Although the noise thresholds may be described herein as first and second noise thresholds 508, it should be understood that the noise thresholds may include more than two noise thresholds.

[0077] In one or more embodiments, the first noise threshold 506 may be a noise threshold used to determine whether operation is in normal mode or in a first noise mode. When low-noise interference is detected on the touchscreen 102 of the electronic device 100, the touch controller 104 may perform touch detection in normal mode. Low-noise interference exists when the amplitude of the noise signal 502 remains below the first noise threshold 506. In one or more embodiments, the normal mode may rely on noise reduction techniques, such as grounding and shielding arrangements in the hardware of the electronic device 100, to minimize noise coupled to the touch sensing layer 116. While noise reduction techniques in normal mode may be suitable for low-noise interference, they may be insufficient for moderate or severe noise that could interfere with touch detection accuracy.

[0078] In one or more embodiments, when moderate noise interference is detected on the touchscreen 102 of the electronic device 100, the touch controller 104 performs touch detection in a first noise mode. Moderate noise interference is present when the noise amplitude of the noise signal 502 exceeds a first noise threshold 506. In one or more embodiments, the first noise mode may incorporate additional noise reduction techniques, such as incorporating touch delay or increasing the touch reporting threshold, to reduce the impact of moderate noise interference on the electronic device 100. While noise reduction measures in the first noise mode may be appropriate for moderate noise interference, they may be insufficient for severe noise. In various embodiments, the first noise threshold 506 may be referred to as the moderate noise threshold, and the first noise mode may be referred to as the moderate noise mode.

[0079] In one or more embodiments, when severe noise interference is detected on the touchscreen 102 of the electronic device 100, the touch controller 104 performs touch detection in a second noise mode. Severe noise interference occurs when the noise amplitude of the noise signal 502 exceeds a second noise threshold 508. In one or more embodiments, the second noise mode may incorporate dynamic noise reduction techniques, such as firmware accumulation or transitions, to reduce the impact of severe noise interference on the electronic device 100. In various embodiments, the second noise threshold 508 may be referred to as a severe noise threshold, and the second noise mode may be referred to as a severe noise mode.

[0080] In one or more embodiments, the touch controller 104 can dynamically switch between noise operation modes as the characteristics of the noise signal 502 change with each noise monitoring scan. The various noise operation modes can be distinguished from genuine touch events by applying noise reduction techniques appropriate to the noise intensity.

[0081] Figure 6The processing flow of adaptive noise management in an electronic device according to an embodiment of this application is illustrated. It will be described in conjunction with the above-described figures. Figure 6 .

[0082] Starting from frame 602, the touch controller 104 performs a noise monitoring scan on the touchscreen 102. The noise monitoring scan can be performed as described above. Figure 2 The process is performed as described in [the document]. As shown in the next box 604, the touch controller collects noise data from the noise monitoring scan in box 602. In one or more embodiments, the noise data may be stored, for example, in a circular buffer. The circular buffer may store noise data for each frequency in multiple frames for each sensing channel. In various embodiments, the number of frames may represent the number of samples of noise data for each frequency. When a new frame or sampled noise data is collected, the new noise data may overwrite the oldest data in the circular buffer, and a scrolling window of frames or samples is maintained for each frequency and sensing channel combination.

[0083] After collecting noise data in box 604, the touch controller 104 further determines whether to perform touch detection in normal mode, a first noise mode, or a second noise mode. In normal mode, the touch controller 104 can continue to perform touch detection without applying additional noise reduction measures. In the first noise mode, the touch controller 104 can apply a first set of noise reduction measures to reduce moderate noise levels that may interfere with touch detection. In the second noise mode, the touch controller 104 can apply a second set of noise reduction measures to reduce severe noise levels that may interfere with touch detection.

[0084] Referring to the determination diamond 606, the touch controller 104 determines whether the noise data is greater than a first noise threshold 506 and less than a second noise threshold 508. In one or more embodiments, the first noise threshold 506 may be a moderate noise threshold, while the second noise threshold 508 may be a severe noise threshold, as described above. Figure 5 As described in [the document]. Although the noise threshold can be described as a first noise threshold 506 and a second noise threshold 508, it should be understood that the noise threshold may include more than two noise thresholds.

[0085] In one or more embodiments, when noise data is greater than a first noise threshold 506 and less than a second noise threshold 508, the touch controller 104 may determine that moderate noise interference has been detected on the electronic device 100. When the noise data is greater than the first noise threshold 506 and less than the second noise threshold 508 (i.e., 606 = yes), the touch controller 104 enters a first noise mode in block 608. The first noise mode may include a first set of noise reduction measures, such as increasing touch latency by increasing the touch reporting threshold or by smoothing noise effects by incorporating an IIR (Infinite Impulse Response) filter.

[0086] Touch latency refers to the processing of detected touch input on subsequent frames. For example, if touch input indicates a touch is present in the current frame N, the touch controller processes the touch input on subsequent frames (e.g., N+1, N+2, etc.). Touch latency can improve touch detection by reporting touch inputs that have already existed in consecutive frames.

[0087] A touch reporting threshold refers to the intensity threshold used to report touch input. For example, a touch input might have an intensity value of 250, which can be treated as a touch when the touch reporting threshold is 200. However, when noise interference has an intensity value greater than the touch reporting threshold, it can be treated as touch input that causes ghosting. By increasing the touch reporting threshold from, for example, 200 to a higher threshold of 300, noise interference below the higher threshold is not reported as touch input. While this first set of noise reduction measures can help with moderate noise levels, the method may not completely eliminate severe noise interference.

[0088] In one or more embodiments, when the noise data is not greater than a first noise threshold 506 and less than a second noise threshold 508 (i.e., 606 = No), the touch controller 104 determines in decision diamond 816 whether the noise data is greater than the second noise threshold 508. In one or more embodiments, when the noise data is greater than the second noise threshold 508, the touch controller 104 may determine that severe noise interference has been detected on the electronic device 100. When the noise data is greater than the second noise threshold 508 (i.e., 608 = Yes), the touch controller enters a second noise mode in box 618. The second noise mode may apply a second set of noise reduction measures, such as firmware accumulation and transitions.

[0089] Firmware accumulation refers to performing two or more mutual scans to collect multiple touch intensity measurements within a frame period. Firmware accumulation will be described in detail below. Skipping refers to adjusting the scan frequency used for mutual scanning based on the frequency of the noise monitoring scan. By performing skipping, the noise level, which is typically close to the scan frequency used for mutual scanning, can be dynamically adjusted to eliminate noise that may interfere with touch detection. Skipping will be described in detail below. In one or more embodiments, firmware accumulation or skipping can be implemented in a second noise mode. In other embodiments, firmware accumulation and skipping can be implemented together in the second noise mode. In some embodiments, skipping can be performed before firmware accumulation, such that the two or more mutual scans are performed at an adjusted scan frequency.

[0090] When the noise data is not greater than the second noise threshold 508, the process proceeds to the normal mode in block 624. In one or more embodiments, the touch controller 104 can exit the first noise mode 608 or the second noise mode 618 based on the previous operating state. After entering the first or second noise mode or returning to the normal mode, the process loops back to performing a noise monitoring scan in block 602. The touch controller 104 continuously monitors noise data and adapts to noise interference to improve touch detection. Continuous monitoring of noise intensity allows the touch controller to dynamically adjust its operation based on noise interference.

[0091] Figure 7 A flowchart for performing a transition according to an embodiment of this application is shown. It will be described in conjunction with the above-described drawings. Figure 7 .

[0092] In one or more embodiments, a jump can be performed to dynamically adjust the mutual scan frequency to eliminate noise that may interfere with touch detection. In one or more embodiments, the standard deviation (current standard) and minimum standard deviation (minimum standard) of the intensity data from the current frame of the noise analysis process 400 can be used to determine whether to adjust the mutual scan frequency used for touch detection. The touch controller 104 can determine the optimal frequency for performing subsequent mutual scans 222 to minimize noise interference while collecting intensity data. The touch controller 104 can adjust the mutual scan frequency to the optimal frequency for subsequent mutual scans 222.

[0093] Reference Figure 7 Flowchart 700 begins at start 702 and obtains the current standard deviation (current std) and minimum standard deviation (min std) of the current frame from the noise analysis process 400 in box 704. The current standard deviation and minimum standard deviation can be compared with the jump threshold.

[0094] In decision box 706, touch controller 104 calculates the difference between the current standard deviation (current std) and the minimum standard deviation (min std) of the current frame, and compares the difference in standard deviations with a transition threshold. This comparison determines whether the current mutual scan frequency is experiencing significant noise interference, compared to a noise monitoring scan frequency with the lowest noise data. In various embodiments, such as... Figure 4 As described in the standard deviation calculation, for the current mutual scanning frequency, the standard deviation of the current frame can be calculated for the data measurements collected on the current frame.

[0095] For example, when the difference in standard deviations is greater than the jump threshold, the current mutual scan frequency experiences significant noise interference compared to the noise monitoring scan frequency with the least noise data. When the difference in standard deviations is less than the jump threshold, the current mutual scan frequency experiences less noise interference compared to the noise monitoring scan frequency with the least noise data. When the difference in standard deviations exceeds the jump threshold (i.e., 706 = Yes), the process moves to block 708. In block 708, the touch controller 104 sets the mutual scan frequency for the next mutual scan to the noise monitoring scan frequency with the least noise data. By adjusting the mutual scan frequency, severe noise interference can be avoided when performing touch detection. In various embodiments, the new mutual scan frequency can be maintained until the noise conditions change.

[0096] When the difference in standard deviation at decision box 704 does not exceed the threshold (i.e., 704 = No), processing flow 700 continues at box 708, maintaining the current mutual scanning frequency. Flowchart 700 can be continuously repeated during device operation to dynamically adjust the mutual scanning frequency used for mutual scanning based on noise conditions in the previous noise monitoring scan. This adaptive frequency determination helps maintain reliable touch detection by avoiding frequencies most affected by noise interference.

[0097] Figure 8 The processing flow of adaptive noise management in an electronic device according to an embodiment of this application is illustrated. It will be described in conjunction with the above-described figures. Figure 8 .

[0098] In one or more embodiments, the jump threshold can be dynamically adjusted based on the standard deviation (current std) and minimum standard deviation threshold (min_std_threshold) of the intensity data of the current frame from the noise analysis process 400. Flowchart 800 illustrates the process for dynamically adjusting the jump threshold. In one or more embodiments, the touch controller 104 can evaluate noise conditions and adjust the jump threshold based on the noise conditions.

[0099] In one or more embodiments, the standard deviation of the current frame from the noise analysis process 400 can be used to determine a jump threshold for determining the mutual scanning frequency of touch detection in flowchart 700.

[0100] In decision box 802, the touch controller 104 compares the standard deviation of the current frame with a minimum standard deviation threshold (min_std_thres). The minimum standard deviation threshold can be a predetermined value, such as value 30, that can be stored in the memory 110 of the touch controller 104. This comparison determines whether the current noise conditions guarantee the adjustment of the jump threshold. In various embodiments, such as... Figure 4As described above, standard deviation calculation can be performed on data measurements collected across multiple frames for each scan frequency.

[0101] In one or more embodiments, the jump threshold can be dynamically adjusted to a higher threshold to suit the current noise conditions. When the current standard deviation exceeds the minimum standard deviation threshold, the process moves to block 804. In block 804, the touch controller 104 adjusts the jump threshold based on a predetermined switching threshold, the current frame's standard deviation (current std), the minimum standard deviation (min std), and a predetermined scaling factor. The switching threshold and scaling factor can be predetermined values ​​stored in memory 110. For example, the switching threshold could be a value of 15, and the scaling factor could be 1 / 4. The noise threshold can be adjusted based on the following formula: Jump threshold = Switch threshold + (current std - min std) (Scaling factor). By adjusting the jump threshold to a higher threshold, the touch controller 104 can evaluate touch detection when the current noise conditions indicate severe noise interference.

[0102] When the current standard deviation is less than the minimum standard deviation threshold at decision box 802, the process proceeds to box 806. At box 806, the jump threshold is set to be equal to the switching threshold. The switching threshold can be threshold 15. In various embodiments, the jump threshold adjustment process can be repeated continuously during device operation to maintain an appropriate noise detection threshold when noise conditions change.

[0103] Figure 9A and Figure 9B This illustrates an intensity bitmap according to an embodiment of this application. (The bitmap will be combined with...) Figure 1A and Figure 1B describe Figure 9A - Figure 9B . Figure 9A An intensity bitmap 900 is shown, representing the capacitance change on the electronic device 100. Figure 9B An intensity bitmap 902 representing frame N+1 of capacitance changes on electronic device 100 is shown. Intensity bitmaps 900 and 902 can be used to illustrate a noise reduction technique that can improve touch detection accuracy by reporting touch events when capacitance changes indicate touch input and ignoring (e.g., not reporting) capacitance changes that indicate noise interference.

[0104] In one or more embodiments, the touch controller 104 generates intensity bitmaps 900, 902, which include intensity values ​​(e.g., N, N+1, etc.) representing capacitance changes for each frame. Each frame of the intensity bitmaps 900, 902 provides a snapshot of the sensing nodes, and the corresponding intensity values ​​can be recorded and analyzed on consecutive frames to determine which sensing nodes may indicate touch input or noise interference.

[0105] In one or more embodiments, the intensity values ​​may include both positive and negative values. A positive intensity value may represent an increase in capacitance, for example, caused by a finger or stylus. A negative intensity value may represent a decrease in capacitance, which may occur around the edges of a touch event or due to environmental factors. The magnitude of these intensity values ​​is related to the intensity of the touch input or noise interference. A larger positive intensity value indicates a stronger contact or the presence of a more significant conductive object. The intensity bitmap may display the intensity values ​​as grayscale levels or as colors to represent the touch intensity.

[0106] In one or more embodiments, the touch controller 104 can be configured to adjust the touch reporting threshold as a noise reduction technique. The touch reporting threshold can be used to determine when touch input exists. When the intensity value of a sensing node exceeds the touch reporting threshold, the touch controller 104 determines that touch input exists at the respective sensing node and can report it as a touch event. When the intensity value of a sensing node is less than the touch reporting threshold, the touch controller 104 can ignore the corresponding sensing node.

[0107] In one or more embodiments, the touch reporting threshold can be set to a value higher than the amplitude of a noise signal capable of interfering with touch detection. For example, when the amplitude of the noise signal is 250, the touch reporting threshold can be set to +800. In various embodiments, the touch reporting threshold can be adjusted or increased when moderate or severe noise is present. By increasing the touch reporting threshold, moderate or severe noise that would otherwise exceed the set touch reporting threshold can be ignored by adjusting the touch reporting threshold. The touch reporting threshold can vary for different noise levels, devices, or projects requiring different touch intensities. For example, the touch reporting threshold can be 150, 200, 250, etc. In various embodiments, when moderate noise interference is present, the adjustment of the touch reporting threshold can be combined with a moderate noise mode.

[0108] In one or more embodiments, the touch controller 104 may store intensity bitmaps of multiple consecutive frames in memory 110 to enable analysis of overlapping touch patterns on the frames to determine the location of a touch input. When the intensity value exceeds a touch reporting threshold, the touch controller 104 may use the intensity bitmaps to determine the presence of a touch input and report the touch input as a touch event to the system-on-chip 106.

[0109] like Figure 9A and Figure 9BAs shown, intensity bitmap 900 includes the intensity values ​​of touch input 904a and noise interference 906a in frame N, and intensity bitmap 902 includes the intensity values ​​of touch input 904b and noise interference 906b in frame N+1. Touch input 904a in frame N and touch input 904b in frame N+1 are shown on sensing nodes overlapping consecutive frames N and N+1. Noise interference 906a on frame N and noise interference 906b on frame N+1 are shown on different sensing nodes between consecutive frames N and N+1. While some noise interference 906a may cause sensing nodes to have intensity values ​​exceeding the touch reporting threshold, it can be incorporated into touch latency to further improve touch detection accuracy.

[0110] In one or more embodiments, the touch controller 104 can be configured to incorporate touch latency as a noise reduction technique. Capacitance changes from touch input are typically detected at sensing nodes across overlapping consecutive frames. On the other hand, capacitance changes caused by noise interference typically do not overlap between consecutive frames. In various embodiments, touch latency can be incorporated into a moderate noise mode when moderate noise interference is present.

[0111] Touch delay can be performed by analyzing the intensity bitmaps 900, 902 of multiple consecutive frames. When capacitance changes on a sensing node overlap across multiple consecutive frames, touch controller 104 can determine that touch input exists at the overlapping sensing nodes and can report the touch input as a touch event. For example, when capacitance changes on a sensing node are observed across multiple frames (e.g., frames N, N+1, or N+n), touch controller 104 can determine that the capacitance changes on the sensing node are touch input. Although touch input can be detected on the first frame N with touch delay, touch controller 104 reports the touch input as a touch event when it detects touch input on a later frame (e.g., N+1, N+2, or N+n). Touch controller 104 can be configured to report touch events on a specific frame (e.g., N+1). The specific frame used to report touch events can vary for different devices or projects.

[0112] Figure 10A and Figure 10B The output signal according to an embodiment of this application is shown. It will be described in conjunction with the above-described drawings. Figure 10A and Figure 10B . Figure 10A and Figure 10B Exemplary output signals 1000a and 1000b with different scanning configurations are shown.

[0113] Figure 10AAn exemplary output signal 1000a for one frame cycle of mutual scanning is shown. Output signal 1000a illustrates intensity data measurements collected from the mutual scan. In one or more embodiments, touch controller 104 may perform mutual scanning to collect a single intensity data measurement for each frame cycle. When low or moderate noise interference is present, a single intensity data measurement per frame may be sufficient to perform accurate touch detection. When noise interference is severe, a single intensity data measurement per frame may not provide accurate touch detection. For example, if a single intensity data measurement coincides with a noise spike, touch controller 104 may handle an erroneous touch or mask an actual touch. Noise spikes in severe noise interference can be omitted during touch detection by collecting multiple intensity data measurements for each frame, or by enabling firmware accumulation.

[0114] Figure 10B An exemplary output signal 1000b is shown for one frame period of mutual scanning with firmware accumulation enabled. When firmware accumulation is enabled, the touch controller 104 performs two or more mutual scans on the same portion of a frame to collect multiple intensity measurements within each frame period. For example, output signal 1000b shows two intensity data measurements collected during one frame period. Although output signal 1000b shows two intensity measurements, the touch controller 104 can be configured to perform any number of mutual scans within each frame period to collect any number of intensity data measurements in each frame, such as three, four, or more intensity data measurements.

[0115] In one or more embodiments, firmware accumulation can provide more robust touch detection in environments with severe noise interference. Firmware accumulation provides enhanced noise immunity by collecting and averaging multiple intensity measurements within each frame period. The averaging of multiple intensity measurements can reduce the impact of random noise fluctuations and transient interference compared to a single intensity measurement. Since random noise typically varies between measurements, and the effective touch signal remains relatively stable, averaging multiple intensity data measurements can improve the signal-to-noise ratio of the touch measurement. For example, noise interference from the power supply, charger, or display components can produce periodic noise patterns that cause spikes in random noise. By collecting and averaging multiple measurements, the impact of individual random noise spikes can be reduced, resulting in more reliable touch detection.

[0116] In various embodiments, multiple intensity data measurements per frame also enable additional noise analysis. Variations between multiple intensity data measurements within a frame can also provide information about noise characteristics to improve touch detection. Statistical analysis of multiple intensity data measurements can identify and compensate for different types of interference patterns, thereby further improving touch detection reliability in noisy environments.

[0117] In one or more embodiments, intensity data measurements can be collected at different frame rates depending on the scan configuration of the mutual scan. For example, a mutual scan configured to collect one intensity measurement per frame can be processed at a frame rate of 120 Hz. When firmware accumulation is enabled, a mutual scan configured to collect multiple intensity measurements can be processed at a lower frame rate and requires more scan time. For example, a mutual scan configured to collect two intensity data measurements can reduce the frame rate from 120 Hz to 90 Hz. In one or more embodiments, the frame rate can be further reduced for each additional intensity data measurement. While firmware accumulation requires additional scan time and reduces the frame rate, the trade-off between response speed and noise reduction is worthwhile in noisy environments.

[0118] In one or more embodiments, the touch controller 104 may dynamically enable or disable firmware accumulation based on detected noise conditions. By enabling and disabling firmware accumulation based on noise conditions, the touch controller 104 can provide enhanced noise reduction when noise interference is severe, and maintain processing speed when noise interference is low or moderate.

[0119] Figure 11 The processing flow of adaptive noise management in an electronic device according to an embodiment of this application is illustrated. It will be described in conjunction with the above-described figures. Figure 11 .

[0120] Process flow 1100 begins by performing a noise monitoring scan in block 1102 and collecting noise data from the noise monitoring scan in block 1104. The noise monitoring scan in block 1102 corresponds to the above-described noise monitoring scan. Figure 6 The noise monitoring scan described in block 602, and the noise data set 1104 corresponds to the above-described noise monitoring scan. Figure 6 The noise data set described in block 604.

[0121] In one or more embodiments, noise data may be stored, for example, in a cyclic buffer. The cyclic buffer may store noise data for each frequency across multiple frames for each sensing channel. In various embodiments, the number of frames may represent the number of samples of noise data for each frequency. When a new frame or sampled noise data is collected, the new noise data may overwrite the oldest data in the cyclic buffer, and a rolling window of frames or samples is maintained for each frequency and sensing channel combination.

[0122] After collecting noise data in block 1104, touch controller 104 continues to determine whether to perform touch detection in normal mode 1126, medium noise mode 1108, or severe noise mode 1118. In one or more embodiments, touch controller 104 continues to perform touch detection without applying additional noise reduction measures in normal mode 1126. Touch controller 104 may apply a first set of noise filters to reduce the medium noise level that may interfere with touch detection in medium noise mode 1108. Touch controller 104 applies a second set of noise filters to reduce the severe noise level that may interfere with touch detection in severe noise mode 1118.

[0123] Referring to the judgment diamond 1106, the touch controller 104 determines whether the noise data is greater than the medium noise threshold 506 and less than the severe noise threshold 508. Figure 6 As shown. In one or more embodiments, when the noise data is greater than a moderate noise threshold 506 and less than a severe noise threshold 508, the touch controller 104 determines that moderate noise interference has been detected on the electronic device 100. When the noise data is greater than the moderate noise threshold 506 and less than the severe noise threshold 508 (i.e., 1106 = yes), the touch controller 104 enters a moderate noise mode 1108. In one or more embodiments, the moderate noise mode 1108 includes a first set of noise reduction measures, which includes adding a touch delay 1110 to verify touches across multiple frames, and increasing a touch reporting threshold 1112 to distinguish valid touches from noise, as described above. Figure 9A and 9B As described in [the text].

[0124] In one or more embodiments, the moderate noise threshold 506 may be a predetermined first noise threshold, while the severe noise threshold 508 may be a predetermined second noise threshold. The predetermined first noise threshold is less than the predetermined second noise threshold. For example, the moderate noise threshold 506 may be set to 40, while the severe noise threshold 508 may be set to 80. Although the noise thresholds may be described herein as a moderate or first noise threshold 506 and a severe or second noise threshold 508, it should be understood that the noise thresholds may include more than one noise threshold.

[0125] When the noise data is not greater than the moderate noise threshold 506 and less than the severe noise threshold 508 (i.e., 1106 = No), the touch controller 104 determines in the decision diamond 1116 whether the noise data is greater than the severe noise threshold 508. In one or more embodiments, when the noise data is greater than the severe noise threshold 508, the touch controller 104 determines that severe noise interference has been detected on the electronic device 100. When the noise data is greater than the severe noise threshold 508 (i.e., 1116 = Yes), the touch controller enters a severe noise mode 1118. In one or more embodiments, the severe noise mode 1118 includes a second set of noise reduction measures, which include, for example... Figure 10A and Figure 10B Firmware accumulation 1120 and as described in Figure 7 The jump 1122 described in the text.

[0126] When the noise data is not greater than the severe noise threshold 508 (i.e., 1116 = No), the process proceeds to normal mode 1126 to perform touch detection. In one or more embodiments, the touch controller 104 may exit the medium noise threshold 506 or the severe noise threshold 508 based on the previous operating state.

[0127] The process proceeds from Normal Mode 1126, Medium Noise Mode 1108, and Severe Noise Mode 1118 to performing mutual scanning. Mutual scanning collects touch intensity data from the touch sensing layer 116 based on noise reduction measures applied in the respective noise mode. For example, when operating in Normal Mode 1126, mutual scanning collects one intensity measurement per frame at a frame rate of 120Hz, and the touch controller 104 processes the individual touch intensity data to determine the coordinates of the touch input. For example, when operating in Medium Noise Mode 1108, the touch controller 104 adds a touch delay 1110 to process touch input detected on a later frame and increases the touch reporting threshold 1112 above a threshold for the noise data collected from frame 1104. For example, when operating in Severe Noise Mode 1118, the touch controller 104 enables Firmware Accumulation 1120 to collect and average multiple intensity data measurements from mutual scanning and performs a jump 1122 by changing the scan frequency used for mutual scanning based on the frequency of the noise monitoring scan.

[0128] Touch controller 104 can process touch intensity data from mutual scanning to determine touch coordinates on the touchscreen and report the touch to the system on chip 106. System on chip 106 can provide output to touchscreen 102 based on the reported touch coordinates.

[0129] Following the mutual scan in block 1124, process 1100 returns to block 1102 to perform a noise monitoring scan. The process continues in a continuous loop, returning to perform noise monitoring scan 1102 to adapt to changing noise conditions. In one or more embodiments, the touch controller 104 can continuously monitor noise data and adapt to noise interference to improve touch detection. Continuous monitoring of noise data allows the touch controller 104 to dynamically adjust its operation based on the severity of noise interference. This adaptive approach allows the touch controller to maintain reliable operation under varying levels of environmental interference.

[0130] The exemplary embodiments of this application are summarized herein. Other embodiments can also be understood from the entirety of the description and claims submitted herein.

[0131] Example 1. The first example includes a method of operating a touchscreen device. The method includes: performing a noise monitoring scan on the touchscreen device; collecting noise data from the noise monitoring scan; determining whether the noise data is greater than a first noise threshold and less than a second noise threshold, and if so, determining whether the noise data is greater than the second noise threshold, the second noise threshold being greater than the first noise threshold; entering a first noise mode to apply a first noise filter in response to the noise data being greater than the first noise threshold and less than the second noise threshold; and entering a second noise mode to apply a second noise filter in response to the noise data being greater than the second noise threshold.

[0132] Example 2. The method of Example 1, wherein applying the first noise filter includes: adding a touch delay such that the reported touch input is delayed by multiple frames; increasing the touch reporting threshold; and reporting the touch input based on the increased touch delay and the increased touch reporting threshold.

[0133] Example 3. The method as described in either Example 1 or 2, wherein applying the second noise filter includes: performing two or more mutual scans on the same portion of a frame on the touchscreen device; collecting intensity data from each of the two or more mutual scans; calculating an average intensity from the intensity data of the two or more mutual scans; and reporting a touch input in response to the calculated average intensity exceeding a touch reporting threshold.

[0134] Example 4. The method of any one of Examples 1 to 3, wherein applying the second noise filter comprises: setting a mutual scan frequency for subsequent mutual scans based on the noise data from the noise monitoring scan; performing two or more mutual scans on the same portion of a frame at the mutual scan frequency based on the noise data; collecting intensity data from each of the two or more mutual scans; calculating an average intensity from the intensity data of the two or more mutual scans; and reporting a touch input in response to the calculated average intensity exceeding a touch reporting threshold.

[0135] Example 5. The method of any one of Examples 1 to 4, wherein performing the noise monitoring scan includes performing the noise monitoring scan on a plurality of frames at a first frequency, a second frequency, and a third frequency, and wherein collecting the noise data from the noise monitoring scan further includes: collecting noise data at the first frequency, the second frequency, and the third frequency; calculating a first maximum standard deviation at the first frequency, a second maximum standard deviation at the second frequency, and a third maximum standard deviation at the third frequency; and determining that the first maximum standard deviation is less than the second maximum standard deviation and the third maximum standard deviation.

[0136] Example 6. The method of any one of Examples 1 to 5 further includes: performing a mutual scan on a current frame of the touchscreen device; collecting intensity data from the mutual scan for the current frame; and calculating a current standard deviation of the intensity data for the current frame, wherein applying a second noise filter includes: calculating the difference between the current standard deviation and the first maximum standard deviation; comparing the difference of the standard deviation with a jump threshold; determining that the difference of the standard deviation is greater than the jump threshold; and in response to determining that the difference of the standard deviation is greater than the jump threshold, setting the mutual scan frequency for subsequent mutual scans to the first frequency.

[0137] Example 7. The method of any one of Examples 1 to 6, wherein applying the second noise filter further comprises: performing two or more mutual scans on the same portion of a frame for subsequent mutual scans of the touchscreen device; collecting intensity data from each of the two or more mutual scans; calculating an average intensity from the intensity data of the two or more mutual scans; and reporting a touch input in response to the calculated average intensity exceeding a touch reporting threshold.

[0138] Example 8. A second example includes another method of operating a touchscreen device. The method includes: performing a first noise monitoring scan on the touchscreen device; collecting first noise data from the first noise monitoring scan; determining that the first noise data is greater than a first noise threshold and less than a second noise threshold, the second noise threshold being greater than the first noise threshold; entering a first noise mode in response to the first noise data being greater than the first noise threshold and less than the second noise threshold; performing a second noise monitoring scan on the touchscreen device; collecting second noise data from the second noise monitoring scan; determining that the second noise data is greater than a second noise threshold; and entering a second noise mode in response to the second noise data exceeding the second noise threshold, the second noise mode including performing two or more mutual scans on the same portion of a frame.

[0139] Example 9. The method as described in Example 8, wherein the first noise mode further includes: adding a touch delay; increasing a touch reporting threshold; and reporting touch input based on the increased touch delay and the increased touch reporting threshold.

[0140] Example 10. The method as described in either Example 8 or 9, wherein the second noise mode further comprises: collecting intensity data from each of the two or more mutual scans; calculating an average intensity from the intensity data of the two or more mutual scans; and reporting a touch input in response to the calculated average intensity exceeding a touch reporting threshold.

[0141] Example 11. The method of any one of Examples 8 to 10, wherein the second noise mode further comprises: setting a mutual scan frequency for subsequent mutual scans based on the second noise data from the second noise monitoring scan; and performing the subsequent mutual scans at the set mutual scan frequency.

[0142] Example 12. A method as described in any one of Examples 8 to 11, wherein: performing the second noise monitoring scan includes performing the second noise monitoring scan on a second plurality of frames at a first frequency, a second frequency, and a third frequency; and collecting the second noise data from the second noise monitoring scan includes: collecting the second noise data from a plurality of sensing channels for the second plurality of frames at the first frequency, the second frequency, and the third frequency; calculating a first maximum standard deviation at the first frequency, a second maximum standard deviation at the second frequency, and a third maximum standard deviation at the third frequency; and determining that the first maximum standard deviation is less than the second maximum standard deviation and the third maximum standard deviation.

[0143] Example 13. The method of any one of Examples 8 to 12 further includes: performing a first mutual scan on a current frame of the touchscreen device before entering the second noise mode; collecting intensity data from the first mutual scan for the current frame; and calculating a current standard deviation of the intensity data for the current frame. The second noise mode further includes: calculating the difference in standard deviations between the current standard deviation and a first maximum standard deviation; comparing the difference in standard deviations with a jump threshold; determining whether the difference in standard deviations is greater than the jump threshold; and, in response to the difference in standard deviations being greater than the jump threshold, setting the mutual scan frequency of the two or more mutual scans to the first frequency; wherein performing the two or more mutual scans on the same portion of the frame includes: performing the two or more subsequent mutual scans on the same portion of the frame at the set mutual scan frequency; collecting intensity data from each of the two or more mutual scans; calculating an average intensity from the intensity data of the two or more mutual scans; and reporting a touch input in response to the calculated average intensity exceeding a touch reporting threshold.

[0144] Example 14. A third example includes a device comprising: a touchscreen; and a touch controller. The touch controller is configured to: perform a noise monitoring scan on the touchscreen; collect noise data from the noise monitoring scan; determine whether the noise data is greater than a first noise threshold and less than a second noise threshold, or determine whether the noise data is greater than the second noise threshold, the second noise threshold being greater than the first noise threshold; operate in a first noise mode to apply a first noise filter in response to the noise data being greater than the first noise threshold and less than the second noise threshold; and operate in a second noise mode to apply a second noise filter in response to the noise data being greater than the second noise threshold.

[0145] Example 15. A device as in Example 14, wherein, when the touch controller operates in the first noise mode, the touch controller is further configured to: add a touch delay such that reported touch input is delayed by multiple frames; and add a touch reporting threshold; and report touch input based on the touch delay and the touch reporting threshold.

[0146] Example 16. A device as described in either Example 14 or 15, wherein, when the touch controller operates in the second noise mode, the touch controller is further configured to: perform two or more mutual scans on the same portion of a frame on the touchscreen; collect intensity data from each of the two or more mutual scans; calculate an average intensity from the intensity data of the two or more mutual scans; and report a touch input in response to the calculated average intensity exceeding a touch reporting threshold.

[0147] Example 17. A device as described in any one of Examples 14 to 16, wherein, when the touch controller operates in the second noise mode, the touch controller is further configured to set a mutual scanning frequency based on noise data from the noise monitoring scan.

[0148] Example 18. A device as described in any one of Examples 14 to 17, wherein the touch controller is further configured to: perform noise monitoring scans on a plurality of frames at a first frequency, a second frequency, and a third frequency; collect noise data for the first frequency, the second frequency, and the third frequency; calculate a first maximum standard deviation for the first frequency, a second maximum standard deviation for the second frequency, and a third maximum standard deviation for the third frequency; and determine that the first maximum standard deviation is less than the second maximum standard deviation and the third maximum standard deviation.

[0149] Example 19. A device as described in any one of Examples 14 to 18, wherein the touch controller is further configured to: perform a mutual scan of a current frame of the touchscreen; collect intensity data from the mutual scan for the current frame; calculate a current standard deviation of the intensity data for the current frame; calculate the difference in standard deviations between the current standard deviation and a first maximum standard deviation; compare the difference in standard deviations with a jump threshold; determine whether the difference in standard deviations is greater than the jump threshold; and, in response to the difference in standard deviations being greater than the jump threshold, set the mutual scan frequency to the first frequency.

[0150] Example 20. A device as in any one of Examples 14 to 19, wherein, when the touch controller operates in a second noise mode, the touch controller is further configured to: perform two or more mutual scans on the same portion of a frame at a set mutual scan frequency; collect intensity data from each of the two or more mutual scans; calculate the average intensity from the intensity data of the two or more mutual scans; and report a touch input in response to the calculated average intensity exceeding a touch reporting threshold.

[0151] Although the invention has been described with reference to illustrative embodiments, the description is not intended to be limiting. Various modifications and combinations of the illustrative embodiments, as well as other embodiments of the invention, will be apparent to those skilled in the art based on the specification. Therefore, the appended claims are intended to cover any such modifications or embodiments.

Claims

1. A method for operating a touchscreen device, the method comprising: Perform a noise monitoring scan on the touchscreen device; Noise data is collected from the noise monitoring scan; Determine whether the noise data is greater than a first noise threshold and less than a second noise threshold, and if the noise data is greater than the first noise threshold and less than the second noise threshold, determine whether the noise data is greater than the second noise threshold, wherein the second noise threshold is greater than the first noise threshold; In response to the noise data being greater than the first noise threshold and less than the second noise threshold, a first noise mode is entered to apply a first noise filter; as well as In response to the noise data being greater than the second noise threshold, a second noise mode is entered to apply a second noise filter.

2. The method of claim 1, wherein applying the first noise filter comprises: Add a touch delay so that the reported touch input is delayed by several frames; Increase the touch reporting threshold; as well as Touch input is reported based on the added touch latency and the increased touch reporting threshold.

3. The method of claim 1, wherein applying the second noise filter comprises: Perform two or more mutual scans on the same portion of the frame on the touchscreen device; Intensity data is collected from each of the two or more mutual scans; Calculate the average intensity from the intensity data of the two or more mutually scanned samples; and A touch input is reported in response to the calculated average intensity exceeding the touch reporting threshold.

4. The method of claim 1, wherein applying the second noise filter comprises: The mutual scan frequency for subsequent mutual scans is set based on the noise data from the noise monitoring scan. Based on the noise data, two or more mutual scans are performed on the same portion of the frame at the mutual scan frequency; Intensity data is collected from each of the two or more mutual scans; Calculate the average intensity from the intensity data of the two or more mutually scanned samples; and A touch input is reported in response to the calculated average intensity exceeding the touch reporting threshold.

5. The method of claim 1, wherein performing the noise monitoring scan comprises performing the noise monitoring scan on a plurality of frames at a first frequency, a second frequency, and a third frequency, and wherein collecting the noise data from the noise monitoring scan further comprises: Collect noise data for the first frequency, the second frequency, and the third frequency; Calculate the first maximum standard deviation for the first frequency, the second maximum standard deviation for the second frequency, and the third maximum standard deviation for the third frequency; as well as The first maximum standard deviation is determined to be less than the second maximum standard deviation and the third maximum standard deviation.

6. The method of claim 5, further comprising: Perform a mutual scan on the current frame of the touchscreen device; Intensity data is collected from the mutual scans targeting the current frame; as well as Calculating the current standard deviation of the intensity data for the current frame, wherein applying the second noise filter includes: Calculate the difference in standard deviation between the current standard deviation and the first maximum standard deviation; The difference in the standard deviation is compared with the jump threshold; Determine that the difference in the standard deviation is greater than the jump threshold; and In response to determining that the difference in the standard deviation is greater than the jump threshold, the mutual scanning frequency for subsequent mutual scanning is set to the first frequency.

7. The method of claim 6, wherein applying the second noise filter further comprises: For the subsequent mutual scan of the touchscreen device, two or more mutual scans are performed on the same portion of the frame; Intensity data is collected from each of the two or more mutual scans; Calculate the average intensity from the intensity data of the two or more mutually scanned samples; and A touch input is reported in response to the calculated average intensity exceeding the touch reporting threshold.

8. A method for operating a touchscreen device, the method comprising: Perform a first noise monitoring scan on the touchscreen device; The first noise data is collected from the first noise monitoring scan; The first noise data is determined to be greater than a first noise threshold and less than a second noise threshold, wherein the second noise threshold is greater than the first noise threshold. The system enters a first noise mode in response to the first noise data being greater than the first noise threshold and less than the second noise threshold. Perform a second noise monitoring scan on the touchscreen device; The second noise data is collected from the second noise monitoring scan; It is determined that the second noise data is greater than the second noise threshold; as well as In response to the second noise data exceeding the second noise threshold, a second noise mode is entered, the second noise mode comprising performing two or more mutual scans on the same portion of the frame.

9. The method of claim 8, wherein the first noise mode further comprises: Add touch delay; Increase the touch reporting threshold; as well as Touch input is reported based on the added touch latency and the increased touch reporting threshold.

10. The method of claim 8, wherein the second noise mode further comprises: Intensity data is collected from each of the two or more mutual scans; Calculate the average intensity from the intensity data of the two or more mutually scanned samples; and A touch input is reported in response to the calculated average intensity exceeding the touch reporting threshold.

11. The method of claim 8, wherein the second noise mode further comprises: The mutual scan frequency for subsequent mutual scans is set based on the second noise data from the second noise monitoring scan. as well as The subsequent mutual scan is performed at the set mutual scan frequency.

12. The method according to claim 8, wherein: Performing the second noise monitoring scan includes performing the second noise monitoring scan on a second plurality of frames at a first frequency, a second frequency, and a third frequency; as well as The second noise data collected from the second noise monitoring scan includes: The second noise data is collected from multiple sensing channels of the second plurality of frames used for the first frequency, the second frequency, and the third frequency; Calculate the first maximum standard deviation for the first frequency, the second maximum standard deviation for the second frequency, and the third maximum standard deviation for the third frequency; and The first maximum standard deviation is determined to be less than the second maximum standard deviation and the third maximum standard deviation.

13. The method of claim 12, further comprising: Before entering the second noise mode, a first mutual scan is performed on the current frame of the touchscreen device; Intensity data is collected from the first mutual scan targeting the current frame; Calculate the current standard deviation of the intensity data for the current frame; The second noise mode further includes: Calculate the difference in standard deviation between the current standard deviation and the first maximum standard deviation; The difference in the standard deviation is compared with the jump threshold; Determine whether the difference in the standard deviation is greater than the jump threshold; and In response to the difference in the standard deviation being greater than the jump threshold, the mutual scanning frequency used for the two or more mutual scans is set to the first frequency; Performing the two or more mutual scans on the same portion of the frame includes: Perform two or more subsequent mutual scans on the same portion of the frame at the set mutual scan frequency; Intensity data is collected from each of the two or more mutual scans; Calculate the average intensity from the intensity data of the two or more mutually scanned samples; and A touch input is reported in response to the calculated average intensity exceeding the touch reporting threshold.

14. An apparatus comprising: touchscreen; as well as The touch controller is configured as follows: Perform a noise monitoring scan on the touchscreen; Noise data is collected from the noise monitoring scan; Determine whether the noise data is greater than a first noise threshold and less than a second noise threshold, or determine whether the noise data is greater than the second noise threshold, where the second noise threshold is greater than the first noise threshold; In response to the noise data being greater than the first noise threshold and less than the second noise threshold, the system operates in a first noise mode to apply a first noise filter. as well as In response to the noise data being greater than the second noise threshold, the system operates in a second noise mode to apply a second noise filter.

15. The device according to claim 14, wherein, When the touch controller operates in the first noise mode, the touch controller is also configured to: Add a touch delay so that the reported touch input is delayed by several frames; Increase the touch reporting threshold; and Touch input is reported based on the touch latency and the touch reporting threshold.

16. The device according to claim 14, wherein, When the touch controller operates in the second noise mode, the touch controller is also configured to: Perform two or more mutual scans on the same portion of the frame on the touchscreen; Intensity data is collected from each of the two or more mutual scans; Calculate the average intensity from the intensity data of the two or more mutually scanned samples; and A touch input is reported in response to the calculated average intensity exceeding the touch reporting threshold.

17. The device according to claim 14, wherein, When the touch controller operates in the second noise mode, the touch controller is also configured to set the mutual scanning frequency based on the noise data from the noise monitoring scan.

18. The device of claim 14, wherein the touch controller is further configured to: The noise monitoring scan is performed on multiple frames at a first frequency, a second frequency, and a third frequency. Collect noise data for the first frequency, the second frequency, and the third frequency; Calculate the first maximum standard deviation for the first frequency, the second maximum standard deviation for the second frequency, and the third maximum standard deviation for the third frequency; as well as The first maximum standard deviation is determined to be less than the second maximum standard deviation and the third maximum standard deviation.

19. The device of claim 18, wherein the touch controller is further configured to: Perform a mutual scan on the current frame of the touchscreen; Intensity data is collected from the mutual scans targeting the current frame; Calculate the current standard deviation of the intensity data for the current frame; Calculate the difference in standard deviation between the current standard deviation and the first maximum standard deviation; Compare the difference between the standard deviation and the jump threshold; Determine whether the difference in the standard deviation is greater than the jump threshold; and In response to the difference in the standard deviation being greater than the jump threshold, the mutual scanning frequency is set to the first frequency.

20. The device according to claim 19, wherein, When the touch controller operates in the second noise mode, the touch controller is also configured to: Perform two or more mutual scans on the same part of the frame at the set mutual scan frequency; Intensity data is collected from each of the two or more mutual scans; Calculate the average intensity from the intensity data of the two or more mutually scanned samples; and A touch input is reported in response to the calculated average intensity exceeding the touch reporting threshold.