Table of Contents

 0 Introduction   vi
        0.1 Organization   vi
        0.2 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 CCCs
        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 Authenticated 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 and session termination
                  8.2.6 APS-CCC diagnostic message
9 Behavioural model: MQTT
        9.1 Overview of operation
                  9.1.1 Graceful APS termination
        9.2 Interaction of the Health & Fitness services application with the PHG application
        9.3 State of the PHG's connection to the HFS MQTT server
                  9.3.1 Interaction of a PHG 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 PHG SMS information
       10.5 SMS message structure
       10.6 PHG application requirements
       10.7 Semantic behaviour of the PHG application relative to ST reception
Annex A – Normative guidelines for the APS-CCC
       A.1 Guidelines for the APS components in capabilities exchange
       A.2 Guidelines for PHG APS management (APS-CCC-PHG)
       A.3 Guidelines for the PHG application interactions with the MQTT server
       A.4 Guidelines for HFS application APS management
       A.5 Guidelines for the PHG application SMS shoulder tap
       A.6 Guidelines for the Health & Fitness services application SMS shoulder tap
Annex B – XML schema for the APB resource
Appendix I – APS details
       I.1 APS information in the root.xml
       I.2 APS authentication: Resource owner password credentials approach
       I.3 APS establishment: PHG application POST with partial APB
                  I.3.1 APS establishment: PHG GET for completed APB
                  I.3.2 APS establishment: PHG setup with MQTT server
                  I.3.3 MQTT: PHG application subscribes to commands
                  I.3.4 MQTT: PHG Application Publishes "CONNECTED"
       I.4 APS establishment: PHG application enables APS
       I.5 Operation
Appendix II – Example Health & Fitness service root.xml file
Bibliography