Gateway Application for RTSP Request Multiplexing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional techniques for controlling streaming data transmission are limited in supporting multiple types of server applications simultaneously, leading to issues like port conflicts, request dispatching challenges, transparency problems, and redundant processing, which restrict a content engine's ability to service diverse RTSP-based requests efficiently.
Innovation Solution
A gateway application is introduced in the content engine to process and dispatch RTSP-based requests, allowing multiple types of servers to operate simultaneously by identifying client properties and forwarding requests to the appropriate servers, thereby bypassing port conflicts and redundant processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple types of server applications operate simultaneously on a single content engine, then the adaptability and versatility of the content engine is improved, but port conflicts and request dispatching challenges arise
Solution Approach 1:
A gateway application is introduced as an intermediary component between external RTSP requests and multiple backend server applications. The gateway receives RTSP requests, identifies the appropriate server type based on request properties, and forwards requests to the correct server. This mediator approach allows multiple server types to coexist without direct conflicts while maintaining a unified entry point.
Solution Approach 2:
The system architecture is segmented into distinct functional components: the gateway application handles request routing and protocol management, while multiple specialized server applications handle specific streaming tasks. This segmentation allows each component to operate independently with well-defined interfaces, reducing complexity despite supporting multiple server types.
2Productivity
If a gateway application processes and dispatches requests, then redundant processing is minimized and performance is enhanced, but the gateway must identify client properties and manage request routing
Solution Approach 1:
The gateway application performs preliminary analysis of incoming RTSP requests by examining client properties and request characteristics before forwarding to backend servers. This preliminary action enables intelligent routing decisions and prevents unnecessary processing by the wrong server type, improving overall efficiency while centralizing the complexity of property identification in the gateway.
Solution Approach 2:
The gateway application serves multiple functions: it acts as an RTSP protocol handler, a request router, a client property analyzer, and a coordinator between clients and multiple server types. This multi-functional design consolidates various responsibilities in a single component, improving productivity while managing complexity through a unified interface.
3Speed
If servers establish direct links with requesting users to bypass the gateway port, then data transmission efficiency is improved, but the gateway can no longer process all data flow
Solution Approach 1:
The patent extracts the high-volume data streaming traffic from the gateway application by establishing direct links between backend servers and requesting users. Only control plane traffic (RTSP requests and responses) continues to flow through the gateway, while data plane traffic bypasses the gateway directly. This extraction improves transmission speed by removing the gateway as a bottleneck for data flow while maintaining gateway control over session management.
Data Source
AI summary
A gateway application in a content engine multiplexes requests for real-time content to servers that, in turn, service the requests by streaming appropriate real-time content to requesting users. A software communication port of the content engine may be reserved to receive request messages from multiple client computers, at least two of which request streaming of real-time content according to different selected formats. After identifying client properties (e.g., a format for which to receive streaming real-time content) associated with the requests for real-time content, the gateway application identifies corresponding servers of the content engine to serve the real-time content according to the different selected formats. The gateway application forwards the requests for streaming of real-time content associated with the request messages to the corresponding servers which, in turn, satisfy the requests by streaming the requested real-time content to the client computers.