1       Definition

Data produced by a “time-of-flight”-based active sensor called Radio Detection and Ranging (RADAR) able to measure the distance and speed of objects from the time it takes for a signal emitted by the sensor to hit an object and be reflected.

RADAR operates in the mm range. It can detect vehicles (CAVs and trucks) because they typically reflect radar signals while smaller and less reflecting objects, e.g., pedestrians and motorcycles have a poor reflectance. In a busy environment, the reflections of big vehicles can overcome a motorcycle’s causing missed detection of important objects (e.g., a human next to a vehicle), while a can may produce an image out of proportion to its size.

2       Functional Requirements

The main features of Radar Data are:

  1. Ability to detect objects and measure speed @ ≤ 250 m (long range radar in the 76-77 GHz).
  2. Ability to provide a resolution of ~25-cm radial and ~1.5 degrees angular.
  3. Suitability to measure distance (short range radar in the 25 GHz band).

3       Syntax

https://schemas.mpai.community/CAV2/V1.0/data/InputRADAR.json

4       Semantics

Label Size Description
Header N1 Bytes Input RADAR Header
– Standard 9 Bytes The characters “CAV-IRA-V”
– Version N2 Bytes Major version – 1 or 2 characters
– Dot-separator 1 Byte The character “.”
– Subversion N3 Byte Minor version – 1 or 2 characters
MInstanceID N4 Bytes ID of the Virtual Space.
InputRADARID N5 Bytes ID of Input RADAR.
RADARSensorID N6 Bytes ID of RADAR Sensor.
InputRADARData Ny Bytes Set of Input RADAR Data
– InputRADARQualifier N12 Bytes The Qualifier of Input RADAR
– InputRADARPayload N13 Bytes The Payload of Input RADAR
– InputRADARDataLength N14 Bytes The Length of Input RADAR Data in Bytes
– InputRADARDataURI N15 Bytes URI of Input RADAR Data
DescrMetadata N16 Bytes Descriptive Metadata

 

Label Size Description
Header N1 Bytes Input RADAR Header
·         Standard 9 Bytes The characters “CAV-IRA-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.
InputRADARID N5 Bytes Identifier of Input RADAR  Data.
RADARSensorID N6 Bytes Identifier of RADAR Sensor.
InputRADARTimeSpace N7 Bytes Space and Time of Input RADAR Data.
InputRADARData N8 Bytes Set of Input RADAR Data.
·         InputRADARFormatID N9 Bytes Format ID of Input RADAR Data.
·         InputRADARDataLength N10 Bytes Data Length of Input RADAR Data in Bytes.
·         InputRADARDataURI N11 Bytes Location of Input RADAR Data.
InputRadataAttributes[] N12 Bytes Attributes of Input RADAR Data.
·         InputRADARAttributeID N13 Bytes ID of Attribute of Input RADAR Data
·         RADARAttributeFormatID N14 Bytes ID of Attribute Format of Input Audio Data
·         InputRADARAttributeLength N15 Bytes Number of Bytes in Input RADAR Data
·         InputRADARAttributeDataURI N16 Bytes URI of Data of Input RADAR Data

5       Data Formats

Input RADAR requires:

  1. RADAR Format.
  2. RADAR Attribute Format.

6       To Respondents

Respondents are invited to:

  1. Identify functional requirements of the output data produced by RADAR sensors for indoor/outdoor (cabin) use.
  2. Propose Sub-Types, Formats, and Attributes for use in the future Technical Specification: Data Types, Formats, and Attributes (MPAI-TFA).