Media Server Automatic Multi-Destination Stream Publishing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content creators face the manual and time-consuming process of configuring where and how to publish video or audio streams, lacking an automated solution for simultaneous publication to multiple destinations.
Innovation Solution
A media server equipped with a push publishing module and a publishing map that automatically identifies matching stream names and publishes streams to corresponding destinations, supporting multiple protocols and adaptive streaming, enabling simultaneous publication to multiple destinations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If manual configuration is used for publishing streams, then flexibility and control over publishing destinations are improved, but time consumption and operational complexity increase
Solution Approach 1:
The system pre-configures publishing destinations and criteria in a publishing map before streams arrive. When a stream is received, the system automatically matches it against pre-defined criteria in the publishing map and publishes to appropriate destinations without manual intervention, thus resolving the time consumption issue while maintaining configuration flexibility through the pre-set publishing rules
Solution Approach 2:
The publishing system performs self-service by automatically matching incoming streams with appropriate destinations based on pre-configured criteria. The system independently determines which destinations to publish to without requiring manual configuration for each stream, eliminating repetitive manual work while maintaining control through the publishing map
2Productivity
If automatic publishing is implemented, then time consumption and operational complexity are reduced, but system complexity and configuration requirements increase
Solution Approach 1:
The publishing map serves as an intermediary component that decouples the stream reception logic from the publishing destination logic. It stores pre-configured matching criteria and destination information, allowing the system to automatically match streams to destinations without complex real-time decision-making, thus improving productivity while managing system complexity through this intermediate data structure
Solution Approach 2:
The publishing system is segmented into distinct functional components: stream reception, criteria matching, and destination publishing. The publishing map itself is segmented into individual entry structures, each handling specific matching criteria and destination configurations. This segmentation allows each component to be independently managed and configured, reducing overall system complexity while enabling efficient automatic publishing
3Adaptability or versatility
If multiple streams are published to multiple destinations simultaneously, then content distribution capability is improved, but system resource consumption and processing load increase
Solution Approach 1:
The system implements partial action by matching each incoming stream against only the relevant criteria in the publishing map and publishing to only the appropriate destinations that match the stream characteristics. Rather than publishing all streams to all possible destinations, the system performs selective partial publishing based on criteria matching, thus enabling multi-destination capability while reducing unnecessary resource consumption
Data Source
AI summary
Systems and methods of automatically publishing a stream to multiple destinations are disclosed. A media server receives a stream and identifies a plurality of entries in a publishing map stored at the media server, where the each of the plurality of entries is associated with the stream. A first entry of the plurality of entries identifies a first publishing destination and a second entry of the plurality of entries identifies a second publishing destination that is different from the first publishing destination. The media server automatically publishes the stream to the first publishing destination and to the second publishing destination.


