Method and system for utilizing vehicle odometer values and dynamic compliance

Abstract

A system and method vehicle dynamic compliance and utilizing multiple vehicle odometer values is disclosed herein. The system comprises a vehicle (210) comprising an on-board computer (232) with a memory (231) having a vehicle identification number (233), a connector plug (235), and an motorized engine (234), a connected vehicle device (130) comprising a processor, a WiFi radio, a BLUETOOTH radio, a memory, and a connector for mating with the connector plug of the vehicle (210), and a mobile device (110) comprising a graphical user interface (335), a processor (310), a WiFi radio (307), a BLUETOOTH radio (306), and a cellular network interface (308).

Claims

1. A system for vehicle dynamic compliance with multiple vehicle statutes and regulations, the system comprising: a connected vehicle device (CVD) comprising a processor, a radio, a memory, and a connector for connecting to a vehicle; a mobile device comprising a graphical user interface, a processor, a radio, and a cellular network interface; and a server; wherein a location of the vehicle is transmitted to the server by the CVD; wherein the server retrieves a plurality of real-time compliance rules for the location of the vehicle; wherein the server transmits the plurality of real-time compliance rules to the CVD for display on the mobile device.

2. The system according to claim 1 wherein the mobile device is a tablet computer.

3. The system according to claim 1 wherein the plurality of databases comprises at least one of a plurality of State vehicle databases, a plurality of municipal vehicle databases, plurality of county vehicle databases, or a plurality of Federal vehicle databases.

4. The system according to claim 1 wherein the vehicle is a delivery truck.

5. The system according to claim 1 wherein the radio of the CVD is a WiFi radio.

6. The system according to claim 1 wherein the CVD obtains a vehicle identification number (VIN) from an on-board computer of the vehicle and transmits the VIN with the location to the server for verification of the vehicle.

7. A method for vehicle dynamic compliance with multiple vehicle statutes and regulations, the method comprising: receiving at a server from a connected vehicle device (CVD) a location of a vehicle, the CVD comprising a processor, a radio, a memory, and a connector for connecting to the vehicle; retrieving at the server a plurality of real-time compliance rules for the location of the vehicle from a plurality of databases; and transmitting from the server to the CVD the plurality of real-time compliance rules for display.

8. The method according to claim 7 further comprising displaying the plurality of real-time compliance rules on a display of a mobile device.

9. The method according to claim 7 wherein the plurality of databases comprises at least one of a plurality of State vehicle databases, a plurality of municipal vehicle databases, plurality of county vehicle databases, or a plurality of Federal vehicle databases.

10. The method according to claim 7 wherein the vehicle is a delivery truck.

11. The method according to claim 7 wherein the CVD radio is a WiFi radio.

12. The method according to claim 7 wherein the CVD obtains a vehicle identification number (VIN) from an on-board computer and transmits the VIN with the location to the server for verification of the vehicle.

13. A method for vehicle dynamic compliance with multiple vehicle statutes and regulations, the method comprising: transmitting to a server from a connected vehicle device (CVD) a location of a vehicle, the CVD comprising a processor, a radio, a memory, and a connector for connecting to the vehicle; receiving from the server at the CVD a plurality of real-time compliance rules for the location of the vehicle, the plurality of real-time compliance from a plurality of databases rules; displaying the plurality of real-time compliance rules.

14. The method according to claim 13 wherein the plurality of databases comprises at least one of a plurality of State vehicle databases, a plurality of municipal vehicle databases, plurality of county vehicle databases, or a plurality of Federal vehicle databases.

15. The method according to claim 13 wherein the vehicle is a delivery truck.

16. The method according to claim 13 wherein the CVD radio is a WiFi radio.

17. The method according to claim 13 wherein the CVD obtains a vehicle identification number (VIN) from an on-board computer and transmits the VIN with the location to the server for verification of the vehicle.

Description

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

(1) FIG. 1 is a block diagram of system for securely connecting a wireless device to a single access point in a vehicle.

(2) FIG. 2 is a block diagram of system for securely connecting a wireless device to a single access point in a vehicle.

(3) FIG. 3 is an illustration of a driver identifying a vehicle through connection of a tablet computer to an unpublished network.

(4) FIG. 4 is an isolated view of general electrical components of a mobile communication device.

(5) FIG. 5 is an isolated view of general electrical components of a server.

(6) FIG. 6 is a flow chart of method for securely connecting a wireless device to a single access point in a vehicle.

(7) FIG. 7 is an illustration of a system for securely connecting a wireless device to a single access point in a vehicle.

(8) FIG. 8 is an illustration of a driver identifying a vehicle through connection of a tablet computer to an unpublished network.

(9) FIG. 9 is a flow diagram.

(10) FIG. 10 is a flow diagram.

DETAILED DESCRIPTION OF THE INVENTION

(11) FIGS. 1 and 2 illustrate a pairing process for a system 100 for securely connecting a wireless device to a single access point in a vehicle. The secure connection is preferably established between a tablet computer 110 and connected vehicle device (“CVD”) 130. The CVD 130 is preferably physically connected to an on-board computer of a vehicle. The vehicle is preferably a delivery truck or a long-haul semi-truck. The CVD 130 does not broadcast a SSID, and thus the wireless network is unpublished. The tablet computer 110, having previously paired with the CVD 130, is used to “find” or re-pair with the wireless network of the CVD 130 since WiFi settings are retained in a memory of the tablet computer 130. At block 111, the installation begins for the tablet computer 110. At block 112, a setup screen having an ESN, a power unit identification and a tablet computer serial number is displayed. At block 113, the identifications are inputted, and at block 121 they are validated. At block 114, it finds the default SSID plus the password. At block 115, the processing occurs including the processing of the tablet computer setup and the verification of the power unit identification. At block 116, it connects with the default settings to the CVD 130 pairing with the default settings 131 of the CVD 130. At block 117, the tablet computer sends configuration data to the CVD 130. At block 132, the CVD 130 updates the WiFi settings and at block 133 validates the power unit to the VIN. At block 140, the CVD 130 is registered with a cloud computing service 140, and at block 142, the tablet computer is registered with the cloud computing service 140. At block 118, the tablet computer 110 sets the configured SSID and password from the CVD 130. At block 119, the tablet computer 110 reconnects with the configured WiFi settings. At block 134 on the CVD 130, the configured WiFi settings include the SSID, encrypted, the WPA2 PSK: encrypt (power unit identification salt) and the SSID is not broadcasted. At block 122, the settings are validated on the tablet computer 110. Block 120 is a critical error screen in which the tablet WIFI setup failed or the power unit identification was not verified. At block 123, a confirmation screen is shown on the tablet computer 110. At block 124, the setup is complete.

(12) As shown in FIG. 3, each of a multitude of trucks 210a-210d broadcast a wireless signal 224a-d for a truck specific network, with one truck 210c broadcasting a wireless signal 225. However, the SSID is not published so unless a driver is already in possession of the SSID, the driver will not be able to pair the tablet computer 110 with the CVD 130 of the truck 210 to which the driver is assigned. So even though the wireless signals 224a-d are being “broadcast”, they will not appear on a driver's tablet computer 110 (or other mobile device) unless the tablet computer 110 has already been paired with the CVD 130 of the vehicle 210. A driver 205 in possession of a tablet computer 110 pairs, using a signal 230, the tablet computer 110 with the wireless network 225 of the CVD of the truck 210c, and thus the driver locates the specific truck 210c he is assigned to in a parking lot full of identical looking trucks 210a-d.

(13) For example, on an IPHONE® device from Apple, Inc., the “UDID,” or Unique Device Identifier is a combination of forty numbers and letters, and is set by Apple and stays with the device forever.

(14) For example, on an ANDROID based system, one that uses Google Inc.'s ANDROID operating system, the ID is set by Google and created when an end-user first boots up the device. The ID remains the same unless the user does a “factory reset” of the phone, which deletes the phone's data and settings.

(15) The mobile communication device 110, or mobile device, is preferably selected from mobile phones, smartphones, tablet computers, PDAs and the like. Examples of smartphones and the device vendors include the IPHONE® smartphone from Apple, Inc., the DROID® smartphone from Motorola Mobility Inc., GALAXY S® smartphones from Samsung Electronics Co., Ltd., and many more. Examples of tablet computing devices include the IPAD® tablet computer from Apple Inc., and the XOOM™ tablet computer from Motorola Mobility Inc.

(16) The mobile communication device 110 then a communication network utilized preferably originates from a mobile communication service provider (aka phone carrier) of the customer such as VERIZON, AT&T, SPRINT, T-MOBILE, and the like mobile communication service providers, provide the communication network for communication to the mobile communication device of the end user.

(17) Wireless standards utilized include 802.11a, 802.11b, 802.11g, AX.25, 3G, CDPD, CDMA, GSM, GPRS, radio, microwave, laser, Bluetooth, 802.15, 802.16, and IrDA.

(18) BLUETOOTH™ technology operates in the unlicensed 2.4 GHz band of the radio-frequency spectrum, and in a preferred embodiment the secondary device 30 and/or primary device 25 is capable of receiving and transmitting signals using BLUETOOTHTM technology. LTE Frequency Bands include 698-798 MHz (Band 12, 13, 14, 17); 791-960 MHz (Band 5, 6, 8, 18,19,20); 1710-2170 MHz (Band 1, 2, 3, 4, 9, 10, 23, 25, 33, 34, 35, 36, 37, 39); 1427-1660.5 MH (Band 11, 21, 24); 2300-2700 MHz (Band 7, 38, 40, 41); 3400-3800 MHz (Band 22, 42, 43), and in a preferred embodiment the secondary device 30 and/or the primary device 25 is capable of receiving and transmitting signals using one or more of the LTE frequency bands. WiFi preferably operates using 802.11a, 802.11b, 802.11g, 802.11n communication formats as set for the by the IEEE, and in in a preferred embodiment the secondary device 30 and/or the primary device 25 is capable of receiving and transmitting signals using one or more of the 802.11 communication formats. Near-field communications (NFC) may also be utilized.

(19) As shown in FIG. 4, a typical mobile communication device 110 preferably includes an accelerometer 301, I/0 (input/output) 302, a microphone 303, a speaker 304, a GPS chipset 305, a Bluetooth component 306, a Wi-Fi component 307, a 3G/4G component 308, RAM memory 309, a main processor 310, an OS (operating system) 311, applications/software 312, a Flash memory 313, SIM card 314, LCD display 315, a camera 316, a power management circuit 317, a battery 318 or power source, a magnetometer 319, and a gyroscope 320.

(20) Each of the interface descriptions preferably discloses use of at least one communication protocol to establish handshaking or bi-directional communications. These protocols preferably include but are not limited to XML, HTTP, TCP/IP, Serial, UDP, FTP, Web Services, WAP, SMTP, SMPP, DTS, Stored Procedures, Import/Export, Global Positioning Triangulation, IM, SMS, MMS, GPRS and Flash. Databases that may be used with the system preferably include but are not limited to MSSQL, Access, MySQL, Progress, Oracle, DB2, Open Source DBs and others. Operating system used with the system preferably include Microsoft 2010, XP, Vista, 200o Server, 2003 Server, 2008 Server, Windows Mobile, Linux, Android, Unix, I series, AS 400 and Apple OS.

(21) The underlying protocol at the cloud server 140, is preferably Internet Protocol Suite (Transfer Control Protocol/Internet Protocol (“TCP/IP”)), and the transmission protocol to receive a file is preferably a file transfer protocol (“FTP”), Hypertext Transfer Protocol (“HTTP”), Secure Hypertext Transfer Protocol (“HTTPS”) or other similar protocols. The transmission protocol ranges from SIP to MGCP to FTP and beyond. The protocol at the authentication server 40 is most preferably HTTPS.

(22) Wireless standards include 802.11a, 802.11b, 802.11g, AX.25, 3G, CDPD, CDMA, GSM, GPRS, radio, microwave, laser, Bluetooth, 802.15, 802.16, and IrDA.

(23) Components of a cloud computing server 140 of the system 100, as shown in FIG. 5, preferably includes a CPU component 401, a graphics component 402, PCI/PCI Express 403, memory 404, non-removable storage 407, removable storage 408, Network Interface 409, including one or more connections to a fixed network, and SQL database(s) 45a-45d, which includes the venue's CRM. Included in the memory 404, is an operating system 405, a SQL server 406 or other database engine, and computer programs/software 410. The venue server 40 also includes at least one computer program configured to receive data uploads and store the data uploads in the SQL database. Alternatively, the SQL server can be installed in a separate server from the venue server 40.

(24) A flow chart for a method 600 for a secure connection to a wireless network of a vehicle is shown in FIG. 6. At block 601, the CVD broadcasts an encrypted, blind SSID based on specific vehicle data. At block 602, leveraging the known vehicle data and the encryption algorithm a mobile device searches for a vehicle having a CVD broadcasting the wireless network. At block 603, the mobile device is paired with the CVD.

(25) A system for a secure connection to a wireless network of a vehicle is shown in FIG. 7. A truck 210a. Those skilled in the pertinent art will recognize that the truck 210a may be replaced by any type of vehicle (such as a bus, sedan, pick-up, sport utility vehicle, limousine, sports car, delivery truck, van, mini-van, motorcycle, and the like) without departing from the scope of spirit of the present invention. The truck 210a preferably comprises a motorized engine 234, a vehicle identification number (“VIN”), an on-board computer 232 with a memory 231 and a connector plug 235. The on-board computer 232 preferably has a digital copy of the VIN in the memory 231. The on-board computer 232 is preferably in communication with the motorized engine 234. The truck 210a may also have a GPS component for location and navigation purposes, a satellite radio such as SIRIUS satellite radio, a driver graphical interface display, a battery, a source of fuel and other components found in a conventional long distance truck.

(26) Also in the truck 210a is a CVD 130 comprising a processor, a WiFi radio, a BLUETOOTH radio, a memory and a connector to connect to the connector plug of the on-board computer 232.

(27) A driver 205 preferably has a mobile communication device such as a tablet computer 110 in order to pair with a wireless network generated by the CVD 130 of the truck 210a. The tablet computer 110 preferably comprises a graphical user interface 335, a processor 310, a WiFi radio 307, a BLUETOOTH radio 306, and a cellular network interface 308.

(28) As shown in FIG. 8, each of a multitude of trucks 210a-210k broadcast a wireless signal 224a-k for a truck specific network, with one truck 210f broadcasting a wireless signal 225. However, all of the wireless signal 224a-224k and 225 do not publish their respective SSID so that a mobile device 110 must already be paired with the CVD 130 of the truck 210 in order to connect to the truck based wireless network 224a-224k or 225 of each of the CVDs 130 of each of the trucks 210a-210k. A driver 205 in possession of a tablet computer 110 pairs with the specific truck wireless network 225 of the CVD 130 of the truck 210f, and thus the driver locates the specific truck 210f he is assigned to in a parking lot full of identical looking trucks 210a-210k.

(29) The master device manager and device communication layer is a component of the system. Shared Key AES-256-CBC —shared versioned key between all devices and a device master for versioned device master communication. The device is self-updatable for master device manager communication if encrypted response payload includes updated device manager configuration. The device status post can log which devices are using which manager version and validation of deployment authentication registration. Upon successful communication with device manager, the device will attempt to communicate with given API host. Upon successful API host communication, will report back to device manager as provisioned =true. Upon successful installation, the device should be able to gather a VIN number from an installed truck. Once the VIN exists, the device will send a new status to the device manager with VIN defined and it will record when the device was installed.

(30) Device and deployment API communication layer is a component of the system. Once a device gets deployment host API configuration information from a device master, it will have the URL, API version and token to communicate with the deployment's API. API tokens are unique per deployment host and used along with the device's serial number to create an API authentication key. Once the API authentication key is generated, it is passed along with each API request via the X-Authorization header from the device. On a first communication with the deployment API, the device will download a configuration defined for the device. This will include various pieces of information based on the type of device it is and which version of the apps/roms are involved. For example: Apps/Versions; Roms/Versions; Config Settings; Deployment Config, Log parameters, Permissions; SSID List + Geo Fences; Can Bus Service Config.

(31) One embodiment is a system for vehicle dynamic compliance with multiple vehicle statutes and regulations. The system comprises a truck 210, a CVD 130, a tablet computer 110, a server 140 and a plurality of databases. The vehicle comprises an on-board computer with a memory having a vehicle identification number (VIN), a connector plug, and a motorized engine. The CVD 130 comprises a processor, a WiFi radio, a BLUETOOTH radio, a memory, and a connector for mating with the connector plug of the vehicle. The tablet computer 110 comprises a graphical user interface, a processor, a WiFi radio, a BLUETOOTH radio, and a cellular network interface. A location of the truck 210 is determined using a GPS component of the truck 210. The location of the truck 210 is transmitted to the server 140 by the CVD. The server 140 retrieves real-time compliance rules for the location of the truck from the plurality of databases, which are preferably State vehicle databases, municipal vehicle databases, county vehicle databases, and Federal vehicle databases. The server 140 transmits the real-time compliance rules to CVD 130 for display on the tablet computer 110 so that a driver of the truck 210 can stay in real-time compliance with State and Federal motor vehicle and driving rules. The rules pertain to speed limits, transport of toxic waste, the transport of refrigerated cargo, the rest durations for drivers, the necessary insurance coverage, the type of taxes and fees to be paid, and the like. The display on the tablet computer is preferably in the form of a visual alert, an audio alert or a haptic alert. Other displays include forms such as attestation forms, and data such as timers, current speed limits, and the like. The trigger for each jurisdiction is preferably from the GPS of the truck 210, the speed of the truck 210, cellular or WiFi triangulation from a network, and the like.

(32) The CVD 130 obtains the vehicle identification number (VIN) from the on-board computer and transmits the VIN with the location to the server 140 for verification of the truck 210.

(33) Another embodiment is a system for utilizing multiple vehicle odometer values. The system comprises a vehicle 210, a CVD 130, a tablet computer 110, a server 140 and a plurality of databases. The vehicle comprises an on-board computer with a memory having a vehicle identification number (VIN), a connector plug, a motorized engine, an odometer component from an engine source, an odometer component from a dashboard source, an odometer component from a chassis source, and an odometer component from a transmission source. Thus, the truck 210 has a multiple of odometers that can be used to determine a mileage of the truck 210. The connected vehicle device (CVD) 130 comprises a processor, a WiFi radio, a BLUETOOTH radio, a memory, and a connector for mating with the connector plug of the vehicle. The tablet computer 110 comprises a graphical user interface, a processor, a WiFi radio, a BLUETOOTH radio, and a cellular network interface. Each of the odometer component from an engine source, the odometer component from a dashboard source, the odometer component from a chassis source, and the odometer component from a transmission source generates an odometer value. The CVD 130 generates a delta value for odometer value relative to a control odometer value. The CVD 130 monitors the odometer value from each of the odometer component from an engine source, the odometer component from a dashboard source, the odometer component from a chassis source, and the odometer component from a transmission source. The CVD 130 generates a new odometer value for one of the odometer component from an engine source, the odometer component from a dashboard source, the odometer component from a chassis source, and the odometer component from a transmission source, and the CVD modifies the odometer value by the delta value to generate the new odometer value.

(34) From the foregoing it is believed that those skilled in the pertinent art will recognize the meritorious advancement of this invention and will readily understand that while the present invention has been described in association with a preferred embodiment thereof, and other embodiments illustrated in the accompanying drawings, numerous changes modification and substitutions of equivalents may be made therein without departing from the spirit and scope of this invention which is intended to be unlimited by the foregoing except as may appear in the following appended claim. Therefore, the embodiments of the invention in which an exclusive property or privilege is claimed are defined in the following appended claims.