Commit cee3c3e8 authored by Michel Roy's avatar Michel Roy
Browse files

Update README.md

parent 13475d35
Loading
Loading
Loading
Loading
+16 −20
Original line number Diff line number Diff line
@@ -2,22 +2,23 @@
> The purpose of the MEC Sandbox Macro Network City Scenario is to provide a MEC Sandbox user with an understanding of MEC Service API behavior in an urban setting:  MNO Network with 3GPP Points of Attachment (e.g. 4G & 5G) and WiFi hotspots.  

## Scenario Contents
  * [Scenario Location - Monaco](#macro-network-location-monaco)
  * [Macro Network and Terminal Configuration](#macro-network-and-terminal-configuration)
  * [Scenario Location](#scenario-location)
      * Monaco
  * [Network and Terminal Configuration](#network-and-terminal-configuration)
      * network: 4G, 5G, WiFi
      * terminal: high-velocity, low-velocity, stationary
  * [MEC Services APIs](#mec-services-apis)
    * MEC013 - Location Service
    * MEC012 - Radio Network Information Service
    * MEC028 - WLAN Access Network Information Service
  * [Example MEC Sandbox Use Cases](#example-mec-sandbox-use-cases)
  * [MEC Sandbox Use Cases](#mec-sandbox-use-cases)
     * Sandbox External ME App discovery of the Network and Tracking a Device via Location Service API
     * Browser based MEC client tracking the Location of a Device
  * [Assumptions and Miscellaneous](#assumptions-and-miscellaneous)
  * [Assumptions and Limitations](#assumptions-and-limitations)



## Macro Network Location Monaco
## Scenario Location
> The MEC Sandbox Macro Network is set in an interesting section of Monaco, where the following client or terminal types are expected:  Vehicles, Pedestrians and Fixed Wireless Infrastructure.   

[Monaco City and Port Reference -  Google Maps](https://www.google.com/maps/@43.7339073,7.4200297,1752m/data=!3m1!1e3?hl=en&authuser=0):  
@@ -25,8 +26,8 @@

![MonacoImage](Monaco-Sandbox-Area-Of-Interest.png)

## Macro Network and Terminal Configuration
> This section describes the MEC Sandbox network topologies & terminal configuration options
## Network and Terminal Configuration
> This section describes the MEC Sandbox network & terminal configuration options

- [Macro Networks](https://forge.etsi.org/rep/stf-587/mec-sandbox-scenarios/tree/master/Macro-Network-Scenario/macro-networks.md)
- [Terminals](https://forge.etsi.org/rep/stf-587/mec-sandbox-scenarios/tree/master/Macro-Network-Scenario/terminals.md)
@@ -41,23 +42,18 @@
|MEC028 | [WLAN Access Network Information Service](https://forge.etsi.org/rep/stf-587/mec-sandbox-scenarios/tree/master/Macro-Network-Scenario/MEC028.md)
 

## Example MEC Sandbox Use Cases
## MEC Sandbox Use Cases
> This section provides different MEC Sandbox use cases

| Client | Use case
| Client type | Use case
| - | -
|External ME App |  [Discovering of the network & tracking a terminal location](https://forge.etsi.org/rep/stf-587/mec-sandbox-scenarios/tree/master/Macro-Network-Scenario/use-case1.md)
|Browser | [Tracking a terminal location](https://forge.etsi.org/rep/stf-587/mec-sandbox-scenarios/tree/master/Macro-Network-Scenario/use-case2.md)

## Assumptions and Miscellaneous

1. Network configuration is static:  
    * Number of access points, zones, etc.  
    * Service status is always on:  "Serviceable".

2. Sandbox uses local server time as a reference and does not correlate to Sandbox user time.

3. Sandbox UI will be designed & optimized for the Chrome desktop browser
  - Other browsers & mobile platform browsers are not guaranteed
## Assumptions and Limitations
| Category | Assumptions/Limitations
| - | -
|Network configuration|- network configuration is static<br>- Number of access points, zones, etc. does not change at execution time<br>- Service status is always:  "Available"
|Time|- sandbox uses local server time as a reference and does not correlate to user time
|UI | - UI is designed & optimized for Chrome desktop browser<br> - other browsers/platforms (including mobile) are not guaranteed
4. [Monaco 3D Map](Monaco-3D-Map.md)