Light control: Difference between revisions

Revision as of 09:31, 14 October 2016

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:

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.
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.
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.
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.

Application developer Guide

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

@@ Line 3: / Line 3: @@
 </div>
 -----
+== 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:
@@ Line 29: / Line 31: @@
 [[MEDIA:TR-0025_V1.1.0.doc  ‎ | Application developer Guide TR-0025_V1.1.0.doc ‎‎  (Sept 2016)]]
-== Use case description ==
-This clause briefly describes the use case from perspective of service being provided by the oneM2M platform. The physical device components are introduced in the current section.
-The described use case enables the remote control of lights via a smartphone or smart tab which embeds an application that gains access to a oneM2M service platform. The overview of the use case of remote lights control is shown in figure 5.1. The main components are introduced as follows:
-<ol>
-<li>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.
-</li>
-<li>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.
-</li>
-①		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.
-②		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.
-③		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.
-④		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.
-Figure 5.1: Overview of remote lights control use case
 == Architecture ==
 == Procedure ==
 == Implementations ==