Phone Driven Interactions; An Exemplary Startup Interaction - Unify OpenStage Developer's Manual

Provisioning interface
Table of Contents

Advertisement

c03.fm
Basic Communication Procedures

Phone Driven Interactions

3.5
Phone Driven Interactions
Three different kinds of activities initiated by phones can be distinguished:
1.
Register with the provisioning service after startup, either initial startup, subsequent resets
or a factory reset.
Please ensure to provide the phone with the contact address of the provisioning
>
service (see Section 2.2, "Extended Configuration"). Otherwise, it will not be
able to register with the provisioning service after a factory reset.
2.
Inform the provisioning service about local configuration changes, even in case of a factory
reset.
Please ensure to provide the phone with the contact address of the provisioning
>
service (see Section 2.2, "Extended Configuration"). Otherwise, it will not be
able to register with the provisioning service after a factory reset.
3.
Inform the provisioning service about the status of a software or file deployment.
3.5.1

An Exemplary Startup Interaction

3.5.1.1
Message Flow
On startup, the phone informs the provisioning service about its existence. The following dia-
gram shows an example message flow which might occur on phone startup:
Phone
1
2
3
4
32
HTTPS Request
Reason for contact: start-up
<Basic data items>
HTTPS Response
Action: ReadAllItems
HTTPS Request
Reason for contact: reply-to
<All data items>
HTTPS Response
CleanUp
Nur für den internen Gebrauch
Provisioning Service
A31003-S2000-R102-16-7620 02/2016
Provisioning Service, Developer's Guide

Advertisement

Table of Contents
loading

This manual is also suitable for:

Openscape

Table of Contents