Mobile Edge Cloud Services in 5G

Size: px

Start display at page:

Download "Mobile Edge Cloud Services in 5G"

Judith Greene
6 years ago
Views:

1 Mobile Edge Cloud Services in 5G Yanyong Zhang, Rutgers University

2 Edge clouds, edge applications MOTIVATION

3 Mobile Edge Clouds

4 Edge Applications Mobile Edge Cloud Services Emergency Service Safety Smart Factory Automatic driving Real-time alert Real-time response Field machine control Emergency stop AR navigation Automatic translation Scalability for devices and objects

Challenges Terminal Mobility Complexity - Device/Object ID - Sensed data Query Data-

Sensing (3) Actuation Response (2) Computation.

X2 X1 2 X2 2 X2 10^12 10^12 10^12 Service Directories - Actuation command Large # of

5 Challenges Terminal Mobility Complexity - Device/Object ID - Sensed data Query Data- Intensive Distributed, Parallel, and Pipelined Computation Multi-sensory fusion (1) Sensing (3) Actuation Response (2) Computation... Cloud Network domain Valu IDObject e Valu GUID Object e Valu 1 GUID X1 e 1 X1 2 1 X2 X1 2 X2 2 X2 10^12 10^12 10^12 Service Directories - Actuation command Large # of NW domains Real-time <100msec response time in application Scale Trillion-order edge devices & objects are properly handled

6 Network virtualization, ASR, task mapping, spatial and temporal scheduling SMART-EDGE

7 SmartEdge Vision

Global Name Resolution Globally unique name (GUID) for network attached objects device, content, context, AS name, sensor, and so on Multiple domain-specific naming services Global Name Resolution

8 Global Name Resolution Globally unique name (GUID) for network attached objects device, content, context, AS name, sensor, and so on Multiple domain-specific naming services Global Name Resolution Service for GUID NA mappings Hybrid GUID/NA approach Both name/address headers in PDU Fast path when NA is available GUID resolution, late binding option Sue s_mobile_2 John s _laptop_1 Host Naming Service Server_1234 Sensor Naming Service Sensor@XYZ Taxis in NB Media File_ABC Globally Unique Flat Identifier (GUID) Global Name Resolution Service Network Content Naming Service Context Naming Service Network address Net1.local_ID Net2.local_ID

Mobility Service via Name Resolution Service API capabilities: - send (GUID, options, data) Options = anycast, mcast, time,.. - get (content_guid, options) Options = nearest, all,.

9 Mobility Service via Name Resolution Service API capabilities: - send (GUID, options, data) Options = anycast, mcast, time,.. - get (content_guid, options) Options = nearest, all,.. GUID lookup from directory Name Certification Services (NCS) Register John Smith22 s devices with NCS GUID assigned MobilityFirst Network (Data Plane) NA99 GNRS update (after link-layer association) Send (GUID = , SID=01, data) NA32 GUID <-> NA lookup GNRS query GNRS GUID = Send (GUID = , SID=01, NA99, NA32, data) Represents network object with 2 devices DATA GUID SID NAs Packet sent out by host

10 Overview of Virtual Mobile Cloud Network (vmcn) Name resolution layer (3) Service Anycast & Dynamic Migration smartedge slice (1) Name-based virtual network ID Query Packet VN Routing layer (2) VN & vbs on the move Virtual base station (vbs)

11 MF Extended to Support VN (3) GNRS Service Plane GUID Locator VN Type A1 19 No VNID_1 VR1, VR2, Yes VR1 1a Yes VR2 1b Yes (1) (1) Virtual GUID as an identifier of a VN (2) Ingress router identifies VNs (3) GNRS is exploited to capture VN membership and access control VR2 Central Coordinator Network 19 VR6 A1 VR1 A2 S (2) Ingress Router VR3 VR5 Network 53a B1

vbs: A Technique of Building a Service-specific VN in WiFi

Network-driven association and handover Cooperative NW

Unified Policy vbs 1 vbs 2 vbs 3 BS Resource Pool Virtual BS

Shoji, WiFi Network Virtualization to Control the

12 vbs: A Technique of Building a Service-specific VN in WiFi Isolated BS resources assigned to a target service Network-driven association and handover Cooperative NW virtualization in backhaul Elastic QoS Controllability Unified Policy vbs 1 vbs 2 vbs 3 BS Resource Pool Virtual BS (vbs) Physical BS The other services K. Nakauchi and Y. Shoji, WiFi Network Virtualization to Control the Connectivity of a Target Service, IEEE Transactions on Network and Service Management, June, 2015

servers Application-level metric is used

13 Application-Specific Routing Virtual Routing VR1 DST_ GUID A1 A2 B1 <App, Link, N_Hop> <0.2, 5x, VR2> <0.7, 5x, VR2> <0.3, 3x, VR3> S <0, 1, S> Service GUID is assigned to a group of replicated servers Application-level metric is used for routing decision Application state is periodically announced computation load, waiting time, etc. S VR1 VR2 Network 19 VR6 A1 Service Y A2 VR3 VR5 Network 53a B1

14 Edge Cloud Assignment Spatial Scheduling An edge application consists of a sequence of requests each having a deadline and demanding a certain amount of resource Each edge cloud periodically exposes its available resources CPU utilization, data set, pending workload, Then we pick one that can satisfy the real-time constraint; if no server is qualified, we consider migrating existing requests (without violating their deadlines) Delayed scheduling Migration may be needed due to user mobility Mobility prediction

15 Parallel, Distributed, and Pipelined Execution

16 Efficient Runtime Management Data shipping or computation shipping? Approximate computing to hide network latency Co-scheduling across multiple sites

17 PROTOTYPING & EVALUATION

Initial Prototype vbs remote control software is

vbs Written in Python vbs MobilityFirst vbs Prototype

(MF-enabled) vbs VNCS & OFS & MM MF Central Coordinator

254 Python script VR2 Cloud Server1 GUID 21 VR1

18 Initial Prototype vbs remote control software is implemented in the MF stack Common C-plane for MF and vbs Written in Python vbs MobilityFirst vbs Prototype MF-VN Prototype Service GUID 1331 CPS Terminal (MF-enabled) vbs VNCS & OFS & MM MF Central Coordinator Python script VR2 Cloud Server1 GUID 21 VR1 Non-CPS/CPS Traffic Generator VR3 Cloud Server2 GUID 22 NA: /16 Locator: XX NA: /16 Locator: YY NA: /16 Locator: ZZ

90%ile Response Time Measured vbs Mode: 802.

19 90%ile Response Time Measured vbs Mode: n/a Band: 5GHz Tx Rate: 65Mbps Rx Rate: 65Mbps # of BS: 2 (Ch 36,48) MF VN APP-level Query & Response (mfping) MF-VN Routing: ASR - Reporting interval: 2s Transport: hop-by-hop reliability - Retrans. limit: unlimited - Retrans. timeout: 200ms Response Time T=t 0 T=t 1 query response After Before 90% CDF vbs&mf vbs only w/o vbs&mf 90%ile Response Time Response Time (RTT)

20 WiFi Congestion &Dynamic Server Load Before Without vbs CPS Terminals Non-CPS terminals BS#1 Shared and competed b/w CPS and Non- CPS apps MF VN Server#1 Server#2 Forwarded to the closest server even if the load is high Server#1 Server Load 0. 2 Server 1. Load 0 Without ASR T T After CPS Terminals Non-CPS terminals BS#1 MF VN Server#2 Server Load 0. 2 Server 1. Load 0 T T With vbs Isolated for a specific CPS app 20 Forwarded to less-loaded server With ASR

21 Reduction of 90%ile Response Time from 1900ms to 210ms Emulated cloud app with 50KB Data, w/ Server Load and WiFi Cross Traffic w/ vbs & ASR 214ms 1932ms vbs&asr 90%ile w/o vbs & w/o ASR Due to retransmission s and the potential bogus state in the MF transport protocol 100

22 Questions & Answers

Content and Context in Mobility First

Content and Context in Mobility First and Context in Mobility First Presented by: Rich Martin WINLAB, Rutgers University Technology Centre of NJ 671 Route 1, North Brunswick, NJ 08902, USA rmartin@cs.rutgers.edu Using the for content and context