SPD_SRAN7.0_CME-Based Data Configuration Methods and Key Points_20120420-A-1.2

8/10/2019 SPD_SRAN7.0_CME-Based Data Configuration Methods and Key Points_20120420-A-1.2

1/83

www.huawei.com

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

CME-based DataConfiguration Methods and

Key Points

OSS DevelopmentDept.1 - CME Development Department


2/83

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved. Page2

References

CME V9R12 Product Manual

BSC6900 GU V9R14 Product Manual

MBTS GL V1R5Product Manual


3/83


Objectives

After completing the course, you should be able to:

Understand the CME-based MBTS data configuration process.

Accomplish MBTS data configuration.


Know the concept and methods of data configuration by using CME.

Know the data configuration methods for SRAN7.0 site deployment.


4/83


Contents

1. CME Overview

2. MBTS Data Preparation

3. MBTS Data Configuration

4. MBTS Data Check

5. MBTS Activation Data Export


5/83


References

CME V9R12 Product Manual

BSC6900 GU V9R14 Product Manual

MBTS GL V1R4 Product Manual


6/83


Objectives


Understand CME-based MBTS data configuration procedure

Accomplish MBTS data configuration


Know the concept and methods of data configuration by using CME

Know the data configuration methods for SRAN7.0 site deployment


7/83


Contents

1. CME Overview


3. MBTS Data Configuration Site Deployment

4. MBTS Data Check



8/83


CME Main Window


9/83


CME Concept

Current Data Area

The CME configuration areas consist of one current data area and

multiple planned data areas.

The current data area stores configuration data. The data can only be

viewed.


10/83


CME Concept

Planned Data Area

The planned data area is used for planning and configuring data. Users

can create multiple planned data areas based on the data in the current

data area to perform different configuration tasks.

By dividing planned data areas, users can have their own workspace,

which allows multiple engineers to work in parallel. The modifications in

one area do not affect the services on the live network before the

modified configuration data is activated. This enhances the reliability and

security of configuration data.


11/83


Data Configuration of the Current Data

Area and the Planned Data Area


12/83


Data Configuration Process

Configuration preparation Start Connect an NE to the M2000

Start the CME client

Synchronize the data on the live

network with current area

Create a Planned Area

Create a BTS (GUI)

Adjust MBTS data configuration

Check data consistency

Export an activation script

Prepare

Configure

Export

Set primary/secondary

technology mode


13/83


Contents

1. CME Overview



4. MBTS Data Check



14/83


Contents


1.1 Configuration Scenario

1.2 Prepare Data

1.3 Create Planned Data Areas on CME

1.4 Set MBTS Primary/Secondary Mode on CME


15/83


Configuration Scenario

Working in single mode

Use the MRFU/MRRU module and work only in GSM mode.

Use the MRFU/MRRU module and work only in LTE mode.

Working in dual modes Working in combined cabinet mode means that the RFU module is

working in either GSM mode or LTE mode.

Working in co-module means that an MRFU/MRRU supports functions

of both the GSM and LTE modes.


16/83


Configuration Preparation

Collect the MBTS planned data

Collect the common device data of the BTS and eNodeB

Collect the BTS data

Collect the transport layer data and radio layer data of the eNodeB

Prepare the MBTS template


17/83


Start the CME Client


18/83


Create a Planned Data Area


19/83


MBTS Primary/Secondary Technology

Management

The CME allows users to set the primary/secondary technology for an MBTS. The

parameter values of the BTS of the primary technology serve as references for

displaying common parameters of MBTS common devices (common MRRU/MRFU

excluded) on the GUI, checking data consistency, and modifying data.


20/83


Contents

1. CME Overview



4. MBTS Data Check



21/83


Choose the method of site deployment based on the capacity and mode of

BTS.

Site Deployment Mode

You should determine the method of site deployment before preparing data. Generally, the

combination of two methods is adopted. For batch site deployment, a special BTS, whose

data configuration is different from others, cannot be created by preparing data in batches.

You need to create the special BTS on the GUI. In addition, you also need to complete the

template data of a typical configuration scenario on the GUI before the batch site deployment.

Small-scaled site

deployment

Site deployment

scenario

Batch site

deployment

Be applicable to the scenario: The

number/model of BTSs is less than 2

Be applicable the scenario: The BTSs

have much data with the same model.

Complete site deployment on the GUI

Create a batch of BTS data files in excel by

2G/3G summary data files (BTS negotiation

and planning data files/IUB data files). Import a

batch of BTS data in excel format into CME tocreate MML scripts.


22/83


Contents


3.1 Configure the Template MBTS Data (GUI)

3.2 Configure the MBTS Data in Batches (Summary)

3.3 Expand Single Mode to Dual Mode in Batches


23/83


Configure the MBTS Data Template (GUI)

Start

Create an eNodeB

End

Create a BTS

Bind BTS and eNodeB


24/83


Process for Adding eNodeB Data

Start

Create an eNodeB

Add eNodeB basic information

Create eNodeB device data

Create eNodeB transport layer data

Create eNodeB radio layer data

Create eNodeB configuration data

End

Step 1 Create a Logical eNodeB


25/83


Step 1 Create a Logical eNodeB

Page25

S 2 C fi N d B D i D


26/83


Step 2 Configure eNodeB Device Data

Configure the Cabinet Data and the BBU3900

Data


27/83



Configure the Cabinet Data and the

BBU3900 Data


28/83



Configure the Radio Frequency Unit (RFU)


29/83


Step 3 Create eNodeB Device Data

If the RF module in the same slot, subrack, and cabinet is

configured for the BTSs, the module runs in dual modes. The

BTS with the RF module is called co-module BTS. If the

module in the same cabinet supports either of dual modes,

the BTSs are called combined cabinet


30/83



Configure the Monitoring Unit

Page30


31/83



Configure the Powder Module

Page31


32/83



Configure the Antenna Data

Page32



33/83



Configure the User-defined Alarm

Page33


34/83


Step 3 Create eNodeB Transport Layer Data


35/83


BTS Data Configuration Process (Abis TDM

Transmission)

Start

Add a BTS

Add a cell

Set a ARFCN

Add a TRX

Check BTS data

End

Activate BTS data

Configure device data

Bind logical TRXs to cells


36/83


BTS Network Topology

1. Area for selecting

interface boards

4. Area for displaying

cells and TRXs


operation buttons


information

In left pane of the topology

view, the area marked 19

represents BSC interface

boards.

6. Area for searching,

refreshing and Help

12

34

5

6


37/83


Step 1 Add a BTS


38/83


Step 1 Add a BTS


39/83


Step 2 Add a Cell


40/83


Step 3 Configure an ARFCN


41/83


Step 4 Add a TRX Board


42/83


Step 4 Add a RUX Board

If the RF module in the same slot, subrack, and cabinet is

configured for the BTSs, the module runs in dual modes.

The BTS with the RF module is called co-module BTS. If

the module in the same cabinet supports either of dual

modes, the BTSs are called combined cabinet base

stations.


43/83


Step 5 Bind Logical TRXs to Cells


44/83


Step 5 Bind Logical TRXs to Cells


45/83


Step 6 Configure Device Data About BTS.


46/83


Configuration Rules of the Board

Board

Type Configuration Principle Slot Number Subrack Number

DEMU It is configured manually. 0, 1 2

Remarks: The

APMU and DTCU

boards can be

configured in slots

0 to 23 in subrack

5.

APMU

DPMUIt is configured manually. 25

DTCU It is configured manually. 6, 7

FMU/FMU

AIt is configured manually. 811

GATM It is configured manually. 16, 17

GTMU It is configured automatically. 6

0UBFA It is configured automatically. 16

UEIU It is configured manually.18, 19

UPEU It is configured automatically.


47/83


Step 7 Check BTS Data


48/83


Step 8 Activate BTS Data


49/83


(Optical) Export MML ScriptsClick here

S C f (


50/83


BTS Data Configuration Process (Abis

IP Transmission)Start

Configure IP address for the port/device

Add BTSs/cells

Configure ARFCNs

Add TRX boards

Set IP address and IP attributes of theBTS

End



Verify/Activate BTS data

The procedure is the

same as that of TDM

configuration.

C fi IP Add f P t f I t f


51/83


Configure IP Address for Ports of Interface

Boards and the Device at the BSC Side


52/83


Add a BTS

Set IP Address and IP Attributes at the BTS Side


53/83


Set IP Address and IP Attributes at the BTS Side


54/83


BTS Data Configuration Process (IP Over E1)

Start

Set IP address for the PPP or MLPPP link at the

BSC side

Add BTSs/cells

ConfigureARFCNs

Add TRX boards

Set IP address and IP attributes at the BTS side

End



Verify/Activate BTS data

The procedure is thesame as that of Abis

IP transmission.


55/83


Set IP Address for the PPP or MLPPP Link

Add BTS


56/83


Add a BTS

C fi MBTS D t With t U i


57/83


Configure MBTS Data Without Using

the Template Bind BTS and eNodeB

Start

Create an eNodeB

End

Create a BTS

Bind BTS and eNodeB

Bi d BTS d N d B


58/83


Bind BTS and eNodeB


59/83


Contents


3.1 Configure the MBTS Template Data (GUI)

3.2 Configure MBTS Data in Batches (Summary)

3.3 Expand to Dual Modes from the Single Mode


60/83


Contents


1.1 Prepare the MBTS template

1.2 Define a Summary Data File

1.3 Import Summary Data Files for Site Deployment


61/83


Scenario

Be suitable for batch sitedeployment

Type the planned data for

site deployment into the

CME planned file andcomplete data creation by

importing the files.

Create MBTSs by Exporting Planned Data

Data Plan Data Preparation Data Activation

CME

NE

Engineer

GBTS planned files

for site deployment

GSM Engineer

eNodeB planned

files for site

deployment

LTE Engineer

GBTS planneddata

eNodeB planneddata

Engineer

MBTS mapping

between GBTS

and eNodeB

MBTS template(including the

content of bothGBTS andeNodeB)

Engineer

Import ExportCreate MBTSwizard

ScriptfilesActivate

BSC

GBTS /eNodeB

GBTS /eNodeB

Engineer

Page62


62/83


Configuration Procedure

Step 1 Specify the site deployment scenario.

Specify whether to deploy a new site or

expand based on the single mode.

Step 2 Specify the planned data file.

The GSM planned sheet: specify the planned

sheet in the GSM mode (sheet and the BTS

planned sheet for site deployment in single

mode).

The eNodeB planned sheet: specify theeNodeB planned sheet (sheet and the eNodeB

planned sheet for site deployment in single

mode).

The MBTS planned sheet: specify MBTS

mapping between GSM and LTE.

Step 3 Import the planned data file and check

consistency.

Import user-specified sheet data.

Check consistency of common board

parameters and reconfigure inconsistent

parameters.

Import planned

data files

eNodeB

planned

data

GBTS

planned

data

MBTS

mapping

Specify the site

deployment

scenario

Specify the

planned data file

Import eNodeB

planned data files

Import GBTS

planned data files

Import MBTS

mapping between

GBTS and eNodeB

Check/Adjust data

consistency of

common devices

Save as MBTS Templates


63/83


Save as MBTS Templates

MBTS templates are of two types:

Default template

cannot be deleted or

modified.

User-defined template

can be added or deleted.


64/83


Manage MBTS Templates

In theMain Viewnavigation tree in the left pane of the planned data area, select

an MBTS NE, and choose Advanced> Template Managementfrom the menu

bar. A dialog box for managing templates is displayed.

Default MBTS template

User-defined MBTS

template

Define the Summary Data File Open


65/83


Define the Summary Data File Open

Summary Data Files

In the main CME window, chooseAdvanced > Customize Summary

Data Filefrom the menu bar. Select data sheets to be edited from the

displayed summary data files and click OK.

Page66

Define the Summary Data File

Edit


66/83


Summary Data Files Define the BTS planned configuration data in the summary data file. The defined

data in the summary is different from the template and needs configured

manually.

Page67

Site Deployment with the Summary


67/83


Site Deployment with the Summary

Template Specify the Scenario

Page68

Site Deployment With the Summary


68/83



Template Import a Planned Data File

Page69



69/83



Template Import a Planned Data File

Page70



70/83



Template Result Report

Page71


71/83


Contents


3.1 Configure the MBTS Template Data (GUI)


3.3 Expand to Dual Modes from Single Mode

Expand BTS to GL Base Station Choose


72/83



the Method of Site Deployment

Page73

Expand BTS to GL Base Station Specify


73/83



the Planned Data File

Page74



74/83


Expand BTS to GL Base StationChoose

the Method of Site Deployment

Page75



75/83


Expand BTS to GL Base StationSpecify

the Planned Data File

Page76


76/83


Contents

1. CME Overview



4. MBTS Data Check


Check MBTS Data Consistency


77/83


Check MBTS Data Consistency

Page78

C


78/83


Contents

1. CME Overview



4. MBTS Data Check


E t BTS MML S i t


79/83


Export BTS MML Scripts

E t N d B XML C fi ti S i t


80/83


Export eNodeB XML Configuration Scripts

Q ti


81/83


Questions

Please describe MBTS data configuration process.

How do you create a Plan in the CME?

Please describe eNodeB data configuration process.

Please describe BTS data configuration process.

How do you bind BTS and eNodeB?

How do you check MBTS data consistency?

How do you export the eNodeB XML configuration script?

S


82/83


Summary

MBTS data configuration

General configuration principles

Configuration scenario

Add eNodeB data

Add BTS data

Bind BTS and eNodeB

Export the BTS MML script and the eNodeB XML configuration script


83/83

Thank youwww.huawei.com

SPD_SRAN7.0_CME-Based Data Configuration Methods and Key Points_20120420-A-1.2

Documents

Transcript of SPD_SRAN7.0_CME-Based Data Configuration Methods and Key Points_20120420-A-1.2