Start by copying the “Example session” below and paste it at the end of the page, replacing its name with the name of your session. Then replace the text in the example session with the relevant information about your session.

(You need to Create a user account and login first.)

NOTE: adding an idea on this page does NOT automatically place it on the unconference agenda. All sessions will need to be pitched during the opening circle in Amsterdam on 18 March, and then they can be added to the agenda. (Sessions that are introduced via a Quickfire Talk during the conference on Day 1 will also need to be briefly pitched during the opening circle.)

Keep these four basic guidelines (more detail here) in mind in planning and hosting your session:

1. Start with an outcome in mind. What do you hope to achieve?
2. Plan a structure to support discussion. It will be easier to keep the conversation focused if you start by creating a high-level agenda – put it on a flipchart or whiteboard so everyone can see it.
3. Encourage broad participation. Sessions work best when everyone is heard, not just one or two voices, and when not dominated by slides or formal presentations.
4. Capture key points visibly. Use a flipchart or whiteboard to keep the group aligned and make reporting easier.

Sessions that tend to work best are those that share experiences, generate ideas, provide an opportunity to pose questions, and gauge interest on a given topic.

Participants react negatively to sessions that consist mainly of PowerPoint presentations and/or are seen as a sales pitch for a given product or service.

• DVB World website
• Unconference sessions: what works and what doesn't

• Your name and company
• Summary of topic: (A sentence or two describing the session)
• Session goals: (Describe what you hope to achieve from this session)

• Fotios Tretas – AnixeNet
• Summary of topic: This session presents a practical examination of the coexistence of DVB-T2 and 5G Broadcast within the same RF channel through the use of DVB-T2 Future Extension Frames (FEFs). The discussion is based on architectural design choices and operational findings derived from a real-world Proof-of-Concept, highlighting both technical feasibility and implementation constraints.
• Session goals: To explain how such a system operates in practice, share architectural choices and lessons learned from a real Proof-of-Concept, and engage the DVB community in an open discussion on feasibility, constraints, and possible next steps, including the role of DVB-I as a potential service discovery layer. The project has been implemented with the support of the ITE Crete Campus (Foundation for Research and Technology – Hellas).

• Peter Lanigan - TP Vision (as chair of CM-I)
• Summary of topic: TVs and STBs mostly have a similar user interface for linear TV services, with a channel list, a “grid” EPG, P+/P- buttons and number keys. This UI is familiar to users and its simplicity and “standardisation” has advantages for e.g. accessibility. However, TVs also integrate linear services with other types of content such as video on demand, for example in a home screen, and search and recommendations. Users also use other kinds of device to access TV services, such as smart phones, tablets and PCs. DVB does not specify or standardise User Interfaces, but DVB specifications may be based on assumptions about UIs, and extensions might enable new kinds of UIs. The DVB-I User Interface competition showed a lot of creative thinking about how to present DVB-I services.
• Session goals: Collect and generate new ideas for how TV services could be presented to and selected by users - considering, for example, different kinds of service, device and personalisation options. Have a first discussion about how DVB-I can support these ideas and identify changes or additions to DVB specifications that might be needed.

• Thomas Stockhammer (Qualcomm)
• Summary of topic: …
• Session goals: To be added

• Dzmitry Kastsenich (Zappin Media)
• Summary of topic: DVB-I massively improves discovery and device reach, but many “next-gen” experiences (AI recommendations/Q&A, highlight recaps, ambient social, etc.) need richer programme-level metadata and time-based events than what's typically available in practice. Let's map the gaps, propose a realistic “metadata+eventing wishlist”, and identify what the DVB ecosystem could standardize vs what apps/platforms must infer.
• Session goals:
  1. Wish-list: top 10 metadata fields + top 10 event types needed for AI/social-native UX (with “must-have/nice-to-have”).
  2. A practicality matrix: where could this data come from (broadcasters, EPG providers, content IDs, automation systems, ad markers, apps/clients) and what's “realistic in 12–24 months”.

• William Cooper (SLR)
• Summary of topic: DVB-I specifies mechanisms for service discovery, but it does not define specific domains for endpoints. What can we learn from how internet infrastructure systems such as the Domain Name System are organised? As DVB-I deployments expand, it may be useful to discuss what discovery architectures could scale effectively across consumer electronics manufacturers, media providers, platforms, and regions.
• Session goals:
  1. Explore possible models for DVB-I service discovery at internet scale
  2. Discuss the potential roles of a central registry, national registries, or federated approaches
  3. Share experiences from existing implementations or related internet infrastructure systems
  4. Identify open questions around governance, coordination, and interoperability

• Régis Moulin and Ralph Edeine (EUTELSAT), Emily DUBS (DVB)

• Summary of topic: Advertising is a key monetization opportunity for broadcasters, especially FTA channels. But in broadcast environments, ads are poorly targeted. So, ads value could be significantly higher if they were tailored to a specific area (or other criteria), without relying on connectivity. DVB may want to standardize the interoperable logic that is needed to make this happen?

• Session goals:
  1. Assess the commercial value
  2. Explore relevant use cases
  3. Discuss potential technical approaches
  4. Suggest potential next steps