Patent Grant
12233883
The present disclosure relates to systems and methods for intelligently transforming data to generate improved output data using a probabilistic multi-application network.
Generating output data based on data from discrete sources is a critical aspect of many industries and commercial products. Integrating and leveraging data from multiple devices, applications, networks, and/or domains, including those associated with one or more multi-device or multi-application networks, is needed to facilitate process optimizations, data inputs and outputs, efficient data cataloging, data tracking, incident handling, data contextualization, location determination or monitoring, and data storage. In particular, during or following an incident, a participant of the incident may have to contact multiple interested parties in response to the incident in order to submit disparate data inputs and receive disparate data outputs related to such incident or participant, including redundant or repetitive data inputs and data outputs. The interested parties may include large entities, small entities, or single individuals with disparate devices, applications, networks, and/or domains associated with one or more multi-device or multi-application networks with disparate interfaces or other means for receiving data inputs and generating and sending data outputs. Contact and coordination of data by an incident participant with a multitude of interested parties, each with unique interfaces or other means for receiving data inputs and generating and sending data outputs, is often an arduous process for an incident participant and the interested parties alike. By implementing a multi-application network for an incident participant to communicate and coordinate in a predictable and efficient manner with some or all interested parties, information sharing, gathering, generating, transformation, collection, storage, and output will be streamlined and improved over existing methods and systems for generating output data during or following an incident.
The present disclosure is directed to systems and methods for intelligently transforming data to generate improved output data, including devices, applications, networks, and/or domains that implement one or more multi-device or multi-application networks. The systems and methods, for example, may include a method of transforming data using a probabilistic network and a knowledge base generated using historic data to generate improved output data, or a system capable of performing such method, the method comprising receiving, at one or more first servers from a first computing device, first data, wherein the first data is associated with a first user and associated with a first incident object associated with the first user. The systems and methods may further include generating, at the one or more first servers, in response to receiving, at the one or more servers from a first computing device, first data, a first computing object. The systems and methods may also include transmitting, from the one or more first servers to the first computing device, the first computing object. The systems and methods may include receiving, at one or more first servers from the first computing device, a first selection, wherein the first selection comprises a selection, by the first user, associated with the first computing object. The systems and methods may include transmitting, from the one or more first servers to the first computing device, a data collection computing input tool. The systems and methods may include receiving, at one or more first servers from the first computing device, a second selection, wherein the second selection comprises a selection, by the first user, associated with the data collection computing input tool. The systems and methods may include receiving, at one or more first servers from the first computing device, second data, wherein the second data is associated with a first incident object of the first user, and wherein the second data comprises a first image of the first incident object from a first angle. The systems and methods may include transmitting, from the one or more first servers to one or more second servers, the second data, wherein the second data indicates at least one characteristic resulting from an incident associated with the first incident object, wherein the at least one characteristic resulting from an incident associated with the first incident object is identifiable (or not identifiable) in the first image of the first incident object from the first angle. The systems and methods may include transforming, at the one or more second servers, the second data, wherein transforming the second data comprises comparing, at the one or more second servers, the second data and the first data to historic data, wherein the historic data is associated with one or more data of the first data and one or more data of the second data, and wherein comparing the second data and the first data to the historic data comprises the steps of generating or accessing, at the one or more second servers, a probabilistic network of the historic data, wherein the probabilistic network comprises a relationship between two or more data of the historic data, wherein the relationship between the two or more data of the historic data comprises one or more probabilities; processing, using at least one processor at the one or more second servers, the historic data, using the probabilistic network, into processed historic data; generating, using the at least one processor at the one or more second servers, one or more machine learning models for producing a knowledge base; producing, using the at least one processor at the one or more second servers and the one or more machine learning models, the knowledge base, wherein the knowledge base is trained to recognize one or more patterns of the processed historic data; and generating, using the at least one processor at the one or more second servers and the knowledge base, one or more data groups, wherein the one or more data groups are associated with at least one of the one or more patterns of the processed historic data, and wherein the one or more data groups are used to transform the second data and the first data, based on the associated at least one of the one or more patterns of the historic data, into modified data. The systems and methods may further include transforming, using the at least one processor at the one or more second servers and the one or more data groups, the second data and the first data into modified data, wherein the modified data is based on the historic data, the first data, and the second data. The systems and methods may include transmitting, from the one or more second servers to the one or more first servers, the modified data. The systems and methods may include generating, from the one or more first servers, first output data, wherein the first output data is based in part on the modified data, and wherein the first output data comprises one or more first locations, and wherein the one or more first locations is based on one or more of a second location associated with the first user or the first computing device and a third location associated with a first user input, wherein the first user input is received, at the one or more first servers, from the first computing device. The systems and methods may also include transmitting, from the one or more servers to the first computing device, the first output data.
These and other implementations may each optionally include one or more of the following features. A data engine may be further used to generate, for example, at least context data (e.g., new or updated context data) associated with a digital request data object, first computing object, or first computing operation result. In one embodiment, the context data indicates one or more of an exception event or a processing stage associated with the digital request data object, first computing object, or first computing operation result. Moreover, the data engine may be used to initiate the display of the context data or one or more vehicle data and/or the first computing result associated with the digital request data object on a graphical user interface or data collection computing input tool. The graphical user interface or data collection computing input tool may comprise, for example, a consolidation of a plurality of graphical user interfaces associated with a first application or a plurality of applications associated with the first set of operation recommendations, context data, or one or more vehicle data, or a condensation of a plurality of display elements associated with the first application or the plurality of applications.
The data engine may be used, according to some embodiments, to automatically format one or more of: the first computing operation (e.g., a machine learning or artificial intelligence (AI) operation) result or transformed or modified data for display on the first graphical user interface or data collection computing input tool based on the context data or vehicle data or transformed or modified data (e.g., the new or updated context data or vehicle data); or a second set of operation (e.g., a machine learning or AI operation) recommendations that are generated based on the first operation recommendation or the context data or vehicle data or transformed or modified data (e.g., the new or updated context data). Furthermore, the data engine may be used to detect, using the context data or vehicle data or transformed or modified data, an exception event associated with the digital request data object. Based on detecting the exception event, the data engine may be used to generate a second set of operation recommendations indicating a stage-wise progression of operations that resolve the exception event. In one embodiment, the data engine may transmit the second set of operation (e.g., a machine learning or AI operation) recommendations for display on a first computing device. In some embodiments, the multi-application network is configured for multi-application data processing associated with a plurality of domains comprised in a digital processing space. In addition, the first application may comprise one of: an application native to the multi-application network; or an application that is not native to the multi-application network. In some embodiments, the parametric data referenced above in association with digital request data object comprises one or more identifier data associated with the digital request data object and/or quantitative data associated with the digital request data object and/or exception event data associated with the digital request data object. Furthermore, the data model (e.g., a machine learning or AI model) may be configured to track or assimilate a trajectory of a plurality of input commands including the first input command leading to a selection of specific operation recommendations including the first operation recommendation. Based on the tracking, the data model (e.g., a machine learning or AI model) may be optimized and used by the data engine to recommend a second set of operation recommendations for display on a graphical user interface or data collection computing input tool associated with the first computing device or a second computing device.
The disclosure is illustrated by way of example and not by way of limitation in the figures of the accompanying drawings. Like reference numerals in the figures may be used to refer to similar elements. It is emphasized that various features may not be drawn to scale and the dimensions of various features may be arbitrarily increased or reduced for clarity of discussion. Further, some components may be omitted in certain figures for clarity of discussion. It is expressly understood that the description and drawings are only for the purpose of illustration and as an aid to understanding and are not intended as a definition of the limits of the invention.
a, 9b, 10 and 11 show potential embodiments of user interfaces or data collection computing input tools on an endpoint (or computing) device associated with a multi-application network, according to some embodiments of this disclosure.
Multi-Application Network
It is increasingly necessary to leverage computational tools (e.g., machine learning elements such as training data or historic data, probabilistic network(s), machine learning model(s), one or more knowledge bases for pattern recognition, one or more data groups or artificial intelligence (AI) features, categories, columns, or rows) that automatically recognize relationships among a plurality of disparate data (e.g., vehicle data or modified, transformed, or output data) associated with a multi-application network, and suggest, estimate, predict, assess, or otherwise recommend operations for transforming or modifying data that can be executed to make such disparate data more meaningful, insightful, and readily ingestible or accessible by other computing systems or applications for further processing or analysis or use by a user of the multi-application network or a third party. There is therefore a need to develop a multi-application network that can recommend operations for transforming or modifying data based on data relationships (e.g., between historic data and new input data) in order to eliminate or otherwise minimize time constraints associated with computing operations within the multi-application network. Furthermore, the cost in terms of time, accuracy, and user experience (e.g., navigating multiple similar or dissimilar tools/interfaces, such as multiple data collection computing input tools) associated with data collection, analysis, transformation, modification, or output can affect productivity and/or workflow efficiency, computational or otherwise, within the multi-application network.
Illustrated in
In some embodiments, the cloud server 102 may include a computing device such as a mainframe server, a content server, a communication server, a laptop computer, a desktop computer, a handheld computing device, a smart phone, a wearable computing device, a tablet computing device, a virtual machine, a mobile computing device, a cloud-based computing solution and/or a cloud-based service, smart or Internet of Things (IoT) devices, network-enabled devices such as smart or connected vehicles or related devices such as those providing internet, voice, or emergency assistance, and/or the like. The cloud server 102 may include a plurality of computing devices configured to communicate with one another and/or implement the techniques described herein.
In some embodiments, the endpoint device 104 may include or constitute a computing device such as a mainframe server, a content server, a communication server, a laptop computer, a desktop computer, a handheld computing device, a smart phone, a wearable computing device, a tablet computing device, a virtual machine, a mobile computing device, a cloud-based computing solution and/or a cloud-based service, smart or Internet of Things (IoT) devices, network-enabled devices such as smart or connected vehicles or related devices such as those providing internet, voice, or emergency assistance, and/or the like.
The cloud server 102 may include various elements of a computing environment as described in association with the computing environment 200 of
Turning back to
The web server 108 may include a secure socket layer (SSL) proxy 112 for establishing HTTP-based connectivity 114 between the cloud server 102 and other devices or systems coupled to the network 106. Other forms of secure connection techniques, such as encryption, may be employed on the web server 108 and across other systems coupled to the network 106. Additionally, the web server 108 may deliver artifacts (e.g., binary code, instructions, data, etc.) to the data engine 118 either directly via the SSL proxy 112 and/or via the network 106. Additionally, the web and agent resources 116 of the cloud server 102 may be provided to the endpoint device 104 via the web app 110 on the web server 108. The web and agent resources 116 may be used to render a web-based graphical interface (GUI or data collection computing input tool) 126 via the web browser 124 running on the endpoint device 104.
The data engine 118 may either be implemented on the cloud server 102 and/or on the endpoint device 104. The data engine 118 may include one or more instructions or computer logic that are executed by the one or more processors such as the processors discussed in association with
In some embodiments, the use of artificial intelligence and machine learning comprises an artificial intelligence engine or knowledge base that has an associated data model (e.g., a machine learning model) comprising a large language model and/or a data classifier, such as a probabilistic network, that can operate and/or is trained on textual data and/or image data and/or audio data and/or video data. For example, the textual data and/or image data and/or audio data and/or video data may be historic data or training data from one or more training data sets. For example, the large language model, according to some embodiments, comprises an artificial intelligence (AI) or a machine learning model configured to process or otherwise analyze vast amounts of character strings associated with spoken and/or written language. As another example, the data classifier comprises an AI or machine learning model generated by processing or otherwise analyzing historic data or training data from one or more training data sets for patterns by establishing a relationship between two or more data of such historic data or training data using a probabilistic network (e.g., a Bayesian network) or the like. The data classifier may further generate a knowledge base that is trained to recognize such patterns of processed or pre-processed historic or training data and generate one more data groups associated with such patterns to enable the transformation or modification of data based on such patterns. In an embodiment, a pattern includes a relationship between data that allows for the prediction of a likely outcome if similar data were substituted into such relationship.
In some embodiments, the data engine 118 may access an operating system 130 of the endpoint device 104 in order to execute the disclosed techniques on the endpoint device 104. For instance, the data engine 118 may gain access into the operating system 130 including the system configuration module 132, the file system 136, and the system services module 134 in order to execute computing operations (e.g., machine learning or AI operations or other non-machine learning or AI operations) associated with a multi-application network such as registering a digital command or selection in a multi-application network, generating dynamic context data or vehicle or modified or transformed data associated with a digital request data object, computing object, or computing operation result in a multi-application network, curating, modifying, transforming, and/or storing data associated with a multi-application network, and generating or accessing one or more digital records or data indicating computing operations (e.g., machine learning or AI operations) and/or state data or other data within a multi-application network. A plug-in 128 of the web browser 124 may provide needed downloads that facilitate operations executed by the operating system 130, the data engine 118, and/or other applications running on the endpoint device 104.
The network 106 may include a plurality of networks. For instance, the network 106 may include any wired and/or wireless communication network that facilitates communication between the cloud server 102, the cloud storage 120, and the endpoint device 104. The network 106, in some instances, may include an Ethernet network, a cellular network, a computer network, the Internet, a wireless fidelity (Wi-Fi) network, a light fidelity (Li-Fi) network, a Bluetooth network, a radio frequency identification (RFID) network, a near-field communication (NFC) network, a laser-based network, a 5G network, and/or the like.
The network systems 138a . . . 138n may include one or more computing devices or servers, services, or applications the can be accessed by the cloud server 102 and/or the endpoint device 104 and or the cloud storage 120 via the network 106. In one embodiment, the network systems 138a . . . 138n may comprise one or more endpoint device(s) or computing devices 104 or local server(s) 102. In one embodiment, the network systems 138a . . . 138n comprises third-party applications or services that are native or non-native to either the cloud server 102 and/or the endpoint device 104. The third-party applications or services, for example, may facilitate executing one or more computing operations associated with resolving an exception event associated with a digital request data. As further discussed below, the digital request data may comprise a document, selection, or file outlining one or more of: account data associated with a client request; or parametric data associated with resolving one or more exception events associated with the digital request data. According to some implementations, the applications or services associated with the network systems 138a . . . 138n and/or associated with the cloud server 102, and/or the endpoint device 104 must be registered to activate or otherwise enable their usage in the multi-application network. In such cases, the applications and/or services may be encapsulated in a registration object such that the registration object is enabled or activated for use by the data engine 118 based on one or more of: context data or vehicle data or modified or transformed data associated with a first user input or selection; device profile data associated with a first interface or data collection computing input tool through which the first user input was received; and user profile data associated with the user providing the first user input or selection. On the flip side, the applications and/or services may be encapsulated in a registration object such that the registration object is deactivated or blocked from usage by data engine 118 based on one or more of: context data or vehicle data or modified or transformed data associated with a second user input or selection; device profile data associated with a second interface or data collection computing input tool through which the second input was received; and user profile data associated with a user providing the second input or selection. The first and second user inputs or selections may both be textual or auditory and may comprise a natural language input, or they may both be object selections of a computing object of an interface or data collection computing input tool.
The cloud storage 120 may comprise one or more storage devices that store data, information and instructions used by the cloud server 102 and/or the endpoint device 104 such as, for example, one or more databases. The stored information may include information about users, information about data models (e.g., machine or other learning model, an artificial intelligence model, etc.), information associated with an object or incident of a user, a user object characteristic, digital request data, vehicle data, information about analysis operations executed by the data engine 118, or the like. In one embodiment, the one or more storage devices mentioned above in association with the cloud storage 120 can be non-volatile memory or similar permanent storage device and media. For example, the one or more storage devices may include a hard disk drive, a CD-ROM device, a DVD-ROM device, a DVD-RAM device, a DVD-RW device, a flash memory device, solid state media, or another mass storage device for storing information on a more permanent basis. While the cloud storage 120 is shown as being coupled to the cloud server 102 and the endpoint device 104 via the network 106, the data in the cloud storage 120 may be replicated, in some embodiments, on the cloud server 102 and/or the endpoint device 104. That is to say that a local copy of the data in the cloud storage 120 may be stored on the cloud server 102 and/or the endpoint device 104. This local copy may be synched with the cloud storage 120 so that when there are any changes to the information in the cloud storage 120, the local copy on either the cloud server 102 or the endpoint device 104 is also similarly updated or synched in real-time or in near-real-time to be consistent with the information in the cloud storage 120 and vice versa.
The endpoint device 104 may be a computing device, a smart phone, a tablet, a laptop computer, a desktop computer, a personal digital assistant (PDA), a smart device, a wearable device, a biometric device, a computer server, a virtual server, a virtual machine, a mobile device, a vehicle, a data collection device, a smart or Internet of Things (IoT) device, network-enabled device such as a smart or connected vehicle or related device such as those providing internet, voice, or emergency assistance, and/or a communication server. In some embodiments, the endpoint device 104 may include a plurality of computing devices configured to communicate with one another and/or implement the techniques described in this disclosure. It is appreciated that according to some implementations, the endpoint device may be used by a user to access the multi-application network for sending and or receiving data and/or executing a plurality of operations associated with a digital request data object, computing object, or computing operation result. The data engine 118 may use the multi-application network to communicate with the user transmitting and/or receiving data and to execute a plurality of analysis operations as further discussed below.
The local storage 122, shown in association with the endpoint device 104, may include one or more storage devices that store data, information, and instructions used by the endpoint device 104 and/or other devices coupled to the network 106. The stored information may include various logs/records or event files (e.g., exception event data associated with a digital request data object), security event data, image and/or video data, vehicle data, modified or transformed data, output data, or any other data described herein. The one or more storage devices discussed above in association with the local storage 122 can be non-volatile memory or similar permanent storage device and media. For example, the one or more storage devices may include a hard disk drive, a floppy disk drive, a CD-ROM device, a DVD-ROM device, a DVD-RAM device, a DVD-RW device, a flash memory device, solid state media, or some other mass storage device known in the art for storing information on a more permanent basis.
The network system local storages 140a . . . 140n, shown in association with one or more network systems 138a . . . 138n, may include one or more storage devices that store data, information, and instructions used by the one or more network systems 138a . . . 138n and/or other devices coupled to the network 106. The stored information may include various logs/records or event files (e.g., exception event data associated with a digital request data object), security event data, image and/or video data, vehicle data, modified or transformed data, output data, or any other data described herein. The one or more storage devices discussed above in association with the local storage 122 or network system local storages 140a . . . 140n can be non-volatile memory or similar permanent storage device and media. For example, the one or more storage devices may include a hard disk drive, a floppy disk drive, a CD-ROM device, a DVD-ROM device, a DVD-RAM device, a DVD-RW device, a flash memory device, solid state media, or some other mass storage device known in the art for storing information on a more permanent basis.
The other elements of the endpoint device 104 are discussed in association with the computing environment 200 of
As seen in
The processing unit 202 may control one or more of the memory unit 204, the I/O unit 206, and the communication unit 208 of the computing environment 200, as well as any included subunits, elements, components, devices, and/or functions performed by the memory unit 204, I/O unit 206, and the communication unit 208. The described sub-elements of the computing environment 200 may also be included in similar fashion in any of the other units and/or devices included in the system 100 of
In some embodiments, the processing unit 202 may be implemented as one or more computer processing unit (CPU) chips and/or graphical processing unit (GPU) chips and may include a hardware device capable of executing computer instructions. The processing unit 202 may execute instructions, codes, computer programs, and/or scripts. The instructions, codes, computer programs, and/or scripts may be received from and/or stored in the memory unit 204, the I/O unit 206, the communication unit 208, subunits, and/or elements of the aforementioned units, other devices, and/or computing environments, and/or the like.
In some embodiments, the processing unit 202 may include, among other elements, subunits such as a content management unit 212, a location determination unit 214, a graphical processing unit (GPU) 216, and a resource allocation unit 218. Each of the aforementioned subunits of the processing unit 202 may be communicatively and/or otherwise operably coupled with each other.
The content management unit 212 may facilitate generation, modification, analysis, transmission, and/or presentation of content. Content may be file content, exception event content, content associated with a digital request data object, content associated with a registration object (e.g., a registration data object associated with registering a command or an application for use by the multi-application network), media content, security event content, image and/or video data, vehicle date, modified or transformed data, output data, or any other data described herein, or any combination thereof. In some instances, content on which the content management unit 212 may operate includes device information, user interface or data collected and/or stored by the data collection computing input tool, image data, text data, themes, audio data or audio files, video data or video files, documents, and/or the like. Additionally, the content management unit 212 may control the audio-visual environment and/or appearance of application data during execution of various processes (e.g., via web GUI 126 at the endpoint device 104). In some embodiments, the content management unit 212 may interface with a third-party content server (e.g., third-party content server associated with the network systems 138a . . . 138n), and/or specific memory locations for execution of its operations.
The location determination unit 214 may facilitate detection, generation, modification, analysis, transmission, and/or presentation of location information. Location information may include global positioning system (GPS) coordinates, an internet protocol (IP) address, a media access control (MAC) address, geolocation information, a port number, a server number, a proxy name and/or number, device information (e.g., a serial number), an address, a zip code, and/or the like. In some embodiments, the location determination unit 214 may include various sensors, radar, and/or other specifically-purposed hardware elements for the location determination unit 214 to acquire, measure, and/or otherwise transform location information.
The GPU 216 may facilitate generation, modification, analysis, processing, transmission, and/or presentation of content described above, as well as any data described herein. In some embodiments, the GPU 216 may be utilized to render content for presentation on a computing device (e.g., via web GUI 126 at the endpoint device 104). The GPU 216 may also include multiple GPUs and therefore may be configured to perform and/or execute multiple processes in parallel.
The resource allocation unit 218 may facilitate the determination, monitoring, analysis, and/or allocation of computing resources throughout the computing environment 200 and/or other computing environments. For example, the computing environment may facilitate a high volume of data (e.g., data associated with a digital request data object or a registration object), to be processed and analyzed. As such, computing resources of the computing environment 200 used by the processing unit 202, the memory unit 204, the I/O unit 206, and/or the communication unit 208 (and/or any subunit of the aforementioned units) such as processing power, data storage space, network bandwidth, and/or the like may be in high demand at various times during operation. Accordingly, the resource allocation unit 218 may include sensors and/or other specially-purposed hardware for monitoring performance of each unit and/or subunit of the computing environment 200, as well as hardware for responding to the computing resource needs of each unit and/or subunit. In some embodiments, the resource allocation unit 218 may use computing resources of a second computing environment separate and distinct from the computing environment 200 to facilitate a desired operation. For example, the resource allocation unit 218 may determine a number of simultaneous computing processes and/or requests. The resource allocation unit 218 may also determine that the number of simultaneous computing processes and/or requests meet and/or exceed a predetermined threshold value. Based on this determination, the resource allocation unit 218 may determine an amount of additional computing resources (e.g., processing power, storage space of a particular non-transitory computer-readable memory medium, network bandwidth, and/or the like) required by the processing unit 202, the memory unit 204, the I/O unit 206, the communication unit 208, and/or any subunit of the aforementioned units for safe and efficient operation of the computing environment while supporting the number of simultaneous computing processes and/or requests. The resource allocation unit 218 may then retrieve, transmit, control, allocate, and/or otherwise distribute determined amount(s) of computing resources to each element (e.g., unit and/or subunit) of the computing environment 200 and/or another computing environment.
The memory unit 204 may be used for storing, recalling, receiving, transmitting, and/or accessing various files and/or data, such as image and/or video data, vehicle date, modified or transformed data, output data, or any other data described herein, during operation of computing environment 200. For example, memory unit 204 may be used for storing, recalling, and/or updating exception event information as well as other data associated with, resulting from, and/or generated by any unit, or combination of units and/or subunits of the computing environment 200. In some embodiments, the memory unit 204 may store instructions, code, and/or data that may be executed by the processing unit 202. For instance, the memory unit 204 may store code that execute operations associated with one or more units and/or one or more subunits of the computing environment 200. For example, the memory unit may store code for the processing unit 202, the I/O unit 206, the communication unit 208, and for itself.
Memory unit 204 may include various types of data storage media such as solid state storage media, hard disk storage media, virtual storage media, and/or the like. Memory unit 204 may include dedicated hardware elements such as hard drives and/or servers, as well as software elements such as cloud-based storage drives. In some implementations, memory unit 204 may be a random access memory (RAM) device, a dynamic random access memory (DRAM) device, a static random access memory (SRAM) device, flash memory, read only memory (ROM) device, and/or various forms of secondary storage. The RAM device may be used to store volatile data and/or to store instructions that may be executed by the processing unit 202. For example, the instructions stored by the RAM device may be a command, a current operating state of computing environment 200, an intended operating state of computing environment 200, and/or the like. As a further example, data stored in the RAM device of memory unit 204 may include instructions related to various methods and/or functionalities described herein. The ROM device may be a non-volatile memory device that may have a smaller memory capacity than the memory capacity of a secondary storage. The ROM device may be used to store instructions and/or data that may be read during execution of computer instructions. In some embodiments, access to both the RAM device and ROM device may be faster to access than the secondary storage.
Secondary storage may comprise one or more disk drives and/or tape drives and may be used for non-volatile storage of data or as an over-flow data storage device if the RAM device is not large enough to hold all working data. Secondary storage may be used to store programs that may be loaded into the RAM device when such programs are selected for execution. In some embodiments, the memory unit 204 may include one or more databases 310 (shown in
Turning back to
The operating system unit 226 may facilitate deployment, storage, access, execution, and/or utilization of an operating system utilized by computing environment 200 and/or any other computing environment described herein. In some embodiments, operating system unit 226 may include various hardware and/or software elements that serve as a structural framework for processing unit 202 to execute various operations described herein. Operating system unit 226 may further store various pieces of information and/or data associated with the operation of the operating system and/or computing environment 200 as a whole, such as a status of computing resources (e.g., processing power, memory availability, resource utilization, and/or the like), runtime information, modules to direct execution of operations described herein, user permissions, security credentials, and/or the like.
The application data unit 228 may facilitate deployment, storage, access, execution, and/or utilization of an application used by computing environment 200 and/or any other computing environment described herein. For example, the endpoint device 104 may be required to download, install, access, and/or otherwise use a software application (e.g., web application 165) to facilitate implementing a multi-application network, registering a digital command in a multi-application network, generating dynamic context data associated with a digital request data object in a multi-application network, curating data associated with a multi-application network, and generating one or more digital records indicating computing operations and state data within a multi-application network. As such, the application data unit 228 may store any information and/or data associated with an application. The application data unit 228 may further store various pieces of information and/or data associated with the operation of an application and/or computing environment 200 as a whole, such as status of computing resources (e.g., processing power, memory availability, resource utilization, and/or the like), runtime information, user interfaces, modules to direct execution of operations described herein, user permissions, security credentials, and/or the like.
The API unit 230 may facilitate deployment, storage, access, execution, and/or utilization of information associated with APIs of computing environment 200 and/or any other computing environment described herein. For example, computing environment 200 may include one or more APIs for various devices, applications, units, subunits, elements, and/or other computing environments to communicate with each other and/or utilize the same data. Accordingly, API unit 230 may include API databases containing information that may be accessed and/or utilized by applications, units, subunits, elements, and/or operating systems of other devices and/or computing environments. In some embodiments, each API database may be associated with a customized physical circuit included in memory unit 204 and/or API unit 230. Additionally, each API database may be public and/or private, and so authentication credentials may be required to access information in an API database. In some embodiments, the API unit 230 may enable the cloud server 102 and the endpoint device 104 to communicate with each other. It is appreciated that the API unit 230 may facilitate accessing, using the data engine 118, one or more applications or services on the cloud server 102 and/or the network systems 138a . . . 138n.
The content storage unit 232 may facilitate deployment, storage, access, and/or utilization of information associated with performance of implementing operations associated with a multi-application network and/or framework processes by computing environment 200 and/or any other computing environment described herein. In some embodiments, content storage unit 232 may communicate with content management unit 212 to receive and/or transmit content files (e.g., media content, digital request data object content, command content, input content, registration object content, etc.).
As previously discussed, the data engine 118 facilitates executing the processing procedures, methods, techniques, and workflows provided in this disclosure. In particular, the data engine 118 may be configured to execute computing operations associated with the disclosed methods, systems/apparatuses, and computer program products.
The cache storage unit 240 may facilitate short-term deployment, storage, access, analysis, and/or utilization of data. In some embodiments, cache storage unit 240 may serve as a short-term storage location for data so that the data stored in cache storage unit 240 may be accessed quickly. In some instances, cache storage unit 240 may include RAM devices and/or other storage media types for quick recall of stored data. Cache storage unit 240 may include a partitioned portion of storage media included in memory unit 204.
The I/O unit 206 may include hardware and/or software elements for the computing environment 200 to receive, transmit, and/or present information useful for performing the disclosed processes. For example, elements of the I/O unit 206 may be used to receive input from a user of the endpoint device 104. As described herein, I/O unit 206 may include subunits such as an I/O device 242, an I/O calibration unit 244, and/or driver 246.
The I/O device 242 may facilitate the receipt, transmission, processing, presentation, display, input, and/or output of information as a result of executed processes described herein. In some embodiments, the I/O device 242 may include a plurality of I/O devices. In some embodiments, I/O device 242 may include a variety of elements that enable a user to interface with computing environment 200. For example, I/O device 242 may include a keyboard, a touchscreen, a button, a sensor, a biometric scanner, a laser, a microphone, a camera, and/or another element for receiving and/or collecting input from a user. Additionally and/or alternatively, I/O device 242 may include a display, a screen, a sensor, a vibration mechanism, a light emitting diode (LED), a speaker, a radio frequency identification (RFID) scanner, and/or another element for presenting and/or otherwise outputting data to a user. In some embodiments, the I/O device 242 may communicate with one or more elements of processing unit 202 and/or memory unit 204 to execute operations associated with the disclosed techniques and systems.
The I/O calibration unit 244 may facilitate the calibration of the I/O device 242. For example, I/O calibration unit 244 may detect and/or determine one or more settings of I/O device 242, and then adjust and/or modify settings so that the I/O device 242 may operate more efficiently. In some embodiments, I/O calibration unit 244 may use a driver 246 (or multiple drivers) to calibrate I/O device 242. For example, the driver 246 may include software that is to be installed by I/O calibration unit 244 so that an element of computing environment 200 (or an element of another computing environment) may recognize and/or integrate with I/O device 242 for the processes described herein.
The communication unit 208 may facilitate establishment, maintenance, monitoring, and/or termination of communications between computing environment 200 and other computing environments, third party server systems, and/or the like (e.g., between the cloud server 102 and the endpoint device 104 and or the network systems 138a . . . 138n). Communication unit 208 may also facilitate internal communications between various elements (e.g., units and/or subunits) of computing environment 200. In some embodiments, communication unit 208 may include a network protocol unit 248, an API gateway 250, an encryption engine 252, and/or a communication device 254. Communication unit 208 may include hardware and/or other software elements.
The network protocol unit 248 may facilitate establishment, maintenance, and/or termination of a communication connection for computing environment 200 by way of a network. For example, the network protocol unit 248 may detect and/or define a communication protocol required by a particular network and/or network type. Communication protocols used by the network protocol unit 248 may include Wi-Fi protocols, Li-Fi protocols, cellular data network protocols, Bluetooth® protocols, WiMAX protocols, Ethernet protocols, powerline communication (PLC) protocols, and/or the like. In some embodiments, facilitation of communication for computing environment 200 may include transforming and/or translating data from being compatible with a first communication protocol to being compatible with a second communication protocol. In some embodiments, the network protocol unit 248 may determine and/or monitor an amount of data traffic to consequently determine which particular network protocol is to be used for establishing a secure communication connection, transmitting data, and/or performing malware scanning operations and/or other processes described herein.
The API gateway 250 may allow other devices and/or computing environments to access the API unit 230 of the memory unit 204 associated with the computing environment 200. For example, an endpoint device 104 may access the API unit 230 of the computing environment 200 via the API gateway 250. In some embodiments, the API gateway 250 may be required to validate user credentials associated with a user of the endpoint device 104 prior to providing access to the API unit 230 to a user. The API gateway 250 may include instructions for the computing environment 200 to communicate with another computing device and/or between elements of the computing environment 200.
If the object impact assessment 432 does not exceed the determined object impact threshold 434, then the multi-application network sends the object impact assessment 432, digital request submissions, and generated occurrence data to one or more network systems 138a . . . 138n comprising an object section supplier 410. The object section supplier 410 may utilize information provided within and external to the multi-application network to determine object section quantitative data 442. The object section supplier 410 would also assess object section concerns 444, such as object section shortages. If an object section concern 444 is identified, the multi-application network would report the object section concern 444 to the object coverage affiliate 430 and then proceed with termination 428 of communication and connection with one or more endpoint devices 104. If no object section concern 444 is detected, the object section quantitative data 442 will be transmitted through the multi-application network to the data compilation affiliate 404 for object restoration affiliate selection 416 by the digital requester. Once an object restoration affiliate is selected, object documentation 412 will be collected and included in object restoration affiliate communications 424. Object documentation 412 may be accessed from an object documentation database 402 within cloud storage 120 or one or more network system local storage 140a . . . 140n. After object restoration affiliate selection 416, a direct affiliate relationship 418 is assessed to determine if there is a direct relationship between the object coverage affiliate and the object restoration affiliate selected. If so, the digital requester may immediately commence object restoration scheduling 420 and temporary object replacement orders 422. If there is not a direct affiliate relationship 418 between the object coverage affiliate and the object restoration affiliate selected, the digital requester may be provided with object restoration data 426 before proceeding to temporary object replacement orders 421. After both the object restoration affiliate and temporary object replacement have been selected, the selections and associated data are stored and transferred to the object coverage affiliate 430 and to the selected object restoration affiliate and temporary object replacement affiliate before terminating the transfer of data within the multi-application network. At any stage in the aforementioned processes, data may be stored within one or more cloud storages 120, local storages 122, memory units 204, and/or one or more network system local storages 140a . . . 140n. The various steps in
An example of the above embodiments may apply to accidents involving motor vehicles. A participant of an accident may call their insurance provider and provide basic information about themselves and their insurance coverage. The insurance company may then input this information in their database (or this data may be input into one or more servers of the multi-application network directly or via a third party or third-party server) and send the customer a link to open a mobile application or user interface (e.g., a data collection computing input tool) to upload images, videos, augmented reality or virtual reality captures, etc. of the accident or a characteristic of the accident (e.g., damage caused by the accident as described herein). In some embodiments, the customer may comprise a user. The images, etc. of the accident or characteristic are then uploaded and the multi-application network sends the images, etc. of the accident or characteristic to a server associated with a second network to assess the damage and provide either a salvage quote or a repair quote, which may include an estimated number of labor hours required for a repair. The customer may then use the mobile application to select a rental vehicle from a number of rental vehicle options and a repair shop from a number of repair shop options if their vehicle is repairable. This whole process may be consolidated within a single multi-application network or multiple multi-application networks. In one embodiment, the user may be able to contact a towing or salvage service depending on an analysis of the images, etc. of the accident or characteristic through the use of the data collection computing input tool and multi-application network. In another embodiment, the user may be able to hail a taxi or otherwise connect with a ride share service or vehicle through the use of the data collection computing input tool and multi-application network. In yet another embodiment, the repair shop options provided to the user may include repair shops that are certified to repair the damage or characteristic identified by the images, etc. of the accident or characteristic submitted through the interface or data collection computing input tool and multi-application network. In an embodiment, an identified or identifiable characteristic includes a characteristic that is able to be one or more of seen, determined, located, assessed, analyzed, evaluated, or the like. Similarly, in an embodiment, a characteristic that is not identified or identifiable includes a characteristic that is not able to be one or more of seen, determined, located, assessed, analyzed, evaluated, or the like. In one embodiment, the certified repair shop options provided may be specific to repair shops certified to repair the make and model of an electric vehicle involved in the accident and shown or otherwise provided in the images, etc. of the accident or characteristic, or other user data, submitted through the interface or data collection computing input tool or accessed by the multi-application network. In some embodiments, these described embodiments may comprise a server or network of the multi-application network communicating with one or more other server(s) or network(s) associated with the multi-application network to enable the user's connection with one or more separate applications for towing, salvage, ride share, etc. In another embodiment, the towing, salvage, ride share, etc. options or related data may be hosted at a separate server from the server of the data collection computing input tool but are displayed by the data collection computing input tool for user review and selection. In an embodiment, a vehicle may be one or more of a motor, electric, nautical, flying, hybrid, multi-purpose, all-terrain, or similar vehicle or combination thereof.
Going back to
Going to
In some embodiments, the first vehicle output data comprises generating a list or data of vehicle repair facilities and rental vehicle facilities based on the modified vehicle data and additional data, such as the customer's current location, occurrence location, or location of residence. In some embodiments, the customer's current location, occurrence location, or location of residence may be manually input by the customer, or may generate based on the operating system 130 of the customer's endpoint device 104. In some embodiments, vehicle output data further comprises one or more of repair data, repair facility data, rental vehicle reservation data, rental vehicle facility data, appraisal data, appraisal facility data, salvage data, or salvage facility data. At block 2524, the method comprises transmitting, from the one or more first servers to the first computing device, the first vehicle output data. In some embodiments, the transmitting of the first vehicle output comprises sending the generated data or list of repair facilities and rental vehicle facility options to the customer. In some embodiments, repair data may comprise original equipment manufacturer documents, original equipment manufacturer certification requirements, original equipment manufacturer procedures, or any other information relating to the ability of facilities to restore the vehicle. In some embodiments, repair facility data may comprise location data, certification data, inventory data, cost data, operation hours, and/or availability data for one or more potential repair facilities. In some embodiments, rental vehicle reservation data may comprise location data of one or more rental vehicles, categorical vehicle data such as type of one or more vehicles, cost of one or more rental vehicles, mileage of one or more rental vehicles, and/or other characteristic vehicle data. In some embodiments, rental vehicle facility data may comprise location data for one or more rental facilities, inventory data for the one or more rental facilities, associated costs at the one or more rental facilities, and/or operation hours of the one or more rental facilities. In some embodiments, appraisal data may comprise vehicle incident assessments such as time required to reverse the impact to the vehicle from the incident, cost of replacement vehicle parts and components to reverse the vehicle impact, whether the vehicle should be salvaged or repaired, and/or the difference in vehicle valuation before and after the incident. In some embodiments, appraisal facility data may comprise location data, cost data, operation hours, and/or availability data for one or more potential appraisal facilities. In some embodiments, salvage data may comprise vehicle incident assessments such as cost to scrap vehicle, value of functioning and nonfunctioning vehicle parts and components, and/or whether the vehicle should be salvaged. In some embodiments, salvage facility data may comprise location data, cost data, operation hours, and/or availability data for one or more potential salvage facilities. In some embodiments, the vehicle output data may be provided to the user after the vehicle output data and modified vehicle data have been generated.
In some embodiments, the methods described may also be executed within a system. In some embodiments of the corresponding system, the one or more first servers and the one or more second servers are the same server. In some embodiments of the system, the one or more first servers, the one or more second servers, and the first computing device communicate via a cloud-based network. In some embodiments, the cloud-based network comprises a system 100 wherein the network 106 or the system 100 as a whole exists on the cloud via the internet. In some embodiments of the system, the one or more first servers, the one or more second servers, and the first computing device communicate via a local network. In some embodiments, the local network comprises a network 106 that is managed from a command line or server accessible without the internet. In some embodiments of the system, the at least one characteristic resulting from an incident associated with the first vehicle is vehicle damage, and wherein the incident associated with the first vehicle is one or more of a vehicle accident associated with the first vehicle, a vehicle crash associated with the first vehicle, or a vehicle incident where damage is caused to the first vehicle.
An invention, and the software and/or network services comprising the invention, can provide some or all of the functionality described herein related to machine learning. For example, a network service can be deployed through a service provider network (e.g., using an operating system and/or application programs). The network service can allow for third party usc of the techniques described herein for applying machine learning of an auxiliary machine learning model with a relatively large capacity. The network service can be deployed across one or more host processors, computers, servers, or other computer hardware, and can be provided over one or more network connections. Additionally, according to at least one example, knowledge related to the size and attributes of labeled machine learning training observations can be stored or retained at the one or more local storage 122, cloud storage 120, or one or more network system local storages 140a . . . 140n. While the subject matter described herein is presented in the general context of program modules that execute in conjunction with the execution of an operating system and application programs on a computer system, those skilled in the art will recognize that other examples can be performed in combination with other types of program modules. Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the subject matter described herein can be practiced with various computer system configurations, including single-processor or multiprocessor systems, single core or multi-core processors, microprocessor-based or programmable consumer electronics, hand-held computing devices, minicomputers, personal computers, mainframe computers, combinations thereof, and the like.
Encoding the multi-application network and its components presented herein also may transform the physical structure of the computer readable media presented herein. The specific transformation of physical structure may depend on various factors, in different implementations of this description. Examples of such factors may include, but are not limited to, the technology used to implement the one or more network systems 138a . . . 138n, whether the one or more network system local storages 140a . . . 140n are characterized as primary or secondary storages, and the like. For example, if the one or more network system local storages 140a . . . 140n are implemented as semiconductor-based memories, the methods disclosed herein may be encoded on the one or more network system local storages 140a . . . 140n by transforming the physical state of the semiconductor memory. For example, the methods may transform the state of transistors, capacitors, or other discrete circuit elements constituting the semiconductor memory. The methods also may transform the physical state of such components in order to store data thereupon.
As another example, the one or more network system local storages 140a . . . 140n described herein may be implemented using magnetic or optical technology. In such implementations, the methods presented herein may transform the physical state of magnetic or optical media, when the methods are encoded therein. These transformations may include altering the magnetic characteristics of particular locations within given magnetic media. These transformations also may include altering the physical features or characteristics of particular locations within given optical media, to change the optical characteristics of those locations. Other transformations of physical media are possible without departing from the scope and spirit of the present description, with the foregoing examples provided only to facilitate this description. In light of the above, it should be appreciated that many types of physical transformations take place in the potential system 100 in order to store and execute the software components presented herein.
In some embodiments, the multi-application network may function as a probabilistic network to transform vehicle data. In some embodiments, the one or more cloud storages 120, local storages 122, and/or one or more network system local storages 140a . . . 140n may contain historic vehicle data. In some embodiments, the one or more network systems 138a . . . 138n, one or more cloud servers 102, and one or more endpoint devices 104 may comprise a knowledge base generated using the historic vehicle data to generate improved vehicle output data.
All potential embodiments of user interface described above may be accessed through devices other than an endpoint device 104, such as through a cloud-based device or through one or more network servers 138a . . . 138n. Although one digital requester was often mentioned in the prior detailed descriptions, other embodiments comprise one or more digital requesters submitting information into the user interfaces. Any mention of a selectable object may comprise a clickable hyperlink, button, or icon to redirect a user to another digital location. Any mention of a singular network system may comprise one or more network systems 138a . . . 138n or one or more cloud servers 102.
The figures and descriptions provided herein may have been simplified to illustrate aspects that are relevant for a clear understanding of the herein described devices, systems, and methods, while eliminating, for the purpose of clarity, other aspects that may be found in typical similar devices, systems, and methods. Those of ordinary skill may recognize that other elements and/or operations may be desirable and/or necessary to implement the devices, systems, and methods described herein. But because such elements and operations are well known in the art, and because they do not facilitate a better understanding of the present disclosure, a discussion of such elements and operations may not be provided herein. However, the present disclosure is deemed to inherently include all such elements, variations, and modifications to the described aspects that would be known to those of ordinary skill in the art. Any other variation of fabrication, use, or application should be considered apparent as an alternative embodiment of the present invention.
The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting. For example, as used herein, the singular forms “a”, “an” and “the” may be intended to include the plural forms as well, unless the context clearly indicates otherwise. The terms “comprises,” “comprising,” “including,” and “having,” are inclusive and therefore specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. The method steps, processes, and operations described herein are not to be construed as necessarily requiring their performance in the particular order discussed or illustrated, unless specifically identified as an order of performance. It is also to be understood that additional or alternative steps may be employed.
As used herein, the term “if” may be construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context.
Although the terms first, second, third, etc., may be used herein to describe various elements, components, regions, layers and/or sections, these elements, components, regions, layers and/or sections should not be limited by these terms. These terms may be only used to distinguish one element, component, region, layer or section from another element, component, region, layer or section. That is, terms such as “first,” “second,” and other numerical terms, when used herein, do not imply a sequence or order unless clearly indicated by the context. These terms are used to distinguish one element from another. For example, a first object or step could be termed a second object or step, and, similarly, a second object or step could be termed a first object or step, without departing from the scope of the invention. The first object or step, and the second object or step, are both objects or steps, respectively, but they are not to be considered the same object or step.
Those with skill in the art will appreciate that while some terms in this disclosure may refer to absolutes, e.g., all source receiver traces, each of a plurality of objects, etc., the methods and techniques disclosed herein may also be performed on fewer than all of a given thing, e.g., performed on one or more components and/or performed on one or more source receiver traces. Accordingly, in instances in the disclosure where an absolute is used, the disclosure may also be interpreted to be referring to a subset.
Finally, the above descriptions of the implementations of the present disclosure have been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the present disclosure to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to explain the principles of the disclosed subject-matter and its practical applications, to thereby enable others skilled in the art to use the technology disclosed and various embodiments with various modifications as are suited to the particular use contemplated. It is intended that the scope of the present disclosure be limited not by this detailed description, but rather by the claims of this application. As will be understood by those familiar with the art, the present disclosure may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. It is appreciated that the term optimize/optimal and its variants (e.g., efficient or optimally) may simply indicate improving, rather than the ultimate form of ‘perfection’ or the like. Accordingly, the present disclosure is intended to be illustrative, but not limiting, of the scope of the present disclosure, which is set forth in the following claims.
The present application is a continuation of U.S. patent application Ser. No. 18/382,418, filed on Oct. 20, 2023, all the contents and disclosures of which are hereby incorporated by reference in their entirety for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3665397 | Di Napoli et al. | May 1972 | A |
| 4714989 | Billings | Dec 1987 | A |
| 4736294 | Gill et al. | Apr 1988 | A |
| 4757267 | Riskin | Jul 1988 | A |
| 4774663 | Musmanno et al. | Sep 1988 | A |
| 4788643 | Trippe et al. | Nov 1988 | A |
| 4797818 | Cotter | Jan 1989 | A |
| 4799156 | Shavit et al. | Jan 1989 | A |
| 4831526 | Luchs et al. | May 1989 | A |
| 4858121 | Barber et al. | Aug 1989 | A |
| 4891785 | Donohoo | Jan 1990 | A |
| 4897867 | Foster et al. | Jan 1990 | A |
| 4899292 | Montagna et al. | Feb 1990 | A |
| 4916611 | Doyle, Jr. et al. | Apr 1990 | A |
| 4931932 | Dalnekoff et al. | Jun 1990 | A |
| 4934419 | Lamont et al. | Jun 1990 | A |
| 4951196 | Jackson | Aug 1990 | A |
| 4984155 | Geier et al. | Jan 1991 | A |
| 5058044 | Stewart et al. | Oct 1991 | A |
| 5063506 | Brockwell et al. | Nov 1991 | A |
| 5182705 | Barr et al. | Jan 1993 | A |
| 5210687 | Wolfberg et al. | May 1993 | A |
| 5216592 | Mann et al. | Jun 1993 | A |
| 5218697 | Chung | Jun 1993 | A |
| 5224034 | Katz et al. | Jun 1993 | A |
| 5237499 | Garback | Aug 1993 | A |
| 5253165 | Leiseca et al. | Oct 1993 | A |
| 5262941 | Saladin et al. | Nov 1993 | A |
| 5270922 | Higgins | Dec 1993 | A |
| 5289369 | Hirshberg | Feb 1994 | A |
| 5309355 | Lockwood | May 1994 | A |
| 5311425 | Inada | May 1994 | A |
| 5319542 | King, Jr. et al. | Jun 1994 | A |
| 5355474 | Thuraisngham et al. | Oct 1994 | A |
| 5361199 | Shoquist et al. | Nov 1994 | A |
| 5369570 | Parad | Nov 1994 | A |
| 5375207 | Blakely et al. | Dec 1994 | A |
| 5390314 | Swanson | Feb 1995 | A |
| 5396600 | Thompson et al. | Mar 1995 | A |
| 5406475 | Kouchi et al. | Apr 1995 | A |
| 5422809 | Griffin et al. | Jun 1995 | A |
| 5432904 | Wong | Jul 1995 | A |
| 5465206 | Hilt et al. | Nov 1995 | A |
| 5471615 | Amatsu et al. | Nov 1995 | A |
| 5475585 | Bush | Dec 1995 | A |
| 5504674 | Chen et al. | Apr 1996 | A |
| 5506897 | Moore et al. | Apr 1996 | A |
| 5515268 | Yoda | May 1996 | A |
| 5528490 | Hill | Jun 1996 | A |
| 5530844 | Phillips et al. | Jun 1996 | A |
| 5544040 | Gerbaulet | Aug 1996 | A |
| 5544320 | Konrad | Aug 1996 | A |
| 5550734 | Tarter et al. | Aug 1996 | A |
| 5557515 | Abbruzzese et al. | Sep 1996 | A |
| 5557518 | Rosen | Sep 1996 | A |
| 5570283 | Shoolery et al. | Oct 1996 | A |
| 5581461 | Coll et al. | Dec 1996 | A |
| 5586312 | Johnson et al. | Dec 1996 | A |
| 5586313 | Schnittker et al. | Dec 1996 | A |
| 5588048 | Neville | Dec 1996 | A |
| 5592375 | Salmon et al. | Jan 1997 | A |
| 5592378 | Cameron et al. | Jan 1997 | A |
| 5640505 | Hearn et al. | Jun 1997 | A |
| 5644721 | Chung et al. | Jul 1997 | A |
| 5644778 | Burks et al. | Jul 1997 | A |
| 5664207 | Crumpler et al. | Sep 1997 | A |
| 5666493 | Wojcik et al. | Sep 1997 | A |
| 5694551 | Doyle et al. | Dec 1997 | A |
| 5696901 | Konrad | Dec 1997 | A |
| 5696965 | Dedrick | Dec 1997 | A |
| 5704045 | King et al. | Dec 1997 | A |
| 5710887 | Chelliah et al. | Jan 1998 | A |
| 5710889 | Clark et al. | Jan 1998 | A |
| 5712989 | Johnson et al. | Jan 1998 | A |
| 5721832 | Westrope et al. | Jan 1998 | A |
| 5721913 | Ackroff et al. | Feb 1998 | A |
| 5724520 | Goheen | Mar 1998 | A |
| 5726885 | Klein et al. | Mar 1998 | A |
| 5732398 | Tagawa | Mar 1998 | A |
| 5734823 | Saigh et al. | Mar 1998 | A |
| 5737215 | Schricker et al. | Apr 1998 | A |
| 5754772 | Leaf | May 1998 | A |
| 5754830 | Butts et al. | May 1998 | A |
| 5757925 | Faybishenko | May 1998 | A |
| 5758329 | Wojcik et al. | May 1998 | A |
| 5758341 | Voss | May 1998 | A |
| 5764981 | Brice et al. | Jun 1998 | A |
| 5768510 | Gish | Jun 1998 | A |
| 5768511 | Galvin et al. | Jun 1998 | A |
| 5774873 | Berent et al. | Jun 1998 | A |
| 5774883 | Andersen et al. | Jun 1998 | A |
| 5778178 | Arunachalam | Jul 1998 | A |
| 5781892 | Hunt et al. | Jul 1998 | A |
| 5784565 | Lewine | Jul 1998 | A |
| 5793966 | Amstein et al. | Aug 1998 | A |
| 5794207 | Walker et al. | Aug 1998 | A |
| 5796634 | Craport et al. | Aug 1998 | A |
| 5796967 | Filepp et al. | Aug 1998 | A |
| 5797126 | Helbling et al. | Aug 1998 | A |
| 5799157 | Escallon | Aug 1998 | A |
| 5799289 | Fukushima et al. | Aug 1998 | A |
| 5802293 | van der Sijpt | Sep 1998 | A |
| 5802530 | Van Hoff | Sep 1998 | A |
| 5805689 | Neville | Sep 1998 | A |
| 5805829 | Cohen et al. | Sep 1998 | A |
| 5808894 | Wiens et al. | Sep 1998 | A |
| 5809478 | Greco et al. | Sep 1998 | A |
| 5812067 | Bergholz et al. | Sep 1998 | A |
| 5818715 | Marshall et al. | Oct 1998 | A |
| 5819274 | Jackson, Jr. | Oct 1998 | A |
| 5832451 | Flake et al. | Nov 1998 | A |
| 5832452 | Schneider et al. | Nov 1998 | A |
| 5832454 | Jafri et al. | Nov 1998 | A |
| 5835724 | Smith | Nov 1998 | A |
| 5838910 | Domenikos et al. | Nov 1998 | A |
| 5838916 | Domenikos et al. | Nov 1998 | A |
| 5839112 | Schreitmueller et al. | Nov 1998 | A |
| 5839114 | Lynch et al. | Nov 1998 | A |
| 5842176 | Hunt et al. | Nov 1998 | A |
| 5845077 | Fawcett | Dec 1998 | A |
| 5847957 | Cohen et al. | Dec 1998 | A |
| 5848131 | Shaffer et al. | Dec 1998 | A |
| 5848241 | Misinai et al. | Dec 1998 | A |
| 5850446 | Berger et al. | Dec 1998 | A |
| 5857191 | Blackwell, Jr. et al. | Jan 1999 | A |
| 5862346 | Kley et al. | Jan 1999 | A |
| 5864818 | Feldman | Jan 1999 | A |
| 5864827 | Wilson | Jan 1999 | A |
| RE36111 | Neville | Feb 1999 | E |
| 5870719 | Maritzen et al. | Feb 1999 | A |
| 5870733 | Bass et al. | Feb 1999 | A |
| 5875110 | Jacobs | Feb 1999 | A |
| 5877765 | Dickman et al. | Mar 1999 | A |
| 5881230 | Christensen et al. | Mar 1999 | A |
| 5889863 | Weber | Mar 1999 | A |
| 5889942 | Orenshteyn | Mar 1999 | A |
| 5890129 | Spurgeon | Mar 1999 | A |
| 5890140 | Clark et al. | Mar 1999 | A |
| 5892905 | Brandt et al. | Apr 1999 | A |
| 5893904 | Harris et al. | Apr 1999 | A |
| 5897620 | Walker et al. | Apr 1999 | A |
| 5898835 | Truong | Apr 1999 | A |
| 5901214 | Shaffer et al. | May 1999 | A |
| 5903873 | Peterson et al. | May 1999 | A |
| 5904727 | Prabhakaran | May 1999 | A |
| 5909542 | Paquette et al. | Jun 1999 | A |
| 5909570 | Webber | Jun 1999 | A |
| 5909581 | Park | Jun 1999 | A |
| 5910982 | Shaffer et al. | Jun 1999 | A |
| 5915241 | Giannini | Jun 1999 | A |
| 5918215 | Yoshioka et al. | Jun 1999 | A |
| 5920696 | Brandt et al. | Jul 1999 | A |
| 5922040 | Prabhakaran | Jul 1999 | A |
| 5923552 | Brown et al. | Jul 1999 | A |
| 5926793 | de Rafael et al. | Jul 1999 | A |
| 5926798 | Carter | Jul 1999 | A |
| 5926817 | Christeson et al. | Jul 1999 | A |
| 5930474 | Dunworth et al. | Jul 1999 | A |
| 5931878 | Chapin, Jr. | Aug 1999 | A |
| 5931917 | Nguyen et al. | Aug 1999 | A |
| 5933810 | Okawa | Aug 1999 | A |
| 5944784 | Simonoff et al. | Aug 1999 | A |
| 5946660 | McCarty et al. | Aug 1999 | A |
| 5946687 | Gehani et al. | Aug 1999 | A |
| 5948040 | Delorme et al. | Sep 1999 | A |
| 5950169 | Borghesi et al. | Sep 1999 | A |
| 5953706 | Patel | Sep 1999 | A |
| 5956397 | Shaffer et al. | Sep 1999 | A |
| 5956487 | Venkatraman et al. | Sep 1999 | A |
| 5956509 | Kavner | Sep 1999 | A |
| 5956706 | Carey et al. | Sep 1999 | A |
| 5961569 | Craport et al. | Oct 1999 | A |
| 5961572 | Craport et al. | Oct 1999 | A |
| 5963915 | Kirsch | Oct 1999 | A |
| 5966451 | Utsumi | Oct 1999 | A |
| 5970475 | Barnes et al. | Oct 1999 | A |
| 5973619 | Paredes | Oct 1999 | A |
| 5974444 | Konrad | Oct 1999 | A |
| 5977966 | Bogdan | Nov 1999 | A |
| 5978577 | Rierden et al. | Nov 1999 | A |
| 5978747 | Craport et al. | Nov 1999 | A |
| 5978817 | Giannandrea et al. | Nov 1999 | A |
| 5978834 | Simonoff et al. | Nov 1999 | A |
| 5978840 | Nguyen et al. | Nov 1999 | A |
| 5982867 | Urban et al. | Nov 1999 | A |
| 5982868 | Shaffer et al. | Nov 1999 | A |
| 5983200 | Slotznick | Nov 1999 | A |
| 5983208 | Haller et al. | Nov 1999 | A |
| 5987423 | Arnold et al. | Nov 1999 | A |
| 5991739 | Cupps et al. | Nov 1999 | A |
| 5995939 | Berman et al. | Nov 1999 | A |
| 5996017 | Cipiere | Nov 1999 | A |
| 6002767 | Kramer | Dec 1999 | A |
| 6005568 | Simonoff et al. | Dec 1999 | A |
| 6006148 | Strong | Dec 1999 | A |
| 6006201 | Berent et al. | Dec 1999 | A |
| 6009464 | Hamilton et al. | Dec 1999 | A |
| 1830000 | Petrimouix et al. | Jan 2000 | A |
| 6012083 | Savitzky et al. | Jan 2000 | A |
| 6014673 | Davis et al. | Jan 2000 | A |
| 6014702 | King et al. | Jan 2000 | A |
| 6016496 | Roberson | Jan 2000 | A |
| 6016515 | Shaw et al. | Jan 2000 | A |
| 6018627 | Iyengar et al. | Jan 2000 | A |
| 6021406 | Kuznetsov | Feb 2000 | A |
| 6023679 | Acebo et al. | Feb 2000 | A |
| 6026379 | Haller et al. | Feb 2000 | A |
| 6029175 | Chow et al. | Feb 2000 | A |
| 6031533 | Peddada et al. | Feb 2000 | A |
| 6043815 | Simonoff et al. | Mar 2000 | A |
| 6044382 | Martino | Mar 2000 | A |
| 6049671 | Slivka et al. | Apr 2000 | A |
| 6049774 | Roy | Apr 2000 | A |
| 6049832 | Brim et al. | Apr 2000 | A |
| 6054983 | Simonoff et al. | Apr 2000 | A |
| 6058179 | Shaffer et al. | May 2000 | A |
| 6058378 | Clark et al. | May 2000 | A |
| 6061665 | Bahreman | May 2000 | A |
| 6061691 | Fox | May 2000 | A |
| 6064973 | Smith et al. | May 2000 | A |
| 6067531 | Hoyt et al. | May 2000 | A |
| 6070142 | McDonough et al. | May 2000 | A |
| 6072870 | Nguyen et al. | Jun 2000 | A |
| 6073163 | Clark et al. | Jun 2000 | A |
| 6073214 | Fawcett | Jun 2000 | A |
| 6076066 | DiRienzo et al. | Jun 2000 | A |
| 6076067 | Jacobs et al. | Jun 2000 | A |
| 6078321 | Simonoff et al. | Jun 2000 | A |
| 6078322 | Simonoff et al. | Jun 2000 | A |
| 6084585 | Kraft et al. | Jul 2000 | A |
| 6085169 | Walker et al. | Jul 2000 | A |
| 6085170 | Tsukuda | Jul 2000 | A |
| 6088677 | Spurgeon | Jul 2000 | A |
| 6091409 | Dickman et al. | Jul 2000 | A |
| 6091412 | Simonoff et al. | Jul 2000 | A |
| 6091810 | Shaffer et al. | Jul 2000 | A |
| 6094640 | Goheen | Jul 2000 | A |
| 6094679 | Teng et al. | Jul 2000 | A |
| 6097802 | Fleischer, III et al. | Aug 2000 | A |
| 6101496 | Esposito | Aug 2000 | A |
| 6108650 | Musk et al. | Aug 2000 | A |
| 6112185 | Walker et al. | Aug 2000 | A |
| 6119105 | Williams | Sep 2000 | A |
| 6119149 | Notani | Sep 2000 | A |
| 6122642 | Mehovic | Sep 2000 | A |
| 6125384 | Brandt et al. | Sep 2000 | A |
| 6125391 | Meltzer et al. | Sep 2000 | A |
| 6144944 | Kurtzman, II et al. | Nov 2000 | A |
| 6144990 | Brandt et al. | Nov 2000 | A |
| 6148289 | Virdy | Nov 2000 | A |
| 6148290 | Dan et al. | Nov 2000 | A |
| 6154172 | Piccionelli et al. | Nov 2000 | A |
| 6163772 | Kramer et al. | Dec 2000 | A |
| 6167567 | Chiles et al. | Dec 2000 | A |
| 6175832 | Luzzi et al. | Jan 2001 | B1 |
| 6178409 | Weber et al. | Jan 2001 | B1 |
| 6185290 | Shaffer et al. | Feb 2001 | B1 |
| 6185540 | Schreitmueller et al. | Feb 2001 | B1 |
| 6189003 | Leal | Feb 2001 | B1 |
| 6192347 | Graff | Feb 2001 | B1 |
| 6192415 | Haverstock et al. | Feb 2001 | B1 |
| 6205482 | Navarre et al. | Mar 2001 | B1 |
| 6223094 | Muehleck et al. | Apr 2001 | B1 |
| 6226654 | Van Hoff | May 2001 | B1 |
| 6226675 | Meltzer et al. | May 2001 | B1 |
| 6229534 | Gerra et al. | May 2001 | B1 |
| 6230117 | Lymer et al. | May 2001 | B1 |
| 6233329 | Urban et al. | May 2001 | B1 |
| 6233609 | Mittal | May 2001 | B1 |
| 6240365 | Bunn | May 2001 | B1 |
| 6243643 | Uematsu | Jun 2001 | B1 |
| 6253188 | Witek et al. | Jun 2001 | B1 |
| 6263322 | Kirkevold et al. | Jul 2001 | B1 |
| 6272528 | Cullen et al. | Aug 2001 | B1 |
| 6272675 | Schrab et al. | Aug 2001 | B1 |
| 6275843 | Chorn | Aug 2001 | B1 |
| 6282489 | Bellesfield et al. | Aug 2001 | B1 |
| 6282517 | Wolfe et al. | Aug 2001 | B1 |
| 6282568 | Sondur et al. | Aug 2001 | B1 |
| 6286028 | Cohen et al. | Sep 2001 | B1 |
| 6292185 | Ko et al. | Sep 2001 | B1 |
| 6298333 | Manzi et al. | Oct 2001 | B1 |
| 6304892 | Bhoj et al. | Oct 2001 | B1 |
| 6308120 | Good | Oct 2001 | B1 |
| 6308160 | Rex | Oct 2001 | B1 |
| 6311207 | Mighdoll et al. | Oct 2001 | B1 |
| 6311213 | Dawson et al. | Oct 2001 | B2 |
| 6324568 | Diec | Nov 2001 | B1 |
| 6327574 | Kramer et al. | Dec 2001 | B1 |
| 6327617 | Fawcett | Dec 2001 | B1 |
| 6332163 | Bowman-Amuah | Dec 2001 | B1 |
| 6334146 | Parasnis et al. | Dec 2001 | B1 |
| 6336100 | Yamada | Jan 2002 | B1 |
| 6339773 | Rishe | Jan 2002 | B1 |
| 6343290 | Cossins et al. | Jan 2002 | B1 |
| 6347302 | Joao | Feb 2002 | B1 |
| 6347398 | Parthasarathy et al. | Feb 2002 | B1 |
| 6351738 | Clark | Feb 2002 | B1 |
| 6360205 | Iyengar et al. | Mar 2002 | B1 |
| 6363388 | Sprenger et al. | Mar 2002 | B1 |
| 6370523 | Anderson | Apr 2002 | B1 |
| 6381324 | Shaffer et al. | Apr 2002 | B1 |
| 6381603 | Chan et al. | Apr 2002 | B1 |
| 6381617 | Frolund et al. | Apr 2002 | B1 |
| 6385312 | Shaffer et al. | May 2002 | B1 |
| 6389431 | Frolund et al. | May 2002 | B1 |
| 6393415 | Getchius et al. | May 2002 | B1 |
| 6393471 | Kobata | May 2002 | B1 |
| 6397191 | Notani et al. | May 2002 | B1 |
| 6397208 | Lee | May 2002 | B1 |
| 6397219 | Mills | May 2002 | B2 |
| 6401094 | Stemp et al. | Jun 2002 | B1 |
| 6418400 | Webber | Jul 2002 | B1 |
| 6418554 | Delo et al. | Jul 2002 | B1 |
| 6445309 | Walker et al. | Sep 2002 | B1 |
| 6477452 | Good | Nov 2002 | B2 |
| 6502080 | Eichorst et al. | Dec 2002 | B1 |
| 6505106 | Lawrence et al. | Jan 2003 | B1 |
| 6526392 | Dietrich et al. | Feb 2003 | B1 |
| 6542912 | Meltzer et al. | Apr 2003 | B2 |
| 6567783 | Notani et al. | May 2003 | B1 |
| 6587836 | Ahlberg et al. | Jul 2003 | B1 |
| 6587841 | DeFrancesco et al. | Jul 2003 | B1 |
| 6594633 | Broerman | Jul 2003 | B1 |
| 6609050 | Li | Aug 2003 | B2 |
| 6609108 | Pulliam et al. | Aug 2003 | B1 |
| 6609118 | Khedkar et al. | Aug 2003 | B1 |
| 6622129 | Whitworth | Sep 2003 | B1 |
| 6654726 | Hanzek | Nov 2003 | B1 |
| 6654770 | Kaufman | Nov 2003 | B2 |
| 6694234 | Lockwood et al. | Feb 2004 | B2 |
| 6701232 | Yamaki | Mar 2004 | B2 |
| 6725201 | Joao | Apr 2004 | B2 |
| 6728685 | Ahluwalia | Apr 2004 | B1 |
| 6732358 | Siefert | May 2004 | B1 |
| 6748426 | Shaffer et al. | Jun 2004 | B1 |
| 6757698 | McBride et al. | Jun 2004 | B2 |
| 6785658 | Merker et al. | Aug 2004 | B1 |
| 6802061 | Parthasarathy et al. | Oct 2004 | B1 |
| 6810401 | Thompson et al. | Oct 2004 | B1 |
| 6823319 | Lynch et al. | Nov 2004 | B1 |
| 6910040 | Emmick et al. | Jun 2005 | B2 |
| 6950826 | Freeman | Sep 2005 | B1 |
| 6952680 | Melby et al. | Oct 2005 | B1 |
| 6965886 | Govrin et al. | Nov 2005 | B2 |
| 6968388 | Fuldseth et al. | Nov 2005 | B1 |
| 6976251 | Meyerson | Dec 2005 | B2 |
| 7020620 | Bargnes et al. | Mar 2006 | B1 |
| 7050986 | Vance et al. | May 2006 | B1 |
| 7062765 | Pitzel et al. | Jun 2006 | B1 |
| 7089588 | Schaefer et al. | Aug 2006 | B2 |
| 7124088 | Bauer et al. | Oct 2006 | B2 |
| 7136821 | Kohavi et al. | Nov 2006 | B1 |
| 7145998 | Holder et al. | Dec 2006 | B1 |
| 7184978 | Tams et al. | Feb 2007 | B1 |
| 7243075 | Shaffer et al. | Jul 2007 | B1 |
| 7275038 | Weinstock et al. | Sep 2007 | B1 |
| 7283972 | Himes | Oct 2007 | B2 |
| 7324951 | Renwick et al. | Jan 2008 | B2 |
| 7328166 | Geoghehan et al. | Feb 2008 | B1 |
| 7636676 | Wolery et al. | Dec 2009 | B1 |
| 7685063 | Schuchardt et al. | Mar 2010 | B2 |
| 7899690 | Weinstock et al. | Mar 2011 | B1 |
| 8160906 | Smith et al. | Apr 2012 | B2 |
| 8160907 | Smith et al. | Apr 2012 | B2 |
| 8340989 | Weinstock et al. | Dec 2012 | B2 |
| 8374894 | Weinstock et al. | Feb 2013 | B2 |
| 8401881 | Weinstock et al. | Mar 2013 | B2 |
| 8412546 | Smith et al. | Apr 2013 | B2 |
| 8600783 | Smith et al. | Dec 2013 | B2 |
| 8712893 | Brandmaier et al. | Apr 2014 | B1 |
| 8775222 | Smith et al. | Jul 2014 | B2 |
| 9449495 | Call et al. | Sep 2016 | B1 |
| 9721304 | Parchment et al. | Aug 2017 | B1 |
| 9773281 | Hanson | Sep 2017 | B1 |
| 9990661 | Taylor | Jun 2018 | B2 |
| 10013718 | Leise | Jul 2018 | B1 |
| 10354230 | Hanson et al. | Jul 2019 | B1 |
| 10366352 | Smith et al. | Jul 2019 | B2 |
| 10929920 | Smith et al. | Feb 2021 | B2 |
| 11037107 | Hanson et al. | Jun 2021 | B1 |
| 20010005831 | Lewin et al. | Jun 2001 | A1 |
| 20010008998 | Tamaki et al. | Jul 2001 | A1 |
| 20010010058 | Mittal | Jul 2001 | A1 |
| 20010011222 | McLauchlin et al. | Aug 2001 | A1 |
| 20010011246 | Tammaro | Aug 2001 | A1 |
| 20010014907 | Brebner | Aug 2001 | A1 |
| 20010016825 | Pugliese, III et al. | Aug 2001 | A1 |
| 20010016868 | Nakamura et al. | Aug 2001 | A1 |
| 20010018661 | Sato et al. | Aug 2001 | A1 |
| 20010021912 | DeMarcken et al. | Sep 2001 | A1 |
| 20010027420 | Boublik et al. | Oct 2001 | A1 |
| 20010027439 | Holtzman et al. | Oct 2001 | A1 |
| 20010027483 | Gupta et al. | Oct 2001 | A1 |
| 20010029459 | Fujiwara | Oct 2001 | A1 |
| 20010032113 | Rudnick | Oct 2001 | A1 |
| 20010032273 | Cheng | Oct 2001 | A1 |
| 20010034686 | Eder | Oct 2001 | A1 |
| 20010034690 | Joseph | Oct 2001 | A1 |
| 20010034700 | Foss et al. | Oct 2001 | A1 |
| 20010037224 | Eldridge et al. | Nov 2001 | A1 |
| 20010037255 | Tambay et al. | Nov 2001 | A1 |
| 20010037298 | Ehrman et al. | Nov 2001 | A1 |
| 20010037331 | Lloyd | Nov 2001 | A1 |
| 20010039525 | Messmer et al. | Nov 2001 | A1 |
| 20010044811 | Ballantyne et al. | Nov 2001 | A1 |
| 20010049653 | Sheets | Dec 2001 | A1 |
| 20010056361 | Sendouda | Dec 2001 | A1 |
| 20020002478 | Swart et al. | Jan 2002 | A1 |
| 20020004796 | Vange et al. | Jan 2002 | A1 |
| 20020007289 | Malin et al. | Jan 2002 | A1 |
| 20020010604 | Block | Jan 2002 | A1 |
| 20020010781 | Tuatini | Jan 2002 | A1 |
| 20020013767 | Katz | Jan 2002 | A1 |
| 20020016655 | Joao | Feb 2002 | A1 |
| 20020019821 | Rosenbluth | Feb 2002 | A1 |
| 20020022979 | Whipp et al. | Feb 2002 | A1 |
| 20020026336 | Eizenburg et al. | Feb 2002 | A1 |
| 20020026337 | Sasaki | Feb 2002 | A1 |
| 20020032626 | DeWolf et al. | Mar 2002 | A1 |
| 20020032706 | Perla et al. | Mar 2002 | A1 |
| 20020032790 | Linderman | Mar 2002 | A1 |
| 20020035488 | Aquila et al. | Mar 2002 | A1 |
| 20020035592 | Wu et al. | Mar 2002 | A1 |
| 20020038272 | Menchero | Mar 2002 | A1 |
| 20020040352 | McCormick | Apr 2002 | A1 |
| 20020042843 | Diec | Apr 2002 | A1 |
| 20020042849 | Ho et al. | Apr 2002 | A1 |
| 20020046143 | Eder | Apr 2002 | A1 |
| 20020046144 | Graff | Apr 2002 | A1 |
| 20020046213 | Vinati et al. | Apr 2002 | A1 |
| 20020046294 | Brodsky et al. | Apr 2002 | A1 |
| 20020046301 | Shannon et al. | Apr 2002 | A1 |
| 20020049603 | Mehra et al. | Apr 2002 | A1 |
| 20020049659 | Johnson et al. | Apr 2002 | A1 |
| 20020059345 | Wang et al. | May 2002 | A1 |
| 20020062262 | Vasconi et al. | May 2002 | A1 |
| 20020065690 | Kusumoto | May 2002 | A1 |
| 20020065698 | Schick et al. | May 2002 | A1 |
| 20020065707 | Lancaster et al. | May 2002 | A1 |
| 20020069123 | Soderlind et al. | Jun 2002 | A1 |
| 20020069143 | Cepeda | Jun 2002 | A1 |
| 20020072937 | Domenick et al. | Jun 2002 | A1 |
| 20020072938 | Black et al. | Jun 2002 | A1 |
| 20020072958 | Yuyama et al. | Jun 2002 | A1 |
| 20020073012 | Lowell et al. | Jun 2002 | A1 |
| 20020073236 | Helgeson et al. | Jun 2002 | A1 |
| 20020076029 | Shaffer et al. | Jun 2002 | A1 |
| 20020077871 | Udelhoven et al. | Jun 2002 | A1 |
| 20020077944 | Bly et al. | Jun 2002 | A1 |
| 20020082860 | Johnson | Jun 2002 | A1 |
| 20020082899 | Aley | Jun 2002 | A1 |
| 20020082912 | Batachia et al. | Jun 2002 | A1 |
| 20020082966 | O'Brien et al. | Jun 2002 | A1 |
| 20020083095 | Wu et al. | Jun 2002 | A1 |
| 20020083099 | Knauss et al. | Jun 2002 | A1 |
| 20020087374 | Boubez et al. | Jul 2002 | A1 |
| 20020087378 | Como | Jul 2002 | A1 |
| 20020091533 | Ims et al. | Jul 2002 | A1 |
| 20020095319 | Swart et al. | Jul 2002 | A1 |
| 20020099562 | Bruce, Sr. et al. | Jul 2002 | A1 |
| 20020099575 | Hubbard et al. | Jul 2002 | A1 |
| 20020099613 | Swart et al. | Jul 2002 | A1 |
| 20020099618 | Stiberman | Jul 2002 | A1 |
| 20020099735 | Schroeder et al. | Jul 2002 | A1 |
| 20020099738 | Grant | Jul 2002 | A1 |
| 20020106069 | Shaffer et al. | Aug 2002 | A1 |
| 20020107873 | Winkler et al. | Aug 2002 | A1 |
| 20020107918 | Shaffer et al. | Aug 2002 | A1 |
| 20020111846 | Singer | Aug 2002 | A1 |
| 20020111876 | Rudraraju et al. | Aug 2002 | A1 |
| 20020116205 | Ankireddipally et al. | Aug 2002 | A1 |
| 20020116236 | Johnson et al. | Aug 2002 | A1 |
| 20020116309 | Keyes et al. | Aug 2002 | A1 |
| 20020116454 | Dyla et al. | Aug 2002 | A1 |
| 20020120459 | Dick et al. | Aug 2002 | A1 |
| 20020120776 | Eggebraaten et al. | Aug 2002 | A1 |
| 20020128864 | Maus et al. | Sep 2002 | A1 |
| 20020128985 | Greenwald | Sep 2002 | A1 |
| 20020129021 | Brown | Sep 2002 | A1 |
| 20020133359 | Brown | Sep 2002 | A1 |
| 20020133517 | Carlson et al. | Sep 2002 | A1 |
| 20020136381 | Shaffer et al. | Sep 2002 | A1 |
| 20020138379 | Yuasa et al. | Sep 2002 | A1 |
| 20020143644 | Tosun et al. | Oct 2002 | A1 |
| 20020143673 | Hitchings et al. | Oct 2002 | A1 |
| 20020143819 | Han et al. | Oct 2002 | A1 |
| 20020147601 | Fagan | Oct 2002 | A1 |
| 20020152092 | Bibas et al. | Oct 2002 | A1 |
| 20020152100 | Chen et al. | Oct 2002 | A1 |
| 20020156693 | Stewart et al. | Oct 2002 | A1 |
| 20020156865 | Rajarajan et al. | Oct 2002 | A1 |
| 20020169658 | Adler | Nov 2002 | A1 |
| 20020169842 | Christensen et al. | Nov 2002 | A1 |
| 20020171650 | Prabhakaran | Nov 2002 | A1 |
| 20020177926 | Lockwood et al. | Nov 2002 | A1 |
| 20020178080 | Ly et al. | Nov 2002 | A1 |
| 20020178087 | Henderson et al. | Nov 2002 | A1 |
| 20020178129 | Horimoto et al. | Nov 2002 | A1 |
| 20020178147 | Arroyo et al. | Nov 2002 | A1 |
| 20020184054 | Cox et al. | Dec 2002 | A1 |
| 20020184219 | Preisig et al. | Dec 2002 | A1 |
| 20020184266 | Blessin | Dec 2002 | A1 |
| 20020186144 | Meunier | Dec 2002 | A1 |
| 20020188761 | Chikirivao et al. | Dec 2002 | A1 |
| 20020194218 | Bradley et al. | Dec 2002 | A1 |
| 20020194219 | Bradley et al. | Dec 2002 | A1 |
| 20020198743 | Ariathurai et al. | Dec 2002 | A1 |
| 20020198797 | Cooper et al. | Dec 2002 | A1 |
| 20020198820 | Mills | Dec 2002 | A1 |
| 20030004746 | Kheirolomoom et al. | Jan 2003 | A1 |
| 20030004822 | Shorter et al. | Jan 2003 | A1 |
| 20030004937 | Salmenkaita et al. | Jan 2003 | A1 |
| 20030005181 | Bau et al. | Jan 2003 | A1 |
| 20030009545 | Sahai et al. | Jan 2003 | A1 |
| 20030014270 | Qureshi et al. | Jan 2003 | A1 |
| 20030014295 | Brookes et al. | Jan 2003 | A1 |
| 20030014352 | Marzan | Jan 2003 | A1 |
| 20030014442 | Shiigi et al. | Jan 2003 | A1 |
| 20030014733 | Ringseth et al. | Jan 2003 | A1 |
| 20030018551 | Hanson et al. | Jan 2003 | A1 |
| 20030018666 | Chen et al. | Jan 2003 | A1 |
| 20030023450 | Casati et al. | Jan 2003 | A1 |
| 20030023463 | Dombroski et al. | Jan 2003 | A1 |
| 20030023545 | Hawkins et al. | Jan 2003 | A1 |
| 20030023957 | Bau et al. | Jan 2003 | A1 |
| 20030028404 | Herron et al. | Feb 2003 | A1 |
| 20030028533 | Bata et al. | Feb 2003 | A1 |
| 20030033242 | Lynch et al. | Feb 2003 | A1 |
| 20030033369 | Bernard | Feb 2003 | A1 |
| 20030036891 | Aragones et al. | Feb 2003 | A1 |
| 20030036917 | Hite et al. | Feb 2003 | A1 |
| 20030036930 | Matos et al. | Feb 2003 | A1 |
| 20030036964 | Boyden et al. | Feb 2003 | A1 |
| 20030036966 | Amra et al. | Feb 2003 | A1 |
| 20030041012 | Grey et al. | Feb 2003 | A1 |
| 20030041180 | Schlussman | Feb 2003 | A1 |
| 20030046179 | Anabtawi et al. | Mar 2003 | A1 |
| 20030046199 | Murase et al. | Mar 2003 | A1 |
| 20030050942 | Ruellan et al. | Mar 2003 | A1 |
| 20030055666 | Roddy et al. | Mar 2003 | A1 |
| 20030055868 | Fletcher et al. | Mar 2003 | A1 |
| 20030061137 | Leung et al. | Mar 2003 | A1 |
| 20030061158 | Guy et al. | Mar 2003 | A1 |
| 20030069837 | Mills et al. | Apr 2003 | A1 |
| 20030074296 | Blanchard et al. | Apr 2003 | A1 |
| 20030074423 | Mayberry et al. | Apr 2003 | A1 |
| 20030093402 | Upton | May 2003 | A1 |
| 20030093403 | Upton | May 2003 | A1 |
| 20030093470 | Upton | May 2003 | A1 |
| 20030093575 | Upton | May 2003 | A1 |
| 20030097286 | Skeen | May 2003 | A1 |
| 20030101087 | Walker et al. | May 2003 | A1 |
| 20030101190 | Horvitz et al. | May 2003 | A1 |
| 20030110112 | Johnson et al. | Jun 2003 | A1 |
| 20030110315 | Upton | Jun 2003 | A1 |
| 20030114967 | Good | Jun 2003 | A1 |
| 20030115548 | Melgar | Jun 2003 | A1 |
| 20030115572 | Zondervan et al. | Jun 2003 | A1 |
| 20030120464 | Taft et al. | Jun 2003 | A1 |
| 20030120502 | Robb et al. | Jun 2003 | A1 |
| 20030120509 | Bruch et al. | Jun 2003 | A1 |
| 20030120526 | Altman et al. | Jun 2003 | A1 |
| 20030120586 | Litty et al. | Jun 2003 | A1 |
| 20030120665 | Fox et al. | Jun 2003 | A1 |
| 20030125992 | Rogers et al. | Jul 2003 | A1 |
| 20030126047 | Hollar et al. | Jul 2003 | A1 |
| 20030126048 | Hollar et al. | Jul 2003 | A1 |
| 20030126063 | Reuter et al. | Jul 2003 | A1 |
| 20030126098 | Hine et al. | Jul 2003 | A1 |
| 20030130966 | Thompson et al. | Jul 2003 | A1 |
| 20030131073 | Lucovsky et al. | Jul 2003 | A1 |
| 20030135447 | Blanz et al. | Jul 2003 | A1 |
| 20030135584 | Roberts et al. | Jul 2003 | A1 |
| 20030139985 | Hollar et al. | Jul 2003 | A1 |
| 20030139993 | Feuerverger | Jul 2003 | A1 |
| 20030140057 | Thomas et al. | Jul 2003 | A1 |
| 20030145047 | Upton | Jul 2003 | A1 |
| 20030145067 | Cover et al. | Jul 2003 | A1 |
| 20030149600 | Williams | Aug 2003 | A1 |
| 20030154111 | Dutra et al. | Aug 2003 | A1 |
| 20030154142 | Ginsburg et al. | Aug 2003 | A1 |
| 20030177133 | Hikida | Sep 2003 | A1 |
| 20030187765 | Sgaraglio | Oct 2003 | A1 |
| 20030200151 | Ellenson et al. | Oct 2003 | A1 |
| 20030216976 | Ehrman et al. | Nov 2003 | A1 |
| 20030216995 | DePauw et al. | Nov 2003 | A1 |
| 20030225643 | Kakoschke | Dec 2003 | A1 |
| 20030225707 | Ehrman et al. | Dec 2003 | A1 |
| 20040001575 | Tang | Jan 2004 | A1 |
| 20040015394 | Mok et al. | Jan 2004 | A1 |
| 20040019516 | Puskorius et al. | Jan 2004 | A1 |
| 20040036716 | Jordahl | Feb 2004 | A1 |
| 20040039504 | Coffee et al. | Feb 2004 | A1 |
| 20040039612 | Fitzgerald et al. | Feb 2004 | A1 |
| 20040039678 | Fralic | Feb 2004 | A1 |
| 20040054600 | Shike et al. | Mar 2004 | A1 |
| 20040064393 | Luenberger | Apr 2004 | A1 |
| 20040073468 | Vyas et al. | Apr 2004 | A1 |
| 20040075581 | Staniszewski | Apr 2004 | A1 |
| 20040078318 | Miller | Apr 2004 | A1 |
| 20040088104 | Izbicki et al. | May 2004 | A1 |
| 20040093134 | Barber et al. | May 2004 | A1 |
| 20040107144 | Short | Jun 2004 | A1 |
| 20040111330 | Stanton | Jun 2004 | A1 |
| 20040122621 | Vezzu et al. | Jun 2004 | A1 |
| 20040133456 | Nagelvoort | Jul 2004 | A1 |
| 20040148241 | Qi et al. | Jul 2004 | A1 |
| 20040153356 | Lockwood et al. | Aug 2004 | A1 |
| 20040172227 | Aragones | Sep 2004 | A1 |
| 20040172260 | Junger et al. | Sep 2004 | A1 |
| 20040172304 | Joao | Sep 2004 | A1 |
| 20040186620 | Chirnomas | Sep 2004 | A1 |
| 20040215630 | Parekh et al. | Oct 2004 | A1 |
| 20040243423 | Rix et al. | Dec 2004 | A1 |
| 20040243619 | Kelly et al. | Dec 2004 | A1 |
| 20050021378 | Weinstock et al. | Jan 2005 | A1 |
| 20050055351 | Barton et al. | Mar 2005 | A1 |
| 20050091087 | Smith et al. | Apr 2005 | A1 |
| 20050119921 | Fitzgerald et al. | Jun 2005 | A1 |
| 20050125261 | Adegan | Jun 2005 | A1 |
| 20050144048 | Belanger et al. | Jun 2005 | A1 |
| 20050171900 | Onneken | Aug 2005 | A1 |
| 20050187833 | Royer et al. | Aug 2005 | A1 |
| 20050197866 | Salcedo et al. | Sep 2005 | A1 |
| 20050216385 | Schneider | Sep 2005 | A1 |
| 20050228756 | Bealke et al. | Oct 2005 | A1 |
| 20050234792 | Gagnon et al. | Oct 2005 | A1 |
| 20050246206 | Obora et al. | Nov 2005 | A1 |
| 20060031041 | Afshar et al. | Feb 2006 | A1 |
| 20060035692 | Kirby et al. | Feb 2006 | A1 |
| 20060140348 | Wallace et al. | Jun 2006 | A1 |
| 20060190273 | Wilbrink et al. | Aug 2006 | A1 |
| 20060265235 | Schuchardt et al. | Nov 2006 | A1 |
| 20070174081 | Smith et al. | Jul 2007 | A1 |
| 20070198311 | Menendez et al. | Aug 2007 | A1 |
| 20070203777 | Berkey et al. | Aug 2007 | A1 |
| 20070239494 | Stephens et al. | Oct 2007 | A1 |
| 20070260496 | Weinstock et al. | Nov 2007 | A1 |
| 20070271124 | Weinstock et al. | Nov 2007 | A1 |
| 20070271125 | Weinstock et al. | Nov 2007 | A1 |
| 20070271128 | Terrence Bolling | Nov 2007 | A1 |
| 20070294116 | Stephens et al. | Dec 2007 | A1 |
| 20080010105 | Rose et al. | Jan 2008 | A1 |
| 20080046261 | Cunningham | Feb 2008 | A1 |
| 20080097798 | DeVallance et al. | Apr 2008 | A1 |
| 20080133281 | Bolt et al. | Jun 2008 | A1 |
| 20080140460 | Smith et al. | Jun 2008 | A1 |
| 20080162199 | Smith et al. | Jul 2008 | A1 |
| 20080243562 | Weinstock et al. | Oct 2008 | A1 |
| 20080243563 | Weinstock et al. | Oct 2008 | A1 |
| 20080249814 | Weinstock et al. | Oct 2008 | A1 |
| 20090018859 | Purifoy et al. | Jan 2009 | A1 |
| 20090030747 | Smith et al. | Jan 2009 | A1 |
| 20090099732 | Pisz | Apr 2009 | A1 |
| 20090215466 | Ahl et al. | Aug 2009 | A1 |
| 20090216552 | Watrous | Aug 2009 | A1 |
| 20100023352 | Smith et al. | Jan 2010 | A1 |
| 20110153372 | Weinstock et al. | Jun 2011 | A1 |
| 20110153375 | Weinstock et al. | Jun 2011 | A1 |
| 20110313951 | Cook | Dec 2011 | A1 |
| 20120197672 | Smith et al. | Aug 2012 | A1 |
| 20120203580 | Smith et al. | Aug 2012 | A1 |
| 20120203581 | Smith et al. | Aug 2012 | A1 |
| 20120203582 | Smith et al. | Aug 2012 | A1 |
| 20130006469 | Green et al. | Jan 2013 | A1 |
| 20130041950 | Chan | Feb 2013 | A1 |
| 20130159033 | Weinstock et al. | Jun 2013 | A1 |
| 20130218614 | Weinstock et al. | Aug 2013 | A1 |
| 20130238373 | Smith et al. | Sep 2013 | A1 |
| 20130246104 | Weinstock et al. | Sep 2013 | A1 |
| 20140052478 | Weinstock et al. | Feb 2014 | A1 |
| 20140067429 | Lowell | Mar 2014 | A1 |
| 20140095228 | Smith et al. | Apr 2014 | A1 |
| 20140106712 | Scholz et al. | Apr 2014 | A1 |
| 20140200760 | Kaufmann et al. | Jul 2014 | A1 |
| 20140278572 | Mullen et al. | Sep 2014 | A1 |
| 20150158447 | Nonaka | Jun 2015 | A1 |
| 20150163832 | Hosey et al. | Jun 2015 | A1 |
| 20150172894 | Gabel | Jun 2015 | A1 |
| 20150178852 | Mullen | Jun 2015 | A1 |
| 20200265655 | Ha | Aug 2020 | A1 |
| 20200267503 | Watkins | Aug 2020 | A1 |
| 20210225094 | Salodkar et al. | Jul 2021 | A1 |
| Number | Date | Country |
|---|---|---|
| 1724719 | Nov 2006 | EP |
| 2001344490 | Dec 2001 | JP |
| 2002074126 | Mar 2002 | JP |
| 9966738 | Dec 1999 | WO |
| 0052601 | Sep 2000 | WO |
| 0197072 | Dec 2001 | WO |
| 0221314 | Mar 2002 | WO |
| 0229675 | Apr 2002 | WO |
| 02057873 | Jul 2002 | WO |
| 02067079 | Aug 2002 | WO |
| 02067175 | Aug 2002 | WO |
| 02080646 | Oct 2002 | WO |
| 02097700 | Dec 2002 | WO |
| 03067851 | Aug 2003 | WO |
| 2007062047 | May 2007 | WO |
| 2008073427 | Jun 2008 | WO |
| 2014207558 | Dec 2014 | WO |
| Entry |
|---|
| Reddy, Dasari Anantha, et al. “Automatic Vehicle Damage Detection Classification framework using Fast and Mask Deep learning.” 2022 Second International Conference on Computer Science, Engineering and Applications (ICCSEA). IEEE, 2022. (Year: 2022). |
| Ye, Hao, et al. “Machine learning for vehicular networks: Recent advances and application examples.” IEEE vehicular technology magazine 13.2 (2018): 94-101. (Year: 2018). |
| Fogue, Manuel, et al. “A system for automatic notification and severity estimation of automotive accidents.” IEEE Transactions on mobile computing 13.5 (2013): 948-963. (Year: 2013). |
| Examiner's Answer for U.S. Appl. No. 09/698,491 dated Jun. 5, 2007. |
| Examiner's Answer for U.S. Appl. No. 09/698,502 dated Apr. 25, 2005. |
| Examiner's Answer for U.S. Appl. No. 09/698,502 dated Mar. 7, 2007. |
| Examiner's Answer for U.S. Appl. No. 09/698,552 dated Dec. 9, 2008. |
| Examiner's Answer for U.S. Appl. No. 09/698,552 dated Jun. 28, 2007. |
| Examiner's Answer for U.S. Appl. No. 09/698,552 dated Mar. 8, 2007. |
| Specification and Drawings for U.S. Appl. No. 09/698,491. |
| Specification and Drawings for U.S. Appl. No. 09/698,502. |
| Specification and Drawings for U.S. Appl. No. 09/698, 552. |
| Office Action for U.S. Appl. No. 13/025,617 dated Apr. 27, 2012. |
| Response to Office Action for U.S. Appl. No. 11/823,782 dated Feb. 17, 2011. |
| Response to Office Action for U.S. Appl. No. 11/881.216 dated Sep. 28, 2011. |
| Response to Office Action for U.S. Appl. No. 11/881,383 dated Sep. 6, 2011. |
| Response to Office Action for U.S. Appl. No. 11/929,277 dated Aug. 18, 2011. |
| Response to Office Action for U.S. Appl. No. 11/929,350 dated Aug. 30, 2011. |
| U.S. Appl. No. 60/194,128, Aquila. |
| Notice of Allowance for U.S. Appl. No. 11/747,645 dated Dec. 28, 2011. |
| Office Action for U.S. Appl. No. 11/747,645 dated Aug. 27, 2010. |
| Office Action for U.S. Appl. No. 11/868,266 dated Sep. 30, 2010. |
| Office Action for U.S. Appl. No. 12/179,071 dated Sep. 14, 2010. |
| Office Action for U.S. Appl. No. 11/609,844 dated Mar. 23, 2011. |
| Response to Office Action for U.S. Appl. No. 11/747,645 dated Aug. 27, 2010. |
| Response to Office Action for U.S. Appl. No. 11/868,266 dated Sep. 30, 2010. |
| Response to Office Action for U.S. Appl. No. 11/929,277 dated Oct. 12, 2010. |
| Response to Office Action for U.S. Appl. No. 12/179,071 dated Sep. 14, 2010. |
| Prosecution History for U.S. Appl. No. 11/609,844, filed Dec. 12, 2006 (as of Apr. 20, 2011). |
| U.S. Appl. No. 09/596,024, filed Jun. 15, 2000, Shaffer et al. |
| U.S. Appl. No. 09/678,752, filed Oct. 3, 2000, Shaffer et al. |
| “AALA01: Lease Settlement Adjustment Direct Entry”, Apr. 8, 1997. |
| AALD01: Lease Unit Settlement, Jun. 1996. |
| Orion Systems, Ltd., System Overview and Handheld Terminals, downloaded from www.orsys.com on Dec. 1, 1997, pp. 1-5. |
| Orion Systems, Ltd., System Overview with Screens and Reports, May 1996. |
| Our Packages Come In All Sizes!, Nov. 1999, pp. 1-2. |
| PGMR, ECARS—Enterprise Computer Assisted Rental System, pp. 1-4. |
| Preview Travel, Inc., Car Reservations, 1999. |
| Rental 101, pp. 1-30. |
| Rental Redesign Requirements—Contract Process, pp. 1-5, Feb. 16, 2000. |
| Rental Redesign Requirements Contract, pp. 1-56, Feb. 15, 2000. |
| Rental Redesign, Rental Management, RMS (Rental Management Services), Sep. 30, 1998, pp. 1-2. |
| Rosen, Cheryl, “OTA Debuts Data Protocol”, Business Travel News, Jan. 10, 2000. |
| Rosen, Cheryl, “OTA Publishes XML Data Standard”, Business Travel News, pp. 1-2, Mar. 20, 2000. |
| The ARMS Connection, Safeco/Enterprise Rent-A-Car, pp. 1-4. |
| The Connection, State Farm Insurance/Enterprise Rent-A-Car, Rental Process Automation and Procedures, pp. 1-3. |
| The Hertz Corporation, 1998. |
| TSD Brochure, “Are You Comparing Apples to Apples When Choosing Rental Software”, pp. 1-3. |
| TSD Brochure, RENT 2000 from TSD, Rental Management Software, Revolutionize the Way You Do Business, pp. 1-29. |
| TSD Brochure, Rent 2000 from TSD, Rental Management Software, Revolutionize the Way You Do Business with the Proven Solution, pp. 1-2. |
| Warner, Fara, “Car Race in Cyberspace”. |
| Welcome to ARMS/400, New York State Rollout and Implementation Session, Oct. 28, 1999, pp. 1-51. |
| Welcome to the Data Warehouse, Jun. 2000, pp. 1-2. |
| Interactions, vol. 1, No. 3, Jul. 1992. |
| Interactions, Special Edition, vol. 1, No. 4, Aug. 1992. |
| Interactions, vol. 1, No. 5, Sep. 1992. |
| Interactions, Special Edition, Nov. 1992. |
| Interactions, vol. 1, No. 8, Dec. 1992. |
| Interactions, vol. 2, No. 1, Jan. 1993. |
| Interactions, vol. 2, No. 5, May 1993. |
| Interactions, vol. 2, No. 7, Jul. 1993. |
| Interactions, vol. 2, No. 8, Aug. 1993. |
| Interactions, vol. 2, No. 11, Oct. 1, 1993. |
| Interactions, vol. 2, No. 13, Nov. 1, 1993. |
| Interactions, vol. 2, No. 14, Nov. 15, 1993. |
| Interactions, Published especially for our Farmers adjusters, 1994. |
| Interactions, vol. 3, No. 1, Jan. I, 1994. |
| Interactions, vol. 3, No. 1, Jan. 15, 1994. |
| Interactions, ARMS, vol. 3, No. 6, Mar. 15, 1994. |
| Interactions, vol. 3, No. 8, Apr. 15, 1994. |
| Interactions, vol. 3, No. 10, May 15, 1994. |
| Interactions, vol. 3, No. 11, Jun. 1, 1994. |
| Interactions, vol. 3, No. 12, Jun. 15, 1994. |
| Interactions, vol. 3, No. 14, Jul. 15, 1994. |
| Interactions, vol. 3, No. 15, Aug. 1, 1994. |
| Interactions, vol. 3, No. 21, Nov. 1, 1994. |
| Interactions, vol. 3, No. 23, Dec. 1, 1994. |
| Interactions, vol. 4, No. 3, Feb. 1, 1995. |
| Interactions, “Electronic Connections”, p. 3, Mar. 15, 1995. |
| Interactions, vol. 4, No. 6, Mar. 15, 1995. |
| Interactions, vol. 4, No. 9, May 1, 1995. |
| Interactions, vol. 4, Issue 14, Jul. 15, 1995. |
| Interactions, vol. 4, Issue 16, Aug. 15, 1995. |
| Prosecution History for U.S. Appl. No. 11/929,277, filed Oct. 30, 2007 Parts 1 & 2 (as of Nov. 16, 2011). |
| Prosecution History for U.S. Appl. No. 11/929,350, filed Oct. 30, 2007 Parts 1 & 2 (as of Nov. 16, 2011). |
| Office Action for U.S. Appl. No. 1 1/881.216 dated Sep. 28, 2011. |
| Jul. 11, 2018—U.S. Non-Final Office Action—U.S. Appl. No. 15/009,418. |
| Travel Web site Expedia's shares takes off during initial offering, Reeves, Nov. 1999, Denver Post, p. C-02, entire document. |
| Copyright Chronicle Publishing Company, May 2, 1997, “Booking a room, vehicle for vacation via the 'Net”, Pantagraph, C. 1. |
| Yenckel, James T., Feb. 11, 1996, “For This Cyberspace Visitor, Once Is More Than Enough”, The Washington Post (Pre-1997 Fulltext), ISSN 01908286, p. E.01. |
| U.S. Appl. No. 60/194,128, Aquila. “Information on Hertz Corporation”; Sep. 24, 2002; pp. 1-61. “Welcome to the Hertz Interactive Reservation Process”; Mar. 3, 2000; pp. 62-27. |
| “All Open Orders for Customer No. 218556”; Motorola Corporation; Nov. 23, 1999. |
| ARMS/400 Update, Mar. 15, 2000, pp. I-4. |
| Office Action for U.S. Appl. No. 10/343,576 dated Aug. 3, 2009. |
| Office Action for U.S. Appl. No. 10/343,576 dated Nov. 19, 2008. |
| U.S. Appl. No. 09/564,911, filed May 4, 2000 (Williams). |
| U.S. Appl. No. 09/694,050, filed Oct. 20, 2000 (Weinstock et al.). |
| U.S. Appl. No. 09/698,491, filed Oct. 27, 2000 (Menendez et al.). |
| U.S. Appl. No. 09/698,502, filed Oct. 27, 2000 (Menendez et al.). |
| U.S. Appl. No. 09/698,552, filed Oct. 27, 2000 (Menendez et al.). |
| U.S. Appl. No. 60/828,540, filed Oct. 6, 2006 (Smith et al.). |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 18382418 | Oct 2023 | US |
| Child | 18745961 | US |
