ETSI's Bug Tracker - ASN.1
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0006329ASN.1Base Specpublic12-11-2012 10:1904-01-2013 08:46
ReporterSebastian Muellers 
Assigned ToAndras Kovacs 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product VersionV0.0.4 
Target VersionFixed in VersionV0.0.5 
Summary0006329: CAM - HighFrequencyContainer-type contains only one choice
DescriptionDear Sebastian,

During today's ITS WG1 CAM meeting, I raised an issue with the ASN1:

The HighFrequencyContainer-type contains only one choice: BasicVehicleContainerHighFrequency. As a result, all ITS-S types are required to include this container while it makes no sense for an RSU. Solution I opted during the meeting is to include at least an empty high frequency container for the RSU and leave it empty but extendible. Dieter asked me to inform you about this issue and proposal:

HighFrequencyContainer ::= CHOICE {
    basicVehicleContainerHighFrequency BasicVehicleContainerHighFrequency,
    basicRSUContainerHighFrequency BasicRSUContainerHighFrequency,
    ...
}

BasicRSUContainerHighFrequency ::= SEQUENCE {
    ...
}

Can you please update the ASN.1 accordingly?

Thank you very much!

Best regards,

Laurens

--
Laurens HOBERT

Development Engineer
Cooperative System Team
Information & Communication Technologies Laboratory (ICTL)
HITACHI Europe - ERD

Hitachi c/o "Ecolucioles"
955, Routes des Lucioles
F-06560 Valbonne - Sophia Antipolis
FRANCE
http://www.hitachi.eu [^]
**************************************************************************************************
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
12-11-2012 10:19Sebastian MuellersNew Issue
21-11-2012 08:17Sebastian MuellersNote Added: 0011182
26-12-2012 15:31Andras KovacsNote Added: 0011313
26-12-2012 15:31Andras KovacsAssigned To => Andras Kovacs
26-12-2012 15:31Andras KovacsStatusnew => confirmed
26-12-2012 15:32Andras KovacsStatusconfirmed => acknowledged
04-01-2013 08:39Sebastian MuellersStatusacknowledged => resolved
04-01-2013 08:39Sebastian MuellersFixed in Version => V0.0.5
04-01-2013 08:39Sebastian MuellersResolutionopen => fixed
04-01-2013 08:39Sebastian MuellersNote Added: 0011315
04-01-2013 08:46Sebastian MuellersStatusresolved => closed

Notes
(0011182)
Sebastian Muellers   
21-11-2012 08:17   
Hi Sebastian,
 The intention of this choice type is also to enable various RSU types to include different structures according to their particular role.
 I agree with Laurens, that we should add here an empty container, to cover the case where the RSU does not have any high-frequency data to send. I would call it EmptyRSUContainerHighFrequency (instead of BasicRSUContainerHighFrequency), and define as follows:
EmptyRSUContainerHighFrequency ::= NULL

 Future definitions of RSU-specific high frequency containers will just introduce new choice possibilities, there is no backwards compatibility problem in my opinion.

Best regards,

Andras
(0011313)
Andras Kovacs   
26-12-2012 15:31   
I have made the following asn.1 update according to our email discussion of this issue:

 HighFrequencyContainer ::= CHOICE {
  basicVehicleContainerHighFrequency BasicVehicleContainerHighFrequency,
  emptyRSUContainerHighFrequency ::= NULL,
  ... -- further type specific RSU containers might be added as extensions
 }
(0011315)
Sebastian Muellers   
04-01-2013 08:39   
OK