Patent Grant
12073448
The decision of buying or leasing a specific vehicle involves not only fulfilling the consumer's desired list of attributes for the vehicle, but also the consumer's ability to finance the purchase or lease of the specific vehicle with such attributes. Furthermore, the list of attributes and the financing options are interdependent, since the consumer's list of desired attributes may be affected by the ability to pay for such attributes, and the financing options available to the consumer are dependent on the vehicle's attributes which would affect the vehicle's price. The computer systems (and other computing devices) available to consumers today provide the ability to browse vehicles' attributes. Other systems available provide the ability to determine financing options available to consumers, independent of knowledge or the specific vehicles the consumer may be interested in. Additionally, vehicle seller systems may track the browsing history of consumers to determine which vehicles the consumer is interested in. There is currently no interconnection between all of the vehicle seller systems, financing systems, and consumer systems. Therefore, vehicle sellers are not made aware of the qualifications of such interested consumers and thus sellers may waste resources in attempts to sell a vehicle which the consumer cannot afford. The process of locating and purchasing a vehicle, or for selling the vehicle, using such independent systems is also much more time consuming and less efficient for the consumer as well as the car dealers and the lenders involved. Accordingly, systems and processes for integrating vehicle history report requests with requests for consumer information, processing the requested information against financing determination factors to determine a consumer's prequalified financing options, correlating these determinations with the consumer's browsing activities, and communicating such determinations to the consumer and the vehicle seller are desired.
The systems, methods, and devices of the invention each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of this invention as expressed by the claims which follow, some features will now be discussed briefly. After considering this discussion, and particularly after reading the section entitled “Detailed Description,” one will understand how the features of the various aspects of this invention provide advantages that include improved communications between access points and stations in a wireless network.
One aspect of this disclosure provides a vehicle history and prequalification system. The system comprises a computer system, having a processor and a memory, and a data storage module accessible by the computer system. The computer system is configured to provide an interface for operation by a user at a remote computing device and receive a request, via the interface, from the user regarding a vehicle history report of a vehicle, the request including at least one of a vehicle identification number (VIN) of the vehicle, a license plate of the vehicle, or other unique identifier of the vehicle. The computer system is also configured to prompt the user, via the interface, for an indication of user interest in a prequalification for a financing offer associated with the vehicle. The computer system is further configured to receive the indication of user interest in the prequalification, via the interface, the indication including personal information of the user. The data storage module is configured to retrieve data corresponding to the vehicle from at least one of a third party information database, an industry publication database, a safety ratings database, and a vehicle specification database. The data storage module is further configured to store the retrieved data according to the VIN, license plate, or other unique identifier for the vehicle. The data storage module is also configured to retrieve data corresponding to a determination regarding the prequalification for the financing offer. The data storage module is also further configured to store the retrieved data according to one or more unique identifiers for the user. The computer system is then further configured to convey, via the interface, the vehicle history report to the user, the vehicle history report generated based on the retrieved and stored data corresponding to the vehicle and convey, via the interface, the prequalification determination to the user.
Another aspect disclosed is a method, the method comprising providing an interface for operation by a user at a remote computing device and receiving a request, via the interface, from the user regarding a vehicle history report of a vehicle, the request including at least one of a vehicle identification number (VIN) of the vehicle, a license plate of the vehicle, or other unique identifier of the vehicle. The method also comprises prompting the user, via the interface, for an indication of user interest in a prequalification for a financing offer associated with the vehicle and receiving the indication of user interest in the prequalification, via the interface, the indication including personal information of the user. The method further comprises retrieving data corresponding to the vehicle from at least one of a third party information database, an industry publication database, a safety ratings database, and a vehicle specification database and storing the retrieved data according to the VIN, license plate, or other unique identifier for the vehicle. The method also further comprises retrieving data corresponding to a determination regarding the prequalification for the financing offer and storing the retrieved data according to one or more unique identifiers for the user. The method further also comprises conveying, via the interface, the vehicle history report to the user, the vehicle history report generated based on the retrieved and stored data corresponding to the vehicle and conveying, via the interface, the prequalification determination to the user.
Another aspect disclosed is an apparatus for vehicle history and prequalification determination. The apparatus comprises means for providing communication with a user at a remote computing device and means for receiving a request from the user regarding a vehicle history report of a vehicle, the request including at least one of a vehicle identification number (VIN) of the vehicle, a license plate of the vehicle, or other unique identifier of the vehicle. The apparatus further comprises means for prompting the user for an indication of user interest in a prequalification for a financing offer associated with the vehicle and means for receiving the indication of user interest in the prequalification the indication including personal information of the user. The apparatus also comprises means for retrieving data corresponding to the vehicle from at least one of a third party information database, an industry publication database, a safety ratings database, and a vehicle specification database and means for storing the retrieved data according to the VIN, license plate, or other unique identifier for the vehicle. The apparatus also further comprises means for retrieving data corresponding to a determination regarding the prequalification for the financing offer and means for storing the retrieved data according to one or more unique identifiers for the user. The apparatus further also comprises means for conveying the vehicle history report to the user, the vehicle history report generated based on the retrieved and stored data corresponding to the vehicle and means for conveying the prequalification determination to the user.
Another aspect disclosed is a computer program product comprising a computer readable medium comprising instructions that, when executed, cause an apparatus to perform a method. The method comprises providing an interface for operation by a user at a remote computing device and receiving a request, via the interface, from the user regarding a vehicle history report of a vehicle, the request including at least one of a vehicle identification number (VIN) of the vehicle, a license plate of the vehicle, or other unique identifier of the vehicle. The method also comprises prompting the user, via the interface, for an indication of user interest in a prequalification for a financing offer associated with the vehicle and receiving the indication of user interest in the prequalification, via the interface, the indication including personal information of the user. The method further comprises retrieving data corresponding to the vehicle from at least one of a third party information database, an industry publication database, a safety ratings database, and a vehicle specification database and storing the retrieved data according to the VIN, license plate, or other unique identifier for the vehicle. The method also further comprises retrieving data corresponding to a determination regarding the prequalification for the financing offer and storing the retrieved data according to one or more unique identifiers for the user. The method further also comprises conveying, via the interface, the vehicle history report to the user, the vehicle history report generated based on the retrieved and stored data corresponding to the vehicle and conveying, via the interface, the prequalification determination to the user.
The above-mentioned aspects, as well as other features, aspects, and advantages of the present technology will now be described in connection with various aspects, with reference to the accompanying drawings. The illustrated aspects, however, are merely examples and are not intended to be limiting. Throughout the drawings, similar symbols typically identify similar components, unless context dictates otherwise. Note that the relative dimensions of the following figures may not be drawn to scale.
Various aspects of the novel systems, apparatuses, and methods are described more fully hereinafter with reference to the accompanying drawings. The teachings disclosed may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings herein, one skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the novel systems, apparatuses, and methods disclosed herein, whether implemented independently of or combined with any other aspect of the invention. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the invention is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the invention set forth herein. It should be understood that any aspect disclosed herein may be embodied by one or more elements of a claim.
Although particular aspects are described herein, many variations and permutations of these aspects fall within the scope of the disclosure. Although some benefits and advantages of the preferred aspects are mentioned, the scope of the disclosure is not intended to be limited to particular benefits, uses, or objectives. Rather, aspects of the disclosure are intended to be broadly applicable to different consumer goods and services industries. The detailed description and drawings are merely illustrative of the disclosure rather than limiting, the scope of the disclosure being defined by the appended claims and equivalents thereof.
Popular network technologies may include various types of wireless or wired networks. The wireless or wired network may be used to interconnect nearby devices together, employing widely used networking protocols. The various aspects described herein may apply to any communication standard, such as a wireless 802.11 protocol.
In some embodiments, a consumer may use the consumer terminal 104 to shop for a vehicle that the consumer intends to purchase. For example, the consumer terminal 104 may comprise a laptop, a desktop, a tablet, a mobile phone, a PDA, or any other computing device with which the consumer may browse the Internet. In some embodiments, the consumer may be shopping for another good besides a vehicle, for example furniture, a home, a marine vehicle, or similar goods which may involve financing. For simplicity, a consumer shopping activity described herein will be directed to a vehicle purchase or lease as an example, though other similar purchase activities as those described above are contemplated. When shopping for a vehicle, the consumer may be browsing a vehicle dealer's website. In some embodiments, the dealer website may be hosted by the dealer server 108. While shopping, the consumer may filter various listings on the dealer website to view only vehicles that meet various criteria as established by the consumer. While browsing the dealer's website, the consumer may select one or more vehicles that interest the consumer and may request a vehicle history report (VHR), or other additional information associated with the selected one or more vehicles. The request for the vehicle history report may initiate a communication from the dealer server 108 that is hosting the dealer website to the VHPS 106, though the VHR request may be handled in various other manners.
The VHPS 106 may comprise a server that provides one or more of VHRs and financing prequalification determinations. For example, the VHPS 106 may be able to provide the VHR for a vehicle given its vehicle identification number (VIN) or other unique identifying information, such as a license plate, etc. Additionally, or alternatively, the VHPS 106 may provide financing prequalification determinations for potential financing offers based on information from or about the consumer, information regarding the vehicle in which the consumer is interested, and qualification criteria as received from financial institutions and underwriters providing the financial offers. In some embodiments, the VHRs and the prequalification determinations may be provided by two distinct servers (not shown in this figure).
In providing the VHRs, the VHPS 106 may retrieve the VHRs from the vehicle history data store 116. The vehicle history data store 116 may comprise a database or other storage device comprising VHRs organized in a searchable manner. The vehicle history data store 116 may include one or more internal and/or external data sources. The data sources may include internal and external data sources which store, for example, vehicle history attributes data and/or other consumer data. In some embodiments, the vehicle history data store 116 may comprise a plurality of databases or sources, including third party databases or sources, such as an industry publication database, a safety ratings database, and a vehicle specification database, that include information regarding a vehicle history. In some embodiments, one or more of the databases or data sources may be implemented using a relational database, such as Sybase, Oracle, CodeBase and Microsoft® SQL Server as well as other types of databases such as, for example, a flat file database, an entity-relationship database, and object-oriented database, and/or a record-based database.
In some embodiments, the vehicle history data store 116 may comprise searchable data that will eventually be rendered to generate the VHRs. The VHRS can be used to aggregate information about a specific vehicle. In some embodiments, the vehicle history reports may include information regarding accident history, mileage history, ownership history, among others, for a designated vehicle (identified by the VIN or other unique identifying information).
Accordingly, in some embodiments, the VHPS 106 (or similar device) may request and extract appropriate data for the selected vehicle based on the provided VIN or other unique identifying information. In some embodiments, the extracted data or the vehicle history report may be provided to the requesting consumer in the form of the vehicle history report. For example, when the VHPS 106 receives a complete vehicle history report from another source, that vehicle history report may be communicated to the consumer, as requested. In some embodiments, the VHPS 106 may verify one or more pieces of information on the received complete vehicle history report to confirm the vehicle history report is accurate. In some embodiments, the VHPS 106 may generate the vehicle history report from extracted data received from one or more vehicle history data stores 116.
Additionally, or alternatively, the extracted data or the vehicle history report, or portions thereof, may be used in the prequalification determination. For example, when the VHPS 106 performs the prequalification determination, the VHPS 106 may analyze information regarding the specific vehicle, consumer information, and the qualification information provided by financial parties to determine if the consumer can be prequalified for a financing offer in relation to the specific vehicle. In some embodiments, the information regarding the specific vehicle may include price, make, model, year, body style, mileage, etc. In some embodiments, the consumer information may include name, birthdate, income, credit history, etc. The VHPS 106 may be configured to request and receive data from various databases based on the information needed to make the prequalification determination. For example, when the consumer requests the vehicle history report as described above, the consumer may be presented with one or more financing offers. If the consumer selects a financing offer of interest, the consumer may be prompted to enter information used in the financing prequalification (e.g., income, debt, credit score, biographical information, etc.). In some embodiments, the consumer may not be prompted to select a financing offer of interest, but rather the VHPS 106 may determine the consumer's prequalification status for all available financing offers in view of the provided vehicle and consumer information.
In determining prequalification for potential financing offers, the VHPS 106 may retrieve the qualification criteria directly from financing institutions (e.g., lenders' servers 110A-110C). In some embodiments, more than one financing institution may provide qualification criteria for financing offers, and the VHPS 106 may determine whether the consumer is prequalified. The VHPS 106 may determine the consumer's prequalification status based on the information provided by the consumer and the criteria provided by the financing institutions. For example, in some embodiments, a financing offer may comprise criteria requiring that the consumer have a credit score above 650 and an annual income of greater than $40,000. Accordingly, if the consumer can meet these criteria (e.g., has an income greater than $40,000 and a credit score of at least 650), then the VHPS 106 may determine that the consumer is qualified for that financing offer. In some embodiments, the VHPS 106 may be configured to provide the consumer information and/or the specific vehicle information to one or more of the lenders' servers 110A-110C.
In some embodiments, as shown in
In some embodiments, the prequalification determination results from the lenders' servers 110A-110C and/or the VHPS 106 may be communicated to the dealer. In some embodiments, when the prequalification determination results are communicated to the dealer, they may be communicated along with a request to automatically filter the dealer listings to display only cars that the consumer is qualified to purchase using financing. For example, when the lenders' servers 110A-110C or the VHPS 106 determine that the consumer is not prequalified to purchase the specific vehicle selected by the consumer, they may idea what vehicle specifics would be acceptable (e.g., lower price, different make/model, fewer features, etc.). Accordingly, the “acceptable” vehicle specifics may be communicated to the dealer with a request to filter the dealer listings to show the consumer vehicles they are prequalified to purchase.
In some embodiments, certain modules described below, such as a user interface module 210, a vehicle history report (VHR) module 214, or a financing module 216 included with the VHPS 106 may be included with or performed by different and/or multiple devices of the communication system 100. For example, certain user interface functionality described herein may be performed by the user interface module 210 of the VHPS 106 and/or by the user interface module 210 of the consumer terminal 104.
In an embodiment, various software modules are included in the vehicle history reporting and financing system 100, which may be stored on a component of the system 100 itself, or on computer readable storage media separate from the system 100 and in communication with the system 100 via the network 102 or other appropriate means.
The VHPS 106 may include, for example, a computer that is IBM, Macintosh, or Linux/Unix compatible or a server or workstation. In some embodiments, the VHPS 106 comprises a smart phone, a personal digital assistant, a kiosk, or a media player. In some embodiments, the VHPS 106 includes one or more central processing units (“CPUs”) 202, I/O interfaces and devices 204, memory 206, mass storage device 208, the user interface module 210, multimedia device 212, the VHR module 214, the financing module 216, and bus 218.
The CPU 202 may control operation of the VHPS 106. The CPU 202 may also be referred to as a processor. The CPU 202 may comprise or be a component of a processing system implemented with one or more processors. The one or more processors may be implemented with any combination of general-purpose microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate array (FPGAs), programmable logic devices (PLDs), controllers, state machines, gated logic, discrete hardware components, dedicated hardware finite state machines, or any other suitable entities that can perform calculations or other manipulations of information.
The I/O interface 204 may comprise a keypad, a microphone, a touchpad, a speaker, a touchscreen, and/or a display, or any other commonly available input/output (I/O) devices and interfaces. The I/O interface 204 may include any element or component that conveys information to a consumer of the VHPS 106 and/or receives input from the consumer. In one embodiment, the I/O interface 204 includes one or more display devices, such as a monitor, that allows the visual presentation of data to the consumer. More particularly, the display device may provide for the presentation of GUIs, application software data, and multimedia presentations, for example.
In some embodiments, the I/O interface 204 may provide a communication interface to various external devices. For example, the VHPS 106 may be electronically coupled to the network 102 (
The memory 206, which may include both read-only memory (ROM) and random access memory (RAM), may provide instructions and data to the CPU 202. For example, inputs received by one or more components of the device 202 may be stored in the memory 206. A portion of the memory 206 may also include non-volatile random access memory (NVRAM). The CPU 202 typically performs logical and arithmetic operations based on program instructions stored within the memory 206. The instructions in the memory 206 may be executable to implement the methods described herein.
The VHPS 106 may also include the mass storage device 208 for storing software or information (for example, the vehicle history reports or associated data). Software shall be construed broadly to mean any type of instructions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Instructions may include code (e.g., in source code format, binary code format, executable code format, or any other suitable format of code). The instructions, when executed by the one or more processors, cause the processing system to perform the various functions described herein. Accordingly, the VHPS 106 may include, e.g., hardware, firmware, and software, or any combination therein. The mass storage device 208 may comprise a hard drive, diskette, solid state drive, or optical media storage device.
As shown in
In some embodiments, the VHR module 214 may be configured to identify a request for a vehicle history report as received from the consumer using the consumer terminal 104 of
In some embodiments, the VHR module 214 may use the VIN to generate a request to a vehicle history data store (e.g., the external vehicle history data store 116 of
As shown in
In some embodiments, the financing determination module 216 may be configured to identify a request, as received from the consumer using the consumer terminal 104 of
Accordingly, in some embodiments, the request for the prequalification determination may include vehicle information as well as information about the consumer (e.g., personal information, financial information, etc.) and the consumer identifier that identifies the consumer requesting the prequalification determination. In some embodiments, the consumer information may be saved as part of a consumer profile, for example, as associated with a consumer account with the dealer or the lenders. Accordingly, when the consumer information is part of the consumer profile, the prequalification determination request may not include receiving the personal information from the consumer, but rather from the dealer server 106 or the consumer terminal 104 or the lender server 110A-110C. In some embodiments, the consumer information may be linked with a third party account. For example, when prompted for consumer information, the consumer may provide login credentials for a third party account (e.g., a bank account, a store account, etc.), and the third party account may be used a source for the desired consumer information. For example, when prompted for consumer financial information, the consumer may provide their bank account credentials, and the VHPS 106 (via one or more of the I/O interfaces and devices 204, the CPU 202, the user interface module 210, and the financing determination module 216) may request and receive the consumer financial information from the bank account.
In some embodiments, the financing determination module 216 may receive the prequalification determination request from the consumer and communicate the request to one or more of the lenders' servers 110A-110C for the lenders themselves to determine via a financing determination process. The financing determination process may comprise a process of applying the consumer information and/or the vehicle information to the financing criteria established by the lenders. Accordingly, the financing determination module 216 may receive a communication from the lenders' server 110A-110C regarding the determination (e.g., qualified or not qualified) and may communicate that determination to the dealer and/or the consumer via the I/O interfaces and devices 204 and/or the user interface module 210 and the user identifier.
In some embodiments, the financing determination module 216 may receive the prequalification criteria from the lenders' servers 110A-110C. The financing determination module 216 may be configured to apply the information received in the prequalification determination request to the prequalification criteria received from the lenders' servers 110A-110C to generate the requested prequalification determination. Accordingly, the financing determination module 216 may perform the financing determination process. As described above, when the lenders perform the financing determination process to determine the result of the prequalification determination request, the result may be communicated back to the financing determination module 216 (e.g., via the I/O interfaces and devices 204), which may communicate the result to the consumer using the consumer identifier. This result may also be communicated to the dealer in conjunction with the consumer identifier to allow the dealer to better customize their sales efforts based on the consumer prequalification results. When the financing determination module 216 determines the result of the prequalification determination request itself, the financing determination module 216 may communicate the result to the consumer using the consumer identifier. Similarly, the result may be communicated to the dealer to allow for customized sales efforts based on that consumer's qualifications.
In some embodiments, the result of the prequalification determination request may be a simple “Yes” or “Prequalified” or “Approved” or “No” or “Denied”, among others. In some embodiments, if the result of the prequalification determination request is negative, the financing determination module 216 may use the provided consumer information and specific vehicle information (when applicable) to generate attributes or factors that may lead to a prequalification determination for the consumer. For example, if the specific vehicle selected by the consumer is too expensive in view of the financial information provided by the consumer, then the financing determination module 216 may generate an attribute or factor indicating the price of the specific vehicle was too high. Alternatively, or additionally, if the specific vehicle selected involves too much risk in view of the criteria, the financing determination module 216 may generate vehicle features (e.g., the vehicle has too many miles or is of an undesirable make/model or includes a title issues) associated with these risks.
In some embodiments, the financing determination module 216 may then generate a communication to the dealer (e.g., via the I/O interfaces and devices 204) requesting the dealer provide a listing of vehicles that meet the generated list of attributes or factors. This requested listing may comprise a list of vehicles available at the dealer for which the consumer would be prequalified to purchase. The financing determination module 216 may then cause the listing of vehicles that meet the generated list of attributes or factors to be displayed or provided to the consumer, for example via the user interface module 210 or via the I/O interfaces and devices 204. In some embodiments, the financing determination module 216 may provide this listing of vehicles to the dealer in conjunction with the consumer identifier so the dealer may tailor its services and offerings to the consumer. Accordingly, even if the consumer is not approved for the requested financing offer (or any automatically searched financing offer), the financing determination module 216 may provide the consumer with options that would be available. Accordingly, the financing determination module 216 may ensure that the consumer receives the requested prequalification determination regardless of where the determination is made and may be provided with purchase options regardless of the prequalification determination.
The VHPS 106 also includes the user interface module 210. In some embodiments, the user interface module 210 may also be stored in the mass storage device 208 as executable software code that is executed by the CPU 202. In the embodiment shown in
The user interface module 210 may be configured to generate, provide, and/or operate user interfaces of various types. In some embodiments, the user interface module 210 constructs pages or displays to be displayed in a web browser or computer/mobile application. In some embodiments, the user interface module 210 may provide an application or similar module for download and operation on the consumer terminal 104, through which the consumer and the VHPS 106 may interact. The pages may, in some embodiments, be specific to a type of device, such as a mobile device or a desktop web browser, to maximize usability for the particular device.
For example, the user interface module 210 may be configured to automatically detect a type of computing device that is requesting vehicle history information or prequalification determinations, such as a mobile phone, a desktop computer, etc. This detection may be made via an identifier that is communicated with the request. In some embodiments, the detection may be based on a consumer selection when the consumer interacts with the VHPS 106 for the first time. According to the detection, the user interface module 210 may determine to send information formatted optimized for the proper computing device being used by the consumer.
In some embodiments, the user interface module 210 may also interact with a client-side application, such as a mobile phone application (an “app”), a standalone desktop application, or user communication accounts (e.g., e-mail, SMS messaging, etc.) and provide data as necessary to display vehicle history and prequalification determinations. When interacting with the client-side application that is provided by the VHPS 106 (e.g., a VHPS 106 specific application or similar application), the user interface module 210 may be configured to format data for communication according to specifications and standards associated with that application. For example, the user interface module 210 may be configured to format all communication messages according to specific information elements that may be understood by the application on the computing device. Accordingly, information may be securely and efficiently communicated back and forth when both sides know the appropriate specifications and standards.
In some embodiments, one or more windows or interactions between the VHPS 106 and the consumer may involve a lightbox or overlay layer or a popup or window. For example, a lightbox or overlay may comprise a format that displays images and/or videos and text or prompts by filling the screen, and dimming out the rest of the web page or display. The lightbox or overlay may, alternatively, or additionally, places a new set of images, information, or prompts over existing data while maintaining the existing data though it is covered (and thus not viewable) while the new set of information is visible. Use of the lightbox or overlay may allow for the presentation of new information to the consumer without causing the consumer to lose the existing information. Additionally, or alternatively, the lightbox or overlay allows the consumer to view at least a portion of the existing information simultaneously with the information in the lightbox or overlay. Additionally, or alternatively, the popup or window may allow for the resizable display of information or requests to the user while allowing for simultaneous viewing and access to new and existing information. The VHPS 106 may also include one or more multimedia devices 140, such as speakers, video cards, graphics accelerators, and microphones, for example.
The various components of the VHPS 106 may be coupled together by a bus system 218. The bus system 218 may include a data bus, for example, as well as a power bus, a control signal bus, and a status signal bus in addition to the data bus. In different embodiments, the bus could be implemented in Peripheral Component Interconnect (“PCI”), Microchannel, Small Computer System Interface (“SCSI”), Industrial Standard Architecture (“ISA”) and Extended ISA (“EISA”) architectures, for example. In addition, the functionality provided for in the components and modules of VHPS 106 may be combined into fewer components and modules or further separated into additional components and modules than that shown in
The VHPS 106 may be controlled by operating system software, such as Windows XP, Windows Vista, Windows 7, Windows 8, Windows Server, Unix, Linux, SunOS, Solaris, IOS, Android, Blackberry OS, or other similar operating systems. In Macintosh systems, the operating system may be any available operating system, such as MAC OS X. In other embodiments, the VHPS 106 may be controlled by a proprietary operating system. Conventional operating systems control and schedule computer processes for execution, perform memory management, provide file system, networking, I/O services, and provide a user interface, such as a graphical user interface (“GUI”), among other things.
Process 300 begins at block 302 and progresses to block 304. At block 304, the consumer visits a vehicle shopping portal or website, for example the vehicle website discussed above. The visit to the vehicle shopping portal may include browsing or searching for a vehicle of interest by the consumer. Once the consumer identifies a vehicle of interest, the process 300 proceeds to block 306.
At block 306, the consumer requests a vehicle history report (VHR) for the identified vehicle of interest. In some embodiments, the consumer may request multiple VHRs when there are multiple identified vehicles of interest. In some embodiments, requesting the VHR may comprise selecting or identifying a specified link or VHR request button, as will be described in further detail below. In some embodiments, the VHR request link or button may be on a vehicle listing's specific page or may be an option when viewing a group of listing as applied to multiple specific listings. Once the consumer requests the VHR, the process 300 proceeds to block 308.
At block 308, the consumer is presented with a prompt to input information regarding a prequalification determination for one or more available financing offers. In some embodiments, the prompt may be presented to the consumer based on the consumer requesting the VHR for the vehicle of interest. In some embodiments, the prompt may be presented to the consumer based on the consumer selecting a link or button regarding prequalification determinations. In some embodiments, the prompt may request the consumer provide information regarding the type of financing offer the consumer desires. In some embodiments, the prompt may appear as part of an overlay, lightbox, or popup. In some embodiments, the prompt may include individual fields for entry by the consumer for each item of information needed for the prequalification determination. In some embodiments, the prompt may include login credentials for various accounts that may already include the consumer information needed for the prequalification determination. For example, the fields may include a login credentials request for a bank account, a store website or a credit vendor. Once the prompt has been provided to the consumer, the process 300 proceeds to block 310.
At block 310, the process 300 determines if the consumer provided consumer information when prompted at block 308. If the consumer did provide the requested consumer information when prompted, the process 300 proceeds to block 314. If the consumer did not provide the requested consumer information when prompted, the process 300 proceeds to block 312.
At block 312, the process 300 may interpret the consumer's failure to provide consumer information when requested as a lack of interest in a financing prequalification determination and may place a temporary cookie on the consumer terminal to prevent future prompts requesting consumer information for the vehicle of interest. By making this interpretation and placement of the cookie, the process 300 may streamline the consumer's shopping experience by refraining from prompting the consumer for consumer information simply because the consumer requests the associated vehicle history report.
In some embodiments, the process 300 at block 312 will again prompt the consumer, this time asking the consumer if they would like to block future consumer information prompts. If the consumer indicates that they do want to block future prompts, then the process 300 may set the cookie preventing future consumer information prompts. If the consumer indicates that they do not want to block future consumer information prompts, then the process 300 may not set the cookie preventing future consumer information prompts. By this second prompt, the process 300 may avoid improperly interpreting the consumer's failure to provide consumer information as a lack of interest. In some embodiments, the cookie may expire after a predetermined amount of time. In some embodiments, the consumer may manually request to reactivate the consumer information prompts if desired. Once the process 300 determines whether or not to set the cookie at block 312, the process 300 proceeds to block 302 and restarts.
At block 314, the process 300 may acknowledge the receipt of the consumer's information when requested and may place a temporary cookie on the consumer terminal to prevent future prompts requesting consumer information for the vehicle of interest. The process 300 may assume that future prompts requesting the consumer information may not be needed for each vehicle of interest because the consumer information may remain constant regardless of the vehicle. Accordingly, the consumer information might only be received once and then stored for application in any and all financing offer prequalification determinations. In some embodiments, the consumer will be again prompted at block 314, this time the prompt requesting that the consumer confirm whether or not they would like to block future consumer information prompts. If the consumer indicates that they do want to block future consumer information prompts, then the process 300 might set the cookie preventing future consumer information prompts. If the consumer indicates that they do not want to block future consumer information prompts, then the process 300 might not set the cookie preventing future consumer information prompts. In some embodiments, the cookie might expire after a predetermined amount of time. In some embodiments, the consumer may manually trigger or adjust the cookie.
Once the process 300 determines whether or not to set the cookie at block 314, the process 300 forwards the information from the consumer to the financing determination process (described above in relation to
After the cookie is set in either blocks 312 or 314, consumer information prompts may be blocked based on the previously set cookie as the consumer continues to visit the vehicle shopping website. In some embodiments, the cookie may block prompts for only the previously viewed vehicles, so that repeated views of the same vehicle will not generate multiple, useless prompts. In some embodiments, the cookie may block prompts for all vehicles for the predetermined amount of time. In some embodiments, the cookie may be replaced by any other flag, indicator, value, or process that may be used to control whether or not the prompts are displayed subsequently.
At block 316, the process 300 proceeds to send the prequalification determination to the consumer and the dealer. In some embodiments, the prequalification determination may be presented to the consumer and/or the dealer as a lightbox, overlay, or popup. In some embodiments, the prequalification determination may include multiple options of financing offers available and allow or request the consumer to select one or more of the multiple options. In some embodiments, the prequalification determination may be negative for the selected vehicle and may provide alternate options for the consumer to review for which the consumer may be approved. In some embodiments, the prequalification determination may be negative with no alternatives. Once the prequalification determination is provide to the consumer and the dealer, the process 300 ends at block 318.
In some embodiments, the consumer may not be prompted for information regarding the prequalification determination until the VHR requested by the consumer is displayed to the consumer. For example, the lightbox, overlay, or popup including the prequalification questions may display over the VHR. In some embodiments, the prompt for information regarding the prequalification determination may occur as soon as the VHR is requested and while the VHR is being retrieved and/or generated.
Beginning at block 605, the VHPS 106 receives a consumer request for a vehicle history report for a specific vehicle while the consumer is browsing vehicles at a dealer. For example, the request may be received from the consumer via an application executing on the consumer terminal 104 (
At block 610, the VHPS 100 presents the generated or acquired vehicle's history report to the consumer. In addition, either automatically or in response to a consumer request, the VHPS 106 presents to the consumer a user interface, such as, for example a fillable form, or the like, to receive loan eligibility information from the consumer, including, for example, the consumer's name, address, email address, phone number, date of birth, social security number, and the like. An example of the form is shown in
Continuing at block 615, the VHPS 106 receives the information from the consumer using the user interface presented. In some embodiments, if the consumer refuses to fill out the information, a temporary cookie may be placed on the consumer terminal 104 of the consumer to prevent the presentation of the user interface until expiration of the temporary cookie. In other embodiments, other such preventive measures may be used, or the consumer may be asked for the information after a predetermined time period. The consumer may also be prompted to make a selection of specific lenders to contact. Additionally, or alternatively, at block 615, the process 600 may be configured to use the received login credentials to access the indicated account to acquire the necessary loan eligibility information.
Next at block 620, the VHPS 106 provides the information to one or more lenders to determine eligibility for the consumer. In some embodiments, the VHPS 106 uses the information to access a data storage storing credit information for consumers, in parallel with and/or instead of submitting the eligibility requests to the one or more lenders. The accessed data storage may provide credit information for the consumer that may be used, in conjunction with financing criteria received from the one or more lenders, to determine eligibility for the consumer (e.g., via the financing determination module 216 of
At block 625, the VHPS 106 receives (or accesses) lending decisions based on the information received from the consumer. For example, the lending decisions may come from the one or more lenders described above in block 620. In some embodiments, the lending decisions may be made pursuant to a process similar to the financing determination process described above. For example, when the pre-qualification decision is made by the lenders, the VHPS 106 may receive the decision from the lenders via the network 102 of the system 100 of
At block 630a, the VHPS 106 provides the pre-qualification and/or pre-screening data to the consumer interested in the specific vehicle. The data presented to the consumer may include loan offers for which the consumer is pre-screened and pre-qualified. In some embodiments, the consumer may also be prompted to provide consent for receiving a pre-qualification report. In some embodiments, the consumer may also be presented with information that the consumer does not qualify for any loan offers, or that the vehicle in which the consumer is interested does not qualify for any loan offers. If the vehicle does not qualify for any loan offers, the VHPS 106 may provide a list of vehicles, available at the dealer, that would qualify for loan offers.
For each loan offer, various information about the particular loan offer may be presented to the consumer, including for example who is the lender, what the loan offer includes (for example, an annual percentage rate (APR) and a term/duration for the loan), any conditions which may need to be satisfied prior to the loan being approved or distributed, and an associated action the consumer may take now with respect to the loan offer. The associated action presented may depend on the type of loan offer—for example, the consumer may have the option to “Lock-in Rate” or “Apply Now!” If the consumer selects to move forward with the loan offer, the consumer may be directed to the lender's website or may be requested to provide additional information needed to proceed with applying for the loan offer.
At block 630b, instead of, or in addition to block 630a, the VHPS 106 provides the pre-qualification and/or pre-screening data of consumers interested in specific vehicles to a seller of the specific vehicle—such as for example the dealer. The dealer may then use this information to present additional vehicle options to the consumer. In some embodiments, the dealer may receive information only indicating that the consumer did or did not qualify for a loan offer. For example, if the dealer receives indication that the consumer does not qualify for a loan offer for a specific vehicle, the dealer may redirect the consumer to another vehicle with similar attributes for which the consumer may qualify. On the other hand, if the dealer sees that the consumer did qualify for the loan offer, the dealer may more aggressively try to close the sale of that vehicle to the consumer.
Alternatively, or additionally, the dealer may be provided with detailed information as to why the consumer did or did not qualify when the information relates to the vehicle, which the dealer may use try to sell a different vehicle to better suit the needs of both the dealer and the consumer. In some embodiments, in order to maintain confidentiality, the determination may not be provided to the dealer in any circumstances. In some embodiments, when additional vehicle options are presented to the consumer, they may be presented via the same user interface. The additional vehicle options may be determined based on the vehicle attributes selected by the consumer, as well as the financing amount for which the consumer is pre-screened and/or pre-qualified. The determination of additional vehicles satisfying the criteria may be completely automated.
Beginning at block 705, the consumer begins a vehicle search. In some embodiments, this vehicle search may begin on a dealer or a vehicle listing (e.g., portal) website. As part of the consumer's vehicle search, the consumer may identify a vehicle of interest and may request the vehicle history report for that vehicle. This request may be communicated to the dealer or portal website and communicated to the VHPS 106. The VHPS 106 receives the consumer request for the vehicle history report (similar to block 605 of process 600), and may present the consumer with the vehicle history report on the dealer or portal website at block 710 (similar to block 610 of process 600). While the vehicle history report is being viewed by the consumer, the consumer may be presented with an opportunity to prequalify for financing and provide consumer information needed for the prequalification process at block 715. At block 720, similar to block 620 of process 600, the consumer enters their consumer information and provides their consent for a prequalification decision.
Then, at block 725, a lender (or the VHPS 106 as described above) may use the consumer information to determine if the consumer qualifies for any financing options using specific lender criteria. At block 730, the process 700 may include a decisioning as a service (DaaS) platform to process the prequalification decision based on the various lender criteria. At block 735, the consumer is presented with the prequalification determination and options, similar to block 630a of process 600. Once the consumer is presented with the options, at block 740, the consumer may have the opportunity to pursue one of the financing options for which the consumer is prequalified. If the consumer decides not to select a prequalification option (or fails to provide a response), the process 700 proceeds to block 745, where the consumer is redirected to another website and the consumer's data and prequalification determinations are cleared.
If the consumer decides to select a prequalification option at block 740, the process proceeds to block 750, the process 700 may notify the lender that the consumer does want to pursue one of the financing offers and may redirect the consumer to the lender's website. Once the lender is notified of the consumer's interest, the process 700 proceeds to block 755, where the dealer is notified of the consumer's interest, as this may comprise a sales lead for the dealer. Then the process 700 proceeds to block 760, where the consumer is provided details of the prequalification via a web confirmation and/or an e-mail. In some embodiments, the presentation of information to the consumer may be via an overlay or lightbox interface as described above.
Terminals and computing devices, which may comprise the software and/or hardware described above, may be an end user computing device that comprises one or more processors able to execute programmatic instructions. Examples of such computing devices are a desktop computer workstation, a smart phone such as an Apple iPhone or an Android phone, a computer laptop, a tablet PC such as an iPad, Kindle, or Android tablet, a video game console, or any other device of a similar nature. In some embodiments, the computing devices may comprise a touch screen that allows a user to communicate input to the device using their finger(s) or a stylus on a display screen.
The computing devices may also comprise one or more client program applications, such as a mobile “app” (e.g. iPhone or Android app) that may be used to visualize data, and initiate the sending and receiving of messages in the VHPS 106. This app may be distributed (e.g. downloaded) over the network to the computing devices directly from the VHPS 106 (e.g., the user interface module 210 or the storage device 208) or from various third parties such as an Apple iTunes or Google Play repository or “app store.” In some embodiments, the application may comprise a set of visual interfaces that may comprise templates to display vehicle history reporting and financing information. In some embodiments, as described above, visual user interfaces may be downloaded from another server or service, such as the VHPS 106. This may comprise downloading web page or other HTTP/HTTPS data from a web server and rendering it through the “app”. In some embodiments, no special “app” need be downloaded and the entire interface may be transmitted from a remote Internet server to computing device, such as transmission from a web server that is a part of the VHPS 106 to an iPad, and rendered within the iPad's browser.
In general, the word “module,” as used herein, refers to logic embodied in hardware or firmware, or to a collection of software instructions, possibly having entry and exit points, written in a programming language, such as, for example, Java, Lua, C or C++. A software module may be compiled and linked into an executable program, installed in a dynamic link library, or may be written in an interpreted programming language such as, for example, BASIC, Perl, or Python. It will be appreciated that software modules may be callable from other modules or from themselves, and/or may be invoked in response to detected events or interrupts. Software modules configured for execution on computing devices may be provided on a computer readable medium, such as a compact disc, digital video disc, flash drive, or any other tangible medium. Such software code may be stored, partially or fully, on a memory device of the executing computing device, such as the vehicle history reporting and financing system 100, for execution by the computing device. Software instructions may be embedded in firmware, such as an EPROM. It will be further appreciated that hardware modules may be comprised of connected logic units, such as gates and flip-flops, and/or may be comprised of programmable units, such as programmable gate arrays or processors. The modules described herein are preferably implemented as software modules, but may be represented in hardware or firmware. Generally, the modules described herein refer to logical modules that may be combined with other modules or divided into sub-modules despite their physical organization or storage.
In some embodiments, the system distinguishes between the initial transmission of loan application data required for user interfaces, and subsequent transmissions of user interface data so that it may transmit only portions that are necessary to update a vehicle history reporting and financing user interface. This may be done, for example, using an XMLHttpRequest (XHR) mechanism, a data push interface, Asynchronous JavaScript and XML (“Ajax”), or other communication protocols.
Each of the processes, methods, and algorithms described in the preceding sections may be embodied in, and fully or partially automated by, code modules executed by one or more computer systems or computer processors comprising computer hardware. The code modules may be stored on any type of non-transitory computer-readable medium or computer storage device, such as hard drives, solid state memory, optical disc, and/or the like. The systems and modules may also be transmitted as generated data signals (for example, as part of a carrier wave or other analog or digital propagated signal) on a variety of computer-readable transmission mediums, including wireless-based and wired/cable-based mediums, and may take a variety of forms (for example, as part of a single or multiplexed analog signal, or as multiple discrete digital packets or frames). The processes and algorithms may be implemented partially or wholly in application-specific circuitry. The results of the disclosed processes and process steps may be stored, persistently or otherwise, in any type of non-transitory computer storage such as, for example, volatile or non-volatile storage.
The various features and processes described above may be used independently of one another, or may be combined in various ways. All possible combinations and sub combinations are intended to fall within the scope of this disclosure. In addition, certain method or process blocks may be omitted in some implementations. The methods and processes described herein are also not limited to any particular sequence, and the blocks or states relating thereto can be performed in other sequences that are appropriate. For example, described blocks or states may be performed in an order other than that specifically disclosed, or multiple blocks or states may be combined in a single block or state. The example blocks or states may be performed in serial, in parallel, or in some other manner. Blocks or states may be added to or removed from the disclosed example embodiments. The example systems and components described herein may be configured differently than described. For example, elements may be added to, removed from, or rearranged compared to the disclosed example embodiments.
Conditional language, such as, among others, “can,” “could.” “might,” or “may.” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
Any process descriptions, elements, or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art.
All of the methods and processes described above may be embodied in, and partially or fully automated via, software code modules executed by one or more general purpose computers. For example, the methods described herein may be performed by the vehicle history reporting and financing system 100, consumer terminal 104, and/or any other suitable computing device. The methods may be executed on the computing devices in response to execution of software instructions or other executable code read from a tangible computer readable medium. A tangible computer readable medium is a data storage device that can store data that is readable by a computer system. Examples of computer readable mediums include read-only memory, random-access memory, other volatile or non-volatile memory devices, CD-ROMs, magnetic tape, flash drives, and optical data storage devices.
It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure. The foregoing description details certain embodiments of the invention. It will be appreciated, however, that no matter how detailed the foregoing appears in text, the invention can be practiced in many ways. As is also stated above, it should be noted that the use of particular terminology when describing certain features or aspects of the invention should not be taken to imply that the terminology is being re-defined herein to be restricted to including any specific characteristics of the features or aspects of the invention with which that terminology is associated. The scope of the invention should therefore be construed in accordance with the appended claims and any equivalents thereof.
Other embodiments relating to the systems and methods disclosed herein are detailed in the following documents, found in the Appendix of the present application, the entirety of which is bodily incorporated herein and the entirety of which is also incorporated herein by reference.
Any and all applications for which a foreign or domestic priority claim is identified in the Application Data Sheet as filed with the present application are hereby incorporated by reference under 37 CFR 1.57. This application is a continuation of U.S. patent application Ser. No. 16/792,107, filed Feb. 14, 2020, which is a continuation of U.S. patent application Ser. No. 14/975,470, filed Dec. 18, 2015, which claims the benefit of priority under 35 U.S.C. § 119(c) of U.S. provisional Application No. 62/093,973, filed Dec. 18, 2014, the disclosure of each of which is hereby incorporated by reference in its entirety for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4989144 | Barnett, III | Jan 1991 | A |
| 5120704 | Lechter et al. | Jun 1992 | A |
| 5201010 | Deaton et al. | Apr 1993 | A |
| 5216612 | Cornett et al. | Jun 1993 | A |
| 5488360 | Ray | Jan 1996 | A |
| 5532838 | Barbari | Jul 1996 | A |
| 5587575 | Leitner et al. | Dec 1996 | A |
| 5630070 | Dietrich et al. | May 1997 | A |
| 5748098 | Grace | May 1998 | A |
| 5765143 | Sheldon et al. | Jun 1998 | A |
| 5819234 | Slavin et al. | Oct 1998 | A |
| 5878403 | DeFrancesco | Mar 1999 | A |
| 5940812 | Tengel et al. | Aug 1999 | A |
| 5950169 | Borghesi et al. | Sep 1999 | A |
| 5963129 | Warner | Oct 1999 | A |
| 5995947 | Fraser et al. | Nov 1999 | A |
| 6006201 | Berent et al. | Dec 1999 | A |
| 6038554 | Vig | Mar 2000 | A |
| 6052065 | Glover | Apr 2000 | A |
| 6052068 | Price et al. | Apr 2000 | A |
| 6076064 | Rose, Jr. | Jun 2000 | A |
| 6126332 | Cubbage et al. | Oct 2000 | A |
| 6154152 | Ito | Nov 2000 | A |
| 6182048 | Osborn et al. | Jan 2001 | B1 |
| 6208979 | Sinclair | Mar 2001 | B1 |
| 6236977 | Verba et al. | May 2001 | B1 |
| 6259354 | Underwood | Jul 2001 | B1 |
| 6278936 | Jones | Aug 2001 | B1 |
| 6282517 | Wolfe et al. | Aug 2001 | B1 |
| 6330499 | Chou et al. | Dec 2001 | B1 |
| 6330546 | Gopinathan et al. | Dec 2001 | B1 |
| 6430539 | Lazarus et al. | Aug 2002 | B1 |
| 6516239 | Madden et al. | Feb 2003 | B1 |
| 6587841 | DeFrancesco | Jul 2003 | B1 |
| 6609108 | Pulliam et al. | Aug 2003 | B1 |
| 6714859 | Jones | Mar 2004 | B2 |
| 6738748 | Wetzer | May 2004 | B2 |
| 6754564 | Newport | Jun 2004 | B2 |
| 6760794 | Deno et al. | Jul 2004 | B2 |
| 6772145 | Shishido | Aug 2004 | B2 |
| 6804606 | Jones | Oct 2004 | B2 |
| 6839682 | Blume et al. | Jan 2005 | B1 |
| 6904359 | Jones | Jun 2005 | B2 |
| 6938021 | Shear et al. | Aug 2005 | B2 |
| 6959281 | Freeling et al. | Oct 2005 | B1 |
| 6980963 | Hanzek | Dec 2005 | B1 |
| 7024418 | Childress | Apr 2006 | B1 |
| 7050982 | Sheinson et al. | May 2006 | B2 |
| 7069118 | Coletrane et al. | Jun 2006 | B2 |
| 7092898 | Mattick et al. | Aug 2006 | B1 |
| 7113853 | Hecklinger | Sep 2006 | B2 |
| 7130821 | Connors et al. | Oct 2006 | B1 |
| 7181427 | DeFrancesco | Feb 2007 | B1 |
| 7184974 | Shishido | Feb 2007 | B2 |
| 7191058 | Laird et al. | Mar 2007 | B2 |
| 7228298 | Raines | Jun 2007 | B1 |
| 7288298 | Raines | Jun 2007 | B2 |
| 7275083 | Seibel et al. | Sep 2007 | B1 |
| 7366694 | Lazerson | Apr 2008 | B2 |
| 7392203 | Edison et al. | Jun 2008 | B2 |
| 7392221 | Nabe et al. | Jun 2008 | B2 |
| 7418408 | Heppe | Aug 2008 | B1 |
| 7421322 | Silversmith et al. | Sep 2008 | B1 |
| 7433891 | Haber et al. | Oct 2008 | B2 |
| 7444302 | Hu et al. | Oct 2008 | B2 |
| 7472088 | Taylor et al. | Dec 2008 | B2 |
| RE40692 | Rose, Jr. | Mar 2009 | E |
| 7505838 | Raines et al. | Mar 2009 | B2 |
| 7561963 | Brice et al. | Jul 2009 | B2 |
| 7567922 | Weinberg et al. | Jul 2009 | B1 |
| 7571139 | Giordano et al. | Aug 2009 | B1 |
| 7580856 | Pliha | Aug 2009 | B1 |
| 7590589 | Hoffberg | Sep 2009 | B2 |
| 7593893 | Ladd et al. | Sep 2009 | B1 |
| 7596512 | Raines et al. | Sep 2009 | B1 |
| 7603293 | Chenn | Oct 2009 | B2 |
| 7610257 | Abrahams | Oct 2009 | B1 |
| 7630932 | Danaher et al. | Dec 2009 | B2 |
| 7653592 | Flaxman et al. | Jan 2010 | B1 |
| 7693896 | Raines | Apr 2010 | B1 |
| 7739142 | Chand et al. | Jun 2010 | B2 |
| 7778841 | Bayer et al. | Aug 2010 | B1 |
| 7788147 | Haggerty et al. | Aug 2010 | B2 |
| 7835940 | Kowalchuk | Nov 2010 | B2 |
| 7865409 | Monaghan | Jan 2011 | B1 |
| 7877320 | Downey | Jan 2011 | B1 |
| 7925654 | Raines | Apr 2011 | B1 |
| 7945478 | Hogan et al. | May 2011 | B2 |
| 7945483 | Inghelbrecht et al. | May 2011 | B2 |
| 7962404 | Metzger, II et al. | Jun 2011 | B1 |
| 7966210 | Hall et al. | Jun 2011 | B2 |
| 7974886 | Coleman | Jul 2011 | B2 |
| 7991689 | Brunzell et al. | Aug 2011 | B1 |
| 8005759 | Hirtenstein et al. | Aug 2011 | B2 |
| 8005795 | Galipeau et al. | Aug 2011 | B2 |
| 8036952 | Mohr et al. | Oct 2011 | B2 |
| 8055544 | Ullman et al. | Nov 2011 | B2 |
| 8078524 | Crawford et al. | Dec 2011 | B2 |
| 8104671 | Besecker et al. | Jan 2012 | B2 |
| 8121938 | Zettner et al. | Feb 2012 | B1 |
| 8185417 | Brown et al. | May 2012 | B1 |
| 8219464 | Inghelbrecht et al. | Jul 2012 | B2 |
| 8239388 | Raines | Aug 2012 | B2 |
| 8244563 | Coon et al. | Aug 2012 | B2 |
| 8255243 | Raines et al. | Aug 2012 | B2 |
| 8255244 | Raines et al. | Aug 2012 | B2 |
| 8285656 | Chang et al. | Oct 2012 | B1 |
| 8355983 | Parr et al. | Jan 2013 | B1 |
| 8380594 | Berkman et al. | Feb 2013 | B2 |
| 8392334 | Hirtenstein et al. | Mar 2013 | B2 |
| 8438048 | Benavides, III | May 2013 | B1 |
| 8438170 | Koran et al. | May 2013 | B2 |
| 8521615 | Inghelbrecht et al. | Aug 2013 | B2 |
| 8560161 | Kator | Oct 2013 | B1 |
| 8577736 | Swinson et al. | Nov 2013 | B2 |
| 8595079 | Raines et al. | Nov 2013 | B1 |
| 8600783 | Smith et al. | Dec 2013 | B2 |
| 8600823 | Raines et al. | Dec 2013 | B1 |
| 8606648 | Bayer et al. | Dec 2013 | B1 |
| 8626560 | Anderson | Jan 2014 | B1 |
| 8630929 | Haggerty et al. | Jan 2014 | B2 |
| 8645193 | Swinson et al. | Feb 2014 | B2 |
| 8661032 | Otten et al. | Feb 2014 | B2 |
| 8725584 | Eager et al. | May 2014 | B1 |
| 8762191 | Lawrence et al. | Jun 2014 | B2 |
| 8781846 | Swinson et al. | Jul 2014 | B2 |
| 9020843 | Taira et al. | Apr 2015 | B2 |
| 9020844 | Taira et al. | Apr 2015 | B2 |
| 9053589 | Kator et al. | Jun 2015 | B1 |
| 9053590 | Kator et al. | Jun 2015 | B1 |
| 9076276 | Kator et al. | Jul 2015 | B1 |
| 9087335 | Rane et al. | Jul 2015 | B2 |
| 9105048 | Koran et al. | Aug 2015 | B2 |
| 9111308 | Taira et al. | Aug 2015 | B2 |
| 9123056 | Singh et al. | Sep 2015 | B2 |
| 9129325 | Taira et al. | Sep 2015 | B2 |
| 9147217 | Zabritski et al. | Sep 2015 | B1 |
| 9292860 | Singh et al. | Mar 2016 | B2 |
| 9501781 | Singh et al. | Nov 2016 | B2 |
| 9646308 | Eager et al. | May 2017 | B1 |
| 9690820 | Girulat, Jr. | Jun 2017 | B1 |
| 9697544 | Bayer et al. | Jul 2017 | B1 |
| 9727904 | Inghelbrecht et al. | Aug 2017 | B2 |
| 9741066 | Eager et al. | Aug 2017 | B2 |
| 9754304 | Taira et al. | Sep 2017 | B2 |
| 9818140 | Inghelbrecht et al. | Nov 2017 | B2 |
| 9904933 | Taira et al. | Feb 2018 | B2 |
| 9904948 | Taira et al. | Feb 2018 | B2 |
| 10009432 | Tang et al. | Jun 2018 | B1 |
| 10162848 | Mohan et al. | Dec 2018 | B2 |
| 10163156 | Shapley | Dec 2018 | B1 |
| 10217123 | Taira et al. | Feb 2019 | B2 |
| 10269030 | Taira et al. | Apr 2019 | B2 |
| 10269031 | Inghelbrecht et al. | Apr 2019 | B2 |
| 10380654 | Hirtenstein et al. | Aug 2019 | B2 |
| 10409867 | Von Busch et al. | Sep 2019 | B1 |
| 10430848 | Cotton et al. | Oct 2019 | B2 |
| 10489809 | Inghelbrecht et al. | Nov 2019 | B2 |
| 10489810 | Taira et al. | Nov 2019 | B2 |
| 10515382 | Taira et al. | Dec 2019 | B2 |
| 10565181 | Hjermstad et al. | Feb 2020 | B1 |
| 10580054 | Cain et al. | Mar 2020 | B2 |
| 10581825 | Poschel et al. | Mar 2020 | B2 |
| 10740404 | Hjermstad et al. | Aug 2020 | B1 |
| 10853831 | Inghelbrecht et al. | Dec 2020 | B2 |
| 10977727 | Smith et al. | Apr 2021 | B1 |
| 11017427 | Badger et al. | May 2021 | B1 |
| 11157835 | Hjermstad et al. | Oct 2021 | B1 |
| 11176608 | Smith | Nov 2021 | B1 |
| 11210276 | Smith | Dec 2021 | B1 |
| 11210351 | Von Busch et al. | Dec 2021 | B1 |
| 11257126 | Hirtenstein et al. | Feb 2022 | B2 |
| 11301922 | Smith | Apr 2022 | B2 |
| 11366860 | Hjermstad et al. | Jun 2022 | B1 |
| 11481827 | Cain et al. | Oct 2022 | B1 |
| 11532030 | Smith | Dec 2022 | B1 |
| 11568005 | Von Busch et al. | Jan 2023 | B1 |
| 11587163 | Smith | Feb 2023 | B1 |
| 11640433 | Hjermstad et al. | May 2023 | B1 |
| 11790269 | Hjermstad et al. | Oct 2023 | B1 |
| 11836785 | Smith | Dec 2023 | B1 |
| 11886519 | Von Busch et al. | Jan 2024 | B1 |
| 20010044769 | Chaves | Nov 2001 | A1 |
| 20020023051 | Kunzle et al. | Feb 2002 | A1 |
| 20020042752 | Chaves | Apr 2002 | A1 |
| 20020072964 | Choi | Jun 2002 | A1 |
| 20020082978 | Ghouri et al. | Jun 2002 | A1 |
| 20020091706 | Anderson et al. | Jul 2002 | A1 |
| 20020099628 | Takaoka et al. | Jul 2002 | A1 |
| 20020103622 | Burge | Aug 2002 | A1 |
| 20020128960 | Lambiotte et al. | Sep 2002 | A1 |
| 20020161496 | Yamaki | Oct 2002 | A1 |
| 20020193925 | Funkhouser et al. | Dec 2002 | A1 |
| 20030033242 | Lynch et al. | Feb 2003 | A1 |
| 20030041019 | Vagim, III et al. | Feb 2003 | A1 |
| 20030046179 | Anabtawi et al. | Mar 2003 | A1 |
| 20030101111 | Dang et al. | May 2003 | A1 |
| 20030105728 | Yano et al. | Jun 2003 | A1 |
| 20030144950 | O'Brien et al. | Jul 2003 | A1 |
| 20030177481 | Amaru et al. | Sep 2003 | A1 |
| 20030187753 | Takaoka | Oct 2003 | A1 |
| 20030200151 | Ellenson et al. | Oct 2003 | A1 |
| 20030216965 | Libman | Nov 2003 | A1 |
| 20030233323 | Bilski et al. | Dec 2003 | A1 |
| 20040034657 | Zambo et al. | Feb 2004 | A1 |
| 20040039646 | Hacker | Feb 2004 | A1 |
| 20040088228 | Mercer et al. | May 2004 | A1 |
| 20040093286 | Cooper et al. | May 2004 | A1 |
| 20040107125 | Guheen et al. | Jun 2004 | A1 |
| 20040128262 | Nafousi | Jul 2004 | A1 |
| 20040163101 | Swix | Aug 2004 | A1 |
| 20040193644 | Baker et al. | Sep 2004 | A1 |
| 20040243506 | Das | Dec 2004 | A1 |
| 20040249532 | Kelly et al. | Dec 2004 | A1 |
| 20050010555 | Gallivan | Jan 2005 | A1 |
| 20050021384 | Pantaleo et al. | Jan 2005 | A1 |
| 20050038580 | Seim et al. | Feb 2005 | A1 |
| 20050113991 | Rogers et al. | May 2005 | A1 |
| 20050173524 | Schrader | Aug 2005 | A1 |
| 20050177489 | Neff et al. | Aug 2005 | A1 |
| 20050209892 | Miller | Sep 2005 | A1 |
| 20050234912 | Roach | Oct 2005 | A1 |
| 20050246256 | Gastineau et al. | Nov 2005 | A1 |
| 20050251820 | Stefanik et al. | Nov 2005 | A1 |
| 20050256780 | Eldred | Nov 2005 | A1 |
| 20050267754 | Schultz et al. | Dec 2005 | A1 |
| 20050267774 | Merritt et al. | Dec 2005 | A1 |
| 20060004731 | Seibel et al. | Jan 2006 | A1 |
| 20060010052 | Willingham | Jan 2006 | A1 |
| 20060015425 | Brooks | Jan 2006 | A1 |
| 20060031182 | Ryan et al. | Feb 2006 | A1 |
| 20060041443 | Horvath | Feb 2006 | A1 |
| 20060107560 | Wong | May 2006 | A1 |
| 20060149674 | Cook et al. | Jul 2006 | A1 |
| 20060163868 | Baumann | Jul 2006 | A1 |
| 20060178957 | LeClaire | Aug 2006 | A1 |
| 20060178973 | Chiovari et al. | Aug 2006 | A1 |
| 20060202012 | Grano et al. | Sep 2006 | A1 |
| 20060202862 | Ratnakar | Sep 2006 | A1 |
| 20060206416 | Farias | Sep 2006 | A1 |
| 20060218079 | Goldblatt et al. | Sep 2006 | A1 |
| 20060229799 | Nimmo et al. | Oct 2006 | A1 |
| 20060242046 | Haggerty et al. | Oct 2006 | A1 |
| 20060242050 | Haggerty et al. | Oct 2006 | A1 |
| 20060277141 | Palmer | Dec 2006 | A1 |
| 20070011083 | Bird et al. | Jan 2007 | A1 |
| 20070027791 | Young et al. | Feb 2007 | A1 |
| 20070043487 | Krzystofczyk et al. | Feb 2007 | A1 |
| 20070059442 | Sabeta | Mar 2007 | A1 |
| 20070136163 | Bell | Jun 2007 | A1 |
| 20070156515 | Hasselback et al. | Jul 2007 | A1 |
| 20070162293 | Malkon | Jul 2007 | A1 |
| 20070173993 | Nielsen et al. | Jul 2007 | A1 |
| 20070179798 | Inbarajan | Aug 2007 | A1 |
| 20070179860 | Romero | Aug 2007 | A1 |
| 20070185777 | Pyle et al. | Aug 2007 | A1 |
| 20070192165 | Haggerty et al. | Aug 2007 | A1 |
| 20070226131 | Decker et al. | Sep 2007 | A1 |
| 20070244732 | Chatterji et al. | Oct 2007 | A1 |
| 20070250327 | Hedy | Oct 2007 | A1 |
| 20070271178 | Davis et al. | Nov 2007 | A1 |
| 20070282713 | Ullman et al. | Dec 2007 | A1 |
| 20070288271 | Klinkhammer | Dec 2007 | A1 |
| 20070294163 | Harmon et al. | Dec 2007 | A1 |
| 20080015954 | Huber et al. | Jan 2008 | A1 |
| 20080016119 | Sharma et al. | Jan 2008 | A1 |
| 20080059317 | Chandran et al. | Mar 2008 | A1 |
| 20080071882 | Hering et al. | Mar 2008 | A1 |
| 20080097663 | Morimoto | Apr 2008 | A1 |
| 20080120155 | Pliha | May 2008 | A1 |
| 20080126137 | Kidd et al. | May 2008 | A1 |
| 20080177590 | Brodsky et al. | Jul 2008 | A1 |
| 20080183689 | Kubota et al. | Jul 2008 | A1 |
| 20080183722 | Lane et al. | Jul 2008 | A1 |
| 20080201163 | Barker et al. | Aug 2008 | A1 |
| 20080228635 | Megdal et al. | Sep 2008 | A1 |
| 20080235061 | Innes | Sep 2008 | A1 |
| 20080255897 | Megdal et al. | Oct 2008 | A1 |
| 20080294540 | Celka et al. | Nov 2008 | A1 |
| 20080294546 | Flannery | Nov 2008 | A1 |
| 20080301188 | O'Hara | Dec 2008 | A1 |
| 20080312969 | Raines et al. | Dec 2008 | A1 |
| 20090018996 | Hunt et al. | Jan 2009 | A1 |
| 20090055044 | Dienst | Feb 2009 | A1 |
| 20090063172 | Thomas et al. | Mar 2009 | A1 |
| 20090083130 | Hall et al. | Mar 2009 | A1 |
| 20090138290 | Holden | May 2009 | A1 |
| 20090144201 | Gierkink et al. | Jun 2009 | A1 |
| 20090187513 | Noy et al. | Jul 2009 | A1 |
| 20090240602 | Mohr et al. | Sep 2009 | A1 |
| 20090240735 | Grandhi et al. | Sep 2009 | A1 |
| 20090254856 | Cwajbaum | Oct 2009 | A1 |
| 20090271296 | Romero | Oct 2009 | A1 |
| 20090271385 | Krishnamoorthy et al. | Oct 2009 | A1 |
| 20090287370 | Iwai et al. | Nov 2009 | A1 |
| 20100030649 | Ubelhor | Feb 2010 | A1 |
| 20100049538 | Frazer et al. | Feb 2010 | A1 |
| 20100070343 | Taira et al. | Mar 2010 | A1 |
| 20100070382 | Inghelbrecht et al. | Mar 2010 | A1 |
| 20100076881 | O'Grady et al. | Mar 2010 | A1 |
| 20100082792 | Johnson | Apr 2010 | A1 |
| 20100088158 | Pollack | Apr 2010 | A1 |
| 20100094664 | Bush et al. | Apr 2010 | A1 |
| 20100153235 | Mohr et al. | Jun 2010 | A1 |
| 20100161486 | Liu et al. | Jun 2010 | A1 |
| 20100174657 | Stanton, Jr. | Jul 2010 | A1 |
| 20100179861 | Teerilahti et al. | Jul 2010 | A1 |
| 20100198629 | Wesileder et al. | Aug 2010 | A1 |
| 20100217616 | Colson et al. | Aug 2010 | A1 |
| 20100223106 | Hallowell et al. | Sep 2010 | A1 |
| 20100293089 | Peterson et al. | Nov 2010 | A1 |
| 20100293181 | Muller et al. | Nov 2010 | A1 |
| 20100299190 | Pratt et al. | Nov 2010 | A1 |
| 20100332292 | Anderson | Dec 2010 | A1 |
| 20110022489 | Hallowell et al. | Jan 2011 | A1 |
| 20110022525 | Swinson et al. | Jan 2011 | A1 |
| 20110040440 | de Oliveira et al. | Feb 2011 | A1 |
| 20110082759 | Swinson et al. | Apr 2011 | A1 |
| 20110137758 | Bienias | Jun 2011 | A1 |
| 20110161115 | Hampton | Jun 2011 | A1 |
| 20110202471 | Scott et al. | Aug 2011 | A1 |
| 20110213641 | Metzger, II et al. | Sep 2011 | A1 |
| 20110264595 | Anspach et al. | Oct 2011 | A1 |
| 20110270706 | Anspach et al. | Nov 2011 | A1 |
| 20110270707 | Breed et al. | Nov 2011 | A1 |
| 20110276467 | Blackburn et al. | Nov 2011 | A1 |
| 20110320241 | Miller | Dec 2011 | A1 |
| 20120005045 | Baker | Jan 2012 | A1 |
| 20120005070 | McFall et al. | Jan 2012 | A1 |
| 20120005108 | Hollenshead et al. | Jan 2012 | A1 |
| 20120106801 | Jackson | May 2012 | A1 |
| 20120109770 | Seergy et al. | May 2012 | A1 |
| 20120197699 | Snell et al. | Aug 2012 | A1 |
| 20120221485 | Leidner et al. | Aug 2012 | A1 |
| 20120239637 | Prakash et al. | Sep 2012 | A9 |
| 20120254017 | Fusco et al. | Oct 2012 | A1 |
| 20120265648 | Jerome et al. | Oct 2012 | A1 |
| 20120271850 | Licata Messana et al. | Oct 2012 | A1 |
| 20120331010 | Christie | Dec 2012 | A1 |
| 20130006801 | Solari et al. | Jan 2013 | A1 |
| 20130006809 | Hollenshead et al. | Jan 2013 | A1 |
| 20130159033 | Weinstock et al. | Jun 2013 | A1 |
| 20130173453 | Raines et al. | Jul 2013 | A1 |
| 20130173481 | Hirtenstein et al. | Jul 2013 | A1 |
| 20130238455 | Laracey | Sep 2013 | A1 |
| 20130268298 | Elkins et al. | Oct 2013 | A1 |
| 20140025681 | Raines | Jan 2014 | A1 |
| 20140058956 | Raines et al. | Feb 2014 | A1 |
| 20140082017 | Miller | Mar 2014 | A1 |
| 20140258309 | Young | Sep 2014 | A1 |
| 20140278402 | Charugundla | Sep 2014 | A1 |
| 20140279868 | Astorg et al. | Sep 2014 | A1 |
| 20140358719 | Inghelbrect et al. | Dec 2014 | A1 |
| 20150154608 | Raines | Jun 2015 | A9 |
| 20150213559 | Raines et al. | Jul 2015 | A1 |
| 20150227942 | Sidman et al. | Aug 2015 | A1 |
| 20150310865 | Fay et al. | Oct 2015 | A1 |
| 20150317728 | Nguyen | Nov 2015 | A1 |
| 20150324400 | Sheck et al. | Nov 2015 | A1 |
| 20150332411 | Bush et al. | Nov 2015 | A1 |
| 20150348143 | Raines et al. | Dec 2015 | A1 |
| 20150348145 | Nakajima | Dec 2015 | A1 |
| 20160004742 | Mohan et al. | Jan 2016 | A1 |
| 20160012494 | Lasini | Jan 2016 | A1 |
| 20160048698 | Sahu et al. | Feb 2016 | A1 |
| 20160104222 | Savir | Apr 2016 | A1 |
| 20160217046 | Lamoureux et al. | Jul 2016 | A1 |
| 20160267588 | Cain et al. | Sep 2016 | A1 |
| 20160299905 | Geyer et al. | Oct 2016 | A1 |
| 20160321726 | Singh et al. | Nov 2016 | A1 |
| 20160379486 | Taylor | Dec 2016 | A1 |
| 20170052652 | Denton et al. | Feb 2017 | A1 |
| 20170270490 | Penilla et al. | Sep 2017 | A1 |
| 20170323295 | Kranzley et al. | Nov 2017 | A1 |
| 20180018723 | Nagla et al. | Jan 2018 | A1 |
| 20180107676 | Vora | Apr 2018 | A1 |
| 20180108189 | Park et al. | Apr 2018 | A1 |
| 20180157761 | Halstead et al. | Jun 2018 | A1 |
| 20180165747 | Patten et al. | Jun 2018 | A1 |
| 20180260838 | New et al. | Sep 2018 | A1 |
| 20180349988 | Shebesta et al. | Dec 2018 | A1 |
| 20190295133 | Hirtenstein et al. | Sep 2019 | A1 |
| 20200051102 | Taira et al. | Feb 2020 | A1 |
| 20200065885 | Smith | Feb 2020 | A1 |
| 20200065898 | Forrester | Feb 2020 | A1 |
| 20200265480 | Swinson et al. | Aug 2020 | A1 |
| 20220198527 | Hirtenstein et al. | Jun 2022 | A1 |
| Number | Date | Country |
|---|---|---|
| 0 749 081 | Dec 1996 | EP |
| 1 122 664 | Aug 2001 | EP |
| 09-251486 | Sep 1997 | JP |
| 10-222559 | Aug 1998 | JP |
| 10-261009 | Sep 1998 | JP |
| 2000-331068 | Nov 2000 | JP |
| 2001-297141 | Oct 2001 | JP |
| 2001-344463 | Dec 2001 | JP |
| 2001-357256 | Dec 2001 | JP |
| 2002-149778 | May 2002 | JP |
| 2002-163498 | Jun 2002 | JP |
| 2002-259753 | Sep 2002 | JP |
| 2003-271851 | Sep 2003 | JP |
| 2003-316881 | Nov 2003 | JP |
| 2004245897 | Sep 2004 | JP |
| 2007-299281 | Nov 2007 | JP |
| 10-2000-0036594 | Jul 2000 | KR |
| 10-2000-0063995 | Nov 2000 | KR |
| 10-2001-0016349 | Mar 2001 | KR |
| 10-2001-0035145 | May 2001 | KR |
| 10-2002-0007132 | Jan 2002 | KR |
| 10-2002-0068866 | Aug 2002 | KR |
| 20140020388 | Feb 2014 | KR |
| 503219 | Aug 2003 | NZ |
| WO 99004350 | Jan 1999 | WO |
| WO 99022328 | May 1999 | WO |
| WO 01071458 | Sep 2001 | WO |
| WO 01075754 | Oct 2001 | WO |
| WO 03101123 | Dec 2003 | WO |
| WO 2007149941 | Dec 2007 | WO |
| WO 2008022289 | Feb 2008 | WO |
| WO 2018199992 | Nov 2018 | WO |
| Entry |
|---|
| U.S. Appl. No. 14/975,470, U.S. Pat. No. 10,580,054, System, Method, Apparatus and Medium for Simultaneously Generating Vehicle History Reports and Preapproved Financing Options, filed Dec. 18, 2015. |
| U.S. Appl. No. 16/792,107, U.S. Pat. No. 11,481,827, System, Method, Apparatus and Medium for Simultaneously Generating Vehicle History Reports and Preapproved Financing Options, filed Feb. 14, 2020. |
| “Activant PartExpert with Vehicle Identification Number (VIN) Lookup”, Activant Solutions, Inc., Livermore, CA, Copyright 2006, http://counterworks.com/PartExp_DS_092806.pdf, pp. 2. |
| “AutoConnect Partners with Organic to Build World's Most Comprehensive Online Emporium of Pre-Owned Vehicles”, PR Newswire, May 19, 1998, pp. 2. |
| “Auto Market StatisticsSM:Drive Response with Aggregated Motor Vehicle Information”, Experian, Apr. 2007, http://www.experian.com/assets/marketing-services/product-sheets/auto-market-statistics.pdf, pp. 2. |
| “Appraisal Tool”, VAuto Live Market View, Dec. 14, 2007, http://www.vauto.com/vAuto_solution/appraisal.asp, pp. 3. |
| Autobytel.com, http://web.archive.org/web/20040806010507//http://autobytel.com/, as archived Aug. 6, 2004, pp. 3. |
| Bala, Pradip Kumar, “Purchase-Driven Classification for Improved Forecasting in Spare Parts Inventory Replenishment,” International Journal of Computer Applications, Nov. 2010, vol. 10, No. 9, pp. 40-45. |
| Bankrate.com, http://web.archive.org/web/20040809000026/www.bankrate.com/brm/default.asp, as archived Aug. 9, 2004, pp. 3. |
| “Carfax Teams with Esurance”, PR Newswire, May 14, 2001, p. 1. |
| Cars.com, http://web.archive.org/web/20041010081241/www.cars.com/go/index.jsp?aff=national, as archived Oct. 10, 2004, pp. 2. |
| Carsdirect.com, http://web.archive.org/web/20040730142836/www.carsdirect.com/home, as archived Jul. 30, 2004, pp. 2. |
| Checkbook.org, http://web.archive.org/web/20040604192834/www.checkbook.org/auto/carbarg.cfm, as archived Jun. 4, 2004, p. 1. |
| “Consumer Reports Finds American-Made Vehicles Close Reliability Gap with European-Made Vehicle—As Japanese Continue to Set New Benchmarks for the Industry”, Consumer Reports: Consumers Union, Yonkers, NY, Apr. 2003, pp. 2. |
| Cohen et al., “Optimizer: IBM's Multi Echelon Inventory System for Managing Service Logistics”, Interfaces, vol. 20, No. 1, Jan.-Feb. 1990, pp. 65-82. |
| Copeland et al., “Wallet-on-Wheels—Using Vehicle's Identity for Secure Mobile Money”, 17th International Conference on Intelligence in Next Generation Networks, 2013, pp. 102-109. |
| “Driveitaway.com Links with AutoCheck to Provide Car Shoppers Vehicle Histories; Consumers Bidding on Driveitaway.com's Used Auto Auctions Can Now Go Online to Research a Specific Vehicle's History”, PR Newswire, Jan. 15, 2001, p. 1. |
| “Experian Uses SSA-NAME3 to Match 40 to 50 Million Transactions per Month Against an 11.5 Billion Row Database”, DM Review, Apr. 2001, vol. 11, No. 4, pp. 3. |
| Farrell et al., “Installed Base and Compatibility: Innovation, Product Preannouncements, and Predation”, The American Economic Review, Dec. 1986, vol. 76, No. 5, pp. 940-955. |
| Garcia-Molina et al., “Database Systems: The Complete Book”, Prentice Hall, Inc., Ch. 15, Oct. 1, 2001, pp. 713-715. |
| Grange, Frank, “Challenges in Modeling Demand for Inventory Optimization of Slow-Moving Items,” Proceedings of the 1998 Winter Simulation Conference, 1998, pp. 1211-1217. |
| Greenlight.com Teams up With Credit Online to Expand Online Financing Options, Published in PR Newswire Association LLC; New York; Aug. 28, 2000 extracted from Dialog on Jun. 14, 2021, pp. 3. |
| Haffar, Imad, “SPAM: A Computer Model for Management of Spare-Parts Inventories in Agricultural Machinery Dealerships”, Computers and Electronics in Agriculture, vol. 12, Issue 4, Jun. 1995, pp. 323-332. |
| Handfield et al., “Managing Component Life Cycles in Dynamic Technological Environments”, International Journal of Purchasing and Materials Management, Tempe, Spring 1994, vol. 30, No. 2, pp. 20-28. |
| Inderfurth et al., “Decision Support for Spare Parts Acquisition in Post Product Life Cycle”, Central European Journal of Operations Research, 2008, vol. 16, pp. 17-42. |
| “Intelligence Insight Impact”, Polk Automotive Manufacturers; http://usa.polk.com/Industries/AutoMfr/Analyze/MarketAnalysis/, Dec. 13, 2007, pp. 3. |
| International Search Report and Written Opinion in PCT Application No. PCT/US07/76152, dated Mar. 20, 2009. |
| Invoicedealers.com, http://web.archive.org/web/20040804044511/http://www.invoicedealers.com/, Aug. 4, 2004, pp. 2. |
| Ivillage.com, http://web.archive.org/web/20040729234947/http://www.ivillage.com/, Jul. 29, 2004, pp. 2. |
| “Japan's JAAI System Appraises Used Cars Over Internet”, Asia Pulse, Mar. 3, 2000, p. 1. |
| Jaro, Matthew A., “Probabilistic Linkage of Large Public Health Data Files”, Statistics in Medicine, 1995, vol. 14, pp. 491-498. |
| Käki, Anssi, “Forecasting in End-Of-Life Spare Parts Procurement”, Master's Thesis, Helsinki University of Technology, System Analysis Laboratory, Jul. 27, 2007, pp. 84. |
| Kennedy et al., “An Overview of Recent Literature on Spare Parts Inventories”, International Journal of Production Economics, 2002, vol. 76, pp. 201-215. |
| Kim et al., “Optimal Pricing, EOL (End of Life) Warranty, and Spare Parts Manufacturing Strategy Amid Product Transition”, European Journal of Operation Research, 2008, vol. 188, pp. 723-745. |
| Koller, Mike, “Wireless Service Aids,” InternetWeek, Jul. 9, 2001, p. 15. |
| Krupp, James A.G., “Forecasting for the Automotive Aftermarket”, The Journal of Business Forecasting Methods & Systems, Winter 1993-1994, vol. 12, No. 4, ABI/Inform Global, pp. 8-12. |
| Lapide, Larry, “New Developments in Business Forecasting”, The Journal of Business Forecasting, Spring 2002, pp. 12-14. |
| Lee, Ho Geun, “AUCNET: Electronic Intermediary for Used-Car Transactions”, EM—Electronic Markets, Dec. 1997, vol. 7, No. 4, pp. 24-28. |
| Miller, Joe, “NADA Used-Car Prices Go Online”, Automotive News, Jun. 14, 1999, p. 36. |
| Moore, John R., Jr. “Forecasting and Scheduling for Past-Model Replacement Parts”, Management Science, Application Series, vol. 18, No. 4, Part 1, Dec. 1971, pp. B-200-B-213. |
| “NAAA—Recommended Vehicle Condition Grading Scale”, Noted as early as 2007, pp. 3. |
| Packer, A. H., “Simulation and Adaptive Forecasting an Applied to Inventory Control”, Operations Research, Jul. 1965, vol. 15, No. 4, pp. 660-679. |
| “Power Information Network: Power to Drive your Business”, J.D. Power and Associates Power Information Network, http://www.powerinfonet.com/products/productDetail.asp?type=financialinstitutions, Dec. 13, 2007, pp. 2. |
| Peters, Peter-Paul, “A Spare Parts Configurator for the European Service Business” (Graduation Report), Honeywell, Industrial Service Logistic Center, Amsterdam, The Netherlands, Mar. 2000, pp. 80. |
| Porter, G. Zell, “An Economic Method for Evaluating Electronic Component Obsolescence Solutions”, www.gidep.org/data/dmsms/library/zell.pdf, May 1998, pp. 1-9. |
| “Pricing Tool”, vAuto Live Market View, http://www.vauto.com/vAuto_Solution/pricing.asp, Dec. 13, 2007, pp. 2. |
| Reinbach, Andrew, “MCIF Aids Banks in CRA Compliance”, Bank Systems & Technology, Aug. 1995, vol. 32, No. 8, p. 27. |
| Roos, Gina, “Web-Based Service Helps OEMs Cure Parts Obsolescence Blues”, Electronic Engineering Times, Oct. 8, 2001, p. 86. |
| Santarini, Michael, “Forecasts the Probable Obsolescence of Components—Module Predicts Parts Life”, Electronic Engineering Times, Jan. 11, 1999, vol. 1, p. 48. |
| Sawyers, Arlena, “NADA to Offer Residual Guide”, Automotive News, May 22, 2000, p. 1. |
| Shapiro et al., “Systems Competition and Aftermarkets: an Economic Analysis of Kodak”, The Antitrust Bulletin, Spring 1994, pp. 135-162. |
| “Stoneage Corporation Announces Database of 250,000 Used Cars Posted to the Internet”, PR Newswire, Feb. 24, 1998, p. 1. |
| Sullivan, Laurie, “Obsolete-Parts Program Thriving”, EBN, Manhasset, NY, Jan. 21, 2002, Issue 1296, p. 26. |
| “The Most Reliable Cars 2006”, https://www.forbes.com/2006/04/20/reliable-vehicles-japanese_cx_dl_0424feat%20html?sh=19b3172a48f3, Apr. 24, 2006, pp. 4. |
| “Urban Science Launches Second Generation Lead Scoring Solution”, Urban Science, Detroit, MI, Mar. 1, 2007, http://www.urbanscience.com/newsevents/pr_20070222.html, pp. 3. |
| “WashingtonPost.com and Cars.com Launch Comprehensive Automotive Web Site For the Washington Area”, PR Newswire, Oct. 22, 1998. pp. 2. |
| Watts, Craig, “Consumers Now Can Know What Loan Rate Offers to Expect Based on Their FICO Credit Score at MyFICO.com,” San Rafael, CA, Mar. 6, 2002, pp. 2, http://www.myfico.com/PressRoom/PressReleases/2002_03_06.aspx. |
| Webster, Lee R., “Failure Rates & Life-Cycle Costs”, Consulting-Specifying Engineer, Apr. 1998, vol. 23, No. 4, ABI/Inform Global, p. 42. |
| “Web Sites Let Automotive Consumers Arm Themselves with Price Information”, Orange County Register, Nov. 14, 1997, pp. 3. |
| “Yahoo! Autos Provides Enhanced Road Map for Researching, Buying and Selling Cars Online”, PR Newswire, Oct. 13, 1998, pp. 2. |
| Number | Date | Country | |
|---|---|---|---|
| 62093973 | Dec 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16792107 | Feb 2020 | US |
| Child | 17948081 | US | |
| Parent | 14975470 | Dec 2015 | US |
| Child | 16792107 | US |
