Call Management Server Routing via Public Private Identifier Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Telecommunications systems face challenges in managing call requests, particularly in ensuring privacy for users with multiple phone numbers and handling calls from approved and unapproved parties effectively.
Innovation Solution
A method and apparatus that process call requests in a communication network by identifying approved calling party identifiers and routing calls using private identifiers for approved parties, while applying call handling treatments for unapproved parties, such as forwarding to voicemail or surrogate devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If users have multiple phone numbers associated with various devices, then users can have flexibility in communication channels, but user privacy is compromised and call management becomes complex
Solution Approach 1:
The system introduces a call management server as an intermediary between the calling party and the recipient. This server maintains a mapping between public identifiers and private identifiers, and approved calling party lists. The server routes calls by comparing calling party identifiers against approved lists and selecting appropriate private identifiers, thereby managing the complexity centrally rather than at each user device.
Solution Approach 2:
The system segments the identifier space into public identifiers (visible to others) and private identifiers (used for actual routing). This segmentation allows users to have multiple public identifiers for different devices while maintaining a single private identifier space that is managed centrally, reducing the complexity of managing multiple phone numbers across devices.
2Object-affected harmful factors
If users keep telephone numbers private, then user privacy is protected, but the ability to receive calls from approved parties becomes difficult
Solution Approach 1:
The call management server acts as an intermediary that enables private number protection while maintaining call reception capability. The server stores the mapping between public and private identifiers and handles the routing logic, allowing users to keep their private identifiers hidden while still receiving calls from approved parties through the public identifier system.
Solution Approach 2:
The system implements feedback mechanisms where the call management server continuously compares incoming calling party identifiers against the approved calling party lists stored in the database. This feedback loop ensures that only approved callers can reach the user while maintaining privacy protection.
3Productivity
If all call requests are routed through centralized management, then call handling efficiency improves, but system complexity increases
Solution Approach 1:
The call management server serves as a centralized intermediary that improves call handling efficiency by automating the routing decisions. It compares calling party identifiers against approved lists and selects appropriate private identifiers without requiring complex logic at each user device, thereby centralizing the complexity in a dedicated system component.
Solution Approach 2:
The call management server performs multiple functions: it maintains the public-to-private identifier mapping, stores approved calling party lists, compares incoming calls against approved lists, and routes calls to appropriate destinations. This multi-functionality consolidates what would otherwise be distributed complexity across multiple devices into a single universal system.
Data Source
AI summary
Method and apparatus for managing call requests in a communication network is described. In one example, a call request for a public identifier associated with a recipient party is received from an originating device. A set of approved calling party identifiers associated with the public identifier is identified. A calling party identifier associated with the originating device is compared with the set of approved calling party identifiers. If the calling party is approved, then: a private identifier for a recipient device is selected based on the calling party identifier, and the call request is routed to the recipient device using the private identifier. If the calling party is not approved, then: a call handling treatment associated with the public identifier may be identified, and the call request may be handled in accordance with the calling handling treatment.