ETSI's Bug Tracker |
Anonymous | Login | Signup for local Mantis account | 02-05-2024 20:01 IST |
Main | My View | View Issues | Change Log | Roadmap | Monitor project |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0006329 | ASN.1 | Base Spec | public | 12-11-2012 10:19 | 04-01-2013 08:46 | ||||
Reporter | Sebastian Muellers | ||||||||
Assigned To | Andras Kovacs | ||||||||
Priority | normal | Severity | minor | Reproducibility | have not tried | ||||
Status | closed | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | V0.0.4 | ||||||||
Target Version | Fixed in Version | V0.0.5 | |||||||
Summary | 0006329: CAM - HighFrequencyContainer-type contains only one choice | ||||||||
Description | Dear 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 [^] ************************************************************************************************** | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||
Notes | |
(0011182) Sebastian Muellers (administrator) 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 (developer) 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 (administrator) 04-01-2013 08:39 |
OK |
Issue History | |||
Date Modified | Username | Field | Change |
12-11-2012 10:19 | Sebastian Muellers | New Issue | |
21-11-2012 08:17 | Sebastian Muellers | Note Added: 0011182 | |
26-12-2012 15:31 | Andras Kovacs | Note Added: 0011313 | |
26-12-2012 15:31 | Andras Kovacs | Assigned To | => Andras Kovacs |
26-12-2012 15:31 | Andras Kovacs | Status | new => confirmed |
26-12-2012 15:32 | Andras Kovacs | Status | confirmed => acknowledged |
04-01-2013 08:39 | Sebastian Muellers | Status | acknowledged => resolved |
04-01-2013 08:39 | Sebastian Muellers | Fixed in Version | => V0.0.5 |
04-01-2013 08:39 | Sebastian Muellers | Resolution | open => fixed |
04-01-2013 08:39 | Sebastian Muellers | Note Added: 0011315 | |
04-01-2013 08:46 | Sebastian Muellers | Status | resolved => closed |
MantisBT 1.2.14 [^] Copyright © 2000 - 2024 MantisBT Team |