Multimedia Content Delivery via Segmented Edge Servers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The rapid growth of data traffic in multimedia services over broadcasting networks leads to issues such as server overload and access speed delays, necessitating efficient traffic management and content delivery solutions.
Innovation Solution
A method and apparatus utilizing the MPEG Media Transport Protocol (MMTP) for content distribution, where a terminal receives content-related information and allocates resources by sending DNS query messages to an IP providing DNS server, which responds with necessary IP addresses, port information, and media information to optimize content delivery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If content delivery is centralized at a single center server, then system complexity is reduced, but server overload and access speed delays occur due to rapid growth of data traffic
Solution Approach 1:
The patent segments the centralized content delivery system into a hierarchical structure with center servers and multiple edge servers. Content is divided and distributed across these segmented server nodes, allowing parallel processing of data traffic. This segmentation resolves the contradiction by maintaining manageable system complexity through modular architecture while significantly improving productivity through distributed content delivery capacity.
Solution Approach 2:
The patent introduces a spatial dimension to content delivery by deploying edge servers at multiple geographic locations closer to terminals. This dimensional expansion allows content to be delivered from nearest available edge server, reducing access delays and distributing traffic load across multiple spatial nodes, thereby improving productivity without proportionally increasing system complexity.
2Productivity
If edge servers are added to distribute content processing, then server overload is reduced, but data traffic management complexity increases for each edge server
Solution Approach 1:
The patent introduces DNS servers as intermediary components that mediate between terminals and edge servers. The DNS server receives content delivery requests, determines the appropriate edge server based on terminal location and server status, and redirects requests accordingly. This intermediary simplifies traffic management complexity for individual edge servers while maintaining high content delivery capacity through intelligent request routing.
Solution Approach 2:
The patent implements feedback mechanisms where edge servers report their status (load, availability) to DNS servers, which then adjust request routing dynamically. This feedback loop allows the system to automatically balance traffic distribution across edge servers, reducing manual traffic management complexity while optimizing content delivery capacity based on real-time server conditions.
3Productivity
If DNS query messages include detailed media information, then resource allocation is optimized, but message size and processing overhead increase
Solution Approach 1:
The patent extracts detailed media information from the main DNS query/response flow and places it in separate TXT record fields. This extraction allows the DNS protocol to maintain its standard compact structure while still conveying necessary resource allocation information through standardized TXT records, thereby optimizing resource allocation without significantly increasing message size or processing overhead.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The present disclosure relates to a method and device for receiving a content by a terminal device. The method for receiving a content by a terminal device comprises the steps of: transmitting a query message requesting content-related information to a first server; receiving a response message including the content-related information from the first server; on the basis of the response message, requesting a content from a second server corresponding to the content-related information; and receiving the content from the second server, wherein the content-related information includes internet protocol (IP) addresses of the second server, pieces of port information, and pieces of media information relating to a content.