User Tools

Site Tools


start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
start [2025/03/04 13:31] – [Example session title] rbstart [2025/04/04 17:44] (current) – old revision restored (2025/03/19 16:05) dvbw-wiki
Line 55: Line 55:
  
   * Rainer Biehn, bmt   * Rainer Biehn, bmt
-  * Summary of topic: When using DVB-I, in addition to downloading service lists, information is also retrieved from third-party servers (e.g. for content guides). This raises questions regarding data protection and the extent to which viewers must be informed about this. + 
-  Session goals:  +Summary of topic: When using DVB-I, in addition to downloading service lists, information is also retrieved from third-party servers (e.g. for content guides). This raises questions regarding data protection and the extent to which viewers must be informed about this. 
-     ** what information must be given to the viewer before the DVB-I function is activated + 
-     ** what consensus requirements result from communication with the service registry and service list +Session goals:  
-     ** which consensus requirements result from access to the HTTP endpoints for Content Guide and Now/Next, which are offered by the individual broadcasters on a distributed basis  +     What information must be given to the viewer before the DVB-I function is activated? 
 +     What data may be collected by a service list provider without consent (technically necessary access)?   
 +     What consensus requirements result from communication with the service registry and service list? 
 +     Which consensus requirements result from access to the HTTP endpoints for Content Guide and Now/Next, which are offered by the individual broadcasters on a distributed basis?  
 +     * What data may be collected by a service list provider without consent (technically necessary access)?  
  
 ==== How do we make DVB specifications more developer friendly? ==== ==== How do we make DVB specifications more developer friendly? ====
Line 91: Line 95:
  
 Ultimately, this session would kick-off a new working group for a standard that will allow simulcasting content to both DTH and B2B in a way accepted by content owners and providers. Ultimately, this session would kick-off a new working group for a standard that will allow simulcasting content to both DTH and B2B in a way accepted by content owners and providers.
 +
 +==== Where next with Test Materials, Test Streams & Open Source in DVB ====
 +
 +  * Jon Piesing, TP Vision (in my role as Technical Module Chair)
 +  * Review what DVB's V&V activities have achieved including test streams, test materials and sponsored open source developments. 
 +  * Session goals: Generate ideas for what can be improved about how DVB approaches this. Generate ideas for new test streams or other test materials or open source projects DVB could sponsor.
 +
 +==== How can DVB help Chinese manufacturers to make products for DVB-I markets?  ====
 +
 +  * Elfed Howells (Huawei)
 +  * Summary of topic: What can DVB do to help manufacturers in China make products for DVB-I markets in, for example, Europe.
 +  * Session goals: (will follow)
 +
 +====  How can DVB help China to launch DVB-I in China? ====
 +
 +  * Elfed Howells (Huawei)
 +  * Summary of topic: 
 +1. work our which problem you want to solve  - reasons why
 +2. establish your hardware and device profile
 +3. work out your application profile (OSD/Presentation/DRM) e.g. TVOS with a HTML application
 +4. Find a device that matches you needs as a development platform
 +5. Bring together all stakeholders (e.g. Operators, Telcos, Broadcasters)
 +6. Decide on Distribution architecture
 +7. Decide on Hardware selling/distribution model (sell in shop, give away with broadband package, existing own device)
 +8. Decide if and how you want to apply DRM/encryption
 +9. Decide who is in charge of the channel list CRS (ABS in China)
 +10. make a POC trial for real people to try
 +11. make a development platform sandbox for trying out new things in the lab
 +12. decide on your regionalization usecases
 +13.USE THE STANDARD for generating a playlist
 +   # CSR Selection (China)
 +   # Service List Provider Selection (NRTA ABS)
 +   # Service List Selection (Telco)
 +   # Region Selection (Shenzhen/Beijing)
 + 14. Encode profile
 +15. Metadata  - convert from Legacy or make new
 +16. Certification Who,Test Set, self cert or lab.
 + 
 +
 +
 +
 +
 +
 +  * Session goals: Regular monthly meeting with the Chinal Trial Launch team to check on progress and offer advice
 +
 +==== End-to-end protection for high-value content in DVB-I ====
 +
 +  * Elfed Howells (Huawei)
 +  * Summary of topic: With reference to 4K live high-value content delivered as a DVB-I service, how can it be protected from end to end (CAS/DRM, subscription, etc.)
 +  * Session goals: (will follow)
 +
 +==== Evolution of DVB-DASH ====
 +
 +  * Jon Piesing, TP Vision
 +  * Summary of topic: Discuss possibilities for the future evolution of DVB-DASH for example MPEG DASH 6th edition, DASH-HLS interoperability, SGAI.
 +  * Session goals: Identify options for the future evolution of DVB-DASH, discuss. debate which are most relevant for DVB and what requirements or use-cases or scenarios they meet. Consider where new commercial requirements are needed and who might be prepared to contribute them.
 +
 +
 +==== DVB-I for OnDemand ====
 +
 +  * Bram Tullemans, EBU; Remo Vogel, ARD
 +  * Summary of topic: Discuss the opportunities of DVB-I to create a distributed Video OnDemand ecosystem
 +  * Session goals: Discuss the business potential for distributed media libraries and correlating technology requirements. How is SSO enabled? How does recommendation work on a distributed media pool? How How are these offerings promoted to search engines?
 +
 +
 +==== Breaking silos, building (interoperable) blocks with greater SDO collaboration ====
 +
 +  * Emily Dubs, DVB Project Office
 +
 +  * Summary: In today’s fragmented landscape and with the rise of new SDOs, collaboration between them is more critical than ever. While some efforts are already underway, there’s still room to strengthen these collaborations to avoid redundancy, foster interoperability, and ultimately benefit the market by creating a harmonized, modular media delivery ecosystem based on interoperable and interchangeable components. Given DVB’s position in the industry, it could (and should!) be a driving force in this direction. What steps can we take to move toward such ideal collaboration? And as Head of Technology, how can I help facilitate this process?
 +
 +  * Goals:
 +  - Identify the most relevant SDOs and topics that would benefit from enhanced collaboration.
 +  - Generate actionable insights to move toward a scalable ecosystem based on interoperable components.
 +  - Explore whether and how DVB can facilitate stronger connections with the SDOs whose work is most aligned with our own.
 +
 +
 +==== Implementing DVB-I: It's all about the data ====
 +
 +  * Gordon Maynard, OnScreen Publishing
 +  * Summary of topic: Creating ServiceLists and Content Guides is straightforward these days but static data is no use to anyone: for live working all DVB-I metadata must be up to date. This includes channel lists, content guide data plus on demand content and availability. Modern networks have all this data in management systems and feeds but how to do you integrate that data with your DVB-I management system?
 +  * Session goals: 
 +  - identify the data sources which are needed for DVB-I deployment
 +  - discuss the challenges of integrating this data: both technical and operational
 +  - equip broadcasters and network operators to create their own plans for data integration in their environments
 +
 +=== DVB IP streaming architecture ===
 +
 +* Rufael Mekuria, Huawei
 +
 +Identify all functional blocks in the streaming architectures and identify interop points and related them to DVB 
 +specifications. Increas visibility of DVB work and enable external colllaboration. Improve the internal consideration for upstream work and upstream interop that does not target end devices but instead targets upstream components. 
 +
start.1741091497.txt.gz · Last modified: 2025/03/04 13:31 by rb