Unified Call Routing via Meta-Identity Aggregation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network communication systems face complexity in call routing due to multiple identities of a caller, such as SIP URIs and mobile numbers, making it difficult to manage incoming calls effectively, especially in federated public Internet clouds where instant messaging clients can initiate IP voice calls.
Innovation Solution
The architecture aggregates multiple alternate identities of a user into a meta-identity, allowing a single call routing rule to be applied across all identities, enabling uniform call management and prioritization, with the ability to collect and link identities from internal and external data sources, and resolve conflicts using confidence ratings.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If call routing is performed for each individual identity (SIP URI, phone number), then routing precision for single identity is improved, but system complexity increases significantly when handling multiple identities of the same caller
Solution Approach 1:
The patent merges multiple alternate identities (SIP URIs, phone numbers, extensions) of the same caller into a unified call routing profile. Instead of maintaining separate routing rules for each identity, the system aggregates them under a single caller identifier, applying the same routing logic across all identities. This reduces system complexity while maintaining routing precision.
Solution Approach 2:
The call routing system is designed to handle multiple types of identities (SIP URIs, E.164 numbers, extensions, instant messaging handles) through a universal routing framework. A single routing rule set can be applied universally across different identity types, eliminating the need for identity-specific routing configurations and reducing overall system complexity.
2Adaptability or versatility
If multiple alternate identities of a caller are supported, then caller versatility is improved, but call routing management becomes complex or impossible
Solution Approach 1:
The patent introduces an intermediary layer (caller profile/aggregation service) that sits between the multiple identities and the call routing engine. This intermediary aggregates alternate identities, resolves conflicts, and presents a unified view to the routing system. Users manage routing rules at this intermediary level rather than for each individual identity, greatly simplifying operation.
Solution Approach 2:
The system performs preliminary aggregation and normalization of alternate identities before call routing decisions are made. By pre-processing identity information and establishing unified caller profiles in advance, the system eliminates the need for complex real-time routing management across multiple identities, making the system easier to operate.
3Measurement precision
If call routing rules are applied individually to each identity, then routing accuracy for that identity is improved, but time to manage and configure routing rules increases
Solution Approach 1:
The patent combines multiple identity-specific routing configurations into a single unified routing rule set. By merging alternate identities under a common profile, administrators can configure routing rules once and have them automatically applied to all associated identities, dramatically reducing configuration time while maintaining routing accuracy.
Solution Approach 2:
The system creates a master routing profile that can be copied or replicated across multiple identities. When a caller has alternate identities, the routing rules are copied from the unified profile to each identity, ensuring consistent and accurate routing without requiring separate manual configuration for each identity.
Data Source
AI summary
Architecture for enabling user identities of callers to be collected from data sources and aggregated into respective meta-identities for each caller. Alternate user identities are searched, collected and associated with the meta-identity that can be a user name. A routing rule applied to the meta-identity is then applied across the alternate identities. The user identities can include a name of the caller, a phone number of the caller, or caller information collected from an external source. The phone numbers can include a partial phone number that is normalized into a full phone number format. The user identities can be mapped to the meta-identity and stored according to a hierarchy of confidence ratings. The user identities can be tagged with corresponding data source identifiers that designate respective data sources of the user identities. Conflict resolution is provided for selecting a suitable call routing path between callers having similar meta-identities.