idnits 2.17.1 draft-baba-iot-webapi-01.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 : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (April 30, 2017) is 2546 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Research Task Force H. Baba 3 Internet-Draft The University of Tokyo 4 Intended status: Informational Y. Ishida 5 Expires: November 1, 2017 Japan Network Enabler Corporation 6 T. Amatsu 7 H. Masuda 8 Tokyo Electric Power Company, Inc. 9 S. Ogura 10 Intel K.K. 11 K. Kunitake 12 BroadBand Tower, Inc. 13 April 30, 2017 15 Report on Problem Solving Experiment for Realization of Web-API-based 16 IoT 17 draft-baba-iot-webapi-01 19 Abstract 21 The University of Tokyo (UOT) is currently performing a demonstration 22 experiment in COMMA House, the experimental smart-house owned by UOT 23 and used as a connected house. The things installed in the house 24 (Things) are operated using applications on smartphones and other 25 devices. The various Things in the smart-house are operated online 26 via a Web API that has been created as a prototype. This report is 27 an overview of the experimental demonstration, which is gradually 28 clarifying that Web API should be effective for solving issues for 29 IoT. 31 Status of This Memo 33 This Internet-Draft is submitted in full conformance with the 34 provisions of BCP 78 and BCP 79. 36 Internet-Drafts are working documents of the Internet Engineering 37 Task Force (IETF). Note that other groups may also distribute 38 working documents as Internet-Drafts. The list of current Internet- 39 Drafts is at http://datatracker.ietf.org/drafts/current/. 41 Internet-Drafts are draft documents valid for a maximum of six months 42 and may be updated, replaced, or obsoleted by other documents at any 43 time. It is inappropriate to use Internet-Drafts as reference 44 material or to cite them other than as "work in progress." 46 This Internet-Draft will expire on November 1, 2017. 48 Copyright Notice 50 Copyright (c) 2017 IETF Trust and the persons identified as the 51 document authors. All rights reserved. 53 This document is subject to BCP 78 and the IETF Trust's Legal 54 Provisions Relating to IETF Documents 55 (http://trustee.ietf.org/license-info) in effect on the date of 56 publication of this document. Please review these documents 57 carefully, as they describe your rights and restrictions with respect 58 to this document. Code Components extracted from this document must 59 include Simplified BSD License text as described in Section 4.e of 60 the Trust Legal Provisions and are provided without warranty as 61 described in the Simplified BSD License. 63 Table of Contents 65 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 66 2. Structure of Web API . . . . . . . . . . . . . . . . . . . . 3 67 3. Demonstration Tests with Prototype Web API . . . . . . . . . 5 68 4. Advantages of Web API with the structure . . . . . . . . . . 5 69 4.1. Security for IoT appliances/devices and the consideration 70 of privacy for obtained data . . . . . . . . . . . . . . 5 71 4.2. Mapping of the physical world and the virtual world . . . 6 72 4.3. Mismatch between the digenesis of ICT technology and the 73 duration of the use of the Things . . . . . . . . . . . . 6 74 4.4. Speed of standardization of specifications and a large 75 number of specifications . . . . . . . . . . . . . . . . 6 76 4.5. Interconnectivity, responsibility demarcation points, and 77 quality assurance in general . . . . . . . . . . . . . . 6 78 4.6. Evolution of the product design policy . . . . . . . . . 7 79 4.7. Change in the design paradigm from enclosure of users to 80 design that is more open . . . . . . . . . . . . . . . . 7 81 4.8. The problem with increased cost and monetization . . . . 7 82 4.9. Security in society and consideration of privacy . . . . 7 83 5. Survey on worldwide trends . . . . . . . . . . . . . . . . . 7 84 6. Future challenges . . . . . . . . . . . . . . . . . . . . . . 8 85 7. Security Considerations . . . . . . . . . . . . . . . . . . . 8 86 8. Normative References . . . . . . . . . . . . . . . . . . . . 8 87 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 89 1. Introduction 91 Outline of Web API and COMMA House 93 COMMA House, the smart-house, was built at the Komaba Research Campus 94 of UOT in 2011, with the intention of conducting research into 95 energy, including HEMS and heat insulation performance. The smart- 96 house is intended for demonstrations, equipped with solar power 97 generation equipment and household lithium ion batteries. The 98 research team arranged the system under discussion with multiple 99 businesses so that the concurrent development of value-added 100 applications can be materialized for the acceleration of the 101 dispersion of smart-houses because energy-related applications alone 102 are not sufficient for their consistent dissemination. 104 It is presupposed that the value-added apps will be developed by 105 third parties that are not directly related to the Things in smart- 106 houses and installed in smartphones/tablets. As part of the joint 107 research with private companies, UOT implemented Web API as a 108 prototype, to enable flexible manipulation of the appliances within 109 the smart-house from the devices. Value-added apps allow you to 110 manipulate the appliances within the smart-house. In addition, such 111 apps were implemented in other demonstrative smart-houses around 112 Japan so that installed appliances could be operated based on the 113 same mechanism. The results confirmed that the Web API was capable 114 of absorbing differences in communications media and protocols for 115 operating Things installed in different smart-houses. 117 Many issues with the realization of IoT have already been reported. 118 Web API may be a solution to some of those issues. 120 2. Structure of Web API 122 Figure 1 shows the structure of a prototype Web API implemented by 123 UOT. The structure has two things of note, which are expected to 124 greatly benefit the realization of IoT. 126 (1) Application to Web API 128 It is often said that a special communications protocol should be 129 prepared for the operation of the Things. However, the cost for 130 learning or additional resources can be avoided if an existing 131 standard protocol is available. This will be a favorable 132 situation for application developers. Accordingly, the structure 133 of prototype Web API permits access from applications with 134 standard protocols, such as HTTP and JSON, which are usually used. 136 (2) Web API to Things 138 The Internet of Things, IoT, is a system that connects everything 139 via the Internet. Needless to say, the Things are limitlessly 140 varied in their prices, with differences of up to five or six 141 digits. One might naturally think that the manufacturing cost 142 would increase if the existing Things that are not networked were 143 connected to the Internet. It would be unreasonable to try to 144 unite the communications protocols for operating the Things. In 145 other words, the acceptable additional cost is naturally different 146 between the Thing worth one dollar and one worth a thousand 147 dollars. Namely, a single communications protocol will not 148 suffice to address the difference. 150 Virtual Driver 151 Machines Softwares 152 Block Block Things alpha 153 +------------+----------+ +----------+ 154 | | +-+ | +------+ | 155 | | |A+-------------------->Firm A| | 156 | | +-+ | +------+ | 157 | | +-+ | +------+ | 158 | +-----+ | |B+-------------------->Firm B| | 159 +-------->alpha+-------> +-+ | +------+ | 160 | | +-----+ | +-+ +-------------+ | +------+ | 161 | | | |C+-->Private Cloud+--->Firm C| | 162 | | | +-+ +-------------+ | +------+ | 163 | | | | | | 164 | | | +-+ +--------+ | +------+ | 165 | | | |Z+-->InfraRed+-------->Firm Z| | 166 +----+ | | | +-+ +--------+ | +------+ | 167 |apps+---+ +------------+----------| +----------+ 168 +----+ | | | +-+ 169 | | | |a+---------+ +----------+ 170 | | | +-+ | | +------+ | 171 | | +-----+ | +-+ +---------->Firm a| | 172 +-------->beta +------> |b+------+ | +------+ | 173 | +-----+ | +-+ | | +------+ | 174 | | +-+ +------------->Frim b| | 175 | | |d+---+ | +------+ | 176 | | +-+ | | +------+ | 177 +------------+----------+ +---------------->Firm d| | 178 | +-----+ | | | +------+ | 179 | |gamma| | | +----------+ 180 | +-----+ | | Things beta 181 +------------+----------+ 183 Figure 1: Structure of Web API at University of Tokyo. 185 A prototype Web API is based on the idea that various communications 186 protocols can be used. It does not matter to users whether the 187 communications protocols are united or not. They are satisfied as 188 long as the Things operate properly. This is similar to the case 189 where users do not find it to be an inconvenience if printer 190 manufacturers have different types of driver software for operating a 191 printer and for printing data from the computer. For this reason, 192 the authors tentatively call the structure of Web API on the Things 193 side the printer driver model. It is assumed that manufacturers of 194 the Things would provide the driver software when the time of IoT 195 arrives. 197 3. Demonstration Tests with Prototype Web API 199 The following Things were used. They have different communications 200 protocols for their operations. For some, signals of infrared ray 201 remote controllers were emulated for operation. 203 Electric windows 205 Electric blinds 207 Lighting (ECHONET Lite/Hue) 209 Air conditioners (ECHONET Lite and infrared ray) 211 Fans 213 Applications developed for the appliances above by third parties are 214 as follows: 216 Control of windows/air conditioners according to the weather 218 Control of the indoor environment according to the sleeping status 219 of users 221 Control of lighting to respond to early earthquake warnings, such 222 as lights turning on 224 These applications were easily applied to other smart-houses by 225 making changes to the driver portion, after they were implemented at 226 COMMA House, regardless of the different types of appliances. 228 4. Advantages of Web API with the structure 230 The previously mentioned basic advantages of Web API can help solve 231 issues in [ID-baba-iot-problems] for the achievement of IoT as 232 follows: 234 4.1. Security for IoT appliances/devices and the consideration of 235 privacy for obtained data 237 IoT services are assumed to involve combined appliances and systems 238 in many different industries. Under such circumstances, it is 239 important to set responsibility demarcation points to maintain 240 security. Being called the printer driver model, Web API is expected 241 to effectively clarify who should update and what should be updated 242 to maintain security. Web API would enable the control of privacy 243 for the obtained data, because it is a mechanism to access all 244 appliances. 246 4.2. Mapping of the physical world and the virtual world 248 Significant labor is required to link applications to the Things. 249 The use of a considerable amount of labor can be avoided by making 250 the Web API intermediary a series of tasks comprised of installation, 251 linking, and calibration, and by performing the tasks like software 252 operations. 254 4.3. Mismatch between the digenesis of ICT technology and the duration 255 of the use of the Things 257 The ICT technology used for mobile phones is subject to alteration 258 every few years, while the entrance doors are usually used for twenty 259 to thirty years. If Web API is the intermediary, it will absorb the 260 mismatch between the ICT and the life of Things. 262 4.4. Speed of standardization of specifications and a large number of 263 specifications 265 There are still a high number of specifications to be introduced into 266 IoT appliances/devices. Additional specifications are under 267 consideration. Such a wide variety of options should not be 268 overlooked. However, the companies that produce and provide services 269 are not necessarily familiar with the specifications, just being 270 users of the specifications. The Web API that is compared to a 271 printer driver model would support the activities of the companies 272 that produce and provide services while they are not bothered by the 273 specifications for operating the Things similar to the users of 274 printers for computers. 276 4.5. Interconnectivity, responsibility demarcation points, and quality 277 assurance in general 279 IoT services are expected to become multifarious through 280 collaboration based on open innovation in the future. In this case, 281 interconnectivity will be secured, and open innovation will be 282 accelerated if Web API is used as an intermediary and a point of 283 responsibility demarcation. 285 4.6. Evolution of the product design policy 287 In the time of IoT, it is anticipated that Things will change from 288 those packed with many functions to those with simplified functions 289 that are allowed to exhibit their versatility through applications. 290 Again, in this case, if interconnectivity is accelerated and 291 responsibility demarcation points are clarified as stated above, then 292 the collaboration will be accelerated between the providers of the 293 Things and the application producers because of the easy-to- 294 understand structure of Web API. 296 4.7. Change in the design paradigm from enclosure of users to design 297 that is more open 299 Same as Section 4.6 above. 301 4.8. The problem with increased cost and monetization 303 In some cases, companies hesitate to enter the IoT appliances market 304 because of the increased cost for conversion into IoT, the 305 effectiveness of which can be hard to see. More providers will be 306 able to develop services/applications based on IoT appliances, 307 appliances will do away with more complicated incorporation/ 308 implementation than necessary and providers will be able to reduce 309 costs while adding more advantages if connection via Web API is 310 materialized. 312 4.9. Security in society and consideration of privacy 314 A socially acceptable system is required in order to transmit and 315 store varied data collected from IoT appliances and appropriately 316 provide consent. However, it is difficult to solve the issues if 317 data is gathered unsystematically. Web API may help to manage such 318 data and solve problems as a system for accessing all appliances. 320 5. Survey on worldwide trends 322 The world is moving towards the widespread use of Web API. In todays 323 world, having a strong API strategy is not just good software 324 practice; it is a powerful business practice and the key to apps that 325 connect the Internet of Things (IoT). Some examples of business 326 strategies based around an API: 328 - Amazon has built a multibillion-dollar revenue business in 329 Amazon Web Services (AWS), leveraging powerful API-based elements 330 such as EC2. 332 - Google Maps would be a much smaller business if the only access 333 were directly through its website. 335 - Twitter has opened up an entire class of businesses and 336 analytical modules by sharing its data API and platform. 338 - Even Salesforce.com, with over 800,000 developers and more than 339 2.5 million applications on the Force.com platform, proudly states 340 that API calls drive more than 60 percent of total traffic to the 341 site. 343 6. Future challenges 345 Those who are interested in Web API with the aforementioned structure 346 are now collaborating in preparation for the creation of Web API with 347 open specifications. For this, UOT is working to provide the 348 opportunity for a discussion that allows private companies to be 349 involved. 351 7. Security Considerations 353 Security issues are described in Section 4.1 and Section 4.9. 355 8. Normative References 357 [ID-baba-iot-problems] 358 Baba, H., Ishida, Y., Amatsu, T., Kunitake, K., and K. 359 Maeda, "Problems in and among industries for the prompt 360 realization of IoT and safety considerations", 2017, 361 . 363 Authors' Addresses 365 Hiroyuki Baba 366 The University of Tokyo 367 Institute of Industrial Science 368 4-6-1 Komaba 369 Meguro-ku, Tokyo 153-8505 370 Japan 372 Email: hbaba@iis.u-tokyo.ac.jp 373 Yoshiki Ishida 374 Japan Network Enabler Corporation 375 21F KDDI Otemachi Bldg. 376 1-8-1 Otemachi 377 Chiyoda-ku, Tokyo 100-0004 378 Japan 380 Email: ishida@jpne.co.jp 382 Takayuki Amatsu 383 Tokyo Electric Power Company, Inc. 384 1-1-3 Uchisaiwai-cho 385 Chiyoda-ku, Tokyo 100-8560 386 Japan 388 Email: amatsu.t@tepco.co.jp 390 Hiroshi Masuda 391 Tokyo Electric Power Company, Inc. 392 1-1-3 Uchisaiwai-cho 393 Chiyoda-ku, Tokyo 100-8560 394 Japan 396 Email: masuda.hiroshi1p@tepco.co.jp 398 Shintaro Ogura 399 Intel K.K. 400 Kokusai Bldg. 5F 401 3-1-1 Marunouchi 402 Chiyoda-ku, Tokyo 100-0005 403 Japan 405 Email: shintaro.ogura@intel.com 407 Koichi Kunitake 408 BroadBand Tower, Inc. 409 Uchisaiwaicho Tokyu Bldg. 410 1-3-2 Uchisaiwai-cho 411 Chiyoda-ku, Tokyo 100-0011 412 Japan 414 Email: kokunitake@bbtower.co.jp