Modular RTP Streaming Architecture Reducing Integration Complexity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current multimedia systems face challenges in reusing common components across applications due to the need for substantial time and effort in customizing independent modules, leading to increased development time and costs, and complexities for system designers.

Innovation Solution

A modular, reusable, and extensible architecture for RTP streaming systems is developed, comprising standalone modules like RTP, RTCP, and AJB, with well-defined APIs, allowing for easy configuration and integration, reducing system development and integration efforts by 30-50% compared to traditional approaches.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If independent modules with generic APIs are developed for reusability, then component reusability is improved, but system designer complexity and customization time increase

Engineering Contradiction:
Improvecomponent reusabilityVSAvoidsystem designer complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a framework layer as an intermediary between independent modules and the final application. This framework provides pre-built integration logic, configuration management, and coordination mechanisms that mediate between reusable components, eliminating the need for system designers to manually tie modules together and reducing integration complexity

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The framework is designed with universal, application-agnostic interfaces and configuration mechanisms that can accommodate multiple different multimedia applications. By creating a multi-functional framework that handles common integration patterns, the system enables broad component reusability across diverse applications without increasing designer complexity

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

2Adaptability or versatility

If independent modules are customized for each application, then application-specific functionality is improved, but development time and costs increase

Engineering Contradiction:
Improveapplication-specific functionalityVSAvoiddevelopment time
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system segments functionality into three distinct layers: reusable independent modules, a configurable framework, and application-specific configurations. This segmentation allows developers to reuse core modules across applications while only customizing the framework configuration and application layer, dramatically reducing development time for application-specific functionality

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The framework performs preliminary integration work by providing pre-configured module interfaces, connection templates, and coordination logic. By doing the heavy lifting of module integration in advance through the framework, developers don't need to perform time-consuming customization for each application, thus improving productivity

Inventive Principle:
Principle #10Preliminary action

3Manufacturing precision

If detailed knowledge of each module is required for integration, then integration precision is improved, but ease of operation deteriorates

Engineering Contradiction:
Improveintegration precisionVSAvoidease of integration
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The framework acts as an intermediary that abstracts away the need for detailed module knowledge. It provides standardized interfaces and configuration mechanisms that handle the complex integration details internally, allowing developers to integrate modules without needing to understand their internal workings, thus improving ease of operation while maintaining integration precision

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8307118B2Architecture, system and method for an RTP streaming system
Publication Date: 2012.11.06 ITTIAM SYST P
  • US8307118B2 patent drawing
  • US8307118B2 patent drawing
  • US8307118B2 patent drawing

AI summary

An architecture, system and method for an RTP streaming system is disclosed. In one embodiment, a method includes developing multiple standalone modules, developing application programming interfaces associated with the standalone modules, and tying together the standalone modules to form a subsystem associated with a streaming application and with a network. The method further includes integrating standalone modules including an RTP module, an RTCP module and a payload interface, associated with any one of a server mode and a client mode. The method also includes managing a streaming session associated with media streams via an RTPSS manager, adding the media streams to a stream manager. For each media stream of the streaming session: the method includes performing packetization services in the server mode and de-packetization services in the client mode, and performing server-mode related services in the server mode and client-mode related services in the client mode.