We are proud to announce the release of new major versions of our ASN1VE and ASN2TXT products for 2020.
ASN1VE (ASN.1 Viewer / Editor) is a graphical user interface (GUI) tool for analyzing and editing ASN.1 encoded data. In the new 3.0 release, we have added the following capabilities:
- Added verification and encoding support for canonical encoding rules including DER, CER, and COER. The new capability checks for canonical rule violations within the encoded data. New messages can be created in these formats and existing messages transformed to ensure canonical form.
- The capability to import JSON or XML messages into Octet Encoding Rules (OER) format has been added.
- The capability to copy and paste tree nodes in element view has been added.
- Improved performance in loading and searching for data in large TAP3 and other CDR files.
- Changed the Windows installation procedure to first deinstall an existing version before trying to install a newer version.
ASN2TXT (ASN.1 to text translator) is a command-line tool for translating ASN.1 encoded data to and from various textual formats (XML, JSON, CSV). The main new capability added in the 3.0 release is a Python wrapper that makes it possible to use the DLL in Python applications.
Other new features for the two products are documented in the Release Notes and Change Log. See the Product Support Page at obj-sys.com/support.php
This is an update to the original blog post on this topic done on June 28, 2011 at http://www.obj-sys.com/blog/?p=355. At the time, we did not have support in ASN1VE to process 3GPP TS 32.297 CDR headers, which is what the Huawei IMS CDR’s mentioned in the post contained. Although it is still possible to skip these headers, this is not reliable as the headers may be variable length. The updated procedure to view these CDR files with a newer version of ASN1VE is as follows:
- Open the CDR file. The “Assign All Items Wizard” popup window will appear:
Select the “cdr” option (not “ber”) and click Next.
The second wizard popup will appear:
On this popup, check the “3GPP TS 32.297 Headers” radio button and click Next.
The normal procedure for assigning an ASN.1 schema file can then be followed from that point forward. The result will be the display of the CDR file with the headers fully decoded.
An example of this can be found in the sample/ts32297 directory within an ASN1VE installation.
If you’re running a Windows system with a version of the operating system that’s older than Windows 10, there’s a chance you’ll see a pop-up box like this if you install and try to start ASN1VE:
The missing DLL is part of the Visual Studio 2015 redistributable kit. If this error occurs, it means your Windows system doesn’t have this kit.
You can download the kit and install it from here.
New major releases of our ASN1VE and ASN2TXT products are now available. The primary new feature added to each is support for the new ASN.1 JSON Encoding Rules (JER) as documented in the ITU-T X.697 standard that was made public last fall. ASN1VE now has a JSON tab that shows the JSON encoding for any binary message type. In addition, the Import and Export options under the File pulldown menu allow export to, or importing from JSON. ASN2TXT support translations in both directions (binary -> JSON and JSON -> binary).
Other improvements to ASN1VE included the following:
- Added the capability to display and edit the contents of OCTET or BIT STRING types with contents constraints (CONTAINING constructs) using the inner contained type.
- Added level to the tag search dialog to make it possible to search for tags at a given level instead of at any level.
- Improved PDU tag matching for BER/DER messages with UNIVERSAL tags (common in ASN.1 used in security specifications). This makes it easier to find the PDU type of a message if it is not known.
- Changed the Windows and Mac installation procedures to install the executable files in the Program Files area and sample programs in the User area. On Windows, sample programs are now copied to the user’s Documents directory under the ASN1VE folder.
For ASN2TXT, the capability do tag path filtering was another new feature that was added. This makes it possible to find and output elements in textual form if the full ASN.1 specification is not available. This capability was further described in this blog post.
Further details can be found in the release notes:
ASN1VE Release Notes
ASN2TXT Release Notes
The latest release of our ASN.1 to Text Translation Tool (ASN2TXT) contains a new feature called “tag path filtering”. The purpose of this is to allow users to target specific items within a BER-encoded message without the need for full ASN.1 schema information. One use case for this would be the case where a user has a Call Detail Record (CDR) specification which has snippets of ASN.1 code, but which does not have the full specification. Another use case is where the user has the full specification, but is only interested in accessing a few specific items within the encoded data.
The way it works is the “tag path” to specific elements within the message is specified in an XML file along with other information such as the data type of the item and names to be used. The tag path is a concatenated list of ASN.1 tag values using a special compact syntax. So instead of using the full name for a tag such as [UNIVERSAL 22], only the first letter of the tag class would be used and there would be no space between the letter and the tag number. Therefore, [U22] would be the shorthand name for this tag.
In addition to the tag path, the following items can be used in a tag path specification:
- name – a name that will be used in some types of output formats in place of the generated tag name.
- type – the data type of the element used to format the value for output.
- value – a textual value that would replace the actual data at the tag location.
The specification of a complete tag path is expressed in XML as follows:
<path> path in tag path format </path>
<name> name of the element </name>
<type> data type of the element </type>
<value> value to use for the element </value>
A tag path filter consists of one or more of these elements wrapped in an <asn1TagFilter> element.
This is just a brief summary of the basic idea behind tag paths. Full details can be found in the ASN2TXT User’s Manual in the section on ASN.1 Tag Path Filtering.