Assessment of electronic sensor data to remotely identify a motor vehicle and monitor driver behavior

Information

  • Patent Grant
  • 11004277
  • Patent Number
    11,004,277
  • Date Filed
    Thursday, July 7, 2016
    8 years ago
  • Date Issued
    Tuesday, May 11, 2021
    3 years ago
Abstract
A computing device is connected to a motor vehicle's diagnostic port or communication port to acquire vehicle sensor data, for example from various pressure, temperature, oxygen, fuel and other sensors typically installed on a motor vehicle for other reasons. Acquired sensor data is wirelessly transmitted to a remote server where the acquired sensor data can be compared to a database of stored sensor data to identify the motor vehicle. Additional functionality is described that leverages uploaded sensor data. Sensor data may be uploaded to the server in near-real time, and/or buffered locally and uploaded by periodic or episodic, push or pull communication protocols.
Description
COPYRIGHT NOTICE

©2012-2013 Airbiquity Inc. A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever. 37 CFR § 1.71(d).


TECHNICAL FIELD

This disclosure pertains to powered vehicles, and more specifically to motor vehicles, and concerns communications of data between a vehicle and a centralized server to enable various beneficial applications.


BACKGROUND OF THE INVENTION

The ubiquitous CAN bus (for controller area network) is a vehicle bus standard designed to allow microcontrollers and devices to communicate with each other within a vehicle without a host computer. CAN bus is one of five protocols used in the OBD-II vehicle diagnostics standard. The OBD-II standard has been mandatory for all cars and light trucks sold in the United States since 1996, and the EOBD standard has been mandatory for all petrol vehicles sold in the European Union since 2001 and all diesel vehicles since 2004. CAN is a multi-master broadcast serial bus standard for connecting electronic control units (ECUs).


Each node is able to send and receive messages, but not simultaneously. A message consists primarily of an ID (identifier), which represents the priority of the message, and up to eight data bytes. It is transmitted serially onto the bus. This signal pattern is encoded in non-return-to-zero (NRZ) and is sensed by all nodes. The devices that are connected by a CAN network are typically sensors, actuators, and other control devices. In general, these devices are not connected directly to the bus, but through a host processor and a CAN controller. In any event, the CAN networks are confined to the motor vehicle.


SUMMARY OF THE INVENTION

The following is a summary of the invention in order to provide a basic understanding of some aspects of the invention. This summary is not intended to identify key/critical elements of the invention or to delineate the scope of the invention. Its sole purpose is to present some concepts of the invention in a simplified form as a prelude to the more detailed description that is presented later.


In general, on-board electronic communications continue to evolve in motor vehicles, but they remain confined in the vehicle. One feature of the present disclosure extends aspects of the on-board networks, sensors and other nodes to a remote server location.


In another aspect of this disclosure, a remote server can acquire data from a motor vehicle, including on-board sensor data.


In still another aspect, sensor data can be used to remotely identify a motor vehicle at a remote server.


In still another aspect, sensor data can be used to remotely identify a current driver of a motor vehicle at a remote server.


Additional aspects and advantages of this invention will be apparent from the following detailed description of preferred embodiments, which proceeds with reference to the accompanying drawings.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a simplified block diagram illustrating selected components of one example of a fleet management monitoring system consistent with the present disclosure.



FIG. 2 illustrates a server-based process to collect electronic sensor data from a remote vehicle.





DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

A problem arises in that the data communications ports on some vehicles do not provide a Vehicle Identification Number (VIN), which is a unique identifier. Without the ability to uniquely identify a vehicle, a fleet management system is severely constrained. For example, it cannot implement an automated provision system to quickly provision the vehicle systems with calibration parameters. In some case, such parameters may be unique to the behavior of a vehicle. Downloaded parameters or other data may be used by on-board software. In some embodiments on-board software or systems may utilize driver behavior algorithms for monitoring driver behavior. Further, an automated system cannot collect data from vehicles without having to manually correlate the data to the fleet vehicles, if possible, by some other means. Various advantageous functions can be implemented from a remote server given a way to uniquely identify each vehicle.


In an embodiment, a computing device may be connected to a motor vehicle's diagnostic port or communication port to acquire vehicle sensor data, for example from various pressure, temperature, oxygen, fuel and other sensors typically installed on a motor vehicle for other reasons. The computing device may be a mobile device such as a smart phone. The device may be connected to a port, for example an OBD port. The device may be connected by cable or short-range wireless connection (e.g., a Bluetooth® connection) to an on-board network.


Acquired sensor data may be wirelessly transmitted via the smart phone to a remote server where the acquired sensor data can be stored and or compared to a database of stored sensor data to identify the motor vehicle and for other functions. Acquired sensor data may also be transmitted via an on-board or embedded NAD (network access device).


Sensor data may be uploaded to the server in near-real time, and/or buffered locally and uploaded by periodic or episodic, push or pull communication protocols. Acquired sensor data may be stored at a central server. Acquired data may be stored in a database coupled to a central server. It may be used to form stored baseline data. The determined vehicle ID can be used by a backend server system to compare the historical operation of the vehicle to determine if there are any anomalies associated with its behavior. In addition the vehicle ID can be used to determine if any anomalies may be caused by the driver operating the vehicle, as further explained below. Further, the vehicle ID may be used for provisioning data or software from the server to the vehicle, especially to adapt it to current conditions.


In FIG. 1, a simplified block diagram illustrates the main components of one example of a fleet management or driver behavior monitoring system. In this example, a motor vehicle's data communication port 100 or other interface is coupled, via a cable or wireless connection, to a computing and communications device, such as a user's “smart phone” 104. For example, a Bluetooth® connection may be used, or similar short-range wireless connection, between the portable device and the vehicle port/adapter, but this connection can be made via any means available.


In an embodiment, the smart phone 104 communicates via the cellular data communication network 110 (aka “mobile network”), and IP gateway where needed, to a remote server (“back end system”) 120 which receives and stores and maintains data of several types. One type may be historical data 122. Historical data 122 may include, but is not limited to, the following examples: (a) sensor data for vehicle identification; (b) historical driver and vehicle behavior data; (c) calibration parameters and other data for download to the vehicle and (d) geographic location data provided, for example, by an internal or external GPS sensor. In addition to historical data, the server system may include a provisioning manager 130 for provisioning the computing device in the vehicle. The computing device in the vehicle may comprise a portable device, as illustrated, or in another embodiment one or more processors (not shown) that are embedded in the vehicle for various purposes.


In some embodiments, stored baseline sensor data includes sensor data acquired from a corresponding motor vehicle during at least one known steady-state condition. To illustrate, a first steady state condition may be defined within a predetermined time window, for example 5 seconds, after startup of the vehicle engine from a cold start. This may be called a cold condition.


A second steady-state condition may be defined after expiration of at least a predetermined minimum time period of continuous operation of the vehicle engine. For example, this period may be on the order of 5 or 10 minutes. It may be called a “hot” or running condition. In some embodiments, the stored baseline sensor data includes sensor data acquired from a corresponding motor vehicle during the cold condition. In some embodiments, the stored baseline sensor data includes data acquired from a corresponding motor vehicle during the hot or running condition. An ensemble of multiple sensor readings, for example readings from three or four different sensors, may be stored at the server and used to identify a remote vehicle. In some embodiments, the sensor readings may be cold condition, hot condition, or a combination of the two types.


By way of illustration and not limitation, vehicle sensors used to provide data may include the following:

    • engine coolant temperature
    • engine air temperature
    • fuel rail pressure
    • engine oil temperature
    • absolute throttle position limit
    • engine RPM at idle
    • Lambda exhaust oxygen sensor voltage


So, for example, engine RPM at idle may be acquired, at cold condition, as well as the same metric at a hot condition. The same data (hot and cold) may be acquired for fuel rail pressure and engine oil temperature, for a total of nine measurements. Data sets of this type may be used to identify the vehicle. An elapsed time period may be used to delineate cold to hot. Or, a rate of change may be used to indicate a running (steady-state) condition. Other sensors may be used in addition, or in lieu of those mentioned. A greater number of sensors generally will better distinguish one vehicle from another. Comparison of acquired data to previously stored baseline data may be accomplished using known database query technologies. Fuzzy matching may be used.


In some implementations, said acquiring sensor data from the remote vehicle includes acquiring sensor data for at least three of the foregoing steady-state sensor output values; and wherein said comparing step includes comparing the at least three steady-state sensor output values to the corresponding stored baseline data.


Thus in one aspect of the present disclosure, a method of identifying a vehicle may comprise a combination of characterizing the sensor data values that are read from the vehicle data communication port at known steady state vehicle conditions, and characterizing certain sensor values as the state of the vehicle is changing in a previously characterized rate and direction of change. The accuracy of the vehicle sensor measurements preferably are on the order of <=+/−1 accuracy.


Other metrics may include dynamic measurement conditions. Examples of dynamic measurements may include, without limitation, the following:

    • Engine idle at startup mapped to previously recorded engine cold start temperatures.
    • Engine idle at specified hot engine temperatures
    • The duration of engine temperature change from cold start to hot temp relative to a previously recorded average engine load over the time it takes to change from cold temp to hot temp.
    • GPS location to differentiate between two vehicles with similar sensor data values.


In an embodiment, we propose to characterize a vehicle based in part on steady state sensor output values. This would involve the measurement of vehicle sensor data provided by the data communication port under steady state vehicle connections such as but not limited to the following:


Engine coolant temperature, typically measured in a range of −40° F. to 419° F. (−40° C. to 215° C.). This sensor typically has an accuracy of +/−5% which equates to a result in deviation from one sensor output to another of +22.95° F. (+5° C.) to −22.95° F. (−5° C.) relative to the actual temperature of the coolant. With this output deviation from sensor to sensor the output can be used along with other types sensor outputs to develop a “finger print” for the vehicle.


Engine air temperature is typically measured in a range of −40° F. to 419° F. (−40° C. to 215° C.). This sensor typically has a accuracy of +/−5% which equates to can result in a deviation from one sensor to another of +22.95° F. (+5° C.) to −22.95° F. (−5° C.) relative to the actual temperature of the engine intake air. With this output deviation from sensor to sensor the output can be used along with other types sensor outputs to develop a “finger print” for the vehicle.


Fuel Rail Pressure will vary greatly from one make and model vehicle to another. For same make and model vehicles there will be a deviation from one vehicle to another that is a function of the accuracy of the fuel pressure regulator and the fuel pressure sensor. Even if these two devices are 1% accurate the total accuracy will be +/−2%. This is a measurable sensor output that is unique to a specific vehicle.


Engine oil temperature will vary greatly from one make and model vehicle to another. For same make and model vehicles there will be a deviation from one vehicle to another that is a function oil viscosity, engine block mass and thermal dissipation, and oil temperature accuracy which typically is +/−5%. This is a measurable sensor output that is unique to a specific vehicle.


Absolute throttle position is measured in 0 to 100% maximum throttle opening. From same vehicle make and model or for different vehicle make and model the minimum value could be unique. This is due to the mechanical closed throttle limit which is often governed by an air idle set screw or throttle casting closed position stop.


Engine RPM: This value is usually within 1% of the actual the engine RPM, however the engine RPM is a factor of many vehicle specific variables which affect the engine RPM at any steady state condition. These vehicle specific variables include the temperature of the engine and air at steady state condition, upstream of the throttle air pressure drop due to air filter cleanliness. How well each engine cylinder is generating cylinder pressure during the fuel and air combustion process, and the closed loop engine idle RPM where a desired measured air fuel ratio has been obtained by the engine management system that is relative to stoichiometric air fuel ratio at the desired engine RPM for the fuel typed used. This desired engine RPM can be the product of the engine management system learned output that results in the best emission output of the engine at that steady state condition and it will vary from one vehicle to another.


Lambda sensor. For the specific fuel used in the vehicle the Lambda sensor voltage output range can vary from one sensor to another due to age of the sensor, sensor accuracy, sensor manufacturing techniques for oxygen reference cell. The number of active lambda sensors that can be measured can be used to determine difference for vehicle make and models that have engines with different number of cylinders or difference sophistication of the engine management system which is responsible for controlling engine output relative to engine emissions. In an embodiment, several of the foregoing metrics are used in combination to determine a unique identification or profile of a vehicle.


In another aspect, we characterize the vehicle's dynamic state change to determine a rate of change profile for sensor output values. For example:

    • 1. Engine idle RPM as the vehicle changes temp from cold start to a predefined hot operating temperature.
    • 2. Engine oil temperature change relative to engine coolant temperature change from a cold start engine temperature to a predefined hot engine temperature.


Some embodiments thus may be summarized as follows: A computer-implemented method of identifying a motor vehicle comprising: acquiring first sensor data from the vehicle during a first steady state operating condition of the vehicle; acquiring second sensor data from the vehicle during a second steady state operating condition of the same vehicle; wherein the first and second sensor data each include data acquired from no less than three sensors installed on board the vehicle, the first and second data being acquired from the same sensors at different times; and storing the acquired first and second sensor data so as to form baseline sensor data for use in subsequent identification of the vehicle.


A method consistent with the present disclosure may further include comparing the first and second sensor data to stored baseline sensor data; and forming an identifier of the vehicle based on the said comparing step.



FIG. 2 is a simplified flow diagram illustrating a server-based process 200 to collect electronic sensor data from a remote vehicle. In the figure, a wireless communication link 202 is formed between a central server, for example, a fleet management system, and a remote vehicle. The link may be over the wireless telecom network. The link may utilize in-band signaling to transmit data over a voice channel. The link may utilize a data service.


If sensor data is buffered at the vehicle and is ready, decision 204, it is uploaded, block 206. If it is not ready, the process may loop at 208. Uploaded data may undergo error correction in the process, and optionally it may be scrubbed to help ensure valid data, block 210.


After data is ready, a database coupled to the server, for example, a baseline database, may be queried to look for matching data, block 220. Matching baseline sensor data may be used to identify the vehicle. If a unique match is found, decision 222, the data may be added to a database, block 230. The process may loop via 240 in some cases to acquire additional data. If a unique match was not found initially at 222, an effort may be undertaken to disambiguate among plural vehicles reporting similar sensor values, for example, based on acquiring corresponding location data of each of the vehicles. Location data may be acquired from GPS receiver in the vehicle. A GPS receive may be coupled to an on-board network so that the location data is accessible. In the case of using a mobile device such as a smart phone for communication with the server, the smart phone embedded GPS receiver may be used to acquire location of a vehicle. If disambiguation does not succeed, decision block 232, additional sensor data may be requested, block 250, and the matching process repeated via loop 252.


Driver Behavior


Another feature of the present disclosure involves acquiring sensor data, which may be buffered, stored, or transmitted in near-real time, and analyzing that sensor data to infer characteristics of driver behavior. Data may be accumulated over time for a given driver to form a profile. Deviation from the profile may indicate driver impairment, due to medical or other factors. Profiles based on sensor data also may be used to infer the identity of a current driver of a vehicle.


Fuel Efficiency


Another feature of the present disclosure involves acquiring sensor data, and based on the stored data, calculating a mileage rate or fuel efficiency of the motor vehicle. The mileage rate refers to miles traveled per gallon of liquid fuel, or per kilowatt-hour of electrical energy for an electric vehicle. Using the techniques above, fuel efficiency may be determined for each vehicle, under various conditions. Deviation from the normal fuel efficiencies may indicate a maintenance issue that requires attention. If no maintenance issue exists then the difference in calculated average fuel efficiency can also be used to uniquely identify the vehicle if driver behavior can be ruled out as a reason for fuel efficiency variability.


In some cases, changes in vehicle performance as reflected in sensor data may be due to driver behavior rather than maintenance issues. Distinguishing between these two causes may be achieved by analysis of data acquired over time. Other case—very different vehicle causes very different readings, not the driver.


It will be obvious to those having skill in the art that many changes may be made to the details of the above-described embodiments without departing from the underlying principles of the invention. The scope of the present invention should, therefore, be determined only by the following claims.

Claims
  • 1. A system arranged to transform intrinsic data collected from a plurality of vehicles into a vehicle identification value that identifies a given vehicle of the plurality of vehicles, the system comprising: a processor to operate in a server remote from the plurality of motor vehicles, the processor configured to: for each vehicle of the plurality of vehicles, acquire digital values intrinsically used by a propulsion unit controller to control one or more operating parameters of one or more of an engine or a motor of the corresponding vehicle, wherein for each vehicle the corresponding digital values include first data acquired under a first operating condition of the corresponding vehicle and second data acquired under a second operation condition of the corresponding vehicle, wherein the first operating condition of the corresponding vehicle is a cold condition and the second operating condition of the corresponding vehicle is a steady-state operating condition, and wherein the steady-state operating condition is defined as a predetermined period of time after startup of the corresponding vehicle;identify driver profiles and store the driver profiles in a data store, each driver profile representing a human operator in combination with a vehicle of the plurality of vehicles, wherein each driver profile of the driver profiles is identified responsive to: associate some of the acquired digital values with a human operator of human operator(s) of the plurality of vehicles, wherein the associated human operator operated a corresponding vehicle of the plurality of vehicles when the associated digital values were generated; andanalyze the associated digital values so as to form the driver profile associated with the human operator in combination with the corresponding vehicle;acquire additional digital values corresponding to the given vehicle during operation of the given vehicle by a given driver;identify the given vehicle by comparing the additional digital values to baseline data formed from the acquired digital values, including generating the vehicle identification value correlating the given vehicle to an individual vehicle of the plurality of vehicles;responsive to a result of the vehicle identification value of the given vehicle, infer an identity of the given driver by comparing the sensor data associated with the given vehicle to the stored driver profiles; andgenerate a message reporting the inferred identity of the given driver and the vehicle identification value.
  • 2. The system of claim 1, wherein the processor is further configured to: following inferring the identity of the given driver, detect a threshold deviation from one of the driver profiles that corresponds to the inferred identity, wherein the threshold deviation is indicative of driver impairment;wherein the message includes information about the driver impairment.
  • 3. The system of claim 1, wherein the acquired digital values are transmitted wirelessly from the corresponding vehicle.
  • 4. The system of claim 2, wherein the processor is further configured to: compare the additional digital values to ones of the acquired digital values that correspond to a same vehicle; anddetect a maintenance issue of the corresponding vehicle based on the comparison.
  • 5. The system of claim 1, wherein the processor comprises a first processor, and, for each vehicle, the corresponding acquired digital values are read from a vehicle data communication port of the corresponding vehicle for transmission over a wireless telecommunication link to the first processor,wherein the system further includes a mobile device coupled to the vehicle data communication port of the corresponding vehicle, andwherein the mobile device includes a second processor configured to acquire the additional digital values via the vehicle data communications port and substantially immediately transmit the additional digital values using the wireless telecommunication link.
  • 6. The system of claim 1, wherein, for each vehicle, the corresponding acquired digital values are taken from an internal communications network of the corresponding vehicle,wherein the additional digital values are acquired over the internal communications network of the given vehicle, andwherein the internal communications network operates based on the controller area network (CAN) protocol.
  • 7. The system of claim 1, wherein, for each vehicle, the acquired digital values are taken from an internal communications network of the corresponding vehicle, andthe additional digital values are acquired over the internal communications network of the given motor vehicle of the plurality of vehicles.
  • 8. The system of claim 1, wherein the additional digital values specify at least one of: engine coolant temperature,engine air temperature,fuel rail pressure,engine oil temperature,absolute throttle position limit,engine revolutions per minute (RPM) at idle, orLambda exhaust oxygen sensor voltage.
  • 9. An apparatus arranged to transform intrinsic data collected from a plurality of vehicles into a vehicle identification value that identifies a given vehicle of the plurality of vehicles, the apparatus comprising: a processor to operate remotely from the plurality of vehicles, the processor in communication with the plurality of vehicles via one or more wireless links, the processor configured to:for each vehicle of the plurality of vehicles, acquire digital values intrinsically used by a propulsion unit controller to control one or more operating parameters of one or more of an engine or a motor of the corresponding vehicle, wherein for each vehicle the corresponding digital values include first data acquired under a first operating condition of the corresponding vehicle and second data acquired under a second operation condition of the corresponding vehicle, wherein the first operating condition of the corresponding vehicle is a cold condition and the second operating condition of the corresponding vehicle is a steady-state operating condition, and wherein the steady-state operating condition is defined as a predetermined period of time after startup of the corresponding vehicle;obtain, via one of the one or more wireless links, additional digital values corresponding to the given vehicle of the plurality of vehicles;compare the additional digital values to baseline data formed from the acquired digital values;generate the vehicle identification value that identifies the given vehicle of the plurality of vehicles based on the comparison; andoutput control data and/or control software to the given vehicle of the plurality of vehicles based on the acquired digital values and/or the obtained additional digital values, wherein the control data and/or the control software is configured to cause the given vehicle to adapt to current conditions.
  • 10. The apparatus of claim 9, wherein the processor is further configured to: following the identification of the given vehicle of the plurality of vehicles based on the comparison, use sensor data associated with the given vehicle to identify a current driver of the given vehicle of the plurality of vehicles; andoutput first information including the inferred identity of the current driver and the vehicle identification value.
  • 11. The apparatus of claim 10, wherein the processor is further configured to: compare the sensor data to a driver profile for the identified current driver to detect a threshold deviation from the driver profile, wherein the threshold deviation is indicative of driver impairment; andoutput second information about the driver impairment based on the comparison.
  • 12. The apparatus of claim 9, wherein the wireless link of the one or more wireless links couples to a mobile device, and wherein the additional digital values are received from the mobile device.
  • 13. The apparatus of claim 9, wherein the additional digital values comprise at least one of: engine coolant temperature,engine air temperature,fuel rail pressure,engine oil temperature,absolute throttle position limit,engine revolutions per minute (RPM) at idle, orLambda exhaust oxygen sensor voltage.
RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 14/753,290, filed Jun. 29, 2015, which is a division of U.S. patent application Ser. No. 13/911,454, filed Jun. 6, 2013, now issued as U.S. Pat. No. 9,104,538, which is a non-provisional of US Provisional Application No. 61/657,192 filed Jun. 8, 2012, all of which are incorporated herein by this reference.

US Referenced Citations (228)
Number Name Date Kind
5798695 Metalis Aug 1998 A
5898910 Miyake Apr 1999 A
6105063 Hayes, Jr. Aug 2000 A
6148253 Taguchi Nov 2000 A
6175789 Beckert Jan 2001 B1
6295000 Kuhn Sep 2001 B1
6356812 Cragun Mar 2002 B1
6377810 Geiger Apr 2002 B1
6434450 Griffin, Jr. Aug 2002 B1
6487717 Brunemann Nov 2002 B1
6535811 Rowland Mar 2003 B1
6553375 Huang Apr 2003 B1
6559773 Berry May 2003 B1
6578047 Deguchi Jun 2003 B1
6650534 Tree Nov 2003 B2
6799201 Lee Sep 2004 B1
6812942 Ribak Nov 2004 B2
6853910 Oesterling Feb 2005 B1
6850252 Hoffberg May 2005 B1
6895316 Chen May 2005 B2
6915176 Novelli Jul 2005 B2
6961536 Himmel Nov 2005 B2
6973476 Naden Dec 2005 B1
6981022 Boundy Dec 2005 B2
7053866 Mimran May 2006 B1
7062528 Deguchi Jun 2006 B2
7069434 Ilnicki Jun 2006 B1
7107234 Deguchi Sep 2006 B2
7127454 Deguchi Oct 2006 B2
7139660 Sarkar Nov 2006 B2
7190798 Yasuhara Mar 2007 B2
7190971 Kawamoto Mar 2007 B1
7206574 Bright Apr 2007 B2
7218925 Crocker May 2007 B2
7251473 Alrabady Jul 2007 B2
7302243 Tarbouriech Nov 2007 B2
7327228 Min Feb 2008 B2
7334041 Swindells Feb 2008 B2
7346435 Amendola Feb 2008 B2
7362239 Franczyk Apr 2008 B2
7363357 Parupudi Apr 2008 B2
7366892 Spaur Apr 2008 B2
7379541 Iggulden May 2008 B2
7398055 Tajima Jul 2008 B2
7403769 Kopra Jul 2008 B2
7437183 Makinen Oct 2008 B2
7461122 Kawana Dec 2008 B2
7467028 Pilgrim Dec 2008 B2
7480512 Graham Jan 2009 B2
7505732 McDonough Mar 2009 B2
7552009 Nelson Jun 2009 B2
7613564 Vorona Nov 2009 B2
7623949 Nou Nov 2009 B2
7634095 Arun Dec 2009 B2
7643788 Habaguchi Jan 2010 B2
7643913 Taki Jan 2010 B2
7657368 Weiss Feb 2010 B2
7663495 Haque Feb 2010 B2
7676830 Kuz Mar 2010 B2
7684908 Ogilvie Mar 2010 B1
7693612 Bauchot Apr 2010 B2
7805240 Naitou Sep 2010 B2
7805542 Hindman Sep 2010 B2
7809506 Kuge Oct 2010 B2
7812712 White Oct 2010 B2
7815100 Adams Oct 2010 B2
7826945 Zhang Nov 2010 B2
7885599 Yuhara Feb 2011 B2
7917644 Vedantham Mar 2011 B2
7970436 Katzer Jun 2011 B1
8014915 Jeon Sep 2011 B2
8799360 Nicholson Aug 2014 B2
9370029 O'Meara et al. Jun 2016 B2
9401057 Garrett Jul 2016 B2
9730254 O'Meara et al. Aug 2017 B2
10223751 Hutchinson Mar 2019 B1
20010018632 Thomas Aug 2001 A1
20020040401 Yasushi Apr 2002 A1
20020087655 Bridgman Jul 2002 A1
20020091848 Agresta Jul 2002 A1
20020103622 Burge Aug 2002 A1
20020123336 Kamada Sep 2002 A1
20020190856 Howard Dec 2002 A1
20020197983 Chubb Dec 2002 A1
20030003892 Makinen Jan 2003 A1
20030147534 Ablay Aug 2003 A1
20030182320 Lai et al. Sep 2003 A1
20030195925 Kaneko Oct 2003 A1
20040002938 Deguchi Jan 2004 A1
20040158372 Schwertfuehrer Aug 2004 A1
20040163046 Chu Aug 2004 A1
20040259545 Morita Dec 2004 A1
20050031100 Iggulden Feb 2005 A1
20050060350 Baum Mar 2005 A1
20050085965 Issa Apr 2005 A1
20050089750 Ng Apr 2005 A1
20050097186 Redpath May 2005 A1
20050132024 Habaguchi Jun 2005 A1
20050137757 Phelan Jun 2005 A1
20050216553 Mallonee Sep 2005 A1
20050216902 Schaefer Sep 2005 A1
20050221878 Van Bosch Oct 2005 A1
20050245272 Spaur Nov 2005 A1
20050249351 Miyahara Nov 2005 A1
20050264404 Franczyk Dec 2005 A1
20050266879 Spaur Dec 2005 A1
20050278080 Pilgrim Dec 2005 A1
20050283284 Grenier Dec 2005 A1
20060015221 Sarkar Jan 2006 A1
20060025897 Shostak Feb 2006 A1
20060025907 Kapolka Feb 2006 A9
20060036356 Rasin Feb 2006 A1
20060041337 Augsburger Feb 2006 A1
20060122749 Phelan Jun 2006 A1
20060141962 Forbes Jun 2006 A1
20060145827 Kuge Jul 2006 A1
20060161312 Juengling Jul 2006 A1
20060202799 Zambo Sep 2006 A1
20060241847 Kolmanovsky Oct 2006 A1
20060253874 Stark Nov 2006 A1
20070005206 Zhang Jan 2007 A1
20070013676 Obata Jan 2007 A1
20070021885 Soehren Jan 2007 A1
20070043829 Dua Feb 2007 A1
20070080816 Haque Apr 2007 A1
20070100513 Asano May 2007 A1
20070100766 Healy May 2007 A1
20070111710 Pietruszka May 2007 A1
20070126604 Thacher Jun 2007 A1
20070129878 Pepper Jun 2007 A1
20070143798 Jira Jun 2007 A1
20070155384 Haran Jul 2007 A1
20070200663 White Aug 2007 A1
20070208464 Moorhead Sep 2007 A1
20070208471 Lewis Sep 2007 A1
20070229307 Pawlenko et al. Oct 2007 A1
20070265744 Nicolai Nov 2007 A1
20070265745 Styles Nov 2007 A1
20070272423 Cutler Nov 2007 A1
20070281606 Baunach Dec 2007 A1
20080000959 Faoro et al. Jan 2008 A1
20080004038 Dunko Jan 2008 A1
20080005733 Ramachandran Jan 2008 A1
20080007120 Weyl Jan 2008 A1
20080071882 Hering Mar 2008 A1
20080120025 Naitou May 2008 A1
20080120175 Doering May 2008 A1
20080143497 Wasson Jun 2008 A1
20080172147 Taki Jul 2008 A1
20080204178 Maranville Aug 2008 A1
20080214236 Harb Sep 2008 A1
20080248742 Bauer Oct 2008 A1
20080249886 Woodard, Jr. Oct 2008 A1
20080266051 Taki Oct 2008 A1
20080268810 Kobayashi Oct 2008 A1
20080269961 Shitanaka Oct 2008 A1
20080272900 Schillinger Nov 2008 A1
20090012675 Laghrari Jan 2009 A1
20090075624 Cox Mar 2009 A1
20090079555 Aguirre De Carcer Mar 2009 A1
20090119657 Link, II May 2009 A1
20090128286 Vitito May 2009 A1
20090138942 Alrabady May 2009 A1
20090168742 Sumcad Jul 2009 A1
20090178651 Gale Jul 2009 A1
20090204815 Dennis Aug 2009 A1
20090215466 Ahl Aug 2009 A1
20090265173 Madhavan Oct 2009 A1
20090265633 Lim Oct 2009 A1
20090265701 Naslaysky Oct 2009 A1
20090271296 Romero Oct 2009 A1
20090290757 Mian Nov 2009 A1
20090300595 Moran Dec 2009 A1
20100037057 Shim Feb 2010 A1
20100082559 Sumcad Apr 2010 A1
20100088367 Brown Apr 2010 A1
20100115505 Touati May 2010 A1
20100125387 Sehyun May 2010 A1
20100153207 Roberts Jun 2010 A1
20100186711 Speers Jul 2010 A1
20100205012 McClellan Aug 2010 A1
20100222939 Nannburu Sep 2010 A1
20100235045 Craig Sep 2010 A1
20100287222 Wright Nov 2010 A1
20100332074 Brisighella, Jr. Dec 2010 A1
20110038307 Madhavan Feb 2011 A1
20110054768 Sullivan Mar 2011 A1
20110068912 Tollkuehn Mar 2011 A1
20110093136 Moinzadeh Apr 2011 A1
20110093153 Moinzadeh Apr 2011 A1
20110093154 Moinzadeh Apr 2011 A1
20110093846 Moinzadeh Apr 2011 A1
20110196568 Nickolaou Aug 2011 A1
20110208567 Roddy Aug 2011 A9
20110224865 Gordon et al. Sep 2011 A1
20110258044 Kargupta Oct 2011 A1
20110289186 Bell Nov 2011 A1
20120072244 Collins Mar 2012 A1
20120089423 Tamir Apr 2012 A1
20120094628 Mader Apr 2012 A1
20120130604 Kirshon May 2012 A1
20120163361 Moeller Jun 2012 A1
20120259511 Kuchler Oct 2012 A1
20120283893 Lee Nov 2012 A1
20130054121 Casoni Feb 2013 A1
20130166098 Lavie Jun 2013 A1
20130204455 Chia Aug 2013 A1
20130211662 Blumer Aug 2013 A1
20130238165 Garrett Sep 2013 A1
20130244634 Garrett Sep 2013 A1
20130304308 Maruyama Nov 2013 A1
20130304338 Frelich Nov 2013 A1
20130307972 Stone Nov 2013 A1
20130307989 Stone Nov 2013 A1
20130331056 McKown Dec 2013 A1
20130332024 Garrett Dec 2013 A1
20130332402 Rakshit Dec 2013 A1
20140025259 Szwabowski Jan 2014 A1
20140100740 Chutorash Apr 2014 A1
20140179274 O'Meara Jun 2014 A1
20140244104 Tan Aug 2014 A1
20150082297 Parry Mar 2015 A1
20150230277 O'Meara Aug 2015 A1
20150294565 Follmer Oct 2015 A1
20160046296 Offenhaeuser Feb 2016 A1
20160086285 Jordan Peters Mar 2016 A1
20160171521 Ramirez Jun 2016 A1
20170289810 O'Meara Oct 2017 A1
Foreign Referenced Citations (74)
Number Date Country
2242494 Sep 1997 CA
1268713 Oct 2000 CN
1452845 Oct 2003 CN
101132187 Feb 2008 CN
102 26 425 Dec 2003 DE
10 2005 044943 Mar 2006 DE
0 978 433 Feb 2000 EP
1 125 784 Aug 2001 EP
1 205 883 Jun 2008 EP
1978490 Oct 2008 EP
1978490 Oct 2008 EP
2 012 090 Jan 2009 EP
2 756 602 Jul 2014 EP
2 756 689 Jul 2014 EP
10163988 Jun 1998 JP
2002058013 Feb 2002 JP
2003085388 Mar 2003 JP
2003216261 Jul 2003 JP
2003222523 Aug 2003 JP
2005028997 Feb 2005 JP
2005044391 Feb 2005 JP
2005244878 Sep 2005 JP
2005309645 Nov 2005 JP
2005311810 Nov 2005 JP
2005331682 Dec 2005 JP
2006121573 May 2006 JP
2006317421 Nov 2006 JP
2006319453 Nov 2006 JP
2006-352850 Dec 2006 JP
2007015503 Jan 2007 JP
2008193337 Aug 2008 JP
2009077031 Apr 2009 JP
2009168772 Jul 2009 JP
2010130669 Aug 2010 JP
I291665 Dec 2007 TW
M329579 Apr 2008 TW
200926037 Jun 2009 TW
I311114 Jun 2009 TW
200937248 Sep 2009 TW
200941347 Oct 2009 TW
WO 00043870 Jul 2000 WO
WO 0101076 Jan 2001 WO
WO 0219116 Mar 2002 WO
2002076048 Sep 2002 WO
WO 03034235 Apr 2003 WO
2005006716 Jan 2005 WO
2005041071 May 2005 WO
WO 05041071 May 2005 WO
2005019834 Nov 2005 WO
WO 05105509 Nov 2005 WO
2006008731 Jan 2006 WO
WO 06023713 Mar 2006 WO
WO 2006024957 Mar 2006 WO
WO 06116190 Nov 2006 WO
2007022788 Mar 2007 WO
WO 07057895 May 2007 WO
WO 07092463 Aug 2007 WO
WO 07094988 Aug 2007 WO
WO 08050136 May 2008 WO
WO 08055117 May 2008 WO
WO 08112586 Sep 2008 WO
WO 080124795 Oct 2008 WO
WO 09016917 Feb 2009 WO
WO 09058154 May 2009 WO
2009088437 Jul 2009 WO
2010021982 Feb 2010 WO
WO 11037982 Mar 2011 WO
WO 11046823 Apr 2011 WO
WO 11047037 Apr 2011 WO
WO 11047045 Apr 2011 WO
WO 11047052 Apr 2011 WO
WO 11047056 Apr 2011 WO
WO 13039760 Mar 2013 WO
WO 13039763 Mar 2013 WO
Non-Patent Literature Citations (42)
Entry
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects Push Architecture (Release 6); 3GPP TR 23.976,” ETSI Standards; v. 3-SA2, No. V6 1.0; pp. 1-34, Jun. 1, 2004.
“Hybrid Vehicular Display” UTC; Aug. 24, 2004; United States; 5 pages.
“Mobile Device used as an External Graphical User Interface for Telematics Hardware installed in a Car. Demonstrating Speeding control and Road User Charge;” Disclosed by IBM; UTC; Oct. 13, 2005; 2 pages. Best Available Copy.
“Vehicle Console Personalization” Aug. 10, 2006; UTC; United States; 3 pages.
EP Supplemental Search Report EP 13801039; dated Jul. 2, 2015; 7 pages.
Listing of Related Cases; Schwabe, Williamson & Wyatt, Portland OR; Aug. 8, 2016; 2 Pages.
Kumehara, Sakae; Linux Network Guide for Firewall Administrators, Softbank Publishing Inc.; Feb. 25, 2000, first ED., pp. 150-180; cited in related JP application No. 2015-549739, (English translation not available).
Kumehara, S.; Linux Network Firewall Managers Guide; Softbank Publishing Co.; Feb. 25, 2000; First Edition, Japan; p. 150-180 (no English translation available).
EPO, International Search Report and Written Opinion of the International Searching Authority for International Patent Application No. PCT/US2016/031665, dated Sep. 2, 2016, 11 pages.
Alpine Electronics of America, Inc.; “Alpine Launches Mobile Phone Solution That Integrates With Car Audio Head Units;” Dec. 23, 2009; 2 pages.
Anonymous: “NAVTEQ, Nokia and Magneti Marelli Integrate Smartphone Into Car Entertainment System,” Internet citation, Sep. 17, 2009, pp. 1-3. Retrieved from the Internet: URL: http://www.gadgetpaper.com/navteq-nokia-and-magneti-marelli-integrate-smartphone-into-care-entertainment-system/ [retrieved on Jan. 28, 2011] p. 2, paragraph 1-3.
European Patent Office; International Search Report for PCT/US2009/062431; dated Jan. 25, 2010; 3 pages.
Extended European Search Report for European Application No. EP 10 82 4027 dated May 2, 2013; 8 pages.
Fuchs et al. “End to End Content Delivery Using UPnP and WiFi Network.” In: Connected Services in Mobile Networks—San Diego, CA, USA. Jan. 10-12, 2004. Retrieved on Jan. 7, 2012 from the internet at URL: <http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.110.7788&rep=rep1&type=pdf>. 11 pages.
Global Patent Solutions LLC, “Additional Search Results” dated Feb. 10, 2011; 4 pages.
Global Patent Solutions LLC, “Additional Search Results” dated Feb. 5, 2011; 4 pages.
Global Patent Solutions LLC, “Additional Search Results” for Search Name: Centralized Management of Motor Vehicle Software Applications and Services, Dec. 27, 2010; 4 pages.
Global Patent Solutions LLC, “Search Report” for Search Name: Centralized Management of Motor Vehicle Software Applications and Services, Jul. 30, 2010; 19 pages.
International Search Report dated Dec. 15, 2010 for PCT/US2010/052515; 3 pages.
International Search Report dated Dec. 20, 2010 for PCT/US2010/052511; 4 pages.
International Search Report dated Feb. 10, 2011 for PCT/US2010/052493; 5 pages.
International Search Report dated Feb. 10, 2011 for PCT/US2010/052502; 5 pages.
International Search Report for PCT/US2010/051978 dated Jan. 19, 2012; 3 pages.
International Search Report for PCT/US2012/053977 dated Nov. 27, 2012; 2 pages.
International Search Report for PCT/US2013/044448 dated Jan. 14, 2014; 2 pages.
Lau, F et al.; “Code-on-Demand and Code Adaptation for Mobile Computing”; Apr. 2005; internet citation http://i.cs.hku.hk/-clwang/papers/book-sparkle-lau-2005.pdf.
International Search Report for PCT/US2013/076710 dated Jul. 23, 2014; 6 pages.
Marisetty et al., “An architecture for In-Vehicle Infotainment Systems,” Jan. 29, 2010; URL: http://www.ddj.com/embedded-systems/222600438. 21 pages.
Nilsson et al.; “Secure Firmware Updates Over the Air in Intelligent Vehicles,” May 19-23, 2008; 5 pages.
Ryu et al.: “The Design of Remote Vehicle Management System Based on OMA DM Protocol and AUTOSAR S/W Architecture;” Jul. 23-25, 2008; 5 pages.
Supplementary European Search Report based on EP 06 71 9988 completed Jun. 13, 2008; 8 pages.
Supplementary European Search Report based on EP 08 73 1753 dated Sep. 19, 2012; 7 pages.
European Patent Office ISA; PCT International Search Report and Written Opinion; PCT/US2013/076710; dated Jun. 23, 2014; 14 pages.
United States Patent and Trademark Office ISA; PCT International Search Report; PCT/U52008/056323; dated Jun. 30, 2008; 2 pages.
Visteon Corporation; “Visteon Helps Connect Drivers and Passengers to Their Vehicle . . . and Their Vehicle to the World,” Jan. 7, 2010; http://www.prnewswire.com/news-releases/visteon-helps-connect-drivers-and-passengers-to-their-vehicles--and0-their-vehicles-to-the-world-80902587.html. 3 pages.
Jansen S., et al.; “Defining App Stores: The Role of Curated Marketplaces in Software Ecosystems”; 4th International Conference, ICSOB 2013; Potsdam Germany; Jun. 11-14, 2013 Proceedings. pp. 195-206.
United States Patent and Trademark Office, Office Action issued in U.S. Appl. No. 13/911,454, dated Dec. 4, 2014, 19 pages.
United States Patent and Trademark Office, Response to Office Action filed in U.S. Appl. No. 13/911,454, dated Feb. 26, 2015, 7 pages.
United States Patent and Trademark Office, Notice of Allowance issued in U.S. Appl. No. 13/911,454, dated May 1, 2015, 12 pages.
European Patent Office, Extended European Search Report issued in EP Application No. 13801039.2, dated Jul. 2, 2015, 7 pages.
European Patent Office, Response to Extended European Search Report filed in EP Application No. 13801039.2, dated Jan. 28, 2016, 10 pages.
European Patent Office, Notice of Intent to Grant issued in EP Application No. 13801039.2, dated Apr. 9, 2020 22 pages.
Related Publications (1)
Number Date Country
20160321844 A1 Nov 2016 US
Provisional Applications (1)
Number Date Country
61657192 Jun 2012 US
Divisions (1)
Number Date Country
Parent 13911454 Jun 2013 US
Child 14753290 US
Continuations (1)
Number Date Country
Parent 14753290 Jun 2015 US
Child 15204930 US