3.1020 min read

Worked Example: Mobile 5G B2B

Worked Example: Mobile 5G B2B — "5G Fleet Connect Premium"

This is the fifth and final technology-specific worked example in Module 3 (Sections 3.6–3.10), and the most technically advanced. Where previous sections traced broadband B2C (3.6), broadband B2B (3.7), mobile 4G B2C (3.8), and SD-WAN enterprise (3.9), this section introduces three constructs that do not appear in any earlier example: 5G network slicing (dedicated URLLC and eMBB slices with separate SLA guarantees), eSIM bulk provisioning (1,000 eSIM profiles via SM-DP+ instead of physical SIM allocation), and fleet device management (a self-service portal for bulk device lifecycle operations). Despite this complexity, the same COM → SOM → ROM pattern scales identically — the architecture is unchanged, only the technology-specific CFS and RFS definitions differ.

Mobile 5G B2B activation — SOM orchestrates through ROM to provision UDM/UDR, PCF, NSMF, NSSF, SM-DP+, and fleet management

The Most Technically Advanced Example

This example introduces three concepts not seen in Sections 3.6–3.9: (1) Network slicing — dedicated URLLC and eMBB slices with separate SLA guarantees, (2) eSIM bulk provisioning — 500 eSIM profiles via SM-DP+ instead of physical SIM allocation, (3) Fleet device management — a portal for bulk device lifecycle operations. Despite this complexity, the COM→SOM→ROM pattern remains identical.

The Scenario

Customer Scenario

FleetConnect Logistics operates a 500-vehicle delivery fleet across Australia. They need real-time vehicle tracking (URLLC — low latency, high reliability) and driver tablets for route management and proof-of-delivery (eMBB — high bandwidth). Each vehicle has two connections: a tracking IoT module (eSIM, URLLC slice) and a tablet (eSIM, eMBB slice). Total: 1,000 eSIM profiles (500 tracking + 500 tablets).

Order Summary

Attribute	Value
Customer	FleetConnect Logistics (CUST-ENT-3340)
Account	ACC-ENT-7721
Product Offering	5G Fleet Connect Premium (PO-5GFCP-01)
Product Specification	Enterprise 5G Fleet Service (PS-5GFS-01)
Fleet Size	500 vehicles
Devices per Vehicle	2 — IoT tracker + driver tablet
Total eSIM Profiles	1,000
URLLC Slice	S-NSSAI: 1-000001, <10ms latency, 99.99%
eMBB Slice	S-NSSAI: 1-000002, 100Mbps DL, 99.95%
eSIM Platform	SM-DP+ via GSMA SGP.22
Fleet Portal	Self-service bulk device management
SLA	Platinum — 99.99% URLLC / 99.95% eMBB
Contract	36 months, $85/vehicle/month
Rollout	Pilot: 50 vehicles → Bulk: 450 vehicles

Step 1: Solution Design, Slice Selection & Order Submission

Enterprise Solution Design

Fleet Assessment & Slice Design

Solution Design → Slice Catalog

Solution architect reviews FleetConnect requirements. Two distinct connectivity profiles: tracking (URLLC — low latency, small packets, ultra-reliable) and tablets (eMBB — high bandwidth, standard reliability). This maps to two 5G network slices with different S-NSSAI values, QoS 5QI values, and SLA tiers.

eSIM Strategy

Solution Design → eSIM Platform

Physical SIMs impractical for 1,000 devices. Solution uses eSIM (eUICC) with SM-DP+ bulk provisioning. Two eSIM profiles per vehicle: one for tracking IoT module, one for tablet. Profiles can be remotely managed (enable/disable/swap) via fleet portal without physical access to devices.

Coverage & Capacity Check

Solution Design → RF Planning

Operator validates 5G SA coverage across FleetConnect's primary delivery corridors (metro Melbourne, Sydney, Brisbane). 95% coverage confirmed. 4G fallback for remaining 5%. Slice capacity reserved: URLLC (500 concurrent sessions), eMBB (500 concurrent sessions).

Pricing & Contract

CPQ → Pricing Engine

$85/vehicle/month covers both connections (tracking + tablet). Volume discount applied (vs. $120 list price). Total: $42,500/month, $1,530,000 contract value. Platinum SLA included.

Order Submitted to COM

Sales Console → COM (TMF622)

CPQ submits TMF622 order with 2 POIs: POI-001 (URLLC fleet tracking, 500 devices) and POI-002 (eMBB fleet tablets, 500 devices). Each POI is a bulk order item — not 500 individual POIs.

TMF622 — Bulk Enterprise Product Order

COM assigns PO-2024-03445. State: "acknowledged". 2 POIs with bulk quantities: POI-001 (action: add, quantity: 500, sliceType: URLLC, deviceType: IoT-tracker) and POI-002 (action: add, quantity: 500, sliceType: eMBB, deviceType: tablet). This is the first example where a POI has quantity > 1.

Step 2: COM Validation and Slice-Aware Decomposition

COM Processing

Enterprise Credit & Contract Validation

COM → Credit Engine / Approval

$1.53M contract within credit limit. Platinum SLA confirmed available. Enterprise approval workflow completes.

Bulk-to-Individual Decomposition

COM → Bulk Decomposition

COM's bulk handler expands POI-001 (qty 500) and POI-002 (qty 500) into individual service line items. However, certain CFS types are per-slice (not per-device): network slice itself, PCF policy. COM groups intelligently.

Slice-Aware CFS Decomposition

COM → Service Catalog

COM reads PS-5GFS-01 and produces: CFS:5G-Network-Slice (2 — one URLLC, one eMBB, shared across all devices in that slice), CFS:5G-Subscriber-Access (1,000 — one per device/eSIM), CFS:eSIM-Management (1,000 — one per eSIM profile), CFS:Fleet-Portal-Access (1 — single fleet management portal instance).

Rollout Phasing

COM → Phasing Engine

COM creates: SO-PILOT (50 vehicles = 100 subscriber access SOIs + 100 eSIM SOIs + 2 slice SOIs + 1 portal SOI = 203 SOIs) and SO-BULK (450 vehicles = 900 subscriber access + 900 eSIM + 0 slices (already active) = 1,800 SOIs). Slices and portal created during pilot; bulk phase only provisions subscribers and eSIMs.

Service Orders Submitted

COM → SOM (TMF641)

SO-PILOT submitted to SOM immediately. SO-BULK scheduled pending pilot success.

Slice Before Subscribers

Network slices must be created before any subscriber can be assigned to them. COM tags the slice SOIs as dependencies for subscriber SOIs. This is conceptually similar to the hub-before-branch dependency in SD-WAN (Section 3.9) — infrastructure before endpoints.

COM Decomposition: Pilot Phase SOIs (Summary)

CFS Type	Quantity	Action	Key Characteristics
CFS:5G-Network-Slice	2	add	URLLC: S-NSSAI=1-000001, 5QI=1 / eMBB: S-NSSAI=1-000002, 5QI=9
CFS:5G-Subscriber-Access	100	add	50 URLLC (tracker) + 50 eMBB (tablet), per-device SUPI
CFS:eSIM-Management	100	add	eSIM profile per device, SM-DP+ bulk download
CFS:Fleet-Portal-Access	1	add	Admin portal, bulk ops, device lifecycle dashboard

Step 3: SOM Orchestration and CFS → RFS Decomposition

SOM processes slice creation first (infrastructure), then subscriber provisioning (endpoints), then eSIM and fleet portal. This three-phase approach ensures that infrastructure exists before any subscriber is assigned, and that subscriber records exist before eSIM profiles reference them.

CFS:5G-Network-Slice with sliceType=URLLC decomposes into 3 RFS items — one for each 5G core network function involved in slice lifecycle:

RFS Type	Action	Key Characteristics
RFS:NSMF-Slice-Instance	add	sliceType=URLLC, sNssai=1-000001, qos5qi=1, maxDevices=500
RFS:NSSF-Registration	add	sNssai=1-000001, amfSet=AMF-SET-1, coverage=metro
RFS:PCF-Slice-Policy	add	sNssai=1-000001, gbr=guaranteed, latency=<10ms, availability=99.99%

SOM Orchestration Plan (Pilot Phase)

Orchestration Plan: Dependencies

Task	Depends On	Reason
Phase 1: NSMF Slice Instances (2)	(none)	Infrastructure must exist first
Phase 1: NSSF Registrations (2)	NSMF	NSSF needs slice IDs to register
Phase 1: PCF Slice Policies (2)	NSMF	Policy bound to slice instance
Phase 2: UDM Subscriber Profiles (100)	Phase 1 complete	Subscribers assigned to slices
Phase 2: PCF Subscriber Policies (100)	UDM profiles	Per-subscriber policy references UDM record
Phase 3: SM-DP+ eSIM Profiles (100)	Phase 2 complete	eSIM profile needs IMSI from UDM
Phase 3: Fleet Portal Provisioning (1)	Phase 2 complete	Portal needs device records to display

Bulk Orchestration Optimisation

SOM doesn't create 100 individual resource orders for Phase 2. Instead, it uses bulk resource order items — a single TMF652 Resource Order with 100 ROIs for UDM provisioning. ROM's UDM adapter processes these in batch mode (parallel API calls with rate limiting). Similarly, SM-DP+ supports bulk eSIM profile preparation in a single ES2+ batch request.

Step 4: ROM Resource Allocation and Activation

ROM Processing: Phase 1 — Slice Infrastructure

NSMF Slice Instantiation

ROM → NSMF (3GPP 28.531)

ROM's NSMF adapter calls the Network Slice Management Function via 3GPP TS 28.531 API. Creates two network slice instances: NSI-URLLC-FC (S-NSSAI 1-000001, URLLC parameters) and NSI-EMBB-FC (S-NSSAI 1-000002, eMBB parameters). NSMF allocates network resources (RAN slice, transport slice, core slice) and returns slice instance IDs.

NSSF Registration

ROM → NSSF (HTTP/2 SBI)

ROM's NSSF adapter registers both slices in the Network Slice Selection Function. NSSF now includes FleetConnect's slices in AMF slice selection. When a device attaches, NSSF routes it to the correct slice based on subscribed NSSAI.

PCF Slice Policy

ROM → PCF (HTTP/2 SBI)

ROM's PCF adapter installs per-slice QoS policies: URLLC slice gets 5QI 1 (GBR, <10ms, PDB 10ms, PER 10^-6), eMBB slice gets 5QI 9 (non-GBR, 100Mbps). Policies apply to all subscribers in each slice.

ROM Processing: Phase 2 — Subscriber Provisioning (Bulk)

UDM Bulk Subscriber Provisioning

ROM → UDM/UDR (HTTP/2 SBI)

ROM's UDM adapter provisions 100 subscriber profiles (50 URLLC + 50 eMBB) in batch via HTTP/2 SBI (Nudm). Each profile: SUPI, 5G-AKA auth, subscribed NSSAI (assigned slice), DNN (fleet.operator.com). ROM uses parallel API calls with rate limiting (20 concurrent) to respect UDM capacity.

PCF Per-Subscriber Policy

ROM → PCF (HTTP/2 SBI)

ROM's PCF adapter binds per-subscriber policies to slice defaults. URLLC devices get guaranteed bitrate; eMBB devices get best-effort with 100Mbps cap. Policies reference UDM subscriber SUPI.

ROM Processing: Phase 3 — eSIM & Fleet Portal

SM-DP+ Bulk eSIM Preparation

ROM → SM-DP+ (ES2+ REST)

ROM's eSIM adapter calls Thales SM-DP+ via ES2+ REST API. Bulk request: prepare 100 eSIM profiles (50 URLLC + 50 eMBB) with pre-assigned IMSIs from UDM. SM-DP+ generates profiles linked to device EIDs. Profiles are ready for download — triggered when devices are powered on or via fleet portal push.

Fleet Portal Provisioning

ROM → Fleet Management Portal

ROM's Fleet adapter provisions FleetConnect's self-service portal: admin accounts, device inventory (100 pilot devices with eSIM status), bulk operations (enable/disable/swap profile), SLA dashboard. Portal links to UDM, PCF, and SM-DP+ for real-time status.

Resource Allocation Summary (Pilot — 50 Vehicles)

Resource Type	Quantity	System	Details
NSMF Slice Instances	2	NSMF	NSI-URLLC-FC + NSI-EMBB-FC
NSSF Registrations	2	NSSF	Slice selection rules for both S-NSSAIs
PCF Slice Policies	2	PCF	URLLC (5QI 1) + eMBB (5QI 9)
UDM Subscriber Profiles	100	UDM/UDR	50 URLLC trackers + 50 eMBB tablets
PCF Subscriber Policies	100	PCF	Per-subscriber slice binding
eSIM Profiles	100	SM-DP+	50 URLLC + 50 eMBB profiles
Fleet Portal Instance	1	Fleet Mgmt	Admin access + device dashboard

Step 5: Completion Cascade and Bulk Rollout

Completion Cascade

Pilot Phase Completes

ROM → SOM (TMF652 Events)

All slice, subscriber, eSIM, and portal ROIs complete. 50 vehicles provisioned. Devices activated as tracking modules and tablets are powered on in field.

Pilot Validation

FleetConnect → Account Team

FleetConnect confirms: tracking latency <10ms (URLLC slice), tablet throughput >80Mbps (eMBB slice), fleet portal operational. SLA monitoring confirms Platinum targets met. Pilot approved.

Bulk Phase Triggered

COM → SOM (TMF641)

COM triggers SO-BULK. SOM processes: 900 subscriber access + 900 eSIM SOIs. Slices and portal already active — no re-creation needed.

Bulk Provisioning Executes

ROM → UDM / SM-DP+

ROM processes 900 UDM profiles + 900 eSIM profiles in bulk batches. Rate-limited to UDM/SM-DP+ capacity (50-100 concurrent provisioning calls). Total bulk provisioning: ~4-6 hours for 900 devices.

eSIM Profiles Downloaded

SM-DP+ → Devices (SGP.22)

As devices are powered on in fleet depots, eSIM profiles auto-download. Fleet portal shows real-time activation status. FleetConnect ops team monitors progress.

Full Order Complete

SOM → COM → Billing

All 1,000 devices provisioned. COM marks PO complete. Billing starts: $42,500/month. Fleet portal shows 500 vehicles, 1,000 connections, 2 slices, all active.

Order Timeline

End-to-End Timeline

Time	Event	System	State
T+0	Solution design submitted	Sales Console → COM	PO: acknowledged
T+2 days	Enterprise approval completes	Approval Workflow	PO: approved
T+3 days	COM decomposes, pilot SO created (203 SOIs)	COM → SOM	SO-PILOT: acknowledged
T+3 days	Phase 1: NSMF creates 2 slices	ROM → NSMF	Slice instances active
T+3 days	Phase 1: NSSF + PCF slice config	ROM → NSSF/PCF	Slice infra complete
T+4 days	Phase 2: UDM bulk provisioning (100 subs)	ROM → UDM	Subscribers provisioned
T+4 days	Phase 2: PCF per-subscriber policies	ROM → PCF	Policies bound
T+5 days	Phase 3: SM-DP+ bulk eSIM prep (100)	ROM → SM-DP+	Profiles ready
T+5 days	Phase 3: Fleet portal provisioned	ROM → Fleet Portal	Portal active
T+5 days	Pilot SO complete (203 SOIs)	SOM → COM	SO-PILOT: completed
T+7 days	Pilot devices activated in field	Fleet Operations	50 vehicles tracking
T+14 days	Pilot validation approved	FleetConnect	Pilot: passed
T+15 days	Bulk SO triggered (1,800 SOIs)	COM → SOM	SO-BULK: acknowledged
T+16 days	Bulk UDM + eSIM provisioning (~900)	ROM → UDM/SM-DP+	Bulk in progress
T+18 days	Bulk provisioning complete	ROM → SOM	SO-BULK: completed
T+21 days	All devices activated in fleet depots	Fleet Operations	500 vehicles active
T+21 days	Full order complete	COM	PO: completed

What-If Scenarios

Enterprise 5G with network slicing introduces failure modes and change scenarios unique to the 5G domain. Here are three scenarios that demonstrate how COM, SOM, and ROM handle 5G-specific complications:

Scenario: NSMF reports insufficient RAN resources for the URLLC slice in the Brisbane corridor.

ROM marks the URLLC slice ROI as "held" with reason: "insufficient RAN capacity in Brisbane corridor"
SOM escalates to capacity planning — this is not a transient failure, it requires infrastructure decision
Options presented to FleetConnect: (a) reduce URLLC device count in Brisbane, (b) request RAN capacity expansion (2-4 week lead time), (c) fall back to eMBB-only in Brisbane with software-defined latency optimisation
Decision requires customer input — SOM holds the slice SOI in "pending" state
Pilot proceeds in Melbourne/Sydney corridors where URLLC capacity is confirmed
Brisbane URLLC slice provisioned after RAN expansion or scope adjustment

Complete Entity Map

Here is the complete set of entities created across all systems for this 5G B2B fleet order. This is the highest entity count of any worked example in Module 3 — over 4,000 entities across COM, SOM, ROM, and the 5G core network functions:

Entities Created by This Order

Entity	System of Record	System of Engagement	System of Reference	Notes
Product Order PO-2024-03445	COM	Sales Console	—	2 POIs (URLLC fleet + eMBB fleet)
Service Order SO-PILOT	SOM	COM	—	203 SOIs (2 slices + 100 subs + 100 eSIM + 1 portal)
Service Order SO-BULK	SOM	COM	—	1,800 SOIs (900 subs + 900 eSIM)
Resource Orders	ROM	SOM	—	Pilot: ~207 ROIs + Bulk: ~1,800 ROIs
Network Slice Instances (2)	NSMF	ROM	—	NSI-URLLC-FC + NSI-EMBB-FC
UDM Subscriber Profiles (1,000)	UDM/UDR	ROM	—	500 URLLC + 500 eMBB
PCF Policies (1,002)	PCF	ROM	—	2 slice + 1,000 subscriber
eSIM Profiles (1,000)	SM-DP+	ROM	—	500 URLLC + 500 eMBB
Fleet Portal Instance (1)	Fleet Mgmt	ROM	—	Self-service admin portal
Product Instances (1,000)	Product Inventory	COM	—	Per-device subscription
Service Instances (2,003)	Service Inventory	SOM	—	2 slices + 1,000 access + 1,000 eSIM + 1 portal

Section 3.10 Key Takeaways

5G network slicing introduces a new infrastructure layer — slices must be created before subscribers can be assigned, similar to hub-before-branch in SD-WAN
A single enterprise order for 500 vehicles generates over 2,000 service order items and 2,000 resource order items — the highest entity count in Module 3
Bulk provisioning patterns (batch UDM calls, batch SM-DP+ requests) are essential — individual provisioning of 1,000 subscribers would be impractical
eSIM via SM-DP+ enables remote, zero-touch device provisioning — no physical SIM handling for 1,000 devices
Dual-slice architecture (URLLC + eMBB) provides differentiated SLA within a single enterprise account — this is a 5G-specific capability that does not exist in 4G
The fleet management portal is a CFS-level construct provisioned as part of the order — it is not a separate product but an integrated management capability
Slice capacity planning is a new constraint — unlike physical port allocation (broadband) or spectrum (4G), 5G slice resources are dynamically allocated and may require RAN capacity expansion
The COM→SOM→ROM pattern scales identically from a single broadband B2C order (Section 3.6) to a 1,000-device enterprise 5G deployment — the architecture is the same, only the technology-specific CFS/RFS definitions change
Cross-reference: Section 3.11 covers the southbound activation protocols (HTTP/2 SBI, 3GPP 28.531, SGP.22) in vendor-specific detail