Cross-platform framework-independent synchronization abstraction layer

• US 7,404,194 B2
• Filed: 11/21/2003
• Issued: 07/22/2008
• Est. Priority Date: 06/22/1999
• Status: Expired due to Fees

• Current Assignee: MediaPlatform, Inc.
• Original Assignee: Mediaplatofrm On-Demand Incorporated
• Inventors: Mills, Michael, O'Brien, Chris, Wallace, Bruce A., Wason, Andrew
• Primary Examiner(s): An, Meng-Ai
• Assistant Examiner(s): Cao, Diem K
• Application Number:
  US10/719,641
• Publication Number:
  US 20040225994A1
• Time in Patent Office: 1,705 Days
• Field of Search: 717100-123, 719310-320, 719328-332
• US Class Current: 719/328
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04N 21/2381 Adapting the multiplex stream to a specific network, e.g. an Internet Protocol [IP] network transmission of MPEG streams over ATM H04L12/5601
• CPC Class Codes: H04N 21/43072 of multiple content streams on the same device
• CPC Class Codes: H04N 21/4381 Recovering the multiplex stream from a specific network, e.g. recovering MPEG packets from ATM cells transmission of MPEG streams over ATM H04L12/5601
• CPC Class Codes: H04N 21/4431 characterized by the use of Application Program Interface [API] libraries
• CPC Class Codes: H04N 21/4437 Implementing a Virtual Machine [VM] virtual machines in general G06F9/45533
• CPC Class Codes: H04N 21/6125 involving transmission via Internet transmission by internet of broadcast information H04H60/82
• CPC Class Codes: H04N 21/64322 IP
• CPC Class Codes: H04N 21/8193 dedicated tools, e.g. video decoder software or IPMP tool
• CPC Class Codes: H04N 7/52 Systems for transmission of a pulse code modulated video signal with one or more other pulse code modulated signals, e.g. an audio signal or a synchronizing signal assembling of a multiplex stream by combining a video stream with other content or additional data, remultiplexing of multiplex streams, insertion of stuffing bits into the multiplex stream, assembling of a packetised elementary stream at server side H04N21/236; disassembling of a multiplex stream, remultiplexing of multiplex streams, extraction or processing of Service Information, disassembling of packetised elementary stream at client side H04N21/434

Abstract

This invention is a synchronization abstraction layer (SAL) providing a uniform interface to frameworks operating on sequenced flow data. It allows content developers to design and build interactive content that will operate interchangeably in different multimedia frameworks (e.g., Apple Computer, Inc.'"'"'s QuickTime™, Microsoft Corporation'"'"'s NetShow™, RealNetworks, Inc.'"'"'s RealPlayer™, Sun Microsystems, Inc.'"'"'s Java™ Media Framework) and on different hardware platforms (e.g., desktop PC, Macintosh™, Television set-top boxes such as those from General Instrument Corporation and Scientific Atlanta Inc., Inc., Internet appliances such as AOL™-TV, and other appliances, e.g., a kitchen Internet radio). The uniform interface is independent of the particular framework and the platform on which the SAL is implemented, so that a single instance of content, whether created in Java™, JavaScript, VBscript, HTML, XML, or some other language, can run appropriately on different hardware, e.g., on a Television set-top and on a desktop PC.

In one realization, the synchronization abstraction layer provides a Java™ VIRTUAL MACHINE (JVM) interface for running Java™ plug-ins for streaming media applications such as Real Networks, Inc.'"'"'s RealPlayer™, Microsoft Corporation'"'"'s Windows Media Technologies (NetShow™), Apple Computer, Inc.'"'"'s QuickTime™, Sun Microsystems, Inc.'"'"'s Java™ Media Framework. The JVM interface allows third-party developers to design platform- and framework-independent plug-ins for streaming media applications.

This invention allows content providers to use plug-ins or compatible software objects (such as Java™ applets) to build, for example, interactive streaming media content that is fully interactive but independent of the particular underlying hardware and software technologies, such as RealNetworks™ G2, Microsoft Corporation'"'"'s NetShow™, a desktop PC, or a television.

Claims

1. A computer system having at least a processor using an extension layer for extending the functionality of a framework which is separate from an operating system, comprising:

a first framework;

a first access system coupled to said first framework and which interacts with said first framework;

a second framework, different from said first framework;

a second access system coupled to said second framework and which interacts with the second framework;

an extension module;

an extensible abstraction layer framework; and

a coupling system for connecting said extension module to said extensible abstraction layer framework thereby providing access to said extension module;

wherein the extension layer provides a uniform, cross-platform, framework-independent interface between said first and second frameworks and said extension module.

2. The computer system of claim 1 further comprising:

a synchronization system for synchronizing data from said extension module.

3. The computer system of claim 2 further comprising:

a communication system allowing for the transfer of data or instructions between said extension module and said extensible abstraction layer framework.

4. A computer system having at least a processor using an extension layer for accessing and using an ordered file, comprising:

a first extensible ordered-data flow-based framework;

a second extensible ordered-data flow-based framework which is not identical to said first extensible ordered-data flow-based framework;

an extensible ordered-data flow-based abstraction layer framework;

an extension module for an extensible ordered-data flow-based abstraction layer framework containing ordered data;

an abstraction layer having a uniform cross-platform interface between said extension module and said extensible ordered-data flow-based framework, said abstraction layer being separate from an operating system; and

a synchronization module for handling data flowing between the extension module and the extension layer;

wherein the extension layer provides a uniform, cross-platform, framework-independent interface between the first and second frameworks and the extension module.