ASN-1Step — Enhancements History

ASN-1Step 10.1.2 (latest version)

ASN-1Step 10.1.1

ASN-1Step 10.1

  • ASN-1Step now includes ASN.1 Studio v10.1.
  • The limit of 50 on the user-specified maximum number of CSVs created for multiple components of each SET OF and SEQUENCE OF type values has been removed in the -csv option. See the following example:
    asn1step bcas.asn test.ber -decodePdu BBCard -csv dash,4000
    The total number of additional CSVs for all SET OF and SEQUENCE OF types is limited to the maximum between the user-specified number and 50, multiplied by 50.
  • ASN-1Step now issues a warning when an untagged open type precedes the extension marker in an extensible type in violation of the tag uniqueness requirement (see X.680 clauses 25.7, 52.7.3, 52.7.4, X.681 14.2 b) NOTE 2).
  • ASN-1Step now correctly considers extensible internal subtype constraints on TIME types as OER-invisible. Previously, such constraints were treated as OER-visible, which could prevent optimized encoding of some TIME types. For example, a value of the following type T was previously encoded using the non-optimized TIME encoding:
    T ::= DATE ("2020-10-10", ...)
    It is now encoded using the optimized DATE encoding.

ASN-1Step 10.0.1

  • ASN-1Step now includes ASN.1 Studio v10.0.1.
  • ASN-1Step now allows you to specify the maximum number of messages to decode and optionally, when possible, to skip the specified number of messages before decoding starts.
  • When creating and printing ASN.1 types and values, ASN-1Step now supports open types derived from a component relation constraint nested within a contents constraint applied to fields that contain BIT STRING or OCTET STRING types.
  • When an OSS.PrintFunctionName directive that contains an OSS conversion function specified as a parameter is applied to OCTET STRING types and conversion is possible, the value notation will now include the actual BCD, TBCD, ASCII, IP address, or time stamp values inside an ASN.1 comment, for example:
    '0711071136492B0000'H -- 2007-11-07 11:36:49 --

ASN-1Step 9.0.0

  • ASN-1Step now includes ASN.1 Studio v9.0.0.
  • ASN-1Step now supports X.680 Amendment 1, which relaxes the IMPORTS clause to allow symbols to be imported from the latest module version, as indicated by the object identifier. The IMPORTS clause can now include WITH SUCCESSORS and WITH DESCENDANTS as the SelectionOption.
  • The JSON encoders now support an alternative form of encoding values of BIT STRING or OCTET STRING types with contents constraints when an ENCODED BY is absent. When you select this method, the values are encoded as text (the JSON value represents the contained value) rather than hex string.

ASN-1Step 8.3.0

  • ASN-1Step now includes ASN.1 Studio v8.3.0.
  • Support for the Canonical Packed Encoding Rules (ALIGNED and UNALIGNED), as specified by ITU-T Recommendation X.691 (08/2015) | ISO/IEC 8825-2:2015 has been added:
    • The new -cper and -cuper compiler options instruct ASN-1Step to enable support for CPER.
    • For better security, the CPER decoder operates in strict mode: every deviation from the X.691 standard is reported.
  • ASN-1Step will now accept any valid value of GeneralizedTime and UTCTime types and will encode it according to X.690 Clause 11.7 and 11.8. Previously, it was assumed that the input value already satisfied the restrictions imposed on its encoding by these clauses. Therefore
    • All encoders reported an error if the time differential was present in the input value.
    • The DER/CER/COER encoders reported an error if the input value represented as a NULLTERM string did not contain the minutes or seconds component.
  • The XER and E-XER encoders now encode any valid NULLTERM values of GeneralizedTime and UTCTime types without making additional changes. Previously, when the input value did not contain a minutes or seconds component, the encoders unnecessarily included a zero minutes or seconds component in the encoding and recalculated the fractional part, if any.
  • The JSON encoders will now always encode non-special REAL values as JSON numbers. The JSON decoders will accept both encoding forms: JSON number and JSON object encodings. Previously, non-special REAL values could be encoded as JSON objects. For example, an unconstrained REAL type value was encoded as {base10value: N } The decoders reported an error when such values were encoded as JSON numbers.

ASN-1Step 8.2.0

  • ASN-1Step now includes ASN.1 Studio v8.2.0.
  • Conformance to Draft ITU-T Recommendation X.jsoner:
    • ASN-1Step supports the JSON Encoding Rules. The existing -json command-line option instructs the compiler to enable support for X.jsoner at runtime.
    • The JSON codec supports the following encoding instructions:
      • JER:ARRAY
      • JER:BASE64
      • JER:NAME
      • JER:OBJECT
      • JER:TEXT
  • ASN-1Step supports 3GPP CDR files containing messages encoded using various encoding rules that are specified inside record headers. Currently the BER, PER, UPER, and XER encoding rules are supported.

ASN-1Step 8.1.1

ASN-1Step 8.1.0

  • 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 support for the 2015 version of the ASN.1 standard.

ASN-1Step 7.4.0

  • ASN-1Step now includes ASN.1 Studio v7.4.0
  • 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.0

  • ASN-1Step now includes ASN.1 Studio v7.1.0
  • ASN-1Step now supports Octet Encoding Rules (OER) and Canonical Octet Encoding Rules (COER) 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.0

  • ASN-1Step now includes ASN.1 Studio v7.0.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.