SD-RAN v1.1. Techinar - April 28, 2021 | 9am PDT Saurav Das - Open Networking Foundation
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
SD-RAN v1.1. Techinar
April 28, 2021 | 9am PDT
Joe Thome Cory Modlin Saurav Das
AirHop Facebook ONF
SD-RAN Solution
ONF, O-RAN and TIP
O-RAN OSC
Joint Task
Group
SD-RAN v1.0
KPImon
xApp KPImon xApp
μONOS-RIC μONOS-RIC
go-SDK go-SDK
onos-topo* O1t* onos-topo*
O1t*
(R-NIB) (onos- (R-NIB)
(onos-
config) config)
UE-NIB* UE-NIB*
onos-e2sub onos-e2sub
A1t* A1t*
atomix atomix
onos-cli onos-e2-sm * * onos-cli onos-e2-sm * *
onos-e2t onos-e2t
E2AP 1.0 over E2AP 1.0 over
ASN.1/SCTP ASN.1/SCTP
KPM SM KPM 1.0
E2/ CU-C E2
KPM 1.0 SM SM *
UE
E2/ CU-C (OAI) DU / CU (OAI) RANSim
RU / DU / CU (OAI) OMEC
UE (OAI)
USRP+NUCs
USRP+NUCs
OMEC
phone
SD-RAN on hardware SD-RAN in a Box
SD-RAN v1.1 5
test 2 6
eSON srv srv
4 KPImon PCI
KPImon xApp 2 fb-ah xApp xApp xApp
μONOS-RIC μONOS-RIC
go-SDK py-SDK go-SDK
onos-topo* O1t* onos-topo*
(R-NIB) (R-NIB) 3 O1t*
(onos-
(onos-
config) UE-NIB*
UE-NIB* config)
onos-e2sub onos-e2sub
A1t* atomix A1t*
atomix
onos-cli
onos-cli onos-e2-sm * * onos-e2-sm * *
onos-e2t onos-e2t
2 10 onos-operator
2 7
k8s
E2AP 1.0.1 over 1 E2AP 1.0.1 over
ASN.1/SCTP Helm ASN.1/SCTP 1
KPM 2.0.3 SM RC-PRE 1.0 SM 7
2 E2/ CU-C E2 KPM 2.0.3 SM 2
KPM 2.0.3 SM 2
UE
E2/ CU-C (OAI) DU / CU (OAI) RANSim 8
RU / DU / CU (OAI) OMEC
UE (OAI)
USRP+NUCs
USRP+NUCs topo pci pci 9
OMEC gen gen GUI
phone
SD-RAN on hardware SD-RAN in a Box
ONF Collaboration
April 28, 2021
6 © 2021 AirHop Communications, Inc. PageAirHop eSON Overview
• 1-to-1 mapping of cells to Cell Optimization Engine (COE) microservices
• Microservices (COE) dynamically coordinate information among influencing cells
• Fully distributed applications resulting in network level optimization decisions
© 2021 AirHop Communications, Inc. Page 7eSON as an xApp on O-RAN aligned nRT-RIC
SMO / OSS SMO / OSS
O1 PM Streaming
nRT A1 O1
RIC eSON
xAPP
eSON Cluster
nRT-RIC APIs
nRT RIC Services
eSON API E2
eSON API Support
Binary client and API eSON client eSON
eSONclient
•
eSON client
eSONclient
(4G)
client E2 client
• gRPC protobuf eNB/CU/DU eNB/CU/DU
definitions (4G/5G) eNB/CU/DU eNB/CU/DU
gNB/CU/DU gNB/CU/DU
© 2021 AirHop Communications, Inc. Page 8Integration with ONF nRT RIC
eSON system (AirHop) eSON system COE-based architecture
supports (commercially deployed):
COE1 COE2 … COEN
AirHop defined interface • (near real-time) PCI optimization
(gRPC)
xApp adaptor
(Facebook) • near real-time RACH optimization
nRT RIC (ONF) • near real-time Mobility Load Balancing
• Mobility Robustness Optimization
E2AP (ASN.1)
• near real-time UL/DL Inter-cell
Cell1 Cell2 … CellN
interference coordination
E2 node(s)
RANSim (ONF) • …
© 2021 AirHop Communications, Inc. Page 9First feature integration: 4G PCI conflict detection and resolution
• In collaboration with Facebook and ONF, a new
eSON system (AirHop) Service Model was defined (E2-SM-RC-PRE)
COE1 COE2 … COEN
AirHop defined interface
(gRPC)
• near-real time cell registration with eSON
xApp adaptor
(Facebook)
• near-real time provision of parameters:
nRT RIC (ONF) • Cell parameters (ECGI, DL EARFCN, PCI
pool)
• Neighbor Relation Table (NRT)
E2AP (ASN.1) • Add/removal of neighbor relations
Cell1 Cell2 … CellN
E2 node(s) • near-real time closed loop optimization
RANSim (ONF) • PCI collision detection and resolution
• PCI confusion detection and resolution
© 2021 AirHop Communications, Inc. Page 10Next steps
eSON system (AirHop) Onboarding of all eSON features:
COE1 COE2 … COEN
AirHop defined interface
• 5G PCI optimization
(gRPC) • 4G/5G MLB
xApp adaptor
(Facebook)
• …
nRT RIC (ONF) For each feature (use case) gaps in the existing
Service Models (SMs) are identified:
E2AP (ASN.1)
• New service models defined
Cell1 Cell2 … CellN
• Existing service models extended
E2 node(s)
RANSim (ONF)
© 2021 AirHop Communications, Inc. Page 11Thank You © 2021 AirHop Communications, Inc. Page 12
Facebook RIC SDK Facebook
Orchestration & Automation
Design Inventory Policy Config Non-RT RIC
O-RAN A1
Architecture RAN Intelligent Controller (RIC):
Near-RT
A1T
3rd party
O1
O1T
DB xApp
E2T
E2
E1
CU-CP CU-UP CU
F1
O-DU: RLC/MAC/PHY-high
Open Front Haul
O-RU: PHY-low/RF
14TIP-RIA (RAN Intelligence and Automation)
q RIA sub-group overview
ü Launched in July 2020 as a sub-group of the TIP OpenRAN project group
ü 311 total members representing 39 operators and 90 vendors
ü AirHop, ONF and Facebook are contributing members of TIP-RIA
ü Founding Operators: T-Mobile USA, Vodafone, British Telecom
q RIA Goal
ü Enable MNOs and Open RAN ecosystem to collaborate on RAN use case development, testing and deployment
that leverage the strength of Data Science and AI/ML technologies and open interfaces based on industry
standards.
q RIA Use Case Classification & Prioritization
ü 7 Near-RT and 5 Non-RT use cases contributed by operators and vendors
ü Trials are currently planned with lead operators to showcase use cases
15
1Software Development Kit (SDK) Vision
o Open: Make SDK freely available
o Standards-based: SDK is based on O-RAN standard-defined APIs
o Benefits:
ü app vendors: no need to customize per deployment
ü OEMs: large number of apps to draw from
ü operators: access to leading edge AI/ML technology
16SDK Goals
• make apps simple to develop/test
• make apps portable across RIC platforms
xApp (vendor B) xApp (vendor B)
standard-defined interface
RIC (vendor A) RIC (vendor C)
Facebook companySDK Concept
xApp
RIC Abstraction SDK APIs platform-independent
Layer
provided by
SDK implementation portability layer
Portability SDK
A1 (JSON) RIC Platform O1 (NETCONF/YANG,
JSON)
E2 (ASN.1)
Portability SDK 18Portability
• SDK implementation is provided by the platform
xApp vendor
• xApp and SDK APIs remain the same across
SDK APIs platforms
SDK implementation xApp
RIC Platform 1 SDK APIs
SDK implementation
e.g. ASN.1 over TCP
RIC Platform 2
e.g. protobuf over gRPC
Portability SDK 19What does the SDK include?
SDK APIs
- RIC abstraction layer
- SDK APIs SDK implementation
- SDK Implementation
- libraries (e.g. asyncio, Prometheus, HTTP …)
- test framework
- logging framework
- code samples/guides
- tools for ease of deployment/development
20PCI Demo AirHop eSON
System
AirHop
ONF
gRPC
grafana xApp (Python): Facebook
AirHop client
AirHop Adapter
3rd Party
prometheus
SDK APIs SDK (aiomsa)
Prometheus SD-RAN Portability
Endpoint Layer
Logging
gRPC
onos_e2sub onos_topo onos_e2t onos_config
ASN.1/SCTP AirHop test
SD-RAN from ONF onos_ransim vectorsE2 Subscribe Example (preliminary)
xApp (Python):
AirHop client
AirHop Adapter
SDK APIs SDK (aiomsa)
Prometheus SD-RAN RIC
Endpoint Implementation
Logging
22Thank you. Facebook
RANSim in SD-RAN v1.1
24Simulation Model
E2 Agent E2 Agent
Key Entities
● E2 Node is identified by eNBId/gNBId and has a number of
associated cells’ ECGIs
E2 Node E2 Node ● Cell is identified by an ECGI and has geo location, azimuth, arc
width and a list of neighboring cells’ ECGIs
● UE is identified by IMSI, has a geo location, heading, serving cell
ECGI and CRNTI assigned by serving cell
Cell Cell ● Route is assigned to UE via IMSI and has a set of geo coordinates
Cell Cell
Cell Cell as waypoints; intended to drive simulation of UE mobility
Metrics
UE
UE UE
UE ● Set of (Entity ID/Key/Type/Value) tuples, where entity ID can be:
UE UE
UE UE ○ EnbID, GEnbID, ECGI or IMSI
● Allows for simulation of arbitrary metrics and data associated with
Route
Route Route
Route
Route Route Nodes, Cells or UEs
Route RouteRAN Simulator Architecture
to RIC
E2T E2T ... E2T
ASN.1/SCTP
E2 Agent E2 Agent E2 Agent ... E2 Agent
RAN Sim API
RAN Model (nodes, locations, power, E2T bindings, etc.) Nodes, locations, events
E2 Node E2 Node E2 Node ... E2 Node
induce failures, events, etc.
onos ransim CLI
RAN Simulation
KPM SM Handler
Radio Emulation
H/O SM Handler
Node Coverage
RC-PRE SM
Model (YAML)
Handler
Loader
GUI
(“semi-static”)
...
Nodes, SM IDs
Prometheus
Cells, Locations
Metrics
UE Sim API
...
UE UE UE UE UE UE UE UE
UEs & events
UE Model (UEs, node associations, routes, RSSI, etc. control UI counts
induce joins, movement, etc.
manage routes, etc.PCI Conflict Resolution Demo
https://www.youtube.com/watch?v=RJmrXRRGsCM&ab_channel=OpenNetworkingFoundation
27What’s Next?
Upgrades
Ø Keeping up with O-RAN Standards
Ø Moving from 4G to 5G – PCI
New Use-cases
Ø New Service Models
Ø Mobility Load Balancing (MLB)
Ø Mobile HandOver (MHO)
More Integration
Ø Commercial RAN Vendor(s)
Ø Aether (https://aetherproject.org/)
28Thank You https://opennetworking.org/sd-ran/
You can also read
