ACE Repeater NMS(R-NMS ) Functional Elements , Integration with R-JIO Network , Functional Flow and Integration Requirements from R-JIO
O&M Console
OTA Firmware Management.
Functional Flow of Registration and Start Up Process.
Functional Flow of Registration Configaration Download.
Functional Flow of Registration Configaration Download.
Functional Flow of Acknowledgment of Provided Cell.
Functional Flow of Acknowledgment of Provided Cell.
Functional Flow of Interference Reporting.
Functional Flow of Interference Reporting.
Proposed Integration Phases of the R-NMS
Phase 1: R-NMS and Repeater Integration
Description : Phase I goal for basic integration of repeater to the network and independently configurable in the network with no Dependencies.
R-JIO End Requirements :
- Basic XEON server( Based on Final Dimension) called as R-NMS server, OS based on R-JIO IT policy.
- 10GE / 1GE Optical Port to core O&M Network.
- One Repeater installed on the network in controlled environment.
- Static IP assigned to R-NMS server with all TCP/IP + UDP ports enabled for external Access.
- Two sample simcards.
- Accurate AIR Interface network monitoring Hardware + Software.
- One terminal workstation for config and Monitoring support system to work.
Phase 2: R-NMS and Repeater Volume Integration.
Description : Phase II goal for high-level functional integration of the network with volume compatibility of minimum of 20K Repeaters manageable in one instance.
R-JIO End Requirements :
- Permission of Additional PCIe Hardware in the TOR Rackspace.
- Database integration : Groupe License of any Database compatible in Windows and Linux.
- Static Span IP assigned of 256 IP to R-NMS server with all TCP/IP + UDP ports enabled for external Access.
- Permission for Testing on Air interface in Live.
Phase 3: R-NMS and Repeater Volume Integration on GIS.
Description : Phase III goal for full functional integration.
R-JIO End Requirements :
- R-JIO in a position to deploy 1K Units as a Trial
- O&M terminals of minimum 5#.