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

Update README.md - GitLab markdown rendering cleanup

parent bfb3fb7e

Macro-Network-Scenario/README.md

+7 −14
Original line number Diff line number Diff line
@@ -65,8 +65,6 @@ The following applies across all the Sandbox Macro Network Scenarios options: 
| zone03   | Macro Cells:  M6, M7     | |









### Macro Network 4G and WiFi



*  Seven 4G Macro Cell Tower Locations (same as 4G option without WiFi)
@@ -97,7 +95,6 @@ The following applies across all the Sandbox Macro Network Scenarios options: 
    *  Small cells have a 100 meter range

*  Terminal connection preference is Small Cells over Macro Cells - single PoA connection at any given time





![5GMacroTopologyImage](5G-Macro-Network-Topology.png)



#### Location Zones
@@ -138,7 +135,6 @@ The MEC Sandbox Macro Network Scenario includes the following terminal types: 




### Terminal Mobility Path Examples in Monaco



> These are examples.  Specific terminal mobility paths will be determined during scenario implementation.



#### Example #1 - High Mobility Terminal
@@ -151,7 +147,7 @@ The MEC Sandbox Macro Network Scenario includes the following terminal types: 




## Macro Network User Configuration Options

> When selecting this scenario, a Sandbox User has options to configure the following:

When selecting this scenario, a Sandbox User has options to configure the following:

 1.  Network Configuration:  4G vs 5G; option to include WiFi hotspots (needed for WLAN API) - using the topologies in [Macro Network Topology Options:](#macro-network-topology-options)

 2.  Type and number of terminals
@@ -166,8 +162,7 @@ See details below. 




## Macro Network MEC Service API Usage

> This section describes how MEC Service APIs may be utilized by a MEC Sandbox user.  

Note, the MEC Service APIs are not isolated from each other.  For example, a Sandbox User may call the Location Service and RNIS at the same time.  The MEC Sandbox  API responses will be consistent across both Services.

> This section describes how MEC Service APIs may be utilized by a MEC Sandbox user.  Note, the MEC Service APIs are not isolated from each other.  For example, a Sandbox User may call the Location Service and RNIS at the same time.  The MEC Sandbox  API responses will be consistent across both Services.



### MEC013 Location Service

> _v2 will be considered when available on Forge.  However, v2 delta summary and impact to the Sandbox is provided._
@@ -249,7 +244,7 @@ References: 
## Example MEC Sandbox Use Cases



### Sandbox External ME App discovery of the Network and Tracking a Device via Location Service API

> Objective:

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 it's location via both queries and notifications:  connected zone, connected access point, and geo-location.
@@ -269,7 +264,7 @@ References: 
| 11. Log-out of the MEC Sandbox (Forge Dev account) |  |



### Browser based MEC client tracking the Location of a Device

> Objective:

Objective:

  * Sandbox User can learn about MEC Service APIs without having to build an ME App or specialized environment external to the Sandbox, exploring the APIs in a friendly manner such as Swagger.

  * All API returned data is consistent with the External MEC Client endpoints.  

     * They can both be called simultaneously.
@@ -298,10 +293,8 @@ References: 
    * Access points (3GPP or WiFi) do not appear or disappear.  

    * 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 for a desk-top browser without a mobile version.



4. [Monaco 3D Map](Monaco-3D-Map.md)