Patent Grant
10032216
The present disclosure generally relates to assessing the condition of a vehicle and, more particularly, to a method for gathering and analyzing condition related data.
When customers purchase used vehicles, they often encounter the challenge of assessing the actual condition of vehicles with limited access to information about the vehicles. In most cases, customers only have access to general information about vehicles, such as year, make, model, mileage and physical appearance. From such general information, it is impossible to accurately assess the condition of a vehicle, much less how the vehicle was driven (e.g. severe acceleration and braking, towing a trailer, etc.), where the vehicle was driven (rural areas, urban areas, the “salt belt,” etc.), and under what conditions was the vehicle driven (e.g. traffic, highway, snow, etc.).
In one embodiment, a computer-implemented method comprises receiving information identifying a vehicle via a computer network, retrieving, with one or more processors, condition data corresponding to the vehicle from a condition database, wherein a device inside the vehicle generates at least some of the condition data while the vehicle is being operated, and analyzing, with one or more processors, the condition data to determine a condition of the vehicle, wherein the condition of the vehicle relates to at least one of a quality or a value of the vehicle. Further, the method comprises communicating, via the computer network, an indication of the vehicle condition to an end user device, in response to the indication of the vehicle condition, receiving, via the computer network, an offer to purchase the vehicle, and generating, with one or more processors, a notification based on the offer to purchase the vehicle, wherein the notification indicates a status of a purchase of the vehicle according to the offer to purchase the vehicle, and communicating, via the computer network, the notification to the end user device.
In another embodiment, a computer-implemented method for buying and selling vehicles on a computing device including a user interface and a display device, comprises receiving, via the user interface, information identifying a vehicle, generating, with one or more processors, an identification message including at least some of the information identifying the vehicle of interest, and sending, via a network interface at the computing device, the identification message to a server. Further the method comprises, in response to the identification message, receiving, via the network interface at the computing device, condition information corresponding to the vehicle and reflecting a condition of the vehicle, wherein the condition of the vehicle is determined based on an analysis of condition data generated by a device inside the vehicle while the vehicle is being operated, and wherein the condition of the vehicles includes a value of the vehicle. Also, the method comprises rendering, with one or more processors, an image of at least part of the condition information, presenting, via the display device, the image of at least part of the condition information to a user of the computing device, receiving, via the user interface, an offer to purchase the vehicle, generating, with one or more processors, an offer message including the offer to purchase the vehicle, and sending, via the network interface at the computing device, the offer message to the server. Still further, the method comprises, in response to the offer message, receiving, via the network interface at the computing device, a notification indicating a status of a purchase of the vehicle according to the offer to purchase the vehicle, rendering, with one or more processors, an image of the notification, and presenting, via the display device, the image of the notification to the user of the computing device.
In yet another embodiment, a computer device for assessing the condition of a vehicle comprises one or more processors and one or more non-transitory memories coupled to the one or more processors, wherein the one or more memories include computer executable instructions stored therein that, when executed by the one or more processors, cause the one or more processors to: receive information identifying a vehicle via a computer network, retrieve condition data corresponding to the vehicle from a condition database, wherein a device inside the vehicle generates at least some of the condition data while the vehicle is being operated, and analyze, with one or more processors, the condition data to determine a condition of the vehicle, wherein the condition of the vehicle relates to at least one of a quality or a value of the vehicle. Further, when executed by the one or more processors, the computer executable instructions cause one or more processors to: communicate, via the computer network, an indication of the vehicle condition to an end user device, in response to the indication of the vehicle condition, receive, via the computer network, an offer to purchase the vehicle, generate, with the one or more processors, a notification based on the offer to purchase the vehicle, wherein the notification includes information related to the purchase of the vehicle, and communicate, via the computer network, the notification to the end user device.
Although the following text sets forth a detailed description of numerous different embodiments, it should be understood that the legal scope of the description is defined by the words of the claims set forth at the end of this disclosure. The detailed description is to be construed as exemplary only and does not describe every possible embodiment since describing every possible embodiment would be impractical, if not impossible. Numerous alternative embodiments could be implemented, using either current technology or technology developed after the filing date of this patent, which would still fall within the scope of the claims.
It should also be understood that, unless a term is expressly defined in this patent using the sentence “As used herein, the term ‘——————’ is hereby defined to mean . . . ” or a similar sentence, there is no intent to limit the meaning of that term, either expressly or by implication, beyond its plain or ordinary meaning, and such terms should not be interpreted to be limited in scope based on any statement made in any section of this patent (other than the language of the claims). To the extent that any term recited in the claims at the end of this patent is referred to in this patent in a manner consistent with a single meaning, that is done for the sake of clarity only so as to not confuse the reader, and it is not intended that such claim term be limited, by implication or otherwise, to that single meaning. Finally, unless a claim element is defined by reciting the word “means” and a function without the recital of any structure, it is not intended that the scope of any claim element be interpreted based on the application of 35 U.S.C. § 112, sixth paragraph.
As used herein, the term “vehicle” may refer to any of a number of motorized transportation devices. A vehicle may be a car, truck, bus, train, boat, plane, etc. Additionally, as used herein, the term “driver” may refer to any operator of a vehicle. A driver may be a car driver, truck driver, bus driver, train engineer, captain of a boat, pilot of an airplane, etc.
System Overview
In some implementations, the vehicle 104 may upload condition data to the condition report server 102 via the network 110. For example, an on-board computing device (not shown) or end user device disposed in the vehicle 104 may wirelessly upload data from braking, acceleration, motion, force, environment, image, etc. sensors, via one or more wireless interfaces (not shown), for assessing the condition of the vehicle 104. In turn, the condition report server 102 may store the condition data in a condition database 115 that is communicatively coupled to the condition report server 102. The condition database 115 may include an assortment of computer-readable media. By way of example and without limitation, computer-readable media may include both volatile and nonvolatile media, removable and non-removable media.
Although the example system 100 is shown to include one condition report server 102 and five end user devices 106, it is understood that different numbers of servers and end user devices may be utilized. Furthermore, the processing performed by the condition report server 102 may be distributed among a plurality of servers in an arrangement known as “cloud computing,” in an implementation. This configuration may provide several advantages, such as enabling near real-time uploads and downloads of information as well as periodic uploads and downloads of information, for example.
While shown as a single block in
In other implementations, the end user device 200 is capable of executing a graphical interface (GUI) for an online vehicle condition reporting tool within a web browser application, such as Apple's Safari®, Google Android™ mobile web browser, Microsoft Internet Explorer®, etc. The web browser application may be implemented as a series of machine-readable instructions for receiving, interpreting, and displaying web page information (e.g. from web server 143) while also receiving inputs from the user.
Further, the portable device 200 includes a communication module 235, that facilitates wireless communication for data exchange over a mobile and/or wide area network, and a user interface 240. The user interface may include devices to receive inputs from a user, such as a keyboard, touchscreen, buttons, trackballs, etc., and display devices, such as liquid crystal displays (LCD), light emitting diodes (LED), organic light-emitting diodes (OLED), ePaper displays, etc.
Vehicle Condition Assessment
To begin, a vehicle condition query is received from an end user device (block 302). In one scenario, a user of one of the end user devices 106 may locate a used car for sale and input, via a user interface, information identifying the used car, via a user interface to one of the end user devices 106. For example, the information identifying the used car may include a license plate number, license plate state, manufacturer name, model name or number, color, vehicle identification number (VIN), registered owner name, owner contact information, insurance policy number, etc. In turn, the one of the end user devices 106 may send a vehicle condition query, including the information identifying the vehicle, to the condition report server 102 to obtain an assessment of the condition (e.g. quality or market value) of the used car, in the example scenario. In another scenario, the registration or entry of a vehicle in an online auction may trigger the communication of a vehicle condition query corresponding to the vehicle.
In some implementations, a vehicle condition query may include only vehicle interest information. For example, a user of the one or more end user devices 106 may input information related to a types of vehicles or specific vehicles the user is interested in purchasing. In such an implementation, the condition report server 102 may match certain vehicles, with corresponding condition data in the condition database 115, to the vehicle interest data. For example, the vehicle interest data may include an indication that the user is interested in a 1995 Jeep Wrangler within a certain geographic area. The condition server may query the condition database, as known in the industry, to find all such vehicles within the geographic area and subsequently assess the condition of the matched vehicles, as described below. In some implementations, the condition server 102 may only assess the condition of a pre-defined, or otherwise determined, number of matched vehicles. Further details regarding vehicle interest information are discussed with reference to
Upon receiving the vehicle condition query, condition data corresponding to the identified vehicle is retrieved from a vehicle condition database (block 304), such as condition database 115. In some implementations, the condition data may include data gathered from a variety of data sources, as described in U.S. application Ser. No. 13/897,646 entitled “Systems and Methods to Identify and Profile a Vehicle Operator” and filed on May 20, 2013, the entire disclosure of which is hereby incorporated by reference herein. By way of example and without limitation, such data sources may include: (i) sensors installed in vehicles, such as braking/acceleration/cornering sensors, tire pressure sensors, cameras, microphones, engine temperature sensors, mileage sensors, clocks, etc., (ii) sensors in mobile devices (e.g. smartphones, tablet computers, geopositioning receivers, etc.), where the mobile devices are temporarily disposed in vehicles, and (iii) third party databases (e.g. public record databases, insurance databases, etc.).
In some implementations, the condition data corresponding to the vehicle may be immediately descriptive of vehicle condition or descriptive of vehicle condition after manipulation. For example, data indicating vehicle mileage, year, and previous collisions/incidents may be immediately descriptive of the condition of a vehicle. On the other hand, engine rotations per minute (RPM), braking profiles, and geographic locations are example types of data that may be descriptive of the condition of a vehicle only after manipulation. In one scenario, an analysis of engine RPM data may indicate that a vehicle is frequently used for towing a trailer, and towing a trailer may be highly correlated with vehicle depreciation and/or high maintenance costs, example factors related to vehicle condition.
In some implementations, owners of used vehicles may receive incentives for contributing condition data for storage in a condition database. For example, car dealerships may offer more money to buy a car that has corresponding condition data recorded over the life of the car, as compared with a car that has no recorded condition data. In another example, an insurance company may provide coupons, discounts, or other rewards to customers that contribute condition data from insured vehicles.
The condition data stored in the condition database 115 may, in some implementations, be protected against fraud. For example, the condition data collected from used vehicles may be collected in real-time (i.e. wirelessly communicated to the condition server 102 immediately after being generated) and stored in a secure database (e.g. protected by authentication, encryption, etc.). In such a way, vehicle operators, or other interested persons, are prevented from modifying vehicle condition data to inaccurately reflect good/bad vehicle conditions.
Returning to
In a simple example scenario, the condition report server 102 may retrieve geopositioning data, acceleration/braking/cornering data, and maintenance history data from the condition database 115. The maintenance history data may indicate that a vehicle has a history free of frequent or severe maintenance/repair issues. However, the geopositioning data may indicate that the vehicle has primarily been driven in the “salt belt” region of the United States (a region where vehicles commonly encounter corrosion due to the use of road salt) and the acceleration/braking/cornering data may indicate erratic and severe acceleration, braking, and/or cornering (i.e. reckless driving). In such an example scenario, the condition report server 102 may assess the condition of the vehicle as relatively low quality/value because of probable current and/or future issues caused by the driving environment and driving behavior.
A customer considering only the maintenance history and general vehicle information (e.g. mileage, make, model, year, etc.) may overvalue the used car, in the above scenario. In contrast, the techniques of the present disclosure are able to provide an accurate assessment of vehicle quality by collectively analyzing condition data gathered from the vehicle over time, such as the geopositioning and acceleration/braking/cornering data in the above scenario, for example.
In some implementations, the condition report server 102 may collectively or comparatively analyze the condition data to assess vehicle condition. For example, mileage data may indicate a relatively high mileage (e.g. 100,000 miles as compared with an average of 75,000 miles for cars of the same year), whereas geopositioning data may indicate that the vehicle is predominately driven in rural areas of the state of Arizona. Independently, the high mileage may indicate low quality or value. However, when combined with geopositioning data, from which one could infer mostly highway driving (i.e. rural driving) in a dry climate (Arizona), the condition report server 102 may more moderately assess the vehicle quality and value, in the example case.
The condition report server 102 may assess both the past and future condition of the vehicle in addition to the current condition of the vehicle, in some implementations. The condition report server 102 may use prediction, modeling, simulation, or other suitable algorithms to infer a condition of a vehicle at times in the past and predict conditions of a vehicle in the future, for example. A prediction algorithm (e.g. trained on reference data) may predict that a certain vehicle will need brake replacement in one year, transmission service in two years, and tire replacement in one and a half years, in an example scenario.
Also, the condition report server 102 may use prediction, modeling, etc. algorithms to accurately assess the current condition of a vehicle, even when condition data is not available over the entire life, or age, of the vehicle. For example, condition data may be available for only five out of ten years of the life of a vehicle. In such a case, a simulation/modeling algorithm may stitch together the available data with simulations to provide an accurate assessment of current vehicle condition.
Once the vehicle condition is assessed, vehicle condition descriptors reflecting the condition of the vehicle are developed. The condition descriptors may include any suitable representation or representations of the condition of the vehicle, in an implementation. The condition descriptors may include, by way of example: (i) scores or ratings representing relative quality, value, mechanical operation, etc., such as a score between one and one hundred or a rating of one to five stars; (ii) text statements reflecting a condition, such as “low,” “moderate,” or “high” cost of ownership, “this car may have major repair needs within two years,” etc.; (iii) graphical representations of condition information, such as graphs, plots, or charts indicating average engine temperature as a function of time, maintenance/repair events per year, etc.; (iv) images or icons, such as a thumbs up/down, caution sign icons, etc.
Next, a vehicle condition report is generated to be presented on an end user device (block 310). In some implementations, the vehicle condition report includes some or all of the condition descriptors developed at block 306. For example, the condition report server 102 may generate a vehicle condition report in the form of one or more web pages including at least some of the condition descriptors, where the web pages may be displayed via a web browser application executed on the one or more end user devices 106.
In some implementations, the vehicle condition report is interactive. For example, the condition report server 102 may develop a vehicle condition report in the form of one or more interactive web pages or in the form of content for an interactive vehicle condition reporting application. An initial web page may display a general representation of vehicle condition, such as a series of scores or ratings, and, upon customer selection of a score or rating, further or modified web pages may display more detailed information, such as graphs, tables, etc. or even portions of the raw condition data itself, for example.
The vehicle condition report is sent to an end user device for presentation to a user (block 312). In some implementations, the condition report server 102 may initially send a partial vehicle condition report to the end user device, and then, based on user interaction with the report, the condition report server 102 may send additional portions of the vehicle condition report. Further, the condition report server 102 may generate and send variations of the vehicle condition report based on end user device configurations, in an implementation. For example, the condition report server may generate one variation of a vehicle condition report for a visually appealing display on a smartphone and another variation of a vehicle condition report for a visually appealing display on a tablet, laptop, or desktop computer.
In response to the vehicle condition report, offers to purchase the vehicle may be received (block 314). For example, users of the one or more end user devices 106 may view a vehicle condition report and offer to buy the vehicle assessed in the condition report. In some implementations, a plurality of users may make offers or bids to purchase the vehicle with each offer being higher than the previous offer. For example, users of the one or more end user devices 106 may view a current offer to buy the vehicle 104 as part of the vehicle condition report, and the condition report server 102 may communicate updates to the current offer periodically or each time a new offer is received.
In an implementation, the owner of the vehicle 104 or a third party auction service may generate the vehicle condition query and advertise the vehicle 104 to other users of a vehicle condition reporting tool. For example, users of the one or more end user devices 106 may initiate a vehicle condition reporting tool, such as vehicle condition reporting tool 215, which, in turn, displays vehicles available for purchase along with vehicle condition reports corresponding to the vehicles available for purchase. Moreover, in some implementations, users of a vehicle condition reporting tool may view vehicle condition reports corresponding to vehicles that are not available for purchase, and the users may still make offers to buy a vehicle that is not available for purchase or inquire as to when the vehicle will be available for purchase.
Finally, a buyer is identified, among the users who submitted an offer to purchase the vehicle, and the buyer is notified (block 316). For example, the condition report server 102 may identify a buyer as the user with the highest offer or the highest offer within a certain amount of time. Alternatively, the owner of a vehicle may specify criteria for a potential buyer, and communicate the criteria to the condition report server 102. For example, the condition report server may identify the buyer as the user with the highest offer and, according to criteria defined by the owner of the vehicle 104, is within a certain geographic area of the owner of the vehicle 104.
In some implementations, the buyer and/or the owner of the vehicle is notified of the final purchase price of the vehicle, the identity of the buyer, the contact information of the buyer/seller, etc. (block 318). For example, the buyer of the vehicle may be electronically contacted via email, text message, mobile phone alert, etc. with information indicating a successful purchase of the vehicle and instructions for completing purchase of the vehicle.
Vehicle Condition Reporting and Auction Tool
To begin, a vehicle condition reporting tool is initiated (block 402). In one implementation, one of the end user devices 106 may execute a vehicle condition reporting tool stored in memory (e.g. the vehicle condition reporting tool 215), where the vehicle condition reporting tool facilitates communications with the condition report server 102 and the display of vehicle condition reports and vehicle auction information. In another implementation, a user of one of the end user devices 106 may initiate a vehicle condition reporting tool via a web browser application.
Next, vehicle interest information, related to vehicles a user is interested in purchasing, is received via a user interface (block 404), such as the user interface 240. In some implementations, one of the end user devices 106 may display a series of forms, questions, buttons, etc. to prompt a user of one of the end user devices 106 to enter vehicle interest information. For example, the vehicle interest information may include indications of types of vehicles (e.g. truck, sport utility vehicle, luxury car, etc.), vehicle characteristics (e.g. four-door, power windows, heated seats, etc.), price ranges, preferred conditions (e.g. good/moderate/bad conditions, mileage, no major mechanics issues, etc.), or any other suitable indications that generally define a vehicle of interest. Alternatively, the vehicle interest information may include identifications of particular vehicles, in an implementation. For example, a user may identify a vehicle of interest at a car dealership, via personal interaction with the owner of the vehicle, via an online advertisement, etc. The user may enter (e.g. via the vehicle condition reporting tool) a VIN number, or other unique identification of the vehicle, for example.
In another implementation, a user of an end user device may use sensors in the device itself to automatically generate vehicle interest information. For example, a camera on a smartphone may capture an image of a license plate or scan a bar code representing a VIN number. In such a case, the end user device may analyze the automatically generated data and, in some implementations, transform the data into convenient formats (e.g. text, numbers, etc.) for vehicle identification.
Once vehicle interest information is received, a vehicle condition query is sent to a condition report server (block 406). The vehicle condition query includes the vehicle interest information, and, in some implementations, the vehicle condition query includes device specific information. For example, the vehicle condition query may include device specific information indicating device configurations (e.g. hardware, software, etc.), device users (e.g. usernames, passwords, identification numbers, etc.), device locations, etc.
Returning to
In some implementations, the condition report server 102 may use device specific information to customize vehicle condition reports. For example, the condition report server may use a device location to generate vehicle condition reports emphasizing relevant vehicle condition descriptors (e.g. through prominent display, icons, bold text, etc.).
In one scenario, an end user device may be located in an area with severe winter weather, and, as such, the condition report server may generate a vehicle condition reports that emphasize mechanical operation issues, repair issues, etc. that would be particularly relevant in cold climates (e.g. problems with a four wheel drive differential, problems starting an engine in cold weather, etc.). In another example, the condition report server 102 may customize vehicle condition reports for individual device users. In one scenario, a device user may indicate (via a user interface) that maintenance issues are not as important as vehicle aesthetic condition (e.g. paint condition, body condition, etc.). As such, the condition report server 102 may display information regarding vehicles aesthetics predominately in a vehicle condition report or analyze data related to aesthetics in more detail, for example.
Upon receiving the vehicle condition report, all or part of the vehicle condition report is displayed (block 410). For example, one of the end user devices 106 may display interactive web pages or other interactive vehicle condition content, as described with reference to
An end user device or condition report server may compare vehicle condition reports for multiple vehicles, matching the vehicle interest information, to create a comparison chart, relative scoring or rating of vehicles, or other suitable representation of the comparison of vehicle condition reports, in an implementation. For example, a user may save multiple vehicle condition reports (generated at different times) in the memory of one of the end user devices 106 and select the multiple vehicle condition reports to generate a vehicle condition comparison.
Next, an offer to purchase a vehicle may be received via a user interface of an end user device (block 412). For example, the one or more end user devices 106 may display text boxes, buttons, etc. for entering an offer to purchase one of the vehicles matching the vehicle interest information. In some implementations, vehicle condition reports may include suggested offer values, minimum offer values, or offer values pre-approved by the vehicle owner. In such a case, a user of the one or more end user devices 106 may select one of these offer values (e.g. via a click or tap) to submit an offer of that offer value.
Next, the offer to purchase the vehicle (received at block 412) is communicated to the condition report server (block 414). The offer to purchase the vehicle may be sent to the condition report server in any suitable form, such as a numerical value, text file, etc., for example. As mentioned above, the condition report server 102 may update the current offer on the vehicle according to the newly received offer.
In response to the communication of the offer, an auction notification is received (block 416). The auction notification may include, by way of example, a notification of purchase of a vehicle by the user, purchase of a vehicle by another party, an updated offer, termination of a vehicle auction, instructions to complete payment for a vehicle purchase, and of other vehicles of potential interest to the user. In some implementations, a user may display further portions of vehicle condition reports or different vehicle condition reports in response to the auction notification. Further, a user may make higher/different offers to purchase a vehicle in response to the auction notification.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3702989 | Provenzano, Jr. et al. | Nov 1972 | A |
| 3866166 | Kerscher, III et al. | Feb 1975 | A |
| 4027289 | Toman | May 1977 | A |
| 4159531 | McGrath | Jun 1979 | A |
| 4258421 | Juhasz et al. | Mar 1981 | A |
| 5361201 | Jost et al. | Nov 1994 | A |
| 5797134 | McMillan et al. | Aug 1998 | A |
| 5941915 | Federle et al. | Aug 1999 | A |
| 6289332 | Menig et al. | Sep 2001 | B2 |
| 6502080 | Eichorst et al. | Dec 2002 | B1 |
| 6526335 | Treyz et al. | Feb 2003 | B1 |
| 6654770 | Kaufman | Nov 2003 | B2 |
| 6711495 | Ukai et al. | Mar 2004 | B1 |
| 7111005 | Wessman | Sep 2006 | B1 |
| 7174243 | Lightner et al. | Feb 2007 | B1 |
| 7676306 | Kubo et al. | Mar 2010 | B2 |
| 7711574 | Bradley et al. | May 2010 | B1 |
| 7765039 | Hagenbuch | Jul 2010 | B1 |
| 8014974 | Doddek et al. | Sep 2011 | B2 |
| 8140358 | Ling et al. | Mar 2012 | B1 |
| 8838324 | Suzuki et al. | Sep 2014 | B2 |
| 20020065698 | Schick et al. | May 2002 | A1 |
| 20020143646 | Boyden | Oct 2002 | A1 |
| 20030009270 | Breed | Jan 2003 | A1 |
| 20040019517 | Sennott | Jan 2004 | A1 |
| 20040024483 | Holcombe | Feb 2004 | A1 |
| 20040153356 | Lockwood et al. | Aug 2004 | A1 |
| 20050154657 | Kim et al. | Jul 2005 | A1 |
| 20060033625 | Johnson et al. | Feb 2006 | A1 |
| 20060053075 | Roth et al. | Mar 2006 | A1 |
| 20060114531 | Webb et al. | Jun 2006 | A1 |
| 20060253293 | Osborn | Nov 2006 | A1 |
| 20070136077 | Hammond et al. | Jun 2007 | A1 |
| 20080046383 | Hirtenstein et al. | Feb 2008 | A1 |
| 20100005010 | Chenn | Jan 2010 | A1 |
| 20100106534 | Robinson et al. | Apr 2010 | A1 |
| 20100274571 | McFall | Oct 2010 | A1 |
| 20100318451 | Niccolini et al. | Dec 2010 | A1 |
| 20110264278 | Gilbert et al. | Oct 2011 | A1 |
| 20120197699 | Snell et al. | Aug 2012 | A1 |
| 20120209634 | Ling et al. | Aug 2012 | A1 |
| 20120246036 | Marr et al. | Sep 2012 | A1 |
| 20120262283 | Biondo et al. | Oct 2012 | A1 |
| 20130157647 | Kolodziej | Jun 2013 | A1 |
| 20140052501 | Dickson et al. | Feb 2014 | A1 |
| 20140058618 | Rude et al. | Feb 2014 | A1 |
| 20140095047 | Naylor | Apr 2014 | A1 |
| 20140289078 | Paul | Sep 2014 | A1 |
| 20140310186 | Ricci | Oct 2014 | A1 |
| 20140322676 | Raman | Oct 2014 | A1 |
| Entry |
|---|
| Honeycutt, Earl D., et al. “Determinants of ethical behavior: A study of autosalespeople.” Journal of Business Ethics 32.1 (2001): 69-79. (Year: 2001). |
| Office Action in U.S. Appl. No. 14/047,268 dated Jan. 29, 2014. |
| Office Action in U.S. Appl. No. 14/047,279 dated Jan. 29, 2014. |
| Office Action in U.S. Appl. No. 14/047,256 dated Jan. 27, 2014. |
| Office Action in U.S. Appl. No. 14/047,259 dated Jan. 16, 2014. |
| CarFax Sample Report, www.CarFax.com, accessed at http://www.carfax.com/phoenix/vehicle_history/SampleReport.cfx?reportName=consumerMobileWeb, archived Nov. 2012, accessed Jul. 2014. |
| Office Action in U.S. Appl. No. 14/047,259 dated Aug. 1, 2014. |
| Office Action in U.S. Appl. No. 14/047,268 dated Aug. 1, 2014. |
| Office Action in U.S. Appl. No. 14/047,279 dated Aug. 7, 2014. |
| Office Action in U.S. Appl. No. 14/047,256 dated Aug. 13, 2014. |
| Office Action in U.S. Appl. No. 14/047,256 dated Dec. 15, 2014. |
| Office Action in U.S. Appl. No. 14/047,268 dated Dec. 19, 2014. |
| Office Action in U.S. Appl. No. 14/047,279 dated Dec. 23, 2014. |
| Office Action in U.S. Appl. No. 14/047,259 dated Mar. 2, 2015. |
| Office Action in U.S. Appl. No. 14/047,268 dated Mar. 26, 2015. |
| Number | Date | Country | |
|---|---|---|---|
| 20150100448 A1 | Apr 2015 | US |
