IP Library Granted Patent US 7,236,983
Granted Patent B1
US 7,236,983 · App. 09/374,577 · Granted Jun 26, 2007

Hierarchical data structure for vehicle identification and configuration data including protected customer data

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,236,983
App. No.
09/374,577
Granted
Jun 26, 2007
Kind
B1
Abstract

A description language providing a hierarchical data structure that includes a public portion, hierarchically storing product information including identification of the product and standard and optional features desired for the product. The data structure further includes a private portion for secure storage of customer information. The discloser includes a system comprising a server with a product database, an intermediary subsystem, and a seller subsystem. A product is configured which stores the configured product and features in the data structure. A request for quote (RFQ) is transmitted, with the data structure, to sellers in the customer's geographic area, based on a comparison of product features with sellers stock. Quotes are returned from the sellers in response to which the customer sends an acceptance of a quote to the appropriate seller. While the invention is applicable to any product available in multiple configurations, specific embodiments are directed to vehicle implementations.

Claims (26)

1. A vehicle description language (VDL) hierarchical data structure that is stored in a memory system of one or more communicatively coupled computing systems interconnected through an intermediary subsystem and transmitted via communications medium between the communicatively coupled computing systems to communicate information associated with a vehicle in support of application(s) executing thereon, the data structure comprising:

(a) a public block of data, having starting and ending delimiters that identify the beginning and end of the block of data, wherein the public block of data comprises:

(i) a vehicle identification sub-block hierarchically nested in the public block of data and comprising a plurality of data items wherein the data items are selected from the group consisting of manufacturer, model, model year and style of the vehicle,

(ii) a vehicle detail sub-block hierarchically nested in the public block of data, wherein the vehicle detail sub-block comprises:

(1) a standard feature sub-block hierarchically nested in the vehicle detail sub-block and comprising a plurality of standard feature categories, wherein each standard feature category is hierarchically nested in the standard feature sub-block and comprises a plurality of data items relating to standard equipment available on a vehicle, and

(2) an optional feature sub-block hierarchically nested in the vehicle detail sub-block and comprising a plurality of option categories, wherein each option category is hierarchically nested in the option sub-block and comprises a plurality of data items relating to a particular category of optional equipment desired on a particular vehicle; and

(b) a private block of data comprising a plurality of data items relating to the customer who is ordering the vehicle including at least a ranking of product attributes;

wherein one of the computing systems receives the data structure and operates on at least the vehicle detail sub-block to select a subset of a target group of sellers by comparing at least features of the vehicle in a request for quote (RFQ) with products of at least one seller from the target group of sellers.

2. The vehicle description language of claim 1 wherein each sub-block contains a starting delimiter and an ending delimiter, wherein the starting delimiter identifies the block or sub-block within which the sub-block is nested.

3. The vehicle description language of claim 1 wherein each category consists essentially of a starting delimiter and an ending delimiter identifying the sub-block within which the category is nested.

4. The vehicle description language of claim 1 wherein each data item consists essentially of a starting delimiter and an ending delimiters identifying the block, sub-block or category within which the data item is nested.

5. The vehicle description language of claim 1 wherein the standard categories are selected from the group consisting of comprise exterior, interior, mechanical, safety, fuel mileage, rating, and combinations thereof.

6. The vehicle description language of claim 1 wherein the option categories are selected from the group consisting of emissions, engine, transmission, preferred equipment groups, appearance package, tires, seat type, seat trim, paint additional options, and combinations thereof.

7. The vehicle description language of claim 1 wherein the public block further comprises a color sub-block nested within the public block, wherein the color sub-block having nested therein categories comprises color selections and color combinations.

8. The vehicle description language of claim 1 wherein the data items in the private block comprise the customer's name, address and phone number.

9. The vehicle description language of claim 1 wherein the language is implemented with Extensible Markup Language (XML).

10. The vehicle description language of claim 1 , wherein the vehicle description language is employed in communications between at least two communicatively coupled computing systems.

11. A storage medium comprising content which, when executed, causes a computing system to process a vehicle descriptor language (VDL) datagram including information to describe an automobile for transmission stored in a memory, the VDL datagram comprising:

(a) a public block of data, having starting and ending delimiters that identify the beginning and end of the block of data, wherein the public block of data comprises:

(i) a vehicle identification sub-block hierarchically nested in the public block of data and comprising a plurality of data items wherein the data items are selected from the group consisting of manufacturer, mode, model year and style of the vehicle,

(ii) a vehicle detail sub-block hierarchically nested in the public block of data, wherein the vehicle detail sub-block comprises:

(1) a standard feature sub-block hierarchically nested in the vehicle detail sub-block and comprising a plurality of standard feature categories, wherein each standard feature category is hierarchically nested in the standard feature sub-block and comprises a plurality of data items relating to standard equipment available on a vehicle, and

(2) an optional feature sub-block hierarchically nested in the vehicle detail sub-block and comprising a plurality of option categories, wherein each option category is hierarchically nested in the option sub-block and comprises a plurality of data items relating to a particular category of optional equipment desired on a particular vehicle; and

(b) a private block of data comprising a plurality of data items relating to the customer who is ordering the vehicle including at least a ranking of product attributes;

wherein computing system operates on at least the vehicle detail sub-block to select a subset of a target group of sellers by comparing at least features of the vehicle in a request for quote (RFQ) with products of at least one seller from the target group of sellers.

12. A storage medium according to claim 11 , wherein the communicatively coupled memory is located within a remote computing appliance, coupled to the computing system through transmission means.

Assignments (19)
RELEASE OF SECURITY INTEREST Recorded May 30, 2019
From: ROYAL BANK OF CANADA, AS COLLATERAL AGENT
To: AUTODATA, INC.; AUTODATA SOLUTIONS, INC.
Reel/Frame 049324/0982 →
RELEASE OF SECURITY INTEREST Recorded May 30, 2019
From: ROYAL BANK OF CANADA, AS COLLATERAL AGENT
To: AUTODATA, INC.; AUTODATA SOLUTIONS, INC.
Reel/Frame 049324/0973 →
SECURITY INTEREST Recorded Dec 14, 2017
From: AUTODATA, INC.; AUTODATA SOLUTIONS, INC.
To: ROYAL BANK OF CANADA, AS COLLATERAL AGENT
Reel/Frame 044397/0347 →
SECURITY INTEREST Recorded Dec 14, 2017
From: AUTODATA, INC.; AUTODATA SOLUTIONS, INC.
To: ROYAL BANK OF CANADA, AS COLLATERAL AGENT
Reel/Frame 044397/0256 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 24, 2015
From: CHROME DATA SOLUTIONS, LP
To: AUTODATA, INC.
Reel/Frame 037134/0507 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 23, 2015
From: CHROME SYSTEMS, INC.
To: CHROME DATA SOLUTIONS, LP
Reel/Frame 036865/0841 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (016249/0980) Recorded Oct 5, 2015
From: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
To: CHROME SYSTEMS, INC.
Reel/Frame 036754/0980 →
CHANGE OF NAME Recorded Jun 16, 2015
From: BRIGHT ACQUISITION CORPORATION
To: CHROME SYSTEMS, INC.
Reel/Frame 035923/0481 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 16, 2015
From: CSC OREGON HOLDINGS, INC.
To: BRIGHT ACQUISITION CORPORATION
Reel/Frame 035844/0994 →
MERGER Recorded Jun 16, 2015
From: CHROME DATA CORPORATION
To: CHROME SYSTEMS CORPORATION
Reel/Frame 035919/0535 →
CHANGE OF NAME Recorded Jun 16, 2015
From: CHROME SYSTEMS CORPORATION
To: CSC OREGON HOLDINGS, INC.
Reel/Frame 035920/0102 →
RELEASE OF PATENT SECURITY INTEREST RECORDED AT REEL/FRAME 026278/0761 Recorded Jun 2, 2014
From: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
To: DEALERTRACK, INC.; DEALERTRACK AFTERMARKET SERVICES, INC; DEALERTRACK DATA SERVICES, INC.; CHROME SYSTEMS, INC.; FDI COMPUTER CONSULTING, INC.
Reel/Frame 033076/0775 →
SECURITY AGREEMENT Recorded May 16, 2011
From: DEALERTRACK, INC.; DEALERTRACK AFTERMARKET SERVICES, INC.; DEALERTRACK DATA SERVICES, INC.; CHROME SYSTEMS, INC.; FDI COMPUTER CONSULTING, INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 026278/0761 →
SECURITY AGREEMENT Recorded Jul 12, 2005
From: CHROME SYSTEMS, INC.
To: JPMORGAN CHASE BANK, N.A. AS ADMINISTRATIVE AGENT
Reel/Frame 016249/0980 →
RELEASE OF SECURITY INTEREST Recorded Apr 21, 2005
From: SILICON VALLEY BANK
To: CHROME SYSTEMS CORPORATION
Reel/Frame 016470/0735 →
PLEASE CORRECT BRIEF ON DOCUMENT #102447154A TO READ SECURITY AGREEMENT AS STATED ON ORIGINAL COVERSHEET AND NOT ASSIGNMENT Recorded Apr 13, 2004
From: CHROME SYSTEMS CORP
To: SILICON VALLEY BANK
Reel/Frame 015203/0695 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 12, 2003
From: CHROME SYSTEMS CORP
To: SILICON VALLEY BANK
Reel/Frame 014052/0987 →
SECURITY INTEREST Recorded Feb 7, 2000
From: CHROME DATA CORPORATION
To: LAWRENCE WASSERMAN AS AGENT FOR LENDERS
Reel/Frame 010606/0653 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 5, 1999
From: NABORS, FORREST; HUG, CELAS; GARRIGUS, TOM; ZHANG, CHARLIE
To: CHROME DATA CORPORATION
Reel/Frame 010283/0397 →