Presentation is loading. Please wait.

Presentation is loading. Please wait.

IEEE Application Profile - Common Network Services - UML adaptation

Similar presentations


Presentation on theme: "IEEE Application Profile - Common Network Services - UML adaptation"— Presentation transcript:

1 IEEE 11073 20401 Application Profile - Common Network Services - UML adaptation
Vivek Kamath, Jan Wittenber,

2 IEEE 11073-20401 Project (PAR) Scope:
Within the framework of IEEE 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 Define common set of networking services Transport Neutral
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 networked medical devices Enables profiling of clinical scenarios from communication perspective. Defines Transport Independent System Layer (TISL) as a standard interface to upper layers

5

6 Clinical Scenarios - ENV 13735 Annex E 2.1
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

7 Application Scenarios ENV 13735 Annex E 3
Communication Requirements Data Logger ( 3.1) Graphic parameter data volumes can require high bandwidth ‘Loose’ device time stamp synchronization, in the order of 0.01 second, is required. Real Time Data Display (3.2) Latency of data between amplifier output and display on screen must be less than 0.2 seconds to be invisible for user. Patient Alarm Monitoring (3.3) The communication of alarm related information must be expedited, in order to be processed prior to other data, and must be reliable. Display Device must be able to detect when a Data Agent is removed. Ideally it should be able to distinguish between an intentional disconnection and unintentional disconnection. The latency of occurrence of alarm and signaling to user must be less than 0.25 seconds.

8 Application Scenarios
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.

9 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) Symmetry in communication between device (DCC) and BCC Symmetry in data propagation in through the BCC - from device (DCC) through BCC to Application System and vice versa Propagation of a containment tree of a remote device to the receiver (DCC)

10 Link Profile <type>
Transport Stack View Note: this slide is adapted from the UML F&O UML F&O. ethernet 11073 “upper layers” Wi-Fi Cellular Data Wi-Max 802.3 10/100/ 1000BT 802.11 RF GPRS EDGE 1xRTT 4G /LTE 802.16 IP RTP 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 short term point to point links possible future IP centric links ether class drv profile MICS WMTS ZigBee Link Profile <type> Link Profile <type> TISL <type>

11 Provides uniform interface to upper layers Has following services
TISL Provides uniform interface to upper layers Has following services Discovery of services and devices Connectivity Provisioning Security Quality Of Service (QoS)

12 CNS Framework

13 What’s next … Next steps: Questions?
Align with IHE DPI Thursdays 11:00 “AFC” Pacific Core content ready by 2013 September WGM Draft ready by 2014 January WGM Questions?

14 TISL – connectivity primitives
TISL_connectivity_init TISL_connectivity_get_providers TISL_connectivity_set_provider TISL_connectivity_set_callback TISL_connectivity_set_mode TISL_connectivity_connect TISL_connectivity_disconnect TISL_connectivity_accept TISL_connectivity_listen

15 TISL connectivity primitives continued
TISL_connectivity_send TISL_connectivity_receive TISL_connectivity_uninit Preferred transport based on underlying layer support.

16 TISL – Discovery of services and devices primitives
TISL_discovery_init TISL_discovery_get_providers TISL_discovery_set_provider TISL_discovery_set_service_callback TISL_discovery_set_device_callback TISL_discovery_start TISL_discovery_cancel TISL_discovery_uninit Preferred provider SSDP

17 TISL provisioning primitives
TISL_provisioning_init TISL_provisioning_get_providers TISL_provisioning_set_provider TISL_provisioning_add_item TISL_provisioning_remove_item TISL_provisioning_get_item TISL_provisioning_uninit Preferred provider based on type of transport – can be DHCP, directory or some other mechanism

18 TISL security primitives
TISL_security_init TISL_security_get_providers TISL_security_set_provider TISL_security_select_key TISL_security_encrypt TISL_security_decrypt TISL_security_sign TISL_security_verify_signature

19 CNS UML modeling MDC CNS - UML
The following set of diagrams show initial mapping/transformation of previous UML, as follows: MDC CNS - UML Topological Framework and Overview. Application Profiling TISL Profiling – Link-level Profile topology TILS Profiling – Primitives Heuristics Profiles

20 MDC - UML- Topological Framework and Overview (F&O)
The “CNS Framework” mapped to UML. The constructs at left are “Profile” [compositions], and the ones at top to the right, are ‘use cases’ (of composite Profiles); the lower set are MDS-level, and the upper set are composites. The initial’ exemplar Profiles are at lower left, e.g. Monitor, Infusor, and Ventilator in the Critical-Acute Care [Unit] scopes.

21 MDC CNS - UML- Application Profiling
APPLication-level CNS Profiling characterizes the key semantics relative to the x73 “harmonization” definitions (see Wiki for Harmonization Framework documents).

22 MDC CNS - UML- TISL/Link-level component mapping topology
Link-level Profiles are typed and related to a normalized set of TISL Primitives.

23 MDC CNS - UML- TISL – Primitive [subset] mapping
TISL-level CNS Profiling characterizes the TISL Primitive subsets previously characterized.

24 MDC CNS - UML- Heuristic Profiles
This diagram will be used to overlay particular Profiles for heuristic purposes, generally trying to select Profile components to show typical variations in the highlighted topological scope. Link-level notations are productions of “[w][P/L]AN”, e.g. PAN, LAN, P/LAN, wPAN, wP/LAN, and wLAN. See shaded areas on the following diagram (F&O) for key heuristics, highlighting key variations. Mgr Agent[s] Agent P/LAN [w]PLAN wPAN _jw2a


Download ppt "IEEE Application Profile - Common Network Services - UML adaptation"

Similar presentations


Ads by Google