Recommendations Huawei Learning Website http://learning.huawei.com/en Huawei e-Learning n it o http://support.huawei.com/learning/NavigationAction!createNavi?navId=MW 000001_term1000025144&lang=en a c i if t r Ce http://support.huawei.com/learning/NavigationAction!createNavi?navId=_31 & &lang=en g in n Find Training ai r T i http://support.huawei.com/learning/NavigationAction!createNavi?navId=_trai e w ningsearch&lang=en a u H n More Information it o a c i f i t r Huawei learning APP e C & ng i in a r T ei w a Hu Huawei Certification 版权所有© 2018 华为技术有限公司 eNodeB LTE V100R013C10 Initial Configuration by MML Practice Guideica n it o (Cover) ISSUE 1.00 aw e n tio a c i if ei H w a u ai r T g n ni & rt e C Hu ra T i i n i ng & Ce f i t r Contents 1 eNodeB Data Configuration Preparation ..............................................................................1-4 1.1 Network Topology......................................................................................................................................... 1-4 1.2 Data Configuration Flow ............................................................................................................................... 1-5 1.3 Negotiated Data Preparation ......................................................................................................................... 1-5 n it o 1.4 LMT Tool ...................................................................................................................................................... 1-6 2 eNodeB Common Device Data Configuration .....................................................................2-7 a c i f 2-8 i 2.1.1 Task: Configuring eNodeB Basic Data ................................................................................................ t r 2-9 2.2 eNodeB Hardware Data Configuration ......................................................................................................... e C 2.2.1 Task: Configuring Cabinets and Subracks of the eNodeB ................................................................... 2-9 & 2.2.2 Task: Configuring Boards for the BBU.............................................................................................. 2-10 2.2.3 Task: Configuring RF Unit Data ........................................................................................................ 2-12 ng i 2.3 eNodeB Time and Clock Data Configuration ............................................................................................. 2-14 in a r 2.3.1 Task: Configuring Time Data ............................................................................................................. 2-14 T 2.3.2 Task: Configuring Clock Data ........................................................................................................... 2-15 ei w 3 eNodeB Transport Data Configuration ............................................................................... 3-16 a u 3.1 Low Layer IP Transport Data Configuration ............................................................................................... 3-17 H 3.1.1 Task: Configuring a Physical Port ...................................................................................................... 3-17 3.1.2 Task: Configuring a Service and OM IPn ............................................................................................ 3-18 o i t 3.1.3 Task: Configuring an IP Route ........................................................................................................... 3-18 a c 3.1.4 Task: Configuring VLAN................................................................................................................... 3-19 i f i t 3.2 High Layer Transport Data Configuration .................................................................................................. 3-19 r e 3.2.1 Task: (Optional) Configuring S1 Interface Data in Link Mode ......................................................... 3-19 C 3.2.2 Task: Configuring S1 Interface Data in Endpoint Mode .................................................................... 3-21 & S1 Interface Data in Endpoint Mode (Simplified Configuration) ........................ 3-23 3.2.3 Task: Configuring ng OM Channel Data ................................................................................................ 3-25 3.2.4 Task:iConfiguring in Data Configuration ......................................................................................4-25 a 4 eNodeB Radio Tr Data Configuration........................................................................................................................... 4-25 4.1i Sector e 4.1.1 Task: Configuring a Sector................................................................................................................. 4-26 w a 4.2 Cell Data Configuration .............................................................................................................................. 4-26 u 4.2.1 Task: Configuring a Cell .................................................................................................................... 4-27 H 2.1 eNodeB Basic Data Configuration ................................................................................................................ 2-7 4.3 *(Optional) Neighboring Cell Data Configuration ...................................................................................... 4-28 4.3.1 Task: Adding an Intra-Frequency Neighboring Cell .......................................................................... 4-28 4.3.2 Task: Adding an Inter-Frequency Neighboring Cell .......................................................................... 4-30 4.4 *(Optional) TDD Cell Configuration .......................................................................................................... 4-31 4.5 *(Optional) Massive MIMO Cell Configuration ......................................................................................... 4-33 5 eNodeB Script Verification ....................................................................................................5-37 5.1 Single-eNodeB Script Execution and Verification ...................................................................................... 5-37 5.1.1 Logging In to the eNodeB Using the U2000 Client in Web Mode .................................................... 5-37 5.1.2 Executing MML Scripts in Batches ................................................................................................... 5-38 5.2 Single-eNodeB Verification Experience...................................................................................................... 5-38 5.2.1 Procedure ........................................................................................................................................... 5-38 6 RAN Sharing Data Configuration ........................................................................................6-40 6.1 RAN Sharing with Common Carriers Data Configuration.......................................................................... 6-41 n it o 6.1.1 Task: Configuring RAN Sharing with Common Carriers Data .......................................................... 6-41 a c i if i n i ng aw e n tio a c i if ei H w a u ai r T g n ni & rt e C Hu ra T i & t r Ce 1 eNodeB Data Configuration Preparation About This Chapter The following table lists the contents of this chapter. Describes 1.1 Network Topology Know the topology of the lab network. 1.2 Data Configuration Flow Know the procedure of data configuration. 1.3 Negotiated Data Preparation Prepare the negotiated data. 1.4 LMT Tool LMT tool instruction. Know the topology of the lab networking. a c i if ei w a u ai r T g n ni rt e C n tio Figure 1-1 Topology of the lab networking Hu ra T i e aw Description & ng i n i 1.1 Network Topology H n it o Section & t r Ce a c i if Figure 1-2 Hardware configuration n it o a c i if 1.2 Data Configuration Flow i n i ng aw e n tio a c i if g n ni & rt e C i 1.3 Negotiated ra Data Preparation Hu T i Figure e 1-3 Control plane protocol stack w a Hu ra T i & t r Ce Figure 1-4 User plane protocol stack n it o a c i if This practice is based on the dedicated negotiated data. Use the planned data when you config the live network. 1.4 LMT Tool ng Figure 1-5 LMT offline MML login window i n i aw e n tio a c i if ei H w a u ai r T g n ni & rt e C Hu ra T i & t r Ce Figure 1-6 LMT offline MML configuration window n it o a c i if 2 eNodeB Common Device Data Configuration ra i n i T i e n & w a Hu About This Chapter tio ng t r Ce The following table lists the contents of this chapter. Section a c i if Describes Learn how to configure the basic data. rt e 2.2 eNodeB Hardware Data Configuration Learn how to configure the device hardware data. C &Data Configuration 2.3 eNodeB Time and Clock Learn how to configure the time and clock data. g in n i a r 2.1 eNodeB T Basic Data Configuration i e w Description a u H Learn how to configure the basic data 2.1 eNodeB Basic Data Configuration Reference LMT MML/U2000 Client, LMT Offline MML 2.1.1 Task: Configuring eNodeB Basic Data Table 2-1 Configuring eNodeB basic data Step Description Fulfilled 1 Log in the U2000 client or LMT MML, use DSP APP to check the application ID with application type set to be eNodeB. □Yes □No n it o a c i if 2 t r e □Yes (Optional) Add an application for the eNodeB if there is no specified application running C on the base station. & □No ng i in a r T ei w a Open LMT Offline MML, use this command to add u □Yes H an eNodeB function. □No n it o a c i f i t Set Network Element Name, Site r Location, Deployment Identifier, Site Name and □Yes e User Label. □No C & ng i in a r T eiAdd an operator. □Yes 3 4 w a u 5 H 6 □No Add tracking area configuration for the CN Operator. TAC is negotiated data, determined by the EPC. □Yes □No Step Description Fulfilled 7 Set special status of the NE. □Yes □No a c i if n it o 2.2 eNodeB Hardware Data Configuration i n i Description ra T i Learn how to configure the device hardware data. Reference ng & e aw u H 2.2.1 Task: Configuring Cabinets and Subracks of the eNodeB n o i Table 2-2 Configuring cabinets and subrackst of the eNodeB a c Step Description i f i t r 1 Add a cabinet. e C & ng i in a r T ei w a Hu2 Add a subrack for BBU. LMT Offline MML t r Ce Fulfilled □Yes □No □Yes □No Step Description Fulfilled n it o 3 a c i if (Optional for an RFU) Add a subrack for an RFU. i n i ng ra T i & t r □Yes Ce □No e w 2.2.2 Task: Configuring Boards for the BBU a u H Table 2-3 Configuring boards for the BBU n Step Description it o a 1 Add a UMPT board. c i f i t r e C & ng i in a r T ei w a Hu2 Add an LBBP board. Fulfilled □Yes □No □Yes □No Step Description Fulfilled n it o a c i if 3 (Optional) Add a UBBP board. g n ni ei n w a Hu ai r T & t r Ce □Yes □No tio 4 a c i (Optional) Add an LPMP board.if rt e C & ng i in a ra FAN board. Add T ei 5 aw Hu 6 Add a UPEU board. □Yes □No □Yes □No □Yes □No Step Description Fulfilled n it o a c i if 2.2.3 Task: Configuring RF Unit Data Table 2-4 Configuring RF unit data Step Description 1 Add an RRU chain. ni ng ei n w a Hu ai r T & t r Ce Fulfilled □Yes □No tio a c i if rt e Add an RRU (if the RFC unit is an RRU). & ng i in a r T ei Repeat this command to add more RRU chains. 2 H w a u □Yes □No Step Description Fulfilled n it o a c i if i n i ng e aw n Hu ra T i & t r Ce tio a c i if & rt e C Repeat this command to add more. 3 ni i ra T i e H ng Add an RFU, if the RF unit is an RFU. w a u □Yes □No Step Description Fulfilled n it o a c i if ng i n i e aw n Hu ra T i & t r Ce 2.3 eNodeB Time and Clock Data tio Configuration a c i if Description rt e C Learn how to configure the time and clock data. Reference i g n ni & LMT Offline MML 2.3.1 Task:raConfiguring Time Data T i e 2-5 Configuring time data Table w a Description Fulfilled 1 Set the time zone and the daylight saving time (DST) information about the NE. □Yes Step u H □No Step Description Fulfilled n it o 2 a c i if □Yes Set the time source. i n i ng Table 2-6 Configure clock data Step Description 1 Add a GPS. g n ni & C t er ai r SetTthe working mode of the reference clock source. ei 2 aw Hu 3 n Hu tio a c i if Set the clock synchronization mode of a BS. e aw 2.3.2 Task: Configuring Clock Data ra T i & t □No r Ce Fulfilled □Yes □No □Yes □No Fulfilled Step Description Fulfilled n it o a c i if 3 eNodeB Transport Data Configuration About This Chapter i n i ng ra T i The following table lists the contents of this chapter. & t r Ce Section Describes 3.1 Low Layer IP Transport Data Configuration Learn how to configure the layer 1, layer 2, and layer 3 transport data. 3.2 High Layer Transport Data Configuration Learn how to configure transport layer data. a c i f Figure 3-1 Network transport interfaces i t r e C & ng i in a r T ei aw UE n tio S1-C Uu eNB S1-U MME X2 OM eNB Hu e aw U2000 S-GW Hu Figure 3-2 S1 Interface & OM channel topology Client&..&2100 10.20.1.100/24 10.20.1.1 n it o 10.1.20.100/24 10.1.20.1 10.20.1.100/24 3.1 Low Layer IP Transport Data Configuration Description ra T i i n i ng & a c i if t r Ce e aw Learn how to configure the layer 1, layer 2, and layer 3 transport data. Reference n o i t Port 3.1.1 Task: Configuring a Physical a ic f i Table 3-1 Configure a physical port rt e Step Description C &port. 1 Configure an Ethernet ng i in a r T ei w a Hu Hu LMT Offline MML Fulfilled □Yes □No 3.1.2 Task: Configuring a Service and OM IP Table 3-2 Configure a service and OM IP Step Description Fulfilled 1 Add device IP addresses for control plane, user plane, and OM channel. □Yes □No n it o a c i if i n i 3.1.3 Task: Configuring an IP Route Table 3-3 Configuring an IP Route ra T i & e aw Step Description 1 Based on the actual network, multiple IP routes can be added to different destination IP by executing the following MML multiple times. on i ei H ng t r Ce w a u ai r T g n ni & C f i t er t a ic Hu Fulfilled □Yes □No 3.1.4 Task: Configuring VLAN Table 3-4 Configuring VLAN Step Description Fulfilled 1 Add an entry of mapping from a next-hop IP address to single VLAN. □Yes □No n it o a c i if 3.2 High Layer Transport Data Configuration Description ra T i Learn how to configure the high layer transport data. Reference LMT Offline MML n & e aw Hu i n i ng t r Ce 3.2.1 Task: (Optional) ConfiguringioS1 Interface Data in Link Mode f i t er t a ic Table 3-5 Configuring S1 interface data in link mode Step C Configure the user plane link: Add an IP path. & ng i in a r T ei 1 H Description Fulfilled □Yes □No w a u 2 Configure the control plane link: Add an SCTP link. □Yes □No Step Description Fulfilled n it o a c i if i n i ng 3 4 g n ni a c i if C t er ai r T the application type of the IP path for S1 interface. Add i e 5 aw Hu & n Hu tio Add an S1 interface. e aw Add a control port bearer. ra T i & t r Ce □Yes □No □Yes □No □Yes □No 3.2.2 Task: Configuring S1 Interface Data in Endpoint Mode Table 3-6 Configuring S1 interface data in endpoint mode Step Description Fulfilled 1 Configure the S1-C: Add an SCTP parameter template. □Yes □No n it o a c i if 2 i n i ng Configure the S1-C: Add an SCTP host. ei n w a Hu a Tr & t r Ce □Yes □No tio a c i if 3 & rt e C Configure the S1-C: Add an SCTP peer. i in a r ng □Yes □No T i e H w a u 4 Configure the S1-U: Add a user-plane host. □Yes □No Step Description Fulfilled 5 Configure the S1-U: Add a user-plane peer. □Yes □No a c i if n it o 6 i n i ng Add an endpoint group. n tio 7 Add the control-plane and user-plane hosts and control-plane and user-plane peers to the endpoint group. ei H w a u 8 a c i if ai r T g n ni Add an S1 object. & C t er □Yes □No e aw Hu ra T i & t r Ce □Yes □No □Yes □No Step Description Fulfilled n it o a c i if t 3.2.3 Task: Configuring S1 Interface Data in Endpoint Mode (Simplified r Configuration) Ce ng & Simplified configuration is suitable when the S1 control plane and user plane of the eNodeB use the same IP address. Set the global transport parameters using the SET GTRANSPARA command, and then set S1 and SCTPHOST MOs. The eNodeB then automatically generates USERPLANEHOST and EPGROUP MOs, and adds them to the EPGROUP MO. i n i e aw n Hu ra T i tio a c i if & rt e C g n i The MOs in n need to be manually configured. The MOs in black are automatically generated by the i redeNodeB eNodeB.a The automatically adds MOs to the EPGROUP MO, without manual intervention. r T i Table e 3-7 Configuring S1 interface data in endpoint mode (simplified configuration) w Description Step Fulfilled a u H 1 Set the global transport parameters, where the End Point Configure Mode parameter □Yes must be set to S1SIMPLE_MODE. □No Step Description Fulfilled n it o a c i if ng ni 2 & t r Ce Configure the S1-C: Add the SCTP host, and enable the simplified configuration mode. ei n w a Hu ai r T □Yes □No tio a c i if 3 Add an S1 object. g in in a r T i e H w a u & rt e C □Yes □No 3.2.4 Task: Configuring OM Channel Data Table 3-8 Configuring OM channel data Step Description Fulfilled 1 Add a remote maintenance channel. □Yes □No n it o a c i if i n i 4 eNodeB Radio Data Configuration n Hu ra T i & e aw About This Chapter ng t r Ce The following table lists the contents of this chapter. Section 4.1 Sector Data Configuration f i t r ica tio e C 4.3 *(Optional) Neighboring Cell Data Configuration & ng i in Configuration 4.1 Sector aData r T Description ei wLearn how to configure sector data. a Hu 4.2 Cell Data Configuration Reference LMT Offline MML Describes Learn how to configure sector data. Learn how to configure cell data. Learn how to configure a neighboring cell. 4.1.1 Task: Configuring a Sector Table 4-1 Configuring a sector Step Description Fulfilled 1 Add a sector. □Yes □No n it o a c i if i n i ng Repeat this command to add more sectors. 2 Add a set of sector equipment. on i ei H w a u ai r T g n ni & f i t er t a ic C Repeat this command to add more sets of sector equipment. 4.2 Cell Data Configuration Description Learn how to configure cell data. e aw Hu ra T i & t r Ce □Yes □No Reference LMT Offline MML 4.2.1 Task: Configuring a Cell Table 4-2 Configuring a cell Step Description Fulfilled 1 Add a cell. □Yes n it o a c i if □No i n i ng e aw n Hu ra T i & t r Ce tio a c i if & g n i Repeat this n command to add more cells. i a Bindr the cell with the sector equipment. T ei 2 H rt e C w a u □Yes □No Step Description Fulfilled Repeat this command to add more bind the cell with the sector equipment. 3 □Yes Add an operator for the cell. □No n it o a c i if i n i ng e aw Repeat this command to add an operator for the other cell. 4 Activate the cell. on Hu ra T i i f i t er t a ic & t r Ce □Yes □No Repeat this command to activate another cell. & C g 4.3 *(Optional)nNeighboring Cell Data Configuration ni i Description ra T Learn ei how to configure a neighboring cell. w a Reference Hu LMT Offline MML 4.3.1 Task: Adding an Intra-Frequency Neighboring Cell Step Description Fulfilled 1 Add an external E-UTRAN cell. □Yes □No Step Description Fulfilled n it o a c i if 2 (Optional) Add an additional PLMN ID for an external E-UTRAN cell. Add the neighbor relationship with an intra-frequency E-UTRAN cell. n it o a c i if ei H Hu w a u ai r T g n ni & rt e C & □Yes □No e aw 3 ra T i i n i ng t r Ce □Yes □No 4.3.2 Task: Adding an Inter-Frequency Neighboring Cell Step Description Fulfilled 1 Add an external E-UTRAN cell. □Yes □No n it o a c i if 2 ra T i (Optional) Add an additional PLMN ID for an external E-UTRAN cell. e w a Hu n o i Add a neighboring E-UTRAN frequency. t a ic f i rt e C & ng i in a r T eiAdd the neighbor relationship with an inter-frequency E-UTRAN cell. 3 4 H w a u i n i ng & t r Ce □Yes □No □Yes □No □Yes □No Step Description Fulfilled n it o a c i if i n i ng 4.4 *(Optional) TDD Cell Configuration Step Description 1 Add a TDD LBBP Board. ic f i rt i at ei H w a u 2 ai r T g n ni Add a TDD RRU. & on e aw Hu ra T i & t r Ce Fulfilled □Yes □No Ce □Yes □No Step Description Fulfilled n it o a c i if i n i ng e aw n Hu ra T i & t r Ce tio a c i if 3 Add a TDD cell. ei H w a u ai r T g n ni & rt e C □Yes □No Step Description Fulfilled n it o a c i if i n i ng e aw n Hu ra T i & t r Ce tio a c i if rt e C & MIMO Cell Configuration 4.5 *(Optional) Massive ai r T g n ni Massive MIMO is a leading multiple-antenna technology and a key technology for 4.5G. It features the use of massive antenna arrays (up to 64 antenna arrays) on a single eNodeB for 3D beamforming and multi-user multiplexing. This technology reduces the demand for site resources, improves network coverage, and enhances user experience with various services. ei H w a u Traditional multiple-antenna technologies support beam adjustment only on the horizontal plane. Massive MIMO, in contrast, supports adjustment of broadcast beams and downlink traffic beams in both the horizontal and vertical planes, significantly enhancing system coverage. Massive MIMO supports multi-user spatial multiplexing using up to 8 layers in the uplink and 16 layers in the downlink, significantly improving system capacity. n it o a c i if i n i ng ra T i & t r Ce e aw u H Massive MIMO mainly aims to improve cell coverage and capacity. A massive MIMO site can be deployed on new sites or by reconstructing existing sites. Massive n MIMO is typically deployed in hotspot areas and for o covering tall buildings. ti a Massive MIMO requires the deployment of the UMPTe, UBBPe, and 64T64R AAU. The MML commands iaccommon f of the UMPTe are the same as that iof main control board. The following describes how to t configure the UBBP, AAU, cellrand massive MIMO. e C Step Description Fulfilled & 1 Configure a UBBP, □Yes g with the CPRI interface type set to XCI_QSFP. n □No ni i ra T ei w a Hu 2 Add an RRU chain between BBU and AAU, with the topology type set to TRUNK_CHAIN. □Yes □No Step Description Fulfilled n it o 2 i n i 3 ica tio Configure a sector with the number of antennas set to 0. 4 ai r T g n ni & f i t er □Yes □No C Configure a set of sector equipment with the antenna configuration mode set to BEAM. ei w a u 5 n Hu ra T i & e aw H t r □Yes Ce □No Configure a 64T64R AAU with the RRU type set to AIRU and the numbers of TX and RX channels set to 0. ng a c i if Activate a weight database file for a beamforming antenna. □Yes □No □Yes □No Step Description Fulfilled 6 Add an antenna device. □Yes □No n it o a c i if i n i ng 7 Add a TDD cell with 64T64R and enhanced compression. n tio a c i if ei H w a u ai r T g n ni & rt e C w a Hu e ra T i & t r Ce □Yes □No Step 8 Description Fulfilled Set the weight number of the cell sector equipment to the same value as the antenna device number. i n i ng 5 eNodeB Script Verification ion t a ic a c i if □Yes □No t r Ce e aw Hu ra T i & n it o 5.1 Single-eNodeB Script Execution and Verification f ti r 5.1.1 Logging In to the eNodeB Using the U2000 Client in Web Mode Ce Enter the following address & in the address box of the Internet Explorer: https://U2000_IP address/eNodeB_omIP/. nghttps://10.77.199.42/10.20.9.94/ in Microsoft Windows 7 or Windows 8 operating system, i For example, enter in or enter https://10.77.199.42/10.20.9.94/ in Microsoft Windows XP operating system. a r Tto the Web LMT using the default user name admin and password hwbs@com. Log in i e w a u H Figure 5-1 Logging in to the eNodeB using the OMC in web mode n it o a c i if i n i ng 5.1.2 Executing MML Scripts in Batches Figure 5-2 Executing MML scripts in batches n ra T i e aw Hu tio a c i if ai r T g n ni & rt e C i e 5.2w Single-eNodeB Verification Experience a Hu5.2.1 Procedure 1. Run the DSP CELL command to check whether Cell Status is Normal %%DSP CELL: LocalCellId=72;%% RETCODE = 0 Operation succeeded. Display dynamic parameters of cells ----------------------------------Local Cell ID = 72 Cell Name = 0 & t r Ce Cell instance state = Reason for latest state change = Normal Cell setup succeeded. Cell latest setup time = 2018-04-25 11:52:44 Cell latest setup operate type = Act Cell Cell latest remove time = 0000-00-00 00:00:00 Cell latest remove operate type = No Operation Cell power save state = Uninstall Symbol shutdown state = Uninstall Anti Interfere Status in High Speed Scenario = Disable Primary BBP information = 0-0-2 Cell topology type = Basic Type Maximum transmit power(0.1dBm) = 400 n it o a c i if (Number of results = 1) Information About the RF module and BBP Serving the Cell -------------------------------------------------------- t r Ce eNodeB ID RF Module Information TX Channel No. RX Channel No. Served BBP Information Work Status MPT information 8787 0-62-0 R0A-R0B R0A-R0B ni & 0-0-2 Normal i a r Run the DSP BRDVER command to check whether the version T number of the board is displayed. If the i version number is displayed, it indicates that the board status is normal e w a u H n it o a c i f i t r e C & ng i in a Tr 0-0-7 (Number of results = 1) 2. ng %%DSP BRDVER:;%% RETCODE = 0 Operation succeeded. Result of current board software query -------------------------------------- Cabinet No. Subrack No. Slot No. Type Application Type Software Version BootROM Version 0 0 Hardware Version Operation Result 0 UTRP Node 500.007.10.000 96 00.317.01.001 Operation succeeded. 0 0 1 WBBP NodeB 200.019.10.000 17955 01.017.01.002 UMPT Node 500.007.10.000 2576 00.010.01.003 UMPT GBTS 100.019.10.000 2576 00.010.01.003 UMPT NodeB 200.019.10.000 2576 00.010.01.003 UMPT eNodeB 100.012.10.000 2576 00.010.01.003 Operation succeeded. 0 0 6 Operation succeeded. 0 0 6 Operation succeeded. ei Hu aw 0 0 6 Operation succeeded. 0 0 6 Operation succeeded. 0 0 16 FAN NULL 3 FAN.0 NULL 19 UPEU NULL NULL NULL NULL Operation succeeded. 0 0 Operation succeeded. (Number of results = 8) 3. Run the DSP S1INTERFACE command to check the status of the S1-C interface. %%DSP S1INTERFACE:;%% RETCODE = 0 Operation succeeded. Display S1 Interface Information -------------------------------S1 Interface ID = 0 S1 Interface CP Bearer ID = 0 CN Operator ID = 0 MME Release = Release 9 S1 Interface Is Blocked = FALSE Control Mode = MANUAL_MODE Auto Config Flag = Manual Created MME Selection Priority = 255 CN Operator Sharing Group ID = 255 S1 Interface State = Normal S1 CP Bearer State = Normal MME Is Overloaded = FALSE S1 Interface User Number = 0 MME Name = NULL Served PLMNs = 460-01 n it o a c i if Served GUMMEIs = 460-01-32769-1 MME Relative Capacity = 255 S1 Interface Fault Reason = NULL i n i (Number of results = 1) 4. ng ra T i & t r Ce Run the DSP IPPATH command to check the status of the S1-U interface (link mode). %%DSP IPPATH: PATHID=0;%% RETCODE = 0 aw DSP IP Path Result TX Bandwidth(kbit/s) Hu = 0 RX Bandwidth(kbit/s) = 0 Non-Realtime Reserved TX Bandwidth(kbit/s) = 0 Non-Realtime Reserved RX Bandwidth(kbit/s) = 0 Realtime TX Bandwidth(kbit/s) = 0 Realtime RX Bandwidth(kbit/s) = 0 -----------------Path ID n tio i ra e Operation succeeded. a c i if t er C = 0 Non-Realtime TX Bandwidth(kbit/s) = 0 Non-Realtime RX Bandwidth(kbit/s) = 0 Transport Resource Type = High Quality IP Path Check Result = IP Path Check Disabled IPMUX Switch Flag = Disable Service Type = NULL Fault Generation Time = NULL ni ng & T i e Sharing Data Configuration 6 RAN w ua (Number of results = 1) H About This Chapter The following table lists the contents of this chapter. Section Describes 6.1 RAN Sharing with Common Carriers Data Learn how to configure RAN sharing with common Section Describes Configuration carriers data. 6.1 RAN Sharing with Common Carriers Data Configuration Description n it o Learn how to configure RAN Sharing with Common Carriers data. a c i if Reference LMT MML Figure 6-1 RAN sharing with common carriers i n i ng e aw n Hu ra T i & t r Ce tio a c i if g & rt e C 6.1.1 Task: Configuring RAN Sharing with Common Carriers Data in in a Figure r 6-2 Configuring RAN sharing with common carriers data T i Step e Description w Modify the eNodeB sharing mode. 1a Hu 2 Configure the primary and secondary operators. The primary operator must be added Fulfilled □Yes □No □Yes Step 3 Description Fulfilled before the secondary operators are added. □No Add a tracking area for the eNodeB. □Yes a c i if □No 4 Add a cell operator. g n ni ei n w a Hu ai r T & t r Ce □Yes □No tio a c i if g in 5 & rt e C Configure the number of active users. in a r □Yes □No T i e H w a u 6 Configure the traffic volume. □Yes □No 7 Set the traffic sharing type. n it o □Yes □No Step Description Fulfilled 8 Set the portion of traffic of different operators. □Yes □No n it o a c i if i n i ng aw e n tio a c i if ei H w a u ai r T g n ni & rt e C Hu ra T i & t r Ce eNodeB LTE V100R013C10 Initial Configuration by CME Practice Guide e aw u ISSUEH1.00 ic f i rt i n ni ei H w a u a Tr g & Ce io t a n ra T i i n i ng & r e C a c i tif tio n Contents 1 Laboratory Networking Introduction ....................................................................................1-1 1.1 Lab Networking ............................................................................................................................................ 1-1 2 Customizing the Summary Data File .....................................................................................2-2 2.1 Task: Logging In to the U2000 ...................................................................................................................... 2-2 tio 2.2 Task: Customizing the Summary Data File Base on the Transmission Scenario .......................................... 2-3 a c i f 3-16 i t 3.1 Task: Filling in the Common Data Sheet..................................................................................................... r e 3.2 Task: Filling in the Transport Data Sheet .................................................................................................... 3-18 C 3.3 Task: Filling in the Radio Data Sheet .......................................................................................................... 3-19 & 3.4 Task: Filling in the DevIPPattern Sheet ...................................................................................................... 3-21 g n i 3.5 Task: Filling in the IPRoutePattern Sheet.................................................................................................... 3-22 in 3.6 Task: Filling in the VLANMAPPattern Sheet ............................................................................................. 3-23 a r 3.7 Task: Filling in the Auto Deployment Sheet ............................................................................................... 3-23 T i e 4 Creating eNodeBs .................................................................................................................... 4-23 w a 4.1 Task: Creating a Single eNodeB.................................................................................................................. 4-24 u 4.1.1 Creating the CME Planned Area ........................................................................................................ 4-24 H 4.1.2 Creating Initial Data of a Single eNodeB........................................................................................... 4-25 n 4.1.3 Configuring eNodeB Data ................................................................................................................. 4-26 it o 4.1.4 Checking eNodeB Data and Exporting a Data...................................................................................... 4-28 c i 4.2 Task: Creating eNodeBs in Batches f ............................................................................................................ 4-30 i t r Data..................................................................................................... 4-30 4.2.1 Importing eNodeB Summary e 4.2.2 Checking eNodeBC Data and Exporting Data...................................................................................... 4-30 & ng i in a r T ei w a Hu 2.3 Task: (Optional) Basic Edit Operation on Summary Data File ................................................................... 2-11 3 Filling in the Summary Data File .........................................................................................3-15 n Figures Figure 1-1 Lab networking ................................................................................................................................. 1-1 Figure 1-2 Hardware configuration and slot assignment .................................................................................... 1-1 tio i n i ng e aw ic f i rt i n ni ei H w a u a Tr g & Ce io t a n Hu ra T i & r e C a c i tif n Tables Table 2-1 Logging in to the U2000 MBB server ................................................................................................ 2-2 Table 2-2 Customizing the summary data file .................................................................................................... 2-3 Table 2-3 Customizing the summary data file .................................................................................................. 2-11 Table 3-1 CnOperator ....................................................................................................................................... 3-16 tio Table 3-2 MME information ............................................................................................................................. 3-16 a c i f 3-17 Table 3-4 Time source ...................................................................................................................................... i t r 3-17 e Table 3-5 Network time protocol ...................................................................................................................... C Table 3-6 Time zone and daylight saving time ................................................................................................. 3-17 & g Table 3-7 System clock..................................................................................................................................... 3-17 in n Table 3-8 GPS clock information ..................................................................................................................... 3-17 i a r Table 3-9 eNodeB data ..................................................................................................................................... 3-18 T i Table 3-10 Ethernet port attribute ..................................................................................................................... 3-18 e w a Table 3-11 IP address ........................................................................................................................................ 3-18 u H Table 3-12 GPS Info ......................................................................................................................................... 3-18 Table 3-13 IP route (part 1)............................................................................................................................... 3-19 n o i t Table 3-14 IP route (part 2)............................................................................................................................... 3-19 a c Table 3-15 LTE cell basic parametersfi(part 1) .................................................................................................. 3-19 i t r Table 3-16 LTE cell basic parameters e (part 2) .................................................................................................. 3-19 C Table 3-17 LTE cell basic parameters (part 3) .................................................................................................. 3-20 & parameters (part 4) .................................................................................................. 3-20 Table 3-18 LTE cell basic g n i Table 3-19 LTE n cell basic parameters (part 5) .................................................................................................. 3-20 i Table 3-20 ra LTE cell basic parameters (part 6) .................................................................................................. 3-20 T i 3-21 LTE cell basic parameters (part 7) .................................................................................................. 3-21 eTable Table 3-3 S-GW information ............................................................................................................................ 3-16 H w Table 3-22 Cell sector equipment parameters................................................................................................... 3-21 a u Table 3-23 DevIPPattern sheet (part 1) ............................................................................................................. 3-21 Table 3-24 DevIPPattern sheet (part 2) ............................................................................................................. 3-21 Table 3-25 IPRoutePattern sheet (part 1) .......................................................................................................... 3-22 Table 3-26 IPRoutePattern sheet (part 2) .......................................................................................................... 3-22 Table 3-27 IPRoutePattern sheet (part 3) .......................................................................................................... 3-22 Table 3-28 VLANMAPPattern Sheet ............................................................................................................... 3-23 n Table 3-29 PnP Parameters ............................................................................................................................... 3-23 Table 4-1 Creating the CME planned area ........................................................................................................ 4-24 Table 4-2 Creating initial data of a single eNodeB ........................................................................................... 4-25 Table 4-3 Configuring eNodeB Data ................................................................................................................ 4-26 Table 4-4 Checking eNodeB data and exporting Data ...................................................................................... 4-28 Table 4-5 Importing eNodeB summary data ..................................................................................................... 4-30 tio Table 4-6 Checking eNodeB data and exporting data....................................................................................... 4-30 i n i ng e aw ic f i rt i n ni ei H w a u a Tr g & Ce io t a n Hu ra T i & r e C a c i tif n 1 Laboratory Networking Introduction About This Chapter The following table lists the contents of this chapter. Section Description 1.1 Lab Networking Describe introduction to the lab networking. 1.1 Lab Networking tio i n i Figure 1-1 Lab networking e aw ic f i rt i n ni a Tr g & io t a n Hu Ce Figure 1-2 Hardware configuration and slot assignment ei H w a u ng 1-1 ra T i & r e C a c i tif n 2 Customizing the Summary Data File About This Chapter The following table lists the contents of this chapter. Section Description 2.1 Task: Logging In to the U2000 Describes how to use the U2000 MBB client to log in to U2000 MBB server. 2.2 Task: Customizing the Summary Data File Base on the Transmission Scenario Describes how to customize a summary data file base on the transmission scenario on the CME. 2.3 Task: (Optional) Basic Edit Operation on Summary Data File Describes how to edit the summary data file on the CME. i n i 2.1 Task: Logging In to the U2000 e aw Table 2-1 Logging in to the U2000 MBB server Hu ra T i & Step Description 1 On the PC, click Start > iManager U2000 MBB Client > U2000 MBB Client. Input the user name, password and server IP address, and click Login. ic f i rt n ni i ei H ng r e C w a u a Tr g & io t a n Ce 2-2 tio a c i tif Fulfilled □Yes □No n 2.2 Task: Customizing the Summary Data File Base on the Transmission Scenario Table 2-2 Customizing the summary data file Step Description Fulfilled 1 On the U2000 MBB client, click CME > Advanced > Customize Summary Data File. □Yes □No i n i ng e aw ra T i & r e C a c i tif u H Open a default summary data file that is released with the CME product or a customized one. n it o a c i f i t r e C & ng i in a r T ei H w a u Click the red zone, and select the transmission scenario. 2-3 tio □Yes n Step Description Fulfilled □No tio i n i ng e aw ic f i rt i n ni ei H w a u a Tr g & io t a n Ce 2-4 Hu ra T i & r e C a c i tif n Step Description Fulfilled 2 Select the NE transport configuration mode. □Yes □No tio i n i ng e aw io t a n Hu ra T i & r e C a c i tif Select the Base station Port Type and set the port count. ic f i rt i n ni ei H w a u a Tr g & Ce Set the Base station IP Count and select the Vlan Mode. 2-5 □Yes n Step Description Fulfilled □No tio i n i ng Set the Base station Interface IP Type. ic f i rt i n ni ei H w a u a Tr g & io t a e aw n Hu ra T i & r e C a c i tif Ce □Yes Set the Base station EPGroup. □No 2-6 n Step Description Fulfilled tio i n i ng Add the IP of SCTPHost. ic f i rt i n ni ei H w a u a Tr g & e aw io t a n Hu ra T i & r e C a c i tif Ce □Yes Add the IP of UserPlaneHost. □No 2-7 n Step Description Fulfilled tio i n i ng Set the S1/X2 Count. ic f i rt i n ni ei H w a u a Tr g & e aw io t a n Hu ra T i & r e C a c i tif Ce □Yes Set the EPGroup used by RAT. □No 2-8 n Step Description Fulfilled tio i n i ng Set the IP of OMCH. ic f i rt i n ni ei H w a u a Tr g & e aw io t a n Hu ra T i & r e C a c i tif Ce Select the Base station reference clock source. □Yes □No 2-9 n Step Description Fulfilled tio i n i ng Finish the customization task. ic f i rt i n ni ei H w a u a Tr g & e aw io t a n Ce 2-10 Hu ra T i & r e C a c i tif n 2.3 Task: (Optional) Basic Edit Operation on Summary Data File Table 2-3 Customizing the summary data file Step Description Fulfilled 1 On the U2000 MBB client, click CME > Advanced > Customize Summary Data File. □Yes □No tio i n i ng e aw Hu ra T i & r e C Open a default summary data file that is released with the CME product or a customized one. ic f i rt i n ni ei H w a u a Tr g & io t a n Ce 2-11 a c i tif n Step Description Fulfilled □Yes □No tio i n i ng 2 Edit the summary data file as needed. Modify the group name or the summary data name. ic f i rt i n ni ei H w a u a Tr g & io t a n Ce Modify an attribute. 2-12 w a Hu e ra T i & r e C a c i tif □Yes □No n Step Description Fulfilled tio i n i ng ic f i rt i n ni ei H w a u a Tr g & e aw Move lists up or down. io t a n Hu ra T i & r e C Ce Select the related tree node to locate the list in the right table to the corresponding node of the left tree. 2-13 a c i tif n Step Description Fulfilled tio i n i ng Add and delete some attribute references in the below table. e aw ic f i rt i n ni ei H w a u 3 a Tr g & io t a n Hu ra T i & r e C a c i tif Ce Set whether the Parameters display in the LLD template or not. □Yes □No 2-14 n Step Description Fulfilled tio 4 & r e C Save the completed customized summary data file as a data template for later data filling in. g n ni e aw ic f i rt n ni g & io t a n Hu ai r iT a c i tif □Yes □No Ce ai r T in the Summary Data File 3 Filling i e w a u H About This chapter The following table lists the contents of this chapter. Section Description 3.1 Task: Filling in the Common Data Sheet Describes how to fill in the common data sheet according to the network structure. 3-15 n Section Description 3.2 Task: Filling in the Transport Data Sheet Describes how to fill in the transport data sheet according to the network structure. 3.3 Task: Filling in the Radio Data Sheet Describes how to fill in the radio data sheet according to the network structure. 3.4 Task: Filling in the DevIPPattern Sheet Describes how to fill in the DevIPPattern sheet according to the network structure. 3.5 Task: Filling in the IPRoutePattern Sheet Describes how to fill in the IPRoutePattern sheet according to the network structure. 3.6 Task: Filling in the VLANMAPPattern Sheet Describes how to fill in the PnP Parameters according to the network structure. 3.1 Task: Filling in the Common Data Sheet i n i Open a user-defined summary data file. Fill the common data in the following tables. e aw Table 3-1 CnOperator u H *CN Operator type n o i t CNOPERATOR_PRIMARY a ic f i rt CnOperator *CN Operator ID *CN Operator name 0 0 & ng ra T i & r e C tio a c i tif *Mobile country code *Mobile network code 441 00 Ce Table 3-2 MME information MME Info *SCTP Peer ID ai g r176.11.180.10 T i First Peer IP Address Mask Second Peer IP Address Second Peer IP Address Mask e 0 aw Hu n ni *First Peer IP Address *Peer SCTP Port No. 36412 Table 3-3 S-GW information S-GW Info *User Plane Peer ID *Peer IP Address 0 176.11.41.100 3-16 Peer IP Address Mask n Table 3-4 Time source Time Source Time Source NTP tio Table 3-5 Network time protocol Network Time Protocol a c i tif *IPv4 Address NTP IP Port of NTP Server Mask Number Synchronization Authentication Authentication Authentication Master Period(min) Mode Key Key Index Flag 10.175.165.166 30 123 PLAIN i n i Table 3-6 Time zone and daylight saving time Time Zone and Daylight Saving Time *Time DST Tag DST DST DST DST Start DST Start DST Zone Information Start Start Start Week Mode Month Day Weekday Sequence GM NO T+0 800 ic f i rt e C System Clock Link Management & Source Clock Working Clock ngNo. Mode i in 0 MANUAL a r T ei wTable 3-8 GPS clock information a Hu Table 3-7 System clock ng e w a Hu ra T i DST DST DST DST End DST End DST Start End End End Week Weekday End Time Mode Month Day io t a n Sequence & r e C Slave DST Time Offset(min) Difference(min) Time Selected Clock Source Clock Synchronization Mode Quality Level GPS TIME QL-SSU-B GPS Clock Link Management GPS Clock No. Cabinet No. Subrack No. Slot No. GPS Work Mode Priority 0 0 0 7 GPS 4 3-17 n 3.2 Task: Filling in the Transport Data Sheet Fill in the Transport data in the following tables. Table 3-9 eNodeB data eNodeB *eNodeB *eNodeB *Product Cabinet Name ID Type Type 196.11.11 611112 .12 Mode *eNodeB Template DBS3900 VIRTUAL TDD _LTE Base Station BTS *eNodeB Configuration Design Radio File Template DBS3900_Vir tual_TDD_S1 11_8T8R Ethernet Port *Port No. *Port Attribute *Speed 1 AUTO AUTO ic f i rt Table 3-11 IP address IP address *IP 1 176.11.11.12 i n ai r T i ng & Ce io t a n 255.255.255.0 Table 3-12 GPS Info e w a Length(m) Cable u H GPS Clock Link Management 0 3-18 e w a Hu *IP 1 Mask g n ni Table 3-10 Ethernet port attribute ai r iT io t 611112 Radio_TDD a _SA2 ic f i t r e C & *Duplex AUTO n Table 3-13 IP route (part 1) IPRoute Destination IP1 Destination Mask1 Next Hop IP Address1 177.12.164.100 255.255.255.255 177.11.12.1 VLAN ID1 VLAN Priority1 tio a c i tif Table 3-14 IP route (part 2) IPRoute Destination IP2 Destination Mask2 Next Hop IP Address2 172.12.180.10 255.255.255.255 177.11.12.1 eNodeB LTE Cell *eNodeB Name *Local CellID 192.11.11.12 0 i n ni a Tr g n o i t *Cell BTS Design *Cell a Cell ID icName ID f i rt TCell0 0 e 0 C & e aw Hu Table 3-15 LTE cell basic parameters (part 1) g n ni 3.3 Task: Filling in the Radio Data Sheet Fill in the Radio Data in the following tables. VLAN ID2 ai r iT r e C Priority2 VLAN & *TrackingAreaId *Tracking area code *CN Operator ID 0 9 0 Table 3-16 LTE cell basic parameters (part 2) ei LTE Cell H w a u NB-IoT TA Flag Csg indicator Uplink cyclic prefix length Downlink cyclic prefix length NB-IoT Cell Flag BOOLEAN _FALSE BOOLEAN_FA LSE NORMAL_CP NORMAL_CP FLASE 3-19 Coverage Level Type Frequency band 42 n Table 3-17 LTE cell basic parameters (part 3) LTE Cell Uplink EARFCN indication Uplink Downlink Downlink Uplink *Physical Additional Cell EARFCN EARFCN bandwidth bandwidth cell ID spectrum active emission state NOT_CFG 43290 CELL_BW_ CELL_BW_ 1 N100 N100 Cell admin state CELL_A CELL_UN CTIVE BLOCK tio Table 3-18 LTE cell basic parameters (part 4) LTE Cell Cell middle block timer(min) *Cell FDD TDD indication Subframe assignment Special subframe patterns CELL_TDD SA2 SSP7 e aw Hu Table 3-19 LTE cell basic parameters (part 5) LTE Cell *Root sequence index High speed flag 1 LOW_SPEED i n ni a Tr g & n o i Preamble tCell format ca radius(m) i f i rt 0e 10000 C ng & r e C Cell specific offset(dB) i n dB0 i ra T i Customized bandwidth configure indicator a c i tif Frequency offset(dB) dB0 Customized uplink bandwidth(0.1MHz) NOT_CFG Table 3-20 LTE cell basic parameters (part 6) ei LTE Cell H w a u Customized downlink bandwidth(0.1MHz) Reference signal power (0.1 dBm) Cell reselection priority Ue max power allowed configure indicator 120 7 NOT_CFG 3-20 Max transmit power allowed(dBm) n Table 3-21 LTE cell basic parameters (part 7) LTE Cell Flag of Multi-RRU Cell Mode of Multi-RRU Cell *Cell transmission and Cell Radius Start Location(m) *Cell Template reception mode BOOLEAN_FALSE 8T8R Cell_TDD_20M_S1_8T8R_TDL tio Table 3-22 Cell sector equipment parameters eNodeB Cell Sector Equipment *eNodeB Name *LocalCe llID Sector Equipment ID Baseband equipment ID 196.11.11.12 0 0 255 Azimuth i n i ra T i e w a 3.4 Task: Filling in the DevIPPattern Sheet u H Table 3-23 DevIPPattern sheet (part 1) n Device IP Address it o a *Cabinet *Subrack *Slot No. ic Subboard Type Port Type f No. No. i rt BASE_BOARD ETH 0 0 7 e C &7 0 0 BASE_BOARD ETH g in n ai r T i e w a Table 3-24 DevIPPattern sheet (part 2) u H Device IP Address *VRF Index *IP Address *Mask 0 Base Station Transport Data\IP address\*IP 1 Base Station Transport Data\IP address\*IP 1 Mask 0 Base Station Transport Data\IP address\*IP 2 Base Station Transport Data\IP address\*IP 2 Mask ng Mechanical Tilt Port No. Base Station Transport Data\Ethernet Port\*Port No. Base Station Transport Data\Ethernet Port\*Port No. User Label 3-21 & Electrical Tilt r e C a c i tif Borrow IFIP n Device IP Address *VRF Index *IP Address *Mask User Label Borrow IFIP 3.5 Task: Filling in the IPRoutePattern Sheet tio Table 3-25 IPRoutePattern sheet (part 1) IP Route *Route Index Cabinet No. Subrack No. *Slot No. Subboard Type Route Type 0 0 0 7 BASE_BOARD NEXTHOP 0 0 0 7 BASE_BOARD NEXTHOP Table 3-26 IPRoutePattern sheet (part 2) Hu g n ni e aw IP Route Port Type ai r iT & r e C Port No. a c i f tiVRF Index 0 0 *Destination IP *Mask Base Station Transport Data\IPRoute\*Destination IP1 Base Station Transport Data\IPRoute\*Destination Mask1 Base Station Transport Data\IPRoute\Next Hop IP Address1 Base Station Transport Data\IPRoute\*Destination IP2 Base Station Transport Data\IPRoute\*Destination Mask2 Base Station Transport Data\IPRoute\Next Hop IP Address2 g & n it o a c i if t r e C Next Hop IP Table 3-27 IPRoutePattern sheet (part 3) Peer IP ei H w a u n ni MTU Switch i a Tr Maximum Transmission Unit(byte) Preference 60 60 3-22 Description Info n 3.6 Task: Filling in the VLANMAPPattern Sheet Table 3-28 VLANMAPPattern Sheet VLAN Mapping Based on Next Hop IP *VRF Index *Next Hop IP *Mask *VLAN Mode VLAN ID Set VLAN Priority 0 177.11.12.1 255.255.255.255 SINGLEVL AN 101 DISABLE 3.7 Task: Filling in the Auto Deployment Sheet i n i ng Table 3-29 PnP Parameters VLAN Priority VLAN Group No. tio & r e C a c i tif ra T *Name ESN Sub Sub *Software Cold Patch Hot Patch Authentication ei *Connection Network Area Version Version Version Type Type w a u H n o i t 4 Creating eNodeBs a ic f i rt e About This Chapter C & nglists the contents of this chapter. The following itable in a Section Description r T 4.1 Task: how to create and a planned area and create initial data of ei Creating a Single eNodeB aDescribes single eNodeB using the CME. w a Hu4.2 Task: Creating eNodeBs in Batches Describes how to create eNodeBs in batches using the CME. PnP Parameters 4-23 n 4.1 Task: Creating a Single eNodeB 4.1.1 Creating the CME Planned Area Table 4-1 Creating the CME planned area Step Description Fulfilled □Yes 1 tio □No 2 i n i Input the area name and click OK. e aw ic f i rt i n ni ei H w a u a Tr g & ng io t a n Ce 4-24 Hu ra T i & r e C a c i tif □Yes □No n Step Description Fulfilled tio After a while, an empty planned area will be created. ra T i i n i ng & e w a 4.1.2 Creating Initial Data of a Single eNodeB u H Table 4-2 Creating initial data of a single eNodeB n Step Description it o aApplication >Create Base Station, and start the 1 On the U2000 MBB client, click LTE c i f wizard on the CME. i t r e C & ng i in a r T ei w a Hu Fill the eNodeB basic data, and select the corresponding template to finish the creation. 4-25 r e C a c i tif Fulfilled □Yes □No n Step Description Fulfilled tio i n i Click Next, and then click Finish. e aw ic f i rt i n ni g & ng io t a n Hu ra T i & r e C a c i tif Ce 4.1.3 Configuring eNodeB Data ra T i e w a u1 Modify the device data. Table 4-3 Configuring eNodeB Data H □Yes □No 4-26 n tio 2 i n i Modify the transmission data. e aw ic f i rt i n ni ei H a Tr g & ng io t a n Hu ra T i & r e C a c i tif □Yes □No Ce wModify the radio data. a u □Yes 3 □No 4-27 n tio ng i n i & r e C ra T 4.1.4 Checking eNodeB Data and Exporting Data ei w a Table 4-4 Checking eNodeB data and exporting Data u H Step Description n 1 After creating the eNodeB successfully, you can find the "eNodeB" you've configured in o i the Main View window. Right-click theteNodeB, select the Check eNodeB Data menu to a check the data c i f i t r e C & ng i in a r T ei w a Hu 2 If the eNodeB data check is successful, right-click the eNodeB, and select Export NE Files. 4-28 a c i tif Fulfilled □Yes □No □Yes □No n Step Description Fulfilled tio i n i ng & The Export NE Files window is displayed. Set the file path and cancel the check flags (because you already do it in previous step), select the base station, and click OK. The eNodeB configuration file (in XML format) will be exported to your PC. ra T i The file can be used for LMT local commissioning or USB commissioning. e aw ic f i rt i n ni ei H w a u a Tr g & io t a n Ce 4-29 Hu r e C a c i tif n 4.2 Task: Creating eNodeBs in Batches 4.2.1 Importing eNodeB Summary Data Table 4-5 Importing eNodeB summary data Step Description Fulfilled □Yes 1 tio □No i n i ng e aw u ra T i & r e C a c i tif 4.2.2 Checking eNodeB Data and Exporting H Data io t a n Table 4-6 Checking eNodeB data and exporting data ic f i After the summary data is imported successfully, you can find the eNodeB you've t to CME r configured in the Main View window. Right-click the eNodeB, select the Check eNodeB e Data menu to check the C data. & ng i in a r T ei Step 1 H Description Fulfilled □Yes □No w a u 2 If the eNodeB data check is successful, right-click the eNodeB, and select Export NE Files. 4-30 □Yes n Step Description Fulfilled □No tio i n i ng e aw io t a n Hu ra T i & The Export NE Files window is displayed. Set the file path and cancel the check flags (because you already do it in previous step), select the base station, and click OK. The eNodeB configuration file (in XML format) will be exported to your PC. ic f i rt The file can be used for LMT local commissioning or USB commissioning. i n ni ei H w a u a Tr g & Ce 4-31 r e C a c i tif n Step Description Fulfilled 3 If you want to perform remote commissioning, you can select the menu shown in the following figure. The configuration file can be exported to U2000 MBB server for remote commissioning (Auto Deployment). □Yes □No tio i n i ng e aw ic f i rt i n ni ei H w a u a Tr g & io t a n Ce 4-32 Hu ra T i & r e C a c i tif n eNodeB LTE V100R013C10 Reconfiguration Practice Guide ISSUE1.00 i n i ng e aw ic f i rt i n ni ei H w a u a Tr g & Ce io t a n Hu ra T i & r e C a c i tif tio n Contents 1 Adding an FDD/NB-IoT Cell (Common) ................................................................................. 6 1.1 Application Scenario ........................................................................................................................................ 6 1.2 Task Description ............................................................................................................................................... 6 1.3 Engineering Preparation ................................................................................................................................... 6 1.3.1 Information Collection ............................................................................................................................ 6 tio 1.4 Engineering Implementation ..........................................................................................................................a18 ic 18 1.4.1 CME-based Operations ......................................................................................................................... f i t 21 1.4.2 MML-based Operations ........................................................................................................................ r 1.5 Engineering Verification................................................................................................................................. 24 Ce & 2 Changing the Cell Bandwidth .................................................................................................. 24 g 2.1 Application Scenario ...................................................................................................................................... 24 n i 2.2 Task Description ............................................................................................................................................. 25 in a r 2.3 Engineering Preparation ................................................................................................................................. 25 T i 2.3.1 Information Collection .......................................................................................................................... 25 e 2.3.2 Data Preparation.................................................................................................................................... 25 w a 2.4 Engineering Implementation .......................................................................................................................... 33 u H 2.4.1 CME-based Operations ......................................................................................................................... 33 2.4.2 MML-based Operations ........................................................................................................................ 36 n o 2.5 Engineering Verification................................................................................................................................. 40 ti a 3 Changing the Cell EARFCNs.................................................................................................... 40 ic f i t 3.1 Application Scenario ...................................................................................................................................... 40 r e 3.2 Task Description ............................................................................................................................................. 40 C 3.3 Engineering Preparation ................................................................................................................................. 41 & .......................................................................................................................... 41 3.3.1 Information Collection ng .................................................................................................................................... 41 3.3.2 Data iPreparation in Implementation .......................................................................................................................... 47 3.4 Engineering a r CME-based Operations ......................................................................................................................... 47 3.4.1 T e3.5i Engineering Verification................................................................................................................................. 50 w 4a Changing the Neighboring Cell Parameters.......................................................................... 50 Hu 4.1 Application Scenario ...................................................................................................................................... 50 1.3.2 Data Preparation...................................................................................................................................... 7 4.2 Task Description ............................................................................................................................................. 50 4.3 Engineering Preparation ................................................................................................................................. 51 4.3.1 Information Collection .......................................................................................................................... 51 4.3.2 Data Preparation.................................................................................................................................... 51 4.4 Engineering Implementation .......................................................................................................................... 57 4.4.1 CME-based Operations ......................................................................................................................... 57 n 4.5 Engineering Verification................................................................................................................................. 60 5 Changing the Cell ID ................................................................................................................. 61 5.1 Application Scenario ...................................................................................................................................... 61 5.2 Task Description ............................................................................................................................................. 61 5.3 Engineering Preparation ................................................................................................................................. 61 5.3.1 Information Collection .......................................................................................................................... 61 5.3.2 Data Preparation.................................................................................................................................... 62 tio 5.4 Engineering Implementation .......................................................................................................................... 67 a c i f 71 i t 6.1 Application Scenario ...................................................................................................................................... r e 6.2 Task Description ............................................................................................................................................. 71 C 6.3 Engineering Preparation ................................................................................................................................. 72 & 6.3.1 Information Collection .......................................................................................................................... 72 g 6.3.2 Data Preparation.................................................................................................................................... 72 in n 6.4 Engineering Implementation .......................................................................................................................... 79 ai r 6.4.1 CME-based Operations ......................................................................................................................... 79 T i 6.4.2 MML-based Operations ........................................................................................................................ 81 e w 6.5 Engineering Verification................................................................................................................................. 84 a 7 Adding an S-GW Connection ................................................................................................... 84 Hu 7.1 Application Scenario ...................................................................................................................................... 84 n 7.2 Task Description ............................................................................................................................................. 85 it o 7.3 Engineering Preparation ................................................................................................................................. 85 a c i 7.3.1 Information Collection .......................................................................................................................... 85 f i t r 7.3.2 Data Preparation.................................................................................................................................... 86 e 7.4 Engineering Implementation C .......................................................................................................................... 93 7.4.1 CME-based Operations & ......................................................................................................................... 93 g Operations ........................................................................................................................ 96 7.4.2 MML-based n i 7.5 Engineering n Verification............................................................................................................................... 100 i a 8 Changingrthe VLAN Mode from VLAN Group to Single VLAN ................................... 101 T i Application Scenario .................................................................................................................................... 101 e8.1 w 8.2 Task Description........................................................................................................................................... 101 a 8.3 Engineering Preparation ............................................................................................................................... 101 Hu 5.5 Engineering Verification................................................................................................................................. 71 6 Adding a Neighboring eNodeB ............................................................................................... 71 8.3.1 Information Collection ........................................................................................................................ 101 8.3.2 Data Preparation.................................................................................................................................. 101 8.4 Engineering Implementation ........................................................................................................................ 109 8.4.1 CME-based Operations ....................................................................................................................... 109 8.4.2 MML-based Operations ...................................................................................................................... 113 8.5 Engineering Verification............................................................................................................................... 116 9 Changing the eNodeB ID ........................................................................................................ 117 n 9.1 Application Scenario .................................................................................................................................... 117 9.2 Task Description ........................................................................................................................................... 117 9.3 Engineering Preparation ............................................................................................................................... 117 9.3.1 Information Collection ........................................................................................................................ 117 9.3.2 Data Preparation.................................................................................................................................. 118 9.4 Engineering Implementation ........................................................................................................................ 122 9.4.1 CME-based Operations ....................................................................................................................... 122 9.5 Engineering Verification............................................................................................................................... 126 tio 10 Changing Cabinet and Subrack No..................................................................................... 126 a c i f 126 10.2 Task Description ......................................................................................................................................... i t r 127 10.3 Engineering Preparation ............................................................................................................................. e C 10.3.1 Information Collection ...................................................................................................................... 127 & 10.3.2 Data Preparation................................................................................................................................ 127 10.4 Engineering Implementation ...................................................................................................................... 130 ng i 10.5 Engineering Verification............................................................................................................................. 134 in a r 11 Replacing the Main Control Board ...................................................................................... 134 T i 11.1 Application Scenario .................................................................................................................................. 134 e w 11.2 Task Description ......................................................................................................................................... 134 a u 11.3 Engineering Implementation ...................................................................................................................... 134 H 11.3.1 Information Collection ...................................................................................................................... 134 n 11.3.2 Data Preparation ................................................................................................................................ 135 o i t 11.3.3 Commissioning Preparation .............................................................................................................. 140 a 11.4 Engineering Implementation ...................................................................................................................... 144 ic f i 11.5 Engineering Verification ............................................................................................................................. 151 t r e 12 Transmission CapacityC Expansion from One UMPT Board to Two UMPT Boards (FDD/NB-IoT) ............................................................................................................................... 151 & 12.1 Application Scenario g .................................................................................................................................. 151 n i 12.2 Task Description ......................................................................................................................................... 152 in Preparation ............................................................................................................................. 152 12.3 Engineering a r Information Collection ...................................................................................................................... 152 T 12.3.1 ei 12.3.2 Data Preparation................................................................................................................................ 153 w 12.4 Engineering Implementation ...................................................................................................................... 160 a 12.4.1 Local Operations ............................................................................................................................... 160 Hu 10.1 Application Scenario .................................................................................................................................. 126 12.4.2 Remote Operations............................................................................................................................ 160 12.4.3 CME-based Operations ..................................................................................................................... 160 12.4.4 MML-based Operations .................................................................................................................... 164 12.5 Engineering Verification............................................................................................................................. 167 13 Replacing BBPs ........................................................................................................................ 168 13.1 Application Scenario .................................................................................................................................. 168 n 13.2 Task Description ......................................................................................................................................... 168 13.3 Engineering Preparation ............................................................................................................................. 168 13.3.1 Information Collection ...................................................................................................................... 168 13.3.2 Data Preparation................................................................................................................................ 169 13.4 Engineering Implementation ...................................................................................................................... 176 13.4.1 CME-based Operations ..................................................................................................................... 176 13.4.2 MML-based Operations .................................................................................................................... 180 13.5 Engineering Verification............................................................................................................................. 185 tio i n i ng e aw ic f i rt i n ni ei H w a u a Tr g & Ce io t a n Hu ra T i & r e C a c i tif n 1 Adding an FDD/NB-IoT Cell (Common) 1.1 Application Scenario There are weak-signal areas or coverage holes in the current eNodeB coverage, requiring an additional cell to supplement coverage. As the eNodeB traffic increases, the capacity requirements of cell edge UEs (CEUs) cannot be met. In this situation, the coverage areas of the existing cells need to be reduced and an additional cell needs to be added. The operator uses a new frequency band. tio 1.2 Task Description r e C a c i tif There is a weak-signal area in the current eNodeB coverage. We need to add an additional FDD/NB-IoT cell to supplement coverage. We adopt the following scheme: add an LBBP and an RF module. Figure 1 shows the topology changes after an LBBP and an RF module are added. i n i ng Figure 1-1 Topology changes e aw ic f i rt io t a n Hu ra T i & Ce 1.3 Engineering Preparation & g in Collection 1.3.1 Information in a Whether… r T i The baseband e resources are insufficient w a u H The RF resources are insufficient An RET is to be configured Judging □Yes □No □Yes □No □Yes □No A TMA is to be configured □Yes □No Writing the specific information n Whether… Judging A new Sector is to be configured □Yes Writing the specific information □No A new Cell is to be configured □Yes □No A new License is to be prepared □Yes □No A new Software is to be prepared tio □Yes □No r e C a c i tif & g Task 1 Data preparation by using the "batch reconfiguration"in mode of the CME n Step Description Fulfilled ai r T File (CME client □Yes 1. On the menu bar, choose Advanced > Customize Summary Data i e (U2000 client mode). □No mode) or CME > Advanced > Customize Summary Data File w A dialog box is displayed for you to open the summary a data file. u H n it o a c i f i t r e C & ng i in a r T 2. dialog box, select the following options in sequence Default > NodeB/eNodeB □Yes eiInBulktheConfiguration > eNodeB > base station version, Click OK to enable the □No w function of customizing a summary data file. a Hu 1.3.2 Data Preparation n Step Description Fulfilled tio i n i ng ra T i & e w Click . Select a scenario-based template: Cell Data a Reconfigurations > Adding u an FDD Cell (or Adding an NB-IoT Cell), select MOs H you want to change, and then click OK. n it o a c i f i t r e C & ng i in a r T i 3. r e C a c i tif □Yes □No e aw Hu 4. Click , specify a save path for the exported file, save the summary data file to a local PC. The CME automatically customizes the parameter names contained in the template in the summary data file. □Yes □No n Step Description Fulfilled tio a c i tif 5. 6. ei H w a u r e C □Yes Based on the parameter names in the summary data file, export the eNodeB data to be & □No reconfigured from the planned data area to the summary data file. g On the menu bar of the planned data area, choose LTE Application > Export > n >Data i Export Base Station Bulk Configuration Data (CME client mode) or CME LTE inData Application > Export Data > Export Base Station Bulk Configuration a r (U2000 client mode). The data export function is enabled. T ei w a Hu n it o a c i f i t rin sequence "Scenario > Adjust data by NE > e Select the following options □Yes version >NEs need to C be adjusted" in the pop-up dialog box. Click "Next". □No & ng i in a Tr n Step 7. Description Fulfilled 1. Select Bulk configuration template. □Yes 2. In Bulk configuration data file, select the prepared file and export configuration data from the CME based on the MOs in this file. □No 3. In Export path, specify a save path for the file that contains the exported data. 4. Click "Next", the CME verifies the configuration data to be exported. After the export is complete, click "Finish". i n i ng e aw io t a 8. Open the local summary data file and reconfigure data in the summary data file based on planned data. ic f i Import the edited summary data t file into the CME. r On the menu bar of the planned data area, choose LTE Application > Import Data > Ce Configuration Import Base Station Bulk Data (CME client mode) or CME > LTE Application > Import & Data > Import Base Station Bulk Configuration Data (U2000 client g mode). The data import function is enabled. n ni i ra T i 9. e aw Hu n Hu ra T i & tio r e C a c i tif □Yes □No □Yes □No n Step 10. Description Fulfilled Select files to import and data types to adjust, select "I have read the note" and click Next. □Yes □No tio ng i n i Select base stations whose data you want to import and click Next. ic f i rt n ni i ei H e aw 11. ra T i w a 12. u a Tr g & io t a n Hu & r e C a c i tif □Yes □No Ce After the import is complete, click "Finish". Finish the data preparation by using "batch reconfiguration" mode of CME. □Yes □No n Step Description Fulfilled tio i n i ng e ra T i & r e C a c i tif Task 2 Data preparation by using the GUI mode of CME Hu Configure baseband equipment data of the base station. In the left pane of the planned data area, right-click an eNodeB you want to nthe shortcut reconfigure and choose Device Panel from menu. The eNodeB device o i t panel is displayed. a c i f i t r e C & ng i in a r T i Step Description 1 2 Fulfilled □Yes □No e aw Hu aw Add an LBBP board. □Yes Select the slot for installing a board. Right-click the slot and choose to add a required board. □No n Step Description Fulfilled tio 3 Set board parameters and click OK. ni e aw ic f i rt n ni io t a n Hu ai r iT & □Yes □No Ce i a r InTthe lower left part of the device panel, right-click TOPO and choose Add Chain Add an RRU chain. □Yes eifrom the shortcut menu. □No 4 H g & ng r e C a c i tif w a u n Step Description Fulfilled 5 Based on the planned data, set the related information such as the number and networking mode of the RXU chain/ring and the port on the board to which the RXU chain/ring head is connected. Click OK. The configured RXU chain/ring is displayed under the TOPO node. □Yes □No tio ng i n i e Hauconfigured RXU chain, and In the lower left part of the device panel, right-click choose Add Board > Board Type from the shortcut menu. A dialog box is displayed n for you to add an RF board. it o a c i f i t r e C & ng i in a r T i 6 Add an RRU. 7 □Yes □No e aw Hu aw ra T i & r e C a c i tif In the dialog box, set the working mode and other related attributes for the RRU. □Yes □No n Step Description Fulfilled tio i n i ng 8 Configure ALDs on the device panel. e w a Hu ra T i & In the right pane of the device panel, click RET and configure RET and RETSUBUNIT. After the configuration is complete, click OK. ic f i rt & Hu n Configure sectors and cells. e □Yes □No Ce g n i In the left pane of the planned data area, right-click a base station you want to nand i configure Carrier Resource Management from the shortcut menu. The aresourcechoose r carrier management window is displayed. iT 9 aw io t a r e C a c i tif □Yes □No n Step Description Fulfilled tio a c i tif 10 r e C □Yes Right-click in the blank area of sector zone and choose Add Sector from the shortcut & □No menu. In the displayed dialog box, set the sector attributes and antennas. Click "OK". g in n ai r T i e w a u H n it o a c i f i t r e C & ng i in a r T i e aw Hu11 Right-click the sector icon to add sector equipment, In the displayed dialog box, set the sector equipment attributes. Click "OK". □Yes □No n Step Description Fulfilled tio a c i tif 12 Right-click in the blank area of cell zone and choose to create LTE cell from the shortcut menu. In the displayed dialog box, set the cell attributes. Click "OK". ng i n i e aw ic f i rt n ni n Ce ai r We T can search another MOs in the object navigation tree, click the Search tab and type eithe MO information you want to configure. The CME automatically finds the 13 aw Hu g & io t a Hu ra T i & r e □Yes C □No corresponding MOs. Double-click the MO you want to configure and edit the planned data in the right pane. Click to save the configured data. □Yes □No n Step Description Fulfilled tio Task 3 Data preparation by using the MML Step Description 1 Prepare MML configuration scripts 1.4.1 CME-based Operations ic f i rt i n i e 1.4 Engineering Implementation io t a n ng w a Hu ra T i & Step Description 1 Set the eNodeB engineering maintenance mode to expand status to prevent any alarm from being reported during the reconfiguration. & Ce r e C a c i tif Fulfilled □Yes □No Fulfilled □Yes □No On the U2000 Client, choose Configuration > Settings > Maintenance Mode (application style) or Maintenance > Maintenance Mode (traditional style). i n ni ei H w a u 2 a Tr Click g at the upper left corner of the Maintenance Mode window. In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE maintenance mode to a customized expand status. Click OK to complete the setting. In the displayed Confirm dialog box, click Yes. □Yes □No n Step Description Fulfilled tio i n i ng e aw 3 Hu ra T i & r e C a c i tif Deliver and activate the configuration on the eNodeB. □Yes On the menu bar of the planned data area, choose Area Management > Planned Area > Export Incremental Scripts (CME client mode) or CME > Planned Area > Export Incremental Scripts (U2000 client mode) to start the wizard of exporting scripts. □No n it o a c i if t i n ni ei H w a u 4 a Tr g & r e C Select Launch script executor only in the wizard to activate exported scripts for data to take effect on the live network. □Yes □No n Step Description Fulfilled tio i n i ng ra T i 5 6 Hu e w a Set the Maintenance Mode of the eNodeB to NORMAL. u H > Maintenance Mode On the U2000 Client, choose Configuration > Settings (application style) or Maintenance > Maintenance Mode (traditional style). n it o a c i f i t r e C & ng i Click in at the upper left corner of the Maintenance Mode window. In the Set a Mode dialog box, select the eNodeBs to be configured. Set NE Maintenance r T imaintenance mode to NORMAL. Click OK to complete the setting. In the displayed e Confirm dialog box, click Yes. aw & r e C a c i tif □Yes □No □Yes □No n Step Description Fulfilled tio ng i n i e aw 1.4.2 MML-based Operations ic f i rt io t a n Hu ra T i & Step Description 1 Set the eNodeB engineering maintenance mode to expand status to prevent any alarm from being reported during the reconfiguration. & Ce r e C a c i tif Fulfilled □Yes □No Run the following command: SET MNTMODE: MNTMODE=ExpandStatus1 in MML input window. i n ni ei H w a u 3 a Tr g From the main menu of the U2000 client, choose Trace and Maintenance > Maintenance > MML Command (application style) or Maintenance > MML Command (traditional style). □Yes □No n Step Description 4 Fulfilled In the left pane, select a base station type: BTS3900 LTE. In the navigation tree, select the eNodeBs to be reconfigured, click to enter the script mode. i n i ng e aw io t a 5 ei H w a u 6 n Hu ra T i & ic f i In the right pane, copy and paste rt the MML commands to be executed in sequence to e area 1, Click to C create a batch processing task. & ng i in a Tr In the New Task dialog box, enter a name in Task Name. Choose Other > MML Script in Task Type. Set Execution Type, and click Next. a c i tif □Yes □No r e C tio □Yes □No □Yes □No n Step Description Fulfilled tio 7 i n i Set the time or period to execute the task and click Next. e ic f i rt i n ni ei H w a u 8 a Tr g & io t a n ng w a Hu ra T i & r e C a c i tif □Yes □No Ce Select the Select NE option. In the Confirm dialog box displayed, click OK. Select the eNodeBs on which the MML scripts are to be executed, set Run Mode and Execution Result, and click Finish. □Yes □No n Step Description Fulfilled tio i n i ng e aw 9 Set the Maintenance Mode of the eNodeB to NORMAL. Hu ra T i & Run the following command: SET MNTMODE: MNTMODE=NORMAL in MML input window. ic f i rt g & io t a n r e C a c i tif □Yes □No Ce n 1.5 Engineering ni Verification Step eiCheck whether MOs have been modified. aw 1 Hu i a r Description T Fulfilled □Yes □No 2 Changing the Cell Bandwidth 2.1 Application Scenario The current bandwidth is less than 20 MHz and cannot meet service requirements due to the growing number of users. n 2.2 Task Description As the growing number of users, we need to expand bandwidth to meet service requirement. We adopt the following scheme: change cell bandwidth into 20Mhz. Figure 2 shows the changes of topology. Figure 2-1 Topology changes tio i n i ng 2.3.1 Information Collection Whether… c it fi The baseband resources are insufficient e aw 2.3 Engineering Preparation io t a n r The RF resources are insufficient e C & The transmission rate ofg the optical module is insufficient in n aiis to be collected Cell information r T i e w a u H Hu Judging ra T i & r e C a c i tif Writing the specific information □Yes □No □Yes □No □Yes □No □Yes □No 2.3.2 Data Preparation Task 1 Data preparation by using the "batch reconfiguration" mode of the CME Step 1. Description Fulfilled On the menu bar, choose Advanced > Customize Summary Data File (CME client mode) or CME > Advanced > Customize Summary Data File (U2000 client mode). A dialog box is displayed for you to open the summary data file. □Yes □No n Step Description Fulfilled tio 2. ng ni e aw ic f i rt n ni i ei H & In the dialog box, select the following options in sequence Default > NodeB/eNodeB Bulk Configuration > eNodeB > base station version, Click OK to enable the function of customizing a summary data file. 3.w a u a Tr g & io t a n Hu ai r iT r e C a c i tif □Yes □No Ce Click . Select a scenario-based template: Cell Data Reconfigurations >Changing the Cell Bandwidth, select MOs you want to change, and then click OK. □Yes □No n Step Description Fulfilled tio ng i n i e aw 4. Hu ra T i & Click to perform rule check against the template. If the check is passed, the "Rule check is successful." message will be displayed. ic f i rt 5. & io t a n Ce Click , specify a save path for the exported file, save the summary data file to a local PC. The CME automatically customizes the parameter names contained in the template in the summary data file. i n ai r T i ng r e C a c i tif □Yes □No □Yes □No e aw Hu 6. Based on the parameter names in the summary data file, export the eNodeB data to be □Yes n Step Description Fulfilled reconfigured from the planned data area to the summary data file. □No On the menu bar of the planned data area, choose LTE Application > Export Data > Export Base Station Bulk Configuration Data (CME client mode) or CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data (U2000 client mode). The data export function is enabled. tio Select the following options in sequence "Scenario > Adjust data by NE > version >NEs need to be adjusted" in the pop-up dialog box. Click "Next". e aw ic f i rt n ni i ei H ng ni 7. w a u a Tr g & Ce io t a n Hu ai r iT & r e C a c i tif □Yes □No n Step 8. Description Fulfilled 1. Select Bulk configuration template. □Yes 2. In Bulk configuration data file, select the prepared file and export configuration data from the CME based on the MOs in this file. □No 3. In Export path, specify a save path for the file that contains the exported data. 4. Click "Next", the CME verifies the configuration data to be exported. After the export is complete, click "Finish". i n i ng e aw io t a 9. Open the local summary data file and reconfigure data in the summary data file based on planned data. ic f i Import the edited summary data t file into the CME. r On the menu bar of the planned data area, choose LTE Application > Import Data > Ce Configuration Import Base Station Bulk Data (CME client mode) or CME > LTE Application > Import & Data > Import Base Station Bulk Configuration Data (U2000 client g mode). The data import function is enabled. n ni i ra T i 10. e aw Hu n Hu ra T i & tio r e C a c i tif □Yes □No □Yes □No n Step 11. Description Fulfilled Select files to import and data types to adjust, select "I have read the note" and click Next. □Yes □No tio i n i ng Select base stations whose data you want to import and click Next. ic f i rt n ni i ei H e aw 12. ra T i w a u a Tr g & Ce io t a n Hu & r e C a c i tif □Yes □No n Step 13. Description Fulfilled After the import is complete, click "Finish". Finish the data preparation by using "batch reconfiguration" mode of CME. □Yes □No tio i n i ng e aw Hu ra T i & r e C a c i tif Task 2 Data preparation by using the GUI mode of CME Step Description i t a In the left pane of the planned data area, right-click an eNodeB you want to ic from the shortcut menu. The eNodeB device reconfigure and choose Device Panel f i panel is displayed. rt e C & ng i in a r T i 1 Configure baseband equipment data of the base station. 2 Fulfilled □Yes □No e aw Hu on Add an LBBP board. □Yes n Step Description Fulfilled Select the slot for installing a board. Right-click the slot and choose to add a required board. □No tio i n i ng 3 Set board parameters and click OK. ic f i rt i n ni ei H w a u4 a Tr g & e aw io t a n Hu ra T i & r e C a c i tif □Yes □No Ce We can search another MOs in the object navigation tree, click the Search tab and type the MO information you want to configure. The CME automatically finds the corresponding MOs. Double-click the MO you want to configure and edit the planned data in the right pane. Click to save the configured data. □Yes □No n Step Description Fulfilled tio Task 3 Data preparation by using the MML Step Description 1 Prepare MML configuration scripts 2.4.1 CME-based Operations ic f i rt i n i e 2.4 Engineering Implementation io t a n ng w a Hu ra T i Step Description 1 Set the eNodeB engineering maintenance mode to expand status to prevent any alarm from being reported during the reconfiguration. & Ce On the U2000 Client, choose Configuration > Settings > Maintenance Mode (application style) or Maintenance > Maintenance Mode (traditional style). n ni i ei H & w a u a Tr g r e C a c i tif Fulfilled □Yes □No Fulfilled □Yes □No n Step 2 Description Fulfilled Click □Yes at the upper left corner of the Maintenance Mode window. In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE maintenance mode to a customized expand status. Click OK to complete the setting. In the displayed Confirm dialog box, click Yes. □No tio i n i ng e aw io t a ic f i Deliver and activate the configuration t on the eNodeB. r e On the menu bar of the planned data area, choose Area Management > Planned C Scripts (CME client mode) or CME > Planned Area > Area > Export Incremental & Scripts (U2000 client mode) to start the wizard of exporting Export Incremental scripts. ng i in a r T i 3 4 □Yes □No e aw Hu n Hu ra T i & r e C a c i tif Select Launch script executor only in the wizard to activate exported scripts for data to take effect on the live network. □Yes □No n Step Description Fulfilled tio ng i n i ra T i 5 e w a Set the Maintenance Mode of the eNodeB to NORMAL. u On the U2000 Client, choose Configuration > Settings H > Maintenance Mode (application style) or Maintenance > Maintenance Mode (traditional style). n it o a c i f i t r e C & ng i in a r T i e Hu aw & r e C a c i tif □Yes □No n Step 6 Description Fulfilled Click at the upper left corner of the Maintenance Mode window. In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE maintenance mode to NORMAL. Click OK to complete the setting. In the displayed Confirm dialog box, click Yes. □Yes □No tio i n i ng e aw ic f i rt io t a n Hu ra T i & r e C a c i tif e C 2.4.2 MML-based Operations Step 1 & g n i Set the eNodeB engineering maintenance mode to expand status to prevent any alarm in reported from a being during the reconfiguration. r T the following command: SET MNTMODE: MNTMODE=ExpandStatus1 in iRun Description e MML input window. H w a u Fulfilled □Yes □No n Step Description Fulfilled 2 From the main menu of the U2000 client, choose Trace and Maintenance > Maintenance > MML Command (application style) or Maintenance > MML Command (traditional style). □Yes □No tio a c i tif 3 ng i n i e aw ic f i rt n ni i 4 H r e □Yes C □No In the left pane, select a base station type: BTS3900 LTE. In the navigation tree, select the eNodeBs to be reconfigured, click to enter the script mode. a Tr g & io t a n Hu ra T i & Ce w a u eiIn the right pane, copy and paste the MML commands to be executed in sequence to area 1, Click to create a batch processing task. □Yes □No n Step Description Fulfilled tio 5 In the New Task dialog box, enter a name in Task Name. Choose Other > MML Script in Task Type. Set Execution Type, and click Next. i n i ng e aw ic f i rt 6 ei H w a u io t a n Hu e C Set the time or period to execute the task and click Next. & ng i in a Tr ra T i & a c i tif □Yes □No r e C □Yes □No n Step Description Fulfilled tio i n i ng Select the Select NE option. In the Confirm dialog box displayed, click OK. Select the eNodeBs on which the MML scripts are to be executed, set Run Mode and Execution Result, and click Finish. ic f i rt n ni i ei H w a u 8 e aw 7 ra T i & a Tr g & io t a n Hu r e C a c i tif □Yes □No Ce Set the Maintenance Mode of the eNodeB to NORMAL. □Yes Run the following command: SET MNTMODE: MNTMODE=NORMAL in MML input window. □No n Step Description Fulfilled tio 2.5 Engineering Verification Step Description 1 Check whether MOs have been modified. i n i 3 Changing the Cell EARFCNs 3.1 Application Scenario ng e aw ra T i & a c i f i t Fulfilled r e C □Yes □No u H The operator needs to re-plan frequency resources. n o i 3.2 Task Description t a ic resources. Figure 3 shows the cell information changes. One operator needs to re-plan frequency f i rt e Figure 3-1 Cell information changes C & ng i in a r T ei w a Hu The current EARFCNs of the cell are inappropriate. n 3.3 Engineering Preparation 3.3.1 Information Collection Whether… Judging The EARFCNs of cells need to be collected □Yes Writing the specific information □No tio a c i tif 3.3.2 Data Preparation r e C Fulfilled Task 1 Data preparation by using the CME-provided "radio data planning file". Step 1. Description i n i e aw ic f i rt g & io t a n Hu ra T i & w a u □No The CME-provided "radio data planning file" supports automatic update of the information about external cells when cell-related parameters are modified. n ni On the LTE network, this option applies only to radio network planning data and ID/name modification. eisynchronize cell parameters in the entire network and click OK. 2. □Yes Ce i a r On the Cell Parameter Auto-Synchronization Policy tab page, select Auto T H ng To ensure that the associated parameters of the external cells in the current data area are consistent, choose System > Options (CME client mode) or CME > Options (U2000 client mode) on the menu bar of the main window. The setting function is started. □Yes □No n Step Description Fulfilled tio i n i 3. ra T i & On the menu bar of the planned data area, choose CME > LTE Application > Export Data > Export Radio Network Planning Data (U2000 client mode) or LTE Application > Export Data > Export Radio Network Planning Data (CME client mode). Export planned radio data from the CME to the file. e ic f i rt 4. n ni g & io t a n w a Hu aw e r T i □Yes □No Ce A dialog box is displayed for you to select NEs. Choose NE version, add the NEs to be reconfigured from the left pane to the right pane, and click Next. ai Hu ng r e C a c i tif □Yes □No n Step Description Fulfilled tio ng i n i Add the Cells to be reconfigured from the left pane to the right pane, and click Next. ic f i rt n ni i ei H w a u 6. e aw 5. ra T i & a Tr g & io t a n Hu r e C a c i tif □Yes □No Ce Select the radio network planning objects those need to be reconfigured, and click Next. □Yes □No n Step Description Fulfilled tio i n i ng 7. e Click , specify a save path for the exported file, and click Next. The CME starts the export. After the export is complete, click Finish. ic f i rt n ni i ei H w a u 8. ra T i & a Tr g & io t a n w a Hu r e C a c i tif □Yes □No Ce Edit data in the file based on the prepared data. Then, close the file. □Yes □No 9. Import the edited data file into the CME. □Yes n Step Description Fulfilled On the menu bar of the planned data area, choose CME > LTE Application > Import Data > Import Radio Network Planning Data (U2000 client mode) or LTE Application > Import Data > Import Radio Network Planning Data (CME client mode). A dialog box is displayed for you to import planned radio data. □No tio 10. Click Add, select the file to be imported. Then, click Next. ni e aw ic f i rt i n ni 11. H w a u ei a Tr g & io t a n Hu ng ai r iT & r e C a c i tif □Yes □No Ce Select base stations whose data you want to import and click Next. □Yes □No n Step Description Fulfilled tio ng i n Select the radio network planning objects those need to be imported, and ai click Next. The CME starts the import. After the import is complete, click Finish. r T i e w a u H n it o a c i f i t r e C & ng i in a r T i 12. e Hu aw & r e C a c i tif □Yes □No n 3.4 Engineering Implementation 3.4.1 CME-based Operations Step Description Fulfilled 1 Set the eNodeB engineering maintenance mode to expand status to prevent any alarm from being reported during the reconfiguration. □Yes □No On the U2000 Client, choose Configuration > Settings > Maintenance Mode (application style) or Maintenance > Maintenance Mode (traditional style). 2 i n i ng Click ra T i at the upper left corner of the Maintenance Mode window. tio & In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE maintenance mode to a customized expand status. Click OK to complete the setting. In the displayed Confirm dialog box, click Yes. e aw ic f i rt i n ni ei H w a u 3 a Tr g & io t a n Hu r e C a c i tif □Yes □No Ce Run the MOD GLOBALPROCSWITCH command to set the values of the options under the X2-based Neighboring Cell Configuration Update Switch to OFF □Yes □No n Step Description 4 Fulfilled Run the MOD ENODEBALGOSWITCH command to set the values of the options under the ANR algorithm switch to OFF. i n i ng e aw ra T i & u H On the menu bar of the planned data area, choose Area Management > Planned Area > Export Incremental Scripts (CMEn client mode) or CME > Planned Area > it o mode) to start the wizard of exporting Export Incremental Scripts (U2000 client scripts. a c i f i t r e C & ng i in a r T i 5 Deliver and activate the configuration on the eNodeB. e 6 w a u H Select Launch script executor only in the wizard to activate exported scripts for data to take effect on the live network. a c i □Noif t r Ce tio □Yes □Yes □No □Yes □No n Step Description Fulfilled tio ng i n i ra T i 7 e w a Set the Maintenance Mode of the eNodeB to NORMAL. u H > Maintenance Mode On the U2000 Client, choose Configuration > Settings (application style) or Maintenance > Maintenance Mode (traditional style). n it o a c i f i t r e C & ng i in a r T i e Hu aw & r e C a c i tif □Yes □No n Step Description 8 Fulfilled □Yes Click at the upper left corner of the Maintenance Mode window. In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE maintenance mode to NORMAL. Click OK to complete the setting. In the displayed Confirm dialog box, click Yes. □No tio i n i ng e aw ic f i rt io t a n Hu ra T i & r e C a c i tif e C 3.5 Engineering Verification & ng i Check whether in MOs have been modified. a r T i Step Description 1 e aw Hu4 Changing the Neighboring Cell Parameters 4.1 Application Scenario The previous neighboring cell parameter plan is inappropriate and a new plan is required. 4.2 Task Description Add the cells of LTE "ADDNENB" and UMTS "NODEB" to be the neighboring cells of LTE "LTETEST010". Figure 4 shows the topology information. Fulfilled □Yes □No n Figure 4-1 Topology information tio i n i 4.3 Engineering Preparation 4.3.1 Information Collection Base Station LTE Frequency band Bandwidth ADDNENB LTETEST010 UMTS ic f i rt NODEB n ni g io t a n e aw CELLID Hu ra T i MCC & MNC LAC TAC e 4.3.2 Data PreparationC & ng r e C a c i tif Task 1 Data preparation by using the CME-provided "radio data planning file". Step eiare consistent, choose System > Options (CME client mode) or CME > Options 1. aw Hu ai r Tensure that the associated parameters of the external cells in the current data area To Description (U2000 client mode) on the menu bar of the main window. The setting function is started. Fulfilled □Yes □No n Step Description Fulfilled tio The CME-provided "radio data planning file" supports automatic update of the information about external cells when cell-related parameters are modified. On the LTE network, this option applies only to radio network planning data and ID/name modification. ic f i rt n ni i H & On the Cell Parameter Auto-Synchronization Policy tab page, select Auto synchronize cell parameters in the entire network and click OK. e aw a Tr g & io t a n Hu ra T i □Yes □No Ce the menu bar of the planned data area, choose CME > LTE Application > Export eiOn Data > Export Radio Network Planning Data (U2000 client mode) or LTE w a u 3. ng i n i 2. r e C a c i tif Application > Export Data > Export Radio Network Planning Data (CME client mode). Export planned radio data from the CME to the file. □Yes □No n Step Description Fulfilled tio 4. A dialog box is displayed for you to select NEs. Choose NE version, add the NEs to be reconfigured from the left pane to the right pane, and click Next. i n i ng e aw ic f i rt 5. n ni n aw e r T i r e C □No Ce Add the Cells to be reconfigured from the left pane to the right pane, and click Next. ai Hu g & io t a Hu ra T i & a c i tif □Yes □Yes □No n Step Description Fulfilled tio ng i n i Select the radio network planning objects those need to be reconfigured, and click Next. ic f i rt n ni i ei H e aw 6. ra T i w a u a Tr g & Ce io t a n Hu & r e C a c i tif □Yes □No n Step Description 7. Fulfilled □Yes Click , specify a save path for the exported file, and click Next. The CME starts the export. After the export is complete, click Finish. □No tio i n i ng e aw io t a 8. 9. ei H w a u 10. n Hu ra T i & r e C a c i tif Edit data in the file based on the planning data. Then, close the file. □Yes icCME. Import the edited data file into ithe f rt data area, choose CME > LTE Application > Import On the menu bar of the planned e Data > Import Radio C Network Planning Data (U2000 client mode) or LTE Application > Import Data > Import Radio Network Planning Data (CME client &is displayed for you to import planned radio data. mode). A dialog box ng i in a Tr □No Click Add, select the file to be imported. Then click Next. □Yes □No □Yes □No n Step Description Fulfilled tio i n i ng ra T i e w a Next. Select base stations whose data you want to import, click u H n it o a c i f i t r e C & ng i in a r T i 11. □Yes □No e aw Hu 12. & r e C a c i tif Select the radio network planning objects those need to be imported, and click Next. The CME starts the import. After the import is complete, click Finish. □Yes □No n Step Description Fulfilled tio i n i ng 4.4 Engineering Implementation 4.4.1 CME-based Operations Description 1 Hu Hu n o i Set the eNodeB engineering maintenance t mode to expand status to prevent any alarm a from being reported during the reconfiguration. fic i On the U2000 Client, choosetConfiguration > Settings > Maintenance Mode r (application style) or Maintenance > Maintenance Mode (traditional style). Ce & ng i in a r T i Step e aw e aw ra T i & r e C a c i tif Fulfilled □Yes □No n Step 2 Description Fulfilled Click □Yes at the upper left corner of the Maintenance Mode window. In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE maintenance mode to a customized expand status. Click OK to complete the setting. In the displayed Confirm dialog box, click Yes. □No tio i n i ng e aw io t a ic f i Run the MOD GLOBALPROCSWITCH command to set the values of the options t Cell Configuration r under the X2-based Neighboring Update Switch to OFF Ce & ng i in a r T i 3 □Yes □No e aw Hu4 n Hu ra T i & r e C a c i tif Run the MOD ENODEBALGOSWITCH command to set the values of the options under the ANR algorithm switch to OFF. □Yes □No n Step Description 5 ei H w a u tio a c i f i □No On the menu bar of the planned data area, choose Area Management > Planned t r Area > Export Incremental Scripts (CME client mode) or CME > Planned Area > e C Export Incremental Scripts (U2000 client mode) to start the wizard of exporting scripts. & g in n ai r T i e w a u H n o i Select Launch script executor only intthe wizard to activate exported scripts for data □Yes to take effect on the live network. a □No ic f i rt e C & ng i in a Tr Deliver and activate the configuration on the eNodeB. 6 Fulfilled □Yes n Step Description Fulfilled 7 Set the Maintenance Mode of the eNodeB to NORMAL. □Yes On the U2000 Client, choose Configuration > Settings > Maintenance Mode (application style) or Maintenance > Maintenance Mode (traditional style). □No tio 8 Click at the upper left corner of the Maintenance Mode window. In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE maintenance mode to NORMAL. Click OK to complete the setting. In the displayed Confirm dialog box, click Yes. i n i ng e aw ic f i rt n ni i ei H w a u a Tr g & io t a n Hu ra T i & a c i tif r □Yes e C □No Ce 4.5 Engineering Verification Step Description Fulfilled 1 Check whether MOs have been modified. □Yes □No n 5 Changing the Cell ID 5.1 Application Scenario The previous cell ID plan is inappropriate and a new plan is required. 5.2 Task Description The cell ID of an LTE cell served by an eNodeB needs to be changed to 200. The eNodeB has intra-frequency and inter-frequency neighboring cells, as shown in figure 5. Figure 5-1 Cell ID changes i n i ng e aw 5.3 Engineering Preparation fic io t a ti r 5.3.1 Information Collection Ce & Whether… ntogbe changed. Cell information needs i in a rcell information needs to be changed. Neighboring T ei w a Hu n Hu Judging □Yes □No □Yes □No ra T i & r e C a c i tif tio Writing the specific information n 5.3.2 Data Preparation Task 1 Data preparation by using the CME-provided ID/Name Adjustment Data Step 1. Description Fulfilled On the menu bar of the main window, choose System > Options (CME client mode) or CME > Options (U2000 client mode). The setting function is started. □Yes □No tio ng i n i ra T i & r e C a c i tif On the LTE network, this option applies only to radio network planning data and ID/name modification. n ni i ei w a u 3. Hu Select Cell Parameter Auto-Synchronization Policy from the navigation tree on the left pane of the Options dialog box. Then, select Auto synchronize cell parameters in the entire network on the right pane and click OK. ic f i rt H e aw 2. a Tr g & io t a n □Yes □No Ce On the menu bar of the planned data area, choose LTE Application > Export Data > Export ID/Name Adjustment Data (CME client mode) or CME > LTE Application > Export Data > Export ID/Name Adjustment Data (U2000 client mode). The data export function is enabled. □Yes □No n Step Description Fulfilled tio 4. a c i In the displayed dialog box, select the NEs to be adjusted and then set a file path. Click □Yesif t r Next to export the names and IDs of the eNodeB and cells to a file. □No Ce & g in n ai r T i e w a u H n it o a c i f i t r e C & ng i After the □Yes inexport succeeded, click Finish. a r □No iT 5. e Hu aw n Step Description Fulfilled tio i n i ng 6. io t a n On the menu bar of the planned data area, choose LTE Application > Import Data > Import ID/Name Adjustment Data (CME client mode) or CME > LTE Application > Import Data > Import ID/Name Adjustment Data (U2000 client mode). The data import function is enabled. ic f i rt n ni i ei w a u 8. Hu Open the exported file, modify the corresponding MOs according to the planned data. Then, save the modification and close the file. 7. H e aw ra T i & a Tr g & r e C a c i tif □Yes □No □Yes □No Ce In the displayed Import ID/Name Adjustment Data dialog box, select the file to be imported, and then click Next. □Yes □No n Step Description Fulfilled tio i n i ng 9. n ni i ei w a u 10. Hu After the "Operation succeeded." message is displayed, click Finish. The data in the file has been successfully imported into the CME. ic f i rt H e aw ra T i & r e C a Tr g & io t a n Ce On the menu bar of the planned data area, choose CME > Advanced > Check Data (U2000 client mode) or Advanced > Check Data (CME client mode) to start verifying data. a c i tif □Yes □No n Step Description Fulfilled tio i n i 11. ic f i rt n ni i ei w a u 12. ra T i & Select the NEs to be verified on the left pane of the Check Data dialog box and add them to the right pane. Then, click OK to start verification. A maximum of 50 eNodeBs can be verified at a time. e aw H ng a Tr g & io t a n Hu Ce During data verification, modify the configuration data based on the verification prompt until the verification succeeds. r e C a c i tif n 5.4 Engineering Implementation Step Description Fulfilled 1 Set the eNodeB engineering maintenance mode to expand status to prevent any alarm from being reported during the reconfiguration. □Yes □No On the U2000 Client, choose Configuration > Settings > Maintenance Mode (application style) or Maintenance > Maintenance Mode (traditional style). tio i n i ng e aw ic f i rt i n ni ei H w a u a Tr g & Ce io t a n Hu ra T i & r e C a c i tif n Step 2 Description Fulfilled Click □Yes at the upper left corner of the Maintenance Mode window. In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE maintenance mode to a customized expand status. □No tio ng i n i e aw 3 c it fi ei H n If any options of the X2-based Neighboring Cell Configuration Update Switch parameter are selected, run the MOD GLOBALPROCSWITCH command to deselect them all. n ni i w a u 4 io t a Hu ra T i & a Tr g & r e C a c i tif □Yes □No r e C If any options of the ANR algorithm switch parameter are selected, run the MOD ENODEBALGOSWITCH command to deselect them all. □Yes □No n Step Description 5 ei H w a u 6 7 8 Fulfilled a c i f i □No On the menu bar of the planned data area, choose Area Management > Planned t Area > Export Incremental Scripts (CME client mode) or CME > Planned Area > er Export Incremental Scripts (U2000 client mode) to start the wizard of exporting C scripts. & Select Launch script executor only in the wizard to activate exported scripts g for data to take effect on the live network. in n ai r T i e w a u H n it o a c i f i t r e C & ng i in a Tr tio Deliver and activate the configuration on the eNodeB. □Yes Run the MOD GLOBALPROCSWITCH command to restore the setting of the parameter modified in step 3. □Yes Run the MOD ENODEBALGOSWITCH command to restore the setting of the parameter modified in step 3. □Yes Set the Maintenance Mode of the eNodeB to NORMAL. □Yes On the U2000 Client, choose Configuration > Settings > Maintenance Mode (application style) or Maintenance > Maintenance Mode (traditional style). □No □No □No n Step Description Fulfilled tio ng i n i e aw 9 Click at the upper left corner of the Maintenance Mode window. In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE maintenance mode to NORMAL. Click OK to complete the setting. ic f i rt n ni i ei H n Hu ra T i w a u a Tr g & Ce io t a & r e C a c i tif □Yes □No n 5.5 Engineering Verification Step Description Fulfilled 1 Check whether MOs have been modified. □Yes □No 6 Adding a Neighboring eNodeB tio 6.1 Application Scenario r e C a c i tif The capacity or coverage of the eNodeB cannot meet the requirement and therefore a neighboring eNodeB is required. 6.2 Task Description i n i ng & A neighboring eNodeB is added. We need to configure the parameters related to neighboring EUTRAN cells and information about X2 self-setup. Figure 5 shows the topology changes after an X2 interface between the local eNodeB and the neighboring eNodeB is added. ic f i rt i n ni a Tr g & io t a n e aw Figure 6-1 Topology changes after an X2 interface is added. Hu ra T i Ce ei Reconfiguration modes of MOs for neighboring cells have been introduced in the chapter 4. This section will only H w a u introduce reconfiguration modes of MOs for X2. n 6.3 Engineering Preparation 6.3.1 Information Collection Whether… Judging The information of Neighboring eNodeB needs to be collected, such as Frequency, BandWidth, PLMN, and CELL ID. □Yes The information of Routing information of the X2 link. □Yes Writing the specific information □No tio □No 6.3.2 Data Preparation ng & r e C a c i tif Task 1 Data preparation by using the "batch reconfiguration" mode of the CME Step i n i 1. Description e ic f i rt n ni g & io t a n w a Hu w a u □Yes □No Ce i a r InTthe dialog box, select the following options in sequence Default > NodeB/eNodeB ei Bulk Configuration > eNodeB > base station version, Click OK to enable the 2. H ra T i On the menu bar, choose Advanced > Customize Summary Data File (CME client mode) or CME > Advanced > Customize Summary Data File (U2000 client mode). A dialog box is displayed for you to open the summary data file. Fulfilled function of customizing a summary data file. □Yes □No n Step Description Fulfilled tio ng i n i ra T i e w Click . Select a scenario-based template: AdjustingaeNodeB u Configurations >Adding a Neighboring eNodeB, select MOs you want to change, H and then click OK. n it o a c i f i t r e C & ng i in a r T i 3. e aw Hu 4. & Click to perform rule check against the template. If the check is passed, the "Rule check is successful." message will be displayed. r e C a c i tif □Yes □No n Step Description 5. Fulfilled Click , specify a save path for the exported file, save the summary data file to a local PC. The CME automatically customizes the parameter names contained in the template in the summary data file. i n i ng e aw u H Based on the parameter names in the summary data file, export the eNodeB data to be n summary data file. reconfigured from the planned data area to the o i On the menu bar of the planned data area, t choose LTE Application > Export Data > a Export Base Station Bulk Configuration (CME client mode) or CME > LTE ic BaseData f Application > Export Data > iExport Station Bulk Configuration Data (U2000 client mode). The data rt export function is enabled. e C & ng i in a r T i 6. e Hu aw ra T i & □Yes □No r e C a c i tif tio □Yes □No n Step 7. Description Fulfilled Select the following options in sequence "Scenario > Adjust data by NE > version >NEs need to be adjusted" in the pop-up dialog box. Click "Next". □Yes □No tio i n i ng 8. e aw 1. Select Bulk configuration template. Hu ra T i & 2. In Bulk configuration data file, select the prepared file and export configuration data from the CME based on the MOs in this file. io t a n r e C a c i tif □Yes □No 3. In Export path, specify a save path for the file that contains the exported data. ic f i rt 4. Click "Next", the CME verifies the configuration data to be exported. After the export is complete, click "Finish". i n ni ei H w a u 9. a Tr g & Ce Open the local summary data file and reconfigure data in the summary data file based on planned data. □Yes □No n Step 10. Description Fulfilled Import the edited summary data file into the CME. □Yes On the menu bar of the planned data area, choose LTE Application > Import Data > Import Base Station Bulk Configuration Data (CME client mode) or CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data (U2000 client mode). The data import function is enabled. □No tio 11. ni e aw ic f i rt n ni i ei H ng & Select files to import and data types to adjust, select "I have read the note" and click Next. w a u a Tr g & Ce io t a n Hu ai r iT r e C a c i tif □Yes □No n Step 12. Description Fulfilled Select base stations whose data you want to import and click Next. □Yes □No tio ng i n i 13. e aw ic f i rt n ni i ei H ra T i After the import is complete, click "Finish". Finish the data preparation by using "batch reconfiguration" mode of CME. w a u a Tr g & Ce io t a n Hu & r e C a c i tif □Yes □No n Task 2 Data preparation by using the GUI mode of CME Step Description Fulfilled 1 Select an eNodeB from the left pane of the planned data area. The object navigation tree is displayed in the lower left part of the window. In the object navigation tree, click the Search tab and type the MO information you want to configure. The CME automatically finds the corresponding MOs. □Yes □No tio i n i ng e aw 2 ei ra T i & u H Select the required MO from the search result and edit the planned data in the right n pane. Click to save the configured data. it o a c i f i t r e C & ng i in a Tr r e C a c i tif □Yes □No Task 3 Data preparation by using the MML H w a u Step 1 Description Fulfilled Prepare MML configuration scripts □Yes □No n 6.4 Engineering Implementation 6.4.1 CME-based Operations Step Description Fulfilled 1 Set the eNodeB engineering maintenance mode to expand status to prevent any alarm from being reported during the reconfiguration. □Yes □No On the U2000 Client, choose Configuration > Settings > Maintenance Mode (application style) or Maintenance > Maintenance Mode (traditional style). 2 i n i ng Click ra T i at the upper left corner of the Maintenance Mode window. tio & In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE maintenance mode to a customized expand status. Click OK to complete the setting. In the displayed Confirm dialog box, click Yes. e aw ic f i rt i n ni ei H w a u 3 a Tr g & io t a n Hu r e C a c i tif □Yes □No Ce Deliver and activate the configuration on the eNodeB. □Yes On the menu bar of the planned data area, choose Area Management > Planned Area > Export Incremental Scripts (CME client mode) or CME > Planned Area > Export Incremental Scripts (U2000 client mode) to start the wizard of exporting □No n Step Description Fulfilled scripts. tio 4 Select Launch script executor only in the wizard to activate exported scripts for data to take effect on the live network. ng i n i e aw ic f i rt ei H n ni w a u g n □Yes r e □No C Ce Set the Maintenance Mode of the eNodeB to NORMAL. □Yes On the U2000 Client, choose Configuration > Settings > Maintenance Mode (application style) or Maintenance > Maintenance Mode (traditional style). □No i 5 & io t a Hu ra T i & a c i tif a Tr n Step 6 Description Fulfilled Click at the upper left corner of the Maintenance Mode window. In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE maintenance mode to NORMAL. Click OK to complete the setting. In the displayed Confirm dialog box, click Yes. □Yes □No tio ng i n i e aw ic f i rt io t a n Hu ra T i & r e C a c i tif e C 6.4.2 MML-based Operations Step 1 & g n i Set the eNodeB engineering maintenance mode to expand status to prevent any alarm in reported from a being during the reconfiguration. r T the following command: SET MNTMODE: MNTMODE=ExpandStatus1 in iRun Description Fulfilled □Yes □No e MML input window. H w a u 3 From the main menu of the U2000 client, choose Trace and Maintenance > □Yes n Step Description Fulfilled Maintenance > MML Command (application style) or Maintenance > MML Command (traditional style). □No tio 4 5 ei H w a u 6 a c i f i In the left pane, select a base station type: BTS3900 LTE. In the navigation tree, select □Yes t r the eNodeBs to be reconfigured, click to enter the script mode. e □No C & g in n ai r T i e w a u H n it o a c i f i t r e C & ng i in pane, copy and paste the MML commands to be executed in sequence to □Yes In the right a □No Tr area 1, Click to create a batch processing task. In the New Task dialog box, enter a name in Task Name. Choose Other > MML □Yes n Step Description Fulfilled Script in Task Type. Set Execution Type, and click Next. □No tio i n i ng 7 Set the time or period to execute the task and click Next. ic f i rt n ni i ei H w a u 8 e aw a Tr g & io t a n Hu ra T i & r e C a c i tif □Yes □No Ce Select the Select NE option. In the Confirm dialog box displayed, click OK. Select the eNodeBs on which the MML scripts are to be executed, set Run Mode and Execution Result, and click Finish. □Yes □No n Step Description Fulfilled tio i n i ng ra T i & e w Run the following command: SET MNTMODE: MNTMODE=NORMAL in MML a u input window. H n it o a c i f i t r e C & 6.5 Engineering ngVerification i in a Step Description r T 1 eiCheck whether MOs have been modified. w a Hu 9 Set the Maintenance Mode of the eNodeB to NORMAL. 7 Adding an S-GW Connection 7.1 Application Scenario The existing S-GW cannot meet the service requirements. r e C a c i tif □Yes □No Fulfilled □Yes □No n 7.2 Task Description As the existing S-GW cannot meet the service requirements, an S-GW connection needs to be added. Figure 8 shows the topology changes after an S-GW connection is added. Figure 7-1 Topology changes tio i n i ng e aw 7.3 Engineering Preparationic io t a n f i t r 7.3.1 Information Collection e C Whether… & gis required for a new S-GW A new device IP address n i connection. in a r the eNodeB and the new S-GW needs A route between T to be added. ei w a Hu Hu Judging □Yes □No □Yes □No ra T i & r e C a c i tif Writing the specific information n 7.3.2 Data Preparation Task 1 Data preparation by using the "batch reconfiguration" mode of the CME Step 1. Description Fulfilled On the menu bar, choose Advanced > Customize Summary Data File (CME client mode) or CME > Advanced > Customize Summary Data File (U2000 client mode). A dialog box is displayed for you to open the summary data file. □Yes □No tio i n i ng e aw 2. In the dialog box, select the following options in sequence Default > NodeB/eNodeB Bulk Configuration > eNodeB > base station version, Click OK to enable the function of customizing a summary data file. ic f i rt n ni i ei H on Hu ra T i & w a u a Tr g & Ce i at r e C a c i tif □Yes □No n Step 3. Description Fulfilled □Yes Click . Select a scenario-based template: Interface and Link Data Reconfigurations > Adding an S-GW Connection(Endpoint)/Adding an S-GW Connection(Link), select MOs you want to change, and then click OK. □No tio ng i n i e aw 4. n Click to perform rule check against the template. If the check is passed, the "Rule check is successful." message will be displayed. c ifi t 5. H io t a Hu ra T i & r e C i a Tr Click PC. n ni g & r e C and select a save path to save the customized summary data file to the local w a u eiEach MO to be configured is an independent List sheet. The values of parameters on all sheets of the summary data file are blank. a c i tif □Yes □No □Yes □No n Step Description Fulfilled tio a c i tif 6. ei H w a u r e C □Yes Based on the parameter names in the summary data file, export the eNodeB data to be & □No reconfigured from the planned data area to the summary data file. g On the menu bar of the planned data area, choose LTE Application > Export > n >Data i Export Base Station Bulk Configuration Data (CME client mode) or CME LTE inData Application > Export Data > Export Base Station Bulk Configuration a r (U2000 client mode). The data export function is enabled. T ei w a Hu n it o a c i f i t r e C & ng i in a Tr n Step 7. Description Fulfilled In the displayed dialog box, specify the scenario, adjustment mode, base station version, and select the NE to be reconfigured. Then, click Next. □Yes □No tio ng i n i 8. 1. Select Bulk configuration template. e Hu aw ra T i & 2. In Bulk configuration data file, select the prepared file and export configuration data from the CME based on the MOs in this file. r e C a c i tif □Yes □No n o i t 4. Click Next, the CME verifies the configuration data to be exported. After the a c export is complete, click Finish. i f i rt e C & ng i in a Tr 3. In Export path, specify a save path for the file that contains the exported data. ei H w a u 9. Open the local summary data file and reconfigure data in the summary data file based on planned data. □Yes □No n Step 10. Description Fulfilled Import the edited summary data file into the CME. □Yes On the menu bar of the planned data area, choose LTE Application > Import Data > Import Base Station Bulk Configuration Data (CME client mode) or CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data (U2000 client mode). The data import function is enabled. □No tio 11. i n i ic f i rt n ni i e a Tr g & io t a n Hu □Yes □No Ce eiSelect base stations whose data you want to import and click Next. aw Hu ra T i & Select files to import and data types to adjust, check "I have read the note" and click Next. aw 12. ng r e C a c i tif □Yes □No n Step Description Fulfilled tio ng i n The CME verifies the imported data. If the verification is successful, a thei "Operation r succeeded." message will be displayed. Then, click Finish. T i e w a u H n it o a c i f i t r e C & ng i in a r T i 13. e Hu aw & r e C a c i tif □Yes □No n Task 2 Data preparation by using the GUI mode of CME Step 1. Description Fulfilled In the left pane of the planned data area, click an eNodeB you want to reconfigure. The object navigation tree is displayed in the lower left area. □Yes □No You can search MOs in the object navigation tree by clicking the Search tab and typing the MO information you want to configure. The CME automatically finds the corresponding MOs. tio i n i ng e aw ic f i rt i n ni ei H w a u a Tr g & Ce io t a n Hu ra T i & r e C a c i tif n Step 2. Description Fulfilled Double-click the MO you want to configure and edit the planned data in the right pane. □Yes Click □No to save the configured data. tio a c i tif Task 3 Data preparation by using the MML Step Description 1 Prepare MML configuration scripts. ng ni 7.4 Engineering Implementation e aw 7.4.1 CME-based Operations Hu ai r iT Step Description 1 Set the eNodeB engineering maintenance mode to expand status to prevent any alarm from being reported during the reconfiguration. t c ifi io t a n On the U2000 Client, choose Configuration > Settings > Maintenance Mode (application style) or Maintenance > Maintenance Mode (traditional style). n ni i ei H & w a u a Tr g & r e C r e Fulfilled C □Yes □No Fulfilled □Yes □No n Step 2 Description Fulfilled Click □Yes at the upper left corner of the Maintenance Mode window. In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE maintenance mode to a customized expand status. Click OK to complete the setting. □No tio i n i ng e aw 3 Hu n Deliver and activate the configuration on the eNodeB. □Yes On the menu bar of the planned data area, choose Area Management > Planned Area > Export Incremental Scripts (CME client mode) or CME > Planned Area > Export Incremental Scripts (U2000 client mode) to start the wizard of exporting scripts. □No c it fi r e C Select Launch script executor only in the wizard to activate exported scripts for data &live network. to take effect on the ng i in a r T i e aw io t a Hu ra T i & r e C a c i tif n Step Description Fulfilled tio ng i n i ra T i 4 e w Set the Maintenance Mode of the eNodeB to NORMAL. a u On the U2000 Client, choose Configuration > Settings H > Maintenance Mode (application style) or Maintenance > Maintenance Mode (traditional style). n it o a c i f i t r e C & ng i in a r T i e Hu aw & r e C a c i tif □Yes □No n Step Description 5 Fulfilled □Yes Click at the upper left corner of the Maintenance Mode window. In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE maintenance mode to NORMAL. Click OK to complete the setting. □No tio ng i n i e aw 7.4.2 MML-based Operationsic n e C Set the eNodeB engineering maintenance mode to expand status to prevent any alarm &during the reconfiguration. from being reported g command: SET MNTMODE: MNTMODE=Expand in MML Run the following n i input window. in a r T i Step Description 1 Fulfilled □Yes □No e aw Hu2 f i t r io t a Hu ra T i & r e C a c i tif From the main menu of the U2000 client, choose Trace and Maintenance > Maintenance > MML Command (application style) or Maintenance > MML Command (traditional style). □Yes □No n Step Description Fulfilled tio i n i ng e aw u H In the left pane, select a base station type, for example, BTS3900 LTE. In the n navigation tree, select the eNodeBs to be reconfigured, click to enter the script it o mode. a c i f i t r e C & ng i in a r T i 3 e Hu aw ra T i & r e C a c i tif □Yes □No n Step Description Fulfilled tio i n i ng e aw 4 ic f i rt n ni i ei w a u 5 n In the right pane, copy and paste the MML commands to be executed in sequence to area 1. Click H io t a Hu ra T i & a Tr Ce to create a batch processing task. g & In the New Task dialog box, enter a name in Task Name. Choose Other > MML Script in Task Type. Set Execution Type, and click Next. r e C a c i tif □Yes □No □Yes □No n Step Description Fulfilled tio 6 i n i Set the time or period to execute the task and click Next. e ic f i rt i n ni ei H w a u a Tr g & Ce io t a n ng w a Hu ra T i & r e C a c i tif □Yes □No n Step Description Fulfilled 7 Select the Select NE option. Select the eNodeBs on which the MML scripts are to be executed, set Run Mode and Execution Result, and click Finish. In the displayed Confirm dialog box, select the Continue to execute the MML script task option, and then click Yes. □Yes □No tio i n i ng e aw Hu 8 ra T i & n o i t Run the following command: SET MNTMODE: MNTMODE=NORMAL in MML a input window. c i f i rt e C & ng i in a r T i Set the Maintenance Mode of the eNodeB to NORMAL. r e C a c i tif □Yes □No e 7.5w Engineering Verification a u H Step 1 Description Fulfilled Check whether MOs have been modified. □Yes □No n 8 Changing the VLAN Mode from VLAN Group to Single VLAN 8.1 Application Scenario The VLAN mode is re-planned: changing from VLAN group to single VLAN. The VLAN groups meet both of the following conditions: − In each VLAN group, all service types are mapped to the same VLAN ID. That is, the service types are not isolated using VLANs. − Throughout the VLAN groups, each service type is assigned a unique differentiated services code point (DSCP) value, or service types with an identical DSCP value are assigned the same VLAN priority. 8.2 Task Description The VLAN mode is re-planned: changing from VLAN group to single VLAN. 8.3 Engineering Preparation i n i ng 8.3.1 Information Collection ra T i & r e C a c i tif Information Description VLAN ID The VLAN ID of each VLAN. DSCP priority The DSCP values of user data, signaling, high-priority OM data, low-priority OM data, and other data, and the mapping priorities. ic f i rt 8.3.2 Data Preparation io t a e aw n Hu Ce 8.3.2.1 Task 1 Data preparation by using the "batch reconfiguration" mode of the CME Step 1. ei H ng Description w a u i n ai & On the menu bar, choose Advanced > Customize Summary Data File (CME client mode) or CME > Advanced > Customize Summary Data File (U2000 client mode). A dialog box is displayed for you to open the summary data file. Tr tio Fulfilled □Yes □No n Step Description Fulfilled tio i n i 2. ic f i rt n ni i ei w a u 3. & In the dialog box, select the following options in sequence Default > NodeB/eNodeB Bulk Configuration > eNodeB > base station version, Click OK to enable the function of customizing a summary data file. e aw H ng a Tr g & io t a n Hu ra T i r e C a c i tif □Yes □No Ce Click . Select a scenario-based template: Security Networking Data Reconfigurations > Changing the VLAN Mode from VLAN Group to Single VLAN, select MOs you want to change, and then click OK. □Yes □No n Step Description Fulfilled tio ng i n i 4. Hu Click to perform rule check against the template. If the check is passed, the "Rule check is successful." message will be displayed. ic f i rt Click PC. e aw & io t a n Ce g n i Each MO be configured is an independent List sheet. The values of parameters on nofto the i all sheets summary data file are blank. a r iT 5. Hu e aw ra T i & r e C and select a save path to save the customized summary data file to the local a c i tif □Yes □No □Yes □No n Step 6. Description Fulfilled Based on the parameter names in the summary data file, export the eNodeB data to be reconfigured from the planned data area to the summary data file. □Yes □No On the menu bar of the planned data area, choose LTE Application > Export Data > Export Base Station Bulk Configuration Data (CME client mode) or CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data (U2000 client mode). The data export function is enabled. tio ng 7. e 1. Select Bulk configuration template. Hu aw 8. i n i station In the displayed dialog box, specify the scenario, adjustment mode, base a r version, and select the NE to be reconfigured. Then, click Next. T ei w a Hu n it o a c i f i t r e C & ng i in a r T i & 2. In Bulk configuration data file, select the prepared file and export configuration data from the CME based on the MOs in this file. 3. In Export path, specify a save path for the file that contains the exported data. 4. Click "Next", the CME verifies the configuration data to be exported. After the export is complete, click "Finish". r e C a c i tif □Yes □No □Yes □No n Step Description Fulfilled tio ng 9. 10. 11. H i n idata file based Open the local summary data file and reconfigure data in the summary a r on planned data. T i e Import the edited summary data file into the CME. w On the menu bar of the planned data area, choose LTE a Application > Import Data > u Import Base Station Bulk Configuration Data (CME mode) or CME > LTE H Bulkclient Application > Import Data > Import Base Station Configuration Data (U2000 client mode). The data import function n is enabled. o ti a ic f i rt e C & ng i in a r T iSelect files to import and data types to adjust, select "I have read the note" and click e Next. w a u & r e C a c i tif □Yes □No □Yes □No □Yes □No n Step Description Fulfilled tio 12. Select base stations whose data you want to import and click Next. e aw ic f i rt n ni i 13. H ra T i a Tr g & io t a n Hu i n i ng & □Yes □No Ce CME verifies the imported data. If the verification is successful, the "Operation eiThe succeeded." message will be displayed. Then, click Finish. w a u r e C a c i tif □Yes □No n Step Description Fulfilled tio i n i ng e aw ic f i rt i n ni ei H w a u a Tr g & Ce io t a n Hu ra T i & r e C a c i tif n Task 2 Data preparation by using the GUI mode of CME Step 1. Description Fulfilled In the left pane of the planned data area, click an eNodeB you want to reconfigure. The object navigation tree is displayed in the lower left area. □Yes □No You can search MOs in the object navigation tree by clicking the Search tab and typing the MO information you want to configure. The CME automatically finds the corresponding MOs. tio i n i ng e aw ic f i rt i n ni ei H w a u a Tr g & Ce io t a n Hu ra T i & r e C a c i tif n Step 2. Description Fulfilled Double-click the MO you want to configure and edit the planned data in the right pane. □Yes Click □No to save the configured data. tio a c i tif Task 3 Data preparation by using the MML Step Description 1 Prepare MML configuration scripts. ng ni 8.4 Engineering Implementation e aw 8.4.1 CME-based Operations Hu ai r iT Step Description 1 Set the eNodeB engineering maintenance mode to expand status to prevent any alarm from being reported during the reconfiguration. t c ifi io t a n On the U2000 Client, choose Configuration > Settings > Maintenance Mode (application style) or Maintenance > Maintenance Mode (traditional style). n ni i ei H & w a u a Tr g & r e C r e Fulfilled C □Yes □No Fulfilled □Yes □No n Step 2 Description Fulfilled Click □Yes at the upper left corner of the Maintenance Mode window. In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE maintenance mode to a customized expand status. Click OK to complete the setting. □No tio i n i ng e aw ic f i rt i n ni ei H w a u a Tr g & Ce io t a n Hu ra T i & r e C a c i tif n Step Description Fulfilled 3 Deliver and activate the configuration on the eNodeB. □Yes On the menu bar of the planned data area, choose Area Management > Planned Area > Export Incremental Scripts (CME client mode) or CME > Planned Area > Export Incremental Scripts (U2000 client mode) to start the wizard of exporting scripts. □No Select Launch script executor only in the wizard to activate exported scripts for data to take effect on the live network. ng i n i e aw io t a ic f i Set the Maintenance Mode of rtthe eNodeB to NORMAL. e On the U2000 Client, choose C Configuration > Settings > Maintenance Mode (application style) or Maintenance > Maintenance Mode (traditional style). & ng i in a r T i 4 e Hu aw n Hu ra T i & tio r e C a c i tif □Yes □No n Step Description Fulfilled tio ng i n i e aw 5 Click at the upper left corner of the Maintenance Mode window. In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE maintenance mode to NORMAL. Click OK to complete the setting. ic f i rt n ni i ei H n Hu ra T i w a u a Tr g & Ce io t a & r e C a c i tif □Yes □No n 8.4.2 MML-based Operations Step Description Fulfilled 1 Set the eNodeB engineering maintenance mode to expand status to prevent any alarm from being reported during the reconfiguration. □Yes □No Run the following command: SET MNTMODE: MNTMODE=Expand in MML input window. tio 2 From the main menu of the U2000 client, choose Trace and Maintenance > Maintenance > MML Command (application style) or Maintenance > MML Command (traditional style). i n i ng e aw ic f i rt i n ni ei H w a u 3 a Tr g & io t a n Hu ra T i a c i tif & □Yes r e □No C Ce In the left pane, select a base station type, for example, BTS3900 LTE. In the navigation tree, select the eNodeBs to be reconfigured, click to enter the script mode. □Yes □No n Step Description Fulfilled tio i n i ng e aw 4 ic f i rt n ni i ei w a u 5 n In the right pane, copy and paste the MML commands to be executed in sequence to area 1. Click H io t a Hu ra T i & a Tr Ce to create a batch processing task. g & In the New Task dialog box, enter a name in Task Name. Choose Other > MML Script in Task Type. Set Execution Type, and click Next. r e C a c i tif □Yes □No □Yes □No n Step Description Fulfilled tio 6 i n i Set the time or period to execute the task and click Next. e ic f i rt i n ni ei H w a u 7 a Tr g & io t a n ng w a Hu ra T i & r e C a c i tif □Yes □No Ce Select the Select NE option. Select the eNodeBs on which the MML scripts are to be executed, set Run Mode and Execution Result, and click Finish. In the displayed Confirm dialog box, select the Continue to execute the MML script task option, and then click Yes. □Yes □No n Step Description Fulfilled tio i n i ng ra T i & e w a Run the following command: SET MNTMODE: MNTMODE=NORMAL in MML u input window. H n it o a c i f i t r e C & ngVerification 8.5 Engineering i in a Step Description r T 1 eiCheck whether MOs have been modified. w a Hu 8 Set the Maintenance Mode of the eNodeB to NORMAL. r e C a c i tif □Yes □No Fulfilled □Yes □No n 9 Changing the eNodeB ID 9.1 Application Scenario The previous eNodeB ID plan is inappropriate and a new plan is required. 9.2 Task Description The eNodeB ID of LTETEST010 needs to be changed from 10 to 100 as figure 6 shows. tio Figure 9-1 eNodeB ID changes eNodeB ID:10→100 i n i ng 9.3 Engineering Preparation 9.3.1 Information Collection Whether… ic f i rt The eNodeB ID needs to be collected. i n ni ei H w a u a Tr g & Ce e aw Hu n it oJudging a □Yes □No ra T i & r e C Writing the specific information a c i tif n 9.3.2 Data Preparation Task 1 Data preparation by using the CME-provided ID/Name Adjustment Data Step 1. Description Fulfilled To ensure that the associated parameters of the external cells in the current data area are consistent, choose System > Options (CME client mode) or CME > Options (U2000 client mode) on the menu bar of the main window. The setting function is started. □Yes ng i n i 2. r e C The CME-provided "radio data planning file" supports automatic update of the information about external cells when cell-related parameters are modified. On the LTE network, this option applies only to radio network planning data and ID/name modification. io t a n Hu On the Cell Parameter Auto-Synchronization Policy tab page, select Auto synchronize cell parameters in the entire network and click OK. n ni i ei w a u 3. tio ic f i rt H e aw ra T i & □No a Tr g & a c i tif □Yes □No Ce On the menu bar of the planned data area, choose CME > LTE Application > Export Data > Export ID/Name Adjustment Data (U2000 client mode) or LTE Application > Export Data > Export ID/Name Adjustment Data (CME client mode). Export the eNodeB names and IDs, and cell and local cell IDs and names to a □Yes □No n Step Description Fulfilled file. tio 4. A dialog box is displayed for you to select NEs. Add the NEs to be reconfigured from the left pane to the right pane, and click Next. i n i ng e aw ic f i rt i n ni ei H w a u a Tr g & Ce io t a n Hu ra T i & a c i tif r □Yes e C □No n Step 5. Description Fulfilled Click . Specify a save path for the exported file, and click Next. The CME starts the export. After the export is complete, click Finish. □Yes □No tio i n i ng e aw 6. Open the exported file, in the ID Modification Of eNodeB sheet of the file, modify the eNodeB ID parameter value of the eNodeB to the target value. Then, save the modification and close the file. ica f i t r n ni i H a Tr g & Ce eiImport the changed IDs and names to CME. w a u 7. n it o Hu ra T i & On the menu bar of the planned data area, choose LTE Application > Import Data > Import ID/Name Adjustment Data (CME client mode) or CME > LTE Application > Import Data > Import ID/Name Adjustment Data (U2000 client mode). A dialog box is displayed for you to select files. r e C a c i tif □Yes □No □Yes □No n Step Description Fulfilled tio 8. Click 9. After the import is complete, click Finish. n i ra iT e aw Hu a c i , select the file to be imported, and click Next. The CME starts the import. □Yesif t r □No Ce & g in n ai r T i e w a u H n it o a c i f i t r e C & g in □Yes □No n Step Description Fulfilled tio i n i ng 9.4 Engineering Implementation 9.4.1 CME-based Operations Description 1 Hu Hu n it o a mode to expand status to prevent any alarm Set the eNodeB engineering maintenance c i from being reported during the reconfiguration. f i t On the U2000 Client, choose > Settings > Maintenance Mode r Configuration e (application style) or Maintenance > Maintenance Mode (traditional style). C & ng i in a r T i Step e aw e aw ra T i & r e C a c i tif Fulfilled □Yes □No n Step 2 Description Fulfilled Click □Yes at the upper left corner of the Maintenance Mode window. In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE maintenance mode to a customized expand status. Click OK to complete the setting. In the displayed Confirm dialog box, click Yes. □No tio i n i ng e aw io t a ic f i Run MOD GLOBALPROCSWITCH to set Update eNB Configuration Via X2 t r Switch to OFF. Ce & ng i in a r T i 3 e Hu aw n Hu ra T i & r e C a c i tif □Yes □No n Step Description Fulfilled 4 Run MOD ENODEBALGOSWITCH to set ANR algorithm switch to CLEAR ALL. □Yes □No tio 5 a c i tif Deliver and activate the configuration on the eNodeB. & On the menu bar of the planned data area, choose Area Management > Planned Area > Export Incremental Scripts (CME client mode) or CME > Planned Area > Export Incremental Scripts (U2000 client mode) to start the wizard of exporting scripts. i n i ng e aw ic f i rt 6 n Select Launch script executor only in the wizard to activate exported scripts for data to take effect on the live network. n ni i ei H io t a Hu ra T i w a u a Tr g & Ce r □Yes e C □No □Yes □No n Step Description Fulfilled tio i n i ng ra T i e w a Set the Maintenance Mode of the eNodeB to NORMAL u On the U2000 Client, choose Configuration > Settings H > Maintenance Mode (application style) or Maintenance > Maintenance Mode (traditional style). n it o a c i f i t r e C & g n i Click upper left corner of the Maintenance Mode window. In the Set n at theMode i Maintenance box, select the eNodeBs to be configured. Set NE a mode todialog r maintenance NORMAL. Click OK to complete the setting. In the displayed T dialog box, click Yes. iConfirm 7 8 e Hu aw & r e C a c i tif □Yes □No □Yes □No n Step Description Fulfilled tio i n i ng e aw Hu ra T i & r e C a c i tif n o i 9.5 Engineering Verification t a c i Step Description Fulfilled f i t r 1 Check whether MOs haveebeen modified. □Yes C □No & ng i in Cabinet and Subrack No. 10 Changing a r T 10.1 Application Scenario ei w a The cabinet and subrack numbers of an eNodeB were inappropriately planned and require replanning. u H 10.2 Task Description Change the RRU subrack number of the eNodeB "FDD eNodeB102" to 66. n 10.3 Engineering Preparation 10.3.1 Information Collection Information Description Cabinet number Subrack number within the cabinet tio RRU subrack number a c i tif r e C Task 1 Data preparation by using the CME-provided ID/Name Adjustment Data & Step Description Fulfilled g n i 1. On the menu bar of the planned data area, choose CME > LTE Application in > Export □Yes Data > Export Cabinet and Subrack No. Adjustment Data (U2000 client mode) or a rNo. Adjustment □No LTE Application > Export Data > Export Cabinet and Subrack T Data (CME client mode) to enable the data export function. i e w a u H n it o a c i f i t r e 2. In the displayed dialogC box, specify the export scenario, export mode, related eNodeB, □Yes and export path. Then, click Next to export the cabinet and subrack numbers of the & □No eNodeB from the CME to a file. g in n ai r T i e w a u H 10.3.2 Data Preparation n Step Description Fulfilled tio i n i ng 3. ic f i rt i n ni ei H w a u 4. a Tr g & io t a e aw After the export is complete, click Finish. n Hu ra T i & r e C a c i tif □Yes □No Ce Open the exported file. In the Base Station CN SRN Adjustment sheet of the file, modify the cabinet and subrack numbers of the eNodeB to the target values. Then, save the modification and close the file. □Yes □No n Step 5. Description Fulfilled On the menu bar of the planned data area, choose CME > LTE Application > Import Data > Import Cabinet and Subrack No. Adjustment Data (U2000 client mode) or LTE Application > Import Data > Import Cabinet and Subrack No. Adjustment Data (CME client mode) to enable the data import function. □Yes □No tio ng i n idialog box, In the displayed Import Cabinet and Subrack No. Adjustment Data a r specify the save path, select the NE, and click Next. T i e w a u H n it o a c i f i t r e C & ng i in a r T i 6. e Hu aw & r e C a c i tif □Yes □No n Step 7. Description Fulfilled Observe the adjustment progress. After the adjustment is complete, the "Operation succeeded." message will be displayed. Then, click Finish. □Yes □No tio i n i ng e aw Hu ra T i & n o i 10.4 Engineering Implementation t a ic Step Description f i t rmaintenance 1 Set the eNodeB engineering mode to expand status to prevent any alarm e C the reconfiguration. from being reported during & choose Configuration > Settings > Maintenance Mode On the U2000 Client, (application style) ng or Maintenance > Maintenance Mode (traditional style). i in a r T ei w a Hu r e C a c i tif Fulfilled □Yes □No n Step Description Fulfilled tio i n i ng e aw 2 Click n Hu ra T i & at the upper left corner of the Maintenance Mode window. io t a In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE maintenance mode to a customized expand status. Click OK to complete the setting. ic f i rt i n ni ei H w a u a Tr g & Ce r e C a c i tif □Yes □No n Step Description Fulfilled 3 Deliver and activate the configuration on the eNodeB. □Yes On the menu bar of the planned data area, choose Area Management > Planned Area > Export Incremental Scripts (CME client mode) or CME > Planned Area > Export Incremental Scripts (U2000 client mode) to start the wizard of exporting scripts. □No Select Launch script executor only in the wizard to activate exported scripts for data to take effect on the live network. ng i n i e aw ic f i rt n e C On the U2000 Client, choose Configuration > Settings > Maintenance Mode (application style)& or Maintenance > Maintenance Mode (traditional style). g in n ai r iT 4 Set the Maintenance Mode of the eNodeB to NORMAL. e aw Hu io t a Hu ra T i & tio r e C a c i tif □Yes □No n Step Description Fulfilled tio ng i n i e aw 5 Click at the upper left corner of the Maintenance Mode window. In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE maintenance mode to NORMAL. Click OK to complete the setting. ic f i rt n ni i ei H n Hu ra T i w a u a Tr g & Ce io t a & r e C a c i tif □Yes □No n 10.5 Engineering Verification Step Description Fulfilled 1 Check whether MOs have been modified. □Yes □No 11 Replacing the Main Control Board tio 11.1 Application Scenario r e C When the current main control board cannot meet service requirements, it needs to be replaced. 11.2 Task Description i n i ng & a c i tif Initially, the eNodeB is configured with LMPT board. With the increase of traffic, we need to replace the LMPT board with UMPT board. Figure 7 shows the topology changes when an LMPT using optical port 0 is replaced with a UMPT using optical port 1. Figure 11-1 Topology changes ic f i rt & e aw io t a n Hu ra T i Ce 11.3 Engineering g Implementation in n 11.3.1 Information Collection ai r T Whether… i e Thew MPT information needs to be collected. a u H Judging □Yes □No Writing the specific information n 11.3.2 Data Preparation Task 1 Data preparation by using the "batch reconfiguration" mode of the CME Step 1. Description Fulfilled On the menu bar, choose Advanced > Customize Summary Data File (CME client mode) or CME > Advanced > Customize Summary Data File (U2000 client mode). A dialog box is displayed for you to open the summary data file. □Yes □No tio i n i ng ra T i & 2. e w In the dialog box, select the following options in sequence a Default > NodeB/eNodeB u Bulk Configuration > eNodeB > base station version, Click OK to enable the H function of customizing a summary data file. n it o a c i f i t r e C & ng i in a r T i r e C a c i tif □Yes □No e aw Hu 3. Click . Select a scenario-based template: Device Data Reconfiguration > Replacing the Main Control Board When No SeGW Is Deployed, select MOs you want to change, and then click OK. □Yes □No n Step Description Fulfilled tio ng i n i 4. 5. ra T Click , specify a save path for the exported file, save the summary i data file to a local PC. The CME automatically customizes the parameter e names contained in the w template in the summary data file. a Hu n it o a c i f i t r e C & ng i in a r on the parameter names in the summary data file, export the eNodeB data to be Based T ireconfigured from the planned data area to the summary data file. e On the menu bar of the planned data area, choose LTE Application > Export Data > aw Hu & Export Base Station Bulk Configuration Data (CME client mode) or CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data (U2000 client mode). The data export function is enabled. r e C a c i tif □Yes □No □Yes □No n Step Description 6. Fulfilled i n i ng e aw ic f i rt i n ni ei H w a u a Tr g & Ce io t a n Hu ra T i a c i f i □No t r e C □Yes Select the following options in sequence "Scenario > Adjust data by NE > version >NEs need to be adjusted" in the pop-up dialog box. Click "Next". & tio n Step 7. Description Fulfilled 1. Select Bulk configuration template. □Yes 2. In Bulk configuration data file, select the prepared file and export configuration data from the CME based on the MOs in this file. □No 3. In Export path, specify a save path for the file that contains the exported data. 4. Click "Next", the CME verifies the configuration data to be exported. After the export is complete, click "Finish". i n i ng e aw io t a 8. Open the local summary data file and reconfigure data in the summary data file based on planned data. ic f i Import the edited summary data t file into the CME. r On the menu bar of the planned data area, choose LTE Application > Import Data > Ce Configuration Import Base Station Bulk Data (CME client mode) or CME > LTE Application > Import & Data > Import Base Station Bulk Configuration Data (U2000 client g mode). The data import function is enabled. n ni i ra T i 9. e aw Hu n Hu ra T i & tio r e C a c i tif □Yes □No □Yes □No n Step 10. Description Fulfilled Select files to import and data types to adjust, select "I have read the note" and click Next. □Yes □No tio i n i ng Select base stations whose data you want to import and click Next. ic f i rt n ni i ei H e aw 11. ra T i w a u a Tr g & Ce io t a n Hu & r e C a c i tif □Yes □No n Step 12. Description Fulfilled After the import is complete, click "Finish". Finish the data preparation by using "batch reconfiguration" mode of CME. □Yes □No tio i n i ng 11.3.3 Commissioning Preparation Step on Description 1. ti a ic e Hu aw ra T i & Upload the software package of a target version that you have obtained from Huawei engineers and decompressed the software package on a local PC to the U2000 server. tif On the U2000 client, choose SON > Self Planning > Auto Deployment (application style) or SON > Auto Deployment (traditional style). The Auto Deployment window is displayed. i n ni ei H w a u a Tr g & r e C r e C a c i tif Fulfilled □Yes □No n Step 2. Description Fulfilled Select tab page Prepare File & Data > Software & Cold Patch, Click Transfer, and choose From OSS Client to OSS Server from the shortcut menu. The NE File Transfer dialog box is displayed. □Yes □No tio i n i 3. □Yes respectively. Click in the Source Path area. The Select Folder dialog box is displayed. Select the folder that contains the software package to be uploaded, and click OK. The NE File Transfer dialog box is displayed. □No ic f i rt n ni i ei w a u 4. & Select the NE type and file type from the NE Type and File Type drop-down lists, e aw H ng r e C a c i tif a Tr g & io t a n Hu ra T i Ce Click OK. The NE File Transfer dialog box is closed, and the upload starts. Wait for the upload over. □Yes □No n Step Description Fulfilled tio i n i ng 5. Uploading a Commissioning License e w a Hu ra T i & On the U2000 client, choose SON > Self Planning > Auto Deployment (application style) or SON > Auto Deployment (traditional style). The Auto Deployment window is displayed. ic f i rt i n ni ei H w a u a Tr g & Ce io t a n r e C a c i tif □Yes □No n Step 6. Description Fulfilled Click the Prepare File & Data tab and then the License tab. Click Transfer, and choose From OSS Client to OSS Server from the shortcut menu. The Upload License dialog box is displayed. □Yes □No tio i n i 7. ic f i rt n ni i ei w a u 8. ra T i & Click in the Source Path area. The Select Folder dialog box is displayed. Select the file to be uploaded, and click Open. The Upload License dialog box is displayed. Click OK. The Upload License dialog box is closed, and the upload starts. e aw H ng a Tr g & io t a n Hu r e C a c i tif □Yes □No Ce The local engineer reports the site position and ESN of each base station to the remote engineer, helps remote engineers use the ESN to bind the base station to the U2000. □Yes □No n Step Description Fulfilled tio 11.4 Engineering Implementation Description 1 Hu & i n i any alarm Set the eNodeB engineering maintenance mode to expand status to prevent a r from being reported during the reconfiguration. T i On the U2000 Client, choose Configuration > Settings > Maintenance Mode e (application style) or Maintenance > Maintenance Modew (traditional style). a u H n it o a c i f i t r e C & ng i in a r T i Step e aw ng r e C a c i tif Fulfilled □Yes □No n Step 2 Description Fulfilled Click □Yes at the upper left corner of the Maintenance Mode window. In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE maintenance mode to a customized expand status. Click OK to complete the setting. In the displayed Confirm dialog box, click Yes. □No tio i n i ng e aw io t a ic f i t eNodeB and remove the main control board to be (Local operation) Power offrthe replaced. e C (Local operation) Install the new main control board and power on the eNodeB. & g from the main topology. Remove the eNodeB n i From thenmain menu of the U2000, choose Topology > Main Topology(application style a oritraditional style). r iT 3 4 5 e aw Hu 6 n Hu ra T i & Right-click the eNodeB to be removed and choose Delete. In the displayed Confirm dialog box, click Yes. In the displayed Deletion Result dialog box, verify that Result is Succeeded, and then click Close. r e C a c i tif n Step Description Fulfilled tio i n i ng 7 H e Data (CME client On the menu bar, choose Advanced > Export Auto Deployment w mode) or CME > Advanced > Export Auto Deployment (U2000 client mode). a Data A dialog box is displayed for you to export auto-deployment data. u H n it o a c i f i t r e C & ng i in a Tr Deliver and activate the configuration on the eNodeB. eiSelect Site creation/expansion scenario, and click Next. w a u 8 ra T i & r e C a c i tif □Yes □No □Yes □No n Step Description Fulfilled tio ng i n i ra T Select the base stations whose auto-deployment data you want ito export, and click e Next. w a u H n it o a c i f i t r e C & ng i in a r T i 9 e aw Hu10 & Click . Select a save path for the exported file and a method for processing data, and click Next. r e C a c i tif n Step Description Fulfilled tio i n i ng ra T i e w View data in the base station deployment list, ensure that a the software version is u correct, input new ESN, and click Next. The CME starts H to verify data correctness and exports the data. n it o a c i f i t r e C & ng i in a r T i 11 e aw Hu 12 & r e C If the export is successful in U2000, select Open the Auto Deployment window, click Finish. The CME automatically switches to the auto-deployment window and creates a commissioning task. a c i tif n Step Description Fulfilled tio i n i ng ra T i 13 Hu e w a commissioning tasks. Click Select one or more commission tasks and right-click these u Start. The Task Parameter Settings window is displayed. H n it o a c i f i t r e C & ng i in a r T i e Set Step Parameters and Extended Parameters as planned. Click OK. aw 14 & r e C a c i tif n Step Description Fulfilled tio ng i n i 15 e ra T i & r e C a c i tif After the project quality check of an NE is complete, the commissioning tasks enter the Waiting for Confirmation state. Manually confirm that the commissioning is complete. aw Hu Right-click the tasks and choose Confirm Completion from the shortcut menu to confirm the completion. ic f i rt 16 n ni H n Ce ai r On T the U2000 Client, choose Configuration > Settings > Maintenance Mode Set the Maintenance Mode of the eNodeB to NORMAL. ei(application style) or Maintenance > Maintenance Mode (traditional style). w a u 17 g & io t a Click at the upper left corner of the Maintenance Mode window. In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE □Yes □No □Yes □No n Step Description Fulfilled maintenance mode to NORMAL. Click OK to complete the setting. In the displayed Confirm dialog box, click Yes. tio i n i ng e aw c io t a n Hu ra T i & r e C a c i tif 11.5 Engineering Verification ifi t r e C Step Description 1 Check whether MOs have been modified. i ni a Tr ng & Fulfilled □Yes □No 12 Transmission Capacity Expansion from One UMPT Board to ei Two aw UMPT Boards (FDD/NB-IoT) Hu12.1 Application Scenario You can expand transmission capacity from one UMPT board to two UMPT boards if the volume of traffic that flows over the eNodeB configured with a single UMPT board cannot meet service requirements. Currently, the model of the UMPT board used for LTE is UMPTb. The total uplink and downlink traffic volume supported by UMPTb+UMPTb can reach 4 Gbit/s. n 12.2 Task Description After the UMPT board is added, two UMPT boards must be connected to different ports of transmission equipment to ensure transmission traffic. Assume that the two UMPT boards are connected to different ports of the same switch and router. Figure 8 shows the topology changes before and after the reconfiguration. Figure 12-1 Topology changes tio i n i ng e aw io t a n Hu ra T i & r e C a c i tif 12.3 Engineering Preparation fic ti r 12.3.1 Information Collection Ce & Information g Device IP address ofin the new UMPT board in a r the route from the new UMPT Information about T board toithe S-GW e w VLAN ID for the new UMPT board a HuID of the end point group to which the new local end on the user plane is added Description Including the device IP address, subnet mask, and number of the physical port in use. Including the local device IP address and the next hop IP address. n 12.3.2 Data Preparation Task 1 Data preparation by using the "batch reconfiguration" mode of the CME Step 1. Description Fulfilled On the menu bar, choose Advanced > Customize Summary Data File (CME client mode) or CME > Advanced > Customize Summary Data File (U2000 client mode). A dialog box is displayed for you to open the summary data file. □Yes □No tio i n i ng e aw 2 In the dialog box, select the following options in sequence Default > NodeB/eNodeB Bulk Configuration > eNodeB > base station version, Click OK to enable the function of customizing a summary data file. ic f i rt n ni i ei H on Hu ra T i & w a u a Tr g & Ce i at r e C a c i tif □Yes □No n Step Description 3 Fulfilled □Yes Click . Select a scenario-based template: Device Data Reconfiguration > Transmission Capacity Expansion from One UMPT Board to Two UMPT Boards, select MOs you want to change, and then click OK. □No tio i n i ng e aw Hu 4 ei H w a u 5 ra T i & r e C n o i Click and select a save path to save t the customized summary data file to the local a PC. ic Each MO to be configured is anifindependent List sheet. The values of parameters on rt file are blank. all sheets of the summary data e C & ng i in a Tr Based on the parameter names in the summary data file, export the eNodeB data to be reconfigured from the planned data area to the summary data file. On the menu bar of the planned data area, choose LTE Application > Export Data > Export Base Station Bulk Configuration Data (CME client mode) or CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data a c i tif □Yes □No □Yes □No n Step Description Fulfilled (U2000 client mode). The data export function is enabled. tio a c i tif 6 In the displayed dialog box, specify the scenario, adjustment mode, base station version, and select the NE to be reconfigured. Then, click Next. i n i ng e aw ic f i rt i n ni ei H w a u a Tr g & Ce io t a n Hu ra T i & r e □Yes C □No n Step Description Fulfilled 7 1. Select Bulk configuration template. □Yes 2. In Bulk configuration data file, select the prepared file and export configuration data from the CME based on the MOs in this file. □No 3. In Export path, specify a save path for the file that contains the exported data. 4. Click "Next", the CME verifies the configuration data to be exported. After the export is complete, click "Finish". i n i ng e aw Hu n o i t Open the local summary data file and reconfigure data in the summary data file based a on planned data. ic f i t file into the CME. Import the edited summary r data e On the menu bar of theC planned data area, choose LTE Application > Import Data > Import Base Station Bulk Configuration Data (CME client mode) or CME > LTE & Application > Import Data > Import Base Station Bulk Configuration Data (U2000 client ngmode). The data import function is enabled. i in a r T i 8 9 e Hu aw ra T i & tio r e C a c i tif □Yes □No □Yes □No n Step Description Fulfilled 10 Select files to import and data types to adjust, select "I have read the note" and click Next. □Yes □No tio i n i ng Select base stations whose data you want to import and click Next. ic f i rt n ni i ei H e aw 11 ra T i w a u a Tr g & Ce io t a n Hu & r e C a c i tif □Yes □No n Step Description Fulfilled 12 The CME verifies the imported data. If the verification is successful, the "Operation succeeded." message will be displayed. Then, click Finish. □Yes □No tio i n i ng e aw Hu ra T i & r e C a c i tif Task 2 Data preparation by using the GUI mode of CME Step 1. ei H n o i t click an eNodeB you want to reconfigure. The In the left pane of the planned data area, a object navigation tree is displayedic in the lower left area. f i You can search MOs in the object tree by clicking the Search tab and t wantnavigation r typing the MO information you to configure. The CME automatically finds the e corresponding MOs. C & ng i in a Tr Description w a u Fulfilled □Yes □No n Step Description Fulfilled tio i n i ng e aw ic f i rt 2. i H n ni w a u ei a Tr g & io t a n Hu ra T i & r e C a c i tif Ce Double-click the MO you want to configure and edit the planned data in the right pane. □Yes Click □No to save the configured data. n Task 3 Data preparation by using the MML Step Description Fulfilled 1 Prepare MML configuration scripts. □Yes □No 12.4 Engineering Implementation tio 12.4.1 Local Operations 1. Insert the new UMPT board into the subrack. 2. Connect the transmission port of the new UMPT board to the gateway. 12.4.2 Remote Operations 12.4.3 CME-based Operations Description 1. Hu & ra T Set the eNodeB engineering maintenance mode to expand status ei to prevent any alarm from being reported during the reconfiguration. w On the U2000 Client, choose Configuration > Settingsa> Maintenance Mode (application style) or Maintenance > Maintenance Mode (traditional style). Hu n it o a c i f i t r e C & ng i in a r T i Step e aw i n i ng r e C a c i tif Fulfilled □Yes □No n Step 2. Description Fulfilled Click □Yes at the upper left corner of the Maintenance Mode window. In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE maintenance mode to a customized expand status. Click OK to complete the setting. □No tio i n i ng e aw ic f i rt i n ni ei H w a u a Tr g & Ce io t a n Hu ra T i & r e C a c i tif n Step 3. Description Fulfilled Deliver and activate the configuration on the eNodeB. □Yes On the menu bar of the planned data area, choose Area Management > Planned Area > Export Incremental Scripts (CME client mode) or CME > Planned Area > Export Incremental Scripts (U2000 client mode) to start the wizard of exporting scripts. □No Select Launch script executor only in the wizard to activate exported scripts for data to take effect on the live network. ng i n i e aw ic f i rt n Ce Configuration > Settings > Maintenance Mode On the U2000 Client, choose (application style)& or Maintenance > Maintenance Mode (traditional style). ng i in a r T i 4. Set the Maintenance Mode of the eNodeB to NORMAL. e aw Hu io t a Hu ra T i & tio r e C a c i tif □Yes □No n Step Description Fulfilled tio ng i n i e aw u H Click at the upper left corner of the Maintenance Mode window. In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE n maintenance mode to NORMAL. Clicko it OK to complete the setting. a c i f i t r e C & ng i in a r T i 5. e Hu aw ra T i & r e C a c i tif □Yes □No n 12.4.4 MML-based Operations Step Description Fulfilled 1 Set the eNodeB engineering maintenance mode to expand status to prevent any alarm from being reported during the reconfiguration. □Yes □No Run the following command: SET MNTMODE: MNTMODE=Expand in MML input window. tio 2 From the main menu of the U2000 client, choose Trace and Maintenance > Maintenance > MML Command (application style) or Maintenance > MML Command (traditional style). i n i ng e aw ic f i rt i n ni ei H w a u 3 a Tr g & io t a n Hu ra T i a c i tif & □Yes r e □No C Ce In the left pane, select a base station type, for example, BTS3900 LTE. In the navigation tree, select the eNodeBs to be reconfigured, click to enter the script mode. □Yes □No n Step Description Fulfilled tio i n i ng e aw 4 ic f i rt n ni i ei w a u 5 n In the right pane, copy and paste the MML commands to be executed in sequence to area 1. Click H io t a Hu ra T i & a Tr Ce to create a batch processing task. g & In the New Task dialog box, enter a name in Task Name. Choose Other > MML Script in Task Type. Set Execution Type, and click Next. r e C a c i tif □Yes □No □Yes □No n Step Description Fulfilled tio 6 i n i Set the time or period to execute the task and click Next. e ic f i rt i n ni ei H w a u 7 a Tr g & io t a n ng w a Hu ra T i & r e C a c i tif □Yes □No Ce Select the Select NE option. Select the eNodeBs on which the MML scripts are to be executed, set Run Mode and Execution Result, and click Finish. In the displayed Confirm dialog box, select the Continue to execute the MML script task option, and then click Yes. □Yes □No n Step Description Fulfilled tio i n i ng ra T i & e w a Run the following command: SET MNTMODE: MNTMODE=NORMAL in MML u input window. H n it o a c i f i t r e C & ng Verification 12.5 Engineering i in a r Step Description T 1 eiCheck whether MOs have been modified. w a Hu 8 Set the Maintenance Mode of the eNodeB to NORMAL. r e C a c i tif □Yes □No Fulfilled □Yes □No n 13 Replacing BBPs 13.1 Application Scenario The baseband processing unit (BBP) in use is faulty and must be replaced with one of other BBP types. The BBP in use does not meet service requirements and must be upgraded. For example, upgrade the LBBPd to the UBBP or upgrade the LBBPc to the LBBPd or UBBP. tio 13.2 Task Description Replacing BBPs Reconfiguration Schemes Replacing an LBBPc with an LBBPd Modify Delta shift in the PUCCHCfg MO: ● If this parameter is set to 2, change the value to 1. Replacing an LBBPc with a UBBP Replacing an LBBPd with a UBBP Replacing a UBBP with an LBBPd i n ai r T i & g MO: Modify Indication of PRACH Configuration Index in the RACHCfg n i ● If this parameter is set to CFG(Configure), set PRACH inConfiguration Index to the a target value, ensuring that the values of PRACH Configuration Index for all cells in r T the same eNodeB are unique. ei no change is required. ● If this parameter is set to NOT_CFG(Not configure), aw Modify Board Type in the BBP MO tou UBBP(UBBP) and modify Base Band Work Standard to LTE_FDD(LTE FDD)H or LTE_TDD(LTE TDD). Modify Delta shift in the PUCCHCfg n MO: o ● If this parameter is setttoi 2, change the value to 1. a to 1 or 3, no change is required. ● If this parameter iscset i tif in the BBP MO to UBBP(UBBP) and modify Base Band Work Modify BoardrType Standard toe C LTE_FDD(LTE FDD) or LTE_TDD(LTE TDD). & Type in the BBP MO to LBBP(LBBP) and set Work Mode to Set Board g Division Duplex). nFDD(Frequency ● If this parameter is set to 1 or 3, no change is required. Replacing an LBBPd with an LBBPc r e C a c i tif 13.3 Engineering Preparation e H w a u13.3.1 Information Collection Information Information The delta shift of cells of the replaced BBP Modify the delta shift of the new BBP based on the information. The PRACH configuration index of cells of the replaced BBP Constraints on the setting of PRACH configuration indexes are different for the LBBPd and the LBBPc. The number of the slot where the baseband - n Information Information processing board to be replaced is located The maximum number of cells that can be established on the replaced BBP Check whether the new BBP supports the establishment of cells of such a quantity. 13.3.2 Data Preparation Task 1 Data preparation by using the "batch reconfiguration" mode of the CME Step Description 1 On the menu bar, choose Advanced > Customize Summary Data File (CME client mode) or CME > Advanced > Customize Summary Data File (U2000 client mode). A dialog box is displayed for you to open the summary data file. Fulfilled ng i n i e aw ic f i rt i n ni ei H w a u a Tr a c i tif g & Ce io t a n Hu ra T i & tio r □Yes e C □No n Step Description Fulfilled 2 In the dialog box, select the following options in sequence Default > NodeB/eNodeB Bulk Configuration > eNodeB > base station version, Click OK to enable the function of customizing a summary data file. □Yes □No tio i n i ng e aw 3 Click . Select a scenario-based template: Device Data Reconfiguration > Replacing Baseband Processing Units, select MOs you want to change, and then click OK. ica f i t r n ni i ei H n it o Hu ra T i & w a u a Tr g & Ce r e C a c i tif □Yes □No n Step Description 4 Click PC. Fulfilled and select a save path to save the customized summary data file to the local □Yes □No Each MO to be configured is an independent List sheet. The values of parameters on all sheets of the summary data file are blank. tio i n i ng 5 ra T i & Based on the parameter names in the summary data file, export the eNodeB data to be reconfigured from the planned data area to the summary data file. e w a Hu On the menu bar of the planned data area, choose LTE Application > Export Data > Export Base Station Bulk Configuration Data (CME client mode) or CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data (U2000 client mode). The data export function is enabled. ic f i rt i n ni ei H w a u a Tr g & Ce io t a n r e C a c i tif □Yes □No n Step Description Fulfilled 6 In the displayed dialog box, specify the scenario, adjustment mode, base station version, and select the NE to be reconfigured. Then, click Next. □Yes □No tio ng i n i 7 1. Select Bulk configuration template. e Hu aw ra T i & 2. In Bulk configuration data file, select the prepared file and export configuration data from the CME based on the MOs in this file. In Export path, specify a save path for the file that contains the exported data. ei H w a u 8 r e C a c i tif □Yes □No n o i t Click Next, the CME verifies the configuration data to be exported. After the a export is complete, click Finish. ic f i rt e C & ng i in a Tr Open the local summary data file and reconfigure data in the summary data file based on planned data. □Yes □No n Step Description Fulfilled 9 Import the edited summary data file into the CME. □Yes On the menu bar of the planned data area, choose LTE Application > Import Data > Import Base Station Bulk Configuration Data (CME client mode) or CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data (U2000 client mode). The data import function is enabled. □No tio i n i ng 10 On the Import Base Station Bulk Configuration Data page, select a path for saving the configuration file and select Adjust Data by NE. Select I have read the note and click Next. e ic f i rt n ni i ei H ra T i & w a u11 a Tr g & io t a n w a Hu r e C a c i tif □Yes □No Ce Select base stations whose data you want to import and click Next. □Yes □No n Step Description Fulfilled tio i n i ng 12 ra T i & r e C The CME verifies the imported data. If the verification is successful, the "Operation succeeded." message will be displayed. Then, click Finish. e ic f i rt n ni i ei w a u a Tr g & io t a n w a Hu a c i tif □Yes □No Ce H Task 2 Data preparation by using the GUI mode of CME Step 1. Description Fulfilled In the left pane of the planned data area, click an eNodeB you want to reconfigure. The object navigation tree is displayed in the lower left area. □Yes You can search MOs in the object navigation tree by clicking the Search tab and typing the MO information you want to configure. The CME automatically finds the corresponding MOs. □No n Step Description Fulfilled tio i n i ng e aw ic f i rt 2. i H n ni w a u ei a Tr g & io t a n Hu ra T i & r e C a c i tif Ce Double-click the MO you want to configure and edit the planned data in the right pane. □Yes Click □No to save the configured data. n Task 3 Data preparation by using the MML Step Description Fulfilled 1 Prepare MML configuration scripts. □Yes □No 13.4 Engineering Implementation a c i f i Description Fulfilled t r Set the eNodeB engineering maintenance mode to expand status to prevent any alarm Ce □Yes from being reported during the reconfiguration. & □No On the U2000 Client, choose Configuration > Settings > Maintenance Mode (application style) or Maintenance > Maintenance Mode (traditional style). ng i in a r T ei w a Hu n it o a c i f i t r e C & ng i in a Tr 13.4.1 CME-based Operations Step 1. ei H w a u tio n Step 2. Description Fulfilled Click □Yes at the upper left corner of the Maintenance Mode window. In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE maintenance mode to a customized expand status. Click OK to complete the setting. □No tio ng i n i e aw Hu 3. ei 4. H w a u 5. ra T i & n o i t Type set to IMMEDIATE(Immediate) to Run the BLK BRD command with Block a block a BBP. ic f i rt e C & ng i in a Runrthe DEA CELL command to deactivate the cells bound to the BBP by T r e C a c i tif □Yes □No □Yes configuring the eUCellSectorEqm or EuSectorEqmGroup MO. □No (Local operation) Replace the BBP. □Yes □No Notice In any of the following situations, ensure that the time interval between board removal and installations is greater than 5 minutes so that the cell can be activated. A UBBP is replaced with an LBBP n Step Description 6. Fulfilled An LBBP is replaced with a UBBP Deliver and activate the configuration on the eNodeB. □Yes On the menu bar of the planned data area, choose Area Management > Planned Area > Export Incremental Scripts (CME client mode) or CME > Planned Area > Export Incremental Scripts (U2000 client mode) to start the wizard of exporting scripts. □No Select Launch script executor only in the wizard to activate exported scripts for data to take effect on the live network. ng i n i e aw ic f i rt 7. ei w 8. a u 9. n Ce Run the UBL BRD command to unblock the BBP. n ni i H io t a Hu ra T i & a Tr g & tio r e C a c i tif □Yes □No Run the ACT CELL command to activate the cells that are deactivated owing to BBP replacement. □Yes Set the Maintenance Mode of the eNodeB to NORMAL. □Yes On the U2000 Client, choose Configuration > Settings > Maintenance Mode □No □No n Step Description Fulfilled (application style) or Maintenance > Maintenance Mode (traditional style). tio i n i ng e aw u H Click at the upper left corner of the Maintenance Mode window. In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE n to complete maintenance mode to NORMAL. Click OK the setting. o i t a c i f i t r e C & ng i in a r T i 10. e Hu aw ra T i & r e C a c i tif □Yes □No n 13.4.2 MML-based Operations Step 1. Description Fulfilled Set the eNodeB engineering maintenance mode to expand status to prevent any alarm from being reported during the reconfiguration. □Yes □No Run the following command: SET MNTMODE: MNTMODE=Expand in MML input window. tio 2. Run the BLK BRD command with Block Type set to IMMEDIATE(Immediate) to block a BBP. ng i n i e aw 3. Hu ra T i Run the DEA CELL command to deactivate the cells bound to the BBP by configuring the eUCellSectorEqm or EuSectorEqmGroup MO. io t a 4. n ic f i (Local operation) Replace thetBBP. r e C Notice In any of the following situations, ensure that the time interval between board removal and & installations is greater than 5 minutes so that the cell can be activated. g A UBBP n is replaced with an LBBP i An LBBP in is replaced with a UBBP a From Tr the main menu of the U2000 client, choose Trace and Maintenance > & a c i tif □Yes r e □No C □Yes □No □Yes □No eiMaintenance > MML Command (application style) or Maintenance > MML 5. H w a u Command (traditional style). □Yes □No n Step Description Fulfilled tio i n i ng e aw u H In the left pane, select a base station type, for example, BTS3900 LTE. In the n navigation tree, select the eNodeBs to be reconfigured, click to enter the script it o mode. a c i f i t r e C & ng i in a r T i 6. e Hu aw ra T i & r e C a c i tif □Yes □No n Step Description Fulfilled tio i n i ng e aw 7. ic f i rt n ni i ei w a u 8. n In the right pane, copy and paste the MML commands to be executed in sequence to area 1. Click H io t a Hu ra T i & a Tr Ce to create a batch processing task. g & In the New Task dialog box, enter a name in Task Name. Choose Other > MML Script in Task Type. Set Execution Type, and click Next. r e C a c i tif □Yes □No □Yes □No n Step Description Fulfilled tio 9. i n i Set the time or period to execute the task and click Next. e ic f i rt i n ni ei H w a u 10. a Tr g & io t a n ng w a Hu ra T i & r e C a c i tif □Yes □No Ce Select the Select NE option. Select the eNodeBs on which the MML scripts are to be executed, set Run Mode and Execution Result, and click Finish. In the displayed Confirm dialog box, select the Continue to execute the MML script task option, and then click Yes. □Yes □No n Step Description Fulfilled tio i n i ng 11. Run the UBL BRD command to unblock the BBP. 12. ic f i rt n Hu Ce Run the ACT CELL command to activate the cells that are deactivated owing to BBP replacement. n ni g & ai r Set T the Maintenance Mode of the eNodeB to NORMAL. eiRun the following command: SET MNTMODE: MNTMODE=NORMAL in MML 13. aw Hu io t a e aw ra T i & input window. r e C a c i tif □Yes □No □Yes □No □Yes □No n 13.5 Engineering Verification Step Description Fulfilled 1 Check whether MOs have been modified. □Yes □No tio i n i ng e aw ic f i rt i n ni ei H w a u a Tr g & Ce io t a n Hu ra T i & r e C a c i tif n Recommendations Huawei Learning Website http://learning.huawei.com/en Huawei e-Learning n it o http://support.huawei.com/learning/NavigationAction!createNavi?navId=MW 000001_term1000025144&lang=en a c i if t r Ce http://support.huawei.com/learning/NavigationAction!createNavi?navId=_31 & &lang=en g in n Find Training ai r T i http://support.huawei.com/learning/NavigationAction!createNavi?navId=_trai e w ningsearch&lang=en a u H n More Information it o a c i f i t r Huawei learning APP e C & ng i in a r T ei w a Hu Huawei Certification 版权所有© 2018 华为技术有限公司
