Same as for 1.2.9.3.
TBCD-STRING ::= OCTET STRING
LAI ::= TBCD-STRING (SIZE(3))
The size constraint is not passed on during encode,decode
resulting in wrong encoding for PER , it is
coded with a length determinant which should not be there
when the length is fixed. For BER this does not matter because the constraints does
not affect the encodings.
ber_bin
available that can be used to
generate encode/decode functions for BER that uses the new "bit-syntax" to
make the functions more efficient. The ber_bin
option is used
as an alternative to the ber
and per
options.
The encode function then produces a possibly nested list of binaries and integer lists. The decode function does in this case require a single binary as input instead of a list. The modules generated with this option require that you have an R7A or later system, otherwise they will not compile and the runtime module asn1rt_ber_bin can not be executed.
The ber_bin option is not officially supported in this version (will be in a later version) but is provided for those who want to try it. It should be significantly faster at decode and is slightly faster at encode. Exactly how performance differs between this binary approach and the list approach depends highly on the type of input. Another thing worth noting is that both approaches still have a lot of solutions in common which can be improved a lot to gain even better performance.
COMPONENTS OF
is now implemented.