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

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

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

4. 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. 5 Security issues in WP3 Integration with WP2 Alternatives of connections to WSB: –Using HTTP: Rely on GPRS security –Using HTTPs –Tunneling: IPsec

6. 6 MobiHealth Communication Architecture 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

7. 7 WSB (Wireless Service Broker) 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.

8. 8 WSB functionalities 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).

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

10. 10 GPRS Architecture BTS BSC MSC/VLR SGS N Backbone Network GGS N External X.25 Network External IP Network AUCHLR EIR Traffic and signalling Signalling MS

11. 11 RADIU S INTERN ET WSB Special access number SGS N GGSN GPRS Access MovilForum Health Broker Sites Sensor Front-End Security Data Collectio n Tool MobiHealth Architecture - TME

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

13. 13 Roaming GPRS

14. 14 Location based services -TME 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).

15. 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. 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. 17 APIAPI LOCATIO N Geo IP Location requests INTERNE T Application s Server MS C GGS N WAP GPRS Access WAP GSM Access MovilForum Gateway WAP Location – Geo IP

18. 18 Location http requests Application s Server MS C GGS N SMC SMS Access GPRS Access GSM Access MovilForum ISDN API LOCATIO N GPP Location - GPP

19. 19 Technical requirements of trial scenarios

20. 20 Technical requirements of trial scenarios

21. 21 Technical requirements of trial scenarios

22. 22 Technical requirements to be defined Identify type of information: Voice, data Number of simultaneous users in each trial site  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)

23. 23 Data collection tool 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.

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

25. 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. 26 Planning 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