Live Streaming Content Segmentation for CDN Efficiency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current live streaming technologies over communication networks focus on maintaining continuous data flow, which is costly and complex, whereas there is a need for a more efficient method that can deliver live content using existing Internet protocols and leverage established technologies.

Innovation Solution

Converting live streams into a sequence of static files that can be individually requested and delivered using FTP and HTTP protocols, allowing for 'pull' based delivery and leveraging existing CDN infrastructure, enabling flexible viewing and reduced costs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If continuous live streaming is implemented using dedicated CDN infrastructure, then real-time content delivery is achieved, but system complexity and cost increase significantly

Engineering Contradiction:
Improvereal-time content deliveryVSAvoidCDN infrastructure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates static file copies of live stream content at CDN edges, allowing users to retrieve content from cached copies rather than maintaining continuous live stream connections. This copying approach eliminates the need for complex live streaming infrastructure while delivering content efficiently.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

Instead of pushing live streams continuously to users, the patent inverts the approach by having users pull static file copies from CDN edges. This inversion transforms the complex push-based live streaming model into a simple pull-based file retrieval model.

Inventive Principle:
Principle #13The other way round (Inversion)

2Loss of energy

If static file delivery is used instead of continuous streaming, then infrastructure cost is reduced, but continuous playback experience may be affected

Engineering Contradiction:
Improveinfrastructure costVSAvoidcontinuous playback experience
Core Design Contradiction:
Loss of energyVSReliability

Solution Approach 1:

The patent segments live stream content into discrete static files that can be individually cached and delivered. By dividing the continuous stream into segments, the system reduces infrastructure costs while maintaining playback continuity through sequential file delivery.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary encoding and file creation of stream content before delivery. By pre-processing content into static files that can be cached in advance, the system enables cost-effective delivery while ensuring content is ready for immediate playback without requiring continuous streaming infrastructure.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If live streams are converted to static files, then existing Internet protocols can be leveraged, but stream continuity is broken

Engineering Contradiction:
Improveprotocol compatibilityVSAvoidstream continuity
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent changes the fundamental parameter of content delivery from continuous dynamic streaming to discrete static file transfer. This parameter change enables the use of standard Internet protocols like HTTP and FTP while maintaining user experience through sequential file delivery that reconstructs the continuous stream.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS9654301B2Method, system and software product for streaming content
Publication Date: 2017.05.16 VIVIDAS TECH
  • US9654301B2 patent drawing
  • US9654301B2 patent drawing
  • US9654301B2 patent drawing

AI summary

The present invention relates to methods and systems for streaming content and in particular, live content. The method includes the steps of: receiving a content stream; periodically encoding the received stream into a sequence of content files to thereby create a plurality of sequential content files; assigning a sequence identifier to each content file; storing the files on a host; delivering a data file to a media player responsive to a request for live content, said data file including information enabling the media player to sequentially and individually request each content file from the host and play the requested content file; and delivering requested content files responsive to each request.