Requirements for defining a balanced relationship between State and Local governments when regulating Connected Autonomous Vehicles.

1. Requirements for a Balanced
Connected Autonomous Vehicle
Regulatory Model
© 2023, Corverity Corporation
Author: Joseph Urban
info@corverity.com

2. Classification
A. Road Classification:
• Interstate Highway
• US Highway
• State Highway
• County Road
• City or Municipal street
• Rural Road
• Parkways and Boulevards
• Limited Access Road
• Frontage Road
B. Traversing mode:
• Intersection (potential turns)
• Proceeding (mostly straight street)
• Unstructured (parking lot)
• Sidewalk (only where the vehicle crosses)
• Terminus (i.e. parking spot)
C. Range class of
• Length
• Width
• Grade (incline)
• Speed
• Weight capacity
D. Surface type
E. Range of population concentration
F. Adjacent attributes
(i.e. parallel lane: same direction or opposite, parking, curb, shoulder, etc.)
G. Adjacent buildings (for assessing quality of GPS signal):
• Setback
• Height
H. Jurisdiction (i.e. public or private)
1) Define all known classes of road types, intersections, and traversing segments (i.e. sidewalks)
providing variations, at a minimum, based on:

3. Best Practices, Scenarios
2) Define the best-practice guidance for traversing each class of road types
3) Define all known classes of scenarios including but not limited to:
a. Emergency incidents
b. Emergency vehicle transit
c. Blocked passage (object in road)
d. Work zones
e. School in-session
f. Rush hour
g. Scheduled event (parade)
h. Exceeding safe CAV capacity

4. Assignment
4) Require that local transit authorities assign each class of road type to each segment of
road (aka: road segment) where CAVs will be expected to transit:
• Streets
• Sidewalk crossings
• Parking lots
• Parking garages
• Any other legally accessible areas for vehicles
5) Define the best-practices for defining and identifying each class of road type and collect
the relevant data when assigning the road type to each segment of road

5. CAV & Operator Responsibility
6) Require that every CAV and CAV operator be able to precisely determine when the
vehicle has entered a specific road segment

6. Risk Mitigation & Road Assignment
7) Define the acceptable range of procedures for mitigating risks (aka “Mitigating Procedures”) within each
class of scenario
8) Assign best-practices and scenarios to specific road segment providing variations, at a minimum, based on:
a) Time of day
b) Season
c) Weather
d) Type & model of CAV
e) CAV fleet operator or private class (i.e. Tesla owner)
f) Type of payload (i.e. DOT class, Alcohol, etc.)

7. State & Local Authorities
9) Enable authorization and administrative capability for state and federal
authorities to assign and reassign best practices and mitigating procedures to
classes of road segments and to specific road segments
10) Allow local authorities to:
1) Petition to change a road type assignment to a road segment
2) Propose improvements to best-practices for certain classes of road type
3) Directly adjust the range of mitigating procedures for road segments within their jurisdiction
4) Assign road types to custom groups to facilitate administration
5) Propose improvements to mitigating procedures and the range of procedures assigned to classes of
road types
6) Update a clearinghouse, in a timely manner, with incident details that are necessary to adjust traffic
flow or reduce risk to first responders or passengers

8. CAV Responsibility & Standards
11) Require that all CAV operators to:
a) Demonstrate awareness of the most current guidance for procedures for each segment a vehicle will traverse
b) Subscribe to the same clearinghouse such that immediate actions can be triggered in their CAVs to execute the prescribed
actions in reaction to incident details or other changes to conditions along their planned route
c) Demonstrate that their CAVs can execute the Mitigating Procedures using data stored in the CAV before the triggering event is
received (less reliance on wireless communication)
d) Demonstrate that their CAVs can receive messages from local sources, such as near an emergency incident, that will trigger the
Mitigating Procedures without communicating with their centralized administration system
e) Report metrics on incidents received and the time to react by the impacted CAVs in their fleet
f) Message, to a clearinghouse, that a prescribed procedure was triggered during transit of a specific road segment
g) Reroute their CAVs to avoid upstream road segments that have been closed since the journey was initiated
12) Establish a minimum reaction time for CAV operators to trigger adjustments to CAV operations in reaction
to relevant clearinghouse events (i.e. emergency incidents)

9. Data: Capture & External Sources
13) Organize all incident data by road segment such that optimal solutions can be matched against evidence
14) Allow linking/subscribing of road segments to third-party systems to receive operational data (i.e. weather,
open drawbridge, security protocol for opening a garage door, etc.)