MEC Deployment Framework: Difference between revisions
No edit summary |
|||
| (10 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<big> | <big> | ||
After the successfull campaign of MEC Proof of Concepts (PoC), ETSI ISG MEC has developed the '''MEC Deployment Trial Framework''' ( | After the successfull campaign of MEC Proof of Concepts (PoC), ETSI ISG MEC has developed the '''MEC Deployment Trial Framework''' (MDT). | ||
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 standardization work. | ||
| Line 7: | Line 7: | ||
== How does it work == | == How does it work == | ||
The MEC Deployment Trial Framework | The MEC Deployment Trial Framework follows the same process as PoCs. The MEC Deployment Trial framework describes the process and criteria that a MEC Deployment Trial demonstration must adhere to. The latest version of this document can be downloaded here: MEC PoC/MDT Framework [//www.etsi.org/deliver/etsi_gs/MEC/001_099/005/02.01.01_60/gs_MEC005v020101p.pdf] | ||
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 | A 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. | ||
'''The MDT Proposal is expected to be deployed in a commercial network or a field trial network''' relying on the principles of MEC and its interfaces as much as applicable for | |||
the demonstrated use case. | |||
=== MDT Team === | |||
In particular, the MDT Team will have at a minimum 2 different stakeholder members among: | 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 is an ISG MEC Member or an ISG MEC Participant. | The MDT Point of Contact is an ISG MEC Member or an ISG MEC Participant. | ||
The MDT Proposal will address at least one of the [[PoC Topics]] listed on this wiki. | The MDT Proposal will address at least one of the [[PoC Topics]] listed on this wiki. | ||
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 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. | ||
| Line 26: | Line 29: | ||
== How to propose a MEC Deployment Trial == | == How to propose a MEC Deployment Trial == | ||
The MDT proposal will be uploaded on the ETSI Portal as a contribution to ISG MEC | The MDT proposal will be uploaded on the ETSI Portal as a contribution to ISG MEC and a link to the contribution sent to the following address: | ||
MEC_PoC_support_team at etsi.org | MEC_PoC_support_team at etsi.org | ||
| Line 32: | Line 35: | ||
<center> | <center> | ||
<big> | <big> | ||
'''[ | '''[//mecwiki.etsi.org/images/MEC_Deployment_Trial_Proposal.doc Download the template to fill in a Proposal for an MDT]''' | ||
</big> | </big> | ||
</center> | </center> | ||
| Line 38: | Line 41: | ||
== How to report a the concluded MDT == | == How to report a the concluded MDT == | ||
Fill in the template below and email it at | Fill in the template below and email it at | ||
MEC_PoC_support_team at etsi.org | |||
<center> | <center> | ||
[ | <big> | ||
'''[//mecwiki.etsi.org/images/MEC_Deployment_Trial_Report_Template.doc Download the template to fill in a Proposal for an MDT]''' | |||
</big> | |||
</center> | </center> | ||
Latest revision as of 16:55, 26 March 2024
After the successfull campaign of MEC Proof of Concepts (PoC), ETSI ISG MEC has developed the MEC Deployment Trial Framework (MDT).
The goal of MDTs is to demonstrate the viability of MEC in commercial trials/deployments and to provide feedback to the standardization work.
How does it work
The MEC Deployment Trial Framework follows the same process as PoCs. The MEC Deployment Trial framework describes the process and criteria that a MEC Deployment Trial demonstration must adhere to. The latest version of this document can be downloaded here: MEC PoC/MDT Framework [1]
A 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.
The MDT Proposal is expected to be deployed in a commercial network or a field trial network relying on the principles of MEC and its interfaces as much as applicable for 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 is an ISG MEC Member or an ISG MEC Participant. The MDT Proposal will address at least one of the PoC Topics listed on this wiki.
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.
How to propose a MEC Deployment Trial
The MDT proposal will be uploaded on the ETSI Portal as a contribution to ISG MEC and a link to the contribution sent to the following address:
MEC_PoC_support_team at etsi.org
How to report a the concluded MDT
Fill in the template below and email it at
MEC_PoC_support_team at etsi.org