Definition
Functional Requirements
Syntax
Semantics
Conformance
Performance
1 Definition
CAV State is a Data Type generated by the Autonomous Motion Subsystem (AMS) that describes the operational condition of the CAV at a specific Time and Position. It is derived from measurements, estimations, and assessments performed inside the CAV using onboard sensing, diagnostics, and monitoring functions.
2 Functional Requirements
A CAV State shall include the following information:
- Time and Position of CAV State generation.
- Battery State, including temperature overload, remaining capacity, and abnormal discharge indicators.
- Brake Responsiveness, based on effective deceleration relative to the reference performance defined in UNECE braking regulations.
- Motor Responsiveness, based on effective acceleration derived from available motor torque, gear ratio, wheel radius, and vehicle mass.
- Wheel Responsiveness, describing traction effectiveness, slip behaviour, rotational anomalies, and mechanical integrity.
The AMS uses CAV State to estimate operational time and distance by combining CAV State with Route, lighting configuration, air conditioning load, cabin temperature, and Velocity.
3 Syntax
https://schemas.mpai.community/CAV2/V2.0/data/CAVState.json
4 Semantics
Table 1 specifies the semantics of the CAV State Data Type.
| Label | Type | Req. | Description |
|---|---|---|---|
| Header | string (CAV-CST-V2.0) | Yes | CAV State Header – Standard CAV-CST-Vx.y |
| MInstanceID | string | Identifier of the M-Instance (Virtual Space) associated with this CAV State. | |
| UEnvironmentID | string | Identifier of the U-Environment (Real Space) associated with this CAV State. | |
| CAVStateID | string | Yes | Unique identifier of this CAV State instance. |
| CAVStateTime | Simple Time | Time this CAV State was produced. | |
| CAVStateSpaceTime | Simple Time | Space/Time where/when this CAV State was generated. | |
| CAVState | object | Yes | Set of data describing the operational condition of the CAV. |
| CAVState. |
object | Battery condition including capacity, temperature, and abnormal discharge indicators. | |
| CAVState. |
string | Unit of battery capacity measurement. One of: mAh, Wh. | |
| CAVState. |
number | Battery capacity value in the specified MeasureType. | |
| CAVState. |
number | Remaining battery capacity as a percentage. | |
| CAVState. |
object | Brake performance based on effective deceleration relative to UNECE braking regulations. | |
| CAVState. |
number | Measured vehicle deceleration (m/s²). | |
| CAVState. |
number | Expected deceleration per UNECE reference (m/s²). | |
| CAVState. |
number | Difference between measured and expected deceleration (m/s²). | |
| CAVState. |
string | Identifier of the UNECE braking regulation used as reference. | |
| CAVState. |
object | Effective acceleration derived from available motor torque, gear ratio, wheel radius, and vehicle mass. | |
| CAVState. |
number | Measured vehicle acceleration (m/s²). | |
| CAVState. |
number | Expected vehicle acceleration (m/s²). | |
| CAVState. |
number | Available motor torque (N·m). | |
| CAVState. |
number | Current gear ratio. | |
| CAVState. |
number | Wheel radius (m). | |
| CAVState. |
number | Vehicle mass (kg). | |
| CAVState. |
object | Traction effectiveness, slip behaviour, rotational anomalies, and mechanical integrity. | |
| CAVState. |
number | Wheel slip ratio derived from wheel-speed sensors. | |
| CAVState. |
boolean | Indicates whether a rotational anomaly is detected. | |
| CAVState. |
string | Description of wheel mechanical integrity status. | |
| DataXMData | Data Exchange Metadata | MPAI-PTF Data Exchange Metadata providing provenance, authorisation, legal, security, and confidence information associated with this CAV State in a trusted data exchange context. | |
| DescrMetadata | string | Human-readable descriptive metadata of the CAV State (plain text, max 2048 characters). |
5 Conformance Testing
Data conform to the CAV State Data Type when they validate against its schema. If the schema references other schemas, data referencing a secondary schema shall also validate against that schema, if present, and conform with the Qualifier, if present.
