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

Compare with Current View Page History

« Previous Version 2 Next »

User documentation

The application shows the actual values of all attributes of the ONF-TR-532 for a selected physical network function (PNF). Each view of a functional element is divided into capabilities, configuration, status, current problem, current performance and history performance information according to TR-532.

A separate window is available for modifying the configuration. All changes made are sent to the device in a single NetConf bulk request. The operator is notified about successfully configuring the device.

Specification

“Configuration” User Interface should be implemented to show the capabilities, configuration, status, current problem, current performance and history performance information of the selected network element

The graphical user interface is structured according to ONF-TR-532

Below are the UI elements to be implemented.

  1. Drop-down to select the connected device/networkElement.
  2. Once the connected device is selected from the above drop-down, it should display the below four panels/accordions.
    1. Network Element
    2. Ethernet container
    3. Structure (pure ethernet)
    4. AirInterface



a)      Network element:  The view of network element when expanded is divided into three different panels.

    • LTP(ETH-CTP)
    • LTP(MWS-TTP)
    • LTP(MWPS-TTP)


b)     Ethernet Container: The view of Ethernet Container when expanded is divided into six different panels  

  i.     Capability

 ii.     Performance history: This should be a table view which has below fields

            a)  History-data-id
            b)  Granularity-period
            c)  Performance-data
            d)  Period-end-time
            e)  Suspect-interval-flag

          The Performance history data is available in the database in the below index.

          The index is “sdnperformance” the doctype “historicalperformance15min” and   “historicalperformance24h”

  iii.   Current performance

  iv.   Current problem list

  v.    Configuration

  vi.   Status


c)      Structure (pure ethernet): Structure when expanded should have six different panels

  i.     Capability

 ii.     Performance history: This should be a table view which has below fields

            a)  History-data-id
            b)  Granularity-period
            c)  Performance-data
            d)  Period-end-time
            e)  Suspect-interval-flag

          The Performance history data is available in the database in the below index.

          The index is “sdnperformance” the doctype “historicalperformance15min” and   “historicalperformance24h”

iii.     Current performance

iv.     Current problem list

v.      Configuration

vi.     Status


d)     AirInterface:  AirInterface when expanded should have six different panels

i.      Capability

ii.      Performance history: This should be a table view which has below fields

            a)  History-data-id
            b)  Granularity-period
            c)  Performance-data
            d)  Period-end-time
            e)  Suspect-interval-flag

          The Performance history data is available in the database in the below index.

          The index is “sdnperformance” the doctype “historicalperformance15min” and   “historicalperformance24h”

iii.    Current performance

iv.     Current problem list

v.      Configuration

vi.     Status


The config values are available in restConf

 <Incomplete documentation> Yet to be modified



  • No labels