M2M Always Connected in Trustful Domains for Multi vendor devices

[pchainho]

Actors

Alice is a Identified Consumer that purchased a new device from a certain Device Manufacturer (new Business Role?) which is different from the existing installed devices.

Pre-conditions:

Device is configured by the manufacturer to automatically register, discover and connect to certain types of devices belonging to the same domain. .

Description

1- As soon as the device is turned on and connected to the network, it will register in the domain (e.g. residential or enterprise gateway).
2- Device automatically discovers other devices to connect with or to subscribe to certain events
3- Device connects to other devices to request data, publish data or to subscribe to certain events \ data

Example: new washing machine is connected and discovers the HEMS (Home Energy Management System) system, subscribes to receive events about its level of voltage notifications

Variation

1- As soon as the device is turned on and connected to the network, it will register in the domain (e.g. residential or enterprise gateway).
2- Other devices are notified about the new registered device,
3- Other Devices connects to new device to request data, publish data or to subscribe to certain events \ data

Differentiation – market relevance

Currently, there is no standard mechanism to enable p2p adhoc connections between "smart devices". This is a market with a huge potential namely HEMS (check http://www.greentechmedia.com/research/report/home-energy-management-systems-2013-2017)

[sbecot]

I'm not very comfortable with the example. The solar panel feeds a battery and only that. It can only provide a level of voltage. The battery can provide the information of being enough fueled or not. But who is deciding that the washing machine will work? The machine itself, a programmable system that may trigger when the battery is full, but certainly not the solar panel.

[pchainho]

what about having the new washing machine to discover the Photovoltaic system and asks it to subscribe about its level of voltage notifications?

[pchainho]

Hi @aescobar81 could you review / complete / correct?

thx

[aescobar81]

Preconditions

1. Local Front-end platform or M2M Gateway manages Alice devices. The gateway should support discovering mechanisms, in case that they have RE-Think capabilities. Otherwise the Gateway should support the entire communication stack of the device.
2. Devices supports the discovery mechanisms supported by the gateway.
3. The interworking protocol can follow RE-Think mechanism protocol on the fly provisioning.
4. Both gateway and devices should support similar access technologies.

Description

1. As soon as the device is turned on and connected to the network, it will register in the front-end platform (gateway).
2. Based on certain events generated by these devices, the user can program/configure certain actions.
3. Device / application, automatically discovers other devices to connect with or to subscribe to certain events
4. Device / application connects directly or through mediator (gateway) to other devices to request data, publish data or to subscribe to certain events \ data.

Differentiation – Market relevance
Due to the limitation of resources (smart objects and devices) as well as the heterogeneous access technology, an intermediate component has to be deployed: gateway. The gateway provides the devices management interworking across access technology, and enable user to program/configure/host/deploy the applications.

[aescobar81]

Hi Paulo, we modify the preconditions:

Preconditions

1. Use case User Authentication and Registration #81 User Authentication and Registration with authentication / authorization
2. Local Front-end platform (M2M Gateway or devices) manages Alice sensor/actuator.
3. The gateway should support discovering mechanisms.
4. The device discovering can be done in two levels: 1) An intermediate component /node (gateway) discover the sensor/actuator in certain area, 2) User discovers sensor/actuator in ambient or at given location.
5. Both gateway and devices should support similar access technologies.
6. Devices supports the discovery mechanisms supported by the gateway.
7. The devices should be able to interact interoperable manner to exchange data and commands.

Description

1. As soon as the device is turned on and connected to the network, it will register in the front-end platform (gateway).
2. Based on certain events generated by these devices, the user can program/configure certain actions.
3. Device / application, automatically discovers other devices to connect with or to subscribe to certain events
4. Device / application connects directly or through mediator (gateway) to other devices to request data, publish data or to subscribe to certain events \ data.

Differentiation – Market relevance

Due to the limitation of resources (smart objects and devices) as well as the heterogeneous access technology, an intermediate component has to be deployed: gateway. The gateway provides the devices management interworking across access technology, and enable user to program/configure/host/deploy the applications.

[pchainho]

Hi @aescobar81 feel free to change in the main description (1st comment) or aren't you able to edit it?
Have you seen #6 ?

[antonroman]

Hi,
IMHO the example included in the issue makes sense, however I would change the photovoltaic system for a HEMS (Home Energy Management System) which is the name given by the industry for a device which:

• receives inputs from devices/systems which produce and consume energy in a house
• applies algorithms to make optimization decisions
• sends signals to devices/systems, sends information to external systems, shows information in a human-friendly format.
  BTW HEMS is a relevant market: http://www.greentechmedia.com/research/report/home-energy-management-systems-2013-2017

[pchainho]

Great, just updated the description!