Information Sources

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

Sources

The testbed website draws on four primary source documents and the git repository itself.

SAI and TVR are maintained under the WP 1.2 – Architecture folder on SharePoint; GTR and GCR are in the same folder as the TVR. Source files are kept current in the local cache by npm run sync — see docs/activities/source-sync.md (project docs).

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, GTR, GCR: 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–GCR): 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), 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 GTR 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.

GTR — Global Test Registry

The master test registry (v1.2, 12 June 2026). Provides:

• All formal test cases across Strands 2–6, each with a structured Unique Test ID (S2-WP2.1-EBU-DTE-001, S3-WP3.1.1-SES-DTH-001, etc.)
• Per-test: Strand, Work Package, Testbed, Owner, Title, Description, E2E/Use Case Ref, KPI, KVI, Status, Technical Note, TVR Section
• A canonical testbed name register (Testbeds sheet) — authoritative names used across all strand sheets

Sheets: Instructions · Testbeds · Strand 2 (104 tests) · Strand 3 (20 tests) · Strand 4 (43 tests) · Strand 5 (34 tests) · Strand 6 (2 tests)

Key additions over TVR: Structured Unique Test IDs, responsible partner per test, testbed specificity, and execution status tracking.

GCR — Global Component Registry

The authoritative registry of components across all strands and testbeds. Provides:

• Component inventory across all strands (S2–S6)
• Component → testbed deployment mapping
• Component owner/partner per entry

Used in DBR: informs component cards and testbed mapping pages.

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 to Page Mapping below for the page-level mapping of which sources feed which pages.

Source to Page Mapping

When a new page is added, a source document is updated, or coverage is extended, these tables should be updated in the same session.

Pages to Source Mapping

Data to Source Mapping

Further Reading

• Source pipeline (docs/activities/source-sync.md + docs/activities/reprocess.md) — step-by-step procedures for keeping source files current and applying their updates to the DBR