Central Node Channel Verification for CDN Stream Pushing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current live broadcast technologies in CDNs face internal flow consumption and server resource waste due to overlapping stream-pushing requests, where edge nodes continue to push data after being denied, leading to inefficient resource utilization.
Innovation Solution
A method and system where a central node determines if a stream-pushing request corresponds to an existing channel, sending a prompt message or establishing a new channel, and edge nodes forward-push requests to a target central node based on channel names using a hash algorithm to ensure uniqueness and avoid repeated requests.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple edge nodes forward-push the same stream-pushing request to different central nodes, then the system can handle multiple stream pushers, but internal flow consumption and server resource waste occur due to repeated channel establishment attempts
Solution Approach 1:
The system performs preliminary channel existence verification at the central node before establishing new channels. When a central node receives a stream-pushing request, it first checks whether the channel already exists. This preliminary action prevents repeated channel establishment attempts and the associated resource waste while maintaining the ability to handle multiple stream pushers through proper request routing and verification.
2Adaptability or versatility
If the central node establishes a new channel for each incoming stream-pushing request, then all stream pushers can be accommodated, but server resources are wasted when duplicate channels are created for the same URL
Solution Approach 1:
The central node implements a feedback mechanism by verifying whether a channel already exists before creating a new one. When a stream-pushing request arrives, the central node checks its existing channels, and only creates a new channel if one with the same URL does not already exist. This feedback-based approach ensures that server resources are not wasted on duplicate channel creation while maintaining the ability to accommodate multiple unique stream pushers.
3Reliability
If edge nodes continuously attempt to push after being denied, then they ensure data delivery, but internal flow consumption increases and resource efficiency decreases
Solution Approach 1:
The system performs preliminary verification at the central node to determine channel existence before allowing push operations. This preliminary action prevents edge nodes from continuously attempting to push denied requests, as the central node proactively identifies and handles duplicate requests. The result is maintained data delivery reliability for legitimate requests while eliminating wasteful continuous retry attempts that reduce resource efficiency.
Data Source
Figure 1
Figure 2~3
Figure 4~5
AI summary
A method, a system and a server for stream-pushing are provided. In the stream-pushing method, a central node receives a stream-pushing request forward-pushed by an edge node, and determines whether the stream-pushing request corresponds to an existing channel. When a determination result is yes, the central node sends a prompt message to the edge node; or, when the determination result is no, the central node establishes one channel for the stream-pushing request and receives streaming media data corresponding to the channel. According to an example, internal flow consumption and server resource waste of a CDN can be avoided and the stream-pushing efficiency can be improved.