Message Controller Routing Query Interception
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing message routing systems in mobile networks are inflexible and unable to adapt to changes in network elements, leading to incomplete information retrieval from foreign networks, especially when subscribers move to advanced messaging forms or networks with different capabilities.
Innovation Solution
A message controller that extracts additional information from the original routing query, caches data to generate a fresh query, and dynamically selects nodes for routing, using protocols like Diameter to interact with presence servers and HSS, allowing for versatile processing and routing through smart services control nodes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If the original SRI-SM routing query is used directly, then the message can be routed to the HLR, but the information retrieved is incomplete when network elements have evolved or changed
Solution Approach 1:
The message controller performs preliminary actions by extracting the MSISDN from the original SRI-SM before forwarding, caches this data, and uses it to generate a fresh routing query. This preliminary extraction and caching enables the system to retrieve complete and current routing information from evolved network elements like HSS or presence servers, rather than relying on the potentially outdated original query format.
Solution Approach 2:
The system changes the parameters of the routing query by generating a fresh query with updated protocols (e.g., Diameter protocol) and requesting additional information fields that were not present in the original SRI-SM. This parameter change allows the query to be compatible with evolved network elements and retrieve more complete routing information including SGSN address, IP-SM-GW address, and other relevant data.
2Adaptability or versatility
If a single node processes all routing queries, then the routing logic is simple, but the system lacks flexibility and cannot distribute cache information
Solution Approach 1:
The system segments the routing functionality by introducing multiple message controllers that can independently process routing queries. Each message controller can maintain its own cache of extracted MSISDN data and generate fresh routing queries. This segmentation distributes the routing load and enables flexible selection of which node processes which query, while the overall system complexity is managed through standardized protocols and interfaces.
Solution Approach 2:
The message controller acts as an intermediary between the original SRI-SM sender and the final routing destination. It intercepts the original query, extracts necessary information, caches it, and generates a fresh query to the appropriate network element. This intermediary role adds flexibility to the routing process while managing complexity by centralizing the intelligence in the message controller rather than distributing it across all network elements.
3Reliability
If the message controller extracts and caches additional information, then optimal routing can be provided, but the processing time and complexity increase
Solution Approach 1:
The message controller performs preliminary extraction of the MSISDN from the incoming SRI-SM and caches this data before the actual routing decision is made. By preparing this information in advance and storing it in cache, the system avoids repeated extraction operations and can quickly generate fresh routing queries using the cached data, thereby reducing overall processing time while maintaining reliable message delivery.
Data Source
Figure 1~2
Figure 3~4
Figure 5
AI summary
An originating SMSC in Network A issues an SRI-SM towards the HLR of a recipient (User B in Network B). One of a number of N Platforms or Message Controllers ("MCOs") intercepts the SRI-SM. Instead of passing on the SRI-SM, the MCO terminates it and performs a full decode of all fields, specifically extracting the recipient MSISDN from it. The MCO then constructs a new SRI-SM for the same MSISDN, but forcing the new request to ask for all available data, including, but not necessarily limited to visited-MSC address, SGSN address and IP-SM-GW address. When a response is received the MCO generates a fresh query response for the originating SMSC instead of merely routing on the response which it receives. If the MCO is programmed to provide a false address for smart services it incorporates the false address in the query response which it generates. This avoids need to modify the incoming response and allows considerable additional versatility. For example the MCO may provide a number of false addresses, depending on how it generates the query response.