Jataayu MMLG

Overview

 The MML Gateway shall be used to translate HLR

provisioning requests from one format to another format
in a mobile environment.

 The MML Gateway shall be used to interface between

provisioning clients and provisioning systems from two
different vendors.
 Overview

 The provisioning clients interface using an MML protocol

– a simple text-based attribute-value protocol that
specifies a command along with the parameters to be
used.
 The provisioning systems interface using CORBA and
LDAP. The MML Gateway shall transform MML commands
to CORBA/LDAP and vice-versa.
 Overview

 The components that constitute the MML Gateway are as

follows.
 1.MML Gateway
 2.OMC Manager
 MML Gateway is implemented as multi-threaded network
server. The OMC manager is implemented using CGI’s.
A front end for the same shall be developed using a
simple scripting language, PHP.
 Features

The Jataayu MMLG includes the following features:

 MML Gateway shall support all commands in Erission JPA

versions 5.1.

 MML Gateway translates all MML commands into

equivalent eSM work order format.

 MML Gateway sends all work orders to eSM server.

 Features

 MML Gateway translates the response into MML format

and sends it back to MML Client.

 MML Gateway supports batch process.

 MML Query operations shall process through DG.

 Features

 MMLG supports OMC Manager

 MMLG supports Clustered architecture support

 MMLG uses a local MY SQL server database

MMLG Architecture
 MMLG Architecture
Network Listener:

Single thread listens on the specified IP interface

and port.
The requests from the MML client stored into MML
Translator work queue.
 MMLG Architecture

 Translator:

 MML Translator interfaces with Network listener using

work queue thread model.

 MML Translator interfaces with Message dispatcher using

work queue thread model.
 MMLG Architecture

 Message Dispatcher:
 Message Dispatcher interfaces with MML Translator using
work queue thread model.
 Message Dispatcher interfaces with CORBA client using
function calls.
 Message Dispatcher interfaces with LDAP client using
function calls.
 Message Dispatcher interfaces with Response Generator
using function calls.
 MMLG Architecture

 LDAP Client:
 Read the message from the dispatcher.

 Generate LDAP query request.

 Sends the LDAP query request to eSM Data Grid.

 Receive the response from eSM Data Grid.

 Stores the response in Response Generator queue.

 MMLG Architecture
 COBRA Client:

 Read the message from the dispatcher.

 Generate CORBA work order request.

 Sends the work order to eSM CORBA server.

 Receives the response from eSM CORBA server.

 Stores the response in Response Generator queue.

 MMLG Architecture

 Response generator:

 Response Generator interfaces with LDAP client using

work queues.

 Response Generator interfaces with CORBA Server using

work queues.

 Response Generator interfaces with MML Client using

MML protocol.