Embodiments of the subject matter described herein relate generally to computer systems, and more particularly to the prediction of field values for fields in a form on a computer system.
Many forms are filled out via computer systems. The forms may be configured to capture information about some other document, file, observation, and others. The forms may exist on computer systems and may be generated by application programs on a computer system. A system that could analyze the document, file, observation, etc. that the form is configured to capture information regarding would be advantageous and could improve production.
A more complete understanding of the subject matter may be derived by referring to the detailed description and claims when considered in conjunction with the following figures, wherein like reference numbers refer to similar elements throughout the figures.
The following disclosure provides many different embodiments, or examples, for implementing different features of the provided subject matter. The following detailed description is merely exemplary in nature and is not intended to limit the invention or the application and uses of the invention. Furthermore, there is no intention to be bound by any theory presented in the preceding background or the following detailed description.
As used herein, the term “module” refers to any hardware, software, firmware, electronic control component, processing logic, and/or processor device, individually or in any combination, including without limitation: application specific integrated circuit (ASIC), a field-programmable gate-array (FPGA), an electronic circuit, a processor (shared, dedicated, or group) and memory that executes one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality.
Disclosed herein are systems, apparatus, methods and techniques for predicting field values for preselected fields based on confidence levels in an analyzed dataset. In one example, a predictive model is trained using a pre-existing data set to predict field values for preselected fields from objects contained in the data set. A confidence function is calculated for the preselected fields. A user is provided an option to review the confidence function. The user is provided the option to select a proposed confidence threshold level that is based on the confidence function or to select a different confidence threshold level after reviewing the confidence function. In operation with a new object, the predictive model may predict field values for the preselected fields and a confidence level for the predictions. When a prediction has a confidence level that meets or exceeds a confidence level threshold, the predictive model may designate the prediction as a recommended field value.
The example prediction system 101 includes a prediction module 103 and a model generation module 106. The example prediction module 103 includes a predictive model 104 and a GUI module 105. The example predictive model 104 is configured to analyze a new object received by the example CRM application 102, predict a likely field value for one or more user selected fields within the form generated by the example CRM application 102 based on the object analysis, provide the predicted field values to the example CRM application 102, and calculate a predicted confidence level for each predicted field value. The example model generation module 106 is configured to train the predictive model 104 using machine learning techniques and in accordance with user selected preferences.
The example prediction system 101 is implemented by a controller. The controller includes at least one processor and a computer-readable storage device or media. The processor may be any custom-made or commercially available processor, a central processing unit (CPU), a graphics processing unit (GPU), an application specific integrated circuit (ASIC) (e.g., a custom ASIC implementing a neural network), a field programmable gate array (FPGA), an auxiliary processor among several processors associated with the controller, a semiconductor-based microprocessor (in the form of a microchip or chip set), any combination thereof, or generally any device for executing instructions. The computer readable storage device or media may include volatile and nonvolatile storage in read-only memory (ROM), random-access memory (RAM), and keep-alive memory (KAM), for example. KAM is a persistent or non-volatile memory that may be used to store various operating variables while the processor is powered down. The computer-readable storage device or media may be implemented using any of a number of known memory devices such as PROMs (programmable read-only memory), EPROMs (electrically PROM), EEPROMs (electrically erasable PROM), flash memory, or any other electric, magnetic, optical, or combination memory devices capable of storing data, some of which represent executable instructions, used by the controller in implementing the example prediction system 101.
The instructions may include one or more separate programs, each of which comprises an ordered listing of executable instructions for implementing logical functions. The instructions, when executed by the processor, receive and process data, perform logic, calculations, methods and/or algorithms for implementing the example prediction system 101.
It will be appreciated that while this exemplary embodiment is described in the context of a fully functioning computer system, those skilled in the art will recognize that the mechanisms of the present disclosure are capable of being distributed as a program product with one or more types of non-transitory computer-readable signal bearing media used to store the program and the instructions thereof and carry out the distribution thereof, such as a non-transitory computer readable medium bearing the program and containing computer instructions stored therein for causing a computer processor to perform and execute the program. Such a program product may take a variety of forms, and the present disclosure applies equally regardless of the particular type of computer-readable signal bearing media used to carry out the distribution. Examples of signal bearing media include: recordable media such as floppy disks, hard drives, memory cards and optical disks, and transmission media such as digital and analog communication links. It will be appreciated that cloud-based storage and/or other techniques may also be utilized in certain embodiments.
The example model generation module 106 includes a GUI module 108 and a training module 110. The example GUI module 108 is configured to provide a user interface for user selection of options for operation of the prediction module 103. The example training module 110 is configured to train the predictive model 104 using reinforced learning and/or other machine learning techniques.
The example GUI module 108 is configured to provide a user interface for user selection of the one or more user selected fields within the example CRM application 102. The user is provided a user interface that allows the user to indicate a desire to select one or more fields within the example CRM application for which predicted field values will be provided.
Depicted in
Depicted in
The example training module 110 in the example model generation module 106 is configured to train the prediction model 104 after user selection of fields for prediction. Depicted in
During the training phase, the example training module 110 is also configured to determine, for each user selected field based on the analysis, a confidence function for the predictive model 104. The example training module 110 is configured to determine the confidence function by testing the accuracy of predictions from the predictive model 104. The example confidence function identifies the percentage of field values for a field that were predicted correctly by the trained predictive model 104 at different applied confidence levels, the percentage of field values for the field that were predicted incorrectly by the trained predictive model 104 at different applied confidence levels, and the percentage of cases for a field in which the trained predictive model 104 could not provide a prediction at different applied confidence levels.
The example GUI module 108 is configured to provide a user interface for user review of the confidence function for a user selected field and for user selection of a confidence threshold level to be used with the predictive model 104 for the user selected field. Depicted in
Depicted in
The example model generation module 106 is also configured to provide, for user selection via the user interface, an option for the predictive model 104 to identify a predicted field value as a best recommendation. Also depicted in
The example model generation module 106 is configured to provide an option, via the user interface, to activate the prediction module 103 for use with the example CRM application 102. As an example, as depicted in the example of
When activated for use with the example CRM application 102 and the example CRM application 102 receives a new object, the example prediction module 103 is configured to provide a user option via a user interface provided by the example GUI module 105 to select to receive predicted field values for the user selected fields. When the user option has been selected, the example predictive model 104 is configured to predict field values for the user selected fields based on content in the new object and the example GUI module 105 is configured to automatically enter predicted field values in user selected fields or present the user with predicted field value options for selection depending on prior user selection.
The example process 700 includes providing a user interface for user selection of the one or more user selected fields within the example CRM application (operation 702). This may be provided via a graphical user interface module 108 in a model generation module 106.
The example process 700 includes analyzing a pre-existing, user provided data set of objects for relationships between the one or more user selected fields and content in the objects in the data set (e.g., content in the title and body of message objects) (operation 704). This may be performed via a training module 110 in a model generation module 106.
The example process 700 includes training, based on the analysis, the predictive model (operation 706). This may be performed via a training module 110 in a model generation module 106.
The example process 700 includes determining, for each user selected field based on the analysis, a confidence function for the predictive model that identifies the percentage of cases predicted correctly at different applied confidence levels, the percentage of cases predicted incorrectly at different applied confidence levels, and the percentage of cases in which the prediction model could not provide a prediction at different applied confidence levels (operation 708). This may be performed via a training module 110 in a model generation module 106.
The example process 700 includes providing a user interface for user review of the confidence function for a user selected field and for user selection of a confidence threshold level to be used with the predictive model for the user selected field (operation 710). This may be performed via a GUI module 108 in a model generation module 106.
The chipset 812 is usually located on a motherboard and is a set of electronic components (e.g., in an integrated circuit) that interconnects and manages the data flow between the processing system(s) 802 and other elements of the computer system and connected peripherals. For instance, the chipset 812 provides an interface between the processing system(s) 802 and the main memory 804, and also includes functionality for providing network connectivity through the NID 810, such as a gigabit Ethernet adapter. The chipset 812 typically contains the processor bus interface (also known as a front-side bus), memory controllers, bus controllers, I/O controllers, etc.
Processing system(s) 802 represents one or more general-purpose processing devices such as a microprocessor, central processing unit, or the like. More particularly, the processing system(s) 802 may be a complex instruction set computing (CISC) microprocessor, reduced instruction set computing (RISC) microprocessor, very long instruction word (VLIW) microprocessor, or a processor implementing other instruction sets or processors implementing a combination of instruction sets. The processing system(s) 802 may also be one or more special-purpose processing devices such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), network processor, or the like.
The processing system(s) 802 can include one or more central processing units (CPUs) that operate in conjunction with the chipset 812. The processing system(s) 802 perform arithmetic and logical operations necessary for the operation of the example computer system.
The NID 810 is capable of connecting the example computer system to other computers over a network. The network can be an Ethernet or Gigabyte Ethernet LAN, a fiber ring, a fiber star, wireless, optical, satellite, a WAN, a MAN, or any other network technology, topology, protocol, or combination thereof.
Input system(s) 816 (or input device(s)) allow a user to input information to the computer system and can include things such as a keyboard, a mouse or other cursor pointing device, a pen, a voice input device, a touch input device, a webcam device, a microphone, etc. Output system(s) 818 (or output device(s)) present information to the user of the computer system and can include things such as a display, monitor, speakers, or the like.
The chipset 812 can provide an interface to various forms of computer-readable storage media including a main memory 804 (e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM)), and hard disk 813. The processing system(s) 802 can communicate with the various forms of computer-readable storage media via the chipset 812 and appropriate buses.
A hard disk 813 is a form of non-volatile memory that can store an operating system (OS) 814. The operating system 814 is software that is copied into RAM and executed by the processing system(s) 802 to control the operation of the example computer system, manage computer hardware and software resources, and provide common services for computer programs executed by the processing system(s) 802. Regardless of the implementation, the operating system 814 includes many different “components” that make the different parts of the example computer system work together. The disk controller 815 is the controller circuit which enables the processing system 802 to communicate with a hard disk 813, and provides an interface between the hard disk 813 and the bus connecting it to the rest of the system.
The main memory 804 may be composed of many different types of memory components. The main memory 804 can include non-volatile memory (such as read-only memory (ROM) 806, flash memory, etc.), volatile memory (such as random access memory (RAM) 808), or some combination of the two. The RAM 808 can be any type of suitable random access memory including the various types of dynamic random access memory (DRAM) such as SDRAM, the various types of static RAM (SRAM). The main memory 804 (as well as the processing system(s) 802) may be distributed throughout the example computer system.
The ROM 806 of the main memory 804 can be used to store firmware that includes program code containing the basic routines that help to start up the example computer system and to transfer information between elements within the example computer system. The ROM of the main memory 804 may also store other software components necessary for the operation of the example computer system.
The RAM 808 stores programs/instructions 830 or executable code for one or more programs 834 that can be loaded and executed at processing system(s) 802 to perform various functions. The programs/instructions 830 are computer readable program code that can be stored in RAM 808 (or other a non-transitory computer readable medium of the example computer system) that can be read and executed by processing system(s) 802 to perform various acts, tasks, functions, and steps as described herein. The methods and techniques described herein can be captured in programming instructions 830 for execution by the processing system 802 to cause the example computer system to perform the described methods, processes, and techniques.
In one embodiment, a prediction system is provided. The prediction system is configured to offer recommended field values based on an analyzed data set. The prediction system comprises a processor configured by programming instructions encoded in non-transient computer readable media. The prediction system is configurable to: provide a user interface for user selection of one or more fields within an application for which to automatically predict a field value; analyze a user provided data set of objects for relationships between the user selected one or more fields and content in the objects in the data set; train, based on the analysis, a predictive model configured to predict a likely field value for each of the user selected one or more fields when the application receives a new object and further configured to calculate a predicted confidence level for each predicted likely field value; determine, for each user selected field based on the analysis, a confidence function for the predictive model that identifies the percentage of cases predicted correctly at different applied confidence levels, the percentage of cases predicted incorrectly at different applied confidence levels, and the percentage of cases in which the prediction model could not provide a prediction at different applied confidence levels; provide a user interface for user review of the confidence function for a user selected field and for user selection of a confidence threshold level to be used with the predictive model for the user selected field; and analyze an object received by the application using the predictive model and provide to the application predicted field values for user selected based on the confidence threshold level.
These aspects and other embodiments may include one or more of the following features. The application may provide user-selectable field value choices for the fields and wherein the user-selectable field value choices are selected via a picklist, lookup or checkbox. The model generation module may be configured to provide, for user selection via the user interface, an option for the predictive model to identify a predicted field value as a best recommendation. The confidence threshold level may be used to determine the best recommendation, wherein predicted field values determined by the predictive model that have an associated confidence level that is below the confidence threshold level will not be recommended as a best recommendation and predicted field values determined by the predictive model that have an associated confidence level that is equal to or above the confidence threshold level will be recommended by the predictive model as a best recommendation via a visual indication. The model generation module may be configured to provide an option, for user selection via the user interface, for the predictive model to automatically apply the best recommendation as a field value without user confirmation of the application of the best recommendation as a field value. The model generation module may be configured to recommend the confidence threshold level. The model generation module may be configured to provide an option, via the user interface, to activate the predictive model for use with the application.
In another embodiment, a computing system is provided. The computing system comprises an application configured for use in analyzing customer objects; a predictive model configurable to analyze an object received by the application, predict a likely field value for one or more user selected fields within the application based on the object analysis, provide the predicted field values to the application, and calculate a predicted confidence level for each predicted field value; and a model generation module. The model generation module is configured to: provide a user interface for user selection of the one or more user selected fields within the application; analyze a pre-existing, user provided data set of objects for relationships between the one or more user selected fields and content in the objects in the data set (e.g., content in the title and body of message objects); train, based on the analysis, the predictive model; determine, for each user selected field based on the analysis, a confidence function for the predictive model that identifies the percentage of cases predicted correctly at different applied confidence levels, the percentage of cases predicted incorrectly at different applied confidence levels, and the percentage of cases in which the prediction model could not provide a prediction at different applied confidence levels; and provide a user interface for user review of the confidence function for a user selected field and for user selection of a confidence threshold level to be used with the predictive model for the user selected field.
These aspects and other embodiments may include one or more of the following features. The application may provide user-selectable field value choices for the fields and wherein the user-selectable field value choices are selected via a picklist, lookup or checkbox. The model generation module may be configured to provide, for user selection via the user interface, an option for the predictive model to identify a predicted field value as a best recommendation. The confidence threshold level may be used to determine the best recommendation, wherein predicted field values determined by the predictive model that have an associated confidence level that is below the confidence threshold level will not be recommended as a best recommendation and predicted field values determined by the predictive model that have an associated confidence level that is equal to or above the confidence threshold level will be recommended by the predictive model as a best recommendation via a visual indication. The model generation module may be configured to provide an option, for user selection via the user interface, for the predictive model to automatically apply the best recommendation as a field value without user confirmation of the application of the best recommendation as a field value. The model generation module may be configured to recommend the confidence threshold level. The model generation module may be configured to provide an option, via the user interface, to activate the predictive model for use with the application.
In another embodiment, a method of training a predictive model to predict a likely field value for one or more user selected fields within an application is provided. The method comprises: providing a user interface for user selection of the one or more user selected fields within the application; analyzing a pre-existing, user provided data set of objects for relationships between the one or more user selected fields and content in the objects in the data set (e.g., content in the title and body of message objects); training, based on the analysis, the predictive model; determining, for each user selected field based on the analysis, a confidence function for the predictive model that identifies the percentage of cases predicted correctly at different applied confidence levels, the percentage of cases predicted incorrectly at different applied confidence levels, and the percentage of cases in which the prediction model could not provide a prediction at different applied confidence levels; and providing a user interface for user review of the confidence function for a user selected field and for user selection of a confidence threshold level to be used with the predictive model for the user selected field.
These aspects and other embodiments may include one or more of the following features. The method may further comprise providing, for user selection via the user interface, an option for the predictive model to identify a predicted field value as a best recommendation. The method may further comprise applying the confidence threshold level to determine the best recommendation, wherein predicted field values determined by the predictive model that have an associated confidence level that is below the confidence threshold level will not be recommended as a best recommendation and predicted field values determined by the predictive model that have an associated confidence level that is equal to or above the confidence threshold level will be recommended by the predictive model as a best recommendation via a visual indication. The method may further comprise providing an option, for user selection via the user interface, for the predictive model to automatically apply the best recommendation as a field value without user confirmation of the application of the best recommendation as a field value. The method may further comprise automatically recommending the confidence threshold level. The method may further comprise providing an option, via the user interface, to activate the predictive model for use with the application.
The foregoing description is merely illustrative in nature and is not intended to limit the embodiments of the subject matter or the application and uses of such embodiments. Furthermore, there is no intention to be bound by any expressed or implied theory presented in the technical field, background, or the detailed description. As used herein, the word “exemplary” or “example” means “serving as an example, instance, or illustration.” Any implementation described herein as exemplary is not necessarily to be construed as preferred or advantageous over other implementations, and the exemplary embodiments described herein are not intended to limit the scope or applicability of the subject matter in any way.
For the sake of brevity, conventional techniques related to object models, web pages, cloud computing, on-demand applications, and other functional aspects of the systems (and the individual operating components of the systems) may not be described in detail herein. In addition, those skilled in the art will appreciate that embodiments may be practiced in conjunction with any number of system and/or network architectures, data transmission protocols, and device configurations, and that the system described herein is merely one suitable example. Furthermore, certain terminology may be used herein for the purpose of reference only, and thus is not intended to be limiting. For example, the terms “first,” “second” and other such numerical terms do not imply a sequence or order unless clearly indicated by the context.
Embodiments of the subject matter may be described herein in terms of functional and/or logical block components, and with reference to symbolic representations of operations, processing tasks, and functions that may be performed by various computing components or devices. Such operations, tasks, and functions are sometimes referred to as being computer-executed, computerized, software-implemented, or computer-implemented. In practice, one or more processing systems or devices can carry out the described operations, tasks, and functions by manipulating electrical signals representing data bits at accessible memory locations, as well as other processing of signals. The memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to the data bits. It should be appreciated that the various block components shown in the figures may be realized by any number of hardware, software, and/or firmware components configured to perform the specified functions. For example, an embodiment of a system or a component may employ various integrated circuit components, e.g., memory elements, digital signal processing elements, logic elements, look-up tables, or the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices. When implemented in software or firmware, various elements of the systems described herein are essentially the code segments or instructions that perform the various tasks. The program or code segments can be stored in a processor-readable medium or transmitted by a computer data signal embodied in a carrier wave over a transmission medium or communication path. The “processor-readable medium” or “machine-readable medium” may include any non-transitory medium that can store or transfer information. Examples of the processor-readable medium include an electronic circuit, a semiconductor memory device, a ROM, a flash memory, an erasable ROM (EROM), a floppy diskette, a CD-ROM, an optical disk, a hard disk, a fiber optic medium, a radio frequency (RF) link, or the like. The computer data signal may include any signal that can propagate over a transmission medium such as electronic network channels, optical fibers, air, electromagnetic paths, or RF links. The code segments may be downloaded via computer networks such as the Internet, an intranet, a LAN, or the like. In this regard, the subject matter described herein can be implemented in the context of any computer-implemented system and/or in connection with two or more separate and distinct computer-implemented systems that cooperate and communicate with one another.
While at least one exemplary embodiment has been presented, it should be appreciated that a vast number of variations exist. It should also be appreciated that the exemplary embodiment or embodiments described herein are not intended to limit the scope, applicability, or configuration of the claimed subject matter in any way. Rather, the foregoing detailed description will provide those skilled in the art with a convenient road map for implementing the described embodiment or embodiments. It should be understood that various changes can be made in the function and arrangement of elements without departing from the scope defined by the claims, which includes known equivalents and foreseeable equivalents at the time of filing this patent application. Accordingly, details of the exemplary embodiments or other limitations described above should not be read into the claims absent a clear intention to the contrary.
This application claims the benefit of U.S. Provisional Application No. 62/735,813 filed Sep. 24, 2018, and incorporates this prior application into the present application by reference.
Number | Name | Date | Kind |
---|---|---|---|
5577188 | Zhu | Nov 1996 | A |
5608872 | Schwartz et al. | Mar 1997 | A |
5649104 | Carleton et al. | Jul 1997 | A |
5715450 | Ambrose et al. | Feb 1998 | A |
5761419 | Schwartz et al. | Jun 1998 | A |
5819038 | Carleton et al. | Oct 1998 | A |
5821937 | Tonelli et al. | Oct 1998 | A |
5831610 | Tonelli et al. | Nov 1998 | A |
5873096 | Lim et al. | Feb 1999 | A |
5918159 | Fomukong et al. | Jun 1999 | A |
5963953 | Cram et al. | Oct 1999 | A |
6092083 | Brodersen et al. | Jul 2000 | A |
6161149 | Achacoso et al. | Dec 2000 | A |
6169534 | Raffel et al. | Jan 2001 | B1 |
6178425 | Brodersen et al. | Jan 2001 | B1 |
6189011 | Lim et al. | Feb 2001 | B1 |
6216135 | Brodersen et al. | Apr 2001 | B1 |
6233617 | Rothwein et al. | May 2001 | B1 |
6266669 | Brodersen et al. | Jul 2001 | B1 |
6295530 | Ritchie et al. | Sep 2001 | B1 |
6324568 | Diec et al. | Nov 2001 | B1 |
6324693 | Brodersen et al. | Nov 2001 | B1 |
6336137 | Lee et al. | Jan 2002 | B1 |
D454139 | Feldcamp | Mar 2002 | S |
6367077 | Brodersen et al. | Apr 2002 | B1 |
6393605 | Loomans | May 2002 | B1 |
6405220 | Brodersen et al. | Jun 2002 | B1 |
6434550 | Warner et al. | Aug 2002 | B1 |
6446089 | Brodersen et al. | Sep 2002 | B1 |
6535909 | Rust | Mar 2003 | B1 |
6549908 | Loomans | Apr 2003 | B1 |
6553563 | Ambrose et al. | Apr 2003 | B2 |
6560461 | Fomukong et al. | May 2003 | B1 |
6574635 | Stauber et al. | Jun 2003 | B2 |
6577726 | Huang et al. | Jun 2003 | B1 |
6601087 | Zhu et al. | Jul 2003 | B1 |
6604117 | Lim et al. | Aug 2003 | B2 |
6604128 | Diec | Aug 2003 | B2 |
6609150 | Lee et al. | Aug 2003 | B2 |
6621834 | Scherpbier et al. | Sep 2003 | B1 |
6654032 | Zhu et al. | Nov 2003 | B1 |
6665648 | Brodersen et al. | Dec 2003 | B2 |
6665655 | Warner et al. | Dec 2003 | B1 |
6684438 | Brodersen et al. | Feb 2004 | B2 |
6711565 | Subramaniam et al. | Mar 2004 | B1 |
6724399 | Katchour et al. | Apr 2004 | B1 |
6728702 | Subramaniam et al. | Apr 2004 | B1 |
6728960 | Loomans et al. | Apr 2004 | B1 |
6732095 | Warshavsky et al. | May 2004 | B1 |
6732100 | Brodersen et al. | May 2004 | B1 |
6732111 | Brodersen et al. | May 2004 | B2 |
6754681 | Brodersen et al. | Jun 2004 | B2 |
6763351 | Subramaniam et al. | Jul 2004 | B1 |
6763501 | Zhu et al. | Jul 2004 | B1 |
6768904 | Kim | Jul 2004 | B2 |
6772229 | Achacoso et al. | Aug 2004 | B1 |
6782383 | Subramaniam et al. | Aug 2004 | B2 |
6804330 | Jones et al. | Oct 2004 | B1 |
6826565 | Ritchie et al. | Nov 2004 | B2 |
6826582 | Chatterjee et al. | Nov 2004 | B1 |
6826745 | Coker | Nov 2004 | B2 |
6829655 | Huang et al. | Dec 2004 | B1 |
6842748 | Warner et al. | Jan 2005 | B1 |
6850895 | Brodersen et al. | Feb 2005 | B2 |
6850949 | Warner et al. | Feb 2005 | B2 |
7062502 | Kesler | Jun 2006 | B1 |
7069231 | Cinarkaya et al. | Jun 2006 | B1 |
7181758 | Chan | Feb 2007 | B1 |
7289976 | Kihneman et al. | Oct 2007 | B2 |
7340411 | Cook | Mar 2008 | B2 |
7356482 | Frankland et al. | Apr 2008 | B2 |
7401094 | Kesler | Jul 2008 | B1 |
7412455 | Dillon | Aug 2008 | B2 |
7508789 | Chan | Mar 2009 | B2 |
7620655 | Larsson et al. | Nov 2009 | B2 |
7698160 | Beaven et al. | Apr 2010 | B2 |
7730478 | Weissman | Jun 2010 | B2 |
7779475 | Jakobson et al. | Aug 2010 | B2 |
8014943 | Jakobson | Sep 2011 | B2 |
8015495 | Achacoso et al. | Sep 2011 | B2 |
8032297 | Jakobson | Oct 2011 | B2 |
8082301 | Ahlgren et al. | Dec 2011 | B2 |
8095413 | Beaven | Jan 2012 | B1 |
8095594 | Beaven et al. | Jan 2012 | B2 |
8209308 | Rueben et al. | Jun 2012 | B2 |
8275836 | Beaven et al. | Sep 2012 | B2 |
8457545 | Chan | Jun 2013 | B2 |
8484111 | Frankland et al. | Jul 2013 | B2 |
8490025 | Jakobson et al. | Jul 2013 | B2 |
8504945 | Jakobson et al. | Aug 2013 | B2 |
8510045 | Rueben et al. | Aug 2013 | B2 |
8510664 | Rueben et al. | Aug 2013 | B2 |
8566301 | Rueben et al. | Oct 2013 | B2 |
8646103 | Jakobson et al. | Feb 2014 | B2 |
10599885 | Galitsky | Mar 2020 | B2 |
10769419 | Rodriguez Bravo | Sep 2020 | B2 |
20010044791 | Richter et al. | Nov 2001 | A1 |
20020072951 | Lee et al. | Jun 2002 | A1 |
20020082892 | Raffel | Jun 2002 | A1 |
20020129352 | Brodersen et al. | Sep 2002 | A1 |
20020140731 | Subramanian et al. | Oct 2002 | A1 |
20020143997 | Huang et al. | Oct 2002 | A1 |
20020162090 | Parnell et al. | Oct 2002 | A1 |
20020165742 | Robbins | Nov 2002 | A1 |
20030004971 | Gong | Jan 2003 | A1 |
20030018705 | Chen et al. | Jan 2003 | A1 |
20030018830 | Chen et al. | Jan 2003 | A1 |
20030066031 | Laane et al. | Apr 2003 | A1 |
20030066032 | Ramachandran et al. | Apr 2003 | A1 |
20030069936 | Warner et al. | Apr 2003 | A1 |
20030070000 | Coker et al. | Apr 2003 | A1 |
20030070004 | Mukundan et al. | Apr 2003 | A1 |
20030070005 | Mukundan et al. | Apr 2003 | A1 |
20030074418 | Coker et al. | Apr 2003 | A1 |
20030120675 | Stauber et al. | Jun 2003 | A1 |
20030151633 | George et al. | Aug 2003 | A1 |
20030159136 | Huang et al. | Aug 2003 | A1 |
20030187921 | Diec et al. | Oct 2003 | A1 |
20030189600 | Gune et al. | Oct 2003 | A1 |
20030204427 | Gune et al. | Oct 2003 | A1 |
20030206192 | Chen et al. | Nov 2003 | A1 |
20030225730 | Warner et al. | Dec 2003 | A1 |
20040001092 | Rothwein et al. | Jan 2004 | A1 |
20040010489 | Rio et al. | Jan 2004 | A1 |
20040015981 | Coker et al. | Jan 2004 | A1 |
20040027388 | Berg et al. | Feb 2004 | A1 |
20040128001 | Levin et al. | Jul 2004 | A1 |
20040186860 | Lee et al. | Sep 2004 | A1 |
20040193510 | Catahan et al. | Sep 2004 | A1 |
20040199489 | Barnes-Leon et al. | Oct 2004 | A1 |
20040199536 | Barnes-Leon et al. | Oct 2004 | A1 |
20040199543 | Braud et al. | Oct 2004 | A1 |
20040249854 | Barnes-Leon et al. | Dec 2004 | A1 |
20040260534 | Pak et al. | Dec 2004 | A1 |
20040260659 | Chan et al. | Dec 2004 | A1 |
20040268299 | Lei et al. | Dec 2004 | A1 |
20050050555 | Exley et al. | Mar 2005 | A1 |
20050091098 | Brodersen et al. | Apr 2005 | A1 |
20060021019 | Hinton et al. | Jan 2006 | A1 |
20080249972 | Dillon | Oct 2008 | A1 |
20090063414 | White et al. | Mar 2009 | A1 |
20090100342 | Jakobson | Apr 2009 | A1 |
20090177744 | Marlow et al. | Jul 2009 | A1 |
20110247051 | Bulumulla et al. | Oct 2011 | A1 |
20120042218 | Cinarkaya et al. | Feb 2012 | A1 |
20120218958 | Rangaiah | Aug 2012 | A1 |
20120233137 | Jakobson et al. | Sep 2012 | A1 |
20130212497 | Zelenko et al. | Aug 2013 | A1 |
20130218948 | Jakobson | Aug 2013 | A1 |
20130218949 | Jakobson | Aug 2013 | A1 |
20130218966 | Jakobson | Aug 2013 | A1 |
20130247216 | Cinarkaya et al. | Sep 2013 | A1 |
20180357221 | Galitsky | Dec 2018 | A1 |
20190102452 | Dayan | Apr 2019 | A1 |
20190180737 | Abuelsaad | Jun 2019 | A1 |
20190236155 | Bachrach | Aug 2019 | A1 |
20190251165 | Bachrach | Aug 2019 | A1 |
20190379699 | Katragadda | Dec 2019 | A1 |
20200034749 | Kumar | Jan 2020 | A1 |
Number | Date | Country | |
---|---|---|---|
20200097846 A1 | Mar 2020 | US |
Number | Date | Country | |
---|---|---|---|
62735813 | Sep 2018 | US |