02 Architecture

air’n’gine media architecture

Overview air’n’gine media architecture  air’n’gine media component details  Third-party software  Summary 

Architecture overview

Framework

MTA SMTP

MM4

Process Manager

SMS Adaptor Module

air’n’able text

Message Routing Engine

Multimedia Message Manager airmanager

Message Accounting

SMPP

Call Detail Record

Log Monitor

MM1 Adaptor Module

WAP HTTP

Handset

air’n’gine media components 

Process Manager



Call Display Recorder (CDR)



Framework



Oracle Database (DB)



Message Routing Engine (MRE)



OAMP MIBs/Alarms/Traps



Multimedia Message Manager (MMM Repository)



Log Monitor



Message Accounting and Statistics (MAS)



airmanager



SMPP Adaptor Module (SMPPAM)



MM1 Adaptor Module (MM1AM)



MM4 Adapter Module (MM4AM)

Framework & process manager (FWK/PM) Framework  The framework monitors the components of the system to ensure that they are healthy using a heartbeat mechanism. It also notifies components of the failure of components that they use.  Process manager  The process manager is responsible for ensuring that all the required air’n’gine processes are up and running. 

Message routing engine (MRE) MRE is the message routing engine  MRE is responsible for:  Determining which adapter module to send a message to based on content type and range of addresses  Fanning out multiple recipient messages 

Multimedia message manager (MMM) Provides the message repository for the system  Stores the message bodies and the message headers  Caches messages and writes the messages asynchronously to persistent storage 

SMPP adapter module (SMPPAM) The adapter module supporting the SMPP and PAP protocols  Generates the SIR (Session Initiation Request)  Can interact with multiple SMSCs 

MM1 adapter module (MM1AM) The adapter module responsible for interacting with the handsets  Receives Mobile Originated (MO) requests  Processes Mobile Terminated (MT) Retrieval requests  Invokes Transcoding engine when required 

MM1 immediate retrieval Target MMS Proxy-Relay

MM Originator

Target MMS Client

Interactions occurring beyond MMS M are not in this document's scope

M-Not ificatio n.in

d

ET.req G P T HT WSP/

M-retr ieve.c onf

Interactions occurring beyond MMS M are not in this document's scope

ind Resp. y if t o M-N

MM1 delayed retrieval MM Originator

Target MMS Proxy-Relay

Interactions occurring beyond MMS M are not in this document's scope

Target MMS Client

M-Noti ficatio n.in ifyRe M-Not

d

sp.ind

Time Passes T.req TP GE T H / P WS

M-retr ie

Interactions occurring beyond MMS M are not in this document's scope

ve.con f

ge.ind owled n k c A M-

MM4 adaptor module (MM4AM) Interfaces with an MMSC via MM4  Can be configured as an MM3 (email) adapter (egress only)  Connects either to a single MTA or directly to an MMSC  MM3 egress will convert MO messages into HTML emails 

Call detail recorder (CDR) The CDR component is responsible for storing Call Detail Records  CDRs are  Stored in binary format  Rotated based on time  Binary CDRs can be converted to text using a utility 

Oracle database Oracle Enterprise Edition 9.2.1  Used for storing CDRs in the MAS database  Used to store User Agent Profiles for handsets 

Operations, administration & maintenance (OAM) Each air’n’gine media component generates various SNMP Traps and Alarms  Each component maintains various operational (OAM) values accessed via SNMP GET commands  The OAM values are used to generate the System Performance graphs  The documented MIB allows the customer to integrate this data in to their preferred OAM tool, e.g. HP OpenView 

Log monitor Monitors the amount of free space for logs and CDRs  Rotates log files based on size and time  Performs housekeeping on old log files, e.g. deletion and compression 

Message accounting & statistics (MAS) MAS consists of data storage and data querying  Data storage:  CDRs are loaded into an Oracle database  Older CDR data is removed periodically  Data querying:  Allows searches of the message history based on various criteria 

Third-party software 

Round Robin Database (RRD)  Open-source project  Polls all components for relevant OAM counters at regular (5 min) intervals  Stores data in custom database  Generates graphs at regular (5 min) intervals  Stores data for a maximum configured time (31 days) and then overwrites oldest data, so maintenance free

Summary air’n’gine media architecture is comprised of a core (MRE + MMM) and a number of protocol adapter modules (MM1, MM4, SMPP)  The core is responsible for routing and storage of messages  The MM1 Adapter Module (MM1AM) is responsible for handset interactions (MO & MT)  The MM4 Adapter Module (MM4AM) is responsible for delivering outgoing email  The SMPP Adapter Module (SMPPAM) is responsible for delivering the SIR to the handset via an SMSC  Oracle is used to store MAS records, and Handset Profiles  SNMP is used to generate Alarms and store operational values  Logs are managed and monitored by the Log Monitor  airmanager is used to manage and configure the system 