While the basic SOED API is interpretive when it comes to encoding/decoding, it allows you to directly work with the decoded data as an ordinary C structure.
However, IAAPI, which uses the SOED for encoding/decoding, does not allow you to directly work with the decoded data. Instead, it requires you to determine at runtime what the PDU number is, what the associated ASN.1 type is, how many fields are in PDU, what is the type of the first field in the PDU, whether the first field is mandatory or optional, whether the value is actually present in the encoding, and on and on. It is perfect for browsers and similar applications that learn about the messages they are working with at runtime.
Contrast this with most applications which have a very good idea at development time what messages the application will support. But the penalty is that the IAAPI has high processing overhead when compared to directly referencing instances of C structures that the ASN.1 compiler generates.
The samples included with some of the Knowledge Center answers are meant for your general understanding of the OSS products. Different versions of the products might produce slightly different outputs. Consult the products documentation and samples for the most up-to-date products information and code examples.
Test drive the OSS Nokalva ASN.1, LTE, and XML Tools now! Your trial includes complete software, documentation, sample programs, free 24x7 technical support and more.
Our expert personnel can help you learn ASN.1!
We offer 4-day ASN.1 courses at our headquarters or your premises.