Many vehicles today include a vehicle bus. A vehicle bus is an internal communications network for the vehicle that is used to connect control modules and sensors installed in the vehicle. Modules plugged into the network communicate with each other using a predefined network protocol. Control modules receive input from sensors attached to the vehicle bus network and use the input to control other modules over the network.
Many vehicle busses include connectors that can be used by external devices to access modules on the vehicle bus network. Since 1996, all cars sold in the United States are required to have an On-Board Diagnostics (ODB) connector. The ODB connector can be used to access the car's electronic controllers. An ODB-II connector is included in many of the cars manufactured for the U.S. market today.
As noted above, each vehicle bus employs a predefined network protocol. In the United States, commercial vehicles use the SAE J1939 vehicle bus standard for communication and diagnostics among vehicle components. Fleet managers use external access to the vehicle bus of their fleet vehicles to monitor the performance and usage of their vehicles. One approach is to use a telematics solution to access information on the vehicle bus.
Typical telematics solutions include a Cellular module, a Vehicle Bus, a display, and a complicated mess of wiring and antennas. One such approach is to use a ConnectPort® X5 gateway manufactured by Digi International Inc. of Minnetonka, Minn. to access a SAE J1939 vehicle bus. The ConnectPort X5gateway provides remote connectivity, over a number of communications protocols, to mobile assets to monitor operating health, performance, location and driver/operator behavior.
Xata Turnpike RouteTracker is a module manufactured by Xata Corporation of Eden Prairie, Minnesota that connects via a cable to the vehicle diagnostic port. The RouteTracker captures GPS data and reads engine diagnostic information. The GPS and engine diagnostic information is transmitted via Bluetooth to a smartphone in the vehicle and, through the smartphone, to Xata Turnpike's hosted web site.
Finally, Xirgo Technologies of Camarillo, Calif. manufactures a module that connects to the diagnostic port of a vehicle to provide a cellular interface to the vehicle telematics system.
Current telematics solutions tend to be complicated and costly. What is needed is a system and method for providing telematics solutions in a more efficient manner.
In the drawings, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. The drawings illustrate generally, by way of example, but not by way of limitation, various embodiments discussed in the present document.
In the following detailed description of example embodiments of the invention, reference is made to specific examples by way of drawings and illustrations. These examples are described in sufficient detail to enable those skilled in the art to practice the invention, and serve to illustrate how the invention may be applied to various purposes or embodiments. Other embodiments of the invention exist and are within the scope of the invention, and logical, mechanical, electrical, and other changes may be made without departing from the subject or scope of the present invention. Features or limitations of various embodiments of the invention described herein, however essential to the example embodiments in which they are incorporated, do not limit the invention as a whole, and any reference to the invention, its elements, operation, and application do not limit the invention as a whole but serve only to define these example embodiments. The following detailed description does not, therefore, limit the scope of the invention, which is defined only by the appended claims.
A telematics system is shown in
In some embodiments, vehicle bus connector 108 is an ODB connector such as, for example, an ODB II connector. In other embodiments, vehicle bus connector 108 is a connector used in commercial vehicles, such as a SAE J1939 connector.
In the embodiment shown in
In one embodiment, such as is shown in
In one embodiment the wired connection to connector module 110 is used by connected Wi-Fi devices 124 or by personal communications device 120 to write files to USB-connected storage (not shown).
In one ODB embodiment, connector module 110 is an ODB-II compatible connector. In one commercial embodiment, connector module 110 is a SAE 1939 compatible connector.
In one embodiment, connector module 110 includes a connector interface 112 which can be coupled to vehicle bus connector 108, a USB interface 114, a Wi-Fi interface 116 and a controller 111. Interface 112 is coupled to vehicle bus connector 108. In one embodiment, Wi-Fi interface 116 includes a Wi-Fi antenna 118.
In the embodiment shown, as is shown in
In one embodiment, as is shown in
In one embodiment, personal communications device 120 also includes a wireless interface 130 capable of communication with the wireless interface of module 110. In one such embodiment, personal communications device 120 operates as a wireless access point.
In one embodiment, personal communications device 120 is a smart phone running applications on an operating system such as iOS or Android. In another embodiment, personal communications device 120 is a tablet or personal computer having a cellular modem.
An advantage of the telematics system of
An advantage of the USB connection between module 110 and personal communications device 120 is that the typical GPS receiver in device 120 drains power in device 120 when used frequently, as in a typical telematics application. The power drain is offset by power supplied over the USB interface.
In addition, Wi-Fi interfaces are easy to configure. The Wi-Fi access point of connector module 112 is easily configured via the personal communications device. Finally, a Wi-Fi based OBD-2 device makes it possible for a vehicle bus connected insurance tracker to connect to vehicle control systems via a Smart Phone, Home network, metropolitan Wi-Fi, or Wi-Fi hotspot.
An example embodiment of a vehicle bus connector module 110 is shown in
A more detailed illustration of one example embodiment of vehicle bus connector module 110 is shown in
In the example embodiment shown in
Another example embodiment of a vehicle bus connector module 110 is shown in
In one embodiment telematics application 128 is split between control 111 operating in module 110 and controller 123 operating in personal communications device 120. In some such embodiments, there is cooperation between an application executing in vehicle bus control module 110 and the application running in the cellular phone in order to ensure regulatory compliance. In one such embodiment, personal communications device 120 (e.g., a phone) provides server connectivity, driver/vehicle history information, input from the driver, and GPS data while module 110 provides information about the truck and an interface for downloading driver logs to a USB stick. A representative compliance application needs to take the various inputs from servers, driver, and vehicle and process them into log data that is used to demonstrate compliance. Processing of the inputs could be done solely on the phone, solely on the vehicle bus adapter, or as portions allocated between the two as long as the log data makes it to the back end servers and onto a USB stick on demand.
In one embodiment, each vehicle bus connector module 110 includes a USB interface 114. USB interface 114 is used, for instance, to download driver logs to law enforcement personnel when requested.
In one embodiment, telematics system 100 connects through the cellular or wireless networks 132 to the Internet 170 and through the Internet 170 to server 172. An example of such an embodiment is shown in
In one embodiment, HTTPS terminates in proxy servers 174.
In one embodiment, driver logs are stored in servers 172. Driver logs for commercial vehicles can be accessed by law enforcement. In one embodiment, law enforcement personnel access driver logs via USB interface 114. An officer attaches a device to USB interface 114 and reads the file stored in server 172. One example embodiment is shown in
In the example embodiment shown in
In one alternate embodiment, the request is forwarded from connector module 110 through Wi-Fi access point 136 to server 172 through wireless interface 116 when connector module 110 comes within range of Wi-Fi access point 136. In one embodiment, a compliance application (such as telematics application 128) executing on personal communications device 120 requests information from the vehicle bus connector module 110 via web services, formats the driver log and sends the driver log to the vehicle bus connector module 110 via web services. Module 110, when it detects access point 136, initiates a transfer of accumulated driver logs through access point 136 to server 172. One example embodiment is shown in
In an alternative embodiment, personal communications device 120 communicates directly to Wi-Fi access point 136; an application running on device 120 detects access point 136, makes a connection to access point 136 and initiates the transfer through access point 136 to server 172.
In one embodiment, either connector module 110 or personal communications device 120 initiate a transfer through access point 136 using a physical button and user interface application executing fully or partially on device 120. In one such embodiment, an application executing on personal communications device 120 decides which external network to connect to based on a trusted third party (potentially including authentication information).
In one embodiment, an application executing on module 110 includes a driver which connects to nearby adapters based on input from a driver.
In one embodiment, server 172 is a government server and telematics application 128 delivers the driver logs to the government server periodically, or based on a trigger initiated by the driver.
In one embodiment, personal communications device 120 posts GPS and driver information to the vehicle bus connector module 110 and module 110 combines that with engine information into a driver log.
As noted above, establishing vehicle bus connector module 110 as a wireless access point simplifies the connection to a smartphone or other such device, while eliminating the need for separate displays. Module 110 plugs directly into the vehicle bus connector 108 and communicates with a smartphone, tablet or other such computer to transfer information from the vehicle bus to the smart phone, tablet or other such computer. Since module 110 plugs directly into vehicle bus connector 108, it receives power from the vehicle bus, reducing complicated wiring.
Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that any arrangement which is calculated to achieve the same purpose may be substituted for the specific embodiments shown. The invention may be implemented in various modules and in hardware, software, and various combinations thereof, and any combination of the features described in the examples presented herein is explicitly contemplated as an additional example embodiment. This application is intended to cover any adaptations or variations of the example embodiments of the invention described herein. It is intended that this invention be limited only by the claims, and the full scope of equivalents thereof.