Table of Contents - ITU-T Rec. H.812.4 (11/2015) Interoperability design guidelines for personal health systems: WAN interface: Authenticated persistent session device class


0 Introduction vi 0.1 Organization vi 0.2 CDC guideline releases and versioning vi 0.3 What's new vi 1 Scope 2 References 3 Definitions 4 Abbreviations and acronyms 5 Conventions 6 Authenticated persistent session use case 7 Authenticated persistent session (APS) overview 7.1 Support for multiple CDCs 7.2 Topics used in MQTT 7.3 Shoulder tap 8 APS management 8.1 APB resources 8.2 APS behaviour 8.2.1 APS session state 8.2.2 Authenticate persistent binding identifiers (APBI) 8.2.3 Authenticated persistent binding establishment 8.2.4 Accepting an authenticated persistent binding 8.2.5 Authenticated persistent binding termination 8.2.6 APS-CDC diagnostic message 9 Behavioural model: MQTT 9.1 Overview of operation 9.1.1 Graceful APS termination 9.2 Interaction of the WAN application with the AHD application 9.3 State of the AHD's connection to the WAN MQTT server 9.3.1 Interaction of an AHD application with the MQTT server 10 Behavioural model: SMS shoulder tap capability 10.1 Shoulder tap overview 10.2 Scope 10.3 Shoulder tap invocation determination 10.4 AHD SMS information 10.5 SMS message structure 10.6 AHD application requirements 10.7 Semantic Behaviour of the AHD application relative to ST reception Annex A Normative guidelines for the APS-CDC (This annex forms an integral part of this Recommendation.) A.1 Guidelines for the APS components in capabilities exchange A.2 Guidelines for AHDAPS management (APS-CDC-AHD) A.3 Guidelines for the AHD application interactions with the MQTT server A.4 Guidelines for WAN application APS management A.5 Guidelines for the AHD application SMS shoulder tap A.6 Guidelines for the WAN application SMS shoulder tap Annex B XML schema for the APB resource (This annex forms an integral part of this Recommendation.) Appendix I APS details (This appendix does not form an integral part of this Recommendation.) I.1 APS information in the root.xml I.2 APS Authentication: Resource owner password credentials approach I.3 APS Establishment: AHD application POST with partial APB I.3.1 APS establishment: AHD GET for completed APB I.3.2 APS establishment: AHD setup with MQTT server I.3.3 MQTT: AHD application subscribes to commands I.3.4 MQTT: AHD application publishes "CONNECTED" I.4 APS Establishment: AHD application enables APS I.5 Operation Appendix II Example WAN root.xml file (This appendix does not form an integral part of this Recommendation.)

0     Introduction   vi
        0.1     Organization   vi
        0.2     CDC guideline releases and versioning vi
        0.3     What's new    vi
1     Scope
2     References
3     Definitions
4     Abbreviations and acronyms
5     Conventions
6     Authenticated persistent session use case
7     Authenticated persistent session (APS) overview
        7.1     Support for multiple CDCs
        7.2     Topics used in MQTT
        7.3     Shoulder tap
8     APS management
      8.1     APB resources
        8.2     APS behaviour
                  8.2.1     APS session state
                  8.2.2     Authenticate persistent binding identifiers (APBI)
                  8.2.3     Authenticated persistent binding establishment
                  8.2.4     Accepting an authenticated persistent binding
                  8.2.5     Authenticated persistent binding termination
                  8.2.6     APS-CDC diagnostic message
9     Behavioural model: MQTT
        9.1     Overview of operation
                  9.1.1     Graceful APS termination
        9.2     Interaction of the WAN application with the AHD application
        9.3     State of the AHD's connection to the WAN MQTT server
                  9.3.1     Interaction of an AHD application with the MQTT server
10     Behavioural model: SMS shoulder tap capability
       10.1     Shoulder tap overview
       10.2     Scope
       10.3     Shoulder tap invocation determination
       10.4     AHD SMS information
       10.5     SMS message structure
       10.6     AHD application requirements
       10.7     Semantic Behaviour of the AHD application relative to ST reception
Annex A Normative guidelines for the APS-CDC (This annex forms an integral part of this Recommendation.)
       A.1 Guidelines for the APS components in capabilities exchange
       A.2 Guidelines for AHDAPS management (APS-CDC-AHD)
       A.3 Guidelines for the AHD application interactions with the MQTT server
       A.4 Guidelines for WAN application APS management
       A.5 Guidelines for the AHD application SMS shoulder tap
       A.6 Guidelines for the WAN application SMS shoulder tap
Annex B XML schema for the APB resource (This annex forms an integral part of this Recommendation.)
Appendix I APS details (This appendix does not form an integral part of this Recommendation.)
       I.1 APS information in the root.xml
       I.2 APS Authentication: Resource owner password credentials approach
       I.3 APS Establishment: AHD application POST with partial APB
                  I.3.1 APS establishment: AHD GET for completed APB
                  I.3.2 APS establishment: AHD setup with MQTT server
                  I.3.3 MQTT: AHD application subscribes to commands
                  I.3.4 MQTT: AHD application publishes "CONNECTED"
       I.4 APS Establishment: AHD application enables APS
       I.5 Operation
Appendix II Example WAN root.xml file (This appendix does not form an integral part of this Recommendation.)