SMS Gateway Solutions

  1. Title

  2. Purpose

    • The SMS GW platform is designed for sending mailings and/or single messages to the sms center and to other OTT systems.
  3. General description

    • The SMS GATEWAY platform (SMS GW) is a gateway with a set of various interfaces and additional business logic. The SMS GW platform is designed to send dispatches and/or single messages to the sms center and to other OTT systems. The SMS GW platform allows external customers to Instantly send single smpp messages; Schedule mailings on the platform in advance; Once mailings have been scheduled, change mailing parameters, up to and including deleting the mailing; Receive statistics about the dispatches sent with the exact status of a single message..; Receive statistics about the dispatches with the exact status of a single message. When a new consumer is registered in the SMS GW platform, he is allocated a channel for mailings in tps. The SMS GW platform automatically monitors that the consumer does not exceed the tps of the channel allocated to him.
  4. Hardware and software used

    • The solution is deployed on standard x86 servers or in a virtual environment.
  5. Technical description

    • The platform performs a uniform mailing, if needed the provider can schedule a short mailing with a high tps or a long mailing with a low tps value;
    • Time zone accounting;
    • Opportunities to pause and reschedule mailings;
    • The platform supports setting priorities in mailings and then changing them;
    • Correct handling of mailing errors and validation (for example, when a channel is limited and a request is received with exceeding the channel capacity — there is a rebound with the corresponding error);
    • Mailing schedule dosage with the consideration of the channel capacity reserved for the particular mailing, returning the fact of correspondence to the schedule specified in the CM;
    • Channel management for all types of messages, not only for ordinary SMS, but also for Viber;
    • Support of all message languages, including Chinese;
    • Security check of system access to the gateway with login and password;
    • Support of different user roles, logging of user actions;
    • Support for the use of blacklists;
    • Availability of API for integration with Campaign Management, which contains: subscriber number, text message, mailing rate, priority of mailing, date for delayed mailing, login, password, status of receiving package, status of sending on each message, ID of message on client side, on server side, number of requested statuses from queue.
    • Support for N+1 redundancy of all platform components in load sharing mode with automatic switching to remaining components, in case of failure of one or more components
    • Site-by-site redundancy
    • Horizontal scaling of platform components;
    • Flexible restrictions in channels for external partners (e.g. total bandwidth limitation, sms/sec for SMPP link, separate limits for additional criteria, e.g. regions-def numbering of receivers, general limitation - 100 sms/sec, not more than 10 for region A, not more than 50 for region B, etc.)
    • Providing platform components performance statistics;
    • Providing a record of information about each transaction (DB or CDR) both for the purposes of organizing some aggregated statistics and for the purposes of solving problems;
    • Provision of operation with several SMSC/USSDC/MMSC with ability to regulate traffic distribution between centers;
    • Platform side API support for external provisioning/request of data from the platform;
    • Support for protocols to work with both SMSCs and external systems that initiate A2P traffic (in particular SMPP, HTTP, REST).

Solution architecture

Solution architecture