Testbeds
Source: TVR v2.3 §3–§7
This document describes all testbeds active in Phase 2 of the 5G-EMERGE project. Test beds are organised by strand (use case class), with cross-strand infrastructure listed separately.
Overview
Phase 2 testbeds span four use case classes (DTH, DTV, DTE, DTD) plus the Strand 2 cross-infrastructure platform. The mapping of service scenarios to testbeds is defined in TVR §2.8, Table 1.
| Short Name | WP | Testbed |
|---|---|---|
| Strand 2 — Cross-Edge Infrastructure | ||
HNR |
WP 2.1 | HNR |
WP 2.5-Lab |
WP 2.5 | Distributed Lab (NXW / RomARS / MBI / HPE) |
| Strand 3 — DTH Direct to Home | ||
SES-DTH |
WP 3.1 | SES DTH |
EBU-DTH |
WP 3.2 | EBU DTH |
| Strand 4 — DTV Direct to Vehicle | ||
Viasat-DTV |
WP 4.1 | Viasat DTV |
LINKS-DTV |
WP 4.2 | LINKS Turin DTV |
| Strand 5 — DTE Direct to Edge | ||
EBU-DTE |
WP 5.1 | EBU DTE |
Arctic-Space |
WP 5.2 | Arctic Space DTE |
Maritime |
WP 5.3 | Maritime (Telenor Maritime) |
RAI-Broadcast |
WP 5.4 | RAI 5G Broadcast |
| Strand 6 — DTD Direct to Device | ||
Keysight-Func |
WP 6.3 | Keysight Functionality |
Core-Network |
WP 6.3.11 | Core Network (MBS Core Support) |
Keysight-Perf |
WP 6.4.2 | Keysight Performance (System Emulator) |
Verkotan-OTA |
WP 6.4.3 | Verkotan OTA |
DTD-E2E |
WP 6.4.4 | DTD End-to-End |
Testbed × E2E Scenario Cross-Reference
The following table maps testbeds to TVR §2.9.6 Table 3 (Strand 2) performable E2E scenarios. "✓" indicates the scenario is assigned to that testbed; "(p)" indicates a partial/proxy measurement.
| Testbed | B | I | J | K | M | P | R | T | V | A.2 | C.1 | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| RAI (various) | ✓ | ✓ | ✓ | ✓ | ✓ | ||||||||||
| SES DTH | ✓ | ✓ | ✓ | ✓ | |||||||||||
| EBU DTH | ✓ | ✓ | ✓ | ✓ | |||||||||||
| EBU DTE | ✓ | ✓ | ✓ | ✓ | |||||||||||
| Arctic Space | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | |||||||||
| Maritime | (p) | (p) | (p) | (p) | (p) |
Note: RAI runs scenarios across multiple testbed deployments. The maritime testbed uses proxy measurements for all scenarios due to limited player-side telemetry on non-Android devices. Struck-through entries (
E,G,O,W) are no longer supported by any testbed following the STM update of April 2026.
Satellite Segment Summary
| Satellite | Operator | Type | Direction | Used By |
|---|---|---|---|---|
| ASTRA (GEO) | SES | GEO | Receive-only | SES DTH, RAI 5G Broadcast |
| ASTRA (GEO) | SES | GEO | Bidirectional | Viasat DTV |
| Eutelsat (GEO) | Eutelsat | GEO | Bidirectional | EBU DTH |
| Eutelsat (GEO) | Eutelsat | GEO | Receive-only | LINKS Turin DTV |
| Eutelsat (LEO) | Eutelsat | LEO | Bidirectional | Arctic Space DTE |
| THOR-7 (GEO) | Space Norway | GEO | Receive-only | Arctic Space DTE, EBU DTE, Maritime |
Strand 2 — Cross-Edge Infrastructure
Strand 2 comprises the HNR-owned cross-infrastructure platform (WP 2.1) and a distributed cross-partner lab testbed (WP 2.5). WP 2.1 components are shared across all strand-specific testbeds; WP 2.5 validates the integration of those components before deployment.
WP 2.1 HNR Testbed
| Partner | Humans not Robots (HNR) |
| TVR Reference | TBD |
| E2E Scenarios | Sc-B, Sc-C.1, Sc-I, Sc-J, Sc-K, Sc-M, Sc-P, Sc-R, Sc-T, Sc-V, Sc-A.2 |
The HNR testbed is the primary Strand 2 platform. Its components are deployed as shared infrastructure across all 5G-EMERGE testbeds; the testbed itself hosts the cloud and on-premise services that sit behind the transmission hop in every strand.
| Component | Role |
|---|---|
| Media Origin | CMAF packaging and manifest generation; shared across all testbeds |
| Content Discovery API | Catalogue — "what content exists?"; accepts registrations from Demand Control |
| Service Discovery Registry | Capability and stream registration — feeds Content Steering |
| Supply Control Abstraction Layer (SCAL) | Single HNR-owned API abstracting all downstream transmission paths (Fenix, FTA, CAMARA) |
| Content Steering | DASH-IF steering and edge routing (WP 2.4.3); every testbed terminates through this layer |
| Demand Control | Peach (prediction), Varnish (popularity signal), HNR (prioritisation / selection / cache population) |
| Test Harness | HNR Reference Player; emits CMCD / CMSD telemetry |
HNR-internal tests not covered by the named scenario cards (Strand 2 supplementary rows 46–47 in GTL):
- k6 Spike Test — rapid ramp to 1,000 RPS and recovery; KVI: Resilience
- VOD Ingest — S3 source file validation pre-encoding; KVI: Quality; testbed: AWS / HNR
WP 2.5 Distributed Lab Testbed
| Partners | Nextworks (NXW), RomARS, M.B.I. S.r.l. (MBI), HPE Italiana |
| Location | Distributed across four labs in Italy, interconnected via VPN (VPN server at RomARS) |
| TVR Reference | §7.3.2 |
Each lab hosts a distinct domain of the WP 2.5 system architecture:
| Lab | Location | Domain | Key Components |
|---|---|---|---|
| NXW | Pisa | Management & Orchestration + RAN emulation | Service/Network/Resource Orchestrator, Monitoring Platform, Exposure Gateway (CAMARA APIs), open-source 5G CN with emulated RAN |
| HPE | Bolzano Vicentino | Near Edge | Commercial 5G Core (CP + UP), gNB (real RAN), near-edge compute |
| RomARS | Rome | Far Edge | N3IWF (non-3GPP access), 5GC UPF with IGMP (multicast), far-edge compute |
| MBI | Pisa | Satellite Domain | Starfish platform (satellite KPI delivery and monitoring) |
Following the MS2 review, the near-edge data network is connected to the HNR testbed to provide the shared video source used across 5G-EMERGE testbeds.
Key capabilities tested: Service lifecycle management, 5G Core + RAN integration (3GPP and non-3GPP access), multicast delivery, QoD-driven broadband switching, satellite KPI monitoring, E2E media streaming.
Strand 3 — Direct to Home (DTH)
SES DTH Testbed
| Partner | SES |
| Satellite | SES GEO (ASTRA), receive-only |
| Terrestrial IP | Available |
| TVR Reference | §3.1.1, §3.2.1 |
| E2E Scenarios | 1 (Linear, terrestrial available), 2 (VoD, terrestrial available) |
| Performance tests | M (startup times), P (buffering frequency), R (resolution switches), A.2 (downtime) |
The SES DTH testbed validates satellite-extended home streaming services where adequate terrestrial internet exists but satellite extends the footprint. Content from a RAI server passes through the full 5G-EMERGE signal chain to consumer UEs.
Phase 2 additions vs Phase 1:
- Player replaced with FTA or HNR player (replacing NAGRA)
- MinWave prototype flat-panel receive-only antenna added
- CMAF transcoder for re-encoding content from RAI or SES sources
- GMOP (Global Mission Operational Platform) for broadcaster service requests
- OpenTelemetry telemetry collection at every step of the chain
EBU DTH Testbed
| Partner | EBU (European Broadcasting Union) |
| Satellite | Eutelsat GEO, bidirectional |
| Terrestrial IP | Not available (satellite is primary return path) |
| TVR Reference | §3.1.2, §3.2.2 |
| E2E Scenarios | 3 (Linear, no terrestrial), 4 (VoD, no terrestrial) |
| Performance tests | M, P, R, A.2 |
| Telemetry | OpenTelemetry Platform; user data recorded in PEACH (subject to FTA Player App publishing relevant data) |
The EBU DTH testbed demonstrates bidirectional satellite home delivery where no terrestrial broadband is available. The receiver can operate with or without terrestrial connectivity.
Antennas used:
| Antenna | Type | Size |
|---|---|---|
| Egatel | Fixed rooftop dish | 75 cm |
| Technisat | Fixed small rooftop dish | 33 cm |
| MinWave | Portable phased-array with foldable reflector | — |
Phase 2 additions vs Phase 1:
- MinWave portable foldable antenna integration
- 5G-Orchestrated Multigateway solution (Nextworks)
- Shared telemetry solution (co-developed with SES)
- Playout solution and recommendation system integration
Strand 4 — Direct to Vehicle (DTV)
Viasat DTV Testbed
| Partner | Viasat |
| Satellite | SES ASTRA GEO, bidirectional |
| Terrestrial IP | Available |
| TVR Reference | §4.1 |
| E2E Scenarios | 5 (Linear, terrestrial + sat), 6 (VoD, terrestrial + sat) |
Viasat's testbed evaluates satellite streaming to a bus-mounted antenna, testing pointing and tracking under vehicle motion. The return link uses two MBI solutions (narrowband and broadband) to assess bandwidth versatility.
Key tests: Bi-directional GEO link performance (on-demand and linear); antenna pointing and tracking on a moving bus; MBI narrowband vs broadband return link comparison.
LINKS Turin DTV Testbed
| Partner | LINKS Foundation (Turin) |
| Satellite | Eutelsat GEO Ku-band, receive-only (no return channel) |
| Terrestrial IP | Not available |
| TVR Reference | §4.2 |
| E2E Scenarios | 7 (Linear, no terrestrial, no return link) |
LINKS' 2D-scan hybrid antenna (fabricated Phase 1, finalised Phase 2) is mounted on a vehicle in Turin. Testing progresses from static antenna verification through moving-vehicle tracking to full mobile media delivery with content redistributed to passengers via Wi-Fi / 5G-N3IWF.
Key tests: Static antenna connection verification; moving vehicle tracking; mobile media reception and redistribution to passenger devices.
Strand 5 — Direct to Edge (DTE)
EBU DTE Testbed
| Partner | EBU |
| Satellite | Space Norway (SES receive-only) |
| Terrestrial IP | Available |
| TVR Reference | §5.1 |
| E2E Scenarios | 8 (Linear, terrestrial available), 9 (VoD, terrestrial available) |
The EBU DTE testbed is focused on 5G Media Streaming (unicast) and 5G MBS (Multicast/Broadcast Services) over satellite-extended edge infrastructure.
5G Media Streaming (Unicast) tests:
- Functional E2E: reception on client and mobile FTA App
- Performance E2E: startup times (Scenario M), buffering frequency (P), resolution switches (R), downtime (A.2)
- Publishing user data following 5G-MAG specifications (FTA Player App)
5G MBS tests: Component functional tests (MBSTF, MB-UPF, MB-SMF, AF/AS with MBSTF, gNB MBS signal, UE); subject to availability of external 5G NR MBS components.
Arctic Space DTE Testbed
| Partner | Arctic Space Technologies |
| Satellite | Space Norway THOR-7 GEO (Nittedal teleport → Piteå far-edge); Eutelsat LEO bidirectional |
| Terrestrial IP | Available |
| 5G network partner | Luleå Technical University |
| TVR Reference | §5.2 |
| E2E Scenarios | 8, 9 (GEO receive-only); 10, 11 (LEO bidirectional) |
| KPIs | Throughput (Mbps), Latency (ms), TTFB, TTLB |
| TVR Scenarios | B, I, J, V, A.2 · |
Arctic Space tests FENIX-protocol satellite file transmission over GEO, integrated with a Varnish caching solution and a local 5G network.
| Test | Description |
|---|---|
| API integration | FENIX API calls for content distribution; key integration with Varnish |
| GEO satellite transmission | THOR-7 multicast, throughput measurement and capacity limits |
| 5G connectivity | Device connection through 5G AP to far-edge content; K6 load testing for concurrent user simulation |
| E2E | HLS and VOD content reliably transmitted over satellite and served over 5G without playback interruption |
Maritime Testbed (Telenor Maritime)
| Partner | Telenor Maritime |
| Use Case | Direct to Edge — Maritime |
| Satellite | Space Norway, receive-only |
| Terrestrial IP | Not available |
| TVR Reference | §5.3 |
| E2E Scenarios | 12 (Linear, no terrestrial), 13 (VoD, no terrestrial) |
| Player | QStream (Android only; iPhone not yet supported) |
| Edge component | FTA far-edge gateway (mABR statistics collection) |
The maritime testbed operates on a vessel with 5G small cells, satellite backhaul via Space Norway, and ETSI OSM / Magma core / RAN integration. All infrastructure monitoring tests are proxy-based — no direct player-side measurement unless QStream publishes relevant data.
Infrastructure monitoring tests:
| Scenario | Measurement approach |
|---|---|
| M | HTTP manifest-to-first-segment latency at Edge Gateway |
| P | HTTP request gaps >1.3× segment duration as stall indicator |
| T | Origin server issues via MABR error messages |
| V | Edge Gateway 404 rate increase under 10–20 concurrent 5G users |
| A.2 | Service availability monitoring through error logs |
5G network tests (vessel-specific): Bandwidth stress testing (10–20 users, video streams + Teams calls); small cell signal coverage mapping across vessel decks; 5G handover testing as users move between cells.
5G core/RAN integration tests: ETSI OSM deployment timing; Magma Access Gateway and Orchestrator; full 5G core; 5G throughput and latency.
RAI 5G Broadcast Testbed
| Partner | RAI (Radiotelevisione Italiana) |
| Use Case | Direct to Edge (5G Broadcast) |
| Satellite | SES, receive-only |
| Terrestrial IP | Not available |
| TVR Reference | §5.4 |
| E2E Scenarios | 14 (Linear, no terrestrial) |
The RAI 5G Broadcast testbed integrates 5G broadcast with the satellite content delivery chain, featuring the M1 Adapter Block and related broadcast components. Test plan is a combination of component and E2E tests.
Strand 6 — Direct to Device (DTD)
| Testbed | Partner | WP | TVR Ref | E2E Scenarios | Description |
|---|---|---|---|---|---|
| Keysight Functionality | MediaTek / Keysight | 6.3 | §6.2 | 15 (Linear), 16 (VoD) | Component-level and functional testing of DTD chipset and protocol stack in a controlled lab environment |
| Keysight Performance | Keysight | 6.4.2 | §6.3 | — | System emulator for performance characterisation of DTD receiver chipset under controlled emulated channel conditions |
| Verkotan OTA | Verkotan | 6.4.3 | §6.4 | — | Over-the-air radiated performance measurements of DTD terminals in an anechoic chamber |
| Core Network | — | 6.3.11 | §6.5 | — | Validation of mandatory R17 features for Multicast and Broadcast Services (MBS) within the 5G core |
| DTD End-to-End | — | 6.4.4 | §6.6 | — | Full E2E integrating satellite reception, 5G NR broadcast air interface, and DTD terminal in a realistic deployment scenario |
See also E2E Scenarios and Framework §6 — KVIs and KPIs.