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 six primary source documents, one public white paper, and the git repository itself.

Ref	Document	Scope	Format	Current filename	Last modified	Owner
SAI	Service Architecture and Interfaces	All	`.docx`	`5G-EMERGE_P2_Service Architecture and Interfaces (SAI)_v2.3.docx`	01 May 2026	WP 1.2 / All partners
CTM	Component to Testbed Mapping (Strand 2)	All	`.xlsx`	`Component to Testbed Mapping (Strand 2).xlsx`	20 Apr 2026	WP 2 / EBU
TVR	Testing, Validation and Results	Testing	`.docx`	`5G-EMERGE_P2_Testing, Validation and Results(TVR)_v2.3.docx`	14 May 2026	WP 1.2 / All partners
GTL	Global Test List — TVR 5G-Emerge	Testing	`.xlsx`	`Global Test List-TVR 5G-Emerge-v3.xlsx`	30 Apr 2026	WP 1.2 / All partners
STM	Scenario to Testbed Mapping	Testing	`.xlsx`	`Scenario to Test Bed Mapping.xlsx`	20 Apr 2026	WP 1.2 / All partners
TPT	Telemetry Project Tracking — Telemetry Hub inventory and planning	Telemetry	`.xlsx`	`5G-EMERGE_P2_WP2_3_1_Telemetry_Project_Tracking.xlsx`	08 May 2026	WP 2.3.1 / EBU
WP 3	Third White Paper on 5G-EMERGE	All	`.pdf`	— (public)	2025	5G-EMERGE consortium
DBR	`5g-emerge-testbed-website` repository	All	Git	—	—	GitHub — 5G-EMERGE organisation

Most SharePoint source documents are maintained under the WP 1.2 – Architecture folder; TPT lives in the WP 2.3.1 library. Source files are kept current in the local cache by npm run sync — see docs/activities/source-sync.md (project docs).

Note (2026-05-15): The standalone S2TL (Strand 2 Testsheet) workbook is no longer tracked as a separate source — its data has been folded into the GTL as a Strand 2 sheet/tab.

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/...

TPT: 5g-emerge_phase2 › Strand 2 – Cross edge functionalities BroadcastC › WP2.3 › WP2.3.1 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.

Information type	SAI	TVR	STM	GTL	CTM	DBR
Testbed descriptions & architecture		✓				✓ (docs)
Satellite segment definitions		✓				✓ (docs)
Service interface & component definitions	✓					✓ (cards)
Service-level test KPI targets		✓		✓		✓ (cards + docs)
All test cases (formal IDs)		✓		✓		✓ (docs + cards)
Testbed assignment per test		✓	✓	✓		✓ (cards)
Responsible partner per test				✓		✓ (cards)
Component → testbed mapping		✓ (tables)			✓	✓ (.xlsx)
E2E scenario → testbed mapping		✓ (App.1)	✓	✓		✓ (cards + docs)
KPI/KVI catalogue		✓		✓		✓ (docs)
Strand 2 supplementary test data				✓ (S2 sheet)		✓ (cards)
Inputs, outputs, expected results, actual results & comments						DBR only
Test execution status & results						DBR only
Findings, risks, blockers						DBR only
Actions & next steps						DBR only
Rendered / navigable dashboard						DBR only

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 testbeds (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
Strand 2 supplementary test data (since 2026-05-15) — the former S2TL workbook now lives as a sheet within GTL, covering 82 tests across WP 2.1, WP 2.1.1, WP 2.3.1, WP 2.3.2, WP 2.3.3, and WP 2.4.3 with testbed, partners, title, description, KPI, KVI, preconditions, test steps, inputs, outputs, and expected results

Sheets: Service level tests · E2E performance tests · Strand 2 tests · Strand 2 supplementary (formerly S2TL) · 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, and the full Strand 2 supplementary detail.

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).

TPT — Telemetry Project Tracking

The canonical inventory and planning record for Telemetry Hub work under WP 2.3.1. A spreadsheet covering: components (62 rows mapped to telemetry categories and per-testbed status), the Telemetry Category taxonomy (Health, QoS, QoE, QoI, OA(M/E/L/T)), the Component Type master list organised by Service Function group (SF1p, SF2, SF3, SF4, SF1c, SF5), early metric specifications, and testbed information.

Used in DBR: drives the Telemetry / State of Play page; data extracted to src/_data/telemetry/ via npm run extract:tpt.

SharePoint location: 5g-emerge_phase2 › Strand 2 – Cross edge functionalities BroadcastC › WP2.3 › WP2.3.1 https://ebu1.sharepoint.com/.../...

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)

WP 3 — 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.