PT03 - MEC Architecture: Difference between revisions
| Line 10: | Line 10: | ||
==Points to prove/refute== | ==Points to prove/refute== | ||
Demonstrate the technical feasibility of the described MEC Architecture | |||
==Criterion of success== | ==Criterion of success== | ||
Revision as of 14:33, 13 January 2016
Description
Demonstrate the MEC Architectural components as defined the current draft DGS MEC003.
MEC PoC Topic Proposal - MEC Architecture
Status
ACTIVE
What is expected to be learnt from the PoCs
Points to prove/refute
Demonstrate the technical feasibility of the described MEC Architecture
Criterion of success
• Feedback on the MEC Architecture
Other information
• Used information flows and information model used.
Technical information to be provided by the PoC Team
Mapping of the PoC components to the MEC Architecture (some PoC components might not be mapped to the MEC architectural blocks)
Information flows and information models used by the PoC (optional)
Template for the PoC Feedback Contribution
No specific template. POC Teams are expected to submit a Technical Report covering the points mentioned above.
Concerned WGs/WI
GS MEC003 Mobile Edge Computing (MEC); MEC Architecture(See latest draft)
Coordinator
MEC IEG Chair: Yun Chao Hu, Huawei (yunchao.hu@huawei.com) MEC-IEG006 Rapporteur: Patrice Hede, Huawei (Patrice.Hede@huawei.com)
CTI Support: cti_support@etsi.org
Contributions (feedback) deadline
Q4 2016