1、 ETSI GS MEC-IEG 005 V1.1.1 (2015-08) Mobile-Edge Computing (MEC); Proof of Concept Framework Disclaimer This document has been produced and approved by the Mobile-Edge Computing (MEC) ETSI Industry Specification Group (ISG) and represents the views of those members who participated in this ISG. It
2、does not necessarily represent the views of the entire ETSI membership. GROUP SPECIFICATION ETSI ETSI GS MEC-IEG 005 V1.1.1 (2015-08) 2 Reference DGS/MEC-IEG005 Keywords MEC, proof of concept ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65
3、 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 electronic versions and/or i
4、n 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
5、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 http
6、:/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:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic o
7、r 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. European Telecommuni
8、cations Standards Institute 2015. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit 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
9、 GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI GS MEC-IEG 005 V1.1.1 (2015-08) 3 Contents Intellectual Property Rights 4g3Foreword . 4g3Modal verbs terminology 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative references 5g33 Definitions an
10、d abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 PoC framework 6g34.0 Rationale. 6g34.1 Roles and responsibilities . 7g34.2 PoC activity process . 7g34.3 PoC proposal acceptance criteria 11g34.4 PoC report acceptance criteria 12g35 PoC support tools . 12g35.0 General . 12g35.1 PoC ma
11、iling list 12g35.2 PoC WIKI . 12g3Annex A (informative): Bibliography . 13g3ETSI ETSI GS MEC-IEG 005 V1.1.1 (2015-08) 4 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if
12、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
13、 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 IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or m
14、ay be, or may become, essential to the present document. Foreword This Group Specification (GS) has been produced by ETSI Industry Specification Group (ISG) Mobile-Edge Computing (MEC). Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “
15、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. ETSI ETSI GS MEC-IEG 005 V1.1.1 (2015-08)
16、 5 1 Scope The present document defines a framework to be used by ETSI ISG MEC to coordinate and promote multivendor Proofs of Concept (PoC) projects illustrating key aspects of MEC technology. Proofs of Concept are an important tool to demonstrate the viability of a new technology during its early
17、days and or pre-standardisation phase. The main objectives of the MEC PoC framework are: to ensure the PoC projects are scoped around relevant topics for ISG MEC that require from-the-field input; to ensure that the PoC results, lessons learnt and identified gaps are feedback to ISG MEC; to build co
18、nfidence on the viability of MEC technology; to encourage the development of a diverse and open ecosystem by fostering the integration of components from different players; to support standardization and industry promotion activities of ISG MEC. This framework describes: The different roles and resp
19、onsibilities in the PoC activity process. The PoC activity 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 edition number or version number) or non-specific. For specific re
20、ferences, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE:
21、 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 applicable. 2.2 Informative references References are either specific
22、 (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
23、 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 particular subject area. Not applicable. ETSI ETSI GS MEC-IEG
24、 005 V1.1.1 (2015-08) 6 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: application provider: entity that manages and distributes software-based services and solutions to customers content provider: entity (e.g. a w
25、eb server, or a content distribution network) that provides content to consumers expected contribution: input/feedback expected from the PoC team on a specific PoC topic infrastructure provider: entity that provides components into the network infrastructure ranging from compute elements and/or plat
26、forms to a software component. (i.e. software component examples include security, virtualization, controller, etc.) network operator: organisation that provides a network for the provision of telecommunications services NOTE: If the same organisation also offers services it also becomes the service
27、 provider. PoC demo: public demonstration of a PoC project PoC project: multi-party endeavour 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 PoC report: compilation of test results
28、, lessons learned, contributions and recommendations provided by a PoC team during or at the end of a PoC project PoC team: organizations participating in the PoC project PoC test plan: description of the test objectives of each targeted scenario PoC topic: specific topic identified by the ISG MEC,
29、where some from-the-field input or feedback is required from the PoCs 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CTI Centre for Testing and Interoperability ISG Industry Standardization Group MEC Mobile-Edge Computing PoC Proof of Concept 4 PoC fra
30、mework 4.0 Rationale MEC proposes a new edge based service and computation platform, which may inspire the development and of new types of applications and services. Proof of Concepts are an important tool to demonstrate MEC as a viable technology. Results and feedback from the PoCs can guide the wo
31、rk in the ISG MEC on interoperability and other technical challenges. The public demonstration of MEC concepts helps to build commercial awareness and confidence in this technology, and helps to develop a diverse, open, MEC ecosystem. The PoCs are scoped around the PoC Topics identified by the ISG M
32、EC (i.e. service scenarios, use cases, etc.). ETSI ETSI GS MEC-IEG 005 V1.1.1 (2015-08) 7 4.1 Roles and responsibilities ISG MEC: The ISG MEC is interested in the outcome of the PoC projects. In the context of the PoC framework, it is in charge of: - identifying PoC topics; - identifying expected co
33、ntributions and timelines for PoC topics; - processing the contributions made by the PoC teams on those topics. PoC Support Team: Entity in charge of administering the PoC activity process. It is in charge of: - maintaining and making available the PoC topics; - reviewing PoC proposals and PoC repor
34、ts 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 ISG MEC; - monitoring the PoC project timelines, and sending the appropriate reminders to the PoC teams (for expected contributions,
35、 PoC report, etc.). PoC Team: Group of organizations participating in a PoC project. The PoC team is in charge of: - writing the PoC proposal; - submitting the expected contributions to the ISG MEC; - writing the PoC report. 4.2 PoC activity process Figure 1 provides a description of the PoC activit
36、y process. ETSI ETSI GS MEC-IEG 005 V1.1.1 (2015-08) 8 Figure 1 It includes 9 stages: 1) Stage 1: New PoC topic identification Main task: To identify and describe a new PoC topics. Responsibility: ISG MEC. Input: None. Output: New PoC topic. Duration: Any. Description: The ISG MEC identify the topic
37、s and contributions expected from the PoC projects. This information is sent to the PoC support team to feed the PoC topics list. For each PoC topic, ISG MEC provides detailed information on: - the contribution(s) expected from the PoC; New PoC topic New PoC topic identification Comments Comments Ye
38、s Yes PoC proposal No PoC Report No PoC proposal review PoC project lifetime PoC report review PoC proposal preparation Accepted? PoC team PoC support team ISG MEC 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
39、 topics list 9 ETSI ETSI GS MEC-IEG 005 V1.1.1 (2015-08) 9 - the expected timing for the contributions. 2) 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.
40、 Input: New PoC topics. Output: PoC topics list, notifications (e.g. New PoC topic). Duration: Any. Description: The PoC support team maintains and gives visibility to the PoC topics list in the MEC WIKI. The PoC topics and the description of the specific contributions expected for each of them help
41、s PoC teams to concentrate their efforts on the most valuable topics for the ISG MEC. The PoC topics list is made widely available among the community, and appropriate notifications are sent to the community when it is updated. 3) Stage 3: PoC proposal preparation Main task: To prepare and submit th
42、e PoC proposal. Responsibility: PoC team. Input: Previous ISG MEC publications, PoC topics, PoC proposal template. Output: PoC proposal. Duration: Any. Description: During this stage, the PoC team is formed. PoC team formation is beyond the scope of the ISG MEC. The PoC team prepares a PoC proposal
43、according to the PoC proposal template available in the MEC WIKI, in compliance with the PoC proposal acceptance criteria. The PoC proposal will be uploaded on the ETSI Portal as a contribution to ISG MEC IEG and a link to the contribution sent to the ISG_MEC_IEGLIST.etsi.org mailing list with ISG M
44、EC PoC proposal in the subject line. 4) Stage 4: PoC proposal review Main task: To review the PoC proposal according to the PoC proposal acceptance criteria. Responsibility: PoC support team. Input: PoC proposal, PoC proposal acceptance criteria. Output: Response (Accepted / Not accepted), Comments.
45、 Duration: 14 calendar days. Description: The PoC support team reviews the PoC proposal against the PoC proposal acceptance criteria identified in clause 4.3. Comments are sent back to the PoC Team with the response: Accepted / Not accepted. The PoC Team can incorporate the comments received to the
46、PoC proposal and re-submit it as follows: - The updated PoC proposal is uploaded to the ETSI portal as a revision of the original PoC proposal contribution to ISG MEC IEG. - The PoC Team informs of the PoC proposal re-submission by emailing the revised contribution link to ISG_MEC_IEGLIST.etsi.org.
47、5) 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. ETSI ETSI GS MEC-IEG 005 V1.1.1 (2015-08) 10 Input: PoC proposal. Output: New P
48、oC project 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, but are not restricted to: - Send an announcement email to the ISG MEC. - Updat
49、e the MEC WIKI. Note that all accepted PoC proposals are expected to be executed, to submit the expected contributions to the ISG MEC and to produce and submit a PoC report. The PoC support team monitors and makes available to the community the status of these PoC project milestones. Appropriate reminders are sent to the PoC teams when required. 6) Stage 6: PoC Project Lifetime Main task: To run the PoC project, to produce and submit the expected contribution(s) to the ISG MEC. To produce and submit the PoC report. Responsibility: PoC team. Input: PoC prop
