Commit d8b383b9 authored by Robert Gazda's avatar Robert Gazda
Browse files

Update use-case5.md - editorial updates.

parent eda6ea88
Loading
Loading
Loading
Loading
+5 −5
Original line number Diff line number Diff line
# Use case for MEC application using "scope of locality"
# Use case for MEC application using "scope of locality" - multiple MEC platform or host locations within the MEC Sandbox

This section describes a use case that the user can accomplish using the MEC Sandbox APIs from a MEC application

Objective:
  * As a MEC Sandbox User, I have an ME App that can execute in different MEC platforms with different localities.
  * As a MEC Sandbox User, I have an MEC App that can execute in different MEC platforms with different localities within the Sandbox emulated edge network.
    * `mep1` locality is Zone 1 & 2
    * `mep2` locality is Zone 3 & 4
  * ME App can register in one of the MEC platform to discover available MEC services
  * ME App learns that
  * MEC App can register in one of the MEC platform to discover available MEC services available via the local MEP
  * MEC App learns that
    * Location service is available at the _ZONE_GROUP_ level
      * total of 2 instances; 1 instance per MEC platform
    * RNIS, WAIS are available at the _MEC_SYSTEM_ level
      * total of 1 instance of each; available in all zones
  * ME App uses the discovered services
  * MEC App uses the discovered services

*See [user interface wireframes](../Sandbox-User-Interface#mec-sandbox-wireframe) for frontend details*