SMPP Message Routing via Load Balancing and Sequence Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
SMSC bandwidth limitations lead to dropped or delayed SMPP messages during high volume periods, affecting the quality of service in SMS messaging.
Innovation Solution
A network traffic management apparatus that selects the most suitable SMSC server based on load balancing decisions and generates a new sequence number for SMPP request messages, storing this information in a mapping table to ensure accurate routing and prevent message rejection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If SMSC bandwidth is increased to handle high volume messages, then message delivery capacity is improved, but system cost and complexity increase
Solution Approach 1:
The patent segments the SMSC into multiple servers (first SMSC server, second SMSC server, etc.) that can process messages in parallel. This segmentation allows the system to handle high message volumes by distributing the load across multiple independent units, thereby improving productivity without requiring a single oversized complex system.
Solution Approach 2:
The patent introduces a traffic management apparatus as an intermediary component that sits between the ESME and multiple SMSC servers. This intermediary manages message routing, sequence number coordination, and load distribution, enabling the system to scale message delivery capacity while keeping individual SMSC server components relatively simple.
2Loss of time
If load balancing is implemented to distribute messages across multiple SMSC servers, then message delivery latency is reduced, but system complexity increases
Solution Approach 1:
The patent implements feedback mechanisms where the traffic management apparatus monitors message flow and uses sequence numbers to track the state of message processing across multiple SMSC servers. This feedback allows dynamic adjustment of message routing to optimize delivery latency while maintaining system manageability through structured control.
Solution Approach 2:
The patent changes the sequence number parameter dynamically when routing messages to different SMSC servers. By modifying sequence numbers based on the selected server and maintaining mapping tables, the system achieves effective load balancing and reduced latency without requiring complex routing protocols or state management.
3Ease of operation
If sequence number management is simplified, then ease of operation is improved, but message routing accuracy deteriorates
Solution Approach 1:
The patent creates copies of sequence number mappings in the traffic management apparatus's memory (mapping tables). These copies store the relationship between original sequence numbers and the SMSC servers they should be routed to. This allows the system to maintain routing accuracy by referencing stored mappings while simplifying real-time operation through direct table lookups rather than complex calculations.
Solution Approach 2:
The patent performs preliminary action by pre-establishing mapping tables that store sequence number to SMSC server correspondences before message processing begins. This preliminary setup allows the traffic management apparatus to quickly determine routing decisions without performing complex real-time analysis, thereby simplifying operation while maintaining accuracy.
Data Source
AI summary
A method, non-transitory computer readable medium, and network traffic management apparatus that selects a first one of a plurality of Short Message Service Center (SMSC) servers based on a load balancing decision in response to an external short messaging entity (ESME) SMPP request message received from a first one of a plurality of ESMEs. A first sequence number is generated for the ESME SMPP request message. The first sequence number is stored in a first entry of a mapping table as associated with a sequence number included in the ESME SMPP request message and an indication of the first one of the plurality of SMSC servers. The sequence number included in the ESME SMPP request message is replaced with the first sequence number. The ESME SMPP request message is sent to the first one of the plurality of SMSC servers.