1. IEEE 11073 20101 ACSE_SA_rev03.ppt SLIDE 1 IEEE 11073 20101 Application Profile – Association Control Function Paul Spadafora, pjspadafora@center4mi.org

2. IEEE 11073 20101 ACSE_SA_rev03.ppt SLIDE 2 Scope Define compatible set of association control messages for both 20101 & 20601 Allow all data to be communicated using MDER (Simpler than BER) Support multiple protocol / application services (e.g., POC, PHD, PCD,...) Support “Fast reconnect”

3. IEEE 11073 20101 ACSE_SA_rev03.ppt SLIDE 3 Status A draft proposal has been created start with the 20601 approach to messaging Moved away from ACSE Standard – including removal of the Presentation and Session Layer Added new data fields to the 20601 structures to capture needed 20101 data

4. IEEE 11073 20101 ACSE_SA_rev03.ppt SLIDE 4 Open Issues 20101 allows for MDAP-XT (expedited) and coalesced messages at the session Layer. These do not exist in 20601. Do we need to support these?

5. IEEE 11073 20101 ACSE_SA_rev03.ppt SLIDE 5 Open Issues Can we support “fast to operating” feature? Reduces the amount of time and data transferred from association to operating state. Needs to be studied 20101 is based on the Manager initiating association Does the existing state machine and messages after association support this? How about “fast to in-sync”?

6. IEEE 11073 20101 ACSE_SA_rev03.ppt SLIDE 6 20101 – Start-up System Interaction “fast to operating” would eliminate this

7. IEEE 11073 20101 ACSE_SA_rev03.ppt SLIDE 7 “fast to in-sync” Two substates of operating: -“in-sync” -“out-of-sync”

8. IEEE 11073 20101 ACSE_SA_rev03.ppt SLIDE 8 Open Issues Should we harmonize the manager/agent association initiation? Currently Manager in 20101 initiates the association. Agent in 20601 initiates the association PHD are generally low powered devices Makes sense to reduce the burden of discovery / association. Doesn’t necessarily apply for POC devices If we change there will be legacy issues

9. IEEE 11073 20101 ACSE_SA_rev03.ppt SLIDE 9 Future considerations Harmonized association moves away from standardized association towards a custom solution for medical devices Session and Presentation Layer is null Presentation Layer is hardcoded to MDAP Does this constrain us too much in the future? If need be, could put presentation context at application layer

10. IEEE 11073 20101 ACSE_SA_rev03.ppt SLIDE 10 Next Steps Participant review of draft proposal Identify any issues and address them Discuss on periodic web-ex Investigate and propose a solution for: “fast to operating” Manager vs Agent association initiation Finalize proposal and vote