5G-EMERGE Global Component Register

Source: Global Component Registry — the canonical inventory of components and their telemetry classifications across all strands.

In this documentation GCR always means Global Component Registry. It is distinct from Gcore, the CDN provider represented in the registry.

Live status for each component entry is on the Telemetry Status page.


Telemetry Categories

The taxonomy used to classify telemetry signals.

Category Signal Type Description
Health Metrics Heartbeat and health check metrics checking for availability and uptime for the component
QoS Metrics —
QoE Metrics —
QoI Metrics —
OA(M) Metrics Operational Analytics using Metrics
OA(E) Events Operational Analytics using Events
OA(L) Logs Operational Analytics using Logs
OA(T) Traces Operational Analytics using Traces

Component Types

The Component Type master list, organised by Service Function group.

Component Type SF In Diagram
Web CMS SF1p Yes
Authentication Authorization SF1p Yes
Personalisation SF1p Yes
Origin (Web) SF1p Yes
Metadata CMS SF1p Yes
Content Discovery API SF1p Yes
Ingest SF1p Yes
Transcode SF1p Yes
Package SF1p Yes
Content Steering (Server) SF1p Yes
Origin (Media) SF1p Yes
5GMSd MBS AS SF2 Yes
MABR Server SF2 Yes
5GC UPF (unicast) SF2 Yes
CDN Proxy SF2 Yes
DVB-S/S2(X) SF3 Yes
5G Broadcast (FeMBMS) SF3 Yes
5GMSd MBS Client SF4 Yes
MABR Gateway SF4 Yes
Content Cache + Edge Compute SF4 Yes
CDN Edge / PoP SF4 Yes
Mini CDN SF4 Yes
5GMSd MBS Client SF1c Yes
Content Steering SF1c Yes
Presentation UI (Test Harness) SF1c Yes
Media Players (Platform Specific) SF1c Yes
CMS Editorial UI SF5 Yes
Service Provisioning SF5 Yes
Analytics UI SF5 Yes
Demand Controller SF5 Yes
Telemetry Server SF5 Yes
Data Collection SF5 Yes
5GC Control Plane SF5 Yes
Service & Network Orchestrator SF5 Yes
Exposure Gateway SF5 Yes
NWDAF SF5 Yes
5GMSd Event Subscriber (R1) SF5 Yes
5GMSd Event Receiver (R6) SF5 Yes
Telemetry Proxy SF5 Yes
5G Direct Data Collection Client SF5 Yes
N3IWF SF4 Yes
UPF (multicast) SF4 Yes
5G Non-3GPP UE SF1 Yes