Light control

From OneM2M
Revision as of 09:35, 14 October 2016 by Admin (talk | contribs)
Jump to: navigation, search
Light Control example

Use case description

The described use case enables the remote control of lights via a smartphone which embeds an application that gains access to a oneM2M service platform. The main components are introduced as follows:

Lamp diagram1.jpg

  1. Light lamps shown in the current use case are deployed at a house and attached to a home gateway. The light lamps are able to interact with a oneM2M platform through a wireless access interface.
  2. The home gateway is configured to be able to search and connect light lamps into itself and to communicate with a oneM2M service platform in terms of exchanging and storing light lamps states between the light lamps and the oneM2M service platform.
  3. oneM2M service platform provides vertical application services targeted at different field domains, for instance, home, vehicle, and industry. The oneM2M service platform supports a group of common service functionalities such as registration, discovery, data management, group management, subscription/notification etc.
  4. The smartphone application is embedded into a smartphone and acts as a remote light controller with capabilities as the follows:
    • Discovery of light lamps deployed into the home gateway.
    • Sending commands to change light states i.e. ON and OFF.
    • Retrieval of light states.


    This clause describes the architecture of the implemented use case with components represented by the oneM2M entity roles. For instance, a physical device can be modelled as an ADN-AE and the oneM2M service system can be modelled as an IN-CSE, etc. The remote lights control use case shown in figure 5.1 can be mapped into the oneM2M functional architecture depicted in figure 6.1.

    Lamp diagram2.jpg In oneM2M functional architecture two entity roles are defined, one is AE and the other is CSE. Application dedicated devices e.g. light lamps are usually acted as an ADN-AE. Smartphone applications that are embedded into smartphone devices and able to communicate directly with oneM2M service platform can also be acted as an ADN-AE. oneM2M service system is acted as an IN-CSE and the home gateway plays a role of MN-CSE. Two reference points, mca and mcc which are defined in the oneM2M functional architecture are used between AE and CSE and between two CSEs in the current use case, respectively. As figure 6.1 shows, the reference point used between any light application (ADN-AE-1 or ADN-AE-2) and home gateway MN-CSE is mca while that of between home gateway and oneM2M service platform is mcc. In summary, applications used in the current use case are classified as follows:

    1. ADN-AE1: an application embedded in the light lamp Light#1 with capabilities to control light lamp Light#1 and interact with the home gateway MN-CSE through mca reference point;
    2. ADN-AE2: an application embedded in the light lamp Light#2 with capabilities to control light lamp Light#2 and interact with the home gateway MN-CSE through mca reference point;
    3. IN-AE: a smartphone application embedded in the smartphone device with capabilities to interact directly with the oneM2M service platform IN-CSE through mcc reference point and thereby remotely control light lamps Light#1 and Light#2;
    4. MN-AE: a gateway application embedded into the home gateway MN-CSE and interact with MN-CSE through mca reference point.
    5. Procedure


      Application developer Guide

      Application developer Guide TR-0025_V1.1.0.doc ‎‎ (Sept 2016)