Lets talk protocols and communications

I have been reviewing the literature about Dedicated Short Range Communications for peer to peer auto communications. I presumed one big issue was security of the unique identity of the auto, and it is.

Anonymous Link Layer Packet Protocol:

I still aim for autonomous tracking link layer. The link layer packet ID contains device class, motion path, and error band. I added error band from my last thoughts. Nothing in this link ID informs about the unique id of the auto. Autos accept these link layer addresses, and manage a a real time Kalman filter multi target map, a map of the local world it monitors.

Any auto sensor, say a vision based object tracker, can create link layer addresses of object found and enter them into the tracking map. And autos talk to each other and to roadside devices, sending link layer packet IDs.

Immediately we have covered 80% of the most important coordination applications, namely where and what things are on the road. For the purpose of congestion control, system devices can forward link layer addresses and issue these PIDs as commands, to create convoys. Still retaining anonymous auto identity.

But, somewhere a unique ID must be passed from system to auto, to pass personal and payment info later. The easiest way to pass these from system to auto is at the toll booth, with close proximity and low power to resist leakage. Or perhaps the car drives by a special encrypted link device. However, once randomly chosen IDs are passed in secret, they are good for the day, seek, month. They remain in the auto, under driver control. The unique, and secret IDs, are used in the application layer for payments and other secret messages. The person or auto can rotate through a set of random numbers, pre-assigned in secret. This simple security device is probably good enough and drivers control the deceptive switching of IDs.