METHOD AND SYSTEM FOR SYNCHRONIZING EVENTS WITHIN A SECURE WIRELESS NETWORK.

Abstract

This document discloses a system (1100) and method (1600) for generating an event session for a mobile object using computational data and information from sources both inside and outside the vehicle. The system (1100) comprises an allocation authority engine (1105), a mobile device (110) for a vehicle (1000), a connected vehicle device (135) comprising data inside the vehicle for the vehicle (1000), and an outside-vehicle source selected from a database (1125), a cloud source (1180), or a physical structure (1140). The allocation authority engine (1105) is configured to inform a set of instructions based on the data and at least one input of both off-road and on-road data, initiate a record of one or more outputs in a superset of outputs to generate an event session, and associate the event session with an individual common event and timestamp.

Description

METHOD AND SYSTEM FOR SYNCHRONIZING EVENTS WITHIN A SECURE WIRELESS NETWORK i Qztrnn / cznz / e / YiAi FIELD OF INVENTION The present invention relates in general to the synchronization of events within a secure wireless network. BACKGROUND OF THE INVENTION The previous technique analyzes different techniques for wireless networks for vehicles. United States patent number 9215590 for Authentication Using Vehicle Data Pairing discloses the wireless pairing of a handheld device with a vehicle's onboard computer to authenticate a transaction with a third party. The following are general definitions of the terms used in the relevant technique. A beacon is a management panel that contains all the information about a network. In a WLAN, beacon panels are periodically transmitted to announce the network's presence. BLUETOOTH technology is a standard short-range radio link that operates in the unlicensed 2.4 gigahertz band. FTP, or File Transfer Protocol, is a protocol for moving files over the Internet from one computer to another. The Hypertext Transfer Protocol (“HTTP”) is a set of conventions for controlling the transfer of information over the Internet from a web server computer to a client computer, and also from a client computer to a web server, and the Hypertext Transfer Protocol Secure (“HTTPS”) is a communications protocol for secure communication over a network from a web server computer to a client computer, and also from a client computer to a web server by verifying at least the authenticity of a website. The Internet is the worldwide, decentralized network of server computers and data transmission paths that can supply information to a connected client computer equipped with a browser, and can receive and send information entered from the client computer. The Media Access Control (MAC) address is a unique identifier assigned to the network interface by the manufacturer. Memory in general includes any type of integrated circuit or storage device configured to store digital data, including but not limited to ROM, PROM, EEPROM, DRAM, SDRAM, SRAM, flash memory and the like. An Organizationally Unique Identifier (OUI) is a 24-bit number that uniquely identifies a vendor, manufacturer, or organization worldwide. The OUI is used to help distinguish both physical devices and software, such as a network protocol, that belong to one entity from those that belong to another. The processor in general includes all types of processors including, without limitation, microprocessors, general purpose processors, gate arrays, array processors, application-specific integrated circuits (ASIO), and digital signal processors. SCP (Secure Connection Packet) is used to provide authentication between multiple devices or a local party and a remote host computer to enable secure communication or computer file transfer. SSID (Service Set Identifier) ​​is a string of 1 to 32 bytes that uniquely names a wireless local area network. The Transfer Control Protocol / Internet Protocol (“TCP / IP”) is a protocol for moving files across the Internet. A URL, or Uniform Resource Locator, is an address on the World Wide Web. The user interface (UI) is the link between a user and a computer program. An interface is a set of commands or menus through which a user interacts with a program. A command-driven interface is one in which the user enters commands. A menu-driven interface is one in which the user selects command options from different menus displayed on the screen. A web server is a computer capable of simultaneously managing many internet data exchange processes. Server computers are typically more powerful than client computers and are administratively and / or geographically centralized. An interactive data collection process is generally controlled from a server computer, which is accessible to the process sponsor. There are multiple data sources that a vehicle can use for efficiency and cost savings. However, there is a need to collect, process, and interpret the data in a way that is usable by the vehicle. BRIEF DESCRIPTION OF THE INVENTION The present invention provides a system and method where an allocation authority is configured to enable, disable, or manage at least one function of a mobile device or CVD through a secure wireless network. One aspect of the present invention is a method for generating an event session for a mobile object. The method includes accessing, through an allocation authority, data for a mobile object comprising at least one driver event, one data event, or one sensor event data. The method also includes informing a set of instructions based on the data and at least one data input from outside the vehicle and data from inside the vehicle. The method further includes initiating a record of one or more outputs in a superset of outputs to generate an event session. The method also includes associating the event session with an individual common event and timestamp. The event session provides a record of a defined data set from at least one data stream of the mobile object. 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 the mobile object, a connected device comprising onboard data for the mobile object, an allocation authority engine, and at least one offboard 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 allocation authority is configured to access data for the mobile object comprising at least one operator event, one data event, or one sensor event data. The allocation authority is configured to report a set of instructions based on the data and at least one offboard data input and one onboard data input. The allocation authority is configured to initiate a recording of one or more outputs in a superset of outputs to generate an event session.The assignment authority is configured to associate the event session with an individual common event and timestamp. The event session provides a record of a defined dataset from at least one data stream of the moving object. BRIEF DESCRIPTION OF THE FIGURES FIGURE 1 is a block diagram of a system for remote profile management to use computational data and information from sources inside and outside the vehicle. FIGURE 2 is a block diagram of data sources for remote profile management for a vehicle. FIGURE 3 is a block diagram of a system for remote profile management to use computational data and information from sources inside and outside the vehicle. FIGURE 4 is an illustration of multiple sensors on a truck. FIGURE 4A is an illustration of multiple sensors on a truck connected to a truck BUS. FIGURE 5 is a flowchart for a method for remote profile management to utilize computational data and information from sources inside and outside the vehicle. FIGURE 6 is a block diagram of a system for a secure communication protocol to connect a wireless device to an individual access point in a vehicle. FIGURE 6A is a continuation of the block diagram in FIGURE 1. FIGURE 7 is a flowchart of a method for a secure connection to a vehicle's wireless network. FIGURE 8 is an illustration of a driver identifying a vehicle by connecting a tablet computer to an unpublished network. FIGURE 9 is an isolated view of general electrical components of a mobile communication device. FIGURE 10 is an isolated view of general electrical components of a server. FIGURE 11 is a flowchart of a method for securely connecting a wireless device to an individual access point in a vehicle. FIGURE 12 is an illustration of a system for securely connecting a wireless device to an individual access point in a vehicle. FIGURE 13 is an illustration of a driver identifying a vehicle by connecting a tablet computer to an unpublished network. FIGURE 14 is a block diagram of a system for remote profile management to utilize computational data and information from sources inside and outside the vehicle. FIGURE 15 is a block diagram of a method for synchronizing events within a secure wireless network. FIGURE 16 is a block diagram of a method for synchronizing events within a secure wireless network. DETAILED DESCRIPTION OF THE INVENTION The invention allows the allocation authority to have access to data (e.g., driver events, data events, or sensor event data) and to inform a set of instructions based on data outside the vehicle and / or inside the vehicle. The “assignment authority” is configured to access and combine content outside the vehicle and / or data inside the vehicle in order to enable, disable, or manage at least one function of a mobile device connected to a CVD. The instruction set comes from the allocation authority, but preferably resides in the devices. The allocation authority has access to data for a mobile object (e.g., a vehicle) comprising at least one driver event, one data event, or one sensor event data. The allocation authority informs a set of instructions based on the data and data input from outside the vehicle and / or inside the vehicle. The allocation authority initiates a record of one or more outputs in a superset of outputs to generate an event session for the mobile object by fusing data and computational information from inside and outside vehicle sources. The allocation authority associates the event session with an individual common event and timestamp. The event session provides a record (preferably for visualization) of the total outputs created from the mobile object's data stream, comprising data collected within a defined time period (a day, a week, a trip, etc.). Mobile Device Management (MDM) reacts to conditions and manages devices. MDM does the following: it tells the tablet what a driver can do and when; it adapts to the current environment as reported by Remote Platform Management (RPM); and mobile device edge self-repair: it is used to diagnose and troubleshoot problems, because if RPM is in place, problems can be resolved in an inclusive manner. SCP can be used to provide a secure connection to the device. Dynamic MDM would enable, disable (restrict access / views), or manage at least one function on the device. Examples: Wheels in access areas that restrict movement: In one mode, the allocation authority can be configured to enable or disable at least one application on the mobile device based on vehicle data, synchronization, event and / or positioning (“VTEP”) (e.g., based on vehicle driving status or service status). It uses multiple data points to detect wheel speed and sends these data points via a secure wireless connection to the mobile device. The device has access to the assignment authority's instruction set and can disable, enable, or manage device functionalities and / or applications. In another modality, the allocation authority may provide a set of instructions 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 applications (e.g., access to a data source outside the vehicle, temporary access, delivery instructions, or access protocols to a location (e.g., a delivery location, a building, a gate, a controlled access entry point, a parking structure, a weigh station, a toll collection structure, a fuel supply equipment, a vehicle service equipment). Figure 1 is a block diagram of a system 1100 for generating an event session for a mobile object using computational data and information from sources inside and outside the vehicle. The system 1100 includes a vehicle 1000, an allocation authority engine 1105, a remote profile manager (RPM) toolset 1130 with an RPM synchronization program 1135, and a plurality of databases 1125, both accessible via 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 preferably consists of multiple databases 1125a-d.A physical structure (a light pole) 1140 has a wireless communication device (preferably a passive device and more preferably a BLUETOOTH device) to provide data (e.g., time and date a vehicle passed through an intersection) as a source outside the vehicle. The allocation authority engine 1105 preferably has a job assignment that has been generated for a specific vehicle 1000. In a preferred embodiment, the allocation authority engine 1105 resides on a server for the 1100 system, and the RPM toolset 1130 resides on a separate server. Alternatively, the allocation authority engine 1105 and the RPM toolset 1130 reside on the same server. The allocation authority engine 1105 is preferably configured to access and combine off-vehicle content and on-vehicle data, along with the job assignment, to produce dynamic, time-based combinations of data elements and instructions for the 1000 vehicle. Additionally, the allocation authority engine 1105 provides permission for different applications to share data for application-to-application integration.In one example, allocation authority engine 1105 grants permission to a workflow application running on a mobile communication device to allow vehicle 1000 to obtain data from a navigation application running on the same mobile communication device. Allocation authority engine 1105 instructs the navigation application to share the data with the workflow application. In this specific example, the shared data is GPS coordinates for the vehicle. Figure 2 is a block diagram of a set of 2000 data sources for remote profile management for a vehicle. The set of 2000 preferably includes vehicles 2001, devices 2002, operations 2003, assignments 2004, third parties 2005, software applications 2006, miscellaneous 2007, and other 2008. Figure 3 is a block diagram of a system 1300 for remote profile management using computational data and information from sources inside and outside the vehicle. As shown in Figure 3, the system 1300 comprises an allocation authority engine 1105, a remote profile manager toolset 1130, databases (Figure 2), cloud sources, a vehicle 1000, and a CVD 135 inside the vehicle 1000. The cloud sources include the protected main cloud / server 1183, an original equipment manufacturer cloud / server 1182, a customer cloud / server 1181, and a public cloud / server 1180. Multiple other servers / clouds and / or databases may be used with the present invention without departing from the scope and spirit of the claims.The cloud sources, databases, RPM 1130, and allocation authority engine 1105 communicate with the CVD 135 using various wireless communication protocols, including Wi-Fi, cellular networks, Bluetooth, GPS, and similar technologies. The contents of each of the databases (2001–2008) and cloud sources are accessible and combinable by the allocation authority engine 1105 to produce dynamic time combinations of data elements and instructions for the vehicle 1000. The allocation authority engine 1105 is configured to use the remote profile manager toolset 1130 to execute the dynamic time combinations. These dynamic time combinations access data from the cloud sources, comprising third-party data and vehicle, synchronization, event, and / or positioning (“VTEP”) data 1160, to inform the instruction sets delivered by the allocation authority engine 1105.Instruction sets are, preferably, temporary permissions for sources inside the vehicle and sources outside the vehicle (e.g., applications) to connect and share data with each other. One or more elements of the VTEP 1160 data are used as the basis for synchronization between the data, or computational outputs, of two or more electronic information sources. An individual coherent information image (1170) is formed from fused data and computational information from sources inside and outside the vehicle. The new combination of information data sets (individual coherent information image) is an information visualization generated from the combination of data from sources inside and outside the vehicle.The dataset may include dynamic route information (changes in road conditions due to weather, construction, and the like), an updated driver profile, vehicle engine date, cargo data, dynamic compliance rules, micronavigation data, fuel stop data, inspection stations along the route, wireless communication connectivity status, time to destination, and the like. An example of a new information dataset combination is imparting GPS location data from a truck / CVD to the cargo (the potato chip example). The new information dataset combination is preferably any new combination of data from connected data sources for the specific vehicle of interest. Figure 15 is a block diagram of a method 1500 for synchronizing events within a secure wireless network. The data flows include a job / driver 1501, a driver profile 1502, devices 1503, cameras 1504, a session 1505 that includes driver events 1506, sensor events 1507, and third-party data inputs 1508. Additional data is generated on-premises, in-vehicle, or in the cloud in 1509. In 1510, the allocation authority engine is configured to inform a set of instructions based on the data and at least one off-board and on-board data input, initiate a record of one or more outputs in a superset of outputs to generate an event session, and associate the event session with an individual common event and timestamp. In 1511, session-based aggregation is carried out with allocation in 1512, aggregation in 1513, and session in 1514.The event session provides a record of a defined data set from at least one data stream of the moving object. Figure 16 is a block diagram of a method 1600 for synchronizing events within a secure wireless network. Data inside the vehicle is acquired from sensors 1000 for a temporal state 1609. Data outside the vehicle 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, an operator profile 1610, a job (job assignment) 1612, and a job operation 1613. The data is broadcast at 1614 for devices 1607 to generate an event session and associate the event session with an individual common event and timestamp. Figure 14 is a block diagram of a 1500 system for remote profile management that utilizes computational data and information from sources both inside and outside the vehicle. In step A, VTEP data is collected from multiple databases, cloud services, and other sources outside the vehicle, as well as sources inside the vehicle. In step B, the RPM toolset is used to configure multiple allocation authority rules based on the collected VTEP data. In step C, multiple instruction sets are delivered to multiple cloud services, other sources outside the vehicle, and sources inside the vehicle. In step D, the sources outside the vehicle, such as physical infrastructure, vehicles, mobile devices, and mobile applications, share data through the delivered instruction sets.In step E, office managers, physical infrastructure, sources inside and outside the vehicle are provided with new combinations of information datasets that enable new processing capabilities for the system. In one modality, the source outside the vehicle is a mobile application that operates on a mobile device, and the data originates from the mobile application. In another approach, application-to-application integration is used to generate the dataset. Application-to-application integration can be performed on a remote server, within an application on a mobile device, in a CVD, or a combination thereof. i ozhnn / cznz / R / YiAi 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 provider, device provider and the like), a customer (end user) cloud and / or a public cloud. The system also preferably includes physical infrastructure with communication devices comprising at least one building, a door, a controlled access entry point, a parking structure, a weigh station, a toll collection structure, a fuel dispensing unit, and a vehicle service unit. In one modality, a passive device in a physical structure broadcasts a unique ID that is received by a mobile device and a vehicle gate device. If the passive device is a Bluetooth device, it broadcasts a Bluetooth advertisement. Multiple vehicle-connected mobility devices are preferably used with the system and comprise at least one of a tablet computer, a mobile phone, a scanning device, a beacon, a passive or active RF communication device, and a signature capture device. Affiliates with the system include at least one other vehicle authorized to share data via vehicle-to-vehicle (V2V), cloud, or other RF communication protocols, a TMS system authorized by allocation authority engine 1105 to directly take data from or provide data to vehicle CVD 135, an authorized cloud provider, and an authorized user granted access by the allocation authority. Vehicle 1000 is preferably one of a long-haul semi-trailer, a bus, a sedan, a pickup truck, a sports utility vehicle, a limousine, a sports car, a delivery truck, a van, or a minivan. As shown in Figure 3, the vehicle 1000 has multiple endpoints with direct connectivity to the CVD 135 and does not require routing through a cloud service. The endpoints are user interfaces or integrated displays, devices connected via wired or wireless connection to the vehicle's CVD 135, sensors connected via a vehicle bus (see Figure 4A) to the CVD 135, or directly to the CVD 135 via wired or wireless connection. The vehicle 1000 is preferably a primary generator and VTEP 1160 data source. RPM 1130 preferably includes an RPM 1135 synchronization for synchronization with other devices, servers, the cloud, CVD and the like. The real-time data for vehicle 1000 preferably comprises a real-time vehicle speed, tire pressure values ​​from a plurality of i ozhnn / cznz / R / viAi tire sensors, cooling / HVAC unit values, a plurality of fluid levels, a plurality of energy unit values, a real-time fuel tank capacity, and a fuel type. The plurality of configurable real-time vehicle data activation events comprises a value outside of a predetermined range for real-time vehicle data. The real-time driver / operator profile comprises the amount of driving time during a predetermined time period, the number of breaks during the predetermined time period, license compliance data, physical disabilities, and driving violations. An example of an off-vehicle fuel source is a fuel station. A fuel station profile preferably includes real-time fuel types available, established billing instructions, physical dimensions of multiple fuel pumps, GPS coordinates, hours of operation, food service availability, and rest area availability. The predetermined refueling time period is a time interval for refueling the vehicle based on the vehicle's real-time GPS location, real-time vehicle speed, distance to the selected fuel station from the vehicle's real-time GPS location, and the fuel station's hours of operation. A vehicle configuration 1000 is preferably selected from one of a single trailer, a double trailer, a triple trailer, and a refrigerated trailer. Another example of an off-vehicle source is a database (federal, state, or local) with dynamic compliance rules. Dynamic compliance rules include speed limits, transportation of hazardous waste, transportation of refrigerated cargo, rest periods for drivers / operators, required insurance coverage, and the types of taxes and fees payable. The workflow used by the 1105 allocation authority engine preferably comprises a vehicle origin location, a vehicle destination, a route to the destination, a load, a departure time, and an arrival time. In a non-limiting example, allocation authority engine 1105 receives data via the cloud from client server 1181 that a shipment of potato chip bags was damaged in transit. Allocation authority engine 1105 accesses a CVD 135 or mobile device for the vehicle that delivered the potato chip bags to determine the origin location, destination location, and route. Allocation authority engine 1105 uses a navigation application on the mobile device (tablet-type computer) to determine the route and elevation along the route. Allocation authority engine 1105 determines that the vehicle traveled through a high-elevation mountain range, which likely resulted in the damage to the potato chip bags due to a pressure differential.Allocation authority engine 1105 uses this information to reroute a subsequent shipment of potato chip bags to avoid the high elevation mountain range. Figure 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 relevant art will recognize that other multiple sensors may be used without departing from the scope and spirit of the present invention. Figure 4A is an illustration of multiple sensors on a truck connected to a truck data bus.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 1035) is preferably connected to the data bus to transfer data to an on-board vehicle computer 1000, or directly to the CVD 135. Alternatively, some or all of the sensors use wireless communication to communicate with the CVD 135. Figure 5 is a flowchart for a 500 method for remote profile management using computational data and information from sources inside and outside the vehicle. In block 501, the contents of each of a plurality of databases are accessed by an allocation authority engine. In 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. In block 503, the plurality of dynamic temporal combinations are executed. In block 504, data from a plurality of cloud sources, comprising third-party data and vehicle, synchronization, event, and / or positioning (“VTEP”) data, is accessed to inform the plurality of instruction sets delivered by the allocation authority engine to the RPM.In block 505, one or more elements of the VTEP data are used as a basis for synchronization between data, or computational outputs, from two or more electronic information sources. In block 506, a coherent individual information image is formed from fusion data and computational information from sources inside and outside the vehicle. A system 10 for securely connecting a wireless device to an individual access point in a vehicle for a predetermined job assignment is shown in FIGURES 6 and 6A. The system 10 preferably comprises a remote server (cloud) 11, a vehicle gate device 130, an intelligent device 110, and a passive device 61. The vehicle gate device 130 is preferably a connected vehicle device (“CVD”). Server / cloud 11 accesses dataset 12 and retrieves driver information, vehicle information, mobile device information (MAC address), passive device information (beacon ID), and other information to compile SCP package 14. In block 15, server 11 provides SCP definitions to vehicle hatch device 130 and mobile device 110. In block 16, server / cloud 11 authorizes the SCP. In block 17, server / cloud 11 communicates with vehicle hatch device 130. Vehicle Hatch Device 130 uses datasets 22, with beacon ID 23, a wireless device scan 24, along with SCP definitions 26 received from server / cloud 11 to compile a CVD-compiled SCP packet 25. The CVD-compiled SCP packet is sent to cloud / server 11 in block 16, and authorization / validation of the CVD-compiled SCP packet is received in block 27. In block 28, the SCP is authorized to broadcast on Vehicle Hatch Device 130 a wireless network with a hidden and uniquely hashed SSID for the vehicle—the hidden and hashed SSID generated from the validated SCP packet. In block 29, Vehicle Hatch Device 130 communicates the broadcast to server / cloud 11.In block 31, the vehicle gate device 130 communicates with other devices, specifically, the smart device 110 via preferably a WiFi access point 32 and the passive device 61 by pairing using a BLUETOOTH communication protocol in block 33. In block 49, smart device (mobile device) 110 compiles a fulfilled mobile device SCP packet from SCP definition 42, dataset 48, beacon ID 43, tablet ID 45, driver ID 46, vehicle ID 47, and wireless device scan 44. Mobile device 110 generates a hashed SSID and password from the fulfilled mobile device SCP packet. In block 51, mobile device 110 connects to WiFi access point 32 on vehicle device gate 130. Passive device 61 broadcasts a unique ID in block 62 that is received by mobile device 110 and vehicle gate device 130. In block 63, if it is a BLUETOOTH device, it broadcasts a BLUETOOTH advertisement in block 64. The SCP is defined by an assignment authority on server / cloud 11. Server / cloud 11 sends the SCP definition and any other required data in datasets to CVD 130 and mobile device 110. CVD 130 adds contextual data from local datasets to the data sent by the server to compile its SCP-based definition. Local datasets include data wirelessly scanned from passive devices, preferably transmitting a Bluetooth beacon. Other local datasets include vehicle information. CVD 130 sends its compiled SCP packet to server 11 for authorization. Server 11 verifies the SCP packet compiled by CVD, and if valid, server 11 transmits a validation / approval signal to CVD 130. CVD then generates an access point password / SSID containing the SCP.Similarly, Mobile Device 110 uses contextual data from local datasets to compile its SCP based on the definitions. Mobile Device 110 connects to the access point of CVD 130 using the SCP. CVD 130 and Mobile Device 110 also connect to Passive Device 61, as it is part of the SCP definition. As used by the 1105 assignment authority engine, a predetermined work assignment is a temporary event with a fixed start and end based on assignable boundary conditions. An assignable boundary condition is at least one of a predetermined time period, a geographic destination, and a defined route. Alternatively, an assignable boundary condition can be any characteristic with a start and end date. Assignment authority is exercised by a person or persons who have the appropriate authority and mechanisms to assign specific tasks and assets to a specific vehicle and to the vehicle's operator or custodian, and to assign workflow assignments to them.The default job 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 are automatically populated or otherwise automatically satisfy a plurality of credential requirements, wherein the plurality of credential requirements are automatically made available or revoked based on the assignable boundary condition identified in a pairing event. The CVD 130 primarily broadcasts a Wi-Fi network with a hidden, uniquely hashed SSID for the central vehicle, protected by a dynamically generated, hashed, and unique password. The vehicle ID is entered into an application on the tablet, which then converts it into the same hashed password and SSID, allowing the tablet to attempt to connect to the corresponding CVD Wi-Fi network and initiate communication.A 900 method for a secure connection to a vehicle's wireless network is shown in FIGURE 7. In block 901, a server generates definitions for an SCP packet to assign authority to a vehicle. In block 902, the server transmits the definitions for the SCP packet to a CVD and a mobile device. In block 903, the CVD compiles the SCP packet to generate a CVD-compiled SCP. In block 904, the CVD transmits the CVD-compiled SCP to the server for authorization. In block 905, the server transmits authorization for the CVD-compiled SCP from the CVD for the creation of a validated SCP. In block 906, the mobile device generates a dataset to compile a mobile device-compiled SCP. In block 907, the CVD broadcasts on a wireless network iQztrnn / cznz / e / YiAi with a hidden SSID and a unique hash for the vehicle. The hidden and hashed SSID is generated from the validated SCP packet.In block 908, the mobile device generates a hash SSID and password from the data set, allowing it to connect to the wireless network. In block 909, the mobile device searches for a vehicle equipped with a CVD (Cycle-Controlled Device) that broadcasts the wireless network in stealth mode. In block 910, the mobile device securely connects to the CVD. One modality utilizes a system for secure wireless vehicle-to-mobile device 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 onboard computer with a memory containing a vehicle identification number (VIN), a male connector, and a motorized motor. The CVD 130 comprises a processor, a Wi-Fi radio, a Bluetooth radio, memory, and a connector for mating with the vehicle's male connector. The mobile device 110 comprises a graphical user interface, a mobile application, a processor, a Wi-Fi radio, and a cellular network interface. The passive communication device 61 operates on a Bluetooth communication protocol. The server 11 is configured to generate multiple definitions for an SCP packet to assign authority to the vehicle.Server 11 is configured to transmit the plurality of definitions for the SCP packet from the server to CVD 130 and mobile device 110. CVD 130 is configured to compile the SCP packet to generate a CVD-compiled SCP. CVD 130 is configured to transmit the CVD-compiled SCP to Server 11 for authorization. Server 11 is configured to transmit the authorization for the CVD-compiled SCP to CVD 130 for the creation of a validated SCP. Mobile device 110 is configured to generate a dataset to compile a mobile device-compiled SCP. CVD 130 is configured to broadcast a wireless network with a hidden, uniquely hashed SSID for the vehicle, the hidden, hashed SSID generated from the validated SCP packet. Mobile device 110 is configured to generate the hashed SSID and a password from the dataset, allowing the mobile device to connect to the wireless network.Mobile device 110 is configured to search for a vehicle equipped with a CVD that broadcasts the wireless network in stealth mode. Mobile device 110 is then configured to connect to CVD 130 via the wireless network. The dataset preferably comprises at least one of a plurality of definitions for the SCP package, a tablet ID, a driver ID, a vehicle ID, a beacon ID, an entity / participant identified or defined for the transaction, descriptions, actions or states of affairs, characteristics of identifiable devices, when present in a certain proximity and / or context. Optionally, the mobile device 110 connects to a passive device, which operates on a Bluetooth communication protocol. The passive device 61 is preferably a Bluetooth-enabled device that advertises a unique ID as a beacon, or a complex system (speaker, computer, etc.) that broadcasts a Bluetooth-enabled device advertising a unique ID as a beacon. Mobile device 110 preferentially receives input from a vehicle driver and / or server 11 contains the assignment authority that generates the SCP definitions. The passive device 61 is preferably an internal device in the vehicle or an external device placed on a door to a facility and which generates a beacon. The beacon of 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 allocation authority through the server 11. Preferably, the automatic connection between the mobile device 110 and the CVD occurs because the allocation authority, through the server, has dictated that it occurs. As shown in FIGURE 8, in a truck storage yard 210a-201d, each of a multitude of 210a-210d trucks broadcasts a wireless signal for a specific truck network, with one 210c truck broadcasting a 225 wireless signal. However, the SSID is not advertised, so unless a driver already has the SSID, the driver will not be able to pair the 110 tablet computer with the 130 CVD of the 210 truck to which the driver is assigned. Therefore, even though the wireless signals are being “broadcast,” they will not appear on the driver's 110 tablet computer (or other mobile device) unless the 110 tablet computer has already been paired with the 210 vehicle's CVD.A driver 205 in possession of a tablet-type computer 110 pairs, using a signal 230, the tablet-type computer 110 with the wireless network 225 of the CVD of truck 210c and thus the driver locates the specific truck 210c to which he is assigned in a parking lot full of identical-looking trucks 210a-d. For example, on an Apple, Inc. iPhone device, the “UDID” or unique device identifier is a combination of forty numbers and letters, and is set by Apple and remains with the device forever. For example, on an Android-based system, one that uses Google Inc.'s Android operating system, the ID is set by Google and created when an end user first boots up the device. The ID remains the same unless the user performs a "factory reset" of the phone, which erases the phone's data and settings. The term "mobile communication device 110," or "mobile device," is primarily selected from mobile phones, smartphones, tablet computers, PDAs, and similar devices. Examples of smartphones and device vendors include the iPhone® smartphone from Apple, Inc., the Droid® smartphone from Motorola Mobility Inc., the Galaxy S® smartphones from Samsung Electronics Co., Ltd., and many more. Examples of tablet computing devices include the iPad® tablet computer from Apple Inc., and the Xoom® tablet computer from Motorola Mobility Inc. The mobile communication device 110 and then a communication network used originates preferably from a mobile communication service provider (also known as a telephone operator) of the customer such as VERIZON, AT&T, SPRINT, TMOBILE and similar mobile communication service providers, provide the communication network for communication to the end user's mobile communication device. The wireless standards used include 802.11a, 802.11b, 802.11g, AX.25, 3G, CDPD, CDMA, GSM, GPRS, radio, microwave, laser, Bluetooth, 802.15, 802.16 and IrDA. Bluetooth® technology operates in the unlicensed 2.4 GHz band of the radio frequency spectrum, and in a preferred mode, the secondary device 30 and / or the primary device 25 is capable of receiving and transmitting signals using Bluetooth® technology. LTE frequency bands include 698–798 MHz (bands 12, 13, 14, 17); 791–960 MHz (bands 5, 6, 8, 18, 19, 20); 1710–2170 MHz (bands 1, 2, 3, 4, 9, 10, 23, 25, 33, 34, 35, 36, 37, 39); and 1427–1660.5 MHz (bands 11, 21, 24). 2300-2700 MHz (bands 7, 38, 40, 41); 3400-3800 MHz (bands 22, 42, 43), and in a preferred mode 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, and 802.11g communication formats.11 n as established for IEEE, 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 802.11 communication formats. Near field communications (NFC) may also be used. As shown in FIGURE 9, a typical mobile communication device 110 preferably includes an accelerometer 301, I / O (input / output) 302, a microphone 303, a speaker 304, a GPS chipset 305, a Bluetooth component 306, a WiFi component 307, a 3G / 4G component 308, RAM memory 309, a main processor 310, an OS (operating system) 311, applications / software 312, flash memory 313, SIM card 314, LCD screen 315, a camera 316, a power management circuit 317, a battery 318 or power supply, a magnetometer 319, and a gyroscope 320. Each interface description preferably discloses the use of at least one communication protocol for establishing acknowledgment or bidirectional communication. 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, GPS triangulation, IM, SMS, MMS, GPRS, and Flash. Databases that can be used with the system preferably include, but are not limited to, MSSQL, Access, MySQL, Progress, Oracle, DB2, open-source databases, and others. Operating systems used with the system preferably include Microsoft Windows Server 2010, XP, Vista, 2000, 2003, 2008, Windows Mobile, Linux, Android, Unix, i-series, AS / 400, and Apple OS. The underlying protocol on cloud server 11 is preferably the Internet protocol suite (Transmission Control Protocol / Internet Protocol (“TCP / IP”)), and the transmission protocol for receiving a file is preferably a File Transfer Protocol (“FTP”), Hypertext Transfer Protocol (“HTTP”), Hypertext Transfer Protocol Secure (“HTTPS”), or other similar protocols. The transmission protocol varies from SIP to MGCP to FTP and beyond. The protocol on authentication server 40 is most preferably HTTPS. 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. The components of a cloud computing server 40 of the system, as shown in FIGURE 10, preferably include a CPU component 401, a graphics component 402, PCI / PCI Express 403, memory 404, non-removable storage 407, removable storage 408, a network interface 409, which includes one or more connections to a fixed network, and SQL databases 45a-45d, which includes the site CRM. An operating system 405, an SQL server 406 or other database engine, and computer programs / software 410 are included in memory 404. The server 40 also preferably includes at least one computer program configured to receive data loads and store the data loads in the SQL database. Alternatively, the SQL server can be installed on a separate server from the server 40. A flowchart for an alternative method 600 for a secure connection to a vehicle's wireless network is shown in FIGURE 11. In block 601, the CVD broadcasts a blind, encrypted SSID based on specific vehicle data. In block 602, leveraging the known vehicle data and encryption algorithm, a mobile device searches for a vehicle that has a CVD broadcasting the wireless network. In block 603, the mobile device connects to the CVD. A system for a secure connection to a wireless network of a vehicle is shown in FIGURE 12. A truck 210a. Those skilled in the relevant art will recognize that the truck 210a can be replaced by any type of vehicle (such as a bus, sedan, pickup truck, sports utility vehicle, limousine, sports car, delivery truck, van, minivan, motorcycle, and the like) without departing from the scope 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 male connector 235. The on-board computer 232 preferably has a digital copy of the VIN in memory 231. The on-board computer 232 is preferably in communication with the motorized engine 234.The 210a truck 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 fuel source, and other components found in a conventional long-haul truck. Also in the 210a truck there is a CVD 130 comprising a processor, a WiFi radio, a BLUETOOTH radio, a memory and a connector to connect to the male connector of the on-board computer 232. A driver 205 preferably has a mobile communication device such as a tablet-type computer 110 in order to pair with a wireless network generated by the CVD 130 of the truck 210a. The tablet-type 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. As shown in FIGURE 13, a 210a21 Ok truck storage yard, each of a multitude of 210a-210k trucks broadcasts a 224a-k wireless signal for a truck-specific network, with one truck, 21 Of, broadcasting a 225 wireless signal. However, all the 224a-224k and 225 wireless signals do not advertise their respective SSIDs, so a 110 mobile device must already be paired with the CVD 130 of truck 210 in order to connect to the 224a-224k or 225 truck-based wireless network from each of the CVD 130s of each of the 210a-210k trucks. A driver 205 in possession of a tablet-type computer 110 pairs with the truck-specific wireless network 225 of the CVD 130 of truck 21 Of and, whereby, the driver locates the specific truck 21 Of to which he is assigned in a parking lot full of identical-looking trucks 210a-210k. Yet another modality 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 in-vehicle data for the vehicle 1000, an allocation authority engine 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 allocation authority engine 1105 is preferably configured to access data for a mobile object comprising at least one driver event, event data, or sensor event data.The 1105 allocation authority engine is preferably configured to report a set of instructions based on data and at least one data input from outside the vehicle and data from inside the vehicle. The 1105 allocation authority engine is preferably configured to initiate a logging of one or more outputs into a superset of outputs to generate an event session. The 1105 allocation authority engine is configured to associate the event session with an individual common event and timestamp. The event session provides a log of a defined dataset from at least one data stream of the moving object during the specified time period. Yet another modality is a method for generating an event session for a moving object. The method includes accessing, through a plurality of permissions granted and managed by an 1105 allocation authority engine, data for a moving object comprising at least one operator event, one data event, or one sensor event data. The method also includes informing a set of instructions based on the data and at least one off-board data input and one on-board data input, wherein the set of instructions creates an output, wherein the output is sequenced and associated with an individual common timestamp by a session engine. The method also includes initiating a logging of one or more outputs into a superset of outputs managed by the session engine to generate an event session, wherein each output in the superset of outputs is associated with the same individual common events and timestamp.The event session provides a record of the total outputs created from at least one data stream of the moving object comprising data collected within a defined time period. Yet another modality 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 onboard data for the mobile object, an allocation authority engine 1105 located on a remote server 1135, and at least one offboard 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 allocation authority engine 1105 is configured to access data for the mobile object comprising at least one operator event, one data event, or one sensor event data. The allocation authority engine 1105 is configured to report a set of instructions based on the data and at least one offboard data input and one onboard data input.The allocation authority engine 1105 is configured to initiate logging of one or more outputs in a superset of outputs to generate an event session. The allocation authority engine 1105 is configured to associate the event session with an individual common event and timestamp. The event session provides a record of a set of data defined from at least one data stream of the moving object. Yet another modality is a method for generating an event session for a mobile object. This method involves accessing, via an 1105 allocation authority engine over a secure wireless network, data for a mobile object comprising at least one operator event, one data event, or one sensor event data. The method also includes informing a set of instructions based on the data and at least one off-board data input and one on-board data input, where the instruction set creates an output, and where the output is sequenced and associated with a unique common timestamp by a session engine. The method further includes initiating a record of one or more outputs in a superset of outputs managed by the session engine to generate an event session, where each output in the superset of outputs is associated with the same event and unique common timestamp.The event session provides a record of the total outputs created from at least one data stream of the moving object comprising data collected within a defined time period. Yet another modality is a method for generating an event session for a mobile object. This method involves accessing, via an 1105 allocation authority engine over a fixed wireless network, data for a mobile object comprising at least one operator event, one data event, or one sensor event data stream. The method also includes informing a set of instructions based on the data and at least one off-board data input and one on-board data input. Furthermore, the method includes initiating a record from one or more outputs in a superset of outputs to generate an event session. Finally, the method includes associating the event session with an individual common event and timestamp. The event session provides a record of a defined dataset derived from at least one data stream of the mobile object. Yet another modality is a method for generating an event session for a mobile object. The method includes accessing, through an assignment authority engine 1105, data for a mobile object comprising a known operator profile and at least one data event or sensor event data. The method also includes informing a set of instructions based on the data and at least one off-board data input and on-board data, where the instruction set creates an output, where the output is sequenced and associated with an individual common timestamp by a session engine. The method also includes initiating a record of one or more outputs in a superset of outputs managed by the session engine to generate an event session, where each output in the superset of outputs is associated with the same individual common events and timestamp.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 time period i ozhnn / cznz / R / viAi. Yet another modality is a method for generating an event session for a mobile object. The method includes accessing, through an 1105 allocation authority engine, data for a mobile object comprising at least one known operator profile, event data, or sensor event data. The method also includes informing a set of instructions based on the data and at least one off-board data input and on-board data comprising components, sensors, or APIs that provide data. The method also includes initiating a logging of one or more outputs into a superset of outputs to generate an event session. The method also includes associating the event session with an individual common event and timestamp. The event session provides a log of a defined dataset from at least one data stream of the mobile object. Yet another modality is a system for generating an event session for a mobile object. The system comprises an allocation authority engine 1105 located on a remote server 1135, a mobile device 110 for a mobile object, a connected vehicle device 135 comprising onboard 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 allocation authority engine 1105 is configured to access data via a secure wireless network for a mobile object comprising at least one driver event, one data event, or one sensor event data.The 1105 allocation authority engine is configured to report a set of instructions based on data and at least one data input from outside the vehicle and data from inside the vehicle. The 1105 allocation authority engine is configured to initiate a logging process from one or more outputs into a superset of outputs to generate an event session. The 1105 allocation authority engine is configured to associate the event session with an individual common event and timestamp. The event session provides a log of a defined dataset from at least one data stream of the moving object during the specified time period. Yet another modality 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 onboard data for the mobile object, an allocation authority engine 1105, and at least one offboard 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 allocation authority engine 1105 is configured to access data via a fixed wireless network for the mobile object, comprising at least one operator event, one data event (i ozhnn / cznz / R / viAi), or sensor event data. The allocation authority engine 1105 is configured to report a set of instructions based on the data and at least one offboard data input and one onboard data input.The 1105 allocation authority engine is configured to initiate logging of one or more outputs in a superset of outputs to generate an event session. The 1105 allocation authority engine is configured to associate the event session with an individual common event and timestamp. The event session provides a record of a defined dataset from at least one data flow of the moving object. Yet another modality 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 onboard data for the mobile object, an allocation authority engine 1105, and at least one offboard 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 allocation authority 1105 is configured to access data for the mobile object comprising a known operator profile and at least one data event or sensor event data. The allocation authority engine 1105 is configured to report a set of instructions based on the data and at least one off-vehicle data input and one on-vehicle data input.The 1105 allocation authority engine is configured to initiate logging of one or more outputs in a superset of outputs to generate an event session. The 1105 allocation authority engine is configured to associate the event session with an individual common event and timestamp. The event session provides a record of a defined dataset from at least one data stream of the moving object during the specified time period. Yet another modality 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 onboard data for the mobile object, an allocation authority engine 1105, and off-board and onboard data sources comprising components, sensors, or APIs that provide data. The allocation authority engine 1105 is configured to access data for the mobile object comprising at least one operator event, one data event, or one sensor event data. The allocation authority engine 1105 is configured to inform a set of instructions based on the data and at least one off-vehicle data input and one on-vehicle data input. The allocation authority engine 1105 is configured to initiate a recording of one or more outputs in a superset of outputs to generate an event session.The 1105 allocation authority engine is configured to associate the event session with an individual common event and timestamp. The event session provides a record of a defined dataset from at least one data stream of the moving object during the specified time period. The at least one off-board data item 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, a controlled access entry point, a parking structure, a weigh station, a light pole, a toll collection structure, a fuel dispensing equipment, and a vehicle service equipment. Alternatively, the at least one off-board source is 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 a database and a mobile application operating on a mobile device, with the data originating from the mobile application. The on-board source preferably comprises a processor, a Wi-Fi radio, a Bluetooth radio, a data storage memory, and a connector for pairing with a male connector on the mobile object. The recorder is a camera or other component of the mobile object. The data preferably comprises at least one PSI, barometer, altimeter, speedometer, odometer, video, audio, radar, LIDAR, or infrared sensor. An operating system controls the execution of other computer programs, the execution of the PSO platform, and provides scheduling, input / output control, file and data management, memory management, and control of communications and related services. The operating system might be, for example, Windows (available from Microsoft, Corp. of Redmond, Wash.), Linux or other UNIX variants (available from Red Hat of Raleigh, NC, and other vendors), Android and its variants (available from Google, Inc. of Mountain View, Calif.), Apple OS X, macOS, and its variants (available from Apple, Inc. of Cupertino, Calif.), or similar systems. The system and method described in connection with the embodiments disclosed herein are preferably implemented 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, EPROM, EEPROM, RAM, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An example storage medium is preferably coupled to the processor, such that the processor reads information from and writes information to the storage medium. Alternatively, the storage medium is integral with the processor. In further embodiments, the processor and the storage medium reside on an application-specific integrated circuit (ASIC).In additional modes, the processor and storage medium reside as discrete components within a computing device. In additional modes, 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 and / or computer-readable medium, which are incorporated into a computer software program. In additional modalities, the described functions 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 include both computer storage media and communication media, encompassing any means that facilitates the transfer of a computer program from one location to another. A storage medium is any available medium that can be accessed by a computer.By way of example, and not as a limitation, these computer-readable media may include 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. Any connection is also called a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using 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 the medium.“Disc” and “floppy disk,” as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where discs usually reproduce data magnetically, whereas digital discs usually reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media. A computer program code for carrying out operations of the present invention is preferably written in an object-oriented programming language, with or without scripting, such as C++, C#, SQL, Java, Python, JavaScript, Typescript, PHP, Ruby, or similar. Each interface description preferably discloses the use of at least one communication protocol for establishing acknowledgment or bidirectional communication. 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, GPS triangulation, IM, SMS, MMS, GPRS, and Flash. Databases used with the system preferably include, but are not limited to, MSSQL, Access, MySQL, Oracle, DB2, open-source databases, and others. Operating systems used with the system preferably include Microsoft Windows Server 2010, XP, Vista, 2000, 2003, 2008, Windows Mobile, Linux, Android, Unix, i-series, AS / 400, and Apple OS. The underlying protocol on a server is preferably the Internet protocol suite (Transmission Control Protocol / Internet Protocol (“TCP / IP”)), and the transmission protocol for receiving a file is preferably a File Transfer Protocol (“FTP”), Hypertext Transfer Protocol (“HTTP”), Hypertext Transfer Protocol Secure (“HTTPS”), or other similar protocols. The protocol on the server is preferably HTTPS. The components of a server include a CPU component, a graphics component, memory, non-removable storage, removable storage, a network interface (including one or more connections to a wired network), and SQL databases. Memory includes an operating system, an SQL server or other database engine, and computer programs / software.

Claims

1. A method for generating an event session for a mobile object, the method being characterized in that it comprises: having access, through a plurality of permissions granted and managed by an allocation authority engine, to data for a mobile object comprising at least one of an operator event, a data event, or sensor event data; informing, in the allocation authority, a set of instructions based on the data and at least one onboard and off-board data input, wherein the set of instructions creates an output, wherein the output is sequenced and associated with an individual common timestamp by a session engine; initiating a recording of one or more outputs in a superset of outputs managed by the session engine to generate an event session, wherein each output in the superset of outputs is associated with the same event and individual common timestamp;where the event session provides a record of the total outputs created from at least one data stream of the moving object comprising data collected within a defined time period.

2. The method according to claim 1, characterized in that the at least one off-board data is 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.

3. The method according to claim 2, characterized in that the at least one off-board source is at least one physical infrastructure with the selected communication device from the group comprising a building, a gate, a controlled access entry point, a parking structure, a weigh station, a toll collection structure, a fuel supply equipment, and a vehicle service equipment.

4. The method according to claim 2, characterized in that the at least one off-board source is 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.

5. The method according to claim 2, characterized in that the at least one off-board source is at least one database and a mobile application operating on a mobile device, and the data originates from the mobile application.

6. The method according to claim 1, characterized in that an onboard source comprises a processor, a WiFi radio, a BLUETOOTH radio, a data storage memory, and a connector for pairing with a male connector of the mobile object. i Qztrnn / cznz / e / YiAi 7. A system for generating an event session for a mobile object, the system being characterized in that it comprises: at least one mobile device for a vehicle or a connected vehicle device (CVD) comprising in-vehicle data for a vehicle; an allocation authority engine; and at least one out-of-vehicle data input selected from a source comprising at least one database, at least one cloud source, or at least one physical structure capable of collecting and transferring data in a consumable manner accessible to the session with a communication device; wherein the allocation authority engine is configured to have access to data for a mobile object comprising at least one driver event, one data event, or one sensor event data;wherein the allocation authority engine is configured to report a set of instructions based on data and at least one data input from outside the vehicle and data from inside the vehicle; wherein the allocation authority engine is configured to initiate a record of one or more outputs in a superset of outputs to generate an event session; wherein the allocation authority engine is configured to associate the event session with an individual common event and timestamp; wherein the event session provides a record of a defined dataset from at least one data stream of the moving object during the specified time period.

8. The system according to claim 7, characterized in that the allocation authority engine is configured to access data through a fixed wireless network for the mobile object.

9. The system according to claim 7, characterized in that the at least one source outside the vehicle is at least one physical infrastructure with the selected communication device from the group comprising a building, a gate, a controlled access entry point, a parking structure, a weigh station, a toll collection structure, a fuel supply equipment or a vehicle service equipment.

10. The system according to claim 7, characterized in that the at least one source outside the vehicle is 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.

11. The system according to claim 7, characterized in that the at least one source outside the vehicle is at least one database and a mobile application operating on a mobile device, and the data originates from the mobile application.

12. The system according to claim 7, characterized in that a source within the vehicle comprises a processor, a WiFi radio, a BLUETOOTH radio, a memory that stores vehicle data, and a connector for pairing with a male connector of the vehicle.

13. The system according to claim 7, characterized in that the recording is from a camera or other component of the moving object.

14. A system for generating an event session for a mobile object, the system being characterized in that it comprises: a mobile device for a mobile object; a connected vehicle comprising on-board data for the mobile object; an allocation 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; wherein the allocation authority engine is configured to access data for the mobile object comprising at least one operator event, one data event, or one sensor event data; wherein the allocation authority engine is configured to report a set of instructions based on the data and at least one off-board data input and on-board data;wherein the allocation authority engine is configured to initiate a record of one or more outputs in a superset of outputs to generate an event session; wherein the allocation authority engine is configured to associate the event session with an individual common event and timestamp; wherein the event session provides a record of a defined dataset from at least one data stream of the moving object.

15. The system according to claim 14, characterized in that the allocation authority engine is configured to access data through a secure wireless network for the mobile object.

16. The system according to claim 14, characterized in that the allocation authority engine is configured to access data through a fixed wireless network for the mobile object.

17. A system for generating an event session for a mobile object, the system being characterized in that it comprises: a mobile device for a mobile object; a connected vehicle comprising on-board data for the mobile object; an allocation 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; wherein the allocation authority is configured to have access to data for the mobile object comprising a known operator profile and at least one event data or sensor event data; wherein the allocation authority engine is configured to inform a set of instructions based on the data and at least one off-vehicle data input and on-vehicle data;wherein the allocation authority engine is configured to initiate a logging of one or more outputs in a superset of outputs to generate an event session; wherein the allocation authority engine is configured to associate the event session with an individual common event and timestamp; wherein the event session provides a logging of a defined dataset from at least one data stream of the moving object during the specified time period.

18. The system according to claim 17, characterized in that the data comprises at least one of PSI, barometer, altimeter, speedometer, odometer, video, audio, radar, LIDAR or infrared.

Images