Software Defined X and ETSI MEC

These days “Software Defined X” is one of the magic words. Many initiatives tackle the topic, which is primarily follow the cloud native approach including the question how to describe a workload on a hardware abstracted environment. For V2X ETSI Multi Access Edge Computing (MEC) provide an almost complete specification.

MEC 003

https://www.etsi.org/deliver/etsi_gs/MEC/001_099/003/02.02.01_60/gs_MEC003v020201p.pdf 

  • MEC host, including the following:
    • MEC platform
    • MEC applications
    • Virtualisation infrastructure
  • MEC system level management
  • MEC host level management

MEC 009

https://www.etsi.org/deliver/etsi_gs/MEC/001_099/009/03.01.01_60/gs_MEC009v030101p.pdf

Describe the restful HTTP communication schema including the basic semantic of the verbs such as HTTP PUT, GET, POST, etc.

MEC 010

https://www.etsi.org/deliver/etsi_gs/MEC/001_099/01002/02.01.01_60/gs_mec01002v020101p.pdf

Application of HTTP Rest schema including

  • message flows,
  • information model and
  • API interfaces

for Application, its application package (description) and application lifecycle (management).

Application package

  • On-board application package
  • Query application package information
  • Disable application package
  • Enable application package
  • Delete application package
  • Fetch application package

Application Lifecycle (aka LCM)

  • Instanciate
  • Terminate
  • Operate
    • Start
    • Stop

Information Model

  • AppD (application descriptor) – 6.2.1
  • Application Ifecycle Management – 6.2.2
  • Application Package model – 6.2.3
  • Granting Information -6.2.4
  • Common Informatio Model – 6.2.5

Interfaces

  • Application Lifecycle Management – 6.3.1
    • Create application instance identifier
    • Application instantiation
    • Application instance terminate
    • Delete application instance identifier.
    • Query application instance information.
    • Change application instance state.
    • Query application lifecycle operation Status.
    • Subscribe to notifications relating to application lifecycle management.
  • Application Package management – 6.3.3
    • Fetch onboarded application package operation – 6.3.3.1
    • Query application package information operation – 6.3.3.2 
    • Subscribe operation – 6.3.3.3
    • Notify application package operation – 6.3.3.4
    • Onboarding operation – 6.3.3.5
    • Enable operation – 6.3.3.6
    • Disable operation – 6.3.3.7
    • Delete operation – 6.3.3.9
    • Abort application package deletion operation – 6.3.3.10
  • Granting interface – 6.3.4
    • Granting request – 6.3.4.2

API definiiton

{apiRoot}/{apiName}/{apiVersion}/

  • apiRoot : e.g., https
  • apiName: e.g., app_pkgm
  • apiVersion: e.g., V1

… and the URI schema for the information model afore.

MEC 011:

https://www.etsi.org/deliver/etsi_gs/MEC/001_099/011/02.01.01_60/gs_mec011v020101p.pdf

Primary description of basic service(s) and its traffic routing, DNS, timing and transport (protocol) information.

This entry was posted in Uncategorized. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *