Skip to content

TIM REST Endpoint Changes

hmusavi edited this page Dec 6, 2017 · 2 revisions

The TIM POST REST endpoint (https//ip:port/tim) has been updated as follows:

  • packetID will now be expected in HEX format. The value must be 9 bytes (18 hex characters) or less. For example:
    "packetID": "EC9C236B0000000000"
  • msgId is no longer string data type. Instead the msgId is now a JSON object with the following elements:
        "msgId": {
          "roadSignID": {
            "position": {
              "latitude": "41.678473",
              "longitude": "-108.782775",
              "elevation": "917.1432"
            },
            "viewAngle": "1010101010101010",
            "mutcdCode": "warning",
            "crc": "ABCD"
          },
          "furtherInfoID": "CDEF"
        }

Note that msgId now encapsulates either roadSignIDorfurtherInfoID. These elements are mutually exclusive and **only one should exist** in msgId. These elements were moved from being directly under a dataFrameto be a member ofmsgIdand should no longer be present underdataFrame. Consequently, position, viewAngle, mutcdCodeandcrcelements moved withroadSignID` element.

  • frameType element under a dataFrame is expected to be the enumeration string constant name as defined in J2735 TravelerInfoType rather than the integer value (ordinal) of the enumeration. Valid values are:
          unknown,
          advisory,
          roadSignage,
          commercialSignage
  • mutcdCode element under a roadSignID is expected to be the enumeration string constant name as defined in J2735 MUTCDCode rather than the integer value (ordinal) of the enumeration. The element name also changed from mutcd to mutcdCode to be consistent with J2735 element name. Valid values are:
          none,             -- non-MUTCD information
          regulatory,       -- "R" Regulatory signs
          warning,          -- "W" warning signs
          maintenance,      -- "M" Maintenance and construction
          motoristService,  -- Motorist Services
          guide,            -- "G" Guide signs
          rec               -- Recreation and Cultural Interest

see jpo-ode/data/TIM_Message_Testing_Files folder for sample test JSON data to be used in the REST endpoint.

Releases

Change Notices

Informational Reference

  • 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

Test Procedures

  • 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

Archived

  • 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
Clone this wiki locally