| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0006932 | MAP/SPAT | TSS&TP | public | 10-03-2015 15:56 | 23-11-2016 14:31 |
|
| Reporter | tepelmann | |
| Assigned To | Sebastian Muellers | |
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | |
| Platform | | OS | | OS Version | |
| Product Version | Test_Spec_TS103191_v1.1.1 | |
| Target Version | Next Release | Fixed in Version | | |
|
| Summary | 0006932: Check for introducing a test for revision as stated in section "1.10.4 DF_IntersectionState" |
| Description | In TP/MAP-SPAT/MSD/BV/03 and TP/MAP-SPAT/MSD/BV/04 the field msgIssueRevision(MsgCount) of the MapData message is tested which seems to be invalid, however the revision in the intersection state might be tested instead:
"
2.2.4 DF_IntersectionState
2.2.4.1 revision
The data element "revision" is used to communicate the actual valid release of the intersection description. If there are no changes in the deployed intersection description almost the same revision counter is transmitted. Due to a revised deployment of the intersection description (e.g. introduction of additional status element), the revision is increased by one. After revision equal to 127 the increment leads to 0 (due to the element range).
The intersection state and the intersection geometry is related each other. Therefore the revision of the intersection state shall be the same as the revision of the intersection geometry (see "DF_IntersectionGeometry").
"
|
| Tags | No tags attached. |
|
| Attached Files | |
|
Relationships 
Relationships 