SIP Call Routing via Terminal ID Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current telecommunications systems lack the ability to efficiently manage and differentiate between multiple user devices associated with a single public user ID, leading to challenges in alerting and routing calls to the appropriate device based on device-specific attributes and preferences.
Innovation Solution
Assigning a unique terminal ID to each user device in addition to a public user ID, allowing network components to identify and communicate with specific devices, and implementing a predetermined order of alerts or attributes for call routing and service delivery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a single public user ID is used for multiple user devices, then call routing simplicity is maintained, but the ability to differentiate and alert specific devices is lost
Solution Approach 1:
The patent segments the identification system by introducing terminal IDs that uniquely identify each user device while maintaining the public user ID for overall user identification. This allows the network to differentiate between multiple devices (improving adaptability) while keeping the call routing process structured and manageable (controlling complexity).
Solution Approach 2:
The patent adds a new dimension to the identification system by introducing terminal IDs as a secondary identifier layer. This dimensional addition enables device-specific differentiation without disrupting the existing public user ID-based routing framework, thus improving versatility while maintaining routing simplicity.
2Adaptability or versatility
If terminal IDs are assigned to each user device, then device-specific alerting and routing is enabled, but system complexity increases
Solution Approach 1:
The system segments identification into two distinct layers: public user ID for user-level routing and terminal ID for device-level differentiation. This segmentation enables device-specific alerting and routing capabilities while maintaining a structured and organized system architecture that manages complexity through clear separation of concerns.
Solution Approach 2:
The terminal ID acts as an intermediary between the public user ID and the specific user device. This intermediary enables precise device identification and routing without requiring fundamental changes to the existing public user ID system, thus enhancing versatility while controlling the increase in system complexity.
3Measurement precision
If multiple identifiers are used per user, then precise device identification is achieved, but information management complexity increases
Solution Approach 1:
The identification system is segmented into public user ID for user-level identification and terminal ID for device-level identification. This segmentation achieves precise device identification by providing distinct identifier types for different levels of granularity, while managing information complexity through a hierarchical and organized structure.
Solution Approach 2:
Different identifier types are applied locally according to the specific routing or alerting need: public user ID is used for overall user routing, while terminal ID is used specifically when device differentiation is required. This local application of appropriate identifier types achieves precise identification without requiring complex management of multiple identifiers in all scenarios.
Data Source
AI summary
A method may include receiving, at an application server, a session initiation protocol (SIP) message including a public user identifier (ID) associated a user. The public user ID corresponds to a plurality of user devices. The method also includes determining an applicable order of alerting at least one of the plurality of user devices. The method further includes identifying at least one available user device associated with the user, based on a terminal identifier (ID) associated with each at least one available user device. The method also includes selecting a user device from the at least one available user device based on the applicable order of alerting. A SIP invite message, including a terminal ID for the selected user device, is generated. The method includes sending the SIP invite message to the selected user device based on the applicable order of alerting, and receiving a response to the SIP invite message.