Streaming Media Management Component for RTP Protocol Handling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The OpenMAX IL API lacks direct support for streaming media content delivered over real-time network transport protocols like RTP, leading to issues with playback, recording, and synchronization, particularly with RTSP and RTP protocols, which are not integrated into the OpenMAX framework, resulting in limitations such as inability to perform seeking, pause, and control streaming sessions effectively.

Innovation Solution

An electronic device with a multimedia framework that includes a streaming media management component within the integration layer, which configures and manages content pipes to access packets according to real-time network transport protocols, maps content pipes to sockets, and processes packets to provide media content to media processing components, enabling seamless playback of streaming media content.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the OpenMAX IL API is used to process streaming media content delivered over real-time network transport protocols, then media content can be processed through predefined media processing components, but the API lacks direct support for RTSP and RTP protocols, resulting in inability to perform seeking, pause, and control streaming sessions effectively

Engineering Contradiction:
Improveprotocol supportVSAvoidstreaming control capability
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces an RTSP application layer component as an intermediary between the OpenMAX IL API and the RTSP/RTP protocols. This intermediary translates RTSP control commands into operations that the OpenMAX IL framework can handle, enabling seeking, pausing, and other streaming controls without modifying the core OpenMAX IL API. The intermediary layer handles protocol-specific operations while the underlying OpenMAX IL components continue to process media content as before.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If content pipes are configured to access packets according to real-time network transport protocols, then streaming media content can be accessed, but the content pipes or media components would need to process these protocols directly, increasing complexity

Engineering Contradiction:
Improvestreaming media access efficiencyVSAvoidprotocol processing complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent extracts protocol processing functionality from the content pipes and media processing components by introducing a dedicated RTSP application layer. This layer handles all RTSP/RTP protocol-specific operations including packet access, synchronization, and control commands, allowing the content pipes and media components to remain protocol-agnostic. The extraction reduces complexity in the media processing path while maintaining efficient streaming media access through the specialized RTSP layer.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentEP2223492B1Real-time network transport protocol interface method and apparatus
Publication Date: 2015.04.15 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • EP2223492B1 patent drawingFigure 1
  • EP2223492B1 patent drawingFigure 2
  • EP2223492B1 patent drawingFigure 3

AI summary

An electronic device has a multimedia framework including an integration layer and a higher-level application layer. The integration layer includes predefined media processing components having an input/output interface configurable based on the type and format of media content delivered to the device during a streaming media session and that provide predefined media processing functions to the application layer for enabling playback of the media content. A streaming media management component included in the integration layer establishes and manages the streaming media session and configures one or more content pipes used during the streaming media session to access packets received by one or more sockets. The component also maps the content pipes to the sockets and processes packets retrieved from the one or more content pipes such that the media content is provided to corresponding ones of the predefined media processing components in accordance with their configured input/output interfaces.