...
LON devices are provisioned by the SmartServer IoT.
...
Event-driven updates occur when a datapoint is updated on an edge device and then the update is automatically sent to the SmartServer. For LON devices, these are peer-to-peer connections with the source on an edge device going to the SmartServer. For BACnet devices that support COV, these are COV connections from a COV datapoint to the SmartServer.
Event-driven updates are not supported for Modbus devices.
...
Independent Management Mode
(IMM)
...
LON devices are provisioned by an external tool based on the IzoT Net Server.
...
| Term | Definition | ||
|---|---|---|---|
| Broker | A broker in MQTT receives the MQTT messages and sends each message to the appropriate subscribed client. | ||
| Channel | The IAP groups topics and message handling attributes into directional communication channels. See Channel in the IAP/MQ Topic Syntax table. | ||
| CMS | Central Management System, which includes the CMS web pages as well as the CMS REST and WebSocket APIs. | ||
| Commission | Configures a device to a specific network (same as provision). This process is different for each protocol. For LON devices, provisioning assigns a logical domain/subnet/node ids, configures peer-to-peer connections, and optionally sets the original value. For BACnet and Modbus, provisioning verifies that the SmartServer can read one the datapoints (usually the first in the XIF file). | ||
| Context | Contexts are used to organize devices within the SmartServer IoT. Context types include world, region, campus, building, floor, room, and area. Contexts are created and viewed using the SmartServer CMS Planning widget. The Planning widget allows you to create a hierarchical representation of where devices appear at a site (e.g., factory or store). This representation allows you to look at a subset of devices based on location instead of seeing all devices. | ||
| Customer | An organization or person that licenses the SmartServer IoT. | ||
| Device Management Mode (DMM) | LON devices are provisioned by the SmartServer IoT. | ||
| Edge Server | Manages a segment.The SmartServer is an Edge Server. | ||
| Event-driven updates (Datapoint Properties) | Event-driven updates occur when a datapoint is updated on an edge device and then the update is automatically sent to the SmartServer. For LON devices, these are peer-to-peer connections with the source on an edge device going to the SmartServer. For BACnet devices that support COV, these are COV connections from a COV datapoint to the SmartServer. Event-driven updates are not supported for Modbus devices. | ||
| Geozone | Geographic area defined with the CMS; may contain embedded geozones. | ||
| Handle | Handles are unique identifiers of addressable items used with IAP topics. For more information, see Handle in the IAP/MQ Topic Syntax table, and Handle Allocation. | ||
| IoT Access Protocol (IAP) | |||
Independent Management Mode | LON devices are provisioned by an external tool based on the IzoT Net Server. | ||
| Long Range Wide Area Network (LoRaWAN) | Long Range Wide Area Network (LoRaWAN) used for low transmission frequency, low energy consumption devices spread over wide area (10+ km in rural areas, ~2 km in urban areas). | ||
| LonWorks Network Server (LNS) | LonWorks Network Services (LNS) is a control network operating system for Windows-based computers supporting both client/server and stand-alone applications. It allows a computer to provide a broad range of services over LonWorks networks. It can be used to manage and control LON devices. | ||
| LoRaWAN Network Server (LNS) | LoRaWAN Network Server (LNS) manages a network of Low-Power Wide Area Network (LPWAN) devices using the LoRaWAN protocol. | ||
| Peer-to-Peer Connections | Peer-to-peer connections exist between LON devices only. If devices are on the same LON channel and you remove the SmartServer then source datapoints updates will continue to be sent to the destination device. | ||
| Point-to-Point Connections | This is a connection between datapoints, but with the SmartServer in the middle. In this case, the source datapoint value has to be sent to the SmartServer by polling or event-driven updates, and if the source datapoint value changes, then the SmartServer will send the update to the destination datapoints. If you remove the SmartServer, then the connections will no longer work. | ||
| Provision | Configure a device to a specific network (same as Commission). This process is different for each protocol. For LON devices, provisioning assigns a logical domain/subnet/node ids, configures peer-to-peer connections and optionally sets the original value. For BACnet and Modbus, provisioning just makes sure that the SmartServer can read one the datapoints (usually the first in the XIF file). | ||
| Public Key Infrastructure (PKI) | The most distinct feature of Public Key Infrastructure (PKI) is that it uses a pair of keys to achieve the underlying security service. The key pair comprises of private key and public key | ||
| Resource | For REST, a resource is an object with a type, associated data, relationships to other resources, and a set of methods that operate on it. Essentially a resource is every thing or entity that can be identified, named, addressed, or handled, in any way whatsoever, on the web. For MQTT, a topic is the equivalent of a REST resource. | ||
| Resource Type | IAP supports a variety of resource types such as devices, groups, schedules, etc. See Resource_Type in the IAP/MQ Topic Syntax table. | ||
| SID | See Segment Identifier. | ||
| Segment | A collection of devices that can be addressed with a common segment ID. | ||
| Segment Identifier | The SID is the Segment Identifier, which is the logical address of the device that controls a segment. In IAP, that device is either an edge server, or, an IAP-native edge device that is the only device on that segment. Such an edge device can still implement other object types, such as alarms or connections for itself, and uses the standard topic layout. For more information, see SID in the Syntax table. | ||
| Scalar Datapoints | Scalar datapoints represent a single field where the value is an integer or float as shown in the Datapoints widget example below.
| ||
| SmartServer Platform | The SmartServer platform includes all of the built-in functions within the SmartServer except the CMS web pages, which can be hosted on the SmartServer or on a cloud server. | ||
| Structured Datapoints | Structured datapoints represent more than one value where multiple fields are separated by a comma as shown in the Datapoints widget example below.
| ||
| Topic | In MQTT, a topic refers to a string that the broker uses to filter messages for each connected client. An MQTT client can publish and subscribe to a topic. A topic in MQTT is the equivalent of a REST resource. | ||
| User | A person associated with a customer account with access to one or more geozones associated with one or more SmartServer IoT licenses. | Unique Identifier (UID) | Unique identifier for the device.associated with one or more SmartServer IoT licenses. |
| Unique Identifier (UID) | Unique identifier for the device. Each device must have a unique UID. The UID format for each protocol is different. Examples:
|
