1、 ETSI TS 103 371 V1.1.1 (2015-08) Network Technologies (NTECH); Autonomic network engineering for the self-managing Future Internet (AFI); Proofs of Concept Framework TECHNICAL SPECIFICATION ETSI ETSI TS 103 371 V1.1.1 (2015-08)2 Reference DTS/NTECH-AFI-0026-GANA-PoC Keywords autonomic networking, P
2、roof of Concept, Self-Management, use case ETSI 650 Route des Lucioles F-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 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The
3、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
4、 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 th
5、at 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 http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: https:/
6、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 mo
7、dified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2015. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefi
8、t of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 103 371 V1.1.1 (2015-08)3 Contents Intellectual Property Rights 4
9、g3Foreword . 4g3Modal verbs terminology 4g3Introduction 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative references 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 PoC Framework 7g34.1 Roles and responsibilities . 7g34.2 PoC Activity Pro
10、cess 7g34.3 PoC Proposal Acceptance Criteria . 12g34.4 PoC Report Acceptance Criteria 12g35 PoC Support Tools . 13g35.1 PoC mailing list 13g35.2 PoC WIKI . 13g3History 14g3ETSI ETSI TS 103 371 V1.1.1 (2015-08)4 Intellectual Property Rights IPRs essential or potentially essential to the present docum
11、ent 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
12、ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/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 IPR
13、s 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. Foreword This Technical Specification (TS) has been produced by ETSI Technical Committee Network Technologies (NTECH). Modal verbs terminology In the pr
14、esent document “shall“, “shall not“, “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 deliverabl
15、es except when used in direct citation. Introduction The present document defines a framework to coordinate and promote public demonstrations of Proofs of Concept (PoC) illustrating key aspects of Autonomic Management to ensure that the PoC results, lessons learnt and identified gaps are feedback to
16、 the AFI working group of TC NTECH; to build confidence on the viability of autonomic management and control technology; to encourage the development of a diverse and open ecosystem by fostering the integration of components from different players; to support standardization activities of the AFI wo
17、rking group of TC NTECH. This framework describes: the different roles and responsibilities in the PoC process; the PoC process; the acceptance criteria for PoC Proposals and Reports. 2 References 2.1 Normative references References are either specific (identified by date of publication and/or editi
18、on number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected locat
19、ion might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. Not applicabl
20、e. 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 reference document (including any
21、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 following referenced documents are not necessary for the application of the present document but they assist the user with regard to a pa
22、rticular subject area. i.1 ETSI TS 103 194 (V1.1.1): “Network Technologies (NTECH); Autonomic network engineering for the self-managing Future Internet (AFI); Scenarios, Use Cases and Requirements for Autonomic/Self-Managing Future Internet“. ETSI ETSI TS 103 371 V1.1.1 (2015-08)6 i.2 ETSI Directive
23、s. NOTE: Available at https:/portal.etsi.org/directives/34_directives_dec_2014.pdf. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: contribution: contribution of the PoC Project to the standardization work NOTE: A c
24、ontribution can take various forms, e.g. a proposal for modification of one or more ETSI deliverables, a report on lessons learnt, or a set of recommendations on future standardization activities. Committed Contribution: contribution that the PoC Team commits to provide manufacturer: company having
25、a substantial capacity to develop and/or produce and/or install and/or maintain products to be used in, or directly or indirectly connected to, an electronics communications network NOTE: An association or organization of such manufacturers also falls within this category. EXAMPLE: Membership catego
26、ry from ETSI Directives i.2. network operator: operator of an electronics communications network or part thereof NOTE: An association or organization of such manufacturers also falls within this category. EXAMPLE: Membership category from ETSI Directives i.2. PoC Demo: public demonstration of a PoC
27、Project PoC Project: multi-vendor endeavor targeting to prove some concepts in the context of a given technology PoC Proposal: initial description of a multivendor PoC Project, and the feedback it will provide to a Technical Body (TB) PoC Report: compilation of test results, lessons learnt and recom
28、mendations provided by a PoC Team at the end (of each phase) of a PoC Project PoC Test Plan: description of the test objectives of each targeted scenario PoC Topic: specific topic identified by the TB or a WG, where some from-the-field input or feedback is required WIKI: website whose users can add,
29、 modify, or delete its content via a web browser using a simplified markup language or a rich-text editor 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AFI Autonomic network engineering for the self-managing Future Internet AMC Autonomic Management an
30、d processing the contributions made by the PoC Teams on those topics. In the context of the present document, the TB WG role is played by the AFI Working Group of the NTECH Technical Committee. PoC Support Team: Entity or group in charge of administering the PoC process. It is in charge of: maintain
31、ing and making available the PoC Topics List; reviewing PoC Proposals and PoC Reports against the acceptance criteria; declaring the acceptance and end of each PoC; compiling the accepted PoC Proposals and Reports and making them available to the TB WG; and monitoring the PoC Project timelines, and
32、sending the appropriate reminders to the PoC Teams (for Committed Contributions, PoC Report, etc.). In the context of the present document, the PoC Support Team role is assigned to a group of experts, including the chairman of the AFI Working Group of the NTECH Technical Committee, other experts fro
33、m this Working Group appointed by the Technical Committee and experts from the ETSI Centre for Testing and Interoperability (CTI). PoC Team: Group of organizations participating in a PoC Project. The PoC Team is in charge of: writing the PoC Proposal; submitting the Committed Contributions to the TB
34、 WG; and writing the PoC Report. 4.2 PoC Activity Process Figure 1 provides a description of the PoC activity process. ETSI ETSI TS 103 371 V1.1.1 (2015-08)8 Figure 1: POC process overview It includes 9 stages: Stage 1: New PoC Topic identification - Main task: To identify and describe a new PoC Top
35、ics - Responsibility: NTECH/AFI WG - Input: Member contributions, ETSI deliverables produced by the NTECH AFI WG - Output: New PoC Topic - Duration: Any - Description: The NTECH/AFI WG identifies the topics and feedback expected from the PoC Projects. This information is sent to the PoC Support Team
36、 to feed the PoC Topics List. For each PoC Topic, the NTECH AFI WG provides detailed information on: square4 the contribution(s) expected from the PoC; and New PoC Topic New PoC Topic Identification PPRR PRRR PPRR Yes Yes PoC Proposal No PoC Report No PoC Proposal Review PoC Project Lifetime PoC Rep
37、ort Review PoC Proposal Preparation Accepted? PoC Team PoC Support Team TB WG PoC Contributions handling Accepted? PoC start PoC end PoC Topic List maintenance Feedback PoC Project Contributions 5 4 7 6 3 1 8 2 PoC Topics List 9 ETSI ETSI TS 103 371 V1.1.1 (2015-08)9 square4 the expected timing for
38、the contributions. Stage 2: PoC Topics List maintenance - Main task: To maintain and make available the PoC Topics list. To notify the community when there is a change in the list - Responsibility: PoC Support Team - Input: New PoC Topics - Output: PoC Topics list, notifications (e.g. New PoC Topic)
39、 - Duration: Any - Description: The PoC Support Team maintains and gives visibility to the PoC Topics List. The PoC topics and the description of the specific feedback expected for each of them helps PoC Teams to concentrate their efforts on the most valuable topics for the NTECH AFI WG. The PoC Top
40、ics list is made widely available among the community, and appropriate notifications are sent to the community when it is updated. Stage 3: PoC Proposal Preparation - Main task: To prepare and submit the PoC Proposal - Responsibility: PoC Team - Input: Previous TB publications, PoC Topics, PoC Propo
41、sal Template - Output: PoC Proposal - Duration: Any - Description: During this stage, the PoC Team is formed. The PoC Team prepares a PoC Proposal according to the PoC Proposal template available on the AFI PoC WIKI (see clause 5.2) and the PoC Topics from stage 2. PoC proposals are submitted as fol
42、lows: 1) PoC Proposals are uploaded to the ETSI portal as regular contributions to the NTECH AFI WG. 2) The PoC Team informs the community of the PoC proposal submission by emailing the contribution link to NTECH_AFILIST.ETSI.ORG. Stage 4: PoC Proposal Review - Main task: To review the PoC Proposal
43、according to the PoC Proposal Acceptance Criteria - Responsibility: PoC Support Team - Input: PoC Proposal, PoC Proposal Acceptance Criteria - Output: PoC Proposal Review Record (PPRR) - Duration: 2 weeks - Description: The PoC Support Team reviews the PoC Proposal against the PoC Proposal Acceptanc
44、e Criteria identified in clause 4.3. During the review, a PoC Proposal Review Record (PPRR) is generated to support the discussion and decision. The PPRR is sent back to the PoC Team with the response: Accepted/Not Accepted. The PoC Team can incorporate the comments received in the PPRR to the PoC P
45、roposal and re-submit it as follows: 1) The new PoC Proposal is uploaded to the ETSI portal as a revision of the original PoC Proposal contribution. 2) The PoC Team informs the PoC Support Team of the PoC proposal re-submission by emailing the revised contribution link to NTECH_AFILIST.ETSI.ORG. ETS
46、I ETSI TS 103 371 V1.1.1 (2015-08)10 Stage 5: PoC Start - Main task: To announce and create awareness of the new PoC Project. To monitor the new PoC Project milestones and to send the appropriate reminders to the PoC Team - Responsibility: PoC Support Team - Input: PoC Proposal - Output: New PoC Pro
47、ject Announcement - Duration: Any - Description: Once the PoC Support Team has declared a new PoC Proposal accepted, a number of actions are taken to create awareness among the wider community. These actions include: square4 Send an announcement email to the NTECH_AFILIST.ETSI.ORG and NTECH_AFILIST.
48、ETSI.ORG. square4 Update the AFI PoC WIKI page. NOTE: All accepted PoC Proposals are expected to be executed, to submit the Committed Contributions to the NTECH AFI WG and to produce and submit a PoC Report. The PoC Support Team monitors and makes available to the community the status of these PoC P
49、roject milestones. Appropriate reminders are sent to the PoC Teams when required. Stage 6: PoC Project Lifetime - Main task: To run the PoC project, to produce and submit the Committed Contribution(s) to the NTECH/AFI WG. To produce and submit the PoC Report - Responsibility: PoC Team - Input: PoC Proposal, Test Plan Template, Feedback from the NTECHAFI WG - Output: PoC Project Contribution(s), PoC Report(s) - Duration: Typically 3-9 months - Description: During the PoC Project lifetime, the PoC Team works on different tasks such a
