Modulo SMS Center is a carrier-class high-performance SMS center for simple and cost-effective deployment in GSM/UMTS mobile networks. Equipped with a simple and easy-to-use RESTful HTTP API for sending and receiving SMS messages through external applications, our Short Message Center features is suitable for MNOs, MVNOs and fixed line operators.
Featuring simple and easy to use RESTful HTTP API, Modulo SMSC provides unlimited flexibility in regard to developing additional services based on the SMSC. Enabling any web developer to create specialized SMS-based services, Modulo SMSC enables any MNOs, MVNOs and Telecom OEMs to deploy value added services in an economic, quick and easy way. Allowing dynamic and easy deployment adjustments according to changes in SMS traffic in the network, Modulo SMSC is a complete and yet cost-effective solution. With a low entry-level cost.
Modulo SMSC includes a Gateway Home Location Register (GHLR), which provides fixed networks the ability to send and receive SMS messages. The GHLR also includes SMS home routing capabilities for handling inbound SMS traffic, directing it to an SMS router that can act as a firewall and perform actions like copying and forwarding of messages, sending automatic replies, and more. This allows fixed line operators to create revenue from SMS services even though they are not mobile operators and do not handle SMS-capable handsets.
Flexible delivery scenario management embedded “First Delivery Attempt” feature, policy management, convenient licensing principles and a powerful SMS routing subsystem all make Modulo’s SMSC the perfect choice for any mobile operator’s needs. Routing and bandwidth configuration tools support fully functional SMPP interface with efficient access policy for interaction with external applications. Horizontal scaling architecture allows for achieving high reliability and for adjusting the SMSC’s performance as the network grows. Features like SMS forwarding, auto-reply and detailed reports increase service convenience for subscribers.
In a small-scale deployment, high availability is ensured by implementing an Active-Active configuration with a single signaling point code (SPC). Both nodes are actively handling traffic and load balancing is employed to equally distribute the workload between the two, ensuring that neither node becomes overloaded. Since both nodes share the same SPC, they are treated as a single logical entity by the signaling network, simplifying management and ensuring seamless failover. In the event of a node failure, the remaining healthy node automatically takes over all the traffic and transactions without any service disruption, maintaining continuous operation. This approach guarantees high availability through redundancy, ensuring that even if one node fails, the other can seamlessly handle the entire load without affecting service performance.
SMSC Deployed in a Combined Linkset
In larger scale deployments, high availability and scalability are achieved by using a signaling front-end coupled with an N+1 configuration. The signaling front-end acts as a centralized point that manages and distributes traffic to multiple backend nodes, which are configured in an N+1 setup. This configuration ensures that there are more operational nodes than the minimum required (N nodes), with one additional spare node (the “+1”) that serves as a backup in case of node failure. The front-end intelligently directs traffic to the active nodes and can reroute it to the backup node if any of the primary nodes become unavailable. This setup provides not only redundancy but also load balancing across multiple nodes, ensuring optimal performance even under high traffic loads. With this architecture, the system can scale efficiently, handling large volumes of traffic while maintaining service continuity and minimizing downtime during failures.
SMSC Deployed with Signaling Front-End
| Host | General purpose server with Linux OS |
| TDM interface | PCIe E1/T1/J1 adapter with MTP2 software |
| IP interface to PSTN | M3UA, M2PA, M2UA over SCTP |
| IP interface to LAN | HTTP RESTfull API SMPP v3.4 |
| SS7 links | 4 to 256 LSL |
| SIGTRAN associations | Up to 1024 |
| E1 interfaces | 4 to 16 per machine |
| MAP protocol stack | GSM 09.02 (TS 100.914) GSM 29.002 |
| TCAP protocol stack | ITI-T Q.771 through Q.774 X.680, X.690 ETSI ETS 300.134 ETSI ETS 300.287 ANSI T1.114 |
| SCCP protocol stack | ITU-T Q.711 through Q.714 Connection-less class 0 & 1 ETSI ETS 300.589 ANSI T1.112 |
