Transcript WP3 meeting - MobiHealth

WP3 meeting
2.5 - 3G Communication
Infrastructure
Madrid, November 12 & 13, 2002
Telefónica Móviles España
Agenda Tuesday, November 12,
2002
16:00
Visit to TME Demo Center
17:00
Security issues
18:30
2
•
Review of MobiHealth security requirements
•
Dynamic/static IP addressing
•
Security mechanisms and services of operators
•
Security mechanisms to implement in MobiHealth
End
Agenda Wednesday, November 13,
2002
9:00
3
Communication infrastructure
•
Location of CMG WSB
•
Measurement strategy
•
UDP/TCP demo
10:45
Coffee break
11.00
Technical requirements of trial scenarios
•
Review of technical requirements from WP1
•
Technical limitations
•
Redefinition of trials
Agenda Wednesday, November 13,
2002
11.45
Data collection tool
•
Required technical parameters
•
Situation in every trial site  Telia, TME and non-
MobiHealth operators
4
12:15
Coffee break
12:30
Deliverable D3.1
13:00
Conclusions and planning of WP3 activities
14:00
End
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)
5
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
6
Communication infrastructure
BEsys
Mobile
operator
BAN
Subscriber
DB
WSB
BANData
Repositor
y
LookU
p
Service
Surrogat
e Host
Two possible scenarios:

Centralized BEsys scenario  One BEsys for
MobiHealth

Local BEsys scenario  One BEsys for each trial
7
scenario
Hospital
systems
End User
Applicatio
n
Centralized BEsys scenario
Subscriber
DB
WSB
BEsy
s
End user
application
Swedish
trial
End user
application
Spanish
trial
End user
application
??
Non-MobiHealth
operators
8
Dutch trial
End user
application
German
trial
Local BEsys scenario
WS
B
WSB
Non-MobiHealth
operators
9
??
WSB
BEsy
s
BEsy
s
BEsy
s
End user
application
Swedish
trial
End user
application
Spanish
trial
End user
application
German/Ducth
trial
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.

10
IP Protocols: TCP/UDP.
Communication infrastructure in Spain
Data
collection
tool
RADIU
S
GGS
N
Subscriber BEsys
BANData
DB
BAN
Proxy
authentication
Repositor
y
LookU
p
Service
Corporacio
Sanitaria
Clinic
End User
Applicatio
WSB
Surrogat
e Host
11
n
Technical requirements of trials scenarios
GSCOUT (Germany)
TITLE
MEASUREMENTS
TOTAL
NUMBER OF
SUBJECTS
BANS
30
??
TRIAL RUN
BANDWIDTH TECHNOLOGY
TIME
ECG (continuos)
Secondary prevention in
coronary heart disease
Movement (continuos)
Blood pressure (circa every
hour)
3 months
55 kbps or
less (maybe
half)
GPRS
MST (The Netherlands)
TITLE
Integrated Homecare in
women with high-risk
pregnancies
Tele Trauma Team
(PARAMEDICS)
MEASUREMENTS
Maternal Blood Pressure (circa
every hour)
Foetal ECG (continuos)
Video (still image or a few
photos an hour)
TOTAL
NUMBER OF
SUBJECTS
BANs
26 (each
Test unit
patient
(December)
monitored for 4-5 BANs in
2 weeks)
May
Circa 25
6 months
50 kbps or
half if
necessary
GPRS
2 BANs
Until
enough
patients are
treated
Unknown
GPRS/ UMTS (if
possible)
4-5 BANs
Until
enough
patients are
treated
< 10 kbps
GPRS/ UMTS (if
possible)
Audio
Pulse
Tele Trauma Team
(PATIENTS)
Blood pressure
Breathing frecuency
Pupil reaction
12
Circa 25 (each
patient
monitored
continuously)
TRIAL RUN
BANDWIDTH TECHNOLOGY
TIME
Technical requirements of trials scenarios
CSC (Spain)
TITLE
MEASUREMENTS
TOTAL
NUMBER OF
SUBJECTS
BANs
12 patients (1
visit per week)
2-3 BANs
2 months
unknown
GPRS/ UMTS (if
possible)
10 (1 week per
patient)
3-4 BANs
3 months
55 kbps
GPRS/ UMTS (if
possible)
TRIAL RUN
BANDWIDTH TECHNOLOGY
TIME
Pulse oximetry
Mobile Chronic Care
Scenario 1A
Support of home-based
healthcare services (nurse
visits at patient's home)
ECG 3 leads
Forced spirometry
Temperature
Blood pressure
Video
Glucose (if possible)
Pulse oximetry
ECG 3 leads
Mobile Chronic Care
Scenario 1B
Support of home-based
healthcare services (patient
monitoring at home)
SLEEP STUDIES
Forced spirometry
Temperature
Blood pressure
Mobility
Video
Glucose (if possible)
13
Technical requirements of trials scenarios
CSC (Spain)
TITLE
MEASUREMENTS
TOTAL
NUMBER OF
SUBJECTS
BANs
10 patients
10 BANs
2 months
50-55 kbps or GPRS/ UMTS (if
less
possible)
10 patients (2
months per
patient)
10 BANs
2 months
50-55 kbps or GPRS/ UMTS (if
less
possible)
10 patients (2
months per
patient)
10 BANs
2 months
50-55 kbps or GPRS/ UMTS (if
less
possible)
TRIAL RUN
BANDWIDTH TECHNOLOGY
TIME
Pulse oximetry
ECG 3 leads
Forced spirometry
Mobile Chronic Care
Scenario 1B
Support of home-based
healthcare services (patient
monitoring at home)
HOME VENTILATION
Temperature
Blood pressure
Mobility
Video
Glucose (if possible)
Pressure (home ventilation)
Flow (home ventilation)
Pulse oximetry
Mobile Chronic Care
Scenario 1B
Support of home-based
healthcare services (patient
monitoring at home)
HIGH RISK OF HOSPITAL READMISSION
ECG 3 leads
Forced spirometry
Temperature
Blood pressure
Mobility
Glucose (if possible)
Mobile Chronic Care
Scenario 2
Outdoors patient's
rehabilitation
14
Pulse oximetry
ECG 3 leads
Movement
Technical requirements of trials scenarios
LTU (Sweden)
TITLE
MEASUREMENTS
TOTAL
NUMBER OF
SUBJECTS
BANs
16
8 BANs
1 month
8-10 (1 week
per patient)
2 BANs
2 months
20 kbps
GPRS
15 (one 24hour period
per patient)
2 BANs
3 months
< 25 kbps
GPRS
8-10 (1 week
per patient)
2 BANs
2 months
< 10 kbps
GPRS
5-10 (1 week
per patient)
3 BANs
3 months
50 kbps
GPRS/ UMTS (if
possible)
TRIAL RUN
BANDWIDTH TECHNOLOGY
TIME
Pulse
The Lighthouse alarma and
locator trial
Falls (drop sensors)
Position
< 5 kbps for GPRS/ UMTS (if
sensors
possible)
Video
Physical activity and
impediments to activity in
women with RA
Monitoring of vital
parameters in patients with
respiratory insufficiency
Heart rate
Movement
Surface EMG
Pulse oximetry
Heart rate
Physical activity after a
stroke
Movement
Surface EMG
Heart rate
Home care and remote
consultation for recentlyreleased patients in a rural
area
15
Blood glucose
Standard rest ECG (12-lead)
Oxygen saturation
Breathing parameters
(opcional)
Required bandwidth of transmitted data
TRANSMITTED DATA
REQUIRED BANDWIDTH
Blood glucose 4 times a day
128bits/day
Blood glucose continuously
32bits/sec
Blood pressure once per 30 min
256bits/hour
Blood pressure continuously
3kbits/sec
Respiration signal
320bits/sec
CTG (Calculated out of 4 FECG signals)
15kbits/sec (4 ECG signals)
ECG -12 leads
200kbits/sec
ECG -3 leads
50kbits/sec
Forced spirometry (Jaeger) (3 times per day)
1kbit/day
Heart rate (calculated form ECG)
200bits/sec
Movement (accelerometers)
10kbits/sec
Oxygen saturation (numeric value)
24bits/sec
Pulse oximetry (Ir. wave form)
1kbits/sec
Pupil reaction
once a day
Surface EMG striated, 1 channel
32kbits/sec
Temperature
32bits/sec
Breathing frecuency is calculated out of the respiration signal
16
Step length and walking distance are calculated out of the movement signal
Technical limitations
17

Bandwidth

Roaming and cross border connectivity

Coverage

Speed

Handover
Bandwidth: GPRS rates
Radio Carrier: 8 channels
12345678
GSM Voice: 1 conversation  1 channel
1 channel for GSM data
 9.6 kbps
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/slot
CS-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).
18
Roaming and cross border connectivity
GPRS ROAMING AGREEMENTS
COUNTRY
OPERATOR
Alemania
T-Mobile Deutchland
Austria
T-Mobile Austria
Bélgica
Mobistar
Chequia
RadioMobil
Filipinas
Smart
Francia
Orange France
Hutchison Telephone
Hong Kong
Hong Kong CSL
Italia
TIM
Portugal
TMN
O2 UK
Reino Unido
Orange UK
19
Singapur
MobileOne
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.
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.
20
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.
21

Possibility of measurement probe in Telia network??
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:

22
•
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)
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.

23
The available data are:
•
Connection duration
•
Connection date and time
•
Number of sent/received bytes
•
Assigned IP address
Data collection tool in TME

This tool provides information about the connection of a user, 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.
24
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.

25
Tests of the tools before trials.
Deliverable D3.1
Trial ready GPRS networks

GPRS network:
•
Description of communication architecture
•
Technical limitations in each trial scenario
 Deliverable
1.3


26
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
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)
27