Table of Contents
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
...
Below are the UI elements to be implemented.
- Drop-down Table (with table properties) to select the connected device/networkElement.
- Once the connected device is selected from the above drop-downtable, it should display the below four panels/accordions.
- Network Element
- Ethernet container
- Structure (pure ethernet)
- 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)
...
- LTPs associated with the selected network element.
- Once the LTP is selected below configurations should be displayed based on the LTP.
a) Ethernet Container: The
...
Ethernet Container
...
have the below different fields
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
...
v. Configuration
vi. Status
cb) Structure (pure ethernet): Structure when expanded should have six the below different panelsfields
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
...
v. Configuration
vi. Status
dc) AirInterface: AirInterface when expanded should have six the below different panelsfields
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
...
v. Configuration
vi. Status
...
The config values are available in restConf
<Incomplete documentation> Yet to be modified