Source Delta Tracking
This site is not a direct mirror of the upstream source documents (GTL, TVR, STM, SAI, etc.). In some cases it intentionally diverges from them — reflecting a corrected or intended state where an error, gap, or omission has been identified and resolved here but not yet incorporated back into the canonical source.
This page tracks those differences. Each entry represents a change that needs reviewing by the relevant work package lead and folding back into the appropriate source document. Once a source has been updated to reflect the correction, remove the corresponding entry from both the summary table and the details section below.
A second section — DBR Content Gaps — records content that is missing or incomplete within the DBR itself, pending input from partners or infrastructure teams.
Summary
| # | Source | Location | Summary | Owner |
|---|---|---|---|---|
| 1 | GTL v3 | Strand 2 sheet — all 13 WP 2.1 rows | Responsible / Nature of test / Test level / KPI columns blank | WP 2.1 lead |
| 2 | GTL v3 | Strand 4 sheet — WP 4.1.3 | Three earlier DBR test titles absent from v3 | WP 4.1 lead |
| 3 | GTL v3 | Strand 2 sheet — WP 2.1 scenario list | Scenarios I and C.1 from TVR Appendix 1 missing | WP 2.1 lead |
| 4 | SAI v2.2 | Chapter 3 (functional and logical architecture) | Supply & Demand control model not captured | Architecture lead (WP 1.2) |
Details
1. GTL v3 Strand 2 — blank metadata columns
Source: GTL v3 — Strand 2 sheet Location: All 13 WP 2.1 rows
The Responsible, Nature of test, Test level, and KPI columns are blank for every Strand 2 test. These fields should be populated by the WP 2.1 lead(s) to match the level of detail present in the Strand 3–6 sheets.
Until corrected, the DBR represents these tests without Responsible or Nature metadata.
2. GTL v3 Strand 4 — WP 4.1.3 test title set
Source: GTL v3 — Strand 4 sheet Location: WP 4.1.3
Three test descriptions present in earlier DBR versions — Multicast reception, Tracking satellite, and Strand 2 integration — do not appear in GTL v3, which lists six WP 4.1.3 tests:
- Closing the link
- RTN link protocols switch (5G orchestrator)
- Live TV over NTN
- VoD over NTN
- Internet connectivity over NTN
- ARCA SATCOM VPN
The DBR has been corrected to match GTL v3.
Action required: if the three absent titles represent real tests (e.g. from a prior GTL version or the TVR), the WP 4.1 lead should reinstate them in the GTL.
3. GTL v3 Strand 2 — missing Scenarios I and C.1
Source: GTL v3 — Strand 2 sheet Location: WP 2.1 scenario list
TVR Appendix 1 includes Scenarios I and C.1 which are not present in the GTL v3 Strand 2 sheet. As of 12 Apr 2026, a testbed (Arctic Space) is confirmed for both scenarios and they have been moved to performable (A.1) in the DBR's E2E Scenarios reference. The DBR now tracks both scenarios.
Verified 20 Apr 2026 against cache/Global Test List-TVR 5G-Emerge-v3.xlsx: the Strand 2 sheet still lists only the 13 scenarios (B, E, G, J, K, M, O, P, R, T, V, W, A.2) and continues to omit I and C.1.
Action required: WP 2.1 lead to add Scenarios I and C.1 to the GTL Strand 2 sheet.
4. SAI v2.2 Chapter 3 — Supply & Demand control model
Source: SAI v2.2 — Chapter 3 Location: §3 (functional and logical architecture)
SAI §3 does not document the two-sided Supply & Demand control model that governs the 5G-EMERGE content delivery architecture:
- Demand Controls (SF1–SF2) — produce the content-selection signal (SC-Sel) from service discovery, content discovery, business rules, content selection, prioritisation, prediction, and popularity
- Supply Controls (SF3–SF5) — receive SC-Sel and coordinate the actual delivery: content steering, transmission management, exposure gateway, far edge cache, access network, and player
- Telemetry (SF5) — closes the loop back into Content Prediction and Content Popularity on the demand side
The DBR captures this on Supply & Demand Control.
Action required: a future SAI revision should incorporate the Supply & Demand control model into Chapter 3, with corresponding updates to the WP 3 public white paper derived from §3. Until corrected upstream, the DBR reflects the intended state.
DBR Content Gaps
Content that is missing or incomplete within the DBR itself — not a source document delta, but pending input or confirmation before the DBR can be updated.
| # | Location | Summary | Owner |
|---|---|---|---|
| A | Tools & Resources — Media Resources | 10 stream URLs (live and VOD) still [TBC] |
Infrastructure lead |
A. Media stream URLs
Location: Tools & Resources — Media Resources section
Ten stream URLs covering live (HLS/DASH via MediaPackage origin, CloudFront, GCore) and VOD (HLS/DASH via CloudFront and GCore) are currently listed as [TBC]. The infrastructure exists; the URLs need to be confirmed and supplied by the infrastructure lead so the page can be completed.
Action required: supply confirmed stream URLs so the [TBC] placeholders in the Tools & Resources page can be replaced.