# US 12,225,131 B2 · Data offload and time synchronization for ubiquitous visual computing witness > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,225,131 B2 - Document ID: US12225131B2 - Status: Granted - Kind: B2 - Application number: 18/313,953 - Filed: 2023-05-08 - Published: 2023-09-07 - Granted: 2025-02-11 - Earliest claimed: 2019-06-28 - Assignees: Intel Corporation - Applicants: Intel Corporation - Inventors: Eve M. Schooler; Hassnaa Moustafa; Maruti Gupta Hyde; Ned M. Smith - Web page: https://patentgrep.com/patent/US12225131B2 ## CPC - H04L 9/32: including means for verifying the identity or authority of a user of the system {or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials} - H04L 9/3228: {One-time or temporary data, i.e. information which is sent for every authentication or authorization, e.g. one-time-password, one-time-token or one-time-key} - H04L 9/3268: {using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]} - H04L 9/3297: {involving time stamps, e.g. generation of time stamps} - H04L 63/0838: {using one-time-passwords} - H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] - H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks - H04L 67/14: Session management (for real-time applications in data packet communications networks H04L65/1066) - H04L 67/141: Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70) - H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services - H04W 4/38: for collecting sensor information - H04W 4/44: for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H] - H04W 8/005: {Discovery of network devices, e.g. terminals} - H04W 12/06: Authentication - H04W 56/001: {Synchronization between nodes} - H04L 2209/805: Lightweight hardware, e.g. radio-frequency identification [RFID] or sensor - H04L 2209/84: Vehicles - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract In one embodiment, a road side unit (RSU) establishes a data offload session with a vehicle in the vicinity of the RSU based on a session establishment request sent by the vehicle, and stores data received from the vehicle during the data offload session in its memory. The RSU generates storage record information (including identifying information for the RSU) for the stored data, and transmits the storage record information to the vehicle. ## Claims ### Claim 1 A vehicle comprising: a plurality of sensors; memory to store data from the plurality of sensors; wireless communication circuitry to communicate with road side units (RSUs) in the vicinity of the vehicle; and processing circuitry to: cause a data offload session establishment request to be transmitted to a RSU; cause sensor data to be transmitted to the RSU after establishing a data offload session with the RSU; and store storage record information received from the RSU corresponding to the sensor data transmitted to the RSU. ### Claim 2 (depends on 1) The vehicle of claim 1, wherein the processing circuitry is to generate the data offload session establishment request based on at least one of a determination that a remaining capacity of the memory is below a threshold, a determination or notification that a particular event has occurred in the vicinity of the vehicle, and a request to offload sensor data for a particular time, location, or event occurrence. ### Claim 3 (depends on 1) The vehicle of claim 1, wherein the processing circuitry is to determine to establish a data offload session with the RSU based on a received availability advertisement indicating an amount of storage available at the RSU. ### Claim 4 (depends on 3) The vehicle of claim 3, wherein the RSU is a first RSU and the availability advertisement is received from a second RSU. ### Claim 5 (depends on 1) The vehicle of claim 1, wherein the storage record information comprises one or more of an identification of the RSU, location information for the RSU, information identifying an event witnessed by the vehicle or RSU, and a time associated with the event witnessed by the vehicle. ### Claim 6 (depends on 1) The vehicle of claim 1, wherein the processing circuitry is further to cause authentication credentials to be transmitted to the RSU before transmitting the sensor data to the RSU. ### Claim 7 (depends on 1) The vehicle of claim 1, wherein the processing circuitry is further to process storage service information from the RSU; and determine sensor data to offload to the RSU based on the storage service information. ### Claim 8 (depends on 7) The vehicle of claim 7, wherein the storage service information indicates one or more of a maximum amount of storage available for the sensor data, a maximum duration of storage for the sensor data, a type of sensor data accepted by the RSU for storage, a service charge for storage of the sensor data, and privacy information related to storage of the sensor data. ### Claim 9 (depends on 1) The vehicle of claim 1, wherein the processing circuitry is further to at least partially encrypt the sensor data using on a bulk encryption key (BEK), and cause a wrapped BEK to be transmitted to the RSU during the data offload session. ### Claim 10 (depends on 9) The vehicle of claim 9, wherein the sensor data comprises unencrypted metadata indicating a location associated with the encrypted data, a time associated with the encrypted data, or an event associated with the encrypted data. ### Claim 11 (depends on 1) The vehicle of claim 1, wherein the RSU is one of a traffic light, light post, road or traffic sign, or building adjacent a road. ### Claim 12 At least one non-transitory machine accessible storage medium having instructions stored thereon, wherein the instructions, when executed on a machine, cause the machine to: generate a request to establish a data offload session between a vehicle and a road side unit (RSU); cause the request to be transmitted from the vehicle to the RSU; cause sensor data stored at the vehicle to be transmitted to the RSU after establishing a data offload session with the RSU; and store storage record information received from the RSU corresponding to the sensor data transmitted to the RSU. ### Claim 13 (depends on 12) The storage medium of claim 12, wherein the instructions are to generate the request to establish a data offload session based on at least one of a determination that a remaining capacity of the memory is below a threshold, a determination or notification that a particular event has occurred in the vicinity of the vehicle, and a request to offload sensor data for a particular time, location, or event occurrence. ### Claim 14 (depends on 12) The storage medium of claim 12, wherein the instructions are to determine to establish a data offload session with the RSU based on a received availability advertisement indicating an amount of storage available at the RSU. ### Claim 15 (depends on 12) The storage medium of claim 12, wherein the instructions are to cause the machine to: process storage service information from the RSU; and determine sensor data to offload to the RSU based on the storage service information. ### Claim 16 (depends on 15) The storage medium of claim 15, wherein the storage service information indicates one or more of a maximum amount of storage available for the sensor data, a maximum duration of storage for the sensor data, a type of sensor data accepted by the RSU for storage, a service charge for storage of the sensor data, and privacy information related to storage of the sensor data. ### Claim 17 (depends on 12) The storage medium of claim 12, wherein the instructions are further to cause the machine to at least partially encrypt the sensor data using on a bulk encryption key (BEK), and cause a wrapped BEK to be transmitted to the RSU during the data offload session. ### Claim 18 A method comprising: generating, at a vehicle, a request to establish a data offload session with a road side unit (RSU); transmitting the request to the RSU; transmitting sensor data stored at the vehicle to the RSU after establishing a data offload session with the RSU; and receiving, at the vehicle, storage record information from the RSU corresponding to the sensor data transmitted to the RSU. ### Claim 19 (depends on 18) The method of claim 18, wherein the data offload session establishment request is generated based on at least one of a determination that a remaining capacity of the memory is below a threshold, a determination or notification that a particular event has occurred in the vicinity of the vehicle, and a request to offload sensor data for a particular time, location, or event occurrence. ### Claim 20 (depends on 18) The method of claim 18, wherein the storage record information comprises one or more of an identification of the RSU, location information for the RSU, information identifying an event witnessed by the vehicle or RSU, and a time associated with the event witnessed by the vehicle.