Patent Grant
11966540
Computing devices with touch-sensitive displays enable a user to interact with the computer via touch from a stylus or a digit. The touch-sensitive displays are configured for universal use, regardless of user characteristics such as handedness, writing pressure, writing speed, pen tilt, and the like.
To address the issues discussed herein, a computing system is provided. According to one aspect, the computing system includes a touch-sensitive display and one or more processors. The touch-sensitive display is configured to detect a run-time touch input from a user. The one or more processors are configured to execute instructions using portions of associated memory to implement a touch driver of the touch-sensitive display and an artificial intelligence model. The touch driver is configured to process the run-time touch input based at least in part on a plurality of calibration parameters and output a touch event and a plurality of run-time touch input parameters associated with the touch input event. The artificial intelligence model is configured to receive, as input, the run-time touch input parameters. Responsive to receiving the run-time touch input parameters, the artificial intelligence model is configured to output a personalized user touch driver profile including a plurality of updated calibration parameters for the touch driver.
In some configurations, the artificial intelligence model is trained in an initial training phase with a training data set that includes a plurality of training data pairs. Each training data pair may include training phase touch input parameters indicating a characteristic of the touch input and ground truth output indicating calibration parameters for the paired touch input parameters. Training phase touch input parameters from a plurality of users may be interpreted by a clustering algorithm to identify a plurality of user clusters, and each user cluster may define a cohort of users. The training data set used to train the artificial intelligence model may be created from training data examples derived from a cohort of users.
In some configurations, the artificial intelligence model is trained in a feedback training phase. The artificial intelligence model may collect user feedback via an implicit or explicit user feedback interface and perform feedback training based at least in part on the user feedback. The artificial intelligence model may be further configured to adjust internal weights to enhance one or more calibration parameters via a backpropagation algorithm.
In some configurations, the artificial intelligence model includes one or more neural networks. A first neural network of the one or more neural networks may be configured to output an X coordinate offset and a Y coordinate offset of the touch input. When the touch input is performed with a stylus, a second neural network of the one or more neural networks may be configured to output a tilt offset and an azimuth offset of the touch input.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to implementations that solve any or all disadvantages noted in any part of this disclosure.
Several significant challenges exist to the effective implementation of personalized human-computer interactions (HCI) in modern computing systems. Touch input from a stylus or a digit of a user has become a prominent HCI tool. However, a need exists to personalize the HCI and replace generic procedures that produce a single set of touch input parameters regardless of a user's personal preferences or touch input characteristics. Training an artificial intelligence model to recognize user-specific touch input parameters and adapt processing of the touch input accordingly would improve the user experience and lead to an efficient and more natural HCI. Further, tuning the touch input during run-time would provide a consistent user experience, even under conditions of fatigue. Recognizing user-specific touch input parameters at run-time would additionally facilitate calibrating the touch input according to different users of the same computing device, resulting in a smooth transition between users and/or mode of touch input. A computing system with an artificial intelligence model configured to enhance a touch driver operation according to a user's profile and preferences would increase the user's comfort and enhance productivity, both during touch input from a digit or hand of the user, as well as from a stylus. However, heretofore challenges have existed in the development of such a system.
As schematically illustrated in
A touch driver 14 of the touch-sensitive display 12 is stored in an associated memory 16 and implemented by one or more processors 18. In a run-time phase, the touch driver 14 is configured to process the run-time touch input 20 based at least in part on a plurality of calibration parameters 22. The calibration parameters 22 may include, for example, X coordinate and Y coordinate offsets based at least in part on the sensed position of the detected touch input 20 and/or tilt and azimuth offsets based at least in part on a sensed thickness of the detected touch input 20. Upon processing the run-time touch input 20, the touch driver 14 outputs a touch input event 24 and a plurality of run-time touch input parameters 26. The touch input event may be passed to a program 42, which in turn generates display output 44 based thereon. The run-time touch input parameters 26 may be stored in memory as they are gathered over a period of time based at least in part on a series of run-time touch inputs, and may be characteristics associated with each touch input event 24 such as measurements of digit size, handedness, inking smoothness, stroke speed, stutter, latency, accuracy, repeatability, pressure, tilt, and azimuth. The memory 16 further includes an artificial intelligence model that may be implemented as a touch driver enhancer artificial intelligence model 28. The touch driver enhancer artificial intelligence model 28 is configured to receive the run-time touch input parameters 26 and, in response, output a personalized user touch driver profile 30 that is enhanced according to the processed touch input 20 and includes a plurality of updated calibration parameters 32 for the touch driver 14. In one example, the touch driver enhancer artificial intelligence model 28 is configured to optimize the touch driver profile 30 by computing updated calibration parameters 32 that optimize the performance of the touch driver 14. In other examples, the touch driver enhancer artificial intelligence model 28 may be configured to output updated calibration parameters 32 that are an improvement over the original calibration parameters 22, but are not necessarily optimized.
A detailed schematic diagram of the computing system 100 is illustrated in
The touch input event 24 is transferred to an input stack 38, and an input handler 40 sends it to an application program 42. The application program 42 is configured to convert data from the touch input event 24 into a display output 44 that is sent to a display driver 46 to be displayed to the user on the touch-sensitive display 12. As described below, the application program 42 further includes a feedback module 48 configured to communicate data from the touch input event 24 associated with the touch input 20 to the touch driver enhancer artificial intelligence model 28 where it may be used to enhance the touch driver 14 according to characteristics of the user's touch input 20.
The touch input parameters 26 are recorded in a log 50 and sent to a profile module 52 that includes the touch driver enhancer artificial intelligence model 28. As described above with reference to
The profile module 52 further includes a template profile classifier 54 that is configured to receive the run-time touch input parameters 26, classify them according to a plurality of user template profiles, and output a template profile 56 for the user performing the touch input 20. As described in detail below with reference to
The template profile 56 provides a starting point for the calibration parameters 22 used by the touch driver 14 to process the run-time touch input 20. As the touch driver 14 continues to receive and process touch input 20 from the user, the touch driver enhancer artificial intelligence model 28 is configured to receive touch input parameters 26 from the touch driver 14 and output updated calibration parameters 32 included in the personalized user touch driver profile 30 to enhance the user experience during the human-computer interaction.
Turning to
As indicated above, the touch driver enhancer artificial intelligence model 28 is trainable. Accordingly,
The touch driver enhancer artificial intelligence model 28 further includes one or more neural networks 64 that may have an input layer, one or more convolutional layers, one or more fully connected hidden layers, and an output layer. It will be appreciated that the one or more neural networks 64 may be configured to include one or more convolutional layers, one or more fully connected hidden layers, or both one or more convolutional layers and one or more fully connected hidden layers. The input layer includes a plurality of nodes corresponding to the training phase touch input parameters 66, which indicate a characteristic of the training phase touch input 68. The output layer includes a plurality of output nodes corresponding to the ground truth output 72, which indicate training phase calibration parameters 74 for the training data pair 70. Nodes in each layer are linked by weighted associations, and the touch driver enhancer artificial intelligence model 28 is configured to adjust internal weights to enhance one or more of the plurality of calibration parameters 74 via a backpropagation algorithm according to a loss function during training to increase the accuracy of the output nodes during run-time. As described in detail below with reference to
A schematic diagram of the template profile classifier 54 during a run-time phase is shown in
Turning to
As described above with reference to
As shown in the example illustrated in
Additionally or alternatively, the calibration graphic 84 displayed on the touch input calibration GUI 82 during the calibration phase may be configured to assess X coordinate and Y coordinate offsets concurrently with tilt and azimuth offsets. In any implementations of the calibration phase, the explicit user feedback 78 may be processed by the feedback module 48 and sent to the touch driver enhancer artificial intelligence model 28, which outputs the personalized user touch driver profile 30 enhanced according to the explicit user feedback 78, including a plurality of updated calibration parameters 32 for the touch driver 14.
As indicted above and illustrated in
As shown in
An example of the extraction of features 88A for the neural network 64A is shown in
At step 202, the method 200 may comprise detecting a run-time touch input on a touch-sensitive display. The run-time touch input may be received from a digit or a stylus of a user. Accordingly, the touch-sensitive display may be configured as a capacitive touch screen equipped with a plurality of conductive layers. The touch-sensitive display may further include a digitizer layer that enables the computing device to be used with an active stylus, such as a digital pen. The touch input may be detected via sensors, such as touch sensors that detect stimulation of an electrostatic field of the touch-sensitive display and/or sensors in the digitizer layer.
Continuing from step 202 to step 204, the method 200 may include processing the run-time touch input. The touch input may be processed by a touch driver based at least in part on a plurality of calibration parameters. The calibration parameters may include, for example, X coordinate and Y coordinate offsets based at least in part on the sensed position of the detected touch input and/or tilt and azimuth offsets based at least in part on a sensed thickness of the detected touch input.
Proceeding from step 204 to step 206, the method 200 may include outputting a touch input event. The touch input event may be transferred to an input stack, and an input handler may send it to an application program. The application program may be configured to convert data from the touch input event into a display output that is sent to a display driver. Accordingly, advancing from step 206 to step 208, the method 200 may include displaying output to the user on the touch-sensitive display.
After processing the touch input event at step 204, the method 200 may additionally or alternatively continue to step 210. At step 210, the method 200 may include outputting touch input parameters. The touch input parameters may be recorded in a log and sent to a profile module that includes a touch driver enhancer artificial intelligence model.
Continuing from step 210 to step 212, the method 200 may include, receiving, by the touch driver enhancer artificial intelligence model, the run-time touch input parameters. The run-time touch input parameters may be characteristics associated with the touch input event, such as measurements of digit size, handedness, inking smoothness, stroke speed, stutter, latency, accuracy, repeatability, pressure, tilt, and azimuth, for example.
Proceeding from step 212 to 214, the method 200 may include outputting, by the touch driver enhancer artificial intelligence model, a personalized user touch driver profile. The personalized user touch driver profile be based at least in part on the run-time touch input parameters associated with the user's touch input, and may include updated calibration parameters. The updated calibration parameters may be sent to the touch driver such that the touch driver may be updated with the personalized user touch driver profile.
In some implementations, the application program may include a feedback module. As such, after outputting the touch input event at step 206, the method 200 may include collecting user feedback at step 216. The feedback module may be configured to collect user feedback and communicate user feedback associated with the touch input to the touch driver enhancer artificial intelligence model where it may be used to enhance the touch driver according to characteristics of the user's touch input.
At step 302, the method 300 may comprise receiving training phase touch input parameters from a plurality of users. Touch input parameters may be characteristics associated with touch input, such as measurements of digit size, handedness, inking smoothness, stroke speed, stutter, latency, accuracy, repeatability, pressure, tilt, and azimuth, for example. These parameters may be collected from a plurality of users to be processed for training the artificial intelligence model.
Continuing from step 302 to step 304, the method 300 may include interpreting the training phase touch input parameters. The training phase touch input parameters may be interpreted with a clustering algorithm.
Proceeding from step 304 to step 306, the method 300 may include identifying a plurality of user clusters. Touch input parameters from the plurality of users may be grouped by like characteristics by the clustering algorithm to identify user clusters. As such, each user cluster may define a cohort of users having similar training phase touch input parameters. For example, the cohorts may be clustered according to similarities detected in digit size, handedness, inking smoothness, stroke speed, stutter, latency, accuracy, repeatability, pressure, tilt, and/or azimuth.
Advancing from step 306 to step 308, the method 300 may include training the artificial intelligence model with training data sets derived from the user clusters. The training data sets may include a plurality of training data pairs from a cohort of training data examples derived from respective a cohort of users, i.e., a user cluster identified via the clustering algorithm. Each training data pair may include training phase touch input parameters and ground truth output.
Continuing from step 308 to step 310, the method 300 may include creating a template profile with calibration parameters for each user cluster. Template profiles are created for each cohort of users, with each template profile including calibration parameters associated with a respective cohort. A plurality of template profiles may be communicated to a template profile classifier, which determines a template profile for the touch driver at run-time based at least in part on the touch input parameters of a user's touch input. The template profile provides a starting point for the calibration parameters used by the touch driver to process the run-time touch input such that a personalized user touch driver profile may be created.
In some embodiments, the methods and processes described herein may be tied to a computing system of one or more computing devices. In particular, such methods and processes may be implemented as a computer application program or service, an application-programming interface (API), a library, and/or other computer program product.
Computing system 900 includes a logic processor 902 volatile memory 904, and a non-volatile storage device 906. Computing system 900 may optionally include a display subsystem 908, input subsystem 910, communication subsystem 912, and/or other components not shown in
Logic processor 902 includes one or more physical devices configured to execute instructions. For example, the logic processor may be configured to execute instructions that are part of one or more applications, programs, routines, libraries, objects, components, data structures, or other logical constructs. Such instructions may be implemented to perform a task, implement a data type, transform the state of one or more components, achieve a technical effect, or otherwise arrive at a desired result.
The logic processor may include one or more physical processors (hardware) configured to execute software instructions. Additionally or alternatively, the logic processor may include one or more hardware logic circuits or firmware devices configured to execute hardware-implemented logic or firmware instructions. Processors of the logic processor 902 may be single-core or multi-core, and the instructions executed thereon may be configured for sequential, parallel, and/or distributed processing. Individual components of the logic processor optionally may be distributed among two or more separate devices, which may be remotely located and/or configured for coordinated processing. Aspects of the logic processor may be virtualized and executed by remotely accessible, networked computing devices configured in a cloud-computing configuration. In such a case, these virtualized aspects are run on different physical logic processors of various different machines, it will be understood.
Non-volatile storage device 906 includes one or more physical devices configured to hold instructions executable by the logic processors to implement the methods and processes described herein. When such methods and processes are implemented, the state of non-volatile storage device 906 may be transformed, e.g., to hold different data.
Non-volatile storage device 906 may include physical devices that are removable and/or built-in. Non-volatile storage device 906 may include optical memory (e.g., CD, DVD, HD-DVD, Blu-Ray Disc, etc.), semiconductor memory (e.g., ROM, EPROM, EEPROM, FLASH memory, etc.), and/or magnetic memory (e.g., hard-disk drive, floppy-disk drive, tape drive, MRAM, etc.), or other mass storage device technology. Non-volatile storage device 906 may include nonvolatile, dynamic, static, read/write, read-only, sequential-access, location-addressable, file-addressable, and/or content-addressable devices. It will be appreciated that non-volatile storage device 906 is configured to hold instructions even when power is cut to the non-volatile storage device 906.
Volatile memory 904 may include physical devices that include random access memory. Volatile memory 904 is typically utilized by logic processor 902 to temporarily store information during processing of software instructions. It will be appreciated that volatile memory 904 typically does not continue to store instructions when power is cut to the volatile memory 904.
Aspects of logic processor 902, volatile memory 904, and non-volatile storage device 906 may be integrated together into one or more hardware-logic components. Such hardware-logic components may include field-programmable gate arrays (FPGAs), program- and application-specific integrated circuits (PASIC/ASICs), program- and application-specific standard products (PSSP/ASSPs), system-on-a-chip (SOC), and complex programmable logic devices (CPLDs), for example.
The terms “module,” “program,” and “engine” may be used to describe an aspect of computing system 900 typically implemented in software by a processor to perform a particular function using portions of volatile memory, which function involves transformative processing that specially configures the processor to perform the function. Thus, a module, program, or engine may be instantiated via logic processor 902 executing instructions held by non-volatile storage device 906, using portions of volatile memory 904. It will be understood that different modules, programs, and/or engines may be instantiated from the same application, service, code block, object, library, routine, API, function, etc. Likewise, the same module, program, and/or engine may be instantiated by different applications, services, code blocks, objects, routines, APIs, functions, etc. The terms “module,” “program,” and “engine” may encompass individual or groups of executable files, data files, libraries, drivers, scripts, database records, etc.
When included, display subsystem 908 may be used to present a visual representation of data held by non-volatile storage device 906. The visual representation may take the form of a graphical user interface (GUI). As the herein described methods and processes change the data held by the non-volatile storage device, and thus transform the state of the non-volatile storage device, the state of display subsystem 908 may likewise be transformed to visually represent changes in the underlying data. Display subsystem 908 may include one or more display devices utilizing virtually any type of technology. Such display devices may be combined with logic processor 902, volatile memory 904, and/or non-volatile storage device 906 in a shared enclosure, or such display devices may be peripheral display devices.
When included, input subsystem 910 may comprise or interface with one or more user-input devices such as a keyboard, mouse, touch screen, or game controller. In some embodiments, the input subsystem may comprise or interface with selected natural user input (NUI) componentry. Such componentry may be integrated or peripheral, and the transduction and/or processing of input actions may be handled on- or off-board. Example NUI componentry may include a microphone for speech and/or voice recognition; an infrared, color, stereoscopic, and/or depth camera for machine vision and/or gesture recognition; a head tracker, eye tracker, accelerometer, and/or gyroscope for motion detection and/or intent recognition; as well as electric-field sensing componentry for assessing brain activity; and/or any other suitable sensor.
When included, communication subsystem 912 may be configured to communicatively couple various computing devices described herein with each other, and with other devices. Communication subsystem 912 may include wired and/or wireless communication devices compatible with one or more different communication protocols. As non-limiting examples, the communication subsystem may be configured for communication via a wireless telephone network, or a wired or wireless local- or wide-area network, such as a HDMI over Wi-Fi connection. In some embodiments, the communication subsystem may allow computing system 900 to send and/or receive messages to and/or from other devices via a network such as the Internet.
The following paragraphs provide additional description of aspects of the present disclosure. One aspect provides a computing system for enhancing a touch driver operation. The computing system may comprise a touch-sensitive display and one or more processors. The touch-sensitive display may be configured to detect a run-time touch input from a user. The one or more processors may be configured to execute instructions using portions of associated memory to implement a touch driver of the touch-sensitive display and an artificial intelligence model. The touch driver of the touch-sensitive display may be configured to process the run-time touch input based at least in part on a plurality of calibration parameters, and output a touch input event and a plurality of run-time touch input parameters associated with the touch input event. The artificial intelligence model may be configured to receive, as input, the run-time touch input parameters. Responsive to receiving the run-time touch input parameters, the artificial intelligence model may output a personalized user touch driver profile including a plurality of updated calibration parameters for the touch driver.
In this aspect, additionally or alternatively, in an initial training phase, the one or more processors may be configured to receive training phase touch input parameters from a plurality of users, and instruct a clustering algorithm to interpret the training phase touch input parameters and identify a plurality of user clusters, each user cluster defining a cohort of users.
In this aspect, additionally or alternatively, the artificial intelligence model may have been trained in the initial training phase with a training data set including a plurality of training data pairs from a cohort of training data examples derived from a cohort of users. Each training data pair may include training phase touch input parameters indicating a characteristic of the touch input and ground truth output indicating calibration parameters for the paired touch input parameters. In this aspect, additionally or alternatively, the one or more processors may be configured to create a template profile for each cohort of users. Each template profile may include calibration parameters associated with a respective cohort.
In this aspect, additionally or alternatively, in a run-time phase, the one or more processors may be configured to perform cluster analysis on the run-time touch input parameters to determine the cohort of users with which the user is associated, and set the calibration parameters for the personalized user touch driver profile according to the calibration parameters included in the template profile associated with the determined cohort of users.
In this aspect, additionally or alternatively, in a feedback training phase, the artificial intelligence model may be configured to collect user feedback via an implicit or explicit user feedback interface, and perform feedback training of the artificial intelligence model based at least in part on the user feedback. In this aspect, additionally or alternatively, the artificial intelligence model may be configured to adjust internal weights to enhance one or more of the plurality of calibration parameters via a backpropagation algorithm.
In this aspect, additionally or alternatively, the touch input parameters may be recorded as raw input values for user touch input on the touch-sensitive display, and touch input features may be extracted from the raw input values.
In this aspect, additionally or alternatively, the artificial intelligence model may include one or more neural networks. In this aspect, additionally or alternatively, a first neural network of the one or more neural networks may be configured to output an X coordinate offset and a Y coordinate offset of the touch input. In this aspect, additionally or alternatively, a second neural network of the one or more neural networks may be configured to output a tilt offset and an azimuth offset of the touch input.
In this aspect, additionally or alternatively, the touch input may be performed with a stylus or one or more digits of the user. In this aspect, additionally or alternatively, the characteristic of the touch input may be associated with at least one of digit size, handedness, inking smoothness, stroke speed, stutter, latency, accuracy, repeatability, pressure, tilt, and azimuth.
Another aspect provides a computing method for enhancing a touch driver operation. The method may comprise, at one or more processors of a computing system including a touch-sensitive display configured to detect a run-time touch input from a user, processing the run-time touch input based at least in part on a plurality of calibration parameters. The method may further include outputting a touch input event and a plurality of run-time touch input parameters associated with the touch input event. The method may further include receiving, as input for an artificial intelligence model, the run-time touch input parameters. Responsive to receiving the run-time touch input parameters, the method may further include outputting, by the artificial intelligence model, a personalized user touch driver profile including a plurality of updated calibration parameters for a touch driver of the touch-sensitive display.
In this aspect, additionally or alternatively, the method may further comprise, in an initial training phase, receiving training phase touch input parameters from a plurality of users, and instructing a clustering algorithm to interpret the training phase touch input parameters and identify a plurality of user clusters, each user cluster defining a cohort of users.
In this aspect, additionally or alternatively, the method may further comprise, in the initial training phase, training the artificial intelligence model with a training data set including a plurality of training data pairs from a cohort of training data examples derived from a cohort of users. Each training data pair may include training phase touch input parameters indicating a characteristic of the touch input and ground truth output indicating calibration parameters for the paired touch input parameters.
In this aspect, additionally or alternatively, the method may further comprise creating a template profile for each cohort of users. Each template profile may include calibration parameters associated with a respective cohort.
In this aspect, additionally or alternatively, the method may further comprise, in a run-time phase, performing cluster analysis on the run-time touch input parameters to determine the cohort of users with which the user is associated, and setting the calibration parameters for the personalized user touch driver profile according to the calibration parameters included in the template profile associated with the determined cohort of users.
In this aspect, additionally or alternatively, the method may further comprise, in a feedback training phase, collecting user feedback via an implicit or explicit user feedback interface, and performing feedback training of the artificial intelligence model based at least in part on the user feedback.
Another aspect provides a computing system for enhancing a touch driver operation. The computing system may comprise a touch-sensitive display and one or more processors. The touch-sensitive display may be configured to detect a run-time touch input from a user. The one or more processors may be configured to execute instructions using portions of associated memory to implement a touch driver of the touch-sensitive display and an artificial intelligence model. The touch driver of the touch-sensitive display may be configured to process the run-time touch input based at least in part on a plurality of calibration parameters, and output a touch input event and a plurality of run-time touch input parameters associated with the touch input event. The artificial intelligence model may be configured to receive, as input, the run-time touch input parameters. Responsive to receiving the run-time touch input parameters, the artificial intelligence model may output a personalized user touch driver profile including a plurality of updated calibration parameters for the touch driver. The artificial intelligence model may include a first neural network configured to output an X coordinate offset and a Y coordinate offset of the touch input. The artificial intelligence model may further include a second neural network configured to output a tilt offset and an azimuth offset of the touch input. In a feedback training phase, the artificial intelligence model may be configured to collect user feedback via an implicit or explicit user feedback interface, and perform feedback training of the artificial intelligence model based at least in part on the user feedback.
It will be understood that the configurations and/or approaches described herein are exemplary in nature, and that these specific embodiments or examples are not to be considered in a limiting sense, because numerous variations are possible. The specific routines or methods described herein may represent one or more of any number of processing strategies. As such, various acts illustrated and/or described may be performed in the sequence illustrated and/or described, in other sequences, in parallel, or omitted. Likewise, the order of the above-described processes may be changed.
The subject matter of the present disclosure includes all novel and non-obvious combinations and sub-combinations of the various processes, systems and configurations, and other features, functions, acts, and/or properties disclosed herein, as well as any and all equivalents thereof.
This application is a continuation of U.S. patent application Ser. No. 17/323,757, filed May 18, 2021, the entirety of which is hereby incorporated herein by reference for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 8436821 | Plichta | May 2013 | B1 |
| 9075464 | Mankowski | Jul 2015 | B2 |
| 9286482 | Dumont | Mar 2016 | B1 |
| 10650290 | Singh | May 2020 | B2 |
| 11526235 | Livny | Dec 2022 | B1 |
| 20080165141 | Christie | Jul 2008 | A1 |
| 20110314427 | Sundararajan | Dec 2011 | A1 |
| 20120007821 | Zaliva | Jan 2012 | A1 |
| 20120162111 | Lee | Jun 2012 | A1 |
| 20120319948 | Kim | Dec 2012 | A1 |
| 20130120298 | Zhou | May 2013 | A1 |
| 20140143404 | Kennedy | May 2014 | A1 |
| 20140247251 | Zhang | Sep 2014 | A1 |
| 20150066762 | Chatterton | Mar 2015 | A1 |
| 20150094127 | Canose | Apr 2015 | A1 |
| 20150286338 | Zhang | Oct 2015 | A1 |
| 20160140623 | Gupta | May 2016 | A1 |
| 20170230363 | Deutschmann | Aug 2017 | A1 |
| 20180150280 | Rhee | May 2018 | A1 |
| 20180181245 | Beck | Jun 2018 | A1 |
| 20180224958 | Sadahiro | Aug 2018 | A1 |
| 20180239526 | Varanasi | Aug 2018 | A1 |
| 20180253209 | Jaygarl | Sep 2018 | A1 |
| 20190069154 | Booth | Feb 2019 | A1 |
| 20190370617 | Singh | Dec 2019 | A1 |
| 20200027554 | Boroczky | Jan 2020 | A1 |
| 20200234198 | Feng | Jul 2020 | A1 |
| 20200252214 | Cheng | Aug 2020 | A1 |
| 20200257847 | El-Rayes | Aug 2020 | A1 |
| 20210011592 | Liu | Jan 2021 | A1 |
| 20210217406 | Jang | Jul 2021 | A1 |
| 20220076385 | K S | Mar 2022 | A1 |
| 20230103621 | Livny | Apr 2023 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20230103621 A1 | Apr 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17323757 | May 2021 | US |
| Child | 18064114 | US |
