Description
As the TMC, the ODE needs to have the full functionality to manage the deletion and placement of TIMs within an RSU, enabling the RSUs to hold multiple TIM messages at the same time.
CONVERSATION
Result of the following issue: https://github.com/usdot-jpo-ode/jpo-ode/issues/117
Features needed:
- SNMP query of the RSU to view existing TIM index sets
- Updated field in POST TIM message that includes an index on the RSU to place the TIM message (need index range)
- DELETE API call to remove TIM messages at a specific index on an RSU
USER ACCEPTANCE CRITERIA
( ) Query an RSU to view all current TIMs that are active (including the TIM index set on the RSU)
( ) TIM REST call to the ODE to include an index for the TIM.
( ) REST call to the ODE to delete a TIM from an RSU(s).
BUSINESS VALUE
In order to fully manage TIM messages on an RSU, there needs some additional CRUD API Calls to manage the index location of a TIM message and deleting existing messages.
DEFINITION OF DONE
( ) User acceptance criteria in the user story has been met; this includes user acceptance testing,
( ) Unit testing has been completed
( ) The code has been pushed out to GitHub
( ) This process has been documented in jira & release notes
( ) Demonstrated to Product Owner