Multiparty Service Routing via Priority Rules
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Multiparty service architectures face challenges in efficiently routing session establishment messages between private and public endpoints, especially when expanding to serve public domain customers over the Internet, requiring modifications to session establishment procedures to handle proprietary signaling and diverse endpoint configurations.
Innovation Solution
The implementation of priority rules for routing within the multiparty service architecture, which inspects session establishment messages to determine whether to route them to private or public endpoints, using databases to identify destination addresses and employing communication managers, DNS lookups, and PIP/MPLS systems to manage routing effectively.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the multiparty service architecture uses traditional routing methods to handle session establishment messages, then the system can maintain simplicity in routing logic, but it cannot efficiently differentiate between private and public endpoints leading to suboptimal routing performance
Solution Approach 1:
The routing logic is segmented into distinct priority levels (first priority for private endpoints, second priority for public endpoints). The system divides the routing decision process into separate evaluation stages, where each stage handles specific endpoint types with dedicated routing rules, thereby improving routing efficiency without overwhelming complexity
Solution Approach 2:
The system performs preliminary classification of session establishment messages by identifying endpoint types before routing decisions are made. By预先 determining whether an endpoint is private or public and assigning priority levels, the system prepares routing information in advance, enabling faster and more efficient routing execution
2Reliability
If the system routes all session establishment messages through the same path, then the routing process is simple, but it causes increased latency when private endpoints are congested or unreachable
Solution Approach 1:
The routing system dynamically adjusts path selection based on real-time conditions. When private endpoints are congested or unreachable, the system automatically switches to alternative paths through public endpoints. This dynamic adaptability ensures reliable service delivery while minimizing latency by avoiding congested routes
Solution Approach 2:
Public endpoints serve as intermediary routing options when direct private endpoint routing is unavailable. The system uses public endpoints as mediator nodes to establish multiparty sessions, ensuring that service delivery continues without interruption even when private routing paths are blocked or congested
3Adaptability or versatility
If the multiparty service architecture expands to serve public domain customers over the Internet, then the system gains broader service coverage, but it requires modifications to session establishment procedures increasing system complexity
Solution Approach 1:
The routing system is designed with universal capabilities to handle multiple endpoint types (private and public) and various session establishment scenarios through a unified framework. This multi-functional approach enables the system to serve both private and public domain customers without requiring separate procedural frameworks, thereby expanding service coverage while controlling complexity
Solution Approach 2:
The system applies different routing rules and priority levels tailored to specific endpoint types and service scenarios. Private endpoints receive first-priority routing with dedicated rules, while public endpoints receive second-priority routing with appropriate rules. This localized customization allows the system to adapt to diverse customer requirements without overwhelming global complexity
Data Source
AI summary
Methods, devices, and storage media provide for receiving a request to use a multiparty service; applying priority rules for routing the request toward a destination endpoint, wherein the applying comprises determining whether the destination endpoint is a private destination endpoint or a public destination endpoint; routing the request toward the private destination endpoint in response to determining that a destination address or a portion thereof included in the request corresponds to the private destination endpoint; and routing the request toward the public destination endpoint in response to determining that the destination address or the portion thereof included in the request corresponds to the public destination endpoint.