# US 12,003,367 B2 · Systems and methods for fast vehicular micro cloud formation > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,003,367 B2 - Document ID: US12003367B2 - Status: Granted - Kind: B2 - Application number: 17/877,328 - Filed: 2022-07-29 - Published: 2024-02-01 - Granted: 2024-06-04 - Earliest claimed: 2022-07-29 - Assignees: Toyota Motor Engineering & Manufacturing North America, Inc.; Toyota Jidosha Kabushiki Kaisha - Applicants: Toyota Motor Engineering & Manufacturing North America, Inc. - Inventors: Seyhan Ucar; Takamasa Higuchi; Onur Altintas - Web page: https://patentgrep.com/patent/US12003367B2 ## CPC - H04L 41/0816: the condition being an adaptation, e.g. in response to network events - G08G 1/012: {from other sources than vehicle or roadside beacons, e.g. mobile networks} - H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) - 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: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G08G: TRAFFIC CONTROL SYSTEMS (guiding railway traffic, ensuring the safety of railway traffic B61L; arrangement of road signs or traffic signals E01F9/00; radar or analogous systems, sonar systems, lidar systems specially adapted for traffic control G01S13/91, G01S15/88, G01S17/88; {radar or analogous systems, sonar systems, lidar systems specially adapted for anti-collision purposes G01S13/93, G01S15/93, G01S17/93}) ## Abstract Systems and methods for fast vehicular micro cloud formation are disclosed herein. In one example, a system includes a processor and a memory in communication with the processor and having instructions. When executed by the processor, the instructions cause the processor to receive an identifier of the vehicle and determine if the identifier matches the information in stored metadata. If the identifier matches the information in the stored metadata, the vehicle is allowed to join the vehicular micro cloud without performing a standard onboarding procedure. Otherwise, a standard onboarding procedure is performed to allow the vehicle to join the vehicular micro cloud. ## Claims ### Claim 1 A method for onboarding a vehicle to a vehicular micro cloud entering a vehicular micro cloud region, the vehicular micro cloud having a micro cloud leader, the method comprising steps of: receiving an identifier of the vehicle by the micro cloud leader, the micro cloud leader being another vehicle that is part of the vehicular micro cloud; in response to a determination by the micro cloud leader that the identifier of the vehicle matches information in metadata and a time to live has not expired, allowing, by the micro cloud leader, the vehicle to join the vehicular micro cloud without performing a standard onboarding procedure, the time to live having a duration based on a frequency in which the vehicle has previously accessed the vehicular micro cloud; and in response to a determination by the micro cloud leader that the identifier of the vehicle does not match information in the metadata, performing by the micro cloud leader the standard onboarding procedure for allowing the vehicle to join the vehicular micro cloud. ### Claim 2 (depends on 1) The method of claim 1, wherein the time to live is further based on a historical location of the vehicle with respect to a location of the vehicular micro cloud region. ### Claim 3 (depends on 2) The method of claim 2, wherein the historical location of the vehicle includes at least one of previous trajectories, parked locations, and time spent at particular locations. ### Claim 4 (depends on 1) The method of claim 1, wherein the standard onboarding procedure includes the steps of: performing an initial security check of the vehicle; verifying an identity of the vehicle; determining resource availability of the vehicle; and generating the metadata for the vehicle. ### Claim 5 (depends on 4) The method of claim 4, wherein the metadata further includes at least one of: time and date of creation of the metadata; location of the vehicle on the vehicular micro cloud; location of the vehicle when the metadata was created; standards and process used to create the metadata; and a pseudo-ID of the vehicle. ### Claim 6 (depends on 5) The method of claim 5, further comprising the step of updating the pseudo-ID of the vehicle with a new pseudo-ID of the vehicle. ### Claim 7 (depends on 1) The method of claim 1, further comprising the step of distributing the metadata to a different micro cloud leader, the different micro cloud leader being a second vehicle that is part of the vehicular micro cloud. ### Claim 8 A system for onboarding a vehicle to a vehicular micro cloud entering a vehicular micro cloud region, the vehicular micro cloud having a micro cloud leader, the system comprising: a processor; and a memory in communication with the processor, the memory having instructions that; when executed by the processor, cause the processor to: receive an identifier of the vehicle by the micro cloud leader, the micro cloud leader being another vehicle that is part of the vehicular micro cloud, in response to a determination by the micro cloud leader that the identifier of the vehicle matches information in metadata and a time to live has not expired, allow, by the micro cloud leader, the vehicle to join the vehicular micro cloud without performing a standard onboarding procedure, the time to live having a duration based on a frequency in which the vehicle has previously accessed the vehicular micro cloud, and in response to a determination by the micro cloud leader that the identifier of the vehicle does not match information in the metadata, perform by the micro cloud leader the standard onboarding procedure for allowing the vehicle to join the vehicular micro cloud. ### Claim 9 (depends on 8) The system of claim 8, wherein the time to live is based further on a historical location of the vehicle with respect to a location of the vehicular micro cloud region. ### Claim 10 (depends on 9) The system of claim 9, wherein the historical location of the vehicle includes at least one of previous trajectories, parked locations, and time spent at particular locations. ### Claim 11 (depends on 8) The system of claim 8, wherein the standard onboarding procedure includes causing the processor to: perform an initial security check of the vehicle, verify an identity of the vehicle, determine resource availability of the vehicle, and generate the metadata for the vehicle. ### Claim 12 (depends on 11) The system of claim 11, wherein the metadata further includes at least one of: time and date of creation of the metadata; location of the vehicle on the vehicular micro cloud; location of the vehicle when the metadata was created; standards and process used to create the metadata; and a pseudo-ID of the vehicle. ### Claim 13 (depends on 12) The system of claim 12, wherein the memory further comprises instructions that, when executed by the processor, cause the processor to update the pseudo-ID of the vehicle with a new pseudo-ID of the vehicle utilizes the new pseudo-ID. ### Claim 14 (depends on 1) The system of claim 1, wherein the memory further comprises instructions that, when executed by the processor, cause the processor to distribute the metadata to a different micro cloud leader, the different micro cloud leader being a second vehicle that is part of the vehicular micro cloud. ### Claim 15 A non-transitory computer readable medium including instructions that, when executed by a processor of a micro cloud leader, the micro cloud leader being another vehicle that is part of a vehicular micro cloud, cause the processor to: receive an identifier of a vehicle by the micro cloud leader; in response to a determination by the processor of the micro cloud leader that the identifier of the vehicle matches information in metadata and a time to live has not expired, allow, by the micro cloud leader, the vehicle to join the vehicular micro cloud without performing a standard onboarding procedure, the time to live having a duration based on a frequency in which the vehicle has previously accessed the vehicular micro cloud; and in response to a determination by the processor of the micro cloud leader that the identifier of the vehicle does not match information in the metadata, perform by the micro cloud leader the standard onboarding procedure for allowing the vehicle to join the vehicular micro cloud. ### Claim 16 (depends on 15) The non-transitory computer readable medium of claim 15, wherein the time to live is further based on a historical location of the vehicle with respect to a location of a vehicular micro cloud region.