Systems and methods for implementing autonomous vehicle collaboration via a hybrid distributed connected network

1. A vehicle collaboration system of an autonomous vehicle, comprising:

a transceiver at a first autonomous vehicle configured to:

broadcast a first collaboration message comprising first vehicle data associated with the first autonomous vehicle in connection with a collaboration application to a collaboration domain group via a hybrid distributed-connected network (HYDIN), the collaboration domain group including at least the first autonomous vehicle and a second autonomous vehicle; and

receive a second collaboration message comprising second vehicle data associated with the second autonomous vehicle in connection with the collaboration application via the HYDIN, the second collaboration message being broadcast from the second autonomous vehicle to the collaboration domain group via the HYDIN;

a collaboration controller at the first autonomous vehicle configured to implement a collaboration action associated with the collaboration application based at least in part on the first and second vehicle data;

a local data buffer at the first autonomous vehicle; and

a resource allocation module at the first autonomous vehicle, the resource allocation module configured to:

determine whether buffer space is available at the local data buffer; and

allocate a first application buffer space in the local data buffer for the collaboration domain group in connection with the collaboration application based on the determination,

wherein upon a determination that buffer space is available at the local data buffer, the collaboration controller is configured to:

receive the first vehicle data from a vehicle electronic control unit (ECU) via an in-vehicle bus at a first time and store the first vehicle data at the first application buffer space;

broadcast the first collaboration message including the first vehicle data to the HYDIN as real time vehicle data;

receive a third vehicle data in connection with the collaboration application from the vehicle ECU via the in-vehicle bus at a second time and store the third vehicle data at the first application buffer space;

broadcast a third collaboration message comprising the third vehicle data to the collaboration domain group via the HYDIN as real time vehicle data;

retrieve the first and third vehicle data from the first application buffer space; and

broadcast a fourth collaboration message comprising the first vehicle data and the third vehicle data at a third time as historical vehicle data.

2. The system of claim 1 , wherein the first and second collaboration messages consist of a data link layer and a physical layer.

3. The system of claim 1 , wherein each of the first and second collaboration messages further comprise a collaboration application identifier associated with the collaboration application and a domain group identifier associated with the collaboration domain group.

4. The system of claim 1 , wherein the collaboration application comprises one of a platooning application and a lane changing application.

5. The system of claim 1 , wherein the first vehicle data comprises real time vehicle data.

6. The system of claim 1 , wherein upon a determination that buffer space is unavailable at the local data buffer the collaboration controller is configured to:

receive the first vehicle data from a vehicle ECU via an in-vehicle bus at a first time;

broadcast the first collaboration message including the first vehicle data to the collaboration domain group via the HYDIN as real time vehicle data, the second autonomous vehicle being configured to store the first vehicle data at a second application buffer space at the second autonomous vehicle;

receive a third vehicle data in connection with the collaboration application from the vehicle ECU via the in-vehicle bus at a second time;

broadcast a third collaboration message including the third vehicle data to the collaboration domain group via the HYDIN as real time vehicle data, the second autonomous vehicle being configured to store the third vehicle data at the second application buffer space at the second autonomous vehicle; and

receive a fourth collaboration message comprising the first and third vehicle data at a third time, the fourth collaboration message being broadcast by the second autonomous vehicle to the collaboration domain group via the HYDIN at a third time as historical vehicle data associated with the first autonomous vehicle.

7. The system of claim 1 , further comprising a resource identification module at the first autonomous vehicle, the resource identification module configured to:

determine whether at least one collaboration message has been received from each of the autonomous vehicles in the collaboration domain group via the HYDIN during a pre-defined period of time;

generate a collaboration domain group list associated with the collaboration domain group based at least in part on the determination; and

broadcast a fifth collaboration message comprising the collaboration domain group list to the collaboration domain group via the HYDIN.

8. A non-transitory computer readable medium comprising instructions stored thereon for implementing autonomous vehicle collaboration that upon execution by a processor, cause the processor to:

broadcast a first collaboration message comprising first vehicle data associated with a first autonomous vehicle in connection with a collaboration application from the first autonomous vehicle to a collaboration domain group via a hybrid distributed-connected network (HYDIN), the collaboration domain group including at least the first autonomous vehicle and a second autonomous vehicle;

receive a second collaboration message comprising second vehicle data associated with the second autonomous vehicle in connection with the collaboration application via the HYDIN at the first autonomous vehicle, the second collaboration message being broadcast from the second autonomous vehicle to the collaboration domain group via the HYDIN; and

implement a collaboration action associated with the collaboration application at the first autonomous vehicle based at least in part on the first and second vehicle data;

determine whether buffer space is available at a local data buffer of the first autonomous vehicle;

allocate a first application buffer space in the local data buffer for the collaboration domain group in connection with the collaboration application based on the determination, wherein when it is determined that buffer space is unavailable at the local data buffer, cause the processor to:

receive the first vehicle data from a vehicle ECU via an in-vehicle bus at a first time;

broadcast the first collaboration message including the first vehicle data to the collaboration domain group via the HYDIN as real time vehicle data, the second autonomous vehicle being configured to store the first vehicle data at a second application buffer space at the second autonomous vehicle;

receive a third vehicle data in connection with from the vehicle ECU via the in-vehicle bus at a second time;

broadcast a third collaboration message including the third vehicle data to the collaboration domain group via the HYDIN as real time vehicle data, the second autonomous vehicle being configured to store the third vehicle data at the second application buffer space at the second autonomous vehicle; and

receive a fourth collaboration message comprising the first and third vehicle data at a third time, the fourth collaboration message being broadcast by the second autonomous vehicle to the collaboration domain group via the HYDIN at a third time as historical vehicle data associated with the first autonomous vehicle.

9. The non-transitory computer readable medium of claim 8 , further comprising instructions that upon execution by the processor cause the processor to broadcast the first collaboration message from the first autonomous vehicle to the collaboration domain group via the HYDIN, the first collaboration message comprising, the first vehicle data, a collaboration application identifier associated with the collaboration application, and a domain group identifier associated with the collaboration domain group.

10. The non-transitory computer readable medium of claim 8 , further comprising instructions that upon a determination that buffer space is available at the local data buffer and upon execution by the processor cause the processor to:

receive the first vehicle data from a vehicle electronic control unit (ECU) via an in-vehicle bus at a first time and store the first vehicle data at the first application buffer space;

broadcast the first collaboration message including the first vehicle data to the HYDIN as real time vehicle data;

receive a third vehicle data in connection with the collaboration application from the vehicle ECU via the in-vehicle bus at a second time and store the third vehicle data at the first application buffer space;

broadcast a third collaboration message comprising the third vehicle data to the collaboration domain group via the HYDIN as real time vehicle data;

retrieve the first and third vehicle data from the first application buffer space; and

broadcast a fourth collaboration message comprising the first vehicle data and the third vehicle data at a third time as historical vehicle data.

11. The non-transitory computer readable medium of claim 8 , further comprising instructions that upon execution by the processor cause the processor to:

determine whether at least one collaboration message has been received from each of the autonomous vehicles in the collaboration domain group at the first autonomous vehicle via the HYDIN during a pre-defined period of time;

generate a collaboration domain group list associated with the collaboration domain group based at least in part on the determination; and

broadcast a fifth collaboration message comprising the collaboration domain group list to the collaboration domain group via the HYDIN.

12. A method of implementing an autonomous vehicle collaboration comprising:

broadcasting a first collaboration message comprising first vehicle data associated with a first autonomous vehicle in connection with a collaboration application from the first autonomous vehicle to a collaboration domain group via a hybrid distributed-connected network (HYDIN), the collaboration domain group including at least the first autonomous vehicle and a second autonomous vehicle;

receiving a second collaboration message comprising second vehicle data associated with the second autonomous vehicle in connection with the collaboration application via the HYDIN at the first autonomous vehicle, the second collaboration message being broadcast from the second autonomous vehicle to the collaboration domain group via the HYDIN; and

implementing a collaboration action associated with the collaboration application at the first autonomous vehicle based at least in part on the first and second vehicle data determining whether buffer space is available at a local data buffer of the first autonomous vehicle;

allocating a first application buffer space in the local data buffer for the collaboration domain group in connection with the collaboration application based on the determination

upon a determination that buffer space is available at the local data buffer, the method further comprises:

receiving the first vehicle data from a vehicle electronic control unit (ECU) via an in-vehicle bus at a first time and storing the first vehicle data at the first application buffer space;

broadcasting the first collaboration message including the first vehicle data to the HYDIN as real time vehicle data;

receiving a third vehicle data in connection with the collaboration application from the vehicle ECU via the in-vehicle bus at a second time and storing the third vehicle data at the first application buffer space;

broadcasting a third collaboration message comprising the third vehicle data to the collaboration domain group via the HYDIN as real time vehicle data;

retrieving the first and third vehicle data from the first application buffer space; and

broadcasting a fourth collaboration message comprising the first vehicle data and the third vehicle data at a third time as historical vehicle data.

13. The method of claim 12 , wherein broadcasting the first collaboration message comprising the first vehicle data, comprises broadcasting the first collaboration message comprising the first vehicle data, a collaboration application identifier associated with the collaboration application, and a domain group identifier associated with the collaboration domain group.

14. The method of claim 12 , that upon a determination that buffer space is unavailable at the local data buffer further comprises:

receiving the first vehicle data from a vehicle ECU via an in-vehicle bus at a first time;

broadcasting the first collaboration message including the first vehicle data to the collaboration domain group via the HYDIN as real time vehicle data, the second autonomous vehicle being configured to store the first vehicle data at a second application buffer space at the second autonomous vehicle;

receiving a third vehicle data in connection with the collaboration application from the vehicle ECU via the in-vehicle bus at a second time;

broadcasting a third collaboration message including the third vehicle data to the collaboration domain group via the HYDIN as real time vehicle data, the second autonomous vehicle being configured to store the third vehicle data at the second application buffer space at the second autonomous vehicle; and

receiving a fourth collaboration message comprising the first and third vehicle data at a third time, the fourth collaboration message being broadcast by the second autonomous vehicle to the collaboration domain group via the HYDIN at the third time as historical vehicle data associated with the first autonomous vehicle.