📑Description of Terms

📘 Introduction to the NUBISON IoT Cloud

Following is a glossary of terms used in the NUBISON IoT service.

🔖 Service

To use NUBISON IoT, you must first create a new service.

All information configured to manage the user's IoT service depends on the created service.

Multiple registrations are possible for a service, and data is not shared between services.

The service includes information regarding the device, timeline, location, service user, permission, and IoT extensions, which varies depending on the service.

Each service has its own Service URL and App Key; using this information, IoT services can be operated.

On the 📖 Service Home page, you can find a wealth of information about the service.

🔖 Product Model

The product model indicates the type of hardware that is configured to connect to the NUBISON IoT. Product model information is used to interpret the product's IoT data information by pre-defining the model's properties (product name, model name, communication protocol, product description information and functions performed, etc.).

Product models are categorized into two main types.

🔖 IoT Device

This refers to a type of product that supports direct Internet connectivity and the transmission of data to the NUBISON IoT server or the processing of requests.

🔖 Local Device

This refers to a type of product that supports the transmission of data or the processing of requests through an IoT device to the NUBISON IoT Server.

Detailed information about product models can be found on the 📖 Product Model Management page.

🔖 Device

This refers to each connected device within the NUBISON IoT.

🔖 Identification Key

This refers to a key that is used to identify a device within the NUBISON IoT Cloud.

🔖 Unit

This refers to a key that is used to identify a device within the NUBISON IoT Cloud.

🔖 Unit Number

This refers to a number that identifies a unit among NUBISON IoT Cloud-connected devices.

For instance, if the device is a PLC, the unit number can be entered as the same number as the PLC's memory address.

In addition, if the device is configured with the NUBISON IoT SDK, the data index corresponding to this unit can be set as the unit number in the data payload section transmitted by the device. The first item in this array is the unit number 0, and subsequent items can be set to increment by one.

🔖 Unit Type

This refers to the operating mode of this unit. Unit types are separated into two categories:

1. Inquiry

   A type in which the device generates data, stores the data, and can transmit it to the outside world.

2. Control

   A type in which the device receives external commands to execute specific actions or alter values.

When defining a unit type, it can be categorized as follows:

For example, a temperature sensor in the form of a transmitter that only transmits a value corresponds to an inquiry unit.

If an operating device lacks a status value and operates solely in response to a command, it is a control unit.

In addition, if the operating device has a status value, it falls under both inquiry and control units.