...

Links offer a button to "calculate link". Losses such as obstruction loss are calculated for the given link.

Site type icons

In the Berlin5G network, the type of sites is known. A site might be a high rise building, a data center, a factory or even a street lamp.

If the zoom level is bigger than 11, the normal 'dots', which represent sites, are exchanged by according icons. If the zoom level is smaller than 11, the icons are swapped back to the dots.

The user should be able to activate or deactivate the icons, once they are shown. The user cannot force-show the icons once the zoom level is smaller than 11.

If the site data has no type information, the icons are not swapped.

Additional map functionality

...

If the connection cannot be established, a suitable info text + icon should appear on the map.

URL

centering map

If latitude, longitude and zoom values are passed in via the url, the map should center on that location.

If the latitude, longitude, zoom part is removed from the url, the map should stay at its former location.

working with details

If a site or link are passed in via the url (via details), the details panel should load the information. The detail-element should be highlighted on the map and the map re-centered accordingly.

If no site nor link with such a name can be found, the details panel should show an error message.

If the details part of the url is removed, the details panel should change to an empty state.

Architecture

Note on Link Calculation

Originally, the link calculation should have been included in the network map.

...

The ODLUX Link Calculator accesses the topology-api server to do its calculations.

Interfaces

URL

odluxurl/{lat},{lon},{zoom}*/details/{detailsName}

*the zoom is optional. If no zoom was passed, a default zoom of 11 should be used

Updating the URL

The URL can be set manually by the user. The map and details panel will adjust accordingly.

When the map stops moving or a details element, either link or site, is loaded, the URL gets updated automatically.

Image

• Topology-api server backend is provided as docker image.
• Docker image with node base container (Dockerhub)
• Startup configuration via -e command line option
  • Choose model data provider
    1. Model "5GBerlin" (Used for ONAP Integration test)
    2. Model "Winlab" (OWL/Cosmos demo)
    3. htTracking with URL (Used for OSNL Integration test)

...

Roadmap

Version 1 Study and conceptual approach (Guilin)

...

• General
  • Prototyp for study and presentation purpose
  • Use public available (License conditions) server like Openstreetmap -> request Ok for presentations and this study purpose
• Browser app
  • Map visualization of database topology information for a "planner"
  • Map projection: WGS84-Format and marcator
  • Interface and first release abstract map provider
  • Scaling/Performance
    • Zoom function (World .. till 50 meters) See http://webhelp.esri.com/arcgisserver/9.3/java/index.htm#designing_overlay_gm_mve.htm
    • Handling of 50000+ map elements
    • show up to 1000 in one zoom level
  • Investigate and proof of concept of map-framework for browser implementation on top of ONAP/React/Typescript App Framework
    • List: MapBox, OpenLayer, Favorit MapBox. Both BSD .. to investigate license conditions for bundling with MapApp
  • For desktop screens size, not mobile
  • Interface for value add extension (Makro function, Gui cut through to other application)

...