Server Protocol Message Prioritization via Service Type
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In advanced communication networks, such as 3GPP IMS and LTE, the Home Subscriber Server (HSS) faces inefficiencies in managing protocol messages due to the lack of differentiation between critical and non-critical requests, leading to performance issues during heavy-load or overload conditions, where conventional systems fail to prioritize messages effectively based on the type of service application.
Innovation Solution
The implementation of a system that allows clients to include a data unit in protocol messages indicating the type of service application, enabling servers to prioritize and schedule these messages based on the 'App Type' attribute, thereby distinguishing between different service applications and managing requests more efficiently, especially during overload conditions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the server processes all protocol messages equally without differentiation, then the system maintains simplicity in message handling, but the server performance deteriorates during heavy-load conditions due to inability to prioritize critical messages
Solution Approach 1:
The patent applies local quality by differentiating message handling based on the specific characteristics of each message type. The server identifies the service application type (e.g., initial registration vs. re-registration) and applies different prioritization rules to different message categories, rather than treating all messages uniformly. This allows critical messages to be processed with higher priority while maintaining simpler handling for non-critical messages.
Solution Approach 2:
The patent changes the parameter of message priority by introducing a priority indicator based on service application type. The server modifies its processing behavior by adjusting the priority level assigned to messages depending on whether they originate from critical services (like initial registration) or non-critical services (like re-registration). This parameter change enables dynamic resource allocation without fundamentally altering the message handling architecture.
2Reliability
If the server prioritizes critical messages during overload conditions, then the reliability of critical services improves, but the complexity of message scheduling increases
Solution Approach 1:
The patent segments the message stream into different categories based on service application type. By dividing messages into distinct groups (e.g., initial registration messages, re-registration messages, other service messages), the server can apply specific prioritization rules to each segment. This segmentation simplifies the scheduling mechanism compared to implementing complex priority queues for individual messages, as it operates at the service type level rather than the individual message level.
Solution Approach 2:
The patent implements preliminary action by pre-defining priority levels for different service application types. Instead of making complex real-time decisions about message priority during overload conditions, the system establishes prioritization rules in advance based on service criticality. When a message arrives, the server simply looks up the priority associated with its service type, eliminating the need for complex runtime scheduling decisions.
3Stability of the object's composition
If the server rejects or drops messages during overload conditions, then the system maintains stability, but the loss of information increases for non-critical messages
Solution Approach 1:
The patent applies local quality by differentiating between critical and non-critical messages when applying overload protection. The server identifies the service application type and applies selective rejection rules: critical messages (e.g., initial registration) are protected from rejection, while non-critical messages (e.g., re-registration) may be rejected during overload conditions. This localized differentiation maintains system stability while minimizing information loss for essential services.
Data Source
AI summary
System(s) and method(s) are provided for prioritizing protocol messages received at a server. A client generates a request message and incorporates a data unit therein in order to indicate type of service application that triggered generation of the request message. The client conveys the request message to a server configured to respond to the request message. To supply data in response to the message request, the server prioritizes the request message based at least on the data unit that conveys the type of service application. The server can assign a set of request messages to a group of scheduling queues based at least on ranking of the type of service associated with at least one request message in the set of request messages. Based on performance conditions, the server also can reject one or more request messages according to the ranking.