Note: Descriptions are shown in the official language in which they were submitted.
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
1
Assigning Authority For Electric Vehicle Charging
Technical Field
The present invention generally relates to charging electric vehicles.
Background Art
[0001] An electric vehicle (EV) is the common name given to
describing
automobiles designed to operate their electric motor on a rechargeable
battery.
The battery is recharged when the electric vehicle is connected to an electric
vehicle charging station or electric vehicle supply equipment (EVSE). Power
from the electrical grid is used to "refuel" an electric vehicle.
[0002] Electric vehicle charging stations or electric vehicle supply
equipment
(EVSE) provide an electric vehicle with the capability to recharge the
vehicle's battery or energy storage device. An electric vehicle may drive up
to
a charging station, connect to the charging station, and receive power from
the
electricity grid.
[0003] Assigning authority engine is a computer device running a
software
program that determines the parameters of an electric vehicle charging session
based on input received over a network from the connected vehicle devices,
passive devices, other devices, and/or other settings. The assigning authority
engine is optionally stored in the cloud or on premise.
[0004] Beacon is a management frame that contains all of the
information
about a network. As specified in IEEE 802.11 for Wireless Local Area
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
2
Network (WLAN), Beacon frames are periodically transmitted to announce
the presence of the network. Beacon frames typically include the WLAN's
service set identifier (S SID).
[0005] BLUETOOTH technology is a standard short range radio link that
operates in the unlicensed 2.4 gigaHertz band, defined in IEEE 802.15.1
originally an now by the Bluetooth Special Interest Group (SIG).
[0006] 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.
[0007] Secure Connection Packet (SCP) 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.
[0008] Service Set Identifier (S SID) is a 1 to 32 byte string that
uniquely
names a wireless local area network.
[0009] User Interface (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.
[00010] 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
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
3
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.
[00011] 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.
Summary Of The Invention
[00012] The present invention provides a system and method for enabling a
vehicle utilizing electrical propulsion to selectively commence a re-charging
session based on one or more variables determined by an assigning authority
that is connected to the vehicle through a mobile network.
[00013] One aspect of the present invention is a system for enabling a vehicle
utilizing electrical propulsion to selectively commence a re-charging session
based on one or more variables determined by an assigning authority that is
connected to the vehicle through a mobile network. The system preferably
comprises an assigning authority engine, an electric vehicle, a charging
station
and a mobile communications device within the electric vehicle and connected
to a secure network. The assigning authority engine is aware of the future
assignments (cargo (weight), destination, travel distance, time of travel,
operating speeds, etc.) for the vehicle and the time of charging costs for
electricity in the jurisdiction where the vehicle resides. The assigning
authority
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
4
engine is in communication with the charging station and the mobile
communication device over a secure network. The assigning authority engine
[00014] Yet another aspect of the present invention is a system for
instructing a
vehicle where and when to re-charge. The system comprises a known vehicle,
where that vehicle requires electrical charging and periodic re-charging to
power the propulsion and/or operation of that vehicle, an authorized mobile
communications device attached to a secure mobile network for a vehicle, and
on-vehicle and off-vehicle data, wherein the control of a set of constraints
on
factors such as the timing and percentage completion of a particular charge is
desired. The constraint factors may include, but are not limited to, target
charging level, targeting completion time of charging to the indicated % level
of completion, or any other user configurable quality or characteristic that
is
measurable and knowable prior to the initiation of a charging session, and a
known vehicle with an authorized mobile communications device attached to
the secure network, which is attached to the vehicle.
[00015] Yet another aspect of the present invention is a method for
instructing
a vehicle where and when to re-charge. The method includes receiving at a
server a workflow for a vehicle comprising an origination location of the
vehicle, a destination of the vehicle, a route (one or more potential routes)
to
the destination, a cargo, a time of departure, and a time of arrival. The
method
also includes receiving at the server a real-time driver profile for the
driver of
the vehicle. The method also includes receiving at the server real-time data
for
the vehicle from a CVD connected to on board diagnostics for the vehicle,
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
including a charging level. The method also includes receiving at the server a
configuration of the vehicle. The method also includes receiving at the server
a plurality of dynamic compliance rules. The method also includes receiving
at the server a plurality of configurable real-time vehicle data trigger
events.
5 The method also includes determining at the server a real-time GPS
location
for the vehicle. The method also includes determining at the server a
plurality
of potential re-charging stops along the route(s). The method also includes
calculating a re-charging stop from the plurality of re-charging stops for the
vehicle based on the workflow, the real-time driver profile, the configuration
of the vehicle, the real-time GPS location of the vehicle, the real-time
vehicle
data, the plurality of dynamic compliance rules, and the selected re-charging
station profile. The method also includes transmitting to the vehicle guidance
to the selected re-charging stop from the current location of the vehicle,
wherein the guidance includes micro-navigation to an exact charging station
(direct or inductive charge) of the re-charging stop for re-charging during a
predetermined charging time period.
[00016] Yet another aspect of the present invention is a method for
instructing
a vehicle where and when to re-charge. The method includes determining a
real-time GPS location for a vehicle. The method also includes determining a
plurality of re-charging stops along a route for the vehicle. The method also
includes calculating a re-charging stop from the plurality of re-charging
stops
for the vehicle based on the following: a workflow, a real-time driver
profile, a
configuration of the vehicle, the real-time GPS location of the vehicle, real-
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
6
time vehicle data, a plurality of dynamic compliance rules, and a selected re-
charging stop profile. The method also includes transmitting to the vehicle
guidance to the selected re-charging stop from the current location of the
vehicle, wherein the guidance includes micro-navigation to an exact re-
charging station of the re-charging stop for charging during a predetermined
time period.
[00017] 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 instructing a vehicle where and when to re-charge. The functions
include determining a real-time GPS location for a vehicle; determining a
plurality of re-charging stops along a route for the vehicle; calculating a re-
charging stop from the plurality of re-charging stops for the vehicle based on
a
workflow, a real-time driver profile, a configuration of the vehicle, the real-
time GPS location of the vehicle, real-time vehicle data, a plurality of
dynamic
compliance rules, and a selected fuel stop profile; and transmitting to the
vehicle guidance to the selected re-charging stop from the current location of
the vehicle, wherein the guidance includes micro-navigation to an exact
charging station of the re-charging stop for charging during a predetermined
time period.
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
7
Brief Description Of The Drawings
[00018] FIG. 1 is a block diagram of a system for remote profile management
(RPM) for utilizing data and computational information from on-vehicle and
off-vehicle sources.
[00019] FIG. 2 is a block diagram of sources of data for RPM for a vehicle.
[00020] FIG. 3 is a block diagram of a system for RPM for utilizing data and
computational information from on-vehicle and off-vehicle sources.
[00021] FIG. 4 is an illustration of multiple sensors on a truck.
[00022] FIG. 4A is an illustration of multiple sensors on a truck connected to
a
BUS for the truck.
[00023] FIG. 5 is a flow chart for a method for RPM for utilizing data and
computational information from on-vehicle and off-vehicle sources.
[00024] FIG. 6 is a block diagram of a system for a secure communication
protocol for connecting a wireless device to a single access point in a
vehicle.
[00025] FIG. 6A is a continuation of the block diagram of FIG. 6.
[00026] FIG. 7 is a flow chart of a method for a secure connection to a
wireless
network of a vehicle.
[00027] FIG. 8 is an illustration of a driver identifying a vehicle through
connection of a tablet computer to an unpublished network.
[00028] FIG. 9 is an isolated view of general electrical components of a
mobile
communication device.
[00029] FIG. 10 is an isolated view of general electrical components of a
server.
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
8
[00030] FIG. 11 is a flow chart of a method for securely connecting a wireless
device to a single access point in a vehicle.
[00031] FIG. 12 is an illustration of a system for securely connecting a
wireless
device to a single access point in a vehicle.
[00032] FIG. 13 is an illustration of a driver identifying a vehicle through
connection of a tablet computer to an unpublished network.
[00033] FIG. 14 is a block diagram of a system for RPM for utilizing data and
computational information from on-vehicle and off-vehicle sources.
[00034] FIG. 15 is a block diagram of a system for enabling a vehicle
utilizing
electrical propulsion to selectively commence a re-charging session.
[00035] FIG. 16 is a block diagram of a system for determining the parameters
of a charging session for an electric vehicle.
[00036] FIG. 17 is a flow chart of a method for determining the parameters of
a
charging session for an electric vehicle.
[00037] FIG. 18 is a block diagram of a system for instructing a vehicle where
and when to re-charge.
[00038] FIG. 19 is a flow chart of a method for instructing a vehicle where
and
when to re-charge.
[00039] FIG. 20 is a flow chart of a method instructing a vehicle where and
when to re-charge.
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
9
Best Mode(s) For Carrying Out The Invention
[00040] FIG. 15 is a block diagram of a system 730 for enabling a vehicle
utilizing electrical propulsion to selectively commence a re-charging session
based on one or more variables determined by an assigning authority 1105 that
is connected to the vehicle through a communications network 1110. Some
EV charging standards, such as the SAE J1772 and IEC 61851 standards, use
a pilot signal to provide signaling and communication with an EV 710. For
example, an SAE J1772 compliant pilot signal is a pulse width modulated
signal whose voltage level indicates a charging status (e.g., standby, vehicle
detected, ready, with ventilation, no power, error) and whose duty cycle
indicates an ampere capacity of the charging equipment. In some
embodiments, the EV charging circuitry 328 may generate a pilot signal in
accordance with the SAE J1772 or the IEC 61851 standards.
[00041] The constraint factors used by the assigning authority engine 1105 may
include a cable rating of a charging coupler, a duty cycle for a charging
current, a length of time for charging an electric vehicle 710, a threshold
level
for aggregate electrical consumption, a maximum allowable charge rate, a
micro-grid rating, a plug rating, a price of electricity, a protection fuse
rating,
a quantity of electricity stored within a micro-grid, a specified time for
completing the charging of an electric vehicle, a total cost of charging an
electric vehicle, an operational limit set by a grid utility or other energy
provider, a battery temperature of an electric vehicle, a current battery
charge
of an electric vehicle, a time of day, a time until an electric vehicle's next
use,
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
a weather reading, a future power draw from an electric vehicle, a level for
instantaneous electric consumption, a present power draw from an electric
vehicle, a quantity of electricity stored within a micro-grid, an option for
econo-charging, and an option for using green energy. Econo-charging allows
5 a user to reduce the overall cost of a charging transaction for an
electric
vehicle by scheduling the charge transfer around times or days where
electricity is sold at a lower price than another time. Renewable energy
refers
to electricity generated from wind turbines, solar power, hydroelectric power,
or another renewable energy resources.
10 [00042] FIG. 16 is a block diagram of a system 700 for determining the
parameters of a charging session for an electric vehicle. The system 700
includes an electric vehicle (EV) 710, and EV charging station 715, a mobile
communication device 110, and an assigning authority engine 1105. The
assigning authority engine 1105 is preferably in communication with the
mobile communication device 110 and the EV charging station 715. Further,
the assigning authority engine 1105 preferably determines a time of charging
for the EV 710 and a target charging level based on a plurality of constraint
factors.
[00043] The constraint factors utilized in the determination are the
results of
inputs, combinations of inputs or calculations derived through the use of one
or more inputs derived from applications or instruction sets delivered by the
assigning authority engine to the EV that are applicable to that EV for a
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
11
temporal period or session defined and or determined by the assigning
authority engine.
[00044] The system 700 preferably includes a secure communication network
705, wherein the assigning authority engine 1105 is in communication with
the mobile communication device 110 and the EV charging station 715 over
the secure communication network 705.
[00045] The assigning authority 1105 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 off-vehicle source is preferably at least one cloud source
selected from the group comprising a public cloud source, a private cloud
source, a hybrid cloud source, or a multi-cloud source.
[00046] The EV 710 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.
[00047] The assigning authority engine comprises a predetermined work
assignment having a temporal event with a fixed start and completion based
on at least one assignable boundary condition. An assigning authority for the
assigning authority engine 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
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
12
[00048] The mobile communication device comprises a processor, a graphical
user interface, a memory, a plurality of sensors, a wireless transceiver and a
mobile application. The EV charging station is in communication with the
assigning authority engine through the mobile communication device.
[00049] The assigning authority engine accesses a database comprising data on
a plurality of costs for charging an EV at a plurality of specific times of
the
day, and the assigning authority engine determines a most cost-effective time
of the day to charge the EV. The assigning authority engine also determines an
electric load on the EV charging station, and is configured to determine an
initial state of charge and a charge rating of the EV charging station.
Determining the time to full charge is based on the initial state of charge
and
the charge rating.
[00050] FIG. 17 is a flow chart of a method 720 for determining the parameters
of a charging session for an electric vehicle. Step 721 is determining, at an
assigning authority engine, that an EV is plugged into an EV charging station.
Step 722 is receiving, at the assigning authority engine, a plurality of
constraint factors for charging of the EV. Step 723 is determining a time of
charging for the EV and a target charging level based on a plurality of
constraint factors for the EV.
[00051] Preferably, the constraint factors utilized in the determination are
the
results of inputs, combinations of inputs or calculations derived through the
use of one or more inputs derived from applications or instruction sets
delivered by the assigning authority engine to the EV that are applicable to
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
13
that EV for a temporal period or session defined and or determined by the
assigning authority engine.
[00052] The assigning authority engine is in communication with the mobile
communication device and the EV charging station over a secure
communication network 705. 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 assigning authority engine is also configured
to
access a database comprising data on a plurality of costs for charging an EV
at
a plurality of specific times of the day, and the assigning authority engine
determines a most cost-effective time of the day to charge the EV. The
assigning authority engine is also preferably configured to determine an
electric load on the EV charging station. The assigning authority engine is
further configured to determine an initial state of charge and a charge rating
of
the EV charging station, wherein determining the time to full charge is based
on the initial state of charge and the charge rating.
[00053] FIG. 18 is a block diagram of a system 920 for instructing a vehicle
where and when to re-charge. The system comprises a known vehicle 925
requiring electrical charging and periodic re-charging to power the propulsion
and/or operation of that vehicle 925, an authorized mobile communications
device 110 attached to a secure mobile network for a vehicle, and on-vehicle
and off-vehicle data, wherein the control of a set of constraints on factors
such
as the timing and percentage completion of a particular charge is desired. The
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
14
constraint factors may include, but are not limited to, target charging level,
targeting completion time of charging to the indicated percentage level of
completion, or any other user configurable quality or characteristic that is
measurable and knowable prior to the initiation of a charging session, and a
known vehicle 925 with an authorized mobile communications device 110
attached to the secure network, which is attached to the vehicle 925.
[00054] The constraint factors utilized in the determination are the
results of
inputs, combinations of inputs or calculations derived through the use of one
or more inputs derived from instruction sets delivered by the assigning
authority to that vehicle. The applicable constraint factors to that vehicle
are
defined and/or determined by the assigning authority for a temporal period or
session. The applicable constraint factors (hours of service - HOS, driver
breaks) for a known driver are defined and/or determined by the assigning
authority.
[00055] The constraint factors utilized in the determination are the
results of
inputs, combinations of inputs or calculations derived through the use of one
or more inputs derived from applications.
[00056] Additional configurable constraints, to the existing
constraints (timing,
distance) for a known driver, known vehicle, and other data inputs, include
the
following: HOS, driver breaks, loads - percent completion requirements,
weather adjustment to range, and any other configurable quality or
characteristic. A load constraint includes ETA's (estimated time of arrival)
for
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
warehouse pickup/delivery. A weather constraint includes battery usage
information to maintain a battery in cold weather.
[00057] Inputs from on-vehicle preferably include data from sensors, inputs
derived from applications, and instruction sets on a mobile device. Inputs
from
5 off-vehicle preferably include data from infrastructure/beacon, and
instruction
sets delivered by the assigning authority.
[00058] FIG. 19 is a flow chart of a method 1220 for instructing a vehicle
where and when to re-charge, also illustrated in FIG. 18. The method includes
step 1221, receiving at a server 923 a workflow for a vehicle 925 comprising
10 an origination location 921 of the vehicle 925, a destination 950 of the
vehicle,
a route 922 (one or more potential routes) to the destination 950, a cargo, a
time of departure, and a time of arrival. At step 1222, receiving at the
server a
real-time driver profile for the driver of the vehicle. At step 1223,
receiving at
the server real-time data for the vehicle from a CVD connected to on board
15 diagnostics for the vehicle, including a charging level. At step 1224,
receiving
at the server a configuration of the vehicle. At step 1225, receiving at the
server a plurality of dynamic compliance rules. At step 1226, receiving at the
server a plurality of configurable real-time vehicle data trigger events. At
step
1227, determining at the server 923 a real-time GPS location for the vehicle.
At step 1228, determining at the server a plurality of potential re-charging
stops 930a-930e along the route(s) 922. At step 1229, calculating a re-
charging stop from the plurality of re-charging stops 930a-930e for the
vehicle
based on the workflow, the real-time driver profile, the configuration of the
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
16
vehicle, the real-time GPS location of the vehicle, the real-time vehicle
data,
the plurality of dynamic compliance rules, and the selected re-charging
station
profile. At step 1230, transmitting to the vehicle guidance the selected re-
charging stop from the current location of the vehicle, wherein the guidance
includes micro-navigation to an exact charging station (direct or inductive
charge) of the re-charging stop for re-charging during a predetermined
charging time period.
[00059] FIG. 20 is a flow chart of a method 1200 for instructing a vehicle
where and when to re-charge. The method includes step 1201, determining a
real-time GPS location for a vehicle. At step 1202, determining a plurality of
re-charging stops along a route for the vehicle. At step 1203, calculating a
re-
charging stop from the plurality of re-charging stops for the vehicle based on
the following: a workflow, a real-time driver profile, a configuration of the
vehicle, the real-time GPS location of the vehicle, real-time vehicle data, a
plurality of dynamic compliance rules, and a selected re-charging stop
profile.
At step 1204, transmitting to the vehicle guidance to the selected re-charging
stop from the current location of the vehicle, wherein the guidance includes
micro-navigation to an exact re-charging station of the re-charging stop for
charging during a predetermined time period.
[00060] A preferred embodiment of the invention includes a non-transitory
computer-readable medium that stores a program that causes a processor to
perform functions for instructing a vehicle where and when to re-charge. The
functions include determining a real-time GPS location for a vehicle;
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
17
determining a plurality of re-charging stops along a route for the vehicle;
calculating a re-charging stop from the plurality of re-charging stops for the
vehicle based on a workflow, a real-time driver profile, a configuration of
the
vehicle, the real-time GPS location of the vehicle, real-time vehicle data, a
plurality of dynamic compliance rules, and a selected fuel stop profile; and
transmitting to the vehicle guidance to the selected re-charging stop from the
current location of the vehicle, wherein the guidance includes micro-
navigation to an exact charging station of the re-charging stop for charging
during a predetermined time period.
[00061] FIG. 1 is a block diagram of a system 1100 for remote profile
management for utilizing data and computational information from on-vehicle
and off-vehicle sources. The system 1100 includes a vehicle 1000, an
assigning authority engine 1105, a remote profile manager (RPM) toolset 1130
with an RPM sync program 1135, and a plurality of databases 1125, both
accessible through the cloud 1110. The vehicle 1000 preferably includes a
connected vehicle device (CVD) 135. The remote profile manager toolset
1130 preferably includes a server 1135. The plurality of databases 1125 is
preferably composed of multiple databases 1125a-d.
[00062] The assigning authority engine 1105 preferably has a work assignment
that has been generated for a specific vehicle 1000. In a preferred
embodiment, the assigning authority engine 1105 resides at a server for the
system 1100, and the RPM toolset 1130 resides at a separate server.
Alternatively, the assigning authority engine 1105 and the RPM toolset 1130
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
18
reside at the same server. The assigning authority engine 1105 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 1000. Additionally, the
assigning authority engine 1105 provides permission to various applications to
share data for app-to-app integration. In one example, the assigning authority
engine 1105 grants permission to a workflow application running on a mobile
communication device for the vehicle 1000 to obtain data from a navigation
application running on the mobile communication device. The assigning
authority engine 1105 instructs the navigation application to share the data
with the workflow application. In one specific example, the shared data is
GPS coordinates for the vehicle.
[00063] FIG. 2 is a block diagram of a set 2000 of sources of data for remote
profile management for a vehicle. The set 2000 preferably includes vehicles
2001, devices 2002, operations 2003, assignments 2004, third parties 2005,
software apps 2006, miscellaneous 2007 and other 2008.
[00064] FIG. 3 is a block diagram of a system 1300 for remote profile
management for utilizing data and computational information from on-vehicle
and off-vehicle sources. As shown in FIG. 3, the system 1300 comprises an
assigning authority engine 1105, a remote profile manager toolset 1130,
databases (FIG. 2), cloud sources 1175, a vehicle 1000 and a CVD 135 within
the vehicle 1000. The cloud sources 1175 include a main protected
server/cloud 1183, an original equipment manufacturer server/cloud 1182, a
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
19
customer server/cloud 1181 and a public server/cloud 1180. 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
1175, databases 1125, RPM 1130 and assigning authority engine 1105
communicate with the CVD 135 utilizing various wireless communication
protocols including WiFi, cellular networks, BLUETOOTH, GPS, and the
like. The contents of each of the databases (1125a-1125d) and cloud sources
1175 are accessible and combinable by the assigning authority engine 1105 to
produce dynamic, temporal combinations of data elements and instructions for
the vehicle 1000. The assigning authority engine 1105 is configured to use the
remote profile manager toolset 1130 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 1160 to inform instruction sets delivered by the
assigning authority engine 1105. 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 1160 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 1170 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
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
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
5 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
10 sources data for the specific vehicle of interest.
[00065] FIG. 14 is a block diagram of a system 1500 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
15 sources. At step B, the RPM tool set 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
20 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.
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
21
[00066] In one embodiment, the off-vehicle source is a mobile application
operating on a mobile device, and the data originates from the mobile
application.
[00067] 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.
[00068] 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 1 supplier, device supplier and the like), a
customer cloud (end user) and/or a public cloud.
[00069] 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. In one
embodiment, the passive device is a BLUETOOTH that broadcasts a
BLUETOOTH advertisement.
[00070] Multiple vehicle connected mobility devices are preferably used with
the system 1500 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.
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
22
[00071] Affiliates with the system 1500 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 1105 to directly take data from or provide data to the vehicle CVD 135,
an authorized cloud provider, and an authorized user granted access by the
assigning authority.
[00072] The vehicle 1000 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.
[00073] As shown in FIG. 3, the vehicle 1000 has multiple endpoints with
direct connectivity to the CVD 135, 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 135,
sensors connected through a vehicle bus 105 (see FIG. 4A) to the CVD 135, or
directly to the CVD 135 via wired or wireless connection, like devices. The
vehicle 1000 is preferably a primary generator and source of VTEP data 1160.
[00074] The RPM 1130 preferably comprises a RPM sync 1135 for syncing
with other devices, servers, the Cloud, the CVD and the like.
[00075] The real-time data for the vehicle 1000 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.
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
23
[00076] 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.
[00077] 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.
[00078] 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.
[00079] A configuration of the vehicle 1000 is preferably selected from one of
a single trailer, a dual trailer, a triple trailer, and a refrigeration
trailer.
[00080] 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.
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
24
[00081] The workflow utilized by the assigning authority engine 1105
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.
[00082] In one non-limiting example, the assigning authority engine 1105
receives data over the cloud from a customer server 1181 that a shipment of
bags of potato chips were damaged in transit. The assigning authority engine
1105 accesses a CVD 135 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 1105 uses a navigation
app on the mobile device (tablet computer) to determine the route, and an
elevation of the route. The assigning authority engine 1105 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 1105 uses this information to
reroute a subsequent shipment of bags of potato chips to avoid the high
elevation mountain range.
[00083] FIG. 4 is an illustration of multiple sensors on a truck 1000. The
vehicle/truck 1000 preferably comprises an oil level sensor 1005, an engine
sensor 1010, a power sensor 1015, a refrigeration/HVAC sensor 1020, a
temperature sensor 1025, a tire pressure sensor 1030, and a fuel sensor 1035.
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
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
invention. FIG. 4A is an illustration of multiple sensors on a truck connected
to a data bus 105 for the truck. Each of the sensors (oil level sensor 1005,
engine sensor 1010, a power sensor 1015, a refrigeration/HVAC sensor 1020,
a temperature sensor 1025, tire pressure sensors 1030a-d, and fuel sensor
5 1035) is preferably connected to the data bus 105 for transferring data
to an
on-board computer of the vehicle 1000, or directly to the CVD 135.
Alternatively, some or all of the sensors use wireless communications to
communication with the CVD 135.
[00084] FIG. 5 is a flow chart for a method 500 for remote profile management
10 for utilizing data and computational information from on-vehicle and off-
vehicle sources. At block 501, the contents of each of a plurality of
databases
are accessed by an assigning authority engine. At block 502, 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 503, the
15 plurality of dynamic, temporal combinations is executed. At block 504,
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 505, one or more elements of the VTEP data is used as a basis
20 to synchronize timing between the data, or computational outputs of two
or
more sources of electronic information. At block 506, a single coherent
information picture is formed from fusing data and computational information
from the on-vehicle and the off-vehicle sources.
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
26
[00085] FIG. 6 and FIG. 6A show a system 10 for securely connecting a
wireless device to a single access point in a vehicle for a predetermined work
assignment. The system 10 preferably comprises a remote server (cloud) 11, a
vehicle gateway device 130, a smart device 110, and a passive device 61. The
vehicle gateway device 130 is preferably a connected vehicle device ("CVD").
[00086] The server/cloud 11 accesses dataset 12 and obtains driver
information. Vehicle information, mobile device information (MAC address),
passive device information (beacon ID), and other information to compile a
SCP packet 14. At block 15, the server 11 provides SCP definitions to the
vehicle gateway device 130 and the mobile device 110. At block 16 the
server/cloud 11 authorizes the SCP. At block 17, the server/cloud 11
communicates with the vehicle gateway device 130.
[00087] The vehicle gateway device 130 compiles a CVD compiled SCP
packet 25 using datasets 22, the beacon ID 23, a scan of wireless devices 24,
and the SCP definitions 26 received from the server/cloud 11. The CVD
compiled SCP packet is sent to the cloud/server 11 at block 16 and
authorization/validation of the CVD compiled SCP packet is received at block
27. At block 28 the SCP is authorized for broadcasting at the vehicle gateway
device 130 a wireless network with a hidden and hashed S SID unique to the
vehicle, the hidden and hashed SSID generated from the validated SCP packet.
At block 29, the vehicle gateway device 130 communicates the broadcast with
the server/cloud 11. At block 31, the vehicle gateway device 130
communicates with other devices, namely the smart device 110 over
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
27
preferably a WiFi hotspot 32 and the passive device 61 by pairing using a
BLUETOOTH communication protocol at block 33.
[00088] At block 49, the smart device (mobile device) 110 compiles a
complied mobile device SCP packet from the SCP definitions 42, the data sets
48, the beacon ID 43, the Tablet ID 45, a driver ID 46, a vehicle ID 47 and
scan of wireless devices 44. The mobile device 110 generates the hashed
SSID and a passphrase from the complied mobile device SCP packet. At block
51, the mobile device 110 connects to the WiFi hotspot 32 of the vehicle
gateway 130.
[00089] The passive device 61 broadcast a unique ID at block 62 which is
received by the mobile device 110 and the vehicle gateway device 130. At
block 63, if a BLUETOOTH device, it broadcasts a BLUETOOTH
advertisement at block 64.
[00090] The SCP is defined by an assigning authority in the server/cloud 11.
The server/cloud 11 sends the SCP definition and any other required data in
datasets to the CVD 130 and the mobile device 110. The CVD 130 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 130 sends its
compiled SCP packet to the server 11 for authorization. The server 11 verifies
the CVD compiled SCP packet, and if valid, the server 11 transmits a
validation/approval signal to the CVD 130. The CVD then generates an access
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
28
point SSID/passphrase with SCP. Likewise, the mobile device 110 utilizes
contextual data from local datasets to compile its SCP based on the
definitions. The mobile device 110 connects to the access point of the CVD
130 using the SCP. The CVD 130 and the mobile device 110 also connect to
the passive device 61 since it is part of the SCP definition.
[00091] As used by the assigning authority engine 1105, 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.
[00092] The CVD 130 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
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
29
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.
[00093] A method 900 for a secure connection to a wireless network of a
vehicle is shown in FIG. 7. At block 901, a server generates definitions for a
SCP packet for assigning authority for a vehicle. At block 902 the server
transmits the definitions for the SCP packet to a CVD and a mobile device. At
block 903, the CVD compiles the SCP packet to generate a CVD compiled
SCP. At block 904, the CVD transmits the CVD compiled SCP to the server
for authorization. At block 905, the server transmits authorization for the
CVD
compiled SCP from to the CVD for creation of a validated SCP. At block 906,
the mobile device generates a dataset to compile a mobile device compiled
SCP. At block 907, 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 908, 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 909, the mobile
device searches for a vehicle having the CVD broadcasting the wireless
network in a hidden mode. At block 910, the mobile device securely connects
with the CVD.
[00094] One embodiment utilizes a system for vehicle to mobile device secure
wireless communications. The system comprises a vehicle 210, a CVD 130, a
mobile device 110 and a passive communication device 61. The vehicle 210
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
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.
5 The mobile device 110 comprises a graphical user interface, a mobile
application, a processor, a WiFi radio, and a cellular network interface. The
passive communication device 61 operates on a BLUETOOTH
communication protocol. The server 11 is configured to generate a plurality of
definitions for a SCP packet for assigning authority for the vehicle. The
server
10 11 is configured to transmit the plurality of definitions for the SCP
packet
from the server to the CVD 130 and the mobile device 110. The CVD 130 is
configured to compile the SCP packet to generate a CVD compiled SCP. The
CVD 130 is configured to transmit the CVD compiled SCP to the server 11
for authorization. The server 11 is configured to transmit authorization for
the
15 CVD compiled SCP to the CVD 130 for creation of a validated SCP. The
mobile device 110 is configured to generating a dataset to compile a mobile
device compiled SCP. The CVD 130 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 110
20 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 110 is configured to search for a vehicle having the CVD broadcasting
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
31
the wireless network in a hidden mode. The mobile device 110 is configured
to connect to the CVD 130 over the wireless network.
[00095] 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.
[00096] Optionally, the mobile device 110 connects to a passive device, the
passive device operating on a BLUETOOTH communication protocol. The
passive device 61 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.
[00097] The mobile device 110 preferably receives input from a driver of the
vehicle, and/or the server 11 contains the assigning authority that generates
the
SCP definitions.
[00098] The passive device 61 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 110 and the CVD 130 occurs at a
specific physical location dictated by the assigning authority through the
server 11. Preferably, the automatic connection between the mobile device
110 and the CVD occurs because the assigning authority, through the server,
has dictated that it occur.
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
32
[00099] As shown in FIG. 8, 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 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 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.
[000100] For example, on an 'PHONE 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.
[000101] 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.
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
33
[000102] 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 'PHONE
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 XOOMTm tablet computer
from Motorola Mobility Inc.
[000103] 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.
[000104] 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.
[000105] BLUETOOTHTm 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-7981V1Hz (Band 12, 13, 14, 17); 791-960MHz (Band 5, 6, 8, 18,19,20);
1710-2170MHz (Band 1, 2, 3, 4, 9, 10, 23, 25, 33, 34, 35, 36, 37, 39); 1427-
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
34
1660.5MH (Band 11, 21, 24); 2300-2700MHz (Band 7, 38, 40, 41); 3400-
3800MHz (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.
[000106] As shown in FIG. 9, 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.
[000107] 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, SFTP, SCP, RSync, Web Services,
WAP, SMTP, SMPP, DTS, Stored Procedures, Import/Export, Global
Positioning Triangulation, IM, SMS, MIMS, GPRS, WebDAP, and Flash.
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
Databases that may be used with the system preferably include but are not
limited to MS SQL, Access, My SQL, Progress, Oracle, DB2, Redis,
MongoDB, Amazon Aurora, Amazon Redshift, Amazon RDS, Amazon
DynamoDB, Apache Hadoop, Open Source DBs and others. Operating
5 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.
[000108] The underlying protocol at the cloud server 11, is preferably
Internet
Protocol Suite (Transfer Control Protocol/Internet Protocol ("TCP/IP")), and
10 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.
15 [000109] 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.
[000110] Components of a cloud computing server 40 of the system, as shown in
FIG. 10, preferably includes a CPU component 401, a graphics component
20 402, PCl/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) 415a-415d, which
includes the venue's CRM. Included in the memory 404, is an operating
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
36
system 405, a SQL server 406 or other database engine, and computer
programs/software 410. The server 40 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 406 can be
installed in a separate server from the server 40.
[000111] Cloud service providers optionally used in the present invention
include Amazon Web Services (AWS), Google Compute Engine (GCE),
Microsoft Azure, Digital Ocean, CloudFlare, Akamai, IBM Cloud, Oracle
Cloud Infrastructure, and similar.
[000112] A flow chart for an alternative method 600 for a secure connection to
a
wireless network of a vehicle is shown in FIG. 11. 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 connected with the CVD.
[000113] A system for a secure connection to a wireless network of a vehicle
is
shown in FIG. 12. 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
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
37
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.
[000114] 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.
[000115] 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.
[000116] As shown in FIG. 13, a staging yard for trucks 210a-210k, 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 S SID 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
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
38
thus the driver locates the specific truck 210f he is assigned to in a parking
lot
full of identical looking trucks 210a-210k.
[000117] 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 210, a CVD 130, a tablet computer 110, a server
40 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 40 by the CVD. The server 40 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 40 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
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
39
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.
[000118] The CVD 130 obtains the vehicle identification number (VIN) from
the on-board computer and transmits the VIN with the location to the server
40 for verification of the truck 210.
[000119] Another embodiment is a system for utilizing a remote profile manager
for utilizing multiple vehicle odometer values. The system comprises a vehicle
210, a CVD 130, a tablet computer 110, a server 40 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
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
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
5 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
10 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.
[000120] An operating system controls the execution of other computer
programs, running of the PSO platform, and provides scheduling, input-output
15 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.C. and various
other vendors), Android and variants thereof (available from Google, Inc. of
20 Mountain View, Calif), Apple OS X, iOs and variants thereof (available
from
Apple, Inc. of Cupertino, Calif.), or the like.
[000121] The system and method described in connection with the embodiments
disclosed herein is preferably embodied directly in hardware, in a software
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
41
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.
[000122] 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. Computer-readable media includes
both computer storage media and communication media including any
medium that facilitates transfer of a computer program from one place to
another. 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
CA 03212995 2023-09-08
WO 2022/203940
PCT/US2022/020822
42
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.
[000123] 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.
[000124] 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. The databases used with the system
preferably include but are not limited to MSSQL, Access, MySQL, 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.
