Source: http://www.google.com/patents/US7979886?dq=6978253
Timestamp: 2014-12-22 07:50:56
Document Index: 651253255

Matched Legal Cases: ['art 3', 'art 3', 'art 3', 'art 12', 'art 12', 'art 3', 'art 3', 'art 3', 'art 1', 'art 3', 'art 1', 'art 10', 'art 10', 'art 2', 'art 2', 'art 3', 'art 3', 'art 4', 'art 4', 'art 5', 'art 6', 'art 7', 'art 7', 'art 8', 'art 8', 'art 9', 'art 2', 'art 2']

Patent US7979886 - Container format for multimedia presentations - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsIn a method for transmitting a multimedia presentation comprising a number of media objects: the media objects are organized in a multimedia container or container format; identifiers referring to the media objects are organized in the same container; and an identifiable file coordinating the media objects...http://www.google.com/patents/US7979886?utm_source=gb-gplus-sharePatent US7979886 - Container format for multimedia presentationsAdvanced Patent SearchPublication numberUS7979886 B2Publication typeGrantApplication numberUS 10/963,771Publication dateJul 12, 2011Filing dateOct 14, 2004Priority dateOct 17, 2003Also published asUS8555329, US20050086582, US20110314176Publication number10963771, 963771, US 7979886 B2, US 7979886B2, US-B2-7979886, US7979886 B2, US7979886B2InventorsPer Frojdh, Torbjorn Einarsson, Magnus WesterlundOriginal AssigneeTelefonaktiebolaget Lm Ericsson (Publ)Export CitationBiBTeX, EndNote, RefManPatent Citations (18), Non-Patent Citations (42), Referenced by (3), Classifications (9), Legal Events (2) External Links: USPTO, USPTO Assignment, EspacenetContainer format for multimedia presentationsUS 7979886 B2Abstract In a method for transmitting a multimedia presentation comprising a number of media objects: the media objects are organized in a multimedia container or container format; identifiers referring to the media objects are organized in the same container; and an identifiable file coordinating the media objects is also provided in the container.
TECHNICAL FIELD The present invention relates to media objects in general, specifically to multimedia presentations including coordinated media objects.
BACKGROUND Multimedia can be of many different types, e.g. video, audio, still images, vector graphics. Typically, each kind of media has a native file format, depending on the format of the media, for storage in computer systems.
SUMMARY An object of the present invention is to enable improved transmission of multimedia presentations.
It is yet another specific object of the present invention to provide a solution including information for decryption of individual files, media tracks, the full data box (�mdat�) or parts thereof.
DETAILED DESCRIPTION The present invention will be described in the context of extending the prior art 3GPP file format (3GP) to a general container format for multimedia presentations. The invention may, however, be embodied in many different forms and should not be construed as limited to the examples and embodiments set forth herein. Rather, these examples and embodiments are provided so that this disclosure will be thorough, and will convey the invention to those skilled in the art.
The common denominator in the conventional art is that the content of a 3GP file is timed�a 3GP file contains one or more parallel tracks of timed multimedia or hints. Each track is divided into individually accessible time units that make synchronization and random access feasible. Of all the media types that can constitute a presentation in MSS or a session in PSS, 3GP files can only early audio, video and timed text.
1) It must be clear where the starting point is (e.g. the name or location of the SMIL file). 2) Content creators need to deliver several files or objects with dependencies to operators. This can cause problems as it involves many files that also need to be stored in a certain way to preserve their dependencies. If one file is missing, the presentation may not be possible to use at all. Therefore, it would be advantageous to be able to gather all media objects of a multimedia presentation in one container 3) Users need to handle several files instead of one �item�. It has been identified as problematic to move or send several files to a peer and still keep the relative structure between the files. 4) The timing for requesting several files may be problematic as they may be of different size and span different time ranges. An interleaved file format that allows for media prepared for timely delivery is lacking. Moreover, the client would need to know, given a transport bandwidth, how much to download in bytes or seconds, before playback is started (in order to avoid interruptions). In addition to multimedia that is carried by 3GP files there are a number of media types in PSS that are stored in their native file formats: still images (JPEG), bitmap graphics (GIF and PNG), vector graphics (SVG), synthetic audio (SP-MIDI) and text (XHTML and SMIL). As only audio and video are streamed in a PSS session, these media types must be delivered file-by-file via HTTP to a PSS client in conventional art.
An encryption mechanism is also needed that can reveal the content types �in the clear� for encoded content.
The File-directory profile (branded �3gd6�) is defined for 3GP files that include a file directory. Files conforming to the File-directory profile shall include a File tree with one or more file entries. One of these may be a start file, i.e. contain a scene description for the presentation or streaming session.
The File-directory profile is a 3GP profile and should be used with the file extension �0.3gp�.
A file directory for storage of binary files is normally included at the top level of an extended 3GP file. The tree looks like a normal directory and can include any type of binary file and/or sub directories. The file directory is stored as meta-data in the File-tree box, whereas the binary content of the included files is stored as chunks in the Media-data box �mdat� of the containing file.
The File-tree box �ftre� is a container box. It is a top-level box and shall be located after the File-type box �ftyp� in a 3GP file and preferably before the Movie box �moov�. (See FIG. 8) In order to allow for future revisions, the File-tree box is based on a so-called Full box with version number, as shown in Table 1.
�ftre�
The File-tree box defines the root level of the 3GP file tree. A hierarchy of Directory boxes �diry� defines lower levels of the file tree. Directory boxes according to Table 2 below are contained in the File-tree box or other Directory boxes.
�diry�
Each directory box can be required to contain one Directory-name box �dirn� according to Table 3:
�dirn�
A file in the file tree is defined by a File-entry box �fent�, that can be stored at any level in the file tree, including the root level. The File entry box is a container box and is defined below in Table 4.
�fent�
Each File entry box is preferred to include a File-info box �finf� and a Chunk-info box �chin�, as defined below in Table 5 and Table 6.
�finf�
File name and Content type can be null-terminated strings in UTF-8 characters. Content type should be the MIME type for the file. Content encoding is an optional null-terminated string used to indicate that the file stored within the 3GP file is encoded, and needs to be decoded before interpreted, similar to Content-Encoding for HTTP 1.1. Some possible values are �gzip�, �compress�, �deflate�, but for interoperability reasons, the only entry to be used is referred by �gzip�.
�chin�
[ChunkOffset, ChunkSize]�N
int(64)[2�N]
The actual content of an included file can be stored as one or more continuous fragments (i.e. chunks, extents) of data in the media-data box �mdat�. ChunkOffset is a 64 bit integer that gives the offset of the start of the chunk into the containing 3GP file and ChunkSize is a 64 bit integer that gives the size of the chunk, i.e. the length of the file defined by the File-entry box. Note that the chunk offset always refers to the containing file, i.e. the 3GP file. We have refrained from using a Data-reference box to indicate possible external locations of the data, as the point of including binary files in a 3GP file is to have a self-contained file.
�sloc�
An extended 3GP file may contain one Progressive-download information box �pdin� located in the File-tree box, as defined below in Table 8:
�pdin�
[Rate, InitialDelay]�N
int(32)[2�N]
set the Content-Type to the value of the file entry box, set the Content-Location to the URI of the binary file within the 3GP file. As an example, the 3GP file in FIG. 8 with hint tracks included may contain a PSS session. When the client accesses the SMIL file over HTTP, it also receives the Content-Location of the SMIL file, e.g. �http://mediaportal/show.3gp/�. All HTTP references within the SMIL file will then be based upon the Content-Location, enabling HTTP GET to refer to binary files within the 3GP file.
<image src=�cat.jpg� dur=�3s�/>
<image src=�dog.jpg� dur=�5s�/>
�http://www.example.com/exampledir/show.3gp/img/start.smil�, which when the processing of the SMIL file is performed will result in that the resolved HTTP URIs: �http://www.example.com/exampledir/show.3gp/img/cat.jpg� �http://www.example.com/exampledir/show.3gp/img/dog.jpg�
One way to signal encrypted media in a 3GP file is to define and use an Encryption profile (branded �3ge6�) Further details on the kind of file that is encrypted is given by other brands, such as a Basic profile brand for download of audio/video presentations or Streaming-server profile for serving of encrypted content.
The Encrypted-basic profile is a 3GP profile and should be used with the file extension �0.3gp�.
The principle behind storing encrypted media in a track is to �disguise� the original sample description entry with a generic code point for encrypted media. We define three code points (four-character codes of the sample description entries) for signalling encrypted video, audio and text as follows in Table 9:
The �encrypted� versions of the sample descriptions replicate the original sample descriptions and include a protection information box with details on the original format as well as all requirements for decrypting the encoded media. The EncryptedVideoSampleEntry and the EncryptedAudioSampleEntry are defined in Table 10 and Table 11, where TheProtectionInfo box is simply added to the list of boxes contained in a sample entry.
�encv�
�enca�
TABLE 12 EncryptedTextSampleEntry Field Type Details Value BoxHeader.Size Unsigned int(32) BoxHeader.Type Unsigned int(32) �enct� All fields and boxes of TextSampleEntry. ProtectionInfoBox Box with information on the original format and encryption Key Management
�sinf�
�frma�
DataFormat identifies the format (codec) of the decrypted, encoded data. The currently defined formats in 3GP files include �mp4v�, �h263�, �mp4a�, �samr�, sawb� and �3gtt�.
�schm�
�schi�
Scheme type: �odrm� Scheme version: 0 Scheme-specific boxes: OMADRMSampleFormatBox and OMADRMHeadersBox, see Table 17 and Table 18,
�osfm�
TABLE 18 OMADRMHeadersBox Field Type Details Value BoxHeader.Size Unsigned int(32) BoxHeader.Type Unsigned �ohdr� int(32) BoxHeader.Version Unsigned 0 int(8) BoxHeader.Flags Bit(24) 0 CTLen Unsigned Length of fixed int(8) headers (for performance reasons) CIDLen Unsigned Length of Content ID int(8) ContentType Unsigned Content Type header int(8)[CTLen] ContentID Unsigned Content ID header int(8)[CIDLen] Headers Unsigned Rest of headers, int(8) [ ] including issuer URL, to end of box Encrypted Server Files
By default, binary files are stored �in the clear�. However, it is also possible to include encrypted binary files in the file directory of a 3GP file. The presence of a Protection information box in a file entry box indicates that the content of the binary file (media data) is encrypted. Moreover, the Protection information box identifies the encryption scheme and all information required to decrypt the corresponding media data.
The Protection information box �sint� contains the Scheme type box �schm�, which identifies the protection scheme used to protect the media, and the Scheme information box �schi�, which contains scheme-specific data (defined for each scheme.
The boxes contained by the SchemeInformationBox are defined by the scheme type. Similarly, it is possible to define boxes that apply to the full �mdat� or a byte range inside �mdat�. This could be good for a presentation with many small files.
3GP files that are extended according to the invention and contain a file tree may define a 3GP profile (brand). Files in the file tree can be stored �in the clear� or encrypted together with requirements on how to decrypt them.
REFERENCES [1] ITU-T Recommendation H.263 (2001), Video codec for low bit rate communication. [2] 3GPP TS 26.071: Mandatory Speech CODEC speech processing functions; AMR Speech CODEC; General description. [3] ISO/IEC 14496-2:2001, Information technology�Coding of audio-visual objects�Part 3: Audio (MPEG-4 part 3).
[6] ISO/IEC 14496-12:2003 | 15444-12:2003: Information technology�Coding of audio-visual objects�Part 12: ISO base media file format | Information technology�JPEG 2000 image coding system�Part 12: ISO base media file format. [7] U.S. Pat. No. 2003/0053416 A1, Generalized Reference Decoder for Image or Video Processing, Ribas-Corbera et al., Microsoft.
[9] 3GPP TS 26.234: Transparent end-to-end packet switched streaming service (PSS); Protocols and codecs. Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS6098126 *Oct 27, 1998Aug 1, 2000Apple Computer, Inc.Method and apparatus for synchronization of data retrieval and presentationUS6430177Jun 9, 1998Aug 6, 2002Unisys CorporationUniversal messaging system providing integrated voice, data and fax messaging services to pc/web-based clients, including a content manager for receiving information from content providers and formatting the same into multimedia containers for distribution to web-based clientsUS6792433 *Apr 6, 2001Sep 14, 2004Avid Technology, Inc.Indexing interleaved media dataUS7246318 *Jun 28, 2002Jul 17, 2007Microsoft CorporationApplication programming interface for utilizing multimedia dataUS7296063 *Feb 28, 2003Nov 13, 2007Microsoft CorporationActive stream format for holding multiple media streamsUS20020026521 *Jan 10, 2001Feb 28, 2002Sharfman Joshua Dov JosephSystem and method for managing and distributing associated assets in various formatsUS20030050919 *Sep 5, 2001Mar 13, 2003International Business Machines CorporationApparatus and method for providing access rights information in a portion of a fileUS20030053416Sep 19, 2001Mar 20, 2003Microsoft CorporationGeneralized reference decoder for image or video processingUS20030061369Sep 20, 2002Mar 27, 2003Emre AksuProcessing of multimedia dataUS20040001106 *Jun 26, 2002Jan 1, 2004John DeutscherSystem and process for creating an interactive presentation employing multi-media componentsUS20040190606 *Mar 31, 2003Sep 30, 2004Deshpande Sachin GovindHypothetical reference decoderUS20050004997 *Jun 9, 2004Jan 6, 2005Nokia CorporationProgressive downloading of timed multimedia contentUS20050071744 *Sep 30, 2003Mar 31, 2005Microsoft CorporationImage file containerUS20050102371 *Nov 7, 2003May 12, 2005Emre AksuStreaming from a server to a clientUS20060256130 *Dec 13, 2002Nov 16, 2006Activesky, Inc.Multimedia publishing system for wireless devicesUS20080025704 *Oct 1, 2007Jan 31, 2008Yoo Jea YMethod for processing connection request for a disk playerUS20100138736 *Feb 1, 2010Jun 3, 2010Canon Kabushiki KaishaDelivering multimedia descriptionsWO2001026378A1Oct 5, 2000Apr 12, 2001Streaming21 IncMethod and apparatus for managing streaming data* Cited by examinerNon-Patent CitationsReference13GPP TS 26.234 V6.0.0, Jun. 2004, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Transparent end-to-end Packet switched Streaming Service (PSS); Protocols and codecs (Release 6) (94 pages).23GPP TS 26.244 V6.0.0, Mar. 2004, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects Transparent end-to-end packet switched streaming service (PSS); 3GPP file format (3GP) (Release 6) (35 pages).3ARIB STD-T63-26.071 V4.0.0, Mandatory Speech Codec speech processing functions; AMR Speech Codec; General Description (Release 4) (13 pages).4CCITT The International Telegraph and Telephone Consultative Committee, T.81, Sep. 1992, Terminal Equipment and Protocols for Telematic Services, Information Technology-Digital Compression and Coding of Continuous-Tone Still Images-Requirements and Guidelines (186 pages).5CCITT The International Telegraph and Telephone Consultative Committee, T.81, Sep. 1992, Terminal Equipment and Protocols for Telematic Services, Information Technology�Digital Compression and Coding of Continuous-Tone Still Images�Requirements and Guidelines (186 pages).6Cover Page for ISO/IEC JTC 1/SC 29 N, 6792, Coding of Audio, Picture, Multimedia and Hypermedia Information, Jul. 13, 2005, Final Text of ISO/IEC 14496-3 3rd Edition: Information technology-Coding of audio-visual objects-Part 3: Audio (2 pages).7Cover Page for ISO/IEC JTC 1/SC 29 N, 6792, Coding of Audio, Picture, Multimedia and Hypermedia Information, Jul. 13, 2005, Final Text of ISO/IEC 14496-3 3rd Edition: Information technology�Coding of audio-visual objects�Part 3: Audio (2 pages).8Covering Note-ITU-T Recommendation H.263 Appendix II, May 2001, Recommended Optional Enhancement (1 page).9Covering Note�ITU-T Recommendation H.263 Appendix II, May 2001, Recommended Optional Enhancement (1 page).10David Singer et al., "ISO Base Media File Format incorporating amendment 1", International Organisation for Standardisation, Organisation Internationale De Normalisation, Coding of Audio, Picture, Multimedia, and Hypermedia Information, ISO/IEC JTC1/SC29/ (98 pages).11International Search Report and Written Opinion mailed Jan. 20, 2005 in corresponding PCT Application PCT/SE2004/001482.12ISO/IEC 14496-3: 2005(E) Introduction (13 pages).13ISO/IEC 14496-3: 2005(E), Information technology Coding of audio-visual objects-Part 3: Audio, Subpart 1 (120 pages).14ISO/IEC 14496-3: 2005(E), Information technology Coding of audio-visual objects�Part 3: Audio, Subpart 1 (120 pages).15ISO/IEC 14496-3: 2005(E), Subpart 10: Lossless coding of oversampled audio-DST (37 pages).16ISO/IEC 14496-3: 2005(E), Subpart 10: Lossless coding of oversampled audio�DST (37 pages).17ISO/IEC 14496-3: 2005(E), Subpart 2: Speech coding-HVXC (152 pages).18ISO/IEC 14496-3: 2005(E), Subpart 2: Speech coding�HVXC (152 pages).19ISO/IEC 14496-3: 2005(E), Subpart 3: Speech coding-CELP (165 pages).20ISO/IEC 14496-3: 2005(E), Subpart 3: Speech coding�CELP (165 pages).21ISO/IEC 14496-3: 2005(E), Subpart 4: General Audio coding (GA)-AAC, TwinVQ, BSAC (344 pages).22ISO/IEC 14496-3: 2005(E), Subpart 4: General Audio coding (GA)�AAC, TwinVQ, BSAC (344 pages).23ISO/IEC 14496-3: 2005(E), Subpart 5: Structured Audio (SA) (149 pages).24ISO/IEC 14496-3: 2005(E), Subpart 6: Text to Speech Interface (TTSI) (10 pages).25ISO/IEC 14496-3: 2005(E), Subpart 7: Parametric Audio Coding-HILN (59 pages).26ISO/IEC 14496-3: 2005(E), Subpart 7: Parametric Audio Coding�HILN (59 pages).27ISO/IEC 14496-3: 2005(E), Subpart 8: Parametric coding for high quality audio-SSC (109 pages).28ISO/IEC 14496-3: 2005(E), Subpart 8: Parametric coding for high quality audio�SSC (109 pages).29ISO/IEC 14496-3: 2005(E), Subpart 9: MPEG-1/2 Audio in MPEG-4 (14 pages).30ISO/IEC JTC 1/SC 29 N, 4298, Coding of Audio, Picture, Multimedia and Hypermedia Information, Jul. 16, 2001, Final Text of ISO/IEC 14496-2:2001: Information technology-Coding of audio-visual objects-Part 2: Visual (538 pages).31ISO/IEC JTC 1/SC 29 N, 4298, Coding of Audio, Picture, Multimedia and Hypermedia Information, Jul. 16, 2001, Final Text of ISO/IEC 14496-2:2001: Information technology�Coding of audio-visual objects�Part 2: Visual (538 pages).32ITU-T Telecommunication Standardization Sector of ITU, H.263, Feb. 1998, Series H: Audiovisual and Multimedia Systems, Infrastructure of audiovisual services-Coding of moving video, Video coding for low bit rate communication (167 pages).33ITU-T Telecommunication Standardization Sector of ITU, H.263, Feb. 1998, Series H: Audiovisual and Multimedia Systems, Infrastructure of audiovisual services�Coding of moving video, Video coding for low bit rate communication (167 pages).34ITU-T Telecommunication Standardization Sector of ITU, H.263-Annex U, Nov. 2000, Series H: Audiovisual and Multimedia Systems, Infrastructure of audiovisual services-Coding of moving video, Video coding for low bit rate communication-Annex U: Enhanced reference picture selection mode (35 pages).35ITU-T Telecommunication Standardization Sector of ITU, H.263�Annex U, Nov. 2000, Series H: Audiovisual and Multimedia Systems, Infrastructure of audiovisual services�Coding of moving video, Video coding for low bit rate communication�Annex U: Enhanced reference picture selection mode (35 pages).36ITU-T Telecommunication Standardization Sector of ITU, H.263-Annex V, Nov. 2000, Series H: Audiovisual and Multimedia Systems, Infrastructure of audiovisual services-Coding of moving video, Video coding for low bit rate communication-Annex V: Data-partitioned slice mode (14 pages).37ITU-T Telecommunication Standardization Sector of ITU, H.263�Annex V, Nov. 2000, Series H: Audiovisual and Multimedia Systems, Infrastructure of audiovisual services�Coding of moving video, Video coding for low bit rate communication�Annex V: Data-partitioned slice mode (14 pages).38ITU-T Telecommunication Standardization Sector of ITU, H.263-Annex W, Nov. 2000, Series H: Audiovisual and Multimedia Systems, Infrastructure of audiovisual services-Coding of moving video, Video coding for low bit rate communication-Annex W: Additional supplemental enhancement information specification (21 pages).39ITU-T Telecommunication Standardization Sector of ITU, H.263�Annex W, Nov. 2000, Series H: Audiovisual and Multimedia Systems, Infrastructure of audiovisual services�Coding of moving video, Video coding for low bit rate communication�Annex W: Additional supplemental enhancement information specification (21 pages).40ITU-T Telecommunication Standardization Sector of ITU, H.263-Appendix III, Jun. 2001, Series H: Audiovisual and Multimedia Systems, Infrastructure of audiovisual services-Coding of moving video, Video coding for low bit rate communication-Appendix III: Examples of H.263 encoder/decoder implementations (50 pages).41ITU-T Telecommunication Standardization Sector of ITU, H.263�Appendix III, Jun. 2001, Series H: Audiovisual and Multimedia Systems, Infrastructure of audiovisual services�Coding of moving video, Video coding for low bit rate communication�Appendix III: Examples of H.263 encoder/decoder implementations (50 pages).42Mexican Office Action dated Mar. 13, 2009 w/ English translation (6 pages total).Referenced byCiting PatentFiling datePublication dateApplicantTitleUS8046439 *Aug 26, 2009Oct 25, 2011Hong Fu Jin Precision Industry (Shenzhen) Co., Ltd.Method for installing EXT file systemUS20100158255 *Sep 8, 2009Jun 24, 2010Electronics And Telecommunications Research InstituteMethod and system for protecting broadcasting programUS20120233345 *Sep 12, 2011Sep 13, 2012Nokia CorporationMethod and apparatus for adaptive streaming* Cited by examinerClassifications U.S. Classification725/135, 709/231International ClassificationH04L29/06, G06F15/00, H04N7/16Cooperative ClassificationH04L65/607, H04L29/06027European ClassificationH04L29/06C2, H04L29/06M6ELegal EventsDateCodeEventDescriptionApr 10, 2012CCCertificate of correctionDec 1, 2004ASAssignmentOwner name: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL), SWEDENFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:FROJDH, PER;EINARSSON, TORBJORN;WESTERLUND, MAGNUS;REEL/FRAME:016037/0046;SIGNING DATES FROM 20041109 TO 20041115Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:FROJDH, PER;EINARSSON, TORBJORN;WESTERLUND, MAGNUS;SIGNING DATES FROM 20041109 TO 20041115;REEL/FRAME:016037/0046RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google