Address Registration Server Access Information Extraction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing telecommunications systems face challenges in efficiently retrieving access information for communication sessions across different networks and applications, particularly when parties are subscribed to different communication applications or systems, requiring updates to central databases and authentication policies.
Innovation Solution
A method utilizing an Address Registration Server (ARS) that registers parties with unique identities and network contact addresses, allowing parties to store and manage their own access information, which includes communication capabilities, protocols, and preferences, enabling efficient communication session setup without relying on central databases.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a central database is used to store access information of all parties, then communication session establishment is simplified, but the system becomes dependent on intensive central processing and database updates are required for new protocols and applications
Solution Approach 1:
The patent extracts the access information storage function from the central database and relocates it to the user equipment itself. Each device stores its own access information locally, eliminating the need for continuous central database updates and reducing central processing load while maintaining ease of communication establishment.
Solution Approach 2:
User equipment is empowered to store and manage its own access information autonomously without requiring central database intervention. The device serves itself by maintaining local access information, which can be retrieved by other devices initiating communication sessions.
2Ease of operation
If access information is stored centrally, then retrieving communication details is straightforward, but security is compromised as sensitive information is centralized
Solution Approach 1:
The patent extracts sensitive access information from the centralized storage location and places it in distributed storage at individual user equipments. This extraction eliminates the security vulnerability of centralized sensitive information storage while preserving the ability to retrieve communication details when needed.
3Adaptability or versatility
If new protocols and applications are added to the central database, then communication capabilities are enhanced, but the system requires continuous updates and maintenance of central repositories
Solution Approach 1:
The patent segments the monolithic central database into distributed storage units at each user equipment. Each device independently stores its own access information for new protocols and applications, eliminating the need for centralized system updates and maintenance while maintaining full adaptability to new communication capabilities.
4Ease of operation
If the Address Registration Server processes all access requests, then centralized control is maintained, but the server becomes a bottleneck with intensive processing requirements
Solution Approach 1:
The patent extracts the access information storage and retrieval function from the Address Registration Server, leaving the server with only essential registration and lookup tasks. User equipment independently stores and provides access information, dramatically reducing server processing requirements while maintaining centralized control over the registration process.
Data Source
AI summary
A party (2) in a telecommunications network (1) comprises access information (3) pertaining to communication capabilities the party (2) is able to handle. The party (2) is registered (4) with a unique identity (6) and at least one network contact address (7) at a server (5). Access information required for setting up a communication session with the party (2) is retrieved by initiating, by an entity (8) in the network (1), of a contact request (9) to the server (5) for at least one network contact address (7) of the party (2) from which access information of the party (2) is available. The server (5) forwards the at least one network contact address (6) of the party (2) in a token (10). Using the received at least one network contact address (6), the entity (8) initiates an access request (11) to the party (2) for retrieving access information (3) and receives access information (12) from the party (2) in response to the access request (11).


