Mark Schnell, mschnell@cisco

1. IEEE 11073 Inter-LAN Work Group Statusin association with HL7 DEV SIG & ISO TC 215 @ HL7 Working Group Meeting, San Antonio, TX, USA, 2008Jan18 Mark Schnell, mschnell@cisco.com

2. 11073 Inter-LAN Agenda • History / Goals from <Atlanta, GA, USA, 2007.09.20> • Re-factor work items between… • -30200 Cable connected • -30400 Cabled Ethernet • -20401 Common Network Infrastructure • Status • Next Steps • Back up

3. goals New breakdown • 30200: Cabled Connected • IrDA over RS232 signaling • MIB powering (2 options) • 10 Mbps Ethernet signaling (optional) • 10/100 Mbps Ethernet signaling (optional) • MIB vs. Ethernet PoE “cross connect” annex • POC scope only (update and re-ballot) • 30400: Cabled Ethernet – Infrastructure • 10/100/1G Mbps Ethernet over Cat5 • Real Ethernet signaling • Real Power over Ethernet • NOT POC scope (i.e. BCC upstream only) Use “Slide Show” mode: build a slide Re-factored work items: Old breakdown • 30200: Cable Connected • IrDA over RS232 signaling • MIB powering (2 options) • 10 Mbps Ethernet signaling (optional) • 30400:Cabled Ethernet - POC • 10/100 Ethernet signaling compatible with 30200 • MIB power vs. Ethernet PoE “cross connect” annex

4. Non-PoC area Point of Care area “Curtain” Infrastructure Ethernet “A” reference point DCC “F” : BCC “G” “B” “E” DCC : BCC MIB : Aggregation Device “H” “C” “D” “I” DCC : BCC MIB : Aggregation Device “J” Network Connected Medical Device = not allowed by definition = -30200 connector = -30400 connector <any> = Traditional Ethernet connector Clinical Point of Care deployment diagram

5. goals Revisit Discovery Analysis due to Microsoft not putting WS-Discovery into an SDO. Use “Slide Show” mode: build a slide -20401 Work Item List: Device list, data rates, event intervals, …. • Device communications characteristics • Application & Transport data types & characteristics • IP Interoperability Framework Analysis • IP address assignment mechanism • Service discovery (w/ service attribute matching) • Service definition mechanism • Control (aka command/response) mechanism • Notification (aka async event reporting) mechanism • Data transport • Continuous (via streaming) data type • Episodic, Control, Alarm (via transaction) data types • Document (via batch) data type • Inter-LAN test cases • Functionality defined • Control Specifics defined • Data transport Specifics defined • Test case system “Extended Services” Defined • In service fault detection mechanism • dropped packets • latency measure • … Ö Latency/reliability “12-box” • Application typical use: continuous, episodic, control, alarm, document • Transport: streaming, transaction, batch Ö Ö Ö Ö 11073 “Upper Layers” support this directly. • Logging/audit mechanism • alarms • alerts • interesting events • misc. notes/messages

6. 11073 Inter-LAN Agenda • History / Goals from <Atlanta, GA, USA, 2007.09.20> • Status • -30400 Cabled Ethernet • -30200 Cable connected • -20401 Common Network Infrastructure • Next Steps • Back up

7. & status Ö Ö Ö Ö Ö – 2008Jan25, Fri Use “Slide Show” mode: build a slide -30400 Work Item List: goals (Presentation mode: build-a-slide) • 11073-30400 Cabled Ethernet Infrastructure “Intent” • High level goals. (i.e. Cat 5 cabling; 10/100/1000 baseT; special features) • NOT POC scope (aka BCC upstream only) • Documentation strategy • Start with 802.3-2005 (the latest monolithic 802.3 spec) • Clause by clause (1 thru 67) and annex by annex: record thumbs up or thumbs down with an explanation/rationale as to the choice. • Turn the crank • Technical content is complete • Balloting logistics • Ballot group invitation started • IEEE editorial review complete & comments folded in • Ballot group invitation closes • Ballot started • Disposition comments • Ballot complete

8. & status Ö Yet to do. Ö Ö 75% complete Use “Slide Show” mode: build a slide -30200 Work Item List: goals • Document strategy • No Word version of existing doc • Only generate/review deltas to existing -30200 spec • Have IEEE editors merge changes into a new, full -30200 spec • Ballot resulting spec • Start with existing -30200 Cable Connected spec • Add current errata • Change existing -30200 Annex F • From: 10 Mbps Ethernet signaling (optional) • To: 10/100 Mbps Ethernet signaling (optional) • Add new (informative) -30200 Annex O • From: MIB power vs. Ethernet PoE “cross connect” -30400 annex ATo: MIB power vs. Ethernet PoE “cross connect” -30200 annex O • Update “cross connect” details with latest “termination” information • Ballot logistics Thanks Todd, for this suggestion!

9. & status No progress : ( • Macro use scenarios • 11073-20601 (PHD) over IP. (i.e. 1-agent to 1-manager) • Classic 11073 upper layers over IP. (i.e. 1-agent to 1-manager and 1-agent to n-managers) • Profile outline • Data plane: • Control plane: • Security plane: • Test case system “Extended Services” Defined • In service fault detection mechanism • dropped packets • latency measure • … More on next slides channel use models <investigating> <investigating> Use “Slide Show” mode: build a slide -20401 Work Item List: goals Common Network Infrastructure Device list, data rates, event intervals, …. • Device communications characteristics • Application & Transport data types & characteristics • IP Interoperability Framework Analysis • IP address assignment mechanism • Service discovery (w/ service attribute matching) • Service definition mechanism • Control (aka command/response) mechanism • Notification (aka async event reporting) mechanism • Data transport • Continuous (via streaming) data type • Episodic, Control, Alarm (via transaction) data types • Document (via batch) data type • Inter-LAN test cases • Functionality defined • Control Specifics defined • Data transport Specifics defined • Test case system “Extended Services” Defined • In service fault detection mechanism • dropped packets • latency measure • … Ö Latency/reliability “12-box” • Application typical use: continuous, episodic, control, alarm, document • Transport: streaming, transaction, batch Ö Revisit Discovery Analysis due to Microsoft not putting WS-Discovery into an SDO. Ö Ö Ö 11073 “Upper Layers” support this directly. • Logging/audit mechanism • alarms • alerts • interesting events • misc. notes/messages

10. TCP socket TCP socket TCP socket TCP socket TCP or UDP or SCTP or <whatever> socket(s) TCP socket TCP socket TCP or UDP or SCTP or <whatever> socket(s) Well known port: <WKP> Well known port: <WKP> Ephemeral port:<EP> Well known port: <WKP> Ephemeral port(s): <EP1-x> Well known port: <WKP> Ephemeral port:<EP0> Ephemeral port(s): <EP1-x> 1 chan mode 2 chan mode m chan mode n chan mode Data plane: Possible channel use models • Role A: start up path • Initial contact • Negotiate for ‘transport control channel” • Note: temporary role • Role B: Transport control path • Negotiate for ‘data channel(s)” • Note: permanent role • Role C: 11073 data path(s) • 11073 APDUs • Real measurement data • Note: permanent role

11. Mgr Mgr Mgr : Classic 11073overIP-30200/30300 PHD overUSBBTIP Classic’ 11073or PHDoverIP Agt Agt Agt 1 to 1 1 to 1 1 to n -20101 Classic 11073 -20601 PHD USB PHDC Blue Tooth MDP Macro use scenarios Dev/Networkmgt tools?? Mgr POCTA-1overIP-30200/30300 Agt 1 to 1 “upper layer” options -90101 POCT1-A -30200 Cable connected -30300 Infrared wireless “lower layers” options IP centric

12. -30000 Items • Re-kick off -30000: Transport Framework & Overview • Officially open PAR now • -30000 Topics • Transport Service Model (TSM) • Seed with Transport Independent SubLayer (TISL) • Seed with Generic Transport Model (GTM) • Seed with “12 box” reliability.latency model • “PHD/11073” “dev spec” discovery…. • Real transports stacks characteristics • Map real transports to “transport characteristics” • Transport characteristics : FlowCtl, Reliable, Latency, Wired/wireless, … • New idea of a “fast-reconnect” (i.e. preserve state agent/manager over a TCP timeout) • Use 2-3 representative examples from 11073 lower layers • Use case collection? • Possible sources: • RF guidelines doc (-00101) • -20401 Inter-LAN analysis • PHD

13. 11073 Inter-LAN Agenda • History / Goals from <Atlanta, GA, USA, 2007.09.20> • Status • -30400 Cabled Ethernet • -30200 Cable connected • -20401 Common Network Infrastructure • Next Steps • Back up

14. Next steps • -30400 Cabled Ethernet • Finish ballot process • -30200 Cable connected • Finish ‘delta’ document • Start and finish ballot process • -20401 Common Network Infrastructure • Develop transport architecture • Overlay supporting network services • -30000 Transport Framework & Overview • ??work as back ground to -20401 activities??

15. Logistics/contacts Emails: list: x73-30400@ieee.org chair: x73-30400-chair@ieee.org Weekly calls: • Date: Weekly on Tuesday • Time: 12:00 PM (noon) USA/Eastern Time

16. Back up / details

17. (Item 1 from -20401 Work List)Device communications characteristics

18. 10 11 12 Max. latency tolerance(transport latency budget) 7 8 9 4 5 6 1 2 3 (Item 2 from -20401 Work List)Healthcare data types Presentation mode: build a slide

19. Data Path Establishment ServiceDiscovery Ö A Day In The Life Of A Networked Medical Device (Presentation mode: build-a-slide) Stage 0 Stage 1 Stage 2 Stage 3 Stage 4 Stage 5 Set up in hospital IT?? Find a network Get on the IP network Get the “clinical framework” AssociateMed. end pts Disassociate Med. End pts Encryption keys?? Home “domain”?? (enables HLR/ VLR from cellular) L2 activity AAA (Authentication, Authorization, & Accounting)? 802.1x, Bluetooth “pairing”, other out-of-band pairing, … ? IP addr Sub-net Local domain Gateway Pri/sec “Clinical Framework” server (aka config server) NAC (Network Access Control)? Med SLA check? Network services • Pri/sec association server • NTP • “Home” POC (for HLR/VLR for POC roaming?) • … Clinical “services” • Which VS Mon • Which Nurse station • Which printer • Which plotter • … Dimensions • Static part • Dynamic part (esp. w/ wireless access) (use a “touch” association?) Association negotiation (esp. Med SLA check) (SIP w/ SDP ?) RTP/RCTP (w/ new profiles?) (use a ‘test stream’ to measure the net at set up?) (like a telephony ‘continuity tone’?) RSVP?? Transfer data Release association (aka release end point & network resources) Note: The 11073 Inter-LAN working group is using the above working diagram to assist in keeping focus on the appropriate scope for each step of our work

20. (Item 3 from -20401 Work List)IP Interoperability Framework: definitions (Presentation mode: build-a-slide) 3. IP Interoperability Framework feature areas: • IP address assignment mechanism • How are IP addresses assigned to all the devices in an 11073 MDC system? • Service discovery (w/ service attribute matching) • How are the various “services” of a given device advertised and discovered by other devices in the 11073 MDC system? • Service definition mechanism • How are the various “services” of a given device actually described and defined such that the “service” is usable & understandable by other devices in the 11073 MDC system? • Control mechanism • aka command/response mechanism • How is a generic “command” sent to a device and how is a response (if any) returned to the caller? • Notification mechanism • aka subscribe/notify mechanism • aka receive specific/interesting async events • How does an “interested party” register with a device such that it will be notified when a particular event occurs? • Data transport • How are the specific medical data transported over the IP network… • Document/batch data types • Episodic/transaction data types • Continuous/streaming data types …such that their specific latency & reliability requirements are met?

21. Preferred (Item 3A & 3B from -20401 Work List)Service Discovery Analysis: Short list Revisit Discovery Analysis due to Microsoft not putting WS-Discovery into an SDO. Risks/Issues • No Discovery Proxy • No standards body home • No Interoperable Directory Agent • “Service description framework” is out of scope • “Service description framework” and… • Discovery “query matching” are out of scope • WS-Discovery • SLP • ZeroConf Web Services Discovery Service Location Protocol Zero Configuration

22. (Item 3A & 3B from -20401 Work List)Service Discovery Analysis: Summary

23. Transport Stack Overview 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” RTP TCP UDP SCTP TinyTP L4 - xport IP IrLMP L3 - net IP profile ether class drv GPRS EDGE 1xRTT MDP PHDC 802.3 802.11 IrLAP 802.16 L2 - link ZigBee Cellular Data USB USB BlueTooth BlueTooth ethernet 10/100/ 1000BT Wi-Max IR RS-232 RF RF RF L1 - phy Wi-Fi MICS WMTS current In process short term possible future possible future point to point links IP centric links

24. The Eight Fallacies of Distributed Computing “Essentially everyone, when they first build a distributed application, makes the following eight assumptions. All prove to be false in the long run and all cause big trouble and painful learning experiences.“ • The network is reliable • Latency is zero • Bandwidth is infinite • The network is secure • Topology doesn't change • There is one administrator • Transport cost is zero • The network is homogeneous Attribution: The true origins of this list are somewhat mythic, being largely based on the collective experience of many hackers in the early days of building distributed systems. Peter Deutsch is the one who first enumerated them as a clear way to frame thinking about why distributed systems are fundamentally different. He says the following on his home page: “I first published the "8 Fallacies of Networking" internally while working at Sun Microsystems Labs in 1991-92. (The first 4 were originally described by either Bill or Dick Lyon; I added the other 4.)