SAP SMS 365 SAP Messaging Proxy 365 Product Description August 2016 Version 1.0
TABLE OF CONTENTS 1 INTRODUCTION...3 2 BENEFITS...4 3 FUNCTIONAL DESCRIPTION...5 4 MESSAGE CLASSIFICATION...6 5 ARCHITECTURE...7 6 MESSAGE FLOWS...8 6.1 P2P SS7 Message Flow... 8 6.2 A2P SS7 Message Flow... 8 6.3 P2P IP Message Flow... 9 6.4 A2P IP Message Flow... 9 2
1 INTRODUCTION As subscribers shift to communication formats such as chat apps and social media, revenue from person-toperson (P2P) traffic is beginning to stabilize. Application-to-person (A2P) messaging traffic volume is growing, but A2P messages can be hidden in P2P traffic where it can slip by without detection or payment. SAP Messaging Proxy 365 offers a profitable solution. Mobile network operators (MNOs) may think of messaging as a legacy service undeserving of continued support and resources. SAP Messaging Proxy 365 challenges this thinking by enabling operators to extract more value from existing infrastructure investments. Through simplified management of A2P and P2P messages, and outsourcing short message service (SMS) transmissions, operators can better monetize SMS traffic and offer enhanced messaging services. SAP Messaging Proxy 365 is a cloud-based service hosted and managed by SAP Mobile Services. This service enables the splitting and routing of A2P and P2P messages to the appropriate platform for more accurate delivery to subscribers and invoicing of messaging traffic. Operators simply reroute messaging traffic to the cloud service and SAP Mobile Services does the rest. SAP Messaging Proxy 365 collects messaging traffic in a single feed, regardless of how an operator connects, whether an operator uses Signaling System 7 (SS7) or Internet protocol (IP). The service classifies the messages as either A2P or P2P and sends them along the highest-quality route to the relevant platform for delivery and billing. P2P messages are routed through the SAP SMS 365 mobile service while A2P messages are routed to SAP SMS 365, enterprise service. Throughout this process, operators maintain visibility and control, and online tools enable accurate reporting on all A2P and P2P traffic. SAP Mobile Services handles local industry and regulatory requirements, enabling operators to further optimize the services they provide to enterprise customers. The combination of better routing of messages and enhanced services creates better, more-accurate, and highly effective ways for enterprises to reach an operator s subscribers, which, in turn, opens new revenue opportunities for the operator. 3
2 BENEFITS Through SAP Messaging Proxy 365, an operator can transform legacy-messaging services into a renewed source of incremental revenue. Using an operator s existing infrastructure, SAP Messaging Proxy 365 enables better solutions and practices for messaging traffic management. It saves an operator s internal IT department and teams, the time, cost, and risk of trying to develop, deploy, and manage an on premise middleware solution. SAP Messaging Proxy 365 helps operators simplify complexity and increase revenue. Because it is a managed, cloud-based service, SAP Messaging Proxy 365 requires neither capital expenditure nor additional investment in networks or hardware. Operators only need to reroute traffic to the service, enabling them to derive additional value from existing assets with relative ease. It frees operators to focus resources whether assets or employees on daily operational tasks as well as higher-priority needs By more, accurately classifying and routing an operator s A2P and P2P messages, SAP Messaging Proxy 365 allows an operator to realize numerous benefits, including: 1. Maximized use of its existing infrastructure and network capacity, 2. Improved revenue by optimizing existing messaging streams and closing revenue leaks, 3. Increased monetization by bringing higher-quality traffic into its network, identifying and unblocking illegitimate P2P traffic, and properly routing it so it can capture its rightful revenue, 4. Reducing complexity by connecting messaging streams to SAP Mobile Services using existing points of contact for automated classification and routing of messages to the right platform for delivery, 5. Faster time to value by leveraging a managed, cloud-based service that avoids additional capital expenditures and the commitment of internal resources to manage an on premise solution, 6. Increased visibility and control of messaging traffic with online reporting tools, 7. Better long-term investment by adopting a future-proof platform that is supported and maintained by SAP Mobile Services. 4
3 FUNCTIONAL DESCRIPTION 1. Receives ALL messaging traffic, regardless of how the operator is connected SS7 or IP, 2. Removes the complexity of routing P2P and A2P messages, 3. Classifies the messages, 4. Routes the messaging traffic to the relevant platform Operator Services or Enterprise Messaging for processing and forwarding on to the destination operator and, 5. Bills and reports accordingly. Figure 1: SAP M essaging Proxy 365 5
4 MESSAGE CLASSIFICATION Messages are classified by SAP Messaging Proxy 365 by: 1. Analyzing the Originating Address (OA) of the SMS sent by the SAP Messaging Proxy 365 customer: a. Alphanumerical OAs are classified as A2P traffic. b. Short Codes are classified as A2P traffic. c. In general, only national or international telephone numbers are classified as P2P traffic. 2. Analyzing the Data Coding Scheme (DCS) of the SMS sent by the SAP Messaging Proxy 365 customer: a. Used for identifying the SMS type (Text vs. Binary). a. The following DCS values are automatically classified as A2P traffic: DCS = 2, 4, 5, 9, 10, 245, 246. 3. A White-List exception for the above requirements per Origin Operator: a. List of OA that are classified as A2P (specific Long Codes). b. List of OA that are classified as P2P (Alphanumeric OAs for Operator Names for Welcome Messages). 4. The above classification is configurable per ORIGINATING operator. 5. The above classification and whitelist is also configurable per DESTINATION country. The above Routing Algorithm will be reviewed on an ongoing basis and improvements and new classifications will be implemented when the need arises. Depending on laws and regulations, certain countries have A2P delivery restrictions/limitations, which might make some of the A2P routing algorithms in place invalid. Following the standard A2P process, these A2P delivery restrictions/limitations will be addressed with the operator on a country-by-country basis. 6
5 ARCHITECTURE Figure 2: SAP M essaging Proxy 365 Architectur e 7
6 MESSAGE FLOWS 6.1 P2P SS7 Message Flow Figure 3: P2P SS7 M essage Flow 6.2 A2P SS7 Message Flow Figure 4: A2P SS7 M essage Flow 8
6.3 P2P IP Message Flow Figure 5: P2P IP M essage Flow 6.4 A2P IP Message Flow Figure 6: A2P IP M essage Flow 9
www.sap.com 2016 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE s or its affiliated companies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.