Managing roadway intersections for vehicles

1. A computer-implemented method comprising:

receiving, at a connected roadway device, request messages from a first vehicle and an other vehicle to reserve an intersection;

checking time-token balances associated with the first vehicle and the other vehicle;

responsive to a time-token balance associated with the other vehicle being negative, updating the other vehicle to be associated with a low urgency level and reserving the intersection for the first vehicle;

adding to a corresponding time-token balance associated with the other vehicle based on the other vehicle being associated with the low urgency level and the other vehicle not receiving priority for the intersection; and

generating graphical data for displaying a user interface that includes an option for specifying a level of urgency for the intersection, a transaction with an amount, a resulting time-token balance, and an explanation for why a time token was credited or debited to an account associated with a user of the first vehicle.

2. The method of claim 1 , wherein the user interface further includes an option to specify a destination that the first vehicle is travelling towards and a high urgency level associated with the first vehicle.

3. The method of claim 1 , further comprising:

conducting time-token transactions based on how reserving the intersection for the first vehicle affects the other vehicle, wherein the time-token transactions are based on a high urgency level associated with the first vehicle, the low urgency level associated with the other vehicle, a number of travelers in the first vehicle and the other vehicle, and the time-token balances corresponding to the first vehicle and the other vehicle.

4. The method of claim 3 , wherein an amount of conducted time-token transactions on each time-token account is computed using a Vickrey-Clarke-Groves (VCG) mechanism.

5. The method of claim 1 , wherein the request messages each include a basic safety message that describes a heading and a path history of a corresponding vehicle and further comprising:

determining whether the first vehicle and the other vehicle will be at the intersection at substantially a same time based on the request messages; and

conducting time-token transactions based on how reserving the intersection for the first vehicle affects the other vehicle.

6. The method of claim 1 , wherein the connected roadway device is a roadside unit (RSU).

7. The method of claim 1 , further comprising:

transmitting reservation data to the first vehicle and the other vehicle; and

transmitting a traffic light control message to a traffic light, wherein the traffic light control message instructs the traffic light to display a green light while the first vehicle moves through the intersection.

8. A system comprising:

one or more processors of a connected roadway device that includes a non-transitory memory storing computer code which, when executed by the one or more processors causes the one or more processors to:

receive request messages from a first vehicle and an other vehicle to reserve an intersection;

check time-token balances associated with the first vehicle and the other vehicle;

responsive to a time-token balance associated with the other vehicle being negative, update the other vehicle to be associated with a low urgency level and reserve the intersection for the first vehicle;

add to a corresponding time-token balance associated with the other vehicle based on the other vehicle being associated with the low urgency level and the other vehicle not receiving priority for the intersection; and

generate graphical data for displaying a user interface that includes an option for specifying a level of urgency for the intersection, a transaction with an amount, a resulting time-token balance, and an explanation for why a time token was credited or debited to an account associated with a user of the first vehicle.

9. The system of claim 8 , wherein the user interface further includes an option to specify a destination that the first vehicle is travelling towards and a high urgency level associated with the first vehicle.

10. The system of claim 8 , wherein the computer code is further operable to cause the one or more processors to:

conduct time-token transactions based on how reserving the intersection for the first vehicle affects the other vehicle, wherein the time-token transactions are based on a high urgency level associated with the first vehicle, the low urgency level associated with the other vehicle, a number of travelers in the first vehicle and the other vehicle, and the time-token balances corresponding to the first vehicle and the other vehicle.

11. The system of claim 10 , wherein an amount of conducted time-token transactions on each time-token account is computed using a Vickrey-Clarke-Groves (VCG) mechanism.

12. The system of claim 8 , wherein the request messages each include a basic safety message and the computer code is further operable to cause the one or more processors to:

determine whether the first vehicle and the other vehicle will be at the intersection at substantially a same time based on the request messages; and

conduct time-token transactions based on how reserving the intersection for the first vehicle affects the other vehicle.

13. The system of claim 8 , wherein the connected roadway device is a roadside unit (RSU).

14. The system of claim 8 , wherein the computer code is further operable to cause the one or more processors to:

transmit reservation data to the first vehicle and the other vehicle; and

transmit a traffic light control message to a traffic light, wherein the traffic light control message instructs the traffic light to display a green light while the first vehicle moves through the intersection.

15. A non-transitory memory encoded with a computer program, the computer program comprising instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising:

receiving, at a connected roadway device, request messages from a first vehicle and an other vehicle to reserve an intersection;

checking time-token balances associated with the first vehicle and the other vehicle;

responsive to a time-token balance associated with the other vehicle being negative, updating the other vehicle to be associated with a low urgency level and reserving the intersection for the first vehicle;

adding to a corresponding time-token balance associated with the other vehicle based on the other vehicle being associated with the low urgency level and the other vehicle not receiving priority for the intersection; and

generating graphical data for displaying a user interface that includes an option for specifying a level of urgency for the intersection, a transaction with an amount, a resulting time-token balance, and an explanation for why a time token was credited or debited to an account associated with a user of the first vehicle.

16. The non-transitory memory of claim 15 , wherein the user interface further includes an option to specify a destination that the first vehicle is travelling towards and a high urgency level associated with the first vehicle.

17. The non-transitory memory of claim 15 , wherein the instructions are further operable to perform operations comprising:

conducting time-token transactions based on how reserving the intersection for the first vehicle affects the other vehicle, wherein the time-token transactions are based on a high urgency level associated with the first vehicle, the low urgency level associated with the other vehicle, a number of travelers in the first vehicle and the other vehicle, and the time-token balances corresponding to the first vehicle and the other vehicle.

18. The non-transitory memory of claim 17 , wherein an amount of conducted time-token transactions on each time-token account is computed using a Vickrey-Clarke-Groves (VCG) mechanism.

19. The non-transitory memory of claim 15 , wherein the request messages each include a basic safety message and the instructions are further operable to perform operations comprising:

determining whether the first vehicle and the other vehicle will be at the intersection at substantially a same time based on the request messages; and

conducting time-token transactions based on how reserving the intersection for the first vehicle affects the other vehicle.

20. The non-transitory memory of claim 15 , wherein the connected roadway device is a roadside unit (RSU).