1 / 17

FIMS BM ESSENCE LOCATOR

FIMS BM ESSENCE LOCATOR. 11/27/2012 Loic Barbou Bloomberg/ Triskel Inc. Modeling Principle. FIMS objects should contain media properties allowing interoperability across media services implementations

daria
Download Presentation

FIMS BM ESSENCE LOCATOR

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FIMSBM ESSENCE LOCATOR 11/27/2012 Loic Barbou Bloomberg/Triskel Inc

  2. Modeling Principle • FIMS objects should contain media properties allowing interoperability across media services implementations • The structure of FIMS Media objects should be clear enough to provide a consistent interpretation across media services

  3. Modeling principle bmContentType bmContentFormats bmContentFormatType bmEssenceLocators bmEssenceLocatorType

  4. Approved Structure of bmContent • Asset ID(s) • Editorial metadata bmContentType • Format properties: may contain a collection of Video and/or Audio profile • MIME Type • Duration • Size bmContentFormats bmContentFormatType bmEssenceLocators bmEssenceLocatorType • Base Class: provide an abstract definition of a locator requiring an implementation • Define the physical representation of an asset matching the specified format

  5. bmEssenceLocatorType • Existing Implemenation of the bmEssenceLocatorType • SimpleFileLocatorType • ListFileLocatorType • FolderLocatorType • Goals: provide a SIMPLE way to model asset physical presentation that can be interpreted by Media Services

  6. Interpreted by Media Services ? • What does it mean? • A Media Service (Transform, Transfer, Capture) should be able to receive or create a FIMS object (BMContentType) and understand how to process the information • Transform: needs to understand the input format of the provided asset essence and the location to retrieve the essence. It also needs to generate a FIMS Object representing the newly created essence (format and physical asset)

  7. Interpreted by Media Services ? (2) • What does it mean? • Transfer: needs to understand the source address and the structure of the physical files representing the asset • Capture: needs to create a representation of the generated asset by describing the format and location of the physical asset

  8. SimpleFileLocatorType • Definition: provide a way to describe a physical asset represented by a single file. The single file may or may not contain multiple format. • Usecases: • Single Format • MP4, MOV,… • Multi Format (multi bitrate) • WMV,…

  9. SimpleFileLocatorType Media Service Interpretation • The only FIMS media service inspecting the bits of the physical file is the transform service • A FIMS transform operation request specifies the format and the essence to use. • For single bit rate essence. no confusion exist for the transform service on what to use. • In the context of a single physical file containing multiple bit rates. The transform request only describes the format to be used by the transcoding service NOT all of the bit rates available in the asset. no confusion exist for the transform service on what to use.

  10. SimpleFileLocatorType Media Service Interpretation (2) • A FIMS transform operation response specifies the format and the essence of the created asset. • For single bit rate essence. no confusion exist for the transform service knows how to generate the FIMS object. • In the context of a single physical file containing multiple bit rates. The transform response describes the collection of Video/Audio formats created by transcoding service. no confusion exist for the transform service.

  11. ListFileLocatorType • Definition: provide a way to describe a physical asset represented by multiple files. The multiple files may or may not contain multiple formats (bit rate). The files store different types of data: video or audio data, manifest, structure metadata,…. • Usecases: • Single Format • SmoothStreaming (single bit rate), GXF, … • Multi Format (multi bitrate) • SmoothStreaming, …

  12. ListFileLocatorType Media Service Interpretation • A FIMS transform operation request specifies the format and the essence to use. • For single bit rate essence. no confusion exist for the transform service on what file to use based on the interpretation of the specified format (GXF  MPG2). • The transform request only describes the format to be used by the transcoding service NOT all of the bit rates available in the asset. no confusion exist for the transform service on what to use.

  13. ListFileLocatorTypeMedia Service Interpretation (2) • A FIMS transform operation response specifies the format and the essence of the created asset. • For single bit rate essence. no confusion exist for the transform service. It knows how to generate the FIMS object by creating all the physical files needed for the specified Format. It then adds these files as a ListFileLocatorType object • In the context of a multiple physical files containing multiple bit rates. no confusion exist for the transform service. Same applies as above.

  14. FolderLocatorType • Definition: provide a way to describe a physical asset represented by many files located within the same folder. The multiple files may or may not contain multiple formats (bit rate). The files store different types of data: video or audio data, manifest, structure metadata,…. • Usecases: • Single Format • SmoothStreaming Live, • Multi Format (multi bitrate) • SmoothStreaming Live, Http Live Streaming

  15. FolderLocatorTypeMedia Service Interpretation • A FIMS transform operation request specifies the format and the essence to use. • For single bit rate essence. no confusion exist for the transform service on what file to use based on the interpretation of the specified format. It knows what file to select within the folder. • The transform request only describes the format to be used by the transcoding service NOT all of the bit rates available in the asset. no confusion exist for the transform service on what to use.

  16. FolderLocatorTypeMedia Service Interpretation (2) • A FIMS transform operation response specifies the format and the essence of the created asset. • For single bit rate essence. no confusion exist for the transform service. It knows how to generate the FIMS object by creating all the physical files needed for the specified Format. It then adds these files within a single folder create a FolderLocatorType object representing the folder. • In the context of a multiple physical files containing multiple bit rates. no confusion exist for the transform service. Same applies as above.

  17. CustomLocatorType • It is used to create a strongly type object representing the essence of an asset. • It is required for Media transactions where the properties of the object drive decision at the media service level. “No existing known use cases require a customLocatorType for Implemented FIMS service”Loic • It models better the structure of an asset essence type than other generic types • It requires a sub-class to be created and understood by media services

More Related