MEC Deployment Trials Framework: Difference between revisions

Latest revision as of 10:10, 7 September 2018

After the successful campaign of MEC Proof of Concepts (PoC), ETSI ISG MEC has developed the MEC Deployment Trial (MDT) Framework.

The goal of MDTs is to demonstrate the viability of MEC in commercial trials/deployments and to provide feedback to the standardisation work.

How does it work

The MDT Framework describes the process and criteria that a MDT demonstration must adhere to. The process aligns with that defined for MEC PoCs. A key differentiator to PoCs is that MDT proposals are expected to be deployed/tested in a commercial network or a field trial network.

How to propose a MEC Deployment Trial

A MDT Proposal can be submitted by a MDT team that will have at a minimum 2 different stakeholder members among:

network operator;
infrastructure provider;
content/application provider.

The MDT Point of Contact will be an ISG MEC Member or an ISG MEC Participant.

MDT proposals are expected to be scoped around PoC Topics identified and agreed by the ISG MEC. See details and current list here.

MDT proposals are expected to be deployed in a commercial network or a field trial network relying on the principles of the MEC reference architecture and APIs as much as applicable for the demonstrated use case.

The MDT Team will commit to demonstrating their MDT Proposal at a public event, e.g. Public Exhibition, ISG MEC meeting, or other events outlined in the MDT Proposal.

To submit a MDT Proposal, the Proposal template must be completed and uploaded on the ETSI Portal as a contribution to ISG MEC and a link to the contribution emailed to:

  MEC_PoC_support_team at etsi.org

Download the MDT Proposal template

How to report a the concluded MDT

To report on the conclusion of a MDT, the Report template must be completed and emailed to:

  MEC_PoC_support_team at etsi.org

Download the MDT Report template

@@ Line 1: / Line 1: @@
 <big>
-After the successfull campaign of MEC Proof of Concepts (PoC), ETSI ISG MEC has developed the '''MEC Deployment Trial Framework''' (MTD).
+After the successful campaign of MEC Proof of Concepts (PoC), ETSI ISG MEC has developed the '''MEC Deployment Trial (MDT) Framework'''.
-The goal of MDTs is to demonstrate the '''viability of MEC in commercial trials/deployments''' and to provide feedback to the standardization work.
+The goal of MDTs is to demonstrate the '''viability of MEC in commercial trials/deployments''' and to provide feedback to the standardisation work.
 </big>
 == How does it work ==
-The MEC Deployment Trial Framework is proposes the same process as for PoCs. The MEC Deployment Trial framework will describe the process and criteria that a MEC Deployment Trial demonstration must adhere to.
+The MDT Framework describes the process and criteria that a MDT demonstration must adhere to. The process aligns with that defined for MEC PoCs. A key differentiator to PoCs is that '''MDT proposals are expected to be deployed/tested in a commercial network or a field trial network'''.
-MDT proposal can be submitted by a MDT team consisting of a minimum 2 different stakeholder members among network operator, infrastructure provider and content/application provider. '''MDT proposals are expected to be deployed/tested in running commercial network.'''
+== How to propose a MEC Deployment Trial ==
-The MDT '''is expected to be deployed in a commercial network relying on the principles of the MEC reference architecture and interfaces''' as much as applicable for
+A MDT Proposal can be submitted by a MDT team that will have at a minimum 2 different stakeholder members among:
-the demonstrated use case.
-=== MDT Team ===
-In particular, the MDT Team will have at a minimum 2 different stakeholder members among:
 * network operator;
 * infrastructure provider;
 * content/application provider.
+The MDT Point of Contact will be an ISG MEC Member or an ISG MEC Participant.
-The MDT Point of Contact is an ISG MEC Member or an ISG MEC Participant.
+MDT proposals are expected to be scoped around PoC Topics identified and agreed by the ISG MEC. See details and current list [https://mecwiki.etsi.org/index.php?title=PoC_Topics here].
-The MDT Proposal will address at least one of the [[PoC Topics]] listed on this wiki.
+MDT proposals are expected to be deployed in a commercial network or a field trial network relying on the principles of the MEC reference architecture and APIs as much as applicable for the demonstrated use case.
-The MDT Team is expected to demonstrate their MDT proposal at a public event, e.g. Public Exhibition, ISG MEC meeting, or other events, by means outlined in the MDT proposal.
+The MDT Team will commit to demonstrating their MDT Proposal at a public event, e.g. Public Exhibition, ISG MEC meeting, or other events outlined in the MDT Proposal.
-== How to propose a MEC Deployment Trial ==
-The MDT proposal will be uploaded on the ETSI Portal as a contribution to ISG MEC IEG and a link to the contribution sent to the following address:
+To submit a MDT Proposal, the Proposal template must be completed and uploaded on the ETSI Portal as a contribution to ISG MEC and a link to the contribution emailed to:
     MEC_PoC_support_team at etsi.org
@@ Line 35: / Line 29: @@
 <center>
 <big>
-'''[https://mecwiki.etsi.org/images/MEC_Deployment_Trial_Proposal.doc Dowload the template to fill in a Proposal for an MDT]'''
+'''[https://mecwiki.etsi.org/images/MEC_Deployment_Trial_Proposal.doc Download the MDT Proposal template]'''
 </big>
 </center>
@@ Line 41: / Line 35: @@
 == How to report a the concluded MDT ==
-Fill in the template below and email it at
+To report on the conclusion of a MDT, the Report template must be completed and emailed to:
     MEC_PoC_support_team at etsi.org
@@ Line 47: / Line 41: @@
 <center>
 <big>
-'''[https://mecwiki.etsi.org/images/MEC_Deployment_Trial_Report_Template.doc Dowload the template to fill in a Proposal for an MDT]'''
+'''[https://mecwiki.etsi.org/images/MEC_Deployment_Trial_Report_Template.doc Download the MDT Report template]'''
 </big>
 </center>