2GU_OC01_E1_0 ZXSDR Configuration for GU Co-Site(V4.00.30) 162

ZXSDR BTS Configuration for GU Co-site

Course Objectives:

Understand basic concepts of GU co-site

Master the networking mode of GU co-site

Understand the configuration flow of GU co-site

Grasp the operation of LMT, OMCB, OMCR

Grasp the meanings of each key parameter for SDR

Contents

1 Overview.....................................................................................................................................................1

1.1 SDR Architecture..............................................................................................................................1

1.2 IP Abis/Iub Interface..........................................................................................................................1

1.3 OMCB Definition..............................................................................................................................1

1.4 Networking of GU Co-site................................................................................................................2

1.5 Configuration Flow...........................................................................................................................3

2 Data Planning.............................................................................................................................................5

2.1 Racks and Boards Planning...............................................................................................................5

2.2 Transmission Resource Planning.......................................................................................................5

2.3 Radio Resource Planning..................................................................................................................8

3 LMT Configuration..................................................................................................................................11

3.1 Overview.........................................................................................................................................11

3.2 LMT Login to SDR.........................................................................................................................12

3.2.1 LMT Use Prerequisite..........................................................................................................12

3.2.2 Login Mode..........................................................................................................................12

3.2.3 Login Steps...........................................................................................................................12

3.3 Create SDR Physical Data...............................................................................................................15

3.3.1 Create Basic Attribute...........................................................................................................15

3.3.2 Create Rack..........................................................................................................................17

3.3.3 Create Topology Structure....................................................................................................20

3.3.4 Create Environment Monitoring...........................................................................................22

3.3.5 Create Dry Contact...............................................................................................................24

i

3.3.6 Create Clock Reference Source............................................................................................26

3.4 Configuring Transmission Resource...............................................................................................26

3.4.1 Transmission Resource Configuration Flow.........................................................................26

3.4.2 Create E1/T1 Line (IPoE1)...................................................................................................27

3.4.3 Create HDLC Parameter (IPoE1).........................................................................................28

3.4.4 Create PPP Parameter (IPoE1).............................................................................................31

3.4.5 Create FE Parameter (IPoFE)...............................................................................................35

3.4.6 Create Global Port................................................................................................................36

3.4.7 Create IP Parameter..............................................................................................................38

3.4.8 Create SCTP Association......................................................................................................42

3.4.9 Create SCTP Stream (Only for WCDMA)...........................................................................45

3.4.10 Create OMC-B Link...........................................................................................................46

3.5 Configuring Radio Resource...........................................................................................................48

3.5.1 Create RRU Common Parameter.........................................................................................48

3.5.2 Create RF Connection..........................................................................................................49

3.5.3 Create GSM Radio Resource................................................................................................51

3.5.4 Create WCDMA Radio Resource.........................................................................................54

4 OMCB Configuration..............................................................................................................................61

4.1 Overview.........................................................................................................................................61

4.2 Add a Route.....................................................................................................................................62

4.3 Modify Server Configuration File...................................................................................................62

4.3.1 Modify deploy-030womcb.properties as..............................................................................62

4.3.2 Modify FTP Configuration File as the OMC User...............................................................63

4.3.3 Modify the deploy-default.properties file as the OMC user.................................................63

4.4 Configure Basic Properties..............................................................................................................63

4.4.1 Create SDR Management NE...............................................................................................63

ii

4.4.2 Apply Mutex Right...............................................................................................................65

4.5 Configuring SDR Physical Data......................................................................................................66

4.5.1 Create Base Station Equipment Resource Management.......................................................66

4.5.2 Create Rack..........................................................................................................................67

4.5.3 Create Rack Topology..........................................................................................................71

4.5.4 Create Antenna.....................................................................................................................74

4.5.5 Create Clock Source Priority................................................................................................75

4.5.6 Create Dry Contact Alarm....................................................................................................75

4.6 Configuring Transmission Resource...............................................................................................77

4.6.1 Transmission Resource Configuration Flow.........................................................................77

4.6.2 Create E1/T1 Line (IPoE1)...................................................................................................77

4.6.3 Create High-Level Data Link Control (IPoE1).....................................................................78

4.6.4 Create PPP (IPoE1)..............................................................................................................81

4.6.5 Create Ethernet (IPoFE).......................................................................................................85

4.6.6 Create Global Port................................................................................................................85

4.6.7 Create IP Parameter..............................................................................................................87

4.6.8 Create SCTP Association......................................................................................................92

4.6.9 Create SCTP Stream (Only for WCDMA)...........................................................................94

4.6.10 Create OMC-B Link...........................................................................................................96

4.7 Configuring Radio Resource...........................................................................................................97

4.7.1 Create Base Station Radio Resource Management...............................................................97

4.7.2 Create RRU Common Parameter.........................................................................................98

4.7.3 Create RF Connection..........................................................................................................99

4.7.4 Create GSM Radio Resource..............................................................................................100

4.7.5 Create WCDMA Radio Resource.......................................................................................103

4.8 Data Synchronization....................................................................................................................107

iii

4.9 Upload Data to OMCB..................................................................................................................108

5 BSC Configuration.................................................................................................................................111

5.1 Overview.......................................................................................................................................111

5.2 IP over E1 Interface Configuration................................................................................................111

5.2.1 Create Abis Interface Board................................................................................................111

5.2.2 Create IP Abis Interface......................................................................................................113

5.2.3 Create SDR Real Interface..................................................................................................115

5.2.4 Create IP over E1 Configuration.........................................................................................117

5.2.5 Create PPP Configuration...................................................................................................118

5.3 Create IP Property.........................................................................................................................119

5.4 Create SDR Site and Radio Resource............................................................................................120

6 RNC Configuration................................................................................................................................125

6.1 Overview.......................................................................................................................................125

6.2 IP over E1 Interface Configuration................................................................................................125

6.2.1 Create Iub Interface Board.................................................................................................125

6.2.2 Configure Semi-Permanent Connection For SDTB2.........................................................127

Configure the Connection Between SDTB2 and EIPI.................................................................129

6.2.3 EIPI Configuration.............................................................................................................132

6.3 Configure IP over FE Interface...........................................................................................139

6.3.1 Create Service Resource Pool..................................................................................139

6.4 Create RPU Board IP Address.......................................................................................................141

6.5 Create Node B Office....................................................................................................................142

6.6 Create Path Group.........................................................................................................................144

6.7 Create SCTP Association...............................................................................................................145

6.8 Create Node B Office Properties...................................................................................................147

6.9 Create Global Supplemented Resource.........................................................................................149

iv

6.10 Node B Configuration Information.............................................................................................150

6.11 Create UTRAN CELL.................................................................................................................151

v

1 Overview

1.1 SDR Architecture

Separating baseband from RF helps to make full use of both the baseband and the RF

part The baseband can achieve the maximum integration, while the RF part focuses on

realizing maximum power and efficiency, and thus providing more flexible networking

modes. After the separation, the baseband part is called the base band unit (BBU),

while the RF part is called the radio unit (RU). BBU and RU can be installed into the

same cabinet to form a macro base station, such as BS8800 and BS8900. They can also

be installed in the remote mode to form a remote radio unit (RRU).

BBU is responsible for processing and controlling digital baseband signals, while RU

is responsible for converting digital baseband signals into analog signals between BBU

and antenna. BBU is connected with RU via the BBU-RU interface using the optical

fiber.

One BBU enables multiple RUs of different systems in the same frequency band or

different frequency bands; RRU can support both GSM and UMTS systems

simultaneously in such common frequency bands as 850M, 900M, 1800M, and 1900M.

It is based on two points mentioned above that SDR can support the dual-mode multi-

frequency configuration.

1.2 IP Abis/Iub Interface

Different from traditional base stations, SDR base stations adopt the all-IP architecture.

Their Abis/Iub interfaces use the IP protocol and physical bearing medium is FE/GE or

E1/T1 (IP over E1/T1) instead of traditional TDM over E1/T1. IP over E1/T1 can take

advantage of the existing transmission equipment to save investment. FE/GE can

obtain more bandwidth, which complies with the evolution trend of the IP-based

telecommunications system.

1.3 OMCB Definition

Operation and Maintenance Center for Node B (OMCB) is the operation and

1

maintenance unit that manages Node B in 3GPP. As the dual-mode product that

supports both GSM and UMTS, SDR also needs the management via OMCB.

Logically OMCB is independent from OMCR of GSM and OMM of UMTS.

Physically you need to integrate OMCB and OMCR/OMM into the same network

management system. The figure below shows the networking example of dual-mode

SDR where OMCB is integrated with OMCR. Here OMCB manages SDR via the

channel provided by BSC, which is indicated by the black line in the figure below.

However, BSC is not related to the communication between SDR and OMCB.

Therefore, logically OMCB is directly connected with SDR, which is indicated by the

red dotted line in Figure 1.3-1.

Figure 1.3-1 Logical Position of OMCB

1.4 Networking of GU Co-site

Figure 1.4-2 shows the SDR dual-mode networking mode. To save transmission cost,

you can create a link from STM-1 to RNC, which transmits part of the time slot to the

iBSC in the transparent mode.

2

Figure 1.4-2 GU Co-site Networking

1.5 Configuration Flow

The configuration flow of SDR is shown in Figure 1.5-3.

Data planning is the kernel part process of the entire SDR data configuration. All the

configuration data introduced in this manual are based on data planning.

Hardware Inspection checks the SDR rack, board, physical connection, antenna, and

external alarms. It is performed on the construction site and is not introduced in this

manual.

LMT is a quick configuration tool for a single SDR base station. A maintenance

engineer can connect the SDR and perform data configuration by LMT.

OMCB is the network management configuration tool for SDR base stations. After

SDR is connected to OMCB, all the LMT functions can be performed by OMCB.

Note：

If the SDR data is inconsistent with the OMCB data, the operator may perform data

synchronization on OMCB to download the data to SDR. The operator may also upload

the data to OMCB.

3


The BSC/RNC side uses the interfacing data with SDR.

Figure 1.5-3 SDR Configuration Flow

4

2 Data Planning

Note：

All the configuration data are based on planned data.

2.1 Racks and Boards Planning

1． Rack 1: one BBU (B8200). Figure 2.1-4 shows the board layout.

Figure 2.1-4 B8200 Board Layout

2． Rack 2: one RRU (R8860), with the working frequency band of 1800MHz and

the radio system of GSM.

3． Rack 3: one RRU (R8840), with the working frequency band of 2,100 MHz and

the radio system of WCDMA.

BBUs and RRUs use star connection.

2.2 Transmission Resource Planning

Figure 2.2-5 shows the planning of transmission resources. The SDR base station

connects to the RNC via IP over E1 and IP over FE respectively. CS services are

transmitted via E1 preferentially, while PS services are transmitted via FE

preferentially. The interface board on the RNC side uses SDTB2, which transmits part

of the time slot to iBSC in the transparent mode.

5

Table 2.2-1 shows the specific data planning.

Figure 2.2-5 SDR Transmission Networking

Table 2.2-1 Planning of SDR Transmission Resources and IP addresses

Name Meaning Address

GSM IP GSM IP address of SDR 172.18.6.18/24

WCDMA IP (IPoE1)WCDMA IP address of SDR (IP

over E1)110.10.6.18/24

WCDMA IP (IPoFE)WCDMA IP address of SDR (IP

over FE)60.30.6.18/24

OMCB Link IP OMCB Link IP address of SDR 112.12.6.18/24

EUIP_2GSDRIP address of iBSC for SDR

Gateway (IPoverE1)172.18.6.254/24

6

IP A-BIS

Name Meaning Address

EUIP_3GSDRIP address of RNC for SDR

Gateway (IPoverE1)110.10.6.254/24

EUIP_OMCB_CHIP address of the OMCB channel

for SDR O&M Gateway112.12.6.254/24

GIPI_3GSDRIP address of RNC for SDR

Gateway (IPoverFE)60.30.6.254/24

GIPI_OMCBIP address of RNC for OMCB

Gateway139.29.12.254/24

OMCB_IPOMCB IP address configured for

RNC139.29.12.1/24

IP Abis IP Abis virtual address of iBSC 20.20.0.1

IP IubIP Iub virtual address 1 of RNC 30.20.0.1

IP Iub virtual address 2 of RNC 30.30.0.1

OMCB_CH_IP OMCB Channel IP 113.40.0.1

Table 2.2-2 describes timeslot distribution in IP over E1.

Table 2.2-2 Time Slot Allocation

E1 Link ID Time Slot HDLC IDHDLC ID in

BSC/RNC Side

Connection

ObjectRemarks

Link ID0 Slot 1-31 HDLC ID0 HDLC ID1 iBSCTransparent

transmission via RNC

Link ID1 Slot 1-31 HDLC ID1 HDLC ID2 RNC Straight-through



Link ID3 Slot 1-2 HDLC ID4 HDLC ID5 RNC O&M Link of OMCB

Table 2.2-3 describes the interconnection parameters of SCTP association.

Table 2.2-3 SCTP Association Parameters

Parameter Meaning Planned Value Remarks

GSM No.GSM site number (SCTP port number

of 2GSDR)6

Configure SDR port

number in the case of

SCTP for GSM

Node B ID UMTS site number 6 -

iBSC Port No. SCTP port number of iBSC The home CMP

module number

of SDR is 3.

SCTP port number of

iBSC = 14592 + home

CMP module number of

SDR

7


Parameter Meaning Planned Value Remarks

RNC Port No. SCTP port number of RNC 777

The configuration of

RNC is consistent with

that of SDR

3GSDR Port No. SCTP port number of 2GSDR 777

The configuration of

RNC is consistent with

that of SDR

2.3 Radio Resource Planning

Table 2.3-4 describes radio resource planning of GSM.

Table 2.3-4 GSM Radio Resource

RF Unit R8860

Cell S4

Carrier Wave Power 20W for each Carrier Wave

Frequency point 520, 523, 527, 532

BCCH Frequency point 520

MCC 460

MNC 2

LAC 30

CI 6

NCC 0

BCC 0

Table 2.3-5 describes radio resource planning of WCDMA.

Table 2.3-5 WCDMA Radio Resource

RF Unit R8840

Carriers 3C

Carrier Wave Power 20W for each Carrier Wave

Frequency point 1920,1925,1930,2110,2115,2120

MCC 460

MNC 2

LAC 1

Local Cell ID 0,1,2

8

Clock, Environment, and Monitored Data Clock, environment, and monitored data

should be configured according to actual application, as described in Table 2.3-6.

Table 2.3-6 Clock, Environment, and Monitored Data

Data Type Configuration

Environment Monitoring Configuration Default

Dry Contact Alarm Configuration Main Power Supply has a fault alarm

Clock Source Priority Configuration GPS: High priority; Line clock: Low priority

9

3 LMT Configuration

3.1 Overview

Local Maintenance Terminal (LMT) is intended for the onsite commissioning

personnel that use this tool to perform quick commissioning and maintenance.

By using the LMT, you can operate, maintain and configure the transmission data,

physical data and partial radio data of ZXSDR. In addition, during commissioning, you

can import the ZDB template and then synchronize the entire commissioning data table

from the OMC to NE. This method greatly saves commissioning time and raises

commissioning efficiency.

The LMT configuration flow is as shown in Figure 3.1-6.

Figure 3.1-6 LMT configuration flow

11

3.2 LMT Login to SDR

3.2.1 LMT Use Prerequisite

1. Before using the LMT, install the jre-6u2-windows-i586-p.exe file on your

computer. The installation file is located under the JRE directory of the LMT

installation package.

2. Install the LMT software. The installation file is LMTSetup.exe in the LMT

installation package. Directly run this file.

3.2.2 Login Mode

LMT login supports two modes, online configuration and offline configuration.

· Online configuration

The online configuration is a common mode. The online configuration indicates

direct configuration for the ZDB table of the SDR. The data configured by the

mode is instantly validated. After synchronizing the entire table, the SDR resets

and restarts.

Debug the DEBUG/OMC debugging network port on the CC board of the SDR

that the computer is directly connected to. Then run the LMT program.

· Offline configuration

The offline configuration is used to modify the configuration in the client. The

configuration results are saved into a specified directory in the XML format. The

offline configuration does not affect running of the SDR because it does not

need the direct connection with the SDR.

After enabling the LMT, use the offline configuration. Specify a local

configuration file for the offline configuration. According to the requirement,

select B8200 or B8700.

3.2.3 Login Steps

[Purpose]

Use the offline configuration mode to log in to the SDR.

[Context]

12

· IP calculation of BBU boards

All boards on the BBU have the fixed internal IP addresses which are related

with the corresponding slot of the board. The relation is as follows: 192.

Environment Number. Slot Number.16.

The environment Number is used to distinguish from different SDRs in the same

network. The default environment No. is 254.

Therefore, the IP address of the active CC board (Slot 1) is 192.254.1.16.

· IP configuration of the debugging device

In order to establish the link between the debugging device and SDR, first

configure the IP address that is in the same network segment with the CC board

for the debugging device.

The debugging device connects to the ETH1 interface on the active CC board of

the SDR through the Ethernet cable. Configure the IP address that is in the same

network segment with the CC board but is not repeated with the IPs of other

boards in the SDR. To conveniently access all the boards in the SDR, the subnet

mask should be set to 255.255.0.0, and the network gateway is set according to

your requirement.

· How to distinguish between the active CC and standby CC

If there is only one CC board in the SDR, the CC board must be active.

If there are two CC boards respectively in Slot 1 and Slot 2, after power-on,

observe the MS indicator. The CC board where the MS indicator is on is active.

Connect the active CC board with the debugging device.

Note:

Before configuration, extract the standby CC board. After the active CC board is

configured and runs normally, insert the standby CC board.

[Steps]

1. Choose Start > Program > ZTE GULMT > LMT Start to open the LMT

Start window. The login window is as shown in Figure 3.2-7.

13


Figure 3.2-7 Login Window

2. Select the Online Configuration option button.

3. Click the Station Manage button to open the Station Manage dialog box. Set

the station name and IP address, as shown in Figure 3.2-8.

14

Figure 3.2-8 Set Station Name and IP Address

4. In the LTM Start window, click the Run Version button. The LMT starts to

communicate with the SDR. After waiting for 0.5s, the LTM enters the station

configuration window.

3.3 Create SDR Physical Data

3.3.1 Create Basic Attribute

[Steps]

1． In the resource tree, choose Base Station > Configure Basic Attribute, as

shown in Figure 3.3-9 .

15


Figure 3.3-9 Select Configure Basic Attribute

2． In the Basic Parameter tab, set the NodeB ID, as shown in Figure 3.3-10.

Figure 3.3-10 Configure Basic Attribute

3． In the Other Relevant Parameters tab, configure the other parameters.

16

Figure 3.3-11 Configure Other Relevant Parameters

[Parameter Description]

1. SNTP Server Address: fill in the NTP Server IP as scheduled. If no NTP Server

IP is valid, fill in the OMCB_IP.

2. Transmission Mode: select IP.

3. E1/T1 Medium: This parameter is invalid with IP over FE. In this example,

select E1, because the IP over E1 transmission is used.

4. Radio Mode: select “WCDMA/GSM” for a dual-mode system. Select

WCDMA” or ”GSM” for a single mode system. In this example, select

WCDMA/GSM.

5. GSM Station No: fill in the GSM No as scheduled. In this example, fill in 6.

3.3.2 Create Rack

[Purpose]

This example adds two new RRU racks. They are:

One RRU(R8860), working frequency 1800MHz, and radio mode GSM；

17


One RRU(R8840), working frequency 2100MHz, and radio mode WCDMA；

[Context]

One base station may have more than one rack. BBU corresponds to one rack (main

rack 1), and is mandatory. RRU corresponds to one or more than one rack (up to 12

remote racks).

[Steps]

1. In the default Main Rack1 view, add a new BBU board by right-clicking on the

slot on the view and selecting the board, as shown in Figure 3.3-12.

Figure 3.3-12 Configuring BBU Board

2. In the resource tree, choose Base Station > Add Rack to add a new rack, as

shown in Figure 3.3-13.

18

Figure 3.3-13 Add New Rack R8860

3. Adding Antenna and Board

Currently two types of antenna are available: ANT(common antenna) or

RET(adjustable mechanical antenna).

One RRU(R8860): working frequency 1800MHz, radio mode GSM, and the

corresponding board is GU188.

One RRU(R8840): working frequency 2100MHz, radio mode WCDMA, and the

corresponding board is U216.

4. The rack view after adding new RRU racks is shown in Figure 3.3-14.

19


Figure 3.3-14 New RRU Rack

3.3.3 Create Topology Structure

[Purpose]

The purpose of configuring the topology structure is to determine the port on the FS

board through which RRU is connected to BBU.

[Precondition]

· Configure RRU common parameter before creating rack topology, as described

in section 3.5.1. The main rack and remote rack have been added. At least one

main rack is added. Multiple remote racks are supported.

· The interface boards for topology connection on the rack have been added.

[Context]

ZXSDR BTS/Node B uses FS board on the main rack for the topology connection. One

FS supports up to six interfaces, and can be connected to RRU.

[Steps]

1. Adding B8200 and R8860 topology structure. In the resource tree, choose

Ground Resource Management > Topology. A dialogue box appears, as


20

Figure 3.3-15 Configure Topology Structure

2. Right-click the blank area in the dialogue box. A shortcut menu appears. Select

Add.

3. Configure the parameters according to the actual system and click OK, as


21


Figure 3.3-16 Configure Topology Parameter


(1) Area 1 is the FS board for B8200.

(2) Area 2 is the DTR board for R8860.

(3) Higher-level Board Port ID is the FS fiber port number. It is consistent with the

physical port of FS and R8860 connection. In this example it is set to 0.

(4) Lower-level Board Port ID is kept as 0.

(5) Topology Type is consistent with the physical connection. In this example it is

Star.

Caution：

Upper level and lower level: the board or rack close to the BBU is of the upper level,

while the board or rack far away from the BBU is of the lower level.

Each FS board in the BBU provides six optical fiber interfaces used to connect RRUs.

From the front side of the FS board, you can see that the interface numbers are 0, 1, 2,

3, 4, and 5 from right to left. The RRU provides two optical fiber interfaces via the

DTR board. One is used to connect the BBU with the interface number of LC0; the

other is used to connect the lower-level RRU with the optical interface number of

LC1.Select star or link for the topology type. RRS cascading can be realized only when

the topology type is link.

5. Follow the similar steps to add the topology structure of B8200 and R8840, as

shown Figure 3.3-17.

Figure 3.3-17 Configure Topology Parameter

3.3.4 Create Environment Monitoring

[Purpose]

This step configures the operating environment of B8200. When the system detects the

22

temperature is beyond the allowed range, it generates the environment alarm report.

The default settings are recommended for most cases.

[Context]

The environment monitoring parameters are automatically configured when a new

board is added. The operator may adjust the threshold values by modifying the

environment monitoring configuration.

[Steps]

1． In the resource tree, choose Ground Resource Management > Environment

Monitoring. A dialogue box appears as shown in Figure 3.3-18.

Figure 3.3-18 Configure Environment Monitor Threshold

2． Right-click on the type of the environment monitor threshold to be modified to

bring up the shortcut menu. Then select Modify, as shown in Figure 3.3-19.

23


Figure 3.3-19 Modify Environment Monitor Parameter

3． Modify the threshold of the environment monitor parameter, and click OK.

3.3.5 Create Dry Contact

[Purpose]

This step describes how to configure ports for detecting dry contact alarm signals and

circuit state.

[Prerequisite]

The board used to introduce dry contact signals has been configured, such as the SA

board of the main rack.

[Context]

The base station can receive dry contact alarm signals of external equipment and

displays them in to the network management system of the base station. Dry contact is

passive electric signal. When the normal circuit state is open, an alarm is generated in

the case of short circuit. When the normal circuit status is short circuit, an alarm is

generated when the circuit status is open.

[Steps]

24

1. In the resource tree, choose Ground Resource Management > Dry Contact, to

bright up a dialogue box shown in Figure 3.3-20.

Figure 3.3-20 Configure Dray Contact

2. Right-click the blank area in the dialogue box. A shortcut menu appears. Select

Add.

3. Select the basic parameters and click OK, as shown in Figure 3.3-21.

Figure 3.3-21 Add Dry Contact

25


3.3.6 Create Clock Reference Source

[Purpose]

This task adds the clock reference source used by SDR.

[Steps]

1． In the resource tree, choose Base Station > Configure Clock Reference

Source.

2． In the Configure Clock Reference Source interface, set the priorities of the

clock reference sources. In this example, select Internal GPS as the top

priority, as shown in Figure 3.3-22.

Figure 3.3-22 Configuring Clock Reference Source

3.4 Configuring Transmission Resource

3.4.1 Transmission Resource Configuration Flow

Figure 3.4-23 illustrates the configuration flow in the IPoE1 and IPoFE transmission

modes.

26

Figure 3.4-23 Transmission Resource Configuration Flow

3.4.2 Create E1/T1 Line (IPoE1)

[Purpose]

Perform this operation to create the E1 link in Table 2.2-2.

[Context]

When E1/T1 cable serves as the transmission medium, a maximum of eight pairs of E1

cables is available to one B8200 (one SA board).

[Steps]

1. In the resource tree, choose Transmission Resource Management > Physical

Media Configuration > E1/T1 Link to open the E1/T1 Link window.

2. Right-click the blank pane and choose Add in the shortcut menu to open the

E1/T1 Link Management dialog box.

3. According to the requirement, respectively set the E1 links from the SDR to

BSC and from the SDR to RNC, as shown in Figure 3.4-24.

27


Figure 3.4-24 Create E1/T1 Line (IPoE1)


(1) E1/T1 Link ID: The serial No. of the E1 cable to be used, which must be

consistent with the actually used physical connection.

Note:

The SA provides eight pairs of E1 cables totally, respectively corresponding to Link

ID0~Link ID7. 0 indicates the first pair of E1 cable, corresponding to the serial No. of

the physical connection as 1 and 2. Link ID is used during creating the HDLC channel.

(2) Link Type: Select the type of the base station controller, such as RNC, BSC,

BSC + RNC and NODEB.

Note:

If the link type is set to BSC + RNC, it indicates that GSM and WCDMA share one E1

link (time slot sharing mode). In this topic, the SDR connects with the RNC through

three E1 links, and connects with the iBSC by RNC transparent transmission through

one E1 link.

3.4.3 Create HDLC Parameter (IPoE1)

[Purpose]

Perform this operation to create the HDLC channel in Table 2.2-2.

[Steps]

1. Create HDLC ID0 to the iBSC. In the resource tree, choose Transmission

Resource Management > IP Bearing Configuration > HDLC Parameter to

open the HDLC Parameter window.


HDLC Parameter Management dialog box.

28

3. Set the HDLC configuration data of HDLC ID0, as shown in Figure 3.4-25.

Figure 3.4-25 Create HDLC ID0 Channel Parameter


(1) HDLC ID: The serial No. of the HDLC channel on the E1 cable, numbering

from 0.

(2) Bearing Type: Select the E1.

(3) Link ID: ID of the E1 link where the HDLC channel is located.

(4) Ts-bit Mapping Relation: E1 slot serial No. that the HDLC channel acquires.

One HDLC channel uses the 1st ~ 31st time slots of the specified E1 by default.

You can select the time slot number that you need. Herein, select all the 31 time

slots.

Note:

Generally, one HDLC channel occupies all the 31 time slots of one E1 link. Or,

according to the onsite requirement, assign one E1 link to multiple HDLC channels.

The character string fffffffe in Ts-bit Mapping Relation indicates the used time slots.

29


4. According to the preceding method, continually create HDLC ID1 and HDLC

ID2 to the RNC.

5. Create HDLC ID3 to the RNC. In the HDLC Parameter Management dialog

box, set the configuration data, as shown in Figure 3.4-26 .


6. Create HDLC ID4 to the OMCB. In the HDLC Parameter Management

dialog box, set the configuration data, as shown in Figure 3.4-27.

30


Note:

According to the data planning, Slot 4 ~ Slot 31 of Link ID3 are connected to the RNC

and Slot 2 ~ Slot 3 of Link ID3 are connected to the OMCB.

7. The HDLC channels are established, as shown in Figure 3.4-28.

Figure 3.4-28 Established HDLC Channels

3.4.4 Create PPP Parameter (IPoE1)

[Purpose]

Perform this operation to create three PPP configurations, as described in Table 3.4-7.

Table 3.4-7 PPP Configuration

31


PPP ID Used HDLC ID Connection Object

PPP ID 0 HDLC ID0 iBSC

PPP ID 1 HDLC ID1~3 RNC

PPP ID 2 HDLC ID4 OMCB

[Steps]

1. In the resource tree, choose Transmission Resource Management > IP

Bearing Configuration > PPP Parameter to open the PPP Parameter

window.


PPP Parameter Management dialog box.

3. Create the PPP configuration to the iBSC. In the PPP Parameter Management


Figure 3.4-29 Create PPP Configuration to iBSC


(1) PPP Encapsulation: Consistent with the setting at the BSC side.

Note:

32

When the IP Abis/lub interface uses one HDLC channel, select PPP in Bearer

Protocol. When the IP Abis/lub interface uses multiple HDLC channels, select ML-

PPP in Bearer Protocol.

Herein, the SDR supports the auto-link function. Therefore, even though the Abis

interface only uses one HDLC channel, ML-PPP is still selected in Bearer Protocol.

(2) PPP ID: ID of PPP, which is used in Port ID at Link Layer in the Global Port

Parameter dialog box.

(3) MP’s Header Format: Consistent with the setting at the BSC side or RNC side.

The default value is Long Sequence.

(4) Base Station IP: Type the GSM IP address of the SDR.

(5) HDLC Link ID: Type the HDLC ID to be used in the PPP configuration. In this

topic, the GSM uses HDLC Link ID0.

4. Create the PPP ID1 configuration to the RNC. Right-click the blank pane in the

PPP Parameter window and choose Add in the shortcut menu to open the PPP

Parameter Management dialog box.

5. In the PPP Parameter Management dialog box, set the configuration data, as


33


Figure 3.4-30 Create PPP Configuration to RNC


(1) Base Station IP: Type the WCDMA IP (IPoE1) address of the SDR.

(2) HDLC Link ID: Type the HDLC Link ID to be used in the PPP configuration. In

this topic, the WCDMA uses HDLC ID1 ~ HDLC ID3.

1. Create the PPP ID2 configuration to the OMCB. Right-click the blank pane in

the PPP Parameter window and choose Add in the shortcut menu to open the

PPP Parameter Management dialog box.

2. In the PPP Parameter Management dialog box, set the configuration data, as


Figure 3.4-31 Create PPP Configuration to OMCB


(1) Base Station IP: The OMCB Link IP address of the SDR.

(2) HDLC Link ID: Type the HDLC Link ID to be used in the PPP configuration. In

this topic, the OMCB link uses HDLC ID4.

34

3.4.5 Create FE Parameter (IPoFE)

[Purpose]

In this topic, the Ethernet connection is only available between the RNC and SDR.

Perform this operation to create the basic properties of Ethernet.

[Steps]

1. In the resource tree, choose Transmission Resource Management > Physical

Media Configuration > Ethernet Parameter to open the Ethernet Parameter

window.


Ethernet Parameter Management dialog box.

3. In the Ethernet Parameter Management dialog box, set the FE link, as shown

in Figure 3.4-32.

Figure 3.4-32 Create Ethernet


(1) Board Name: Select the CC board where the lub and Abis IP interfaces are

located.

35


(2) Ethernet Port ID: Select a value from the pull-down list box. Currently, only 0

can be selected, indicating Ethernet access.

(3) Working Mode: Select the Ethernet working mode of the site. Herein, select

100Mbps full-duplex in Working Mode.

(4) Connection Object: For the directly-connected site, select IPbone; for the

cascading site, select BTS. Herein, select IPbone in Link Object.

(5) Configured Bandwidth(Kbps): Total bandwidth of the SDR. The total bandwidth

used by the IP addresses that the same SDR establishes on the FE transmission

does not exceed this value.

3.4.6 Create Global Port

[Purpose]

Perform this operation to create the global port in the FE and E1 transmission modes.

[Context]

ZTE defines the global port as follows: For the transmission mode such as FE or E1,

the data formats are unified after passing the global port, and the subsequent

configuration has no difference between IPoE1 and IPoFE.

[Steps]

1. Create the global port in the FE transmission mode. In the resource tree, choose

Transmission Resource Management > IP Bearing Configuration > Global

Port Parameter to open the Global Port Parameter window.


Global Port Parameter dialog box.

3. In the Global Port Parameter dialog box, set the configuration data, as shown

in Figure 3.4-33.

36

Figure 3.4-33 Create Global Port for IPoFE


(1) Working Mode: Select IP over Ethernet for the FE transmission and select IP

over PPP for the E1 transmission.

(2) Port ID at Link Layer: Select 0 for the FE transmission.

(3) VLAN ID: According to the planning value, type 203; when VLAN is unused,

type 65535.

Note:

After using VLAN, the SDR in the FE transmission mode is disconnected from the

O&M link.

1. Create the global port in the E1 transmission mode. Right-click the blank pane

in the Global Port Parameter window and choose Add in the shortcut menu to

open the Global Port Parameter dialog box. Set the configuration data, as


37


Figure 3.4-34 Create Global Port for PPP ID0


(1) Working Mode: Select IP over Ethernet for the FE transmission and select IP

over PPP for the E1 transmission.

(2) Port ID at Link Layer: Select PPP ID0 for the E1 transmission.

5. According to Step4, continue creating the global ports of PPP ID1 ~ PPP ID2.

3.4.7 Create IP Parameter

[Purpose]

Perform this operation to create four IPs.

· IP ID0: WCDMA IP (IPoFE) uses it.

· IP ID1: GSM IP uses it.

· IP ID2: WCDMA IP (IPoE1) uses it.

· IP ID3: OMCB Link IP uses it.

[Steps]

38


Bearing Configuration > IP Parameter to open the IP Parameter window.

2. Right-click the blank pane and choose Add in the shortcut menu to open the IP

Parameter Management dialog box.

3. Create the IP parameters for WCDMA (IPoFE). In the IP Parameter

Management dialog box, set the configuration data, as shown in Figure 3.4-35.

Figure 3.4-35 Create IP Parameter for WCDMA (IPoFE)


(1) IP ID: The ID of the IP parameter to be created.

(2) Global Port ID: The global port ID while using the FE transmission.

(3) IP Address: Type the WCDMA IP (IPoFE).

(4) Gateway Address: Type the IP address of GIPI_3GSDR.

(5) Bandwidth(Kbps): This value does not exceed the total bandwidth that is

configured in Ethernet Configuration.

(6) Radio Mode: Select WCDMA.

39


3. Create the IP parameter for the GSM. In the IP Parameter Management dialog

box, set the configuration data, as shown in Figure 3.4-36.

Figure 3.4-36 Create IP Parameter for GSM



(2) Global Port ID: The global port2 ID while using the E1 transmission.

(3) IP Address: After finishing the auto link between the NE and OMC, the system

automatically types the GSM IP.

(4) Gateway Address: After finishing the auto link between the NE and OMC, the

system automatically types the IP address of EUIP_2GSDR.

(5) Radio Mode: Select GSM.

5. Create the IP parameter for the WCDMA (IPoE1). In the IP Parameter

Management dialog box, set the configuration data, as shown in Figure 3.4-37.

40

Figure 3.4-37 Create IP Parameter for WCDMA (IPoE1)





automatically types the WCDMA IP (IPoE1).




5. Create the IP parameter for the OMCB link. In the IP Parameter Management


41


Figure 3.4-38 Create IP Parameter for OMCB





automatically types the IP of the OMCB link.


system automatically types the IP of EUIP_OMCB_CH.

(5) Radio Mode: Select WCDMA (The OMCB is installed at the RNC side).

(6) Class of Service: If the IP address is used by OMCB channel only, the value of

COS should be 0. If the value of COS is not 0, service may be set up on this IP.

3.4.8 Create SCTP Association

[Purpose]

Perform this operation to respectively create the SCTP association for the GSM and

WCDMA. The OMCB link does need the SCTP association.

42

[Steps]

1. Create the SCP association for the GSM. In the resource tree, choose

Transmission Resource Management > IP Bearing Configuration > SCTP

Parameter to open the SCTP Parameter window.


SCTP Parameter Management dialog box.

3. In the SCTP Parameter Management dialog box, set the GSM SCTP

parameters, as shown in Figure 3.4-39.

Figure 3.4-39 Create SCTP Association for GSM



(2) Local IP Address: Select the IP address of GSM that is created in IP Parameter

Configuration in No.0 Local IP Address, and select 255 (Invalid) for other

local IP addresses.

(3) Local Port Number: This option appears dimmed and typing is invalid. Use the

GSM No..

43


(4) Remote Port ID: Remote Port Number = 14592 + CMP ID of the SDR.

According to the planning data, the CMP ID of the SDR is 3 and thus type

14595 here.

(5) Remote IP Address: Type the address of the IP Abis interface. For unused IPs,

keep the default values.

3. Create the SCP association for the WCDMA. In the SCTP Parameter

Management dialog box, according to the planning data, set the configuration


Figure 3.4-40 Create SCTP Association for WCDMA

Note:

In the pull-down list box of Local IP Address 2, two all-0 IP addresses are available.

Select IP ID2 in the pull-down list box.



44

(2) Local IP Address: Select the WCDMA IP (IPoE1) and WCDMA IP (IPoFE) that

are created in IP Parameter Configuration respectively in No.0 Local IP

Address and No.1 Local IP Address, and select 255 (Invalid) for other IP

addresses.

(3) Local Port ID: Local port number to be used when the specified SDR establishes

the SCTP association with the RNC.

(4) Remote Port ID: Port number to be used when the RNC establishes the SCTP

association with the SDR. In the WCDMA, the SCTP port No. that the SDR sets

must be consistent with that configured in the RNC.

(5) Remote IP Address: Type the address of the IP lub interface. For unused IPs,


(6) Number of in-and-out Streams: This parameter that the SDR sets must be the

same as the configuration in the RNC. Or else, the signaling is broken.

3.4.9 Create SCTP Stream (Only for WCDMA)

[Purpose]

Perform this operation to create service types for all streams in the SCTP association.

This configuration is available only for WCDMA. The service types include NCP and

CCP as follows.

· NCP: Node B control port, which manages signaling interaction in the common

process.

· CCP: Communication control port, which manages signaling interaction in the

dedicated process.

[Steps]


Bearing Configuration > SCTP Stream Parameter to open the SCTP Stream

Parameter window.


SCTP Stream Parameter Management dialog box.

3. In the SCTP Stream Parameter Management dialog box, according to the

planning data, set the SCTP stream parameters, as shown in Figure 3.4-41.

45


Figure 3.4-41 Create SCTP Stream Parameter


(1) Association ID: Association ID where the SCTP stream is located. This value is

globally unique in the SDR.

(2) Stream ID: ID of the SCTP stream. The number of Stream IDs must be

consistent with the Number of in-and-out Streams parameter configured in

SCTP. To make sure the dedicated signaling communicated, Stream ID of the

CCP must be consistent with the RNC.

(3) User Type: Includes two types such as NCP and CCP. In WCDMA, both the

NCP and CCP must be configured. Only one NCP is available, while multiple

CCPs are available.

Note:

It is unnecessary to set the bandwidth parameters for the NCP and CCP links. The

system automatically sets the default values.

3.4.10 Create OMC-B Link

[Purpose]

In this topic, the OMCB is installed at the RNC side. To realize operation and

maintenance of the OMCB, perform this operation to create the OMC-B link from the

SDR to OMCB.

[Steps]

1. In the resource tree, choose Transmission Resource Management > Channel

Maintenance > OMC-B Parameter to open the OMC-B Parameter window.


OMC-B Connection Management dialog box.

46

3. In the OMC-B Connection Management dialog box, according to the planning

data, set the OMCB parameters, as shown in Figure 3.4-42.

Figure 3.4-42 Create OMC-B Link

Note:

In the pull-down list box of Base Station OMC IP ID, three all-0 IP addresses are

available. Select IP ID3 in the pull-down list box, as shown in Figure 3.4-43.

Figure 3.4-43 Select Base Station Inner IPID


(1) Base Station Inner IP ID: Select IP ID3, that is, OMCB Link IP.

47


(2) Operation and Maintenance Gateway IP: According to the planning data, type

the OMCB_CH_IP.

3.5 Configuring Radio Resource

3.5.1 Create RRU Common Parameter

[Purpose]

Perform this operation to create the RRU common parameters, including the RRU

mode and band.

[Steps]

1. Create the R8860 common parameters. In the resource tree, choose Wireless

Resource Management > RRU Common Parameter to open the RRU

Common Parameter dialog box. Set the GSM configuration data, as shown in

Figure 3.5-44.

Figure 3.5-44 Create R8860 GSM Common Parameter


48

(1) Board Name: Select 2#DTR-GU188-1, that is, R8860.


(3) Parent Frequency Band: According to the planning data, herein select 1800 M.

2. Create the R8840 common parameters. In the resource tree, choose Wireless

Resource Management > RRU Common Parameter to open the RRU

Common Parameter dialog box. Set the WCDMA configuration data, as


Figure 3.5-45 Create R8840 Common Parameter


(1) Board Name: Select 3#RTR-U216-1, that is, R8840.


(3) Parent Frequency Band: According to the planning data, herein select 2100 M.

3.5.2 Create RF Connection

[Purpose]

49


Perform this operation to create the RF connection of the remote rack.

[Context]

The RRU used only in the WCDMA service is required to create the RF connection.

[Steps]

1． In the resource tree, choose Wireless Resource Management > RF

Connection to open the RF Connection window.

2． Right-click the blank pane and choose Add　>　Rack3　in the shortcut menu

to open the RF Connection dialog box．

3． In the RF Connection dialog box, according to the working mode of the

antenna, set the related parameters of the RF connection of Rack2 U216, as


Figure 3.5-46 Create U216 Transmit RF Connection

50

Note:

Currently, one RRU only supports the single-transmitting dual-receiving mode or the

single-transmitting single-receiving mode. For example, when ANT-1 is set to the

transmitting and receiving end, ANT-2 only can be set to the receiving end.


(1) RF Connection ID: Starts from 1 and the like.

(2) Rx/Tx: Select the corresponding RF connection as Transmit or Receive.

(3) RX/TX: Select the port of the RF connection.

(4) Antenna No: Select the corresponding antenna of the RF connection.

4． According to Step1~3, set the two receive connections. The result is as shown

in Figure 3.5-47

Figure 3.5-47 Create U216 RF Connection Result

3.5.3 Create GSM Radio Resource

[Purpose]

Perform this operation to create the GSM sector parameters, the GSM RU parameters

and all carrier parameters in the sector.

[Steps]

1. Create the GSM sector parameters. In the resource tree, choose the Wireless

Resource Management > GSM Sector node.

2. Right-click the blank pane and choose Add in the shortcut menu to open the GSM

Sector dialog box. Set the configuration data, as shown in Figure 3.5-48.

51


Figure 3.5-48 Create GSM Sector Parameter Config


(1) Sector ID: According to the planning data, set the serving sector ID of R8860 to

1.

(2) Channel which high-priority BCCH belongs to: Indicates that the 1st carrier of

R8860 serves as the preferred BCCH. If RU which high-priority BCCH

belongs to is set to Invalid, it indicates the BCCH is randomly assigned.

3. Create the GSM RU parameters. In the resource tree, choose the Wireless

Resource Management > GSM RU node.


GSM RU dialog box. Set the configuration data, as shown in Figure 3.5-49.

52

Figure 3.5-49 Create GSM RU Parameter Config


(1) RU Type: Select RU80. RU80 indicates the RSU60 or R8860.

(2) Number of Carriers: According to the planning data, type 4, indicating that four

carriers are configured for the R8860.

(3) Use the Same Power for All Carriers: Select this parameter.

(4) Carrier 1 power(w): The power sum of all carriers does not exceed TOC(80 w)

of the R8860. According to the data planning, the power of each carrier is 20 w.

(5) Sector (1) No: Select 1, indicating that Sector 1 is valid. Select Invalid for other

sectors.

(6) Number of Carriers in Sector (1): Select 4, that is, four carriers of the R8860

serve Sector 1.

5. Create the GSM carrier wave parameter. In the resource tree, choose the

Wireless Resource Management > GSM Carrier node.


GSM Carrier dialog box. Set the configuration data, as shown in Figure 3.5-50.

53


Figure 3.5-50 Create GSM Carrier Wave Parameter Config


(1) Sector ID: Select the ID of the sector that the carrier wave belongs to.

(2) Logic Carrier ID: Type the ID of the carrier wave. The ID of the 1st carrier wave

is set to 1. Because Sector 1 has four carriers, respectively create the

configuration of other three carrier waves.

3.5.4 Create WCDMA Radio Resource

3.5.4.1 Create Baseband Resource Pool

[Context]

To realize baseband resource sharing and flexibly schedule traffic, create the baseband

resource pool.

In WCDMA, one BPC board has 192 uplink CEs and 192 downlink CEs.

Note:

CE indicates the occupied resources when the 12.2 k service is processed.

When the service is establishing, based on parameter calculation or table query, the

54

capacity control module knows the CE resources that the service needs to occupy. Then

the capacity control module delivers the actual physical resources to the uplink and

downlink processing modules.

[Steps]

1. In the resource tree, choose Wireless Resource Management > Baseband

Resource Pool to open the Baseband Resource Pool Management window.


Baseband Resource Pool Management dialog box.

3. According to the planning data, set the number of the baseband resource pools,

as shown in Figure 3.5-51.

Figure 3.5-51 Create Baseband Pool


(1) Baseband Resource Pool ID: Starts from 0 (the value range from 0 to 35).

(2) Description: Description information of the BPC board where the baseband

resource pool is located.

55


(3) HSUPA Scheduling Algorithm: According to the data planning, set the related

parameters. Normally, select the default values.

3.5.4.2 Create WCDMA Sector

[Purpose]

Perform this operation to create the WCDMA sector.

In WCDMA, a sector involves a geographical concept. The sector indicates the

smallest radio coverage area. Currently, in the WCDMA system, one RF board

supports the maximum of three sectors.

[Steps]

1. In the resource tree, choose Wireless Resource Management > WCDMA

Sector to open the WCDMA Sector window.


WCDMA Sector dialog box.

3. According to the planning data, set the sector and the RF connection of the

sector, as shown in Figure 3.5-52.

Figure 3.5-52 Create WCDMA Sector

56

4. Repeat Step 3 to create Sector 1 and Sector 2.


(1) Sector ID: According to the planning data, respectively set Sector 0, Sector 1

and Sector 2.

(2) Type of Transmission: Select No Diversity.

(3) Tx RF Connection1: Select the corresponding RF connection.

(4) Receiving Type: Select the receiving type. Herein, select Diversity.

(5) Rx RF Connection1: Select the corresponding RF connection.

3.5.4.3 Create WCDMA Cell

[Purpose]

Perform this operation to create the WCDMA cell.

In WCDMA, cells are identified by scramblings and frequencies. Different scramblings

and frequencies indicate different corresponding cells.

Multiple cells can be configured in one sector. However, a maximum of three cells can

be configured in one baseband resource pool (corresponding to one BP board).

[Steps]

1. Right-click the WCDMA Sector window, and choose Add Local Cell in the

shortcut menu to open the Local Cell Management dialog box.

2. In the Local Cell Management dialog box, according to the planning data, set

the cell parameters, as shown in Figure 3.5-53.

57


Figure 3.5-53 Create WCDMA Local Cell (1)

3. Repeat Step 2 to respectively create Cell 1 and Cell 2. After the setting of all

cells is finished, the setting results are displayed in Figure 3.5-54.

Figure 3.5-54 Create WCDMA Local Cell (2)


(1) Local Cell ID: According to the planning data, respectively set Cell 0, Cell 1 and

Cell 2, corresponding to Sector 0, Sector 1 and Sector 2.

(2) Baseband Resource Pool ID: No. of the baseband resource pool where the cell is

located.

(3) Sector ID: Set the sector ID where the cell is located. According to the planning

data, Cell ID 0 is corresponding to Sector ID 0, Cell ID 1 corresponding to

Sector ID 1 and Cell ID 2 corresponding to Sector ID 2.

58

(4) Local Cell Type: Select Common Cell or High Speed Railway Cell in Local

Cell Type. Make sure that the cell types in the same sector are identical.

According to the planning data, select Common Cell here.

(5) Carrier ID: For different carrier IDs, the system assigns various scramblings.

(6) Rx Frequency(UL): Receiving frequency.

(7) Tx Frequency(DL): Transmitting frequency.

59

4 OMCB Configuration

4.1 Overview

OMCB serves as the background network management system of ZXSDR base

stations. You can configure transmission data, physical data, and part of radio data via

OMCB, which can implement the functions of LMT in a more flexible way. Using the

automatic link establishment function, OMCB can open sites in a remote way, which

therefore speeds up site opening and reduces cost. Figure 4.1-55 shows the

configuration flow of OMCB.

Figure 4.1-55 OMCB Configuration Flow

61

4.2 Add a Route

Since the IP addresses of the OMCB server and SDR are not in the same network

segment, you need to add a route from the OMCB gateway to SDR.

In this example, the IP address of the OMCB server is 139.29.12.1. The IP address of

the OMCB gateway GIPI_OMCB is 139.29.12.254. OMCB link IP address of SDR is

112.12.6.18.

[Steps]

1． The command for adding a route on OMCB (SBCX) is:

#route add -net 112.12.6.18 gw 139.29.12.254 netmask 255.255.255.0

139.29.12.1

Note：

In the LINUX system, the command for adding a route is:

route add -net destination network address gw next-hop address netmask IP address of

the network mask

2． After the operation, execute the netstat –nr command to view the route.

3． Set a permanent route. After adding the route using the route add command, to

avoid route loss after restarting the SBCX, you can add the line blow into the

/etc/rc.d /rc.local file as the root user:

#route add –net 112.12.6.18 gw 139.29.12.254 netmask 255.255.255.0

139.29.12.1

4.3 Modify Server Configuration File

To ensure the successful link establishment between the OMCB server and the

foreground SDR base station, it is necessary to check and modify some profiles on the

OMCB server.

4.3.1 Modify deploy-030womcb.properties as OMC user

[Steps]

1． Log in to the server as the OMC user.

62

2． Enter the …\ums-svr\deploy directory, and then open the deploy-

030womcb.properties file.

3． Modify the fields in the red box to OMCB_IP.

Figure 4.3-56 Modify the deploy-030womcb.properties File

4.3.2 Modify FTP Configuration File as the OMC User

1． Log in as the gomcr user, and then check whether userdefined-uep-psl-

ftpserver.port in the /home/gomcr/ums-svr/deploy/deploy-

gsmomcr01.properties file is 20021.

2． Log in as the root user, and then check whether listen_port in the

/etc/vsftpd/vsftpd.conf file is 10021.

3． If the value is not the correct one, modify it.

4.3.3 Modify the deploy-default.properties file as the OMC user

1． Log in to the server as the OMC user.

2． Enter the …\ums-svr\deploy directory, and then open the deploy-

default.properties file.

3． Search the userdefined-uep-psl-ftpserver.port field and make sure that the

value of this field is identical with the configuration of the ftpserver port enabled

on the OMCB server. If it is not, modify the value to 20021.

4.4 Configure Basic Properties

4.4.1 Create SDR Management NE

[Purpose]

63


Perform this operation to create an SDR management NE and generate an SDR node

on the configuration resource tree.

[Steps]

1． Open the Configuration Management window, and then right-click the

resource tree, and then choose Create > UTRAN SubNetwork.

2． Input Alias and SubNetwork ID in the pop-up interface, as shown in Figure

4.4-57.

Figure 4.4-57 Create UTRAN SubNetwork

3． Select a created subnet node from the resource tree, and then choose Create >

Base Station from the shortcut menu.

4． Input the configuration data into the popup interface, as shown in Figure 4.4-58.

64

Figure 4.4-58 Create an SDR Base Station


(1) ManagedElement ID: Input Node B ID.

(2) ManagedElement Type: Distributed base station is selected in this example.

Input ZXSDR BS8700.

(3) ManagedElement IP Address: Input the IP address that the SDR uses to

communicate with the OMCB.

4.4.2 Apply Mutex Right

[Introduction]

After an SDR management NE is created, to perform the subsequent operations, you

need to apply Mutex right first.

[Steps]

1． Choose a created SDR node from the resource tree. Right-click the node, and

then choose Apply Mutex Right from the shortcut menu, as shown in Figure

65


4.4-59.

Figure 4.4-59 Apply Mutex Right

2． If a green lock appears besides the SDR node, it indicates the operation

succeeds, as shown in Figure 4.4-60.

Figure 4.4-60 Success

4.5 Configuring SDR Physical Data

4.5.1 Create Base Station Equipment Resource Management

[Purpose]

Perform this operation to create basic parameters of SDR Equipment Resource.

[Steps]

1． In the configuration resource tree, choose Config Set under the created SDR

management NE, and then choose Create > Base Station Equipment Resource

Management from the shortcut menu. Input the configuration data in the popup

dialog box, as shown in Figure 4.5-61.

66

Figure 4.5-61 Base Station Equipment Resource Management

2． Create the Base Station Equipment Resource Management node on the resource

tree.


(1) BBU Type of Base Station: Input Pack (ZXSDR B8200 GU360).

(2) Transmission Medium: This parameter is invalid for IPoverFE. This example

involves IPoverE1 transmission. Therefore, select E1 in this example.

(3) NTP Server IP Address: Input the planned NTP Server IP. If no NTP ServerIP is

available, input OMCB_IP.

(4) Transmission Type: Select Full IP

(5) Radio Mode：This example is about GSM/UMTS, so select WCDMA/GSM.

(6) Auto Link Function: Select Function Opened.

(7) GSM No.: Fill in the GSM site number according to the plan. It is 6 in this

example.

4.5.2 Create Rack

[Purpose]

The B8200 rack in addition to CC and PM boards is automatically created when

creating base station equipment resource management. This procedure describes how

67


to create other boards of B8200.

[Steps]

1． Under Rack Configuration, double-click Main Rack (B8200 rack). The BBU

rack diagram appears.

2． Create B8200 boards according to the planned data, as shown in Figure 4.5-62.

Figure 4.5-62 B8200 Rack

3． Create GSM RRU (R8860). Choose Rack Configuration from the resource

tree, and then choose Create > Rack Configuration from the shortcut menu.

Select ZXSDR R8860, as shown in Figure 4.5-63.

68

Figure 4.5-63 Create R8860

4． Double-click Rack2（R8860), and then right-click the displayed R8860 rack

diagram. Choose Create Board from the shortcut menu.

5． Select the R8860 board from the popup dialog box, and then select DTR-

GU188, as shown in Figure 4.5-64.

Figure 4.5-64 Create R8860 Board

69



(1) DTR-GU188: Dual-mode carrier board 1800Mhz; TOC: 80W.

1． Create WCDMA RRU (R8840). Choose Rack Configuration from the resource

tree, and then choose Create > Rack Configuration from the shortcut menu.

Select ZXSDR R8840, as shown in Figure 4.5-65.

Figure 4.5-65 Create R8840

2． Double-click Rack3（R8840), and then right-click the displayed R8840 rack

diagram. Choose Create Board from the shortcut menu.

3． Select the R8860 board from the popup dialog box, and then select RTR-U216,

as shown in Figure 4.5-66.

70

Figure 4.5-66 Create R8840 Board


(1) RTR-U216: UMTS carrier board 2100Mhz; TOC: 60W.

4.5.3 Create Rack Topology

[Purpose]

The purpose of setting topology is to determine through which port of which FS board

each RRU is connected to BBU.

[Prerequisites]

· Before creating Rack Topology, you need to create RRU common parameter

first. Refer to 4.7.2 Create RRU Common Parameter.

· Main rack and remote rack are created. There is only one main rack, but there

can be multiple remote racks.

· The interface boards used to realize topology connection on each rack are

created.

[Context]

The interface board used for topology connection on the main rack of ZXSDR

BTS/Node B is FS, which has at most six interfaces used to connect RRUs.

71


[Steps]

1． Create the topology between B8200 and R8860. Choose Rack Configuration

from the resource tree, and then choose Create > Create Rack Topology from

the shortcut menu. Input the configuration data, as shown in Figure 4.5-67.

Figure 4.5-67 Create B8200->R8860 Topology


(1) Area 1: FS board of B8200.

(2) Area 2: DTR board of R8860.

(3) Port ID: FS optical port number: It must be consistent with the actual number of

the port through which FS is connected with R8860. Choose 0 in this example.

(4) RRU Connection Mode: It should be consistent with the configuration of

physical connection. In this example, B8200 is directly connected with R8860,

so select Star.

Caution：

Upper level and lower level: the board or rack close to the BBU is of the upper level,

while the board or rack far away from the BBU is of the lower level.

72

Each FS board in the BBU provides six optical fiber interfaces used to connect RRUs.

From the front side of the FS board, you can see that the interface numbers are 0, 1, 2,

3, 4, and 5 from right to left. The RRU provides two optical fiber interfaces via the

DTR board. One is used to connect the BBU with the interface number of LC0; the

other is used to connect the lower-level RRU with the optical interface number of

LC1.Select star or link for the topology type. RRS cascade can be realized only when

the topology type is link.

2． Create the topology between B8200 and R8840. Choose Rack Configuration

from the resource tree, and then choose Create > Create Rack Topology from

the shortcut menu. Input the configuration data, as shown in Figure 4.5-68.

Figure 4.5-68 Create B8200->R8840 Topology


(1) Area 1: FS board of B8200.

(2) Area 2: RTR board of R8840.

(3) Port ID: FS optical interface number, which should be consistent with the actual

physical port number. It is 1 in this example.

(4) RRU Connection Mode: It must be consistent with that of the physical

73


connection. In this example, B8200 is associated with R8840, so select Star.

4.5.4 Create Antenna

[Purpose]

This procedure describes how to create RRU antenna. Each RRU needs two antennae.

[Steps]

1． Create antenna of R8860. Choose Antenna Configuration from the resource

tree, and then choose Create > Antenna Configuration from the shortcut

menu. Input the configuration data into the pop-up dialog box, as shown in

Figure 4.5-69.

Figure 4.5-69 Create R8860 Antenna 1


(1) Rack No: select 2. It indicates that R8860 is selected.

(2) Slot No.: The total of two antennae can be created. Select 1 for the first antenna.

2． Create the second antenna of R8860 according to step 1.

3． Create two antennae of R8840 according to steps 1 and 2.

4.5.5 Create Clock Source Priority

74

[Purpose]

Perform this operation to create clock source priority of SDR.

[Steps]

1． Set the priority of Internal GPS. Choose Clock Source Priority Configuration

from the resource tree, and then choose Create >Clock Source Priority

Configuration from the shortcut menu. Input the configuration data into the

pop-up dialog box, as shown in Figure 4.5-70.

Figure 4.5-70 Create Clock Source Priority


(1) Priority：The lower the value is, the higher the priority is. In this example, the

GSP clock is priority is quite high. Select 1.

2． Set the line clock priority in the same way. The priority value must be larger

than 1.

4.5.6 Create Dry Contact Alarm

[Purpose]

This procedure describes how to configure ports for detecting dry contact alarm signals

and circuit state.

75


[Prerequisite]

The board used to introduce dry contact signals has been configured, such as the SA

board of the main rack.

[Context]

The base station can receive dry contact alarm signals of external equipment and

display them in the network management system of the base station. Dry contact is

passive electric signal. When the normal circuit state is open, an alarm is generated in

case of short circuit. When the normal circuit status is short circuit, an alarm is

generated when the circuit status is open.

[Steps]

1. Select Dry Contact Alarm Configuration from the resource tree, and then

choose Create > Dry Contact Alarm Configuration from the shortcut menu.

Input the configuration data into the pop-up dialog box, as shown in Figure 4.5-

71.

Figure 4.5-71 Create Dry Contact Alarm


(1) Area 1: SA board of B8200.

(2) Dry Contact No.: Dry contact node number of the SA board. There can be up to

eight pairs of dry contacts.

76

(3) Alarm Content No.: Input this parameter according to the actual situation.

4.6 Configuring Transmission Resource

4.6.1 Transmission Resource Configuration Flow

Figure 3.4-23 illustrates the configuration flow in the IPoE1 and IPoFE transmission

modes.

4.6.2 Create E1/T1 Line (IPoE1)

[Purpose]

Perform this operation to create the E1 link in Table 2.2-2.

[Context]

When the E1/T1 cable serves as the transmission medium, a maximum of eight pairs of

E1 cables is available to one B8200 (one SA board).

[Steps]

1. Create the E1 link to the iBSC. In the resource tree, choose the Transmission

(Full IP) > Physical Layer Management node. Right-click Physical Layer

Management and choose Create > E1/T1 Line Configuration in the shortcut

menu to open the E1/T1 Link Relative Configuration dialog box. Set the

configuration data as shown in Figure 4.6-72.

Figure 4.6-72 Create E1/T1 Line to iBSC


(1) E1/T1 Link ID: The serial No. of the E1 cable to be used, which must be

77


consistent with the actually used physical connection.

Note:

The SA provides eight pairs of E1 cables totally, respectively corresponding to Link

ID0~Link ID07. 0 indicates the first pair of E1 cable, corresponding to the serial No. of

the physical connection as 1 and 2. Link ID is used during creating the HDLC channel.

(2) Link Type: The connection object of the E1 cable; in this topic, Link ID0 is

connected to the iBSC.

2. Create the E1 link to the RNC. In the resource tree, choose the Transmission


Management and choose Create > E1/T1 Line Configuration in the shortcut

menu to open the E1/T1 Link Relative Configuration dialog box. Set the


Figure 4.6-73 Create E1/T1 Line to RNC

3. According to the data planning, Link ID1~Link ID3 should be connected to the

RNC. Therefore, referring to Step2, continue creating the connections of Link

ID2 and Link ID3 to the RNC.

4.6.3 Create High-Level Data Link Control (IPoE1)

[Purpose]

Perform this operation to create the HDLC channel in Table 2.2-2.

[Steps]

1. Create HDLC ID0 to the iBSC. In the resource tree, choose the Transmission

78


Management and choose Create > High-Level Data Link Control in the

shortcut menu to open the High-Level Data Link Control dialog box. Set the


Figure 4.6-74 Create High-Level Data Link Control ID0


(1) HDLC ID: The serial No. of the HDLC channel on the E1 cable, numbering

from 0.

(2) Bearer Link Type: Select the E1.

(3) Bearer Link ID: Select E1 Link ID to be used by the HDLC.

(4) TimeslotMap: Select the time slot of E1 Link. 0 is reserved for system

synchronization and is unavailable.

Note:

79


Generally, one HDLC channel occupies all 31 time slots of one E1 link. Or, according

to the onsite requirement, assign one E1 link to multiple HDLC channels.

2. According to the preceding method, continually create HDLC ID1 and HDLC

ID2 to the RNC.

3. Create HDLC ID3 to the RNC. In the resource tree, choose the Transmission


Management and choose Create > High-Level Data Link Control in the

shortcut menu to open the High-Level Data Link Control dialog box. Set the




(1) TimeslotMap: Select Slot 3 ~ Slot 31. Slot 1 ~ Slot 2 are reserved for HDLC

ID4.

4. Create HDLC ID4 to the OMCB, as shown in Figure 4.6-76.

80


4.6.4 Create PPP (IPoE1)

[Purpose]

Perform this operation to create three PPP configurations, as described in Table 4.6-8.

Table 4.6-8 PPP Configuration

PPP ID Used HDLC ID Connection Object

PPP ID 0 HDLC ID0 iBSC

PPP ID 1 HDLC ID1~3 RNC

PPP ID 2 HDLC ID4 OMCB

[Steps]

1. Create PPP ID0 to the iBSC. In the resource tree, choose the Transmission

(Full IP) > Global Port Layer Management node. Right-click Global Port

Layer Management and choose Create > PPP Configuration in the shortcut

menu to open the PPP Configuration dialog box. Set the configuration data as

81



Figure 4.6-77 Create PPP Configuration to iBSC


(1) PPP ID: The ID of PPP, which is used by Port ID in the Global Port

Configuration dialog box.

(2) Link Type: Select HDLC.

(3) Bearer Protocol: Select ML-PPP.

Note:

When the IP Abis/lub interface uses one HDLC channel, select PPP in Bearer

Protocol. When the IP Abis/lub interface uses multiple HDLC channels, select ML-

PPP in Bearer Protocol.

The SDR initially sets ML-PPP as the default value of Bearer Protocol. To support the

auto-link function, herein, the Abis interface only uses one HDLC channel, but ML-

82

PPP is still selected in Bearer Protocol.

(4) Base Station IP: Type the GSM IP address of the SDR.

(5) HDLC ID: Type the HDLC ID to be used in the PPP configuration. In this topic,

the GSM only uses HDLC ID0.

2. Create PPP ID1 to the RNC. In the resource tree, choose the Transmission (Full

IP) > Global Port Layer Management node. Right-click Global Port Layer

Management and choose Create > PPP Configuration in the shortcut menu to

open the PPP Configuration dialog box. Set the configuration data as shown in

Figure 4.6-78.

Figure 4.6-78 Create PPP Configuration to RNC


(1) Base Station IP: Type the WCDMA IP (IPoE1) address of the SDR.


the WCDMA uses HDLC ID1 ~ HDLC ID3.

83


3. Create PPP ID2 to the OMCB. In the resource tree, choose the Transmission

(Full IP) > Global Port Layer Management node. Right-click Global Port

Layer Management and choose Create > PPP Configuration in the shortcut

menu to open the PPP Configuration dialog box. Set the configuration data as


Figure 4.6-79 Create PPP Configuration to OMCB


(1) Base Station IP: The OMCB Link IP address of the SDR.


the OMCB link uses HDLC ID4.

4.6.5 Create Ethernet (IPoFE)

[Purpose]

In this topic, the Ethernet connection is only available between the RNC and SDR.

84

Perform this operation to create the basic properties of Ethernet.

[Steps]

1. In the resource tree, choose the Transmission (Full IP) > Physical Layer

Management node. Right-click Physical Layer Management and choose

Create > Ethernet in the shortcut menu to open the Ethernet dialog box. Set

the configuration data as shown in Figure 4.6-80.

Figure 4.6-80 Create Ethernet


(1) Working Mode: Select the Ethernet working mode of the site. Herein, select

100Mbps full-duplex in Working Mode.

(2) Link Object: For the directly-connected site, select IPbone; for the cascading

site, select BTS. Herein, select IPbone in Link Object.

(3) Bandwidth(Kbps): Total bandwidth of the SDR. The total bandwidth used by the

IP addresses that the same SDR establishes on the FE transmission does not

exceed this value.

4.6.6 Create Global Port

[Purpose]

Perform this operation to create the global port in the FE and E1 transmission modes.

[Context]

ZTE defines the global port as follows: For the transmission mode such as FE or E1,

85


the data formats are unified after passing the global port, and the subsequent

configuration has no difference between IPoE1 and IPoFE.

[Steps]

1. Create the global port in the FE transmission mode. In the resource tree, choose

the Transmission (Full IP) > Global Port Layer Management node. Right-

click Global Port Layer Management and choose Create > Global Port

Configuration in the shortcut menu to open the Global Port Configuration

dialog box. Set the configuration data as shown in Figure 4.6-81.

Figure 4.6-81 Create Global Port for IPoFE


(1) Port Type: Select IP over Ethernet for the FE transmission and select IP over

PPP for the E1 transmission.

(2) Port ID: Select 0 for the FE transmission.

(3) VLAN ID: According to the planning value, type 203; when VLAN is unused,

type 65535.

Note:

After using VLAN, the SDR in the FE transmission mode is disconnected with the

O&M link.

2. Create the global port in the E1 transmission mode. In the resource tree, choose

the Transmission (Full IP) > Global Port Layer Management node. Right-

click Global Port Layer Management and choose Create > Global Port

Configuration in the shortcut menu to open the Global Port Configuration

86

dialog box. Set the configuration data as shown in Figure 4.6-82.

Figure 4.6-82 Create Global Port for PPP ID0


(1) Port Type: Select IP over Ethernet for the FE transmission and select IP over

PPP for the E1 transmission.

(2) Port ID: Select PPP ID for the E1 transmission.

3. According to Step 2, continue creating the global ports of PPP ID1 ~ PPP ID2.

4.6.7 Create IP Parameter

[Purpose]

Perform this operation to create four IPs.

· IP ID0: WCDMA IP (IPoFE) uses it.

· IP ID1: GSM IP uses it.

· IP ID2: WCDMA IP (IPoE1) uses it.

· IP ID3: OMCB Link IP uses it.

[Steps]

1. Create the IP parameter for the WCDMA (IPoFE). In the resource tree, choose

the Transmission (Full IP) > IP/Static Router Layer Management node.

Right-click IP/Static Router Layer Management and choose Create > IP

Parameter Configuration in the shortcut menu to open the IP Parameter

Configuration dialog box. Set the configuration data as shown in Figure 4.6-83.

87


Figure 4.6-83 Create IP Parameter for WCDMA (IPoFE)



(2) Global Port: The global port ID while using the FE transmission.

(3) IP Address: Type the WCDMA IP (IPoFE).

(4) Gateway Address: Type the IP address of GIPI_3GSDR.

(5) Bandwidth(Kbps): This value does not exceed the total bandwidth that is

configured in Ethernet Configuration.


2. Create the IP parameter for the GSM. In the resource tree, choose the

Transmission (Full IP) > IP/Static Router Layer Management node. Right-

click IP/Static Router Layer Management and choose Create > IP



88

Figure 4.6-84 Create IP Parameter for GSM



(2) Global Port: The global port2 ID while using the E1 transmission.


automatically types the GSM IP.




3. Create the IP parameter for the WCDMA (IPoE1). In the resource tree, choose





89


Figure 4.6-85 Create IP Parameter for WCDMA (IPoE1)





automatically types the WCDMA IP (IPoE1).




4. Create the IP parameter for the OMCB link. In the resource tree, choose the





90

Figure 4.6-86 Create IP Parameter for OMCB





automatically types the IP of the OMCB link.


system automatically types the IP of EUIP_OMCB_CH.

(5) Radio Mode: Select WCDMA (The OMCB is installed at the RNC side).

(6) COS Flag: Class of Service. If the IP address is used by the OMCB channel

only, the value of COS should be 0. If the value of COS is not zero, the service

may be set up on this IP.

4.6.8 Create SCTP Association

91


[Purpose]

Perform this operation to respectively create the SCTP association for the GSM and

WCDMA. The OMCB link does not need the SCTP association.

[Steps]

1. Create the SCP association for the GSM. In the resource tree, choose the

Transmission (Full IP) > Transmission Layer Management node. Right-click

Transmission Layer Management and choose Create > SCTP Configuration

in the shortcut menu to open the SCTP Configuration dialog box. Set the


Figure 4.6-87 Create SCTP Association for GSM



(2) Local IP Address: Select the IP address of GSM that is created in IP Parameter

Configuration in No.0 Local IP Address, and select Invalid in other local IP

addresses.

(3) Local Port Number: This option appears dimmed and typing is invalid. Use the

92

GSM No..

(4) Remote Port Number: Remote Port Number = 14592 + CMP ID of the SDR.

According to the planning data, the CMP ID of the SDR is 3 and thus type

14595 here.

(5) Remote IP Address: Type the address of the IP Abis interface. For unused IPs,


2. Create the SCP association for the WCDMA. In the resource tree, choose the

Transmission (Full IP) > Transmission Layer Management node. Right-click

Transmission Layer Management and choose Create > SCTP Configuration

in the shortcut menu to open the SCTP Configuration dialog box. Set the


Figure 4.6-88 Create SCTP Association for WCDMA

Note:

In the pull-down list box of Local IP Address, two all-0 IP addresses are available.

Select IP ID2 in the pull-down list box, as shown in Figure 4.6-89.

93


Figure 4.6-89 Select WCDMA IP (IPoE1)



(2) Local IP Address: Select the WCDMA IP (IPoE1) and WCDMA IP (IPoFE) that

is created in IP Parameter Configuration respectively in No.0 Local IP

Address and No.1 Local IP Address, and select Invalid in other local IP

addresses.

(3) Local Port Number: Local port number to be used when the specified SDR

establishes the SCTP association with the RNC.

(4) Remote Port Number: Port number to be used when the RNC establishes the

SCTP association with the SDR. In the WCDMA, the SCTP port No. that the

SDR sets must be consistent with that configured in the RNC.

(5) Remote IP Address: Type the address of the IP lub interface. For unused IPs,


(6) Number of in-and-out Streams: This parameter that the SDR sets must be same

as the configuration in the RNC. Or else, the signaling is broken.

4.6.9 Create SCTP Stream (Only for WCDMA)

[Purpose]

Perform this operation to create service types for all streams in the SCTP association.

This configuration is available only for WCDMA. The service types include NCP and

CCP as follows.

· NCP: Node B control port, which manages signaling interaction in the common

process.

· CCP: Communication control port, which manages signaling interaction in the

dedicated process.

94

[Steps]

1. In the resource tree, choose the Transmission (Full IP) > Transmission Layer

Management node. Right-click Transmission Layer Management and choose

Create > SCTP Stream Configuration in the shortcut menu to open the SCTP

Steam Configuration dialog box. Set the configuration data as shown in Figure

4.6-90.

Figure 4.6-90 Create NCP SCTP Stream Parameter 1


(1) Association ID: Association ID where the SCTP stream is located. This value is

globally unique in the SDR.

(2) Stream ID: ID of the SCTP stream. The number of Stream IDs must be

consistent with the Number of in-and-out Streams parameter configured in

SCTP. To make sure the dedicated signaling communicated, Stream ID of the

CCP must be consistent with the RNC.

(3) User Type: Includes two types such as NCP and CCP. In WCDMA, both the

NCP and CCP must be configured. Only one NCP is available, while multiple

CCPs are available.

Note:

It is unnecessary to set the bandwidth parameters for the NCP and CCP links. The

system automatically sets the default values.

2． According to Step 1, create the SCTP stream parameters of CCP.

95


4.6.10 Create OMC-B Link

[Purpose]

In this topic, the OMCB is installed at the RNC side. To realize operation and

maintenance of the OMCB, perform this operation to create the OMC-B link from the

SDR to OMCB.

[Steps]

1. In the resource tree, choose the Transmission (Full IP) > Transmission Layer

Management node. Right-click Transmission Layer Management and choose

Create > OMC-B Link in the shortcut menu to open the OMC-B Link dialog

box. Set the configuration data as shown in Figure 4.6-91.

Figure 4.6-91 Create OMC-B Link

Note:

In the pull-down list box of Base Station OMC IP ID, three all-0 IP addresses are

available. Select IP ID3 in the pull-down list box, as shown in Figure 4.6-92.

96

Figure 4.6-92 Select OMC-B Link IP


(1) Base Station OMC IP ID: Select IP ID3, that is, OMCB Link IP.

(2) Base Station OMC Gateway: According to the planning data, type the

OMCB_CH_IP.

4.7 Configuring Radio Resource

4.7.1 Create Base Station Radio Resource Management

[Purpose]

Perform this operation to create the node of Base Station Radio Resource Management.

[Steps]

1. In the resource tree, choose the Config Set node under the SDR. Right-click

Config Set and choose Create > Base Station Radio Resource Management

in the shortcut menu to open the Base Station Radio Resource Management

dialog box. Click OK.

2. The Base Station Radio Resource Management node is displayed in the

resource tree.

4.7.2 Create RRU Common Parameter

[Purpose]

Perform the RRU common parameters, including the RRU mode and band.

[Steps]

97


1. Create the R8860 common parameters. In the resource tree, choose the Base

Station Radio Resource Management node. Right-click Base Station Radio

Resource Management and choose Create > RRU Common Parameter in the

shortcut menu to open the RRU Common Parameter dialog box. Set the GSM




(1) Radio Rack No.: Select 2 (R8800).


(3) Frequency Band: According to the planning data, select the corresponding value.

Herein, select 1800M (Band III).

2. Create the R8840 common parameters. In the resource tree, choose the Base

Station Radio Resource Management node. Right-click Base Station Radio

Resource Management and choose Create > RRU Common Parameter in the

shortcut menu to open the RRU Common Parameter dialog box. Set the

UMTS configuration data as shown in Figure 4.7-94.

98



(1) Radio Rack No.: Select 3 (R8840).


(3) Frequency Band: According to the planning data, select the corresponding value.

Herein, select 2.1G (Band I).

4.7.3 Create RF Connection

[Purpose]

Perform this operation to create the RF connection of the remote rack.

[Context]

The RRU only used in the WCDMA service is required to create the RF connection.

[Steps]

1． In the resource tree, choose the RF Connection Configuration node. Right-

click RF Connection Configuration and choose Create > RF Connection in

the shortcut menu to open the RF Connection dialog box. Set the configuration


99


Figure 4.7-95 RF Connection Configuration

Note:

Currently, one RRU only supports the single-transmitting dual-receiving mode or the

single-transmitting single-receiving mode. For example, when ANT-1 is set to the

transmitting and receiving end, ANT-2 only can be set to the receiving end.


(1) RF Connection ID: Starts from 1 and the like.

(2) Transceiving Flag: Select Transmit or Receive for the corresponding RF

connection.

(3) RF Connection Type: Select RTR U216.

(4) Rack No: Select the rack type.

4.7.4 Create GSM Radio Resource

[Purpose]

Perform this operation to create the GSM sector parameters, the GSM RU parameters

and all carrier parameters in the sector.

[Steps]

1. Create the GSM sector parameters. In the resource tree, choose the Base Station

Radio Resource Management > GSM Radio Resource Management node.

Right-click GSM Radio Resource Management and choose Create > GSM

100

Sector Parameter Config in the shortcut menu to open the GSM Sector

Parameter Config dialog box. Set the configuration data as shown in Figure

4.7-96.

Figure 4.7-96 Create GSM Sector Parameter Config


(1) Sector number: According to the planning data, set the serving sector ID of

R8860 to 1.

(2) Area 1: Indicates that the 1st carrier of R8860 serves as the preferred BCCH.

If BCCH Rack No. is set to Invalidation, it indicates the BCCH is randomly

assigned.

2. Create the GSM RU parameters. In the resource tree, choose the Base Station

Radio Resource Management > GSM Radio Resource Management node.

Right-click GSM Radio Resource Management and choose Create > GSM

RU Parameter Config in the shortcut menu to open the GSM RU Parameter

Config dialog box. Set the configuration data as shown in Figure 4.7-97.

101


Figure 4.7-97 Create GSM RU Parameter Config


(1) RU Type: Select RU80 (RU80 indicates RSU60 or R8860).

(2) All Sector Carrier Wave Count Sum: According to the data planning, select 4,

that is, configure four carriers for the R8860 totally.

(3) Sector number 1: Select 1. For other sectors, select Invalidation respectively in

Sector number 2 and Sector number 3.

(4) Sector 1 Carrier Wave Count: Select 4, that is, four carriers of the R8860 serve

Sector 1.

(5) Carrier wave power(w): The power sum of all carriers does not exceed TOC(80

w) of the R8860. According to the data planning, the power of each carrier is 20

w.

3. Create the GSM carrier wave parameters. In the resource tree, choose the Base

Station Radio Resource Management > GSM Radio Resource Management

102

node. Right-click GSM Radio Resource Management and choose Create >

GSM Carrier Wave Parameter Config in the shortcut menu to open the GSM

Carrier Wave Parameter Config dialog box. Set the configuration data as


Figure 4.7-98 Create GSM Carrier Wave Parameter Config


(1) Sector Number: Select the serving-sector number of the carrier wave.

(2) Logic Carrier Frequency Number: Type the ID of the carrier wave. The ID of the

1st carrier wave is set to 1. Because Sector 1 has four carriers, respectively create

the configuration of other three carrier waves.

4.7.5 Create WCDMA Radio Resource

4.7.5.1 Create Baseband Resource Pool

[Context]

To realize baseband resource sharing and flexibly schedule traffic, you need to create

the baseband resource pool.

In WCDMA, one BPC board has 192 uplink CEs and 192 downlink CEs.

Note:

CE indicates the occupied resources when the 12.2 k service is processed.

103


When the service is establishing, based on parameter calculation or table query, the

capacity control module knows the CE resources that the service needs to occupy. Then

the capacity control module delivers the actual physical resources to the uplink and

downlink processing modules.

[Steps]

1． In the resource tree, choose the Base Station Radio Resource Management >

WCDMA Radio Resource Management node. Right-click WCDMA Radio

Resource Management and choose Create > Baseband Resource Pool in the

shortcut menu to open the Baseband Resource Pool dialog box. Set the

configuration data as shown in Figure 4.7-99

Figure 4.7-99 Create Baseband Resource Pool


(1) Baseband Resource Pool ID: Starts from 0 (the value range from 0 to 35).

(2) Baseband Resource Pool Info: Description information of the BPC board where

the baseband resource pool is located.

2． Choose the Baseband Resource Pool0 node. Right-click Baseband Resource

Pool0 and choose Create > Baseband Resource Group in the shortcut menu to

open the Baseband Resource Group dialog box. Set the related parameters, as


104

Figure 4.7-100 Create Baseband Resource Group

4.7.5.2 Create WCDMA Sector

[Purpose]

Perform this operation to create the WCDMA sector.

In WCDMA, a sector involves a geographical concept. The sector indicates the

smallest radio coverage area. Currently, in the WCDMA system, one RF board

supports the maximum of three sectors

[Steps]

1． In the resource tree, choose WCDMA Radio Resource Management > Sector

Management to open the Sector Management window. Right-click Sector

Management and choose Create > Sector in the shortcut menu to open the

Sector dialog box. Set the related parameters, as shown in Figure 4.7-101

Figure 4.7-101 Create WCDMA Sector

2． Repeat Step 3 to respectively create Sector 1 and Sector 2.


(1) Sector ID: According to the planning data, respectively set Sector 0, Sector 1

and Sector 2

(2) Transmission Type: Select No Diversity

(3) Transmit RF Connection: Select the corresponding RF connection.

(4) Receiving Type: Select the receiving type. Herein, select Diversity.

105


(5) Receive RF Connection: Select the corresponding RF connection.

4.7.5.3 Create WCDMA Local Cell

[Purpose]

Perform this operation to create the WCDMA cell.

In WCDMA, cells are identified by scramblings and frequency. Different scramblings

and frequencies indicate different corresponding cells.

Multiple cells can be configured in one sector. However, a maximum of three cells can

be configured in one baseband resource pool (corresponding to one BP board).

[Steps]

1． In the resource tree, choose WCDMA Radio Resource Management > Sector

Management > Sector 0 to open the Sector 0 window. Right-click Sector 0 and

choose Create > Local Cell in the shortcut menu to open the Local Cell dialog

box. Set the related parameters, as shown in Figure 4.7-102.

Figure 4.7-102 Create WCDMA Local Cell

2． Repeat Step 1 to respectively create Local Cell 1 and Local Cell 2.


(1) Local Cell ID: According to the planning data, respectively set Cell 0, Cell 1 and

Cell 2, corresponding to Sector 0, Sector 1 and Sector 2.

106

(2) Baseband Resource Pool ID: No. of the baseband resource pool where the cell is

located.

(3) Sector ID: Set the sector ID where the cell is located. According to the planning

data, Cell ID 0 is corresponding to Sector ID 0, Cell ID 1 corresponding to

Sector ID 1 and Cell ID 2 corresponding to Sector ID 2.

(4) Local Cell Type: Select Common Cell or High Speed Railway Cell in Local

Cell Type. Make sure that the cell types in the same sector are identical.

According to the planning data, select Common Cell here.

(5) Carrier ID: For different carrier IDs, the system assigns various scramblings.

(6) Rx Frequency(UL): Receiving frequency.

(7) Tx Frequency(DL): Transmitting frequency.

4.8 Data Synchronization

[Purpose]

Perform this operation to synchronize the data configured in the OMCB to the SDR.

[Prerequisite]

After properly configuring the transmission resources and establishing the link between

the OMCB and SDR, you need to perform data synchronization.

[Steps]

1. Right-click the SDR root node and choose Synchronize All Tables in the

shortcut menu, as shown in Figure 4.8-103. The Synchronize All Tables dialog

box is displayed. Click OK.

107


Figure 4.8-103 Synchronize All Tables


(1) Synchronize All Tables: Synchronize all data under the SDR node to the SDR.

(2) Synchronize Modified Tables: Synchronize the modified data under the SDR

node to the SDR.

4.9 Upload Data to OMCB

[Context]

The configuration data has existed in the SDR, for example, the SDR data has been

configured by using the LMT. For this scenario, you need to upload the SDR data to

the OMCB.

[Steps]

1. Right-click the SDR root node and choose Base Station Configuration

Wizard(SDR) in the shortcut menu. The Configuration Wizard dialog box is

displayed as shown in Figure 4.9-104.

108

Figure 4.9-104 Base Station Configuration Wizard(SDR)


(1) Online Upload Data: Read the data from the link-established SDR and configure

it to the OMCB.

(2) Offline Upload Data: Read the existing data file from the disk

109

5 BSC Configuration

5.1 Overview

Note:

The iBSC has finished commissioning and debugging, and all functions are normal.

This chapter only describes the operation of connection between the iBSC and SDR.

Figure 5.1-105 shows the configuration flow in the iBSC side.

Figure 5.1-105 BSC Configuration Flow

5.2 IP over E1 Interface Configuration

5.2.1 Create Abis Interface Board

[Purpose]

Perform this operation to create the Abis interface boards such as SDTB2 and EIPI and

to connect one HDLC channel.

111

[Steps]

1. Create the SDTB2 board. In the Configuration Management window, open the

iBSC rack architecture, and create the SDTB2 board in the BIU unit of the

resource shelf.

2. In the Create Board dialog box, click the PCM Information tab. Add one

PCM to the SDR in the right list, as shown in Figure 5.2-106.

Figure 5.2-106 Create Interface Board (1)


(1) PCM type: Select Type of EUIP.

(2) PCM No.: The value of PCM No. must be consistent with the physical

connection. Herein, select 9 (indicating the 1st PCM).

(3) Frame mode: Corresponding to the SDR site, select Multi frame.

3. Create the EUIP board in the BIU unit of the resource shelf.

4. In the Board Property dialog box, click the HDLC Information tab. Connect

the HDLC channel, as shown in Figure 5.2-107.

112

Figure 5.2-107 Create Interface Board (2)


(1) EUIP 2MHW No.: 2MHW No. of the EUIP board. Herein, select 9 (indicating

the 1st HW).

(2) DT Unit No.: Select the SDTB2 board to be connected. 111 indicates the 1st rack,

1st shelf and 1st slot.

(3) DT PCM No.: PCM No. of the SDTB2 board. Select the PCM that is created in

Step2.

(4) Button 2: Click to connect all the selected slots of the EUIP and SDTB2.

The connection results are displayed in the right Selected TS Information pane.

(5) Button 1: Click the button to successfully connect the HDLC channel.

5.2.2 Create IP Abis Interface

[Purpose]

Perform this operation to create the IP Abis interface.

[Context]

The IP Abis is created in the RPU. All the addresses in the RPU are virtual addresses.

113


[Steps]

1. In the resource tree, choose BSC Function > IP Related Config to open the IP

Related Config window. Click the Interface tab, as shown in Figure 5.2-108.

Figure 5.2-108 IP Related Config Interface

2. Click to open the Create Interface dialog box. Set the IP address of the IP

Abis interface, as shown in Figure 5.2-109.

Figure 5.2-109 Create IP Abis


（1） Board function type: Select RPU.

114

（2） Port No: Select the default value 1. When multiple virtual addresses are

configured in the RPU, the port No. of each address should be different.

（3） The number of IP: Select 1.

（4） IP address: According to the data planning, type the address of IP Abis.

（5） Subnet mask: The subnet mask of the virtual address must be 255.255.255.255.

5.2.3 Create SDR Real Interface

[Purpose]

Perform this operation to create the SDR real interface to the iBSC, that is, the

EUIP_2GSDR interface.

[Steps]

1. In the resource tree, choose BSC Function > IP Related Config to open the IP

Related Config window. Click the Interface tab, as shown in Figure 5.2-110.

Figure 5.2-110 IP Related Config Interface

2. Click to open the Create Interface dialog box. Set the IP address of the

EUIP_2GSDR interface, as shown in Figure 5.2-111.

115


Figure 5.2-111 Create IP Address of EUIP_2GSDR


(1) Board function type: Select EUIP.

(2) Port No: Assign one port No. to the real address of each EUIP and use this port

No. to be associated with the port No. of IPOverE1. When the PPP protocol is

used, the valid port No. ranges from 1 to 190. When the ML-PPP protocol is

used, the valid port No. ranges from 191 to 254.

(3) The number of IP: Configure one IP on EUIP. Herein, select 1.

(4) IP address: SDR gateway address. Under the same iBSC, the links of various

EUIPs cannot be set in the same network segment. The IP address must be in the

same network segment with the SDR. Herein, type the IP address of

EUIP_2GSDR.

(5) Subnet mask: According to the data planning, type 255.255.255.0. In the

existing network, based on the number of actual SDR sites, increase or decrease

the mask.

116

5.2.4 Create IP over E1 Configuration

[Purpose]

Perform this operation to create the HDLC No. and slot to be used for IP over E1.

[Steps]

1. In the IP Related Config window, click the IP Over E1 Configuration tab.

Click to open the Create IP Over E1 Configuration dialog box. Set the

configuration data as shown in Figure 5.2-112 .

Figure 5.2-112 Create IP Over E1 Configuration


(1) Port No.: Indicates the port of one IP over E1 on the EUIP board. When the

bearer protocol is PPP, the port No. is set to the same value in the corresponding

EUIP interface configuration. When the bearer protocol is ML-PPP, the port No.

is irrelevant with the EUIP setting. But multiple ports in one MP-PPP cannot be

repeated and these ports are normally set as 1, 2, 3 and 4.

(2) HDLC No: Select HDLC No. that is configured in EUIP Board Properties.

(3) Start TS/End TS: According to the data planning, the slot of the HDLC to the

iBSC ranges from 1 to 31.

117


5.2.5 Create PPP Configuration

[Purpose]

Perform this operation to create the PPP configuration at the BSC side.

[Steps]

1. In the IP Related Config window, click the PPP Configuration tab. Click

to open the Create PPP Configuration dialog box. Set the configuration data as


Figure 5.2-113 Create PPP Configuration


(1) Peer IP: Type the GSM IP address of the SDR.

(2) Subsystem:module:unit:sunit:port: Locates the port of the IP over E1 on the

EUIP. That is, select the same value that is set in the Create IP Over E1

Configuration dialog box.

(3) MP No. sign: When the bearer protocol is PPP, this parameter is set to Invalid;

When the bearer protocol is ML-PPP, it is set to Valid and is used as Port No. of

the corresponding EUIP.

(4) IP header compression sign: Valid when the PPP is configured with compression

transmission.

(5) Keep time/Keep granularity: For example, when keep time is 3s and keep

granularity is 3, it indicates message transmission three times within 3s. If no

118

response message is received three times, it indicates that the PPP link is broken.

Note:

If it is required to add the 2nd IP over E1 to the PPP configuration, execute the

following steps:

Recreate one PPP configuration.

For the Subsystem:module:unit:sunit:port: field, select one IP over E1 that needs to

add the PPP configuration.

The configuration of other parameters is consistent with the 1st PPP configuration.

5.3 Create IP Property

[Purpose]

Generally, the IP properties that the BSC needs to configure are as follows:

· OMCB IP (The OMCB locates at the RNC side and thus this property is not

configured in this topic.)

· OMCB Channel IP (The OMCB locates at the RNC side and thus this property

is not configured in this topic.)

· IP Abis address

Perform this operation to create the IP properties.

[Steps]

1. In the resource tree, choose Config Set > BSC Function to open the BSC

Function window. Click the Basic Property tab.

2. In the Basic Property tab, type the OMCB IP address as shown in Figure 5.3-

114. The OMCB is located at the RNC side, and therefore skip this step.

Figure 5.3-114 Type OMCB IP

119



(1) OMCB IP: Address of the OMCB server.

3. In the IP Property tab, type the IP Abis address and OMCB channel IP, as

shown in Figure 5.3-115. The OMCB is located at the RNC side, and therefore

skip the setting of OMCB channel IP.

Figure 5.3-115 Type IP Abis and OMCB Channel IP


(1) IPABIS: Address that the iBSC uses to transmit the service to the SDR.

(2) OMCB Channel IP: Address that the OMCB uses to transmit the operation and

maintenance command to the SDR.

5.4 Create SDR Site and Radio Resource

[Purpose]

· Creating the SDR radio resource in the OMCB involves the physical data such

as the cell, RU and carrier wave of the RU to be used.

· Creating the SDR radio resource in the OMCR involves the cell property, TRX

property and channel property.

[Steps]

1. In the resource tree, choose the Config Set > BSC Function > Site

Configuration node. Right-click Site Configuration and choose Create > Site

in the shortcut menu to open the Create Site dialog box. Set the site property, as


120

Figure 5.4-116 Create SDR Site


(1) Site type: Select SDR.

(2) Site ID: Type GSM No.. Herein, set this value to 6.

(3) Module No.: Indicates the CMP No. of the SDR site. According to the data

planning, select 3.

(4) IPOverE1 support: Select Yes to support IP over E1.

(5) Bandwidth limit(Kb): Indicates the bandwidth available to the SDR. According

to there being one E1, type 2048.

2. In the resource tree, choose the generated Site6(SDR6) node. Right-click

Site6(SDR6) and choose Create > Cell in the shortcut menu to open the Create

Cell dialog box. Set the radio planning data, as shown in Figure 5.4-117.

121


Figure 5.4-117 Create Cell


(1) Set the related values according to the radio planning data.

3. In the resource tree, choose the generated Cell-1800M node. Right-click Cell-

1800M and choose Create > TRX in the shortcut menu to open the Create

TRX dialog box. Set the radio planning data, as shown in Figure 5.4-118.

Figure 5.4-118 Create TRX


(1) TRX ID(TrxId): TRX number in a cell.

122

(2) BCCH carrier frequency(BcchMark): Select Yes, indicating the TRX is the

BCCH carrier.

(3) Priority(TrxPriority): Indicates the Trx priority. 1 indicates the highest priority.

For the BCCH carrier, the system automatically types 1 in Priority, indicating

that the service is prior to acquire the BCCH carrier.

(4) Support FHS: Indicates whether the FHS is supported. Herein, select NO.

(5) Frequency: Frequency to be used by the TRX (ARFCN). According to the

planning data, type 520.

4. Click the Channel Info tab to set the TS channel property, as shown in Figure

5.4-119.

Figure 5.4-119 Set TS Channel Property

Note:

The channel setting is related with the radio network optimization. Therefore, the

related details are not described in this manual.

5. Click the IP Parameter tab to set the IP property of TRX, as shown in Figure

5.4-120.

123


Figure 5.4-120 Set TRX IP Parameters


(1) BIPB Unit: BIPB unit No. that processes the TRX.

(2) DSP Sunit: The BIPB has 15 SDPs. Select one DSP to process the TRX.

(3) DspMarkSeq: Each DSP has 28 DspMarkSeqs and each DspMarkSeq processes

one TRX.

(4) Port No.: Port No. of the TRX, unique in the same iBSC.

6. According to Step 3 ~ Step 5, continue creating TRX2 ~ TRX4.

124

6 RNC Configuration

6.1 Overview

Note:

The prerequisite of configuring RNC is that RNC commissioning and debugging is

complete and all the functions are normal.

This chapter only describes how to interconnect RNC and SDR.

6.2 IP over E1 Interface Configuration

6.2.1 Create Iub Interface Board

[Purpose]

This task creates the interface boards, SDTB2 and EIPI, at Iub interface.

Knowledge Point:

SDTB2 and EIPI can be inserted in any slots except Slot 9 and Slot 10 in the GB

resource shelf.

[Steps]

1. Create SDTB2 board.

In the Configuration Management window, open the RNC rack diagram.

Right-click the interface frame and choose Create > Board.

2. In the popup dialog box, select the board type SDTB2(EUIP_PCM), as shown in

Figure 6.2-121.

125

Figure 6.2-121 Creating SDTB2 Board

3. Select the Unit tab. Set the parameters E1/T1 Conflg, Master Optical Port

No., and Slave Optical Port No.. as shown in Figure 6.2-122.

Figure 6.2-122 Setting SDTB2 Board Properties


(1) E1/T1 Conflg: used to set the E1/T1 type supported by SDTB2. According to

the planned data, select E1 supported.

(2) Master Optical Port No.: refers to the number of master optical port.

(3) Slave Optical Port No.: refers to the number of slave optical port.

4. Repeat step 2 to create EIPI interface board. Set the EIPI board properties, as


126

Figure 6.2-123 Setting EIPI Board Properties


(1) Unit type: Select EUIP.

(2) Channel Configuration.: determines whether the channel type is FE or GE.

According to the planned data, set this parameter to 4 FE In.

(3) E1/T1 Conflg: used to set the E1/T1 type supported by EIPI. According to the

planned data, select E1 supported.

6.2.2 Configure Semi-Permanent Connection For SDTB2

[Purpose]

This task creates the connection relation between SDTB2 and IBSC.

After the configuration is successful, the data of the specified interface on SDTB2 is

directly transmitted to iBSC through another transparent interface.

[Steps]

1. Choose Transmission Configuration > Connection relation configuration in

the resource tree.

2. Right-click Connection relation configuration and choose Create>Semi-

permanent Connection from the shortcut menu.

127


3. In the Semi-permanent Connection dialog box, create the transmission channel

from SDTB2 to IBSC side, as shown in Figure 6.2-124.

Figure 6.2-124 Creating Semi-Permanent Transmission Channel for SDTB2


(1) A-end resource circuit Subsystem No.: refers to the number of the shelf where

the SDTB2 board at end A of E1 link is located.

(2) A-end resource circuit Unit No.: refers to the number of the slot where the

SDTB2 board at end A of E1 link is located.

(3) A-end resource circuit subunit No.: refers to the number of the E1 where the

SDTB2 board at end A of E1 link is located.

(4) A-end resource circuit No.: refers to the number of the port where IP over E1

the SDTB2 board at end A of E1 link is located.

(5) B-end resource circuit Subsystem No.: refers to the number of the shelf where

the SDTB2 board at end B of E1 link is located

(6) B-end resource circuit Unit No.: refers to the number of the slot where the

SDTB2 board at end B of E1 link is located.

(7) B-end resource circuit subunit No.: refers to the number of the E1 where the

128

SDTB2 board at end B of E1 link is located.

(8) B-end resource circuit No.: refers to the number of the port where IP over E1

the SDTB2 board at end B of E1 link is located.

For other parameters, use the default setting.

Configure the Connection Between SDTB2 and EIPI

[Purpose]

This task creates the connection between SDTB2 board and EIPI board.

According to the planned data, HDLC ID1 is transmitted to iBSC through semi-

permanent channel. Therefore, only the remaining four HDLC channels need to be

configured at RNC side. For the corresponding IDs and timeslots, refer to Table 6-9

Timeslot Allocation Table.

[Steps]

1. Choose Transmission Configuration > IP Protocol Configuration > DT and

EIPI Connection in the resource tree.

2. Right-click DT and EIPI Connection and choose Create > DT and EIPI

Connection from the shortcut menu.

3. Configure HDLC ID2. Use all the timeslots from 1 to 31. In the DT and EIPI

Connection dialog box, create the connection HDLC channel, as shown in

Figure 6.2-125.

129


Figure 6.2-125 Configuring HDLC ID2 Connection Relation


Connection dialog box, create the connection HDLC channel, as shown in the

Figure 6.2-126.



Connection dialog box, create the connection HDLC channel, as shown in the

Figure 6.2-127.


130


Connection dialog box, create the connection HDLC channel, as shown in

Figure 6.2-128.



(1) Subsystem No.: refers to the number of the shelf where EIPI board is located.

(2) Unit No.: refers to the number of the slot where EIPI board is located.

(3) HDLC ID.: refers to the number of HDLC. According to the planned data, there

are four HDLCs for connecting SDTB2 and RNC EIPI. The corresponding

HDLC IDs are from 1 to 4.

(4) 2MHW No. in EIPI: refers to the logical number of HW channel on EIPI board.

Generally, set 2MHW No. in EIPI and E1 No. in DTB to the same value. That

is, create the correspondence between channel on EIPI board and E1 line pair on

SDTB2 board.

(5) DT unit No.: refers to the number of the DT unit specified by HDLC channel,

that is, the slot number of SDTB board.

(6) E1 No. in DTB: refers to the physical number of E1 line on SDTB2 board. 9

indicates the first line. Because HDLC ID 0 is occupied to connect iBSC, the

corresponding E1 No. in DTB 9 is occupied. Therefore, the E1 No. in DTB for

connecting EIPI board at RNC side starts from 10. Four lines, 10, 11, 12, and 13,

131


need to be configured. They correspond to four HDLC channels.

(7) Time Slot No. in EIPI: refers to the timeslot number used by EIPI of

corresponding HDLC channel. The value is generally consistence with that of

Time Slot No. in DTB.

(8) Time Slot No. in DTB: refers to the timeslot number used by SDTB2 of

corresponding HDLC channel. The value is generally consistence with that of

Time Slot No. in EIPI.

Note:

When configuring Time Slot, ensure that the last bit, that is, bit 0, must be 0.

6.2.3 EIPI Configuration

6.2.3.1 Create IP Over E1 Ports

[Purpose]

This task creates E1 link at EIPI side and the corresponding port number. The interface

number is applicable in subsequent PPP link configuration.

According to the planned data, there are totally four E1 lines to be processed on EIPI

board. HDLC ID2, HDLC ID3, and HDLC ID4 use the same communication port

number. HDLC ID5 is a dedicated channel of OMCB and it needs an individual port

number. Therefore, four IP Over E1 port numbers need to be created.

[Steps]

1. Select IP Over E1 Configuration in the resource tree.

2. Right-click IP Over E1 Configuration and choose Create > IP Over E1

Configuration from the shortcut menu.

3. Set the port number of the E1 link corresponding to HDLC ID2, as shown in

Figure 6.2-129.

132

Figure 6.2-129 Setting Port Number of E1 Link Corresponding to HDLC ID2


Figure 6.2-130.



Figure 6.2-131.


133



Figure 6.2-132.



(1) Interface Port No.: refers to the transmission port number of the E1 that

contains corresponding HDLC.

(2) Interface E1 No.: locates to an IP over E1 port on an EUIP board, that is, to

select a DT and EIPI Connection.

(3) Time Slot: refers to the timeslot used by corresponding HDLC link. After

Interface E1 No. is selected, the system automatically reads the timeslot data

configured in DT and EIPI Connection.

6.2.3.2 Create PPP Link for EUIP Port

[Purpose]

This task creates PPP link for EUIP port.

Each IP over E1 must be configured with a PPP link. The links with the same

InterfaceE1 No will be automatically bound in the same PPP link.

[Steps]

1. Choose IP Over E1 Configuration on the resource tree.

2. Right-click IP Over E1 Configuration and choose Create > PPP Connection

from the shortcut menu.

3. Set the PPP link parameters corresponding to HDLC ID2- HDLC ID4 links, as

134


Figure 6.2-133 Setting the PPP Parameters Corresponding to HDLC ID2- HDLC ID4 Links

4. Set the PPP link parameters corresponding to the HDLC ID5 link, as shown in

Figure 6.2-134.

135


Figure 6.2-134 Setting the PPP Parameters Corresponding to HDLC ID5 Link


(1) Interface Port No.: refers to the transmission port number of the E1

corresponding to HDLC ID5. After the user selects the corresponding IP Over

E1 Configuration, the system automatically reads data.

(2) Peer IP: refers to the NMS data transmission channel corresponding to OMCB,

that is HDLC ID5. Here, set the parameter to OMCB Link IP Address at SDR

base station side, that is, 112.12.6.18.

(3) Subsystem:module:unit:sunit:port: locates to an IP over E1 port on an EUIP,

that is, to select an IP over E1 Configuration.

(4) Mpno. Sign: When the bearing protocol is PPP, set the parameter to No. the

bearing parameter is ML-PPP, set the parameter to Yes.

(5) Keep time/Keep Granularity: For example, if keep time is 3s and keep

granularity is 3, the system sends messages three times with three seconds. If no

response is received for continuous three times, it indicates that PPP link is

broken.

136

6.2.3.3 Create Interface IP Addresses

[Purpose]

The following two IP addresses need to be configured for EIPI board:

· EUIP_3GSDR: This IP address is used to transfer service data.

· EUIP_OMCB: This IP address is used to transfer OMCB supervision data.

This task creates the two IP addresses.

[Steps]

1. In the resource tree, right-click Interface Configuration and choose Create >

Interface Configuration from the shortcut menu.

2. In the popup dialog box, select EIPI from the drop-down list, as shown in

Figure 6.2-135.

Figure 6.2-135 Selecting EIPI

3. Configure the IP address corresponding to EUIP_3GSDR, as shown in Figure 6.2-

136.

137


Figure 6.2-136 Configuring EUIP_3GSDR IP Address

4. Configure the IP address corresponding to EUIP_OMCB, as shown in Figure

6.2-137.

Figure 6.2-137 Configuring EUIP_OMCB IP Address

138


(1) Local Port No: Assign a port number to each EUIP actual address to correlate to

the port numbers in IPOverE1. When PPP protocol is used, the valid port

numbers range from 1 to 190. When ML-PPP protocol is used, the valid port

numbers range from 191 to 254.

(2) The number of IP: refers to the number of IP addressed configured on EUIP.

Set it to 2.

(3) IP address: refers to the actual IP address of EUIP for SDR. Different EUIP

links cannot be within the same network section. In addition, the IP address must

be within the same network section with SDR side. Here, according to the

planned data, type the IP addresses of EUIP_3GSDR and EUIP_OMCB IP.

(4) Subnet mask: According to the planned data, type 255.255.255.0.

6.3 Configure IP over FE Interface

6.3.1 Create Service Resource Pool

[Purpose]

This task creates IP resource pool for IP service.

According to the topology planning, IP Over FE is introduced in from GIPI board.

[Steps]

1． In the configuration resource tree, select Interface Configuration. In the

shortcut menu, choose Create > Interface Configuration.

2． Select the GIPI board in the pull-down menu, as shown in Figure 6.3-138.

Figure 6.3-138 Select GIPI Board

139


3． In the IP Interface Configuration window, set the IP port number and the IP

address of OMCB port, as shown in Figure 6.3-139.

Figure 6.3-139 Configure OMCB Port IP Address of GIPI Board

4． In the IP Interface Configuration window, set the IP port number and the IP

address of 3G_SDR port, as shown in Figure 6.3-140.

140

Figure 6.3-140 Configure 3G_SDR Port IP Address of GIPI Board


(1) User Label.: the name of the service resource pool. If it is left blank, the system

will assign a name for it.

(2) RNC ID: the NE ID of RNC. It is generated by the system.

(3) RNC ID:Subsystem:module:unit:sunit:Local Port: the IP over FE port on a GIPI

board. It selects an IP over FE Configuration. In which the Local Port No. is an

optional item. User selects the FE access port according to the actual system.

(4) IP number at port: the number of the IP addresses for this interface. The default

value is 1.

(5) IP Address: the IP address of the GIPI interface board. According to the

planning, FE1 is the OMCB gateway and is set to the GIPI_OMCB address. FE2

is the SDR gateway, and is set to the GIPI_GSDR address.

6.4 Create RPU Board IP Address

[Purpose]

This task creates the IP address of RRU board.

[Steps]

1． In the configuration resource tree, select Interface Configuration. In the

shortcut menu, choose Create > Interface Configuration.

2． Select the RRU board in the pull-down menu, as shown in Figure 6.4-141.

Figure 6.4-141 Select RRU Board

141


3． In the Interface Configuration window, set the IP address of RPU, as shown in

Figure 6.4-142.

Figure 6.4-142 Configure RRU Board IP Address


(1) User Label.: the name of RPU. If it is left blank, the system will assign a name

for it.

(2) Local Port Number: RPU port number.

(3) IP Number at port: the number of IP addresses on the RPU port. A maximum of

4 IP address can be configured.

(4) IP Address: the IP address configured for the RPU port.

6.5 Create Node B Office

[Purpose]

This task creates the NE information required to add a Node B NE in radio

142

configuration.

[Steps]

1． In the configuration resource tree, select Information Configuration. In the

shortcut menu, choose Create > Node B Office.

2． In the Basic Configuration tab, set the Global Physical Net Element ID and

ANI to 6 for Node B NE as scheduled. And assign a corresponding Net Element

ID to 100, as shown in Figure 6.5-143.

Figure 6.5-143 Fill in Basic Configuration

3． In the Node B Config tab, set the bearer type. In this example, three bearers are

all set to IP, as shown in Figure 6.5-144.

Figure 6.5-144 Fill in Node B Config

4． In the Basic Config-1 menu, select the protocol version and the transport bear

143


type index, as shown in Figure 6.5-145.

Figure 6.5-145 Fill in Basic Config-1


(1) Protocol Version: select the protocol version used.

(2) Basic Priority Transport Bearer Type Index: select the transport bear type index.

6.6 Create Path Group

[Purpose]

This task creates the path group and assigns the path group number.

[Steps]

1． In the configuration resource tree, select Path Group Configuration. In the

shortcut menu, choose Create > Path Group.

2． Configure the Path Group Configuration parameters as schedule, as shown in

Figure 6.6-146.

144

Figure 6.6-146 Fill in Path Group Configuration


(1) PathGroup ID: This is a user defined number used to distinguish the different

path groups in the system. It is a unique number and no repeated number is

allowed.

(2) Forward/Backward Bandwidth: it is 3800 by default, and the unit is kbps.

Configure this according to the actual conditions.

6.7 Create SCTP Association

[Purpose]

This task creates SCTP in the WCDMA side.

The GSM SCTP is added at the GSM side.

[Steps]

1． In the configuration resource tree, choose Sigtran Configuration > SCTP

Association Configuration. In the shortcut menu, choose Create > SCTP

Association Configuration.

2． Open the Basic Configuration of SCTP Association window and configure the

basic SCTP association parameters, as shown in Figure 6.7-147.

145


Figure 6.7-147 Fill in Basic Configuration of SCTP Association


(1) SCTP Association ID: user defined data. It is a unique data and no repeated

number is allowed.

(2) Protocol Type of SCTP Association: select NBAP. Other options are not

currently valid.

(3) Application Property of SCTP Association: currently client and server are of the

same function though client is recommended.

(4) No of Connected incoming streams: it is 6 by default. Fill in a proper number

according to the actual system. But it must be consistent with the number of the

connected outgoing streams.

(5) No of Connected incoming streams: it is 16 by default. Fill in a proper number

according to the actual system. But it must be consistent with the number of the

connected incoming streams.

Use the default values for other parameters.

3． Click the IP Configuration of SCTP Association tab to open the dialog box,

and configure the basic SCTP association parameters, as shown in Figure 6.7-

148.

146

Figure 6.7-148 Fill in IP Configuration of SCTP Association


(1) Local-end Port No.: the local SCTP port number assigned for RNC. Set the

SCTP port number to 777 as scheduled.

(2) Peer-end Port No: the peer-end SCTP port number assigned for Node B. It may

be and may not be the local port number. Set the SCTP port number to 777 as

scheduled.

(3) Local-end IP Address: the IP address of a service board. It is the IP Iub port

address of the ROMB board. Fill in a number as scheduled.

(4) Peer-end IP Address: the peer-end IP address of the peer-end Node B. Fill in a

number as scheduled.

6.8 Create Node B Office Properties

[Purpose]

This task configures the office related properties after a Node B office is added.

[Steps]

147


1． In the configuration resource tree, choose NE Information Configuration, and

double-click the Node B office added.

2． Click the Node B office tab and set the related parameters in the Node B office

dialog box, as shown in Figure 6.8-149.

Figure 6.8-149 Set Node B office Properties

3． Click the SCTP Resource Relation tab and set the SCTP association

information in the SCTP Resource Relation dialog box, as shown in Figure

6.8-150 .

Figure 6.8-150 Set SCTP Resource Relation Properties

148

4． Click the Node B Port Configuration tab and configure the SCTP stream

parameter in the Node B Port Configuration dialog box, as shown in Figure

6.8-151 .

Figure 6.8-151 Fill in NodeB Port Configuration


1. No.: the association number of the SCTP stream. It is unique in the base station.

2. Port Type: NCP or CCP. Both NCP and CCP are needed in a WCDMA system.

Configure one NCP and multiple CCP.

Note:

The NCP and CCP bandwidth is configured by the system automatically.

6.9 Create Global Supplemented Resource

[Purpose]

This task creates global supplemented resources.

Global supplemented resource is used for OMCB RPU IP address and outgoing OMCB

NM IP.

[Steps]

1． In the configuration resource tree, choose RNC Config Set. In the shortcut

menu, choose Create > Global Supplemented Configuration.

2． In the Global Supplemented Configuration tab, configure the global

supplemented parameters, as shown in Figure 6.9-152.

149


Figure 6.9-152 Fill in Global Supplemented Configuration


(1) OMCB server IP address: set the IP address for the OMCB Server. Fill in a

number as scheduled.

(2) Manager Node B IP: the virtual IP address configured on ROMB RPU for

OMCB information processing.

6.10 Node B Configuration Information

[Purpose]

This task creates the management relation between RNC and Node B, and configures

the basic information.

[Steps]

1． In the configuration resource tree, choose RNC Config Set > RNC Radio

Resource Management > NodeB Configuration Information.

2． In the NodeB Configuration Information tab, select the Node B to be

configured and leave other parameters to the default values, as shown in Figure

6.10-153.

150

Figure 6.10-153 Node B Information Configuration

6.11 Create UTRAN CELL

[Purpose]

This task creates UTRAN cells. It configures the parameters for the serving cell global

information and cell creation.

[Steps]

1． In the configuration resource tree, choose RNC Config Set > RNC Radio

Resource Management > UTRAN CELL.

2． In the shortcut menu, choose Create > Create UTRAN CELL.

3． Click the UTRAN Cell Global Information tab, and set the global information

for a 3G serving cell in the UTRAN Cell Global Information dialog box, as

shown in Figure 6.11-154 .

151


Figure 6.11-154 Set Serving Cell Global Information


(1) Cell Identity: the identity of a cell. It is a unique number in the RNC.

(2) RCP Module Number: the RCP module number that a cell belongs to.

(3) NodeB Number: the Node B number that a cell belongs to.

(4) Sector Identity: the sector number that a cell belongs to.

(5) Location Area Code: the location area code of a cell.

(6) Service Area Code for CS and PS Domain: the service area code for CS and PS

domain of a cell.

(7) Routing Area Code: the routing area code of a cell.

4． Click the Cell Setup Parameters tab and configure the basic setup parameters

of a cell in the Cell Setup Parameters dialog box, as shown in Figure 6.11-155.

152

Figure 6.11-155 Configure Basic Setup Parameters


(1) Local Identity: the identity of a local cell. It is a unique number in the RNC.

(2) Local Cell Group Identity: the identity of a local cell group.

(3) Scenario Type: a parameter used for the network planning and optimization.

(4) T_Cell: the starting time and the scheduled delay of the SCH, the CPICH, and

the downlink code of a cell.

(5) Frequency Band Indicator: the indicator of the frequency band of a cell.

(6) UUARFCN/DUARFCN: the central frequency of the unlink/downlink carriers.

(7) Cell Maximum Transmission Power: the maximum transmission power of cell.

(8) Cell Primary Scrambling Code: the primary scrambling code in a cell. A

UTRAN system supports 512 scrambling codes at a range of [0,511].

(9) Primary SCH Power: the primary SCH transmission power, or the transmission

power of the main synchronization channel in a cell. It is a relative value in

relation to the main pilot transmission power in the cell.

(10) Secondary SCH Power: the secondary SCH transmission power, or the

transmission power of the secondary synchronization channel in a cell. It is a

153


relative value in relation to the main pilot transmission power in the cell.

(11) BCH Power: the BCH transmission power. It is a relative value in relation to the

main pilot transmission power in the cell.

(12) P-CPICH Power: the public pilot channel transmission power. It is the power

used by a cell when sending P-CPICH. It is an absolute value.

154

2GU_OC01_E1_0 ZXSDR Configuration for GU Co-Site(V4.00.30) 162

Documents

passive electric

option appears

zxsdr bts

manages signaling

flexibly schedule

popup dialog

optical fiber

slave optical