ieee sdn initiative preindustrial committee workshop on ... · ieee sdn initiative preindustrial...
TRANSCRIPT
© 2013 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
IEEE SDN Initiative
Preindustrial Committee
Workshop on Mobile Edge Cloud
With large fragmentation in the implementation of SDN/NFV, the main objective of Preindustrial committee is to
create technical and economic conditions (with proper guidelines & direction) of interoperability and feasibility of
technologies around SDN/NFV (widened to include the RAN) within the industry and academia using IEEE SDN
initiative.
In order to do this the committee will analyze and evaluate potential methodologies, make recommendations and
create industrial agreements. This committee will look at opportunities and support POC around key technologies
and establish relationships with other groups doing relevant work in Europe, Asia, Americas, Africa, etc. to increase
collaboration & reduce duplication.
IEEE SDN Initiative, Preindustrial Committee
07:00 Breakfast (60 min)08:00 Welcome introduction by IEEE SDN Initiative08:10 IEEE Preindustrial Committee Introduction, Objective, Background (20 min)08:30 Organizers talks on Mobile Edge Cloud9:30 Prof Mung Chiang (45 min)10:15 Coffee Break (30 min)10:45 Prof. Sachin Katti (45 min)11:30 Prof. Guru Parulkar: ON.lab presentation on the proposed POC (45 min)1215 Lunch (60 min)01:15 Participant positions & presentations03:30 Coffee Break (30 min)03:30 Group forming & investigations, 3-4 areas, e.g.:
Service mobility/Content Distribution Radio, core functions disaggregation Control loops, what is centralized, what is at the edge Mobility management
05:30 Group findings06:30 Closing remarks 7:00 Dinner (Hosted by IEEE PC)
(Open) Mobile Edge CloudDraft Agenda (Subject to change based on participation)
(Open) Mobile edge cloud
4 © 2013 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
Cagatay Buyukkoc, PhDIEEE SDN Initiative steering committee member
Preindustrial Committee Co-chair
AT&T Architecture & Design**for Identification only, I don’t talk on behalf of AT&T
“Simplicity is a great virtue but it requires hard work to achieve it and education to appreciate it. And to make matters worse: complexity sells better.”
- Edsger W. Dijkstra
Cautionary Language Concerning “Forward-Looking” Statements
“This presentation contains 'forward-looking statements' which are based on management's beliefs as well as
on a number of assumptions concerning future events made by and information currently available to
management. Readers are cautioned not to put undue reliance on such forward-looking statements, which are
not a guarantee of performance and are subject to a number of uncertainties and other factors, many of which
are outside AT&T's control, that could cause actual results to differ materially from such statements. These
risk factors include the impact of increasing competition, continued capacity oversupply, regulatory
uncertainty and the effects of technological substitution, among other risks. For a more detailed description of
the factors that could cause such a difference, please see AT&T's 10-K, 10-Q, 8-K and other filings with the
Securities and Exchange Commission. AT&T disclaims any intention or obligation to update or revise any
forward-looking statements, whether as a result of new information, future events or otherwise. This
information is presented solely to provide additional information to further understand the results of AT&T.”
5
• Evolution & revolution in parallel
• Rethink everything: Software, Automation,
Shannon, Control, Cellular structure, BS, Spectrum,
AI, Core, RAN, Edge, Complexity, Resilience
• User centric networking
• Control plane (loops) are acting in multiple time
scales & in support of users & networks
• Analytical framework in every aspect (optimization
and more)
• Address density by design, not “band-aid”
solutions, how to balance with complexity?
5G era needs a new thinking in architecture
Re: 5G PPP Horizon 2020
© 2010 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.7
Use cases: (Google wouldn’t be around if use cases drove innovation)GSMA & METIS based use cases
Objective: Lets define the “edge”
Need Business &
Value drivers
Intended &
Uninted consequences!
(Wireless) Network architecture
• A new architectural design philosophy:
• Software Defined, Virtualized & Programmable (SD/VP) ecosystem, address densification (diversity, self-backhauling, M-RAT), use distributed system principles (auto-management, resilience, software architecture,,..) and investigate techno-economical implications with key architectural principles
• NG RAN & NG Core networks are being re-architected in the industry: add edge as a new architectural component
• Many new areas of applications should be enabled by the architecture
Rethink Control loops
• Central control, orchestration, management, policy (ECOMP, various other COMPA, METIS MO,..)• Centralized orchestration, Service composition, Resiliency, Policy extraction (NFR->FR), coordination, Management, A-A-A
• Charging, Big data analytics,
• Edge control, management & policy and Analytics
• RRM* (admission control & QoS), Mobility Management , Subscriber IB proxy, Security (A-A-A), LI, Edge Analytics,
• End device control • End user participation, UCN, cost models, resiliency choices (security, performance,..), economics, more refined UE policy
enfor,…SIM/UICC
• Data plane: Distributed & Programmable to a fine grain
• ETSI/MEC: “Mobile-edge Computing offers application developers and content providers cloud-computing
capabilities and an IT service environment at the edge of the mobile network. This environment is characterized
by ultra-low latency and high bandwidth as well as real-time access to radio network information that can be
leveraged by applications.”
• Fog Computing: “A network architecture that uses one or more end-user clients or near-user edge devices to
carry out a substantial amount of storage (rather than stored primarily in cloud data centers), communication
(rather than routed over backbone networks), and control, configuration, measurement and management (rather
than controlled primarily by network gateways such as those in the LTE core).”
© 2013 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.10
Mobility Edge efforts
© 2013 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.11
ETSI/MEC
Problem space (is same):Mobile Edge Computing
proposes co-locating computing and storage resources
at BS..
Solution idea (is same): MEC servers are deployed
next to base stations: MEC servers are equipped with
cloud HW, commodity hardware etc. and addressing
transparent/pass-through and terminating applications
Components of solution:
• A virtualization layer for abstracting the cloud
resources
• An application platform: VM, and Application
services (Traffic offload, Radio Information
Services, Communication services, Registry etc
• APIs to APPs
Ref: Mobile Edge Computing: A Taxonomy, Michael Till Beck, et. Al.
AFIN 2014 : The Sixth International Conference on Advances in Future Internet
© 2013 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.12
Fog computing/networking
Ref: Finding your Way in the Fog: Towards a Comprehensive Definition
Fog Computing, Vaquero and Rodero-Merino
Problem space (is same): Limited compute/storage on smart devices
might utilize cloud computing as a extension facility;
Solution idea (is same): What if we can add: mobility support, geo-
distribution, location-awareness and low latency. Fog networking/
computing is originally proposed to enable this extension at the “edge”
of the network
Components of solution: (so far no architectural proposal)
• Cloudlet (Satyanarayan) is a resource-rich “cloud in a box”, for use
by nearby mobile devices
• IOx is from Cisco works by hosting applications in a Guest
Operating System (GOS) running in a hypervisor directly on the
Connected Grid Router (CGR)
© 2013 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.13
Edge cloud (Service Mobility)
Ref: Service Mobility in Mobile Networks,
Hany Assasa, Srinivasa Vinay Yadhav and Lars Westberg
Problem space (is same): traffic between UE and services on the public
cloud is “tromboned” towards the anchor point which leads to inefficiencies.
Solution idea is same: Deploying services closer to the UE, near the eNB.
The services are deployed on “small scale data centers” connected to, or
collocated with the eNB, called eNBC.
To make this work solve issues like, mobility management, context
management etc. Excellent prospects on (O)MEC.
Components of solution:
IEEE 802.21 Media Independent Handover,
Context Transfer Protocol,
Session Migration Mechanism
POC with ON.lab:Mobile CORD platform (with EPC UP/CP separation)
Networking Fabric
Front-haul
Optical
Switch
CPRI (E)
Virtualized
BBUs
Edge Service
Functions
EPC control
Applications
CORD
Platform
EPC control
Applications
Backhaul
&
Backbone
Switch
Video
Caching
DNS
Security
SGW-C
PGW-C
XOSMME
OpenStack
ONOS
PCRF
SGW-D PGW-D
vBBU
vBBU
vBBU
Operator’s specific Applications
Mobile Resource & Service Orchestration CORD
Platform (ONOS + XOS + OpenStack)
RadioResource
Scheduling
Network
Slices
LTE,5G
IoT
Enterprise
Real-time
Analytics
MBBMVNO
Testbed
Service
Chaining
SGW-D, PGW-D: Data plane of SGW/PGW SGW-C/ PGW-C: Control plane of SGW/PGW
…
Mobile Edge Mobile Core
SGW-D PGW-D
SGW-C
PGW-C
Service
View
Top
olo
gyV
iew
(Open) Mobile Edge Cloud
• (An open) cloud platform that uses some end-user clients and located at the “mobile edge” to carry out a substantial amount of storage (rather than stored primarily in cloud data centers) and computation (including edge analytics, rather than relying on cloud data centers) in real time, communication (rather than routed over backbone networks), and control, policy and management (rather than controlled primarily by network gateways such as those in the LTE core). (Based on largely Prof Mung Chiang work)
• Develop an architecture to support this vision:
• OMEC concept can be developed based on softRAN OS & fog networking amalgamation & distributed functional decomposition of both NG core and RAN functions on a common cloud platform: (MCORD or similar)
• Partners: Stanford U (Prof Sachin Katti), Princeton U (Prof Mung Chiang), ON.lab, Vendor community, Chip industry, ALL!
© 2013 AT&T Intellectual Property. All
rights reserved. AT&T and the AT&T
logo are trademarks of AT&T Intellectual
Property.
16
Reconstructing the network architecture: Study which ones to move to the (O)MEC ?
Objective: To refactor the E2E network functions based on three industry trends: a) Re-architecting the RAN, b) Re-architecting the NG core c) (very little in
devices)
These two major industry efforts overlap at the mobility edge, and a new rethinking is required to address the mobility edge (and subsequently the converged
wireline/wireless edge).
Progress: Traditionally Core functions & RAN functions are separate. There is a lot of work on the mobile edge as a key architectural component. Several POCs
are being done (here IEEE is supporting one through ON.lab. )
NG RAN
Functions
NG Core
FunctionsRefactor to
NG
RAN
NG
Mobile
EdgeNG Core
Functions
NG UE
Functions
NG
UE
© 2013 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T
Intellectual Property. 17
Capabilities sets (DBs etc.) Subscriber Policy Charging Device
M, O, C, P
E2E Control Applications Mobility mgmt Security QoSNet control&
mon.Optimization
API
Network Topology and
Resource Utilization
SDN ControllerRAN Apps: e.g.,
LTE-A, IoT, Analytics, Slicing
SD RAN Controller
WNOS
UE/dev NGAP NGBS OMEC
D
PC
PD
PC
P
D
P
C
PD
PC
P
MSO Nw Ctr. App Ctr.Fallout
Mgm
(OSS).
Others
Data/Control Interface
API
Access Agnostic Interface
API
SDN based vRAN Reference Architecture (Study Areas)
API
Software Defined RAN Access Agnostic NG Core
Decompose the layers!
Objectives: • Decouple CP/UP, create flexibility
• Distribute CP/DP functions according to apps &transport options using the SD-RAN
• Create open interfaces between layers to drive innovation & insertion of “your secret sauce”
control programs
• Whitebox opportunities
© 2014 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement.
18
RF & A/D CP & FFTRE
demap
Rx procEqual., MIMO
rec IDFT, demap
DEC MACrt IP
RRU BBU
L1 L3L2-RT
• RLC
• Scheduler
MACnrt
L2-NRT
• RLC
• PDCPCP DPCP DP CP DP CP DP
A B C D E F G
I/Q FW
L1’ L1””
SubframeFW
Rx dataFW
SoftBitFW
MACpayload
MACpayload
PDCPpayload
2.46 Gbps*
*Example : 20 Mhz/2x2 antenna config. MCS of Spectral eff=3 bit/cu
720 Mbps* 360 Mbps* 180 Mbps* 27 Mbps*
CPU + NPUDSP/HW Acc./ASICFPGA/ASIC/RF
UE
Specialized/but opening will drive standardization/price drop
CP DP CP DP
Handoverforwarding
Ciphering
Segment
ReTX
HARQ
MCS
MIMO
Mobility Control
Load Balancing
Admission Cntrl
Interference Management
Flow QoSManagement
Scheduler
Power Control
CP/UP decoupling
© 2013 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
19
NG AP
Wi-Fi
Data AP
MANO
Coordination
MANO
Big DataValue added
Services
Refactored
RAN-e
Value added Service Chains
(Firewall,NAT,…)
MVNO
OTT Enterprise
SDN controller
SD RAN Resource
CONTROLLER
E2E Architectural principles
• Simplicity (as opposed to complexity
• Efficiency (Energy & spectrum), Modularity,
Scalability, Flexibility
• Resiliency
• Software architecture focus
• Shared Cloud platform
• Drives an (Open) Mobile Ecosystem
• Compatible with SDN/NFV frameworks that
are Programmable
• Good TCO/flexible transport
• Future proof
• Allows (Easily deployable) Value Creation
platforms
E2E Software Defined Architecture
Capability sets
DB’s, profiles,
device man,
charging,…Refactored
NGxCore-c
Data/Control Interface
Access diversity
Integrated Cloud
InfrastructureAPI
Open Mobile Edge Cloud
Devices
Areas of
Investigation
Refactored
CORE-e
Refactored RAN-c
Flexible transport options
(FH/MH/BH)
Environments
Summary & next steps
5G era is more than an air interface and would require rethinking everything!
No buzzwords: Use a word means developing a capability to measure, analyze!
Mobile edge is a key intersection where 5G will be based
Next steps: Create a common architecture across the industry, unify the approaches,
based on initial decompositions to see what additional POCs to schedule in 2016+.
Need to merge different methodologies in one common architecture: use your secret
sauce on it!
20