Tuesday 2 October 2018

Self Configuration

Self-configuration strives towards the "plug-and-play" paradigm in the way that new base stations shall automatically be configured and integrated into the network. This means both connectivity establishment, and download of configuration parameters are software. Self-configuration is typically supplied as part of the software delivery with each radio cell by equipment vendors. When a new base station is introduced into the network and powered on, it gets immediately recognized and registered by the network. The neighboring base stations then automatically adjust their technical parameters (such as emission power, antenna tilt, etc.) in order to provide the required coverage and capacity, and, in the same time, avoid the interference.

Ideally a base station or cell that is to be added to an existing network deployment should configure itself, following a “plug & play” principle (self-configuration). Parameters usually configured manually by the network operator should be set automatically based on the measured radio conditions.

One of the first standardized SON features, related to the “self-configuration” category, is automatic neighbor relation (ANR). ANR significantly reduces the time required to set up a base station by automatically managing neighbor cell relations, thus replacing time-consuming manual setup. ANR relies on the mobile terminal’s capability to report cells that it has detected but that are not part of the neighbor list broadcasted by the LTE network.

Self-configuration process is defined as the process where newly deployed nodes (eNBs) are configured by automatic installation procedures to get the necessary basic configuration for system operation. Self-configuration process works in pre-operational state, which starts from when the eNB is powered up and has backbone connectivity until the RF transmitter is switched on. 

As shown in Figure, self-configuration includes two stages: basic setup and initial radio configuration. 
1. An IP address is allocated to the new eNB and the information of the Self configuration Subsystem of OAM (Operation and Management) is given to the eNB. 
2. A GW is configured for the new eNB so that the eNB can exchange IP packets with other internet nodes. 
3. The new eNB provides its information, including type, hardware and etc., to the Self-configuration Subsystem for authentication. Necessary software and configuration data are downloaded from the Self-configuration Subsystem. 
4. The new eNB is configured based on the transport and radio configuration data.
5. The new eNB connects to the normal OAM subsystems for other management functions. 6. S1 and necessary X2 interfaces are established


The self-configuration should take care of all soft-configuration aspects of an eNB once it is commissioned and powered up for the first time. It should detect the transport link and establish a connection with the core network elements, download and upgrade to the latest software version, set up the initial configuration parameters including neighbor relations, perform a self-test, and finally set itself to operational mode. In order to achieve these goals, the eNB should be able to communicate with several different entities.

The self-configuration actions will take place after the eNB is physically installed, plugged to the power line and to the transport link. When it is powered on, the eNB will boot and perform a self test, followed by a set of self-discovery functions, which include the detection of the transport type, tower-mounted amplifier (TMA), antenna, antenna cable length and auto-adjustment of the receiver-path.

After the self-detection function, the eNB will configure the physical transport link autonomously and establish a connection with the DHCP/DNS (dynamic host configuration protocol/domain name server) servers, which will then provide the IP addresses for the new node and those of the relevant network nodes, including serving gateway, mobility management entity (MME), and configuration server. After this, the eNB will be able to establish secure tunnels for operations, administration and maintenance (OAM), S1, and X2 links will be ready to communicate with the configuration server in order to acquire new configuration parameters