Table of Contents

Search

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

Data Transformation User Guide

Data Transformation User Guide

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
AsnToXml
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.
The
AsnToXml
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
AsnToXml
document processor in the transformation.
The following example contains the XML that the
AsnToXml
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 September 26, 2018