Table of Contents


  1. Preface
  2. Introduction to Data Transformation
  3. Data Processor Transformation
  4. Wizard Input and Output Formats
  5. Relational Input and Output
  6. Using the IntelliScript Editor
  7. XMap
  8. Libraries
  9. Schema Object
  10. Command Line Interface
  11. Scripts
  12. Parsers
  13. Script Ports
  14. Document Processors
  15. Formats
  16. Data Holders
  17. Anchors
  18. Transformers
  19. Actions
  20. Serializers
  21. Mappers
  22. Locators, Keys, and Indexing
  23. Streamers
  24. Validators, Notifications, and Failure Handling
  25. Validation Rules
  26. Custom Script Components

ASN.1 Input Message Structure

ASN.1 Input Message Structure

The ASN.1 input is in binary format. The wizard creates a transformation for ASN.1 that includes the
document processor. The document processor shows the input in an XML representation.
An ASN.1 source usually contains many messages. Each message is a data structure that conforms to the protocol specification. The source can contain separator strings between the messages, and there can be a header string before the first message.
The data is in a binary format. The following example contains data in the BER encoding:
An ASN.1 source contains binary data that is not readable.
document processor converts the data to the ASN.1 XER encoding, which is an XML representation. When the Data Processor transformation wizard creates a transformation for ASN.1, it includes the
document processor in the transformation.
The following example contains the XML that the
document processor generates:
<mobileTerminatedCall> <basicCallInformation> <chargeableSubscriber> <simChargeableSubscriber> <imsi>45404200</imsi> <msisdn>85290469</msisdn> </simChargeableSubscriber> </chargeableSubscriber>
The XML hierarchy corresponds to the input message structure.

Updated June 14, 2019