Creating a New ASN.1 Data File

To create a new message file, select File -> New -> Message from the File menu. This will launch the New File Wizard.

Select one of the options presented and click Next.

The ber, der, cer, oer, coer, per, and uper options allow a user to create a new ASN.1 data file using one of these encoding rule sets. The cdr option is for creating a Call Detail Record (CDR) file that contains additional non-ASN.1 headers.

If cdr is chosen, proceed to the next section on specification of CDR headers. Otherwise, jump to the next section on assigning ASN.1 schema information.

Specification of CDR Header Data

After "cdr" is chosen, the "Header Format" dialog is presented:


No headers will be added to the encoded data. This is the same as having selected "ber" in the previous window.


Data will be encoded into blocks of a certain size. If a message would normally be encoded across a block boundary (for a block size of 2048 bytes, this boundary is at offsets 2048, 4096, 8192, ...), the rest of the current block is instead padded out and the message is encoded, starting at the beginning of the next block. Padding bytes are also used to determine whether a block contains more data or is padded out.

3GPP TS 32.297 Headers

Data will be encoded according to the TS 32.297 standard. This includes file and message headers of the standard format.

Custom Headers

Custom headers are fixed-length headers that allow data fields within the headers to be specified. Selecting this option will cause an additional dialog to be opened that allows headers and header fields to be declared.

See the section on editing custom headers for details on editing the header format.

Once the header type has been selected, click Next.

Assignment of ASN.1 Schema Files

The next page of the wizard prompts for a schema to use. This would be the first page displayed after a file type other than cdr is selected.

At the top, three options are available, None, User schema files, and Built-in schema files. The None option is only available for BER and allows a user to define a message without schema using hex data. The User schema files option allows the user to select their own ASN.1 schema files. Built-in schema files presents a list of available schemas built into ASN1VE.

Below the selection options, the wizard shows lists for schema files and include directories. ASN.1 schema files should be added to the list of schema files that define the type of message being created. Include directories are directories to search to resolve import statements within the selected schema files.

Clicking Add... next to either list will bring up a file dialog. Navigate to the directory or file(s) to add, highlight them, and click Open.

To remove a listed file or directory, highlight it in the list and click the Remove button next to the list.

Below the schema files and include directories, Configuration File allows the user to apply settings from an Objective Systems configuration file. To select a configuration file, click the Browse... button. See the Configuration Files section for more information.

If Built-in schema files is selected at the top, the wizard will show a list of all the available built-in schemas in ASN1VE. Click to select a schema to use.

Once a schema has been selected, click Next. The wizard will show a list of types that can be used as the protocol data unit (PDU) for the message.

Click a node to select a PDU type. If the type desired is not shown, clicking Display all types at the top of the window will display a list of all the types defined in the selected schema. Once a PDU type is selected, click Finish.

If on the first page "cdr" was chosen, ASN1VE will prompt the user for a number of records to generate. Otherwise (or after choosing how many records to create), the newly-created message will be shown in the Element View and encoded in the Hex tab.