Orion: RAN Slicing for a Flexible and Cost-Effective Multi-Service Mobile Network Architecture
XENOFON FOUKAS *†, M AH ESH K. M ARINA *, KIM ON KONTOVASILIS †
*The University of Edinburgh † NCSR “Demokritos”
Orion: RAN Slicing for a Flexible and Cost-Effective Multi-Service - - PowerPoint PPT Presentation
Orion: RAN Slicing for a Flexible and Cost-Effective Multi-Service Mobile Network Architecture XENOFON FOUKAS * , M AH ESH K. M ARINA * , KIM ON KONTOVASILIS * The University of Edinburgh NCSR Demokritos Service-oriented 5G
XENOFON FOUKAS *†, M AH ESH K. M ARINA *, KIM ON KONTOVASILIS †
*The University of Edinburgh † NCSR “Demokritos”
Connected Car Factory Automation Video Connected City Smart Sensors Smart Grid
Data Rate Latency Mobility Density Reliability
Conventional One-size Fits All Mobile Network Architecture - Optimized for Mobile Broadband
Fixed and Rigid
Radio Access Network (RAN) Physical Network 1 Physical Network 2
Radio Access Network (RAN) Physical Network 1 Physical Network 2
Virtual Network – Slice 1 Virtual Network - Slice 2
Virtual eNodeB Virtual MME Virtual S-GW
Radio Access Network (RAN) Physical Network 1 Physical Network 2
Virtual Network – Slice 1 Virtual Network - Slice 2
Virtual eNodeB Virtual MME Virtual S-GW
RAN Slicing Approaches
RAN Slicing Approaches RAN Sharing (e.g. [NVS - IEEE/ACM TON 2012], [FlexRAN use case – CoNEXT 2016]) ✔ Efficient and adaptive use of radio resources
X No functional isolation
RAN Slicing Approaches RAN Sharing (e.g. [NVS - IEEE/ACM TON 2012], [FlexRAN use case – CoNEXT 2016]) Full isolation (e.g. [FLARE – JIP 2017]) ✔ Efficient and adaptive use of radio resources
X No functional isolation
✔ Functional isolation
X Inefficient use of
radio resources
RAN Slicing Approaches RAN Sharing (e.g. [NVS - IEEE/ACM TON 2012], [FlexRAN use case – CoNEXT 2016]) Full isolation (e.g. [FLARE – JIP 2017]) ✔ Efficient and adaptive use of radio resources
X No functional isolation
✔ Functional isolation
X Inefficient use of
radio resources
Orion RAN slicing system
underlying RAN resources
Physical Base Station Orion Hypervisor
Virtual Control Plane Virtual Control Plane
Physical Base Station Orion Hypervisor
Virtual Control Plane Virtual Control Plane
Hardware and spectrum
provider Shared physical layer
Physical Base Station Orion Hypervisor
Virtual Control Plane Virtual Control Plane
Control-data plane separation
Physical Base Station Orion Hypervisor
Virtual Control Plane Virtual Control Plane
Customized Control Operations (Schedulers, Mobility managers etc.) Virtual Network Functions
Physical Base Station Orion Hypervisor
Virtual Control Plane Virtual Control Plane
Radio resources and data plane state must be isolated among control planes
Physical Base Station Orion Hypervisor
Virtual Control Plane Virtual Control Plane
radio resources
data plane state
Dynamically partition resources to slices based on SLAs
Abstract the frequency dimension
Generic and applicable to different OFDM-based RATs
Slice 1 Slice 2
Frequency Dimension Abstract index-based dimension
Frequency Dimension (Sub-carriers) Physical Radio Resources Slice 1 Slice 2 View in Slice Control Planes
Frequency Dimension (Sub-carriers) Physical Radio Resources
vRRB 1 Capacity = 2 vRRB 2 Capacity = 1
Slice 1 Slice 2 View in Slice Control Planes
Frequency Dimension (Sub-carriers) Physical Radio Resources
vRRB 1 Capacity = 2 vRRB 1 Capacity = 2 vRRB 2 Capacity = 1
Slice 1 Slice 2 View in Slice Control Planes
Physical radio resources (and vRRBs) cannot always be used in all combinations for the scheduling of a UE
Physical radio resources (and vRRBs) cannot always be used in all combinations for the scheduling of a UE
e.g. UL scheduling in LTE
Frequency Dimension
Valid resource allocation (contiguous allocation)
Physical radio resources (and vRRBs) cannot always be used in all combinations for the scheduling of a UE
e.g. UL scheduling in LTE
Frequency Dimension Frequency Dimension
Valid resource allocation (contiguous allocation) Invalid resource allocation (non-contiguous)
Physical radio resources (and vRRBs) cannot always be used in all combinations for the scheduling of a UE
e.g. UL scheduling in LTE
Frequency Dimension Frequency Dimension
Valid resource allocation (contiguous allocation) Invalid resource allocation (non-contiguous)
Problem for slice control plane when abstracting the frequency dimension 3 1 2 3 1 2 vRRBs vRRBs
Contains 1 or more vRRBs A UE can only be allocated vRRBs from a single pool
vRRB pool #2 vRRB pool #1
Frequency Dimension Physical Radio Resources
vRRB 1 vRRB 2 vRRB 3
vRRB pool #2 vRRB pool #1
Frequency Dimension Physical Radio Resources
vRRB 1 vRRB 2 vRRB 3
Slice schedules UE using either pool 1 or 2 (mutually exclusive)
UE 1 IMSI 1234
Slice Information Service
IMSI 1234
Random Access
UE 1 IMSI 1234 UE 1 bearers, HARQ, Tx Queue Sizes ...
UE 1 IMSI 1234 UE 1 bearers, HARQ, Tx Queue Sizes ... UE 2 IMSI 5678 UE 2 bearers, HARQ, Tx Queue Sizes ...
Orion Physical Base Station
Slice 1 Control Plane
Virtual Data Plane State Virtual Radio Resources Custom Control Functions
Slice 2 Control Plane
Virtual Data Plane State Virtual Radio Resources Custom Control Functions
Orion Physical Base Station
Slice 1 Control Plane
Virtual Data Plane State Virtual Radio Resources Custom Control Functions
Slice 2 Control Plane
Virtual Data Plane State Virtual Radio Resources Custom Control Functions Isolated Communication Channels (message-based communication)
Orion Physical Base Station
Slice 1 Control Plane
Virtual Data Plane State Virtual Radio Resources Custom Control Functions
Slice 2 Control Plane
Virtual Data Plane State Virtual Radio Resources Custom Control Functions Isolated Communication Channels (message-based communication) Deploy in isolation (e.g. in VMs/ containers or separate physical machines)
Slice 1 controller Load Balancing Slice 1 controller Load Balancing Slice 2 controller Cross-layer
Slice 2 controller Slice 2 controller Orion Hypervisor Orion Hypervisor Orion Hypervisor Orion Hypervisor
Implemented over OpenAirInterface open source LTE platform
and to support multiple core networks over the same eNodeB
resource abstraction
RAN Sharing FlexRAN use case – CoNEXT 2016 Full isolation FLARE – JIP 2017 ✔ Efficient and adaptive use of radio resources
X No functional isolation
✔ Functional isolation
X Inefficient use of
radio resources
Scalability Comparison with state-of-the-art Impact of communication channel Isolation capabilities Flexible radio resource allocation Deployment in an end-to-end setting
FLARE with 2 slices, each with 5MHz of spectrum as baseline Orion with 2 slices and a pool of 10MHz of spectrum Slice 1:
various rates (4-12Mbps)
Slice 2:
supporting multiple bitrates
FLARE with 2 slices, each with 5MHz of spectrum as baseline Orion with 2 slices and a pool of 10MHz of spectrum Slice 1:
various rates (4-12Mbps)
Slice 2:
supporting multiple bitrates UEs in FLARE retain the same video bitrate
FLARE with 2 slices, each with 5MHz of spectrum as baseline Orion with 2 slices and a pool of 10MHz of spectrum Slice 1:
various rates (4-12Mbps)
Slice 2:
supporting multiple bitrates Orion slice 2 borrows unused resources from slice 1
Orion assumes 1:1 relationship between UE and slice
environment (e.g. MVNO with OTTs)
Orion service container extension
OTT applications
Orion RAN Slicing System
Future Work
paradigm