1 / 23

NOTICE!

NOTICE!.

soyala
Télécharger la présentation

NOTICE!

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NOTICE! • These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer Science and Engineering, University of Mälardalen, Västerås, Sweden and at the Faculty of Electrical Engineering and Computing, University of Zagreb, Croatia (year 2003/2004). • For all other purposes, authors’ written permission is needed! • The purpose of these materials is to help students in better understanding of lectures in DSD and not their replacement!

  2. Selected Topics in Software Engineering-Distributed Software Development

  3. ASN.1 to CSV converter generator Project Current state presentation 2008-12-04 FER: Ivan Škugor Željko Krpetić Željko Knežević MDH: Guido Di Campli Giovanni Piemontese Paolo D’Amelio Steering group:  Igor Čavrak at FER Rikard Lang at MDH M.Sc. Branko Beslać (Ring datacom)

  4. What we will talk about? • Problems • Solution modification • Interfaces • Alternative solution • GUI • General project status

  5. Problems - Mapping of BER to CSV - The BER file format (as described by the ASN.1 grammar) is a structured format, while CSV is a linear format • There is NO direct 1:1 mapping from BER files to CSV files ! • In cooperation with our customer we found a solution • Data in each node of the grammar is represented with a separate, different row in the CSV file • Each row has a type identifier at the beginning • It is not a real CSV file

  6. Problems – testing a lot of tools Open Source • SNACC/eSNACC • ASN1C • Libtasn1 • ... Commercial software • ASN.1 analyzer (Japan) • ASN1C ASN1 Compiler (Objective systems) • MARBEN™ ASNSDK TCE

  7. Problems – eSNACC modification • Modifying eSNACC turned out to be very difficult. • Even just compiling eSNACC from source code was problematic • Finding and modifying  ASN.1 parsing routines was a major problem • We found a better solution (using another ASN1C tool and our own parsing routines)

  8. Problems - Custom code generator • Generating code for all possible cases could be a problem • We extracted many rules from only one sample grammar (and of course, that was the simple one :) • We decided to look for other solutions • We found that BER files have a 1:1 mapping with XML • Alternative solution : use a 3rd party BER to XML converter, and then parse the XML file and generate CSV output

  9. Old software architecture

  10. Solution modifications

  11. Interfaces • Between tree generator and GUI • Between GUI and Custom code generator

  12. Example ASN.1 Grammar Nrtrde ::= [APPLICATION 1] SEQUENCE { specificationVersionNumber SpecificationVersionNumber OPTIONAL, -- *m.m. releaseVersionNumber ReleaseVersionNumber OPTIONAL, -- *m.m. sender Sender OPTIONAL, -- *m.m. recipient Recipient OPTIONAL, -- *m.m. sequenceNumber SequenceNumber OPTIONAL, -- *m.m. fileAvailableTimeStamp FileAvailableTimeStamp OPTIONAL, -- *m.m. utcTimeOffset UtcTimeOffset OPTIONAL, -- *m.m. callEvents CallEventList OPTIONAL, callEventsCount CallEventsCount OPTIONAL -- *m.m. } CallEventList ::= [APPLICATION 2] SEQUENCE OF CallEvent CallEvent ::= CHOICE { moc Moc, mtc Mtc, gprs Gprs }

  13. First interface - XML

  14. Second interface – Xpath format /Nrtrde[@type=‘SEQUENCE’]/CallEventList[@type=‘SEQUENCE OF’]/CallEvent[@type=‘CHOICE’]/Moc[@type=‘SEQUENCE’]/Imsi[@optional=‘YES’] /Nrtrde[@type=‘SEQUENCE’]/CallEventList[@type=‘SEQUENCE OF’]/CallEvent[@type=‘CHOICE’]/Moc[@type=‘SEQUENCE’]/Imei[@optional=‘YES’] /Nrtrde[@type=‘SEQUENCE’]/CallEventList[@type=‘SEQUENCE OF’]/CallEvent[@type=‘CHOICE’]/Moc[@type=‘SEQUENCE’]/CallEventDuration [@optional=‘YES’] /Nrtrde[@type=‘SEQUENCE’]/CallEventList[@type=‘SEQUENCE OF’]/CallEvent[@type=‘CHOICE’]/Moc[@type=‘SEQUENCE’]/DialledDigits [@optional=‘YES’] /Nrtrde[@type=‘SEQUENCE’]/CallEventList[@type=‘SEQUENCE OF’]/CallEvent[@type=‘CHOICE’]/Moc[@type=‘SEQUENCE’]/ChargeAmount [@optional=‘YES’]

  15. Alternative solution

  16. BER

  17. BER to XML

  18. (Quasi) CSV

  19. Custom code generator, xml2csv.c &XML to CSV converter

  20. GUI

  21. General project status Project status : slightly behind

  22. Summary • We learned a lot about the task and the standards thatare involved • Now we understand the problem much better, and our customer also understands the problem much better  • We hope that this presentation will help the steering team also understand the problem.

  23. Summary • The official name of the project is "ASN.1 to CSV converter“ • The input file is in fact a BER file (The BER formatspecifies a self-describing and self-delimiting format for encoding ASN.1 data structures) • The output file isn't actually in CSV format (because it's impossible to convert BER to that kind of format) • We are not producing a converter but a converter generator, and that is significantly different • We put a lot effort to understand all this things

More Related