Patent Description:
The prior art discusses various techniques for wireless networks for vehicles.

<CIT> for Authentication Using Vehicle Data Pairing discloses the wireless pairing of a portable device with an on-board computer of a vehicle for authenticating a transaction with a third party. Chinese Patent Application Publication No. <CIT> relates to a data synchronization system and method.

General definitions for terms utilized in the pertinent art are set forth below.

Beacon is a management frame that contains all of the information about a network. In a WLAN, Beacon frames are periodically transmitted to announce the presence of the network.

BLUETOOTH technology is a standard short range radio link that operates in the unlicensed <NUM> gigaHertz band.

FTP or File Transfer Protocol is a protocol for moving files over the Internet from one computer to another.

Hypertext Transfer Protocol ("HTTP") is a set of conventions for controlling the transfer of information via the Internet from a web server computer to a client computer, and also from a client computer to a web server, and Hypertext Transfer Protocol Secure ("HTTPS") is a communications protocol for secure communication via a network from a web server computer to a client computer, and also from a client computer to a web server by at a minimum verifying the authenticity of a web site.

Media Access Control (MAC) Address is a unique identifier assigned to the network interface by the manufacturer.

Memory generally includes any type of integrated circuit or storage device configured for storing digital data including without limitation ROM, PROM, EEPROM, DRAM, SDRAM, SRAM, flash memory, and the like.

Organizationally Unique Identifier (OUI) is a <NUM>-bit number that uniquely identifies a vendor, manufacturer, or organization on a worldwide basis. The OUI is used to help distinguish both physical devices and software, such as a network protocol, that belong to one entity from those that belong to another.

Processor generally includes all types of processors including without limitation microprocessors, general purpose processors, gate arrays, array processors, application specific integrated circuits (ASICs) and digital signal processors.

SCP (Secure Connection Packet) is used to provide authentication between multiple devices or a local party and remote host to allow for secure communication or the transfer of computer files.

User Interface or UI is the junction between a user and a computer program. An interface is a set of commands or menus through which a user communicates with a program. A command driven interface is one in which the user enter commands. A menu-driven interface is one in which the user selects command choices from various menus displayed on the screen.

Web-Server is a computer able to simultaneously manage many Internet information-exchange processes at the same time. Normally, server computers are more powerful than client computers, and are administratively and/or geographically centralized. An interactive-form information-collection process generally is controlled from a server computer, to which the sponsor of the process has access.

There are multiple sources of data that can be utilized by a vehicle for efficiency and cost savings. However, there is a need for collecting, processing and interpreting the data in a manner that can be utilized by a vehicle.

The present invention provides a system and method for utilizing a remote profile manager for a vehicle.

One aspect of the present invention is a system for utilizing data and computational information from on-vehicle and off-vehicle sources. The system comprises an assigning authority engine, a remote profile manager toolset, a plurality of databases, a plurality of cloud sources, a vehicle and a CVD within the vehicle. A plurality of contents of each of the plurality of databases are accessible and combinable by the assigning authority to produce a plurality of dynamic, temporal combinations of data elements and a plurality of instructions. The assigning authority is configured to use the remote profile manager toolset to execute the plurality of dynamic, temporal combinations. The plurality of dynamic, temporal combinations access data from the plurality of cloud sources comprising third party data and vehicle, timing, event, and/or positioning ("VTEP") data to inform a plurality of instruction sets delivered by the assigning authority. One or more elements of the VTEP data is used as the basis to synchronize timing between the data, or computational outputs of two or more sources of electronic information. A single coherent information picture is formed from fusing data and computational information from on-vehicle and off-vehicle sources.

Another aspect of the present invention is a remote profile manager for utilizing data and computational information from on-vehicle and off-vehicle sources. The remote profile manager is configured to: access and combine a plurality of contents of each of a plurality of databases by an assigning authority to produce a plurality of dynamic, temporal combinations of data elements and a plurality of instructions for a vehicle; execute the plurality of dynamic, temporal combinations; access data from the plurality of cloud sources comprising third party data and vehicle, timing, event, and/or positioning ("VTEP") data to inform a plurality of instruction sets delivered by the assigning authority; use one or more elements of the VTEP data as the basis to synchronize timing between the data, or computational outputs of two or more sources of electronic information; and form a single coherent information picture from fusing data and computational information from on-vehicle and off-vehicle sources.

Yet another aspect of the present invention a non-transitory computer-readable medium that stores a program that causes a processor to perform functions for utilizing a remote profile manager for a vehicle. The functions includes access and combine a plurality of contents of each of a plurality of databases by an assigning authority to produce a plurality of dynamic, temporal combinations of data elements and a plurality of instructions for a vehicle; execute the plurality of dynamic, temporal combinations; access data from the plurality of cloud sources comprising third party data and vehicle, timing, event, and/or positioning ("VTEP") data to inform a plurality of instruction sets delivered by the assigning authority; use one or more elements of the VTEP data as the basis to synchronize timing between the data, or computational outputs of two or more sources of electronic information; form a single coherent information picture from fusing data and computational information from on-vehicle and off-vehicle sources.

Yet another aspect of the present invention is a method for remote profile management for utilizing data and computational information from on-vehicle and off-vehicle sources. The method includes accessing a plurality of contents of each of a plurality of databases by an assigning authority. The method also includes combining the plurality of contents to produce a plurality of dynamic, temporal combinations of data elements and a plurality of instruction sets for a vehicle. The method also includes executing the plurality of dynamic, temporal combinations. The method also includes accessing data from a plurality of cloud sources comprising third party data and vehicle, timing, event, and/or positioning ("VTEP") data to inform the plurality of instruction sets delivered by the assigning authority. The method also includes using one or more elements of the VTEP data as a basis to synchronize timing between the data, or computational outputs of two or more sources of electronic information. The method also includes forming a single coherent information picture from fusing data and computational information from the on-vehicle and the off-vehicle sources.

Yet another aspect of the present invention is a system for utilizing data and computational information from on-vehicle and off-vehicle sources. The system comprises an assigning authority engine, a remote profile manager toolset, at least one on-vehicle source comprising on-vehicle data for a vehicle, and at least one off-vehicle source comprising at least one off-vehicle content. The at least one off-vehicle source is selected from a group comprising at least one database, at least one cloud source or at least one physical structure with a communication device. The assigning authority is configured to access and combine the at least one off-vehicle content and the on-vehicle data to produce a plurality of dynamic, temporal combinations of data elements and a plurality of instructions. The remote profile manager toolset is configured to execute the plurality of dynamic, temporal combinations to access vehicle, timing, event, and/or positioning ("VTEP") data to inform the plurality of instruction sets communicated by the assigning authority engine. The remote profile manager toolset is configured to use one or more elements of the VTEP data to synchronize timing between the on-vehicle data or a computational output of the off-vehicle content, to generate an information data set for the vehicle.

Yet another aspect of the present invention is a system for utilizing data and computational information from on-vehicle and off-vehicle sources. The system comprises an assigning authority engine, a remote profile manager toolset, a plurality of off-vehicle sources and a plurality of on-vehicle sources. The plurality of off-vehicle sources comprises a plurality of databases, at least one cloud source and at least one physical structure with a communication device, wherein each of the plurality of off-vehicle sources comprises off-vehicle content. The plurality of on-vehicle sources comprising a vehicle CVD, a plurality of sensors and an on-vehicle connected mobility device, each of the plurality of on-vehicle sources comprising on-vehicle data for a vehicle. The assigning authority is configured to access and combine the off-vehicle content and the on-vehicle data to produce a plurality of dynamic, temporal combinations of data elements and a plurality of instructions. The remote profile manager toolset is configured to execute the plurality of dynamic, temporal combinations to access vehicle, timing, event, and/or positioning ("VTEP") data to inform the plurality of instruction sets communicated by the assigning authority engine. The remote profile manager toolset is configured to use one or more elements of the VTEP data to synchronize timing between the on-vehicle data or a computational output of the off-vehicle content, to generate an information data set for the vehicle.

<FIG> is a block diagram of a system <NUM> for remote profile management for utilizing data and computational information from on-vehicle and off-vehicle sources. The system <NUM> includes a vehicle <NUM>, an assigning authority engine <NUM>, a remote profile manager (RPM) toolset <NUM> with an RPM sync program <NUM>, and a plurality of databases <NUM>, both accessible through the cloud <NUM>. A vehicle <NUM> preferably includes a CVD <NUM>. The remote profile manager toolset <NUM> preferably includes a server <NUM>. The plurality of databases <NUM> is preferably composed of multiple databases 1125a-d.

The assigning authority engine <NUM> preferably has a work assignment that has been generated for a specific vehicle <NUM>. In a preferred embodiment, the assigning authority engine <NUM> resides at a server for the system <NUM>, and the RPM toolset <NUM> resides at a separate server. Alternatively, the assigning authority engine <NUM> and the RPM toolset <NUM> reside at the same server. The assigning authority engine <NUM> is preferably configured to access and combine off-vehicle content and on-vehicle data, along with the work assignment, to produce dynamic, temporal combinations of data elements and instructions for the vehicle <NUM>. Additionally, the assigning authority engine <NUM> provides permission to various applications to share data for app-to-app integration. In one example, the assigning authority engine <NUM> grants permission to a workflow application running on a mobile communication device for the vehicle <NUM> to obtain data from a navigation application running on the mobile communication device. The assigning authority engine <NUM> instructs the navigation application to hare the data with the workflow application. In one specific example, the share data is GPS coordinates for the vehicle.

<FIG> is a block diagram of a set <NUM> of sources of data for remote profile management for a vehicle. The set <NUM> preferably includes vehicles <NUM>, devices <NUM>, operations <NUM>, assignments <NUM>, third parties <NUM>, software apps <NUM>, miscellaneous <NUM> and other <NUM>.

<FIG> is a block diagram of a system <NUM> for remote profile management for utilizing data and computational information from on-vehicle and off-vehicle sources. As shown in <FIG>, the system <NUM> comprises an assigning authority engine <NUM>, a remote profile manager toolset <NUM>, databases (<FIG>), cloud sources, a vehicle <NUM> and a CVD <NUM> within the vehicle <NUM>. The cloud sources include main protected server/cloud <NUM>, an original equipment manufacturer server/cloud <NUM>, a customer server/cloud <NUM> and a public server/cloud <NUM>. Multiple other servers/clouds and/or databases can be utilized with the present invention without departing from the scope and spirit of the claims. The cloud sources, databases, RPM <NUM> and assigning authority engine <NUM> communicate with the CVD <NUM> utilizing various wireless communication protocols including WiFi, cellular networks, BLUETOOTH, GPS, and the like. The contents of each of the databases (<NUM>-<NUM>) and cloud sources are accessible and combinable by the assigning authority engine <NUM> to produce dynamic, temporal combinations of data elements and instructions for the vehicle <NUM>. The assigning authority engine <NUM> is configured to use the remote profile manager tool set <NUM> to execute the dynamic, temporal combinations. The dynamic, temporal combinations access data from the cloud sources comprising third party data and vehicle, timing, event, and/or positioning ("VTEP") data <NUM> to inform instruction sets delivered by the assigning authority engine <NUM>. The instruction sets are preferably temporal permission for the on-vehicle sources and off-vehicle sources (e.g., applications) to connect and share data with each other. One or more elements of the VTEP data <NUM> is used as the basis to synchronize timing between the data, or computational outputs of two or more sources of electronic information. A single coherent information picture <NUM> is formed from fusing data and computational information from the on-vehicle and the off-vehicle sources. The new information data set combination (single coherent information picture) is a display of information generated from the combination of data from the on-vehicle sources and the off-vehicle sources. The data set can include dynamic route information (road condition changes due to weather, construction and the like), an updated driver's profile, vehicle engine date, cargo data, dynamic compliance rules, micro-navigation data, fuel stop data, inspection stations on the route, wireless communications connectivity status, time to destination, and the like. An example of a new information data set combination is imparting GPS location data from a truck/CVD onto cargo (the potato chips example). The new information data set combination is preferably any new combination of the connected data sources data for the specific vehicle of interest.

<FIG> is a block diagram of a system <NUM> for remote profile management for utilizing data and computational information from on-vehicle and off-vehicle sources. At step A, VTEP data is gathered from multiple databases, cloud services and other off-vehicle sources, as well as on-vehicle sources. At step B, the RPM toolset is used to configure multiple assigning authority rules based on the collected VTEP data. At step C, multiple instruction sets are delivered to multiple cloud services, other off-vehicle sources and on-vehicle sources. At step D, off-vehicle sources such as physical infrastructure, vehicles, mobile devices, and mobile device applications share data per the delivered instruction sets. At step E, back office managers, physical infrastructure, on-vehicle and off-vehicle sources are provided with new information data set combinations enabling novel processing capabilities for the system.

In one embodiment, the off-vehicle source is a mobile application operating on a mobile device, and the data originates from the mobile application.

In another embodiment, app to app integration is utilized to generate the information data set. The app to app integration is performed at a remote server, within an app on a mobile device, on a CVD or a combination thereof. The cloud sources preferably comprise a public cloud source, a private cloud source, a hybrid cloud source, a multi-cloud source, a service provider cloud, a telematics service provider cloud, an original equipment manufacturer cloud (truck manufacturer, Tier <NUM> supplier, device supplier and the like), a customer cloud (end user) and/or a public cloud.

The system also preferably includes physical infrastructures with communication devices comprising at least one of a building, a gate, an access controlled point of entry, a parking structure, a weigh station, a toll collection structure, a fueling equipment and a vehicle service equipment. In one embodiment, a passive device on a physical structure broadcasts a unique ID which is received by a mobile device and a vehicle gateway device. If the passive device is a BLUETOOTH device, it broadcasts a BLUETOOTH advertisement. Multiple vehicle connected mobility devices are preferably used with the system <NUM> and comprise at least one of a tablet computer, a mobile phone, a scanning device, a beacon, a RF passive or active communication device and a signature capture device.

Affiliates with the system <NUM> include at least one of another vehicle authorized to share data via vehicle-to-vehicle (V2V), Cloud, or other RF communication protocols, a TMS system authorized by the assigning authority engine <NUM> to directly take data from or provide data to the vehicle CVD <NUM>, an authorized cloud provider, and an authorized user granted access by the assigning authority.

The vehicle <NUM> is preferably one of a long-haul semi-truck, a bus, a sedan, a pick-up, a sports utility vehicle, a limousine, a sports car, a delivery truck, a van, or a mini-van.

As shown in <FIG>, the vehicle <NUM> has multiple endpoints with direct connectivity to the CVD <NUM>, and requires no routing through a cloud service. The endpoints are user interfaces or built in displays, devices connected through fixed or wireless connection to the vehicle's CVD <NUM>, sensors connected through a vehicle bus (see <FIG>) to the CVD <NUM>, or directly to the CVD <NUM> via wired or wireless connection, like devices. The vehicle <NUM> is preferably a primary generator and source of VTEP data <NUM>.

The RPM <NUM> preferably comprises a RPM sync <NUM> for syncing with other devices, servers, the Cloud, the CVD and the like.

The real-time data for the vehicle <NUM> preferably comprises a real-time speed of the vehicle, tire pressure values from a plurality of tire sensors, refrigeration/HVAC unit values, a plurality of fluid levels, a plurality of power unit values, a real-time fuel tank capacity, and a fuel type.

The plurality of configurable real-time vehicle data trigger events comprises a value outside of a predetermined range for the real-time data of the vehicle.

The real-time driver/operator profile comprises amount of time driving during a pre-determined time period, number of rest breaks during the pre-determined time period, license compliance data, physical disabilities and driving violations.

One example of an off-vehicle source is a fuel stop. A profile of a fuel stop preferably comprises real-time types of fuels available, set billing instructions, physical dimensions of a plurality of fuel pumps, GPS coordinates, hours of operation, food service availability, and resting area availability. The predetermined fueling time period is a time range to fuel the vehicle based on the real-time GPS location of the vehicle, the real-time speed of the vehicle, the distance to the selected fuel stop from the real-time GPS location of the vehicle, and the hours of operation of the fuel stop.

A configuration of the vehicle <NUM> is preferably selected from one of a single trailer, a dual trailer, a triple trailer, and a refrigeration trailer. Another example of an off-vehicle source is a database (Federal, State local) with dynamic compliance rules. The dynamic compliance rules comprise speed limits, transport of toxic waste, the transport of refrigerated cargo, the rest durations for drivers/operators, the necessary insurance coverage, and the type of taxes and fees to be paid.

The workflow utilized by the assigning authority engine <NUM> preferably comprises an origination location of the vehicle, a destination of the vehicle, a route to the destination, a cargo, a time of departure and a time of arrival. In one non-limiting example, the assigning authority engine <NUM> receives data over the cloud from a customer server <NUM> that a shipment of bags of potato chips were damaged in transit. The assigning authority engine <NUM> accesses a CVD <NUM> or mobile device for the vehicle that delivered the bags of potato chips to determine the origination location, the destination location and the route. The assigning authority engine <NUM> uses a navigation app on the mobile device (tablet computer) to determine the route, and an elevation of the route. The assigning authority engine <NUM> determines that the vehicle traveled over a high elevation mountain range that probably resulted in the damage to the bags of potato chips due to a pressure differential. The assigning authority engine <NUM> uses this information to reroute a subsequent shipment of bags of potato chips to avoid the high elevation mountain range.

<FIG> is an illustration of multiple sensors on a truck <NUM>. The vehicle/truck <NUM> preferably comprises an oil level sensor <NUM>, an engine sensor <NUM>, a power sensor <NUM>, a refrigeration/HVAC sensor <NUM>, a temperature sensor <NUM>, a tire pressure sensor <NUM>, and a fuel sensor <NUM>. Those skilled in the pertinent art will recognize that multiple other sensors may be utilized without departing from the scope and spirit of the present invention. <FIG> is an illustration of multiple sensors on a truck connected to a data bus for the truck. Each of the sensors (oil level sensor <NUM>, engine sensor <NUM>, a power sensor <NUM>, a refrigeration/HVAC sensor <NUM>, a temperature sensor <NUM>, tire pressure sensors 1030a-d, and fuel sensor <NUM>) is preferably connected to the data bus for transferring data to an on-board computer of the vehicle <NUM>, or directly to the CVD <NUM>. Alternatively, some or all of the sensors use wireless communications to communication with the CVD <NUM>.

<FIG> is a flow chart for a method <NUM> for remote profile management for utilizing data and computational information from on-vehicle and off-vehicle sources. At block <NUM>, the contents of each of a plurality of databases are accessed by an assigning authority engine. At block <NUM>, the contents are combined to produce a plurality of dynamic, temporal combinations of data elements and a plurality of instruction sets for a vehicle. At block <NUM>, the plurality of dynamic, temporal combinations is executed. At block <NUM>, data from a plurality of cloud sources comprising third party data and vehicle, timing, event, and/or positioning ("VTEP") data is accessed to inform the plurality of instruction sets delivered by the assigning authority engine to the RPM. At block <NUM>, one or more elements of the VTEP data is used as a basis to synchronize timing between the data, or computational outputs of two or more sources of electronic information. At block <NUM>, a single coherent information picture is formed from fusing data and computational information from the on-vehicle and the off-vehicle sources. A system <NUM> for securely connecting a wireless device to a single access point in a vehicle for a predetermined work assignment is shown in <FIG> and <FIG>. The system <NUM> preferably comprises a remote server (cloud) <NUM>, a vehicle gateway device <NUM>, a smart device <NUM> and a passive device <NUM>. The vehicle gateway device <NUM> is preferably a connected vehicle device ("CVD").

The server/cloud <NUM> accesses dataset <NUM> and obtains driver information. Vehicle information, mobile device information (MAC address), passive device information (beacon ID) and other information to compile a SCP packet <NUM>. At block <NUM>, the server <NUM> provides SCP definitions to the vehicle gateway device <NUM> and the mobile device <NUM>. At block <NUM> the server/cloud <NUM> authorizes the SCP. At block <NUM>, the server/cloud <NUM> communicates with the vehicle gateway device <NUM>.

The vehicle gateway device <NUM> uses datasets <NUM>, with the beacon ID <NUM>, a scan of wireless devices <NUM> along with the SCP definitions <NUM> received from the server/cloud <NUM> to compile a CVD compiled SCP packet <NUM>. The CVD compiled SCP packet is sent to the cloud/server <NUM> at block <NUM> and authorization/validation of the CVD compiled SCP packet is received at block <NUM>. At block <NUM> the SCP is authorized for broadcasting at the vehicle gateway device <NUM> a wireless network with a hidden and hashed SSID unique to the vehicle, the hidden and hashed SSID generated from the validated SCP packet. At block <NUM>, the vehicle gateway device <NUM> communicates the broadcast with the server/cloud <NUM>. At block <NUM>, the vehicle gateway device <NUM> communicates with other devices, namely the smart device <NUM> over preferably a WiFi hotspot <NUM> and the passive device <NUM> by pairing using a BLUETOOTH communication protocol at block <NUM>.

At block <NUM>, the smart device (mobile device) <NUM> compiles a complied mobile device SCP packet from the SCP definitions <NUM>, the data sets <NUM>, the beacon ID <NUM>, the Tablet ID <NUM>, a driver ID <NUM>, a vehicle ID <NUM> and scan of wireless devices <NUM>. The mobile device <NUM> generates the hashed SSID and a passphrase from the complied mobile device SCP packet. At block <NUM>, the mobile device <NUM> connects to the WiFi hotspot <NUM> of the vehicle device gateway <NUM>. The passive device <NUM> broadcast a unique ID at block <NUM> which is received by the mobile device <NUM> and the vehicle gateway device <NUM>. At block <NUM>, if a BLUETOOTH device, it broadcasts a BLUETOOTH advertisement at block <NUM>. The SCP is defined by an assigning authority in the server/cloud <NUM>. The server/cloud <NUM> sends the SCP definition and any other required data in datasets to the CVD <NUM> and the mobile device <NUM>. The CVD <NUM> adds the contextual data from local datasets to the sever-sent data to compile its SCP based definition. The local datasets include data wirelessly scanned from passive devices, preferably transmitting a BLUETOOTH beacon. Other local datasets include information from the vehicle. The CVD <NUM> sends its compiled SCP packet to the server <NUM> for authorization. The server <NUM> verifies the CVD compiled SCP packet, and if valid, the server <NUM> transmits a validation/approval signal to the CVD <NUM>. The CVD then generates an access point SSID/passphrase with SCP. Likewise, the mobile device <NUM> utilizes contextual data from local datasets to compile its SCP based on the definitions. The mobile device <NUM> connects to the access point of the CVD <NUM> using the SCP. The CVD <NUM> and the mobile device <NUM> also connect to the passive device <NUM> since it is part of the SCP definition.

As used by the assigning authority engine <NUM>, a predetermined work assignment is a temporal event with a fixed start and completion based on assignable boundary conditions. The assignable boundary condition is at least one of a predetermined time period, a geographical destination, and a set route. Alternatively, the assignable boundary condition is any feature with a beginning and a termination. The assigning authority is performed by a person or persons, who have the appropriate authority and mechanisms to assign specific tasks and assets to a specific vehicle and vehicle operator or custodian, and to assign workflow assignments to same. The predetermined work assignment is assigned to a known person or entity that has its own primary networked device accessible through a password protected user interface, a specific name and password that auto-populates or otherwise automatically satisfies a plurality of credentials requirements, wherein the plurality of credential requirements are automatically available or revoked based on the assignable boundary condition identified in a pairing event.

The CVD <NUM> preferably broadcasts a WiFi wireless network with a hidden and hashed SSID unique to the host vehicle and protected by a unique, dynamically generated and hashed passphrase. The vehicle ID is entered into an application on the tablet that is then converted to the same hashed SSID and passphrase, which allows the tablet to attempt to connect to the corresponding CVD WiFi network and begin communication.

A method <NUM> for a secure connection to a wireless network of a vehicle is shown in <FIG>. At block <NUM>, a server generates definitions for a SCP packet for assigning authority for a vehicle. At block <NUM> the server transmits the definitions for the SCP packet to a CVD and a mobile device. At block <NUM>, the CVD compiles the SCP packet to generate a CVD compiled SCP. At block <NUM>, the CVD transmits the CVD compiled SCP to the server for authorization. At block <NUM>, the server transmits authorization for the CVD compiled SCP from to the CVD for creation of a validated SCP. At block <NUM>, the mobile device generates a dataset to compile a mobile device compiled SCP. At block <NUM>, the CVD broadcasts at a wireless network with a hidden and hashed SSID unique to the vehicle. The hidden and hashed SSID is generated from the validated SCP packet. At block <NUM>, the mobile device generates the hashed SSID and a passphrase from the dataset, which allows the mobile device connect to the wireless network. At block <NUM>, the mobile device searches for a vehicle having the CVD broadcasting the wireless network in a hidden mode. At block <NUM>, the mobile device securely connects with the CVD.

One embodiment utilizes a system for vehicle to mobile device secure wireless communications. The system comprises a vehicle <NUM>, a CVD <NUM>, a mobile device <NUM> and a passive communication device <NUM>. The vehicle <NUM> comprises an on-board computer with a memory having a vehicle identification number (VIN), a connector plug, and a motorized engine. The CVD <NUM> comprises a processor, a WiFi radio, a BLUETOOTH radio, a memory, and a connector for mating with the connector plug of the vehicle. The mobile device <NUM> comprises a graphical user interface, a mobile application, a processor, a WiFi radio, and a cellular network interface. The passive communication device <NUM> operates on a BLUETOOTH communication protocol. The server <NUM> is configured to generate a plurality of definitions for a SCP packet for assigning authority for the vehicle. The server <NUM> is configured to transmit the plurality of definitions for the SCP packet from the server to the CVD <NUM> and the mobile device <NUM>. The CVD <NUM> is configured to compile the SCP packet to generate a CVD compiled SCP. The CVD <NUM> is configured to transmit the CVD compiled SCP to the server <NUM> for authorization. The server <NUM> is configured to transmit authorization for the CVD compiled SCP to the CVD <NUM> for creation of a validated SCP. The mobile device <NUM> is configured to generating a dataset to compile a mobile device compiled SCP. The CVD <NUM> is configured to broadcast a wireless network with a hidden and hashed SSID unique to the vehicle, the hidden and hashed SSID generated from the validated SCP packet. The mobile device <NUM> is configured to generate the hashed SSID and a passphrase from the dataset, which allows the mobile device connect to the wireless network. The mobile device <NUM> is configured to search for a vehicle having the CVD broadcasting the wireless network in a hidden mode. The mobile device <NUM> is configured to connect to the CVD <NUM> over the wireless network.

The dataset preferably comprises at least one of a plurality of definitions for the SCP packet, a tablet ID, a driver ID, a vehicle ID, a beacon ID, identified or defined entity/participant to the transaction, descriptions, actions, or states of thing, characteristics of identifiable devices, when present in a certain proximity and/or context.

Optionally, the mobile device <NUM> connects to a passive device, the passive device operating on a BLUETOOTH communication protocol. The passive device <NUM> is preferably a BLUETOOTH enabled device advertising a unique ID as a beacon or a complex system (speaker, computer, etc.) that emits BLUETOOTH enabled device advertising a unique ID as a beacon. The mobile device <NUM> preferably receives input from a driver of the vehicle, and/or the server <NUM> contains the assigning authority that generates the SCP definitions.

The passive device <NUM> is preferably an internal device in the vehicle or an external device posted on a gate to a facility and generating a beacon. The beacon from the passive device is preferably a mechanism to ensure that the connection between the mobile device <NUM> and the CVD <NUM> occurs at a specific physical location dictated by the assigning authority through the server <NUM>. Preferably, the automatic connection between the mobile device <NUM> and the CVD occurs because the assigning authority, through the server, has dictated that it occur.

As shown in <FIG>, a staging yard for trucks 210a-201d, each of a multitude of trucks 210a-210d broadcast a wireless signal for a truck specific network, with one truck 210c broadcasting a wireless signal <NUM>. 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 <NUM> with the CVD <NUM> of the truck <NUM> to which the driver is assigned. So even though the wireless signals are being "broadcast", they will not appear on a driver's tablet computer <NUM> (or other mobile device) unless the tablet computer <NUM> has already been paired with the CVD <NUM> of the vehicle <NUM>. A driver <NUM> in possession of a tablet computer <NUM> pairs, using a signal <NUM>, the tablet computer <NUM> with the wireless network <NUM> 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.

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.

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.

The mobile communication device <NUM>, 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. , 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. The mobile communication device <NUM> 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. Wireless standards utilized include <NUM>. 11a, <NUM>. 11b, <NUM>, AX. <NUM>, <NUM>, CDPD, CDMA, GSM, GPRS, radio, microwave, laser, Bluetooth, <NUM>, <NUM>, and IrDA.

BLUETOOTH™ technology operates in the unlicensed <NUM> band of the radio-frequency spectrum, and in a preferred embodiment the secondary device <NUM> and/or primary device <NUM> is capable of receiving and transmitting signals using BLUETOOTH™ technology. LTE Frequency Bands include <NUM>-<NUM> (Band <NUM>, <NUM>, <NUM>, <NUM>); <NUM>-<NUM> (Band <NUM>, <NUM>, <NUM>, <NUM>,<NUM>,<NUM>); <NUM>-<NUM> (Band <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>); <NUM>-<NUM>. 5MH (Band <NUM>, <NUM>, <NUM>); <NUM>-<NUM> (Band <NUM>, <NUM>, <NUM>, <NUM>); <NUM>-<NUM> (Band <NUM>, <NUM>, <NUM>), and in a preferred embodiment the secondary device <NUM> and/or the primary device <NUM> is capable of receiving and transmitting signals using one or more of the LTE frequency bands. WiFi preferably operates using <NUM>. 11a, <NUM>. 11b, <NUM>, <NUM>. 11n communication formats as set for the by the IEEE, and in in a preferred embodiment the secondary device <NUM> and/or the primary device <NUM> is capable of receiving and transmitting signals using one or more of the <NUM> communication formats. Near-field communications (NFC) may also be utilized.

As shown in <FIG>, a typical mobile communication device <NUM> preferably includes an accelerometer <NUM>, I/O (input/output) <NUM>, a microphone <NUM>, a speaker <NUM>, a GPS chipset <NUM>, a Bluetooth component <NUM>, a Wi-Fi component <NUM>, a <NUM>/<NUM> component <NUM>, RAM memory <NUM>, a main processor <NUM>, an OS (operating system) <NUM>, applications/software <NUM>, a Flash memory <NUM>, SIM card <NUM>, LCD display <NUM>, a camera <NUM>, a power management circuit <NUM>, a battery <NUM> or power source, a magnetometer <NUM>, and a gyroscope <NUM>.

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 <NUM>, XP, Vista, 200o Server, <NUM> Server, <NUM> Server, Windows Mobile, Linux, Android, Unix, I series, AS <NUM> and Apple OS.

The underlying protocol at the cloud server <NUM>, 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 <NUM> is most preferably HTTPS. Wireless standards include <NUM>. 11a, <NUM>. 11b, <NUM>, AX. <NUM>, <NUM>, CDPD, CDMA, GSM, GPRS, radio, microwave, laser, Bluetooth, <NUM>, <NUM>, and IrDA.

Components of a cloud computing server <NUM> of the system, as shown in <FIG>, preferably includes a CPU component <NUM>, a graphics component <NUM>, PCI/PCI Express <NUM>, memory <NUM>, non-removable storage <NUM>, removable storage <NUM>, Network Interface <NUM>, 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 <NUM>, is an operating system <NUM>, a SQL server <NUM> or other database engine, and computer programs/software <NUM>. The server <NUM> also preferably 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 server <NUM>.

A flow chart for an alternative method <NUM> for a secure connection to a wireless network of a vehicle is shown in <FIG>. At block <NUM>, the CVD broadcasts an encrypted, blind SSID based on specific vehicle data. At block <NUM>, 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 <NUM>, the mobile device is connected with the CVD.

A system for a secure connection to a wireless network of a vehicle is shown in <FIG>. 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 <NUM>, a vehicle identification number ("VIN"), an on-board computer <NUM> with a memory <NUM> and a connector plug <NUM>. The on-board computer <NUM> preferably has a digital copy of the VIN in the memory <NUM>. The on-board computer <NUM> is preferably in communication with the motorized engine <NUM>. 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.

Also in the truck 210a is a CVD <NUM> 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 <NUM>.

A driver <NUM> preferably has a mobile communication device such as a tablet computer <NUM> in order to pair with a wireless network generated by the CVD <NUM> of the truck 210a. The tablet computer <NUM> preferably comprises a graphical user interface <NUM>, a processor <NUM>, a WiFi radio <NUM>, a BLUETOOTH radio <NUM>, and a cellular network interface <NUM>.

As shown in <FIG>, a staging yard for trucks 210a-<NUM>, each of a multitude of trucks 210a-<NUM> broadcast a wireless signal 224a-k for a truck specific network, with one truck 210f broadcasting a wireless signal <NUM>. However, all of the wireless signal 224a-<NUM> and <NUM> do not publish their respective SSID so that a mobile device <NUM> must already be paired with the CVD <NUM> of the truck <NUM> in order to connect to the truck based wireless network 224a-<NUM> or <NUM> of each of the CVDs <NUM> of each of the trucks 210a-<NUM>. A driver <NUM> in possession of a tablet computer <NUM> pairs with the specific truck wireless network <NUM> of the CVD <NUM> 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-<NUM>.

One embodiment is a system for utilizing a remote profile manager for vehicle dynamic compliance with multiple vehicle statutes and regulations. The system comprises a truck <NUM>, a CVD <NUM>, a tablet computer <NUM>, a server <NUM> 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 <NUM> 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 <NUM> comprises a graphical user interface, a processor, a WiFi radio, a BLUETOOTH radio, and a cellular network interface. A location of the truck <NUM> is determined using a GPS component of the truck <NUM>. The location of the truck <NUM> is transmitted to the server <NUM> by the CVD. The server <NUM> 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 <NUM> transmits the real-time compliance rules to CVD <NUM> for display on the tablet computer <NUM> so that a driver of the truck <NUM> 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 <NUM>, the speed of the truck <NUM>, cellular or WiFi triangulation from a network, and the like.

The CVD <NUM> obtains the vehicle identification number (VIN) from the on-board computer and transmits the VIN with the location to the server <NUM> for verification of the truck <NUM>.

Another embodiment is a system for utilizing a remote profile manager for utilizing multiple vehicle odometer values. The system comprises a vehicle <NUM>, a CVD <NUM>, a tablet computer <NUM>, a server <NUM> 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 <NUM> has a multiple of odometers that can be used to determine a mileage of the truck <NUM>. The connected vehicle device (CVD) <NUM> 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 <NUM> 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 <NUM> generates a delta value for odometer value relative to a control odometer value. The CVD <NUM> 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 <NUM> 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.

An operating system controls the execution of other computer programs, running of the PSO platform, and provides scheduling, input-output control, file and data management, memory management, and communication control and related services. The operating system may be, for example Windows (available from Microsoft, Corp. of Redmond, Wash. ), LINUX or other UNIX variants (available from Red Hat of Raleigh, N. and various other vendors), Android and variants thereof (available from Google, Inc. of Mountain View, Calif. ), Apple OS X, iOs and variants thereof (available from Apple, Inc. of Cupertino, Calif. ), or the like.

The system and method described in connection with the embodiments disclosed herein is preferably embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module preferably resides in flash memory, ROM memory, EPROM memory, EEPROM memory, RAM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is preferably coupled to the processor, so that the processor reads information from, and writes information to, the storage medium. In the alternative, the storage medium is integral to the processor. In additional embodiments, the processor and the storage medium reside in an Application Specific Integrated Circuit (ASIC). In additional embodiments, the processor and the storage medium reside as discrete components in a computing device. In additional embodiments, the events and/or actions of a method reside as one or any combination or set of codes and/or instructions on a machine-readable medium and/or computer-readable medium, which are incorporated into a computer software program.

In additional embodiments, the functions described are implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions are stored or transmitted as one or more instructions or code on a computer-readable medium. A storage medium is any available media that is accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures, and that can be accessed by a computer. Also, any connection is termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. "Disk" and "disc", as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and BLU-RAY disc where disks usually reproduce data magnetically, while discs usually reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable medium. A computer program code for carrying out operations of the Present Invention is preferably written in an object oriented, scripted or unscripted programming language such as C++, C#, SQL, Java, Python, Javascript, Typescript, PHP, Ruby, or the like.

Claim 1:
A system (<NUM>) for utilizing data and computational information from on-vehicle and off-vehicle sources, the system comprising:
an assigning authority engine (<NUM>);
a remote profile manager toolset (<NUM>);
at least one off-vehicle source comprising at least one off-vehicle content, the at least one off-vehicle source selected from a group comprising at least one database, at least one cloud source, or at least one physical structure with a communication device; and
at least one on-vehicle source comprising on-vehicle data for a vehicle;
wherein the assigning authority is configured to access and combine the at least one off-vehicle content and the on-vehicle data to produce a plurality of dynamic, temporal combinations of data elements and a plurality of instructions;
wherein the remote profile manager toolset is configured to execute the plurality of dynamic, temporal combinations to access vehicle, timing, event, and/or positioning, VTEP, data (<NUM>) to inform the plurality of instruction sets communicated by the assigning authority engine;
wherein the remote profile manager toolset is configured to use one or more elements of the VTEP data to synchronize on-vehicle data elements or a computational output of the off-vehicle content, to generate a new information data set combination.