Category:WP4 - Revision history

Liangwang: /* WP4 Contacts */

2015-08-02T11:32:15Z

‎WP4 Contacts

2015-07-31T10:35:44Z

‎WP4 Contacts

2015-07-31T10:35:02Z

‎Goals

2015-07-31T10:34:26Z

‎Related UMOBILE Documents

2015-07-31T10:33:29Z

‎Related UMOBILE Documents

2015-07-31T10:29:41Z

2015-02-20T14:36:32Z

Created page with "..."

New page

...

@@ Line 2: / Line 2: @@
 * WP leader: Rute Sofia (rute.sofia@sen-ception.com)
-* Task 4.1 - Providing different levels of QoS and flow control, M6-M30 - UCAM (??); PARTNERS: UCAM, DUTH, UCL
+* Task 4.1 - Providing different levels of QoS and flow control, M6-M30 - UCAM (Liang); PARTNERS: UCAM, DUTH, UCL
 * Task 4.2 - Data collection and contextual inference, M6-M30 - Senception (Rute); PARTNERS: Senception, AFA, DUTH
 * Task 4.3 - Name-based replication priorities - UCL (Ioannis); PARTNERS: UCL, Senception

@@ Line 1: / Line 1: @@
 === WP4 Contacts ===
-WP leader: Rute Sofia (rute.sofia@sen-ception.com)
+* WP leader: Rute Sofia (rute.sofia@sen-ception.com)
-Task 4.1 - Providing different levels of QoS and flow control, M6-M30 - UCAM (??); PARTNERS: UCAM, DUTH, UCL
+* Task 4.1 - Providing different levels of QoS and flow control, M6-M30 - UCAM (??); PARTNERS: UCAM, DUTH, UCL
-Task 4.2 - Data collection and contextual inference, M6-M30 - Senception (Rute); PARTNERS: Senception, AFA, DUTH
+* Task 4.2 - Data collection and contextual inference, M6-M30 - Senception (Rute); PARTNERS: Senception, AFA, DUTH
-Task 4.3 - Name-based replication priorities - UCL; PARTNERS: UCL, Senception
+* Task 4.3 - Name-based replication priorities - UCL (Ioannis); PARTNERS: UCL, Senception
-−
 === WP4 Meetings ===

@@ Line 13: / Line 13: @@
 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.1: To enable services which fully exploit the inherent opportunistic nature of communications.
-O4.3: to develop mechanisms for processing of sensor data through context understanding.
+* 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.4: to provide different levels of QoS depending on the needs of each user/network ranging from less-than-best-effort to guaranteed services.
+* O4.3: to develop mechanisms for processing of sensor data through context understanding.
 === Related UMOBILE Documents ===
 [[Media:2015-07-31_UMOBILE_WP4.ppt]] -- initial roadmap

← Older revision		Revision as of 10:34, 31 July 2015
Line 20:		Line 20:
	=== Related UMOBILE Documents ===		=== Related UMOBILE Documents ===

−	[[2015-07-31_UMOBILE_WP4.ppt]] -- initial roadmap	+	[[Media:2015-07-31_UMOBILE_WP4.ppt]] -- initial roadmap

← Older revision		Revision as of 10:33, 31 July 2015
Line 19:		Line 19:

	=== Related UMOBILE Documents ===		=== Related UMOBILE Documents ===
−	...	+
		+	[[2015-07-31_UMOBILE_WP4.ppt]] -- initial roadmap

← Older revision		Revision as of 10:29, 31 July 2015
Line 1:		Line 1:
		+	=== WP4 Contacts ===
		+
		+	WP leader: Rute Sofia (rute.sofia@sen-ception.com)
		+	Task 4.1 - Providing different levels of QoS and flow control, M6-M30 - UCAM (??); PARTNERS: UCAM, DUTH, UCL
		+	Task 4.2 - Data collection and contextual inference, M6-M30 - Senception (Rute); PARTNERS: Senception, AFA, DUTH
		+	Task 4.3 - Name-based replication priorities - UCL; PARTNERS: UCL, Senception
		+
		+
		+	=== WP4 Meetings ===
		+	http://doodle.com/purrib4irfdnw8uw
		+
		+	=== 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.
		+
		+	=== Related UMOBILE Documents ===
	...		...