Juno: An adaptive delivery-centric middleware

Gareth Tyson; Andreas Mauthe; Sebastian Kaune; Paul Grace; Thomas Plagemann

doi:10.1109/CCNC.2012.6181010

Juno: An adaptive delivery-centric middleware

Gareth Tyson^*, Andreas Mauthe, Sebastian Kaune, Paul Grace, Thomas Plagemann

^*Corresponding author for this work

Research output: Chapter in Book/Published conference output › Conference publication

Abstract

This paper proposes a new delivery-centric abstraction. A delivery-centric abstraction allows applications to generate content requests agnostic to location or protocol, with the additional ability to stipulate high-level requirements regarding such things as performance, security, resource consumption and monetary cost. A delivery-centric system therefore constantly adapts to fulfil these requirements, given the constraints of the environment. This abstraction has been realised through a delivery-centric middleware called Juno, which uses a reconfigurable software architecture to (i) discover multiple sources of an item of content, (ii) model each source's ability to provide the content, then (iii) adapt to interact with the source(s) that can best fulfil the application's requirements. Juno therefore utilises existing providers in a backwards compatible way, supporting immediate deployment. This paper evaluates Juno using Emulab to validate its ability to adapt to its environment.

Original language	English
Title of host publication	2012 IEEE Consumer Communications and Networking Conference, CCNC'2012
Pages	587-591
Number of pages	5
DOIs	https://doi.org/10.1109/CCNC.2012.6181010
Publication status	Published - 11 May 2012
Event	2012 IEEE Consumer Communications and Networking Conference, CCNC'2012 - Las Vegas, NV, United States Duration: 14 Jan 2012 → 17 Jan 2012

Conference

Conference	2012 IEEE Consumer Communications and Networking Conference, CCNC'2012
Country/Territory	United States
City	Las Vegas, NV
Period	14/01/12 → 17/01/12

Bibliographical note

© 2012 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes, creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works.

Access to Document

10.1109/CCNC.2012.6181010

Juno: An adaptive delivery-centric middleware
© 2012 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes, creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works.
Accepted author manuscript, 198 KB

Cite this

@inproceedings{b2e4df3b66d747e8b6dcc32f5f06c434,

title = "Juno: An adaptive delivery-centric middleware",

abstract = "This paper proposes a new delivery-centric abstraction. A delivery-centric abstraction allows applications to generate content requests agnostic to location or protocol, with the additional ability to stipulate high-level requirements regarding such things as performance, security, resource consumption and monetary cost. A delivery-centric system therefore constantly adapts to fulfil these requirements, given the constraints of the environment. This abstraction has been realised through a delivery-centric middleware called Juno, which uses a reconfigurable software architecture to (i) discover multiple sources of an item of content, (ii) model each source's ability to provide the content, then (iii) adapt to interact with the source(s) that can best fulfil the application's requirements. Juno therefore utilises existing providers in a backwards compatible way, supporting immediate deployment. This paper evaluates Juno using Emulab to validate its ability to adapt to its environment.",

author = "Gareth Tyson and Andreas Mauthe and Sebastian Kaune and Paul Grace and Thomas Plagemann",

note = "{\textcopyright} 2012 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes, creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works. ; 2012 IEEE Consumer Communications and Networking Conference, CCNC'2012 ; Conference date: 14-01-2012 Through 17-01-2012",

year = "2012",

month = may,

day = "11",

doi = "10.1109/CCNC.2012.6181010",

language = "English",

isbn = "9781457720710",

pages = "587--591",

booktitle = "2012 IEEE Consumer Communications and Networking Conference, CCNC'2012",

}

TY - GEN

T1 - Juno

T2 - 2012 IEEE Consumer Communications and Networking Conference, CCNC'2012

AU - Tyson, Gareth

AU - Mauthe, Andreas

AU - Kaune, Sebastian

AU - Grace, Paul

AU - Plagemann, Thomas

N1 - © 2012 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes, creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works.

PY - 2012/5/11

Y1 - 2012/5/11

N2 - This paper proposes a new delivery-centric abstraction. A delivery-centric abstraction allows applications to generate content requests agnostic to location or protocol, with the additional ability to stipulate high-level requirements regarding such things as performance, security, resource consumption and monetary cost. A delivery-centric system therefore constantly adapts to fulfil these requirements, given the constraints of the environment. This abstraction has been realised through a delivery-centric middleware called Juno, which uses a reconfigurable software architecture to (i) discover multiple sources of an item of content, (ii) model each source's ability to provide the content, then (iii) adapt to interact with the source(s) that can best fulfil the application's requirements. Juno therefore utilises existing providers in a backwards compatible way, supporting immediate deployment. This paper evaluates Juno using Emulab to validate its ability to adapt to its environment.

AB - This paper proposes a new delivery-centric abstraction. A delivery-centric abstraction allows applications to generate content requests agnostic to location or protocol, with the additional ability to stipulate high-level requirements regarding such things as performance, security, resource consumption and monetary cost. A delivery-centric system therefore constantly adapts to fulfil these requirements, given the constraints of the environment. This abstraction has been realised through a delivery-centric middleware called Juno, which uses a reconfigurable software architecture to (i) discover multiple sources of an item of content, (ii) model each source's ability to provide the content, then (iii) adapt to interact with the source(s) that can best fulfil the application's requirements. Juno therefore utilises existing providers in a backwards compatible way, supporting immediate deployment. This paper evaluates Juno using Emulab to validate its ability to adapt to its environment.

UR - http://www.scopus.com/inward/record.url?scp=84860662111&partnerID=8YFLogxK

UR - https://ieeexplore.ieee.org/document/6181010

U2 - 10.1109/CCNC.2012.6181010

DO - 10.1109/CCNC.2012.6181010

M3 - Conference publication

AN - SCOPUS:84860662111

SN - 9781457720710

SP - 587

EP - 591

BT - 2012 IEEE Consumer Communications and Networking Conference, CCNC'2012

Y2 - 14 January 2012 through 17 January 2012

ER -

Juno: An adaptive delivery-centric middleware

Abstract

Conference

Bibliographical note

Access to Document

Other files and links

Fingerprint

Cite this