Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

User documentation

Performance Monitoring values measured by the devices are necessary to analyze and optimize the network. Therefore, the application automatically retrieves all historical performance values from the devices and stores them in a database.

The “Performance History” Web Application displays the historical performance values of the device.

Specification

“Performance History” User Interface should be implemented to show the historical performance values of the devices stored in the database.

The model of the data is described in ONF-TR-532 - see xyz-historical-performances.

Below are the UI elements to be implemented.

  1. Table to select a device from all the devices available in PM history database connected device/networkElement.
  2. Once the device is selected from the above table, it should display the below two Dropdowns.
    1. Drop-down to ‘select the LTP’ associated with the selected device.
    2. Drop-down to ‘select the time period’ to show the performance values of the selected device (based on the time period 15min/24hrs)

After selection of a connected device, first LTP is automatically populated, the application collects the received and centralized stored performance values for the selected device from the database and displays them in the table views based on the time period selected. (15min/24hours). Time-period is 15min by default.

To differentiate the performance values of the devices based on different aspects of performance, below seven different accordions/panels should be created with the respected data in its table view and over the table as chart.

  1. Performance Data
  2. Receive Level
  3. Transmission Power
  4. Adaptive Modulation
  5. Temperature
  6. Signal-to-interference-plus-noise ratio
  7. Cross Polar Discrimination

The table view implements the common ux-framework-table supporting sorting, filtering and pagination on the server. The chart is visualing the data of the actual table page.

Visualization

Main window


Once the network element is selected, below page is displayed.

when a panel is expanded it displays table and chart

Summary of functions:

  • Each data is provided by an own section
  • Each section contains in the lower part a table view and in the upper part a chart view
  • The data in the chart is showing the table data of the actual page as a chart
  • For big amount of data, the table is providing a pagination function and filter function
  • The number of table entries can be configured and/or the filtered to show specific information
  • The pagination provides a configuration of sleecting the number of entries in the range of 10 till 100 in four steps

Overview for one data entry, showing the table and the chart.


Data in the database

The performance values are stored on an ElasticSearch database. The REST-API is provided by the ApiGateway.

The index is “sdnperformance” the doctype is

  1. “historicalperformance15min”- when time-period is selected as 15min (has past     15min performance data of the device)
  2. “historicalperformance24h”- when time-period is selected as 24hours (has past 24hours performance data of the device)

Sections/ Panels

The following panels shows the tables with its respective data.

1) Performance Data

The “Performance Data” panel shows the table with the following columns:

  1. Radio Signal Id
  2. Scanner Id
  3. End Time
  4. Suspect Interval flag
  5. ES
  6. SES
  7. UAS

2)  Receive Level

The “Receive Level” panel shows the table with the following columns:

  1. Radio Signal Id
  2. Scanner Id
  3. End Time
  4. Suspect Interval flag
  5. Rx min
  6. Rx avg
  7. Rx max

3) Transmission Power

The “Transmission Power” panel shows the table with the following columns:

  1. Radio Signal Id
  2. Scanner Id
  3. End Time
  4. Suspect Interval flag
  5. Tx min
  6. Tx avg
  7. Tx max

4) Adaptive Modulation

The “Adaptive Modulation” panel shows the table with the following columns:

  1. Radio Signal Id
  2. Scanner Id
  3. End Time
  4. Suspect Interval flag
  5. col5-col36 – QAM2S,QAM2,QAM2L, QAM4S,QAM4,QAM4L, QAM16S,QAM16,QAM16L, QAM32S,QAM32,QAM32L, QAM64S,QAM64,QAM64L, QAM128S,QAM128,QAM128L, QAM256S,QAM256,QAM256L, QAM512S,QAM512,QAM512L, QAM1024S,QAM1024,QAM1024L, QAM2048S,QAM2048,QAM2048L, QAM4096S,QAM4096,QAM4096L, QAM8192S,QAM8192,QAM8192L,

5) Temperature

The “Temperature” panel shows the table with the following columns:

  1. Radio Signal Id
  2. Scanner Id
  3. End Time
  4. Suspect Interval flag
  5. Rf Temp min [deg; C]
  6. Rf Temp avg [deg; C]
  7. Rf Temp max [deg; C]

6) Signal-to-interference-plus-noise ratio (SINR)

The “Signal-to-interference-plus-noise ratio” panel shows the table with the following columns:

  1. Radio Signal Id
  2. Scanner Id
  3. End Time
  4. Suspect Interval flag
  5. SINR min [db]
  6. SINR avg [db]
  7. SINR max [db]

7) Cross Polar Discrimination

The “Cross Polar Discrimination” panel shows the table with the following columns:

  1. Radio Signal Id
  2. Scanner Id
  3. End Time
  4. Suspect Interval flag
  5. CPD min [db]
  6. CPD avg [db]
  7. CPD max [db]

Charts

The charts should be introduced to show the performance values in a line graph.

X axis: TimeStamp

Y axis: performance values

Example:


Implementation

  • GUI Framework: ONAP SDNR React framework
  • Used components:  react-chartjs-2
  • Accessor for getting data from sdnr database via Elasticsearch-Rest API
  • No labels