Bug 11252 - Create a new end-user profile to separate end user devices from gateway profile
Summary: Create a new end-user profile to separate end user devices from gateway profile
Status: RESOLVED WONTFIX
Alias: None
Product: IoT Reference OS Kit
Classification: Yocto Project Subprojects
Component: intel-iot-refkit-profile-gateway (show other bugs)
Version: unspecified
Hardware: All Multiple
: Medium enhancement
Target Milestone: Future
Assignee: Mikko Ylinen
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-03-25 10:01 UTC by Stanley Phoong
Modified: 2017-06-01 09:02 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stanley Phoong 2017-03-25 10:01:52 UTC
1. Feature Description:

Creating and introducing a new profile for end-user client devices to cater to more use-cases for refkit and iot world and to simplify the development for end-user devices.

2. Explanation:

Current implementation seems to be that customers are using gateway profiles to create end-user devices. I think that there should be another profile just for end-user devices as it serves a different use case and functional case to gateway profile.

Quote from wikipedia on definition of IoT gateway:

"An IoT Gateway provides the means to bridge the gap between devices in the field (factory floor, home, etc.), the Cloud, where data is collected, stored and manipulated by enterprise applications, and the user equipment (smart phones, tablets etc.). The IoT Gateway,[6][7] provides a communication link between the field and the Cloud and can also offer local processing and storage capabilities to provide offline services and if required real time control over the devices in the field."

Based on the definition of IoT gateway, a gateway is mainly a bridge to link devices to internet(cloud). By creating a new profile for end-user devices it would greatly help customers to clearly distinguish the differences of the function for gateway and end-user devices.

For example, the bluetooth speaker feature that was recently introduced, this feature should be integrated together with end-user profile rather than gateway profile in order to properly distinguish between the differences of gateway and end-user devices. 

In the near future, when more features and functionality would be introduced, 
this would help the customers understand and distinguish very clearly when designing their own end-user client device e.g remote control car, vending machine, bluetooth speakers, etc... which they would use the end-user profile and if they want to design an IoT gateway, they would use the gateway profile.

It is understandable that most of the time the gateway profile and the end-user client profile might sometimes share certain similarities however, there could be differences between the end-user client devices and the iot gateway. A simple example could be that the end-user client device would require graphics and UI for interaction while the IoT gateway would require multiple routing protocols for WiFi, BLE, 6LowPan, etc...
Comment 1 Mikko Ylinen 2017-06-01 09:01:36 UTC
After a chat with Stanley we agreed to move this to wontfix for now to indicate this is something we are not working on right now.