# MEC Sandbox - Macro Network City Scenario - Monaco
## Purpose
* Provide a MEC Sandbox user with the understanding of MEC Service API behavior in a macro network setting: MNO Network with 3GPP Points of Attachment (e.g. 4G, 5G) and WiFi Hot Spots.
* MEC Service APIs for (current) scenario focus include: MEC013 Location Service, MEC013 RNIS
* MEC Service APIs are not isolated from each other.
* For example, a Sandbox User calls the Location Service and RNIS at the same time.
* The MEC Sandbox API responses will be consistent across both Service APIs.
## Macro Network Location -- Monaco
Interesting section of Monaco, where the following clients are expected:
1. Vehicles (high-mobility terminals)
2. Pedestrians (low-mobility terminals)
3. Fixed (wirelessly devices with no mobility; for example city infrastructure)
[Reference Google Maps - Monaco City and Port](https://www.google.com/maps/@43.7339073,7.4200297,1752m/data=!3m1!1e3?hl=en&authuser=0)
* ~Top right== 43.740791, 7.432699; ~Bottom left == 43.726511, 7.408323
## Macro Network Scenario - User Configuration Options
When selecting this scenario, a Sandbox User has options to configure the following:
1. Network Configuration: 4G vs 5G; option for WiFi (needed for WLAN API)
2. Types and number of terminals
### Macro Network Configuration
| User Option: | Network Configuration | Notes: |
| :--: | ---------- | -------------- |
| 4G / LTE | 10 macro cell tower sites - single cell per tower site <br> Terminals connect to the closest cell tower (i.e. best signal) <br><br> 1 Edge Host site -- in MNO Central Office | Sandbox MVP focus <br><br> Sandbox will appear as a "test" network and not an actual MNO network (e.g. Monaco Telecom) <br><br> PLMN: <br> - MCC = 001 <br> - MNC = 001 <br><br> Sandbox assumes that all calls to MEC Service APIs come from the same ME App instance (i.e. notifications from the same subscriber) |
| 5G / NR | All macro cell sites (signal cell per site) configured as 5G <br><br> In addition, configuration includes 5G Small Cells, ~ 2-3 times the macro cell sites. <br><br> Terminals connect to the closest cell tower or small cell (i.e. best signal) <br><br> 1 Edge Host site -- in MNO Central Office <br>*Future consideration: Edge Hosts near macro towers* | |
| +WiFi | WiFi as an "add-on" option to include in both 4G and 5G configurations. <br><br> WiFi hot-spots included in the network based on WiFi hot spot map. <br><br> All terminal devices are considered dual connected to cellular and WiFi for Location Service, RNIS, and WLAN API reporting | Needed for WLAN API |
This project includes material related to defining the MEC Sandbox Scenarios.
No newline at end of file
This project includes material related to defining the MEC Sandbox Scenarios. A Scenario defines the MEC context and behavior that a Sandbox user will experience (for example, Outdoor Mobile Network Operator Macro Network in a city).
This material is intended to explore and refine how MEC Sandbox by the STF587 team and the STF Steering Committee, before committing development effort.
Sandbox Scenarios are captured in dedicated sub-folders, named for the scenario.
In addition to scenario material, this project also includes MEC Sandbox UI wireframes.
Please refer any questions to the STF587 team: STF587@groups.etsi.org
| Access | As a Sandbox User...<br><br> ...I want to access the sandbox in an isolated setting from other users, using my "Forge Dev" account to identify me. <br><br>...I can sign-in with my "Forge Dev" account from the Sandbox landing page. <br><br> ...I can start my user sandbox after I'm already signed-in to me "Forge Dev" account. <br><br> ...I can start my user sandbox immediately if I am already signed in to "Forge Dev" <br><br>...I want my sandbox instance to be terminated with no state retained when I sign-out from my "Forge Dev" account. | "Forge Dev" account information needed. <br><br> STF assume that Forge will provide: user signup, user authentication, HTTPS certificates, and authentication access tokens (that the Sandbox can use to identify and isolate users)
