| < draft-yang-alto-deliver-functions-over-networks-02.txt | draft-yang-alto-deliver-functions-over-networks-03.txt > | |||
|---|---|---|---|---|
| ALTO WG S. Yang | ALTO WG S. Yang | |||
| Internet-Draft L. Cui | Internet-Draft L. Cui | |||
| Intended status: Standards Track Shenzhen University | Intended status: Standards Track Shenzhen University | |||
| Expires: 31 January 2022 M. Xu | Expires: 22 September 2022 M. Xu | |||
| Tsinghua University | Tsinghua University | |||
| C. Feng | Y. Yang | |||
| Yale University | ||||
| W. Xiao | ||||
| Research Institute of Tsinghua University in Shenzhen | Research Institute of Tsinghua University in Shenzhen | |||
| X.L. Xia | 21 March 2022 | |||
| CRresolink | ||||
| 30 July 2021 | ||||
| Delivering Functions over Networks: Traffic and Performance Optimization | Delivering Functions over Networks: Traffic and Performance Optimization | |||
| for Edge Computing using ALTO | for Edge Computing using ALTO | |||
| draft-yang-alto-deliver-functions-over-networks-02 | draft-yang-alto-deliver-functions-over-networks-03 | |||
| Abstract | Abstract | |||
| As the rapid development of internet, massive data are produced. | As the rapid development of internet, massive data are produced. | |||
| Service providers typically need to deploy services near the edge | Service providers typically need to deploy services near the edge | |||
| networks to better satisfy user_s demand. In order to obtain better | networks to better satisfy user_s demand. In order to obtain better | |||
| quality of the networks, computing functions and user traffic need to | quality of the networks, computing functions and user traffic need to | |||
| be scheduled properly. However, it is challenging to efficiently | be scheduled properly. However, it is challenging to efficiently | |||
| schedule resources among the distributed edge servers because of the | schedule resources among the distributed edge servers because of the | |||
| lack of network information, such as network topology, traffic | lack of network information, such as network topology, traffic | |||
| skipping to change at page 1, line 49 ¶ | skipping to change at page 1, line 49 ¶ | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at https://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on 31 January 2022. | This Internet-Draft will expire on 22 September 2022. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2021 IETF Trust and the persons identified as the | Copyright (c) 2022 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents (https://trustee.ietf.org/ | Provisions Relating to IETF Documents (https://trustee.ietf.org/ | |||
| license-info) in effect on the date of publication of this document. | license-info) in effect on the date of publication of this document. | |||
| Please review these documents carefully, as they describe your rights | Please review these documents carefully, as they describe your rights | |||
| and restrictions with respect to this document. Code Components | and restrictions with respect to this document. Code Components | |||
| extracted from this document must include Simplified BSD License text | extracted from this document must include Revised BSD License text as | |||
| as described in Section 4.e of the Trust Legal Provisions and are | described in Section 4.e of the Trust Legal Provisions and are | |||
| provided without warranty as described in the Simplified BSD License. | provided without warranty as described in the Revised BSD License. | |||
| Table of Contents | Table of Contents | |||
| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | |||
| 2. Conventions and Terminology . . . . . . . . . . . . . . . . . 3 | 2. Conventions and Terminology . . . . . . . . . . . . . . . . . 3 | |||
| 3. Background . . . . . . . . . . . . . . . . . . . . . . . . . 4 | 3. Background . . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 3.1. Edge computing . . . . . . . . . . . . . . . . . . . . . 4 | 3.1. Edge computing . . . . . . . . . . . . . . . . . . . . . 4 | |||
| 3.2. Features of ALTO protocol . . . . . . . . . . . . . . . . 5 | 3.2. Features of ALTO protocol . . . . . . . . . . . . . . . . 4 | |||
| 3.3. Resources and services/functions . . . . . . . . . . . . 5 | 3.3. Resources and services/functions . . . . . . . . . . . . 5 | |||
| 4. Scenario of delivering function . . . . . . . . . . . . . . . 6 | 4. Scenario of delivering function . . . . . . . . . . . . . . . 6 | |||
| 5. Delivering functions by ALTO over edge computing . . . . . . 7 | 5. Delivering functions by ALTO over edge computing . . . . . . 7 | |||
| 6. Implementation and Deployment . . . . . . . . . . . . . . . . 9 | 6. Implementation and Deployment . . . . . . . . . . . . . . . . 9 | |||
| 6.1. Implementation . . . . . . . . . . . . . . . . . . . . . 9 | 7. Management of Functions . . . . . . . . . . . . . . . . . . . 9 | |||
| 6.2. Deployment . . . . . . . . . . . . . . . . . . . . . . . 9 | 8. Multi-domain System . . . . . . . . . . . . . . . . . . . . . 10 | |||
| 6.3. ALTO Integration . . . . . . . . . . . . . . . . . . . . 9 | ||||
| 7. Management of Functions . . . . . . . . . . . . . . . . . . . 10 | ||||
| 8. Multi-domain System . . . . . . . . . . . . . . . . . . . . . 11 | ||||
| 9. Scheduling Framework . . . . . . . . . . . . . . . . . . . . 11 | 9. Scheduling Framework . . . . . . . . . . . . . . . . . . . . 11 | |||
| 10. Security Considerations . . . . . . . . . . . . . . . . . . . 12 | 10. Security Considerations . . . . . . . . . . . . . . . . . . . 12 | |||
| 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 | 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 | |||
| 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 | 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 | |||
| 12.1. Normative References . . . . . . . . . . . . . . . . . . 12 | 12.1. Normative References . . . . . . . . . . . . . . . . . . 12 | |||
| 12.2. Informative References . . . . . . . . . . . . . . . . . 13 | 12.2. Informative References . . . . . . . . . . . . . . . . . 12 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 | |||
| 1. Introduction | 1. Introduction | |||
| For recent years internet has been developing rapidly since it is | For recent years internet has been developing rapidly since it is | |||
| promising to be applied in industrial upgrading. In many scenarios | promising to be applied in industrial upgrading. In many scenarios | |||
| of industrial internet, massive data are produced and require to be | of industrial internet, massive data are produced and require to be | |||
| processed with high efficiency in real time. Typically, various | processed with high efficiency in real time. Typically, various | |||
| functions or services are delivered in these scenarios according to | functions or services are delivered in these scenarios according to | |||
| the users_ demand. These functions or services could be (1) | the users_ demand. These functions or services could be (1) | |||
| surveillance videos that need analysis by AI, (2) Hi-Definition | surveillance videos that need analysis by AI, (2) Hi-Definition | |||
| skipping to change at page 9, line 19 ¶ | skipping to change at page 9, line 14 ¶ | |||
| Note that the data transfer process is using the ALTO protocol | Note that the data transfer process is using the ALTO protocol | |||
| described in [RFC7285] to guarantee the efficiency and security of | described in [RFC7285] to guarantee the efficiency and security of | |||
| the delivering process. In this case, the edge computing clusters | the delivering process. In this case, the edge computing clusters | |||
| are allowed to retrieve the network information, so that the function | are allowed to retrieve the network information, so that the function | |||
| can be delivered to the proper ones to achieve a better performance | can be delivered to the proper ones to achieve a better performance | |||
| in terms of latency, throughput, etc. | in terms of latency, throughput, etc. | |||
| 6. Implementation and Deployment | 6. Implementation and Deployment | |||
| 6.1. Implementation | We have implemented a prototype, where the edge cluster resources are | |||
| managed by K8S and Docker. When users request for edge computing | ||||
| We are inspired by the concept of Serverless Computing, which is a | services, the appropriate edge cluster will be selected by ALTO | |||
| new computing paradigm providing function-based computing services, | according to network map and cost information. | |||
| utilizing containerization technology to run functions. The | ||||
| container, including the running code, library, and data | ||||
| dependencies, will be deployed and orchestrated to target edge | ||||
| servers and clusters by container orchestrator Kubernetes (or K8S). | ||||
| The container orchestration scheme will be computed according to the | ||||
| network information provided by ALTO. | ||||
| IBM OpenWhisk will be used as the FaaS platform in edge clusters, in | ||||
| which the resources are managed by K8S. With this containerization | ||||
| technology, people can deliver functions and services flexibly to the | ||||
| target edge server. Using this standard, users_ request for | ||||
| function-based edge computing services can be efficiently redirected | ||||
| to the target edge server for better performance. | ||||
| 6.2. Deployment | ||||
| We have implemented a prototype and have been deploying it in real | We have deployed the prototype in real network in the China Mobile | |||
| network at a construction site and at a beer plant in Shenzhen, | network. The preliminary results of our deployment show that 1) the | |||
| China. The preliminary results of our deployment show that 1) the | ||||
| performance of edge computing will be greatly improved by using the | performance of edge computing will be greatly improved by using the | |||
| supplied network information and 2) collection and scheduling | supplied network information and 2) collection and scheduling | |||
| policies of this information need to be standardized to obtain | policies of this information need to be standardized to obtain | |||
| coordination among different domains. | coordination among different domains. | |||
| 6.3. ALTO Integration | ||||
| T.B.D. | ||||
| 7. Management of Functions | 7. Management of Functions | |||
| As function standardization in our system could be useful in managing | As function standardization in our system could be useful in managing | |||
| functions efficiently, We will introduce this technique as below. | functions efficiently, We will introduce this technique as below. | |||
| Our system can standardize the functions and expose standard APIs for | Our system can standardize the functions and expose standard APIs for | |||
| users to easily access to and apply for function-based computation | users to easily access to and apply for function-based computation | |||
| services. Above the function-based computation services, certain | services. Above the function-based computation services, certain | |||
| function codes and docker images can be updated and replaced based on | function codes and docker images can be updated and replaced based on | |||
| the user_s demand or standard upgrade. This would be useful to the | the user_s demand or standard upgrade. This would be useful to the | |||
| function management of the platform. Specifically, function | function management of the platform. Specifically, function | |||
| skipping to change at page 13, line 29 ¶ | skipping to change at page 13, line 4 ¶ | |||
| 12.2. Informative References | 12.2. Informative References | |||
| [I-D.ietf-alto-unified-props-new] | [I-D.ietf-alto-unified-props-new] | |||
| Roome, W., Randriamasy, S., Yang, Y., Zhang, J., and K. | Roome, W., Randriamasy, S., Yang, Y., Zhang, J., and K. | |||
| Gao, "Unified Properties for the ALTO Protocol", Work in | Gao, "Unified Properties for the ALTO Protocol", Work in | |||
| Progress, Internet-Draft, draft-ietf-alto-unified-props- | Progress, Internet-Draft, draft-ietf-alto-unified-props- | |||
| new-09, 4 September 2019, <http://www.ietf.org/internet- | new-09, 4 September 2019, <http://www.ietf.org/internet- | |||
| drafts/draft-ietf-alto-unified-props-new-09.txt>. | drafts/draft-ietf-alto-unified-props-new-09.txt>. | |||
| Authors' Addresses | Authors' Addresses | |||
| Shu Yang | Shu Yang | |||
| Shenzhen University | Shenzhen University | |||
| South Campus, Shenzhen University | South Campus, Shenzhen University | |||
| Shenzhen | Shenzhen | |||
| 518060 | 518060 | |||
| P.R. China | P.R. China | |||
| Phone: +86-755-2653-4078 | Phone: +86-755-2653-4078 | |||
| Email: yang.shu@szu.edu.cn | Email: yang.shu@szu.edu.cn | |||
| Laizhong Cui | Laizhong Cui | |||
| Shenzhen University | Shenzhen University | |||
| South Campus, Shenzhen University | South Campus, Shenzhen University | |||
| Shenzhen | Shenzhen | |||
| 518060 | 518060 | |||
| P.R. China | P.R. China | |||
| Phone: +86-755-8695-6280 | Phone: +86-755-8695-6280 | |||
| Email: cuilz@szu.edu.cn | Email: cuilz@szu.edu.cn | |||
| Mingwei Xu | Mingwei Xu | |||
| Tsinghua University | Tsinghua University | |||
| Department of Computer Science, Tsinghua University | Department of Computer Science, Tsinghua University | |||
| Beijing | Beijing | |||
| 100084 | 100084 | |||
| P.R. China | P.R. China | |||
| Phone: +86-10-6278-5822 | Phone: +86-10-6278-5822 | |||
| Email: xumw@tsinghua.edu.cn | Email: xumw@tsinghua.edu.cn | |||
| C.Q. Feng | Richard Yang | |||
| Yale University | ||||
| 51 Prospect St | ||||
| New Haven, CT, 06511 | ||||
| United States of America | ||||
| Email: yry@cs.yale.edu | ||||
| Wei Xiao | ||||
| Research Institute of Tsinghua University in Shenzhen | Research Institute of Tsinghua University in Shenzhen | |||
| Nanshan Hi-new Technology and Industry Park | Nanshan Hi-new Technology and Industry Park | |||
| Shenzhen | Shenzhen | |||
| 518060 | 518060 | |||
| P.R. China | P.R. China | |||
| Email: xiaow@tsinghua-sz.org | ||||
| Email: 236086832@qq.com | ||||
| Xiuli Xia | ||||
| China Resources Resolink | ||||
| Shenzhen New Generation Industrial Park,No.136 Zhongkang Road | ||||
| Shenzhen | ||||
| 518049 | ||||
| P.R. China | ||||
| Email: xiaxiuli@foxmail.com | ||||
| End of changes. 21 change blocks. | ||||
| 51 lines changed or deleted | 32 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||