1. Telefónica Móviles España WP3 meeting 2.5 - 3G Communication Infrastructure Madrid, November 12 & 13, 2002

2. 2 Agenda Tuesday, November 12, 2002 16:00Visit to TME Demo Center 17:00Security issues Review of MobiHealth security requirements Dynamic/static IP addressing Security mechanisms and services of operators Security mechanisms to implement in MobiHealth 18:30End

3. 3 Agenda Wednesday, November 13, 2002 9:00Communication infrastructure Location of CMG WSB Measurement strategy UDP/TCP demo 10:45Coffee break 11.00 Technical requirements of trial scenarios Review of technical requirements from WP1 Technical limitations Redefinition of trials

4. 4 Agenda Wednesday, November 13, 2002 11.45 Data collection tool Required technical parameters Situation in every trial site  Telia, TME and non- MobiHealth operators 12:15Coffee break 12:30Deliverable D3.1 13:00Conclusions and planning of WP3 activities 14:00End

5. 5 Security issues  Review of MobiHealth security requirements (UPF) Advances in WP2 Proposals for WP3  Advantages and drawbacks of using dynamic or static IP addressing (UPF)  Security mechanisms and services of operators (TELIA & TME)  Security functionalities provided by WSB (CMG)  Decision about the security mechanisms to implement in WP3 (ALL)

6. 6 Security mechanisms in TME network  The security functions are related to:  The mobile phone and the SIM card  Security mechanisms between MS and SGSN  PLMN backbone network security  Security between different operators  Security between GGSN and external connected networks and services providers  MoviStar Intranet service

7. 7 Communication infrastructure BAN Mobile operator WSB Two possible scenarios:  Centralized BEsys scenario  One BEsys for MobiHealth  Local BEsys scenario  One BEsys for each trial scenario End User Applicatio n Hospital systems BANData Repositor y LookU p Service BEsys Surrogat e Host Subscriber DB

8. 8 Centralized BEsys scenario Non-MobiHealth operators WSB End user application Swedish trial End user application Spanish trial End user application German trial End user application Dutch trial BEsy s ?? Subscriber DB

9. 9 Local BEsys scenario WS B BEsy s End user application Swedish trial End user application Spanish trial Non-MobiHealth operators WSB BEsy s End user application German/Ducth trial ??

10. 10 Decisions about the communication infrastructure  WSB location: Centralized or Local BEsys scenario. Physical location of equipments (WSB and BEsys) and type of connections between them (depends on security mechanisms and physical location). Connection to WSB for non-MobiHealth operators. Maintainance of Subscriber Database. Technical decisions, but not forget related costs  Connection between BEsys and hospitals systems.  End user application in each trial site.  Static/dynamic IP address in the communication between the MBU and the operator.  IP Protocols: TCP/UDP.

11. 11 Communication infrastructure in Spain WSB GGS N RADIU S Data collection tool Surrogat e Host BANData Repositor y LookU p Service BEsys End User Applicatio n Corporacio Sanitaria Clinic BAN Proxy authentication Subscriber DB

12. 12 Technical requirements of trials scenarios

13. 13 Technical requirements of trials scenarios

14. 14 Technical requirements of trials scenarios

15. 15 Technical requirements of trials scenarios

16. 16 Required bandwidth of transmitted data

17. 17 Technical limitations  Bandwidth  Roaming and cross border connectivity  Coverage  Speed  Handover

18. 18 GSM Voice: GSM Voice: 1 conversation  1 channel 1 channel for GSM data  9.6 kbps 1 2345678 Radio Carrier: Radio Carrier: 8 channels GPRS: GPRS: Use of until 8 channels per user Depending on the code algorithm, we can get several transmission rates: CS-1: 9.05 kbps/slot CS-3: 15.6 kbps/slot CS-2: 13.4 kbps/slotCS-4: 21.4 kbps/slot Actually terminals support until 4+1 slots (4 channels DL + 1 channel UL) Efficiency in resources use: until 8 users/channel. TME GPRS network uses CS-1 and CS-2 coding schemes. Available bandwidth depends on the coding scheme, the allocated time slots and the radioelectric conditions (carrier to interference ratio). Bandwidth: GPRS rates

19. 19 Roaming and cross border connectivity Roaming functionality allows the users to stablish GPRS connections from a foreign country. The visited network VPLMN (Visited Public Land Mobile Network) is selected according to the roaming agreement. Visitor user can use radio resources of the visited network, but the IP address is asigned by the home network. If the user roames to another network during a GPRS connection, the link goes down.

20. 20 Coverage, speed and handover Coverage: TME guarantees coverage in 90% of cases. TME offers many solutions of vertical coverage in special areas as tunnels, parkings, inside buildings, underground,... Speed: As the speed (of mobile motion)increases, GPRS bit rate decreases, because the transmission quality decreases and more data retransmissions are required. The speed limit depends on different agents: coverage, base stations location, number of allocated channels... The maximun allowed speed is around 130-140 Km/h. In special environment, as high speed trains, an extension of the GSM standard can be used to allow GPRS communications with higher motion speeds. Handover: In the same network, the handovers don´t produce any disconnection.

21. 21 Measurement strategy  Development of a model of the end-to-end MobiHealth communication link to predict the overall performance of the system.  The end-to-end link consists of several individual links: BAN<>Operator<>Internet<>Enterprise_network<>Application_host  The better model (the most accurate measurements) is achieved by measuring every individual link, which implies to install a measurement probe in operators networks.  UT will define the measurements methods and the required information for evaluating the system regarding to performance, reliability, coverage, security, BAN mobility…  TME doesn’t allow the installation of a measurement probe in its network.  Non-MobiHealth operators won’t probably allow to perform measurements in their networks.  Possibility of measurement probe in Telia network??

22. 22 Data collection tool  For testing GPRS and UMTS networks, different data collection tools have to be defined, developed, installed and configured, allowing the capture of usage data during the project trials.  WP5 will evaluate the networks depending on the usage data collected during the trials by these tools. WP3 & WP5 have to define: Required parameters to be measured Method of deliver measured parameters Schedule for information delivering  Data collection tools deadline: Start of trials (1st of May, 2003)

23. 23 Data collection tool in TME  TME data collection tool is a software tool that allows the capture of usage data during the trials for the network evaluation. It communicates with different network equipments and captures data generated during GPRS connections.  The available data are: Connection duration Connection date and time Number of sent/received bytes Assigned IP address

24. 24 Data collection tool in TME  This tool provides information about the connection of a use r, group of users and the total number of connections.  Access method to the technical measurements: website with username / password.  Schedule of usage data release: Daily  This tool corresponds with TME solution for GPRS.  Telia will need their own tool for their networks.  For no-MobiHealth operators, we won´t probably have the possibility of data collection, so we could use GPRS invoices to know the number of KB involved.

25. 25 Tasks about data collection tools  Definition of required parameters and the method and schedule of data delivery.  Deadline for development, installation and configuration of the tools in operators.  Tests of the tools before trials.

26. 26 Deliverable D3.1 Trial ready GPRS networks  GPRS network: Description of communication architecture Technical limitations in each trial scenario  Deliverable 1.3  UMTS network state: Telia and TME Overall situation in non-MobiHealth operators Terminals availibility  Decision about operators for Germany and Holland trials  Needed information about their situation

27. 27 Planning  UDP vs TCP demo (1st December 2002)  Definitive communication architecture 13 December 02  Deliverable 3.1 (1st January 2003)  Deployment WSB and security mechanisms  Configuration of communication between WSB, operators, surrogate host and end-user application server  Data collection tool availability  BAN (May 2003)