eLTE eNodeB Management

The capability of managing the eNodeBs in a unified manner is provided, implementing convergent management for wired and wireless networks.

Batch operations can improve the maintenance efficiency and reduce service costs. The in-depth and comprehensive eNodeB access management capability is provided.

• Performance Management

  By default, eSight offers key, major, and minor performance indicator templates. After devices are connected to eSight, collection tasks about key performance indicators (KPIs) are automatically added to collect performance data about network-wide devices.

  eSight supports 15 key performance counter templates, including eNodeB, link, RRU, board, cell, port, and carrier; and automatically creates one-hour performance collection tasks when eNodeBs are created. Users can also manually create and delete periodical detection tasks for eNodeBs at an interval less than one hour.

• Topology Management

  All features are supported. Virtual connections between base stations and service engine devices are displayed in the physical topology. The NE connection status and alarm status are updated in real time in the topology view. Right-click of an NE on the shortcut menu in the topology view, you can perform configuration synchronization, browse alarms, NE details, web NMS, MML command delivery, terminal list, and service channel diagnosis. Users can manually create radio links between devices in the topology view and display them in the topology view. In addition, users can monitor the link status to learn about the network topology and monitor network changes.

• NE Manager

  The NE manager allows users to manage:

  Key NE information models

  Physical resources such as NE attributes, boards, and ports

  Transmission resources such as IP interfaces, S1 interfaces, X2 interfaces, routes, Stream Control Transmission Protocol (SCTP) links, and IP paths

  Wireless resources such as remote radio units (RRUs), RRU chains, sectors, cells, operator information, and cell operator information

  The NE manager also allows users to check current and historical alarms of NEs as well as NTP server configuration.

• Device Software Upgrade

  Users can manage the following files on eSight:

  Version files

  Hot and cold patches

  BootRom files

  Configuration files

  Certificate files

  Users can update the software for multiple devices in a single task instantly or as scheduled.

  Users can also review historical upgrade tasks, monitor the execution status of current upgrade tasks, and control the number of concurrent upgrade tasks based on the file server egress bandwidth.

• MML Script

  eSight delivers MML scripts to multiple devices in batches. MML scripts contain MML commands and are used to perform service deployment for devices in batches. Users can manage script delivery tasks and view script execution reports to learn detailed results of each command executed on each device.

• Configuration Data Synchronization

  To ensure configuration data consistency between eSight and NEs, eSight supports automatic data synchronization after an NE configuration change and manual data synchronization. Users can check synchronization task progresses on the synchronization task management page, and use the NE manager to check common configuration parameters synchronized to eSight.

• User eRAN Monitor

  eSight traces specified target users over the entire network, monitors cross-eNodeB resource usage of users, and displays the monitoring results in graphs. Resource usage information includes cell combination, MCS count, downlink power control, uplink power control, throughput, RLC service volume, scheduling, signal channel quality, power headroom, BLER, and downlink RSRP/RSRQ reporting. Using this function, users can know device performance and system running information in real time.

• Signaling Trace

  By tracking, collecting, and graphically displaying the interface and link messages, such as IFTS trace and Cell DT trace. This function provides data to support routine maintenance, commissioning, and fault locating on devices.

• LMT Proxy

  Users can open the LMT web UI using eSight. If users and NEs are on two isolated networks, users cannot directly access the NEs through the LMT web UI. In this scenario, users can use the LMT proxy capability provided by eSight to access the NEs.

eLTE base station device management provides the capability to monitor and maintain base station devices. Figure 3-113 shows the principle.

Figure 3-113 Principle of the eNodeB device management

• An administrator connects a device. The connected device is displayed in the topology.
• The connected device reports an alarm to eSight.
• The eNodeB device can be monitored and maintained.

• When deployed on a standard-configuration server, eSight can manage a maximum of 500 eNodeBs.
• When deployed on a high-configuration server, eSight can manage a maximum of 2,000 eNodeBs.
  • Standard-configuration server: 12-core 2 GHz CPU, 32 GB memory, and 500 GB hard disk.
  • High-configuration server: 40-core 2 GHz CPU, 64 GB memory, and 1 TB hard disk.