1 / 27

WP3 meeting

WP3 meeting. 2.5 - 3G Communication Infrastructure. Telefónica Móviles España. Review of WP3 activities Security issues related to WP3 MobiHealth Communication Architecture Technical requirements of trial scenarios Data collection tool WP3 Deliverables Planning. Agenda.

masako
Download Presentation

WP3 meeting

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

  2. Review of WP3 activities Security issues related to WP3 MobiHealth Communication Architecture Technical requirements of trial scenarios Data collection tool WP3 Deliverables Planning Agenda

  3. GPRS infrastructure: Communication architecture Technical requirements of trials Security requirements Data collection tool Roaming UMTS infrastructure: Viability?? Review of WP3 activities

  4. Fine tuning and integration of the BAN applications: Integration with WP2 Test the operation of the whole system: Security level Quality of service Deliverable D3.1: Trial ready GPRS and UMTS networks (TME) Deliverable D3.2: MobiHealth system (CMG) Review of WP3 activities

  5. Integration with WP2 Alternatives of connections to WSB: Using HTTP: Rely on GPRS security Using HTTPs Tunneling: IPsec Security issues in WP3

  6. Requirements needed to support a MobiHealth BAN: Integration of the BAN applications Interface with WP2 Wireless Service Broker Integration with operator (Telia, TME) Integration with health broker sites MobiHealth Communication Architecture

  7. For MobiHealth project, there will be a connection between GGSN and WSB, via a tunnel connection (VPN) over Internet, and a tunnel connection between the WSB and the Application Server. In this way we will have a secure connection. WSB (Wireless Service Broker)

  8. Users authentication. Secure access and security management. Protocol conversion (SMS support, WAP support). Personalisation (homepage). Service navigation. (Multimedia) messaging relay. Synchronization. System monitoring and system management. Storage. Location management. Multi device support. WAP 2.0 compliant. In situations of out of coverage, the Push capability works (activate when MBU is in sleep mode and deliver content when device is available; Push Proxy Gateway stored data). WSB functionalities

  9. MSISDN (or equivalent user identifier) forwarding. IP address forwarding. Location data forwarding. VPN infrastructure (recommended). IPsec protocol. Requirements for operators

  10. GPRS Architecture BTS EIR MSC/VLR HLR AUC BSC SGSN External IP Network MS Backbone Network GGSN External X.25 Network Traffic and signalling Signalling

  11. INTERNET Health Broker Sites MobiHealth Architecture - TME MovilForum Special access number GGSN RADIUS SGSN Data Collection Tool GPRS Access Sensor Front-End WSB Security

  12. GPRS aspects (*) Some PDCH staticallyasigned to GPRS and some dynamically shared for GPRS and CSC. The radio allocation depends on the zones

  13. Roaming GPRS

  14. MovilForum provides two location platforms, Geo-IP and GPP, that allow to develop location based services, for any device (WAP, PDAs, handsets, laptops...). Geo IP provides location information in WAP connections. Initiated by user. The user authorizates to be located. GPP (Genasys Positioning Platform) provides location information for any acces: WEB, WAP, SMS...Initiated by user or content provider. (Passive location, for example tracking services). Location based services -TME

  15. Cell-ID accuracy: The network provides the location information of the cell in which the user is. The Cell-ID accuracy depends on the cell size: Urban area: 50-500 m. Rural area: 1-20 km. GSM or GPRS access. Possible improvements: The use of TA (Timing Advance) parameter improves the accuracy, but only with Ericsson BSCs. Location based services -TME

  16. MovilForum provides open APIs (Application Program Interface) in order to access to the location platform. Legal problems: Requests for positioning information is only processed if the user has given his authorization. Location based services -TME

  17. INTERNET Location – Geo IP API LOCATION Geo IP Gateway WAP WAP GPRS Access GGSN Locationrequests MSC WAP GSM Access MovilForum Applications Server

  18. Location - GPP LOCATION GPP SMS Access SMC API GPRS Access GGSN GSM Access MSC MovilForum Location http requests ISDN Applications Server

  19. Technical requirements of trial scenarios

  20. Technical requirements of trial scenarios

  21. Technical requirements of trial scenarios

  22. Identify type of information: Voice, data Number of simultaneous users in each trial site g Number of required IP adresses Required bandwidth Roaming? Location offered by operator? Videoconference in real time & UMTS? For sleep studies in scenario 1B of CSC we have to take into account that TME only offers technical support over MovilForum platform in bussiness hours (8.30h- 18.00h) Technical requirements to be defined

  23. Access method to the technical measurements: Web site with username and password Schedule of usage data release: Daily Available data: Connection duration. Connection date and time. Number of sent bytes. Number of received bytes. Assigned IP address. Data collection tool

  24. Deliverable D3.1: Trial ready GPRS and UMTS networks Responsible: TME Deadline: December 2002 Public Demonstrator WP3 Deliverables: What should we do in order to be ready?

  25. Deliverable D3.2: MobiHealth system Responsible: CMG Deadline: May 2003 Public Prototype WP3 Deliverables: What should we do in order to be ready?

  26. Some deadlines: Trial set-up: November 2002 Trials: February 2003 Deliverable D3.1: December 2002 Tasks to execute: Security aspects decision Integration of WSB with operators and health broker sites Definition, development and instalation of data collection tool Planning

More Related