idnits 2.17.1 draft-wang-detnet-backhaul-requirements-02.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 date (November 11, 2017) is 2359 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'IEEE802.1AS-2011' is defined on line 262, but no explicit reference was found in the text Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 DetNet H. Wang 2 Internet Draft P. Wang 3 Intended status: Standards Track H. Yang 4 Expires: May 15, 2018 Chongqing University of 5 Posts and Telecommunications 6 November 11, 2017 8 Joint Deterministic Scheduling Requirements for Industrial 9 Field/Backhaul Networks 10 draft-wang-detnet-backhaul-requirements-02 12 Abstract 14 This document analyzes the requirements of joint deterministic 15 scheduling in industrial field/backhaul networks. The requirements 16 include six aspects: determinacy, time synchronization, 17 compatibility, scalability, scheduling cost and unified management. 19 Status of this Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF), its areas, and its working groups. Note that 26 other groups may also distribute working documents as Internet- 27 Drafts. 29 Internet-Drafts are draft documents valid for a maximum of six 30 months and may be updated, replaced, or obsoleted by other documents 31 at any time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 The list of current Internet-Drafts can be accessed at 35 http://www.ietf.org/ietf/1id-abstracts.txt 37 The list of Internet-Draft Shadow Directories can be accessed at 38 http://www.ietf.org/shadow.html 40 This Internet-Draft will expire on May 15, 2018. 42 Copyright Notice 44 Copyright (c) 2017 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with 52 respect to this document. Code Components extracted from this 53 document must include Simplified BSD License text as described in 54 Section 4.e of the Trust Legal Provisions and are provided without 55 warranty as described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction ................................................ 2 60 2. Network Structure ........................................... 3 61 3. Joint Scheduling Requirements ............................... 4 62 3.1. Determinacy ............................................ 4 63 3.2. Time Synchronization ................................... 5 64 3.3. Compatibility .......................................... 5 65 3.4. Scalability ............................................ 5 66 3.5. Scheduling Cost......................................... 5 67 3.6. Unified Management ..................................... 5 68 4. Security Considerations ..................................... 6 69 5. IANA Considerations ......................................... 6 70 6. References .................................................. 6 71 6.1. Normative References ................................... 6 72 6.2. Informative References ................................. 6 73 Authors' Addresses ............................................. 7 75 1. Introduction 77 Industrial network includes many types of industrial field networks, 78 such as the three industrial wireless network standards: 79 ISA100.11a[IEC62734], WirelessHART[IEC62591] and WIA-PA[IEC62601]. 80 Most industrial field networks are in a middle or small size, and 81 the network coverage is constant, for example, a field network 82 usually covers a production area of a plant. Therefore, there is a 83 need for industrial backhaul network that makes data flow from an 84 industrial field network to other field networks, or transmits data 85 access to Manufacturing Execution System (MES) or Enterprise 86 Resource Planning (ERP). Thus, a new network architecture, the 87 deterministic industrial field/backhaul network, is proposed in this 88 draft. Some questions of deterministic have been described in the 89 draft [I-D.finn-detnet-problem-statement], and the architecture and 90 application have been illustrated in [I-D.finn-detnet-architecture] 91 and [I-D.bas-usecase-detnet] separately. 93 The proposed network architecture is mainly applied to industrial 94 production environment, which has strong demands on packet loss 95 ratio of network data, low jitter and determinacy and so on. The 96 backhaul network is a heterogeneous network including field wireless 97 networks and wired networks. Industrial backhaul network contains a 98 centralized controller, thus it can schedule the network resources 99 of bandwidth and cache. However, some industrial field networks such 100 as ISA100.11a, WirelessHART, have their own system manager and 101 management mode. At the same time, there is no system manager for 102 some types of networks. Thus, it is an issue remained to study about 103 how to implement a joint scheduling under a complex industrial 104 networks environment. 106 2. Network Structure 108 Figure 1 shows a typical deterministic industrial field/backhaul 109 networks structure. The field network is ISA100.11a, which is a 110 standard of international industrial wireless network. ISA100.11a 111 employs Time Division Multiple Access (TDMA) mechanism to realize 112 the network time-slot, and provide a deterministic guarantee for 113 sensor data. Data derived from the field networks is access to 114 industrial backhaul networks. In the last, sensor data either 115 transmits to another industrial field networks, or to the internet 116 applications or the enterprise information management system like 117 MES/ERP. 119 +------------------------+ 121 | ISA100.11a field | 123 | wireless network | ------------+ 125 +------------------------+ | 127 +---------------------+ +-----------+ 129 | Industrial backhaul | |Internet or| 131 | network | ---| MES/ERP | 133 +---------------------+ +-----------+ 135 +------------------------+ | 137 | ISA100.11a field | ------------+ 139 | wireless network | 141 +------------------------+ 143 Figure 1. Typical network structure 145 Thus, in the above network structure, field network nodes deployed 146 in a plant can communicate with the field network nodes deployed in 147 another plant through the industrial backhaul network. At the same 148 time, the internet or information management system can manage the 149 sensor nodes of the field network remotely through the industrial 150 backhaul network. 152 3. Joint Scheduling Requirements 154 3.1. Determinacy 156 The data, which generates from industrial field network, is directly 157 used to monitor industrial production process, so the requirement of 158 data deterministic transmission is very significant, and data needs 159 to arrive at its destination in a certain time. Industrial 160 field/backhaul network is also a kind of network that is mainly used 161 in the process of industrial production, so it also requires to meet 162 the demands of data determinism in the joint scheduling. 164 3.2. Time Synchronization 166 Because the industrial field/backhaul network is a data aggregation 167 network, and needs scheduling method to ensure deterministic 168 transmission for data stream. Thus, industrial field/backhaul 169 network requires high time synchronization accuracy among all 170 network devices. The accuracy of time synchronization should be held 171 from the range of 10ns to 10ms according to different network 172 applications. Presently, the existing time synchronization protocols 173 include IEEE 1588 and IEEE 802.1 AS, which are raised by Time 174 Sensitive Networking (TSN) Task Group. 176 3.3. Compatibility 178 Industrial field network and backhaul network both comprise 179 different types of networks. Industrial field networks such as 180 ISA100.11a, WirelessHART usually contains built-in system management, 181 which can allocate network communication resources to data stream, 182 while some field networks have no system manager. Although 183 industrial backhaul network is able to control the network with 184 central controller, some mechanisms and interfaces are necessary 185 when conducting joint scheduling to keep compatibility with 186 industrial field/backhaul network. 188 3.4. Scalability 190 Generally, the field network data cannot be transmitted across 191 network. While in the deterministic industrial field/backhaul 192 network, the characteristic of cross-networks should be supported. 193 Therefore, the scalability of data transmission should be ensured 194 during joint scheduling process. 196 3.5. Scheduling Cost 198 The joint scheduling of industrial field/backhaul networks refers to 199 different networks, when the network manager calculates the 200 scheduling results, it should satisfy a low scheduling cost, such as 201 low computation time, and otherwise it will bring extra delay to the 202 transmission of data stream. 204 3.6. Unified Management 206 Most industrial wireless networks have their own network manager. 207 Network manager is able to configure the time slots and channels of 208 field networks. Meanwhile, some backhaul networks also have their 209 independent management units and protocols. For hybrid industrial 210 field/backhaul networks, data stream usually departs from a filed 211 network, and arrives at another field network by passing through 212 backhaul network. It is an important issue to realize the unified 213 management of cross-network data stream in multiple heterogeneous 214 networks by combining every separate network manager. 216 4. Security Considerations 218 5. IANA Considerations 220 This memo includes no request to IANA. 222 6. References 224 6.1. Normative References 226 6.2. Informative References 228 [IEC62734] 229 ISA/IEC, "ISA100.11a, Wireless Systems for Automation, 230 also IEC 62734", 2011, . 234 [IEC62591] 235 www.hartcomm.org, "Industrial Communication Networks - 236 Wireless Communication Network and Communication Profiles 237 - WirelessHART - IEC 62591", 2010,< 238 241 [IEC62601] 242 IEC, "Industrial networks - Wireless communication network 243 and communication profiles - WIA-PA - IEC 62601", 2015, 244 247 [I-D.finn-detnet-problem-statement] 248 Finn, N. and P. Thubert, "Deterministic Networking Problem 249 Statement", draft-finn-detnet-problem-statement-05 (work in 250 progress), March 2016. 252 [I-D.finn-detnet-architecture] 253 Finn, N., Thubert, P., and M. Teener, "Deterministic 254 Networking Architecture", draft-finn-detnet-architecture-08 255 (work in progress), August 2016. 257 [I-D.bas-usecase-detnet] 258 Kaneko, Y., Toshiba and Das, S, "Building Automation Use 259 Cases and Requirements for Deterministic Networking", draft- 260 bas-usecase-detnet-00 (work in progress), October 2015. 262 [IEEE802.1AS-2011] 263 IEEE, "Timing and Synchronizations (IEEE 802.1AS-2011)", 264 2011, . 267 Authors' Addresses 269 Heng Wang 270 Chongqing University of Posts and Telecommunications 271 2 Chongwen Road 272 Chongqing, 400065 273 China 275 Phone: (86)-23-6248-7845 276 Email: wangheng@cqupt.edu.cn 278 Ping Wang 279 Chongqing University of Posts and Telecommunications 280 2 Chongwen Road 281 Chongqing, 400065 282 China 284 Phone: (86)-23-6246-1061 285 Email: wangping@cqupt.edu.cn 287 Hang Yang 288 Chongqing University of Posts and Telecommunications 289 2 Chongwen Road 290 Chongqing, 400065 291 China 293 Phone: (86)-23-6246-1061 294 Email: 18716322620@163.com