sap sms 365, enterprise service€¦ · •content providers connect through a firewall and...

SAP SMS 365, Enterprise Service Platform Overview

© 2013 SAP AG. All rights reserved. 2

Message Types

Mobile Terminated SMS (MT): The delivery of outbound messages from a mobile business application to mobile subscriber handsets Mobile Originated SMS (MO): The

delivery of inbound messages from subscriber handsets to a mobile business application

• Standard/Bulk MT/MO: Subscribers are not charged when receiving an MT or initiating an MO

• Premium MT/MO: Subscribers are charged when receiving an MT or initiating an MO. Charges are paid through mobile telecom operators


Key Components

Components of the enterprise messaging Platform include:

• Content Provider connections Operator connections Routers MT Chain MO Chain Notification Chain Sock_mv server/client


Enterprise Messaging HUB


CP Connection Layer

• Content Providers connect through a firewall and loadbalancer (load balancing does not apply to SMPP or UCP traffic)

• Software listening instances (dedicated or shared) on each port

• Checks for Content Provider source IPs and rejects BIND requests if IPs are not configured with the application


Operator Connections

• Responsible for sending and receiving MTs, MOs, and Notifications

• Other software applications running on the connection servers include: - Retry software – resends MTs based on notification

responses from operators - Notification delay software – verifies mobile notifications

prior to processing - Priority software – manage delivery of messages

according to their pre-assigned priority


MT Chain

• Libsendsms: Converts messages to a Sendxms format; determines data coding scheme to use for connection base, and merges virtual SMSCID into physical connections

• Order ID Server: Issues unique IDs to each MT request

• GN Number Lookup: Interfaces with service providers and internal MNP database to retrieve updated numbering plans

• Additional features: – OCG connector: Manages billing for PSMS flow – DeliveryTimeWindow: Controls delivery of messages

within specified time window – VolumeControl: Prepay mechanism and hack control


MT Chain Workflow

1. Content Providers send messages to connections and message parameters are verified

2. Messages are sent to MT Router and processed by the router and its subcomponents:

- Checks MSISDN and assigns a destination operator

- Adds billing information - Logs everything into database for

billing and tracking - Volume control - Delivery time windows - OCG calls - Subscription manager

3. Message is sent to operator connection 4. Message is delivered to operator SMSC

(and retried in case of failure for selected services)

5. Message is sent to customer


MO Chain

• Operators receive MO traffic from subscribers, and the enterprise messaging hub then delivers it to Content Providers

• MO traffic is received by direct connection to operator platform

• HTTPSMO/SMTPMO: Sends MO messages to CPs • MO Notification: Processes MO files and updates their

statuses in database • OCG Billing: Manages PSMS MO calls to operators

billing platforms


MO Chain Workflow

1. Customer sends a message to an operator

2. Message is received from the operator by the operator connection

3. Message is forwarded to MO Router and processed:

- Verifies a configured customer for the pair connection and short code

- Verifies a configured customer for the keyword, short code, and connection

4. Message is delivered to Content Provider connection

5. Message is delivered to the Content Provider (and retried in case of failure)


Notification Chain

• Notifications are delivered to Content Providers regarding the status of their messages

• Types of notifications include: - SAP Mobile Services Notification: Enterptrise

messaging hub has successfully processed the message

- SMSC Notification: Message has been sent and successfully acknowledged by the operator

- Mobile Notification: Message has been sent and successfully acknowledged by the subscriber handset


Notification Chain Workflow

1. Delivery notification is received from the operator and sent to the Notification Router

2. The Notifsendsms software stores the SMSC acknowledgement and operator messageID in a mysql database

3. The UpdateMTNotif process maps the operator error code to SAP internal error codes, updates the status in the database, and generates a notification file

4. Delivery notification is sent to the Content Provider connection

5. Delivery notification is sent to Content Provider (and retried in case of failure)


Sock_mv server/client

• The sock_mv server/client is: - A generic file transfer

application used between servers and throughout the enterprise hub

- Capable of starting multiple instances scanning the same directories for load balancing and/or redundancy configuration


MNP Management

AR, AU, CA, CZ, FR, DE, IT

MX, NL, NZ, PL, SA, SP, TH

Thank you!

sap sms 365, enterprise service€¦ · •content providers connect through a firewall and...

Documents