1 / 38

IEEE 11073 20401 Common Network Services

IEEE 11073 20401 Common Network Services. Vivek Kamath, vpkamath@westhealth.org. IEEE 11073-20401 Project (PAR) Scope:.

jethro
Download Presentation

IEEE 11073 20401 Common Network Services

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. IEEE 11073 20401 Common Network Services Vivek Kamath, vpkamath@westhealth.org

  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.

  3. Scope Summary: • Define common set of networking services • Transport Neutral • Enable plug-and-play • For medical devices

  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

  5. CNS Discussion Outline • Topological View • Clinical Scenarios • Profiles and Services • Transport Stack • Preferred Technologies • TISL • Services

  6. Clinical Scenarios - ENV 13735 Annex E 2.1

  7. CNS- Profiles

  8. Transport Stack View IP Support Services Location services 11073 “upper layers” LDAP DHCP Net. capacity service Radius 802.1x NAT NTP Presence services SNMP 11073 assoc service 11073 config service DNS Interface to ‘upper layers” - TISL RTP/SCTP TCP UDP SCTP TinyTP IP IrLMP IP profile ether class drv GPRS EDGE 1xRTT 4G /LTE MDP PHDC 802.3 802.11 IrLAP 802.16 ZigBee Cellular Data USB USB BlueTooth BlueTooth ethernet 10/100/ 1000BT Wi-Max IR RS-232 RF RF RF Wi-Fi MICS WMTS current short term short term possible future possible future point to point links IP centric links

  9. Technologies that can be used for CNS(Initial Scope) CNS requirements fall between Transport Type3-Transport Type4

  10. TISL • Provides uniform interface to upper layers • Provides support for following services • Discovery of services • Connectivity • Provisioning • Security • Quality Of Service (QoS)

  11. Interface – Physical/Link Layer 802.3 • Will be used as specified in IEEE 11073-30400 • MAC/PHY specified in 11073-30400

  12. 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?

  13. Provisioning Services DHCP Medical Device (DHCP Client) DHCP Server (selected) DHCP Server (not 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

  14. 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

  15. Provisioning Services (TISL primitives) Providers DHCP, none (for static provisioning)

  16. Provisioning Services (TISL State Chart)

  17. 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

  18. 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

  19. 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)

  20. 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.

  21. Discovery Services – mDNSService Discovery Medical Device (mDNS Client) configured as bed2floor1unit4._11073PocManager._udp.local. Configured to find _11073PocAgent._udp.local. Any services of type _11073PocManager._udp.local. bed2floor1unit4._11073PocManager._udp.local. Request domain name and port for service bed2floor1unit4._11073PocManager._udp.local. machine1.local.:2030 IP:10.10.10.23

  22. 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 tcpin 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

  23. Discovery Services – Resource Types • Device Resource Types • _11073PoCAgent • _11073PoCManager • More? • Additional information in TXT record • Data-proto-id=“20101”,”20202” • More?

  24. Discovery Services - TISL Primitives Providers mDNS for local. scope, DNS for managed network

  25. Discovery Services – State Chart

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

  27. Connectivity Services – TISL primitives

  28. CNS Topics for further discussion

  29. Quality Of Service (QoS) • Reliability • Latency • Priority • Bandwidth

  30. QoS Services – Requirements (11073-00101-2008)

  31. 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

  32. Security Services IPSec • CNS will provide mechanisms to allow for secure connection • Technologies such as IPSec can be used for end to end security.

  33. Security Services - TISL

  34. What’s next … • Next steps: • Align with IHE DPI Discussions @ Thursdays 11:00 “AFC” Pacific • Get content to completion by 2014 January WGM • Draft by 2014 January WGM • Questions?

More Related