DNS Anchor Mechanism for Video Server Affinity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing adaptive streaming technologies face challenges in maintaining continuous video delivery during server saturation, leading to user experience issues like re-buffering and increased response times due to frequent server changes and the limitations of cookie-based sticky routing mechanisms, which are not scalable and incompatible with all devices.
Innovation Solution
A DNS-based request routing mechanism that modifies the domain name by adding an anchor identifier, allowing the DNS to consistently return the same server IP address during a video session without relying on cookies, enabling load balancing while maintaining the same server for ongoing sessions even when congested.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If load balancing mechanisms are used to distribute video streaming requests across multiple servers, then server capacity utilization is improved, but server stability during video sessions deteriorates due to frequent server changes
Solution Approach 1:
The patent applies preliminary action by establishing server affinity at the beginning of a video session through DNS resolution. The system determines the optimal server for a client device before the video session starts and maintains this assignment throughout the session. This preliminary server selection prevents frequent server changes during playback, resolving the contradiction between load balancing and server stability.
Solution Approach 2:
The patent introduces DNS (Domain Name System) as an intermediary between the client device and video servers. The DNS system acts as a mediator that translates domain names to IP addresses while maintaining server affinity information. This intermediary layer enables load balancing across multiple servers while preserving stable server assignments during video sessions, as the DNS system manages the mapping without requiring direct client-server negotiation.
2Stability of the object's composition
If cookie-based sticky routing is used to maintain the same server during video sessions, then server stability is improved, but device compatibility deteriorates due to lack of cookie support in some devices
Solution Approach 1:
The patent replaces cookie-based sticky routing with DNS-based server affinity as an intermediary mechanism. Instead of relying on client-side cookies that require device support, the system uses DNS as a universal intermediary that all devices can communicate with. The DNS system maintains server affinity information and returns consistent IP addresses for the same domain name, achieving server stability without requiring cookie support in client devices.
Solution Approach 2:
The patent substitutes the mechanical cookie-based approach with a DNS-based resolution mechanism. Cookies require specific client software support and state management, while the DNS system provides a standardized, protocol-level solution that works across all HTTP-compatible devices. This substitution replaces a client-dependent mechanism with a network-layer solution that is universally compatible.
3Productivity
If servers are allowed to reject new connections during saturation, then server performance is improved, but user experience deteriorates due to re-buffering and increased response times
Solution Approach 1:
The patent applies preliminary action by establishing server affinity through DNS resolution before the video session begins. When a server becomes saturated, clients with established affinity continue to receive responses from their assigned servers, preventing the avalanche effect. This preliminary assignment ensures that during high demand, servers can manage their capacity without forcing clients to reconnect, thereby maintaining user experience while allowing servers to operate at their limits.
Data Source
Figure 1
Figure 2
Figure 3a
AI summary
Method, system and devices for maintaining the same server during a multimedia (e.g. video) communication session. The proposed solution modifies the domain name adding an anchor, usually during request routing redirections; this anchor enables to the request router to return the same server IP address for any domain resolution during a player video session, solving the problems found in prior art techniques.