ENodeB Integration Procedure Based Dual 20 for TDD-LTE

Ericsson InternalPROCEDURE 1 (22)

Prepared (also subject responsible if other) No.

CBC/PN/N Xiaolong YuApproved Checked Date Rev Reference

2011-06-09 PA1

eNodeB Integration Procedure for EAccess LTE

Contents

1 REVISION HISTORY..............................................................................................................3

2 PURPOSE..............................................................................................................................3

3 OVERVIEW OF THE ENODEB..............................................................................................3

3.1 Digital Unit LTE (DUL)....................................................................................................................................................5

3.2 Remote Radio Unit (RRU)................................................................................................................................................6

3.3 CPRI Connection...............................................................................................................................................................6

3.4 Synchronization.................................................................................................................................................................6

3.5 Sector..................................................................................................................................................................................7

3.6 Cell......................................................................................................................................................................................7

3.7 eNodeB diagram................................................................................................................................................................7

4 REQUISITES..........................................................................................................................9

4.1 Check Basic Package and CV presence in the eNodeB................................................................................................10

4.2 Setting Up a Serial Connection......................................................................................................................................10

4.3 Loading a Basic Package and Basic CV on the DUL 20..............................................................................................12

5 INITIAL ENVIRONMENT SETUP.........................................................................................15

6 LOAD MO SCRIPTS............................................................................................................15

6.1 Configure Transport and O&M Network....................................................................................................................15

6.2 Configure NTP/SYNC.....................................................................................................................................................16




2011-06-09 PA1

6.3 Configure Radio Network..............................................................................................................................................18

6.4 Configure EnodeBfunction and system_constant........................................................................................................19

6.5 Optional Feature Activation...........................................................................................................................................19

6.6 Install LKF File...............................................................................................................................................................19

6.7 Unlock EUtran Cells.......................................................................................................................................................22

6.8 Save new Configuration in ENodeB..............................................................................................................................22

7 References..........................................................................................................................22




2011-06-09 PA1

1 Revision History

Revision Date Responsable CommentPA1 2011-07-11 Exiaoyu Preliminary version

2 Purpose

This document describes the procedure for integration of eNodeB based Dual 20. The procedure is intended to start from the point where the eNodeB is powered up for the first time, to integration the basic software that comes from factory to the agreed software level (L11B), to install the needed capacity and feature license key file, and to use scripts to configure the eNodeB according to the Network Plan. The same procedure can also be used for the integration of the Field Trial sites.

3 Overview of the eNodeB

ENodeB: RBS (2.3GHz – Band40, 5/10/15MHz, 1x DUL, 1 x RRU(2Tx))

Software: L11B

Below is an overview of the eNodeB product “RBS 6601”. More information and detail about the HW can be obtained from the CPI “Generic Hardware RBS 6601”.

The figure below is an overview of the RBS6601 product:




2011-06-09 PA1




2011-06-09 PA1

The next figure shows the DUL board used in the RBS 6601:

3.1 Digital Unit LTE (DUL)

Provides switching, traffic management, timing, baseband processing and the radio interface to RU/RRU. The baseband capacity is pooled to support multiple sectors. Up to four DULs can be installed in a RBS.

DUL board functions:

Timing function

Loadable software

Downlink baseband processing

Uplink baseband processing

IP traffic management

Radio interface

Transmission handling




2011-06-09 PA1

Synchronization (GPS & NTP)

DUL board interfaces:

Marking Connector Description OpticalIndicator

PWR ET20 A -48 V DC Power NoGPS RJ45 GPS External interface NoEC RJ45 EC bus Internal interface No

AUX RJ45 Auxiliary Internal interface NoLMT A RJ45 Console Internal interface NoLMT B RJ45 Site LAN External interface YesTN A RJ45 Transmisson, Ethernet: External interface,

electricalYes

I - Information: Optical indicator, yellow YesO - Operation: Optical indicator, green YesF - Fault: Optical indicator, red Yes

IDL HSIO Inter-DU link: Internal interface, DU to DU NoTN B SFP Transmisson, Ethernet: External interface, optical Yes

RI F - RI A 6 x SFP Radio interface x 6

Internal interface between DU and RU, electricalExternal interface between DU and RRU, optical

Yes

3.2 Remote Radio Unit (RRU)

Refers to the physical hardware that serves a sector. Each radio unit is connected to antenna equipment. A radio unit can be physically located in the eNodeB cabinet, or it can be located externally to the eNodeB where it is referred to as a Remote Radio Unit (RRU), as it is the case with the RBS 6601. Up to six RRUs can be connected to a single DUL.

3.3 CPRI Connection

The Common Public Radio Interface (CPRI) connection provides the communications link between the digital unit and the radio unit. The CPRI standard allows the use of either electrical or optical interface cables. Electrical cables are used for radio units installed in the eNodeB cabinet and optical cables are used for remote radio units.

3.4 Synchronization

The LTE Digital Unit uses an external synchronization source for generating the required system clock signals. The method for synchronization is either via external Global Positioning System (GPS) equipment or via a Network Time Protocol (NTP) time server to provide synchronization via the IP transport interface.




2011-06-09 PA1

3.5 Sector

A geographical area spanned by the transmission angle from one or a group of antennas. The sector is configured to handle one specific frequency band. There may be up to three sectors per eNodeB.

3.6 Cell

Defined with its own carrier frequency and channels within the sector frequency band. There may be up to three cells per eNodeB. It is possible to configure only one cell per sector.

3.7 eNodeB diagram

Below is a diagram of the initial configuration of the eNodeB in EAccess Testbed, in case MIMO is not to be configured:




2011-06-09 PA1

If 2X2 MIMO is configured instead then this is what the eNodeB will look like:




2011-06-09 PA1

4 Requisites

The following tools/softwares are needed for the integration procedure:

A Thin Client (Windows or Linux laptop) with the latest version of Moshell installed

Putty software to be used for Serial / Telnet connection. It can be downloaded here for free, such as Putty/secureCRT:

A Text Edit tool (ex. UltraEdit)

An FTP Client/Server software. Recommended is Filezilla or WinSCP.

A cable for the serial connection (adapter RJ-45 to DSUB 9), Serial port sequency as below:

A crossed Ethernet cable, typically a Cat5 patch cable

MO Scripts containing all the parameters specific to the eNodeB(s) to be integrated. Naming convention for example as below:

1_giga.mo

2_1_transport.mo

2_2_transport.mo

2_3_transport.mo05_Cabinet.mo

3_TuSyncRef_s6_7.mo07_Feature_Activation.mos

4_AddSyncRef_GPS_s6_7.mo09_Tuning_S1.mo

5_radio_create.mo12_External_Relations.mo

6_EnodeBtransport.mo

10_set_system_constant.mo




2011-06-09 PA1

PA25.mo

Integration procedure

4.1 Check Basic Package and CV presence in the eNodeB

This paragraph will explain how to check if the Basic Package and CV are already present in the eNodeB. In case they are not already installed from factory then you will also learn how to upload them into the eNodeB.

4.2 Setting Up a Serial Connection

A serial-to-RJ45 adapter is required to connect to the DUL board.1. Connect the serial-to-RJ45 adapter to the communications port (COMx) of the Thin Client),the “x” need you check the device manager from your PC .

2. Connect the serial-to-RJ45 adapter to the serial port of the DUL board indicated as LMT A.

The connection is used for serial communication through a terminal program. the data as per figure below:




2011-06-09 PA1

The $ prompt is shown in screen indicating that a serial connection is established

Input the following commands:

// Check if “basic_cv” is present.

Note: if the basic CV and package are not present in the node, jump to 4 .1.2 to learn how to upload them into the eNodeB. Otherwise continue with the following steps.

// Check if “basic_cv” is set as the current CV // Check the default IP //Check hard drive C and D space




2011-06-09 PA1

4.3 Loading a Basic Package and Basic CV on the DUL 20

Note: perform the steps in this paragraph only if the Basic CV and Package are not present in the eNodeB. Otherwise jump to Chapter 6.

1. Formatting the Dual board Hard Drive

The eNodeB replies with the following information:

All data on volume will be destroyed. Continue? y/n (n):

Type y.


Formatting Hard Disc-OK !! RESTART system to initialize disc !!

Format the hard drive partition d, using the following command:


All data on volume will be destroyed. Continue? y/n (n):

Type y.


Formatting Hard Disc-OK !! RESTART system to initialize disc !!

Restart the eNodeB using the following command:

//login the backup mode

The info as below:




2011-06-09 PA1

2. Setting an IP Configuration

The Internet Protocol (IP) configuration is necessary for the FTP program and the eNodeBElement Manager (EM). The configuration in the eNodeB is set through the serial connection previously established.

Set the IP configuration using the “ifconfig” command, for example:

//Check had login the backup mode when you can find C2 not C

Check the IP configuration using the “ifconfig” command:

//Go back to basic mode




2011-06-09 PA1

3. Downloading the Basic Software and CV from the Thin Client to the DUL board

This section describes how to upload the basic software and CV to the DUL via FTP. The instructions are valid for most FTP clients.

Note: Use binary transfer mode in the FTP client for all file transfers.

1. Start the FTP client. 2. Connect to the eNodeB using the IP address assigned in the previous step.

3. Enter rbs as user name and rbs as password.

4. Transfer the directories /c2 and /d from the thin client to the root directory of the eNodeB.

5. Exit the FTP client when the file transfer is complete.

6. Restart the eNodeB using the following command:

//Check had login basic mode

//Check the ip address setting




2011-06-09 PA1

5 Initial environment setup

This chapter explains how to setup the eNodeB initial environment in order to make clear any alarm and can get the License file key(LFK) install to eNodeB.

Stop all your firewalls and configure the Thin Client IP Address to 192.168.1.102, Netmask to 255.255.0.0 Connect the Thin Client to the eNodeB port LMT B on the DUL board using the Ethernet cable. Open Moshell on the Thin Client and connect to the eNodeB used IP address 192.168.1.101. :

> secmode –f u> passwd ; rbs; {newpassword}> passwd ; {newpassword}; {newpassword}

6 Load MO Scripts

Stop all your firewalls and use Serial Connection to check the node ip address :ifconfig and configure your laptop IP Address to same subnet with node, Connect the Thin Client to the eNodeB port LMT B on the DUL board using the Ethernet cable.

Open Moshell and connect to the eNodeB example used IP address 192.168.1.102

Note: you need put the MO script under your moshell folder: /home/yourid/

6.1 Configure Transport and O&M Network

Load the following script to configure the TN and O&M links use the command list:: moshell x.x.x.x // the node IP address lt all trun /home/yourid/1_giga.mo trun /home/yourid/2_transport.mo trun /home/yourid/2_2_transport.mo




2011-06-09 PA1

cvms ecn_OK acc 0 manualrestart y 2 0 0 Wait the Dual return to normal status then do: moshell 192.168.1.101 lt all trun /home/yourid/2_3_ transport.mo

Note: S1 link will not be enabled until the RRUs have been defined.

Confirm connectivity to the S1 router, ping from IpAccessHostEt: > acc IpAccessHostEt=1 ping <S1 Default Router IP>

Confirm connectivity to the O&M router, ping from Command Line: > ping <O&M Default Router IP>

6.2 Configure NTP/SYNC

Load the following script to define the NTP/SYNC trun /home/yourid/3_TuSyncRef_s6_7.mo trun /home/yourid/4_AddSyncRef_GPS_s6_7 you can check the SYNC status used: get sync, you need wait about 10 minutes the clock status can change the STARTUP_MODE to LOCKED_MODE.the info as below:




2011-06-09 PA1




2011-06-09 PA1

6.3 Configure Radio Network

Load the following script to allow AutoConfiguration of RRU hardware.

Note: Once the script has executed the node should restart and may or may not automatically create a new CV. If a new CV is created confirm it has not been reloaded. If it has, reload the previous working CV and confirm that AutoConfiguration is enabled:

Load the following script to configure the RU hardware:

trun /home/yourid/5_radio_create.mo

Note: The RRU will only become enabled if the S1 link is enabled.




2011-06-09 PA1

6.4 Configure EnodeBfunction and system_constant

Load the following script to define the cabinet:

trun /home/yourid/6_EnodeBtransport.mo

trun /home/yourid/PA25.mo

trun /home/yourid/10_set_system_constant.mo

6.5 Optional Feature Activation

Define eNodeB UniqueLogicalName (fingerprint). Before the licenses can be activated use moshell a UniqueLogicalName must be defined in the eNodeB.

Note: ULN is detailed in the CDR or find it from LKF .

> sget SystemFunctions=1,Licensing=1 //Check existing setting > acc RbsConfiguration=1 setUniqueLogicalName //Enter UniqueLogicalName > sget SystemFunctions=1,Licensing=1 //Verify and Check new setting

6.6 Install LKF File

This paragraph explains how to install the License Key File into the eNodeB, in order to activate the Capacity Licenses and the Optional Features.

The License Key File is delivered as a zipped file. Save it somewhere in the Thin Client where it can be accessed from Moshell, for example:

/home/yourid/tmp/license/

Install LKF via Moshell with the below commands:

> acc licensing updateLicenseKeyFile

Check if LKF installation has been correctly performed with the following commands:

> get license> license server

There are some picture can be reference:




2011-06-09 PA1




2011-06-09 PA1




2011-06-09 PA1

6.7 Unlock EUtran Cells

Check the RRU and cell status and unlock them: >lt all >lst rru >lst cell

If the status are locked, you may unlock them: >ldeb rru >y >ldeb cell >y

6.8 Save new Configuration in ENodeB

Make a CV in the eNodeB to save the configuration and set it as startable. > al // Check the node alarm > cvms cell_ok > acc 0 manualrestart

7 References

CPI “Generic Hardware RBS 6601”

CPI “LTE RAN L11B”

Documents

ENodeB Integration Procedure Based Dual 20 for TDD-LTE