idnits 2.17.1 draft-liu-apn-edge-usecase-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 : ---------------------------------------------------------------------------- ** There are 8 instances of too long lines in the document, the longest one being 1 character in excess of 72. 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 (July 12, 2020) is 1374 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'I-D.li-apn-framework' is defined on line 474, but no explicit reference was found in the text == Unused Reference: 'I-D.li-apn-problem-statement-usecases' is defined on line 480, but no explicit reference was found in the text == Outdated reference: A later version (-07) exists of draft-li-apn-framework-00 == Outdated reference: A later version (-08) exists of draft-li-apn-problem-statement-usecases-00 Summary: 1 error (**), 0 flaws (~~), 6 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group P. Liu 3 Internet-Draft L. Geng 4 Intended status: Informational China Mobile 5 Expires: January 13, 2021 S. Peng 6 Z. Li 7 Huawei 8 July 12, 2020 10 Use cases of Application-aware Networking (APN) in Edge Computing 11 draft-liu-apn-edge-usecase-01 13 Abstract 15 The ever-emerging new services are imposing more and more highly 16 demanding requirements on the network. However, the current 17 deployments could not fully accommodate those requirements due to 18 limited capabilities. For example, it is difficult to utilize the 19 traditional centralized deployment mode to meet the low-latency 20 demand of some latency-sensitive applications. Moreover, the total 21 amount of centralized service data is growing exponentially, which 22 brings great pressure on the network bandwidth. There has been a 23 clear trend that decentralized sites comprising of computing and 24 storage resources are deployed at various locations to provide 25 services. In particular, when the sites are deployed at the network 26 edge, i.e. the Edge Computing, it can better handle the business 27 needs of the users nearby, which provides the possibilities to 28 provide differentiated network and computing services. In order to 29 achieve the full benefits of the edge computing, it actually implies 30 a precondition that the network should be aware of the applications' 31 requirements in order to steer their traffic to the network paths 32 that can satisfy their requirements. Application-aware networking 33 (APN) fits as the missing puzzle piece to bridge the applications and 34 the network to accommodate the edge services' needs, fully releasing 35 the benefits of the edge computing. 37 This document describes the various application scenarios in edge 38 computing to which the APN can be beneficial, including augmented 39 reality, cloud gaming and remote control, which empowers the video 40 business, users interaction business and user-device interaction 41 business. In those scenarios, APN can identify the specific 42 requirements of edge computing applications on the network, process 43 close to the users, provide SLA guaranteed network services such as 44 low latency and high reliability. 46 Requirements Language 48 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 49 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 50 document are to be interpreted as described in RFC 2119 [RFC2119]. 52 Status of This Memo 54 This Internet-Draft is submitted in full conformance with the 55 provisions of BCP 78 and BCP 79. 57 Internet-Drafts are working documents of the Internet Engineering 58 Task Force (IETF). Note that other groups may also distribute 59 working documents as Internet-Drafts. The list of current Internet- 60 Drafts is at https://datatracker.ietf.org/drafts/current/. 62 Internet-Drafts are draft documents valid for a maximum of six months 63 and may be updated, replaced, or obsoleted by other documents at any 64 time. It is inappropriate to use Internet-Drafts as reference 65 material or to cite them other than as "work in progress." 67 This Internet-Draft will expire on January 13, 2021. 69 Copyright Notice 71 Copyright (c) 2020 IETF Trust and the persons identified as the 72 document authors. All rights reserved. 74 This document is subject to BCP 78 and the IETF Trust's Legal 75 Provisions Relating to IETF Documents 76 (https://trustee.ietf.org/license-info) in effect on the date of 77 publication of this document. Please review these documents 78 carefully, as they describe your rights and restrictions with respect 79 to this document. Code Components extracted from this document must 80 include Simplified BSD License text as described in Section 4.e of 81 the Trust Legal Provisions and are provided without warranty as 82 described in the Simplified BSD License. 84 Table of Contents 86 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 87 2. Edge Computing and APN . . . . . . . . . . . . . . . . . . . 3 88 3. Usage Scenarios of APN in edge computing . . . . . . . . . . 4 89 3.1. Augmented Reality (AR) . . . . . . . . . . . . . . . . . 4 90 3.1.1. Use Case Description . . . . . . . . . . . . . . . . 4 91 3.1.2. Augmented Reality Today . . . . . . . . . . . . . . . 4 92 3.1.3. Augmented Reality with Edge Computing and APN . . . . 5 93 3.2. Cloud Gaming . . . . . . . . . . . . . . . . . . . . . . 6 94 3.2.1. Use Case Description . . . . . . . . . . . . . . . . 6 95 3.2.2. Cloud Gaming Today . . . . . . . . . . . . . . . . . 6 96 3.2.3. Cloud Gaming with Edge Computing and APN . . . . . . 7 97 3.3. Remote control of industry . . . . . . . . . . . . . . . 8 98 3.3.1. Use Case Description . . . . . . . . . . . . . . . . 8 99 3.3.2. Remote control of industry Today . . . . . . . . . . 8 100 3.3.3. Remote control of industry with Edge Computing and 101 APN . . . . . . . . . . . . . . . . . . . . . . . . . 9 102 4. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . 10 103 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 104 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 105 7. Normative References . . . . . . . . . . . . . . . . . . . . 11 106 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 108 1. Introduction 110 Edge computing is to deploy service sites near the user side to 111 provide users with better network and computing services. The 112 services of edge computing can not only be implemented in the edge 113 data center, but also be integrated in the network equipment, which 114 brings the possibility for the convergence of network and computing, 115 and also puts forward the requirements for the technology combining 116 of different industries. On the one hand, the demand of different 117 applications for the network need to be exposed; on the other hand, 118 the network needs to be aware of computing power and steers the 119 traffic along the appropriate path towards the suitable sites. 121 The existing network can only identify the application demands in a 122 coarse granularity. When the application demand is high causing the 123 heavy network load, it usually fails to guarantee the latency and 124 reliability of the applications especially the mission-critical 125 applications. Application-aware networking (APN) is to solve the 126 problem of mutual recognition between network and application. APN 127 enables the network to be aware of the applications' requirements in 128 a fine granularity, and then either steer the corresponding traffic 129 onto the appropriate network path (if exist) that can satisfy these 130 requirements or establish an exclusive network path which wouldn't be 131 influenced by other applications' traffic flow. 133 2. Edge Computing and APN 135 In a whole edge computing network, there are user terminal, edge 136 gateway and edge data center. The edge gateway can be the UPF In 5G 137 network. The edge data center is uasually closed to the user, so it 138 can provide the low latency service. 140 Appilication-aware networking includes the app-aware edge, app-aware 141 process head-end, app-aware process mid-point and app-aware process 142 end-point. A user's request is sent from the client, and then passes 143 through all the nodes of the APN network to the server. 145 The function of app-aware edge can be deployed in the edge gateway, 146 so the request traffic of client can be distinguished by the edge 147 gateway/app-aware edge and sent to the edge data center through the 148 APN. In some cases, the reply of the edge data center will not 149 return to the original client, and may be sent to another client 150 through the APN. 152 +------+ +----------------+ +-------------+ +---------+ 153 | | | Edge Gateway/ | | APN | | Edge | 154 |Client|<-->| |<-->| |<-->| Data | 155 | | | App-aware Edge | | Network | | Center | 156 +------+ +----------------+ +-------------+ +---------+ 158 Edge Computing and APN 160 3. Usage Scenarios of APN in edge computing 162 This section presents several typical scenarios which require edge 163 computing to interconnect and to co-ordinate with APN to meet the 164 service requirements and ensure user experience. 166 3.1. Augmented Reality (AR) 168 3.1.1. Use Case Description 170 Augmented reality is a relatively new application that promotes the 171 integration of real world information and virtual world information 172 content. It includes several technologies, such as track 173 registration, display, virtual object generation, interaction and 174 merging. 176 3.1.2. Augmented Reality Today 178 AR gives users an immersive experience. It is widely used in the 179 consumer industry presently, and may also be applied in industrial 180 fields such as health care and education in the future.The general 181 process of AR / VR is as follows: 183 * Image acquisition equipment (such as camera) collects image or 184 video information and sends it to data center. 186 * Data center carries out identification, feature extraction and 187 template rendering, and sends them to AR terminal. 189 * The AR terminal plays the synthesized information. 191 Considering the user experience, AR usually needs a high bandwidth of 192 100mbps due to multi-channel acquisition of image or video data, and 193 a low end-to-end latency less than 60ms. With centralized 194 deployment, the network transmission distance is too long, so the 195 latency demand can't be met; the large volume of traffic load also 196 imposes high challenge on the network bandwidth. 198 3.1.3. Augmented Reality with Edge Computing and APN 200 If the deployment mode of edge computing is adopted, the following 201 functions can be realized: 203 * The collected image or video information can be encoded/decode and 204 compressed by the edge equipment to reduce the bandwidth requirements 205 of data transmission. 207 * The edge data center can process the collected image or video data 208 nearby and send it to the AR terminal equipment, which reduces the 209 distance of network transmission and greatly reduces the latency. 211 Although edge computing can reduce the overall latency of services 212 and reduce the demand for network bandwidth, it still needs 213 differentiated network services to provide the ultimate guarantee for 214 application with high SLA requirements. APN can achieve: 216 * Edge device obtains and encapsulates AR application feature 217 information and sends it to the head end node. 219 * Head end node in the APN identifies the AR data flow and steers it 220 into a specific transmission path according to the demanded 221 bandwidth, latency and reliability. 223 * Mid point in the APN forwards the data stream along the specific 224 path. 226 * End point in the APN receives AR data stream and forwards it either 227 to Data Centre for processing or to the AR player for playing. 229 In the whole process, because APN identifies the traffic of AR 230 application, it can provide corresponding network services to provide 231 customized high reliability, low latency and other SLA guarantee. 233 +------+ Camera +------+ 234 |Source| ->| AR | 235 |data |-\ / |Player| 236 +------+| +-----+ +-------+ +---------+ +-------+ / +------+ 237 \->|App- | | APN | | Edge | | APN |-/ 238 |aware|-->| |-->| Data |-->| | 239 /->|Edge | |Network| | Center | |Network|-\ 240 +------+ | +-----+ +-------+ +---------+ +-------+ \ +------+ 241 |Source|-/ \ | AR | 242 |data | ->|Player| 243 +------+ Camera +------+ 245 Augmented Reality with Edge Computing and APN 247 3.2. Cloud Gaming 249 3.2.1. Use Case Description 251 Cloud gaming is to deploy the game application in the data center, 252 and realize the functions includes the logical process of game 253 command control, as well as the tasks of game acceleration, video 254 rendering and other tasks with high requirements for chips. In this 255 way, the terminal is a video player. Users can get a good game 256 experience without the support of high-end system and chips. 258 Compared with the traditional game mode, there are several advantages 259 of cloud game, such as no installation, no upgrade, no repair, quick 260 to play and reduce the terminal cost, so it will have stronger 261 promotion. 263 3.2.2. Cloud Gaming Today 265 The biggest feature of cloud games is that users interact with each 266 other through the network. The general process is as follows: 268 * The data center sends game video streaming information to the 269 terminal, including game background picture, characters, etc. 271 * The user makes corresponding operation instructions according to 272 the received game video stream information and sends them to the data 273 center. 275 * The data center constantly updates the video stream and other data 276 of the game according to the user's operation instructions. 278 Game users usually pursue consumption experience. Currently, most 279 users are willing to spend extra money in order to obtain better user 280 experience. Generally speaking, the network latency of game is 281 required to be less than 30ms. For competitive game, the latency 282 will be required to be less than 10ms, because professional players 283 usually can feel the millisecond level latency difference. With 284 centralized deployment, the network transmission distance is too 285 long, which is a huge challenge to the network load, so the latency 286 demand can't be met; the large volume of traffic load also imposes 287 high challenge on the network bandwidth. 289 3.2.3. Cloud Gaming with Edge Computing and APN 291 If the deployment of edge computing is adopted, the following 292 functions can be realized with the deployment of edge data center: 294 * The edge data center sends the game video stream information to the 295 terminal, and receives the user's control instruction information for 296 processing. 298 * users can make corresponding operation instructions according to 299 the received video stream information, and get quick response. 301 Edge computing can reduce the latency of game data transmission as a 302 whole, but it should be noted that cloud games usually have multiple 303 players playing a game together, which requires the deterministic 304 latency of multi-party network path, which needs to be realized with 305 APN: 307 * Multiple edge devices obtain and encapsulate cloud game application 308 feature information and send it to the head end node. 310 * Head end node in the APN identifies the data flow of cloud games 311 (maybe the same game), and steers it into a specific transmission 312 path according to its requirements for bandwidth, delay, reliability, 313 etc., which needs to ensure that the latency of multi-user control 314 instructions arriving at the edge data center is consistent. 316 * Mid point in the APN forwards game data stream according to the 317 predetermined path. 319 * The end point in the APN receives the cloud game data stream and 320 steers it either to the data center for processing the users' control 321 instruction or to the user for playing. 323 The whole process requires APN not only to identify the cloud game 324 traffic and provide customized network forwarding services for it, 325 but also to ensure the deterministic latency of multi-user in the 326 same game and provide better game experience. 328 Client A 329 +---------+ 330 |Game data| 331 +---------+-\ +----------+ +-----------+ +-----------+ 332 |<->|App-aware |-A-| APN |-A-| | 333 | Edge A | | Network A | | | 334 +----------+ +-----------+ | Edge Data | 335 +----------+ +-----------+ | Center | 336 |App-aware | | APN | | | 337 |<->| Edge B |-B-| Network B |-B-| | 338 +---------+-/ +----------+ +-----------+ +-----------+ 339 |Game data| 340 +---------+ 341 Client B 343 Cloud Gaming with Edge Computing and APN 345 3.3. Remote control of industry 347 3.3.1. Use Case Description 349 Industrial remote control refers to the remote control of field 350 equipment in areas that are not convenient for manual field control, 351 such as high-temperature and high-risk areas. In the past, signaling 352 was usually transmitted through industrial private networks and 353 protocols. With the development of industrial Internet, the industry 354 also gradually has the demand of network interconnection. Its 355 network tends to adopt L3 protocol and flat architecture, which makes 356 it possible for cross distance remote control service. 358 3.3.2. Remote control of industry Today 360 In the process of remote control, workers constantly make control 361 instructions according to the received image or video information of 362 field equipment, which requires interaction between personnel and 363 equipment through the network. Because the field environment that 364 needs remote control is generally poor, it is also a challenge for 365 the security of the operation equipment. If the latency is too large 366 or the reliability is not enough, it may cause the operation failure, 367 equipment damage and other serious consequences. Therefore, the 368 remote control service requires low latency and high reliability. 369 The general process of remote control is as follows: 371 * Field equipment (such as camera) collects image or video 372 information and sends it to data center. 374 * The data center receives the field information of the equipment and 375 sends it to the workers in the office. 377 * Workers send control instructions and control equipment according 378 to the received field information. 380 Many industrial enterprises rent public cloud resources to construct 381 their own data center, but the long distance of network transmission 382 is not conducive to the timely transmission of image / video data 383 stream, which will cause large latency and packet loss. 385 3.3.3. Remote control of industry with Edge Computing and APN 387 If the deployment mode of edge computing is adopted, and the data 388 center and edge computing access equipment (such as gateway) are 389 deployed in a location or enterprise park close to the business site, 390 the following functions can be realized: 392 * The collected image or video information can be encoded/ decoded 393 and compressed by edge access equipment to reduce the bandwidth 394 requirements. 396 * The control instruction information can be identified by the edge 397 equipment, so as to provide exclusive network transmission service. 399 * The forwarding path of image / video and control information is 400 shortened, which can greatly reduce the latency. 402 Although edge computing can reduce the overall delay of services and 403 reduce the demand of network bandwidth, it still needs to achieve 404 differentiated network services through APN to provide the ultimate 405 network guarantee for the services with the highest network 406 requirements. 408 For users, APN can realize those functions. 410 * Edge device obtains and encapsulates the image or video information 411 of the remote field device, then sends it to the head end node. 413 * Head end in the APN identifies the information and steers the flow 414 into a specific transmission path according to its requirements for 415 bandwidth, delay, reliability, etc.. 417 * Mid point in the APN forwards along the specific path. 419 * End point receives image or video data stream of field equipment 420 and forwards it to users. 422 For field equipment, APN can realize those functions. 424 * Edge device obtains and encapsulates the control instruction 425 information and sends it to the head end node. 427 * Head end in the APN identifies the control data flow and steers 428 into a specific transmission path according to the demand for 429 bandwidth, latency and reliability. 431 * Mid point in the APN forwards along the specific path. 433 * End point receives control information and forwards to the field 434 equipment. 436 In the whole process, APN identifies the traffic of remote control 437 service, which can provide customized high reliability, low latency 438 and other network guarantee. 440 Worker 441 +------------+ 442 |Control data| 443 +------------+-\ +----------+ +-----------+ +-----------+ 444 |<->|App-aware |-W->| APN |-W->| | 445 | Edge A |<-C-| Network A |<-C-| | 446 +----------+ +-----------+ | Edge Data | 447 +----------+ +-----------+ | Center | 448 |App-aware |-C->| APN |-C->| | 449 Camera |<->| Edge B |<-W-| Network B |<-W-| | 450 +------------+-/ +----------+ +-----------+ +-----------+ 451 | Video data | 452 +------------+ 453 On-site Device 455 Remote control of industry with Edge Computing and APN 457 4. Conclusion 459 APN is able to identify the traffic of specific application, and 460 provide low latency and high reliability network services in various 461 edge computing scenarios such as AR, cloud gaming, remote industrial 462 control, etc.. 464 5. Security Considerations 466 TBD. 468 6. IANA Considerations 470 TBD. 472 7. Normative References 474 [I-D.li-apn-framework] 475 Li, Z., Peng, S., Voyer, D., Li, C., Geng, L., Cao, C., 476 Ebisawa, K., Previdi, S., and J. Guichard, "Application- 477 aware Networking (APN) Framework", draft-li-apn- 478 framework-00 (work in progress), March 2020. 480 [I-D.li-apn-problem-statement-usecases] 481 Li, Z., Peng, S., Voyer, D., Xie, C., Liu, P., Qin, Z., 482 Ebisawa, K., Previdi, S., and J. Guichard, "Problem 483 Statement and Use Cases of Application-aware Networking 484 (APN)", draft-li-apn-problem-statement-usecases-00 (work 485 in progress), March 2020. 487 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 488 Requirement Levels", BCP 14, RFC 2119, 489 DOI 10.17487/RFC2119, March 1997, 490 . 492 Authors' Addresses 494 Peng Liu 495 China Mobile 496 Beijing 100053 497 China 499 Email: liupengyjy@chinamobile.com 501 Liang Geng 502 China Mobile 503 Beijing 100053 504 China 506 Email: gengliang@chinamobile.com 508 Shuping Peng 509 Huawei 510 Beijing 100053 511 China 513 Email: pengshuping@huawei.com 514 Zhenbin Li 515 Huawei 516 Beijing 100053 517 China 519 Email: lizhenbin@huawei.com