WP4 – Services Enablement
Status
Rute Sofia
[email protected]
Telco, 24.09.2015
Senception Lda | [email protected]
1
UMOBILE
WP4
W
P Work package title
No
1
Project Management
Type of
activity
MGT
DUTH
27
M1
End
mont
h
M36
2
Systems Requirement
3
System and node architecture
deployment
RTD
4
Services Enablement
RTD
SENCEPTI 65
ON
M6
M30
5
Overall platform integration
and validation
RTD
GOWEX
M18
M36
Dissemination and
Exploitation
RTD
6
TOTAL
RTD
Lead
partic.
Perso
Start
nmont
mont
h
hs
UCAM
DUTH
AFA
47
M1
133
129
52
M6
M1
453
Senception Lda | [email protected]
M30
M30
M36
WP4
PM
DUTH
14
UCL
12
UCAM
14
COPELABS
0
Tecnalia
0
Tekever
0
Senception
15
GOWEX
0
AFA
10
TOTAL
65
2
UMOBILE
WP4 Goals
• The main objective of WP4 is to enhance the UMOBILE
architecture in terms of QoS/QoE and enable solutions that take
advantage of the unique features of the developed architecture.
This WP will use the architecture developed during WP3 to
provide a set of services. Goals:
– O4.1: To enable services which fully exploit the inherent opportunistic
nature of communications.
– O4.2: To enable the “Internet” experience as many people know it, with
apps such as the Web, e-mail. Challenge: intermittent connectivity
and/or adjusting to QoE.
– O4.3: to develop mechanisms for processing of sensor data through
context understanding.
– O4.4: to provide different levels of QoS depending on the needs of each
user/network ranging from less-than-best-effort to guaranteed services.
UMOBILE
WP4 Deliverables
• Task4.1, UCAM
– D4.1 Flowlet Congestion Control, Initial Report, M18 (July 2016)
•
Includes the initial specification of the rate regulation scheme for flowlets that allows ISPs to have
full control of the traffic within their network.
– D4.2 Flowlet Congestion Control, Final Report, M30 (July 2017)
•
Defines the final specification of the rate regulation scheme for flowlets that allows ISPs to have
full control of the traffic within their network.
• Task4.2, Senception
– D4.5, Report on data collection and inference models, M30 (July 2017)
•
Comprises all processes developed in UMOBILE that involve data collection; context
understanding and data dissemination, depending on the requirements of each scenario and
defined priorities.
• Task 4.3, UCL
– D4.3 Named-based Replication Priorities, M24 (Jan 2017)
•
Describes the mobile named-based replication system.
• WP4, Senception
– D4.4, Set of QoS interfaces and algorithms M28 (May 2017)
•
Describes the different level of services provided by the UMOBILE platform.
UMOBILE
WP4 Tasks & Leaders – Task4.1
•
•
•
•
•
•
T4.1 – Providing different levels of QoS and flow control
M6 – M28 – M8-M28?
Leader: UCAM
Involved partners: UCAM, DUTH, UCL
D4.1 Flowlet Congestion Control – Initial Report, M18 (July 2016)
D4.2 Flowlet Congestion Control – Final Report, M30 (July 2017)
Focus:
• Focused on heterogeneity of the architecture – network types; devices; users.
– Support for multiple needs of QoS levels.
• Intention is to provide services that range from less-than-best-effort to some
form of guarantee.
• Motivation: creation of new access models and support for a wide range of
apps, from IoT data to low cost mobile services.
• Scientific guidelines: notion of flowlets instead that e2e flows
UMOBILE
Task4.1: Initial pointers
•
Al-Naday, Mays F., et al. "Quality of service in an information-centric network." Global
Communications Conference (GLOBECOM), 2014 IEEE. IEEE, 2014.
• Shan Sinha, Srikanth Kandula, Dina Katabi, Harnessing TCP’s Burstiness with Flowlet Switching,
In HotNets-III, 2004
• A. Anand and et al. Packet caches on routers: the implications of universal redundant traffic
elimination. In ACM SIGCOMM, pages 219–230, 2008
• V. Cerf, S. Burleigh, A. Hooke, L. Torgerson, R. Durst, K. Scott, K. Fall, and H. Weiss, “Delaytolerant networking architecture”, IETF, RFC 4838, Apr. 2007, Available:
http://www.ietf.org/rfc/rfc4838.txt.
• W. K. Chai, D. He, I. Psaras, and G. Pavlou. Cache ‘Less for More’ in Information-centric
Networks. In Proc. of IFIP Networking, 2012.
• Ioannis Psaras, Lorenzo Saino, George Pavlou, "Revisiting Resource Pooling: The Case for InNetwork Resource Sharing", in Proc. of ACM Workshop on Hot Topics in Networks 2014
(HotNets 2014), Los Angeles, California, to appear Oct 2014.
http://www.ee.ucl.ac.uk/comit-project/files/inrp-hotnets14.pdf
UMOBILE
Task4.1: Initial Steps
• Start defining an initial list of potential publications derived from
this task
– Table, editors, potential theme, potential target
• D2.1, grab scenarios and extract set of assumptions and
requirements for QoS and QoE levels.
• Analyse the type of flow control required
• Provide an initial skeleton for D4.1
UMOBILE
Task4.1: Status, 24.09.2015
•
Arjuna (UCAM):
•
“we have started working on the issues of computational congestion control (how do we
efficiently utilise the resources for caching/executing services) for SCANDEX but we have to wait
for some more time before we finalise our ideas
•
QoS - is going to be interesting -- we need to think about this especially when we are talking
about services being migrated to the edge -- what is the notion of QoS here and how do we do
it? need to think about this..”
•
Nikos (DUTH): On our side, we’re currently working on T4.1 (flowlet congestion control). Our
main task at this point is the implementation of the In-Network Resource Pooling Principle, as
described in [1]. We do not have something tangible to present or report at this point. We’ll
hopefully have some initial results soon.
•
Regarding QoS, some key aspects that need to be tackled include high delivery ratios in
disconnected environments, low losses in connected environments, short delivery delay,
and low jitter in voice calls. QoE is closely connected to QoS but also includes subjective
metrics, which need to be further specified with respect to the implemented services and
user requirements.
UMOBILE
WP4 Tasks & Leaders – Task4.2
•
•
•
•
•
T4.2 – Data collection and contextual inference
M6-M30
Leader: Senception
Involved partners: Senception, AFA, DUTH
D4.5, Report on Data Collection and inference models, M30 (July 2017)
Focus:
• Focused on data capture and data processing in an efficient way, based on
opportunistic and challenged environments.
• Filters data based on context
• Processes/propagates data based on similarities.
• Key aspect 1: notion of usage contextualization and service personalization
• Key aspect 2: capability to infer specific data usage context to assist in data
prefetching.
• Contextual inference: follows a filtering model approach to interpret data; specific
utility functions (QoE) that take into account proximity and eventually location.
Examples of specific contexts: roaming; entertainment; well-being.
UMOBILE
Task4.2: Initial pointers
•
•
•
•
•
•
•
•
•
•
Bagrow, J. P., Wang, D., Barabási, A.-L. Collective Response of Human Populations to Large-Scale
Emergencies. PLoS One 6:3, 1-8 (2011).
I. Urteaga F. Liberal J. M. Cabero, V. Molina and J. L. Martin. Acquisition of human traces with
bluetooth technology: Challenges and proposals. Ad Hoc Networks, January 2014.
J. Wang, R. Wakikawa, and L. Zhang, “Dmnd: Collecting data from mobiles using named data,” in
IEEE VNC 2010, 2010, pp. 49–56.
Turner, John C., et al. "Self and collective: Cognition and social context." Personality and social
psychology bulletin 20 (1994): 454-454.
Wymeersch, Henk, Jaime Lien, and Moe Z. Win. "Cooperative localization in wireless networks."
Proceedings of the IEEE 97.2 (2009): 427-450.
Makris, Prodromos, Dimitrios N. Skoutas, and Charalabos Skianis. "A survey on context-aware
mobile and wireless networking: On networking and computing environments' integration."
Communications Surveys & Tutorials, IEEE 15.1 (2013): 362-386.
…
UMOBILE
Task4.2: Status, 24.09.2015
• Senception is going to propose to AFA and DUTH a draft for
D4.5 – 08.10.2015
• Intention is to lead the work during the next months
• Currently , following initial steps and gathering related
work and analyzing main differentiators/gaps concerning
contextualization and data capturing – 10.10.2015
•
We need D2.2 and D2.3 to be able to fully devise differentiators
UMOBILE
Task4.2: Initial Steps
• Start defining an initial list of potential publications derived from
this task
– Table, editors, potential theme, potential target
• D2.1, grab scenarios and compile requirements and assumptions
– Define context for the different scenarios
– Compile sensors to be considered
– Define QoE and map it to the potential data/parameters to be extracted
• Provide set of tools as starting point
–
–
–
–
USENSE, CoPELABS
T-Kiddo, Senception
Medallion, Tecnalia
…
UMOBILE
Task4.2: Related Work
• SCAMPI
• IBR-DTN
– Guerrila, Whisper, ...
– …
UMOBILE
WP4 Tasks & Leaders – Task4.3
•
•
•
•
•
T4.3 – Name-based replication priorities
M6-M24  M8-M30
Leader: UCL
Involved partners: UCL, Senception
D4.3: Named-based Replication Priorities, M24 (Jan 2017)
Focus:
• Focused on the support of mobile name-based replication
• Replication expected to be optimized by prioritisation rules.
• Cases with intermittent connectivity (infrastructure not always
available); messages to be stored, carried and forwarded via
mobile devices.
UMOBILE
Task4.3: Initial pointers
•
•
•
•
•
Psaras, Ioannis, et al. "Name-based replication priorities in disaster cases." Computer
Communications Workshops (INFOCOM WKSHPS), 2014 IEEE Conference on. IEEE, 2014.
Tyson, Gareth, et al. "Beyond content delivery: Can icns help emergency scenarios?." Network,
IEEE 28.3 (2014): 44-49.
Li, W. E. N. J. I. E. "Popularity-driven Caching Strategy for Dynamic Adaptive Streaming over
Information-Centric Networks." (2015).
Arifuzzaman, Mohammad, Keping Yu, and Takao Sato. "Content distribution in Information
Centric Network: Economic incentive analysis in game theoretic approach." ITU Kaleidoscope
Academic Conference: Living in a converged world-Impossible without standards?, Proceedings
of the 2014. IEEE, 2014.
Monticelli, Edo, et al. "Combining Opportunistic and Information Centric Networks in Real
World Applications."
UMOBILE
Task4.3: Initial Steps
• Start defining an initial list of potential publications derived from
this task
– Table, editors, potential theme, potential target
• D2.1, grab scenarios and compile requirements and assumptions
– …
UMOBILE
Task4.3: Status, 24.09.2015
•
Yannis: we do not currently have any ongoing task, although our initial work in the
general ICN-DTN architecture area includes the ideas in NREP. We will report on
this during our call tomorrow. For NREP specifically, it’d be good to arrange a call
between UCL and Senception and see what are the possible ways forward.
UMOBILE
WP4 Roadmap, Deliverables, Milestones
M6
M1
M28 M30
M6
M12
D4.1, D4.3, D4.2, D4.4
Task 4.1, UCAM
Task 4.2, Senception
D4.5
D4.3
Task 4.3, UCL
M24
Deliverables (editor, Senception)
D4.1: Flowlet congestion control , initial report
(M18)
D4.2: Flowlet congestion control, final report (M30)
D4.3: Name-based replication priorities (M24)
D4.4: Set of QoS interfaces and algorithms (M28)
D4.5: Report on data collection and inference
models (M30)
Milestones
MS7: QoS interfaces and mechanisms
for data handling (M30)
MS8: Flowlet congestion control
developed (specs, M30)
UMOBILE
WP4 Future Actions
• Regular meetings via skype/videoconferencing
– Proposal: bi-weekly, doodle, starting from M8 (September) -http://doodle.com/purrib4irfdnw8uw
– First f2f meeting proposal: Lisbon, 20-22nd October 2015, ICT2015?
Action items for M6/M7
• Exchange of contacts, people involved
• Data exchange – pointers for relevant work in the field (projects,
papers, tools)
• Discussion concerning initial services to support (WP2, use-cases)
• Discussion concerning QoS/QoE aspects we want to support
• Definition of contexts to support, based on the use-cases (WP2)
• Agree on the tools to consider for validation and specification
Senception Lda | [email protected]
20
20