Information Sources

This document defines the information ecosystem for the 5G-EMERGE Phase 2 testbed website: the canonical sources, what each one contains, how they overlap, and the process by which they are consolidated into the testbed website (DBR).

Sources

The testbed website draws on five primary source documents, one public white paper, and the git repository itself.

All SharePoint source documents are maintained under the WP 1.2 – Architecture folder. Word documents (TVR, SAI) each have their own subfolder; spreadsheets (GTL, CTM, STM) are in the TVR subfolder. Source files are kept current in the local cache by npm run sync — see Source Sync.

SharePoint locations: SAI: 5g-emerge_phase2 › Strand 1 – Research coordination dissemination › WP 1.2 – Architecture › SAI – Service Architecture and Interfaces https://ebu1.sharepoint.com/sites/5g-emerge_phase2/...

TVR: 5g-emerge_phase2 › Strand 1 – Research coordination dissemination › WP 1.2 – Architecture › TVR – Testing, Validation, and Results https://ebu1.sharepoint.com/sites/5g-emerge_phase2/...

Coverage Map

This table shows which types of information are provided by each source and where they surface in the DBR.

Source columns (SAI–CTM): a ✓ means the source contains that information type, with a parenthetical note where the coverage is partial or indirect. DBR column: shows where the information appears in the testbed website — docs (documentation pages), cards (test status cards), .xlsx (generated spreadsheet), or a combination. DBR only rows highlight the value the testbed website adds beyond consolidating existing sources.

What Each Source Contains

SAI — Service Architecture and Interfaces

The architectural reference document for Phase 2. Defines the service interfaces, component interactions, and system architecture that the test programme validates against. Used to understand the intended behaviour and interface contracts that test cases in the TVR and GTL are designed to exercise.

Key sections used in DBR: Interface specifications referenced in Strand 2 component and test-case descriptions; architectural diagrams informing testbed scope.

TVR — Testing, Validation and Results

The master technical document for Phase 2. Defines:

• All test beds (architecture, components, satellite segments — §3–§7)
• Strand 2 test infrastructure and test case specifications (§7.3–§7.4)
• End-to-end service scenarios (Table 1, Appendix 1)
• E2E performance test plans per strand (Table 2)
• Strand 2 tests confirmed for Phase 2 (Table 3 / §2.9.6)
• Component tables per testbed (Tables 4, 5, 9, 15)
• KVI/KPI definitions

Key sections used in DBR: §2.9.6, §3–§7.4, Appendix 1 A.1 & A.2.

GTL — Global Test List

The master test registry. Provides:

• All formal test cases across Strands 2–6, each with a structured ID
• Per-test: Work Package, Use Case, Testbed, Title, Description, Test Level, KPI, Responsible partner, Nature (Functional/Performance)
• Service Level Test definitions (16 E2E service scenarios with KPI targets per testbed)
• The authoritative mapping of E2E scenarios (B, E, G, …) to specific testbeds

Sheets: Service level tests · E2E performance tests · Strand 2 tests · Strand 3 tests · Strand 4 tests · Strand 5 tests · Strand 6 tests

Key additions over TVR: Formal test IDs, responsible partner per test, nature classification, testbed specificity for each E2E scenario.

CTM — Component to Testbed Mapping (Strand 2)

Maps each Strand 2 component (WP 2.1–2.5) to the testbeds where it is deployed. Provides:

• Deployment status per component per testbed (Confirmed / Planned / N/A)
• Component owner/partner
• Notes on how the mapping was derived

Produced from: TVR §7.4 (component list) + Tables 4, 5, 9, 15 (testbed component lists).

STM — Scenario to Testbed Mapping

Maps each E2E service scenario to the testbed(s) responsible for executing it. Provides:

• Which testbed(s) each scenario (B, E, G, …, A.2) is performed on
• Use case class per scenario (DTE, DTH, DTV, DTD)

WP3 — Third White Paper on 5G-EMERGE

The public white paper summarising SAI Chapter 3. It describes the 5G-EMERGE architectural blueprint — functional architecture, logical architecture, architectural evolution of media streaming, and the key technologies and standards — in a form suitable for external audiences. The DBR's Architecture page is derived from this content.

Available at: https://5g-emerge.eu/white-papers/

DBR — The Testbed Website Repository

The DBR is the living consolidation of all source documents, enriched with additional detail, partner context, and status tracking not present in the upstream sources.

See Source Traceability for the page-level mapping of which sources feed which pages.

Related Pages

• Information Flow — current and planned data flow between sources and the DBR
• Working Process — step-by-step procedures for updating the DBR when sources change
• Source Traceability — which sources feed which pages and data
• Source Sync — how source files are kept current locally
• Issues & Roadmap — open questions, pending corrections, and planned improvements