انتقل إلى المحتوى
Network Slicing · 3GPP SA5 · URLLC · eMBB · mMTC

One Physical Network.
Infinite Dedicated Pipelines.

Network slicing (3GPP Rel-15/16, SA5) partitions a single 5G SA infrastructure into isolated virtual networks — each with guaranteed latency, bandwidth, and reliability SLAs. HCT designs, deploys, and manages multi-tenant sliced networks for the most demanding operational environments in Yemen.

Design Our Network SlicesPrivate 5G Platform
3Slice Types: URLLC · eMBB · mMTC
<1msURLLC Air Interface Latency
100%Slice Isolation — No Crosstalk
3GPPRel-15/16 SA Mode Required
Three Slice Types

URLLC. eMBB. mMTC. One Network Serves All.

3GPP defines three distinct service categories for 5G NR. HCT configures each as an isolated slice on a shared 5G SA core — with different QoS profiles, dedicated UPF paths, and independent SLA guarantees.

SHARED 5G NR RADIO ACCESS NETWORK (Physical Layer)

Slice 1 — URLLC

Ultra-Reliable Low-Latency

  • ✓ E2E Latency: <5ms (1ms air interface)
  • ✓ Reliability: 99.9999% (1 error per million)
  • ✓ QCI: 65, 66, 82, 83, 84
  • ✓ Scheduling: Preemptive mini-slot (0.125ms)
  • ✓ Use: AGV, protection relay, drone C2

Slice 2 — eMBB

النطاق العريض المتنقل المحسّن

  • ✓ Peak DL: 20 Gbps (3GPP Rel-15 spec)
  • ✓ Sustained: 1-2 Gbps per sector
  • ✓ QCI: 1, 2, 5, 7, 8, 9
  • ✓ Use: 4K video stream, AR/VR, backhaul
  • ✓ MIMO: Up to 64T64R beamforming

Slice 3 — mMTC

Massive Machine-Type Comms

  • ✓ Density: 1,000,000 devices/km²
  • ✓ Battery life: 10+ years on AA cell
  • ✓ QCI: 6, 70, 79
  • ✓ Power saving: PSM + eDRX
  • ✓ Use: IoT sensors, smart meters, tags

Shared Physical Infrastructure

5G NR RadioShared RAN
5GC AMF/SMFCommon Control
Dedicated UPFPer-Slice Data Path
Network Repo.NRF / NSSF
PCF/UDMPer-Slice Policy
QoS Profiles

5QI Parameters HCT Configures Per Slice

5G QoS Identifiers (5QI) define the scheduling priority, delay budget, and error rate for each traffic class within a slice. HCT tunes these per application, not per slice type generically.

5QISlice TypePriorityDelay Budgetمعدل خطأ الحزمةHCT Application
65URLLC7 (Highest)75ms10^-6MCPTT Voice Floor
66URLLC20100ms10^-6MCVideo Signaling
82URLLC1910ms10^-4AGV / Robot Control
83URLLC2210ms10^-4SCADA Real-Time
1eMBB20100ms10^-2Conversational Video
2eMBB40150ms10^-3CCTV / MCVideo
5eMBB10100ms10^-6IMS Signaling
70mMTC55200ms10^-6Smart Meter / AMI
79mMTC6550ms10^-2Environmental IoT
HCT Slice Capabilities

Engineering Slices That Hold Their SLAs

Slice Design and Dimensioning

HCT radio engineers model slice capacity using stochastic geometry and 3GPP capacity formulas. We calculate UE density, PRB allocation, inter-slice preemption policies, and dedicated UPF N6 routing before a single rack is racked.

3GPP Rel-16 Compliant · PRB Budget Modelling · UPF Route Design

NSSAI / S-NSSAI Configuration

Every slice is identified by a Service Type (SST) + optional Slice Differentiator (SD). HCT configures the NSSF (Network Slice Selection Function), NSSAI whitelists per UE group, and PCF policies per S-NSSAI — so each device connects only to its authorized slice.

SST + SD Per Slice · NSSF Config · UDM NSSAI Subscription

Per-Slice SLA Monitoring

Real-time KPI dashboards track latency, reliability, and throughput per slice via O1 telemetry. Automated SLA breach alerts with root cause identification — RAN congestion, core UPF saturation, or backhaul bottleneck — within 30 seconds.

O1 Telemetry · NETCONF/YANG · 30s SLA Breach Alert

Slice Isolation and Security

Dedicated UPF per sensitive slice ensures zero data leakage between OT and IT traffic. IPSec tunnel between gNB and slice-specific UPF. VLAN/VRF separation at transport layer. Slice-level firewall policy enforced via PCF/SMF rules.

Dedicated UPF · IPSec · VRF Isolation · PCF Firewall Rules

Dynamic Slice Management via NSMF

HCT deploys a Network Slice Management Function (NSMF) integrated with our IoP orchestration layer. Operators can create, resize, and terminate slices via API or dashboard — no manual core config changes required. Slice lifecycle: under 2 minutes.

NSMF · RESTful Slice API · <2min Slice Lifecycle · HCT IoP

Roaming and Handover Between Slices

UEs that need multiple service types (e.g., a patrol vehicle needing MCPTT and HD video) maintain concurrent URLLC and eMBB slice bearers. HCT configures multi-slice UE registration and seamless handover without slice re-establishment.

Multi-Slice UE Registration · Concurrent PDU Sessions · <1ms HO

الأسئلة الشائعة

What is 5G network slicing?

Network slicing partitions a single physical 5G network into multiple isolated logical networks, each with its own guaranteed bandwidth, latency and reliability profile. Traffic on one slice cannot degrade another.

What is the difference between eMBB, URLLC and mMTC slices?

eMBB slices serve high-bandwidth traffic such as video. URLLC slices serve ultra-reliable low-latency control traffic such as robotics and protection systems. mMTC slices serve large volumes of low-bandwidth IoT sensors. HCT Group designs the slice mix against the customer's actual application set.

Does slicing require a 5G Standalone core?

Yes. True end-to-end network slicing requires a 5G SA core. Non-Standalone deployments running on a 4G core cannot deliver guaranteed slice isolation. HCT Group deploys 5G SA cores for this reason.

Can one enterprise network serve multiple tenants securely?

Yes. Slicing allows a single deployed network to carry separate tenants or departments with enforced isolation, which is how multi-tenant private network deployments are delivered.

Design Your Slices

One Network. Every SLA. Guaranteed.

HCT engineers configure and manage multi-slice 5G SA networks for critical operations across Yemen. Let us model your slice requirements.

Request Slice Design WorkshopPrivate 5G Platform