Differences

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

--- start [2025/03/14 15:58] – Added my session topic edubs
+++ start [2025/04/04 17:44] (current) – old revision restored (2025/03/19 16:05) dvbw-wiki
@@ Line 111: / Line 111: @@
   * Elfed Howells (Huawei)
-  * Summary of topic: Discussion should cover profiling, compliance and testing.
+  * Summary of topic:
-  * Session goals: (will follow)
+. work our which problem you want to solve  - reasons why
+. establish your hardware and device profile
+. work out your application profile (OSD/Presentation/DRM) e.g. TVOS with a HTML application
+. Find a device that matches you needs as a development platform
+. Bring together all stakeholders (e.g. Operators, Telcos, Broadcasters)
+. Decide on Distribution architecture
+. Decide on Hardware selling/distribution model (sell in shop, give away with broadband package, existing own device)
+. Decide if and how you want to apply DRM/encryption
+. Decide who is in charge of the channel list CRS (ABS in China)
+. make a POC trial for real people to try
+. make a development platform sandbox for trying out new things in the lab
+. decide on your regionalization usecases
+.USE THE STANDARD for generating a playlist
+   # CSR Selection (China)
+   # Service List Provider Selection (NRTA ABS)
+   # Service List Selection (Telco)
+   # Region Selection (Shenzhen/Beijing)
+. Encode profile
+. Metadata  - convert from Legacy or make new
+. 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 ====
@@ Line 140: / Line 166: @@
   * 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?
-  * Session goals:
+  * Goals:
-	  * Identify the most relevant SDOs and topics that would benefit from enhanced collaboration.
+  - 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.
+  - 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.
+  - 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.