---

5.3 Architecting and Developing for the Edge

版权声明: 转载请注明出处 http://www.codingsoho.com/

This section describes how to deploy an application in a MEC system. Some features are fully defined by the MEC standard, whereas others are left to the specific implementation of the MEC provider.

Several APIs should be considered for application development:

• ETSI GS MEC 003: “Multi-access Edge Computing (MEC); Framework and Reference Architecture”
• ETSI GS MEC 006: “Mobile Edge Computing (MEC); Market Acceleration; MEC Metrics Best Practice and Guidelines”
• ETSI GS MEC 009: “Multi-access Edge Computing (MEC); General principles for MEC Service APIs”
• ETSI GS MEC 010-2: “Mobile Edge Management; Part 2: Application lifecycle, rules and requirements management”
• ETSI GS MEC 011: “Mobile Edge Platform Application Enablement
• ETSI GS MEC 012: “Mobile Edge Computing (MEC); Radio Network Information API”
• ETSI GS MEC 013: “Mobile Edge Computing (MEC); Location API”
• ETSI GS MEC 014: “Mobile Edge Computing (MEC); UE Identity API”
• ETSI GS MEC 015: “Mobile Edge Computing (MEC); Bandwidth Management API”
• ETSI GS MEC 016: “UE application interface”

To facilitate MEC application design, MEC communications can be divided in phases:

• Phase 1 – MEC application packaging & on-boarding
• Phase 2 – MEC application instantiation
• Phase 3 – communication between client-side app and MEC app
• Phase 4 – usage of the MEC platform and services