-
Notifications
You must be signed in to change notification settings - Fork 44
Schema Version 6 Change Notice
Hamid Musavi edited this page Jan 24, 2019
·
27 revisions
The following changes are included in schemaVersion=6
implementation:
- Traveler Information Message (TIM) broadcast requests are published into a new
topic.J2735TimBroadcastJson
(see Sample Data). These messages comply with SAE J2735 2016 standard definition of TIM messages. The existingtopic.OdeTimBroadcastJson
still provides the TIM message broadcast request made by the Transportation Management Center (TMC), received, processed and broadcast by ODE to all designated recipients, i.e. Road Side Unit (RSU), and/or U.S. DOT Situation Data Warehouse (SDW). The schema of the metadata for the new topic is described indocs/ODE_Output_Schema_Reference.docx
and the payload schema is specified by J2735 standard and consistent with Recevied TIM messages. In summary, newrequest
data structure has been included in the outputmetadata
. -
request
structure has also been added totopic.OdeTimBroadcastPojo
andtopic.OdeTimBroadcastJson
metadata structure. -
index
element has been removed from thepayload/data
structure. In its stead,rsuIndex
element has been added to each RSU object inmetadata/request/rsus
. It provides the same information as the priorpayload/data/index
element except that now there can be a unique index for each RSU. - ODE timestamp format was modified to be fully compliant with ISO date/time format by eliminating the non-standard
[ZoneID]
component following the ISO timestamp.
Note: For topic.J2735TimBroadcastJson
and topic.OdeTimBroadcastJson
messages (NOT TIM Broadcast REST API Request), there will always be an rsus
object containing another rsus
object or array. If the TIM message is broadcast to only one RSU, the inner rsus
will be a JSON object. If the message is broadcast to multiple RSUs, the inner rsus
will appear as a JSON array. See samples below.
- Sample TIM Broadcast REST API Request with MULTIPLE RSUs
- Sample TIM Broadcast REST API Request with SINGLE RSU
- Sample topic.OdeTimBroadcastJson with MULTIPLE RSUs
- Sample topic.OdeTimBroadcastJson with SINGLE RSU
- Sample topic.J2735TimBroadcastJson with MULTIPLE RSUs
- Sample topic.J2735TimBroadcastJson with SINGLE RSU
- Decode a file with asn1c
- Deposit BSM to S3
- Docker fix for SSL issues due to corporate network
- Docker management
- ECDSA Primer
- Filter BSMs through PPM module
- Geofence Filtering for PPM
- Import BSMs from RSU log file
- Import TIMs from RSU log file
- jpo security svcs Integration
- Link host directory to Docker directory
- Migrating from SDW websocket depositor to SDW Depositor Submodule
- ODE Release Deployment
- ODE Release Preparation
- Prepare a fresh Ubuntu instance for ODE installation
- Process for Handling Bugs (Code Defects)
- Run the ODE using the ASN codec module
- Query RSU for set TIMs
- Schema Version 6 Change Notice
- Signed Message File Import
- TIM REST Endpoint Changes
- Using the .env configuration file
- Using the ODE test harness
- Delete TIM on RSU test
- Event Logger Test
- Import Decode and Deliver BSM Test
- Manage SNMP Test
- Sending PDM to RSU Test
- Sending TIM to RSU Test
- Submit_TIM_To_SDW Test
- Log File Changes (schemaVersion=4)
- Receive BSMs over UDP
- Receive ISD via UDP and deposit to SDC
- Receive VSD via UDP and deposit to SDC
- Run the crypto test vectors code with ODE team's OSS encoder
- SchemaVersion 5 Change Notice