Skip to content

7.3 Remote control scenarios

7.3.1 Introduction

Lights are able to be controlled remotely through the smartphone application accessing the oneM2M service platform. Two scenarios are introduced in clauses 7.3.2 and 7.3.3.

7.3.2 Single light control

Light#1 and Light#2 are controlled remotely by a human user through a smartphone application (IN-AE). A call flow for single light control is depicted in figure 7.3.2-1 and the steps are ordered as follows:

  1. When the user updates the light state on her/his smartphone, the IN-AE creates a new contentInstance representing a new light state under the targeted container of a Light ADN-AE stored in the MN-CSE.
  2. If the contentInstance is created sucessfully_,_ the MN-CSE sends a notification to the corresponsding Light ADN-AE to notify it that a new contentInstance resource was created.

Single light remote control phase call flows

Figure 7.3.2-1: Single light remote control phase call flows

7.3.3 Multiple light control

Users can also remotely control multiple lights through the smartphone application (IN-AE) by sending a single light control command to the group resource. A call flow for multiple lights control is depicted in figure 7.3.3-1 and the steps are ordered as follows:

  1. When the user updates the state of a group of lights on her/his smartphone, the IN-AE sends a contentInstance create request targeting the group resource on the MN-CSE. The MN-CSE then fans out the request to the individual Light container member resources on the MN-CSE..
  2. For each contentInstances created sucessfully_,_ the MN-CSE sends a notification to the corresponsding Light ADN-AE.

Multiple lights remote control phase call flows

Figure 7.3.3-1: Multiple lights remote control phase call flows