BER - Extending decoding of primitive types

[debackel]

I would like to be able to tailor the decoding of some (specific) OCTET STRING fields.

In 3GPP, they sometimes just specify an OCTET STRING field, referring to other specifications for the precise encoding/decoding

Example: 3GPP TS 32.298, "uETimeZone" is an OCTET STRING for which the encoding is defined in TS 29.060 and in TS 29.212.

I would like to present the decoded field in a readable format (a string would do), not as an OCTET STRING.

What would be the best way to tailor the decoding of a primitive type for certain field names?
Is there a possibility to add a generic mechanism (hooks) to isolate those specific decoding instructions in a separate simple python module?
I would think this would be an easy way for asn1tools to look at specific modules (say PrimitiveTypes.py) in a specific directory, and if exists, hand-over the decoding of those primitives. Or to add the extension class as a parameter in the asn1tools decode function)

Thanks in advance for any advice.

Laurent