ToI: Provider Initiated with Intermittent Connections

Topic of Interest: Topic: PROVIDER Initiated vs. CONSUMER Initiated with Intermittent Connections

Issue

For wearables esp. with battery constraints, devices are only connected intermittently and initiate "upload" when re-connected. NOTE: 11073 Classic (Manager initiated), 11073 PHD (Agent initiated); SDC/SDPi - how to manage both?

NOTES:

• Use case scenarios should capture these. this is normal operation for these devices.
• Strategy could be to establish eventing with a CONSUMER and then at a established periodicity to publish updates and go quiet again etc.)
• Use of a "session" construct has also been suggested

A similar issue exists with Cloud Computing where the device on prem has always to establish the connection to the cloud service (see also Topic: SDC for Remote & Cloud-based Connections )

Review the linked Confluence Topic of Interest and the related “SDC for Remote & Cloud-based Connections” topic, then compare the 11073 Classic, 11073 PHD, and SDC/SDPi initiation models described here. The issue is complete when intermittent provider-initiated connection scenarios are captured and an agreed strategy, such as eventing, periodic publication, or sessions, is documented.