Cache Server Streaming Media Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current streaming media processing technologies face challenges in ensuring real-time processing and diversity of video streaming, particularly in 4G and 5G environments, where delays occur and third-party plug-ins cannot process streaming media data in real time, making it impossible to meet timeliness and diversity requirements.

Innovation Solution

A method involving a cache server that uses a cache dictionary with a management data pool and link list to cache and manage streaming media data, establishing connections between clients and the cache server, and pushing target streaming media data to clients efficiently, utilizing co-routines and JSON character strings for connection requests and data transmission.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If streaming media data is processed in real-time with high-resolution video, then video quality is improved, but delay occurs

Engineering Contradiction:
Improvevideo qualityVSAvoiddelay
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The system pre-establishes multiple connection types (pushing connection, subscription connection, plug-in connection) and caches streaming media data in advance in the cache server. This preliminary preparation allows the system to quickly retrieve and deliver pre-processed high-resolution video data without real-time processing delays, thus maintaining video quality while reducing delay.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If third-party plug-in ends process streaming media data, then diversity of video processing is improved, but real-time processing capability deteriorates

Engineering Contradiction:
Improvediversity of video processingVSAvoidreal-time processing capability
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system segments the processing architecture by introducing a dedicated cache server that handles data storage and management separately from the plug-in ends that handle processing. The cache server pre-processes and caches video data in multiple formats, allowing plug-in ends to access pre-processed data without performing heavy real-time processing, thus maintaining both diversity and real-time capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The cache server acts as an intermediary between the pushing end and plug-in ends. It receives streaming media data, caches it in multiple formats, and provides quick access to plug-in ends. This intermediary structure allows diverse processing operations while maintaining real-time performance by eliminating the need for plug-in ends to perform heavy real-time processing.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If multiple connection types are established for different clients, then adaptability is improved, but system complexity increases

Engineering Contradiction:
ImproveadaptabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The cache server implements a universal architecture that handles multiple connection types (pushing, subscription, plug-in) through a unified data structure and management mechanism. The sequence list and link list provide a universal framework for managing different connection types, allowing the system to support diverse client needs without proportionally increasing complexity through standardized multi-functional design.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11621987B2Method for processing streaming media data
Publication Date: 2023.04.04 BOE TECHNOLOGY GROUP CO LTD
  • US11621987B2 patent drawing
  • US11621987B2 patent drawing
  • US11621987B2 patent drawing

AI summary

A method for processing streaming media data includes: receiving the streaming media data, and caching the streaming media data at a cache server in accordance with a cache dictionary; establishing a connection between a client and the cache server, and determining target streaming media data corresponding to the client, the client including a plug-in end and a subscription end; and pushing the target streaming media data to the client.