Support encvalue()/decvalue() for ASN.1 types
Submitted by Gyorgy Rethy
Link to original bug (#500221)
Description
Currently encvalue() and decvalue() supports TTCN-3 types only. 3GPP and ITS protocols are specified using ASN.1 and PER encoding; thus encvalue() and decvalue() are intensively used in both 3GPP and ETSI ITS test suites.
Because ASN.1 types can use different encodings, a similar support is needed, than for TTCN-3 types with user-defined encode attribute strings: defining an external function with bitstring return value (for encoding functions and bitstring inout and out parameters for decoding functions, and either with BER:BER|CER|DER or with PER encoding specification. When BER is specified, Titan built-in codec functions should be called implicitly. When PER is specified, a manually implemented external function should be called, just like user-defined encode strings.
It should work both for ASN.1-based values and ASN.1 fields of TTCN-3 types (both cases appear in the test suites).
Version: 5.5.0