5G Network Architecture and the Future Mobile Internet IEEE 5G - PowerPoint PPT Presentation

5G Network Architecture and the Future Mobile Internet IEEE 5G Workshop Princeton, May 26, 2015 D. Raychaudhuri WINLAB, Rutgers University ray@winlab.rutgers.edu

Introduction

Introduction: 5G Vision  Faster radio ~Gbps  Low-latency wireless access ~ms  Dynamic spectrum, multiple radio access technologies  Next-gen network with improved support for emerging mobility services : Content Delivery Vehicular Networks Cloud Services Mobile Data (cellular, hetnet) WINLAB Emergency Networks Internet-of-Things

Introduction: Why 5G Needs a New Network Architecture 5G/NGMN/FIA PCRF TODAY SGW PGW LTE LTE w/FIA Mobility-Centric interface Future Internet Architecture Internet MME 4G Radio Access Network Standard FIA Router MSC HSS WAG FIA Distributed AAA Control Plane WiFi WiFi w/FIA interface Hybrid 3GPP & IP arch  Unified Internet/Mobile Net arch with  integrated support for naming, Complex control interfaces!  authentication, mobility, etc. Technology specific  Simplified distributed control!  IP tunneling in data path  Technology neutral – BS or AP plug-in  Gateways (..bottlenecks, sub-  Flat! No gateways or tunnels!  optimum routing,..) Mobile devices as “first class” citizens  WINLAB

Introduction: Why the Internet needs a new mobility-centric protocol architecture  Historic shift from PC’s to mobile computing and embedded devices…  Mobile data growing exponentially – 3.6 Exabytes in 2014, >> wired Internet traffic  Sensor/IoT/V2V ~5-10B units by 2020  Internet in 2020 all about mobile platforms & services  Inevitable convergence of mobile network and Internet industries Wireless Technology Higher speeds/scale, Trend “5G” “network of networks”  Need to think beyond the “G”’s, associated with linear progression in mobile systems Future “Mobile Internet”  Era of vertically integrated protocol stacks built on radio standards coming to an end New wireless/mobile functions, enhanced  Single end-to-end protocol standard for the future security, services Internet Technology mobile Internet! Trend “FIA” Same end users! Research Target of NSF Future Internet Architecture (FIA) MobilityFirst Project WINLAB

Introduction: What a Converged Mobile Internet Protocol Would Look Like…  Mobility was added to IP after the fact due to historical reasons, but single unified solution remains feasible Previous attempts at convergence such as mobile IP proved to be insufficient…  5G is an opportunity for the industry to address this need with a single unified protocol stack for all  services on the Internet, given that mobile is now the dominant use case Can provide significant improvements: radio technology neutral, improved scalability and security, “flat”  network structure, enhanced mobility functions, … 5G/NGMN/FIA TODAY Server BS/AP UE Router Router TP TP FIA IP+ FIA IP+ FIA IP+ FIA IP+ FIA IP+ DLC xG MAC xG MAC DLC DLC xG PHY PHY PHY xG PHY PHY Radio access specific Future Internet Protocol with Integrated Mobility Support Internet Protocol Custom Access Protocols WINLAB

Next-Gen Mobile Network Requirements

Next-Gen Network Requirements: (1) Mobility  End-point mobility as a basic service of the future Internet  Any network connected object or device should be reachable on an efficiently routed path as it migrates from one network to another  Eliminate service gateways (bottleneck points), IP tunnels, etc. (“flat”)  Fast authentication, dynamic handoff (vertical), and global roaming  Mobility service should be scalable (billions of devices) and fast ~50-100 ms  Implications for core naming/routing/security architecture of Internet AS99 AS39 (LTE) (WiFi ) INTERNET Inter-AS Roaming Agreement  “Mobile Peering” AS49 AS2 User/Device Mobility Measured Inter-Network Mobility Traces (Prof. J. Kurose, UMass, 2013) WINLAB

Next-Gen Network Requirements : (2) Handling Disconnection & BW Variation  Wireless medium has inherent fluctuations in bit-rate (as much as 10:1 in 4G access), heterogeneity and disconnection  Poses a fundamental protocol design challenge  New requirements include in-network storage/delay tolerant delivery, dynamic rerouting (late binding), etc.  Transport layer implications  end-to-end TCP vs. hop-by-hop Mobile devices with varying BW due to SNR variation, AP-2 Shared media access and heterogeneous technologies Dis- Bit connect Rate BS-1 (Mbps) BS-1 Wireless Access Net #3 Time Disconnection INTERNET interval Wireless Access Network #2 AP-2 WINLAB

Next-Gen Network Requirements: (3) Multicast as a Basic Service  Many mobility services (content, context) involve multicast  The wireless medium is inherently multicast, making it possible to reach multiple end-user devices with a single transmission  Fine-grain packet level multicast desirable at network routers Packet- level Multicast at Routers/AP’s/BSs Session level Multicast Overlay (e.g. PIM-SIM) Pkt Mcast at Routers Wireless Access Net #11 Access Network INTERNET (Eithernet) INTERNET Radio Broadcast Wireless Access Medium Net #32 RP WINLAB

Next-Gen Network Requirements : (4) Multi-Homing as a Standard Feature  Multiple/heterogeneous radio access technologies (e.g. 4G/5G and WiFi) increasingly the norm  Improved service quality/capacity via opportunistic high BW access  Improved throughput in hetnet (WiFi/small cell + cellular) scenarios  Can also be used to realize ultra-high bit-rate services using multiple technologies, e.g. 60 Ghz supplement to LTE  Implications for naming and routing in the Internet Multihomed devices may utilize two or more interfaces to improve communications quality/cost, with policies such as “deliver on best interface” or “deliver only on WiFi ” o r “deliver on all interfaces” LTE BS 60 Ghz BS (supplement to LTE) Wireless Access Net #3 Wireless Access Net #3 INTERNET WiFi Wireless AP Multiple Access Potential Network Paths #2 Mobile device With dual-radio NICs WINLAB

Next-Gen Network Requirements: (5) Efficient Content Delivery  Delivery of content to/from mobile devices a key service requirement in future networks (…”ICN”, etc.)  This requirement currently served by overlay CDN’s  In-network support for content addressability and caching is desirable  service primitives such as get(content-ID, ..) In-network cache In-network cache Alternative paths for retrieval or delivery Content Owner’s Server Send(“ content_ID ”, “ user_ID ”)) Get (“ content_ID ”) WINLAB

Next-Gen Network Requirements: (6) Context-Aware Services  Context-aware delivery associated with mobile services, M2M  Examples of context are group membership, location, network state, …  Requires framework for defining and addressing context (e.g. “taxis in New Brunswick”)  Anycast and multicast services for message delivery to dynamic group Context = geo-coordinates & first_responder Send (context, data) Context Naming Global Name Service Resolution service NA1:P7, NA1:P9, NA2,P21, .. Context ba123 GUID 341x Context-based Multicast delivery Mobile Device trajectory WINLAB

Next-Gen Network Requirements: (7) Edge Cloud Services  Efficient, low-latency cloud services important for emerging mobile data and cyber physical applications  Tight integration of cloud service with access network  Service “ anycast ” primitive – get(service_ID,..)  Low latency, dynamic migration of state  Option for in-network processing in data plane Mobile Internet Edge Cloud Service Access Network B Edge Cloud B Service Access Network A A “Nearest” Cloud Service Low latency, dynamic migration Get(“ service_ID, data) User Mobility WINLAB

Next-Gen Network Requirements: (8) Edge Peering and Ad Hoc Networks  Wireless devices can form ad hoc networks with or without connectivity to the core Internet  These ad hoc networks may also be mobile and may be capable of peering along the edge  Requires rethinking of inter-domain routing, trust model, etc. Ad Hoc Network Formation, Intermittent Connection to Wired Internet & Network Mobility Access Network Access INTERNET Network V2I ) ) V2V Network WINLAB

Next-Gen Network Requirements: Summary  Security related functions: authentication, data security, etc.  Mobility related functions: end-point migration, network mobility, in- network storage/delay tolerance, edge awareness, ad- hoc modes,…  Multiple interface related functions: separation of object names from network addresses, multi-homing, multi- path, …  Content & context support: named content retrieval, context- specified dynamic multicast, in- network caching, …  In-network processing (optional): media transcoding, cloud services, data aggregation, .. service To more general set of service From today’s abstractions  connection oriented Get (service) named objects, data IP services (“pipes”) … Send (names, data) Open (IP_address, data) WINLAB

From Vision to Proof-of- Concept Realization: MobilityFirst Architecture