Disclaimer

The present document has been produced and approved by the <long ISGname> (<short ISGname>) ETSI Industry Specification Group (ISG) and represents the views of those members who participated in this ISG.

It does not necessarily represent the views of the entire ETSI membership.

ETSI GR ZSM-005 V0.0.4 (2018-10)

GROUP REPORT

Zero Touch Network and Service Management (ZSM);Means of Automation

The GRs (ETSI Group Reports) are deliverables produced by Industry Specification Groups (ISG). GRs are written with the style of a Technical Report (TR), and represent the sole view of the ISG members.

The guidance text (green) shall be removed when no longer needed

<<

ReferenceDGR/ZSM-005ed001

KeywordsAutomation, Solutions, Modelling, Service,

Orchestration, VNF Management, Networks

ETSI

650 Route des LuciolesF-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-préfecture 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 electronic 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 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 documents 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 any 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 reproduction in all media.

© ETSI 2018.All rights reserved.

DECTTM, PLUGTESTSTM, UMTSTM and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.3GPPTM and LTE™ are trademarks of ETSI registered for the benefit of its Members and

of the 3GPP Organizational Partners.oneM2M logo is protected for the benefit of its Members.

GSM® and the GSM logo are trademarks registered and owned by the GSM Association.

ETSI

ETSI GR ZSM-005 V0.0.4 (2018-10)2

ContentsIntellectual Property Rights.................................................................................................................................

Foreword.............................................................................................................................................................

Modal verbs terminology....................................................................................................................................

Executive summary.............................................................................................................................................

Introduction.........................................................................................................................................................

1 Scope.........................................................................................................................................................

2 References.................................................................................................................................................

2.1 Normative references...........................................................................................................................................

2.2 Informative references.........................................................................................................................................

3 Definitions, symbols and abbreviations....................................................................................................

3.1 Definitions (style H2)..........................................................................................................................................

3.2 Symbols...............................................................................................................................................................

3.3 Abbreviations (style H2)......................................................................................................................................

4 Overview...................................................................................................................................................

5 Atomic Means for Automation.................................................................................................................

5.x Means of Automation for <xyz>.........................................................................................................................

5.x.1 Motivation......................................................................................................................................................9

5.X.2 Problems to be solved....................................................................................................................................9

5.X.3 Principles and Concepts.................................................................................................................................9

5.X.4 Implications....................................................................................................................................................9

5.X.5 Proof of concept.............................................................................................................................................9

5.X.6 Relevance for ZSM........................................................................................................................................9

6 Composite Means for Automation..........................................................................................................

6.x Means of Automation for <xyz>.......................................................................................................................

6.x.1 Motivation....................................................................................................................................................10

6.X.2 Problems to be solved..................................................................................................................................10

6.X.3 Principles and Concepts...............................................................................................................................10

ETSI

ETSI GR ZSM-005 V0.0.4 (2018-10)3

6.X.4 Implications..................................................................................................................................................10

6.X.5 Proof of concept...........................................................................................................................................10

6.X.6 Relevance for ZSM......................................................................................................................................10

Annex A: Title of annex....................................................................................................................................

Annex B: Title of annex....................................................................................................................................

B.1 First clause of the annex....................................................................................................................................

B.1.1 First subdivided clause of the annex............................................................................................................12

Annex C: Authors & contributors.....................................................................................................................

Annex <Y>: Bibliography................................................................................................................................

Annex <Z>: Change History.............................................................................................................................

History...............................................................................................................................................................

ETSI

ETSI GR ZSM-005 V0.0.4 (2018-10)4

Intellectual Property Rights Essential patents

IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available 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 (https://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, essential 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 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 Group Report (GR) has been produced by ETSI Industry Specification Group “Zero Touch Network and Service Management” (ZSM).

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 "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

Executive summaryThis unnumbered clause, if present, appears after the "Modal verbs terminology" and before the "Introduction". It is an optional informative element and shall not contain requirements.

The "Executive summary" is used, if required, to summarize the ETSI deliverable. It contains enough information for the readers to become acquainted with the full document without reading it. It is usually one page or shorter.

Introduction This unnumbered clause, if present, appears just before the "Scope". It is an optional informative element and shall not contain requirements.

ETSI

ETSI GR ZSM-005 V0.0.4 (2018-10)5

ETSI

ETSI GR ZSM-005 V0.0.4 (2018-10)6

1 Scope This report explores different existing means or approaches to achieve automation. Such means may exist at different level of management- and managed systems, e.g. at service and network management level, at managed network function level and at managed network level for autonomous optimisation. All these means can have a value to achieve the ZSM goals.

The report does not address a systematic survey of all standardization activities, open-source or other means to achieve automation. Rather it evaluates selected existing and proven means of automation at different levels of managed and management systems, provided by members of the ISG. That comprises for example:

Alternatives for classic modelling such as intent vs. imperative vs. declarative modelling

Lessons learnt from ‘model driven automation’ of service and policy orchestration, including closed loop

Framework for self-managed VNFs based on cloud native network functions and implications

Delineate service modelling against ‘machine learning’-inspired ‘closed loop automation’ modelling

Autonomous management of networks

Means of automation may be single elements or composition of elements which enable service and network automation. They are made visible by this report, and may be considered by the ISG as elements in other work items for specifications.

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 references, 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.

ETSI

ETSI GR ZSM-005 V0.0.4 (2018-10)7

The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area.

Use the EX style, add the letter "i" (for informative) before the number (which shall be in square brackets) and separate this from the title with a tab (you may use sequence fields for automatically numbering references, see clause A.6.9.2: "Sequence numbering") (see example).

EXAMPLE:

[i.1][tab] <Standard Organization acronym> <document number> <version number or date of publication>: "<Title>".

[i.2][tab] <Standard Organization acronym> <document number> <version number or date of publication>: "<Title>".

3 Definitions, symbols and abbreviationsDelete from the above heading the word(s) which is/are not applicable, (see clause 2.11 of EDRs).

Definitions and abbreviations extracted from ETSI deliverables can be useful when drafting documents and can be consulted via the Terms and Definitions Interactive Database (TEDDI) (https://webapp.etsi.org/Teddi/).

3.1 Definitions (style H2)

Clause numbering depends on applicability.

A definition shall not take the form of, or contain, a requirement.

The form of a definition shall be such that it can replace the term in context. Additional information shall be given only in the form of examples or notes (see below).

The terms and definitions shall be presented in alphabetical order.

The following text block applies. More details can be found in clause 2.11.1 of the EDRs.

For the purposes of the present document, the [following] terms and definitions [given in ... and the following] apply:

Definition format

Use the Normal style.

The term shall be in bold, and shall start with a lower case letter (unless it is always rendered with a leading capital) followed by a colon, one space, and the definition starting with a lower case letter and no ending full-stop.

<defined term>: <definition>

EXAMPLE: text used to clarify abstract rules by applying them literally

NOTE: This may contain additional information.

ETSI

ETSI GR ZSM-005 V0.0.4 (2018-10)8

3.2 Symbols Symbols should be ordered alphabetically. Clause numbering depends on applicability.

The following text block applies. More details can be found in clause 2.11.2 of the EDRs.

For the purposes of the present document, the [following] symbols [given in ... and the following] apply:

Symbol format

Use the EW style and separate this from the definition with a tab. Use the EX style for the last term.

<1st symbol> [tab]<1st Explanation> (style EW)

<2nd symbol> [tab]<2nd Explanation> (style EW)

<3rd symbol> [tab]<3rd Explanation> (style EX)

3.3 Abbreviations (style H2)

Abbreviations should be ordered alphabetically. Clause numbering depends on applicability.

The following text block applies. More details can be found in clause 2.11.2 of the EDRs.

For the purposes of the present document, the [following] abbreviations [given in ... and the following] apply:

Abbreviation format

Use the EW style and separate this from the definition with a tab. Use the EX style for the last term.

<1st ACRONYM> [tab]<Explanation> (style EW)

<2nd ACRONYM> [tab]<Explanation> (style EW)

<3rd ACRONYM> [tab]<Explanation> (style EX)

ETSI

ETSI GR ZSM-005 V0.0.4 (2018-10)9

4 OverviewThe subsequent clause will describe means for automation with different granularity (atomic or composite).

Atomic means for automation consist in smaller, stand-alone or self-contained elements for automation. Atomic means can be used or assembled to form a composite means of automation, addressing a bigger automation context or scope.

Composite means for automation consist in the assembly of atomic means creating an integrated mechanism. The description has to explain explicitly how the atomic means are composed.

The description of both atomic and composite means for automation will follow a common structure comprising motivation, problem statement, concepts and principles, implications and relevance for the ZSM ISG. A final sub-clause will address the evaluation of the means for automation. The elements used to demonstrate the evaluation of the means for automation may vary and could range from a theoretical evaluation study up to concrete experiences of vendors or operators with evidence of installations in operational environments.

Editor's Note: example means for automation could be topics such as

Means for automating workflow and process (e.g. orchestration and related things, playbooks, scripts, etc.) means for automating assurance (e.g. closed-loop, analytics, anomaly detection, etc.) means for automating decisions (e.g. rule-based systems, knowledge base, machine learning and artificial

intelligence in general) Means for automating interactions (this is where service modelling and integration abstraction may come

together) Etc.

The decision if something is atomic or composite is up to the contributor: composite means comprises more than one element of automation.

When the draft is stable, the document will be reviewed to ensure the consistent use of the term “means” either as atomic or composite.

The original idea of this report is to show existing and proven (in operations) means for automation, which are beyond existing standards and provide new ways of thinking. Typically, such means are combining several elements of automation.

Based on provided and stable contributions, a clause on synthesis of learnings and implications for the ZSM ISG will be introduced to analyse all contributions collectively. The clause will put the cases in context, show their relevance for ZSM and document implications for the work of the ZSM ISG.

Editor’s note: the term “solution” has a specific meaning in the context of standardization. To avoid confusion between the use of the term solution in this document and the use of solution in other documents of the ISG, it is proposed to remove the term solution and use synonyms instead such as means, mechanism, enabler etc.

ETSI

ETSI GR ZSM-005 V0.0.4 (2018-10)10

5 Atomic Means for Automation

5.x Means of Automation for <xyz> Editor's Note: this level 1 heading is subject to the contributor. It may need to be rephrased/precised, after various concrete contributions have been collected into the WI, in context of a formal milestone.

5.x.1 Motivation

Editor's Note: This clause should contain Business motivation, i.e. drivers or even specific goals, reference to applicable use cases as defined in ZSM001 (possibly with short summary) etc.

5.X.2 Problems to be solved

Editor's Note: This clause should contain the Technical Problem addressed with the means.

5.X.3 Principles and Concepts

Editor's Note: This clause should describe the most essential principle and concepts the means is based on.

5.X.4 Implications

Editor's Note: This clause should explain possible implications to architecture, technologies used, processes (e.g. DevOps).

5.X.5 Proof of concept

Editor's Note: This clause should provide any existing proof points, catalyst, proof of concepts or even customer cases, providing evidence of the means and its business value.

5.X.6 Relevance for ZSM

Editor's Note: This clause should conclude advantages and chances, but also constraints (if existing) to ZSM goals and specification.

ETSI

ETSI GR ZSM-005 V0.0.4 (2018-10)11

6 Composite Means for Automation

6.x Means of Automation for <xyz> Editor's Note: this level 1 heading is subject to the contributor. It may need to be rephrased/precised, after various concrete contributions have been collected into the WI, in context of a formal milestone.

6.x.1 Motivation

Editor's Note: This clause should contain Business motivation, i.e. drivers or even specific goals, reference to applicable use cases as defined in ZSM001 (possibly with short summary) etc.

6.X.2 Problems to be solved

Editor's Note: This clause should contain the Technical Problem addressed with the means.

6.X.3 Principles and Concepts

Editor's Note: This clause should describe the most essential principle and concepts the means is based on, and what single or atomic elements of automation are combined.

6.X.4 Implications

Editor's Note: This clause should explain possible implications to architecture, technologies used, processes (e.g. DevOps).

6.X.5 Proof of concept

Editor's Note: This clause should provide any existing proof points, catalyst, proof of concepts or even customer cases, providing evidence of the means and its business value.

6.X.6 Relevance for ZSM

Editor's Note: This clause should conclude advantages and chances, but also constraints (if existing) to ZSM goals and specification.

ETSI

ETSI GR ZSM-005 V0.0.4 (2018-10)12

Annex A: Title of annex <Text>.

ETSI

ETSI GR ZSM-005 V0.0.4 (2018-10)13

Annex B: Title of annex

B.1 First clause of the annex

B.1.1 First subdivided clause of the annex

<Text>.

ETSI

ETSI GR ZSM-005 V0.0.4 (2018-10)14

Annex C: Authors & contributors The following people have contributed to the present document:

Rapporteur:Andreas Krichel, Hewlett-Packard Enterprise

Other contributors:

Per Kangru, Viavi Solutions

Magnus Buhrgard, Ericsson

Ji Mengdi, Huawei

ETSI

ETSI GR ZSM-005 V0.0.4 (2018-10)15

Annex <Y>: BibliographyThis optional informative clause shall start on a new page and be the last annex of an ETSI deliverable or the last but one if followed by the "Change history/Change request history" annex, if any. The Bibliography shall not contain requirements.

The Bibliography identifies additional reading material not mentioned within the document. Those publications might or might not be publicly available (no check is made by the ETSI Secretariat).

The Bibliography shall include list of standards, books, articles, or other sources on a particular subject which are not referenced in the document.

The Bibliography shall not include references mentioned in the deliverable.

Use Heading 9 style for the "Bibliography" annex, see clause 2.13 of the EDRs for examples.

For the listed material use the Normal style or bulleted lists (e.g. B1+), do not use numbered references.

<Publication>: "<Title>".

OR

<Publication>: "<Title>".

ETSI

ETSI GR ZSM-005 V0.0.4 (2018-10)16

Annex <Z>: Change History If it is desired to keep a detailed record of the changes implemented in a new version it is recommended that this is done by inserting a "Change history/Change request" annex, see clause 2.15.

Date Version Information about changes28.February 2018 0.0.1 Skeleton6. March 2018 0.0.2 Add first contributions from Ericsson and Huawei into Draft15. March 2018 0.0.3 Extract contributions for discussions, simplify Skeleton

ETSI

ETSI GR ZSM-005 V0.0.4 (2018-10)17

History The "History" identifies the major milestones in the life of an ETSI deliverable through the means of a table. The history box shall be provided by the ETSI Secretariat (all additional information will be removed at the publication stage).

Document history

<Version> <Date> <Milestone>

ETSI

ETSI GR ZSM-005 V0.0.4 (2018-10)18