1 Definition
A Description of the state of the road the CAV is traversing inferred by the AMS from information that is internally available and/or received from an external source via a communication channel.
A Description of the responsiveness of the CAV.
2 Functional Requirements
Road State includes the following information:
- Time
- The SA reached at Time.
- Steering Wheels or Brakes do not respond to a command.
- Information about Road state
- Ice, Wind, Water, Pothole, etc.
- Traffic information
3 Syntax
https://schemas.mpai.community/CAV2/V1.0/data/RoadState.json
4 Semantics
| Label | Size | Description |
| Header | N1 Bytes | Road State Header |
| – Standard | 8 Bytes | The characters “CAV-RDS-V” |
| – Version | N2 Bytes | Major version – 1 or 2 Bytes |
| – Dot-separator | 1 Byte | The character “.” |
| – Subversion | N3 Bytes | Minor version – 1 or 2 Bytes |
| RoadStateID | N4 Bytes | Identifier of CAV instance. |
| RouteStateData | N5 Bytes | Set of Road State Data |
| – Pose | N6 Bytes | Identifier of the Way Point the Road State refers to. |
| – CAVState | N7 Bytes | Any of NoWheelResponse, NoBrakeResponse. NoSteeringResponse, |
| – RouteEnvironment | N8 Bytes | One of Ice, Wind, Water, Pothole. |
| – TrafficFlow | N9 Bytes | Traffic Flow |
| – TrafficFlowFormatID | N10 Bytes | Identifier of Traffic Flow Format |
| – TrafficFlowData | N11 Bytes | Traffic Flow Data |
| – Time | N12 Bytes | Time information. |
| DescrMetadata | N13 Bytes | Descriptive Metadata |
5 Data Formats and Attributes
Traffic Flow Format is required.
6 To Respondents
Respondents are requested to:
- Comment on, extend, or reformulate the functional requirements of Road State.
- Propose Traffic Flow Format and any other Format.
