idnits 2.17.00 (12 Aug 2021) /tmp/idnits40732/draft-chen-iot-energy-electricity-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (December 23, 2017) is 1609 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-01) exists of draft-geng-iiot-edge-computing-problem-statement-00 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IoT L. Chen 3 Internet Draft B. Liu 4 Intended Status: Informational Huawei 5 Expires: June 26, 2018 December 23, 2017 7 Overview of Internet of Things 8 with Energy and Electricity Industries 9 draft-chen-iot-energy-electricity-00 11 Abstract 13 This document introduces general problems of energy and electricity 14 industries and discusses how these industries could benefit from 15 Internet of Things (IoT). Use cases are provided and potential 16 technical gaps and protocol needs in IETF are evaluated. 18 Status of this Memo 20 This Internet-Draft is submitted to IETF in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF), its areas, and its working groups. Note that 25 other groups may also distribute working documents as 26 Internet-Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/1id-abstracts.html 36 The list of Internet-Draft Shadow Directories can be accessed at 37 http://www.ietf.org/shadow.html 39 Copyright and License Notice 41 Copyright (c) 2017 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. Acronyms and Terminology . . . . . . . . . . . . . . . . . . . 3 58 3. Problem Statement . . . . . . . . . . . . . . . . . . . . . . . 3 59 3.1. Peak Shaving and Valley Filling of Electrical Grid . . . . 3 60 3.2. Connecting Renewable Energy to the Grid . . . . . . . . . . 3 61 4. IoT Benefits . . . . . . . . . . . . . . . . . . . . . . . . . 4 62 4.1. Data Acquisition and Analysis . . . . . . . . . . . . . . . 4 63 4.2. Demand Prediction and Response . . . . . . . . . . . . . . 4 64 4.3. Energy Routing . . . . . . . . . . . . . . . . . . . . . . 4 65 5. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 66 5.1. Smart (Micro-)Grid . . . . . . . . . . . . . . . . . . . . 5 67 5.2. Distributed Storage . . . . . . . . . . . . . . . . . . . . 5 68 6. Gap Analysis and Protocol Needs . . . . . . . . . . . . . . . . 5 69 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 70 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 71 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 72 9.1. Normative References . . . . . . . . . . . . . . . . . . . 6 73 9.2. Informative References . . . . . . . . . . . . . . . . . . 6 74 Author's Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 76 1. Introduction 78 The traditional energy and electricity industries have not changed a 79 lot in recent years, comparing with the ICT industries. The rise of 80 Internet of Things (IoT) has bring new chances to the energy and 81 electricity industries. 83 A large proportion of energy consumption is in the form of electric 84 energy. Human generate electric energy from fossil fuels, 85 hydroenergy, nuclear energy, etc, and consume electric energy for 86 industry, residential, transport, and other uses. The root cause of 87 most energy and electricity relevant problems is that electric energy 88 can not be easily stored on such a big scale. 90 The development of ICT technologies as well as IoT provides possible 91 solutions on a totally different aspect: focus on the "thing". A 92 thing could generate, consume, or store electric energy. A thing 93 could also have other limited capabilities, e.g., monitoring, 94 communicating, and computing. Using the limited capabilities of those 95 things (constrained nodes) could enable data acquisition and 96 analysis, (electric power) demand prediction and response, energy 97 routing, etc. Thus, the energy and electricity industries could get 98 benefit and the overall energy consumption of human-being could be 99 reduced. 101 To make a better cooperation and convergence for IoT with energy and 102 electricity industries, the idea of edge intelligence (edge 103 computing) as well as cloud computing are important. There are also 104 protocol needs in IETF, accompanied with the development of different 105 kinds of ICT enabling technologies. These protocols are relevant (but 106 not limited) to connectivity and communication among things that 107 generate, consume, or store energy, and configuration and management 108 between the thing and its controller (IoT gateway) or any higher 109 level servers. 111 2. Acronyms and Terminology 113 IoT: Internet of Things 115 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 116 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 117 document are to be interpreted as described in RFC 2119 [RFC2119]. 119 3. Problem Statement 121 As electric energy can not be easily stored on such a big scale, thus 122 causing problems. 124 3.1. Peak Shaving and Valley Filling of Electrical Grid 126 Peak shaving and valley filling is actually a common behavior of the 127 electrical grid to balance the overall energy generating and 128 consuming, but it does cause huge loss of the energy and abrasion of 129 the generating facilities. The peak load of a grid could be twice as 130 the valley load, which means, for example, a 100MW power station 131 switches its output from 100MW to 50MW and then back to 100MW within 132 24 hours, over and over again. The intuition here is similar to 133 driving a car, accelerating and braking continuously not only 134 consumes more oil, but also harms the engine. 136 3.2. Connecting Renewable Energy to the Grid 138 Wind or solar energy stations are "weather sensitive" so that their 139 electrical power output are unstable. Connecting renewable energy 140 stations to the grid could make it more difficult for the grid to do 141 the peak shaving and valley filling job. For example, the wind is 142 averagely more stronger during the night than daytime, meanwhile, the 143 average load of the grid is higher during daytime than night. 145 4. IoT Benefits 147 By implementing IoT nodes (e.g. an IoT specific gateway) to interact 148 with traditional energy generation facilities and energy consumption 149 devices, or embedding edge computing capabilities into these 150 facilities and devices, IoT could benefit the energy and electricity 151 industries. 153 4.1. Data Acquisition and Analysis 155 Data acquisition, including metering, data pre-processing, and 156 communicating, are core capabilities of edge computing. Data analysis 157 can be done at the edge or in the cloud. This enables demand 158 prediction and response, strategy distribution, predictive 159 maintenance, emergency response, etc. 161 4.2. Demand Prediction and Response 163 Data acquired from the consumer side could be used by a data center 164 (cloud) to predict the behavior of consumers in total. For the 165 generating side, most of the power output could be controlled, others 166 such as the maximum output of a wind or solar station could be 167 roughly predicted based on weather forecast. Therefore, the 168 generation-consumption balance for the next time period could be 169 roughly calculated and the grid could be prepared to response 170 properly. 172 Generally, the response contains load control and supply control. A 173 great number of distributed energy consumers could be involved in the 174 load control issue. An IoT gateway or controller that manages a 175 specific kind of consumers could automatically apply different 176 strategies respect to the response needs, e.g., switch down the air- 177 conditioning system when the load is high, switch up the battery 178 charging rate when the load is low. 180 4.3. Energy Routing 182 As the electrical grid has many similar features comparing to the 183 Internet, it could be helpful to introduce the idea of routing into 184 the energy world. Based on real-time supply and demand relationship, 185 a grid could alter its topology to reach an optimized state. 186 Distributed storage stations could act as "buffers" to support energy 187 routing. 189 5. Use Cases 190 5.1. Smart (Micro-)Grid 192 A smart grid that includes smart meters and appliances and different 193 kinds of energy resources could condition the electronic power and 194 control the electricity production and distribution. A smart micro- 195 grid is a localized group of electricity sources and loads. The 196 micro-grid can be connected to the traditional centralized electrical 197 grid (macro-grid), but it can also disconnect from the macro-grid 198 into island mode, depending on the electricity load-supply balance or 199 other needs. The micro-grid is good at integrating various sources of 200 distributed generation, especially renewable energy sources. 202 5.2. Distributed Storage 204 The idea of making huge electric-energy-storage-dedicated batteries 205 does not make sense. Instead, distributed, non-electric-energy- 206 storage-dedicated batteries could be helpful. 208 One good example of distributed energy storage is the Electric 209 Vehicles. 211 Electric vehicles neither save energy nor reduce carbon emission 212 directly, as the electric power they use are mostly generated from 213 fossil fuels. But electric vehicles do help with valley filling of 214 the grid, for a large amount of the electric vehicles are charged at 215 night. In that case, electric vehicles act as batteries, charging 216 when the load is low, via charging points that are 'things' connected 217 to the Internet. 219 6. Gap Analysis and Protocol Needs 221 Internet-related protocols are to be defined, including but not 222 limited to connectivity and communication among things that generate, 223 consume, or store energy, and configuration and management between 224 the thing and its controller or any higher level servers. As there 225 are more than one scenarios within the energy and electricity 226 industries, and each scenario may need a set of Internet-related 227 protocols to support rather than one single protocol, new Internet- 228 related protocols should be defined properly, concluding generally 229 demands as well as mapping different use cases. For example, various 230 wired/wireless protocols should be defined to support communications 231 needs, however, each use case may utilize one or two of these 232 protocols depending on the use case features and that would be enough 233 to match its communication need. 235 [IIoT-EC] has listed some general gaps of edge computing. 237 More details are to be determined. 239 7. Security Considerations 241 TBD. 243 8. IANA Considerations 245 This document does not require any allocations by the IANA and 246 therefore does not have any new IANA considerations. 248 9. References 250 9.1. Normative References 252 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 253 Requirement Levels", BCP 14, RFC 2119, DOI 254 10.17487/RFC2119, March 1997, . 257 9.2. Informative References 259 [IIoT-EC] L. Geng, et al, "Problem Statement of Edge Computing beyond 260 Access Network for Industrial IoT", draft-geng-iiot-edge- 261 computing-problem-statement-00, work in progress. 263 Author's Addresses 265 Lihao Chen 266 Huawei Technologies 267 No.156 Beiqing Rd. Haidian District, 268 Beijing 100095 P.R. China 270 EMail: lihao.chen@huawei.com 272 Bing Liu 273 Huawei Technologies 274 No.156 Beiqing Rd. Haidian District, 275 Beijing 100095 P.R. China 277 EMail:remy.liubing@huawei.com