1 / 17

Deliverable 3.1

Deliverable 3.1. WP3 2.5 -3G Communication Infrastructure. Telefónica Móviles España. 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

kenyon-bray
Download Presentation

Deliverable 3.1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

  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. Selected operators: No problems related to coverage areas. Roaming: Not available between the trial sites with the selected operators GPRS situation in each trial site

  5. UMTS situation in each trial site

  6. Technical requirements and limitations in each trial scenario (I)BANDWIDTH

  7. 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 Technical requirements and limitations in each trial scenario (II)RELIABILITY

  8. Operators involved can´t guarantee the priority of the data over the voice so data traffic may be affected by a voice congestion situation. Technical requirements and limitations in each trial scenario (III)TRAFFIC MANAGEMENT

  9. 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) Technical requirements and limitations in each trial scenario (IV)SECURITY

  10. 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. Technical requirements and limitations in each trial scenario (V)MOBILITY

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

  12. INTERNET BTS BAN Data Repository LookUp Service Surrogate Host MobiHealth architecture overview Operator network Radius BSC GGSN SGSN BAN End-user application WSB Back-End System

  13. INTERNET Operator network MobiHealth architectureTechnical Support VPN Concentrator BESys VPN Tunnel BAN Technical support (CMG & UT)

  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. 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) Deliverable D3.1 planning

  16. 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) Deliverable D3.2 “MobiHealth System” Planning

More Related