Note: Descriptions are shown in the official language in which they were submitted.
CA 03198428 2023-04-06
WO 2022/081494
PCT/US2021/054449
Title
Method And System For Synchronizing Events Within A Secure Wireless Network
(PLS-014W0)
Technical Field
The present invention generally relates to synchronizing events within a
secure wireless
network.
Background Art
[0001] The prior art discusses various techniques for wireless
networks for vehicles.
[0002] U.S. Patent Number 9215590 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.
[0003] General definitions for terms utilized in the pertinent art
are set forth below.
[0004] 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.
[0005] BLUETOOTH technology is a standard short range radio link that
operates in
the unlicensed 2.4 gigaHertz band.
[0006] FTP or File Transfer Protocol is a protocol for moving files
over the Internet
from one computer to another.
[0007] 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.
[0008] Internet is the worldwide, decentralized totality of server
computers and data-
transmission paths which can supply information to a connected and browser-
equipped client computer, and can receive and forward information entered from
the
client computer.
CA 03198428 2023-04-06
WO 2022/081494 2
PCT/US2021/054449
[0009] Media Access Control (MAC) Address is a unique identifier
assigned to the
network interface by the manufacturer.
[00010] 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.
[00011] Organizationally Unique Identifier (OUT) is a 24-bit number that
uniquely
identifies a vendor, manufacturer, or organization on a worldwide basis. The
OUT 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.
[00012] 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.
[00013] 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.
[00014] SSID (Service Set Identifier) is a 1 to 32 byte string that
uniquely names a
wireless local area network.
[00015] Transfer Control Protocol/Internet Protocol ("TCP/IP") is a protocol
for
moving files over the Internet.
[00016] URL or Uniform Resource Locator is an address on the World Wide Web.
[00017] User Interface or UT 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.
[00018] 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.
CA 03198428 2023-04-06
WO 2022/081494 3
PCT/US2021/054449
[00019] 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
[00020] The present invention provides a system and method where an assigning
authority is configured to enable, disable, or manage at least one function of
a mobile
device or CVD through a secure wireless network.
[00021] One aspect of the present invention is a method for generating an
event
session for a mobile object. The method includes accessing, through an
assigning
authority, data for a mobile object comprising at least one of a driver event,
a data
event or a sensor event data. The method also includes informing an
instruction set
based on the data and at least one input from off-vehicle data and on-vehicle
data. The
method also includes initiating a record of one or more outputs into a super-
set of
outputs to generate an event session. The method also includes associating the
event
session with a single common time signature and event. The event session
provides a
record of a defined data set from at least one data stream of the mobile
object.
[00022] Another aspect of the present invention is a system for generating an
event
session for a mobile object. The system includes a mobile device for a mobile
object,
a connected device comprising on-board data for the mobile object, an
assigning
authority engine, and at least one off-board 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. The assigning authority is configured to access data
for the
mobile object comprising at least one of an operator event, a data event or a
sensor
event data. The assigning authority is configured to inform an instruction set
based on
the data and at least one input from off-board data and on-board data. The
assigning
authority is configured to initiate a record of one or more outputs into a
super-set of
outputs to generate an event session. The assigning authority is configured to
associate the event session with a single common time signature and event. The
event
CA 03198428 2023-04-06
WO 2022/081494 4
PCT/US2021/054449
session provides a record of a defined data set from at least one data stream
of the
mobile object.
Brief Description Of The Drawings
[00023] FIG. 1 is a block diagram of a system for remote profile management
for
utilizing data and computational information from on-vehicle and off-vehicle
sources.
[00024] FIG. 2 is a block diagram of sources of data for remote profile
management
for a vehicle.
[00025] FIG. 3 is a block diagram of a system for remote profile management
for
utilizing data and computational information from on-vehicle and off-vehicle
sources.
[00026] FIG. 4 is an illustration of multiple sensors on a truck.
[00027] FIG. 4A is an illustration of multiple sensors on a truck connected to
a BUS
for the truck.
[00028] FIG. 5 is a flow chart for a method for remote profile management for
utilizing data and computational information from on-vehicle and off-vehicle
sources.
[00029] FIG. 6 is a block diagram of system for a secure communication
protocol for
connecting a wireless device to a single access point in a vehicle.
[00030] FIG. 6A is a continuation of the block diagram of FIG. 1.
[00031] FIG. 7 is a flow chart of a method for a secure connection to a
wireless
network of a vehicle.
[00032] FIG. 8 is an illustration of a driver identifying a vehicle through
connection of
a tablet computer to an unpublished network.
[00033] FIG. 9 is an isolated view of general electrical components of a
mobile
communication device.
[00034] FIG. 10 is an isolated view of general electrical components of a
server.
[00035] FIG. 11 is a flow chart of method for securely connecting a wireless
device to
a single access point in a vehicle.
[00036] FIG. 12 is an illustration of a system for securely connecting a
wireless device
to a single access point in a vehicle.
CA 03198428 2023-04-06
WO 2022/081494 5
PCT/US2021/054449
[00037] FIG. 13 is an illustration of a driver identifying a vehicle through
connection
of a tablet computer to an unpublished network.
[00038] FIG. 14 is a block diagram of a system for remote profile management
for
utilizing data and computational information from on-vehicle and off-vehicle
sources.
[00039] FIG. 15 is a block diagram of a method for synchronizing events within
a
secure wireless network.
[00040] FIG. 16 is a block diagram of a method for synchronizing events within
a
secure wireless network.
Best Mode(s) For Carrying Out The Invention
[00041] The invention allows the assigning authority to access data
(e.g., driver events,
data events, or sensor events data) and to inform an instruction set based on
off-
vehicle and/or on-vehicle data.
[00042] The "Assigning Authority" is configured to access and combine off-
vehicle
content and/or on-vehicle data in order to enable, disable, or manage at least
one
function of a mobile device connected to a CVD.
[00043] The instruction set comes from the assigning authority but preferably
resides
in the devices.
[00044] The assigning authority accesses data for a mobile object
(e.g., vehicle)
comprising at least one of a driver event, a data event or a sensor event
data. The
assigning authority informs an instruction set based on the data and input
from off-
vehicle data and/or on-vehicle data. The assigning authority initiates a
record of one
or more outputs into a super-set of outputs to generate an event session for
the mobile
object by fusing data and computational information on vehicle and off-vehicle
sources. The assigning authority associates the event session with a single
common
time signature and event. The event session provides a record (preferably for
visualization) of the total outputs created from the data stream of the mobile
object
comprising data collected within a defined period of time (a day, a week, one
trip,
...etc.).
CA 03198428 2023-04-06
WO 2022/081494 6
PCT/US2021/054449
[00045] MDM (Mobile Device Management) reacts to the conditions and manages
the
devices. MDM does the following: tells the tablet what a driver can do and
when they
can do it; adapts to the current environment as informed by the RPM (remote
platform
management); and mobile device edge self-healing: used to diagnose and
troubleshoot¨because we have RPM we can troubleshoot in encompassing method.
[00046] SCP may be used to provide secure connection to device. Dynamic MDM
would enable, disable (limit access/views), or manage at least one function on
the
device.
[00047] Examples:
[00048] Wheels in motion-limiting access:
[00049] In one embodiment, the assigning authority may be configured to enable
or
disable at least one application on the mobile device based on the vehicle,
timing,
event, and/or positioning ("VTEP") data (e.g., based on vehicle drive status
or duty
status).
[00050] Uses multiple data points to detects wheel speed and sends these data
points
over the secure wireless connection to the mobile device. The Device accesses
the
Assigning Authority's instruction set and disables, enables, or manages the
Device
functionalities and/or applications.
[00051] In another embodiment, the assigning authority may provide an
instruction set
to the Device that uses multiple data points to recognize the presence of an
attached
trailer and enable temporary access on the connected mobile device to
additional
functionality and/or Apps (e.g., access to an off-vehicle data source,
temporary
access, delivery instructions, or access protocols to a location (e.g., a
delivery
location, a building, a gate, an access controlled point of entry, a parking
structure, a
weigh station, a toll collection structure, a fueling equipment, a vehicle
service
equipment).
[00052] FIG. 1 is a block diagram of a system 1100 for generating an event
session for
a mobile object 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
CA 03198428 2023-04-06
WO 2022/081494 7
PCT/US2021/054449
program 1135, and a plurality of databases 1125, both accessible through the
cloud
1110. A vehicle 1000 preferably includes a 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. A physical structure (a
light post)
1140 has a wireless communication device (preferably a passive device and most
preferably a BLUETOOTH device) for providing data (e.g., time and date a
vehicle
passed an intersection) as an off-vehicle source.
[00053] 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 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 hare the data with the workflow application. In one
specific
example, the share data is GPS coordinates for the vehicle.
[00054] 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.
[00055] 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, a
vehicle
CA 03198428 2023-04-06
WO 2022/081494 8
PCT/US2021/054449
1000 and a CVD 135 within the vehicle 1000. The cloud sources include main
protected server/cloud 1183, an original equipment manufacturer server/cloud
1182, a
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,
databases, 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 (2001-
2008) and cloud sources 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
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
CA 03198428 2023-04-06
WO 2022/081494 9
PCT/US2021/054449
set combination is preferably any new combination of the connected data
sources data
for the specific vehicle of interest.
[00056] FIG. 15 is a block diagram of a method 1500 for synchronizing events
within
a secure wireless network. Streams of data include a job/driver 1501, a
profile of the
driver 1502, devices 1503, cameras 1504, session 1505 including driver events
1506
sensor events 1507 and data inputs from 3rd parties 1508. Other data is
generated on
premises, on the vehicle or on-cloud at 1509. At 1510, the assigning authority
engine
is configured to inform an instruction set based on the data and at least one
input from
off-board data and on-board data, initiate a record of one or more outputs
into a super-
set of outputs to generate an event session, and associate the event session
with a
single common time signature and event. At 1511, session based aggregation is
conducted with assigning at 1512, aggregating at 1513 and the session at 1514.
The
event session provides a record of a defined data set from at least one data
stream of
the mobile object.
[00057] FIG. 16 is a block diagram of a method 1600 for synchronizing events
within
a secure wireless network. On vehicle data is acquired from sensors on the
vehicle
1000 for a temporal state 1609. Off-vehicle data is acquired from a network
1650,
databases 1126, the cloud 1110 and physical structures, and then sent to a
gateway
(RPM) 1130. Additional data is acquired from an operator 1606, a profile of
the
operator 1610, a job (work assignment) 1612, and a working operation 1613. The
data
is outputted at 1614 for devices 1607 to generate an event session, and
associate the
event session with a single common time signature and event.
[00058] 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 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
CA 03198428 2023-04-06
WO 2022/081494 10
PCT/US2021/054449
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.
[00059] In one embodiment, the off-vehicle source is a mobile application
operating on
a mobile device, and the data originates from the mobile application.
[00060] 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.
[00061] 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.
[00062] 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.
[00063] Multiple vehicle connected mobility devices are preferably used with
the
system 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.
[00064] Affiliates with the system 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.
CA 03198428 2023-04-06
WO 2022/081494 11
PCT/US2021/054449
[00065] 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.
[00066] 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 (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.
[00067] The RPM 1130 preferably comprises a RPM sync 1135 for syncing with
other
devices, servers, the Cloud, the CVD and the like.
[00068] 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.
[00069] 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.
[00070] 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.
[00071] 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.
CA 03198428 2023-04-06
WO 2022/081494 12
PCT/US2021/054449
[00072] 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.
[00073] 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.
[00074] 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.
[00075] 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.
[00076] 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 invention. FIG. 4A is an illustration of
multiple sensors
on a truck connected to a data bus for the truck. Each of the sensors (oil
level sensor
1005, engine sensor 1010, a power sensor 1015, a refrigeration/HVAC sensor
1020, a
CA 03198428 2023-04-06
WO 2022/081494 13
PCT/US2021/054449
temperature sensor 1025, tire pressure sensors 1030a-d, and fuel sensor 1035)
is
preferably connected to the data bus 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.
[00077] FIG. 5 is a flow chart for a method 500 for remote profile management
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 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 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.
[00078] A system 10 for securely connecting a wireless device to a single
access point
in a vehicle for a predetermined work assignment is shown in FIGS. 6 and 6A.
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").
[00079] 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.
CA 03198428 2023-04-06
WO 2022/081494 14
PCT/US2021/054449
[00080] The vehicle gateway device 130 uses datasets 22, with the beacon ID
23, a
scan of wireless devices 24 along with the SCP definitions 26 received from
the
server/cloud 11 to compile a CVD compiled SCP packet 25. 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 SSID 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 preferably a
WiFi hotspot 32 and the passive device 61 by pairing using a BLUETOOTH
communication protocol at block 33.
[00081] 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 device gateway 130.
[00082] 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.
[00083] 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
point
CA 03198428 2023-04-06
WO 2022/081494 15
PCT/US2021/054449
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.
[00084] 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.
[00085] 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 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.
[00086] 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
CA 03198428 2023-04-06
WO 2022/081494 16
PCT/US2021/054449
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 to
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.
[00087] 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 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 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 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 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 is configured
to
CA 03198428 2023-04-06
WO 2022/081494 17
PCT/US2021/054449
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 the wireless network in a hidden
mode.
The mobile device 110 is configured to connect to the CVD 130 over the
wireless
network.
[00088] 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.
[00089] 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.
[00090] 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.
[00091] 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.
[00092] 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
CA 03198428 2023-04-06
WO 2022/081494 18
PCT/US2021/054449
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.
[00093] 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.
[00094] 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.
[00095] 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.
[00096] 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.
[00097] 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.
CA 03198428 2023-04-06
WO 2022/081494 19
PCT/US2021/054449
[00098] 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-798MHz (Band 12,
13, 14, 17); 791-9601V1Hz (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-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.
[00099] 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, SIIVI 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.
[000100] Each of the interface descriptions preferably discloses use of at
least one
communication protocol to establish handshaking or bi-directional
communications.
These protocols preferably include but are not limited to XML, HTTP, TCP/IP,
Serial,
UDP, FTP, Web Services, WAP, SMTP, SMPP, DTS, Stored Procedures,
Import/Export, Global Positioning Triangulation, IM, SMS, MMS, GPRS and Flash.
Databases that may be used with the system preferably include but are not
limited to
MSSQL, Access, MySQL, Progress, Oracle, DB2, Open Source DBs and others.
Operating system used with the system preferably include Microsoft 2010, XP,
Vista,
CA 03198428 2023-04-06
WO 2022/081494 20
PCT/US2021/054449
200o Server, 2003 Server, 2008 Server, Windows Mobile, Linux, Android, Unix, I
series, AS 400 and Apple OS.
[000101] The underlying protocol at the cloud server 11, is preferably
Internet Protocol
Suite (Transfer Control Protocol/Internet Protocol ("TCP/IP")), and the
transmission
protocol to receive a file is preferably a file transfer protocol ("FTP"),
Hypertext
Transfer Protocol ("HTTP"), Secure Hypertext Transfer Protocol ("HTTPS") or
other
similar protocols. The transmission protocol ranges from SIP to MGCP to FTP
and
beyond. The protocol at the authentication server 40 is most preferably HTTPS.
[000102] 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.
[000103] Components of a cloud computing server 40 of the system, as shown in
FIG.
10, preferably includes a CPU component 401, a graphics component 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) 45a-45d, which includes the venue's CRM. Included in the
memory
404, is an operating system 405, a SQL server 406 or other database engine,
and
computer programs/software 410. The 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 can be installed in a separate
server from
the server 40.
[000104] 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.
[000105] 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,
CA 03198428 2023-04-06
WO 2022/081494 21
PCT/US2021/054449
and the like) without departing from the scope of spirit of the present
invention. The
truck 210a preferably comprises a motorized engine 234, a vehicle
identification
number ("VIN"), an on-board computer 232 with a memory 231 and a connector
plug
235. The on-board computer 232 preferably has a digital copy of the VIN in the
memory 231. The on-board computer 232 is preferably in communication with the
motorized engine 234. The truck 210a may also have a GPS component for
location
and navigation purposes, a satellite radio such as SIRIUS satellite radio, a
driver
graphical interface display, a battery, a source of fuel and other components
found in
a conventional long distance truck.
[000106] 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.
[000107] 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.
[000108] 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 SSID so that a mobile
device
110 must already be paired with the CVD 130 of the truck 210 in order to
connect to
the truck based wireless network 224a-224k or 225 of each of the CVDs 130 of
each
of the trucks 210a-210k. A driver 205 in possession of a tablet computer 110
pairs
with the specific truck wireless network 225 of the CVD 130 of the truck 210f,
and
thus the driver locates the specific truck 210f he is assigned to in a parking
lot full of
identical looking trucks 210a-210k.
[000109] Yet another embodiment is a system for generating an event session
for a
mobile object. The system comprises a mobile device 110 for a vehicle 1000, a
CVD
135 comprising on-vehicle data for the vehicle 1000, an assigning authority
engine
CA 03198428 2023-04-06
WO 2022/081494 22
PCT/US2021/054449
1105, and at least one off-vehicle source 2000. The off vehicle source 2000 is
preferably selected from a group comprising at least one database 1125, at
least one
cloud source 1180, or at least one physical structure 1140 capable of
collecting and
transferring data in a consumable manner accessible to the session with a
communication device. The assigning authority engine 1105 is preferably
configured
to access data for a mobile object comprising at least one of a driver event,
a data
event or a sensor event data. The assigning authority engine 1105 is
preferably
configured to inform an instruction set based on the data and at least one
input from
off-vehicle data and on-vehicle data. The assigning authority engine 1105 is
preferably configured to initiate a record of one or more outputs into a super-
set of
outputs to generate an event session. The assigning authority engine 1105 is
configured to associate the event session with a single common time signature
and
event. The event session provides a record of a defined data set from at least
one data
stream of the mobile object during the specified period of time.
[000110] Yet another embodiment is a method for generating an event session
for a
mobile object. The method includes accessing, through a plurality of
permissions
granted and managed by an assigning authority engine 1105, data for a mobile
object
comprising at least one of an operator event, a data event or a sensor event
data. The
method also includes informing an instruction set based on the data and at
least one
input from off-board data and on-board data, wherein the instruction set
creates an
output, wherein the output is sequenced and associated with a single common
time
signature by a session engine. The method also includes initiating a record of
one or
more outputs into a super-set of outputs managed by the session engine to
generate an
event session, wherein each output of the super-set of outputs is associated
with a
same single common time signature and event. The event session provides a
record of
the total outputs created from at least one data stream of the mobile object
comprising
data collected within a defined period of time.
[000111] Yet another embodiment is a system for generating an event session
for a
mobile object. The system comprises a mobile device 110 for a mobile object, a
connected vehicle 135 comprising on-board data for the mobile object, an
assigning
CA 03198428 2023-04-06
WO 2022/081494 23
PCT/US2021/054449
authority engine 1105 located at a remote server 1135, and at least one off-
board
source 2000 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 engine 1105 is configured to access data for the mobile object
comprising at
least one of an operator event, a data event or a sensor event data. The
assigning
authority engine 1105 is configured to inform an instruction set based on the
data and
at least one input from off-board data and on-board data. The assigning
authority
engine 1105 is configured to initiate a record of one or more outputs into a
super-set
of outputs to generate an event session. The assigning authority engine 1105
is
configured to associate the event session with a single common time signature
and
event. The event session provides a record of a defined data set from at least
one data
stream of the mobile object.
[000112] Yet another embodiment is a method for generating an event session
for a
mobile object. The method includes accessing, through an assigning authority
engine
1105 over a secure wireless network, data for a mobile object comprising at
least one
of an operator event, a data event or a sensor event data. The method also
includes
informing an instruction set based on the data and at least one input from off-
board
data and on-board data, wherein the instruction set creates an output, wherein
the
output is sequenced and associated with a single common time signature by a
session
engine. The method also includes initiating a record of one or more outputs
into a
super-set of outputs managed by the session engine to generate an event
session,
wherein each output of the super-set of outputs is associated with a same
single
common time signature and event. The event session provides a record of the
total
outputs created from at least one data stream of the mobile object comprising
data
collected within a defined period of time.
[000113] Yet another embodiment is a method for generating an event session
for a
mobile object. The method includes accessing, through an assigning authority
engine
1105 over a fixed wireless network, data for a mobile object comprising at
least one
of an operator event, a data event or a sensor event data. The method also
includes
informing an instruction set based on the data and at least one input from off-
board
CA 03198428 2023-04-06
WO 2022/081494 24
PCT/US2021/054449
data and on-board data. The method also includes initiating a record of one or
more
outputs into a super-set of outputs to generate an event session. The method
also
includes associating the event session with a single common time signature and
event.
The event session provides a record of a defined data set from at least one
data stream
of the mobile object.
[000114] Yet another embodiment is a method for generating an event session
for a
mobile object. The method includes accessing, through an assigning authority
engine
1105, data for a mobile object comprising a known operator profile and at
least one of
a data event or a sensor event data. The method also includes informing an
instruction
set based on the data and at least one input from off-board data and on-board
data,
wherein the instruction set creates an output, wherein the output is sequenced
and
associated with a single common time signature by a session engine. The method
also
includes initiating a record of one or more outputs into a super-set of
outputs managed
by the session engine to generate an event session, wherein each output of the
super-
set of outputs is associated with a same single common time signature and
event. The
event session provides a record of the total outputs created from at least one
data
stream of the mobile object comprising data collected within a defined period
of time.
[000115] Yet another embodiment is a method for generating an event session
for a
mobile object. The method includes accessing, through an assigning authority
engine
1105, data for a mobile object comprising at least one of a known operator
profile, a
data event or a sensor event data. The method also includes informing an
instruction
set based on the data and at least one input from off-board data and on-board
data
comprising components, sensors or APIs that provide data. The method also
includes
initiating a record of one or more outputs into a super-set of outputs to
generate an
event session. The method also includes associating the event session with a
single
common time signature and event. The event session provides a record of a
defined
data set from at least one data stream of the mobile object.
[000116] Yet another embodiment is a system for generating an event session
for a
mobile object. The system comprises an assigning authority engine 1105 located
at a
remote server 1135, a mobile device 110 for a mobile object, a connected
vehicle
CA 03198428 2023-04-06
WO 2022/081494 25
PCT/US2021/054449
device 135 comprising on-board data for the mobile object, and at least one
off-
vehicle source selected from a group comprising at least one database 1125, at
least
one cloud source 1180, or at least one physical structure 1140 capable of
collecting
and transferring data in a consumable manner accessible to the session with a
communication device. The assigning authority engine 1105 is configured to
access
data over a secure wireless network for a mobile object comprising at least
one of a
driver event, a data event or a sensor event data. The assigning authority
engine 1105
is configured to inform an instruction set based on the data and at least one
input from
off-vehicle data and on-vehicle data. The assigning authority engine 1105 is
configured to initiate a record of one or more outputs into a super-set of
outputs to
generate an event session. The assigning authority engine 1105 is configured
to
associate the event session with a single common time signature and event. The
event
session provides a record of a defined data set from at least one data stream
of the
mobile object during the specified period of time.
[000117] Yet another embodiment is a system for generating an event session
for a
mobile object. The system comprises a mobile device 110 for a mobile object, a
connected vehicle device 135 comprising on-board data for the mobile object,
an
assigning authority engine 1105, and at least one off-board source selected
from a
group comprising at least one database 1125, at least one cloud source 1180,
or at
least one physical structure 1140 with a communication device. The assigning
authority engine 1105 is configured to access data over a fixed wireless
network for
the mobile object comprising at least one of an operator event, a data event
or a sensor
event data. The assigning authority engine 1105 is configured to inform an
instruction
set based on the data and at least one input from off-board data and on-board
data.
The assigning authority engine 1105 is configured to initiate a record of one
or more
outputs into a super-set of outputs to generate an event session. The
assigning
authority engine 1105 is configured to associate the event session with a
single
common time signature and event. The event session provides a record of a
defined
data set from at least one data stream of the mobile object.
CA 03198428 2023-04-06
WO 2022/081494 26
PCT/US2021/054449
[000118] Yet another embodiment is a system for generating an event session
for a
mobile object. The system comprises a mobile device 110 for a mobile object, a
connected vehicle device 135 comprising on-board data for the mobile object,
an
assigning authority engine 1105, and at least one off-board source selected
from a
group comprising at least one database 1125, at least one cloud source 1180,
or at
least one physical structure 1140 with a communication device. The assigning
authority 1105 is configured to access data over for the mobile object
comprising a
known operator profile and at least one of a data event or a sensor event
data. The
assigning authority engine 1105 is configured to inform an instruction set
based on
the data and at least one input from off-vehicle data and on-vehicle data. The
assigning authority engine 1105 is configured to initiate a record of one or
more
outputs into a super-set of outputs to generate an event session. The
assigning
authority engine 1105 is configured to associate the event session with a
single
common time signature and event. The event session provides a record of a
defined
data set from at least one data stream of the mobile object during the
specified period
of time.
[000119] Yet another embodiment is a system for generating an event session
for a
mobile object. The system comprising a mobile device 110 for a mobile object,
a
connected vehicle device 135 comprising on-board data for the mobile object,
an
assigning authority engine 1105, and off-board data and on-board data sources
comprising components, sensors or APIs that provide data. The assigning
authority
engine 1105 is configured to access data over for the mobile object comprising
at least
one of an operator event, a data event or a sensor event data. The assigning
authority
engine 11105 is configured to inform an instruction set based on the data and
at least
one input from off-vehicle data and on-vehicle data. The assigning authority
engine
1105 is configured to initiate a record of one or more outputs into a super-
set of
outputs to generate an event session. The assigning authority engine 1105 is
configured to associate the event session with a single common time signature
and
event. The event session provides a record of a defined data set from at least
one data
stream of the mobile object during the specified period of time.
CA 03198428 2023-04-06
WO 2022/081494 27
PCT/US2021/054449
[000120] The at least one off-board data is preferably generated from at least
one off-
board 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.
The at
least one off-board source is preferably at least one physical infrastructure
1140 with
the communication device selected from the group comprising a building, a
gate, an
access controlled point of entry, a parking structure, a weigh station, a
light post, a toll
collection structure, a fueling equipment and a vehicle service equipment. The
at least
one off-board source is alternatively 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. The at least one off-board source is alternatively at
least one
database and a mobile application operating on a mobile device, and the data
originates from the mobile application. The on-board source preferably
comprises a
processor, a WiFi radio, a BLUETOOTH radio, a memory storing data, and a
connector for pairing with a connector plug of the mobile object. The record
is from a
camera or other component of the mobile object. The data preferably comprises
at
least one of PSI, barometer, altimeter, speedometer, odometer, video, audio,
radar,
LIDAR, or infrared.
[000121] 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.C. 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.
[000122] 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
CA 03198428 2023-04-06
WO 2022/081494 28
PCT/US2021/054449
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.
[000123] 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 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
CA 03198428 2023-04-06
WO 2022/081494 29
PCT/US2021/054449
magnetically, while discs usually reproduce data optically with lasers.
Combinations
of the above should also be included within the scope of computer-readable
medium.
[000124] 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.
[000125] 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
MS SQL,
Access, My SQL, 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.
[000126] The underlying protocol at a server, 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 protocol at the server is preferably HTTPS.
[000127] Components of a server includes a CPU component, a graphics
component,
memory, non-removable storage, removable storage, Network Interface, including
one or more connections to a fixed network, and SQL database(s). Included in
the
memory, is an operating system, a SQL server or other database engine, and
computer programs/software.
