Consortium Partners
The organisations that make up the 5G-EMERGE consortium, and what each contributes. The list is held in partners.json5 and rendered from there, so it has one home rather than being restated per page.
The contributions are as the programme's work breakdown structure states them, with the work packages each covers. They describe the work, not the organisation: nothing here is a legal description, and where this page and the Consortium Agreement differ the agreement governs.
Who is in the consortium
| Organisation | Contribution |
|---|---|
| EBU | European Broadcasting Union — S1 lead, S4 lead; WP1.2, WP3.2, WP5.1, WP2.4.6 |
| Broadcastcritical | S2 lead (Cross-edge functionalities) |
| HumansnotRobots | S2 prime; WP2.1, WP2.1.1, WP2.1.3, WP2.4.3, WP6.4.1 |
| FTA | Mobile apps (WP2.1.4); mABR/Micro Edge (WP2.4.4, WP2.4.5); DTH gateway (WP3.1.2) |
| Swiss TXT | Business Continuation Management Application (WP2.1.2) |
| Gcore | WAAP AI Security / Edge CDN (WP2.2.1, WP2.4.1) |
| SixSq | Far Edge Firewall (WP2.2.2); Orchestration (WP2.3.2) |
| Varnish | Caching Population and Federation (WP2.4.2); Near/Far Edge DTE (WP5.2.2) |
| HPE | Private 5G Mobile Network and Edge-UPF (WP2.5.3) |
| MBI | Satellite platform integration (WP2.5.5); DTV return link (WP4.1.2); DTH multigateway (WP3.2.2) |
| MinWave | Flat panel antenna development — DTH (WP3.1.1, WP3.2.1) |
| SES | S3 lead; DTH testbed — antenna, streaming, contribution, telemetry (WP3.1) |
| Viasat | DTV — vehicle antenna, link validation (WP4.1) |
| LINKS | DTV — Turin testbed, 2D phased array (WP4.2) |
| Telenor Research | S5 lead; Maritime DTE testbed — vessel 5G, VSAT integration (WP5.3). Abbreviated TR in the WBS. |
| RomARS | Non-3GPP access for the Maritime testbed (WP5.3.2.2, WP5.3.8.2) |
| Arctic Space | DTE — GEO/LEO satellite, far edge cache, 5G campus (WP5.2) |
| RAI | DTE — 5G broadcast testbed, LTE-based terrestrial (WP5.4) |
| Magister Solutions | S6 system modelling lead; 5G NTN technology simulations (WP6.1, WP6.1.3) |
| VTT | NGSO constellation simulation — large-scale system modelling (WP6.1.2) |
| Oulu University | Physical layer simulation (WP6.1.1); Business model and exploitation (WP6.2, led by the Oulu University Business School sub-unit); Use case analysis (WP6.4.5) |
| SnT | University of Luxembourg — MBS mandatory R-17 feature, core network (WP6.3.11) |
| Keysight UK | DTD technology — MBS verification, NR-NTN test (WP6.3.2, WP6.3.3, WP6.3.5, WP6.3.9) |
| Keysight Finland | Channel emulation; final testing support (WP6.1.4, WP6.3.10, WP6.4.6) |
| MediaTek UK | DTD — MBS/NTN integration and device development (WP6.3.1, WP6.3.4, WP6.3.6–8) |
| MediaTek Finland | S6 lead; End-to-end solution and services (WP6.4, WP6.4.2) |
| Verkotan | OTA testbed (WP6.4.3) |
Reading this alongside the test register
The Global Test Register and the testing dashboard both carry an owner for each test, taken from the registry's own Owner column. Those labels are not the names above: the registry shortens HumansnotRobots to HNR and MinWave to Minwave, writes Gcore as G-Core, and names Telenor Maritime and Telenor R&I where this list has Telenor Research. It also names organisations this list does not, including NXW, CYSEC, Brightcove and MediaTek without a country.
So the two cannot be joined mechanically, and this page does not try. Treat the registry's owner as the label the test's author used, and this page as the programme structure.
Further Reading
- Programme Structure — the strand and work package structure these contributions sit in
- Testbeds — how each testbed realises the logical architecture
- Information Sources — which source document each page is built from