CA2478176A1 - Remote monitoring, configuring, programming and diagnostic system and method for vehicles and vehicle components - Google Patents
Remote monitoring, configuring, programming and diagnostic system and method for vehicles and vehicle components Download PDFInfo
- Publication number
- CA2478176A1 CA2478176A1 CA002478176A CA2478176A CA2478176A1 CA 2478176 A1 CA2478176 A1 CA 2478176A1 CA 002478176 A CA002478176 A CA 002478176A CA 2478176 A CA2478176 A CA 2478176A CA 2478176 A1 CA2478176 A1 CA 2478176A1
- Authority
- CA
- Canada
- Prior art keywords
- vehicle
- interface
- application
- board unit
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
Abstract
A system and method for monitoring, configuring, programming and/or diagnosing operation of at least one vehicle includes an on-board unit disposed on the vehicle to send and receive data corresponding to at least one vehicle operating characteristic, a plurality of modular applications, each application having an associated function that processes the data corresponding to said at least one vehicle operating characteristic obtained via the on-board unit, and an interface that allows selection among the plurality of modular applications to create a customized system.
Description
REMOTE MONITORING, CONFIGURING, PROGRAMMING AND
DIAGNOSTIC SYSTEM AND METHOD FOR VEHICLES AND VEHICLE
COMPONENTS
REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation-in-part claiming the benefit of commonly assigned, co-pending U.S. Patent Appln. No. 09/640,785, filed August 18, 2000 entitled "System, Method and Computer Program Product for Remote Vehicle Diagnostics, Monitoring, Configuring and Reprogramming" to Bromley et al., the disclosure of which is incorporated by reference in its entirety.
TECHi~IICAL FIELD
DIAGNOSTIC SYSTEM AND METHOD FOR VEHICLES AND VEHICLE
COMPONENTS
REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation-in-part claiming the benefit of commonly assigned, co-pending U.S. Patent Appln. No. 09/640,785, filed August 18, 2000 entitled "System, Method and Computer Program Product for Remote Vehicle Diagnostics, Monitoring, Configuring and Reprogramming" to Bromley et al., the disclosure of which is incorporated by reference in its entirety.
TECHi~IICAL FIELD
[0002] The present invention relates generally to computer data and information systems, and more particularly to computer tools for storing, processing, and displaying vehicle information.
BACKGROUND OF THE INVENTION
BACKGROUND OF THE INVENTION
[0003] It is common for companies to own a large number, or fleet, of commercial motor vehicles. Typical examples of such companies include commercial courier services, moving companies, freight and trucking companies, truck leasing companies, as well as passenger vehicle leasing companies and passenger Garners. To maintain profitability, a company owning a vehicle fleet ideally minimizes the time spent in vehicle maintenance and repair. Maintaining optimum vehicle performance often involves removing vehicles from service to conduct fault analysis, scheduled maintenance, diagnostics monitoring and parameter modifications.
[0004] Further, companies that manufacture vehicle components may wish to have a central database to access information for product improvements, warranty service, diagnostics, and other component data after components have been installed on the vehicle. Because different companies and different industries have different vehicle data gathering and reporting needs, current solutions involve constructing specialized systems for each particular user application.
[0005] There is a desire for a system that can monitor, configure, program and diagnose vehicles and/or vehicle components while allowing customization of the vehicle data to accommodate the different needs of different users and different.
SUMMARY OF THE INVENTION
SUMMARY OF THE INVENTION
[0006] Accordingly, one embodiment of the present invention is directed to a system for monitoring, configuring, programming and/or diagnosing operation of at least one vehicle, comprising an on-board unit disposed on the vehicle to send and receive data corresponding to at least one vehicle operating characteristic, a plurality of modular applications, each application having an associated function that processes the data corresponding to said at least one vehicle operating characteristic obtained via the on-board unit, and an interface that allows selection among the plurality of modular applications to create a customized.
[0007] Another embodiment of the invention is directed to an on-board unit disposed on a vehicle for use in a system for monitoring, configuring, programming and/or diagnosing operation of at least one vehicle, comprising at least one on-board unit interface to support communication between the on-board unit and at least one device outside the on-board unit, a processor that manages the data sent and received by the on-board unit via said at least one interface, and a memory coupled to the processor.
[0008] A further embodiment of the present invention is directed to a method for monitoring, configuring, programming and/or diagnosing operation of at least one vehicle, comprising obtaining data corresponding to at least one vehicle operating characteristic from an on-board unit on the vehicle, providing a plurality of modular applications that are selectable by the user to create a customized system, and processing the data corresponding to at least one vehicle operating characteristic obtained via the on-board unit according to at least one function associated with at least one selected modular application.
[0009] Further embodiments and variations of the invention will be apparent from the drawings and description below.
BRIEF DESCRIPTION OF THE DRAWINGS
BRIEF DESCRIPTION OF THE DRAWINGS
[0010] Figure 1 is a representative functional block diagram illustrating an overall system according to one embodiment of the present invention;
[0011] Figure 2 is a representative block diagram illustrating a system architecture according to one embodiment of the present invention;
[0012] Figures 3A and 3B are representative block diagrams of one embodiment of an on-board unit in one embodiment of the present invention;
[0013] Figure 4 is a block diagram of a parameter retrieval process according to one embodiment of the present invention;
[0014] Figure S is a block diagram of a parameter retrieval process according to another embodiment of the present invention;
[0015] Figure 6 is a block diagram of a parameter retrieval process according to yet another embodiment of the present invention;
[0016] Figure 7 is a graph illustrating the operation of a threshold alert process according to one embodiment of the present invention;
[0017] Figure 8 is a block diagram illustrating the operation of a tamper alert process according to one embodiment of the present invention;
[0018] Figure 9 is a block diagram illustrating a parameter change process according to one embodiment of the invention;
[0019] Figure 10 is a block diagram illustrating one possible architecture for a remote diagnostics application to be used in one embodiment of the present invention;
and [0020] Figure 11 is a block diagram illustrating one possible architecture of a leased vehicle management application to used in one embodiment of the present invention.
DETAILED DESCRIPTION OF THE EMBODIIVVIENTS
Stem functionalities and architecture [0021] Figure 1 is a representative functional diagram of a vehicle monitoring and diagnostics system 100 according to one embodiment of the present invention.
Generally, the inventive system 100 allows monitoring and control of a vehicle fleet by displaying and controlling data according to a user's customized specifications.
The system 100 is designed with modular applications that interact with core data and services so that vehicle parameters can be monitored, analyzed and displayed in a format that is meaningful to a particular user and/or a particular industry.
This flexibility allows different users and/or industries to use the same overall system 100 for vehicle and component monitoring despite their disparate vehicle data requirements.
and [0020] Figure 11 is a block diagram illustrating one possible architecture of a leased vehicle management application to used in one embodiment of the present invention.
DETAILED DESCRIPTION OF THE EMBODIIVVIENTS
Stem functionalities and architecture [0021] Figure 1 is a representative functional diagram of a vehicle monitoring and diagnostics system 100 according to one embodiment of the present invention.
Generally, the inventive system 100 allows monitoring and control of a vehicle fleet by displaying and controlling data according to a user's customized specifications.
The system 100 is designed with modular applications that interact with core data and services so that vehicle parameters can be monitored, analyzed and displayed in a format that is meaningful to a particular user and/or a particular industry.
This flexibility allows different users and/or industries to use the same overall system 100 for vehicle and component monitoring despite their disparate vehicle data requirements.
[0022] Referring to the Figure, the system 100 may include an application service provider (ASP) infrastructure 102 that acts as a gateway between a plurality of vehicles 104, each vehicle having an associated on-vehicle computer (e.g., an on-board unit or "OBU" 105) and customizable interface 106. The interface 106 allows a user or machine 106a to select among various applications, such as third-party applications 108 as well as original, system-supplied applications 110, to obtain and analyze various data from the vehicles 104. The applications may include, for example, tools for obtaining real-time fleet characteristics, trend analysis and diagnostics, to perform manual, dynamic or rule-based configuration, as well as allow fleet managers to provide real-time driver/fleet notification. To ensure that the user receives data that is meaningful to the user's specific application, the user interface 106 can be customized to operate applications. selected by the user. In the example shown in Figure 1, different types of users 106a may select different applications as a customized application group 112 to accommodate their specific data monitoring and reporting needs applicable to their own business.
[0023] For example, as illustrated in Figure 1, a dealer/repair facility may select from the offered applications 108, 110, vehicle configuration, scheduled maintenance, remote diagnostics, and concierge services as its application group 112, while a truck.
manufacturer may select a different collection of applications 112, such as warranty service/campaign support, vehicle history, and guided diagnostics. By offering a .
variety of modular applications 108, 110, that can be selected and combined according to the needs of a particular user, the same infrastructure 102 can be customized and used by different users for different purposes with little or no modification of the infrastructure 102 itself. Further, by allowing users to access third-party applications 108 through the same infrastructure as system supplied applications 110, the system 100 can leverage services not provided by the system 100 itself, further increasing flexibility and adaptability.
manufacturer may select a different collection of applications 112, such as warranty service/campaign support, vehicle history, and guided diagnostics. By offering a .
variety of modular applications 108, 110, that can be selected and combined according to the needs of a particular user, the same infrastructure 102 can be customized and used by different users for different purposes with little or no modification of the infrastructure 102 itself. Further, by allowing users to access third-party applications 108 through the same infrastructure as system supplied applications 110, the system 100 can leverage services not provided by the system 100 itself, further increasing flexibility and adaptability.
[0024] Further, in an embodiment of the inventive system using an ASP-based model, an application service provider provides and allows access, on a subscriber basis, to a remote vehicle diagnostics, monitoring, configuration and reprogramming tool via the Internet. That is, the application service provider provides the hardware (e.g., servers, an on-vehicle computer) and software (e.g., database) infrastructure, application software, customer support, and billing mechanism to allow its customers (e.g., fleet managers, vehicle distributors, vehicle dealers, original equipment manufacturers ("OEMs"), leasing/rental companies, and the like) to remotely access the vehicles within a fleet. The tool can be used by subscribers to select and access the modular applications 108, 110.
[0025] Note that an ASP-based model can eliminate the need to physically distribute software to users. Instead, new features and updates can be immediately available to users because the system resides and runs on an application server. In one embodiment, applications that are not on the application server can reside on the OBU
105. The on-board unit applications can be loaded onto the OBU 105 during vehicle installation, and additional applications or application updates can be downloaded onto the OBU 105 through a wireless network connection.
105. The on-board unit applications can be loaded onto the OBU 105 during vehicle installation, and additional applications or application updates can be downloaded onto the OBU 105 through a wireless network connection.
[0026] Figure 2 is a representative block diagram of a system architecture 200 according to one embodiment of the present invention. The system architecture shown. in Figure 2 is one possible way for carrying out the functionalities described above and shown in Figure 1. In this example, the architecture includes three primary components: the interface 106, a server 202, and the on-board unit (OBU) 105.
All three components 106, 202, 105 are designed to communicate with each other through any known means, such as via wireless networks 206.
All three components 106, 202, 105 are designed to communicate with each other through any known means, such as via wireless networks 206.
[0027] The interface 106 can be, for example, a user interface and/or a machine interface that allows a human or machine to access the infrastructure 102, which includes the server 202. The server 202 may include, for example, a series of servers that perform web page hosting, run applications, perform data storage, and/or perform wireless communications network management. In this example, the server 202 includes a web/application server 202a, a vehicle server 202b, and a communications server 202c, all of which are linked to a database server 202d. As shown in the Figure, the server 202 acts as a link between a web based client (user) 106 with the OBU 105, allowing user access and control to a vehicle data stream via the Internet 210 or other internetworking system.
[0028] The OBU 105 access the data from various vehicle components and may also generate vehicle data of its own to provide to the server 202. The OBU 105 may include a wireless communication module lOSa to provide a communication link to a wireless network, a vehicle data processing module l OSb to process data obtained from the vehicle components, and a vehicle interface l OSc connected to, for example, the vehicle data bus to gather data from the vehicle components for processing and managing time or process-critical functions with the vehicle systems, such as electronic control units. The OBU 105 may also include a global positioning system and a driver display interface.
(0029] Each of the system architecture components will be described in greater detail below.
Interface [0030] The interface 106 may be a standard browser interface and/or a machine-to-machine interface. In the browser interface, a human user accesses the system via a standard web browser. In one embodiment, the user gains access to the specific set of their authorized vehicles and functions after login and password authorization. In a machine-to-machine interface, server and vehicle data and functions may be accessible via a secure application program interface (API). A machine-to-machine interface allows other applications access to the system's 100 capabilities so they can gain remote access to the vehicle and the capabilities offered by the system.
This allows the system 100 to interface with existing or planned back office applications and operations, making the system 100 suitable for integration with, for example, overall fleet operations or other systems.
S erver [0031] The server system is the fixed-based component of the system and, as explained above, can be an Internet-based system and use an ASP model. The end user can access the system from the interface 106, such as any commercially available web browser. As noted above, the server 202 in this embodiment includes the web application server 202a, the vehicle server 202b, and the communications server 202c, and the database server 202d. Each of these will be described in greater detail below.
Interface [0030] The interface 106 may be a standard browser interface and/or a machine-to-machine interface. In the browser interface, a human user accesses the system via a standard web browser. In one embodiment, the user gains access to the specific set of their authorized vehicles and functions after login and password authorization. In a machine-to-machine interface, server and vehicle data and functions may be accessible via a secure application program interface (API). A machine-to-machine interface allows other applications access to the system's 100 capabilities so they can gain remote access to the vehicle and the capabilities offered by the system.
This allows the system 100 to interface with existing or planned back office applications and operations, making the system 100 suitable for integration with, for example, overall fleet operations or other systems.
S erver [0031] The server system is the fixed-based component of the system and, as explained above, can be an Internet-based system and use an ASP model. The end user can access the system from the interface 106, such as any commercially available web browser. As noted above, the server 202 in this embodiment includes the web application server 202a, the vehicle server 202b, and the communications server 202c, and the database server 202d. Each of these will be described in greater detail below.
[0032] The web application server 202a contains the logic defining one or more applications to an end user. All the data needed for a specific user application is requested and sent to the OBU 105 via the wireless communication network 206.
As will be explained in greater detail below, applications perform the necessary calculations and then package the results for presentation in a defined format to the user. Further, the web application server 202 is responsible for running business applications related to user activities, which may include performing business logic, interfacing to the systems databases for fleet, vehicle, component, and transaction activity, knowledge-base storage, and sending user requested vehicle queries or functions to the vehicle server 202b and the communications server 202c.
As will be explained in greater detail below, applications perform the necessary calculations and then package the results for presentation in a defined format to the user. Further, the web application server 202 is responsible for running business applications related to user activities, which may include performing business logic, interfacing to the systems databases for fleet, vehicle, component, and transaction activity, knowledge-base storage, and sending user requested vehicle queries or functions to the vehicle server 202b and the communications server 202c.
[0033] The vehicle server 202b in the server 202 stores and processes vehicle-specific data and acts as a translator between the applications 108, 110 and the specific vehicle and/or vehicle component. More particularly, the vehicle server 202b is responsible for processing data requests and vehicle responses and converting the outbound and inbound data into translated vehicle information.
[0034] The vehicle server 202b translates user requests from the interface 106 into formats specific to the vehicle 104 to which the request is directed. The vehicle server 202b conducts this translation without any user interaction or property selections. For example, the vehicle server 202b may evaluate a message being sent to a particular vehicle and detect the vehicle type, the vehicle bus type, and the vehicle component or sub-component that is intended as the message recipient.
The vehicle server 202b then packages the message according to the specific communication protocol mandated by the recipient component. As a result, the vehicle server 202b allows monitoring and control of different vehicles having different components through the same interface 106 for a given user and application.
The vehicle server 202b then packages the message according to the specific communication protocol mandated by the recipient component. As a result, the vehicle server 202b allows monitoring and control of different vehicles having different components through the same interface 106 for a given user and application.
[0035] As shown in Figure 2, one embodiment of the inventive system allows communication between at least the vehicles 104 and the server 202 via a wireless network, such as a satellite or terrestrial based network. A communication server 202c may be included in the server 202 to support wireless communications and provide a central location for supporting changes and improvements in wireless technology. In one embodiment, the communication server 202c manages the communications activities between the OBU 105 and the vehicle server 202b and processes vehicle/component specific requests between the OBU 105 and the server 202b.
[0036] In one embodiment, the communications server 202c utilizes a wireless communications framework that provides a communication link between the server 202 and the vehicle 104. Although any wireless mobile communication system can be used in the inventive system 100, a flexible wireless communication infrastructure that is capable of handling multiple platforms and/or multiple communication providers is preferred. One possible embodiment of such a framework is described in U.S. Provisional Application No. 60/351,165 (Attorney Docket No. 65855-0060), entitled "Wireless Communication Framework", filed January 23, 2002, the disclosure of which is incorporated herein by reference in its entirety. To handle multiple communication providers and/or platforms, the flexible wireless communication infrastructure may abstract the needs of a specific wireless communication provider, such as the message size, message format, and specific protocol details, into a standard messaging API understandable by multiple systems and platforms: In one embodiment, the communication server 202c abstracts messages, and stores and forwards messages to ensure later delivery of messages to vehicles that are temporarily outside a wireless communication coverage area, and may even include least cost routing rules to select among multiple wireless networks to prioritize message routing based on cost and/or criticality of the message.
[0037] The server 202 also includes a database server 202d containing relational data tables designed to retain information pertaining to a user, a vehicle, a fleet, system transaction history and other relationships associated with a given vehicle 104. The database server 202d also may be designed to retain the data resulting from any vehicular transaction, such as transactions between the OBU 105 and the server 202.
In one embodiment, the database is structured such that authorized users can access vehicles in a number of ways, for example, by fleet ownership, leasing fleet, vehicle manufacturer, and component manufacturer. This structure enables the system 100 to provide each of these beneficiaries with specific, customized data and access in a format meaningful to each user.
On board unit (OBUI
In one embodiment, the database is structured such that authorized users can access vehicles in a number of ways, for example, by fleet ownership, leasing fleet, vehicle manufacturer, and component manufacturer. This structure enables the system 100 to provide each of these beneficiaries with specific, customized data and access in a format meaningful to each user.
On board unit (OBUI
(0038] As noted above, the OBU 105 provides the vehicle-side, real-time computing base for the system. In one embodiment, the OBU 105 is responsible for data stream processing, discrete measurements, vehicle position information, wireless communications, and real-time analysis of data. Within the system's overall framework, the OBU 105 acts as a vehicle server, providing vehicle specific data and fimctionality. In one embodiment, the OBU 105 may be an expandable custom hardware platform designed and manufactured to reside on a wide variety of vehicles with different component specifications and needs and is preferably capable of running multiple applications while acting as a vehicle data gateway for others.
(0039] Figures 3A and 3B are representative high-level block diagrams of the OBU
105. One embodiment of the OBU 105 may include a data processor 300 and one or more interfaces 302, 304, 306 such as a wireless interface 302 that controls communication between the OBU 105 and the server 202 via the wireless network 206, a vehicle interface 304 that allows the OBU 105 to transmit to and receive from, for example, electronic control units (ECUs), vehicle controllers, and/or other vehicle components 308, and an optional user interface 306 that allows a user to read and/or enter information into the OBU 105.
105. One embodiment of the OBU 105 may include a data processor 300 and one or more interfaces 302, 304, 306 such as a wireless interface 302 that controls communication between the OBU 105 and the server 202 via the wireless network 206, a vehicle interface 304 that allows the OBU 105 to transmit to and receive from, for example, electronic control units (ECUs), vehicle controllers, and/or other vehicle components 308, and an optional user interface 306 that allows a user to read and/or enter information into the OBU 105.
[0040] The wireless interface 302 in one embodiment sends and receives data from the server 202 to and from the OBU 105 and abstracts communications from different wireless network devices to allow the OBU 105 to communicate with a flexible wireless communication infrastructure, such as the type described above with respect to the server 202. More particularly, the wireless interface 302 may encapsulate protocol differences among various wireless network devices to provide a standard output to the processor 300. In one embodiment, wireless network messages are routed from the server 202 to the wireless interface 302 for error checking and filtering. After filtering, commands are passed to the processor 300 and then routed to their respective vehicle components.
(0041] The processor 300 acts as the central process'mg unit (CPU) of the OBU
by managing the sending and receiving of requests between the server 202 and the vehicle 104 via the wireless interface 302. In one embodiment, the processor 300 has the logic and intelligence to carry out vehicle specific services such as diagnostic requests and processing . For example, the processor 300 may run specific applications that are loaded into the OBU's memory 31 S, 316, 318 and coordinates activities between the vehicle datastream, GPS unit, wireless communications, and the remote server 202. Further, in one embodiment, the processor 300 can be updated through the wireless network to add and enhance its functionality. This capability eliminates requiring the vehicle to be at the service bay for software updates that enhance features and functionality.
by managing the sending and receiving of requests between the server 202 and the vehicle 104 via the wireless interface 302. In one embodiment, the processor 300 has the logic and intelligence to carry out vehicle specific services such as diagnostic requests and processing . For example, the processor 300 may run specific applications that are loaded into the OBU's memory 31 S, 316, 318 and coordinates activities between the vehicle datastream, GPS unit, wireless communications, and the remote server 202. Further, in one embodiment, the processor 300 can be updated through the wireless network to add and enhance its functionality. This capability eliminates requiring the vehicle to be at the service bay for software updates that enhance features and functionality.
[0042] The vehicle interface 304 allows the OBU 105 to support a wide variety of vehicle components and subcomponents. Possible interfaces that can be supported by the OBU include SAE J1708, SAE J1939, SAE OBDII/CAN, ISO-9141, discrete I/O, proprietary interfaces, and other interfaces (e.g., discrete or instrumentation interfaces). Further, the vehicle interface 304 provides a single point of contact for all vehicle components and control devices on the vehicle,104, allowing the communication between OBU software with the vehicle's actual data bus line as well as wireless communication devices, such as a satellite-based communications system.
[0043] In one embodiment, the vehicle interface 304 may include a data parser/requester module 310 that contains software code logic that is also responsible for handling direct interfacing between the processor 300 and the vehicle data bus 307 for non-application specific (i.e., "generic" SAE J1708 or SAE1939 discrete measurement points) parameter readings, alerts, configuration or reprogramming data, as explained in greater detail below.
[0044] The vehicle interface 304 may also include, for example, one or more application specific modules 312, such as one for each manufacturer specific controller 308 within the vehicle 104, each containing software code logic that is responsible for handling interfacing between the processor 300 and the vehicle data bus 307 (via data parser/requestor module 310 in this example) for application-specific parameter readings, alerts, configuration or reprogramming data.
(0045] Note that the OBU 105 may act as a server and/or data gateway for an application that places data directly on the vehicle data bus 307. In one embodiment, the OBU 105 uses an interface standard, such as TMC RP 1210A, as an element of to the data gateway. Regardless of the specific standard used, any activity using the OBU 105 as a data gateway will involve data going through the processor 300.
[0046] In an embodiment of the present invention, the OBU 105 is designed to be compliant with the SAE's Joint SAElTMC Recommended Environmental Practices for Electronic Equipment Design (Heavy-Duty Trucks), Document No. ]1455 (August 1994) standard, which is incorporated herein by reference in its entirety, because it will be a component included (or installed) within vehicles 104. As indicated above, the OBU 105 is not limited to be compliant with any particular standard and can accommodate any on-board electronic system standard (e.g., SAE ]1708, SAE
]1939, SAE ]1850, ISO 9141, proprietary data streams, etc.) for any sub-system (e.g., engines, transmissions, braking systems, instrument clusters, etc.) as long as the system 100 is capable of converting commands between the interface 106 and the OBU 105 according to whatever standard is used by a given vehicle electronic system. If the vehicle electronic system uses a proprietary standard, for example, the vehicle server 202b and the associated application specific module 312 on the OBU
105 may be adapted to accommodate the proprietary standard.
]1939, SAE ]1850, ISO 9141, proprietary data streams, etc.) for any sub-system (e.g., engines, transmissions, braking systems, instrument clusters, etc.) as long as the system 100 is capable of converting commands between the interface 106 and the OBU 105 according to whatever standard is used by a given vehicle electronic system. If the vehicle electronic system uses a proprietary standard, for example, the vehicle server 202b and the associated application specific module 312 on the OBU
105 may be adapted to accommodate the proprietary standard.
[0047] Figure 3B illustrates another embodiment of the OBU 105 and explicitly shows the capability to interface with other devices via, for example, a parallel interface, serial interface, universal serial bus (USB), satellite, terrestrial wireless (e.g., 802.1 lb), and/or a global positioning system (GPS). More particularly, the embodiment of the OBU 105 shown in Figure 3B includes a GPS circuit 313 that receives signals from a GPS antenna and a serial interface 314 that communicates with a driver interface or other on-vehicle devices (not shown), such as a handheld device, a cellular telephone, voice messaging system, data logger, or other devices.
Figure 3B also explicitly illustrates a flash memory 315, a dynamic random access memory 316, and an optional compact flash memory 318 coupled to the processor 300 as well as a power supply 320 coupled to the vehicle battery and ignition switch (not shown). Those of skill in the art will understand that the elements and concepts shown in Figures 3A and 3B can be combined in any manner without departing from the scope of the invention.
Figure 3B also explicitly illustrates a flash memory 315, a dynamic random access memory 316, and an optional compact flash memory 318 coupled to the processor 300 as well as a power supply 320 coupled to the vehicle battery and ignition switch (not shown). Those of skill in the art will understand that the elements and concepts shown in Figures 3A and 3B can be combined in any manner without departing from the scope of the invention.
(0048] The application software and the application framework is built with both a software and hardware abstraction layer. This approach makes the framework adaptable to a number of alternative operating system and hardware platforms.
One embodiment of the OBU 105 may use any known real-time operating system.
S sty em operation examples [0049] The overall system 100 can support many possible services and applications, examples of which are described below and illustrated in Figures 4 through 8.
As noted above, the system 100 shown in Figures 1 and 2 illustrate one possible relationship between services and applications for a system 100 using an ASP-based model. In one embodiment, a group of core services 350 that perform vehicle-specific operations are available to the applications 108, 110. As noted above, the applications 108, 110 allow a user to customize the interpretation and display of the vehicle-specific operations based on the user's own requirements. The core services 350 act as building blocks of services that can be selected or combined in any desired manner, and can be accessed by or with any applications 108, 110 in the system 100;
in other words, the applications 108, 110 act as a functional layer over the more primitive core services 350. For example, the core services 350 may be accessed by a help desk application to obtain vehicle location along with parametric data or by a service application to obtain parametric data and to perform functional tests.
Because the system 100 can leverage other applications and services that the system 100 itself may not have and couple them with its own applications and services, the system 100 provides a flexible and adaptable platform that can accommodate many different needs.
One embodiment of the OBU 105 may use any known real-time operating system.
S sty em operation examples [0049] The overall system 100 can support many possible services and applications, examples of which are described below and illustrated in Figures 4 through 8.
As noted above, the system 100 shown in Figures 1 and 2 illustrate one possible relationship between services and applications for a system 100 using an ASP-based model. In one embodiment, a group of core services 350 that perform vehicle-specific operations are available to the applications 108, 110. As noted above, the applications 108, 110 allow a user to customize the interpretation and display of the vehicle-specific operations based on the user's own requirements. The core services 350 act as building blocks of services that can be selected or combined in any desired manner, and can be accessed by or with any applications 108, 110 in the system 100;
in other words, the applications 108, 110 act as a functional layer over the more primitive core services 350. For example, the core services 350 may be accessed by a help desk application to obtain vehicle location along with parametric data or by a service application to obtain parametric data and to perform functional tests.
Because the system 100 can leverage other applications and services that the system 100 itself may not have and couple them with its own applications and services, the system 100 provides a flexible and adaptable platform that can accommodate many different needs.
[0050] In one embodiment, the applications may assemble the core services to perform specific functions. For example, one of the core services 350 may capture measured values and/or change parameters or operational settings in the vehicle 104 while the applications 108, 110 organize and process information from the core services 350 into groupings that are meaningful to a given user. A service outlet, for example, may want different data and/or data organized in a different manner than a leasing organization or a component manufacturer.
(0051] As noted above and as shown in Figures 1 and 2, the interface 106 can be a browser interface or graphical user interface (GU)7 that allows a human user to access the system 100, or a machine-to-machine application programming interface (AP)7.
The user interface 106 allows the system 100 to act as a gateway between the user and the vehicles) 104 via the applications and services.
The user interface 106 allows the system 100 to act as a gateway between the user and the vehicles) 104 via the applications and services.
[0052] As noted above, the core services 350 provided by the system 100 act as building blocks that can be assembled by applications in a variety of ways that can best serve the user. Possible core services 350 include:
Parameters: obtains discrete or data stream-based vehicle parameters, including standard and proprietary messages, upon user request;
Alerts: notification of the occurrence of a particular event (e.g., receipt of a trouble code or a notification of a parameter value occurring outside an acceptable parameter range);
Functions: runs functional tests on vehicle components and generates result reports;
Configuration: performs remote configuration of a vehicle or component by, for example, changing one or more vehicle parameters;
Reprogramming: performs complete reprogramming, or "re-flashing" of a selected on-vehicle controller;
Geographic location: provides vehicle location through, for example, a GPS
system.
Parameters: obtains discrete or data stream-based vehicle parameters, including standard and proprietary messages, upon user request;
Alerts: notification of the occurrence of a particular event (e.g., receipt of a trouble code or a notification of a parameter value occurring outside an acceptable parameter range);
Functions: runs functional tests on vehicle components and generates result reports;
Configuration: performs remote configuration of a vehicle or component by, for example, changing one or more vehicle parameters;
Reprogramming: performs complete reprogramming, or "re-flashing" of a selected on-vehicle controller;
Geographic location: provides vehicle location through, for example, a GPS
system.
[0053] The list of core services 350 above is not meant to be exhaustive, but are simply examples of possible services that can be available directly to users or supplied to applications for further processing. Note that although the explanations below focus on obtaining data from a vehicle ECU 308, the system and functions described below are applicable for any vehicle data.
[0054] The "Parameters" service may include a simple parameter retrieval service as well as more sophisticated parameter retrieval services that address limitations in obtaining vehicle data when, for example, the vehicle is turned off. Figure 4 illustrates one simple process 400 for obtaining a parameter. When the OBU 105 receives a command from the server 202 to retrieve a data value at block 402, the OBU 105 sends a query message to the ECU 308 to obtain the ECU's current reading at block 404. Once the ECU 308 returns a parameter value at block 406, the OBU
105 retrieves the value and forwards it to the server at block 408. Note that frequently used parameters may be packaged and transmitted to the server 202 as a single message as a more efficient way of transfernng data. Further, the specific means for getting a particular data item may depend on the specific requirements of a given ECU 308. For example, as is known in the art, data points corresponding to an anti-lock brake system may be obtained in a different manner than data corresponding to engine coolant temperature.
105 retrieves the value and forwards it to the server at block 408. Note that frequently used parameters may be packaged and transmitted to the server 202 as a single message as a more efficient way of transfernng data. Further, the specific means for getting a particular data item may depend on the specific requirements of a given ECU 308. For example, as is known in the art, data points corresponding to an anti-lock brake system may be obtained in a different manner than data corresponding to engine coolant temperature.
[0055] Figure 5 is a flowchart illustrating one possible process to be offered as a "Parameters" service that is more sophisticated that the simple parameter retrieval service explained above. Although parameter data can simply be read from the vehicle's electronic controllers and provided to the user on demand, the "Parameters"
service can also provide more sophisticated parameter data capture methods such as the type shown in Figure 5. Figure 5 illustrates a "snapshot" process 500 for obtaining a set of parameter values over a period of time, where the reporting of the parameter values is triggered by a specified event. Offering this service as an on-vehicle diagnostic tool is particularly helpful for intermittent fault diagnosis and vehicle performance analysis. Further, gathering data sets at prescribed periodic intervals minimizes negative effects caused by inherent problems in wireless communication systems, such communications drop-out and lack of coverage, which would normally make remote diagnostics ineffective.
service can also provide more sophisticated parameter data capture methods such as the type shown in Figure 5. Figure 5 illustrates a "snapshot" process 500 for obtaining a set of parameter values over a period of time, where the reporting of the parameter values is triggered by a specified event. Offering this service as an on-vehicle diagnostic tool is particularly helpful for intermittent fault diagnosis and vehicle performance analysis. Further, gathering data sets at prescribed periodic intervals minimizes negative effects caused by inherent problems in wireless communication systems, such communications drop-out and lack of coverage, which would normally make remote diagnostics ineffective.
[0056] To carry out the snapshot process 500, the system 100 first initializes at block 502 by, for example, storing the diagnostic parameters to monitor, setting the time intervals at which parameter values are captured, selecting the number of captured values to be included in a single report, and selecting the event that will trigger reporting of the captured values. This information can be inputted into the via the interface 106. The parameter values to be captured can be any parameters accessible on the vehicle's electronic controllers by means of a diagnostic data stream or from discrete inputs on the OBU 105. The triggering event can be any non-continuous event that is monitored on the vehicle, such as the capture of an active trouble code from a vehicle controller or a parameter moving outside an established acceptable range.
[0057] Once the OBU 105 has been configured (block 502), the OBU 105 maintains a number of historical value sets at block 504 by caching a selected number of parameter readings during normal vehicle operation. While the OBU 105 captures the parameter readings, it also waits for the triggering event to occur. Once the trigger event occurs (block 506), the OBU 105 continues caching the configured parameter readings occurring after the event (block 508). The number of historical value sets can be, for example, half the number of captures to be included in the final report, while the number of value sets taken after the triggering event can make up the other half. Note that the OBU 105 may, in another embodiment, capture parameter readings only before or after the triggering event as well or capture different numbers of values on either side of the event.
[0058] After all of the desired value sets have been captured and collected, all of the captured readings, both before and after the event, are combined into a final report at block 510. The report can be stored on the OBU 105 for later retrieval or sent via wireless connection to the application server 202a for immediate viewing.
[0059] Another possible process that can be offered as a "Parameters" service is a "get stored values" (GSV) process 600, as illustrated in Figure 6, for collecting parameter values from a vehicle even if the vehicle is unable to provide current parameter values at the time of the query. The GSV process 600 addresses a situation where the vehicle controllers 308 are unable to respond to a query by the OBU
(e.g., while the vehicle is turned off) to respond to a query. This process is particularly useful in applications requiring remote retrieval of time-sensitive data, such as an odometer reading at the end of a scheduled period, or in any application where the vehicle operating state is unlrnown at the time of the query.
(e.g., while the vehicle is turned off) to respond to a query. This process is particularly useful in applications requiring remote retrieval of time-sensitive data, such as an odometer reading at the end of a scheduled period, or in any application where the vehicle operating state is unlrnown at the time of the query.
[0060] For the GSV process 600 to be effective, the OBU 105 should be designed to allow continuous remote access so that the OBU 105 is always ready for receiving and sending messages. The OBU 105 is initialized by receiving an instruction to periodically collect specified parameter data at a selected query time interval (block 602). After receiving this command, the OBU 105 will periodically collect data at the specified query time intervals (block 604). The values gathered by the OBU 105 are stored in the on-board unit's memory, such as a flash memory, at block 606 before the OBU 105 is shut down when the vehicle 104 is turned off.
[0061] If the OBU 105 receives a GSV "retrieve" command from the application server 202a (block 608), the OBU 105 checks the state of the vehicle controller 308 at block 610. If the vehicle controller 308 is accessible, then the OBU 105 collects the current values from the vehicle controller 308 at that time and sends the collected current values to the server 202. If the vehicle controller 308 is not available at the time of the command (e.g., if the vehicle is turned off), making the current values of the controller 308 unretrievable, the saved values in the OBU 105 are sent back to the server 202 as the retrieved values (block 612).
[0062] By periodically collecting data at selected intervals while the vehicle controller is operational, the OBU 105 can at least obtain recent vehicle controller parameter readings before the controller 308 is inaccessible at some later time. As a result, the GSV process 600 allows the remote server 202 to obtain the most recent controller data if current data is not available at the time of the query. In short, the GSV process 600 returns the last known value in memory to the server 202 if the vehicle is turned on and will retrieve a backup value, which may still be the last known value in memory, if the vehicle is turned off.
[0063] l~rlultiple "?~erts" services may also be provided as a core service in the system 100. In its simplest form, the "Alert" service monitors vehicle trouble codes and transmits a message to the OBU 105 when the trouble code occurs. For example, a fault code may come as solicited or unsolicited, depending on how the controller 308 in the OBU 105 is instnicted to handle faults. To obtain an unsolicited fault, the OBU
105 monitors the vehicle data bus 307 for the occurrence of a fault and notifies the server 202 if a fault occurs. If only a set of individual faults are monitored, additional parsing shall be performed to filter out unwanted faults. For example, if a user only wishes to be informed of fault codes corresponding to a component breakdown, as opposed to being informed of all fault codes, the user can indicate this preference via the interface 106.
105 monitors the vehicle data bus 307 for the occurrence of a fault and notifies the server 202 if a fault occurs. If only a set of individual faults are monitored, additional parsing shall be performed to filter out unwanted faults. For example, if a user only wishes to be informed of fault codes corresponding to a component breakdown, as opposed to being informed of all fault codes, the user can indicate this preference via the interface 106.
[0064] To obtain a solicited fault, the user may set up periodic queries to the OBU
processor 300 in addition to setup notification. Note that the response message may match the message template even if no fault actually existed; in this case, additional parsing of the response message may be necessary to obtain useful information.
For example, if the user solicits a request for information, the user may obtain a response based upon the criteria of that request, which may be different than the criteria for unsolicited notifications.
processor 300 in addition to setup notification. Note that the response message may match the message template even if no fault actually existed; in this case, additional parsing of the response message may be necessary to obtain useful information.
For example, if the user solicits a request for information, the user may obtain a response based upon the criteria of that request, which may be different than the criteria for unsolicited notifications.
[0065] If desired, the "Alert" service may include additional functions such as providing the ability to add/remove individual faults, canceling the alert fimction for a given fault when a fault alert is fired so that only the first fault occurrence (and not subsequent fault occurrences) trigger a notification message, or configuring the "Alert" service to be stored permanently in, for example, the database server 202d until the user removes the service or until the service is cancelled by a fault occurrence.
[0066] With respect to the example shown in Figure 7 and as noted above, the "Alerts" service may include among its functions the detection of a particular event by checking whether a monitored value exceeds a selected threshold. Note that although this example focuses on one diagnostic parameter, any number of diagnostic parameters may be combined into an algorithm to detect threshold limit boundaries.
Further, values may be monitored over time, rather than as one single alert-triggering event, to monitor patterns and trends and to detect events more accurately.
Further, values may be monitored over time, rather than as one single alert-triggering event, to monitor patterns and trends and to detect events more accurately.
[0067] As an example of a "Alert" service that monitors over time, Figure 7 shows an "Over RPM" threshold alert example that detects if a vehicle driver is abusing the vehicle engine. In this example, the Over RPM threshold alert considers the amount of time that the RPM level exceeds a specified limit (6000 RPM in this example) rather than simply generating an alert each time the RPM exceeds the level.
The time delay ensures that alerts are generated only for events that may cause genuine concern.
The time delay ensures that alerts are generated only for events that may cause genuine concern.
[0068] As shovcm in Figure 7 if the RPM exceeds 6000 RPM for a brief period that is less than 2 seconds (at 702), the "Alert" service does not generate an alert.
However, if the RPM does exceed 6000 RPM for more than two seconds (at 704), the service fires an alert 707 and resets itself (at 708) when the RPM drops back below RPM. The actual circuitry for monitoring RPM and implementing this example of the "Alert" service in the system 100 (e.g., on the OBU 105) is well within the skill of those in the art. Further, the time delay concept shown in Figure 7 can be used for any parameter where undesirable operation is preferably detected via time and value thresholds.
However, if the RPM does exceed 6000 RPM for more than two seconds (at 704), the service fires an alert 707 and resets itself (at 708) when the RPM drops back below RPM. The actual circuitry for monitoring RPM and implementing this example of the "Alert" service in the system 100 (e.g., on the OBU 105) is well within the skill of those in the art. Further, the time delay concept shown in Figure 7 can be used for any parameter where undesirable operation is preferably detected via time and value thresholds.
[0069] The "Alert" services may also include a tamper alert feature, as shown in Figure 8, that allows the user to monitor any unauthorized alteration of configurable parameters. This feature 800 generally contains a setup process 802 and a tamper check process 804. When a user requests the tamper alert service (block 806), OBU
105 captures the value of the parameter at the time of the request and saves the parameter value to a file in the OBU's memory (e.g., flash memory 315 or DRAM
316) at block 808. Note that this parameter retrieval process may involve using the "Parameters" service as explained above to query the ECU or other vehicle controller or component 308.
105 captures the value of the parameter at the time of the request and saves the parameter value to a file in the OBU's memory (e.g., flash memory 315 or DRAM
316) at block 808. Note that this parameter retrieval process may involve using the "Parameters" service as explained above to query the ECU or other vehicle controller or component 308.
[0070] The actual tamper check process is conducted when, for example, the vehicle is initially turned on. At this point, the OBU 105 checks the parameter again to get its current value at the time the vehicle ignition is turned on (block 810). If the current value is different than the saved value (block 812), a tamper alert message will be returned to the user (block 814). If the compared values are the same at block 812, however, the vehicle continues operation as usual without transmitting any tamper alert signal (block 816). In one embodiment, the user may add/remove individual tamper alerts, and the tamper alert may be cancelled at block -818 once the alert is fired.
[0071] A "Change Parameters" function may also be included as part of a configuration core service, as shown in Figure 9. This feature may allow a user to remotely insert or update, for example, a parameter or message definition in the vehicle. As shown in Figure 9, the function 850 includes receiving a parameter change request (block 852), receiving the specific parameter to be changed in the vehicle (block 854), changing the parameter (block 856), and saving the parameter in memory (block 858). In one embodiment, the updated parameter definitions are stored permanently in memory until the next change request. Further, in one embodiment, the updated definition takes effect as soon as the update is completed.
[0072] The core services can be accessed by one or more applications, as noted above. The system 100 may include the ability to leverage other services that it may or may not have, such as, Fuel Tax Reporting/State Line Crossing applications, Asset tracking/utilization programs, Driver Performance applications, On-line Vehicle Documentation, detailed mapping applications, etc. This flexibility, coupled with modular services and applications 108, 110 that can be added, subtracted, and combined at will, provides for a very flexible and adaptable platform.
Applications [0073] As described above, the system 100 allows users to customize their own vehicle monitoring, programming and diagnostics systems based on their own specialized needs by offering a plurality of applications that can be selected and combined in a modular fashion as desired by the user. The applications may include service offerings such as Remote Diagnostics, Fuel Economy, Trip Reporting, Automatic Vehicle Location based upon GPS or satellite based system information, and others. The applications listed here and described in greater detail below are only examples and are not meant to be limiting or comprehensive in any manner.
Those of skill in the art will understand that other applications may also be included as possible .
application options.
Applications [0073] As described above, the system 100 allows users to customize their own vehicle monitoring, programming and diagnostics systems based on their own specialized needs by offering a plurality of applications that can be selected and combined in a modular fashion as desired by the user. The applications may include service offerings such as Remote Diagnostics, Fuel Economy, Trip Reporting, Automatic Vehicle Location based upon GPS or satellite based system information, and others. The applications listed here and described in greater detail below are only examples and are not meant to be limiting or comprehensive in any manner.
Those of skill in the art will understand that other applications may also be included as possible .
application options.
[0074] A "Remote Diagnostics" application, for example, provides the ability to perform component analysis before or during a vehicle breakdown and allows vehicle maintenance locations to receive parametric information from a vehicle prior to its arrival, or prior to dispatching a technician to the vehicle. Further, the "Remote Diagnostics" application allows a technician to perform selected diagnostic tests on the vehicle or system, with the test process being managed by the OBU 105. In one embodiment, the "Remote Diagnostics" application allows a user to view parameters, active and inactive fault codes, and vehicle configurations, for example, and may also allow authorized users to perform functional tests and configuration changes on the vehicle. Remote Diagnostics may be initiated when, for example, a vehicle notifies the fleet based upon a series of established alerts or when the diagnostics are requested manually by a fleet authorized user. In practice, the application may provide diagnostic applications via the inventive system 100. When the user logs on to the system 100 via the interface 106, for example, he or she may be presented with a list of vehicles that have reported alerts or notifications that may need attention. If no alerts are active, the user is provided a list of vehicles for which he or she is responsible. At this point the user may elect to use a remote diagnostics application, such as the remote diagnostics application described below and shown in Figure 10, 912, to perform further analysis on the vehicle to determine the severity of the problem.
(0075] Figure 10 is a block diagram illustrating one possible overall web site architecture 900 that includes a remote diagnostics application. In this example, a user may log into the application (block 902) to reach an application home page 904.
From the home page, the user may access a range of information, such as fuel economy 906 or leased vehicle information 908 , or access utilities 910 or a remote diagnostics application (RDA) page 912 to monitor, diagnose, and/or reprogram vehicle parameters. In this example, the utilities 910 allow the user to define and/or modify vehicle groups 914, specific vehicles 916, and alerts 918. The RDA page provides users with access to, for example, vehicle information and parameters 920, including pages that allowing parameter viewing 922 and reprogramming 924.
Note that other architectures and implementations are possible for this application as well as other applications without departing from the scope of the invention.
From the home page, the user may access a range of information, such as fuel economy 906 or leased vehicle information 908 , or access utilities 910 or a remote diagnostics application (RDA) page 912 to monitor, diagnose, and/or reprogram vehicle parameters. In this example, the utilities 910 allow the user to define and/or modify vehicle groups 914, specific vehicles 916, and alerts 918. The RDA page provides users with access to, for example, vehicle information and parameters 920, including pages that allowing parameter viewing 922 and reprogramming 924.
Note that other architectures and implementations are possible for this application as well as other applications without departing from the scope of the invention.
[0076] A "Leased Vehicle Management" (LVM) application is another possible option to generate periodic status reports summarizing selected parameters for each vehicle in a fleet, such as total vehicle distance, total idle fuel, total idle time, total fuel used, and/or total fuel economy. Figure 11 is a block diagram illustrating one possible example architecture for the Leased Vehicle Management application 950.
In this example, the user reaches a main page 952 that allows the user to choose between a group details page 954 and the task details page 956. Crroup details correspond to all information for a selected vehicle group, while task details correspond to all information for a selected task. The group details page 954 may allow the user to, for example, create new tasks (e.g., the timing of data collection for a selected vehicle group) 958, generate a report list 960, or generate more detailed reports listing specifying, for example, parameter values for a selected report 962.
The task details page includes similar options, allowing the user to view reports for a selected task 964 and generate more detailed reports 966. The task details page 956 also allows a user to stop a task 968 or delete a task 970.
In this example, the user reaches a main page 952 that allows the user to choose between a group details page 954 and the task details page 956. Crroup details correspond to all information for a selected vehicle group, while task details correspond to all information for a selected task. The group details page 954 may allow the user to, for example, create new tasks (e.g., the timing of data collection for a selected vehicle group) 958, generate a report list 960, or generate more detailed reports listing specifying, for example, parameter values for a selected report 962.
The task details page includes similar options, allowing the user to view reports for a selected task 964 and generate more detailed reports 966. The task details page 956 also allows a user to stop a task 968 or delete a task 970.
[0077] An "Engine Management" application may also be an option to target fleets whose vehicles encounter varying road and traffic conditions, and varying load types and weights. The objective of the "Engine Management" application is to improve overall fleet fuel economy via dynamic control of a vehicle's operational characteristics, in particular, horsepower ratings and maximum road speed limits.
Traditionally such operating parameters have been established once at a fleet wide level, not taking into consideration some of the variables listed above. In addition, making these changes required physical contact with the vehicle, necessitating undesirable vehicle downtime. Dynamic adjustments based upon operating conditions can provide reductions in vehicle operational costs, thus resulting in significant savings at a fleet level. With this application the user will be able to dynamically configure the vehicle wherever it may be; tailoring its operational characteristics based upon route, load, and other vehicle operation factors.
The "Engine Management" application may include both measured parameters and programmable parameters. Examples of programmable parameters include Vehicle Road Speed Limit, Engine Horsepower/Torque, Engine Idle Shutdown Time and Cruise Control Settings.
Traditionally such operating parameters have been established once at a fleet wide level, not taking into consideration some of the variables listed above. In addition, making these changes required physical contact with the vehicle, necessitating undesirable vehicle downtime. Dynamic adjustments based upon operating conditions can provide reductions in vehicle operational costs, thus resulting in significant savings at a fleet level. With this application the user will be able to dynamically configure the vehicle wherever it may be; tailoring its operational characteristics based upon route, load, and other vehicle operation factors.
The "Engine Management" application may include both measured parameters and programmable parameters. Examples of programmable parameters include Vehicle Road Speed Limit, Engine Horsepower/Torque, Engine Idle Shutdown Time and Cruise Control Settings.
(0078] A "Trip Report" application may also be provided as an option. This application allows the fleet manager to obtain trip information from the vehicle on a near-real-time basis. The user can analyze trip information for single vehicles as well as any increment of their fleet. This application primarily uses measured parameters such as odometer readings, total trip fuel, idle fuel, average fuel economy, vehicle route taken, and others. It also uses some parameters to derive data, such as total idle hours and the type of idle hours recorded. The output from this application can also be used as input to the billing systems of leasing companies who charge customers based upon mileage.
[0079] A "Maintenance Alert" application allows the fleet manager to establish a series of maintenance triggers based upon key parameters. When a parameter threshold is encountered, the fleet manager will be notified automatically by the system, thus initiating a maintenance event without physical contact with the vehicle.
For example, a fleet may establish a preventive maintenance cycle based upon odometer reading. If the server 202 is made aware of the interval, it can notify the fleet of the precise moment when that interval occurs. Alerts may provide notification on parameters such as diagnostic codes, fluid levels and parameter ranges as well as unauthorized tampering with the vehicle.
For example, a fleet may establish a preventive maintenance cycle based upon odometer reading. If the server 202 is made aware of the interval, it can notify the fleet of the precise moment when that interval occurs. Alerts may provide notification on parameters such as diagnostic codes, fluid levels and parameter ranges as well as unauthorized tampering with the vehicle.
[0080] A "Vehicle Configuration" application may be offered to allow a fleet manager to set certain parameters for multiple vehicles in a fleet so that the selected vehicles will operate within its established standards. Examples of parameters include horsepower ratings, maximum road speed limits, maximum and minimum cruise control set speeds and maximum engine idle time before shutdown.
Traditionally, this step has required a physical connection of a diagnostic application or tool to the vehicle, but physical connections are time-consuming and require the same step to be repeated on every vehicle that is serviced. The wireless nature of the "Vehicle Configuration" application allows operational settings and alerts for several vehicles within a fleet at one time by allowing the user to identify selected vehicles, set parameters, and initiate an automated process where each vehicle is systematically configured with the same parameter settings.
Traditionally, this step has required a physical connection of a diagnostic application or tool to the vehicle, but physical connections are time-consuming and require the same step to be repeated on every vehicle that is serviced. The wireless nature of the "Vehicle Configuration" application allows operational settings and alerts for several vehicles within a fleet at one time by allowing the user to identify selected vehicles, set parameters, and initiate an automated process where each vehicle is systematically configured with the same parameter settings.
[0081] A "Warranty Management" application may also be offered as part of a data mining strategy used by, for example, original equipment manufacturers (OEMs) to help diagnose warranty relationships between major components or to assess warranty claims for validity. This application would, for example, obtain detailed vehicle data from the database server 202d, using both fleet specific and system-wide data mining, and then correlate the data with warranty requirements.
[0082] As noted above, the possible modular applications described herein are meant as illustrative examples only. Further, as noted above, the applications 108, accessed by the infrastructure 102 can be generated by third parties and offered as modules for incorporating into a particular user's interface 106 and accessing the OBU
105 and other system-supported core services and applications. The modular functionality offered by independent applications 108, 110 allows disparate users to access the same vehicle data via the same OBUs 105 and the same infrastructure 102, but be offered customized data, functionalities, and interfaces that are meaningful to that user's industry as determined by the particular modular applications selected by the user. The specific manner for implementing the applications via, for example, computer programs, is within those of skill in the art.
105 and other system-supported core services and applications. The modular functionality offered by independent applications 108, 110 allows disparate users to access the same vehicle data via the same OBUs 105 and the same infrastructure 102, but be offered customized data, functionalities, and interfaces that are meaningful to that user's industry as determined by the particular modular applications selected by the user. The specific manner for implementing the applications via, for example, computer programs, is within those of skill in the art.
[0083] The inventive system therefore provides a modular wireless vehicle diagnostics, command and control system that is customizable to a user's specifications. More particularly, the modular applications 108, 110 provide much versatility and allow users from disparate industries to use the same overall inventive system 100 by selecting the applications 108, 110 relevant to their particular industry.
Further, by creating a wireless diagnostics and command and control service, the invention provides real-time remote access to vehicles and vehicle systems via, for example, the Internet and wireless networks. In one embodiment, the inventive system allows users to connect to multiple data points on any given vehicle to interpret and analyze the vehicle data in real time, change vehicle parameters as needed and create historical databases to guide future decisions. Further, by monitoring vehicle operation in real time and providing customized reports for each vehicle, the inventive system achieves high operating efficiency, lowered maintenance costs and downtime, and even allows pre-ordering of parts as vehicles approach scheduled maintenance.
Further, by creating a wireless diagnostics and command and control service, the invention provides real-time remote access to vehicles and vehicle systems via, for example, the Internet and wireless networks. In one embodiment, the inventive system allows users to connect to multiple data points on any given vehicle to interpret and analyze the vehicle data in real time, change vehicle parameters as needed and create historical databases to guide future decisions. Further, by monitoring vehicle operation in real time and providing customized reports for each vehicle, the inventive system achieves high operating efficiency, lowered maintenance costs and downtime, and even allows pre-ordering of parts as vehicles approach scheduled maintenance.
[0084] Note that the capabilities described above are meant to be illustrative and not limiting. The system 100 can be adapted to, for example, establish a setting that is applied to selected group of vehicles with a single command rather than individually establishing a setting for each vehicle. The aspects of the request, including authorization, vehicle/component differences, password differences, and configuration limitations of the specific request, may be managed by,.for example, the server 202. In another embodiment, the system 100 can view each vehicle 104 as a single entity to allow the user to communicate with multiple ECU's on the same vehicle 104 at the same time. For example, data can be obtained from an Engine ECU
and Transmission ECU at the same time, with the resultant data from each controller correlated to the other to add more detail to the data offered to the user.
and Transmission ECU at the same time, with the resultant data from each controller correlated to the other to add more detail to the data offered to the user.
[0085] Variations of the system described above are possible without departing from the scope of the invention. For example, selected applications may be run locally on proprietary equipment owned by the customers (i.e., the fleet managers, vehicle distributors, vehicle dealers and the like) as a stand alone software application instead of over the Internet. Further, the OBU 105 can be equipped with, for example, a bar code scanner and/or other human user interface to facilitate data capture.
Other user interfaces and functions, such as a handheld diagnostics tool, workflow integration tool, links between data captured by different applications, and tools to provide advance warning of vehicle faults or pre-arrival diagnostics information may also be included as application modules or core services or even integrated within the application modules themselves. Note that one or more additional servers can also be incorporated into the system to, for example, accommodate additional data management functions and/or provide interfaces for integrating with existing applications.
Other user interfaces and functions, such as a handheld diagnostics tool, workflow integration tool, links between data captured by different applications, and tools to provide advance warning of vehicle faults or pre-arrival diagnostics information may also be included as application modules or core services or even integrated within the application modules themselves. Note that one or more additional servers can also be incorporated into the system to, for example, accommodate additional data management functions and/or provide interfaces for integrating with existing applications.
[0086] Information obtained via the inventive system can also be used to, for example, re-calibrate vehicle components, perform firmware downloads, perform component failure analysis, determine wear characteristics, analyze quality of components used in their manufacturing processes, retrieve and manage warranty information, receive indications of vehicle maintenance needs, monitor vehicle use and abuse, and/or monitor lessee trip information, perform proactive data analysis, perform pre-arrival diagnostics, re-calibrate vehicle components, and/or perform firmware downloads. Note that this list of options is not exhaustive and those of skill in the art will understand that other variations in the data obtained via the inventive system and how the data is presented and used can vary without departing from the scope of the invention.
[0087] ~It should be understood that various alternatives to the embodiments of the invention described herein may be employed in practicing the invention. It is intended that the following claims define the scope of the invention and that the method and apparatus within the scope of these claims and their equivalents be covered thereby.
Claims (44)
1. A system for monitoring, configuring, programming and/or diagnosing operation of at least one vehicle, comprising:
an on-board unit disposed on the vehicle to send and receive data corresponding to at least one vehicle operating characteristic;
a plurality of modular applications, each application having an associated function that processes the data corresponding to said at least one vehicle operating characteristic obtained via the on-board unit; and an interface that allows selection among the plurality of modular applications to create a customized system.
an on-board unit disposed on the vehicle to send and receive data corresponding to at least one vehicle operating characteristic;
a plurality of modular applications, each application having an associated function that processes the data corresponding to said at least one vehicle operating characteristic obtained via the on-board unit; and an interface that allows selection among the plurality of modular applications to create a customized system.
2. The system of claim 1, wherein the on-board unit includes:
at least one on-board unit interface to support communication between the on-board unit and at least one device outside the on-board unit;
a processor that manages the data sent and received by the on-board unit via said at least one interface; and a memory coupled to the processor.
at least one on-board unit interface to support communication between the on-board unit and at least one device outside the on-board unit;
a processor that manages the data sent and received by the on-board unit via said at least one interface; and a memory coupled to the processor.
3. The system of claim 2, wherein said at least one on-board unit interface is at least one selected from the group consisting of a wireless interface that supports communication with a wireless communication system;
a vehicle interface that supports communication with at least one vehicle component via a vehicle data bus;
a user interface that supports communication with a user;
a serial interface that supports communication with at least one of a driver interface and an on-vehicle device; and a global positioning interface that supports communication with a global positioning system (GPS) device.
a vehicle interface that supports communication with at least one vehicle component via a vehicle data bus;
a user interface that supports communication with a user;
a serial interface that supports communication with at least one of a driver interface and an on-vehicle device; and a global positioning interface that supports communication with a global positioning system (GPS) device.
4. The system of claim 3, wherein the vehicle interface includes at least one selected from the group consisting of:
a data parser/requester module that handles non-application specific interfacing between the processor and the vehicle data bus; and an application specific module coupled to the data parser/requestor module that handles application specific interfacing between the processor and the vehicle data bus.
a data parser/requester module that handles non-application specific interfacing between the processor and the vehicle data bus; and an application specific module coupled to the data parser/requestor module that handles application specific interfacing between the processor and the vehicle data bus.
5. The system of claim 1, wherein the modular applications are selected from the group consisting of third-party applications, system-supplied applications, and core services.
6. The system of claim 5, wherein at least one of the third-party applications and system-supplied applications function using information from at least one core service.
7. The system of claim 5, wherein the core services include a snapshot service that obtains a set of vehicle parameter values over time.
8. The system of claim 7, wherein the snapshot service causes the on-board unit to cache a selected number of parameter readings with respect to a triggering event.
9. The system of claim 8, wherein the on-board unit caches the selected number of parameter readings by storing a plurality of parameter readings at selected time intervals.
10. The system of claim 5, wherein the core services include a get stored values service that outputs at least one vehicle controller value in response to a request, wherein the get stored values service outputs a current vehicle controller value if the vehicle controller is available at the time of the request and output a stored vehicle controller value in the on-board unit if the vehicle controller is not available at the time of the request.
11. The system of claim 10, wherein the get stored values service collects vehicle controller values at a selected time interval and stores a most recent vehicle controller value as the current vehicle controller value.
12. The system of claim 5, wherein the core services include an alert service that detects at least one of a solicited fault and an unsolicited fault.
13. The system of claim 12, wherein the alert service detects a solicited fault by filtering faults and outputting only faults solicited by a user.
14. The system of claim 12, wherein the alert service includes at least one of the functions from the group consisting of adding and removing individual faults, cancelling the alert service for a given fault after an alert has been fired, firing an alert after a parameter exceeds a selected threshold for a selected time period, and comparing a saved parameter with a current parameter to detect tampering.
15. The system of claim 5, wherein the core services include a change parameter service that changes at least one vehicle parameter in response to a request.
16. The system of claim 1, wherein the interface is at least one selected from the group consisting of:
a user interface that supports interaction with a human user; and a machine-to-machine interface.
a user interface that supports interaction with a human user; and a machine-to-machine interface.
17. The system of claim 16, wherein the user interface is a graphical user interface.
18. The system of claim 1, further comprising a server linking the on-board unit to the interface via the modular applications.
19. The system of claim 18, wherein the server includes at least one of the group consisting of:
a web/application server containing logic defining the modular applications;
a vehicle server that acts as a translator between the modular applications and the on-board unit;
a communications server to support communication via a wireless network;
and a database server containing at least one relational data table retaining information associated with the vehicle.
a web/application server containing logic defining the modular applications;
a vehicle server that acts as a translator between the modular applications and the on-board unit;
a communications server to support communication via a wireless network;
and a database server containing at least one relational data table retaining information associated with the vehicle.
20. The system of claim 18, wherein at least one of the server and the modular applications form an application service provider (ASP) infrastructure.
21. The system of claim 1, wherein the plurality of modular applications include a remote diagnostics application.
22. The system of claim 1, wherein the plurality of modular applications include a leased vehicle management application.
23. The system of claim 1, wherein the plurality of modular applications includes at least one from the group consisting of a remote diagnostics application, a leased vehicle management application, a fuel economy application, a vehicle locating application, a trip reporting application, an engine management application, a maintenance alert application, a vehicle configuration application, and a warranty management application.
24. The system of claim 1, wherein at least one of the plurality of modular applications correlates data between at least two vehicle controllers on the same vehicle.
25. The system of claim 1, wherein at least one of the plurality of modular applications establishes a setting for a plurality of vehicles with one command sent via the interface.
26. An on-board unit disposed on a vehicle for use in a system for monitoring, configuring, programming and/or diagnosing operation of at least one vehicle, comprising:
at least one on-board unit interface to support communication between the on-board unit and at least one device outside the on-board unit;
a processor that manages the data sent and received by the on-board unit via said at least one interface; and a memory coupled to the processor.
at least one on-board unit interface to support communication between the on-board unit and at least one device outside the on-board unit;
a processor that manages the data sent and received by the on-board unit via said at least one interface; and a memory coupled to the processor.
27. The on-board unit of claim 26, wherein said at least one on-board unit interface is at least one selected from the group consisting of:
a wireless interface that supports communication with a wireless communication system;
a vehicle interface that supports communication with at least one vehicle component via a vehicle data bus;
an on-board user interface that supports communication with a user;
a serial interface that supports communication with at least one of a driver interface and an on-vehicle device; and a global positioning interface that supports communication with a global positioning system (GPS) device.
a wireless interface that supports communication with a wireless communication system;
a vehicle interface that supports communication with at least one vehicle component via a vehicle data bus;
an on-board user interface that supports communication with a user;
a serial interface that supports communication with at least one of a driver interface and an on-vehicle device; and a global positioning interface that supports communication with a global positioning system (GPS) device.
28. The on-board unit of claim 27, wherein the vehicle interface includes at least one selected from the group consisting of:
a data parser/requester module that handles non-application specific interfacing between the processor and the vehicle data bus; and an application specific module coupled to the data parser/requestor module that handles application specific interfacing between the processor and the vehicle data bus.
a data parser/requester module that handles non-application specific interfacing between the processor and the vehicle data bus; and an application specific module coupled to the data parser/requestor module that handles application specific interfacing between the processor and the vehicle data bus.
29. A method for monitoring, configuring, programming and/or diagnosing operation of at least one vehicle, comprising:
obtaining data corresponding to at least one vehicle operating characteristic from an on-board unit on the vehicle;
providing a plurality of modular applications that are selectable by the user to create a customized system; and processing the data corresponding to at least one vehicle operating characteristic obtained via the on-board unit according to at least one function associated with at least one selected modular application.
obtaining data corresponding to at least one vehicle operating characteristic from an on-board unit on the vehicle;
providing a plurality of modular applications that are selectable by the user to create a customized system; and processing the data corresponding to at least one vehicle operating characteristic obtained via the on-board unit according to at least one function associated with at least one selected modular application.
30. The method of claim 29, further comprising obtaining a set of vehicle parameter values over time.
31. The method of claim 30, wherein the obtaining step includes:
detecting a triggering event; and caching a selected number of parameter readings with respect to a triggering event.
detecting a triggering event; and caching a selected number of parameter readings with respect to a triggering event.
32. The method of claim 31, wherein the caching step includes storing a plurality of parameter readings at selected time intervals.
33. The method of claim 29, further comprising:
detecting a request for a vehicle controller value;
outputting a current vehicle controller value if a vehicle controller is available at the time of the request; and output a stored vehicle controller value if the vehicle controller is not available at the time of the request.
detecting a request for a vehicle controller value;
outputting a current vehicle controller value if a vehicle controller is available at the time of the request; and output a stored vehicle controller value if the vehicle controller is not available at the time of the request.
34. The method of claim 33, further comprising collecting vehicle controller values at a selected time interval and storing a most recent vehicle controller value as the current vehicle controller value.
35. The method of claim 29, further comprising:
detecting at least one of a solicited fault and an unsolicited fault; and firing an alert after the detecting step.
detecting at least one of a solicited fault and an unsolicited fault; and firing an alert after the detecting step.
36. The method of claim 35, wherein detecting a solicited fault includes filtering faults to output only faults solicited by a user.
37. The method of claim 35, further comprising at least one step selected from the group consisting of adding and removing individual faults, cancelling the alert service for a given fault after an alert has been fired, firing an alert after a parameter exceeds a selected threshold for a selected time period, and comparing a saved parameter with a current parameter to detect tampering.
38. The method of claim 29, further comprising changing at least one vehicle parameter in response to a request.
39. The method of claim 29, further comprising translating data between the modular applications and the on-board unit.
40. The method of claim 29, wherein the providing step includes providing a remote diagnostics application.
41. The method of claim 29, wherein the providing step includes providing a leased vehicle management application.
42. The method of claim 29, wherein the providing step provides at least one from the group consisting of a remote diagnostics application, a leased vehicle management application, a fuel economy application, a vehicle locating application, a trip reporting application, an engine management application, a maintenance alert application, a vehicle configuration application, and a warranty management application.
43. The method of claim 29, further comprising correlating data between at least two vehicle controllers on the same vehicle.
44. The method of claim 29, wherein at least one of the plurality of modular applications establishes a setting for a plurality of vehicles with one command sent via the interface.
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/091,096 US7092803B2 (en) | 2000-08-18 | 2002-03-04 | Remote monitoring, configuring, programming and diagnostic system and method for vehicles and vehicle components |
US10/091,096 | 2002-03-04 | ||
PCT/US2003/006475 WO2003077205A2 (en) | 2002-03-04 | 2003-03-03 | Remote monitoring, configuring, programming and diagnostic system and method for vehicles and vehicle components |
Publications (1)
Publication Number | Publication Date |
---|---|
CA2478176A1 true CA2478176A1 (en) | 2003-09-18 |
Family
ID=27804098
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002478176A Abandoned CA2478176A1 (en) | 2002-03-04 | 2003-03-03 | Remote monitoring, configuring, programming and diagnostic system and method for vehicles and vehicle components |
Country Status (7)
Country | Link |
---|---|
US (2) | US7092803B2 (en) |
EP (1) | EP1485878A2 (en) |
JP (1) | JP2005520725A (en) |
AU (1) | AU2003224647A1 (en) |
CA (1) | CA2478176A1 (en) |
TW (1) | TWI237758B (en) |
WO (1) | WO2003077205A2 (en) |
Families Citing this family (308)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8140358B1 (en) | 1996-01-29 | 2012-03-20 | Progressive Casualty Insurance Company | Vehicle monitoring system |
US8090598B2 (en) | 1996-01-29 | 2012-01-03 | Progressive Casualty Insurance Company | Monitoring system for determining and communicating a cost of insurance |
US20020173885A1 (en) | 2001-03-13 | 2002-11-21 | Lowrey Larkin Hill | Internet-based system for monitoring vehicles |
US7092803B2 (en) * | 2000-08-18 | 2006-08-15 | Idsc Holdings, Llc | Remote monitoring, configuring, programming and diagnostic system and method for vehicles and vehicle components |
WO2004093409A2 (en) * | 2003-04-11 | 2004-10-28 | Nnt, Inc. | Wireless communication framework |
US20060025907A9 (en) * | 2000-08-18 | 2006-02-02 | Nnt, Inc. | Vehicle-interactive system |
US7079982B2 (en) * | 2001-05-08 | 2006-07-18 | Hitachi Construction Machinery Co., Ltd. | Working machine, trouble diagnosis system of working machine, and maintenance system of working machine |
US7155321B2 (en) | 2001-08-06 | 2006-12-26 | Idsc Holdings Llc | System, method and computer program product for remote vehicle diagnostics, monitoring, configuring and reprogramming |
JP2003122426A (en) * | 2001-10-16 | 2003-04-25 | Keihin Corp | Remote maintenance system |
US20030093199A1 (en) * | 2001-11-15 | 2003-05-15 | Michael Mavreas | Remote monitoring and control of a motorized vehicle |
US20030162523A1 (en) * | 2002-02-27 | 2003-08-28 | Michael Kapolka | Vehicle telemetry system and method |
US7957509B2 (en) * | 2002-04-30 | 2011-06-07 | At&T Intellectual Property I, L.P. | Voice enhancing for advance intelligent network services |
US7325135B2 (en) * | 2002-06-28 | 2008-01-29 | Temic Automotive Of North America, Inc. | Method and system for authorizing reconfiguration of a vehicle |
US7356393B1 (en) * | 2002-11-18 | 2008-04-08 | Turfcentric, Inc. | Integrated system for routine maintenance of mechanized equipment |
JP3828484B2 (en) * | 2002-11-29 | 2006-10-04 | 株式会社ザナヴィ・インフォマティクス | Data access method and data access apparatus for in-vehicle information equipment |
KR100636513B1 (en) * | 2002-12-19 | 2006-10-18 | 인터내셔널 비지네스 머신즈 코포레이션 | Tcet expander |
PT1608935E (en) * | 2003-02-26 | 2007-12-31 | Tomtom Int Bv | Navigation device and method for displaying simulated navigation data |
US7415243B2 (en) | 2003-03-27 | 2008-08-19 | Honda Giken Kogyo Kabushiki Kaisha | System, method and computer program product for receiving data from a satellite radio network |
US7421334B2 (en) * | 2003-04-07 | 2008-09-02 | Zoom Information Systems | Centralized facility and intelligent on-board vehicle platform for collecting, analyzing and distributing information relating to transportation infrastructure and conditions |
JP2004322740A (en) * | 2003-04-22 | 2004-11-18 | Toyota Motor Corp | Failure diagnosis device for vehicular control device |
US7209813B2 (en) | 2003-05-13 | 2007-04-24 | Spx Corporation | Cellular phone configured with off-board device capabilities and starter/charger and battery testing capabilities |
EP1652128B1 (en) * | 2003-07-07 | 2014-05-14 | Insurance Services Office, Inc. | Traffic information system |
US7113127B1 (en) * | 2003-07-24 | 2006-09-26 | Reynolds And Reynolds Holdings, Inc. | Wireless vehicle-monitoring system operating on both terrestrial and satellite networks |
US9520005B2 (en) | 2003-07-24 | 2016-12-13 | Verizon Telematics Inc. | Wireless vehicle-monitoring system |
US7349794B2 (en) * | 2003-09-03 | 2008-03-25 | Malone Specialty, Inc. | Engine protection system |
CN101409726A (en) * | 2003-10-08 | 2009-04-15 | 通用汽车公司 | Captured test fleet |
US7225064B2 (en) * | 2003-10-31 | 2007-05-29 | Snap-On Technologies, Inc. | Wireless communication for diagnostic instrument |
US7487019B2 (en) * | 2003-12-12 | 2009-02-03 | United States Postal Service | Intelligent vehicle fleet systems and methods |
US7818380B2 (en) * | 2003-12-15 | 2010-10-19 | Honda Motor Co., Ltd. | Method and system for broadcasting safety messages to a vehicle |
US8041779B2 (en) * | 2003-12-15 | 2011-10-18 | Honda Motor Co., Ltd. | Method and system for facilitating the exchange of information between a vehicle and a remote location |
US7584029B2 (en) * | 2003-12-31 | 2009-09-01 | Teradyne, Inc. | Telematics-based vehicle data acquisition architecture |
US20060030983A1 (en) * | 2004-01-06 | 2006-02-09 | Textron Inc. | Apparatus and methods for facilitating vehicle maintenance |
WO2005072458A2 (en) * | 2004-01-28 | 2005-08-11 | Delorme Publishing Company, Inc. | Method and device for processing raw gps data |
US7020545B2 (en) * | 2004-01-28 | 2006-03-28 | General Motors Corporation | Method and system for managing registration requests of telematics units |
DE102004015163A1 (en) * | 2004-02-13 | 2005-08-25 | Volkswagen Ag | Vehicle diagnosis procedure uses processor to filter operating and failure data against manufacturer supplied data |
JP4370960B2 (en) * | 2004-03-29 | 2009-11-25 | 三菱自動車エンジニアリング株式会社 | Vehicle inspection management system |
JP4306510B2 (en) * | 2004-03-29 | 2009-08-05 | 三菱自動車エンジニアリング株式会社 | Vehicle inspection management system |
EP1733513A4 (en) | 2004-04-06 | 2009-05-06 | Honda Motor Co Ltd | Method and system for controlling the exchange of vehicle related messages |
JP4270017B2 (en) * | 2004-04-15 | 2009-05-27 | 三菱自動車工業株式会社 | Vehicle inspection management system |
SE527692C2 (en) * | 2004-05-12 | 2006-05-09 | Hans Ekdahl Med Hg Ekdahl Kons | Procedure in a communication network to distribute driving information for vehicles and systems implementing the procedure |
US7366589B2 (en) * | 2004-05-13 | 2008-04-29 | General Motors Corporation | Method and system for remote reflash |
US7877176B2 (en) * | 2004-06-24 | 2011-01-25 | General Motors Llc | Method and system for remote telltale reset |
US7518530B2 (en) * | 2004-07-19 | 2009-04-14 | Honda Motor Co., Ltd. | Method and system for broadcasting audio and visual display messages to a vehicle |
US7340331B2 (en) | 2004-08-12 | 2008-03-04 | Snap-On Incorporated | Vehicle data recorder using digital and analog diagnostic data |
US20060047419A1 (en) * | 2004-09-02 | 2006-03-02 | Diendorf John R | Telematic method and apparatus for managing shipping logistics |
US7643788B2 (en) * | 2004-09-22 | 2010-01-05 | Honda Motor Co., Ltd. | Method and system for broadcasting data messages to a vehicle |
JP4956894B2 (en) * | 2004-10-19 | 2012-06-20 | 三菱電機株式会社 | Communication terminal and storage medium removable from communication terminal |
DE102004055573A1 (en) * | 2004-11-18 | 2006-05-24 | Robert Bosch Gmbh | Diagnostic interface for applications on a service gateway |
US7272475B2 (en) * | 2004-12-02 | 2007-09-18 | General Motors Corporation | Method for updating vehicle diagnostics software |
US20060271255A1 (en) * | 2004-12-30 | 2006-11-30 | Teradyne, Inc. | System and method for vehicle diagnostics and prognostics |
EP1679867A1 (en) * | 2005-01-06 | 2006-07-12 | Orange SA | Customisation of VoiceXML Application |
US9601015B2 (en) | 2005-02-25 | 2017-03-21 | Concaten, Inc. | Maintenance decision support system and method for vehicular and roadside applications |
US7355509B2 (en) | 2005-02-25 | 2008-04-08 | Iwapi Inc. | Smart modem device for vehicular and roadside applications |
EP1705562A1 (en) * | 2005-03-18 | 2006-09-27 | Orange SA | Applications server and method of providing services |
US7165015B2 (en) * | 2005-03-29 | 2007-01-16 | Cryovac, Inc. | Handheld device for retrieving and analyzing data from an electronic monitoring device |
US7386377B2 (en) * | 2005-04-07 | 2008-06-10 | Sorensen David I | Vehicle and equipment monitoring apparatus |
WO2006122263A2 (en) * | 2005-05-11 | 2006-11-16 | Pinpoint Tracking Solutions, Llc | Method and apparatus for secure storage and remote monitoring vehicle odometer |
US7729824B2 (en) * | 2005-07-29 | 2010-06-01 | Gm Global Technology Operations, Inc. | Remote diagnostic system for detecting tampering of vehicle calibrations |
US20070050095A1 (en) * | 2005-09-01 | 2007-03-01 | Polaris Industries Inc. | Controller area network based self-configuring vehicle management system and method |
US20070109096A1 (en) * | 2005-09-08 | 2007-05-17 | Jeremy Breedlove | Global tracking and communications device |
US7920944B2 (en) * | 2005-10-21 | 2011-04-05 | General Motors Llc | Vehicle diagnostic test and reporting method |
US8255112B2 (en) * | 2005-10-28 | 2012-08-28 | The Boeing Company | Remote aircraft maintenance in a networked environment |
WO2008051236A2 (en) * | 2005-11-09 | 2008-05-02 | Sapias, Inc. | Geospatially aware vehicle security |
US8423430B2 (en) * | 2005-11-16 | 2013-04-16 | The Boeing Company | Integrated materials management for commercial aircraft fleets including access to real-time on-board systems information |
US10878646B2 (en) | 2005-12-08 | 2020-12-29 | Smartdrive Systems, Inc. | Vehicle event recorder systems |
US20070142940A1 (en) * | 2005-12-21 | 2007-06-21 | Ferguson Alan L | Processes for monitoring user-selected parameters |
KR20070108432A (en) * | 2006-01-23 | 2007-11-12 | 엘지전자 주식회사 | Method for scheduling device mangament |
US20070173993A1 (en) * | 2006-01-23 | 2007-07-26 | Nielsen Benjamin J | Method and system for monitoring fleet metrics |
US8594933B2 (en) * | 2006-02-09 | 2013-11-26 | Sap Ag | Transmission of sensor data based on geographical navigation data |
US20070192012A1 (en) * | 2006-02-14 | 2007-08-16 | Detroit Diesel Corporation | Method and system of enhanced vehicle road speed limiting |
US8996240B2 (en) | 2006-03-16 | 2015-03-31 | Smartdrive Systems, Inc. | Vehicle event recorders with integrated web server |
US20070250228A1 (en) * | 2006-04-19 | 2007-10-25 | Snap-On Incorporated | Configurable method and system for vehicle fault alert |
US10528705B2 (en) * | 2006-05-09 | 2020-01-07 | Apple Inc. | Determining validity of subscription to use digital content |
US20080005281A1 (en) * | 2006-06-29 | 2008-01-03 | Microsoft Corporation | Error capture and reporting in a distributed computing environment |
US20080016207A1 (en) * | 2006-07-14 | 2008-01-17 | Wesley Homer Cheng | Electronic driver log application with bi-directional messaging to multiple backend systems |
US20080082221A1 (en) * | 2006-07-14 | 2008-04-03 | David Nagy | System for monitoring, controlling, and reporting vehicle operation through onboard diagnostic port |
US20080015748A1 (en) * | 2006-07-14 | 2008-01-17 | David Nagy | System for monitoring, controlling, and reporting vehicle operation through onboard diagnostic port |
US20080016504A1 (en) * | 2006-07-14 | 2008-01-17 | Wesley Homer Cheng | Dynamically programmable electronic data collection system combining declarative programming and native coding |
US8850083B2 (en) * | 2006-07-26 | 2014-09-30 | Bosch Automotive Service Solutions, LLC | Data management method and system |
US7681201B2 (en) * | 2006-08-04 | 2010-03-16 | Lectronix | Method and system for integrating and controlling components and subsystems |
CA2659271A1 (en) * | 2006-08-04 | 2008-02-14 | Lectronix, Inc. | Method and system for integrating and controlling components and subsystems |
US20080059080A1 (en) * | 2006-08-31 | 2008-03-06 | Caterpillar Inc. | Method and system for selective, event-based communications |
US20080059005A1 (en) * | 2006-08-31 | 2008-03-06 | Jonny Ray Greiner | System and method for selective on-board processing of machine data |
US20080059339A1 (en) * | 2006-08-31 | 2008-03-06 | Gualandri J Joseph | Systems and methods for identifying attachments |
US7711522B2 (en) * | 2006-08-31 | 2010-05-04 | Caterpillar Inc. | Systems and methods for monitoring a machine |
US20080059411A1 (en) * | 2006-08-31 | 2008-03-06 | Caterpillar Inc. | Performance-based job site management system |
DE102006044896B3 (en) * | 2006-09-22 | 2008-04-10 | GM Global Technology Operations, Inc., Detroit | Remote manipulation diagnosis system for vehicle, has server assigned to distributed network information system and having access to service card index, where manipulation flag is maintained until access is made by server |
US7689594B2 (en) * | 2006-09-22 | 2010-03-30 | The Boeing Company | Vehicle management and mission management computer architecture and packaging |
US20080147571A1 (en) * | 2006-09-29 | 2008-06-19 | Caterpillar Inc. | System and method for analyzing machine customization costs |
US20080082345A1 (en) * | 2006-09-29 | 2008-04-03 | Caterpillar Inc. | System and method for evaluating risks associated with delaying machine maintenance |
US9747329B2 (en) | 2006-10-05 | 2017-08-29 | Trimble Inc. | Limiting access to asset management information |
US9519876B2 (en) | 2006-10-05 | 2016-12-13 | Trimble Navigation Limited | Method for providing maintenance to an asset |
US9811949B2 (en) | 2006-10-05 | 2017-11-07 | Trimble Inc. | Method for providing status information pertaining to an asset |
US9747571B2 (en) | 2006-10-05 | 2017-08-29 | Trimble Inc. | Integrated asset management |
US8989959B2 (en) | 2006-11-07 | 2015-03-24 | Smartdrive Systems, Inc. | Vehicle operator performance history recording, scoring and reporting systems |
US8649933B2 (en) | 2006-11-07 | 2014-02-11 | Smartdrive Systems Inc. | Power management systems for automotive video event recorders |
US8868288B2 (en) | 2006-11-09 | 2014-10-21 | Smartdrive Systems, Inc. | Vehicle exception event management systems |
EP3723053B1 (en) | 2006-12-13 | 2023-07-05 | Crown Equipment Corporation | Fleet management system |
US9984341B2 (en) * | 2006-12-13 | 2018-05-29 | Crown Equipment Corporation | Information system for industrial vehicles including cyclical recurring vehicle information message |
US11225404B2 (en) | 2006-12-13 | 2022-01-18 | Crown Equipment Corporation | Information system for industrial vehicles |
US10600256B2 (en) | 2006-12-13 | 2020-03-24 | Crown Equipment Corporation | Impact sensing usable with fleet management system |
US7869906B2 (en) * | 2007-01-08 | 2011-01-11 | Ford Global Technologies | Wireless gateway apparatus and method of bridging data between vehicle based and external data networks |
US8161454B2 (en) | 2007-01-22 | 2012-04-17 | Ford Motor Company | Software architecture for developing in-vehicle software applications |
US9392346B2 (en) * | 2007-02-14 | 2016-07-12 | Leica Geosystems Ag | System and method of remote diagnostics |
US20080270074A1 (en) * | 2007-04-30 | 2008-10-30 | Caterpillar Inc. | User customized machine data acquisition system |
US8050815B2 (en) * | 2007-05-02 | 2011-11-01 | General Motors Llc | Method and system for selectively monitoring vehicle systems and for controlling vehicle system parameters |
US8239092B2 (en) | 2007-05-08 | 2012-08-07 | Smartdrive Systems Inc. | Distributed vehicle event recorder systems having a portable memory data transfer system |
US20080281518A1 (en) * | 2007-05-10 | 2008-11-13 | Dozier Chad A | Vehicular communication and information system and method of using the same |
US8462793B2 (en) * | 2007-05-25 | 2013-06-11 | Caterpillar Inc. | System for strategic management and communication of data in machine environments |
US7668653B2 (en) | 2007-05-31 | 2010-02-23 | Honda Motor Co., Ltd. | System and method for selectively filtering and providing event program information |
US8275522B1 (en) | 2007-06-29 | 2012-09-25 | Concaten, Inc. | Information delivery and maintenance system for dynamically generated and updated data pertaining to road maintenance vehicles and other related information |
US9864957B2 (en) | 2007-06-29 | 2018-01-09 | Concaten, Inc. | Information delivery and maintenance system for dynamically generated and updated data pertaining to road maintenance vehicles and other related information |
DE102007038190B4 (en) * | 2007-08-13 | 2009-07-02 | Siemens Ag | Method for parameterizing a diagnostic device, corresponding computer program and computer program product, and diagnostic system |
JP4408921B2 (en) * | 2007-08-22 | 2010-02-03 | 株式会社デンソー | Electronics |
US8306560B2 (en) * | 2007-09-28 | 2012-11-06 | General Motors Llc | Method and system for configuring a telematics device using two-way data messaging |
US8099308B2 (en) * | 2007-10-02 | 2012-01-17 | Honda Motor Co., Ltd. | Method and system for vehicle service appointments based on diagnostic trouble codes |
US20090106036A1 (en) * | 2007-10-22 | 2009-04-23 | Kazuya Tamura | Method and system for making automated appointments |
US7925398B2 (en) * | 2007-10-31 | 2011-04-12 | Spx Corporation | Error message details for debug available to end user |
US8397228B2 (en) * | 2007-11-14 | 2013-03-12 | Continental Automotive Systems, Inc. | Systems and methods for updating device software |
DE102008025065A1 (en) * | 2007-12-21 | 2009-07-02 | Continental Automotive Gmbh | Method and system for transmitting data |
WO2009088946A1 (en) | 2008-01-03 | 2009-07-16 | Iwapi, Inc. | Integrated rail efficiency and safety support system |
US20090222338A1 (en) * | 2008-03-03 | 2009-09-03 | Hamilton Ii Rick A | Monitoring and Rewards Methodologies for "Green" Use of Vehicles |
JP4629750B2 (en) * | 2008-03-31 | 2011-02-09 | 日立オートモティブシステムズ株式会社 | Embedded control unit |
US9026304B2 (en) | 2008-04-07 | 2015-05-05 | United Parcel Service Of America, Inc. | Vehicle maintenance systems and methods |
JP5163248B2 (en) * | 2008-04-10 | 2013-03-13 | トヨタ自動車株式会社 | Vehicle group running control system |
US9650233B2 (en) * | 2008-04-18 | 2017-05-16 | The Raymond Corporation | Method for operating an industrial vehicle to manage energy costs |
US8301330B2 (en) * | 2008-05-02 | 2012-10-30 | General Electric Company | Method and system for providing supplemental services to telematics systems |
US20090274263A1 (en) * | 2008-05-05 | 2009-11-05 | Collins Michael P | Run-Time Meter With Blind Interface |
US8909466B2 (en) * | 2008-08-01 | 2014-12-09 | Environmental Systems Research Institute, Inc. | System and method for hybrid off-board navigation |
US20100042287A1 (en) * | 2008-08-12 | 2010-02-18 | Gm Global Technology Operations, Inc. | Proactive vehicle system management and maintenance by using diagnostic and prognostic information |
US8521547B2 (en) * | 2008-10-30 | 2013-08-27 | International Business Machines Corporation | Mechanic certification tracking validator |
US9305288B2 (en) * | 2008-12-30 | 2016-04-05 | Ford Global Technologies, Llc | System and method for provisioning electronic mail in a vehicle |
US20100190439A1 (en) * | 2009-01-29 | 2010-07-29 | Ford Global Technologies, Llc | Message transmission protocol for service delivery network |
US8095261B2 (en) * | 2009-03-05 | 2012-01-10 | GM Global Technology Operations LLC | Aggregated information fusion for enhanced diagnostics, prognostics and maintenance practices of vehicles |
US20100250881A1 (en) * | 2009-03-31 | 2010-09-30 | Joseph Bernard Steffler | Systems and method for data recovery |
CA2757453C (en) * | 2009-04-03 | 2020-02-18 | Crown Equipment Corporation | Information system for industrial vehicles |
US20100270859A1 (en) * | 2009-04-24 | 2010-10-28 | Zhengda Gong | Distributed Ultracapacitor Monitoring System Based on iCAN Protocol |
JP5819288B2 (en) * | 2009-05-11 | 2015-11-24 | マヒンドラ レバ エレクトリック ビークルズ プライベート リミテッド | System and method for monitoring and controlling energy systems |
US9916625B2 (en) | 2012-02-02 | 2018-03-13 | Progressive Casualty Insurance Company | Mobile insurance platform system |
US8135804B2 (en) * | 2009-07-07 | 2012-03-13 | Honda Motor Co., Ltd. | Method for scheduling and rescheduling vehicle service appointments |
DE102009038035A1 (en) * | 2009-08-19 | 2011-02-24 | Bayerische Motoren Werke Aktiengesellschaft | Method for configuring infotainment applications in a motor vehicle |
JP5208074B2 (en) * | 2009-08-27 | 2013-06-12 | 日立建機株式会社 | Remote management system for work machines |
RU2547708C2 (en) * | 2009-09-01 | 2015-04-10 | Краун Эквайпмент Корпорейшн | Information system for industrial machines, including cyclically repeating information machine reporting |
GB201013128D0 (en) * | 2009-09-24 | 2010-09-22 | Barloworld Handling Ltd | Maintence control system |
US20110083128A1 (en) * | 2009-10-02 | 2011-04-07 | International Truck Intellectual Property Company, Llc | Method for selecting software and installing same via a telematic module in a motor vehicle |
WO2011078748A1 (en) * | 2009-12-22 | 2011-06-30 | Volvo Lastvagnar Ab | Driver notification system and method |
CA2726124A1 (en) * | 2009-12-31 | 2011-06-30 | Trapeze Software Inc. | System and method for analyzing performance data in a transit organization |
US20110225228A1 (en) * | 2010-03-11 | 2011-09-15 | Ford Global Technologies, Llc | Method and systems for queuing messages for vehicle-related services |
US8902081B2 (en) | 2010-06-02 | 2014-12-02 | Concaten, Inc. | Distributed maintenance decision and support system and method |
EP2393048A1 (en) * | 2010-06-04 | 2011-12-07 | BAE Systems Bofors AB | Service platform system architecture for fleet maintenance and management |
EP2393049A1 (en) * | 2010-06-04 | 2011-12-07 | BAE Systems Bofors AB | On-board service platform and services for fleet maintenance and management |
EP2393050A1 (en) * | 2010-06-04 | 2011-12-07 | BAE Systems Bofors AB | Central service platform and services for fleet maintenance and management |
US9464905B2 (en) | 2010-06-25 | 2016-10-11 | Toyota Motor Engineering & Manufacturing North America, Inc. | Over-the-air vehicle systems updating and associate security protocols |
US8751100B2 (en) | 2010-08-13 | 2014-06-10 | Deere & Company | Method for performing diagnostics or software maintenance for a vehicle |
US8718632B2 (en) | 2010-08-26 | 2014-05-06 | Ford Global Technologies, Llc | Service delivery network |
CN103080719B (en) * | 2010-09-10 | 2016-04-06 | 迪尔公司 | For the method and system of the diagnosis or software maintenance that perform vehicle |
US10719813B1 (en) | 2010-09-29 | 2020-07-21 | Bluelink Diagnostic Solutions, Inc. | Remote diagnostic system for vehicles |
US8726188B2 (en) | 2010-10-29 | 2014-05-13 | Nissan North America, Inc. | Method for presenting information to a host vehicle having a user interface |
US20120110466A1 (en) * | 2010-10-29 | 2012-05-03 | Nissan North America, Inc. | Method for presenting information to a host vehicle having a user interface |
US8688313B2 (en) * | 2010-12-23 | 2014-04-01 | Aes Technologies, Llc. | Remote vehicle programming system and method |
US8863256B1 (en) * | 2011-01-14 | 2014-10-14 | Cisco Technology, Inc. | System and method for enabling secure transactions using flexible identity management in a vehicular environment |
US8751777B2 (en) | 2011-01-28 | 2014-06-10 | Honeywell International Inc. | Methods and reconfigurable systems to optimize the performance of a condition based health maintenance system |
US11197330B2 (en) | 2016-06-19 | 2021-12-07 | Platform Science, Inc. | Remote profile manage for a vehicle |
US11330644B2 (en) | 2016-06-19 | 2022-05-10 | Platform Science, Inc. | Secure wireless networks for vehicle assigning authority |
US10475258B1 (en) | 2016-06-19 | 2019-11-12 | Platform Science, Inc. | Method and system for utilizing vehicle odometer values and dynamic compliance |
US11197329B2 (en) | 2016-06-19 | 2021-12-07 | Platform Science, Inc. | Method and system for generating fueling instructions for a vehicle |
US10652935B1 (en) | 2016-06-19 | 2020-05-12 | Platform Science, Inc. | Secure wireless networks for vehicles |
US20160246296A1 (en) * | 2011-03-11 | 2016-08-25 | Intelligent Agricultural Solutions, Llc | Gateway system and method |
US10321624B2 (en) | 2011-03-11 | 2019-06-18 | Intelligent Agriculture Solutions LLC | Air seeder manifold system |
US10318138B2 (en) | 2011-03-11 | 2019-06-11 | Intelligent Agricultural Solutions Llc | Harvesting machine capable of automatic adjustment |
US8788139B2 (en) * | 2011-03-21 | 2014-07-22 | Webtech Wireless Inc. | Multi-protocol vehicle diagnostic interface device and method |
US8615773B2 (en) | 2011-03-31 | 2013-12-24 | Honeywell International Inc. | Systems and methods for coordinating computing functions to accomplish a task using a configuration file and standardized executable application modules |
WO2012160667A1 (en) * | 2011-05-25 | 2012-11-29 | トヨタ自動車株式会社 | Vehicle information acquiring apparatus, vehicle information supplying apparatus, and information communicating system of vehicle having vehicle information acquiring apparatus and vehicle information supplying apparatus |
US8990770B2 (en) | 2011-05-25 | 2015-03-24 | Honeywell International Inc. | Systems and methods to configure condition based health maintenance systems |
DE102011076638A1 (en) * | 2011-05-27 | 2012-11-29 | Stephan Kaufmann | A method of vehicle communication via a vehicle-implemented vehicle diagnostic system, interface module and vehicle diagnostic interface and diagnostic and control network for a plurality of vehicles |
CN103718218B (en) | 2011-07-26 | 2016-10-05 | 美国联合包裹服务公司 | For managing the system and method for failure code |
JP5807990B2 (en) * | 2011-09-22 | 2015-11-10 | アイトーン、インコーポレイテッド | Monitoring, diagnostic and tracking tools for autonomous mobile robots |
US9183273B2 (en) | 2011-09-23 | 2015-11-10 | Omnitracs, Llc | Systems and methods for processing location-and entity-based workflow data |
US8726084B2 (en) * | 2011-10-14 | 2014-05-13 | Honeywell International Inc. | Methods and systems for distributed diagnostic reasoning |
KR101283051B1 (en) * | 2011-11-25 | 2013-07-05 | 엘에스산전 주식회사 | Method of managing program for electric vehicle |
US20130170107A1 (en) * | 2012-01-04 | 2013-07-04 | Doug Dean | Enclosure for Preventing Tampering of Mobile Communication Equipment in Transportation Industry |
SE536394C2 (en) * | 2012-01-13 | 2013-10-08 | Scania Cv Ab | System and method for providing diagnostic error information based on content from two databases |
US8744668B2 (en) * | 2012-05-09 | 2014-06-03 | Bosch Automotive Service Solutions Llc | Automotive diagnostic server |
JP5613721B2 (en) * | 2012-05-18 | 2014-10-29 | 株式会社日立製作所 | Test support system, test support method, and program |
US8832649B2 (en) | 2012-05-22 | 2014-09-09 | Honeywell International Inc. | Systems and methods for augmenting the functionality of a monitoring node without recompiling |
JP5795287B2 (en) * | 2012-05-23 | 2015-10-14 | 株式会社堀場製作所 | Test system |
EP2696186B1 (en) * | 2012-05-24 | 2019-03-27 | Horiba, Ltd. | Test system |
DE102012010704A1 (en) | 2012-05-30 | 2012-11-29 | Daimler Ag | Method for outputting information, particularly maintenance requests in vehicle, involves transmitting output processed information by employer to vehicle, where appropriate time for output of information is determined by scheduler |
US8832716B2 (en) | 2012-08-10 | 2014-09-09 | Honeywell International Inc. | Systems and methods for limiting user customization of task workflow in a condition based health maintenance system |
US11030560B1 (en) | 2012-10-31 | 2021-06-08 | Brandt Vx Llc | Dispatch system |
US9858809B2 (en) * | 2012-11-08 | 2018-01-02 | Qualcomm Incorporated | Augmenting handset sensors with car sensors |
US9087193B2 (en) * | 2012-11-13 | 2015-07-21 | Gogo Llc | Communication system and method for nodes associated with a vehicle |
DE112012007197T5 (en) | 2012-12-05 | 2015-08-20 | Bendix Commercial Vehicle Systems Llc | Method and apparatus for updating software components in coordination with operating conditions of a motor vehicle |
US8948996B2 (en) * | 2012-12-20 | 2015-02-03 | Fleetmetrica Inc. | Metrics-based transport vehicle fleet safety |
GB2510384B (en) * | 2013-02-01 | 2017-11-29 | Jaguar Land Rover Ltd | Vehicle diagnostics apparatus and method |
US8799034B1 (en) | 2013-03-08 | 2014-08-05 | Allstate University Company | Automated accident detection, fault attribution, and claims processing |
US10032226B1 (en) | 2013-03-08 | 2018-07-24 | Allstate Insurance Company | Automatic exchange of information in response to a collision event |
US9019092B1 (en) | 2013-03-08 | 2015-04-28 | Allstate Insurance Company | Determining whether a vehicle is parked for automated accident detection, fault attribution, and claims processing |
US10963966B1 (en) | 2013-09-27 | 2021-03-30 | Allstate Insurance Company | Electronic exchange of insurance information |
FR3003382A1 (en) * | 2013-03-12 | 2014-09-19 | Mycar Innovations | VEHICLE OPERATING DIAGNOSTIC SYSTEM |
US11222485B2 (en) | 2013-03-12 | 2022-01-11 | Gogoro Inc. | Apparatus, method and article for providing information regarding a vehicle via a mobile device |
US11080734B2 (en) | 2013-03-15 | 2021-08-03 | Cdk Global, Llc | Pricing system for identifying prices for vehicles offered by vehicle dealerships and other entities |
US10445758B1 (en) | 2013-03-15 | 2019-10-15 | Allstate Insurance Company | Providing rewards based on driving behaviors detected by a mobile computing device |
ES2644740T3 (en) * | 2013-04-03 | 2017-11-30 | Iveco S.P.A. | System to estimate the fuel consumption of a vehicle |
GB2519704B (en) | 2013-04-26 | 2017-01-04 | Jaguar Land Rover Ltd | Vehicle diagnostics methods and apparatus |
US8924071B2 (en) * | 2013-04-26 | 2014-12-30 | Ford Global Technologies, Llc | Online vehicle maintenance |
US9165413B2 (en) * | 2013-06-03 | 2015-10-20 | Honda Motor Co., Ltd. | Diagnostic assistance |
US10572943B1 (en) | 2013-09-10 | 2020-02-25 | Allstate Insurance Company | Maintaining current insurance information at a mobile device |
US9443270B1 (en) | 2013-09-17 | 2016-09-13 | Allstate Insurance Company | Obtaining insurance information in response to optical input |
CA2888742C (en) | 2013-09-23 | 2015-09-15 | Jason G. Tatge | Farming data collection and exchange system |
US20150094903A1 (en) * | 2013-09-30 | 2015-04-02 | Ford Global Technologies, Llc | Vehicle diagnostic and prognostic systems and methods |
US20150094929A1 (en) * | 2013-09-30 | 2015-04-02 | Ford Global Technologies, Llc | Vehicle diagnostic and prognostic systems and methods |
US9501878B2 (en) | 2013-10-16 | 2016-11-22 | Smartdrive Systems, Inc. | Vehicle event playback apparatus and methods |
US9610955B2 (en) | 2013-11-11 | 2017-04-04 | Smartdrive Systems, Inc. | Vehicle fuel consumption monitor and feedback systems |
US20150193326A1 (en) * | 2014-01-06 | 2015-07-09 | Ford Global Technologies, Llc | Method and apparatus for error identification and data collection |
US9766874B2 (en) | 2014-01-09 | 2017-09-19 | Ford Global Technologies, Llc | Autonomous global software update |
US9524156B2 (en) | 2014-01-09 | 2016-12-20 | Ford Global Technologies, Llc | Flexible feature deployment strategy |
US8892310B1 (en) | 2014-02-21 | 2014-11-18 | Smartdrive Systems, Inc. | System and method to detect execution of driving maneuvers |
TWI589091B (en) * | 2014-03-06 | 2017-06-21 | 睿能創意公司 | Portable charging device and security system, security system method thereof |
US9323546B2 (en) * | 2014-03-31 | 2016-04-26 | Ford Global Technologies, Llc | Targeted vehicle remote feature updates |
US9716762B2 (en) | 2014-03-31 | 2017-07-25 | Ford Global Technologies Llc | Remote vehicle connection status |
US9325650B2 (en) | 2014-04-02 | 2016-04-26 | Ford Global Technologies, Llc | Vehicle telematics data exchange |
US10140110B2 (en) | 2014-04-02 | 2018-11-27 | Ford Global Technologies, Llc | Multiple chunk software updates |
US9626811B2 (en) | 2014-06-19 | 2017-04-18 | Atieva, Inc. | Vehicle fault early warning system |
US9495814B2 (en) * | 2014-06-19 | 2016-11-15 | Atieva, Inc. | Vehicle fault early warning system |
US9299109B2 (en) * | 2014-07-17 | 2016-03-29 | Kenneth Carl Steffen Winiecki | Motor vehicle monitoring method for determining driver negligence of an engine |
US9460567B2 (en) * | 2014-07-29 | 2016-10-04 | GM Global Technology Operations LLC | Establishing secure communication for vehicle diagnostic data |
CN104181839A (en) * | 2014-08-07 | 2014-12-03 | 深圳市元征科技股份有限公司 | Method and device for processing real-time traveling data of vehicles |
US10146521B2 (en) | 2014-09-09 | 2018-12-04 | Airpro Diagnostics, Llc | Device, system and method for updating the software modules of a vehicle |
DE102014113371A1 (en) | 2014-09-17 | 2016-03-17 | Knorr-Bremse Systeme für Schienenfahrzeuge GmbH | Method for monitoring and diagnosing components of a rail vehicle, with expandable evaluation software |
US9373203B1 (en) | 2014-09-23 | 2016-06-21 | State Farm Mutual Automobile Insurance Company | Real-time driver monitoring and feedback reporting system |
US9056616B1 (en) * | 2014-09-23 | 2015-06-16 | State Farm Mutual Automobile Insurance | Student driver feedback system allowing entry of tagged events by instructors during driving tests |
US11069257B2 (en) | 2014-11-13 | 2021-07-20 | Smartdrive Systems, Inc. | System and method for detecting a vehicle event and generating review criteria |
JP6032265B2 (en) * | 2014-12-10 | 2016-11-24 | トヨタ自動車株式会社 | Vehicle data collection system |
US10713717B1 (en) | 2015-01-22 | 2020-07-14 | Allstate Insurance Company | Total loss evaluation and handling system and method |
US9679420B2 (en) | 2015-04-01 | 2017-06-13 | Smartdrive Systems, Inc. | Vehicle event recording system and method |
TWI557007B (en) * | 2015-04-10 | 2016-11-11 | 宏碁股份有限公司 | Method and system for information transmission for a vehicle |
US10083551B1 (en) | 2015-04-13 | 2018-09-25 | Allstate Insurance Company | Automatic crash detection |
US9767625B1 (en) | 2015-04-13 | 2017-09-19 | Allstate Insurance Company | Automatic crash detection |
US10144389B2 (en) * | 2015-04-20 | 2018-12-04 | Oshkosh Corporation | Response vehicle systems and methods |
US10373523B1 (en) | 2015-04-29 | 2019-08-06 | State Farm Mutual Automobile Insurance Company | Driver organization and management for driver's education |
US9586591B1 (en) | 2015-05-04 | 2017-03-07 | State Farm Mutual Automobile Insurance Company | Real-time driver observation and progress monitoring |
EP3297880A4 (en) * | 2015-05-19 | 2018-06-20 | HEX Microsystems (Pty) Ltd | System and method for transferring diagnostic commands to a vehicle |
US10452508B2 (en) * | 2015-06-15 | 2019-10-22 | International Business Machines Corporation | Managing a set of tests based on other test failures |
US9916700B2 (en) * | 2015-08-17 | 2018-03-13 | Webtech Wireless Inc. | Asset-agnostic framework with asset-specific module for alternate bus parameter calculation |
WO2017100363A1 (en) * | 2015-12-08 | 2017-06-15 | Smartcar, Inc. | System and method for processing requests |
CN105657037B (en) * | 2016-02-04 | 2019-03-15 | 金龙联合汽车工业(苏州)有限公司 | A kind of new-energy automobile and electrically-charging equipment collecting method |
US10706645B1 (en) | 2016-03-09 | 2020-07-07 | Drew Technologies, Inc. | Remote diagnostic system and method |
US10867285B2 (en) | 2016-04-21 | 2020-12-15 | Cdk Global, Llc | Automatic automobile repair service scheduling based on diagnostic trouble codes and service center attributes |
US10853769B2 (en) * | 2016-04-21 | 2020-12-01 | Cdk Global Llc | Scheduling an automobile service appointment in a dealer service bay based on diagnostic trouble codes and service bay attributes |
CA3176870A1 (en) | 2016-04-29 | 2017-11-30 | United Parcel Service Of America, Inc. | Unmanned aerial vehicle pick-up and delivery systems |
US10730626B2 (en) | 2016-04-29 | 2020-08-04 | United Parcel Service Of America, Inc. | Methods of photo matching and photo confirmation for parcel pickup and delivery |
US10010021B2 (en) * | 2016-05-03 | 2018-07-03 | Cnh Industrial America Llc | Equipment library for command and control software |
US10318269B2 (en) * | 2016-05-04 | 2019-06-11 | General Motors Llc | Providing vehicle system module updates |
US11400997B2 (en) | 2016-05-23 | 2022-08-02 | Indian Motorcycle International, LLC | Display systems and methods for a recreational vehicle |
US10917921B2 (en) | 2016-06-19 | 2021-02-09 | Platform Science, Inc. | Secure wireless networks for vehicles |
US11528759B1 (en) | 2016-06-19 | 2022-12-13 | Platform Science, Inc. | Method and system for vehicle inspection |
EP3473029B8 (en) | 2016-06-19 | 2022-05-04 | Platform Science, Inc. | Secure wireless networks for vehicles |
US11503655B2 (en) | 2016-06-19 | 2022-11-15 | Platform Science, Inc. | Micro-navigation for a vehicle |
US11438938B1 (en) | 2016-06-19 | 2022-09-06 | Platform Science, Inc. | System and method to generate position and state-based electronic signaling from a vehicle |
GB2551516B (en) * | 2016-06-20 | 2019-03-20 | Jaguar Land Rover Ltd | Activity monitor |
US10163278B2 (en) | 2016-09-07 | 2018-12-25 | Ford Global Technologies, Llc | Method for sharing and receiving vehicle fuel quality alerts |
US11361380B2 (en) | 2016-09-21 | 2022-06-14 | Allstate Insurance Company | Enhanced image capture and analysis of damaged tangible objects |
US10902525B2 (en) | 2016-09-21 | 2021-01-26 | Allstate Insurance Company | Enhanced image capture and analysis of damaged tangible objects |
US10353691B2 (en) | 2016-09-30 | 2019-07-16 | Cummins Inc. | Updating electronic controller through telematics |
DE102016224193A1 (en) * | 2016-12-06 | 2018-06-07 | Robert Bosch Gmbh | Method for monitoring a control device for a vehicle |
JP6468277B2 (en) * | 2016-12-26 | 2019-02-13 | トヨタ自動車株式会社 | Vehicle communication system |
DE102017107202A1 (en) * | 2017-04-04 | 2018-10-04 | Avl Software And Functions Gmbh | Method and device for protecting control units against harmful software |
US10269192B2 (en) | 2017-04-07 | 2019-04-23 | Airbiquity Inc. | Technologies for verifying control system operation |
US10445953B1 (en) | 2017-04-12 | 2019-10-15 | Drew Technologies, Inc. | Vehicle programming and diagnostic device with integrated battery charger |
US10937103B1 (en) | 2017-04-21 | 2021-03-02 | Allstate Insurance Company | Machine learning based accident assessment |
US10775792B2 (en) | 2017-06-13 | 2020-09-15 | United Parcel Service Of America, Inc. | Autonomously delivering items to corresponding delivery locations proximate a delivery route |
US10748356B1 (en) | 2017-07-17 | 2020-08-18 | Drew Technologies, Inc. | Vehicle diagnostic and programming device and method |
US10289404B2 (en) * | 2017-07-25 | 2019-05-14 | Aurora Labs Ltd. | Detecting anomalies using real-time ECU processing activity |
WO2019027061A1 (en) * | 2017-07-31 | 2019-02-07 | (주)디지파츠 | Connected gateway server system for real-time vehicle control service |
US11189163B2 (en) * | 2017-10-11 | 2021-11-30 | Toyota Motor Engineering & Manufacturing North America, Inc. | Systems and methods for infrastructure improvements |
DE102017221926A1 (en) * | 2017-12-05 | 2019-06-06 | Bayerische Motoren Werke Aktiengesellschaft | Processing unit for a vehicle, a mobile device and a system |
US11125493B2 (en) | 2018-03-07 | 2021-09-21 | Carrier Corporation | Method and system for controlling use of a portable cooling container |
EP3539843B1 (en) * | 2018-03-12 | 2021-05-26 | Railnova SA | A device for processing data of rolling stock |
JP7201329B2 (en) * | 2018-03-12 | 2023-01-10 | トヨタ自動車株式会社 | vehicle controller |
US11190608B2 (en) | 2018-03-21 | 2021-11-30 | Cdk Global Llc | Systems and methods for an automotive commerce exchange |
US11501351B2 (en) | 2018-03-21 | 2022-11-15 | Cdk Global, Llc | Servers, systems, and methods for single sign-on of an automotive commerce exchange |
DE102018003281B4 (en) * | 2018-04-23 | 2019-12-05 | Daimler Ag | Vehicle operating system |
EP3832622B1 (en) | 2018-08-03 | 2023-06-21 | Honda Motor Co., Ltd. | Information management device, vehicle, and method |
US10755494B2 (en) | 2018-08-03 | 2020-08-25 | Ford Global Technologies, Llc | Vehicle component diagnostic |
US11356425B2 (en) | 2018-11-30 | 2022-06-07 | Paccar Inc | Techniques for improving security of encrypted vehicle software updates |
US11449327B2 (en) | 2018-11-30 | 2022-09-20 | Paccar Inc | Error-resilient over-the-air software updates for vehicles |
FR3097664B1 (en) * | 2019-06-19 | 2021-08-13 | Sigfox | Vehicle sharing system and vehicle access method of such a system |
US11257307B1 (en) | 2019-06-24 | 2022-02-22 | Opus Ivs, Inc. | Adaptive vehicle diagnostic system and method |
IT201900010758A1 (en) * | 2019-07-03 | 2021-01-03 | Telepass S P A | On-board device for telematic traffic services |
DE102019211155A1 (en) * | 2019-07-26 | 2021-01-28 | Volkswagen Aktiengesellschaft | Method of a vehicle and a network server for servicing vehicle components |
DE102019211154A1 (en) * | 2019-07-26 | 2021-01-28 | Volkswagen Aktiengesellschaft | Method of a network server for servicing vehicle components |
US11230197B2 (en) * | 2019-08-07 | 2022-01-25 | Toyota Motor Engineering & Manufacturing North America, Inc. | Methods and systems for integrating a hub motor with a vehicle |
US11861954B2 (en) | 2019-08-27 | 2024-01-02 | Opus Ivs, Inc. | Vehicle diagnostic system and method |
US11348382B1 (en) | 2019-10-30 | 2022-05-31 | Opus Ivs, Inc. | System and method for detecting remote vehicle diagnosis |
US11508191B1 (en) | 2019-12-03 | 2022-11-22 | Opus Ivs, Inc. | Vehicle diagnostic interface device |
US11423715B1 (en) | 2019-12-03 | 2022-08-23 | Opus Ivs, Inc. | Vehicle diagnostic device |
US11538290B1 (en) | 2020-01-31 | 2022-12-27 | Opus Ivs, Inc. | Automated vehicle diagnostic navigation system and method |
US10973908B1 (en) | 2020-05-14 | 2021-04-13 | David Gordon Bermudes | Expression of SARS-CoV-2 spike protein receptor binding domain in attenuated salmonella as a vaccine |
US11080105B1 (en) | 2020-11-18 | 2021-08-03 | Cdk Global, Llc | Systems, methods, and apparatuses for routing API calls |
US11514021B2 (en) | 2021-01-22 | 2022-11-29 | Cdk Global, Llc | Systems, methods, and apparatuses for scanning a legacy database |
US11651632B2 (en) | 2021-04-12 | 2023-05-16 | Toyota Motor North America, Inc. | Diagnosis of transport-related issues |
US11887409B2 (en) * | 2021-05-19 | 2024-01-30 | Pony Al Inc. | Device health code broadcasting on mixed vehicle communication networks |
US20220371530A1 (en) * | 2021-05-19 | 2022-11-24 | Pony Ai Inc. | Device-level fault detection |
US11803535B2 (en) | 2021-05-24 | 2023-10-31 | Cdk Global, Llc | Systems, methods, and apparatuses for simultaneously running parallel databases |
DE102021205383A1 (en) * | 2021-05-27 | 2022-12-01 | Robert Bosch Gesellschaft mit beschränkter Haftung | Method for diagnosing a vehicle electrical system |
WO2023102765A1 (en) * | 2021-12-08 | 2023-06-15 | 陈献忠 | Fault alarm system for intelligent electric locomotive |
CN116414052A (en) * | 2021-12-29 | 2023-07-11 | 康明斯有限公司 | System and method for custom calibration updates |
Family Cites Families (112)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
BE792277A (en) | 1971-12-06 | 1973-03-30 | Tull Aviation Corp | REMOTE ACQUISITION SYSTEM OF OPERATING CONDITIONS DATA |
US4067061A (en) * | 1975-03-18 | 1978-01-03 | Rockwell International Corporation | Monitoring and recording system for vehicles |
US4258421A (en) * | 1978-02-27 | 1981-03-24 | Rockwell International Corporation | Vehicle monitoring and recording system |
US4677429A (en) * | 1983-12-01 | 1987-06-30 | Navistar International Transportation Corp. | Vehicle information on-board processor |
US4630292A (en) * | 1984-08-13 | 1986-12-16 | Juricich Ronald A | Fuel tax rebate recorder |
US4926331A (en) * | 1986-02-25 | 1990-05-15 | Navistar International Transportation Corp. | Truck operation monitoring system |
US4809177A (en) * | 1987-08-14 | 1989-02-28 | Navistar International Transportation Corp. | Multiplexed electrical wiring system for a truck including driver interface and power switching |
US4979170A (en) * | 1988-01-19 | 1990-12-18 | Qualcomm, Inc. | Alternating sequential half duplex communication system |
US4939652A (en) * | 1988-03-14 | 1990-07-03 | Centrodyne Inc. | Trip recorder |
JP2574892B2 (en) * | 1989-02-15 | 1997-01-22 | 株式会社日立製作所 | Load sharing control method for automobile |
US5337236A (en) * | 1990-05-21 | 1994-08-09 | Taurean Electronics, Inc. | System for categorizing and recording vehicle trip distance |
US5787373A (en) * | 1990-08-22 | 1998-07-28 | Datatrac International, Inc. | Travel expense tracking system |
DE69225339T2 (en) * | 1991-03-29 | 1998-08-27 | Cummins Electronics | Method and device for generating calibration information for an electronic engine control module |
US5343780A (en) | 1992-07-27 | 1994-09-06 | Cummins Engine Company, Inc. | Variable power drivetrain engine control system |
EP0655150A4 (en) * | 1992-08-14 | 1996-06-05 | Vorad Safety Systems Inc | Recording of operational events in an automotive vehicle. |
US5442553A (en) * | 1992-11-16 | 1995-08-15 | Motorola | Wireless motor vehicle diagnostic and software upgrade system |
DE4304838C2 (en) * | 1993-02-17 | 1996-01-25 | Daimler Benz Ag | Device for determining the usage fees of the web |
US5359528A (en) * | 1993-02-19 | 1994-10-25 | Rockwell International Corp. | System for accurately determining the mileage traveled by a vehicle within a state without human intervention |
AU674189B2 (en) | 1993-02-23 | 1996-12-12 | Moore North America, Inc. | A method and system for gathering and analyzing customer and purchasing information |
DE4310099C2 (en) * | 1993-03-23 | 1997-09-04 | Mannesmann Ag | Path identification device |
US5806018A (en) * | 1993-05-25 | 1998-09-08 | Intellectual Property Development Associates Of Connecticut, Incorporated | Methods and apparatus for updating navigation information in a motorized vehicle |
US5539638A (en) * | 1993-08-05 | 1996-07-23 | Pavilion Technologies, Inc. | Virtual emissions monitor for automobile |
GB2288892A (en) | 1994-04-29 | 1995-11-01 | Oakrange Engineering Ltd | Vehicle fleet monitoring apparatus |
GB9409671D0 (en) | 1994-05-14 | 1994-07-06 | Eaton Corp | Security device |
DE4423328A1 (en) | 1994-06-22 | 1996-01-04 | Schmidt Karsten | Lorry, car and mobile fleet tracking and display system |
GB9417600D0 (en) * | 1994-09-01 | 1994-10-19 | British Telecomm | Navigation information system |
US5619412A (en) * | 1994-10-19 | 1997-04-08 | Cummins Engine Company, Inc. | Remote control of engine idling time |
TW303444B (en) * | 1994-11-22 | 1997-04-21 | Traffic Object Supervision Systems | |
US5648768A (en) * | 1994-12-30 | 1997-07-15 | Mapsys, Inc. | System and method for identifying, tabulating and presenting information of interest along a travel route |
US5579233A (en) * | 1995-01-09 | 1996-11-26 | Burns; Robert R. | Method of on-site refueling using electronic identification tags, reading probe, and a truck on-board computer |
WO1996027513A1 (en) * | 1995-03-03 | 1996-09-12 | Qualcomm Incorporated | Method and apparatus for monitoring parameters of vehicle electronic control units |
GB9505009D0 (en) * | 1995-03-13 | 1995-05-03 | Iu Howard | Apparatus for remotely controlling an automobile in motion |
US5694322A (en) * | 1995-05-09 | 1997-12-02 | Highwaymaster Communications, Inc. | Method and apparatus for determining tax of a vehicle |
US5680328A (en) * | 1995-05-22 | 1997-10-21 | Eaton Corporation | Computer assisted driver vehicle inspection reporting system |
JP3380368B2 (en) * | 1995-06-05 | 2003-02-24 | 三菱電機株式会社 | Vehicle anti-theft device |
US5917434A (en) * | 1995-06-15 | 1999-06-29 | Trimble Navigation Limited | Integrated taximeter/GPS position tracking system |
KR0153605B1 (en) | 1995-10-13 | 1998-11-16 | 김광호 | Remote management system |
US5835376A (en) * | 1995-10-27 | 1998-11-10 | Total Technology, Inc. | Fully automated vehicle dispatching, monitoring and billing |
US5742915A (en) * | 1995-12-13 | 1998-04-21 | Caterpillar Inc. | Position referenced data for monitoring and controlling |
US5729458A (en) * | 1995-12-29 | 1998-03-17 | Etak, Inc. | Cost zones |
US5732074A (en) * | 1996-01-16 | 1998-03-24 | Cellport Labs, Inc. | Mobile portable wireless communication system |
US5803043A (en) * | 1996-05-29 | 1998-09-08 | Bayron; Harry | Data input interface for power and speed controller |
US5931877A (en) * | 1996-05-30 | 1999-08-03 | Raytheon Company | Advanced maintenance system for aircraft and military weapons |
US5919239A (en) * | 1996-06-28 | 1999-07-06 | Fraker; William F. | Position and time-at-position logging system |
TW359800B (en) * | 1996-08-19 | 1999-06-01 | Ibm | Device independent and transfer optimised interactive client-server dialog system and method for performing interactive applications therein |
US5835868A (en) * | 1996-08-30 | 1998-11-10 | Mcelroy; Alejandro S. | Automated system for immobilizing a vehicle and method |
EP0932869A4 (en) * | 1996-10-21 | 2005-07-13 | Orissa Inc | Transportation network system |
US5987378A (en) * | 1996-10-24 | 1999-11-16 | Trimble Navigation Limited | Vehicle tracker mileage-time monitor and calibrator |
US6157317A (en) * | 1996-12-02 | 2000-12-05 | Kline And Walker Llc | Secure communication and control system for monitoring, recording, reporting and/or restricting unauthorized use of vehicle. |
US5954773A (en) * | 1996-12-13 | 1999-09-21 | Eaton Corporation | Vehicle state mileage determination system |
US6122514A (en) * | 1997-01-03 | 2000-09-19 | Cellport Systems, Inc. | Communications channel selection |
US5844987A (en) * | 1997-01-03 | 1998-12-01 | Ericsson Inc. | Communications system and method using vehicle identifications |
EP0956521B1 (en) * | 1997-02-03 | 2001-08-29 | DaimlerChrysler Rail Systems GmbH | Communication based vehicle positioning reference system |
US5974356A (en) * | 1997-03-14 | 1999-10-26 | Qualcomm Incorporated | System and method for determining vehicle travel routes and mileage |
US20010018628A1 (en) * | 1997-03-27 | 2001-08-30 | Mentor Heavy Vehicle Systems, Lcc | System for monitoring vehicle efficiency and vehicle and driver perfomance |
US6253129B1 (en) * | 1997-03-27 | 2001-06-26 | Tripmaster Corporation | System for monitoring vehicle efficiency and vehicle and driver performance |
US5928291A (en) * | 1997-03-27 | 1999-07-27 | Rockwell International Corporation | Mileage and fuel consumption determination for geo-cell based vehicle information management |
US6263268B1 (en) * | 1997-08-26 | 2001-07-17 | Transcontech Corporation | System and method for providing mobile automotive telemetry |
US5938716A (en) * | 1997-09-08 | 1999-08-17 | Cummins Engine Company, Inc. | System for customizing vehicle engine control computer operation |
US6078873A (en) * | 1997-10-02 | 2000-06-20 | Cummins Engine Company, Inc. | Method and apparatus for real-time data stamping via datalink and volatile ECM timer/clock |
US6091340A (en) * | 1997-11-25 | 2000-07-18 | Lee; Brian | Remote on/off disable parts and system |
US6008740A (en) * | 1997-12-17 | 1999-12-28 | Stmicroelectronics, Inc. | Electronic speed limit notification system |
US6108591A (en) * | 1998-01-22 | 2000-08-22 | Qualcomm Incorporated | Method and apparatus for validating vehicle operators |
US6089207A (en) * | 1998-03-02 | 2000-07-18 | Cummins Engine Company, Inc. | Throttle control response selection system |
US6225890B1 (en) | 1998-03-20 | 2001-05-01 | Trimble Navigation Limited | Vehicle use control |
US5999876A (en) * | 1998-04-01 | 1999-12-07 | Cummins Engine Company, Inc. | Method and system for communication with an engine control module in sleep mode |
US6275585B1 (en) * | 1998-04-28 | 2001-08-14 | Motorola, Inc. | Method for reprogramming a vehicle system or a user system in a vehicle |
US6259988B1 (en) * | 1998-07-20 | 2001-07-10 | Lockheed Martin Corporation | Real-time mission adaptable route planner |
US7010603B2 (en) * | 1998-08-17 | 2006-03-07 | Openwave Systems Inc. | Method and apparatus for controlling network connections based on destination locations |
GB2340974B (en) | 1998-08-21 | 2000-08-23 | Stuart Johnson | The remote immobilisation of moving powered vehicles |
BR9914488A (en) * | 1998-11-05 | 2001-10-16 | Int Truck & Engine Corp | Land vehicle communication system and process to provide information and coordinate vehicle activities |
US6487717B1 (en) | 1999-01-15 | 2002-11-26 | Cummins, Inc. | System and method for transmission of application software to an embedded vehicle computer |
US6295492B1 (en) * | 1999-01-27 | 2001-09-25 | Infomove.Com, Inc. | System for transmitting and displaying multiple, motor vehicle information |
US6323874B1 (en) * | 1999-02-08 | 2001-11-27 | Silicon Graphics, Inc. | System and method for rendering an image |
US6060981A (en) * | 1999-04-23 | 2000-05-09 | Caterpillar Inc. | Vehicle security system for unattended idle operations |
US6317668B1 (en) * | 1999-06-10 | 2001-11-13 | Qualcomm Incorporated | Paperless log system and method |
US6370449B1 (en) * | 1999-06-14 | 2002-04-09 | Sun Microsystems, Inc. | Upgradable vehicle component architecture |
US6430164B1 (en) * | 1999-06-17 | 2002-08-06 | Cellport Systems, Inc. | Communications involving disparate protocol network/bus and device subsystems |
KR100369127B1 (en) * | 1999-07-08 | 2003-01-24 | 현대자동차주식회사 | A method for seaching a traveling record of a vehicle |
US6278935B1 (en) * | 1999-07-23 | 2001-08-21 | Navigation Technologies Corp. | Method and system for providing instructions about tollways with a navigation system |
US6167333A (en) * | 1999-08-19 | 2000-12-26 | Lucent Technologies Inc. | Highway information system |
JP2001076012A (en) | 1999-08-31 | 2001-03-23 | Hitachi Ltd | Method and device for gathering vehicle information |
US6292724B1 (en) * | 1999-10-12 | 2001-09-18 | Micrologic, Inc. | Method of and system and apparatus for remotely monitoring the location, status, utilization and condition of widely geographically dispresed fleets of vehicular construction equipment and the like and providing and displaying such information |
BR9905575C1 (en) | 1999-11-24 | 2001-10-09 | Carlos Eduardo Wendler | Anti-theft controller and speed limiter for motor vehicles |
US6204772B1 (en) * | 1999-12-16 | 2001-03-20 | Caterpillar Inc. | Method and apparatus for monitoring the position of a machine |
US6611755B1 (en) * | 1999-12-19 | 2003-08-26 | Trimble Navigation Ltd. | Vehicle tracking, communication and fleet management system |
US6775267B1 (en) * | 1999-12-30 | 2004-08-10 | At&T Corp | Method for billing IP broadband subscribers |
EP1128333A3 (en) | 2000-02-24 | 2004-07-07 | Vodafone Holding GmbH | Method and apparatus for generation of electronic evidence of the travels of a vehicle |
US20010020204A1 (en) * | 2000-03-06 | 2001-09-06 | David Runyon | System for tracking vehicle and driver location and mileage and generating reports therefrom |
US20030158656A1 (en) * | 2000-04-03 | 2003-08-21 | Zvi David | Locating and controlling a remote device through a satellite location system |
US6389337B1 (en) * | 2000-04-24 | 2002-05-14 | H. Brock Kolls | Transacting e-commerce and conducting e-business related to identifying and procuring automotive service and vehicle replacement parts |
US20020007237A1 (en) * | 2000-06-14 | 2002-01-17 | Phung Tam A. | Method and system for the diagnosis of vehicles |
US20020173885A1 (en) * | 2001-03-13 | 2002-11-21 | Lowrey Larkin Hill | Internet-based system for monitoring vehicles |
US6636790B1 (en) * | 2000-07-25 | 2003-10-21 | Reynolds And Reynolds Holdings, Inc. | Wireless diagnostic system and method for monitoring vehicles |
US20020016655A1 (en) * | 2000-08-01 | 2002-02-07 | Joao Raymond Anthony | Apparatus and method for processing and/or for providing vehicle information and/or vehicle maintenance information |
US7092803B2 (en) * | 2000-08-18 | 2006-08-15 | Idsc Holdings, Llc | Remote monitoring, configuring, programming and diagnostic system and method for vehicles and vehicle components |
US20050060070A1 (en) * | 2000-08-18 | 2005-03-17 | Nnt, Inc. | Wireless communication framework |
US20060025907A9 (en) * | 2000-08-18 | 2006-02-02 | Nnt, Inc. | Vehicle-interactive system |
JP2004530174A (en) | 2000-08-18 | 2004-09-30 | エヌエヌティー インク | System, method, and computer program product for remotely diagnosing, monitoring, configuring, and reprogramming vehicles |
US20050203673A1 (en) * | 2000-08-18 | 2005-09-15 | Hassanayn Machlab El-Hajj | Wireless communication framework |
US6694234B2 (en) * | 2000-10-06 | 2004-02-17 | Gmac Insurance Company | Customer service automation systems and methods |
JP2002228552A (en) * | 2001-01-31 | 2002-08-14 | Mazda Motor Corp | Remote failure diagnostic server of vehicle, remote failure diagnostic method of vehicle, remote failure diagnostic program, on-vehicle remote failure diagnostic system and remote failure diagnostic system of vehicle |
US6995572B2 (en) * | 2001-03-05 | 2006-02-07 | The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration | Sensor and method for detecting a superstrate |
US6611740B2 (en) * | 2001-03-14 | 2003-08-26 | Networkcar | Internet-based vehicle-diagnostic system |
US6954689B2 (en) * | 2001-03-16 | 2005-10-11 | Cnh America Llc | Method and apparatus for monitoring work vehicles |
US20030105825A1 (en) * | 2001-05-01 | 2003-06-05 | Profluent, Inc. | Method and system for policy based management of messages for mobile data networks |
US6662091B2 (en) * | 2001-06-29 | 2003-12-09 | Battelle Memorial Institute | Diagnostics/prognostics using wireless links |
US20030093199A1 (en) * | 2001-11-15 | 2003-05-15 | Michael Mavreas | Remote monitoring and control of a motorized vehicle |
US20030105565A1 (en) * | 2001-12-03 | 2003-06-05 | Loda David C. | Integrated internet portal and deployed product microserver management system |
US6714857B2 (en) * | 2002-02-26 | 2004-03-30 | Nnt, Inc. | System for remote monitoring of a vehicle and method of determining vehicle mileage, jurisdiction crossing and fuel consumption |
US20030162523A1 (en) * | 2002-02-27 | 2003-08-28 | Michael Kapolka | Vehicle telemetry system and method |
US7084735B2 (en) * | 2002-08-28 | 2006-08-01 | Idsc Holdings, Llc. | Remote vehicle security system |
-
2002
- 2002-03-04 US US10/091,096 patent/US7092803B2/en not_active Expired - Fee Related
-
2003
- 2003-03-03 CA CA002478176A patent/CA2478176A1/en not_active Abandoned
- 2003-03-03 AU AU2003224647A patent/AU2003224647A1/en not_active Abandoned
- 2003-03-03 EP EP03721326A patent/EP1485878A2/en not_active Withdrawn
- 2003-03-03 JP JP2003575343A patent/JP2005520725A/en active Pending
- 2003-03-03 WO PCT/US2003/006475 patent/WO2003077205A2/en not_active Application Discontinuation
- 2003-03-04 TW TW092104529A patent/TWI237758B/en not_active IP Right Cessation
-
2004
- 2004-05-10 US US10/709,500 patent/US20050038581A1/en not_active Abandoned
Also Published As
Publication number | Publication date |
---|---|
US20040138790A1 (en) | 2004-07-15 |
WO2003077205A3 (en) | 2004-01-29 |
TWI237758B (en) | 2005-08-11 |
EP1485878A2 (en) | 2004-12-15 |
WO2003077205A2 (en) | 2003-09-18 |
JP2005520725A (en) | 2005-07-14 |
US20050038581A1 (en) | 2005-02-17 |
TW200404201A (en) | 2004-03-16 |
US7092803B2 (en) | 2006-08-15 |
AU2003224647A1 (en) | 2003-09-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7092803B2 (en) | Remote monitoring, configuring, programming and diagnostic system and method for vehicles and vehicle components | |
US20050060070A1 (en) | Wireless communication framework | |
US6643571B2 (en) | System and method for communication between vehicles and a supervisor station | |
US20050065678A1 (en) | Enterprise resource planning system with integrated vehicle diagnostic and information system | |
AU2002301638B2 (en) | Integrated internet portal and deployed product microserver management system | |
CA2838632C (en) | Method and apparatus for translating vehicle diagnostic trouble codes | |
CN103080720B (en) | The method and system of diagnosis or software maintenance for performing vehicle | |
US10600096B2 (en) | System and method for obtaining competitive pricing for vehicle services | |
RU2491526C2 (en) | Engine diagnostics method | |
US20170076344A1 (en) | System and method to prevent vehicle failures on public roadways | |
US20160071338A1 (en) | Diagnostic unit and method | |
JP4583594B2 (en) | Vehicle management system | |
US7545262B2 (en) | Method and system for automated recall notification | |
WO2004092857A2 (en) | System, method and computer program product for remote vehicle diagnostics, telematics, monitoring, configuring, and reprogramming | |
US20200043068A1 (en) | System and method for obtaining competitive pricing for vehicle services | |
CN103080719B (en) | For the method and system of the diagnosis or software maintenance that perform vehicle | |
JP2002202003A (en) | Vehicle management system | |
WO2012075055A2 (en) | System and method for obtaining competitive pricing for vehicle services | |
KR20090003541A (en) | Method and system for providing automobile fail diagnosis service by using network | |
US20050177347A1 (en) | Manufacturing device with automatic remote monitoring and a corresponding monitoring method | |
WO2014091361A1 (en) | Vehicle evaluation and lead generation |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
FZDE | Discontinued | ||
FZDE | Discontinued |
Effective date: 20090819 |