AdvantEDGE provides a built-in Event Subsystem that integrates with scenarios.
This feature provides the following capabilities:
- Network mobility event
- Change the network location of a physical node in the network topology; this feature emulates mobility of connected devices.
- Network characteristics event
- Change the configured network characteristics of a scenario node; this features emulates changing network conditions, for example if suddenly latency increases, bandwidth reduces, error rate increases
- Compute event
- Creation/deletion of process scenario nodes; this feature emulates changing compute environment where new edge services or terminal applications can be started at scenario runtime.
- PDU connectivity event
- When executing a scenario in PDU connectivity mode, allows creation/deletion of PDU sessions to target Data Networks; this feature allows to emulate certain behaviors of mobile networks.
Following any of the above events, network charactreristics of all affected nodes are re-calculated and re-applied.
- Sandbox Controller: Events received and executed by the Sandbox Controller
|Connectivity Model||Deployment: PDU events are only available when using |
|Data Network Name||Physical Location: [fog/edge/cloud] PDU session events rely on the specified |
|LADN||Physical Location: [fog/edge/cloud] PDU sessions behave differently when the Data Network (DN) is a regular DN or a Local Area Data Network (LADN). LADNs nodes are only reachable when the terminal is in the same Zone while DNs are reachable from any Zone.|
Events can be triggered against a scenario to modify the running network model topology and network characteristics; these events are described below.
|Network Mobility||A network mobility event represents a Physical Location (e.g. a UE, fog, edge) that changes its parent Network Location (e.g. a PoA for UE and fog nodes, or Zone for edge node). When such an event happens, the network characteristics affecting the moved element are re-calculated by AdvantEDGE. Network mobility also allows to send |
|Network Characteristic||A network characteristic event is used to apply, at runtime, new network characteristics to the selected network element. All traffic flows passing through or reaching the updated network element must be re-calculated and re-applied.|
|Compute||A compute event is used to create/delete processes running on a physical node (UE, fog, edge cloud) in the scenario. Following creation/deletion of a process, network paths are updated for all affected nodes.|
|PDU connectivity||PDU connectivity events only work when executing a scenario in |
There are several modes of firing events towards a scenario at runtime.
|Manual (via GUI)||From the GUI it is possible to fire events that modify the network topology or characteristics.|
|Manual (via REST API)||AdvantEDGE implements the Sandbox Controller API. This API is used by the GUI and provides the same capabilies; generating event programatically via the REST API is useful in certain scenarios.|
|Automated||GIS engine introduces a geospatial aspect to scenarios. This geospatial dimention allows to define PoA and UE location and signal radius; enabling automation of various simulation aspects. The following automations are currently supported: terminal movement, mobility events, PoAs in terminal range and network characteristics. More details are available in the Geospatial Modeling section|
|Replay||All events sent during a scenario session (manual or automated) are captured and can saved in a replay file. In turn, replay files can be used to re-generate events previously recorded following the same timing as originally recorded. Replay files can be executed once or replayed in a loop.|
With regards to events, the following must be understood:
- When an scenario node moves in the network, the child elements follow their parent and network characteristics need to be re-calculated accordingly by the platform.
- With regards to the AdvantEDGE model, when a Physical Location is moved, its associated Processes (e.g. edge-apps, ue-apps) are also moved and follow the Physical Location to its new parent Network Location.
- It is now possible to move a process between two Physical Locations
- When triggering such event, the process is not re-started and only its network characteristics are updated.