SAP SMS 365, enterprise service Standard Rate SMS Messaging. October 2013

Transcription

1 SAP SMS 365, enterprise service Standard Rate SMS Messaging October 2013

2 Message Aggregation SAP SMS 365, enterprise service, provides: Aggregates access to send SMS to 700+ carriers around the world through one connection Allows 2 way messaging from 280 networks through short codes in 91 countries Allows 2 way messaging to hundreds of networks through long codes 2013 SAP AG. All rights reserved. 2

3 2-Way Standard Rate Messaging Short code coverage map: 2013 SAP AG. All rights reserved. 3

4 Key Features Reach Multiple routes/fail-over to most destinations Supports high-volume campaigns Message delivery features include: Batch send Deliver messages in any format, in any language Global Numbering Plan Control when a message is delivered (Delivery Time Window) 2013 SAP AG. All rights reserved. 4

5 Standard Messaging Reach Content Providers send MT traffic using the following support protocols: HTTP and HTTPS SMTP ( ) SMPP (short message peer to peer) SAP Mobile Services Messaging Hub routes MT traffic to the mobile operator, which in turn, delivers the messages to end-users SAP AG. All rights reserved. 5

6 Mobile Messaging with SAP (Push/MT messaging) Real Time Traffic Monitoring Delivery Notifications Your have $100 to pick up, ref Connections Message Prioritisation SAP Mobile Services Delivery Time Window Load Balancer Read Back Single Interface Sap SAP With Delivery The Delivery SAP Mobile provides can SMS our Notifications MT setup Extranet 365, Services traffic, Time priority enterprise single tool Window an Hub are rules provides interface operator generated service, can functionality for direct Client, access for connection reaches for clients multiple to to is ensure various used more who is MT IP overloaded to packets would messages SMS than types deliver 700 of to or otherwise one messages received statistical are mobile dropped delivered of several operators then and have only reports our within acknowledged machines during error negotiate around on the all detection certain using messages preferred the and world by a time connect software the timeframe, sent window. mobile to through can round a operator With diverse re-route with robin the this minimal SAP set the of latency mobile algorithm, feature SMS through network. through operators enabled, its Information which interface a contingency messages is inbuilt order with is available SAP. into from send/receive the route Notifications on the Linux a client daily, kernel push/mt which are weekly as also are well and or outside as generated premium using of monthly the a preferred Veritas basis messages when and Cluster. an delivery is MT to broken subscribers The SMS time load into is window, rejected global balancer from traffic will different by is the be used and spooled operator s networks. traffic on per SMSC We distribute the country/operator SAP support Queue traffic HTTP, until and SMPP the connections next and window SMTP evenly is reached between the servers to gain optimum performance and bandwidth Secure VPN & Firewall 2013 SAP AG. All rights reserved. 6

7 Mobile Messaging with SAP (Two-way, MO/MT Chain) Real Time Traffic Monitoring Delivery Notifications Keyword Routing Send to: Your Nearest nearest ATM ATM machine: machine HA3 is on 2DG Old Street, HA3 (next to the post box). 140 networks Billing Mechanism SAP Mobile Services Delivery Time Window Send Read Back Load Balancer SAP Mobile Services supports keyword routing for both long and short codes. One TPDA (Transmission Path Destination Address) can be shared across a number of Client applications, and each application can have one or more keywords Keyword: ATM Secure VPN & Firewall 2013 SAP AG. All rights reserved. 7

8 Delivery Receipts Content Provider MT SMS Delivery Receipt Level 0 Delivery Receipt Level 1 Delivery Receipt Level 2 SAP SMS 365, enterprise service MT SMS Operator Delivery Receipt Operator MT SMS Handset Acknowledgement End-user SAP SMS 365 Notification: Message was processed successfully by the Messaging Hub SMSC Notification: Message was sent and acknowledged successfully by the operator Mobile Notification: Message was delivered and acknowledged successfully at the handset Error Codes: Further define the status of messages; error codes are the same for all countries/operators, thereby allowing client to implement intelligent and efficient retry mechanisms 2013 SAP AG. All rights reserved. 8

9 Search Messages Search with different criteria: phone number, order ID, time period, message type and country for both MO and MT SAP AG. All rights reserved. 9

10 Real-time Statistics Monthly Traffic Daily Traffic Hourly Traffic Traffic by Country Traffic by Operator Watch your traffic grow Track by Country and Operator Identify peak traffic times 2013 SAP AG. All rights reserved. 10

11 Enterprise Messaging Client SLA Messaging Hub availability 99.5% Scheduled maintenance limited to 1 hour max per month with min 3 days notice Direct and hotline access to helpdesk and support process Response times detailed below: Stage/Priority P1 P2 P3 P4 Customer Type Customer m-commerce Service Level Initial Response Time 1 hour 2 hours 1 day 2 days Target Restoration (work around) 2 hours 5 hours 2 days 5 days Target Resolution 2 days 5 days Next release Next release 2013 SAP AG. All rights reserved. 11

12 SAP Mobile Services General Messaging Recommendations SAP recommends that, where cost effective, short codes be used for 2-way communication with users Shared short codes are beneficial for getting a service up and running quickly, but have drawbacks from having to use keywords and sharing the same code with other companies Long numbers (if local to that country) can be a more cost effective way of setting up 2-way communication, and for replies to MT are just as effective as a short code 2013 SAP AG. All rights reserved. 12

13 Short and Long Code Comparison Metric Dedicated Short Code Shared Short Codes Local Long Code Time to Market Longer Rapid Rapid Cost Highest Moderate Lowest Usability Highest easy to remember sticky; can be in some markets Moderate requires user to remember keyword Moderate best for reply MOs; number may not be easy to remember Branding Best easy to remember numbers to associate with Client Shared with other service providers, nothing to stop competitors using same code Moderate 2013 SAP AG. All rights reserved. 13

14 SAP Mobile Services Short and Long Code Acquisition/Provisioning SAP will be responsible for managing and provisioning short codes or long codes in any country with carriers and/or regulators: SAPcan manage the procurement and provisioning of short codes on major mobile networks worldwide SAP will review client s message flow to help advise compliance with local regulations - Each country will have unique requirements SAP s in-market teams will assess the program to help advise compliance and rapid deployment SAP can grant Client contractual ownership or lease of these short codes as appropriate in the markets SAP AG. All rights reserved. 14

15 SAP Mobile Services Short and Long Code General Considerations Several markets require MO support for MT only campaigns: Support for the STOP and HELP commands is required in several markets Even where not required it is a best practice for enterprise businesses to support STOP command - Dedicated short codes/long codes: STOP will suffice since all messages will be sent to Client - Shared short code: STOP cannot be directed to client since this is a generic keyword. Instead we suggest to use END, QUIT, CANCEL, UNSUB or similar depending on keyword availability Client can run several services on one dedicated short code using different keywords SAP AG. All rights reserved. 15

16 SAP Mobile Services Short and Long Code International Considerations Short codes are country and/or carrier specific: Typically short codes will work in an international roaming scenario Delivery reliability is dependant on the roaming agreements between the mobile user s carrier and the international roaming host carrier This limitation is outside the control of SAP, and SAP will assist Client with the analysis of specific scenarios Long codes are specific to a single carrier: Provisioning with a single carrier enables rapid and cost effective deployment International use results in long distance text messaging charges to the mobile user MO messages are typically supported internationally, since they appear to the local carrier as a person-to-person text message Both MO and MT international delivery are subject to in-country regulations or inter-carrier specific roaming agreements This is also a limitation outside the control of SAP, and SAP will assist Client with the analysis of specific scenarios 2013 SAP AG. All rights reserved. 16

17 Messaging 101 P2P A2P Aggregator MO MT PSMS SMSC Standard rate messaging FTEU Person to person (Operator Services) Application to person (Enterprise Services) Companies aggregating access to multiple mobile networks for messaging access Mobile Originated: From handset to application Mobile Terminated: From application to handset Premium SMS: Overcharged message on bill or prepay account from which there is normal Revenue Share Short Message Service Centre (at carrier) (In US) user still pays to receive though 50% + now from bundle Free to End user: In this model carrier charges SAP/Client to send MT messages or receive MO messages. Short code Number used to address/send messages to or from e.g Long code WAP Push WAP Billing API Billing Mobile length number set up on SMSC to collect incoming messages Encoded SMS used to link to WAP page Ability to initiate billing from within a WAP Session Billing API offered by carrier for WAP and or Web billing 2013 SAP AG. All rights reserved. 17

18 Thank you!