Upload
others
View
0
Download
0
Embed Size (px)
Citation preview
Mobile & Financial Services Need for Accurate Timing and MonitoringTiming & Mobile Content Services and Financial Service Connectivity with SD_WAN
Ian Goetz, Juniper Networks
November, 2017
Market Trends:Cloud, Agility, Virtualisation & Content
Mobile & Enterprise Market Trends: The Customer Experience
Pervasive Coverage Seamlessly Converged Trusted Reliability Application Optimized
• MOBILE:• The Smartphone and Tablet, combined with 3G HSPA and 4G have driven the proliferation of
applications for business, lifestyle and pleasure – BUT Most Value Added Services are now OTT• 4G Advanced and 5G drive towards low latency for IoT and Content is key for consumer segment
• ENTERPRISE:• Moving applications to the cloud for scale, agility and cost reduction• Security becoming paramount• Agile, cost effective connectivity – the rise of SD_WAN
MOBILE ENTERPRISE
Cloud Agility Cost Security
MOBILE: RAN Evolution & Content
Driving Timing Requirements
“I Have LTE-A & No Timing Problem”: LTE-Advanced: Carrier Aggregation
Hub SiteRouter
Macro CoverageArea
UE
Up-LinkFreq
Down-LinkFreq
• LTE-A is already with us and deployed in many 4G networks
• Carrier Aggregation is the simplest method to provide UE’s with increased peak rate speeds
• Using 3GPP R8 & 9 compatible carriers
• Component Carriers are aggregated
• Can be 1.4, 3, 5, 10 or 20MHz (Max)
• Maximum 5 Component carriers = 100MHz
• Can be different in UL & DL
• The eNode B requires only LTE Frequency timing
• 16ppB
LTE-Advanced: Coordinated MultipointAccurate Timing (Phase & Frequency) & Low Latency Are Key
Site 3
Site 2
• Black: Uplink Intersite between cells B1 and A2• Red: Downlink Intersite from B1 and A2• Grey: DL Intrasite between A1 and C1
Feature of 3GPP Rel.11NB: Full Gains realized with R11 Ue!
Site 1 Site 4
MX104DSecGW (LTE-A)
LTE-A X2 IPsec PinnedAt Hub Site
SRX5800LTE SecGWHA Cluster
S1-U & S1-MME IPsec TerminatedAt Core
LTE X2 PinnedAt Core
• LTE Requires Frequency Timing: 50ppB• LTE-A (Uplink CoMP & eICIC) Require Frequency & Phase:
• Frequency16ppB, Phase +/- 0.5µSecs
Hub Site
Core Network Site
eICIC: enhanced Inter-Cell Interference CoordinationAccurate Timing (Phase & Frequency) Are Key eIC IC Feature of 3GPP Rel.10
Hub SiteRouter
Macro CoverageArea
UE1
UE2
• eICIC was introduced in 3GPP R10, aim is to improve Cell Edge Radio performance, gaining
more from valuable spectrum
• The Macrocell transmits ABS (Almost Blank Subframes) and sends pattern to small cell via X2
• Low Latency and accurate timing (Phase & Frequency) are key
Small CellCoverage Area
AB
S
AB
S
AB
S
Macro Cell Downlink Radio Frame (Reduced Power
Small Cell Downlink Radio Frame, Cell Edge UEs told to transmit in ABS subframes
UE’s At Cell Edge
UE1
UE2
X2AP MessageABS Pattern fromMacro to small cell
Mobile Backhaul Environment: The Move To LTE-A And On To 5G• LTE-A Features such as Coordinated Multi-Point (CoMP) and Enhanced Inter-cell Interference Coordination, (eICIC) become available as s/w upgrades to
4G base stations from 2016
• These features drive close coordination between cell sites and place requirements on the backhaul network:
• Timing: Frequency & Phase: Frequency16ppB, Phase +/- 0.5µSecs
• Distributed Security: X2 Handover Interface requires a latency of <3-5ms
• Accurate timing with many vendors current and installed backhaul solutions is a major change as accuracy relies on hardware
• The Core LTE Security Gateway remains at the Core site to terminate the S1 IPsec tunnels and to protect the EPC, Distributed LTE-A SecGW For X2, on
the Hub-Site, deployed at Fibre Edge
CORE “Switch” Site
IP Access Network
POC3Hub Site
MacroCell Site
EDGERouter
EDGERouter
CSR
CoreLTESecGW
SRX5800
MX104
Hub Site
LTE S1 Traffic
LTE X2 Traffic
LTE-A S1 Traffic
LTE-A X2 Traffic
LTE Security Gateway (SecGW)
Provide IPsec Termination For LTE S1 & X2Protects EPCProvides IPsec Termination for LTE-A S1Other security features available
Hub – Site Router
Distributed SecGW can be added using MS-MICProvides IPsec Termination for LTE-A X2
Source: Qualcomm
eMBMS: Broadcast Requires Tight Timing - Phase
• Some content is consumed by many users at the same time
• Mobile broadcast is the efficient method of delivery: eMBMS
• eMBMS Requires Accurate Timing: Frequency16ppB, Phase +/- 1.5µSecs
• Current, purely frequency timing based IP Backhaul networks cannot support this
service without addressing timing distribution
Core Network Site
Internet/
Roaming
Partner
SGi
LI
SGiService LAN
Small Cells
WiFi
Core LTESecGW
S1EPC
Hub Site
Macro Cell
Macro Cell
Multi-Access Edge Computing (MEC) & eMBMS
Multi-Access Edge Computing (MEC) offers application
developers and content providers cloud-computing
capabilities and an IT service environment at the edge of the
mobile network
MEC Characteristics
• Proximity
• Ultra-low latency
• High bandwidth
• Real-time access to radio network information
• Location awareness
MEC Standardised by ETSI ISG MEC
Consumer-oriented services
Operator and 3rd party services
Network performance and QoE Improvements
Mobile Video Delivery Optimization using throughput
guidance for TCP
Local content caching at MEC
Mobile Backhaul Optimization
Traffic De-duplication
Security, safety, data analytics
Active device location tracking
MEC edge video orchestration
Enterprise Mobility Services inc. Local Breakout
V2I
Augmented reality, assisted reality, cognitive
assistance
Gaming and low latency cloud applications
Edge video orchestration
Edge Compute Services: MEC & SDN Automation• MEC Enables applications to be deployed at the mobile network edge
• SDN Enables the chaining of MEC Applications and the Life-cycle Management of MEC Application VNFs using automation
• SDN Automation & Creation of services chains in the Telco Cloud DC and MEC Eco-system
• VNF Orchestration, such as Juniper Contrail Service Orchestrator, can be used to instantiate VNFs and manage their Life-Cycle
• Service chaining is needed to automate the link of IPsec termination (vSecGW), MEC Server & MEC Applications
Hub Site
Small Cell Hub
Enterprise uCPE
HubSite
WiFi & Smallcell HetNet
OS
VM1
vSecGW
JunipervSRX
Hypervisor (KVM)
x86 COTS Server
Juniper SDN Service Chaining
S1-U IPsec
VM2
MECSERVER
SDN Control Link
VM3
MECApplication
1
Hub Site: SDN Enabled MEC
Enterprise uCPE
Juniper MX104
S1-U IPsec
Subscriber A
Subscriber B
VM5
MECApp
2
VM4
vSecGW
JunipervSRX
Internet/
Roaming
PartnerS1
SGi
LI Charging
Core LTESecGW
SGiService LAN
Core Network Site
EPC
SDNControl&VMOrchestration(ETSI NFV)
Virtualised NetworkFunctions
e.g.• EPC, MGE/MSC Server• HLR/HSS, IMS• IN, PCRF• SBC, CMTS• NAT, Gi LAN
MECGateway
LI Charging
VM.. N
MECApp
N
C-RAN Site
Small Cell Hub Site
Enterprise Site
Pre-Agg/Hub Site
Core Network Site
Internet/
Roaming
Partner
MEC edge applications
MEC Server (Access)
MEC Gateway (Core)
MEC Deployment options
Small Cells
WiFi
Compute CPEOr
COTS Server
Small Cells
Macro Cells
RemoteRadioHeads(RRH)
OutdoorSmall Cell Hub Router
COTS ServerAdjacent to Pre-Agg
Router
COTS ServerAdjacent to C-RAN
Control Server
S1 SGi
LICharging
EPC
Core LTESecGW
SGiService LAN
Charging
LI
NOTE: • MEC Gateway is currently being examined by ETSI ISG MEC• Makes a useful point to link MEC to LI and Charging• Connects to MEC Server, bypassing the EPC
Main Focus Areas
Hubsite Router
Backhaul Connection
SRX LTE SecGW
Operator EPC
S1 IPsec
S1
S1 IPsec Backhaul
SGi
S1
MEC Control
API
S1 GTP
eMBMS ServerMEC Application
S1 IP
vSRXvSecGW
S1 IPsec
Contrail vRouter
X86Server
X86Server
MX104
S1 IPsec
OPERATOR Core Network
ChargingLI
S11 Tap
HUB SITE
Hub Site Coverage Area
MEC Gateway
• MEC Allows high bandwidth content to be distributed into the RAN• Reduced EPC load
• However, timing accuracy is now from the MEC Application – eMBMS server to the base stations
MP3
Multi-Access Edge Computing (MEC) & eMBMS
Macro Cell
Macro Cell
Macro Cell
MEC ServerPhase Timing: +/- 1.5µSec
Contrail Service Orchestrator (CSO) & Contrail SDN Controller
ENTERPRISE:SD_WAN & MIFID2
Cloud CPE Solutions
Centralized and Distributed
VNF
Cloud CPE Centralized VNF on server in Telco Cloud
VNF
Cloud CPE DistributedVNF on Juniper NFX device
VNF
Cloud CPE HybridCombined
VNF
Juniper SD_WAN Cloud CPE
x86 Appliances
PE
PEP
P
P
P
PE
PE
VPN Network
PE
PEP
P
P
P
PE
PE
Internet Peering Network
Cloud Service Providers
NATvFirewallJuniper vSRX
Contrail vRouter
Operator POP
Contrail
Networking
SDN
Controller,
CSO
Orchestrator
& Openstack
VIM
3rd PartyVNFs
Gateway
LTE
ISP Broadband
Managed Access
Enterprise Site
NFX Compute SD_WAN CPE(Timing Solution installed as local VNF)
VNFs
Financial Service: SD_WAN With MIFID2 Compliance
• From 2018: US & EU Regulation Requires Financial Trading to time stamp all packets to sub -
µSecond level
• Remote Trading sites with SD_WAN will need to comply
• Requires uCPE to run a suitable timing based application to time stamp all packets for the trading
service
• Most uCPE devices currently allow KVM VNFs or Containers
Operator POPEnterprise Site
x86
NFX Compute SD_WAN CPE(Timing Solution installed as local VNF)
SD_WAN
Backhaul
vSRX vCPE Gateway
Network PerformanceApplication (Core / Cloud)
Timing OP1: Network PerformanceApplication (Local)
TIMING OP2: Network PerformanceApplication (Local)
Timing OP3: NetworkPerformanceApplication
Part of vCPE Cloud Service Chain
Timing OP2: Network PerformanceApplication (Lab)
Enterprise CustomerData Centre or Public/Private Cloud
Thank youThank you