Customer Documentation: Neonode® Touch Sensor Module User's Guide : .ASN.1 PDU Examples in GSER Notation v1.0

The ASN.1 PDU examples are encoded according to the man-readable Generic String Encoding Rules (GSER), as both the information in the PDU definition file and the messages encoded according to DER can be difficult to read for a human.

The following examples are available: 

A short introduction to the GSER notation:

• Sequences and/or sets (items containing sub items) are shown as curly brackets: { _}
• Values encoded as octet strings are written as hexadecimal octets enclosed within single quotes and suffixed with H: 'FF9900'H
• Bit strings are also shown as octet strings when the number of bits is a multiple of 8, otherwise each bit is shown as a single 1 or 0, and suffixed with B: '11010101001'B
• In a choice element, the selected type is denoted by its name followed by a colon: request:

Refer to Generic String Encoding Rules (GSER) for ASN.1 Types for a full reference.

The tool FFASN1Dump can transcode from GSER to DER:

ffasn1dump -I gser -O der zforce_pdu_def.asn ProtocolMessage