WARNING! Gitlab maintenance operation scheduled for Thursday, 18 June between 19:00 and 20:00 (CET). During this time window, short service interruptions (less than 5 minutes) may occur. Thank you in advance for your understanding.
> The MEC Sandbox includes four Macro Network Topology options
A Sandbox User must select one of the following network configuration:
1. 4G Cellular
2. 4G Cellular with WiFi
3. 5G Cellular
4. 5G Cellular with WiFi
1. 4G Cellular (single MEP)
2. 4G Cellular with WiFi (single MEP)
4. 4G, 5G Cellular with WiFi (single MEP)
5. 4G, 5G Cellular with WiFi (dual MEP)
## Macro Network Configuration
| Network | Network Configuration | Notes
| -| - |-
| 4G | Macro cell tower sites - single cell per tower site <br><br> Terminals connect to the closest cell tower (i.e. best signal) <br><br> 1 Edge Host site -- in MNO Central Office | Topology details: [4G Network Topology](#macro-network-4g)<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) |
| 4G | Macro cell tower sites - single cell per tower site <br><br> Terminals connect to the closest cell tower (i.e. best signal) <br><br> 1 Edge Host site -- in MNO Central Office | Topology details: [4G Network Topology](#macro-network-4g)<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 MEC Application instance (i.e. notifications from the same subscriber) |
| 5G | All macro cell sites (signal cell per site) configured as 5G <br><br> Configuration includes 5G Small Cells, in addition to 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 | Topology details: [5G Network Topology](#macro-network-5g)<br><br>*Future consideration beyond STF587 scope: 2-3 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. | Topology details: <br> - [4G Network Topology with WiFi](#macro-network-4g-and-wifi)<br> - [5G Network Topology with WiFi](#macro-network-5g-and-wifi) |
@@ -29,11 +29,14 @@ The following applies across all Macro-Network Scenarios:
* Terminals are identified by IPv4 Address, which is a common identifier across MEC Service APIs: Location Service, RNIS, and WLAN API.
* When connected to WiFi, terminals may also be identified by MAC Address (required in the MEC028 data model)
## Macro Network 4G
## Macro Network 4G - Single MEC Platform
* Seven 4G Macro Cell Tower Locations
* Each macro tower includes a single cell
* Macro tower range = 400 meters
* MEC Platforms
* Single MEC Platform
* mep1 cover Zone 1,2,3,4 localities - represents a central MEP site
* Terminal Mobility
* connects to the closest Macro Cell in range
* remains connected until almost out of range
@@ -42,7 +45,6 @@ The following applies across all Macro-Network Scenarios:
* Eleven WiFi Hotspots positioned in locations with pedestrian traffic (same a 4G option with WiFi)
* Hotspots have a 50 meter range
* MEC Platforms
* Two MEC Platforms
* mep1 cover Zone 1,2,3 localities - represents a central MEP site
* mep2 covers Zone 4 locality - represents a zonal MEP site
* Terminal connection preference is WiFi --> Small Cells --> Macro Cells - single PoA connection at any given time
> _Note: PoAs are the same as Macro Network 4G, 5G, WiFi; this figure highlights placement of both MEC Platforms (`mep1` at bottom, `mep2` at the top)_
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 does not have any prior knowledge or configuration information of the Sandbox Macro Network.
* ME App learns the layout of the network: zones, access points, terminals, etc.
* ME App can select a terminal of interest and start tracking its location via both queries and notifications: connected zone, connected access point, and geo-location.
* As a MEC Sandbox User, I have an MEC Application that does not have any prior knowledge or configuration information of the Sandbox Macro Network.
* MEC Application learns the layout of the network: zones, access points, terminals, etc.
* MEC Application can select a terminal of interest and start tracking its location via both queries and notifications: connected zone, connected access point, and geo-location.
| Operation | Notes |
| --------- | ------ |
| 1. Log-in on the Sandbox landing page with access credentials & go to the User Sandbox area| *See [user interface wireframes](https://forge.etsi.org/rep/stf-587/mec-sandbox-scenarios/tree/master/Sandbox-User-Interface#mec-sandbox-wireframe) for details* |
| 2. Find the Location Service URL endpoints & configure them into my application or environment | *See [user interface wireframes](https://forge.etsi.org/rep/stf-587/mec-sandbox-scenarios/tree/master/Sandbox-User-Interface#mec-sandbox-wireframe) for details* |
| 3. Select the network to deploy in the user sandbox | *See [user interface wireframes](https://forge.etsi.org/rep/stf-587/mec-sandbox-scenarios/tree/master/Sandbox-User-Interface#mec-sandbox-wireframe) for details*|
| 4. Start my application or environment | Note: My ME App knows nothing about the sandbox scenario: zones, access points, terminals, etc. <br><br> The Sandbox User's External MEC Client environment must be able to handle API not available responses to allow the sandbox or user environment to be started independently. |
| I want to learn how the network is organized. <br><br>First, I learn zones in the network and how they are organized. <br><br> 5. Call "/<user-specific-mec-sandbox-url>/location-service/zones" <br><br> 5a. MEC sandbox returns a list of zones with zoneId | Examples are not a fully formed URLs <br><br> Now, my ME app knows all the zones in the network: # of PoAs in each zone and number of UEs in each zone. |
| I want to learn where the access points are in the network and their status (operational, etc.) <br><br> 6. Loop for each zoneID - Call "/<user-specific-mec-sandbox-url>/location-service/zones/{zoneId}/accessPoints" <br><br> 6a. MEC sandbox returns list of accessPoints within a zone | For each call - my ME app now knows the access point id for each PoA in a zone and where it is (geo-location), number of users on each PoA, and each PoA status (Serviceable), etc.|
| I want to learn a terminal's Id – so, I can start tracking it <br><br> 7. For a zone with a user - Call "/<user-specific-mec-sandbox-url>/users(zoneId) <br><br> 7a. MEC Sandbox returns list of users within the zone, including their address (id), connected zoneId, and connected accessPointId. | My ME app now knows the address of a terminal (i.e. its id), what zone the terminal is connected, and the terminal's connected access point. <br><br> With the terminal id, my App can now start tracking this user.
| 4. Start my application or environment | Note: My MEC Application knows nothing about the sandbox scenario: zones, access points, terminals, etc. <br><br> The Sandbox User's External MEC Client environment must be able to handle API not available responses to allow the sandbox or user environment to be started independently. |
| I want to learn how the network is organized. <br><br>First, I learn zones in the network and how they are organized. <br><br> 5. Call "/<user-specific-mec-sandbox-url>/location-service/zones" <br><br> 5a. MEC sandbox returns a list of zones with zoneId | Examples are not a fully formed URLs <br><br> Now, my MEC Application knows all the zones in the network: # of PoAs in each zone and number of UEs in each zone. |
| I want to learn where the access points are in the network and their status (operational, etc.) <br><br> 6. Loop for each zoneID - Call "/<user-specific-mec-sandbox-url>/location-service/zones/{zoneId}/accessPoints" <br><br> 6a. MEC sandbox returns list of accessPoints within a zone | For each call - my MEC Application now knows the access point id for each PoA in a zone and where it is (geo-location), number of users on each PoA, and each PoA status (Serviceable), etc.|
| I want to learn a terminal's Id – so, I can start tracking it <br><br> 7. For a zone with a user - Call "/<user-specific-mec-sandbox-url>/users(zoneId) <br><br> 7a. MEC Sandbox returns list of users within the zone, including their address (id), connected zoneId, and connected accessPointId. | My MEC Application now knows the address of a terminal (i.e. its id), what zone the terminal is connected, and the terminal's connected access point. <br><br> With the terminal id, my App can now start tracking this user.
| I want to track a specific terminal. I selected a terminal (via its address) and I: <br><br> 8. Periodically - Call "/<user-specific-mec-sandbox-url>/users/{userId}" <br><br> 8a. MEC Sandbox returns the current: connected accessPointId, connected zoneId, and geo-location. | My App continuously learns the current status of the user / devices: connected zone, connected access point, and geo-location |
| 9. Stop my ME app | |
| 9. Stop my MEC Application | |
| 10. Terminate my MEC sandbox scenario | |
| 11. Log-out of the MEC Sandbox (Forge Dev account) | |
