1. Telefónica Móviles España Deliverable 3.1 WP3 2.5 -3G Communication Infrastructure

2. 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. 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. 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 CountryOperator GermanyD2- Vodafone SpainTelefónica Móviles (Partner) SwedenTelia (Partner) The NetherlandsO2

5. 5 UMTS situation in each trial site CountrySituation GermanyNot available SpainPossible testbed in Madrid SwedenPossible testbed in other area The NetherlandsPossible testbed in Enschede

6. 6 Technical requirements and limitations in each trial scenario (I) BANDWIDTH ScenarioBW (Kbps)GPRSUMTS Nurse12.57Yes Outdoor15.80Yes Trauma paramedic3.07Yes Patient paramedic1.90Yes High-risk pregnancies 3.62Yes Cardio14.82Yes Lighthouse4.76Yes RA28.90NoYes Respiratory insufficiency 6.40Yes Discharge1.30Yes

7. 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. 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. 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. 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.

11. Telefónica Móviles España MobiHealth Architecture WP3 2.5 -3G Communication Infrastructure

12. 12 MobiHealth architecture overview BTS BSC SGSN GGSN Radius INTERNE T BAN Operator network WSB Surrogate Host LookUp Service BAN Data Repositor y Back-End System End-user applicatio n

13. 13 MobiHealth architecture Technical Support INTERNE T BAN Operato r network BESys Technical support (CMG & UT) VPN Tunnel VPN Concentrator

14. 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. 15 Deliverable D3.1 planning New deadline: 1st March 2003 Responsible: 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. 16 Deliverable D3.2 “MobiHealth System” Planning Deadline: May 2003 Responsible: 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)