Vehicle locating method and system
Claim Score by NHIP
Abstract
A method and service that uses radio frequency identification (RFID) tags to track and monitor vehicles that are being service is presented. Each vehicle has an attached RFID tag that contains detailed information about that vehicle. A customer can log onto a website hosted by a service department. The website is populated with real-time data showing the current service area in which the vehicle is located.

Term
Term ended
Projected expiry passed 25 March 2025, 1.5 years ago.
- Priority
- Filed
- Published
- Projected expiry
- Today
18 claims: 3 independent, 15 dependent
- 1A method for tracking a progress of a product that is receiving scheduled product maintenance service, the method comprising:attaching a radio frequency identifier (RFID) to a product;using the RFID to locate the product within a service area;providing a real-time location for the product within the service area to a website, and accessing the website to determine a progress status of scheduled product maintenance service being performed on the product.
- 9Broadest claimClaim Score 83, broad(NHIP)A method for tracking a progress of a product that is being repaired, the method comprising:attaching a radio frequency identifier (RFID) to a product;using the RFID to locate the product within a repair area;providing a real-time location for the product within the repair area to a website;and accessing the website to determine a progress status of repair work that is being performed on the product.
- 12A computer-readable medium encoded with a computer program for tracking a progress of a product that is receiving scheduled product maintenance service, the computer program comprising computer executable instructions configured for:receiving product identification from a radio frequency identifier (RFID) that is attached to a product;using the RFID to locate the product within a service area;providing a real-time location for the product within the service area to a website;and accessing the website to determine a progress status of scheduled product maintenance service being performed on the product.
Independent claims3
53 paragraphs in 5 sections, as filed
RELATED PATENT APPLICATIONS
0001The present application is a continuation of U.S. patent application Ser. No. 11/062,685 (Atty. Docket No. END920040196US1), filed on Feb. 22, 2005, and entitled, “Product Locating Method and System,” which is incorporated herein by reference.
BACKGROUND OF THE INVENTION
00021. Technical Field
0003The present invention relates in general to the field of computers, and in particular to computer systems that use radio frequency identification (RFID) technology. Still more particularly, the present invention relates to a method and service for physically locating a product, such as a vehicle, that is being serviced.
00042. Description of the Related Art
0005A customer's experience in purchasing a major product, including a vehicle such as a car, truck or boat, is typically a difficult ordeal. In a usual scenario, the customer tells a sales representative generally what he is looking for, and the sales representative then physically looks over inventory on the lot to find a likely match. The sales representative locates keys for a selected vehicle, often after first speaking with a sales manager, and then takes the customer onto the lot to look at the selected vehicle. The customer often decides that the selected vehicle does not meet his needs/desires, and the cycle starts over again with another vehicle.
0006Likewise, after the sale is it difficult for the customer to check on a status of the vehicle when being serviced (maintenance, repairs, etc.). The customer must contact his service representative, who is often on another call or otherwise unavailable, who must then track down the vehicle to determine the completion status of the service work being performed.
SUMMARY OF THE INVENTION
0007What is needed, therefore, is a method and system that locates and tracks a product that is being serviced.
0008Thus, the present invention is directed to a method and service that uses radio frequency identification (RFID) tags to track and monitor vehicles that are being serviced. Each vehicle has an attached RFID tag that contains detailed information about that vehicle. A customer can log onto a website hosted by a service department. The website is populated with real-time data showing the current service area in which the vehicle is located.
0009In one embodiment, the service department has a specific service procedure that describes the order in which service steps will be performed on each vehicle, and in which physical areas of the service shop, thus allowing the customer to know how many more stations are needed to be visited by that vehicle before the service is completed.
0010The above, as well as additional purposes, features, and advantages of the present invention will become apparent in the following detailed written description.
BRIEF DESCRIPTION OF THE DRAWINGS
0011The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, however, as well as a preferred mode of use, further purposes and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, where:
0012<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram of an exemplary computer system that may be used by a wireless tablet computer and by a wireless radio frequency identification (RFID) controller/server according to the present invention;
0013<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram of a inventory lot having RFID interrogators for identifying and locating vehicles that match the requirements of a customer;
0014<figref idref="DRAWINGS">FIGS. 3</figref><i>a</i>-<i>c </i>show sequential graphical user interfaces (GUIs), displayed on the wireless tablet computer, that describe choices and results based on the customer's requirements;
0015<figref idref="DRAWINGS">FIGS. 3</figref><i>d</i>-<i>e </i>shows GUIs offering an option to special order an unavailable vehicle using the wireless tablet computer;
0016<figref idref="DRAWINGS">FIG. 4</figref><i>a </i>illustrates a transport vehicle having an ability to provide real time data regarding a location of a specific vehicle in transit;
0017<figref idref="DRAWINGS">FIG. 4</figref><i>b </i>is a GUI on a computer screen showing a map and location of the transport vehicle in real time;
0018<figref idref="DRAWINGS">FIG. 5</figref><i>a </i>is a map of a service department showing a routing order for a vehicle being serviced;
0019<figref idref="DRAWINGS">FIG. 5</figref><i>b </i>depicts a block diagram of a network that allows a customer to remotely access a website showing a real time location of the vehicle being serviced;
0020<figref idref="DRAWINGS">FIG. 5</figref><i>c </i>is a GUI showing the status of the vehicle being serviced; and
0021<figref idref="DRAWINGS">FIG. 6</figref> is a flow chart of steps taken in a preferred embodiment of the present invention for locating and tracking a vehicle.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
0022With reference now to the figures, and in particular to <figref idref="DRAWINGS">FIG. 1</figref>, there is depicted a block diagram of an exemplary data processing system <b>100</b> in which a preferred embodiment of the present invention may be implemented. Specifically, data processing system <b>100</b> describes in general terms hardware that may be used by a wireless radio frequency identification (RFID) controller/server <b>208</b> and by a wireless tablet computer <b>210</b> shown in <figref idref="DRAWINGS">FIG. 2</figref>.
0023Data processing system <b>100</b> includes a central processing unit (CPU) <b>102</b>, which is connected to a system bus <b>108</b>. In the exemplary embodiment, data processing system <b>100</b> includes a graphics adapter <b>104</b>, which is also connected to system bus <b>108</b>, for providing user interface information to a display <b>106</b>.
0024Also connected to system bus <b>108</b> are a system memory <b>110</b> and an input/output (I/O) bus bridge <b>112</b>. I/O bus bridge <b>112</b> couples an I/O bus <b>114</b> to system bus <b>108</b>, relaying and/or transforming data transactions from one bus to the other. Peripheral devices such as nonvolatile storage <b>116</b>, which may be a hard disk drive, optical drive, or similar mass storage device(s). Also attached to I/O bus <b>114</b> is an input device <b>118</b>, which may include a conventional mouse, a trackball, or the like, as well as a keyboard or similar device.
0025Also coupled to I/<b>0</b> bus <b>114</b> is a wireless interface <b>120</b>, which provides wireless communication with wireless devices, including radio frequency identification (RFID) tags (such as RFID tags <b>204</b> shown in <figref idref="DRAWINGS">FIG. 2</figref>).
0026Also coupled to I/O bus <b>114</b> is a network interface <b>122</b>, which provides network communication via a network <b>124</b> to remote computing systems. Coupled to network <b>124</b> is an inventory server <b>126</b>, which contains a database of inventory that is available on a local lot, a remote lot, or is in transit, as well as products that can be ordered from the manufacturer.
0027The exemplary embodiment shown in <figref idref="DRAWINGS">FIG. 1</figref> is provided solely for the purposes of explaining the invention and those skilled in the art will recognize that numerous variations are possible, both in form and function. For instance, data processing system <b>100</b> might also include a sound card and audio speakers, and numerous other optional components. All such variations are believed to be within the spirit and scope of the present invention.
0028With reference now to <figref idref="DRAWINGS">FIG. 2</figref>, there is depicted an inventory lot <b>200</b> in which the present invention may be implemented. As discussed below, inventory lot <b>200</b> may be a local lot, or it may be a remote lot. Located on inventory lot <b>200</b> are vehicles <b>202</b>. Attached to each vehicle <b>202</b> is a radio frequency identification (RFID) tag <b>204</b>. Each RFID tag <b>204</b> may be attached to a vehicle <b>202</b> by either a manufacturer of the vehicle <b>202</b>, or it may be attached “after market” by a sales or service enterprise.
0029Each RFID tag <b>204</b> contains information specific to the vehicle <b>202</b> to which that RFID tag <b>204</b> is attached. This information may include, but is not limited to, the vehicle identification number (VIN), make, model, features, color, manufacturer's suggested retail price (MSRP), dealer's cost (before and after dealer incentives), availability (how many other similar vehicles are in the dealer's inventory), staleness (how long the vehicle has been sitting on the dealer's lot), new, demonstrator or used status, and available financing (including special interest rates offered by the manufacturer) of the vehicle <b>202</b>.
0030Each RFID tag <b>204</b> (also known as an RFID transponder) is interrogated by one or more RFID interrogators <b>206</b> (also known as an RFID reader). Each RFID tag <b>204</b> includes a radio frequency integrated circuit (RFIC) and an antenna (not shown, but known and understood to those skilled in the art). Each RFID interrogator <b>206</b> includes an antenna and a transceiver, which includes a transmitter and a receiver (not shown, but known and understood to those skilled in the art).
0031Wirelessly coupled to each RFID interrogator <b>206</b> is a wireless RFID controller/server <b>208</b>, which includes hardware and software for interrogating and decoding information from the RFID interrogators <b>206</b>. Alternatively, the structure and/or function of the RFID interrogators <b>206</b> and the wireless RFID controller/server <b>208</b> may be integrated into a single package.
0032Communication between the RFID tags <b>204</b> and the RFID interrogators <b>206</b> may be passive, semi-passive, or active. In the passive mode, the RFID interrogators <b>206</b> send an interrogation radio frequency signal of appropriate frequency and strength to provide power to the RFID tags <b>204</b>. In the semi-passive and active modes, power is supplied to the RFID tags <b>204</b> by an on-board battery. In the semi-passive mode, the RFID tag <b>204</b> either acts in response to an interrogation from an RFID interrogator <b>206</b>, or is on a timer and only periodically sends out information to the RFID interrogators <b>206</b>. In the active mode, communication can be initiated by the RFID tag <b>204</b>.
0033Each RFID interrogator <b>206</b> is capable of determining a distance from that RFID interrogator <b>206</b> and a specific RFID tag <b>204</b>, using techniques known to those skilled in the art, including but not limited to Doppler shifting (change in frequency in an electromagnetic signal being electronically “bounced” off an RFID tag <b>204</b>), and timing delta (measurement of the amount of time required for an RFID tag <b>204</b> to respond to an RFID interrogation from the RFID interrogator <b>206</b>. By taking a distance measurement from multiple RFID interrogators <b>206</b>, then the exact coordinate position of a particular RFID tag <b>204</b> (and its attached vehicle <b>202</b>) can be determined by known methods of “triangulation.” This coordinate location is then used to identify, using a look-up table in a database, the specific row and/or space number in which the vehicle is parked, in order to help the sales representative and customer find the vehicle. By this process of triangulation, for example, the location of vehicle <b>202</b>-<i>a </i>may be determined to be on Row A, Space <b>2</b>.
0034A wireless RFID controller/server <b>208</b> contains a database of vehicles stored on a local inventory lot <b>200</b>, as well as other vehicles available on other lots or in transit. Information stored in each RFID tag <b>204</b> can be updated by the wireless RFID controller/server <b>208</b>, and vice versa. Wireless RFID controller/server <b>208</b> is able to wirelessly communicate with a wireless tablet computer <b>210</b>, as well as a network <b>124</b> (either wirelessly or via a wired connection such as an Ethernet). Wireless RFID controller/server <b>208</b> and wireless tablet computer <b>210</b> can each use the hardware configuration of data processing system <b>100</b> shown in <figref idref="DRAWINGS">FIG. 1</figref>.
0035Wireless table computer <b>210</b>, which alternatively may be any data processing system, either wireless or wired, is preferably available to a sales representative for identifying and locating a vehicle <b>202</b> as described in detail below. Note that vehicle <b>202</b> is defined as any vehicle, including those for land, air or sea travel, such as cars, trucks, boats, aircraft, etc.
0036With reference now to <figref idref="DRAWINGS">FIG. 3</figref><i>a</i>, there is depicted a graphical user interface (GUI) <b>300</b><i>a </i>displayed on a display (such as display <b>106</b> shown in <figref idref="DRAWINGS">FIG. 1</figref>) on a computer (such as wireless tablet computer <b>210</b> shown in <figref idref="DRAWINGS">FIG. 2</figref>). GUI <b>300</b><i>a </i>includes drop down active windows <b>302</b><i>a</i>, which may be actively selected using a stylus pen, cursor controller (mouse), etc. Shown for exemplary purposes, GUI <b>300</b><i>a </i>shows three choices for a body style of a vehicle, including “Sedan,” “Coupe,” or “SUW.” Similarly, three choices of price ranges are given.
0037In a preferred embodiment of the present invention, a sales representative at a car dealership meets with a potential customer. As the customer tells the sales representative what characteristics are important in the type of vehicle he is interested in buying, the sales representative selects the appropriate choice. For example, assume that the customer wants a coupe that costs less than $15,000. The sale representative selects the appropriate active windows <b>302</b><i>a</i>, which causes the wireless RFID controller/server <b>208</b> shown in <figref idref="DRAWINGS">FIG. 2</figref> to search a database for available vehicles (preferably on a local vehicle lot) that meet the selected criteria.
0038Upon locating vehicles, which are preferably presently located in a local inventory lot, that match the needs of the customer, RFID controller/server <b>208</b> then sends a new page shown in <figref idref="DRAWINGS">FIG. 3</figref><i>b </i>as GUI <b>300</b><i>b</i>. Drop down windows <b>302</b><i>b </i>show available appropriate vehicles. Assume that the customer selects a Blue “Model B” vehicle. After the sales representative activates the appropriate active windows <b>302</b><i>b</i>, wireless RFID controller/server <b>208</b> searches its database, and/or interrogates, via RFID interrogators <b>206</b>, the RFID tags <b>204</b> on the vehicles <b>202</b> shown in <figref idref="DRAWINGS">FIG. 2</figref>. Wireless RFID controller/server <b>208</b> then sends a new page shown in <figref idref="DRAWINGS">FIG. 3</figref><i>c </i>as GUI <b>300</b><i>c</i>, showing the location (Row B, space <b>3</b>) and price ($27,589) of the selected vehicle. Note also that GUI <b>300</b><i>c </i>includes locator option buttons <b>304</b> that, if selected, will cause wireless RFID controller/server <b>208</b> to remotely turn on the horn and/or lights of the selected vehicle (using a remote horn/light activation feature on the vehicle <b>202</b>).
0039With reference now to <figref idref="DRAWINGS">FIG. 3</figref><i>d</i>, a GUI <b>300</b><i>d </i>is shown offering the salesman the option of ordering the desired vehicle from a computer, such as but not limited to the wireless tablet computer <b>210</b>. Option buttons <b>306</b>, if clicked, will result in an automatic ordering of the “Blue Model B” via the network <b>124</b> shown in <figref idref="DRAWINGS">FIG. 2</figref>. The inventory server <b>126</b> shown in <figref idref="DRAWINGS">FIG. 1</figref> can access its databank, determine that the Blue Model B can still be ordered from the manufacturer at the suggested MSRP. If the “Yes” button is selected, then a subsequent GUI <b>300</b><i>e</i>, as shown in <figref idref="DRAWINGS">FIG. 3</figref><i>e</i>, will appear, showing the estimated arrival date of the ordered vehicle. Note also that the Wireless RFID Controller/Server <b>208</b> knows which salesman is using the wireless tablet computer <b>210</b>, preferably by the salesman logging on with his UserID at the initiation of his use for the day. Thus, the special automatic ordering will be in the name of the salesman. Alternatively, the salesman can enter the name of the interested customer (entry window not shown).
0040Next, consider a scenario in which the desired vehicle is not on a local vehicle lot. If the desired vehicle, identified by the database stored in (or otherwise available to) wireless RFID controller/server <b>208</b>, is on a remote vehicle lot, then a similar process as described above can be utilized, thus providing locating information to the sales representative when calling or going to the remote vehicle lot. However, there may be times in which the desired vehicle is neither in a local or remote lot, or being test driven, but rather is in transit.
0041Referring then to <figref idref="DRAWINGS">FIG. 4</figref><i>a</i>, a transport vehicle <b>402</b> is shown. Loaded on transport vehicle <b>402</b> are multiple vehicles, each having a unique RFID tag <b>204</b> (including the shown RFID tags <b>204</b><i>a</i>-<i>c</i>) attached to the vehicle. Transport vehicle <b>402</b> has on-board an RFID reader <b>404</b>, which includes (not shown) a transceiver and decoder for reading information from RFID tags <b>204</b>. Preferably, RFID reader <b>404</b> has a range that is so limited as to allow RFID reader <b>404</b> to only read the RFID tags <b>204</b> being transported by transport vehicle <b>402</b>.
0042Transport vehicle <b>402</b> also has on-board a Global Positioning System (GPS) unit <b>406</b>, which is capable of identifying exactly where the transport vehicle <b>402</b> is located in real time. RFID reader <b>404</b> and GPS unit <b>406</b> are coupled to a telecommunications system <b>408</b>, having an antenna <b>410</b>, which allows telecommunication between transport vehicle <b>402</b> and, preferably, wireless RFID controller/server <b>208</b>, either directly or via network <b>124</b>, shown in <figref idref="DRAWINGS">FIG. 2</figref>.
0043Telecommunication system <b>408</b> includes hardware and software that combines information from RFID reader <b>404</b> and GPS unit <b>406</b> into a real-time packet of data that describes exactly where a vehicle in transit is located. For example, logic in telecommunication system <b>408</b> may combine data from RFID tag <b>204</b><i>a </i>with real-time data from GPS unit <b>406</b> to describe the fact that vehicle <b>202</b><i>a </i>is currently at a real-time truck location <b>414</b>, as shown in a GUI <b>412</b> in <figref idref="DRAWINGS">FIG. 4</figref><i>b. </i>
0044GUI <b>412</b>, which may be displayed on wireless tablet computer <b>210</b> shown in <figref idref="DRAWINGS">FIG. 2</figref>, or on any other computer (preferably) at a local dealership, shows a map that includes the real-time truck location <b>414</b> of transport vehicle <b>402</b>. An icon <b>416</b> shows a direction and location that transport vehicle <b>402</b> is traveling. Optionally, icon <b>416</b> can be an active field that, when clicked, displays information on some or all of the vehicles <b>202</b> being transported on transport vehicle <b>402</b>, according to information from their attached RFID tags <b>204</b>.
0045Referring still to <figref idref="DRAWINGS">FIG. 4</figref><i>b</i>, assume that a particular vehicle <b>202</b> is destined for original destination <b>418</b>, which may be another dealership, a remote vehicle lot, etc. The map shown in GUI <b>412</b> shows that a selected vehicle <b>202</b>, which has not been pre-sold, could be easily re-routed to a new desired destination <b>420</b> (such as a dealer's local lot). This re-routing can be accomplished by manually calling the driver of the transport vehicle <b>402</b> (via radio, cell phone, PDA, et al.), or by generating a computer signal to an on-board computer (not shown) on the transport vehicle <b>402</b> instructing the driver to divert to the new desired destination <b>420</b>.
0046Besides needing to locate a vehicle for sale, it is also desirable to track vehicles that are in the process of being serviced. With reference now to <figref idref="DRAWINGS">FIG. 5</figref><i>a</i>, a service department map <b>502</b> is shown. Within the service department are a tune-up area <b>504</b>, a lube area <b>506</b>, a wash rack <b>508</b>, and a parking lot <b>510</b>, all of which can be monitored from a service office <b>512</b> as well as remotely, as described below.
0047Assume for exemplary purposes that a specific vehicle is scheduled to sequentially have work done in the tune-up area <b>504</b>, lube area <b>506</b> and wash rack <b>508</b>, and then, upon completion of the service work, is to be parked in the parking lot <b>510</b>, as shown by the flow arrows. Also assume that this specific vehicle (not shown) has an attached RFID tag (as described above), and that tune-up area <b>504</b>, lube area <b>506</b>, wash rack <b>508</b>, and parking lot <b>510</b> all have adequate RFID interrogators (also described above) to determine which of these areas presently has the vehicle. This determination may be made by the triangulation process described above, or may be through the use of low-power RFID interrogators that, because of their low power, are only able to interrogate RFIDs in their area.
0048As shown in <figref idref="DRAWINGS">FIG. 5</figref><i>b</i>, a customer's browser <b>514</b> can access a service department website <b>516</b> via a network, such as an Internet <b>518</b>. After logging into the base website, and inputting the vehicle's service number, license plate, or other identifier into an active field, a webpage <b>520</b> is sent to the customer's browser <b>514</b>. An exemplary webpage <b>520</b>, as shown in <figref idref="DRAWINGS">FIG. 5</figref><i>c</i>, shows the current status of the service work by showing where the vehicle is currently located, as well as when all service should be completed (as calculated by its location). Thus, the customer can check the status of his vehicle's service on-line without involving a service representative. Alternatively, an electronic message can be sent to the customer, either manually or automatically when the vehicle is in any selected area, informing the customer of the status of his service work. The message can be sent as an e-mail, a cell phone text message, a page signal, or any other electronic message media that is desired.
0049With reference now to <figref idref="DRAWINGS">FIG. 6</figref>, a flow chart of steps taken in a preferred embodiment to locate a vehicle for purchase is depicted. After initiator block <b>600</b>, a sales representative enters the customer's desired vehicle features into his wireless tablet computer (block <b>602</b>), as described in detail above. Information from all RFID tags on vehicles on the lot are read (block <b>604</b>), and a desired vehicle is located based on a match of the customer's desired vehicle features with information from one or more RFIDs (block <b>606</b>). If the desired vehicle is on the local inventory lot (query block <b>608</b>), then the sales representative is so notified of the vehicle's location on his tablet computer (block <b>610</b>), and the vehicle's horn/lights are optionally flashed on to aid in locating the vehicle. Preferably, the location of the vehicle is described as being on a named row and/or space.
0050If the desired vehicle is not on the local lot, then its location is determined (block <b>612</b>) as either being in another lot or else as being in transit (query block <b>614</b>). If it is on another remote lot, then that remote lot has an infrastructure as described above for the local lot, and the specific location of the vehicle is sent to the sale representative. If the desired vehicle is in transit, then the sales representative is so notified and the vehicle is optionally re-routed to the local inventory lot (block <b>616</b>), where the process end (terminator block <b>618</b>).
0051The present invention thus provides an effective way for an RFID tag-equipped vehicle to be identified, located, and tracked for sales and service purposes. The invention reduces customer frustration, and also improves inventory control.
0052It should be understood that at least some aspects of the present invention may alternatively be implemented in a program product. Programs defining functions on the present invention can be delivered to a data storage system or a computer system via a variety of signal-bearing media, which include, without limitation, non-writable storage media (e.g., CD-ROM), writable storage media (e.g., a floppy diskette, hard disk drive, read/write CD ROM, optical media), and communication media, such as computer and telephone networks including Ethernet. It should be understood, therefore in such signal-bearing media when carrying or encoding computer readable instructions that direct method functions in the present invention, represent alternative embodiments of the present invention. Further, it is understood that the present invention may be implemented by a system having means in the form of hardware, software, or a combination of software and hardware as described herein or their equivalent.
0053While the invention has been particularly shown and described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention. For example, while the present invention is described for locating and tracking a vehicle such as an automobile, the present invention is also useful in tracking any product capable of being attached to an RFID tag or any similar wireless device.
Contents5
13 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US9489776B2 | Cited by | United States of America | Applicant |
| US2011148578A1 | Cited by | United States of America | Pre-grant |
| US2009204325A1 | Cited by | United States of America | Pre-grant |
| CN107085903A | Cited by | China | Search report |
| US2012118946A1 | Cited by | United States of America | Pre-grant |
| US9652921B2 | Cited by | United States of America | Applicant |
| US9842455B2 | Cited by | United States of America | Applicant |
| US2009033466A1 | Cited by | United States of America | Pre-grant |
| US2008088473A1 | Cited by | United States of America | Pre-grant |
| US10573953B2 | Cited by | United States of America | Applicant |
| US10861278B2 | Cited by | United States of America | Applicant |
| US10192388B2 | Cited by | United States of America | Applicant |
| CN107077790A | Cited by | China | Search report |
| US8604912B2 | Cited by | United States of America | Search report |
| US9934645B2 | Cited by | United States of America | Applicant |
| CN103679238A | Cited by | China | Search report |
| CN103337192A | Cited by | China | Search report |
| CN105545053A | Cited by | China | Search report |
| US2010148937A1 | Cited by | United States of America | Pre-grant |
| USD863076S | Cited by | United States of America | Applicant |
| US8447463B1 | Cited by | United States of America | Applicant |
| US2012092189A1 | Cited by | United States of America | Pre-grant |
| USD863075S | Cited by | United States of America | Applicant |
| US10068411B2 | Cited by | United States of America | Applicant |
| US8184019B2 | Cited by | United States of America | Applicant |
| US10998612B2 | Cited by | United States of America | Applicant |
| USD863987S | Cited by | United States of America | Applicant |
| USRE48566E | Cited by | United States of America | Applicant |
| US8754783B2 | Cited by | United States of America | Search report |
| US9454745B2 | Cited by | United States of America | Applicant |
| USD863074S | Cited by | United States of America | Applicant |
| USD863988S | Cited by | United States of America | Applicant |
| US10141629B2 | Cited by | United States of America | Applicant |
| US9355064B2 | Cited by | United States of America | Applicant |
| DE102015118598A1 | Cited by | Germany | Search report |
| US9000949B2 | Cited by | United States of America | Search report |
| US10839687B2 | Cited by | United States of America | Applicant |
| US2011063133A1 | Cited by | United States of America | Pre-grant |
| US2010060452A1 | Cited by | United States of America | Pre-grant |
| US8733628B2 | Cited by | United States of America | Search report |
| US7957900B2 | Cited by | United States of America | Search report |
| US10424147B2 | Cited by | United States of America | Applicant |
| US2009267732A1 | Cited by | United States of America | Pre-grant |
| US9911151B1 | Cited by | United States of America | Applicant |
| US8471706B2 | Cited by | United States of America | Applicant |
| US2003111525A1 | Cites | United States of America | Pre-grant |
| US2005073435A1 | Cites | United States of America | Pre-grant |
| US2006229928A1 | Cites | United States of America | Pre-grant |
| US2008027604A1 | Cites | United States of America | Pre-grant |
| US6339736B1 | Cites | United States of America | Pre-grant |
| US7356393B1 | Cites | United States of America | Pre-grant |
4 members in 1 office
Priority claims5
| Document | Office | Kind | Date |
|---|---|---|---|
| 6268505 | United States of America | A | |
| 68932807 | United States of America | A | |
| 11062685 | – | – | – |
| US20050062685 | – | – | – |
| US20070689328 | – | – | – |
Members4
| Document | Office | Kind | |
|---|---|---|---|
| US2006187043A1 | United States of America | A1 | |
| US2007171069A1 | United States of America | A1 | |
| US7323989B2 | United States of America | B2 | |
| US7511619B2 | United States of America | B2 |
27 transactions on the USPTO file
Allowed after 1 non-final rejection.
- Non-final rejections
- 1
- Final rejections
- 0
- RCEs
- 0
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Correspondence Address ChangeC.AD | C.AD | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Mail Examiner's AmendmentMEX.A | MEX.A | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Examiner's Amendment CommunicationEX.A | EX.A | |
| Examiner Interview Summary Record (PTOL - 413)EXIN | EXIN | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Sent to Classification ContractorPGPC | PGPC | |
| Application Is Now CompleteCOMP | COMP | |
| Cleared by L&R (LARS)L128 | L128 | |
| Referred to Level 2 (LARS) by OIPE CSRL198 | L198 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
10 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Fee payment procedure11.5 YR SURCHARGE- LATE PMT W/IN 6 MO, LARGE ENTITY (ORIGINAL EVENT CODE: M1556); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Maintenance fee paymentMAFP | MAFP | |
| Fee paymentFPAY | FPAY | |
| Fee paymentFPAY | FPAY | |
| Surcharge for late paymentSULP | SULP | |
| Maintenance fee reminder mailedREMI | REMI | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP |
Numbers
- Publication
- 20070171069
- Publication, DOCDB
- 2007171069
- Publication, EPODOC
- US2007171069
- Application
- 11689328
- Application, DOCDB
- 68932807
- Application, EPODOC
- US20070689328
Titles
- English
- VEHICLE LOCATING METHOD AND SYSTEM
Classification
- CPC, 1
- G06Q10/087
- IPC, 3
- G08B13 14
- G08G1 01
- G08G1 14
- USPC, 3
- 340572100
- 340932200
- 340933000