Logo etsi

ETSI's Bug Tracker

Notice: information submitted on the ETSI issue Tracker may be incorporated in ETSI publication(s) and therefore subject to the ETSI IPR policy.

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0007295CDD ASN.1 (TS 102 894-2)Bug Reportpublic08-01-2016 16:0728-03-2017 17:45
Reporterlinla 
Assigned ToYann Garcia 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product VersionTS 102 894-2 V1.2.1 
Target VersionNext ReleaseFixed in Version 
Summary0007295: [DE_ClosedLanes]: make drivingLaneStatus OPTIONAL
Description
Motivation:
Quote from CDD TS 102 894-2, page 88:

ClosedLanes ::= SEQUENCE {
hardShoulderStatus HardShoulderStatus OPTIONAL,
drivingLaneStatus DrivingLaneStatus,
...
}
If there is information available about the status of the hardshoulder, but no information regarding the driving lanes, the information for “hardShoulderstatus” cannot be transmitted, since “drivingLaneStatus” is not optional.

Consequence
The actual definition of “ClosedLanes” does not allow to transmit valid information about the hard shoulder status while not knowing the actual road layout – or forces the sender to guess and take the risk of giving false information about the number/status of driving lanes.
Example #1
In some roadworks configurations a closed hardshoulder can be identified by a roadworks trailer (by recognising certain sign configurations on the trailer), even without connection to a backend system and without knowing the lane configuration. This information cannot be transmitted in the structure of “ClosedLanes” as it is defined now.
As a matter of fact : Not wanting to give false informaion or to use a shady workaround, some information, although available, will not be transmitted in roadworks DENMS, just because it is not allowed to code “ClosedLanes” in a DENM with “hardShoulderstatus” alone.
Example 0000002
A broken down vehicle on a motorway might have detected that it is standing on the hard shoulder (e.g. by recognising the thick continous lane marking is located to its left), but it is not possible to convey this information to other vehicles without guessing the remaining road layout (which at this point in time might differ from the static information the car might have on its navigation device).
Again, available information is not transmitted, because it is not allowed to code “ClosedLanes” in a DENM with “hardShoulderstatus” alone – or wrong information might be transmitted about the number of driving lanes and/or their status.

Proposed Change:
“drivingLaneStatus” should become an optional element in the Sequence “ClosedLanes”. This way information only concerning the hard shoulder can be transmitted, even if the status of the driving lanes is not known or not effected at all.
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0013681)
linla (manager)
12-01-2016 12:34

this would break the backward compatibility, in this case, the protocol version number should be increased to 2, in case the present data frame is used by CAM or DENM or any other facilities basic service.
(0013915)
Sebastian Muellers (administrator)
04-04-2016 16:33

please approve at ITSWG1#35
(0013917)
Sebastian Muellers (administrator)
04-04-2016 16:37

this change is not backward compatibile and requires an update of CDD version to V2
(0013932)
linla (manager)
12-04-2016 13:42

approved in ITS WG1#35 meeting, make it OPTIONAL.
(0013938)
linla (manager)
12-04-2016 14:17

if we accept the follwing change:
DrivingLaneStatus ::= BIT STRING { } (SIZE (1..14))

text:
bit 0: reserved and shall be set to 0 by default.
bit 1: outerMostLane
bit 2: secondLaneFromOutMostLane
...

then there is no need to set it to OPTIOANL, because it is sufficient to send a one bit value (bit 0 set to 0)

please consider this and provide feedback to WG1.
(0013952)
Sebastian Muellers (administrator)
04-05-2016 09:26

Please implement
ClosedLanes ::= SEQUENCE {
    hardShoulderStatus HardShoulderStatus OPTIONAL,
    drivingLaneStatus DrivingLaneStatus OPTIONAL,
    ...
}
(0013953)
Yann Garcia (developer)
04-05-2016 09:52

Implementation done
(0014482)
linla (manager)
10-01-2017 15:21
edited on: 10-01-2017 16:12

Implemented in CDD v1.2.3 Jan 2017

(0014505)
linla (manager)
18-01-2017 11:02

reopenned at ITS WG1#38
(0014507)
linla (manager)
18-01-2017 11:09
edited on: 20-01-2017 14:13

modifications implemented in V1.2.4 in WG1#38, renamed as LaneStatus,add innerHardShoulder and outerHardShoulder

(0014543)
linla (manager)
28-03-2017 17:45

already approved in WG1#38

- Issue History
Date Modified Username Field Change
08-01-2016 16:07 linla New Issue
08-01-2016 16:07 linla Status new => assigned
08-01-2016 16:07 linla Assigned To => Sebastian Muellers
12-01-2016 12:34 linla Note Added: 0013681
04-04-2016 16:33 Sebastian Muellers Assigned To Sebastian Muellers => Lan LIN
04-04-2016 16:33 Sebastian Muellers Note Added: 0013915
04-04-2016 16:37 Sebastian Muellers Note Added: 0013917
12-04-2016 13:42 linla Note Added: 0013932
12-04-2016 13:42 linla Status assigned => confirmed
12-04-2016 14:17 linla Note Added: 0013938
12-04-2016 14:17 linla Assigned To Lan LIN => Sebastian Muellers
12-04-2016 14:17 linla Status confirmed => new
04-05-2016 09:25 Sebastian Muellers Assigned To Sebastian Muellers => Yann Garcia
04-05-2016 09:25 Sebastian Muellers Status new => assigned
04-05-2016 09:26 Sebastian Muellers Note Added: 0013952
04-05-2016 09:52 Yann Garcia Note Added: 0013953
04-05-2016 09:52 Yann Garcia Status assigned => resolved
04-05-2016 09:52 Yann Garcia Resolution open => fixed
10-01-2017 15:21 linla Note Added: 0014482
10-01-2017 16:12 linla Note Edited: 0014482 View Revisions
18-01-2017 11:02 linla Note Added: 0014505
18-01-2017 11:02 linla Status resolved => feedback
18-01-2017 11:02 linla Resolution fixed => reopened
18-01-2017 11:09 linla Note Added: 0014507
18-01-2017 11:09 linla Status feedback => assigned
20-01-2017 14:13 linla Note Edited: 0014507 View Revisions
28-03-2017 17:45 linla Note Added: 0014543
28-03-2017 17:45 linla Status assigned => resolved
28-03-2017 17:45 linla Resolution reopened => fixed


MantisBT 1.2.14 [^]
Copyright © 2000 - 2024 MantisBT Team
Powered by Mantis Bugtracker