Upload
lindsey-carter
View
217
Download
0
Embed Size (px)
DESCRIPTION
3 Technical requirements and limitations in each trial scenario –Bandwidth –Coverage and availability –Reliability Conclusions about TCP and UDP performance –Traffic management –Security –Mobility Index (II)
Citation preview
Telefónica Móviles España
Deliverable 3.1WP3
2.5 -3G Communication Infrastructure
2
Index• Introduction to GPRS and UMTS networks
– Architecture overview– Services
• GPRS and UMTS situation in each trial site– GPRS communication architecture
• Commercially available providers• GPRS Roaming partnership• Coverage maps
– UMTS state
3
• Technical requirements and limitations in each trial scenario– Bandwidth– Coverage and availability– Reliability
• Conclusions about TCP and UDP performance– Traffic management– Security– Mobility
Index (II)
4
GPRS situation in each trial site• Selected operators:
• No problems related to coverage areas.• Roaming: Not available between the trial sites with
the selected operators
Country OperatorGermany D2- VodafoneSpain Telefónica Móviles
(Partner)Sweden Telia (Partner)The Netherlands
O2
5
UMTS situation in each trial site
Country SituationGermany Not availableSpain Possible testbed
in MadridSweden Possible testbed
in other areaThe Netherlands Possible testbed
in Enschede
6
Technical requirements and limitations in each trial scenario
(I)BANDWIDTHScenario BW
(Kbps)GPRS UMTS
Nurse 12.57 YesOutdoor 15.80 YesTrauma paramedic
3.07 Yes
Patient paramedic
1.90 Yes
High-risk pregnancies
3.62 Yes
Cardio 14.82 YesLighthouse 4.76 YesRA 28.90 No YesRespiratory insufficiency
6.40 Yes
Discharge 1.30 Yes
7
Technical requirements and limitations in each trial scenario
(II)RELIABILITY
• Conclusions about TCP vs UDP– TCP protocol is suitable for
transporting BAN control data from the End-Host to BAN
– The BAN data can be transported using UDP although some data may be lost
8
Technical requirements and limitations in each trial scenario
(III)TRAFFIC MANAGEMENT
Operators involved can´t guarantee the priority of the data over the voice so data traffic may be affected by a voice congestion situation.
9
Technical requirements and limitations in each trial scenario
(IV)SECURITY• Two security services are required for patients
data in GPRS/UMTS networks: Data confidentiality and authentication
• Security protocols used in MobiHealth from the MS to the server:– Transport Layer SSL connection, data encryption,
X.509 certificates-based client, Server authentication– Data link layer security provided by the Radio Access
Network (authentication and data encryption)
10
Technical requirements and limitations in each trial scenario
(V)MOBILITY• GPRS:
– Roaming functionality allows the users to establish GPRS connections from a foreign country.
– If the user roams to another network during a GPRS connection, the link goes down.
– In the same network, the handovers don't produce any disconnection.
• UMTS: Only handover could be supported at first phase.
Telefónica Móviles España
MobiHealth Architecture
WP3 2.5 -3G Communication
Infrastructure
12
MobiHealth architecture overview
BTS
BSC SGSN GGSN
Radius
INTERNET
BAN
Operator network
WSB
Surrogate Host
LookUp Service
BAN Data
Repository
Back-End System
End-user applicati
on
13
MobiHealth architectureTechnical Support
INTERNET
BAN
Operator network
BESys
Technical support(CMG &
UT)
VPN Tunnel
VPN Concentrat
or
14
• The MobiHealth infrastructure consists of:– Main components: operator network, WSB, SH, LUS, BDR,
technical support centres.– Supplementary components: VPN concentrators, Firewall.
• Definition of the required SW and associated costs:– WSBs and VPN concentrator provided by CMG.– SHs, LUS, BDR: provided by UT (over Linux OS)
• Definition of the required HW and associated costs:– WSBs and VPN concentrator provided by CMG.– SHs, LUS, BDR: 4 hich-end PCs. Costs??
Achievements
15
Deliverable D3.1 planningNew deadline: 1st March 2003Responsible: Marta Olivar (TME)TASKS:
1. Definition of the structure of the document (December 2002)2. Definition of the needed contributions of the partners (December 2002) (TME)3. Collect contributions from the partners (7 January 2003 - 17 January 2003)
(TME)4. Edition of first version and delivery of first draft (17 January 2003) (TME)5. Collect comments from the contributors (17 January 2003 - 31 January 2003)
(TME)6. Edition of final version (1st February 2003 -14 February 2003) (TME)7. Internal delivery of the final version (17 February 2003- 27 February 2003)
(TME)8. Delivery to the EC (28 February 2003) (Rainer)
16
Deliverable D3.2 “MobiHealth System” Planning
Deadline: May 2003Responsible: Hugo Geuverink (CMG)TASKS:
1. Definition of the main purpose and the objective of the deliverable (30 - 31 January 2003) (WP3 participants)
2. Definition of the structure of the document (30 January 2003 - 14 February 2003) (WP3 participants)
3. Definition of the needed contributions of the partners (17 February 2003 - 21 February 2003) (CMG)
4. Collect contributions from the partners (24 February 2003 - 14 March 2003) (CMG)5. Edition of first version and delivery of first draft (17 March 2003 - 18 April 2003)
(CMG)6. Collect comments from the contributors and from all the partners
(21 April 2003 - 5 May 2003) (CMG)7. Edition of final version (5 May -16 May 2003) (CMG)8. Internal delivery of the final version (19 May 2003) (CMG)9. Delivery to the EC (Before 30 May 2003) (Rainer)