1 / 24

IEEE 11073 20401 Application Profile - Common Network Services - UML adaptation

IEEE 11073 20401 Application Profile - Common Network Services - UML adaptation. Vivek Kamath, vpkamath@westhealth.org ; Jan Wittenber, jan.wittenber@philips.com. IEEE 11073-20401 Project (PAR) Scope:.

jihan
Download Presentation

IEEE 11073 20401 Application Profile - Common Network Services - UML adaptation

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 Application Profile - Common Network Services- UML adaptation Vivek Kamath, vpkamath@westhealth.org; Jan Wittenber, jan.wittenber@philips.com

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

  6. Application Scenarios ENV 13735 Annex E 3

  7. Application Scenarios

  8. Transport Stack View Note: this slide is adapted from the UML F&O UML F&O. Link Profile <type> 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 TISL <type> RTP TCP UDP SCTP TinyTP Link Profile <type> Link Profile <type> 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. TISL • Provides uniform interface to upper layers • Has following services • Discovery of services and devices • Connectivity • Provisioning • Security • Quality Of Service (QoS)

  10. CNS Framework

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

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

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

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

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

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

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

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

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

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

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

  22. 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] Mgr Agent Mgr Agent P/LAN wPAN P/LAN wPAN [w]PLAN _jw2a

More Related