introduction to bulk smsc n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Introduction to Bulk SMSC PowerPoint Presentation
Download Presentation
Introduction to Bulk SMSC

Loading in 2 Seconds...

play fullscreen
1 / 19

Introduction to Bulk SMSC - PowerPoint PPT Presentation


  • 257 Views
  • Uploaded on

Introduction to Bulk SMSC. IBA, Karachi 2012 -03-24. SMSC. What is SMS and SMS-C ? Types of SMS: MO – MT MO – AT AO – MT AO – AT Originally, All SMS Gateways were designed for MO – MT traffic . Later, AO – MT and MO – AT SMS were introduced

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Introduction to Bulk SMSC' - conley


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
introduction to bulk smsc

Introduction to Bulk SMSC

IBA, Karachi

2012-03-24

slide2
SMSC
  • What is SMS and SMS-C?
  • Types of SMS:
    • MO – MT
    • MO – AT
    • AO – MT
    • AO – AT
  • Originally, All SMS Gateways were designed for MO – MT traffic.
  • Later, AO – MT and MO – AT SMS were introduced
  • Standards used for Application interface include:
    • SMPP: More widely used and acknowledged, supported by Mobile Arts
    • CIMD: Nokia SMSC specific, supported by Mobile Arts
  • Bulk SMSC mainly focuses on AO – MT SMS for advertisement.
  • All SMS flows to follow in next slides
sms flow mo mt
SMS Flow-MO – MT
  • Normal GSM Network

IN

3. AC, Continue

5. ACR

2. IDP

8. MT-FSM

SMSC

4. FSM

MSC-B

7. SRI-Resp

6. SRI

MSC-A

9 MT-SMS

HLR

1- MO SMS

B-Party

A-Party

sms flow mo app terminated
SMS Flow-MO-App Terminated
  • Normal GSM NW

IN

3. AC, Continue

5. ACR

6. MT-FSM

SMSC

2. IDP

App Router

4. FSM

MSC-A

7

1

Application

B-Party

A-Party

sms flow app originated mt
SMS Flow-App Originated-MT
  • Normal GSM NW

3.SRI

HLR

4. SRI-Resp

SMSC

2. FSM

App Router

5. MT- FSM

MSC-B

1

6

Application

A-Party

B-Party

mobile arts bulk smsc
Mobile Arts Bulk SMSC
  • Specifically designed to cater SMS based Marketing/Advertisement needs of a Telecom Operator
  • Advantages:
    • Complete offload of Legacy SMSC for advertisement traffic
    • Very user friendly interface for campaign management
    • Distribution List Management
    • No Connection/Capacity Utilization of Legacy SMSC
    • SMPP based connections to 3rd Party Advertisers
slide7

SMSC Solution

Bulk Messaging

Web Clients

3rd Party CP / Advertisers

B-SMSC Solution

MEWS

SMSC

solution overview

SMPP Client

Bulk MessagingWeb Client

Solution Overview

web

SMPP

  • Salient Features:
    • MEWS: Message Enabler Web Server
    • SMPP: Short Message Peer to Peer
    • OAM: Operation and Maintenance
    • Distribution List Handling
    • Campaign Management
    • Report/Monitoring

Bulk Messaging

Web Server (MEWS)

SMPP Server

CampaignManagement

DistributionList Handling

Reporting/Monitoring

SMS

Delivery Engine

OAM

main components

SS7

SS7

HLR

MSC

GERAN/UTRAN

mobile

features
Features
  • Distribution List Management for SMS
    • This includes distribution lists of the following types:
    • DL_Type = MSISDN_only (default): exactly the same message will be sent to all MSISDNs
    • DL_Type = MSISDN_and_message: the entire message text is explicitly defined for each MSISDN (non-text content is identical for all MSISDNs)
    • DL_Type = MSISDN_and_fields: a common text template (common for all MSISDNs) is defined for the DL and the template can include 1 or several fields that shall be explicitly defined for each MSISDN. Thus, the text string(s) to be inserted in the field(s) of the template are defined explicitly for each MSISDN in the DL (non-text content is identical for all MSISDNs)
features1
Features
  • Campaign Management for SMS
    • This includes:
      • Naming of campaign
      • Scheduling of Campaign (time-based and campaign-based scheduling)
      • Manual start of campaign
      • Manual cancel of campaign
      • Manual Suspend and Resume of campaign
      • Automatic Suspend during defined time intervals (e.g. nightly)
  • Overall Report for all SMS Campaigns
    • This includes the following statistics:
      • Number of campaigns in state “Initiated”
      • Number of campaigns in state “Ready”
      • Number of campaigns in state “Cancelled before ready”
      • Number of campaigns in state “Validity_period expired”
      • Number of campaigns in state “Cancelled before validity_period expired”
    • The Overall Report for all Campaigns can be retrieved at any time.
features2
Features
  • Campaign-Specific Summary Report for B-SMS
    • The Campaign-specific Summary Report can be retrieved in any state of a Campaign
    • The campaign-specific summary report shall contain the following information:
      • Campaign Name
      • Message id
      • List name
      • Message content
      • Start date
      • End date
      • Number of customers (number of unique MSISDNs in the list)
      • Number of successful SMS deliveries
      • Number of unsuccessful SMS deliveries
      • Campaign state (initiated, ready, cancelled before ready, validity period expired, cancelled before validity period expired)
    • The Campaign-specific Summary Report can only be deleted when a Campaign has ended
features3
Features
  • Campaign-Specific Detailed Report for B-SMS
    • The local MEWS user can request Delivery Receipt for any campaign
    • The Campaign-specific Detailed Report contains six lists:
      • List of MSISDNs to whom the SMS was delivered successfully
      • List of MSISDNs to whom the SMS was delivered unsuccessfully, with reason
complete campaign flow operator initiated
Complete Campaign Flow(Operator Initiated)
  • Step 1:
    • Marketing decides to start promoting a new service
  • Step 2:
    • Marketing requests Business Intelligence to provide list of MSISDN (Distribution List) for specific ARPU segment of subscriber base
  • Step 3:
    • Marketing decides on the exact text to be sent to subscriber
  • Step 4:
    • Marketing using the MEWS interface uploads the new Distribution list to the system
  • Step 5:
    • Marketing using the MEWS interface submits the campaign to Bulk SMSC
  • Step 6:
    • Marketing can extract periodic campaign status any time
    • Complete report available after completion of Campaign.