Erlang -- Internal form and its encodings

User's Guide
Reference Manual
Release Notes
PDF
Top

Megaco/H.248
User's Guide
Version 3.16.0.2

Expand All
Contract All

Chapters

- Introduction
  - Top of chapter
  - Scope and Purpose
  - Prerequisites
  - About This Manual
  - Where to Find More Information
- Architecture
  - Top of chapter
  - Network view
  - General
  - Single node config
  - Distributed config
  - Message round-trip call flow
- Running the stack
  - Top of chapter
  - Starting
  - MGC startup call flow
  - MG startup call flow
  - Configuring the Megaco stack
  - Initial configuration
  - Changing the configuration
  - The transaction sender
  - Segmentation of transaction replies
- Internal form and its encodings
  - Top of chapter
  - Internal form of messages
  - The different encodings
  - Configuration of Erlang distribution encoding module
  - Configuration of text encoding module(s)
  - Configuration of binary encoding module(s)
  - Handling megaco versions
  - Encoder callback functions
- Transport mechanisms
  - Top of chapter
  - Callback interface
  - Examples
- Implementation examples
  - Top of chapter
  - A simple Media Gateway Controller
  - A simple Media Gateway
- Megaco mib
  - Top of chapter
  - Intro
  - Statistics counters
  - Distribution
- Performance comparison
  - Top of chapter
  - Comparison of encoder/decoders
  - System performance characteristics
  - Description of encoders/decoders
  - Setup
  - Summary
- Testing and tools
  - Top of chapter
  - Tracing
  - Measurement and transformation

# 4 Internal form and its encodings

This version of the stack is compliant with:

- Megaco/H.248 version 1 (RFC3525) updated according to Implementors Guide version 10-13.

- Megaco/H.248 version 2 as defined by draft-ietf-megaco-h248v2-04 updated according to Implementors Guide version 10-13.

- Megaco/H.248 version 3 as defined by ITU H.248.1 (09/2005).

### 4.1 Internal form of messages

We use the same internal form for both the binary and text encoding. Our internal form of Megaco/H.248 messages is heavily influenced by the internal format used by ASN.1 encoders/decoders:

- "SEQUENCE OF" is represented as a list.

- "CHOICE" is represented as a tagged tuple with size 2.

- "SEQUENCE" is represented as a record, defined in "megaco/include/megaco_message_v1.hrl".

- "OPTIONAL" is represented as an ordinary field in a record which defaults to 'asn1_NOVALUE', meaning that the field has no value.

- "OCTET STRING" is represented as a list of unsigned integers.

- "ENUMERATED" is represented as a single atom.

- "BIT STRING" is represented as a list of atoms.

- "BOOLEAN" is represented as the atom 'true' or 'false'.

- "INTEGER" is represented as an integer.

- "IA5String" is represented as a list of integers, where each integer is the ASCII value of the corresponding character.

- "NULL" is represented as the atom 'NULL'.

In order to fully understand the internal form you must get hold on a ASN.1 specification for the Megaco/H.248 protocol, and apply the rules above. Please, see the documentation of the ASN.1 compiler in Erlang/OTP for more details of the semantics in mapping between ASN.1 and the corresponding internal form.

Observe that the 'TerminationId' record is not used in the internal form. It has been replaced with a megaco_term_id record (defined in "megaco/include/megaco.hrl").

### 4.2 The different encodings

The Megaco/H.248 standard defines both a plain text encoding and a binary encoding (ASN.1 BER) and we have implemented encoders and decoders for both. We do in fact supply five different encoding/decoding modules.

In the text encoding, implementors have the choice of using a mix of short and long keywords. It is also possible to add white spaces to improve readability. We use the term compact for text messages with the shortest possible keywords and no optional white spaces, and the term pretty for a well indented text format using long keywords and an indentation style like the text examples in the Megaco/H.248 specification).

Here follows an example of a text message to give a feeling of the difference between the pretty and compact versions of text messages. First the pretty, well indented version with long keywords:

       MEGACO/1 [124.124.124.222]
       Transaction = 9998 {
               Context = - {
                       ServiceChange = ROOT {
                               Services {
                                       Method = Restart,
                                       ServiceChangeAddress = 55555,
                                       Profile = ResGW/1,
                                       Reason = "901 Cold Boot"
                               }
                       }
               }
       }

Then the compact version without indentation and with short keywords:

       !/1 [124.124.124.222]
       T=9998{C=-{SC=ROOT{SV{MT=RS,AD=55555,PF=ResGW/1,RE="901 Cold Boot"}}}}

And the programmers view of the same message. First a list of ActionRequest records are constructed and then it is sent with one of the send functions in the API:

      Prof = #'ServiceChangeProfile'{profileName = "resgw", version = 1},
      Parm = #'ServiceChangeParm'{serviceChangeMethod  = restart,
                                  serviceChangeAddress = {portNumber, 55555},
                                  serviceChangeReason  = "901 Cold Boot",
                                  serviceChangeProfile = Prof},
      Req = #'ServiceChangeRequest'{terminationID = [?megaco_root_termination_id],
                                    serviceChangeParms = Parm},
      Actions = [#'ActionRequest'{contextId = ?megaco_null_context_id,
                                  commandRequests = {serviceChangeReq, Req}}],
      megaco:call(ConnHandle, Actions, Config).

And finally a print-out of the entire internal form:

      {'MegacoMessage',
       asn1_NOVALUE,
       {'Message',
        1,
        {ip4Address,{'IP4Address', [124,124,124,222], asn1_NOVALUE}},
        {transactions,
         [
          {transactionRequest,
           {'TransactionRequest',
             9998,
             [{'ActionRequest',
               0,
               asn1_NOVALUE,
               asn1_NOVALUE,
               [
                {'CommandRequest',
                 {serviceChangeReq,
                  {'ServiceChangeRequest',
                   [
                    {megaco_term_id, false, ["root"]}],
                    {'ServiceChangeParm',
                     restart,
                     {portNumber, 55555},
                     asn1_NOVALUE,
                     {'ServiceChangeProfile', "resgw", version = 1},
                     "901 MG Cold Boot",
                     asn1_NOVALUE,
                     asn1_NOVALUE,
                     asn1_NOVALUE
                    }
                  }
                 },
                 asn1_NOVALUE,
                 asn1_NOVALUE
                }
               ]
              }
             ]
           }
          }
         ]
        }
       }
      }

The following encoding modules are provided:

- megaco_pretty_text_encoder - encodes messages into pretty text format, decodes both pretty as well as compact text.

- megaco_compact_text_encoder - encodes messages into compact text format, decodes both pretty as well as compact text.

- megaco_binary_encoder - encode/decode ASN.1 BER messages. This encoder implements the fastest of the BER encoders/decoders. Recommended binary codec.

- megaco_ber_encoder - encode/decode ASN.1 BER messages.

- megaco_ber_bin_encoder - encode/decode ASN.1 BER messages. This encoder uses ASN.1 ber_bin which has been optimized using the bit syntax.

- megaco_per_encoder - encode/decode ASN.1 PER messages. N.B. that this format is not included in the Megaco standard.

- megaco_per_bin_encoder - encode/decode ASN.1 PER messages. N.B. that this format is not included in the Megaco standard. This encoder uses ASN.1 per_bin which has been optimized using the bit syntax.

- megaco_erl_dist_encoder - encodes messages into Erlangs distribution format. It is rather verbose but encoding and decoding is blinding fast. N.B. that this format is not included in the Megaco standard.

### 4.3 Configuration of Erlang distribution encoding module

The encoding_config of the megaco_erl_dist_encoder module may be one of these:

- [] - Encodes the messages to the standard distribution format. It is rather verbose but encoding and decoding is blinding fast.

- [megaco_compressed] - Encodes the messages to the standard distribution format after an internal transformation. It is less verbose, but the total time of the encoding and decoding will on the other hand be somewhat slower (see the performance chapter for more info).

- [{megaco_compressed, Module}] - Works in the same way as the megaco_compressed config parameter, only here the user provide their own compress module. This module must implement the megaco_edist_compress behaviour.

- [compressed] - Encodes the messages to a compressed form of the standard distribution format. It is less verbose, but the encoding and decoding will on the other hand be slower.

### 4.4 Configuration of text encoding module(s)

When using text encoding(s), there is actually two different configs controlling what software to use:

- [] - An empty list indicates that the erlang scanner should be used.

- [{flex, port()}] - Use the flex scanner when decoding (not optimized for SMP). See initial configuration for more info.

- [{flex, ports()}] - Use the flex scanner when decoding (optimized for SMP). See initial configuration for more info.

The Flex scanner is a Megaco scanner written as a linked in driver (in C). There are two ways to get this working:

- Let the Megaco stack start the flex scanner (load the driver).

  To make this happen the megaco stack has to be configured:

  - Add the {scanner, flex} (or similar) directive to an Erlang system config file for the megaco app (see initial configuration chapter for details).

  - Retrieve the encoding-config using the system_info function (with Item = text_config).

  - Update the receive handle with the encoding-config (the encoding_config field).

  The benefit of this is that Megaco handles the starting, holding and the supervision of the driver and port.

- The Megaco client (user) starts the flex scanner (load the driver).

  When starting the flex scanner a port to the linked in driver is created. This port has to be owned by a process. This process must not die. If it does the port will also terminate. Therefor:

  - Create a permanent process. Make sure this process is supervised (so that if it does die, this will be noticed).

  - Let this process start the flex scanner by calling the megaco_flex_scanner:start/0,1 function.

  - Retrieve the encoding-config and when initiating the megaco_receive_handle, set the field encoding_config accordingly.

  - Pass the megaco_receive_handle to the transport module.

### 4.5 Configuration of binary encoding module(s)

When using binary encoding, the structure of the termination id's needs to be specified.

- [driver|_] - make use of the asn1 driver for decode (ber_bin) and encode (per_bin). This option is only available for encoding modules: megaco_binary_encoder, megaco_ber_bin_encoder and megaco_per_bin_encoder.

  If this option is present in the encoding config, it must to be the first, unless the version3 encoding config is present, in which case it must come second, after the version3 encoding config, e.g. [{version3,prev3b},driver].

- [native] - skips the transformation phase, i.e. the decoded message(s) will not be transformed into our internal form.

- [integer()] - A list containing the size (the number of bits) of each level. Example: [3,8,5,8].

- integer() - Number of one byte (8 bits) levels. N.B. This is currently converted into the previous config. Example: 3 ([8,8,8]).

### 4.6 Handling megaco versions

Since the version 3 implemented, in this version of the Megaco application, is preliminary, it is necessary to have a way to handle different version 3 implementations. For this reason the encoding config option {version3, version3()} has been introduced. This option, if present, has to be first in the encoding config list. Version 1 and 2 codec's ignore this option, if found.

    version3() -> prev3a | prev3b | prev3c | v3

- prev3a

  Preliminary version 3, based on TD-33

- prev3b

  Preliminary version 3, based on TD-33, but text encoding updated with the final solution for priority in contextProperty (which is backward compatible with v2).

- prev3c

  Preliminary version 3, based on the final version of the v3-standard, but excluding segments!

- v3

  Full version 3. Including segmentation. This is the default version 3 variant (i.e. if a version 3 messages is to be encoded/decoded and no version3 encoding config is found, then v3 is assumed).

There are two ways to handle the different megaco encoding versions. Either using dynamic version detection (only valid for for incoming messages) or by explicit version setting in the connection info.

For incoming messages:

- Dynamic version detection

  Set the protocol version in the megaco_receive_handle to dynamic (this is the default).
  This works for those codecs that support partial decode of the version, currently text, and ber_bin (megaco_binary_encoder and megaco_ber_bin_encoder).
  This way the decoder will detect which version is used and then use the proper decoder.

- Explicit version

  Explicitly set the actual protocol version in the megaco_receive_handle.
  Start with version 1. When the initial service change has been performed and version 2 has been negotiated, upgrade the megaco_receive_handle of the transport process (control_pid) to version 2. See megaco_tcp and megaco_udp.
  Note that if udp is used, the same transport process could be used for several connections. This could make upgrading impossible.
  For codecs that does not support partial decode of the version, currently megaco_ber_encoder, megaco_per_encoder and megaco_per_bin_encoder, dynamic will revert to version 1.

For outgoing messages:

- Update the connection info protocol_version.

- Override protocol version when sending a message by adding the item {protocol_version, integer()} to the Options. See call or cast.
  Note that this does not effect the messages that are sent autonomously by the stack. They use the protocol_version of the connection info.

### 4.7 Encoder callback functions

The encoder callback interface is defined by the megaco_encoder behaviour, see megaco_encoder.