Cloud SMPP load balancer supporting MO and MT SMS for high availability, reliability and capacity.Categories: Bulk SMS
Use the Melrose Labs SMPP Load Balancer cloud platform with your SMS gateway nodes and SMSCs to provide a high availability endpoint for your clients, insulate your platforms, and optimise SMS traffic loading. Our team has over 20 years in designing, building and operating highly reliable mobile messaging services, and a key part of our success has always been SMPP load balancing, or layer 7 load balancing.
The SMPP Load Balancer service provides an endpoint to which your clients connect using the SMPP protocol to submit messages for delivery to mobiles, and also to receive messages from mobiles. SMPP connections over TCP, with or without TLS, are load balanced at the transport layer (layer 4) onto our nodes. Messages submitted via those client connections are then load balanced (layer 7) across the SMSC pools that you define for your clients' traffic.
The use of the SMPP Load Balancer service can bring the following benefits:
- Consistently low SMPP response times.
- Reduce exposure of platforms to Internet.
- Improved availability.
- Reduced impact from upstream platform failures.
- Enables platform maintenance without service impact.
- Improved utilisation of resources.
Scenario #1: Client-facing endpoint in front of your own messaging platforms
You configure accounts and SMSC pools for your platforms on the SMPP Load Balancer service and your clients connect to the service instead of your own platforms. The service connects to your platforms and messages submitted by clients are load balanced across your platforms, with traffic from multiple clients being multiplexed onto upstream binds. Delivery receipts are routed back from your platforms via the service to the client connection for the SMPP account that submitted the corresponding outbound message.
Optionally, client accounts can be configured to operate in "proxy" mode, where the service proxies SMPP submit_sm requests to your platforms. In this case, a bind is made from the service to your platforms using the client SMPP account credentials and only SMS traffic sent by that client is routed to your platforms using their credentials.
Scenario #2: Client-facing endpoint that routes messages to your suppliers' SMS gateways and SMSC platforms
You configure accounts and SMSC pools for your supplier platforms on the SMPP Load Balancer service and your clients connect to the service. The service connects to your suppliers and messages submitted by clients are load balanced across those suppliers, with traffic from multiple clients being multiplexed onto upstream binds. Delivery receipts are routed back from your suppliers via the service to the client connection for the SMPP account that submitted the corresponding outbound message.
Scenario #3: Own platorm endpoint that routes messages to your suppliers' SMS gateways and SMSC platforms
Use upstream of your platforms to handle message submission to your suppliers. Your platform could be a messaging application, or an application with messaging capability, but you need more control and accounting of messaging. The SMPP Load Balancer service enables your to achieve this.
|Melrose Labs SMPP Load Balancer Summary|
|Client (ESME) Control|
|Reliability and Availability|
- Load balance across multiple SMS gateways and SMSCs
- Bind authorisation on load balancer (or passthru)
- Up to 10000 SMS/sec throughput
- Concatenated SMS support
- A2P SMS
- P2A SMS