Local Cache for Packet Telephony Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Internet telephony service providers face inefficiencies and security concerns when routing calls due to the large size of central databases and the need to query them for every call, leading to potential delays and unauthorized access to subscriber records.
Innovation Solution
Implementing a local cache system that stores records from the central database, allowing ITSPs to route calls based on cached information for frequently dialed numbers and updating records independently, while using encryption and access controls to secure data access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If ITSPs query the central database for every call to retrieve routing information, then accurate routing decisions can be made, but call completion delays occur due to the time required for each query
Solution Approach 1:
The system performs preliminary actions by caching routing information from the central database before it is needed for call routing. The cache stores previously retrieved routing data locally, so when a call needs to be routed, the information is already available without requiring a real-time query to the central database, thus eliminating call completion delays while maintaining routing accuracy.
Solution Approach 2:
The invention creates a local copy of the central database's routing information in a cache memory at the ITSP. This copy contains the same routing data that would be retrieved from the central database, allowing the ITSP to make routing decisions based on the local copy without querying the central database for every call, thereby resolving the contradiction between routing accuracy and call completion speed.
2Adaptability or versatility
If ITSPs maintain access to the large central database, then complete routing information is available, but security risks increase due to potential unauthorized access to subscriber records
Solution Approach 1:
The system extracts only the necessary routing information from the central database and stores it locally in a cache. This extraction process separates the essential routing data from the complete subscriber records, allowing ITSPs to maintain access to routing information while reducing security risks by not having access to the full central database with sensitive subscriber information.
Solution Approach 2:
The invention implements local quality by creating a distributed cache system where each ITSP maintains its own local copy of routing information tailored to its specific needs. This localizes the data storage and access, giving each ITSP only the routing information it requires rather than universal access to the entire central database, thereby enhancing security while maintaining routing capabilities.
3Measurement precision
If the central database is updated frequently to maintain current routing information, then routing accuracy is improved, but the complexity and cost of managing the large database increases
Solution Approach 1:
The system segments the centralized database management into distributed local caches at each ITSP. Instead of one large database that must be managed and updated centrally, the routing information is divided and cached locally at multiple ITSPs. This segmentation reduces the complexity of managing the central database while maintaining routing information currency through independent local updates.
Solution Approach 2:
The local caches are designed to update themselves automatically by periodically retrieving routing information from the central database or through event-driven updates. This self-service mechanism reduces the manual management complexity of the central database, as each local cache independently maintains its own data currency without requiring complex centralized coordination for every update.
Data Source
Figure 1
Figure 2
Figure 3~4
AI summary
A method for telephony includes receiving at a facility of a telephone service provider a first subscriber request to place a first call to a specified telephone number. A provider request is sent to a remote server (26), which maintains a database (28) of records associating telephone numbers with respective packet network addresses, for a record (72) indicating a packet network address to which calls to the specified telephone number should be placed. Upon receiving the record from the remote server, the record is stored in a local cache (42) at the facility of the telephone service provider. After storing the record, upon receiving at the facility of the telephone service provider a second subscriber request to place a second call to the specified telephone number, the record is read from the local cache and is used in placing the second call to the packet network address.