ASN-1Step — Enhancements History

ASN-1Step 8.1.0 (latest version)

  • ASN-1Step now includes ASN.1 Studio v8.1.0.
  • ASN-1Step now supports 64-bit precision (19-20 decimal digits) in TIME type fractions.
  • The PER encoder-decoder implementation now conforms to the recent X.691 corrigendum (2015): an encoding contained in a BIT STRING should be at least one octet for PER ALIGNED and 1 bit for PER UNALIGNED.
  • ASN-1Step now fully conforms to ITU-T X.680 Clause 46.3c. This clause states that the minutes component of a GeneralizedTime type value can be omitted when the difference between local time and UTC is an integral number of hours. Previously, a false error could be issued when the minutes component was absent.

ASN-1Step 8.0.0

  • ASN-1Step now includes ASN.1 Studio v8.0.0.
  • The following command-line options enable support for the new JSON flags and features:
    • The -json option allows you to specify one or more valid JSON runtime flags to control the way the JSON encodings are created.
    • The -jsonIndent option allows you to specify the indentation size for the JSON encoding generated by ASN-1Step.
    For example:
    asn1step -json JSON_ENC_ABSENT_COMPONENTS:JSON_ENC_DEFAULT_VALUES jtest.asn -encode value1 -jsonIndent 4
  • ASN-1Step now includes full support for the 2015 version of the ASN.1 standard.

ASN-1Step 7.4

  • ASN-1Step now includes ASN.1 Studio v7.4
  • The OSS runtime flags are now available through the following ASN-1Step options: -flags <flags>, -encFlags <flags>, and -decFlags <flags>.
    You can specify one or more valid runtime flags separated by commas or colons, immediately after the option. To disable a flag, precede it by an exclamation point ("!").
  • The -csv <flags> command-line option has been added to ASN-1Step to enable support for the Comma-Separated Values (CSV) format when decoding messages.
  • ASN-1Step skips over pad bytes (0x00 or 0xFF) when decoding concatenated BER messages.
  • When encoding with PER, ASN-1Step no longer encodes components defined with a DEFAULT value when the value to be encoded is the default one (of a simple type, as noted in clause 19.5 of X.691).

ASN-1Step 7.1

  • ASN-1Step now includes ASN.1 Studio v7.1
  • ASN-1Step now supports Octet Encoding Rules (OER) and Canonical Octet Encoding Rules (C-OER) as defined in "Rec. ITU-T X.696 | ISO/IEC 8825-7", rather than only the subset of ASN.1 types as defined in the "NTCIP 1102:2004 Octet Encoding Rules (OER) Base Protocol" document.
    The Octet Encoding Rules (OER), like the Packed Encoding Rules (PER), produce compact encodings by taking advantage of information present in the ASN.1 schema to limit the amount of information included in each encoded message. However, in contrast to PER, OER favors encoding/decoding speed over compactness of the encodings.

ASN-1Step 7.0

  • ASN-1Step now includes ASN.1 Studio v7.0
  • ASN-1Step command-line utility improvements:
    • The "-listPduIds" option now accepts the optional "true" argument which, when specified, instructs ASN-1Step to limit the number of printed PDU identifiers available for decoding to unreferenced PDU types and to types marked with PDU directives.
    • Support for two new options: -allSampleAsn1Values and -sampleAsn1Value. With these options, you can create files containing sample messages for PDU types in the ASN.1 input that are in ASN.1 value notation format.
    • Error messages and warnings issued now have the same format as error messages issued by other OSS ASN.1 Tools components. Note that ASN-1Step messages used as headers or as part of a trace may still start with the "ASN1STEP" prefix to visually separate output from different operations.