Get Started for FREE
Sign up with Facebook Sign up with X
I don't have a Facebook or a X account
 Your new post is loading...
Your new post is loading...
Scoop.it!
![[IBC 2013 Talk] The Future of OTT Platforms | Video Breakthroughs | Scoop.it](https://img.scoop.it/QcV918WTWh5B0iROqlVSxDl72eJkfbmt4t8yenImKBVvK0kTmF0xjctABnaLJIm9)
The reign of end-to-end OTT platforms is over, here comes the modular OTT Platform ! With SOA, FIMS, IMF and DASH, agility time has (almost) come...
This is the report/sequel of Vimond's Industry Visionaries IBC2013 talk about “The Future of OTT Platforms: Is it Diversification or Standardization ?” with Eric Schumacher-Rasmussen, Editor of Streaming Media Magazine, and Nicolas Weil. 
No comment yet.
Sign up to comment
Scoop.it!
What has business process management got to do with broadcasting? Surely, it is more relevant to a manufacturing operation; broadcasting is a creative business, isn’t it? Sure, production is creative, but to an outsider, broadcasting operations are much like manufacturing. Raw materials — the program tape or file — arrive from the production company, and at the other end, the broadcaster delivers programs to the viewer.
Through all the many processes, the program has been formatted for the viewer’s television, tablet or smartphone, and any necessary subtitles, captions or dubbed audio have been added to the program. The channel schedule has been delivered to the third-party listings guides with information about each program, and the promotions department may also have created trailers for the program.
Is this not a manufacturing operation, a media factory?
Over the last decade, many verticals outside the media-and-entertainment sector have moved to a software architecture where the processes are managed as a whole, rather than using islands of software to process the product. This holistic management of business processes potentially offers a more efficient way to command, control and optimize media operations.
Scoop.it!
|
|
Scooped by Nicolas Weil |
Scoop.it!
At the recent IBC Show in Amsterdam, numerous vendors were extolling the benefits of a service oriented architecture (SOA) for capturing, producing, processing and distributing video and audio content as digital files. It’s the latest industry buzz term, but this one appears to have staying power as it brings the potential cost- and resource-saving benefits for both customers and the manufacturers themselves.
Although clearly interested, many attendees were left feeling a bit cautious about how to most effectively design and implement such an IT-centric system, even with the knowledge that it would increase efficiency and staff productivity while helping content providers manage the transition to a multi-screen, multi-format universe.
|
|
Scooped by Nicolas Weil |
Scoop.it!
“Conductor” plays a key role in Sony's new Tapeless initiative called Media Backbone. Based on a Service Orientated Architecture (SOA) Media Backbone enables heterogeneous platforms and applications to be easily integrated and managed via a common Enterprise Service Bus (ESB).
The benefits of an efficiently run, modular, scalable system are open-ended. A layered, abstracted system that can be viewed from a high level can be automated to an extreme degree, and integrated seamlessly with external services and consumers. Sony's experience with metadata-driven workflows is the key to integrating the proven benefits of SOA with a media production system.
|
|
Scooped by Nicolas Weil |
Scoop.it!
Le 17 octobre s’est tenu dans l’auditorium de Francetélévisions un Atelier Dig-it intitulé « Dématérialisation des contenus à la TV : les clés de la réussite ! » réunissant les meilleurs spécialistes français de la question, ainsi que plusieurs experts internationaux.
|
|
Scooped by Nicolas Weil |
Scoop.it!
The concept of service-oriented architecture (SOA) is currently being introduced in professional broadcast environments. It offers, in principle, a more effective way of integrating systems in a production platform.
This article illustrates the concept of SOA and describes an actual implementation that has been used in a proof-of-concept study. This study demonstrated the archiving of news as an integrated end-to-end process. The experience gained gives an insight into where, as an integration platform, the benefits of service-oriented architecture lie ... and also where specific challenges might arise.
READ PAPER HERE : http://tech.ebu.ch/docs/techreview/trev_2012-Q2_SOA_archiving_Elser.pdf
|
|
Scooped by Nicolas Weil |
Scoop.it!
Broadcasters no longer have the monopoly on the delivery of A/V entertainment to the home. In the fiercely competitive world of media and entertainment, companies have to deliver more versions and formats, but without increasing their costs. A channel is now expected to have a Web presence, as well as mobile and tablet versions of their content.
Organizations like the EBU and Advanced Media Workflow Association (AMWA) are promoting the service-oriented architecture (SOA) as a route to provide the interoperable media services that can serve the new business requirements.
For the seasoned video engineer, the world of SOA introduces terms and concepts that at first encounter seem foreign and more suited to the IT specialist. As video processing migrates to the file domain, there is no option but to become familiar with what at first sight may appear alien.
Broadcast systems have evolved around the imposed workflow of the serial processing steps of videotape operations. Over time, many processes have moved from dedicated hardware boxes with SDI in and out to software applications on a network. A typical broadcast operation is now a hybrid of SDI and IP connections.
In many cases, the workflow remains as the original tape-based flow. Over time, other applications like asset and workflow management are layered over the entire process chain. The system has grown by accident, not by design, and become a web of custom or proprietary interfaces linking the many applications.
Sure it works, it was designed that way, but when the time comes to replace a component part — say the playout automation — the inflexibility of the system rapidly comes apparent. The parts of the system are linked by a web of custom APIs, often restricted to a specific release of a specific software application. It is just not possible to swap out the automation for the latest product without attending to the web of interfaces.
To meet the demands for new services to the public, the broadcaster must add facilities for a mobile news service, a 3-D channel and interaction with a social media website. Along comes CES and some new consumer device to consume content. How do you add support for this new device? Will it mean more custom interfaces or more special workflow applications? The EBU and AMWA are developing a Framework for Interoperable Media Services (FIMS), which aims to provide a new technology platform that leverages current IT practices, like the use of the SOA, to provide business agility and to control costs.
|
|
Scooped by Nicolas Weil |
Scoop.it!
![Framework for Interoperable Media Services : FIMS White Paper [PDF] | Video Breakthroughs | Scoop.it](https://img.scoop.it/3wbB31kLNiKwnOisLmJzRTl72eJkfbmt4t8yenImKBVvK0kTmF0xjctABnaLJIm9)
Currently in the media industry, users are implementing service-based systems using proprietary systems with bespoke software ‘glue’ holding it all together. They are doing this without an open, agreed framework and without standardized interfaces. While several organizations have identified a number of common processes such as capture which are performed essentially the same way throughout the industry, users are implementing these processes as services in different ways. At the same time, technology vendors are responding to demand for services-based products, but interoperability between different implementations is non-existent. This is because there is a lack of an agreed framework and publically developed service definitions in the media industry.
The AMWA-EBU FIMS (Framework for Interoperable Media Services) Task Force was established in December 2009. FIMS is a framework of service definitions for implementing media related operations using a Service-Oriented Architecture (SOA) approach. Media companies deploying this framework can expect that doing so will promote interoperability and reusability of services. FIMS defines service models with associated management, error handling, communication, and time awareness.
To properly exploit this technology the Task Force has developed a common framework which will help ensure integration interoperability, interchangeability and reusability of services. This will drastically reduce integration costs, allow users to more freely choose the most appropriate products on the market at any given time, improve maintainability, and aid in the adoption of new technologies.
FIMS also has begun the process of defining open services that are loosely coupled thereby enabling multivendor services to be integrated and creating “best-in-class” media systems. The services can span a wide domain of operations and permit integration of FIMS into business and management systems. The bottom line is that implementing FIMS will move facilities to an agile environment that is more easily configured, modified, managed and governed compared to non SOA systems.
Read the full whitepaper here : http://wiki.amwa.tv/ebu/images/1/12/FIMS_WhitePaper_Version_1.0.1.pdf
