What a blueprint is here
An Implementation Blueprint is a specific section within a Technology page: a table that walks through a procedure step by step (for example, everything a UE does to acquire and decode a broadcast service), and for each step names the protocol layer involved, the mechanism 5G-MAG's analysis found, and the exact 3GPP clause it comes from. It sits inside the page's normal analysis prose rather than as a separate page type: the same page explains why, the blueprint section is the in-order how.
This is 5G-MAG's own framing, echoed in the "Profiles and Blueprints" language used to describe this portal's mission, not an externally defined 3GPP or ISO deliverable type; there is no formal industry definition of "implementation blueprint" to cite here.
Blueprints published so far
| Blueprint | Covers | Technology page |
|---|---|---|
| MBS Broadcast RAN acquisition | Full UE path for 5G MBS broadcast: MIB, SIB1, SIB20, MCCH, MTCH, up to decoding the broadcast MRB (TS 38.331 and TS 38.321, both V19.4.0) | MBS Broadcast RAN procedures |
| MBS Multicast RRC_INACTIVE RAN acquisition | The RRC_INACTIVE variant of the same path (SIB24, Multicast MCCH-RNTI, distinct MTCH LCID table; TS 38.331 and TS 38.321, both V19.4.0) | MBS Multicast Inactive RAN procedures |
| UE Data Collection reference points (R1 to R6) | Every DCAF interface: provisioning (R1), data reporting (R2 to R4) and event exposure (R5 to R6), with the service/API and endpoints for each (TS 26.531 V19.0.0) | User Data Collection and Reporting |
| DVB-I service discovery bootstrap | Cold start to content-guide data: locating a Service List Registry, querying it, fetching a Service List, selecting a delivery instance, and (for hybrid clients) de-duplicating against a tuned broadcast service | DVB-I Services over 5G |
| 5GMS session establishment | Cold start to streaming: service discovery, resolving Service Access Information, starting the Media Player, manifest/initialisation (progressive download and DASH variants), and continuous playback | 5GMS Architecture |
| MBS Multicast mobility (handover) | Every multicast mobility case: Xn and N2 handover between nodes that support MBS, to and from a node that does not, handover of an inactive session, and UEs in RRC_INACTIVE within and out of the RNA and the Registration Area (TS 23.247 V20.0.0, clause 7.2.3) | MBS Multicast - End-to-End Procedures |
| MBS Service Layer provisioning-to-announcement | Provisioning MBS Services and Distribution Sessions ahead of activation, through content ingest, to building and exposing the User Service Announcement (TS 26.502 V19.6.0) | MBS User Services Architecture |
More Technology pages will get a blueprint section as their procedures are worked through this way; this index is updated as they're added. For the full set of technology areas (with or without a blueprint section), see All projects.
Related
- Technology: the parent pages these blueprint sections live inside.