FIMS Media SOA Framework - AMWA

More documents

Recommendations

Info

FIMS Media SOA Framework Phase1 (Preliminary)ServiceConsumer:Resource ManagerService:TransformService A:TransformService B:…TransformService N:Service Allocate Request/w “Service Class”, “Service Profile”, and etc.e.g.) Service Class = “Transform Service”Get the transform service list from the SLA repository.Inquiry workload and estimated time of eachtransform service using Queue Status Requestand Job Estimate Request, etc.Decide which service is utilized for the jobbased on business rules.Service Allocate Response/w “Service ID” of the specified servicee.g.) Service ID = “Transform Service B”Transform RequestTransform ACKFigure xxx Resource Manager Sequence DiagramThe sequence of Resource Manager Service is as follows:1. Service Consumer sends a request message to the Resource Manage Service by specifying the “ServiceClass” (such as Transform) and “Service Profile” (parameters such as codec used in the Transform Service),2. The Resource Manager Service obtains the service list of the specified service class from the ServiceRepository,3. The Resource Manager Service obtains the workload and the expected execution time of each service inthe list by using the Queue Status Request and/or Job Estimate Request,4. The Resource Manager Service determines the service to be invoked based on the information obtained inItem 3 above, its SLA, and the business rule,5. The Resource Manager Service returns ID of the selected service to the Service Consumer.In this scenario, all user applications, other workflow services and Middleware (mediator) are regarded as theService Consumer of the Resource Manager Service. A user application will query whether a service is suitableby explicitly issuing the request message to the Resource Manger Service in one case. Or in another case, asystem may provide for automatic selection of an appropriate service by a mediator in the middleware, whoseprocess is hidden from the user applications.9.4 Media Aware Bus9.4.1 DefinitionAn extension to SOA often called the “Media Bus” can facilitate storage and media file centric operations. TheMedia Bus extension is similar to an Enterprise Service Bus (ESB) optimized for large files.Private committee documentWorking Draft for review by FIMS Rev v1, Nov-16-2010 Page 84 of 89
FIMS Media SOA Framework Phase1 (Preliminary)Since the system manages the storage and movement of a very large number of large files (sometimes millionsper project) it is important that an asset data repository be available as part of the system core functionality, oras an external (third party) service.There can be many copies of file instances and also many versions located in multiple island data storage areasin the system. There will also be many lower resolution video proxy files in the system representing the originalhigh resolution “camera negative” files or file sequences. These proxy files must be tracked and versioned aswell.9.4.2 Other Media Bus FeaturesReliable transfers are also critical, so the capability to provide check sums or other file verification technology isalso a function of the media bus.File naming and name management in Post Production workflows is a major issue. File names are oftenchanged when new instances are created to serve the needs of a specific creative task like Picture Editorial orDigital Intermediate. So the same file or sequence may exist in various parts of the system with different filenames. It is critical that all of these instances of the same essence be tracked and managed.Maintaining the correct metadata for any given file or file sequence (clip) as it passes through the manyprocessing stages in a media workflow is also a big problem. Many processes, both internal and outsourced (likeVFX) may change or strip off metadata from the essence and even change the identity of the objects involved.Maintaining a clear relationship between a media object and its original and modified or added metadata is veryimportant.Storage management is also critical due to the large number of large files in a 2K or 4K workflow. The systemmust facilitate the efficient use of the hierarchal storage system and assist is selecting files to be migrated totape library storage.9.4.3 M-SLAFor the treatment of Media Aware Bus in the FIMS Framework, the performance of elements on Media AwareBus (mainly storage devices) such as bandwidth, transfer speed, capacity, and available protocols are to bequeried by using a common format message.Based on this, a client such as service consumer and/or the media infrastructure service can select the storagedevice which is best suited to the client, and/or more precisely estimate the execution time it will request.This corresponds to SLA in a conventional IT-based SOA system and is referred to as M-SLA. Because thedetailed specifications of M-SLA need to be harmonized with SLA, it will be specified at a later date inaccordance with SLA developments.9.4.4 Automatic TransformIn the FIMS Framework, it will be possible for Mediation that resides in the Media Aware Bus to provideautomatic transformation by using the Media Descriptor. But since the support of automatic transformationdepends on the system design policy, it shall not be made mandatory in the FIMS Framework.Private committee documentWorking Draft for review by FIMS Rev v1, Nov-16-2010 Page 85 of 89
Page 1 and 2:
FIMS Media SOA FrameworkAMWA Specif
Page 3 and 4:
FIMS Media SOA Framework Phase1 (Pr
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34: FIMS Media SOA Framework Phase1 (Pr
Page 83: FIMS Media SOA Framework Phase1 (Pr
Page 89: FIMS Media SOA Framework Phase1 (Pr
show all

FIMS Media SOA Framework - AMWA

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?