francesco bronzino, chao han, yang chen*, kiran nagaraja...
TRANSCRIPT
In-Network Compute Layer in MobilityFirst Future Internet Architecture (FIA)
MobilityFirst Overview
Francesco Bronzino, Chao Han, Yang Chen*, Kiran Nagaraja, Ivan Seskar, Xiaowei Yang*, Dipankar Raychaudhuri
WINLAB, Rutgers University and Duke University*
In-Network Transcoding
using MF Compute Layer
Compute Layer Opportunities
Data Packet Handling for Compute
Compute in Contextual and Sensing Cases
Cloudlets: Compute Layer Service
Deployment in ISP networks GENI Demo of MF Compute Layer
2. Mobile M
requests video C
6. Router with
compute layer
plugin forwards
chunk to T
GNRS Service Plane Network
19
Network 53
GUID Locator Locator Type Expiry
C P1 GUID never
P1 19 NA 1 day
M 53a NA 1min
1. P1 publishes
content C (attach
operation)
• Segmented Data Transport with Storage and Edge-
Aware Routing: Data is transported in a hop-by-hop
manner leveraging in-network storage and information
about edge network state to address variability in
access/edge networks, particularly wireless.
Routable topological address
(Network assigned) e.g., an IPvx
Human readable name
E.g., movie Internet Rising
Network name or identifier
GUID: public key, or content hash
Internet scale simulation: 26k ASs (Dimes dataset)
• Building Blocks: A cloudlet is composed of computing hosts
running service instances, a resource controller/manager,
and a API handler for service implementers to register, run
and manager the service instances
• Compute services register with local routing fabric using
GUID: Routers will use fast lookup table to determine co-
located compute layer services.
• Dynamic Placement and Provisioning within service
provider network. We envision a model similar to cloud
platform providers today. Implementers of the compute
service will have a choice of geo-location and dynamic
scaling of the deployed instances
ISP cache Network 53b
(WiFi)
Provider P1
• Multiple sites with InstaGENI, some with WiMAX*:
Rutgers*, Wisconsin*, NYU/NYU-Poly*, Utah,
NYSERNET, GPO, UIUC. Multipoint VLAN connects sites
to enable layer-2 connectivity for non-IP MF protocol
• DASH video stream server and VLC player client. Video
segment requests by client are translated to MF content
get requests. Server includes a compute extension
header in data packets so high quality content may
optionally be transcoded to a rate suitable for client
• Transcoder invoked by co-located router if the monitored
client access bandwidth drops below original encoded
video rate
Dynamic binding for Context
GUID:
A local context defined as
‘unoccupied cabs in location X’ can
be named using a GUID and
resolved dynamically by an in-
network compute layer service.
The service may pull information
from a web-based dispatch service to
determine what end points qualify for
delivering a request message
addressed to this GUID.
In-network Processing and
Aggregation of Sensor data:
Sensed data from vehicles and other
in-field sensors can be aggregated in
the network by a compute layer
service explicitly requested by the
originator of the sensed data, thus
reducing load on a centralized server.
• Provides easy extensibility/upgrade options for data plane
• ISPs can use in-network computing to provide value added services
such as caching, security, and contextual services
• ISPs can monetize their in-network cloud deployments by offering a
Platform as a Service (PaaS) solutions to application service providers
• Application and content providers can deploy close-to-client solutions to
minimize access latency
5. Lookup of M
resolves to
Network 53a Anycast request
Content (entire)
Response blocks
3. Lookup of C
resolves recursively to
Network 19
4. Video Server
streams video
segments
With compute
header for
Transcoder T
Further information and references are available at:
http://mobilityfirst.winlab.rutgers.edu
• Layered Names and Fast,
Global Name Resolution
for Mobility: All objects
including hosts, content,
services and abstract context
definitions can be assigned
network names for direct
addressability
• Resolution is closely
integrated with routing
fabric to enable fast and
dynamic address bindings.
Name-to-address mappings
can be stored/looked up in
the order of 10s of ms.
• Explicit request for compute layer processing with
Service type and custom Extension Header. Extension
header encodes GUID of service and any arguments
besides the payload.
• For instance, to request a transcoding operation on the
payload, extension header contains at the minimum the
transcoding service’s GUID and a target bitrate
• Router redirects data packets with the above set in the
headers to a co-located compute service registered a
priori
MF Packet Network Header
Extension Header for Compute Layer
Processing
Service Type = 0x800 Compute Layer
Processing
Cloudlets - compute hosting platforms closely
integrated with network fabric - may be deployed at
one or more Points of Presence (PoPs) and coordinated
by a Domain Controller run by the ISP.
2. Transcoding
service registers
with router with
GUID T
Cloudlet
Transcoder T
7. T transcodes
content to target
bitrate suitable for M
Network 53a
(4G)