Terms commonly used in these products are explained as follows:
Term | Definitions | Description |
---|---|---|
Product | A collection of OneNET platform resources (including devices, rules, etc.). One product corresponds to a unique accessKey and product ID. There are multiple devices of the product which have the same characteristics. | |
Product ID | pid, a unique product identification code assigned by the platform when a product is created, which is used to identify a unique product as one of the parameters of authentication on device login. | |
accessKey | More secure access keys which are used as an implicit authentication parameter (indirect transmission) to access the platform. Access authentication is performed by participating in token calculation and transmission. | |
token | A more secure authentication parameter which is composed of multiple parameters and transmitted directly in the tunnel. | |
Device | It belongs to a certain product and is a real device mapping onto the platform, which is used to establish a connection with a real device through CONNECT messages and distinguished by device name. | |
Device ID | A platform-wide unique identification number of the device assigned by the platform. | |
Device key | A device’s unique secret key which is used for device connection and access to related services. Access authentication is performed by participating in token calculation and transmission. | |
Child device | A device that indirectly accesses the Internet by connecting to the Gateway. | |
Data stream | One of device properties, which may be a single data property, e.g. temperature = 10, or be a combination of data properties, e.g. coordinates = x: 10 y: 20. | |
Data stream template | A data collection property that all devices of the product are endowed with. For example, every air quality tester can report data such as "PH2.5" and "formaldehyde concentration". | |
Data point | Data that a device uploads to the data stream every time. | |
Device Image | A json description document assigned to each device on the platform. | |
Rule Engine | Support user-defined message forwarding rules, and flexibly interface with multiple VAS backends. |