Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
platform:iot_devices [2019/02/27 15:19]
tmuvee
platform:iot_devices [2019/02/27 15:28]
tmuvee
Line 23: Line 23:
 ThingseeGATEWAY firmware is not published as an open source or as an SDK.  ThingseeGATEWAY firmware is not published as an open source or as an SDK. 
  
-### Initiating Gateway Connections+===== Initiating Gateway Connections ​=====
  
-ThingseeGATEWAY certificates are deployed by using Thingsee Operations Certificate API (Thingsee Master Inventory) ​which will have two main functions+ThingseeGATEWAY certificates are deployed by using the Thingsee Operations Certificate API which will have two main functions:
  
-a gateway can request certificate based on its identification parameters (from manufacturing) +  * a gateway can request ​certificate based on its identification parameters (from manufacturing) 
-a gateway confirms a received certificate and connects to an assigned Thingsee Operations ​Stack+  ​* ​a gateway confirms a received certificate and connects to an assigned Thingsee Operations ​Profile
  
-This is the initial procedure for all the gateways as this is the way how gateways are allocated to different Thingsee Operations ​stacks. When the gateway requests a certificate,​ it will also receive Thingsee Operation ​stack URL and other information required to make a connection to a specific ​stack.+This is the initial procedure for all the gateways as it is the way how gateways are allocated to different Thingsee Operations ​Profiles. When the gateway requests a certificate,​ it will also receive Thingsee Operation ​Profile data and other information required to make a connection to a specific ​profile.
  
-The generated certificate is stored to AWS IoT so that the MQTT(S) communication is authenticated between the specific Thingsee Operations stack and the gateways. The same certificate or its status must be also stored to the master inventoryamong with the other inventory dataso that it status can be revoked or renewed if needed.+The generated certificate is stored to AWS IoT so that the MQTT(S) communication is authenticated between the specific Thingsee Operations stack and the gateways. The same certificate or its status must also be stored to the master inventory among with the other inventory data so that its status can be revoked or renewed if needed.
  
-### SIM activation+===== SIM activation ​=====
  
-A thing deployment and activation are always specific to actual product as it requires communication through the customer application and services layers. There are some cases where activation is done during manufacturing process, but typically, at least with products having cellular connectivity, ​there is a cost optimisation requirement to keep SIM subscriptions deactivated until the device is actually ​taken in use.+A thing deployment and activation are tailored based on the actual product as it requires communication through the customer application and services layers. There are some cases where activation is done during ​the manufacturing process, but typically, at least with products having cellular connectivity,​ cost optimization is achieved by keeping ​SIM subscriptions deactivated until the device is taken in use.
  
-One of the methods ​for activation is to use QR code to scan the device information and then activate that specific device through ​Field Operations Application. The activation process may take some minutes depending on what are the parameters and subprocesses ​that needs to be done in the Thingsee Operations side. +One method ​for activation is to use QR code to scan the device information and then activate that specific device through ​the Thingsee ToolBox Mobile application. The activation process may take some minutes depending on what the parameters ​are, and what subprocesses ​need to be done in the Thingsee Operations side. 
  
-For example, activating SIM subscription to a specific region with specific subscription parameters typically takes 5-10 minutes before data and voice call are operational. +For example, activating SIM subscription to a specific region with specific subscription parameters typically takes 5-10 minutes before ​data and voice call are operational.
- +
-</​markdown>​+