Centralized DNS Database for Network Node Connection Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The introduction of shared account features in cost charging systems complicates system operation and increases overhead by requiring new message signaling pathways and increasing response latency, especially as the system grows, due to the need for network nodes to act as proxies to retrieve shared account records from other nodes.
Innovation Solution
A Domain Name System (DNS) with a centralized database is used to manage network node locations and connections, allowing nodes to interrogate for existing connections and select the best Quality of Service (QoS) path for communication, thereby reducing the need for new signaling pathways and improving response times.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If network nodes act as proxies to retrieve shared account records from other nodes, then shared account features can be supported, but system operation complexity increases and overhead increases
Solution Approach 1:
The patent introduces a centralized database as an intermediary component that stores connection information between network nodes. Instead of nodes acting as proxies to retrieve shared account records, they query the centralized database which maintains a repository of existing connections. This mediator eliminates the need for complex proxy operations while supporting shared account features.
Solution Approach 2:
The centralized database serves multiple functions: it stores connection information, provides lookup services for existing connections, and supports various types of account queries (including shared accounts) through a unified interface. This multi-functional approach reduces system complexity by consolidating what would otherwise require multiple specialized components.
2Adaptability or versatility
If network nodes act as proxies to retrieve shared account records, then shared account access is enabled, but response latency increases
Solution Approach 1:
The system performs preliminary actions by pre-establishing and storing connection information in the centralized database before actual account queries are needed. When nodes need to access shared account records, they can immediately query the pre-populated database for existing connections rather than establishing new connections or routing through proxies, significantly reducing response latency.
Solution Approach 2:
The centralized database acts as a mediator that provides direct access paths to account records. By maintaining a repository of existing connections and providing efficient lookup capabilities, it eliminates the time-consuming proxy retrieval process while enabling shared account access.
3Adaptability or versatility
If new message signaling pathways are created for shared accounts, then account retrieval is possible, but overhead associated with updating connection information increases
Solution Approach 1:
The patent merges the connection information management for all account types (including shared accounts) into a single centralized database. Instead of creating separate message signaling pathways and maintaining separate connection information for shared accounts, the system consolidates all connection data in one repository, reducing the overhead for updating and managing connection information.
Data Source
Figure 1
Figure 2
Figure 3~4
AI summary
Network nodes can add information to a central database (220, 300) that identifies their connections to other network nodes. The central database (220, 300) can thereby serve as a repository of information indicating connections between network nodes. When a first network node (Node 0) needs to establish a session to a second network node (Node 1), it can interrogate the central database (220, 300) to learn what existing connections, if any, can be used for the session. When existing connections provide more than one available pathway between the first and second network nodes (Node 0, Node 1), the first network node (Node 0) may select among the existing connections in response to quality of service values that are provided by the central database (220, 300) for those connections.