msp v3.12 product description

EMEA Empower Interactive Building 10 Chiswick Park 566 Chiswick High Road London W4 5YB UK Tel: +44 (0)20 8987 5100 Fax: +44 (0)20 8987 5101 Email: [email protected] www.eigroup.com

ASIA PACIFIC Empower Interactive Suite 20.3, 20th Floor, Menara IGB, Mid Valley City, Lingkaran Syed Putra 59200 Kuala Lumpur Malaysia Tel: +603 22872876 Fax: +603 22877908

© Empower Interactive Group Ltd

Messaging Service Platform Release 3.12 Product Description

MSP PD PRODMAN_MSP-3.12_PD_1.6 9-November-2006

© 2006 Empower Interactive Group Ltd. All rights reserved. All other trademarks and copyrights referred to herein are the property of their respective holders. No part of this documentation may be reproduced in any form or by any means or used to take any derivative work, without written permission from Empower Interactive Group Ltd. This document is subject to change without prior notice. Whilst Empower Interactive Group Ltd makes every effort to ensure the accuracy and reliability of the information contained in this document, its employees and agents will not be responsible for any loss, however arising, from the use of, or reliance on this information.

Legal Notice: Patents for the Messaging Service Platform have been applied for in a Patent Cooperation Treaty member country.

PRODMAN_MSP-3.12_PD_1.6

DOCUMENT CONTROL

Document ID : PRODMAN_MSP-3.12_PD

Version : 1.6

Version date : 9-November-2006

Period of validity : 19-June-2006 to 01-May-2007

Status : Released

Distribution :

Author :

..............................................

John Hurley

MSP Product Manager

Date: .............................

Approved

(omit if not required)

:

..............................................

Mike Manna

VP of Business Development & Product Management

Date: .............................

PRODMAN_MSP-3.12_PD_1.6 i

Preface This document describes the features and functionality of release 3.12 of Empower Interactive’s Messaging Service Platform (MSP).

Purpose of this Document The purpose of this document is to support the Empower Sales team in their responses to customers and provide prospective customers with information regarding the features and functions of MSP 3.12.

Scope of this Document This document provides an overview of the features and functions of the MSP system without providing technical detail as to the operation of the system. For detailed information about operations procedure, refer to the technical user documentation.

This document does not describe the licensing or pricing of individual features.

Revision History The following table lists all previous versions of this document and the reasons for issuing each new edition:

Version Saved By Date Reason

0.1 John Hurley 24/May/2006 Draft for sales training.

1.0 John Hurley 09/June/2006 Released following review.

1.1 John Hurley 19/June/2006 Additional Diagrams

1.2 John Hurley 10/Aug/2006 Addition of supported versions of UCP Protocol

Update of Time Ten version

1.3 John Hurley 29/Aug/2006 Added licensing disclaimer to preface.

1.4 John Hurley 14/Sept/2006 Additional examples of standard filter types.

1.5 John Hurley 14/Oct/2006 New diagrams and information about platform options.

1.6 John Hurley 9/Nov/2006 Added App-to-App routing.

References The following table lists documents that are referenced in this document:

Reference Document Title Version Date

[1] MSP 3 Operations Guide 3.12 V1.0 15/08/06

[2] MSP 3 SMPP PICS 3.12 V1.0 04/09/2006

[3] MSP 3 UCP/EMI PICS 3.12 V1.0 28/08/2006

[4] MSP 3 CIMD2 PICS 3.12 V1.0 10/09/2006

[5] MSP 3 MM7 PICS 3.12 V1.0 12/09/2006

[6] MSP 3 EAIF PICS 3.12 V1.0 04/08/2006

PRODMAN_MSP-3.12_PD_1.6 ii

CONTENTS

SECTION 1: MSP Overview............................................................................................. 3 1.1 MSP in the Mobile Operator’s Network.......................................................................... 3 SECTION 2: MSP Product Benefits.................................................................................. 4 2.1 Benefits for Mobile Operators...................................................................................... 4 2.2 Benefits for Application Developers.............................................................................. 4 SECTION 3: Overview of MSP Functionality ................................................................... 5 3.1 Summary of Key Features .......................................................................................... 5 3.2 Connectivity to Core Messaging Infrastructure............................................................... 6 3.3 Interfaces for Application Connectivity ......................................................................... 7 3.4 Authentication Mechanisms ........................................................................................ 8 3.4.1 MSP Client Proxy....................................................................................................... 8 3.5 Messaging Persistence ............................................................................................... 9 3.6 Message Modes ........................................................................................................ 9 3.6.1 Transactional Mode ................................................................................................... 9 3.6.2 Store-and-Forward Mode............................................................................................ 9 3.7 Message Buffering....................................................................................................10 3.8 Configurable Messaging Workflow...............................................................................10 3.9 Protecting Mobile Subscribers from Spam Messaging .....................................................12 3.10 Supported Message Formats......................................................................................12 3.11 Application to Application Routing...............................................................................12 3.12 Web-based Management GUI.....................................................................................13 3.13 Administration and Monitoring ...................................................................................13 3.14 Premium Service Validation .......................................................................................14 3.15 Prepaid Charging Triggers .........................................................................................15 3.16 Retry for Mobile Terminated SMS ...............................................................................16 3.17 Flexible Architecture .................................................................................................18 3.18 Platform Deployment Options ....................................................................................19 3.19 Resilient Configurations ............................................................................................20 3.19.1 MSP Gateway for SMS ..............................................................................................20 3.19.2 MSP Gateway for MMS ..............................................................................................21

PRODMAN_MSP-3.12_PD_1.6 3

SECTION 1: MSP Overview

Messaging Service Platform (MSP) is Empower Interactive’s flag-ship product for the delivery of reliable and secure mobile data services.

With the burgeoning growth of application messaging outstripping the capacity and capabilities of existing equipment, mobile operators struggle with increasingly complex configurations and run the risk of revenue loss, brand damage and increased subscriber churn.

Empower’s MSP addresses these issues by:

• Enabling mobile operators to efficiently manage the unique demands of application messaging

• Supporting multiple messaging technologies (SMS & MMS) in a protocol agnostic way

• Easing the deployment of new application-based messaging services

1.1 MSP in the Mobile Operator’s Network

MSP is an intelligent message storage and routing system, located between the SMSC/MMSC and the messaging applications of the mobile operator, content providers, enterprise clients or application developers. It enables operators and service providers to:

• Simplify access to the network for applications and content providers

• Perform protocol conversion between various applications and elements in the core network

• Securely connect applications quickly and easily using standard interfaces

• Intercept and control two-way SMS and MMS application traffic

• Protect the core messaging infrastructure to ensure quality of service

MSP’s functionality is constantly evolving to help operators keep pace with the increasing complexity and sophistication of technology and the market for Mobile Messaging services.

Figure 1: MSP's Position in a Mobile Operator's Network

Note: For more details regarding MSP and other Empower products, please email [email protected] .


SECTION 2: MSP Product Benefits

MSP provides many benefits both for Mobile Network Operators and for external content providers whose applications connect to MSP.

2.1 Benefits for Mobile Operators

• Optimises use of the existing messaging infrastructure

• Eases network configuration & management

• Provides a central interface for management

• Load balances message traffic across available equipment

• Protects Quality of Service (QoS)

• Improves flexibility for routing & filtering messages

• Maximizes Revenue Opportunities and Minimizes Cost of Ownership

• Provides a single point of management for two-way SMS and MMS applications to the mobile messaging network

• Provides a single service provisioning point for a network operator to manage the applications of all service providers

• Reduces the time to market and launch costs by providing validation and testing environment for new services without jeopardising existing revenue streams

2.2 Benefits for Application Developers

• Supports many more protocols than typical SMSCs or MMSCs

• Enables quick conversion of Web and Email applications to SMS services

• Stores and retries submission to SMSC/MMSC

• Simplifies access to the Mobile network for Application and Content providers

• Provides interfaces for many common IT protocols, removing the need for applications to be written using telecommunication protocols


SECTION 3: Overview of MSP Functionality

MSP is deployed on an open, standards-based architecture and future proofed to meet the operator’s evolving requirements for application-based messaging. MSP stores and buffers both Application-to-Mobile and Mobile-to-Application SMS and MMS messages and determines the most appropriate delivery strategy using a variety of routing and throttling algorithms.

The MSP also provides a single point of contact for content and application providers supporting a wide range of protocols such as HTTP, SOAP, SMPP, UCP and MM7. The unique framework provides a single point of management and resilient messaging engine for external Applications Providers.

3.1 Summary of Key Features

Table 1 provides a summary of MSP 3 key features with references to sections that provide more detail:

Feature Reference

Flexible architecture to enable easy addition of optional features Section 3.17

Connectivity to the SMSCs & MMSCs of major vendors Section 3.2

Wide range of interfaces for application connectivity Section 3.3

Support for various authentication mechanisms Section 3.4

Message Persistence (RDBMS or flat file) Section 3.5

Support for Store & Forward and Transactional Modes on a system-wide or application basis Section 3.6

Load-balancing across multiple SMSCs/MMSCs Section 3.2

Flooding Protection for SMSCs & MMSCs Section 3.2

Aliasing of Subscriber MSISDNs for Spam Protection Section 3.9

Configurable Throttling rates for different applications Section 3.2 & 3.8

Configurable messaging workflow based on message attributes (eg. keyword routing) Section 3.8

API for custom-written filter types to expand influence on message flow Section 3.8

Full international language support for messages (including Chinese, Arabic etc.) Section 3.10

Application to Application (AO-AT) Routing Section 3.11

Retry for Mobile Terminated messages Section 3.16

Real-time Triggers for Prepaid Charging (Synchronous/Asynchronous) Section 3.15

Role based WEB Management GUI for Administration, Provisioning and Configuration Section 3.12

Resilient Service Section 3.19

Table 1: Summary of Key Features


3.2 Connectivity to Core Messaging Infrastructure

MSP’s interfaces have been designed in accordance with open standards so that operators can easily integrate MSP with their existing messaging infrastructure (SMSC/MMSC/PPG) in the core network.

MSP has been integrated and is compatible with all major SMSC vendors (CMG, Logica, Nokia, SEMA, Comverse and Ericsson) and a selection of MMSC vendors (Nokia and Ericsson) over both standard and customized messaging protocols.

The so-called “channel” connections between MSP and SMSCs or MMSCs can be configured to protect the SMSC/MMSC from flooding by application messaging. By grouping connections together into Channel Groups, MSP can dynamically load-balance traffic across the SMSCs or MMSCs in the group.

Each channel group automatically load balances across the channels in its group to ensure that channel capacity is optimized. MSP records the Channel Group to which it submits every message and will automatically attempt to direct subsequent commands relating to that message (cancel, replace) to the same Channel Group.

Table 2 shows the standard protocols supported by the MSP 3 for communications with operators' core messaging systems.

Protocol Message Type Version Support connections with

EMI/UCP SMS 3.5, 4.0, 4.6 CMG SMSCs

SMPP SMS 3.3, 3.4 Logica, Comverse etc. SMSCs

CIMD2 SMS 3.0, 4.0 Nokia SMSCs

OIS SMS SMS2000 7.4G SEMA SMSCs

EAIF MMS 3.0 Nokia MMSCs

MM7 MMS TS23.140 R5 3GPP

Table 2: Standard Protocols Supported by MSP for Connections to Mobile Operators

Table 3 shows customer- or vendor-specific protocol implementation that MSP supports for operators with certain messaging systems.

Protocol Message Type Version Support connections with

MAM SMS N/A Omnitel SMSC

PSMC (PAM) SMS N/A Telefonica SMSC

XML SMS/MMS RPC T-mobile ATK platform

E/// MM7 MMS R4.0 Ericsson MMSCs

Table 3: Custom Protocols Supported by MSP for Connections to Mobile Operators


3.3 Interfaces for Application Connectivity

To provide maximum flexibility for external content providers, MSP provides a wide range of protocols and mechanisms for existing applications and enterprise systems to be enabled for two-way messaging. Application and Content providers can connect directly to MSP server via the public Internet, leased lines or dial-up connections using a variety of industry standard protocols such as SMPP, UCP, CIMD2, HTTP, SOAP, EAIF and MM7.

Alternatively, content providers can deploy the light-weight Client Proxy application within their corporate network and utilize MSP’s Java RMI, JDBC, SOAP, HTTP, CORBA, EAIF, MM7, SMTP, POP3, SMPP, UCP and CIMD2 interfaces. The proxy application connects to the MSP server of a mobile operator using a proprietary protocol (RDP), allowing secure integration with corporate email, database, ERP, CRM systems and bespoke applications.

Table 4 shows the application protocols supported by the MSP 3.

Protocol Message Type Version Interface Variants

EMI/UCP SMS 3.5, 4.0, 4.6 SLA and MLA interfaces

SMPP SMS 3.3, 3.4 Trusted, Authenticating, Authenticating & Encrypted (SSL)

CIMD2 SMS 3.0, 4.0 Trusted and Authenticating

EAIF MMS 3.0 Authenticating & Encrypted (HTTPS)

MM7 MMS TS23.140 R5 Authenticating & Encrypted (HTTPS)

RDP SMS Empower Proprietary Authenticating, Authenticating & Encrypted (SSL) for MSP Client Proxy

RMI SMS N/A Authenticating, Authenticating & Encrypted (SSL) or via MSP Client Proxy

HTTP SMS 1.0 and 1.1 Authenticating & Encrypted (SSL)

SOAP SMS Over HTTP 1.0 or 1.1 Authenticating, Authenticating & Encrypted (HTTPS)

SMTP SMS and MMS N/A Trusted or via MSP Client Proxy

POP3 SMS N/A Trusted or via MSP Client Proxy

Lotus Notes SMS N/A Trusted or via MSP Client Proxy

JDBC SMS N/A Trusted or via MSP Client Proxy

CORBA SMS N/A Trusted or via MSP Client Proxy

Note: The term “Trusted” refers to a connection that is not authenticated by a password

Table 4: Protocols MSP Supports for Connections to Value Added Messaging Services


3.4 Authentication Mechanisms

MSP provides a range of security and authentication mechanisms for external applications, depending on the connection protocol used and on whether the application connects directly to the MSP server or to the client proxy. MSP can authenticate application connections using one or more of the following criteria:

• Account id & Password

• Source IP address (and optionally also port)

• SSL Key

3.4.1 MSP Client Proxy

Empower Interactive recognises the need for a cost-efficient and flexible model for security and authentication. The MSP Client Proxy can be deployed either in the operator’s network or in that of the content provider to perform the following functions:

• Authenticate for applications or servers that do not normally authenticate (eg. Mail Servers or Databases)

• Localise transactions on a Database rather than risk integrity with update across multiple networks

• Concentrate application traffic to reduce the number of connections to the MSP Server

• Provide a secure interface (RDP) for transferring valuable SMS transaction data between networks

Figure 2: MSP Client Proxy Providing a Dedicated Secure Connection to MSP Server

The MSP Client Proxy can reduce solution delivery time and the need for bespoke in house development. Transfer times are also reduced, as there is no need for a costly DMZ based proxy layer. Consequently, a secure yet economic connection can be achieved using public networks, such as the internet, if desired.


3.5 Messaging Persistence

MSP stores messages on disk (persistence) while processing them. It is possible for MSP to use flat files for message persistence in low volume deployments but more usually persistence managed by an RDBMS (TimesTen for SMS and Oracle for MMS).

3.6 Message Modes

MSP provides support for two modes of messaging, which can be applied either on a system-wide or application basis:

• Transactional Mode

• Store & Forward Mode

3.6.1 Transactional Mode

In this mode MSP supports messaging between applications and SMSCs in such a way that neither is aware of the MSP mediating their communication. In transactional mode MSP does not acknowledge messaging operations to the source until the destination (SMSC, MMSC or application) has acknowledged the PDUs to MSP.

MSP can be configured to perform manipulation of certain message fields (such as timestamps) to hide its involvement in transactions.

Figure 3: Example Message Flows when MSP uses Transactional Mode

3.6.2 Store-and-Forward Mode

MSP acknowledges receipt of messages and takes responsibility for forwarding them to their destinations (AT or MT). Applications must use this mode to enable MSP to perform retry for their mobile-terminated messages.

Figure 4: Example Message Flows when MSP uses Store and Forward Mode

MSP can simultaneously support applications that use different modes of messaging; some using transactional mode and others store-and-forward mode.


3.7 Message Buffering

MSP uses multiple parallel buffers or “queues” for both MT and MO traffic to ensure that each message is securely stored and routed to its destination in an optimal manner.

MT messages can be stored either in the specific queue of a Channel or Channel group or in the catchall “unrouted” queue.

One or more queues can be defined for each application, into which MO messages can be written until the application connects to receive them. In this way, a poorly performing application will not affect the rate at which messages are delivered to a separate higher speed application. All MO and MT message queues are resilient, with either file system or database persistence, and have configurable volume limits.

3.8 Configurable Messaging Workflow

The default routing of AO-MT messages within MSP is determined by the number of available channel groups and channels and by the throughput limits configured for individual channels. The default routing of MO-AT messages is towards the inbound queue whose mapping matches the destination short code.

By configuring “filters” in MSP. The operator can influence the default routing of messages (AO and AT).

Figure 5: How MSP Filters act on Inbound (AT) and Outbound (AO) Messages

Empower provides a comprehensive set of filter types, which customers can configure and apply to their specific needs to route, modify or block messages based on their attributes. Additionally, filters can be used as triggers to interact with other systems (MCP, CBS etc.). MSP includes 47 standard filter types for the following purposes:

• Blocking Messages (blacklisting addresses, blocking content)

• Throttling Applications (slowing submission)

• Modifying Messages (addresses (including aliasing), tariff codes, SC timestamp etc.)

• Routing Messages (AT, AO, in-sequence)

• Logging Statistics & Properties

Table 5 on page 11 shows a selection of standard filter types provided in MSP 3.12.


Filter Type Description

AddressReplacer Facilitates the replacement of any string within either the source or destination address with another string, e.g. replace +12345xxxxxx with +12399xxxx

AllowedDaysOfWeek Only allows submission of messages to or from a specific account on the configured days (e.g. Mon-Fri)

AllowedTimeOfDay Only allows submission of messages to or from specific accounts on during the configured times (e.g. 9am-5pm)

MMSNumberofRecipients Limits the number of recipients specific Accounts, which the filter applies to, can include in message submissions

Time-period Based

Throttling

Enables the Operator to configure a standard throttle rate for an account and an alternate throttle rate to apply in a specific time period.

SetTarrifCode Enables the insertion or overwrite of a tariff code in the AO messages of a specific account.

PercentageRouting Enables messages submitted by a particular account to be load balanced across channel groups according to configured percentages.

SetAnyMessageProperty Enables MSP to set the value of any of the standard fields of a SMS message.

MetadataSet Enables additional information to be stored with the message in MSP’s storage. Such metadata can be either for use by MSP or by the systems or applications to which it sends the message.

GroupAndChannelRouting Routes AO messages from an account to a specific channel of a specific channel group.

MMSNumberOfRecipients Limits the number of recipients specific Accounts, which the filter applies to, can include in message submissions

MMSSizeBlocking Limits the size of MMS messages on a Global or Account basis

KeyWordCheck Facilitates the routing of specific messages to specific Accounts based on the keyword, hence allowing an Operator to share Short codes across a number of Accounts.

Blacklist Blocks submissions to or from specific subscribers if their MSISDNs are listed in an associated Blacklist

Table 5: Examples of Standard Filter Types in MSP 3.12

Filters can be applied to messages with respect to their scope and direction. They can act on all AO messages or all AT messages or they can act on the AO or AT messages of particular applications.

New filter types can be added to the system and deployed without interruption of service.

If a customer’s needs cannot be met by the standard set of filter types, they can either

• request that Empower provide a custom filter type (preferred option)

• write their own filter types in Java using the APIs published by Empower

Table 6 shows some of custom filter types that have been provided in releases of MSP 3.

Filter Type Description

KeyWordCheck Facilitates the routing of specific messages to specific Accounts based on the keyword, hence allowing an Operator to share Short codes across a number of Accounts.

ConcatMsgRoute Ensures that all components of a concatenated message are routed to the same Channel Group, i.e. SMSC.

KeyWordMessageLimit Will only allow a certain number of messages containing a particular keyword to be sent e.g. you can send 50 messages containing the word 'Vote', after that any messages containing the word 'Vote' will be rejected, although other messages can still be sent

AutoUpdateBlacklist Facilitates the ability for subscribers to add or remove themselves from a specific blacklist by submitting a message to a specific destination and keyword.

Table 6: Examples of Custom Filter Types provided in MSP 3

For a full list of all filters types and their associated functionality, please refer to the MSP Operations Guide

For more information about custom filter development, contact [email protected].


3.9 Protecting Mobile Subscribers from Spam Messaging

MSP’s aliasing feature is designed to help mobile operators protect their subscribers from receiving unsolicited messages. Some unscrupulous content providers, retain a database MSISDNs of all subscribers that have used their services, which they target in subsequent campaigns or trade to other content providers.

MSP’s aliasing and de-aliasing filter types ensure that mobile subscribers’ true MSISDNs are not exposed to messaging applications but are passed in a scrambled format. Applications can respond to requests using the aliased mobile address and also use it for subsequent messages.

Figure 6: MSP Obscuring Subscriber MSISDNs from Messaging Applications

Once the aliasing filter is applied to a Content Provider’s account as in inbound filter, MSP references a special algorithm to generate and aliased form of the source address of MO messages. The de-aliasing filter operates on messages originating at the application.

At any time the MSP administrator can modify the alias version of the filters, which makes previously generated aliases invalid. In this way the operator can control the time period for which the content provider can send messages to a mobile subscriber.

For more information about aliasing and Spam protection, contact [email protected]

3.10 Supported Message Formats

MSP uses Unicode to store messages in its internal storage but can accept messages from applications in various formats before translating them into Unicode. Each channel and client interface can be configured to handle multiple format translations for incoming and outgoing messages taking account of the each message’s protocol, character set and data coding scheme.

Because MSP uses Unicode as its internal format, it supports the storage and transfer of any character that can be rendered in Unicode. This includes Chinese and Arabic characters. MSP’s content-based filters can also be configured to act on text strings entered in Unicode.

3.11 Application to Application Routing

A new system property enables application-to-application routing. When enabled, if an application submits a message with a destination address that matches the mapping of an inbound queue, MSP routes the message to that queue via a special channel group.


3.12 Web-based Management GUI

MSP includes a web-based Management GUI to enable the administration, provisioning and configuration of the System. Access to the system is password controlled and the level of access is determined by the User Group privileges of the user logging in. All operations performed using the Management UI are logged in a separate log file on the system to provide a trail of configuration on the system.

Figure 7: The MSP Web Management Interface

3.13 Administration and Monitoring

The management interface allows queues to be monitored, statistics examined and configuration changes to be made accordingly. Ancillary monitoring applications can enable operators to

• view the performance of individual queues/SMSC connections as real-time graphs or for

• log data over extended time periods for more detailed trend analysis.

It is also possible to generate alerts based on configurable conditions using the following mechanisms:

• email alerts

• SNMP v1 traps


3.14 Premium Service Validation

Empower Interactive provides a separately licensed complimentary system, which enables the mobile operator to ensure that certain types of SMS and MMS content are sent only to appropriate subscribers. This feature comprises

• a database of mobile subscribers and details relevant to their use of particular types of messaging services (age, preferences etc.)

• a filter type that triggers lookup of the subscriber database when applied to applications serving content that may be offensive or costly

Figure 8: MSP with the Premium Service Validation Option

Operators can create various classifications of services (eg. adult, sports, news) and record subscribers’ preferences (opt in or out) for each service or services type.

By configuring a subscriber lookup filter and applying it to the accounts used by particular services, the operator can ensure that subscribers receive only content that suits their preferences or age.


3.15 Prepaid Charging Triggers

A separately licensed feature enables MSP to recognise Prepaid subscribers using messaging services and perform a real-time credit checks before delivering premium service messages.

Figure 9: MSP with Charging Trigger Option

For more information contact [email protected].


3.16 Retry for Mobile Terminated SMS

MSP can deliver MT SMS messages via

• SMSCs

• SMS routers (MDP, Telsis, Cisco ITP)

Most MT messages are delivered on the first attempt. If the initial delivery attempt fails an SMSC can retry delivery based on the error returned by the mobile network. Because SMS routers do not store messages, they cannot perform retry on failed messages.

MSP 3.12 includes functionality to perform retry based on MAP errors when it routes messages to SMS routers that cannot perform retry themselves. This provides the following benefits to the operator:

• Reduced use of SMSC store and retry resources

• Improved QoS on the SMSC

• Cost effective solution for delivery of AO-MT and MO-AT messages

Figure 10: MSP Performing MT Retry for a forward-only SMS Router

MSP 3.12 enables the channel to an SMS router to be configured as a “retry channel”, which causes MSP to request delivery notification for all messages it submits on that channel. If a delivery attempt to the mobile network fails, the SMS router sends a delivery report to MSP, containing the reason code for failure.

MSP’s retry behaviour for a given message is determined by the retry profile associated with the originating application’s account in the system.


The administrator can create multiple retry profiles each of which can have a different retry schedule for different network errors.

Figure 11 shows an example of a retry profile being configured via the MSP GUI. The system also has a default retry profile.

Figure 11: Configuring a Retry Profile for MT SMS

When a retry profile is defined and applied to an Account in MSP, it is used to determine the retry behaviour for the MT messages of that accounts applications.

Table 7 shows examples of retry schedules from MSP’s default profile with descriptions of the behaviour of each.

Error Number

Error Name Retry Schedule Description

001 Unknown Subscriber

P Messages are Not retried

027 Absent Subscriber

3*20 Messages are retried every 20 minutes

100 Memory Capacity Exceeded

1, 5, 10, 20,24*60, 480 Messages are retried on the 1st, 5th, 10, 20 minute, then once every hour for 24 hours, then once every 480 minutes (8 hours) until the message expires

Unless a schedule ends with E or P, the last retry configuration in the comma-separated schedule is repeated until the

message validity period expires.

Table 7: Example Retry Schedules from MSPs Default Retry Profile


3.17 Flexible Architecture

MSP is constructed on an open J2EE architecture, which facilitates easy customization and integration. The Java library structure enables easy expansion of functionality without interruption of service. Configuration files enable automation of provisioning and easy migration to new releases.

The core components of the MSP provide the intelligence for the routing and manipulation of messages.

Authentication of connections and protocol translations and are performed by the Client Interface and Channel components.

Figure 12: Architecture of the MSP Server


3.18 Platform Deployment Options

Empower is constantly benchmarking with the latest hardware from a number of hardware vendors to update its shortlist of standard platforms.

New customers will have MSP installed on one of the standard platforms.

Depending on the specific throughput and storage requirements of the customer and the complexity of message processing they require, Empower will propose a solution based on one of the platform specifications described in Table 8.

Platform Option Specification

Value HP DL385G2 2x Dual-Core Opteron 2.6GHz CPUs 4 GB RAM

Performance HP DL585 R02 4x Dual-Core Opteron 2.8GHz CPUs 8GB of DDR SDRAM

Table 8: Standard Platform Options from MSP 3.12

See also Section 3.19 Resilient Configurations on page 20.

Existing customers will be able to upgrade to MSP 3.12 on their existing platforms provided the specification is equivalent to that of a standard favourably with performance benchmarking results.

Depending on the performance impact of any new or optional features chosen, customers may need to upgrade their existing hardware. For more information contact [email protected].


3.19 Resilient Configurations

For redundancy purposes MSP 3.12 systems are deployed in pairs which share a message store and a single license. At any one time only one system has control of the license and processes messages. The second system runs in passive or “stand-by” mode. If for any reason the active system fails, the cluster management software ensures that the license and control switches or “fails over” to the stand-by system.

3.19.1 MSP Gateway for SMS

A fully resilient configuration of MSP for SMS includes the following elements:

• 2 MSP Application Nodes, each running:

o Cluster-management software (e.g. Lifekeeper)

o MSP software

o An in-memory RDBMS (eg. Times Ten)

• Shared Storage Subsystem

The storage subsystem meets the requirements for shared storage between multiple MSP nodes.

This architecture provides features such as:

• Automatic failover from a master to the slave in the event of system failure.

• Single IP address for client connections, enables clients to re-connect following failover

• In-memory RDBMS (Times Ten) for faster storage and retrieval of SMS messages

• Flushing of data from RDBMS to the disk storage array

• Shared high-performance storage array dramatically reducing the failover time.

Figure 13 illustrates a typical SMS MSP deployment.

Figure 13: MSP for SMS: 2-node Cluster Configuration


3.19.2 MSP Gateway for MMS

A fully resilient configuration of MSP for MMS includes the following elements:

• 3 Servers (eg. HP DL385)

o All running cluster-management software (e.g. Lifekeeper)

o 2 running MSP software

o 1 running an RDBMS (eg. Oracle)

• Shared Storage Subsystem

The storage subsystem meets the requirements for shared storage between multiple MSP nodes.

This architecture provides features such as:

• Automatic failover from a master to the slave in the event of system failure.

• Single IP address for client connections, enables clients to re-connect following failover

• Shared high-performance storage array dramatically reducing the failover time.

• Off-platform RDBMS to deal with storage of multimedia messages and attachments

Figure 14 illustrates a typical MMS MSP deployment.

Figure 14: MSP for MMS: 2-node Cluster Configuration


Glossary The following table provides explanations of acronyms and definitions of technical terms used in this document:

Term Definition

Numeric

3GPP 3rd Generation Partnership Project. 3GPP produce globally applicable technical specifications and technical reports for a 3rd Generation Mobile System based on evolved GSM core networks. They also maintain and develop the Global System for Mobile communication (GSM) technical specifications and technical reports. They are responsible for the MMS message specification, which includes the MM7 interface between applications and MMS networks.

A

Account A record provisioned in MSP for the owner of a messaging application. MSP associates each application connection with an Account. Messages sent to or from an application are then associated with the Account. MSP’s authenticating client interfaces can use an Account‘s ID and password to control application connections.

Aliasing Process by which the MSISDNs of mobile subscribers are scrambled when passed in service requests from MSP to messaging applications.

AO Application Originated. SMS or MMS message sent from an application.

AT Application Terminated. SMS message that terminates at an application.

B

Black list A list of banned values. In the context of MSP the values are most usually subscriber telephone numbers. MSP can check the source and/or destination address of a message against the numbers in a blacklist and reject the message if it finds a match. See also white list.

C

Channel A channel encapsulates the connection path between the MSP and a single SMSC or SMS Router using a specific protocol and transport.

Channel Group A collection of one or more channels, which MSP uses as alternative routes for load-balancing message traffic.

CIMD Computer Interface to Message Distribution. An SMSC interface protocol, used by the Nokia 'Artus' SMSC.

Client Interface A client interface encapsulates a connection between the MSP and an application using a protocol.

CORBA Common Object Request Broker Architecture. An architecture and specification for creating, distributing and managing distributed program objects in a network. It allows programs at different locations and developed by different vendors to communicate in a network through an "interface broker."

D

De-Aliasing Reverse process of aliasing whereby MSP translates the aliased destination address sent by an application to the true MSISDN of the recipient.

E

ESME External Short Messaging Entity; a device external to the mobile network that can be used to originate or deliver an SMS message. Typically an ESME is a messaging application program.

EMI/UCP External Machine Interface/Universal Computer Protocol. An SMS application interface protocol, used by the CMG SMSC.

G

Gateway A network point that acts as an entrance to another network.

H

HTTP Hyper Text Transfer Protocol. The Hypertext Transfer Protocol is the set of rules for


exchanging files (text, graphic images, sound, video, and other multimedia files) on the World Wide Web.

J

Java A simple, object-oriented, architecture-neutral, multithreaded programming language designed expressly for use in the distributed environment of the Internet.

JDBC Java Database Connectivity. A standard SQL database access interface for Java that provides uniform access to a wide range of relational databases.

M

MIB Management Information Base. A management information base (MIB) is a formal description of a set of network objects that can be managed using the Simple Network Management Protocol (SNMP)

MIME Multipurpose Internet Mail Extensions. Is an extension of the original Internet email protocol that enables the exchange of different kinds of data files on the Internet: audio, video, images, application programs, as well as the ASCII handled in the original protocol

MM7 A communication protocol between applications and a network that can send MMS messages.

MMS Multimedia Messaging Services. A system that allows pager and short messaging service (SMS) messaging to include graphics, audio or video components.

MO Mobile Originated. An SMS message that originates at a mobile phone.

MMSC Multimedia Messaging Service Centre

MSISDN Mobile Station International ISDN Number. Used to identify a Mobile Station as an ISDN terminal and to route calls to it from any international telecommunications network (PSTN, ISDN, GSM-PLMN).

MSP Messaging Service Platform. An SMS and MMS gateway that provides intelligent routing protocol-conversion, flood protection and load-balancing capabilities for application based messaging traffic in a mobile network.

MT Mobile Terminated. An SMS message that is delivered to a mobile phone.

R

RDP Empower Interactive’s proprietary protocol for communication between MSP Server and the MSP Client Proxy.

S

SME Short Messaging Entity; any device that can be used to originate or deliver an SMS message for example a mobile handset, an SMSC or an application programme.

See also ESME.

SMIL Synchronized Multimedia Integration Language, pronounced "smile". A mark-up language for authoring interactive audio-visual presentations, which integrate streaming audio and video with images, text or any other media type.

SMPP Short Message Peer-to-Peer. Interworking protocol for SMS between SMSC and non-mobile SMEs.

SMS Short Message Service. Teleservice in a digital mobile network that enables text messages up to 160 characters in single byte character sets, 70 characters in double byte character sets, and up to 140 bytes of raw data, to be sent via SS7 signalling channels.

T

TCP/IP Transport Control Protocol / Internet Protocol. A two-layer communications protocol that manages he end-to-end delivery of data across a network. The TCP layer manages the segmentation of a message or file into smaller packets. The IP layer handles the addressing of each packet routing it to its destination, where the TCP layer re-assembles the packets into the original message.

Ticket A unique identifier associated with a single submitted message.

Transactional mode Messaging mode in which MSP transacts with SMSCs, MMSC and applications in such as way as to suggest that it is not involved in the transaction ie.“transparent”.

U

UCP/EMI External Machine Interface/Universal Computer Protocol. An SMS application interface protocol, used by the CMG SMSC.


V

VAS Value Added Service. An application that sends and/or receives messages to provide a service

VASP Value Added Service Provider. The owner of a VAS.

W

White list A list of approved values. In the context of MSP the values are most usually subscriber telephone numbers. MSP can check the source and/or destination address of a message against the numbers in a white list and forward the message if it finds a match. See also black list.

msp v3.12 product description

Documents