Executive Summary
Climate change and global warming are serious concerns across the globe.
These issues took center stage as high-level representatives from more than 190 countries met in Paris at the end of 2015 to work toward a more sustainable future for the planet. Key focus areas were energy efficiency and how to transition to cleaner energy sources.
Energy initiatives, such as those started in Paris, are giving rise to a new strategic industry, called smart energy, which will bring significant economic and social benefits. The industry will use new technologies to meet national policies that are becoming more aggressive with respect to reducing energy consumption and using energy more efficiently.
The smart energy industry is expected to advance energy conservation through the use of energy efficiency management systems (EEMS), employing Internet of Things (IoT) technologies for data acquisition and processing technologies. This paper discusses an end-to-end energy management solution, covering energy industry connectivity and protocol support, a front-end energy gateway hardware and software framework, a cloud-based gateway management system, and integration support of customer energy management systems. The anchor point of the system is the energy gateway design, based on the Intel® Quark™ System- on-Chip (SoC), covering both the hardware specification and software stacks. The design and specification are founded on a comprehensive Intel study of energy management requirements.
IoT-based energy data acquisition and processing are anchor technologies for enabling significantly improved energy management.
Energy Management Framework Greatly Reduces Effort for Solution Providers
Intel’s end-to-end framework provides the hardware and software elements needed
to connect energy system devices to the cloud, remotely manage them, and identify
ways to dramatically reduce energy consumption.
Business Imperatives
The energy management market is expected to provide exciting new business opportunities for original equipment manufacturers (OEMs), original design manufacturers (ODMs), and systems integrators (SIs). According to the China Strategic Alliance of Smart Energy Industrial Technology Innovation, the market is forecasted to grow quickly from USD 7 billion in 2013 to 30 billion in 2020, which corresponds to a compound annual growth rate (CAGR) of 23 percent.
To achieve this fast growth in the energy management industry, solution providers will need to address today’s challenges, which include:
• Complex connectivity
The lack of standards makes it more difficult to connect industrial devices to a common, IP-based network.
• Large investment
Significant capital expenditures (CapEx) are required for connectivity, storage, and servers.
• High operating costs
Project-specific solutions, developed to address different requirements, often need separate support structures, which add cost.
• Duplication of effort
Independent energy systems are typically inefficient because they perform the same tasks instead of centralizing them.
• Shortage of IT experience
Smart energy is based on information technology (IT), which is a relatively new skill set for the energy industry.
IoT solutions from Intel are available today to help OEMs, ODMs, and SIs develop EEMS solutions that overcome these hurdles.
Solution Overview
An EEMS requires a sophisticated mix of hardware, software, and access networks to establish end-to-end communications between energy devices in the field and energy consumers. In short, the systems shown in Figure 1 quickly collect and analyze data using cloud infrastructure, making it possible for consumers to discover new ways to reduce energy consumption.
Intel is in a unique position to provide this end-to-end solution, from an energy management gateway (that connects to energy and sensors) to the cloud-side device management solution that interfaces with customer systems. Intel supplies management capabilities for devices, data, accounts, and security. To help integrate gateways and cloud-side applications, Intel offers the software development kits (SDKs) and APIs needed to efficiently design a complete EEMS.
Table of Contents
Executive Summary . . . 1
Business Imperatives . . . 2
Solution Overview . . . 2
Use Cases . . . 3
Main Solution Benefits . . . 3
Solution Architecture . . . 4
Gateway Components . . . 4
Cloud Foundational Services . . . 4
Intel Energy Management Gateway Overview . . . 5
Gateway Requirements . . . 5
Main Gateway Components . . . . 5
Gateway Hardware Overview . . . 5
Hardware Features . . . 6
Gateway Software Stack Overview . . . 7
Software Stack Basic Components . . . 7
Application Frameworks . . . 7
Security . . . 7
Wind River IDP* Features . . . 7
Connectivity . . . 8
Manageability . . . 8
Security . . . 8
Cloud-Side Software Framework . 8 Cloud Management Overview . . 8
User Roles and Authentication . 8 Cloud-API-Driven Design . . . 9
Performance Consideration for Remote Gateway Management . 9 Standard Console and SDKs for Integration . . . 10
Cloud Usage Model . . . 10
Summary . . . 10
Intel Energy
Management Gateway Intel Device Management Solution
Building Energy Management System (EMS)
Power Panel Management System
Heating EMS Device
Management
Gateway Gateway
Gateway Data
Management
Meta Data Management
Account and Security
Charging Station EMS
Other Systems Distributed Energy Monitoring System Customer Systems
Cloud API TCP/IP
Figure 1. The solution connects energy sensors and systems to energy consumers via the cloud
Use Cases
An IoT-based EEMS can be used to control various types of systems, including heating, ventilation, and air conditioning (HVAC); power panel management; distributed energy monitoring; and charging stations.
These energy systems typically require energy data processing and handling capabilities such as those shown in Figure 2. Energy management gateways are primarily involved in energy data collection, and the other capabilities are mainly handled by the back-end energy management system.
In a typical energy management application, there are usually a variety of data sources, including but not limited to:
• Various RS485 meters, such as water, point, gas, oil, and heat
• Network-accessible database
• TCP Modbus equipment
• OPC devices
The programmable gateway software framework provides sensor plugin features to support multiple data sources. This method scales well, and is flexible and real-time.
The gateway can support multiple data uploading protocols for different projects using a mix of network plugins.
The programmable gateway application framework enables data transfer from sensor plugins to network plugins via inter-process communication instead of a database, thus incurring much less latency.
Typically, energy management gateways are installed in multiple buildings, posing a challenge for gateway management. In this scenario, the gateway remote management capability helps by providing the following features:
• Gateway online status monitoring
• Remote configuration management
• Remote application deployment and management
• System state monitoring
• System upgrade support - Wind River Intelligent Device
Platform* (IDP) has built-in support for TR-069 and OMA DM management protocols. Customers can also develop customized device management functionality based on the programmable gateway software framework.
Security is another important requirement for energy gateways, including:
• Gateway device security
• Data storage security
• Data transmission security - The Intel Quark SoC supports
secure boot. Wind River IDP provides application integrity checking that further improves device security. Additionally, Wind River Linux* and IDP support storage encryption to provide data storage security. IDP also supports industry standard encryption standards, such as SSL/TLS, providing data transmission security.
Main Solution Benefits
OEMs, ODMs, and SIs addressing the challenges facing the smart energy industry can do so more easily with an IoT-based EEMS and the Intel energy management gateway.
The gateway reduces connecting complexity by integrating a flexible I/O carrier board that can be designed to communicate with any energy device via its native communication protocol.
The Intel solution provides the software needed to communicate with the cloud, which allows customers to use a public cloud instead of making a large investment for their own connectivity, storage, and servers.
The high operating costs associated with project-specific solutions can be dramatically reduced with this cloud- based EEMS architecture, which allows computing resources and support structures to be shared more easily among projects and systems.
Similarly, a cloud-based EEMS helps minimize duplication of effort because common tasks performed by independent energy systems can be centralized in the cloud.
Energy Target Energy Benchmark
Energy Efficiency Analysis
Energy Data Analysis
Energy Data Statistics
Energy Data Storage
Energy Data Acquisition Figure 2. An EEMS
supports various energy data layers
Lastly, the Intel solution provides the software needed to connect to the cloud, thereby reducing the complexity of customers hosting and managing their own IoT infrastructure, which is a big help to customers with a shortage of IT experience.
Solution Architecture Figure 3 shows the high-level components of the end-to-end EEMS system. It identifies the core components supplied by Intel, components supplied by Intel that should be customized by solution developers, and customer components.
The whole solution adopts a layered design where each layer can be individually managed, scaled, and maintained. The gateway abstraction layer is scalable to support a large number of gateways, and uses MQTT and HTTP to enable secure communications with the gateways.
The service abstraction layer is a RESTful interface that provides a list of APIs for developers to use to integrate their systems. To ease integration, Intel provides a JAVA development SDK and a standard web user interface (UI) for the administration console.
Gateway Components
The gateway system bus on the Intel energy management gateway handles remote procedure calls (RPCs) and other communications between the modules. It maintains a registry, allowing components to discover the calls and capabilities provided by other components.
Intel also offers the cloud connectivity module and device management agent module to connect the gateway to the cloud in a secured fashion and at the same time, enable cloud-side management functionalities to be executed on the gateway.
Certain components running on the gateway should be customized by solution developers:
• System level function – exposes system level functions, such as system reboot, firmware update, system log export, etc.
• Gateway application management – exposes the different application configurations, and whether the configurations can be updated, remotely updated, started, or stopped.
Legacy applications can be wrapped and managed by the remote server.
To ease the integration efforts of gateway applications, the gateway framework agent is open sourced.
Cloud Foundational Services
The solution provides many foundational services for energy cloud systems, including those listed in Table 1.
Figure 3. An end-to-end EEMS solution can be customized for different energy systems Device
Management Agent
Gateway
Abstraction Layer Service
Abstraction Layer Gateway
Application Management
Project Metadata Management
Data Management
System
Cloud Development Data SDK
Management Platform
Device Data Management Analytics System
Level Function
Gateway System Bus
Web System Operations Platform
Data Visualization
Energy Data Analytics Other Data
Analytics Wind River IDP* (preferred) or Yocto*-Based OS
Intel Energy Management Gateway Cloud
Energy Systems
Data
Processing Data
MQTT Channel
MQTT Broker Control
Core components provided by Intel
Components provided by Intel, customized by customers External components from customers
Data MQTT Module Protocol
Plugins
Modbus*
Data Acquisition
Module
Table 1. Foundational services of the energy cloud system
CAPABILITIES FEATURES
Gateway remote management
Latency-tolerant gateway management
Gateway authentication Large scale test and validation
Security communication integration
Project metadata management
Flexible asset management Energy metadata
abstraction
Web-front interfaces
Platform API abstraction
Minimal and stable API definitions
Programming language agonistic interface RESTful APIs and SDKs Data
foundation service
Data storage and service Gateway data analytics (diagnostics)
Rule-based alerts
Intel Energy Management Gateway Overview
The Intel energy management gateway hardware design uses a core board, which is a computer-on-module (COM) that is seated on an I/O carrier board with application-specific I/O interfaces.
Intel provides design details for both boards to reduce the development effort for OEMs and ODMs interested in offering their own gateway.
The software design features a programmable gateway software framework, which eases the
development of gateway applications, including the integration of energy meters, application management, gateway maintenance, etc. Wind River IDP is the recommended middleware software for the energy management gateway. IDP enhances the connectivity, manageability, and security functionality of the gateway platform, which further simplifies energy gateway management and software development.
Gateway Requirements
Energy management gateway devices are generally installed near energy meters and sensors in the field.
Energy consumption data is read from meters via standard buses, such as RS485, for the physical layer, and communication protocols, such as Modbus* and DL/T 645, for the application layer. After protocol conversion, energy consumption data is sent to servers via LAN, Wi-Fi, or occasionally 2G/3G networks. ZigBee*
wireless protocol support is optional as it is used in limited scenarios. A USB host port is required to provide convenient data exporting and local configuring support. Meanwhile, in order to facilitate the development and debugging of the system and applications, one debug console port should be provided. Reset and recovery buttons are required for system reset and recovery.
The gateway software stacks simplify the development, integration, and deployment of IoT gateways. Customers may have various requirements for gateway functions, based on factors such as their technical capabilities, business models, and the scope of the existing solutions they provide.
It is important for the software stack to be adequately general to meet the core requirements of most customers, yet be sufficiently flexible to allow customization and integration. Such software requirements are applicable to different energy management vertical markets, such as manufacturing, environmental, and smart building.
Intel’s energy gateway solution provides comprehensive software stacks that include firmware, operating system, middleware, and energy- specific application support. The software architecture is designed with an end-to-end system perspective, focusing on energy sensor integration, energy data delivery and aggregation, device management, and platform management. Particularly, the following aspects are supported and optimized:
• Support for typical energy meter bus standards (RS485, Modbus)
• Small burst data optimization
• Platform compatibility and extendibility
• Device management API abstraction
• Sensor plugins
• System scalability
• System and data security Main Gateway Components The recommended Intel Quark SoC- Based Energy Management Gateway solution includes the following components:
• Core module with the Intel Quark SoC
• I/O carrier board provided by a partner
• Intel® IoT Gateway software stack with Wind River Linux and IDP
• Programmable gateway software framework
• Sensor plugin, the network program, and applications provided by a third- party partner
Figure 4 shows the layered view of these components.
Third-Party Applications Programmable Gateway Software Framework and Customized Plugins
Intel® IoT Gateway Software Stack Core Module and I/O Carrier Board
Intel® Quark™ SoC
Figure 4. The main components of the Intel energy management gateway
Gateway Hardware Overview In the reference design, the core module and I/O board are connected together by a pair of 2x40 pin connectors. The core board is a modular, bootable, Intel Quark SoC-based computer block, and its size is limited to 57mm x 42mm.
Table 2 describes the I/O function groups routed out by the two 40-pin connectors.
The I/O carrier board hosts all the system I/Os. All I/O device functions supported by the core module can be demonstrated and validated by the I/O carrier board. The design is an open reference design, which provides OrCAD* format design and Allegro* PCB layout design. These design documents help reduce design cost and speed up time-to-market.
Table 3. Intel energy management gateway feature specifications
CATEGORY FUNCTION DESCRIPTION REQUIRED
CPU Processor Intel® Quark™ SoC X1000, 400 MHz Yes
Memory RAM DDR3 800/1066MT/s, 256 MB, Memory down Yes
ROM On board 64Mb SPI flash Yes
Wireless Communication
WLAN 802.11 b/g/n wireless module, external antenna, Support 1x Half PCI-e wireless card Optional
3G Module 1x PCI-E 3G with SIM slot Yes
ZigBee* Low power ZigBee* module with an external antenna Optional
GRPS 1x external antenna Yes
I/O Interface
Ethernet 2x 10/100-BaseT(RJ45) Yes
USB 1x USB2.0 Host (Type A) Yes
RS485/232 Port 2x RS232/RS485 with isolation protection Yes
Console Port 1x RS232 (UART1) Yes
RTC Supported Yes
I2C EEPROM for MAC address Yes
Buttons Reset and recovery buttons Yes
LED Indicator LAN, 2G/3G PWR, RUN Yes
ZigBee*, ALARM Optional
Storage SD Card 2 GB SD card Yes
Software OS Linux*, Wind River Linux preferred Yes
Middleware Wind River IDP* preferred Yes
Power Input Voltage 9-36V DC Yes
Misc. Mounting DIN Rail Yes
Cooling Mode Fanless, heat sink Yes
Environmental and Certification
Temperature Operating: -20°C ~ +50°C, Storage: -40°C ~ +60°C Yes
Relative Humidity 10–95%@35°C (non-condensing) Yes
EMC & Safety CCC Yes
Table 2. Key hardware interface on the core module INTERFACE DESCRIPTION
Ethernet 2x 10 and 100 Mbps data transfer rates with RMII interface to communicate with an external Fast Ethernet PHY
PCI-E 2x PCI Express* root ports, each supporting the PCI-e Base Specification Rev 2.0 at a maximum of 2.5GT/s data transfer rates
USB 2x USB 2.0 host, 1x USB 2.0 device interface
Storage 1x port configurable as an SD, SDIO, or eMMC interface, Micro SD slot I2C 1x I2C interface, supports standard (100 Kbit/s) and fast (400 Kbit/s) data rates
UART 2x UART interfaces, supported baud rates from 300 to 2764800 (UART1 for debugging console port) JTAG 1x JTAG interface for OpenOCD
SPI 2x SPI interface for peripheral devices, 1x Legacy SPI for BIOS boot GPIOs 10x general-purpose I/Os
Hardware Features
Table 3 summarizes the typical hardware feature specification and minimal requirements needed to satisfy the common use cases and functionalities of an Intel Quark SoC-based energy management gateway.
• Simple gateway maintenance and application management
• An application framework to simplify application development and integration
Additionally, with the help of the gateway management framework, energy-specific application framework can be included to ease energy edge application development and integration.
Application Frameworks
The energy application framework makes the gateway programmable and provides actuator functionality for energy applications, such as application management, energy message communication protocols, and energy sensor data collection and pre-processing.
The application framework enables energy application management on edge devices, including application configuration management, messaging system configuration, message and data encapsulation, message delivery, and application status monitoring. This will further reduce the engineering effort for solution operators, as remote device and application management can be easily conducted. Furthermore, a sensor protocol plugin framework can be used to support energy industry standard protocols, particularly Modbus and DL/T645 used by smart meters.
The application framework greatly simplifies edge gateway application development: sensor data is read using the provided sensor APIs; data can be submitted to the cloud with configurable destination paths and message encoding options, which are specified in application configuration and supported by the framework; and application status monitoring and upgrade capability are available by default.
Security
Security support is one of the key requirements for the energy gateway, covering all software layers and components, including device authorization and authentication, OS runtime, application attestation, communication security, data security, etc. These security requirements can be categorized into high-level security groups addressing the gateway platform, communications, data, and cloud services.
Gateway platform security protects the edge gateway system and its application from external tampering and information leaks. Intel is in a unique position to provide an exceptionally secure system with security technology covering the CPU, SoC, firmware, OS, and application framework. The Wind River IDP platform integrates trusted boot and a secured OS that help ensure gateway platform security.
The application framework takes advantage of platform security features, together with AES encryption and SSL, to secure data communications.
Wind River IDP Features
The Wind River IDP is based on Wind River’s industry-leading operating systems, which are standards- compliant and fully tested, as well as supported by Wind River development tools. The platform, shown in Figure 5, provides device security, smart connectivity, rich network options, and device management.
IDP is integrated into the Intel IoT Gateway, a family of platforms that enables companies to seamlessly connect industrial devices and other systems into a system of systems. The Intel IoT Gateway enables customers to securely aggregate, share, and filter data for analysis. It helps ensure that Gateway Software Stack Overview
A high-level architectural view of a typical energy management, end-to- end solution is shown in Figure 3 on page 4. The gateway connects to energy sensors across industry- standard communication protocols (e.g., Modbus), allowing data to be accessed by applications running on the gateway. The gateway also provides management and application middleware to enable remote-device and application management. These features are exposed securely via the gateway API.
Software Stack Basic Components The main components and functionality of the energy gateway can be categorized into three layers: generic operating system (OS) and driver layer, gateway management framework, and energy- specific application framework.
For critical applications requiring system stability and customer support, a commercial OS such as Wind River Linux is recommended. The gateway management framework can improve the management, connectivity, and security of the edge solution. It integrates technologies and protocols for networking, embedded control, enterprise-grade security, and easy manageability, thus delivering a platform on which application-specific software can run. Specifically, the framework provides generic capabilities in the following areas:
• Connectivity down to sensors and existing controllers embedded in the system, such as enabling BLE, ZigBee, and the driver framework
• Connectivity up to the cloud and enterprises, including communication libraries and messaging support
• Security features such as data encryption, application attestation, and software lockdown to protect the gateway from attack
federated data generated by devices and systems can travel securely and safely from the edge to the cloud and back—without replacing the existing infrastructure.
Intel IoT Gateways are key building blocks for developers connecting legacy energy devices and other systems to IoT. They integrate technologies and protocols for networking, embedded control, enterprise-grade security, and easy manageability on which application- specific software can run. Connectivity, manageability, and security are core IoT building blocks that help reduce time-to-market, complexity, and risk for device manufacturers. Wind River IDP natively delivers all three types of building blocks.
Connectivity
Pre-integrated smart and connected capabilities enable rich network options that can save development time and costs. Validated and flexible firmware provides an extensive set of
connectivity choices, including broad modem support and PAN, LAN, and WAN network access.
Manageability
Long-term secure remote
manageability simplifies deployment, maintenance, and management of remote devices.
Security
Features, from a hardware root of trust to boot and software loading, are available for IoT software developers to protect critical data throughout the device’s lifecycle. With secure image, data, and management support, devices and data are protected from boot to operations and management.
Customizable secure remote management ensures end device integrity via secure boot, supports encrypted communication between devices and a cloud-based
management console, and limits exposure of untrusted applications through device resource management.
Cloud Side Software Framework To further facilitate and ease management tasks, a cloud management layer is provided for gateway control, metadata management, energy application management, and data storage. With this cloud layer, solution developers can simply call a number of RESTful APIs to conduct sensor data queries, gateway control, and application configurations.
Cloud Management Overview Operating a large number of gateway devices can be a time-consuming and error-prone task, helped by a centralized cloud platform that automates management tasks. In the cloud, since the device remote control functionality works with gateways remotely, special consideration should be given to latency-sensitive operations, scalable batch operations, seamless device authentication, and secure messaging with MQTTs.
With a large number of gateways, configuration and asset management are critical. A cloud platform can provide flexible asset management and energy metadata abstraction, and consequently, ensure data consistency.
Table 4 lists the major APIs of the cloud service.
User Roles and Authentication The cloud management platform defines a number of use roles.
System administrators at the cloud service provider are responsible for project creation and project admin management.
A project is the management domain designed for one customer. All
gateways, metadata, and sensor data of that customer will be managed in this domain. A project administrator owns all the rights to the project-related operations.
Figure 5. Wind River IDP* software stack ZigBee*
Open JDK Lua VM SQLite OSGi
Secure Updates
TCG Standards
Integrity Monitoring Signed Software
Trusted Secure Boot
Application Signing Tool
Wind River Integrated Development Environment Tools
WIND RIVER OPERATING ENVIRONMENTS SECURITY
API
TOOLS
MANAGEMENT CONNECTIVITY
Role-Based Access Control Device Authentication
OMA DM, TR-069 Web Interface
Bluetooth* WWAN VPN MQTT Cloud
Connector
An access control list (ACL) designed for machine-to-machine (M2M) system integration is used to control user access. The project administrator can control the access rights of users individually, for example, which groups of APIs they can access, which subset of gateways they can control, or whether they can query sensor data.
All users can access the cloud platform via their user name and password, or public/private key pair. All access to the cloud management system must present a valid authentication token. A token is obtained by user logins or API logins, has a limited lifetime, and is bound to user/API locations and permissions. All API calls should present this token to allow the backend to authenticate the user. Role descriptions are provided in Table 5.
Cloud-API-Driven Design
One key principle of the cloud system design is to maintain a simple core, and keep it stable and reliable. The core focuses on fundamental features and
data representations, expressed in a list of APIs. The APIs sufficiently expose the capability of the core, based on digested customer requirements.
In other words, the API provides clean separation between platform core functionality and extensions. The core API can be further extended by SDKs, or used directly by partners.
The APIs are designed around the following principles:
• Provide a minimal, stable, easy-to- maintain layer to expose generic functionalities.
• Push complicated extensions to the SDK layer whenever possible.
• Guarantee flexibility, compatibility, and language-independent integration using JSON input and output.
• Ensure there is no dependency on transmission protocol/system.
• Simplify security and access control.
• Pass verifications from partners in the field.
Performance Consideration for Remote Gateway Management It is important to take the performance requirements into account during API system design and implementation.
For cloud-side management and operation, some APIs may take a non- deterministic amount of time (as much as a few seconds) to complete. Typical examples are device control APIs that create network and execution latencies, and data export APIs that require a significant amount of time to create large files for transmission.
Additionally, the API system provides batch operations for high throughput tasks, where a customer can manage a large number of gateways at the same time. In these cases, parallelization can greatly improve system throughput.
To support this, the cloud API layer provides an asynchronous API, also called big-stage API, to increase system concurrency and efficiency.
The first API call returns a query handle and timeout value. A second API is called to obtain the results after the timeout value.
Table 4. Major APIs of the cloud service
Table 5. Role descriptions Gateway Control
• Gateway configuration, system command execution, and file transfer
• Gateway update, reboot, and diagnosis
• Application management: install, start, and stop Accounts and
Authentications
• User management: add, update, and query
• Account authentications with password and keys
• Key and authentication management Project
Management
• Project metadata management with access control
• Query information in a project by entity type (e.g., group) Project Entities
Management
• Gateway metadata management
• Data point metadata management
• Group metadata management and nesting
Data Service
• Raw data query and export
• Stats, alarm data query and export
• Data-based triggers and alarms Platform
Monitoring • Platform log query and export
USER TYPE ROLE DESCRIPTIONS
System admin Super user, read/write to all data. Key functions are: create projects, add project admin accounts, and access platform logs.
Project admin The main operator of the project management: maintain project information and associated metadata, device control, and query and export data and events.
ACL user Controlled and limited access right. For example, read the metadata from project, and access statistics, raw data, and alert/event logs.
Standard Console and SDKs for Integration
To demonstrate the capabilities and typical usage cases of the cloud system, a standard web administrate console is provided for cloud service providers and customers.
Customers with a requirement to integrate with their existing systems can leverage the cloud API directly. In addition to the API, which is optimized to provide fundamental and core functionalities for the backend service, customers can integrate with the service-side SDK to take advantage of more sophisticated APIs, utilities, and programming language support.
The key benefits and functions of the SDK include:
• Extending the scope of APIs: for example, combinations of APIs provide new functions, conversions of generic API entity to actual entities, and utility functions that are not essential to the API (e.g., key-pair generation, import/export)
• Wrapping the RESTful interface to language binding functions (Java*
classes)
• Absorbing and implementing dynamic customer requirements
• Providing a command base tool for platform management
• Directing API calls with parameters and executing interactive tasks
Cloud Usage Model
The cloud service is currently offered as a public service model. Intel releases the solution to selected cloud service providers (CSPs), who will operate and support the service. The CSPs are the platform administrators. On-premise deployment is available, but with a different service model.
Platform administrators access the web console to create a project and project admin account. Projects enable customers to manage their projects, gateways, and export data.
As project administrators, customers can manage their own projects via the web console or through APIs on their own systems. They can also log in to the web console to configure and provision gateways, and create metadata (asset details) for their gateways. Gateways are deployed at customer sites, and they connect to the cloud system.
Summary
Intel is working closely with ecosystem partners to explore the opportunities in the smart energy industry, particularly with respect to energy efficiency management systems. The Intel Quark SoC-based energy management gateway solution satisfies the requirements Intel collected from engagements with a number of local and global partners that are focusing on the energy management market and covering market segments, including environmental, manufacturing,
and smart buildings. It is intended to meet the core hardware and software requirements of energy management projects.
The Intel Quark SoC-based energy management gateway simplifies application development for data collection and transmission. In addition to built-in management protocols, the software framework enables customized device management development. With the Intel Quark SoC and IDP security features, the complexity in securing an end-to-end gateway solution is greatly reduced. All of these capabilities help make building an energy management gateway solution based on the Intel Quark SoC even more efficient and cost effective.
To further facilitate and ease energy system management tasks, a cloud management layer is provided to remotely manage and control gateways, including metadata, energy applications, and data storage. With this cloud layer, customers can simply call a number of RESTful APIs to conduct sensor data queries, gateway control, and application configuration.
The cloud site service is designed to be scalable, reliable, and efficient.
In addition, customers can use the standard web console and an SDK to ease system integration and increase operational efficiency.
For more information about Intel® solutions for the energy industry, visit intel.com/energy.
Intel technologies’ features and benefits depend on system configuration and may require enabled hardware, software or service activation. Performance varies depending on system configuration. No computer system can be absolutely secure. Check with your system manufacturer or retailer or learn more at intel.com/quark.
Copyright © 2016, Intel Corporation. All rights reserved. Intel, the Intel logo, and Intel Quark are trademarks of Intel Corporation in the U.S. and/or other countries.
*Other names and brands may be claimed as the property of others.
0116/MS/CMD/PDF Please Recycle 333836-001US
