ENUM Data Collision Resolution via Virtual IP Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current ENUM systems in IMS networks experience data collisions due to sending duplicate phone number records to different ENUM complexes, leading to failures in IMS services, as these collisions cannot be automatically resolved and require manual intervention.
Innovation Solution
Implementing a system that distinguishes between query and provisioning packets and directs them to specific Virtual IP addresses of ENUM DNS and LDAP servers, ensuring that only one LDAP server is updated at a time to prevent data collisions and allow for automatic resolution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If ENUM systems send duplicate phone number records to different ENUM complexes for redundancy, then system reliability is improved, but data collisions occur causing IMS services to fail
Solution Approach 1:
The patent segments the ENUM system into distinct components: a load balancer that receives provisioning requests, an ENUM complex with multiple LDAP servers, and a DNS server. The load balancer segments the provisioning process by directing requests to specific LDAP servers based on collision detection, preventing duplicate records from being sent to multiple ENUM complexes simultaneously.
Solution Approach 2:
The patent implements feedback mechanisms where the load balancer monitors provisioning requests and detects potential data collisions before they occur. When a collision is detected (e.g., two simultaneous updates to the same phone number record), the load balancer adjusts the provisioning direction to prevent the harmful effect, ensuring only one LDAP server receives the duplicate record.
2Reliability
If manual intervention is used to resolve data collisions, then data consistency is maintained, but system productivity decreases due to operational delays
Solution Approach 1:
The patent enables the ENUM system to resolve data collisions automatically without manual intervention. The load balancer performs self-monitoring and self-correction by detecting duplicate provisioning requests and redirecting them to appropriate LDAP servers, allowing the system to maintain data consistency while continuing operational processes without human intervention.
Solution Approach 2:
The patent takes preliminary action by having the load balancer monitor and detect potential data collisions before they are written to the LDAP servers. By identifying duplicate provisioning requests in advance and redirecting them preventively, the system avoids the need for post-collision manual resolution, maintaining both data consistency and productivity.
3Adaptability or versatility
If multiple LDAP servers are updated simultaneously for high availability, then system scalability is improved, but data collisions increase causing service failures
Solution Approach 1:
The patent introduces dynamic control to the static LDAP server architecture. The load balancer dynamically adjusts provisioning request directions based on real-time collision detection. When multiple LDAP servers are updated simultaneously and conflicts are detected, the load balancer dynamically redirects subsequent requests to avoid colliding records, allowing high availability while preventing service failures.
Data Source
AI summary
An example method involves, when telephone number mapping data packets are query packets, sending the query packets to a virtual Internet protocol address of a telephone number mapping domain name system server; when the telephone number mapping data packets are provisioning packets, sending the provisioning packets to a virtual Internet protocol address of a telephone number mapping lightweight directory access protocol server; and waiting and sending traffic to one lightweight directory access protocol server at a time.