mobilenext - · pdf filemobilenext scalable, ... mme/sgsn mme/sgsn sdg services mme/sgsn...
TRANSCRIPT
MOBILENEXT SCALABLE, ELASTIC AND RELIABLE LTE EPC
December 5rd, 2012
2 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
LEGAL DISCLAIMER
Any product roadmap information in this presentation sets forth Juniper Networks’ current intention and is subject to change at any time without notice.
No purchases are contingent upon Juniper Networks delivering any feature or functionality depicted on this roadmap.
The information provided is protected from disclosure to 3rd parties by mutual NDA agreement.
3 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
AGENDA
§ Mobile Data Network Architecture § EPC Functions § Junipers EPC Architecture § Scalability § Distributed EPC § Summary
4 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
MOBILE DATA NETWORK
Laptop
Smartphone
Feature Phone
2G SGSN
SAE-GW (SGW/PGW/GGSN)
RNC
BTS
NodeB
eNodeB
BSC
3G SGSN
Internet
Other PDNs
MME
Gb
Iu-PS
S1-MME
S1-U
IuB
Abis
S11
PCRF
Gx
HLR/HSS
S6a
OCS
Gy
Gn
Gn
Gr
Services
Transport, Signaling, and Services are often scaled independently. Scaling network in partitions (zones) is a realistic method of operation
5 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
EPC FUNCTIONS S-GW (Serving Gateway or SAE-GW):
§ Is a local mobility anchor for inter-eNB active-mode handovers
− Under control of MME, re-arranges tunnels to direct them to selected eNB
§ Is also the idle-mode anchor § Triggers initiation of paging when a
downstream packet arrives for an idle-mode user (network-requested session establishment); buffers packet pending completion of paging
§ Supports charging functions
− Per user and Qos Class Identifier (QCI)
− For inter-operator charging
P-GW or PDN Gateway § Is the entry-point into the EPS § Mobility anchor for the evolved packet
system bearers (EPS bearers) − Resides in the home network of the
subscriber (H-PLMN) − Manages GTP tunnels towards the
RAN § Assigns the UE IP@ and interfaces to the
PDN via Access Point Name (APN) § Provides reachability info for the UE IP@ to
the external packet data networks (e.g. runs routing protocols)
§ Is a policy management point, for dynamic QoS − Via interfaces to IMS and non-IMS
applications mediated through the policy manager (PCRF)
− Gate control, policing, shaping § Collects call detail records (CDRs) ; § HPLMN Lawful Intercept (LI)
6 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
MOBILENEXT BROADBAND GATEWAY Features:
§ Product family approach: re-uses MX-3D blades
§ Any combination of P-GW, S-GW, GGSN, ePDG
§ Mobility features are built on top of JUNOS => inherits full suite of JUNOS capabilities
§ Can be an MPLS PE, an Agg-Rtr, or a simple CE concurrent with the mobile function
§ Full suite of services § Breakthrough capacity § Integrated charging gateway § One IP address § On-board resource manager daemon
supports zero configuration capacity upgrades § Charging at line rate in (TRIO) PFEs
7 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
MX-960 AND MX2020
8 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
L3 Charging GTP-U FW/NAT
Trio Line Card
Fabric
Trio Line Card MS Card
MS CardTrio Line Card
svc
MX-3D IMPLEMENTATION FOR EPC GW
Fabric
Trio Line Card MS Card
MS CardTrio Line Card
Trio Line Card
GTP-C DHCP AAA DPI/IDP L7 Charging
SBC/ P-CSCF
Feature path
Fast Path
Trio Line Card • Line rate forwarding • Extreme low latency • HW QoS • Counters/Billing • 5-tuple services (L3/L4)
Multi-Services Card • Subscriber record • L7 Services only • DPI • Virtualization possible • Junos SDK
Control Plane User Plane
Services chaining is achieved in the blade
9 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
10 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
11 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
SERVICE CHAINING ON THE MS CARD
Benefits § Better utilization of HW resources lowers CAPEX § Single management interface and common HW lowers OPEX § Chaining multiple JUNOS or third-party services is possible within
one service set § JUNOS native and external SDK based services can be mixed
together § Infrastructure facilitates flow/session management
Multi-Services (MS)
Svc #1
Plug-in Manager Process
Svc #2 Svc #2 Svc #4
Junos SDK Packets In Packets Out
12 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
CAPACITY AND SCALING (*) 14 slots in MX960 of which
§ 12 are for PFE or MS (slots 0 – 5 & 9 – 13) § 3 are used for System Control Boards /SCB (7 – 9) § 2 of the SCP host Routing Engine / RE
PFE Blade § 500k bearer per PFE so 2m bearers § 64m pps at 256B packet size (120 Gbps full duplex) § N:1 redundancy, up to 4:1 (4 active & 1 warm-stand-by)
MS Blade / session § 2.7m subscribers
§ 16k bearer attaches/s § 1:1 redundancy (active/active – checkpointed)
MS Blade / Services ( ): FW, CG-NAT, DPI, etc.
SCB: Slots 6, 7, 8 provide fabric redundancy for a capacity of 240 Gbps (2:1)
RE: 1 :1 redundancy (active/standby)
1 2 3 4 5 60 7 8 9 10 11 12 13
PFE Blade
PFE Blade
SCBRouting Engine (RE)
SCBRouting Engine (RE)
SCB
PFE Blade
MS Blade (session)
MS Blade (session)
MS Blade (services)
MS Blade (services)
MS Blade (services)
MS Blade (services)
MS Blade (services)
MS Blade (services)
(*) “bearer” means bearer equivalents which are default/dedicated bearers or primary/secondary PDP-c’s
13 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
DATA, CONTROL, SERVICE PLANE CARD SCALING COMPARISON
Data Plane (I/O – Line Cards) Control & Service Plane (Processing Cards) Chipset Trio (Tested / 2012) Next Gen Trio (2014) Processor (Tested / 2012) Next Gen Processor
( 2013)
Memory 1G 8G 32G 128G
FD Throughput (IMIX) 160Gbps 500Gbps 8Gbps (DPI) 32Gbps (DPI)
FD Throughput (GTP) 120Gbps 240Gbps NA NA
Bearers 2M 12M 2.66M (S/P GW) 10M S/P GW 7.5M SAE GW
Card Type Fixed 16x10GE
Modular 24x10GE / 4x100GE
MS-DPC Next Gen MS-DPC
Conclusions NG Trio I/O line cards have 8x more memory and 3x more processing capacity (2x for GTP processing) than currently available line cards. This will allow them to support 6x more bearers than current hardware.
Next Gen Processing Cards have 2x more processors, 4x more memory and 2x more processing capacity. This will allow them to support 4x more DPI and ~3x more bearers than current hardware.
1
1. Identical card type used for control and service (DPI) processing. Function (control or service) based upon configuration. 2. Chipsets remain in same family to ensure code compatibility with predictable scaling improvements
2
14 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
VIRTUALIZATION OF THE MOBILE PACKET CORE MULTIPLE DEPLOYMENT OPTIONS FOR THE JUNIPER EPC
• Hybrid (Traditional / Traditional+) • JunosV App control & services • User Plane in Trio • Junos & non-Junos apps • 12-228Mbearers / unlimited control & services
• Fully COTS (Traditional+) Control, inline services & users on COTS • Junos & non-Junos apps • Unbounded Control, Services, User Plane architecture
Control Services
vTrio
Evolved MX Cloud Attached EPC Cloud EPC
Control Services
Control Services Control Services
User
• Fully Integrated (Traditional) • ASIC evolution • Next Gen MX chassis • Next Gen Services Cards • Junos & Junos SDK apps • 24M Bearers & 128G DPI (2013) • 60M Bearers & 192G DPI (2014)
• Independent 3D scaling in all 3 hardware architectures • Common MobileNext software platform • Junos & 3rd party SDK applications supported
Architecture
Platform Features
Use Cases • High throughput • Network optimized
• Any performance & scale • Network & Service optimized
• High compute • Service optimized
Control
Services
MobileNext
User User
15 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
JUNIPER'S VIRTUALIZATION STRATEGY
16 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
BENEFITS OF EPC VIRTUALIZATION
Capacity & Scale
Elasticity
Service velocity
Application acceleration
17 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
OTT Services
VPN
Content
Video
CLOUD-ATTACHED EPC EPC ARCHITECTURAL VISION
Juniper MX Platform
MME/SGSN MME/SGSN MCG MME/
SGSN
MME/SGSN MME/SGSN MBG
Control Plane
MME/SGSN MME/SGSN SDG Services
MME/SGSN MME/SGSN Inline Services
eg PEP, DNS
COTS Compute Platforms
VM
• JunosV App Engine
• Service chaining • 3GPP Control Plane
Subscribers
Mobile Core Director
VM VM VM VM VM VM VM VM
• Elastic capacity
• Subscriber anchor
18 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
JunosV APP ENGINE & JUNOS SDK EVOLUTION OF JUNOS SDK FOR CLOUD ATTACHED EPC
APIs provide Junos (control + data) access to apps
on Juniper devices and developed/ported using a
Junos-like dev environment
Junos SDK (Current)
Extend the model with JunosV APIs providing Junos (control + data) access to apps running on a
Virtual plane on/off box and developed/ported on
OS/Language of choice
Junos SDK (with JunosV)
High (data) Performance Tight Coupling with Devices
Single node deployment
Flexibility, Faster Time to Market (and Develop),
Lower Cost
19 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
JunosV APP ENGINE VIRTUALIZATION VALUE PROPOSITION
§ Software and hardware consolidation
§ Lower cost options than linecard
§ Scaling compute and storage independently
§ Platform and service mgmt integration
§ Deploy using CLI, Space, NETCONF OSS tools
§ No service porting, Faster TTM
§ No Jnpr dependency, Faster TTM
§ Any services applicable to Junos
§ Junos SDK Remote APIs in multiple OS and languages
§ Cloud architectures
§ Efficient, Extensible, Elastic
CAPEX and OPEX Savings Business Agility
Best of breed platform for network application economics
20 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
APPLICATION OAM WITH JunosV APP ENGINE § Junos is a central point of OAM for services that operate on VMs § JDAF is an internal OAM interface between Guest application with
Junos to create a single management entity § JDAF exposes Configuration, Operational State, Fault &
Performance interfaces from Guest Application
VSE appliance
Centos Host OS
KVM Hypervisor
Guest OS
Guest Application JDAF
Juniper RE
JDAF
JUNOS
Juniper PFE
External Interfaces Eg SNMP, syslog
MX COTS
21 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
DATA PLANE WITH JunosV APP ENGINE § Service Engineered Path (SEP) tethers Services plane to the MX § Tethered Services appear identical to integrated Services § JunosV orchestrates SEPs from MX to VM applications § SEPs will be built using stateless GRE
Routing Engine (RE)
VSE Appliance
KVM Hypervisor
Centos (Host OS)
Virtual Junos
Juniper App
Linux (Guest OS)
Other App
Ingr
ess
MP
C
Anc
hor M
PC
Egr
ess
MP
C
SEP Mobile Traffic
MX COTS
22 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
MOBILE CONTROL PLANE WITH JunosV APP ENGINE • JunosV instantiates Virtual Junos VM’s which run MobileNext Control • SEP’s are created for each PFE to interact with MobileNext Control • Fully distributed MobileNext Control VM’s • Resource manager controls VM & MSDPC resources • 1:1 hot standby
Routing Engine (RE)
VSE Appliance
KVM Hypervisor
Centos (Host OS)
Virtual Junos
MobileNext Control
PFE
PFE
PFE
SEPs
MX COTS
VSE Appliance
KVM Hypervisor
Centos (Host OS)
Virtual Junos
MobileNext Control
Act
ive
Hot
Sta
ndby
Resource Manager
Virtual Junos
23 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
MX WITH (TETHERED COTS) - AT&T’S “TRADITIONAL +) § Services hosted on external compute nodes § Control Plane hosted on external VMs § Service Engineered Paths (SEPs) via MX for forwarding § MX as statefull load balancer to virtual application service
chains § Management/Steering via JUNOS for external interfaces
Services & Control Plane hosted on MX chassis as well as external compute nodes
§ Single managed (logical) entity
DPI SAE-GW User Plane
“A” Users / “B” Users
NAT HTTP Content Manipulation
SAE-GW User Plane “A” Users / “B” Users
Other Service SAE-GW User Plane
“A” Only
SAE-GW Control Plane
COTS
24 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
SUMMARY
§ Juniper’s MobileNext solution is ready to meet all of AT&T EPC requirements, scaling in all three dimensions and providing a path from the traditional design to a cloud based architecture.
§ Juniper is able to deliver a complete service zone or its components scaling from small to very large configurations.