ETSI TR 103 527-2018 SmartM2M Virtualized IoT Architectures with Cloud Back-ends (V1 1 1).pdf

1、 ETSI TR 103 527 V1.1.1 (2018-07) SmartM2M; Virtualized IoT Architectures with Cloud Back-ends TECHNICAL REPORT ETSI ETSI TR 103 527 V1.1.1 (2018-07) 2 Reference DTR/SmartM2M-103527 Keywords cloud, IoT, virtualisation ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92

2、 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in el

3、ectronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing

4、 document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI docu

5、ments is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in an

6、y form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproductio

7、n in all media. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is prot

8、ected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TR 103 527 V1.1.1 (2018-07) 3 Contents Intellectual Property Rights 6g3Foreword . 6g3Modal verbs terminology 6g3Introduction 6g31 Scope 8g32 References 8g32.1 Normative ref

9、erences . 8g32.2 Informative references 8g33 Definitions and abbreviations . 9g33.1 Definitions 9g33.2 Abbreviations . 9g34 Rationale for IoT Virtualization . 10g34.1 IoT: towards massive deployments 10g34.2 Cloud Computing and Virtualization . 10g34.3 The new challenge: combining IoT and Cloud Comp

10、uting 11g34.4 Content of the report. 11g35 Some use cases for IoT Virtualization 12g35.1 Introduction 12g35.2 Horizontal up and down Auto-Scaling . 12g35.3 No single point of failure 13g35.4 Data privacy . 13g35.5 The use case selected as a proof-of-concept . 14g36 Cloud Computing features for IoT V

11、irtualization 15g36.1 Introduction 15g36.2 Functional requirements . 15g36.2.1 Introduction. 15g36.2.2 Multi-tenancy 15g36.2.2.1 Definition 15g36.2.2.2 Comparison with multi-instance architectures 15g36.2.3 Massive Data processing 16g36.3 Non-functional requirements 16g36.3.1 High-throughput . 16g36

12、.3.2 High-availability . 17g36.3.3 Low latency 18g36.3.3.1 Requirements 18g36.3.3.2 MapReduce . 18g36.3.3.3 In Memory Databases . 19g36.3.3.4 Edge Computing . 19g36.3.4 Security. 20g36.4 Features in support of virtualized IoT implementations . 20g36.4.1 Microservices 20g36.4.1.1 Definition 20g36.4.1

13、.2 Comparison to monolithic architectures 21g36.4.1.3 Impact on IoT solutions 21g36.4.1.4 Scaling microservices 21g36.4.1.5 Providing persistency for microservices . 22g36.4.1.6 Security for microservices . 23g36.4.2 Inter-Process Communication (IPC) in microservices architecture 23g36.4.2.1 Communi

14、cation Mechanisms 23g36.4.2.2 Synchronous IPC communications: RESTful communication . 23g36.4.2.3 Asynchronous IPC communications: Messaging 24g36.4.2.4 Hybrid IPC communications . 24g3ETSI ETSI TR 103 527 V1.1.1 (2018-07) 4 7 Implications of IoT virtualization . 25g37.1 Introduction 25g37.2 Microse

15、rvices for IoT Virtualization 25g37.2.1 Microservices Architecture . 25g37.2.2 The Microservices Architecture in practice: an example 26g37.2.3 Relationship of the microservice service HLA to oneM2M . 27g37.3 One High-Level Architecture for IoT Virtualization 30g37.3.1 Functional Architecture for Io

16、T Virtualization . 30g37.3.2 HLA for IoT Virtualization and oneM2M HLA . 30g38 Conclusions 33g38.1 Implications 33g38.2 Lessons Learned . 34g38.3 Recommendations to oneM2M 34g3Annex A: Relationship to big data 35g3Annex B: Relationship with NFV . 38g3B.0 Introduction 38g3B.1 Virtualization in the NF

17、V Architecture 38g3B.2 The NFV architecture and the Microservice-based HLA . 39g3Annex C: Change History . 41g3History 42g3ETSI ETSI TR 103 527 V1.1.1 (2018-07) 5 List of figures Figure 1: Options for adoption of Cloud Native solutions 11g3Figure 2: Batch and Streaming data processing 16g3Figure 3:

18、Achieving high throughput processing of data sets .17g3Figure 4: The MapReduce Concept .18g3Figure 5: Device Edge .19g3Figure 6: Cloud Edge 20g3Figure 7: RESTful IPC 23g3Figure 8: Asynchronous Messaging IPC .24g3Figure 9: Hybrid IPC communications 24g3Figure 10: Microservices Architecture for IoT Vi

19、rtualization 25g3Figure 11: Message Flow Example .27g3Figure 12: Common Services Functions defined by oneM2M 28g3Figure 13: Comparison between the microservices architecture and oneM2M CSF 29g3Figure 14: A High-Level Architecture for IoT Virtualization .30g3Figure 15: Mapping the Microservice Archit

20、ecture and oneM2M Common Service Entities 31g3Figure 16: An example of implementation options of the microservices HLA .32g3Figure A.1: Passive IoT fault detection and isolation module .36g3Figure A.2: Fault detection: Outlier data-point .36g3Figure A.3: Fault detection: Spike behaviour 37g3Figure B

21、.1: High Level NFV Framework .39g3ETSI ETSI TR 103 527 V1.1.1 (2018-07) 6 Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available

22、 for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (h

23、ttps:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, es

24、sential to the present document. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce

25、 any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Report (TR) has been produced by ETSI Technical Committee Smart Machine-to-

26、Machine communications (SmartM2M). Modal verbs terminology In the present document “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and

27、 “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. Introduction In addition to interoperability and security that are two recognized key enablers to the development of large IoT systems, a new one is emerging as another key condition of success: virtualization. The

28、 deployment of IoT systems will occur not just within closed and secure administrative domains but also over architectures that support the dynamic usage of resources that are provided by virtualization techniques over cloud back-ends. This new challenge for IoT requires that the elements of an IoT

29、system can work in a fully interoperable, secure and dynamically configurable manner with other elements (devices, gateways, storage, etc.) that are deployed in different operational and contractual conditions. To this extent, the current architectures of IoT will have to be aligned with those that

30、support the deployment of cloud-based systems (private, public, etc.). Moreover, these architectures will have to support very diverse and often stringent non-functional requirements such as scalability, reliability, fault tolerance, massive data, security. This will require very flexible architectu

31、res for the elements (e.g. the application servers) that will support the virtualized IoT services, as well as very efficient and highly modular implementations that will make a massive usage of Open Source components. These architectures and these implementations form a new approach to IoT systems

32、and the solutions that the present document investigates also should be validated: to this extent, a Proof-of-Concept implementation involving a massive number of virtualized elements has been made. ETSI ETSI TR 103 527 V1.1.1 (2018-07) 7 The present document is one of three Technical Reports addres

33、sing this issue: ETSI TR 103 527 (the present document): “Virtualized IoT Architectures with Cloud Back-ends“ (the present document); ETSI TR 103 528 i.1: “Landscape for open source and standards for cloud native software for a Virtualized IoT service layer“; ETSI TR 103 529 i.2: “Virtualized IoT ov

34、er Cloud back-ends: A Proof of Concept“. ETSI ETSI TR 103 527 V1.1.1 (2018-07) 8 1 Scope The present document: makes a description of some use cases that benefit from virtualization and outlines which one will be used for the Proof-of-Concept that is described in depth in ETSI TR 103 529 i.2; addres

35、ses the rationale and requirements for the use of virtualization - and of the cloud in general - in support of IoT systems. It also introduces some features that will be key for the definition and further implementation of virtualized IoT systems such as microservices; provides the identification of

36、 new architectural elements (components, mappings, Application Programming Interfaces (API), etc.) that are required to address IoT on a cloud back-end. In particular, one objective of the present document is to describe how current IoT nodes e.g. the oneM2M CSE, can be modified and improved by the

37、introduction of micro-services. 2 References 2.1 Normative references Normative references are not applicable in the present document. 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific r

38、eferences, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The foll

39、owing referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. i.1 ETSI TR 103 528: “SmartM2M; Landscape for open source and standards for cloud native software applicable for a Virtualized IoT service layer

40、“, 2018. i.2 ETSI TR 103 529: “SmartM2M; IoT over Cloud back-ends: a Proof of Concept“, 2018. i.3 ITU-T News: “What is cloud-native IoT and why does it matter?“, October 2017. NOTE: Available at http:/news.itu.int/what-is-cloud-native-iot-why-does-it-matter/. i.4 Amazon Web Services: “What is Auto-s

41、caling“. NOTE: Available at http:/ i.5 Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Pro

42、tection Regulation). NOTE: Available at https:/eur-lex.europa.eu/legal-content/EN/ALL/?uri=celex%3A32016R0679. i.6 Deloitte: “Data Privacy in the cloud“, 2016. NOTE: Available at https:/ i.7 ETSI TS 118 101 (V2.10.0): “oneM2M; Functional Architecture (oneM2M TS-0001 version 2.10.0 Release 2)“. ETSI

43、ETSI TR 103 527 V1.1.1 (2018-07) 9 i.8 Recommendation ITU-T Y.3600: “Big data - Cloud computing-based requirements and capabilities“, 2015. i.9 ETSI GS NFV 002: “Network Functions Virtualisation (NFV); Architectural Framework“. i.10 ETSI GS NFV-INF 001: “Network Functions Virtualisation (NFV); Infra

44、structure Overview“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: Open Source Software (OSS): computer software that is available in source code form NOTE: The source code and certain other rights normally reserv

45、ed for copyright holders are provided under an open-source license that permits users to study, change, improve and at times also to distribute the software. source code: any collection of computer instructions written using some human-readable computer language, usually as text standard: output fro

46、m an SSO Standards Setting Organization (SSO): any entity whose primary activities are developing, coordinating, promulgating, revising, amending, reissuing, interpreting or otherwise maintaining standards that address the interests of a wide base of users outside the standards development organizat

47、ion NOTE: In the present document, SSO is used equally for both Standards Setting Organization or Standards Developing Organization (SDO). 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AE Application Entity (in oneM2M) AMQP Advanced Message Queuing Pr

48、otocol API Application Programming Interface ARM Acorn RISC Machine architecture BCP Best Common Practices CAPEX Capital Expenditure CEP Complex Event Processing CoAP Constrained Application Protocol CPU Central Processing Unit CSC Cloud Service Customer CSE Common Services Entity (in oneM2M) CSF Co

49、mmon Service Function CSP Cloud Service Provider DDoS Distributed Denial of Service EU European Union GDPR Global Data Protection Regulation HLA High Level Architecture HTTP HyperText Transfer Protocol IaaS Infrastructure as a Service IAM Identity and Access Management ICT Information and Communication Technology IoT Internet of Things IP Internet Protocol IPC Inter-Pr