Contents
ASN-1Step now includes ASN.1 Studio v8.2.
JSON Encoding Rules support in ASN-1Step now conforms to Draft ITU-T Recommendation X.jsoner.
JSON encodings inside files with the .jer extension are now accepted.
ASN-1Step conforms to the draft version of the JSON encoding rules (X.jsoner document) as regards the encoding of REAL types. Previously, REAL types were encoded according to the OSS Technical Specification for JSON Encoding Rules.
ASN-1Step supports 3GPP CDR files with messages encoded using various encoding rules that are specified inside 3GPP record headers. Currently the BER, Aligned and Unaligned PER, and XER encoding rules are supported.
Previously, when the -sampleAsn1Value option was specified, ASN-1Step created invalid sample values that had missing values for non-optional components inside SET or SEQUENCE types with constraints that are not yet supported by sample code generation. Now sample values are created, though they might not satisfy all applied constraints.
ASN-1Step issues an error without attempting to decode when the -decode option is used with an invalid PDU type identifier or a 0-PDU number and the Aligned PER, Unaligned PER, OER, C-OER, or JSON rules are used. Previously, ASN-1Step attempted to decode messages and relied on the corresponding decoder to issue an error.
Trace data generated when decoding PER Aligned messages now prints a whole number of octets in the "Total encoded length" string. Previously, "Total encoded length" was printed without taking the mandatory padding bits into account. For example, 3.2 was printed instead of 4.0 (or 4).
ASN-1Step now includes ASN.1 Studio v8.1.1.
ASN-1Step now includes ASN.1 Studio v8.1.
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.
OER encoding of untagged CHOICE values is now aligned with Corrigendum 1 of the X.696 standard. Previously, such CHOICE values were encoded BER-style: the outermost tag of the chosen alternative was encoded only once.
When OER is used, ASN-1Step now correctly processes ISO 8601 TIME type values with a property settings constraint that specifies "Basic=Date" and "Date=Y", "Date=YM", or "Date=YMD", with no Year settings. Previously, the OER encoder produced a verbose encoding instead of an optimized binary encoding.
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 now includes ASN.1 Studio v8.0.
ASN-1Step now includes support for the 2015 version of the ASN.1 standard.
The following command-line options enable support for the new JSON flags and features:
For example:
asn1step -json JSON_ENC_ABSENT_COMPONENTS:JSON_WRAPPED_ENCODING jtest.asn -encode value1 -jsonIndent 4
ASN-1Step now includes ASN.1 Studio v7.4.
OSS runtime flags are now available through the following ASN-1Step options:
-flags <flags> -encFlags <flags> -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 ("!").
Use the -csv <flags> command-line option to enable support for 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 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 now includes ASN.1 Studio v7.0.
Use the new -allSampleAsn1Values and -sampleAsn1Value options to create files that contain sample messages for PDU types in the ASN.1 input that are in ASN.1 value notation format.
This documentation applies to release 8.2 and later of ASN-1Step®. For earlier versions, consult the PDF manual available in your product installation.
Copyright © 2024 OSS Nokalva, Inc. All rights reserved.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means electronic, mechanical, photocopying, recording or otherwise, without the prior permission of OSS Nokalva, Inc.
Every distributed copy of ASN-1Step is associated with a specific license and related unique license number. That license determines, among other things, what functions of ASN-1Step are available to you.
We stand with Ukraine 