The 2019/05/09 release of EnOS offers the following updates:
This section lists the new services and features in this release.
We added support for resource management so that you can request new resources or scale up existing resources from EnOS Console.
This is the initial release of this service. The initial release includes the following features:
- Requesting resource: request new resource based on your business needs.
- Scaling up resource: extend your capacity to accommodate the increasing business needs.
Availability: In this release, you can only manage the following resources from the EnOS Console:
- Stream analytics computing resources
- Time series database (TSDB)
For more information, see Resource Management.
We added support of data connection to the Azure BLOB database. The data connection configuration specifies the cloud region where the database sits in Azure, and the storage account and password to access the BLOB database. For more information, see Configuring an Azure BLOB data connection.
We added support for batch creation of devices and new asset service APIs.
Batch Registration of Devices¶
- We added support for batch registration of devices to improve the efficiency of device connection. You can import a template (in the
.xlsxformat) to register a maximum of 1000 devices in batch at one time. The template can be obtained or generated in the following methods:
- Download a blank template.
- Create a template based on an existing device and fill in the information of your device records. For more information, see Creating Devices in Batch.
Offline Message Integration¶
Initial release. EnOS provides a data integration channel for 3rd-party systems, users can use the channel to import historical device data from 3rd-party systems into EnOS. The data will be processed, stored, and analyzed with user-defined policies.
Asset service APIs¶
uploadAssetMeasurepoints: Enables non-device asset nodes to report measure point data to EnOS.
updateAsset: Updates asset information. Supports updating specified key-value pairs instead of fully update.
searchTrees: Get detailed asset tree information with asset tree tags.
searchNodePathByAssetId: Search nodes in the asset tree to which the specified asset is bound to.
getEvent: Gets detailed information of an event reported from a device. The event to query is specified by event ID.
searchEvent: Gets detailed information of events that match search conditions.
For more information, log into EnOS Console and select EnOS API > API Documents > Asset Service and EnOS API > API Documents > Connect Service.
Data Asset Management¶
We added a template for electric power calculation and supported processing offline stream data. Also, you can now process and store offline time series data integrated into EnOS.
Electric power calculation template: Initial release. This template calculates daily electric power based on the electric meter readings. The initial release includes the following functions:
- “Sum of delta” calculation method: Obtains the delta of electric meter readings in each time interval. Then sum up the deltas in all time intervals of the day to get the daily electric power.
- Daily electric power: Outputs the daily electric power.
- Detailed electric power: Optionally, outputs electric power of a given time interval.
For more information, see Electric Power Calculation Template.
Offline Message Analytics and Management¶
Initial release. Supports calculation and management of offline time series data integrated from 3rd-party systems through MQTT channels. The initial release includes the following functions:
- Stream analytics of offline data: The processing uses separate computing resources and therefore is metered and billed separately from real-time data.
- Storage of offline data based on policy: When the offline messages are integrated into EnOS and ingested based on the associated model, you can configure the storage policy for the data just as what you can do with the real-time ingested data. Currently, you can only configure the TSDB storage policy for data ingested through offline message integration.
For more information, see Creating a Stream Processing Job.
Adaptation to Extended Resources¶
Initial release. After scaling up your stream analytics resources or when starting new stream analytics jobs, you can pause and restart one or multiple running jobs to re-allocate resources for these jobs to optimize the resource usage.
For more information, see Monitoring the Stream Processing Job.
New Data Service APIs¶
getAssetsCurrentDayElectricPower: Obtains the total daily electric power produced or consumed by a device.
getAssetsElectricPowerData: Obtains the electric power production or consumption data of a device.
filterAssetsLatestData: Filters latest measure point data based on conditions.
For more information, log into EnOS Console and select EnOS API > API Document > Data Service.
This section lists the enhancements and changed behaviors of this release.
A preview release of the next-generation EnOS Edge. EnOS Edge now communicates with EnOS IoT Hub based on the EnOS standard MQTT protocol. To be compatible with the device connectivity and management standards of the latest release of EnOS, the following aspects of EnOS Edge are upgraded:
- Data ingestion
- Edge computing
- Breakpoint resumption
- Device Control
- Communication Debugging
- Data Resolution
- Web-based remote control in EnOS Console
In specifics, the following behaviors are changed:
The following features are added in EnOS Console:
- Viewing the current version, device key, and other basic information of an Edge.
- Adding an EnOS Edge to EnOS.
Data Reporting Method¶
|Before||In the previous release, the data reporting method that you specify applies to all edge devices. The data reporting methods, including reporting upon change (CHANGE), real-time reporting (REALTIME), and periodical reporting (TIMER) were specified in the Model configuration.|
|After||In this preview release, you can define upload types in Edge Gateway > Template. You can use different methods for templates under one model.|
|Before||In the previous release, you configure the script for calculating measure points in Model. The script applies to all Edge devices.|
|After||In the preview release, you can configure the script in Edge Gateway > Template from EnOS Console.. The script applies only to devices that uses the template to connect to the Edge device.|
Upgraded part of supported protocol to be compatible with the latest EnOS connection framework. For detailed list of what’s upgraded, see Protocol list for EnOS Edge. You can also access these protocols in Edge Gateway > Protocols from EnOS Console.
|Before||All devices connected through the target protocol would be affected.|
|After||You can select the devices to upgrade protocol for.|
In this preview release, you can no longer configure protocols in Edge Gateway > Template. Instead, you can now select a model and configure measure points. When you connect new devices to Edge, you must select the corresponding protocol type and protocol, associating one device with only one protocol.
|Before||The device template is associated with a protocol.|
|After||The device template is associated with the model and the point table (point.csv file) of a protocol. You can map a measure point to both the data collection point and the control point at the same time. We also improved the way you edit the point.cvs file.|