N0423 IEEE 11073 20401 Cambridge Update r2 - HL7

slateobservantΔίκτυα και Επικοινωνίες

26 Οκτ 2013 (πριν από 3 χρόνια και 9 μήνες)

117 εμφανίσεις

11073
-
20401
-
20130925


SLIDE
1

IEEE 11073 20401

Common Network Services



Vivek Kamath, vpkamath@westhealth.org

11073
-
20401
-
20130925


SLIDE
2

IEEE 11073
-
20401 Project (PAR) Scope:

Within the framework of IEEE 11073
standards, this standard will define a
common, transport neutral set
of
networking
services that will enable plug
-
and
-
play interoperability of medical
devices.

This project shall not address quality of
service over RF wireless network
connections.

11073
-
20401
-
20130925


SLIDE
3

Scope Summary:


Define common set of networking services



Transport Neutral



Enable plug
-
and
-
play



For medical devices

11073
-
20401
-
20130925


SLIDE
4

Aspects of CNS


Describes topological framework to
standardize network semantics for medical
devices


Enables profiling of clinical scenarios from
a communication perspective.


Defines a Transport
Independent System
Layer
(TISL
) as a standard interface
for
upper layers


Recommends technologies that can be
used for networking medical devices



11073
-
20401
-
20130925


SLIDE
5

CNS Discussion Outline


Topological View


Clinical Scenarios


Profiles and Services


Transport Stack


Preferred Technologies


TISL


Services




11073
-
20401
-
20130925


SLIDE
6

11073
-
20401
-
20130925


SLIDE
7

Clinical Scenarios
-

ENV
13735 Annex
E 2.1

Scenario

Communication Requirements

Emergency Situation


One

of the main
scenarios is alarm
(2.1.1)

Plug and Play
-

the device communication must start
immediately after device connection without any

further user intervention. That implies e.g. automatic
device recognition, identification, and initialization of

communication.


Safety and reliability of communication and network
-

connection of a new device must not influence

the communication of other devices connected earlier


Unique device identification

Normal patient nursing
condition in ICU, non
emergency situations
(2.2)

Same as above

11073
-
20401
-
20130925


SLIDE
8

Scenario

Communication Requirements

Data Logger ( 3.1)

Graphic parameter data volumes can require high
bandwidth

‘Loose’ device time stamp synchronization, in the order of
0.0N=獥捯ndI=i猠牥qui牥d.
=
oeal=Ti浥=aata=
ai獰la礠⠳.2F
=
iaten捹cof=data=between=a浰lifie爠output=and=di獰la礠on=
獣牥en=浵獴=be=le獳sthan=0.2=獥捯nd猠to=be=invi獩ble=
=
fo爠u獥r.
=
偡tient=Ala牭r
Monito物ng=⠳.PF
=
The=捯浭mni捡tion=of=ala牭r牥lated=info牭rtion=浵獴=be=
expeditedI=in=o牤e爠to=be=p牯捥獳sd=p物o爠to=
=
othe爠dataI=and=浵獴=be=牥liable.
=
ai獰la礠aevi捥=浵獴=be=able=to=dete捴=when=a=aata=Agent=
i猠牥浯ved.=fdeall礠it=獨ould=be=able=to=di獴ingui獨=between=
an=intentional=di獣snne捴ion=and=unintentional=
di獣snne捴ion.
=
The=laten捹cof=o捣c牲rn捥=of=ala牭rand=獩gnaling=to=u獥爠
浵獴=be=le獳sthan=0.25=獥捯nd献
=
11073
-
20401
-
20130925


SLIDE
9

Scenario

Communication Requirements

Remote Control (3.4)

In a remote control system, the communication must fulfill
a higher level of reliability, because of a higher

risk for the patient. This includes the needs for
comprehensive message validation, data verification,
message retries, and notification of communication system
failures. This implies the need for system management

functionality.

A mechanism to send control data to the data agent and
acknowledge receipt is required. In some cases

manual control of the device should be precluded.

Patient Viewing
Interoperability (3.5)

There must be some level of control such that a remote
user (i.e. outside the care unit) cannot change the

settings established by a nurse at the bedside.

Harmonization of communication methods for RF telemetry
systems would be required in order to support

interoperable telemetry systems.

Bandwidth management may become a big issue.

The issue of managing multiple associations between a
Data Agent and multiple Data Loggers or Data Dis
-

play needs attention.

11073
-
20401
-
20130925


SLIDE
10


Scenario

Communication Requirements

Patient Monitoring
Interoperability (3.6)

Communication over different hospital LANs

and maybe
even on the Internet.

Ordering of physiological data is important.

Latency from Data Agent to Remote Monitoring Device
must be controlled and specified. Generally, this

should be less than one second to be acceptable.

Maintenance

and
Configuration
Support

(3.8)

Physical connect/disconnect sensing for devices.

System management protocol

Intrabed

Symmetric
Data Exchange
between DCC and
BCC (4.1)


Interbed

Symmetric
Data Exchange over
an "
Interbed

Network“ (4.2)
=
卹浭pt特rin=捯浭mni捡tion=between=devi捥=⡄CC⤠and=
䉃C
=
卹浭pt特rin=data=p牯pagation=in=th牯ugh=the=䉃C=
-
=
f牯洠
devi捥=⡄CC⤠th牯ugh=䉃C=to=Appli捡tion=卹獴e洠
=
and=vi捥=ve牳r
=
偲mpagation=of=a=捯ntain浥nt=t牥e=of=a=牥浯te=devi捥=to=
the=牥捥ive爠⡄CCF
=
11073
-
20401
-
20130925


SLIDE
11

CNS
-

Profiles

11073
-
20401
-
20130925


SLIDE
12

Transport Stack View

ethernet



11073

“upper layers”



Wi
-
Fi

Cellular Data

Wi
-
Max

802.3

10/100/

1000BT

802.11

RF

GPRS

EDGE

1xRTT

4G /LTE

RF

802.16

RF

IP

RTP/SCTP

TCP

UDP

SCTP

IrLAP

IR

IrLMP

TinyTP

RS
-
232

IP Support Services

11073 config
service

11073 assoc
service

DHCP

DNS

Net.
capacity
service

LDAP

NTP

Radius

Location
services

Presence
services

SNMP

802.1x

NAT

USB

BlueTooth

PHDC

MDP

current

s
hort term

point to point links

short term

possible
future

IP centric links

USB

ether

class drv

BlueTooth

IP

profile

MICS

WMTS

ZigBee

possible
future

Interface to ‘upper
layers

-

TISL

11073
-
20401
-
20130925


SLIDE
13

Technologies that can be used for CNS(Initial
Scope)

Components

Layer

Technology

Interface

Physical/Link

802.3

Connectivity

Transport/Network

UDP/IP v4 and TCP/IP
v4

Security

Network

IPSec

over UDP,

IPSec

over TCP, None

Quality

Of Service

Application

RTP

over UDP, RSVP

Discovery

Application

mDNS
, DNS

Provisioning

Application

DHCP,

Statically
provisioned

CNS requirements fall between Transport Type3
-
Transport Type4

11073
-
20401
-
20130925


SLIDE
14

TISL


Provides uniform interface to upper
layers


Provides support for following services


Discovery of
services


Connectivity


Provisioning


Security


Quality Of Service (
QoS
)


11073
-
20401
-
20130925


SLIDE
15

Interface


Physical/Link Layer 802.3


Will be used as specified in IEEE
11073
-
30400


MAC/PHY specified in 11073
-
30400

11073
-
20401
-
20130925


SLIDE
16

Provisioning Services DHCP


Apart from IP address


Following options will be implemented


Domain Name Server Option. Code = 6


Subnet Mask Option. Code=1


Time Server Option. Code=4


Others?


11073
-
20401
-
20130925


SLIDE
17

Provisioning Services DHCP

Medical Device (DHCP Client)

DHCP Server (not selected)

DHCP Server (selected)

Begins Initialization

DHCPDISCOVER

DHCPDISCOVER

Determines Configuration

Determines Configuration

DHCPOFFER

DHCPOFFER

Collects replies

Selects configuration

DHCPREQUEST

DHCPREQUEST

Commits Configuration

DHCPACK

Initialization complete

Graceful shutdown

DHCPRELEASE

Discards Lease

DHCP Server can be used to provision IP Address and other artifacts

11073
-
20401
-
20130925


SLIDE
18

Provisioning Services
DHCP


Autonet

address
selection

Medical Device (DHCP Client)

Begins Initialization

Pick random address in 169.* scope

Is address available?

No Response

Self assign selected address

11073
-
20401
-
20130925


SLIDE
19

Provisioning Services

(TISL primitives)



Name

Description


TISL_provisioning_init

Initialize provisioning services

TISL_provisioning_enum_providers

Enumerate available provisioning providers

TISL_provisioning_set_provider

Set current provider

TISL_provisioning_add_item

Add provisioning item given the code

TISL_provisioning_remove_item

Remove provisioning item given the code


TISL_provisioning_get_item

Get item value given code


TISL_provisioning_auto_start

Start automatic provisioning using current
provider.


TISL_provisioning_uninit

Uninitialize

provisioning services


Providers DHCP, none (for static provisioning)

11073
-
20401
-
20130925


SLIDE
20

Provisioning Services (TISL
State Chart)

11073
-
20401
-
20130925


SLIDE
21

Discovery Services


DNS
mDNS


Plug and Play scenarios need
provisioning in order to successfully
associate with the peer


Can be used to discover services on a
medical network



Examples
:


An Agent starts up and tries to find Manager on local sub
-
network with some additional information to connect


Manager needs to find one of the IHE applications on the
enterprise network to send PCD01 message



11073
-
20401
-
20130925


SLIDE
22

Discovery
Services


DNS
mDNS


Can be done using multicast DNS for local
subnet and unicast DNS for enterprise
scope


Has two parts to it:


Resource Description


Resource Discovery


11073
-
20401
-
20130925


SLIDE
23

Discovery Services

DNS discovery in domain

Medical Device (DNS Client)

DNS Server

DNS Standard Query(SRV)

DNS Standard Query Response (SRV)

DNS Standard Query(A/AAAA)

DNS Standard Query Response (A/AAAA)

11073
-
20401
-
20130925


SLIDE
24

Discovery Services


mDNS

Name Selection and
Publication

Medical Device (
mDNS

Client)

Use configured name
bed2floor1unit4._11073PocAgent._udp.local.

Is address available?

No Response

Start Service with configured Name
on
udp

port XXXX

Register SRV

record with

bed2floor1unit4._11073PocAgent._udp.local.


Now available
bed2floor1unit4._11073PocAgent._udp.local.

11073
-
20401
-
20130925


SLIDE
25

Discovery Services


mDNS

Service Discovery

Medical Device (
mDNS

Client)

Configured to find _11073PocAgent._udp.local.

Any services of type
_
11073PocManager._
udp.local
.


bed2floor1unit4._11073PocManager._udp.local.

configured as
bed2floor1unit4._11073PocManager._
udp.local.

Request domain name and port for service
bed2floor1unit4._11073PocManager._udp.local.

machine1.local.:2030 IP:10.10.10.23

11073
-
20401
-
20130925


SLIDE
26

Discovery
Services


DNS Service URL format


General Service URL format


<Instance> . <Service> . <Domain>


_
tcp



used when
tcp

is the underlying protocol


_
udp



used for everything
else


Example,
_11073PoCAgent._udp.example.com


11073 agent
services
that don’t use
tcp

in the
domain example.com


Instance name is
a user
friendly name
consisting of
upto

63
Net
-
Unicode
[RFC5198] characters.


Example,
bed2Floor1Unit4._11073PoCAgent
._tcp.example.com


11073
-
20401
-
20130925


SLIDE
27

Discovery
Services


Resource Types


Device Resource Types


_11073PoCAgent


_11073PoCManager


More?


Additional information in TXT record


Data
-
proto
-
id=“20101”,”20202”


More?



11073
-
20401
-
20130925


SLIDE
28

Discovery Services
-

TISL Primitives

Name

Description


TISL_discovery_init


Initializes discovery services

TISL_discovery_enum_providers

Enumerates available discovery service
providers

TISL_discovery_init_provider

Initializes provider for use

TISL_discovery_register_service_notification

Sets callback for service discovery

TISL_discovery_start

Start discovery

TISL_discovery_cancel

Cancel discovery in progress

TISL_discovery_setDiscoverable

Set current device as discoverable for zero
-
touch mode

TISL_discovery_resetDiscoverable

Cancel current device as discoverable for
zero
-
touch mode

TISL_discovery_uninit

Uninitialize

discovery services

Providers
mDNS

for local. scope, DNS for managed network

11073
-
20401
-
20130925


SLIDE
29

Discovery
Services


State Chart

11073
-
20401
-
20130925


SLIDE
30

Connectivity Services


TCP/IP and UDP/IP v4


TCP or UDP can be used to establish
communication between agent and
manager


IP address and port needed for manager
or agent service can be obtained using
DNS or
mDNS

mechanism

11073
-
20401
-
20130925


SLIDE
31

Connectivity Services


TISL primitives

Name

Description


TISL_connectivity_init

Initialize connectivity services

TISL_connectivity_enum_providers

Enumerate connectivity service providers

TISL_connectivity_init_provider

Initialize provider

TISL_connectivity_set_notification

Set connectivity notification

TISL_connectivity_set_mode

Set synchronous or asynchronous mode of operation

TISL_connectivity_connect

Connect to peer

TISL_connectivity_disconnect

Disconnect from peer

TISL_connectivity_accept

Accept connection from peer

TISL_connectivity_listen

Listen for connections


TISL_connectivity_send

Send data


TISL_connectivity_receive

Receive data


TISL_connectivity_sendto

Send datagram

TISL_connectivity_uni nit

Uninitialize

connectivity services


11073
-
20401
-
20130925


SLIDE
32

CNS Topics for further discussion

11073
-
20401
-
20130925


SLIDE
33

Quality Of Service (
QoS
)


Reliability


Latency


Priority


Bandwidth

11073
-
20401
-
20130925


SLIDE
34

QoS

Services


Requirements (11073
-
00101
-
2008)

11073
-
20401
-
20130925


SLIDE
35

QoS

Services


Preferred Technologies


RTP
over
UDP


RTP provides a reliability layer over UDP


TCP/IP


Guaranteed delivery


RSVP for bandwidth reservation


All hops in the network have to participate
to reserve bandwidth

11073
-
20401
-
20130925


SLIDE
36

Security Services
IPSec



CNS will provide mechanisms to allow
for secure connection


Technologies such as
IPSec

can be
used for end to end security.

11073
-
20401
-
20130925


SLIDE
37

Security Services
-

TISL

Name

Description


TISL_security_init

Initialize security services

TISL_security_enum_providers

Enumerate security providers

TISL_security_set_provider

Set

current security provider

TISL_security_uninit

Uninitialize

security services

11073
-
20401
-
20130925


SLIDE
38

What’s next …


Next steps:

o
Align with IHE DPI Discussions @ Thursdays
11:00 “AFC” Pacific

o
Get content to completion by 2014 January
WGM

o
Draft by 2014 January WGM



Questions?