BSC6900 UMTS Initial Configuration Guide(V900R013C00_03)(PDF)-En

BSC6900 UMTSV900R013C00

Initial Configuration Guide

Issue 03

Date 2011-08-31

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2011. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respective holders. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,and recommendations in this document are provided "AS IS" without warranties, guarantees or representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 03 (2011-08-31) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

About This Document

PurposeThis document describes the initial configuration of BSC6900.

Product VersionThe following table lists the product version related to this document.

Product Name Product Version

BSC6900 V900R013C00

Intended AudienceThis document is intended for:

l Field engineersl Network operatorsl System engineers

Organization1 Changes in the BSC6900 UMTS Initial Configuration Guide

This chapter describes the changes in the BSC6900 UMTS Initial Configuration Guide.

2 Introduction to Initial Configuration

Initial configuration creates the configuration script for the equipment to start to operate.

3 Data Preparation for Initial Configuration

In the BSC6900 initial configuration, some data is obtained from the data sheets after negotiationwith other network elements. The negotiated data includes the global data, equipment data,interface data, base station data, and cell data.

4 Initial Configuration Procedures

BSC6900 UMTSInitial Configuration Guide About This Document


ii

This chapter describes the process of creating the initial configuration script for the BSC6900.

5 Typical Configuration Script

The typical configuration scripts used in this document derive from the documents related to theBSC6900. The typical configuration scripts concern global data, equipment data, networkinterfaces, base stations, and cells.

6 Configuring the Global Information

This chapter describes how to configure the global information. The global data configurationprovides a basis for all the other configurations, and therefore must be determined during networkplanning. After the BSC6900 global data configuration takes effect, do not modify it unless thenetwork is replanned.

7 Configuring the Equipment Data

This chapter provides the example script for configuring the equipment data for the BSC6900,including the system information and the data about the cabinet, subrack, and board.

8 Configuring the Interfaces

This chapter describes how to configure the UMTS interfaces, including the Iub, Iu-CS, Iu-PS,and Iur interfaces.

9 Configuring the Cell Data

This chapter describes how to configure a UMTS NodeB and its cells, including how to configurethe NodeB, UMTS cell, intra-frequency neighboring cell, inter-frequency neighboring cell, andneighboring GSM cell.

10 Configuration Reference Information

This chapter describes the concepts, principles, rules, and conventions related to dataconfiguration.

ConventionsSymbol Conventions

The symbols that may be found in this document are defined as follows.

Symbol Description

Indicates a hazard with a high level of risk, which if notavoided, will result in death or serious injury.

Indicates a hazard with a medium or low level of risk, whichif not avoided, could result in minor or moderate injury.

Indicates a potentially hazardous situation, which if notavoided, could result in equipment damage, data loss,performance degradation, or unexpected results.

Indicates a tip that may help you solve a problem or savetime.



iii

Symbol Description

Provides additional information to emphasize or supplementimportant points of the main text.

General Conventions

The general conventions that may be found in this document are defined as follows.

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are inboldface. For example, log in as user root.

Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are inCourier New.

Command Conventions

The command conventions that may be found in this document are defined as follows.


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[ ] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated byvertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated byvertical bars. One item is selected or no item is selected.

{ x | y | ... }* Optional items are grouped in braces and separated byvertical bars. A minimum of one item or a maximum of allitems can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated byvertical bars. Several items or no item can be selected.

GUI Conventions

The GUI conventions that may be found in this document are defined as follows.



iv


Boldface Buttons, menus, parameters, tabs, window, and dialog titlesare in boldface. For example, click OK.

> Multi-level menus are in boldface and separated by the ">"signs. For example, choose File > Create > Folder.

Keyboard Operations

The keyboard operations that may be found in this document are defined as follows.

Format Description

Key Press the key. For example, press Enter and press Tab.

Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt+A means the three keys should be pressed concurrently.

Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A meansthe two keys should be pressed in turn.

Mouse Operations

The mouse operations that may be found in this document are defined as follows.

Action Description

Click Select and release the primary mouse button without movingthe pointer.

Double-click Press the primary mouse button twice continuously andquickly without moving the pointer.

Drag Press and hold the primary mouse button and move thepointer to a certain position.



v

Contents

About This Document.....................................................................................................................ii

1 Changes in the BSC6900 UMTS Initial Configuration Guide..............................................1

2 Introduction to Initial Configuration........................................................................................3

3 Data Preparation for Initial Configuration..............................................................................4

4 Initial Configuration Procedures................................................................................................5

5 Typical Configuration Script......................................................................................................6

6 Configuring the Global Information.........................................................................................76.1 Configuring the Basic Information.....................................................................................................................86.2 Configuring the OPC and DPC..........................................................................................................................86.3 Configuring the Area Information....................................................................................................................106.4 Configuring the M3UA Local and Destination Entities...................................................................................10

7 Configuring the Equipment Data.............................................................................................117.1 Configuring the System Information................................................................................................................137.2 Configuring a Cabinet......................................................................................................................................137.3 Configuring a Subrack......................................................................................................................................137.4 Configuring a Board.........................................................................................................................................147.5 Configuring an EMU........................................................................................................................................157.6 Configuring the Clocks.....................................................................................................................................157.7 Configuring the Time.......................................................................................................................................177.8 Configuring the IP Address of the EMS Server...............................................................................................177.9 Configuring BSC Custom Alarm.....................................................................................................................17

8 Configuring the Interfaces.........................................................................................................198.1 Configuring the Iub Interface (over ATM).......................................................................................................21

8.1.1 Configuring the Physical Layer (over ATM)..........................................................................................218.1.2 Configuring the ATM Traffic Resources................................................................................................248.1.3 Configuring the Control Plane of the Iub Interface (over ATM)............................................................248.1.4 Configuring the Mapping Between Service Types and Transmission Resources...................................258.1.5 Configuring the User Plane of the Iub Interface (over ATM).................................................................258.1.6 Configuring the OM Channel over the Iub Interface (over ATM)..........................................................26

8.2 Configuring the Iub Interface (over IP)............................................................................................................26

BSC6900 UMTSInitial Configuration Guide Contents


vi

8.2.1 Configuring the Physical Layer and Data Link Layer (over IP).............................................................278.2.2 Configuring the Control Plane for the Iub Interface (over IP)................................................................308.2.3 Configuring the Mapping Between Service Types and Transmission Resources...................................318.2.4 Configuring the User Plane over the Iub Interface (over IP)...................................................................328.2.5 Configuring an OM Channel over Iub Interface (over IP)......................................................................32

8.3 Configuring the Iub Interface (over ATM and IP)...........................................................................................338.4 Configuring the Iu-CS Interface (over ATM)..................................................................................................34

8.4.1 Configuring the Physical Layer (over ATM)..........................................................................................358.4.2 Configuring the Traffic Resource at the ATM Layer..............................................................................378.4.3 Configuring the Control Plane over the Iu-CS Interface (over ATM)....................................................388.4.4 Configuring the Mapping Between Service Types and Transmission Resources...................................398.4.5 Configuring the User Plane over the Iu-CS Interface (over ATM).........................................................39

8.5 Configuring the Iu-CS Interface (over IP)........................................................................................................398.5.1 Configuring the Physical Layer and Data Link Layer over IP................................................................408.5.2 Configuring the Control Plane over the Iu-CS Interface (over IP)..........................................................448.5.3 Configuring the Mapping Between Service Types and Transmission Resources...................................458.5.4 Configuring the User Plane over the Iu-CS Interface (over IP)..............................................................45

8.6 Configuring the Iu-PS Interface (over ATM)...................................................................................................468.6.1 Configuring the Physical Layer for the UOIa/UOIc Board.....................................................................468.6.2 Configuring the Traffic Resource at the ATM Layer..............................................................................468.6.3 Configuring the Control Plane over the Iu-PS Interface (over ATM).....................................................478.6.4 Configuring the Mapping Between Service Types and Transmission Resources...................................478.6.5 Configuring the User Plane over the Iu-PS Interface (over ATM).........................................................48

8.7 Configuring the Iu-PS Interface (over IP)........................................................................................................488.7.1 Configuring the Physical Layer and Data Link Layer over IP................................................................498.7.2 Configuring the Control Plane over the Iu-PS Interface (over IP)..........................................................538.7.3 Configuring the Mapping Between Service Types and Transmission Resources...................................548.7.4 Configuring the User Plane over the Iu-PS Interface (over IP)...............................................................54

8.8 Configuring the Iur Interface (over ATM).......................................................................................................558.8.1 Configuring the Physical Layer (over ATM)..........................................................................................558.8.2 Configuring the Traffic Resource at the ATM Layer..............................................................................588.8.3 Configuring the Control Plane over the Iur Interface (over ATM).........................................................588.8.4 Configuring the Mapping Between Service Types and Transmission Resources...................................598.8.5 Configuring the User Plane over the Iur Interface (over ATM)..............................................................598.8.6 Configuring a Static Transfer Path..........................................................................................................60

8.9 Configuring the Iur Interface (over IP).............................................................................................................618.9.1 Configuring the Physical Layer and Data Link Layer over IP................................................................618.9.2 Configuring the Control Plane over the Iur Interface (over IP)...............................................................658.9.3 Configuring the Mapping Between Service Types and Transmission Resources...................................668.9.4 Configuring the User Plane over the Iur Interface (over IP)...................................................................668.9.5 Configuring a Static Drift Path................................................................................................................67

8.10 Configuring the Iu-BC Interface (over ATM)................................................................................................68



vii

8.10.1 Configuring the Physical Layer (over ATM)........................................................................................688.10.2 Configuring the Traffic Resource at the ATM Layer............................................................................718.10.3 Configuring the IPoA Data....................................................................................................................718.10.4 Configuring the CBS Address...............................................................................................................72

8.11 Configuring the Iu-BC Interface (over IP).....................................................................................................728.11.1 Configuring the Physical Layer and Data Link Layer over IP..............................................................728.11.2 Configuring the CBS Address...............................................................................................................76

9 Configuring the Cell Data.........................................................................................................779.1 Configuring a NodeB........................................................................................................................................799.2 Configuring a UMTS Cell................................................................................................................................799.3 Configuring an Intra-Frequency Neighboring Cell..........................................................................................809.4 Configuring an Inter-Frequency Neighboring Cell..........................................................................................819.5 Configuring a Neighboring GSM Cell.............................................................................................................829.6 Configuring a Neighboring LTE Cell...............................................................................................................82

10 Configuration Reference Information...................................................................................8410.1 Data Configuration Principles for Equipment................................................................................................85

10.1.1 Configuration Rules of the Cabinets.....................................................................................................8510.1.2 Configuration Rules of the Subracks.....................................................................................................8510.1.3 Configuration Rules of the Boards........................................................................................................8510.1.4 Configuration Rules of the Clock..........................................................................................................8710.1.5 Introduction to Time Synchronization...................................................................................................88

10.2 Data Configuration Principles for Transmission............................................................................................8810.2.1 Physical Layer Data Configuration Principles......................................................................................8810.2.2 ATM Transport Modes..........................................................................................................................9410.2.3 PVC Parameters of the ATM Layer......................................................................................................9910.2.4 ATM Traffic Resource Configuration Principles................................................................................10210.2.5 AAL2 Configuration Principles...........................................................................................................10310.2.6 MTP3/M3UA Configuration Principles..............................................................................................10410.2.7 TRM Configuration Principles............................................................................................................10510.2.8 Activity Factor Configuration Principles............................................................................................106

10.3 Data Configuration Principles for Interfaces................................................................................................10610.3.1 Data Configuration Principles for the Iub Interface (over ATM)........................................................10610.3.2 Data Configuration Principles for the Iub Interface (over IP).............................................................11010.3.3 Data Configuration Principles for the Iub Interface (over ATM and IP)............................................11810.3.4 Data Configuration Principles for the Iu-CS Interface (over ATM)...................................................12210.3.5 Data Configuration Principles for the Iu-CS Interface (over IP).........................................................12710.3.6 Data Configuration Principles for the Iu-PS Interface (over ATM)....................................................13310.3.7 Data Configuration Principles for the Iu-PS Interface (over IP).........................................................13710.3.8 Data Configuration Principles for the Iur Interface (over ATM)........................................................13810.3.9 Data Configuration Principles for the Iur Interface (over IP)..............................................................14110.3.10 Data Configuration Principles for the Iu-BC Interface (over ATM).................................................14410.3.11 Data Configuration Principles for the Iu-BC Interface (over IP)......................................................147



viii

10.4 Data Configuration Principles for Cells.......................................................................................................14910.4.1 Definitions of Sector, Carrier, and Cell...............................................................................................14910.4.2 Definitions of Local Cell and Logical Cell.........................................................................................15010.4.3 Logical Cell Model..............................................................................................................................15110.4.4 Areas of Logical Cells.........................................................................................................................15110.4.5 Definition of Neighboring Cell............................................................................................................152

10.5 Data Configuration Guidelines for Specifications........................................................................................152



ix

1 Changes in the BSC6900 UMTS InitialConfiguration Guide

This chapter describes the changes in the BSC6900 UMTS Initial Configuration Guide.

03 (2011-08-31)

This is the third commercial release of V900R013C00.

Compared with issue 02 (2011-07-11), this issue includes the following new topics:l Configuring a Neighboring LTE Cell

Compared with issue 02 (2011-07-11), this issue does not incorporate any changes.

Compared with issue 02 (2011-07-11), this issue does not exclude any topics.

02 (2011-07-11)

This is the first commercial release of V900R013C00.

Compared with issue 01 (2011-04-25), this issue does not include any new topics.

Compared with issue 01 (2011-04-25), this issue incorporates the following changes:

Content Description

Configuring the OPC and DPC The sentence 'Each BSC6900 can beconfigured with only one OPC.' is deleted.

Compared with issue 01 (2011-04-25), this issue does not excludes any topics.

01 (2011-04-25)

This is the first commercial release of V900R013C00.

Compared with issue Draft A (2011-01-31), this issue does not include any new topics.

Compared with issue Draft A (2011-01-31), this issue incorporates the following changes:

BSC6900 UMTSInitial Configuration Guide

1 Changes in the BSC6900 UMTS Initial ConfigurationGuide


1

Content Description

UMTS Data Preparation for the InitialConfiguration

The recommended configurations of someparameters are added.

Configuring the Clocks The procedure for configuring the externalclock, line clock, and GPS clock is optimized.

Compared with issue Draft A (2011-01-31), this issue excludes the following topics:l Data Configuration Principles for Numbering

Draft A (2011-01-31)This is the Draft A release of V900R013C00.

Compared with issue 04 (2010-11-30) of V900R012C01, this issue does not include any newtopics.

Compared with issue 04 (2010-11-30) of V900R012C01, this issue incorporates the followingchanges:

Content Description

10.5 Data Configuration Guidelines forSpecifications

The specifications are updated.

Compared with issue 04 (2010-11-30) of V900R012C01, this issue does not exclude any topics.

BSC6900 UMTSInitial Configuration Guide

1 Changes in the BSC6900 UMTS Initial ConfigurationGuide


2

2 Introduction to Initial Configuration

Initial configuration creates the configuration script for the equipment to start to operate.

l The configuration script can be created by running MML commands on the BSC6900 LMT.For the LMT operation guide, see the BSC6900 UMTS LMT User Guide.

l During commissioning, the script is imported to the BSC6900. For data modification afterthe BSC6900 starts operating, see the RAN Reconfiguration Guide.

l After the BSC6900 starts operating, operators can enable or disable features based on siterequirements. The related data configuration does not belong to initial configuration. Fordetails, see the RAN Feature Activation Guide.

BSC6900 UMTSInitial Configuration Guide 2 Introduction to Initial Configuration


3

3 Data Preparation for Initial Configuration

In the BSC6900 initial configuration, some data is obtained from the data sheets after negotiationwith other network elements. The negotiated data includes the global data, equipment data,interface data, base station data, and cell data.

For the data preparation for BSC6900 initial configuration, see UMTS Data Preparation forthe Initial Configuration.

For the restrictions on the parameter settings in MML commands, see BSC6900 UMTS MMLCommand Reference.

BSC6900 UMTSInitial Configuration Guide 3 Data Preparation for Initial Configuration


4

4 Initial Configuration Procedures

This chapter describes the process of creating the initial configuration script for the BSC6900.

Figure 4-1 shows the initial configuration process.

Figure 4-1 Initial configuration process

For details about loading the BSC6900 initial configuration data, see the BSC6900 UMTSCommissioning Guide.

BSC6900 UMTSInitial Configuration Guide 4 Initial Configuration Procedures


5

5 Typical Configuration Script

The typical configuration scripts used in this document derive from the documents related to theBSC6900. The typical configuration scripts concern global data, equipment data, networkinterfaces, base stations, and cells.

For details of the BSC6900 typical configuration scripts, see the UMTS Typical ConfigurationScripts.

BSC6900 UMTSInitial Configuration Guide 5 Typical Configuration Script


6

6 Configuring the Global Information

About This Chapter

This chapter describes how to configure the global information. The global data configurationprovides a basis for all the other configurations, and therefore must be determined during networkplanning. After the BSC6900 global data configuration takes effect, do not modify it unless thenetwork is replanned.

1. 6.1 Configuring the Basic InformationThis section describes how to configure the basic data of the BSC6900. The configurationof the BSC6900 basic data is the prerequisite for the initial configuration.

2. 6.2 Configuring the OPC and DPCThis section describes how to configure the OPC and DPC.

3. 6.3 Configuring the Area InformationThis section describes how to configure the area information of the BSC6900. You needto configure the information about the Location Area (LA), Routing Area (RA), ServiceArea (SA), and User Registration Area (URA).

4. 6.4 Configuring the M3UA Local and Destination EntitiesThis section describes how to configure the local and destination M3UA entities. You needto configure the M3UA entities when the IP-based networking is used.

BSC6900 UMTSInitial Configuration Guide 6 Configuring the Global Information


7

6.1 Configuring the Basic InformationThis section describes how to configure the basic data of the BSC6900. The configuration ofthe BSC6900 basic data is the prerequisite for the initial configuration.

Prerequisitel All the subracks are switched to the ineffective mode by running the SET

CFGDATAINEFFECTIVE command.l The basic data is not configured.

ProcedureStep 1 Run the ADD URNCBASIC command to add the basic UMTS data.

Step 2 Run the ADD UCNOPERATOR command to add a primary UMTS operator. In this step, setOperator Type to PRIM(Primary Operator).

Step 3 Optional: To configure more secondary UMTS operators, run the ADD UCNOPERATORcommand repeatedly. In this step, set Operator Type to SEC(Secondary Operator).

Step 4 Run the ADD UCNOPERGROUP command to add a UMTS operator group.

Step 5 Optional: If the internal subnet number of the BSC6900 is the same as the external networknumber, run the SET SUBNET command to set the subnet number according to the networkplanning.

Step 6 Optional: When the BSC6900 acts as the SCTP server, run the SET SCTPSRVPORTcommand to set the SCTP service listening ports.

Step 7 Optional: Run the LST GLOBALROUTESW command to query the setting of the globalroute management switch. If the global route management function is not required but the globalroute management switch is set to ON, run the SET GLOBALROUTESW command to set theswitch to OFF.

----End

6.2 Configuring the OPC and DPCThis section describes how to configure the OPC and DPC.

Prerequisitel The basic data of the BSC6900 has been configured. For details, see Configuring the Basic

Data.

Contextl The MSC server is not directly connected to the BSC6900. Instead, routes are configured

on the MGW to transfer data between the BSC6900 and the MSC server.l The network ID and the signaling point code must be planned in the SS7 network.l When configuring a DPC, specify the signaling route mask for load sharing. When

configuring a signaling link set, specify the signaling link mask to determine the policy of



8

routing between signaling links within that signaling link set. The result of the signalingroute mask AND the signaling link mask should be 0.

Procedure

Step 1 Run the ADD OPC command to add an OPC, repeat this step until all desired OPCs are added.

Step 2 Run the ADD N7DPC command to add a DPC. To add more DPCs, repeat this step until alldesired DPCs are added.l In the case of the Iu-CS interface (over ATM):

– Set Signalling route mask to B0000.– When adding a DSP for the media gateway, set Adjacent flag to YES

(DIRECT_CONNECT), DSP type to IUCS-ALCAP, and STP function switch to ON(ON). This indicates that an STP is added.

– When adding a DSP for the MSC server, set Adjacent flag to NO(NO_DIRECT_CONNECT) and DSP type to IUCS-RANAP. This indicates that theDSP has the Iu-CS radio network control plane function.

l In the case of the Iu-CS interface (over IP):– Set Signalling route mask to B0000.– When adding a DSP for the media gateway, set Adjacent flag to YES

(DIRECT_CONNECT), DSP type to STP, and STP function switch to ON(ON). Thisindicates that an STP is added.

– When adding a DSP for the MSC server, set Adjacent flag to NO(NO_DIRECT_CONNECT) and DSP type to IUCS-RANAP. This indicates that theDSP has the Iu-CS radio network control plane function.

l In the case of the Iu-PS interface (over ATM):– Set Signalling route mask to B0000.– Set DSP Type to IUPS.– Set DSP bear type to MTP3.

l In the case of the Iu-PS interface (over IP):– Set Signalling route mask to B0000.– Set DSP Type to IUPS.– Set DSP bear type to M3UA.

NOTE

l When two MGWs are configured, set Signalling route mask to B0001.

l The settings of Signalling route mask and Signalling link mask differ with the number of MGWsconfigured. The result of the bit AND operation on Signalling route mask and Signalling linkmask, however, must be zero.

l In the case of the Iur interface (over ATM):– Set Signalling route mask to B0000.– Set DSP Type to IUR.– Set DSP bear type to MTP3.

l In the case of the Iur interface (over IP):– Set Signalling route mask to B0000.– Set DSP Type to IUR.



9

– Set DSP bear type to M3UA.

----End

6.3 Configuring the Area InformationThis section describes how to configure the area information of the BSC6900. You need toconfigure the information about the Location Area (LA), Routing Area (RA), Service Area (SA),and User Registration Area (URA).

PrerequisiteThe basic data of the BSC6900 is configured. For details, see Configuring the Basic Data.

Contextl The LA information consists of the Location Area Code (LAC) and PLMN tag range of

the LA. The RA information consists of the Routing Area Code (RAC) and the PLMN tagrange of the RA.

l The SA information consists of the CS SA information and the PS SA information.

Procedure

Step 1 Run the ADD ULAC command to add an LA. To add more LAs, run this command repeatedly.

Step 2 Run the ADD URAC command to add an RA. To add more RAs, run this command repeatedly.

Step 3 Run the ADD USAC command to add a CS/PS SA. To add more SAs, run this commandrepeatedly.

Step 4 Run the ADD UURA command to add a URA. To add more URAs, run this commandrepeatedly.

Step 5 Run the ADD UCZ command to set an SA as a classified zone. To add more classified zones,run this command repeatedly.

----End

6.4 Configuring the M3UA Local and Destination EntitiesThis section describes how to configure the local and destination M3UA entities. You need toconfigure the M3UA entities when the IP-based networking is used.

PrerequisiteThe OPC and DPC are configured. For details, see Configuring the OPC and DPC.

Procedure

Step 1 Run the ADD M3LE command to add an M3UA local entity.

Step 2 Run the ADD M3DE command to add an M3UA destination entity.

----End



10

7 Configuring the Equipment Data

About This Chapter

This chapter provides the example script for configuring the equipment data for the BSC6900,including the system information and the data about the cabinet, subrack, and board.

ContextFamiliarize yourself with 10.1 Data Configuration Principles for Equipment beforeperforming the operations described in this chapter.

1. 7.1 Configuring the System InformationThis section describes how to configure the system information of the BSC6900.

2. 7.2 Configuring a CabinetThis section describes how to configure a cabinet for the BSC6900. You need to configurethe cabinet based on the requirements specified in the actual network planning.

3. 7.3 Configuring a SubrackThis section describes how to configure a subrack for the BSC6900. You need to configurethe subrack based on the requirements specified in the actual network planning.

4. 7.4 Configuring a BoardThis section describes how to configure a board for the BSC6900. You need to configurethe board based on the requirements specified in the actual network planning.

5. 7.5 Configuring an EMUThis section describes how to configure an EMU. An EMU is required for the BSC6900to collect the Boolean value, analog value, and alarm threshold information.

6. 7.6 Configuring the ClocksThis section describes how to configure the BSC6900 clocks. You need to configure theclock source of interface boards, clock source of the system, and work mode of the systemclock source.

7. 7.7 Configuring the TimeThis section describes how to configure the time of the BSC6900. You need to set the timezone, daylight saving time, and Simple Network Time Protocol (SNTP) synchronizationserver.

8. 7.8 Configuring the IP Address of the EMS Server

BSC6900 UMTSInitial Configuration Guide 7 Configuring the Equipment Data


11

This section describes how to configure the IP address for the EMS server. The EMS serveris used to perform OM on the base station through the BSC6900.

9. 7.9 Configuring BSC Custom AlarmThis section describes how to configure alarm ports, alarm IDs, and alarm names of theBSC.



12

7.1 Configuring the System InformationThis section describes how to configure the system information of the BSC6900.


ContextThe system information consists of the system description, system ID, contact information ofthe vendor, system location, and system services.

Procedure

Step 1 Run the SET SYS command to set the system information.

----End

7.2 Configuring a CabinetThis section describes how to configure a cabinet for the BSC6900. You need to configure thecabinet based on the requirements specified in the actual network planning.


ContextThe Main Processing Rack (MPR) is configured by default. You do not need to add it throughthe MML command.

Procedure

Step 1 Run the ADD CAB command to add an Extended Processing Rack (EPR).

----End

7.3 Configuring a SubrackThis section describes how to configure a subrack for the BSC6900. You need to configure thesubrack based on the requirements specified in the actual network planning.

PrerequisiteThe basic data of the BSC6900 has been configured. For details, see Configuring the Basic Data.



13

ContextThe Main Processing Subrack (MPS) is configured by default. You do not need to add thissubrack by running an MML command.

Procedure

Step 1 To add an Extended Processing Subrack (EPS) for the BSC6900, run the ADD SUBRACKcommand. To add more EPSs, repeat this step until all desired EPSs are added.

Step 2 After a subrack is added, run the SET SCUPORT command to enable the corresponding porton the SCU board in the MPS.

Step 3 Run the SET CFGDATAEFFECTIVE command to set the subrack to effective mode.

----End

Follow-up ProcedureTo enable the monitoring function of the power distribution box, complete the following steps:

1. Run the MOD SUBRACK command to enable the monitoring function of the powerdistribution box. In this step:l Set Subrack No. to the number of the subrack connected to the power distribution box.l Set Connect power monitoring board to YES.

2. Run the SET PWRPARA command to set the parameters of the power monitoring board.3. Run the SET PWRALMSW command to set the alarm switch on the power monitoring

board.

NOTEIf output-alarm information needs to be viewed, set the corresponding switch on the PDB to ON.Otherwise, set the corresponding switch on the PDB to OFF. There is no need to set the input switchon the PDB for input alarms.

7.4 Configuring a BoardThis section describes how to configure a board for the BSC6900. You need to configure theboard based on the requirements specified in the actual network planning.

Contextl For the data to be negotiated and planned for configuring a board for the BSC6900, see

Data Preparation for Initial Configuration.l For details about the board configuration rules, see Configuration Rules of the Boards.

Procedure

Step 1 Run the ADD BRD command to add a board to the BSC6900. To add more boards, run thiscommand repeatedly.

Step 2 Optional: When the boards work in active/standby mode, run the SET MSP command to setthe attributes of the Multiplex Section Protection (MSP).

----End



14

7.5 Configuring an EMUThis section describes how to configure an EMU. An EMU is required for the BSC6900 to collectthe Boolean value, analog value, and alarm threshold information.

PrerequisiteThe subrack for housing the EMU is already configured.

Contextl The EMU gathers Boolean values, analog values, and alarm threshold information and

reports them to the LMT.l One cabinet can be configured with only one EMU.

Procedure

Step 1 Run the ADD EMU command to add an EMU.

----End

7.6 Configuring the ClocksThis section describes how to configure the BSC6900 clocks. You need to configure the clocksource of interface boards, clock source of the system, and work mode of the system clock source.


ContextNOTE

The BSC6900 clock information is determined during network planning. In an all-IP over FE/GE network,you do not need to configure a clock source for the BSC6900, and at this time, the BSC use the localoscillator as default.

The clock source of the BSC6900 can be an external clock, line clock, or GPS clock.

l External clockAn external clock can be a BITS clock or an external 8 kHz clock. When the clock sourceis an external clock, the BSC6900 receives the external clock from CLKIN0 or CLKIN1on the GCUa/GCGa board.

l Line clockThe line clock is the 8 kHz clock transmitted from an interface board to the GCUa board.

l GPS clockThe GPS clock is the satellite synchronization clock. When the GCGa board is configuredwith a satellite card, the BSC6900 can use the satellite antenna port on the GCGa board toreceive GPS clock signals.



15

Procedurel Configuring the external clock

1. Run the ADD CLKSRC command to add a system clock source and the clock sourcepriority.

NOTE

l Clock source type

l If the clock signals are extracted from the CN by the interface board (such as the PEUa/AEUa/AOUa/POUa/UOIa interface board) in the EPS and then sent to the GCUa/GCGa board in the MPS through the panels, Clock source type of the MPS needs tobe set to BITS1-2MHZ or BITS2-2MHZ.

l If the clock signals are extracted from the CN by the interface board in the MPS andthen sent to the GCUa/GCGa board through the backplane of the MPS, Clock sourcetype should be set to LINE1_8KHZ or LINE2_8KHZ.

l If the clock signals are provided by the external BITS, Clock source type should beset to BITS1-2MBPS, BITS2-2MBPS, BITS1-1.5MBPS, or BITS2-1.5MBPS.

l If the clock signals are provided by the GPS and then sent to the GCGa board, Clocksource type should be set to GPS.

l If the clock signals are provided by the external 8 kHz clock, Clock source type shouldbe set to 8KHZ.

l Clock source priority

Clock source priority ranges from 1 to 4. The clock source of priority 0 is configured bydefault. Priority 0 is the lowest priority. The descending ranking of priorities is 1, 2, 3, and4.

2. Run the SET CLKMODE command to set the work mode of the system clock source.

NOTE

It is recommended that System clock working mode be set to AUTO(Auto Handover) sothat the system can switch to the highest-priority clock source when the current clock sourceis unavailable.

l Configuring the line clock

1. Run the SET CLK command to set the clock source of the interface board.

NOTE

When the system clock is the line clock, interface boards need to be configured with clocksources.



NOTE


l Configuring the GPS clock

1. If the clock source is the line clock, run the SET CLK command to set the clock sourcefor the interface board.





16

NOTE


----End

Follow-up Procedure

To reconfigure the system clock source and clock source priority, run the SET CLKMODEcommand.

7.7 Configuring the TimeThis section describes how to configure the time of the BSC6900. You need to set the time zone,daylight saving time, and Simple Network Time Protocol (SNTP) synchronization server.


Procedure

Step 1 Run the SET TZ command to set the time zone and daylight saving time of the BSC6900.

Step 2 Run the ADD SNTPSRVINFO command to add the information about the SNTPsynchronization server.

Step 3 Run the SET SNTPCLTPARA command to set the synchronization period of the SNTP client.

----End

7.8 Configuring the IP Address of the EMS ServerThis section describes how to configure the IP address for the EMS server. The EMS server isused to perform OM on the base station through the BSC6900.

Procedure

Step 1 Run the ADD EMSIP command to add the IP address for the EMS server.

----End

7.9 Configuring BSC Custom AlarmThis section describes how to configure alarm ports, alarm IDs, and alarm names of the BSC.

Prerequisitel An environment monitoring unit and the sensor regarding environment alarms are installed.



17

l Data of the environment monitoring unit is configured. For details, see Configuring anEMU.

ContextEach environment alarm is allocated a unique alarm ID. The IDs of the BSC environment alarmsrange from 65334 to 65383.

Procedure

Step 1 Run the SET ALMPORT command to set the environment alarm input port of the BSC.

Step 2 Run the SET ENVALMPARA command. In this step, set Alarm ID, Alarm Name, AlarmSeverity, and Event Type.

----End



18

8 Configuring the Interfaces

About This Chapter

This chapter describes how to configure the UMTS interfaces, including the Iub, Iu-CS, Iu-PS,and Iur interfaces.

ContextFamiliarize yourself with 10.2 Data Configuration Principles for Transmission beforeperforming the operations described in this chapter.

8.1 Configuring the Iub Interface (over ATM)This section describes how to configure the transport network layer of the ATM-based Iubinterface between the BSC6900 and a NodeB.

8.2 Configuring the Iub Interface (over IP)This section describes how to configure the transport network layer of the IP-based Iub interfacebetween the BSC6900 and a NodeB.

8.3 Configuring the Iub Interface (over ATM and IP)This section describes how to configure the transport network layer of the Iub interface overATM/IP dual stack between the BSC6900 and a NodeB.

8.4 Configuring the Iu-CS Interface (over ATM)This section describes how to configure the transport network layer of the ATM-based Iu-CSinterface between the BSC6900 and the CS domain.

8.5 Configuring the Iu-CS Interface (over IP)This section describes how to configure the transport network layer of the IP-based Iu-CSinterface between the BSC6900 and the CS domain.

8.6 Configuring the Iu-PS Interface (over ATM)This section describes how to configure the transport network layer of the ATM-based Iu-PSinterface between the BSC6900 and the PS domain.

8.7 Configuring the Iu-PS Interface (over IP)This section describes how to configure the transport network layer of the IP-based Iu-PSinterface between the BSC6900 and the PS domain.

8.8 Configuring the Iur Interface (over ATM)

BSC6900 UMTSInitial Configuration Guide 8 Configuring the Interfaces


19

This section describes how to configure the transport network layer of the ATM-based Iurinterface between BSC6900s.

8.9 Configuring the Iur Interface (over IP)This section describes how to configure the transport network layer of the IP-based Iur interfacebetween BSC6900s.

8.10 Configuring the Iu-BC Interface (over ATM)This section describes how to configure the transport network layer of the ATM-based Iu-BCinterface on the BSC6900 side. Perform this task only when the BSC6900 is directly connectedto the CBC.

8.11 Configuring the Iu-BC Interface (over IP)This section describes how to configure the transport network layer data for the Iu-BC interfacebetween BSC6900 and the CBC. Perform this task only when the BSC6900 is directly connectedto the CBC.



20

8.1 Configuring the Iub Interface (over ATM)This section describes how to configure the transport network layer of the ATM-based Iubinterface between the BSC6900 and a NodeB.


ContextFamiliarize yourself with Interface Boards Applicable to Terrestrial Interfaces and DataConfiguration Principles for the Iub Interface (over ATM) before performing the operationsdescribed in this section. This task configures only the transport network layer of the Iubinterface. To enable cells under the NodeB to provide services, configure cell-related parameters.

8.1.1 Configuring the Physical Layer (over ATM)This section describes how to configure the physical layer of the interface on the BSC6900 sidein ATM transmission mode. Before the configuration, specify the type of interface boardaccording to network planning.

Different interface boards are recommended for different interfaces. For details, see InterfaceBoards Applicable to Terrestrial Interfaces.

Configuring the Physical Layer for the AEUa BoardThis section describes how to configure the physical layer for the AEUa board, which is usedas the interface board of the BSC6900.


ContextWhen the AEUa board is used as the interface board of the BSC6900, the E1/T1 link can carryonly one type of the following links: IMA link, UNI link, fractional IMA link, fractional ATMlink, and timeslot cross connection.

Procedure

Step 1 Set the E1/T1 link attributes.1. Run the LST E1T1 command to list the attributes of an E1/T1 link.2. Optional: If the planned data is inconsistent with the default data, run the SET E1T1

command to set the attributes of the E1/T1 link.

Step 2 Determine the type of link carried on the E1/T1 link.

If the E1/T1 link carries a/an ... Then...

IMA link Go to Step 3.



21


UNI link Go to Step 4.

Fractional IMA link Go to Step 5.

Fractional ATM link Go to Step 6.

Timeslot cross connection Go to Step 7.

Step 3 Add an IMA group and add IMA links to the IMA group. To add more IMA groups, performthis step repeatedly.1. Run the ADD IMAGRP command to add an IMA group. Set Board Type to AEUa.2. Run the ADD IMALNK command to add an IMA link to the IMA group. To add more

IMA links, run this command repeatedly. Now this task is complete.

Step 4 Run the ADD UNILNK command to add a UNI link. To add more UNI links, run this commandrepeatedly. Now this task is complete.

Step 5 To add a fractional IMA link, perform the following steps:1. Run the ADD IMAGRP command to add a fractional IMA group. Set Board Type to

AEUa.2. Run the ADD FRALNK command to add a fractional IMA link to the fractional IMA

group. To add more fractional IMA links, run this command repeatedly. Now this task iscomplete.

Step 6 Run the ADD FRALNK command to add a fractional ATM link. To add more fractional ATMlinks, run this command repeatedly. Now this task is complete.

Step 7 If the source and destination timeslots are not used, run the ADD TSCROSS command to adda timeslot cross connection. Now this task is complete.

----End

Configuring the Physical Layer for the AOUa/AOUc Board

This section describes how to configure the physical layer for the AOUa/AOUc board, which isused as the interface board of the BSC6900.


Contextl When the AOUa board is used as the interface board of the BSC6900, the E1/T1 link can

carry only the IMA link or UNI link.l When the AOUc board is used as the interface board of the BSC6900, the E1/T1 link can

carry only the IMA link, UNI link, Fractional IMA, or Fractional ATM.

Procedure

Step 1 Set the E1/T1 link attributes.1. Run the LST E1T1 command to list the attributes of an E1/T1 link.



22

2. Optional: If the planned data is inconsistent with the default data, run the SET E1T1command to set the attributes of the E1/T1 link.

Step 2 Set the optical port attributes.1. Run the LST OPT command to list the attributes of an optical port.2. Optional: If the planned data is inconsistent with the default data, run the SET OPT

command to set the attributes of the optical port.

Step 3 Optional: When the BSC6900 needs to interconnect with the equipment from another vendor,run the SET COPTLNK command to set the attributes of a channelized optical port on theinterface board.







Step 5 Add an IMA group and add IMA links to the IMA group. To add more IMA groups, performthe following operations repeatedly.1. Run the ADD IMAGRP command to add an IMA group.2. Run the ADD IMALNK command to add an IMA link to the IMA group. To add more

IMA links, repeat this command until all desired IMA links are added. Now this task iscomplete.

Step 6 Run the ADD UNILNK command to add a UNI link. To add more UNI links, repeat thiscommand until all desired UNI links are added. Now this task is complete.


AOUc.2. Run the ADD FRALNK command to add a fractional IMA link to the fractional IMA


Step 8 Run the ADD FRALNK command to add a fractional ATM link. To add more fractional ATMlinks, repeat this command until all desired fractional ATM links are added . Now this task iscomplete.

----End

Configuring the Physical Layer for the UOIa/UOIc Board

This section describes how to configure the physical layer for the UOIa/UOIc board, which isused as the interface board of the BSC6900.




23

Procedure



----End

8.1.2 Configuring the ATM Traffic ResourcesThis section describes how to configure the ATM traffic resources. You need to add the trafficrecord at the BSC6900 based on the traffic model of the link on each standard interface.


Procedure

Step 1 Run the ADD ATMTRF command to add an ATM traffic record. To add more ATM trafficrecords, run this command repeatedly.

----End

8.1.3 Configuring the Control Plane of the Iub Interface (over ATM)This section describes how to configure the control plane of the Iub interface on the BSC6900in ATM transmission mode. You need to configure the SAAL UNI link, basic data and algorithmparameters of the NodeB, adjacent node, NCP, and CCP.

Prerequisitel The physical layer of the ATM-based Iub interface is configured. For details, see

Configuring the Physical Layer (over ATM).l The ATM traffic resources are configured. For details, see Configuring the ATM Traffic

Resources.

Contextl The ATM-based Iub interface must be configured with at least three SAAL UNI links. One

is used to carry an NCP. At least one is used to carry a CCP. One is used to carry an ALCAP,that is, a Q.AAL2 signaling link.

l The SAAL UNI links used to carry the NCP, CCP, and ALCAP on the same Iub interfacemust be controlled by the same CPUS subsystem.

l Between a BSC6900 and a NodeB, only one NCP can be configured, but multiple CCPsare allowed.

Procedure

Step 1 Run the ADD SAALLNK command to add an SAAL link. Set Interface type to UNI. To addmore SAAL links, run this command repeatedly.



24

Step 2 Configure the NodeB on the BSC6900 side. For details, see Configuring a NodeB.

Step 3 Run the ADD ADJNODE command to add an adjacent node. In this step:l Set Adjacent Node Type to IUB.l Set Transport Type to ATM.

Step 4 Run the ADD UNCP command to add an NCP. Set Bearing link type to SAAL.

Step 5 Run the ADD UCCP command to add a CCP. Set Bearing link type to SAAL. To add moreCCPs, run this command repeatedly.

----End

8.1.4 Configuring the Mapping Between Service Types andTransmission Resources

This section describes how to configure the mapping between the service types and transmissionresources for the adjacent node. You can configure the TRM mapping table and activity factortable for users with different priorities.


Procedure

Step 1 Run the ADD TRMMAP command to add a TRM mapping table. To add more TRM mappingtables, run this command repeatedly.

Step 2 Run the ADD TRMFACTOR command to add an activity factor table.

Step 3 Optional: When the Iub interface is in ATM/IP dual-stack mode or hybrid IP mode, run theADD LOADEQ command to add a threshold table for load balancing between the primary andsecondary paths.

Step 4 Run the ADD ADJMAP command to configure the TRM mapping table and activity factor tablefor users with different priorities.

----End

8.1.5 Configuring the User Plane of the Iub Interface (over ATM)This section describes how to configure the user plane of the Iub interface on the BSC6900 inATM transmission mode. You need to configure the logical port, AAL2 path, and AAL2 route.

PrerequisiteThe control plane of the ATM-based Iub interface is configured. For details, see Configuringthe Control Plane of the Iub Interface (over ATM).

Procedure

Step 1 Optional: When the ATM traffic shaping and backpressure-based congestion control functionsare enabled, run the ADD ATMLOGICPORT command to add an ATM logical port.



25

Step 2 Run the ADD AAL2PATH command to add an AAL2 path. To add more AAL2 paths, repeatthis step until all desired AAL2 paths are added.

----End

8.1.6 Configuring the OM Channel over the Iub Interface (overATM)

This section describes how to configure the OM channel over the Iub interface on theBSC6900 side in ATM transmission mode. You need to configure the device IP address of aninterface board, the IPoA PVC between the BSC6900 and a NodeB, and the OM IP address ofthe NodeB.

Prerequisitel The IP address of the EMS server is configured. For details, see Configuring the IP Address

of the EMS Server.

l The control plane of the ATM-based Iub interface is configured. For details, seeConfiguring the Control Plane of the Iub Interface (over ATM).

l The user plane of the ATM-based Iub interface is configured. For details, see Configuringthe User Plane of the Iub Interface (over ATM).

Procedure

Step 1 Run the ADD DEVIP command to add the device IP address of the interface board.

Step 2 Run the ADD IPOAPVC command to add an IPoA PVC between the BSC6900 and the NodeB.Set Peer type to IUB.

Step 3 Run the ADD UNODEBIP command to add the OM IP address of the NodeB. Set NodeBTransType to ATMTRANS_IP.

----End

8.2 Configuring the Iub Interface (over IP)This section describes how to configure the transport network layer of the IP-based Iub interfacebetween the BSC6900 and a NodeB.


ContextFamiliarize yourself with Interface Boards Applicable to Terrestrial Interfaces and DataConfiguration Principles for the Iub Interface (over IP) before performing the operationsdescribed in this section. This task configures only the transport network layer on the Iubinterface. To enable the cells under the NodeB to provide services, you also need to set the cell-related parameters.



26

8.2.1 Configuring the Physical Layer and Data Link Layer (over IP)This section describes how to configure the physical layer and data link layer of the interfaceon the BSC6900 in IP transmission mode. Before the configuration, specify the type of interfaceboard according to network planning.


Configuring the Physical Layer and Data Link Layer for the FG2a/GOUa/FG2c/GOUc Board

This section describes how to configure the physical layer and data link layer for the FG2a/FG2c/GOUa/GOUc board, which is used as the interface board of the BSC6900. You need to set theEthernet port attributes, add the standby Ethernet port, add the IP address of the Ethernet port,add the link aggregation group, add the link to the link aggregation group, add the IP address ofthe link aggregation group, and add the device IP address.


Procedure

Step 1 Set the Ethernet port attributes.1. Run the LST ETHPORT command to list the attributes of the Ethernet port.2. Optional: If the planned data is inconsistent with the default data, run the SET

ETHPORT command to set the attributes of the Ethernet port.

Step 2 Optional: Run the ADD ETHREDPORT command to configure Ethernet port backup.

Step 3 Optional: Run the ADD DEVIP command to add the device IP address of the board in the caseof logical IP networking.

Step 4 Check whether the link aggregation function is required and then perform the correspondingstep.

If you select... Then...

Link non-aggregation mode Go to Step 5.

Link aggregation mode Go to Step 7.

Step 5 In link non-aggregation mode, run the ADD ETHIP command to add the IP address of theEthernet port. When multiple VLAN gateways are planned, repeat this step until all the IPaddresses are added.

Step 6 Optional: Run the ADD VLANID command to add an IP address to the VLAN ID mappingtable.

Step 7 In link aggregation mode, complete the following steps:1. Run the ADD ETHTRK command to add a link aggregation group.

NOTE

You can run the DSP ETHTRK command to query the status of a link aggregation group.



27

2. Run the ADD ETHTRKLNK command to add a link to the link aggregation group. Toadd more links to the link aggregation group, repeat this step until all desired links areadded.

NOTE

l You can run the DSP ETHTRKLNK command to query the status of a link in a link aggregationgroup and the related statistics.

l The links in a link aggregation group can be carried by non-adjacent ports.

l The port to which a link aggregation group is bound and a port on another board cannot work inactive/standby mode or load sharing mode.

l If a link in a link aggregation group becomes faulty, the system automatically removes this link.When this link becomes normal, the port carrying this link automatically negotiates with the peerend. If the negotiation is successful, the link is automatically added to the link aggregation group.

3. Run the ADD ETHTRKIP command to add the IP address of the link aggregation group.When multiple VLAN gateways are planned, repeat this step until all the IP addresses areadded.

----End

Configuring the Physical Layer and Data Link Layer for the PEUa Board

This section describes how to configure the physical layer and data link layer for the PEUa board,which is used as the interface board of the BSC6900. You need to set the E1/T1 attributes anddevice IP address, and configure the PPP link, MP link group, and MP link.


ContextThe MP link group is also referred to as PPP link group. Either a PPP link or an MP link groupmust be configured.

Procedure




Step 3 Determine the type of link carried on the E1/T1 link (PPP link or MP link group) and performthe corresponding step.

If the E1/T1 link carries a/an... Then...

PPP link Go to Step 4.

MP link group Go to Step 5.

Step 4 Configure a PPP link.



28

Run the ADD PPPLNK command to add a PPP link. To add more PPP links, run this commandrepeatedly. In this step:l Set Board type to PEUa.l Set Logic function type to IP.l It is recommended that Borrow DevIP be set to YES.

Step 5 Add an MP link group.1. Run the ADD MPGRP command to add an MP link group. In this step:

l Set Board type to PEUa.l Set Logic function type to IP.l It is recommended that Borrow DevIP be set to YES.

2. Run the ADD MPLNK command to add an MP link. To add more MP links, run thiscommand repeatedly. Set Board type to PEUa.

----End

Configuring the Physical Layer and Data Link Layer for the POUa/POUc BoardThis section describes how to configure the physical layer and data link layer for the POUa/POUc board, which is used as the interface board of the BSC6900. You need to set the E1/T1attributes, optical port attributes, and attributes of a channelized optical port. In addition, youneed to configure the PPP link, MP link group, and MP link.



Procedure










29




Step 6 Configure a PPP link.Run the ADD PPPLNK command to add a PPP link. To add more PPP links, run this commandrepeatedly. In this step:l Set Board type to POUa or POUc.l It is recommended that Borrow DevIP be set to YES.


l Set Board type to POUa or POUc.l It is recommended that Borrow DevIP be set to YES.

2. Run the ADD MPLNK command to add an MP link.

----End

Configuring the Physical Layer and Data Link Layer for the UOIa BoardThis section describes how to configure the physical layer and data link layer for the UOIa board,which is used as the interface board of the BSC6900.


Procedure




Step 3 Run the ADD PPPLNK command to add a PPP link. To add more PPP links, run this commandrepeatedly.In this step:l Set Board type to UOIa.l It is recommended that Borrow DevIP be set to YES.

----End

8.2.2 Configuring the Control Plane for the Iub Interface (over IP)This section describes how to configure the control plane of the Iub interface on the BSC6900in IP transmission mode. You need to configure the SCTP link, basic data of the NodeB,algorithm parameters of the NodeB, adjacent node, and Iub interface.



30

PrerequisiteThe physical layer and data link layer of the IP-based Iub interface are configured. For details,see Configuring the Physical Layer and Data Link Layer (over IP).

Contextl The IP-based Iub interface must be configured with at least two SCTP links. One is used

to carry an NCP link and the other is used to carry a CCP link. The number of SCTP linksshould increase with the number of CCP links.

l If the Iub interface supports hybrid IP transport, the IP transport over Ethernet and overE1/T1 share the control plane. Therefore, you need to configure the control plane of theIub interface only once.

Procedure

Step 1 Run the ADD SCTPLNK command to add an SCTP link. To add more SCTP links, repeat thisstep until all desired SCTP links are added. In this step:

l Set Signalling link model to SERVER.

l Set Application type to NBAP.

Step 2 Optional: Run the ADD IPRT command to add an IP route when the layer 3 networking modeis used between the BSC6900 and the NodeB. To add more IP routes, repeat this step until alldesired IP routes are added.

Step 3 Configure the NodeB on the BSC6900 side. For details, see Configuring a NodeB.

Step 4 Run the ADD ADJNODE command to add an adjacent node. In this step:

l Set Adjacent Node Type to IUB.

l Set Transport Type to IP.

Step 5 Run the ADD UNCP command to add an NCP link. In this step, set Bearing link type toSCTP.

Step 6 Run the ADD UCCP command to add a CCP link. In this step, set Bearing link type toSCTP. To add more CCP links, repeat this step until all desired CCP links are added.

----End






31

Procedure



Step 3 Optional: When the Iub interface is in ATM/IP dual-stack mode or hybrid IP mode, run theADD LOADEQ command to add a threshold table for load balancing between the primary andsecondary paths.


----End

8.2.4 Configuring the User Plane over the Iub Interface (over IP)This section describes how to configure the user plane of the Iub interface on the BSC6900 inIP transmission mode. You need to configure the logical port, IP path, and IP route.

PrerequisiteThe control plane of the IP-based Iub interface is configured. For details, see Configuring theControl Plane of the Iub Interface (over IP).

Procedure

Step 1 Optional: When the RAN sharing function is used, run the ADD IPLOGICPORT commandto add a logical port.

Step 2 Run the ADD IPPATH command to add an IP path. To add more IP paths, run this commandrepeatedly.

Step 3 Optional: Run the ADD IPRT command to add an IP route when the layer 3 networking modeis used between the BSC6900 and the NodeB. To add more IP routes, run this commandrepeatedly.

Step 4 Optional: Run the LST GLOBALROUTESW command to query the value of the global routemanagement switch. If the global route management function is not required but the global routemanagement switch is set to ON, run the SET GLOBALROUTESW command to set the globalroute management switch to OFF.

----End

8.2.5 Configuring an OM Channel over Iub Interface (over IP)This section describes how to configure the OM channel over the Iub interface on theBSC6900 in IP transmission mode. You need to configure the OM IP address for the NodeB,electrical serial number (ESN), and detection function.

PrerequisiteThe control plane of the IP-based Iub interface is configured. For details, see Configuring theControl Plane of the Iub Interface (over IP).



32

Contextl Dynamic Host Configuration Protocol (DHCP) is a client-server networking protocol. A

DHCP server provides configuration parameters specific to the request of the DHCP clienthost, such as, information required by the host to access the Internet. DHCP also providesa mechanism for allocating addresses to hosts.

l This function enables the NodeB to know the VLAN ID broadcast by the BSC6900 on thenetwork when the NodeB starts operating or becomes faulty. As a result, the NodeB canstart normally and local maintenance is not required.

Procedure

Step 1 Run the ADD UNODEBIP command to add the OM IP address of the NodeB.

Step 2 If the peer NodeB uses the DHCP, perform the following steps:

1. Run the ADD UNODEBESN command to add the ESN of the NodeB.

2. Optional: When the VLAN is configured in the transport networking between theBSC6900 and the NodeB, run the STR UNODEBDETECT command to start the NodeBdetection function.

----End

8.3 Configuring the Iub Interface (over ATM and IP)This section describes how to configure the transport network layer of the Iub interface overATM/IP dual stack between the BSC6900 and a NodeB.


Contextl Perform this task for each Iub interface over ATM/IP dual stack.

l Familiarize yourself with Interface Boards Applicable to Terrestrial Interfaces and DataConfiguration Principles for the Iub Interface (over ATM and IP) before performing theoperations described in this section. This task configures only the transport network layeron the Iub interface. To enable the cells under the NodeB to provide services, you also needto set the cell-related parameters.

l All the data of a NodeB, including data associated with cells and links, should be controlledby one CPUS subsystem.

Procedure

Step 1 Configure the physical layer and ATM traffic resources in ATM transmission mode.

1. Configure the physical layer in ATM transmission mode. For details, see Configuring thePhysical Layer (over ATM).

2. Configure the ATM traffic resources. For details, see Configuring the ATM TrafficResources.



33

Step 2 Configure the physical layer and the data link layer in IP transmission mode. For details, seeConfiguring the Physical Layer and Data Link Layer (over IP).

Step 3 Configure the control plane.

l If ATM transport is applied to the control plane, see Configuring the Control Plane of theIub Interface (over ATM).

l If IP transport is applied to the control plane, see Configuring the Control Plane of the IubInterface (over IP).

Step 4 Configure the TRM mapping for the adjacent nodes. For details, see Configuring the MappingBetween Service Types and Transmission Resources.

Step 5 Configure the user plane.

l If ATM transport is applied to the user plane, see Configuring the User Plane of the IubInterface (over ATM).

l If IP transport is applied to the user plane, see Configuring the User Plane of the Iub Interface(over IP).

Step 6 Configure the OM channel.

l If both ATM transport and IP transport are applied to the OM channel, perform the followingsteps:

– Run the ADD DEVIP and ADD IPOAPVC commands to set up an IPoA PVC, whichis used as the OM channel between the BSC6900 and the NodeB.

– Run the ADD UNODEBIP command to add the OM IP address for the NodeB in ATM/IP dual stack mode.

l If ATM transport is applied to the OM channel, see Configuring the OM Channel over theIub Interface (over ATM).

l If IP transport is applied to the OM channel, see Configuring the OM Channel over the IubInterface (over IP).

----End

8.4 Configuring the Iu-CS Interface (over ATM)This section describes how to configure the transport network layer of the ATM-based Iu-CSinterface between the BSC6900 and the CS domain.


Contextl When the BSC6900 in ATM transmission mode is connected to multiple CS CN nodes,

configure an Iu-CS interface between each CS CN node and the BSC6900.

l Familiarize yourself with Interface Boards Applicable to Terrestrial Interfaces and DataConfiguration Principles for the Iu-CS Interface (over ATM) before performing theoperations described in this section. This task configures only the transport network layerof the ATM-based Iu-CS interface.



34



Configuring the Physical Layer for the AEUa Board

This section describes how to configure the physical layer for the AEUa board, which is usedas the interface board of the BSC6900.



Procedure













Step 5 To add a fractional IMA link, perform the following steps:



35

1. Run the ADD IMAGRP command to add a fractional IMA group. Set Board Type toAEUa.

2. Run the ADD FRALNK command to add a fractional IMA link to the fractional IMAgroup. To add more fractional IMA links, run this command repeatedly. Now this task iscomplete.



----End

Configuring the Physical Layer for the AOUa/AOUc BoardThis section describes how to configure the physical layer for the AOUa/AOUc board, which isused as the interface board of the BSC6900.





Procedure













36










----End

Configuring the Physical Layer for the UOIa/UOIc BoardThis section describes how to configure the physical layer for the UOIa/UOIc board, which isused as the interface board of the BSC6900.


Procedure



----End

8.4.2 Configuring the Traffic Resource at the ATM LayerThis section describes how to configure the ATM traffic resources. You need to add the trafficrecord at the BSC6900 based on the traffic model of the link on each standard interface.




37

Procedure


----End

8.4.3 Configuring the Control Plane over the Iu-CS Interface (overATM)

This section describes how to configure the control plane of the Iu-CS interface on theBSC6900 in ATM transmission mode. You need to configure the SAAL link, MTP3 data,adjacent node, and CN node.

Prerequisitel The OPC and DPC are configured. For details, see Configuring the OPC and DPC.

l The physical layer of the ATM-based Iu-CS interface is configured. For details, seeConfiguring the Physical Layer (over ATM).

l The ATM traffic resources are configured. For details, see Configuring the ATM TrafficResources.

Procedure

Step 1 Run the ADD SAALLNK command to add an SAAL link. Set Interface type to NNI. To addmore SAAL links, run this command repeatedly.

Step 2 Run the ADD MTP3LKS command to add an MTP3 link set.

Step 3 Run the ADD MTP3RT command to add an MTP3 route. To add more MTP3 routes, run thiscommand repeatedly.

Step 4 Run the ADD MTP3LNK command to add an MTP3 link. To add more MTP3 links, run thiscommand repeatedly.

Step 5 Run the ADD ADJNODE command to add an adjacent node and set the appropriate TRMmapping table and activity factor table for users with different priorities. In this step:

l Set Adjacent Node Type to IUCS.

l Set Transport Type to ATM.

Step 6 Run the ADD UCNDOMAIN command to add a CN domain. Set CN domain ID toCS_DOMAIN.

Step 7 Run the ADD UCNNODE command to add a CN node. In this step:

l Set CN domain ID to CS_DOMAIN.

l Set Iu transfers bearer type to ATM_TRANS.

----End



38




Procedure




----End

8.4.5 Configuring the User Plane over the Iu-CS Interface (overATM)

This section describes how to configure the user plane of the Iu-CS interface on the BSC6900in ATM transmission mode. You need to configure the AAL2 path and AAL2 route.

PrerequisiteThe control plane of the ATM-based Iu-CS interface is configured. For details, see Configuringthe Control Plane of the Iu-CS Interface (over ATM).

Procedure


Step 2 Run the ADD AAL2RT command to add an AAL2 route. In this step, set Destination ATMaddress to the ATM address of the MGW. To add more AAL2 routes, repeat this step until alldesired AAL2 routes are added.

----End

8.5 Configuring the Iu-CS Interface (over IP)This section describes how to configure the transport network layer of the IP-based Iu-CSinterface between the BSC6900 and the CS domain.

PrerequisiteThe OPC is configured. For details, see Configuring the OPC and DPC.



39

Contextl When the BSC6900 in IP transmission mode is connected to multiple CS CN nodes,

configure an Iu-CS interface between each CS CN node and the BSC6900.l Familiarize yourself with Interface Boards Applicable to Terrestrial Interfaces and Data

Configuration Principles for the Iu-CS Interface (over IP) before performing the operationsdescribed in this section. This task configures only the transport network layer of the IP-based Iu-CS interface.

8.5.1 Configuring the Physical Layer and Data Link Layer over IPThis section describes how to configure the physical layer and data link layer of the interfaceon the BSC6900 in IP transmission mode. Before the configuration, specify the type of interfaceboard according to network planning.





Procedure












40



NOTE



NOTE






----End

Configuring the Physical Layer and Data Link Layer for the PEUa BoardThis section describes how to configure the physical layer and data link layer for the PEUa board,which is used as the interface board of the BSC6900. You need to set the E1/T1 attributes anddevice IP address, and configure the PPP link, MP link group, and MP link.



Procedure







41




Step 4 Configure a PPP link.Run the ADD PPPLNK command to add a PPP link. To add more PPP links, run this commandrepeatedly. In this step:l Set Board type to PEUa.l Set Logic function type to IP.l It is recommended that Borrow DevIP be set to YES.




----End

Configuring the Physical Layer and Data Link Layer for the POUa/POUc Board

This section describes how to configure the physical layer and data link layer for the POUa/POUc board, which is used as the interface board of the BSC6900. You need to set the E1/T1attributes, optical port attributes, and attributes of a channelized optical port. In addition, youneed to configure the PPP link, MP link group, and MP link.



Procedure







42











----End



ProcedureStep 1 Set the optical port attributes.

1. Run the LST OPT command to list the attributes of an optical port.2. Optional: If the planned data is inconsistent with the default data, run the SET OPT




----End



43

8.5.2 Configuring the Control Plane over the Iu-CS Interface (overIP)

This section describes how to configure the control plane of the Iu-CS interface on theBSC6900 in IP transmission mode. You need to configure the SCTP link, M3UA data, adjacentnode, CN domain, and CN node.

Prerequisitel The OPC and DPC are configured. For details, see Configuring the OPC and DPC.l The M3UA local and destination entities are configured. For details, see Configuring the

M3UA Local and Destination Entities.l The physical layer and data link layer of the IP-based Iu-CS interface are configured. For

details, see Configuring the Physical Layer and Data Link Layer (over IP).

Procedure

Step 1 Run the ADD SCTPLNK command to add an SCTP link. To add more SCTP links, repeat thisstep until all desired SCTP links are added. In this step:l Set Signalling link model to CLIENT.l Set Application type to M3UA.

Step 2 Run the ADD M3LKS command to add an M3UA link set. In this step:l When Local entity type is set to M3UA_IPSP, Work mode of the M3UA link set must be

set to M3UA_IPSP.l When Local entity type is set to M3UA_ASP and Destination entity type is set to

M3UA_SP, Work mode of the M3UA link set must be set to M3UA_IPSP. When Localentity type is set to M3UA_ASP and Destination entity type is not set to M3UA_SP, Workmode of the M3UA link set must be set to M3UA_ASP.

NOTEYou can set Local entity type by running the ADD M3LE command and set Destination entity type by runningthe ADD M3DE command.

Step 3 Run the ADD M3RT command to add an M3UA route.

Step 4 Run the ADD M3LNK command to add an M3UA link. To add more M3UA links, repeat thisstep until all desired M3UA links are added.

Step 5 Optional: Run the ADD IPRT command to add an IP route when the layer 3 networking modeis used between the BSC6900 and the CS domain. To add more IP routes, repeat this step untilall desired IP routes are added.

Step 6 Run the ADD ADJNODE command to add an adjacent node and set the appropriate TRMmapping table and activity factor table for users with different priorities. In this step:l Set Adjacent Node Type to IUCS.l Set Transport Type to IP.

Step 7 Run the ADD UCNDOMAIN command to add a CN domain. Set CN domain ID toCS_DOMAIN.

Step 8 Run the ADD UCNNODE command to add a CN node. In this step:l Set CN domain ID to CS_DOMAIN.



44

l Set IU trans bearer type to IP_TRANS.

----End




Procedure




----End

8.5.4 Configuring the User Plane over the Iu-CS Interface (over IP)This section describes how to configure the user plane of the IP-based Iu-CS interface on theBSC6900 side. You need to configure the IP path and IP route.

PrerequisiteThe control plane is configured over the IP-based Iu-CS interface. For details, see Configuringthe Control Plane of the Iu-CS Interface (over IP).

Procedure

Step 1 Run the ADD IPPATH command to add an IP path. It is recommended that Peer subnetmask be set to 255.255.255.0. To add more IP paths, repeat this step until all desired IP pathsare added.

Step 2 Optional: Run the ADD IPRT command to add an IP route when the layer 3 networking modeis used between the BSC6900 and the CS domain. To add more IP routes, repeat this step untilall desired IP routes are added.


----End



45

8.6 Configuring the Iu-PS Interface (over ATM)This section describes how to configure the transport network layer of the ATM-based Iu-PSinterface between the BSC6900 and the PS domain.


Contextl When the BSC6900 in ATM transmission mode is connected to multiple PS CN nodes,

configure an Iu-PS interface between each PS CN node and the BSC6900.l Familiarize yourself with Interface Boards Applicable to Terrestrial Interfaces and Data

Configuration Principles for the Iu-PS Interface (over ATM) before performing theoperations described in this section. This task configures only the transport network layerof the ATM-based Iu-PS interface.

8.6.1 Configuring the Physical Layer for the UOIa/UOIc BoardThis section describes how to configure the physical layer for the UOIa/UOIc board, which isused as the interface board of the BSC6900.


Procedure



----End



Procedure


----End



46

8.6.3 Configuring the Control Plane over the Iu-PS Interface (overATM)

This section describes how to configure the control plane of the Iu-PS interface on theBSC6900 in ATM transmission mode. You need to configure the SAAL link, MTP3 data,adjacent node, and CN node.

Prerequisitel The OPC and DPC are configured. For details, see Configuring the OPC and DPC.l The physical layer of the ATM-based Iu-PS interface is configured. For details, see

Configuring the Physical Layer (over ATM).l The ATM traffic resources are configured. For details, see Configuring the ATM Traffic

Resources.

Procedure

Step 1 Run the ADD SAALLNK command to add an SAAL link. In this step, set Interface type toNNI. To add more SAAL links, repeat this step until all desired SAAL links are added.

Step 2 Run the ADD MTP3LKS command to add an MTP3 signaling link set.

NOTEWhen two MGWs are configured, set Signalling link mask to B1110.

Step 3 Run the ADD MTP3RT command to add an MTP3 route. To add more MTP3 routes, repeatthis step until all desired MTP3 routes are added.

Step 4 Run the ADD MTP3LNK command to add an MTP3 link. To add more MTP3 links, repeatthis step until all desired MTP3 links are added.

Step 5 Run the ADD ADJNODE command to add an adjacent node and set the appropriate TRMmapping table and activity factor table for users with different priorities. In this step:l Set Adjacent Node Type to IUPS.l Set Transport Type to ATM.

Step 6 Run the ADD UCNDOMAIN command to add a CN domain. In this step, set CN domain IDto PS_DOMAIN.

Step 7 Run the ADD UCNNODE command to add a CN node. In this step, set CN domain ID toPS_DOMAIN.

----End






47

Procedure




----End

8.6.5 Configuring the User Plane over the Iu-PS Interface (overATM)

This section describes how to configure the user plane of the ATM-based Iu-PS interface on theBSC6900 side. You need to configure the device IP address, IPoA PVC, IP path, and IP route.

PrerequisiteThe control plane is configured over the ATM-based Iu-PS interface. For details, see Configuringthe Control Plane of the Iu-PS Interface (over ATM).

Procedure

Step 1 Run the ADD DEVIP command to add the device IP address for the interface board that carriesthe user plane data.

Step 2 Run the ADD IPOAPVC command to add an IPoA PVC. In this step:

l Set Bearing type to NCOPT.

l Set Peer type to IUPS.

Step 3 Run the ADD IPPATH command to add an IP path. It is recommended that Peer subnetmask be set to 255.255.255.0. To add more IP paths, run this command repeatedly.

CAUTIONWhen the IP path is carried on the IPoA PVC, the bandwidth of the IP path cannot be higherthan the physical bandwidth of the IPoA PVC.

Step 4 Optional: Run the ADD IPRT command to add an IP route when the layer 3 networking modeis used between the BSC6900 and the PS domain. To add more IP routes, run this commandrepeatedly.

----End

8.7 Configuring the Iu-PS Interface (over IP)This section describes how to configure the transport network layer of the IP-based Iu-PSinterface between the BSC6900 and the PS domain.



48

Prerequisitel A license for implementing IP transmission over the Iu interface has been obtained.l The basic data of the BSC6900 is configured. For details, see Configuring the Basic Data.

Contextl When the BSC6900 in IP transmission mode is connected to multiple PS CN nodes,

configure an Iu-PS interface between each PS CN node and the BSC6900.l Familiarize yourself with Interface Boards Applicable to Terrestrial Interfaces and Data

Configuration Principles for the Iu-PS Interface (over IP) before performing the operationsdescribed in this section. This task configures only the transport network layer of the IP-based Iu-PS interface.






Procedure










49






NOTE



NOTE






----End




Procedure




50











----End

Configuring the Physical Layer and Data Link Layer for the POUa/POUc BoardThis section describes how to configure the physical layer and data link layer for the POUa/POUc board, which is used as the interface board of the BSC6900. You need to set the E1/T1attributes, optical port attributes, and attributes of a channelized optical port. In addition, youneed to configure the PPP link, MP link group, and MP link.



Procedure




51














----End



Procedure





52



----End

8.7.2 Configuring the Control Plane over the Iu-PS Interface (overIP)

This section describes how to configure the control plane of the Iu-PS interface on theBSC6900 in IP transmission mode. You need to configure the SCTP link, M3UA data, adjacentnode, CN domain, and CN node.

Prerequisitel The OPC and DPC are configured. For details, see Configuring the OPC and DPC.l The M3A local and destination entities are configured. For details, see Configuring the

M3UA Local and Destination Entities.l The physical layer and data link layer of the IP-based Iu-PS interface are configured. For

details, see Configuring the Physical Layer and Data Link Layer (over IP).

ProcedureStep 1 Run the ADD SCTPLNK command to add an SCTP link. To add more SCTP links, repeat this

step until all desired SCTP links are added. In this step:l Set Signalling link model to CLIENT.l Set Application type to M3UA.



M3UA_SP, Work mode of the M3UA link set must be set to M3UA_IPSP. When Localentity type is set to M3UA_ASP and Destination entity type is not set to M3UA_SP, Workmode of the M3UA link set must be set to M3UA_ASP.NOTE

You can set Local entity type by running the ADD M3LE command and set Destination entity type by runningthe ADD M3DE command.


Step 4 Run the ADD M3LNK command to add an M3UA link.

Step 5 Optional: Run the ADD IPRT command to add an IP route when the layer 3 networking modeis used between the BSC6900 and the PS domain. To add more IP routes, repeat this step untilall desired IP routes are added.

Step 6 Run the ADD ADJNODE command to add an adjacent node and set the appropriate TRMmapping table and activity factor table for users with different priorities. In this step:



53

l Set Adjacent Node Type to IUPS.

l Set Transport Type to IP.

Step 7 Run the ADD UCNDOMAIN command to add a CN domain. In this step, set CN domain IDto PS_DOMAIN.

Step 8 Run the ADD UCNNODE command to add a CN node. In this step, set CN domain ID toPS_DOMAIN.

----End




Procedure




----End

8.7.4 Configuring the User Plane over the Iu-PS Interface (over IP)This section describes how to configure the user plane of the IP-based Iu-PS interface on theBSC6900 side. You need to configure the IP path and IP route.

PrerequisiteThe control plane is configured over the IP-based Iu-PS interface. For details, see Configuringthe Control Plane of the Iu-PS Interface (over IP).

Procedure

Step 1 Run the ADD IPPATH command to add an IP path. It is recommended that Peer subnetmask be set to 255.255.255.0. Peer IP address is set to the IP address of the SGSN. To addmore IP paths, repeat this step until all desired IP paths are added.

NOTE

When the one tunnel function is enabled, Peer IP address is set to the IP address of the GGSN.



54

Step 2 Optional: Run the ADD IPRT command to add an IP route when the layer 3 networking modeis used between the BSC6900 and the PS domain. To add more IP routes, repeat this step untilall desired IP routes are added.


----End

8.8 Configuring the Iur Interface (over ATM)This section describes how to configure the transport network layer of the ATM-based Iurinterface between BSC6900s.


Contextl When the local BSC6900 is connected to multiple neighboring BSC6900s, configure an

ATM-based Iur interface between the local BSC6900 and each neighboring BSC6900.

l Familiarize yourself with Interface Boards Applicable to Terrestrial Interfaces and DataConfiguration Principles for the Iur Interface (over ATM) before performing the operationsdescribed in this section. This task configures only the transport network layer of the ATM-based Iur interface.









55

Procedure

Step 1 Set the E1/T1 link attributes.

1. Run the LST E1T1 command to list the attributes of an E1/T1 link.









Step 3 Add an IMA group and add IMA links to the IMA group. To add more IMA groups, performthis step repeatedly.

1. Run the ADD IMAGRP command to add an IMA group. Set Board Type to AEUa.

2. Run the ADD IMALNK command to add an IMA link to the IMA group. To add moreIMA links, run this command repeatedly. Now this task is complete.



1. Run the ADD IMAGRP command to add a fractional IMA group. Set Board Type toAEUa.




----End

Configuring the Physical Layer for the AOUa/AOUc Board

This section describes how to configure the physical layer for the AOUa/AOUc board, which isused as the interface board of the BSC6900.




56


carry only the IMA link or UNI link.

l When the AOUc board is used as the interface board of the BSC6900, the E1/T1 link cancarry only the IMA link, UNI link, Fractional IMA, or Fractional ATM.

Procedure




Step 2 Set the optical port attributes.

1. Run the LST OPT command to list the attributes of an optical port.

2. Optional: If the planned data is inconsistent with the default data, run the SET OPTcommand to set the attributes of the optical port.








Step 5 Add an IMA group and add IMA links to the IMA group. To add more IMA groups, performthe following operations repeatedly.

1. Run the ADD IMAGRP command to add an IMA group.

2. Run the ADD IMALNK command to add an IMA link to the IMA group. To add moreIMA links, repeat this command until all desired IMA links are added. Now this task iscomplete.



1. Run the ADD IMAGRP command to add a fractional IMA group. Set Board Type toAOUc.




57


----End



Procedure



----End



Procedure


----End

8.8.3 Configuring the Control Plane over the Iur Interface (overATM)

This section describes how to configure the control plane of the ATM-based Iur interface. Youneed to configure the SAAL link, basic data of the neighboring BSC6900, MTP3 data, andadjacent node.

Prerequisitel The OPC and DPC are configured. For details, see Configuring the OPC and DPC.l The physical layer of the ATM-based Iur interface is configured. For details, see

Configuring the Physical Layer (over ATM).



58

l The ATM traffic resources are configured. For details, see Configuring the ATM TrafficResources.

Procedure

Step 1 Run the ADD SAALLNK command to add an SAAL link. Set Interface type to NNI. To addmore SAAL links, run this command repeatedly.

Step 2 Run the ADD UNRNC command to add the basic data of the neighboring BSC6900. Toconfigure more neighboring BSC6900s, run this command repeatedly. In this step::l Set IUR Interface Existing Indication to TRUE.l Set IUR trans bearer type to ATM_TRANS.

Step 3 Run the ADD MTP3LKS command to add an MTP3 link set.

Step 4 Run the ADD MTP3RT command to add an MTP3 route. To add more MTP3 routes, run thiscommand repeatedly.

Step 5 Run the ADD MTP3LNK command to add an MTP3 link. To add more MTP3 links, run thiscommand repeatedly.

Step 6 Run the ADD ADJNODE command to add an adjacent node and set the appropriate TRMmapping table and activity factor table for users with different priorities. In this step:l Set Adjacent Node Type to IUR.l Set Transport Type to ATM.

----End




Procedure




----End

8.8.5 Configuring the User Plane over the Iur Interface (over ATM)This section describes how to configure the user plane of the Iur interface on the BSC6900 inATM transmission mode.



59

PrerequisiteThe control plane is configured over the ATM-based Iur interface. For details, see Configuringthe Control Plane of the Iur Interface (over ATM).

Procedure


----End

8.8.6 Configuring a Static Transfer PathThis section describes how to configure a path for SRNC relocation. To reduce the bandwidthoccupied by the Iur interface and the transmission delay on the user plane, static SRNC relocationcan be performed.

PrerequisiteThe IP path on the Iu-PS user plane is configured. For details, see Configuring the User Planeof the Iu-PS Interface (over ATM) or Configuring the User Plane of the Iu-PS Interface (overIP).

Procedure

Step 1 Run the ADD IPRT command to add an IP route to the DRNC. In this step:

l Set Destination IP address to the user plane IP address of the DRNC.

l Set Forward route address to the IP address of the gateway between the DRNC and theSGSN.

Step 2 Run the ADD IPPATH command to add an IP path for static SRNC relocation. In this step:

l Set Adjacent node ID to the adjacent node ID of the SGSN.

l Set Local IP address to the Iu-PS user plane IP address of the SRNC.

l Set Peer IP address to the Iu-PS user plane IP address of the DRNC.

l Set Peer subnet mask to the subnet mask of the Iu-PS user plane IP address of the DRNC.The recommended value is 255.255.255.0.

CAUTIONFor each IP interface board configured with Iu-PS user plane data, it is recommended that theboard be configured with an IP route and IP path towards the DRNC. If multiple destination IPnetwork segments exist at the DRNC, it is recommended that each IP interface board beconfigured with IP routes and IP paths towards each of the network segments. This facilitatesload sharing over the Iu-PS and Iur interfaces.

----End



60

8.9 Configuring the Iur Interface (over IP)This section describes how to configure the transport network layer of the IP-based Iur interfacebetween BSC6900s.


Contextl When the local BSC6900 is connected to multiple neighboring BSC6900s, configure an

IP-based Iur interface between the local BSC6900 and each neighboring BSC6900.l Familiarize yourself with Interface Boards Applicable to Terrestrial Interfaces and Data

Configuration Principles for the Iur Interface (over IP) before performing the operationsdescribed in this section. This task configures only the transport network layer of the IP-based Iur interface.






Procedure







61








NOTE



NOTE






----End

Configuring the Physical Layer and Data Link Layer for the PEUa Board

This section describes how to configure the physical layer and data link layer for the PEUa board,which is used as the interface board of the BSC6900. You need to set the E1/T1 attributes anddevice IP address, and configure the PPP link, MP link group, and MP link.





62

Procedure








Step 4 Configure a PPP link.Run the ADD PPPLNK command to add a PPP link. To add more PPP links, run this commandrepeatedly. In this step:

l Set Board type to PEUa.

l Set Logic function type to IP.

l It is recommended that Borrow DevIP be set to YES.


l Set Board type to PEUa.

l Set Logic function type to IP.

l It is recommended that Borrow DevIP be set to YES.2. Run the ADD MPLNK command to add an MP link. To add more MP links, run this

command repeatedly. Set Board type to PEUa.

----End







63

Procedure















----End



Procedure

Step 1 Set the optical port attributes.



64

1. Run the LST OPT command to list the attributes of an optical port.2. Optional: If the planned data is inconsistent with the default data, run the SET OPT




----End

8.9.2 Configuring the Control Plane over the Iur Interface (over IP)This section describes how to configure the control plane of the Iur interface on the BSC6900in IP transmission mode. You need to configure the SCTP link, basic data of the neighboringBSC6900, M3UA data, and adjacent node.

Prerequisitel The OPC and DPC are configured. For details, see Configuring the OPC and DPC.l The M3UA local and destination entities are configured. For details, see Configuring the

M3UA Local and Destination Entities.l The data link layer of the IP-based Iur interface is configured. For details, see Configuring

the Physical Layer and Data Link Layer (over IP).

Procedure

Step 1 Run the ADD SCTPLNK command to add an SCTP link. To add more SCTP links, repeat thisstep until all desired SCTP links are added. In this step:l Set Signalling link model to CLIENT.l Set Application type to M3UA.

Step 2 Run the ADD UNRNC command to add the basic data of the neighboring BSC6900. In thisstep:l Set Iur Interface Existing Indication to TRUE.l Set IUR trans bearer type to IP_TRANS.



M3UA_SP, Work mode of the M3UA link set must be set to M3UA_IPSP. When Localentity type is set to M3UA_ASP and Destination entity type is not set to M3UA_SP, Workmode of the M3UA link set must be set to M3UA_ASP.

NOTEYou can set Local entity type by running the ADD M3LE command and set Destination entity type by runningthe ADD M3DE command.



65


Step 5 Run the ADD M3LNK command to add an M3UA link. To add more M3UA links, repeat thisstep until all desired M3UA links are added.

Step 6 Optional: Run the ADD IPRT command to add an IP route when the layer 3 networking modeis used between BSC6900s. To add more IP routes, repeat this step until all desired IP routesare added.

Step 7 Run the ADD ADJNODE command to add an adjacent node and set the appropriate TRMmapping table and activity factor table for users with different priorities. In this step:l Set Adjacent Node Type to IUR.l Set Transport Type to IP.

----End




Procedure




----End

8.9.4 Configuring the User Plane over the Iur Interface (over IP)This section describes how to configure the user plane of the IP-based Iur interface on theBSC6900 side. You need to configure the IP path and IP route.

PrerequisiteThe control plane is configured over the IP-based Iur interface. For details, see Configuring theControl Plane of the Iur Interface (over IP).

Procedure

Step 1 Run the ADD IPPATH command to add an IP path. It is recommended that Peer subnetmask be set to 255.255.255.0. To add more IP paths, repeat this step until all desired IP pathsare added.



66

Step 2 Optional: Run the ADD IPRT command to add an IP route when the layer 3 networking modeis used between BSC6900s. To add more IP routes, repeat this step until all desired IP routesare added.


----End

8.9.5 Configuring a Static Drift PathThis section describes how to configure a path for SRNC relocation. To reduce the bandwidthoccupied by the Iur interface and the transmission delay on the user plane, static SRNC relocationcan be performed.

PrerequisiteThe IP path on the Iu-PS user plane is configured. For details, see Configuring the User Planeof the Iu-PS Interface (over ATM) or Configuring the User Plane of the Iu-PS Interface (overIP).

Procedure

Step 1 Run the ADD IPRT command to add an IP route to the DRNC. In this step:

l Set Destination IP address to the user plane IP address of the DRNC.

l Set Forward route address to the IP address of the gateway between the DRNC and theSGSN.

Step 2 Run the ADD IPPATH command to add an IP path for static SRNC relocation. In this step:

l Set Adjacent node ID to the adjacent node ID of the SGSN.

l Set Local IP address to the Iu-PS user plane IP address of the SRNC.

l Set Peer IP address to the Iu-PS user plane IP address of the DRNC.

l Set Peer subnet mask to the subnet mask of the Iu-PS user plane IP address of the DRNC.The recommended value is 255.255.255.0.

CAUTIONFor each IP interface board configured with Iu-PS user plane data, it is recommended that theboard be configured with an IP route and IP path towards the DRNC. If multiple destination IPnetwork segments exist at the DRNC, it is recommended that each IP interface board beconfigured with IP routes and IP paths towards each of the network segments. This facilitatesload sharing over the Iu-PS and Iur interfaces.

----End



67

8.10 Configuring the Iu-BC Interface (over ATM)This section describes how to configure the transport network layer of the ATM-based Iu-BCinterface on the BSC6900 side. Perform this task only when the BSC6900 is directly connectedto the CBC.


ContextFamiliarize yourself with Interface Boards Applicable to Terrestrial Interfaces and DataConfiguration Principles for the Iu-BC Interface (over ATM) before performing the operationsdescribed in this section. This task configures only the transport network layer of the Iu-BCinterface. To enable the BSC6900 to provide the Cell Broadcast Service (CBS), you also needto configure CBS data. For details, see the RAN Feature Description.







Procedure







68











AEUa.2. Run the ADD FRALNK command to add a fractional IMA link to the fractional IMA




----End

Configuring the Physical Layer for the AOUa/AOUc BoardThis section describes how to configure the physical layer for the AOUa/AOUc board, which isused as the interface board of the BSC6900.





Procedure




69

1. Run the LST E1T1 command to list the attributes of an E1/T1 link.2. Optional: If the planned data is inconsistent with the default data, run the SET E1T1


















----End





70

Procedure



----End



Procedure


----End

8.10.3 Configuring the IPoA DataThis section describes how to set up the IPoA PVC between the SGSN and the CBC.

Prerequisitel The data of the physical link or port that carries the IPoA PVC is configured, and the link

or port is not in use. For details, see Configuring the Physical Layer (over ATM).l The ATM traffic resources of the IPoA PVC are configured. For details, see Configuring

the ATM Traffic Resources.

ContextFor details about principles for IPoA configuration on the Iu-BC interface, see IPoA DataConfiguration on the Iu-BC Interface.

Procedure

Step 1 Run the ADD DEVIP command to add the device IP address of the board.

NOTE

Each interface board can be configured with a maximum of five device IP addresses.

Step 2 Run the ADD IPOAPVC command to set up an IPoA PVC between the BSC6900 and theSGSN. In this step:l Set Peer type to IUPS.l Set IP Address to the device IP address of the board.l Set Peer IP Address to the IP address of the SGSN.



71

Step 3 Optional: Run the ADD IPRT command to add a route between the BSC6900 and the CBCwhen the layer 3 networking mode is used.

----End

8.10.4 Configuring the CBS AddressThis section describes how to configure the Cell Broadcast Service (CBS) address, that is, toconfigure the radio network layer data of the CBS.

ContextThe CBS address is an IP address used for the communication between the CBC and theBSC6900.

Procedure

Step 1 Run the ADD UCBSADDR command to add the data related to cell broadcast, such as the CBSaddress.

----End

8.11 Configuring the Iu-BC Interface (over IP)This section describes how to configure the transport network layer data for the Iu-BC interfacebetween BSC6900 and the CBC. Perform this task only when the BSC6900 is directly connectedto the CBC.

PrerequisiteThe OSP data of the BSC6900 is configured. For details, see Configuring the OPC and DPC.

ContextFamiliarize yourself with Interface Boards Applicable to Terrestrial Interfaces and DataConfiguration Principles for the Iu-BC Interface (over IP) before performing the operationsdescribed in this section. This task configures only the transport network layer of the Iu-BCinterface. To enable the BSC6900 to provide the Cell Broadcast Service (CBS), you also needto configure CBS data. For details, see the RAN Feature Description.




This section describes how to configure the physical layer and data link layer for the FG2a/FG2c/GOUa/GOUc board, which is used as the interface board of the BSC6900. You need to set the



72

Ethernet port attributes, add the standby Ethernet port, add the IP address of the Ethernet port,add the link aggregation group, add the link to the link aggregation group, add the IP address ofthe link aggregation group, and add the device IP address.


Procedure












NOTE



NOTE







73


----End




Procedure













74


----End





Procedure














75


l Set Board type to POUa or POUc.

l It is recommended that Borrow DevIP be set to YES.2. Run the ADD MPLNK command to add an MP link.

----End

Configuring the Physical Layer and Data Link Layer for the UOIa Board

This section describes how to configure the physical layer and data link layer for the UOIa board,which is used as the interface board of the BSC6900.


Procedure




Step 3 Run the ADD PPPLNK command to add a PPP link. To add more PPP links, run this commandrepeatedly.In this step:

l Set Board type to UOIa.

l It is recommended that Borrow DevIP be set to YES.

----End

8.11.2 Configuring the CBS AddressThis section describes how to configure the Cell Broadcast Service (CBS) address, that is, toconfigure the radio network layer data of the CBS.

ContextThe CBS address is an IP address used for the communication between the CBC and theBSC6900.

Procedure

Step 1 Run the ADD UCBSADDR command to add the data related to cell broadcast, such as the CBSaddress.

----End



76

9 Configuring the Cell Data

About This Chapter

This chapter describes how to configure a UMTS NodeB and its cells, including how to configurethe NodeB, UMTS cell, intra-frequency neighboring cell, inter-frequency neighboring cell, andneighboring GSM cell.

Contextl This task configures the NodeB logical data on the BSC6900 side. The initial configuration

on the NodeB needs to be performed on the CME. For details, see the NodeB InitialConfiguration in the M2000-CME document disk.

l Familiarize yourself with 10.4 Data Configuration Principles for Cells before performingthe operations described in this chapter.

NOTE

You can download M2000–CME document disk from http://support.huawei.com.

1. 9.1 Configuring a NodeBThis section describes how to configure a NodeB at the BSC6900.

2. 9.2 Configuring a UMTS CellThis section describes how to configure a UMTS cell. During BSC6900 initialconfiguration, perform this task when you need to configure a cell with standard parameterconfiguration.

3. 9.3 Configuring an Intra-Frequency Neighboring CellThis section describes how to configure an intra-frequency neighboring cell. This task isrequired when intra-frequency neighboring cells are planned for the local cell duringBSC6900 initial configuration.

4. 9.4 Configuring an Inter-Frequency Neighboring CellThis section describes how to configure an inter-frequency neighboring cell. This task isrequired when inter-frequency neighboring cells are planned for the local cell duringBSC6900 initial configuration.

5. 9.5 Configuring a Neighboring GSM CellThis section describes how to configure a neighboring GSM cell. This task is required whenneighboring GSM cells are planned for the local cell during BSC6900 initial configuration.

BSC6900 UMTSInitial Configuration Guide 9 Configuring the Cell Data


77

6. 9.6 Configuring a Neighboring LTE CellThis section describes how to configure a neighboring LTE cell. This task is required whenneighboring LTE cells are planned for the local cell during BSC6900 initial configuration.



78

9.1 Configuring a NodeBThis section describes how to configure a NodeB at the BSC6900.

Prerequisitel The physical layer and data link layer of the Iub interface are configured on the

BSC6900 in ATM transmission mode. For details, see Configuring the Physical Layer (overATM).

l The physical layer and data link layer of the Iub interface are configured on theBSC6900 in IP transmission mode. For details, see Configuring the Physical Layer andData Link Layer (over IP).

l The ATM transmission resources are configured over the Iub interface on the BSC6900 inATM transmission mode. For details, see Configuring the ATM Traffic Resources.

ContextThis task configures the NodeB on the BSC6900. For the initial configuration on the NodeB,see the NodeB Initial Configuration in the M2000-CME document disk.

NOTE

You can download M2000–CME document disk from http://support.huawei.com.

Procedure

Step 1 Run the ADD UNODEB command to add a NodeB.

Step 2 Run the ADD UNODEBALGOPARA command to add algorithm parameters for the NodeB.

Step 3 Run the ADD UNODEBLDR command to add load reshuffling algorithm parameters for theNodeB.

Step 4 Run the ADD UNODEBOLC command to add overload algorithm parameters for the NodeB.

----End

9.2 Configuring a UMTS CellThis section describes how to configure a UMTS cell. During BSC6900 initial configuration,perform this task when you need to configure a cell with standard parameter configuration.

Prerequisitel The area information of the cell is configured. For details, see Configuring the Area

Information.

l The equipment data of the BSC6900 is configured. For details, see 7 Configuring theEquipment Data.

l The transport layer of the BSC6900 is configured.



79

Procedure

Step 1 Run the ADD ULOCELL command to add a local cell.

Step 2 Run the ADD USPG command to set the priorities of different services in the cell.

Step 3 Run the ADD UCELLQUICKSETUP command to quickly set up a cell.

Step 4 Run the ACT UCELL command to activate the cell.

----End

9.3 Configuring an Intra-Frequency Neighboring CellThis section describes how to configure an intra-frequency neighboring cell. This task is requiredwhen intra-frequency neighboring cells are planned for the local cell during BSC6900 initialconfiguration.


Information.l Each intra-frequency neighboring cell of a cell has a unique primary scrambling code.l If the intra-frequency neighboring cell belongs to a neighboring BSC6900, the data of the

neighboring BSC6900 and that of the Iur interface must be configured before performingthis task.

Contextl For the neighbor relations, the concept of local cell is relative to the concept of neighboring

cell. The concept of local BSC6900 is relative to the concept of neighboring BSC6900.l In the BSC6900, the neighbor relation is unidirectional. Therefore, after configuring cell

B as an intra-frequency neighboring cell of cell A, check whether cell A should also be anintra-frequency neighboring cell of cell B. If yes, configure cell A as an intra-frequencyneighboring cell of cell B on the BSC6900 that controls cell B.

l Before configuring an intra-frequency neighboring cell for a cell, determine whether thetwo cells are controlled by the same BSC6900 or different BSC6900s.

Procedurel If a specified cell and the local cell are controlled by the same BSC6900, perform the

following step:1. Run the ADD UINTRAFREQNCELL command to add the specified cell as an intra-

frequency neighboring cell of the local cell.l If a specified cell and the local cell are controlled by different BSC6900s, perform the

following step:1. Run the ADD UEXT3GCELL command to add a cell.2. Optional: If the URA information is not configured for the intra-frequency

neighboring BSC6900 that controls the specified cell, run the ADD UNRNCURAcommand to add the URA information of the intra-frequency neighboringBSC6900.



80

3. Run the ADD UINTRAFREQNCELL command to add the specified cell as an intra-frequency neighboring cell of the local cell.

----End

9.4 Configuring an Inter-Frequency Neighboring CellThis section describes how to configure an inter-frequency neighboring cell. This task is requiredwhen inter-frequency neighboring cells are planned for the local cell during BSC6900 initialconfiguration.


Information.

l Each inter-frequency neighboring cell of a cell has a unique combination of uplinkfrequency, downlink frequency, and scrambling code.

l If the inter-frequency neighboring cell belongs to a neighboring BSC6900, the data of theneighboring BSC6900 and that of the Iur interface must be configured before performingthis task.


cell. The concept of local BSC6900 is relative to the concept of neighboring BSC6900.

l In the BSC6900, the neighbor relation is unidirectional. Therefore, after configuring cellB as an inter-frequency neighboring cell of cell A, check whether cell A should also be aninter-frequency neighboring cell of cell B. If yes, configure cell A as an inter-frequencyneighboring cell of cell B on the BSC6900 that controls cell B.

l Before configuring an inter-frequency neighboring cell for a cell, determine whether thetwo cells are controlled by the same BSC6900 or different BSC6900s.

Procedurel If a specified cell and the local cell are controlled by the same BSC6900, perform the

following step:

1. Run the ADD UINTERFREQNCELL command to add the specified cell as an inter-frequency neighboring cell of the local cell.

l If a specified cell and the local cell are controlled by different BSC6900s, perform thefollowing steps:

1. Run the ADD UEXT3GCELL command to add a cell.

2. Optional: If the URA information is not configured for the inter-frequencyneighboring BSC6900 that controls the specified cell, run the ADD UNRNCURAcommand to add the URA information of the inter-frequency neighboringBSC6900.

3. Run the ADD UINTERFREQNCELL command to add the specified cell as an inter-frequency neighboring cell of the local cell.

----End



81

9.5 Configuring a Neighboring GSM CellThis section describes how to configure a neighboring GSM cell. This task is required whenneighboring GSM cells are planned for the local cell during BSC6900 initial configuration.

PrerequisiteEach neighboring GSM cell of a cell has a unique combination of network color code, BS colorcode, frequency number, and frequency band.


cell.

l In the BSC6900, the neighbor relation is unidirectional. Therefore, after the configurationin this task, GSM cell B becomes a neighboring cell of cell A in the local BSC6900;however, cell A is not automatically configured as a neighboring cell of GSM cell B.

Procedure

Step 1 Run the ADD UEXT2GCELL command to add a GSM cell.

Step 2 Run the ADD U2GNCELL command to add the GSM cell as a neighboring cell of the servingcell.

----End

9.6 Configuring a Neighboring LTE CellThis section describes how to configure a neighboring LTE cell. This task is required whenneighboring LTE cells are planned for the local cell during BSC6900 initial configuration.

PrerequisiteThe neighboring LTE cells of one cell cannot have the same tracking area code (TAC), physicalcell ID, frequency band, and downlink frequency point.

Contextl For the neighboring relations, the concept of local cell is relative to the concept of

neighboring cell.

l In the BSC6900, the neighboring cell relation is unidirectional. Therefore, after theconfiguration in this task, LTE cell B becomes a neighboring cell of cell A in the localBSC6900; however, cell A is not automatically configured as a neighboring cell of LTEcell B.

Procedure

Step 1 Run the ADD ULTECELL command to add a LTE cell.



82

Step 2 Run the ADD ULTENCELL command to add the LTE cell as a neighboring cell of the servingcell.

----End



83

10 Configuration Reference Information

About This Chapter

This chapter describes the concepts, principles, rules, and conventions related to dataconfiguration.

10.1 Data Configuration Principles for EquipmentThis section describes the configuration rules and reference information related to theBSC6900 equipment.

10.2 Data Configuration Principles for TransmissionThis section describes the configuration rules and reference information related to the datatransmission of the BSC6900.

10.3 Data Configuration Principles for InterfacesThis section describes the configuration rules and reference information related to theBSC6900 interfaces.

10.4 Data Configuration Principles for CellsThis section describes the configuration rules and reference information related to a cell.

10.5 Data Configuration Guidelines for SpecificationsThis document describes the specifications of the BSC6900.

BSC6900 UMTSInitial Configuration Guide 10 Configuration Reference Information


84

10.1 Data Configuration Principles for EquipmentThis section describes the configuration rules and reference information related to theBSC6900 equipment.

10.1.1 Configuration Rules of the CabinetsThis section describes the configuration rules for the BSC6900 cabinets.

The configuration rules of the BSC6900 cabinets are as follows:

l The cabinets consist of the Main Processing Rack (MPR) and Extended Processing Rack(EPR).

l The MPR is configured by default. You cannot add or remove this cabinet by running theMML command.

l The BSC6900 can be configured with a maximum of two cabinets.

10.1.2 Configuration Rules of the SubracksThis section describes the configuration rules and reference information related to theBSC6900 subracks.

The configuration rules of the BSC6900 subracks are as follows:

l The Main Processing Subrack (MPS) is configured by default. You do not need to add thissubrack by running the MML command.

l Before adding a subrack, ensure that the cabinet to which the subrack is added exists, andthat the MPS works properly.

l Each subrack needs to be equipped with a fan box. The power distribution box can beconfigured as required. Generally, only one subrack in a cabinet can be connected to themonitoring board of the power distribution box.

l The actual board type in a subrack must be consistent with the configured type. The subracknumber of the EPS/TCS must be consistent with the setting of the DIP switch.

l After a subrack is added, run the MML command to enable the corresponding port on theSCU board in the MPS.

l The relation between Subrack No. and Cabinet No. is as follows: Cabinet No. equals thequotient of Subrack No. divided by three.

10.1.3 Configuration Rules of the BoardsThis section describes the configuration rules and reference information related to theBSC6900 boards.

Classification of Boards

Table 10-1 provides the classification of the BSC6900 boards.



85

Table 10-1 Board classification

Board Class Board Type Logical Function Type

Interface board AEUa/AOUa/AOUc/UOIc ATM

PEUa/FG2a/GOUa/GOUc/POUa/POUc/FG2c

IP

UOIa ATM

IP

Data Processing Unit (DPU) DPUb/DPUe UUP

Network Intelligence Unit(NIU)

NIUa NIU

Signaling Processing Unit(XPU)

SPUa/SPUb UCP

RUCP

Operation and MaintenanceUnit (OMU)

OMUa/OMUc OAM

Service Aware Unit (SAU) SAUa/SAUc SAU

Functions of boards

The BSC6900 boards provide different functions when being loaded with different software, asdescribed in Table 10-2.

Table 10-2 Functions of boards

Logical Function Type Description

OAM Operation and maintenance management

UCP All the subsystems are configured as CPU forService (CPUS) subsystems, which are usedto process the services in the control plane ofthe UMTS RNC.

RUCP Subsystem 0 is configured as the MPUsubsystem, which is used to manageresources. All the other subsystems areconfigured as CPUS subsystems, which areused to process the services in the controlplane of the UMTS RNC.

UUP UMTS RNC user plane processing

ATM ATM interface processing

IP IP interface processing



86

Logical Function Type Description

SAU Service aware unit

NIU Network Intelligence Unit

NOTE

l It is recommended that the services of the boards in each subrack be controlled by the MPU subsystemin the same subrack to avoid a large data flow transmitted between subracks.

l At least one SPUb board out of every three pairs of SPUb boards must be of the RGCP type. It isrecommended that you configure one SPUb board of the RGCP type out of every two pairs ofXSPUb boards.

l It is recommended that service processing boards and interface boards be evenly distributed in eachsubrack to reduce data exchanging between subracks.

l It is recommended that interface boards, XPU boards, and DPU boards be evenly distributed in eachsubrack.

10.1.4 Configuration Rules of the ClockThis section describes the configuration rules and reference information related to theBSC6900 clock.

The configuration rules of the board clock are as follows:l The interface boards in the EPS cannot provide 8 kHz clock output through the backplane.l Each channel of 8 kHz backplane clock has only one clock source. The clock output switch

on multiple interface boards for the same channel of 8 kHz backplane clock cannot beturned on at the same time.

l If both data and voice services are carried by the board, the clock source for the two typesof services must be the same in the core network. Otherwise, the data or voice service mayfail.

l Both the LINE1 clock and the LINE2 clock are extracted from Port for LINE.

The configuration rules of the system clock are as follows:l Clock source priority ranges from 1 to 4. The clock source of priority 0 is configured by

default. Priority 0 is the lowest priority. The descending ranking of priorities is 1, 2, 3, and4.

l Clock source type should be set according to the mode of obtaining the clock signals.– If the clock signals are extracted from the CN by the interface board (for example,

PEUa/AEUa/AOUa/POUa/UOIa) in the EPS and then sent to the GCUa/GCGa boardthrough the line clock signal cable, Clock source type should be set toBITS1-2MHZ or BITS2-2MHZ.

– If the clock signals are extracted from the CN by the interface board in the MPS andthen sent to the GCUa/GCGa board through the backplane of the MPS, Clock sourcetype should be set to LINE1_8KHZ or LINE2_8KHZ.

– If the clock signals are provided by the external BITS, Clock source type should be setto BITS1-2MBPS, BITS2-2MBPS, BITS1-1.5MBPS, or BITS2-1.5MBPS.

– If the clock signals are provided by the GPS and then sent to the GCGa board, Clocksource type should be set to GPS.



87

– If the clock signals are provided by the external 8 kHz clock, Clock source type shouldbe set to 8KHZ.

10.1.5 Introduction to Time SynchronizationThe time synchronization function enables the time synchronization of the nodes of the RANsystem.

Synchronization is critical for identifying faults. For example, if an E1 link between theBSC6900 and the base station is broken, time synchronization between the BSC6900 and thebase station ensures that the same fault is reported to the M2000 by the BSC6900 and by thebase station at the same time point.

The Simple Network Time Protocol (SNTP) is used to synchronize the time of the nodes of theRAN system. SNTP serves the time synchronization between a server and multiple clients.Therefore, an SNTP server must be configured in the RAN system. The SNTP server broadcaststime synchronization information to the SNTP clients.

Either the BSC6900 or the M2000 functions as an SNTP server. You can configure an SNTPserver by taking the field condition into consideration.

SNTP works on Greenwich Mean Time (GMT). Therefore, when setting the time at differentnodes, you need to set the time zone where the node is located and decide whether to set DaylightSaving Time (DST). If DST is set, you need to configure the start date/time and end date/timeof DST and the time offset.

10.2 Data Configuration Principles for TransmissionThis section describes the configuration rules and reference information related to the datatransmission of the BSC6900.

10.2.1 Physical Layer Data Configuration PrinciplesThis section describes the principles for configuring physical layer data.

Interface Boards Applicable to Terrestrial InterfacesBefore planning the configuration data, you need to select the appropriate interface boards basedon the features of terrestrial interfaces.

ATM Interface BoardsTable 10-3 lists the recommended interface boards for ATM-based interfaces.

Table 10-3 Recommended ATM interface boards

Interface Recommended ATM Interface Board

Iub AOUa/AOUc, UOIa (UOIa_ATM)/UOIc, andAEUa

Iu-CS UOIa (UOIa_ATM)/UOIc



88

Interface Recommended ATM Interface Board

Iu-PS UOIa (UOIa_ATM)/UOIc

Iur UOIa (UOIa_ATM)/UOIc

Iu-BC UOIa (UOIa_ATM)/UOIc

NOTE

The Iu-BC interface can share physical transmission resources with the Iu-PS interface. In this networking,if the physical layer data of the Iu-PS interface exists, the physical layer configuration is not necessary forthe Iu-BC interface.

IP Interface Boards

Table 10-4 lists the recommended interface boards for IP-based interfaces.

Table 10-4 Recommended IP interface boards

Interface Recommended IP Interface Board

Iub POUa/POUc, UOIa (UOIa_IP), GOUa/GOUc,FG2a/FG2c, and PEUa

Iu-CS GOUa/GOUc, FG2a/FG2c, and UOIa (UOIa_IP)

Iu-PS GOUa/GOUc, FG2a/FG2c, and UOIa (UOIa_IP)

Iur GOUa/GOUc, FG2a/FG2c, and UOIa (UOIa_IP)

Iu-BC GOUa/GOUc, FG2a/FG2c, and UOIa (UOIa_IP)

Upper-Layer Applications Supported by Interface Boards

This section describes the upper-layer applications supported by each interface board you needto know before configuring the physical layer and data link layer data.

Upper-Layer Applications Supported by ATM Interface Boards

Table 10-5 lists the upper-layer applications supported by ATM interface boards.

Table 10-5 Upper-layer applications supported by ATM interface boards

ATM Interface Board Upper-Layer Application

AEUa IMA, UNI, fractional ATM, fractional IMA,and timeslot cross connection

AOUa IMA and UNI



89

ATM Interface Board Upper-Layer Application

AOUc IMA, UNI, Fractional IMA, and FractionalATM

UOIa (UOIa_ATM) and UOIc Optical port transmission

Upper-Layer Applications Supported by IP Interface Boards

Table 10-6 lists the upper-layer applications supported by IP interface boards.

Table 10-6 Upper-layer applications supported by IP interface boards

IP Interface Board Upper-Layer Application

PEUa PPP link and MLPPP link group

POUa and POUc PPP link and MLPPP link group

UOIa_IP PPP link

FG2a and FG2c Ethernet transmission

GOUa and GOUc Ethernet transmission

Numbering of Links Carried on Optical Ports

The numbering of links carried on the optical ports of the interface board is different from thatof common SDH transmission equipment.

The methods used by companies or organizations for numbering transmission equipment are asfollows:

l Huawei: TUG3 + (TUG2 - 1) x 3 + (TU12 - 1) x 21

l Lucent: TU12 + (TUG2 - 1) x 3 + (TUG3 - 1) x 21

l ITU-T: TUG2 + (TU12 - 1) x 7 + (TUG3 - 1) x 21

Table 10-7 describes the relationship between the link numbers of the optical ports on theinterface board and the transmission equipment numbers.

Table 10-7 Relationship between link numbers of optical ports and transmission equipmentnumbers

Numberof TUG3Blocks

Numberof TUG2Columns

Numberof TU12Lines

HuaweiTransmissionEquipment

LucentTransmissionEquipment

ITU-TStandard

LinkNumberofOpticalPort

1 1 1 1 1 1 0



90

Numberof TUG3Blocks


Numberof TU12Lines



ITU-TStandard


1 2 1 4 4 2 1

1 3 1 7 7 3 2

1 4 1 10 10 4 3

1 5 1 13 13 5 4

1 6 1 16 16 6 5

1 7 1 19 19 7 6

1 1 2 22 2 8 7

1 2 2 25 5 9 8

1 3 2 28 8 10 9

1 4 2 31 11 11 10

1 5 2 34 14 12 11

1 6 2 37 17 13 12

1 7 2 40 20 14 13

1 1 3 43 3 15 14

1 2 3 46 6 16 15

1 3 3 49 9 17 16

1 4 3 52 12 18 17

1 5 3 55 15 19 18

1 6 3 58 18 20 19

1 7 3 61 21 21 20

2 1 1 2 22 22 21

2 2 1 5 25 23 22

2 3 1 8 28 24 23

2 4 1 11 31 25 24

2 5 1 14 34 26 25

2 6 1 17 37 27 26

2 7 1 20 40 28 27

2 1 2 23 23 29 28



91

Numberof TUG3Blocks


Numberof TU12Lines



ITU-TStandard


2 2 2 26 26 30 29

2 3 2 29 29 31 30

2 4 2 32 32 32 31

2 5 2 35 35 33 32

2 6 2 38 38 34 33

2 7 2 41 41 35 34

2 1 3 44 24 36 35

2 2 3 47 27 37 36

2 3 3 50 30 38 37

2 4 3 53 33 39 38

2 5 3 56 36 40 39

2 6 3 59 39 41 40

2 7 3 62 42 42 41

3 1 1 3 43 43 42

3 2 1 6 46 44 43

3 3 1 9 49 45 44

3 4 1 12 52 46 45

3 5 1 15 55 47 46

3 6 1 18 58 48 47

3 7 1 21 61 49 48

3 1 2 24 44 50 49

3 2 2 27 47 51 50

3 3 2 30 50 52 51

3 4 2 33 53 53 52

3 5 2 36 56 54 53

3 6 2 39 59 55 54

3 7 2 42 62 56 55

3 1 3 45 45 57 56



92

Numberof TUG3Blocks


Numberof TU12Lines



ITU-TStandard


3 2 3 48 48 58 57

3 3 3 51 51 59 58

3 4 3 54 54 60 59

3 5 3 57 57 61 60

3 6 3 60 60 62 61

3 7 3 63 63 63 62

Configuration Rules of E1/T1 Links and IMA Links

This section describes the rules for configuring E1/T1 links and IMA links for the BSC6900.

The rules for configuring E1/T1 links for the BSC6900 are as follows:

l The physical layer applications of E1/T1 links include IMA links, UNI links, fractionalATM links, and fractional IMA links.

l For a single link or links carried on a single port, the link type cannot be changed from E1to T1 or from T1 to E1. All the links must be set to the T1 or E1 type uniformly.

l An E1/T1 link can serve only one application, such as the IMA link or UNI link. It cannotwork as an IMA link and a UNI link at the same time.

l If an E1/T1 link serves multiple fractional ATM links or fractional IMA links, the fractionalATM or IMA links must be carried on different timeslots.

l One type of upper-layer application can be carried on different types of physical layer links.For example, one AAL2 path is carried on a UNI link and another AAL2 path on an IMAlink.

l The configurations of frame structure, line code, and scrambling switch must be identicalat both ends of an E1/T1 link.

The rules for configuring IMA links for the BSC6900 are as follows:

l All links in an IMA group must be of the same type, either E1 or T1.

l The settings of scrambling switches of all E1/T1 links in an IMA group must be identical.

l All IMA links in an IMA group must be of the same type, either common IMA link orfractional IMA link.

l For a fractional IMA group, the number of timeslots that carry each fractional IMA linkmust be identical. A fractional IMA group is an IMA group that contains only fractionalIMA links.

l The E1/T1 links whose link numbers are congruent modulo 32 cannot be in the same IMAgroup.



93

l Links carried on different optical ports of the AOUa board cannot be in the same IMAgroup.

Configuration Rules of ATM PortsThis section describes the rules of configuring upper-layer applications for ATM-based physicalports. The ATM-based physical ports consist of E1/T1 ports and optical ports.

Port CompatibilityWhen an E1/T1 port carries a UNI or IMA link, the port cannot carry any fractional IMA links,fractional ATM links, or timeslot cross connections. Fractional IMA links, fractional ATM links,and timeslot cross connections can be carried on the same E1/T1 port on the condition that theyoccupy different timeslots.

Timeslot CompatibilityAt one time point, a timeslot can be occupied by only one upper-layer application. Take an AEUaboard for example. If a timeslot is occupied by a fractional ATM link, the timeslot cannot beused by any fractional IMA link or timeslot cross connection.

Application CompatibilityIf IMA links are configured in an IMA group, no fractional IMA link can be added to the group.Similarly, if fractional IMA links are configured in an IMA group, no IMA link can be addedto the group. In a fractional IMA group, each fractional IMA link occupies the same number oftimeslots.

If an E1/T1 port carries a UNI link, it cannot carry any IMA link, fractional IMA link, fractionalATM link, or timeslot cross connection.

10.2.2 ATM Transport ModesThis section describes the configuration rules and reference information related to ATMtransport. ATM transport has four modes: UNI, fractional, timeslot cross connection, and IMA.

UNI ModeThe UNI mode is a transport mode at the Transmission Convergence (TC) sublayer of thephysical layer.

In UNI mode, an ATM cell is directly carried on an E1/T1 frame and the bits of the ATM cellare sequentially mapped to the valid timeslots on the E1/T1 frame. Figure 10-1 shows themapping between the ATM cell and the E1 timeslots in UNI mode. The 53 bytes of the ATMcell are sequentially carried on E1 timeslots. Each E1 frame provides 31 timeslots (with slot 0unavailable) for carrying the ATM cell.



94

Figure 10-1 Mapping between the ATM cell and the E1 timeslots in UNI mode

Fractional Mode

Fractional mode is applicable to the Transmission Convergence (TC) sublayer of the physicallayer. This section describes the principles and functions of fractional mode, introduces twoimplementation modes (that is, fractional IMA and fractional ATM), and provides the guidelinesfor configuring fractional IMA links and fractional ATM links.

Principles of Fractional ATM and Fractional IMA

In the case of fractional ATM, multiple timeslots out of the 32 timeslots on an E1/T1 are usedto transmit an ATM cell. At the transmission end, an ATM cell is mapped to multiple timeslotsamong the 31 timeslots on an E1/T1. At the reception end, the ATM cell is restored from theassociated timeslots on the E1/T1. Figure 10-2 shows the fractional ATM mode. An E1 framehas timeslots numbered from 0 to 31. All the timeslots except timeslot 0 are available for servicedata transmission. A T1 frame has timeslots numbered from 1 to 24. All the timeslots areavailable for service data transmission. The timeslots to which the ATM cell is not mapped cantransmit other data.

Figure 10-2 Fractional ATM mode



95

If multiple E1/T1 trunks exist between the transmission end and the reception end and work inIMA mode, such an IMA mode is called fractional IMA. In fractional IMA mode, an IMA groupcontains multiple fractional ATM links.

Function of Fractional ATMAfter the fractional ATM function is enabled, the ATM cells of a 3G network can be transmittedover an existing 2G network, as shown in Figure 10-3.

Figure 10-3 Fractional ATM function

Two Modes of the Fractional FunctionThere are two implementation modes of the fractional function on the Iub interface:

l Fractional ATMIn fractional ATM mode, multiple idle timeslots can be used for transmission.The fractional ATM mode is implemented only in the AEUa/AOUc board.

l Fractional IMAIn fractional IMA mode, multiple fractional IMA links are logically gathered into a groupwith each fractional IMA link occupying the same number of idle timeslots.The fractional IMA mode is applicable only to the AEUa/AOUc board.

Timeslot Cross Connection ModeThe timeslot cross connection function implements cross connections between timeslots on twoE1/T1s at the physical medium (PM) sublayer of the physical layer. This section describes theprinciples and functions of timeslot cross connection.



96

Principles of Timeslot Cross ConnectionFigure 10-4 shows an example of timeslot cross connection. The timeslot cross connectiondevice cross-connects the timeslots on one E1/T1 to the timeslots on the other E1/T1. In theexample shown in the following figure, the device cross-connects slots 2 and 3 on one E1/T1 toslots 4 and 8 on another E1/T1 respectively.

Figure 10-4 Example of timeslot cross connection

Function of Timeslot Cross ConnectionThe AEUa board supports timeslot cross connection. Through the configured timeslot crossconnection, the E1 data in TS A of the source port is transmitted to TS B of the target port. Thus,the timeslot cross connection helps provide a transparent data transmission channel for the 2Gequipment or NodeB monitoring equipment.

Figure 10-5 shows implementation of timeslot cross connection.

Figure 10-5 Implementation of timeslot cross connection



97

NOTE

l Neither the source timeslot nor the target timeslot of a timeslot cross connection can be used by otherapplications, such as fractional ATM, IMA, and UNI.

l If an E1 link is configured with a timeslot cross connection, the E1 link cannot carry any IMA or UNIlink. The other timeslots on this E1 link can carry fractional ATM or fractional IMA links.

IMA ModeIMA mode is applicable to the Transmission Convergence (TC) sublayer of the physical layer.The IMA function is implemented by the IMA group, which is composed of either IMA linksor fractional IMA links. This section describes the principles, clock modes, and characteristicsof IMA mode.

Principles of IMA ModeFigure 10-6 shows the principles of the IMA mode based on the assumption that each IMAgroup contains three E1/T1 links.

l At the transmission end, the IMA group receives the ATM cell stream from the ATM layerand distributes the cells among the E1/T1 links.

l At the reception end, the IMA group reassembles the cells to restore the original ATM cellstream, and then transfers the cell stream to the ATM layer.

The physical layer provides high-speed transport channels for ATM cells from the perspectiveof the ATM layer.

Figure 10-6 Principles of the IMA mode

In IMA mode, ATM cells, IMA Control Protocol (ICP) cells, and filler cells form an IMA frameto implement necessary controlling functions.

The length of an IMA frame, m, is defined during the setup of an IMA group. Figure 10-7 showsan IMA frame. The mapping between the ATM cell and the physical link (that is, the E1/T1link) is similar to that in UNI mode.



98

Figure 10-7 IMA frame

Clock Modes

The clock mode of an IMA group is defined from the perspective of an IMA group rather thana single link. The IMA group has two clock modes:l Common Transmit Clock (CTC): In CTC clock mode, all links in an IMA group share one

clock source. The clock source may be extracted from the same external clock or from alink.

l Independent Transmit Clock (ITC): In ITC mode, the clocks used by the links within anIMA group are derived from at least two clock sources. The loopback clock mode is aspecial case of the ITC mode.

Characteristics

The IMA mode has the following characteristics:

l The clock modes at the two ends of the IMA group must be identical.l All E1/T1s within an IMA group are simultaneously scrambled or none of them is

scrambled. In other words, the states of the scrambling switches at both ends of E1/T1smust be identical.

l All IMA links within an IMA group must be of the same type, either common IMA link orfractional IMA link.

l If an IMA group is made up of fractional IMA links, the quantity of timeslots carrying eachfractional IMA link must be identical.

10.2.3 PVC Parameters of the ATM LayerWhen the PVC parameters are set at the ATM layer for Huawei BSC6900, the associatedparameters of the ATM Adaptation Layer (AAL) are also configured.

VPI and VCI

The main characteristics of the ATM technology are multiplexing, switching, and transmittingof ATM cells. All these operations are performed over Virtual Channels (VCs). A VC and a



99

Virtual Path (VP) are identified by Virtual Channel Identifier (VCI) and Virtual Path Identifier(VPI) respectively.

Figure 10-8 shows the relationship between VC and VP.

l A VC is identified by a VCI. It is a logical connection between ATM nodes and is thechannel for transmitting ATM cells between two or more nodes. The VC is used for thedata transmission between mobile terminals, between networks, or between mobileterminal and network.

l A VP is a group of VCs at a given reference point. The VCs in the group have the sameVPI.

Figure 10-8 Relationship between VC and VP

Service TypeThe ATM services are of four types: Constant Bit Rate (CBR), Real-Time Variable Bit Rate(RT-VBR), Non-Real-Time Variable Bit Rate (NRT-VBR), and Unspecified Bit Rate (UBR).

Table 10-8 describes the types of service.

Table 10-8 Types of service

Type of Service Abbreviation Description

Constant Bit Rate CBR No error check, flow control,or other processing

Real-Time Variable Bit Rate RT-VBR Rate of a service withvariable-rate data streamsand strict real-timerequirements, for example,interactive compressed video(video telephony).

Non-Real-Time Variable BitRate

NRT-VBR Rate of a delay-tolerantservice. A service of thistype, such as e-mail, isrelatively insensitive todelivery time or delay.



100

Type of Service Abbreviation Description

Unspecified Bit Rate UBR Rate of a service with nocommitment to transmissionand no feedback oncongestion. This type ofservice is ideal for thetransmission of IPdatagrams. In congestion,UBR cells are discarded, andno feedback or request forslowing down the data rate isdelivered to the transmissionend.

Table 10-9 describes the characteristics of different ATM services.

Table 10-9 Characteristics of different ATM services

Characteristic CBR RT-VBR NRT-VBR UBR

Bandwidthguarantee

Yes Yes Yes No

Applicability toreal-timecommunication

Yes Yes No No

Applicability tobursts ofcommunication

No No Yes Yes

Feedback oncongestion

No No No No

Traffic ParametersTraffic parameters refer to the parameters used by each PVC for flow control. The trafficparameters include traffic rate and delay variation.

Table 10-10 describes the ATM traffic parameters.

Table 10-10 ATM traffic parameters

Parameter Name Parameter ID Description

Traffic record index TRFX Identifies a traffic record.



101

Parameter Name Parameter ID Description

Service Type ST Indicates the type of service carried overATM. CBR and RT-VBR indicate real-timeservices, which are usually carried on the userplanes of the Iur, Iub, and Iu-CS interfaces.NRT-VBR and UBR indicate non-real-timeservices, which are usually carried on the userplane of the Iu-PS interface.

Rate unit UT Indicates the unit of PCR, SCR, and MCR.

Peak cell rate PCR Indicates the maximum rate of transmittingATM cells.

Sustainable cell rate SCR Indicates the average rate of transmittingATM cells over a long time.

Minimum cell rate MCR Indicates the minimum rate of transmittingATM cells.

Max burst size MBS Indicates the maximum number of continuousATM cells.

Cell delay variationtolerance

CDVT Indicates the maximum tolerable variation inthe unit of 0.1 μs.

Traffic usedescription

REMARK Describes the usage of the ATM traffic record.

The traffic rate is indicated in the following ways:l PCR: applicable when Service type is set to CBR and the traffic rate is a constant value.l Combination of PCR and SCR: applicable when Service type is set to RTVBR or

NRTVBR.l MCR: applicable when Service Type is set to UBR_PLUS.

10.2.4 ATM Traffic Resource Configuration PrinciplesThis section provides suggestions for configuring service types during configuration of ATMtraffic resources for links.

Table 10-11 lists the recommended service types for links on different interfaces.

Table 10-11 Recommended service types for links on different interfaces

Link Type of Service (In Descending Orderby Priority)

NCP/CCP RTVBR, NRTVBR, CBR

AAL2 path RTVBR, NRTVBR, CBR, UBR

IPoA PVC (user plane) UBR



102

Link Type of Service (In Descending Orderby Priority)

IPoA PVC (management plane) UBR_PLUS, RTVBR, NRTVBR, CBR,UBR

MTP3 link RTVBR, NRTVBR, CBR

NOTE

l In practice, ATM traffic resources should be negotiated between the local and the peer equipment.

l The ATM traffic parameters of an interface, such as PCR and SCR, should be configured dependingon the traffic model in use.

l When configuring ATM traffic resources for links, you need to consider the traffic on the interfaceboards of the BSC6900.

10.2.5 AAL2 Configuration PrinciplesThis section describes the working principles of the AAL2 path and AAL2 route.

AAL2 Path

The Q.AAL2 module is responsible for dynamically setting up and releasing AAL2 connectionsbetween the BSC6900 and the peer end. The peer end can be a NodeB, a CS CN node, or aneighboring BSC6900. An AAL2 path is terminated at the ATM interface boards AEUa, AOUa/AOUc, and UOIa/UOIc of the BSC6900.

Figure 10-9 shows the relationship between an AAL2 path and AAL2 connections on the Iubinterface.

Figure 10-9 Relationship between an AAL2 path and AAL2 connections

AAL2 Route

An AAL2 path may not reach the destination node but reach an adjacent node. In this case, AAL2routes can be configured to reach the destination node.

Figure 10-10 shows an example of the AAL2 route.



103

Figure 10-10 Example of the AAL2 route

NOTE

Even if the destination node and the adjacent node are the same, an AAL2 route needs to be configured.

10.2.6 MTP3/M3UA Configuration PrinciplesThis section describes the types of and specifications for MTP3/M3UA DSPs, the signaling routemask, and the signaling link mask.

Types of MTP3/M3UA DSPs

This section describes the configuration rules and reference information related to destinationsignaling points (DSPs).

DSP Type

Table 10-12 describes the DSPs supported by the BSC6900.

Table 10-12 Types of DSP

DSP Type Description

IUCS R99 MSC DSP. The IUCS DSP has thecontrol plane functions of both radio networklayer and transport network layer on the Iu-CS interface.

IUPS Signaling point in the control plane of the Iu-PS interface

IUR Other BSC6900 signaling points

IUCS_RANAP R4 MSC server DSP. The IUCS_RANAPDSP has the control plane functions of theradio network layer on the Iu-CS interface.

IUCS_ALCAP R4 MGW DSP. The IUCS_ALCAP DSP hasthe control plane functions of the transportnetwork layer on the Iu-CS interface.

AAL2SWITCH AAL2 transfer point



104

DSP Type Description

STP Signaling transfer point

Signaling Route Mask and Signaling Link MaskThis section describes configurations and examples of the signaling route mask and signalinglink mask.

The number (represented by n) of 1s in a signaling route mask determines the maximum numberof routes (2n) that participate in load sharing. For example, B0000 indicates that there is at mostone route. B0001 or B1000 indicates that there are at most two routes.

The number (represented by n) of 1s in a signaling link mask determines the maximum numberof links (2n) that participate in load sharing. For example, B0000 indicates that there is at mostone link. B0001 or B1000 indicates that there are at most two links.

The result of the logical AND operation on the signaling link mask and the signaling route maskmust be 0, as shown in Figure 10-11.

Figure 10-11 Relation between signaling link mask and signaling route mask

10.2.7 TRM Configuration PrinciplesThe Transmission Resource Management (TRM) of the BSC6900 manages the transmissionresources of the interfaces, improving the transmission resource utilization and guaranteeing theQuality of Service (QoS). The BSC6900 determines which type of bearer should be used forcurrent services, depending on certain conditions. These conditions are the service type, thepreset mapping between service types and transmission resources, and the utilization of thetransmission resources.

Background InformationDifferent types of service have different QoS requirements. For example, voice services requirehigh QoS but PS background services do not. Therefore, mapping services with different QoSrequirements onto different transmission resources helps achieve high resource utilization.

Configuration PrinciplesBefore transport bearers are set up for radio links on the interfaces, the BSC6900 applies fortransmission resources, makes admission decisions based on transmission resources, andallocates transmission resources.



105

Transmission resource admission implements admission decision. If the admission is successful,the BSC6900 allocates transmission resources according to the TRM mapping tables. In the caseof ATM transport, the BSC6900 applies for Connection IDs (CIDs) and AAL2 path bandwidthresources. For IP transport, the BSC6900 applies for UDP ports and IP path bandwidth resources.

TRM Configuration DescriptionYou can run the related MML command to configure the mapping between service types andtransmission resources over a specific interface.

CAUTIONThe primary and secondary paths for a type of service must be different.

10.2.8 Activity Factor Configuration PrinciplesThe configuration of activity factors can increase the resource utilization.

Background InformationTransmission resources may not be fully utilized because services are not always active. For thepurpose of resource multiplexing, transmission resources should be reserved according to servicebandwidth x activity factor when a service is initiated. The value of an activity factor affects thenumber of services admitted.

Activity Factor Configuration Policies for Different Service TypesThe following policies should be used to reserve transmission resources irrespective of the typeof interface:l Signaling radio bearer: configured SRB bandwidth x activity factor.l Conversational and streaming services: MBR x activity factor. On the Iu-PS interface, these

services are admitted according to GBR x activity factor.l Inactive and background services: GBR x activity factor.The configured SRB bandwidth depends on the type of channel that carries the SRB. MBRindicates the maximum bit rate. GBR indicates the minimum bit rate.

10.3 Data Configuration Principles for InterfacesThis section describes the configuration rules and reference information related to theBSC6900 interfaces.

10.3.1 Data Configuration Principles for the Iub Interface (overATM)

Related information is required for performing data configurations on the ATM-based Iubinterface. This information refers to the protocol stack, links on the Iub interface, and OMchannel configuration principles.



106

Protocol Structure for the Iub Interface (over ATM)When ATM transport is applied to the Iub interface, the sequence of configuring Iub interfacedata should be consistent with the protocol structure, that is, from the bottom layer to the toplayer and from the control plane to the user plane.

Figure 10-12 shows the protocol stack for the ATM-based Iub interface.

Figure 10-12 Protocol stack for the ATM-based Iub interface

The transport network layer of the Iub interface consists of the transport network layer user plane(area A), transport network layer control plane (area B), and transport network layer user plane(area C).

l Areas A, B, and C share the physical layer and ATM layer. Therefore, all links in the threeareas can be carried on common physical links.

l Links in areas A and B are carried on SAAL links. Based on the type of carried information,the upper layer of area A is classified into the NodeB Control Port (NCP) and theCommunication Control Port (CCP). Only Q.AAL2 links are carried in area B.

l In area C, the user plane data is carried on AAL2 paths. The bearer at the lower layer is theATM PVC. Under the control of Q.AAL2, AAL2 connections can be dynamically set upor released for upper-layer services. Therefore, each AAL2 path must have itscorresponding controlling Q.AAL2.

Links on the Iub Interface (over ATM)This section describes the links on the ATM-based Iub interface.



107

Links on the Iub InterfaceThere are three types of links on the ATM-based Iub interface: SAAL link of User-NetworkInterface (UNI) type, AAL2 path, and IPoA PVC. The SAAL link of UNI type is used to carryNCP, CCP, and ALCAP, as shown in Figure 10-13.

Figure 10-13 Links on the Iub interface (over ATM)

NOTE

l The links in the NodeB are not shown in Figure 10-13 because the data configuration does not involvethe internal information of the NodeB.

l The RINT shown in Figure 10-13 refers to the ATM interface boards of the BSC6900. For therecommended ATM interface boards of the Iub interface, see Interface Boards Applicable to TerrestrialInterfaces.

SAAL Link of UNI TypeAn SAAL link of UNI type carries signaling messages on the Iub interface. The signalingmessages carried on the SAAL links are classified into NCP, CCP, and ALCAP, as describedin Table 10-13.

Table 10-13 Data carried on SAAL links of UNI type

Data Type Description

NCP The NCP carries common process messages of NBAP over the Iub interface.An Iub interface has only one NCP.



108


CCP A CCP carries dedicated process messages of NBAP over the Iub interface. AnIub interface may have multiple CCPs. The number of CCPs depends onnetwork planning.

ALCAP ALCAP is also called Q.AAL2. Typically, an Iub interface has one ALCAP.

An SAAL link of UNI type is carried on a PVC. The PVC identifier (VPI/VCI) and otherattributes of the PVC must be negotiated between the BSC6900 and the NodeB.

AAL2 PathAn AAL2 path is a group of connections between the BSC6900 and the NodeB. An Iub interfacehas at least one AAL2 path. It is recommended that more than one AAL2 path be planned.

An AAL2 path is carried on a PVC. The PVC identifier (VPI/VCI) and other attributes of thePVC must be negotiated between the BSC6900 and the NodeB.

IPoA PVCIPoA is a technology in which IP packets are transmitted over the ATM transport network.Essentially, the ATM links over each interface are carried over PVCs. The IPoA PVCs over theIub interface are used to transmit the OM information of a NodeB. In this case, the IPoA PVCis called the management plane IPoA PVC.

OM IPoA Data Configuration on the Iub Interface (over ATM)On the ATM-based Iub interface, the IPoA PVC functions as the Operation and Maintenance(OM) channel.

IPoA PVCFigure 10-14 shows the IPoA PVCs from the BSC6900 to NodeBs.

Figure 10-14 IPoA PVCs from the BSC6900 to NodeBs



109

NOTE

The RINT shown in Figure 10-14 refers to the ATM interface boards of the BSC6900. For therecommended ATM interface boards of the Iub interface, see Interface Boards Applicable to TerrestrialInterfaces.

Network SegmentsEach IPoA PVC travels through the following network segments before reaching the NodeB:

l The 80.168.3.0 segment (with network mask of 255.0.0.0) between the OMUa board andthe ATM interface board. This network segment is set before delivery of the BSC6900.

l 12.13.1.0 segment (with network mask of 255.255.255.0) between the ATM interface boardand the NodeBs. When setting this network segment, you need to take field conditions intoconsideration.

10.3.2 Data Configuration Principles for the Iub Interface (over IP)Related information is required for performing data configuration on the IP-based Iub interface.This information refers to the protocol stack, links on the Iub interface, IP address and routeconfiguration, and OM channel configuration principles.

Protocol Structure for the Iub Interface (over IP)When IP transport is applied to the Iub interface, the sequence of adding Iub interface data shouldbe consistent with the protocol structure, that is, from the bottom layer to the top layer and fromthe control plane to the user plane.

Figure 10-15 shows the protocol stack for the IP-based Iub interface.



110

Figure 10-15 Protocol stack for the IP-based Iub interface

Links on the Iub Interface (over IP)This section describes the links on the IP-based Iub interface.

Links on the Iub InterfaceThere are two types of links on the IP-based Iub interface: SCTP link and IP path. The SCTPlink is used to carry NCP and CCP, as shown in Figure 10-16.



111

Figure 10-16 Links on the Iub interface (over IP)

NOTE

l The links in the NodeB are not shown in Figure 10-16 because the data configuration does not involvethe internal information of the NodeB.

l The RINT shown in Figure 10-16 refers to the IP interface boards of the BSC6900. For therecommended IP interface boards of the Iub interface, see Interface Boards Applicable to TerrestrialInterfaces.

SCTP LinksAn SCTP link carries signaling messages on the Iub interface. The signaling messages carriedon the SCTP links are classified into NCP and CCP, as described in Table 10-14.

Table 10-14 Data carried on SCTP links


NCP The NCP carries common process messages of NBAP over the Iub interface.An Iub interface has only one NCP.

CCP A CCP carries dedicated process messages of NBAP over the Iub interface. AnIub interface may have multiple CCPs. The number of CCPs depends onnetwork planning.

The SCTP link can work in two modes, SERVER and CLIENT, on the BSC6900 and NodeBsides. On the BSC6900 side, the differences between the two working modes are as follows:

l SERVER: The local end enables only the listening port and the peer end sends theinitialization request.



112

In SERVER mode, all SCTP links use the listening port as a local port. The listening portalso becomes the local port of NCP or CCP on the control plane. On the NodeB side, a portnumber is added to each new NCP and CCP.

l CLIENT: The local end sends the initialization request during the setup of a link.In CLIENT mode, each SCTP link must be configured with a local port, which means thata local port number is added to each NCP and CCP. On the NodeB side, only one portnumber needs to be configured.

It is recommended that the working mode of the BSC6900 be set to SERVER when youconfigure an SCTP link.

IP Path

An IP path is a group of connections between the BSC6900 and the NodeB. An Iub interfacehas at least one IP path. It is recommended that two or more IP paths be planned.

IP Addresses and Routes on the Iub Interface (over IP)

On the IP-based or ATM/IP dual stack-based Iub interface, IP addresses and routes are required.

Networking on the Iub Interface

There are two types of networking on the Iub interface: layer 2 networking and layer 3networking. Compared with layer 3 networking, layer 2 networking is simple because the portIP addresses of the BSC6900 and NodeB are located on the same network segment and no routeis required.

Figure 10-17 shows an example of layer 2 networking on the Iub interface.

Figure 10-17 Layer 2 networking on the Iub interface



113

NOTE

IP1 and IP2 are port IP addresses.

Figure 10-18 shows an example of layer 3 networking on the Iub interface.

Figure 10-18 Layer 3 networking on the Iub interface

NOTE

IP1 and IP2 are device IP address on the IP interface board. IP3 and IP4 are port IP addresses on the IPinterface board. IP5 and IP6 are gateway IP addresses on the BSC6900 side. IP7 is the gateway IP addresson the NodeB side. IP8 is the IP address of the NodeB.

IP Addresses on the Iub Interface

As shown in Figure 10-17 and Figure 10-18, the Iub IP addresses at the BSC6900 consist ofIP addresses of Ethernet ports, local IP addresses of PPP links, local IP addresses of MLPPPgroups, and device IP addresses. Table 10-15 describes these IP addresses.

Table 10-15 IP Addresses on the Iub Interface

IP Address Configuration Scenario Configuration Restriction

IP address of anEthernet port

Required when the FG2a/FG2c/GOUa/GOUc boardfunctions as the interfaceboard

l Each Ethernet port can be configuredwith only one primary IP address andfive secondary IP addresses.

l The IP address of an Ethernet port andthe internal IP address of the BAM mustbe located on different networksegments. For these network segments,one cannot cover another.

l In the BSC6900, the IP addresses ofdifferent Ethernet ports must be locatedon different network segments. For thesenetwork segments, one cannot coveranother.



114

IP Address Configuration Scenario Configuration Restriction

Local IPaddress of aPPP link

Required when the PEUa,POUa/POUc, or UOIa(UOIa_IP) board functionsas the interface board

Each PPP link can be configured with onlyone local IP address.

Local IPaddress of anMLPPP group

Required when the PEUa orPOUa/POUc boardfunctions as the interfaceboard

Each MLPPP group can be configured withonly one local IP address.

Device IPaddress

Required in layer 3networking

l Each interface board can be configuredwith a maximum of five device IPaddresses.

l The IP addresses of any two differentdevices must be located on differentsubnets.

Route on the Iub InterfaceOn the Iub interface where layer 2 networking is applied, no route is required. On the Iub interfacewhere layer 3 networking is applied, you should configure the route described in Table 10-16.

Table 10-16 Route on the Iub interface

Equipment Route Description

IP InterfaceBoard

The route travels from the BSC6900 to the network segment where the NodeBis located.You can configure the route on the BSC6900. Destination IP address is theaddress of the network segment where the NodeB or NodeB IP address islocated, and Next Hop Address is the gateway IP address, for example, IP5or IP6, on the BSC6900 side.

OM Channel Configuration on the Iub Interface (over IP)There are two types of routing for the OM channel on the Iub interface. One is the routing betweenthe M2000 and the NodeB through the BSC6900 and the other is the routing between the M2000and the NodeB not through the BSC6900.

Routing Between the M2000 and the NodeB Through the BSC6900Figure 10-19 shows an example of the routing between the M2000 and the NodeB through theBSC6900. Table 10-17 describes the routes.



115

Figure 10-19 Example of the routing between the M2000 and the NodeB through the BSC6900

NOTE

l Figure 10-19 takes layer 2 networking on the Iub interface as an example. When layer 3 networkingis applied to the Iub interface, the IP interface board and the NodeB communicate with each otherthrough a router.

l The RINT shown in Figure 10-19 refers to the IP interface boards of the BSC6900. For therecommended IP interface boards of the Iub interface, see Interface Boards Applicable to TerrestrialInterfaces.

Table 10-17 Routes between the M2000 and the NodeB through the BSC6900

Equipment Forward Route Reverse Route

M2000 From the M2000 to theNodeB OM network segment19.19.19.X, with Forwardroute address to be theexternal virtual IP address ofthe BAM, that is,172.121.139.200

-

BSC6900 From the BAM to the NodeBOM network segment19.19.19.X, with Forwardroute address to be theinternal IP address of the IPinterface board at theBSC6900, that is,80.168.3.66

From the IP interface boardof the BSC6900 to theM2000 IP network segment172.121.139.XYou can configure the routeon the BSC6900 side. Whenyou run this command, setEMS IP Address to the IPaddress of the M2000, setSubnet mask to the subnetmask of the M2000, andspecify the values of BAMExternal Network VirtualIP and BAM External



116


l If layer 2 networking isapplied, add a route to theOM IP address of theNodeB. Forward routeaddress must be the IPaddress of the NodeBinterface board.

l If layer 3 networking isapplied, add a route to theOM IP address of theNodeB. Forward routeaddress must be thegateway IP address on theBSC6900 side.

Network Mask. In thisexample, EMS IP Address is172.121.139.56, and BAMExternal Network VirtualIP is 172.121.139.200.

NodeB - From the NodeB to theM2000 IP network segment172.121.139.Xl If layer 2 networking is

applied to the Iubinterface, Forward routeaddress is the IP addressof the IP interface board atthe BSC6900, that is,16.16.16.1.

l If layer 3 networking isapplied to the Iubinterface, Forward routeaddress is the gateway IPaddress on the NodeBside.

Routing Between the M2000 and the NodeB Not Through the BSC6900If the OM subnet where the M2000 is located is connected to the IP network that covers theNodeB, routes can be configured between the M2000 and the NodeB not through theBSC6900. Figure 10-20 shows an example of routing between the M2000 and the NodeB notthrough the BSC6900. Table 10-18 describes the routes.

Figure 10-20 Example of the routes between the M2000 and the NodeB not through theBSC6900



117

Table 10-18 Routes between the M2000 and the NodeB not through the BSC6900


M2000 From the M2000 to theNodeB OM network segment19.19.19.X, with Forwardroute address being the portIP address of router 1, that is,10.161.215.200

-

Router 1 From router 1 to the NodeBOM network segment19.19.19.X, with Forwardroute address being the portIP address of router 2, that is,172.16.16.10

-

Router 2 From router 2 to the NodeBOM network segment19.19.19.X, with Forwardroute address being the IPaddress of the IP interfaceboard at the NodeB, that is,16.16.16.2

From router 2 to the M2000network segment10.161.215.100, withForward route addressbeing the port IP address ofrouter 1, that is, 172.16.16.9

NodeB - From the NodeB to theM2000 network segment10.161.215.100, withForward route addressbeing the port IP address ofrouter 2, that is, 16.16.16.20

10.3.3 Data Configuration Principles for the Iub Interface (overATM and IP)

Related information is required for performing data configuration on the ATM/IP dual stack-based Iub interface. This information refers to the ATM/IP hybrid transport, hardwareconfiguration principles, and data configuration principles.

ATM/IP Hybrid Transport on the Iub Interface

With the development of data services, especially with the introduction of HSDPA and HSUPA,there is an increasing demand for bandwidth on the Iub interface. The transmission based onATM over E1, however, increases high costs. Data services produce a decreasing efficiency foroperators. Therefore, the operators require a low-cost Iub transmission solution, which leads tothe introduction of the ATM/IP hybrid transport. It reduces the data transmission costs on theIub interface, while maintaining the proper running of services.



118

Based on the Quality of Service (QoS) and bandwidth requirements, ATM/IP hybrid transportimplements data transmission as follows:l Voice services, streaming services, and signaling have a low requirement for bandwidth

and a high requirement for QoS. These services are transmitted on ATM networks.l BE services and HSDPA/HSUPA services have a relatively high requirement for the

bandwidth and low requirement for the QoS. These services are transmitted on IP networks.

NOTE

l BE service refers to best effort service.

l HSDPA/HSUPA service refers to high speed downlink/uplink packet access services.

ATM/IP hybrid transport protects the investment of the existing ATM networks, reduces theimpact of IP transport on the ATM networks, and meets the requirements of operators for cost-effective data transmission and flexible networking.

Hardware Configuration Principles for ATM/IP Hybrid Transport on the IubInterface

This section describes the hardware configuration principles for ATM/IP hybrid transport onthe Iub interface in terms of board configuration, cable connections, and hardware-relatedprecautions.

Hardware Configuration Principles for ATM/IP Hybrid TransportTo implement ATM/IP hybrid transport, insert ATM and IP interface boards into the slots ofthe MPS and EPS. In this way, an ATM/IP dual stack-based NodeB can be connected to an ATMinterface board and an IP interface board at the same time. The two interface boards can belocated in different subracks.

NOTE

Though the BSC6900 ATM and IP interface boards for one NodeB can be located in different subracks, itis recommended that the interface boards be located in the same subrack if possible.

Interface Board Configuration for ATM/IP Hybrid TransportAll ATM and IP interface boards are available for ATM/IP hybrid transport.

For the recommended interface boards, see Interface Boards Applicable to Terrestrial Interfaces.

Figure 10-21 and Figure 10-22 show the typical configurations of interface boards for ATM/IP hybrid transport. As shown in the figures, the AOUa functions as the ATM interface boardand the GOUa functions as the IP interface board.



119

Figure 10-21 Typical configuration of boards in the MPS for ATM/IP hybrid transport

Figure 10-22 Typical configuration of boards in an EPS for ATM/IP hybrid transport

Cable ConnectionsWhen ATM/IP hybrid transport is applied, the ATM interface at the BSC6900 connects to theNodeB through an ATM network, and the IP interface at the BSC6900 connects to the NodeBthrough an IP network.

Data Configuration Principles for ATM/IP Hybrid Transport on the Iub InterfaceThis section describes the data configuration principles for ATM/IP dual stack-based transporton the Iub interface in terms of VLAN planning, transmission resource allocation, and trafficdistribution.

VLAN PlanningVirtual Local Area Network (VLAN) helps shield the BSC6900 from network storms andimprove the security of layer 2 networking. The priorities in VLAN tags are used for service



120

differentiation. The specifications for VLANs in ATM/IP hybrid transport are the same as thosein IP transport on the Iub interface.

There are two types of VLAN settings: VLAN setting in layer 2 networking and VLAN settingin layer 3 networking.

l VLAN setting in layer 2 networking

The value of VLAN ID ranges from 2 to 4094. Due to the limited VLAN ID resources, itis recommended that an identical VLAN ID be allocated to the NodeBs whose traffic isconverged to the same layer 2 transmission device, for example, a LAN switch. If the layer2 transmission device supports the setting of VLAN priorities, the priorities of servicesneed to be mapped onto those of VLANs. If the layer 2 transmission device identifies thepriorities based on the VLAN IDs, the priorities of services need to be mapped onto VLANIDs based on the service types, so as to implement differentiated services.

l VLAN setting in layer 3 networking

VLANs apply to layer 2 networking only. It does not apply to layer 3 transmission devices.Therefore, interface boards at the BSC6900 do not need to be configured with VLAN tags.If the BSC6900 connects to a layer 3 transmission device through a layer 2 network thatsupports configuration of VLAN priorities, the interface board at the BSC6900 can mapthe priorities of services either onto the priorities of VLANs or onto the VLAN IDs basedon the service types. In layer 3 networking, the VLANs configured at the BSC6900 applyto the BSC6900 and the layer 3 transmission device only. Therefore, VLAN IDs andpriorities are generally based on the service type, rather than based on the NodeB.

Transmission Resource Allocation

When you allocate resources for ATM/IP dual stack-based transport on the Iub interface, takethe following suggestions into consideration:

ATM transport, IP transport, or ATM/IP hybrid transport is applicable to control plane data. Itis recommended that ATM/IP hybrid transport be applied to control plane data for securitypurposes. In other words, the SAAL and SCTP links together carry an NCP or a CCP, and theactive link is the SAAL link.

ATM transport, IP transport, or ATM/IP hybrid transport is applicable to user plane data. It isrecommended that:

l ATM transport be applied to signaling, voice services, CS conversational services, CSstreaming services, PS conversational services, and PS streaming services.

l IP transport be applied to PS interactive services, PS background services, HSDPAconversational services, HSDPA streaming services, HSDPA interactive services, HSDPAbackground services, HSUPA conversational services, HSUPA streaming services,HSUPA interactive services, and HSUPA background services.

Either ATM or IP transport is applicable to management plane data. It is recommended that IPtransport be applied.

Traffic Distribution

For the ATM traffic distribution principles and the relationship between interface links andservice types, see ATM Traffic Resource Configuration Principles.



121

10.3.4 Data Configuration Principles for the Iu-CS Interface (overATM)

Related information is required for performing data configuration on the ATM-based Iu-CSinterface. This information refers to the protocol stack, links on the Iu-CS interface, and thedifferences between R99 and R4/R5/R6/R7/R8.

Protocol Structure for the Iu-CS Interface (over ATM)

If ATM transport is applied to the Iu-CS interface, the sequence of configuring Iu-CS interfacedata should be consistent with the protocol structure, that is, from the bottom layer to the toplayer and from the control plane to the user plane.

Figure 10-23 shows the protocol stack for the Iu-CS interface.

Figure 10-23 Protocol stack for the ATM-based Iu-CS interface

The transport network layer of the Iu-CS interface consists of the following areas:

l Transport network layer user plane (area A)l Transport network layer control plane (area B)l Transport network layer user plane (area C)

Areas A, B, and C share the physical layer and ATM layer. Therefore, all links in the three areascan be carried on common physical links.



122

Links on the Iu-CS Interface (over ATM)

If ATM transport is applied to the Iu-CS interface, there are two types of Iu-CS links on the CNside: MTP3 link and AAL2 path.

Links on the ATM-based Iu-CS Interface

Figure 10-24 shows the links on the ATM-based Iu-CS interface.

Figure 10-24 Links on the Iu-CS Interface (over ATM)

NOTE

The RINT shown in Figure 10-24 refers to ATM interface boards of the BSC6900. For the interface boardsrecommended for the ATM-based Iu-CS interface, see Interface Boards Applicable to Terrestrial Interfaces.

MTP3 Link

MTP3 links are contained in an MTP3 link set. The number of the MTP3 link ranges from 0 to15.

The configuration of MTP3 links between the BSC6900 and the MSC server depends on thenetwork structure between the MSC server and the BSC6900:

l If the MSC server is directly connected to the BSC6900, at least one MTP3 link is requiredfor the MSC server (IUCS_RANAP signaling point). It is recommended that more thanone MTP3 link be configured.

l If the MSC server is connected to the BSC6900 through the MGW, the MSC server(IUCS_RANAP signaling point) does not require any MTP3 link.



123

l If the MSC server is connected to the BSC6900 not only directly but also through the MGW,as shown in Figure 10-25, the MSC server (IUCS-RANAP) requires at least one MTP3link. It is recommended that more than one MTP3 link be configured.

Figure 10-25 Example of connections between the MSC server and the BSC6900

An SAAL link of NNI type is carried on an ATM PVC. The PVC identifier (VPI/VCI) and otherattributes of the PVC must be negotiated between the BSC6900 and the peer end.

AAL2 PathAn AAL2 path is a group of connections to the adjacent node. The path IDs range from 1 to4294967295.

An Iu-CS interface has at least one AAL2 path. It is recommended that two or more AAL2 pathsbe configured.

An AAL2 path is carried over an ATM PVC. The PVC identifier (VPI/VCI) and other PVCattributes must be negotiated between the BSC6900 and the peer end.

Differences of the Iu-CS Interface Between R99 and R4/R5/R6/R7/R8In the 3GPP R99, the MSC connects to the BSC6900 as one entity. In the 3GPP R4/R5/R6/R7/R8, the MSC connects to the BSC6900 after being split into two entities, namely, MSC serverand MGW.

Iu-CS Interface Defined in the 3GPP R4/R5/R6/R7/R8Figure 10-26 shows the Iu-CS interface in the 3GPP R4/R5/R6/R7/R8.



124

Figure 10-26 Iu-CS interface in the 3GPP R4/R5/R6/R7/R8

The network may require multiple MGWs depending on the traffic volume.

In practice, the MSC server is not often directly connected to the BSC6900. Data is forwardedbetween the MSC server and the BSC6900 through the routes configured on the MGW. Figure10-27 shows an example of the network structure on the Iu-CS interface in the 3GPP R4/R5/R6/R7/R8.

Figure 10-27 Example of the network structure on the Iu-CS interface in the 3GPP R4/R5/R6/R7/R8

Functions of the MSC and of the MSC Server and MGW

Figure 10-28 and Figure 10-29 show the protocol stacks for the ATM-based and IP-based Iu-CS interfaces respectively.



125


Figure 10-29 Protocol stack for the IP-based Iu-CS interface



126

The MSC in an R99 network implements the functions in areas A, B, and C of the protocol stack.The MSC server and MGW in an R4/R5/R6/R7/R8 network implement their functions asfollows:

l The MSC server implements the functions in area A.

l On the ATM-based Iu-CS interface, the MGW implements the functions in areas B and Cshown in Figure 10-28. On the IP-based Iu-CS interface, the MGW implements thefunctions in area C shown in Figure 10-29.

Data Configuration on the BSC6900

In the 3GPP R99, the BSC6900 needs to be configured with only one type of Iu-CS signalingpoint, that is, the MSC.

In the 3GPP R4/R5/R6/R7/R8, the BSC6900 needs to be configured with the following twotypes of Iu-CS signaling point:

l MSC server (also called Iu-CS RANAP signaling point)

l MGW (also called Iu-CS ALCAP signaling point)

Table 10-19 describes the differences between signaling point configuration in R99 and that inR4/R5/R6/R7/R8.

Table 10-19 Differences between signaling point configuration in R99 and that in R4/R5/R6/R7/R8

Item R4/R5/R6/R7/R8 R99

Type Iu-CS RANAP signaling point and Iu-CSALCAP signaling point

Iu-CS signalingpoint

Quantity More than one One

10.3.5 Data Configuration Principles for the Iu-CS Interface (overIP)

Related information is required for performing data configuration on the IP-based Iu-CSinterface. This information refers to the protocol stack, links on the Iu-CS interface, and thedifferences between R99 and R4/R5/R6/R7/R8.

Protocol Structure for the Iu-CS Interface (over IP)

If IP transport is applied to the Iu-CS interface, the sequence of configuring Iu-CS interface datashould be consistent with the protocol structure, that is, from the bottom layer to the top layerand from the control plane to the user plane.

Figure 10-30 shows the protocol stack for the Iu-CS interface.



127


Links on the Iu-CS Interface (over IP)If IP transport is applied to the Iu-CS interface, there are two types of Iu-CS links on the CNside: M3UA link and IP path.

Links on the Iu-CS InterfaceFigure 10-31 shows the links on the IP-based Iu-CS interface.



128

Figure 10-31 Links on the Iu-CS interface (over IP)

NOTE

The RINT shown in Figure 10-31 refers to the IP interface boards of the BSC6900. For the IP interfaceboards recommended for the Iub interface, see Interface Boards Applicable to Terrestrial Interfaces.

M3UA LinksM3UA links are contained in an M3UA link set. The number of the M3UA link ranges from 0to 15.

The configuration of M3UA links depends on the network structure between the MSC serverand the BSC6900.

l If the MSC server is directly connected to the BSC6900, at least one M3UA link is requiredfor the MSC server (IUCS_RANAP signaling point). It is recommended that more thanone M3UA link be configured.

l If the MSC server is connected to the BSC6900 through the MGW, you need to configurethe M3UA links only between the BSC6900 and the MGW. The MGW is responsible forforwarding signaling to the MSC server. It is recommended that more than one M3UA linkbe configured.

l If the MSC server is connected to the BSC6900 not only directly but also through the MGW,as shown in BSC6900, you can configure the M3UA links between the BSC6900 and theMSC server (IUCS_RANAP signaling point). You can also configure the M3UA linksbetween the BSC6900 and the MGW, which is responsible for forwarding signaling to theMSC server. Or you can configure the M3UA links between the BSC6900 and the MSCserver and the M3UA links between the BSC6900 and the MGW at the same time. It isrecommended that more than one M3UA link be configured.



129

Figure 10-32 Example of connections between the MSC server and the BSC6900

IP PathAn IP path is a group of connections to the adjacent node. The path ID ranges from 0 to 65535.

An Iu-CS interface has at least one IP path. It is recommended that more than one IP path beconfigured.

Differences of the Iu-CS Interface Between R99 and R4/R5/R6/R7/R8In the 3GPP R99, the MSC connects to the BSC6900 as one entity. In the 3GPP R4/R5/R6/R7/R8, the MSC connects to the BSC6900 after being split into two entities, namely, MSC serverand MGW.

Iu-CS Interface Defined in the 3GPP R4/R5/R6/R7/R8Figure 10-33 shows the Iu-CS interface in the 3GPP R4/R5/R6/R7/R8.

Figure 10-33 Iu-CS interface in the 3GPP R4/R5/R6/R7/R8



130

The network may require multiple MGWs depending on the traffic volume.

In practice, the MSC server is not often directly connected to the BSC6900. Data is forwardedbetween the MSC server and the BSC6900 through the routes configured on the MGW. Figure10-34 shows an example of the network structure on the Iu-CS interface in the 3GPP R4/R5/R6/R7/R8.

Figure 10-34 Example of the network structure on the Iu-CS interface in the 3GPP R4/R5/R6/R7/R8

Functions of the MSC and of the MSC Server and MGWFigure 10-35 and Figure 10-36 show the protocol stacks for the ATM-based and IP-based Iu-CS interfaces respectively.



131





132

The MSC in an R99 network implements the functions in areas A, B, and C of the protocol stack.The MSC server and MGW in an R4/R5/R6/R7/R8 network implement their functions asfollows:

l The MSC server implements the functions in area A.

l On the ATM-based Iu-CS interface, the MGW implements the functions in areas B and Cshown in Figure 10-35. On the IP-based Iu-CS interface, the MGW implements thefunctions in area C shown in Figure 10-36.

Data Configuration on the BSC6900

In the 3GPP R99, the BSC6900 needs to be configured with only one type of Iu-CS signalingpoint, that is, the MSC.

In the 3GPP R4/R5/R6/R7/R8, the BSC6900 needs to be configured with the following twotypes of Iu-CS signaling point:

l MSC server (also called Iu-CS RANAP signaling point)

l MGW (also called Iu-CS ALCAP signaling point)

Table 10-20 describes the differences between signaling point configuration in R99 and that inR4/R5/R6/R7/R8.

Table 10-20 Differences between signaling point configuration in R99 and that in R4/R5/R6/R7/R8

Item R4/R5/R6/R7/R8 R99

Type Iu-CS RANAP signaling point and Iu-CSALCAP signaling point

Iu-CS signalingpoint

Quantity More than one One

10.3.6 Data Configuration Principles for the Iu-PS Interface (overATM)

Related information is required for performing data configuration on the ATM-based Iu-PSinterface. This information refers to the protocol structure, links on the ATM-based Iu-PSinterface, and IPoA configuration principle on the user plane.

Protocol Structure for the Iu-PS Interface (over ATM)

If ATM transport is applied to the Iu-PS interface, the sequence of configuring Iu-PS interfacedata should be consistent with the protocol structure, that is, from the bottom layer to the toplayer and from the control plane to the user plane.

Figure 10-37 shows the protocol stack for the Iu-PS interface.



133

Figure 10-37 Protocol stack for the ATM-based Iu-PS interface

The transport network layer over the Iu-PS interface consists of the transport network layer userplane (area A) and the transport network layer user plane (area C).

Areas A and C share the physical layer and ATM layer. Therefore, all links in the two areas canbe carried on common physical links.

Links on the Iu-PS Interface (over ATM)If ATM transport is applied to the Iu-PS interface, there are two types of Iu-PS links on the CNside: MTP3 link and IPoA PVC.

Links on the Iu-PS InterfaceFigure 10-38 shows the links on the Iu-PS interface.



134

Figure 10-38 Links on the Iu-PS interface (over ATM)

NOTE

The RINT shown in Figure 10-38 refers to the ATM interface boards. For the ATM interface boardsrecommended for the Iu-PS interface, see Interface Boards Applicable to Terrestrial Interfaces.

MTP3 LinkMTP3 links are contained in an MTP3 link set. The number of the MTP3 link ranges from 0 to15.

An Iu-PS interface requires at least one MTP3 link. It is recommended that more than one MTP3link be configured.

MTP3 links are carried on the SAAL links of Network-to-Network Interface (NNI) type.

An SAAL link of NNI type is carried on a PVC. The PVC identifier (VPI/VCI) and otherattributes of the PVC must be negotiated between the BSC6900 and the peer end.

IPoA PVCThe IPoA PVC on the Iu-PS interface is a PVC to the SGSN gateway.

An Iu-PS interface requires at least one IPoA PVC. It is recommended that more than one IPoAPVC be configured.

IPoA Data Configuration on the Iu-PS User Plane (over ATM)On the ATM-based Iu-PS interface, the IPoA PVC is implemented on the user plane.

IPoA PVC on the Iu-PS User PlaneFigure 10-39 shows the IPoA PVC on the Iu-PS user plane.



135

Figure 10-39 IPoA PVC on the Iu-PS interface

NOTE

The RINT shown in Figure 10-39 refers to the ATM interface boards. For the ATM interface boardsrecommended for the Iu-PS interface, see Interface Boards Applicable to Terrestrial Interfaces.

IPoA Data on the Iu-PS User Plane

Table 10-21 describes the IPoA data to be configured on the user plane of the ATM-based Iu-PS interface.

Table 10-21 IPoA data on the user plane of the ATM-based Iu-PS interface

Item Description

Local IP address of the IPoA PVC Device IP address on the ATM interface board ofthe BSC6900

Peer IP address of the IPoA PVC IP address of the gateway on the SGSN side

IPoA PVC between the interface boardand the gateway on the SGSN side

-

Route between the interface boardcarrying the IPoA PVC and the networksegment of the peer SGSN

If the IP address of the interface board carrying theIPoA PVC and the IP address of the SGSN arelocated on different subnets, routes to thedestination IP address need to be configured at theBSC6900. Destination IP address is the IPaddress of the SGSN, and Forward routeaddress is the IP address of the gateway on theSGSN side.

CAUTIONOn the Iu-PS interface, the SGSN must be configured with routes to the network segment wherethe IP address of the BSC6900 interface board is located. Forward route address is the IPaddress of the gateway on the BSC6900 side. Otherwise, PS services cannot be provided.



136

10.3.7 Data Configuration Principles for the Iu-PS Interface (overIP)

Related information is required for performing data configuration on the IP-based Iu-PSinterface. This information refers to the protocol structure and links on the IP-based Iu-PSinterface.

Protocol Structure for the Iu-PS Interface (over IP)If IP transport is applied to the Iu-PS interface, the sequence of configuring Iu-PS interface datashould be consistent with the protocol structure, that is, from the bottom layer to the top layerand from the control plane to the user plane.

Figure 10-40 shows the protocol stack for the Iu-PS interface.

Figure 10-40 Protocol stack for the IP-based Iu-PS interface

The transport network layer of the Iu-PS interface consists of the transport network layer userplane (area A) and the transport network layer user plane (area C).

Areas A and C share the physical layer and data link layer. Therefore, all links in the two areascan be carried on common physical links.

Links on the Iu-PS Interface (over IP)If IP transport is applied to the Iu-PS interface, there are two types of Iu-PS links on the CNside: M3UA link and IP path.

Links on the Iu-PS InterfaceFigure 10-41 shows the links on the IP-based Iu-PS interface.



137

Figure 10-41 Links on the Iu-PS interface (over IP)

NOTE

The RINT shown in Figure 10-41 refers to the IP interface boards of the BSC6900. For the IP interfaceboards recommended for the Iu-PS interface, see Interface Boards Applicable to Terrestrial Interfaces.

M3UA Links

M3UA links are contained in an M3UA link set. The number of the M3UA link ranges from 0to 15.

An Iu-PS interface requires at least one M3UA link. It is recommended that more than oneM3UA link be planned.

M3UA links are carried on SCTP links.

IP Path

An IP path is a group of connections to the adjacent node. The path ID ranges from 0 to 65535.

An Iu-PS interface has at least one IP path. It is recommended that more than one IP path beconfigured.

10.3.8 Data Configuration Principles for the Iur Interface (overATM)

Related information is required for performing data configuration on the ATM-based Iurinterface. This information refers to the protocol structure, links on the ATM-based Iur interface,and configuration of paths for static SRNS reallocation.



138

Protocol Stack on the Iur Interface (over ATM)If ATM transport is applied to the Iur interface, the sequence of configuring Iur interface datashould be consistent with the protocol structure, that is, from the bottom layer to the top layerand from the control plane to the user plane.

Figure 10-42 shows the protocol stack for the Iur interface.

Figure 10-42 Protocol stack for the ATM-based Iur interface

The transport network layer of the ATM-based Iur interface consists of the following areas:l Transport network layer user plane (area A)l Transport network layer control plane (area B)l Transport network layer user plane (area C)

Links on the Iur Interface (over ATM)If ATM transport is applied to the Iur interface, there are two types of Iur links on the CN side:MTP3 link and AAL2 path.

Links on the Iur InterfaceFigure 10-43 shows the links on the ATM-based Iur interface.



139

Figure 10-43 Links on the Iur interface (over ATM)

NOTE

The RINT shown in Figure 10-43 refers to the ATM interface boards of the BSC6900. For the ATMinterface boards recommended for the Iur interface, see Interface Boards Applicable to TerrestrialInterfaces.

MTP3 LinkMTP3 links are contained in an MTP3 link set. The number of the MTP3 link ranges from 0 to15.

The configuration of MTP3 links depends on the network structure between the BSC6900 andthe neighboring BSC6900. The specifics are as follows:

l If the BSC6900 is directly connected to the neighboring BSC6900, the Iur interface requiresat least one MTP3 link. It is recommended that more than one MTP3 link be configured.

l If the BSC6900 is connected to the neighboring BSC6900 through a Signaling TransferPoint (STP), no MTP3 link is required.

MTP3 links are carried on the SAAL links of Network-to-Network Interface (NNI) type. It isrecommended that the SAAL links of NNI type be evenly distributed to the CPU for Service(CPUS) subsystems in the MPS/EPS so that the signaling exchange can be reduced between theCPUS subsystems.

An SAAL link of NNI type is carried over an ATM PVC. The PVC identifier (VPI/VCI) andother attributes of the PVC must be negotiated between the BSC6900 and the peer end.

AAL2 PathAn AAL2 path is a group of connections to the adjacent node. The path IDs range from 1 to4294967295.



140

An Iur interface has at least one AAL2 path. It is recommended that more than one AAL2 pathbe configured.

An AAL2 path is carried over an ATM PVC. The PVC identifier (VPI/VCI) and other PVCattributes must be negotiated between the BSC6900 and the peer end.

Configuration Principles for Static Relocation Routes over IurThe IP routes on the Iur interface are used to forward the PS data during Serving Radio NetworkSubsystem (SRNS) relocation. During the SRNS relocation, the PS data is transferred from thelocal BSC6900 to the SGSN and then to the neighboring BSC6900. Therefore, the prerequisitesfor configuring IP routes on the Iur interface are that the IP paths between the local BSC6900and the SGSN, between the neighboring BSC6900 and the SGSN, and between the servingBSC6900 and the drift BSC6900 are configured.

Figure 10-44 shows the configuration of IP routes on the Iur interface. The IP routes configuredin multiple subsystems are similar.

Figure 10-44 IP route configuration on the Iur interface

NOTE

The RINT shown in Figure 10-44 refers to the interface boards of the BSC6900. For the ATM interfaceboards and IP interface boards recommended for the Iur interface, see Interface Boards Applicable toTerrestrial Interfaces.

10.3.9 Data Configuration Principles for the Iur Interface (over IP)Related information is required for performing data configuration on the IP-based Iur interface.This information refers to the protocol structure, links on the IP-based Iur interface, andconfiguration of paths for static SRNS relocation.

Protocol Stack on the Iur Interface (over IP)If IP transport is applied to the Iur interface, the sequence of configuring Iur interface data shouldbe consistent with the protocol structure, that is, from the bottom layer to the top layer and fromthe control plane to the user plane.

Figure 10-45 shows the protocol stack for the Iur interface.



141

Figure 10-45 Protocol stack for the IP-based Iur interface

The transport network layer of the IP-based Iur interface consists of the transport network layeruser plane (area A) and the transport network layer user plane (area C).

Links on the Iur Interface (over IP)If IP transport is applied to the Iur interface, there are two types of Iur links: M3UA link and IPpath.

Links on the Iur InterfaceFigure 10-46 shows the links on the Iur interface.



142

Figure 10-46 Links on the Iur interface (over IP)

NOTE

The RINT shown in Figure 10-46 refers to the IP interface boards of the BSC6900. For the IP interfaceboards recommended for the Iur interface, see Interface Boards Applicable to Terrestrial Interfaces.

M3UA Links

M3UA links are contained in an M3UA link set. The number of the M3UA link ranges from 0to 15.

The configuration of M3UA links depends on the network structure between the BSC6900 andthe neighboring BSC6900. The specifics are as follows:

l If the BSC6900 is directly connected to the neighboring BSC6900, the Iur interface requiresat least one M3UA link. It is recommended that more than one M3UA link be configured.

l If the BSC6900 is connected to the neighboring BSC6900 through a Signaling TransferPoint (STP), no M3UA link is required.

M3UA links are carried on SCTP links. It is recommended that the SCTP links be evenlydistributed to the CPUS subsystems in the MPS/EPS so that the signaling exchange can bereduced between the CPUS subsystems.

IP Path

An IP path is a group of connections to the adjacent node. The path ID ranges from 0 to 65535.

An Iur interface has at least one IP path. It is recommended that more than one IP path beconfigured.



143

Configuration Principles for Static Relocation Routes over IurThe IP routes on the Iur interface are used to forward the PS data during Serving Radio NetworkSubsystem (SRNS) relocation. During the SRNS relocation, the PS data is transferred from thelocal BSC6900 to the SGSN and then to the neighboring BSC6900. Therefore, the prerequisitesfor configuring IP routes on the Iur interface are that the IP paths between the local BSC6900and the SGSN, between the neighboring BSC6900 and the SGSN, and between the servingBSC6900 and the drift BSC6900 are configured.

Figure 10-47 shows the configuration of IP routes on the Iur interface. The IP routes configuredin multiple subsystems are similar.

Figure 10-47 IP route configuration on the Iur interface

NOTE

The RINT shown in Figure 10-47 refers to the interface boards of the BSC6900. For the ATM interfaceboards and IP interface boards recommended for the Iur interface, see Interface Boards Applicable toTerrestrial Interfaces.

10.3.10 Data Configuration Principles for the Iu-BC Interface (overATM)

Related information is required for performing data configuration on the Iu-BC interface. Thisinformation refers to the protocol structure, network structure, links on the Iu-BC interface, andthe IPoA configuration principle.

Protocol Structure for the Iu-BC Interface (over ATM)If ATM transport is applied to the Iu-BC interface, the sequence of configuring Iu-BC interfacedata should be consistent with the protocol structure, that is, from the bottom layer to the toplayer.

Figure 10-48 shows the protocol stack for the Iu-BC interface.



144

Figure 10-48 Protocol stack for the Iu-BC interface

Networking on the Iu-BC Interface (over ATM)

The BSC6900 connects to the CBC through an SGSN.

The connection between the BSC6900 and CBC through an SGSN can make full use of thephysical transport resources on the Iu-PS interface. Figure 10-49 shows the network structureon the Iu-BC interface.

Figure 10-49 Connection between the BSC6900 and CBC through an SGSN



145

Links on the Iu-BC Interface (over ATM)The Iu-BC interface has only one type of link: IPoA PVC.

Links on the Iu-BC InterfaceFigure 10-50 shows the links on the Iu-BC interface.

Figure 10-50 Links on the Iu-BC interface

NOTE

The RINT shown in Figure 10-50 refers to the ATM interface boards of the BSC6900. For the ATMinterface boards recommended for the Iu-BC interface, see Interface Boards Applicable to TerrestrialInterfaces.

IPoA PVCAn IPoA PVC must be configured on the Iu-BC interface for connecting the BSC6900 to theSGSN gateway because the CBC usually connects to the BSC6900 through an SGSN. In thissituation, the data on the Iu-BC interface is transmitted to the SGSN through the IPoA PVC andthen is routed to the CBC by the SGSN.

IPoA Data Configuration on the Iu-BC Interface (over ATM)The IPoA PVC configured on the Iu-BC interface enables the BSC6900 to indirectly connect tothe CBC.

IPoA PVC on the Iu-BC InterfaceOn the Iu-BC interface, the BSC6900 connects to the CBC through an SGSN, as shown inFigure 10-51.



146

Figure 10-51 IPoA configuration on the Iu-BC interface (through an SGSN)

NOTEThe RINT shown in Figure 10-51 refers to the ATM interface boards of the BSC6900. For the ATMinterface boards recommended for the Iu-BC interface, see Interface Boards Applicable to TerrestrialInterfaces.

IPoA Data on the Iu-BC InterfaceTable 10-22 describes the IPoA data to be configured on the Iu-BC interface.

Table 10-22 IPoA data on the Iu-BC interface

Item Description

Local IP address of the IPoA PVC Device IP address on the ATM interfaceboard of the BSC6900

Peer IP address of the IPoA PVC IP address of the gateway on the SGSN side

IPoA PVC between the interface board andthe gateway on the SGSN side

-

Route between the interface board carryingthe IPoA PVC and the network segment of thepeer SGSN

If the IP address of the interface boardcarrying the IPoA PVC and the destination IPaddress of the SGSN are located on differentsubnets, routes to the destination IP addressof the SGSN must be configured at theBSC6900.

10.3.11 Data Configuration Principles for the Iu-BC Interface (overIP)

Related information is required for performing data configuration on the IP-based Iu-BCinterface. This information refers to the protocol structure and network structure on the Iu-BCinterface.



147

Protocol Structure for the Iu-BC Interface (over IP)

If IP transport is applied to the Iu-BC interface, the sequence of configuring Iu-BC interfacedata should be consistent with the protocol structure, that is, from the bottom layer to the toplayer.

Figure 10-52 shows the protocol stack for the Iu-BC interface.

Figure 10-52 Protocol stack for the Iu-BC interface

Network Structure on the Iu-BC Interface (over IP)

This section describes the network structure between the BSC6900 and the CBC when IPtransport is applied to the Iu-BC interface.

Scenario

The BSC6900 communicates with the CBC through a data network.

Description

In this situation, the Iu-BC interface board of the BSC6900 can be FG2a/FG2c, GOUa/GOUc,or UOIa (UOIa_IP). The BSC6900 supports backup of these boards and also FE/GE port backupof FG2a/FG2c.

Figure 10-53 shows the network structure based on a data transport network. IP transport isapplied on the FE/GE ports.



148

Figure 10-53 IP network structure based on a data transport network

When IP transport is applied to the Iu interface, the BSC6900 and the CBC can directly accessthe IP bearer network, which enables connections over the Iu-BC interface. An Iu-BC interfacecan share an FE/GE port at the BSC6900 with an Iu interface, because of the low traffic on theIu-BC interface.

10.4 Data Configuration Principles for CellsThis section describes the configuration rules and reference information related to a cell.

10.4.1 Definitions of Sector, Carrier, and CellA sector is the smallest radio coverage area unit, which is covered by one or more radio carriers.Each radio carrier occupies a frequency. A sector and a carrier form a cell that is the smallestserving unit for UE access.

There are two types of sectors: omnidirectional sector and directional sector. Theomnidirectional sector provides coverage for small traffic. It covers the 360º circle area with theomnidirectional antenna in the center of the circle. As the traffic grows, the omnidirectionalsector is split into three or six directional sectors. The directional sectors are covered bydirectional antennas. For a 3-sector NodeB, each of the three directional antennas covers a 120ºsector area. For a 6-sector NodeB, each of the six directional antennas covers a 60º sector area.In fact, the azimuth of the antenna is greater than the theoretical value, and therefore there isoverlap between the sectors.

The number of cells supported by a NodeB is equal to the number of sectors multiplied by thenumber of carriers in each sector. Figure 10-54 shows the typical 3 x 2 configuration. The wholecircle area is split into three sectors: sector 0, sector 1, and sector 2. Each sector has two carriers,and each carrier forms a cell. Therefore, there are six cells in total.

Frequency reuse is allowed in a WCDMA system if different downlink primary scramblingcodes are used in neighboring cells of different sectors that use the same frequency. The differentdownlink primary scrambling codes lower the interference between cells.

Figure 10-54 shows the relations between sector, frequency, and cell.



149

Figure 10-54 Relations between sector, frequency, and cell

10.4.2 Definitions of Local Cell and Logical CellIn the 3GPP, a service-providing cell is referred to as a local cell when referring toimplementations, and as a logical cell when referring to logical resource management.

Local CellA local cell is a combination of physical resources, such as hardware resources and softwareresources, in a cell of a NodeB. A local cell is related to the physical implementation of a device.

NodeBs from different vendors have different ways of providing physical resources for cells.Therefore, the concept of logical cell is proposed by the 3GPP to ensure that the BSC6900 cancontrol the radio resources in certain cells through the standard Iub interface. These cells arecarried on NodeBs from different vendors.

Logical CellA logical cell is a standard logical model that helps the BSC6900 control the radio resources ina cell. The model is independent of local cell implementation and ensures that the Iub interfaceis an open interface. For details about the logical cell model, see Logical Cell Model.

The parameters of a local cell are configured at and managed by the NodeB. The parameters ofa logical cell are configured at and managed by the BSC6900. There is a one-to-one mappingbetween a logical cell and a local cell.



150

10.4.3 Logical Cell ModelThis section describes the logical cell model that guides the configuration of logical cells.

Figure 10-55 shows the logical cell configuration model. The number above the square is thequantity of the entities that serve as lower-level nodes. The number below the square is thequantity of the entities that serve as upper-level nodes.

Figure 10-55 Logical cell configuration model

NOTE

l P-CPICH: Primary Common Pilot Channel

l S-CPICH: Secondary Common Pilot Channel

l PSCH: Primary Synchronization Channel

l SSCH: Secondary Synchronization Channel

l P-CCPCH: Primary Common Control Physical Channel

l PICH: Paging Indicator Channel

l S-CCPCH: Secondary Common Control Physical Channel

l PRACH: Physical Random Access Channel

l AICH: Acquisition Indication Channel

l BCH: Broadcast Channel

l PCH: Paging Channel

l FACH: Forward Access Channel

l RACH: Random Access Channel

10.4.4 Areas of Logical CellsA logical cell must exist in a Location Area (LA), a Service Area (SA), a Routing Area (RA),and a UTRAN Registration Area (URA).

l A cell belongs to only one LA.l A cell belongs to only one RA.l A cell belongs to only one CS/PS SA.l A cell belongs to only one CBS SA.l A cell belongs to one to eight URAs.



151

10.4.5 Definition of Neighboring CellA neighboring cell is associated with a specific cell. There are three types of neighboring cellfor UMTS cells: intra-frequency neighboring cell, inter-frequency neighboring cell, andneighboring GSM cell.

l An intra-frequency neighboring cell is a cell that has overlapping coverage with the servingcell and uses the same carrier frequency as the serving cell.

l An inter-frequency neighboring cell is a cell that has overlapping coverage with the servingcell but uses a different carrier frequency from the serving cell.

l A neighboring GSM cell is a cell that is adjacent to the serving cell but belongs to a GSM,General Packet Radio Service (GPRS), or Enhanced Data rates for Global Evolution(EDGE) system.

10.5 Data Configuration Guidelines for SpecificationsThis document describes the specifications of the BSC6900.

Table 10-23 lists the specifications of the BSC6900.

Table 10-23 BSC6900 specifications

Item Specification

Maximum Number of Adjacent RNCs 25

Maximum Number of UMTS Cells 5100

Maximum Number of Neighboring GSM Cells 9600

Maximum Number of Neighboring GSM Cell Relationships 163200

Maximum Number of Neighboring UMTS Cells 7680

Maximum Number of Intra-Frequency Neighboring CellRelationships 163200

Maximum Number of Inter-Frequency Neighboring CellRelationships 326400

Maximum Number of Intra-Frequency Neighboring UMTSCells Supported by a UMTS Cell 32 (including the local cell)

Maximum Number of Inter-Frequency Neighboring UMTSCells Supported by a UMTS Cell 64

Maximum Number of Neighboring GSM Cells Supportedby a UMTS Cell 32

Number of OSPs Supported by an RNC 1

Number of DSPs 187

Maximum Number of MTP3 (MTP3 & MTP3b) Link Sets 187



152

Item Specification

Maximum Number of MTP (MTP3 & MTP3b) LinksSupported by an MTP Link Set 16

Maximum Number of MTP Links 2992

Maximum Number of MTP Routes 374

Number of SAAL NNI Links 2928

Number of SAAL UNI Links 12240

Maximum Number of SAAL UNI Links Supported by aCPUS 125

Maximum Number of SAAL NNI Links Supported by aCPUS 50

Maximum Number of MTP3 Links Supported by a CPUS 50

Maximum Number of SCTP Links Supported by a CPUS 150

Maximum Number of M3UA Links Supported by a CPUS 64

Maximum Number of M3UA Link Sets 187

Maximum Number of M3UA Links 2992

Maximum Number of M3UA Destination Entities 187

Maximum Number of M3UA Local Entities 187

Number of M3UA Routes 366

Maximum Number of STPs 32

Maximum Number of AAL2 Paths 13000

Maximum Number of IP Paths 13000

Maximum Number of AAL2 Paths and IP Paths 13000

Maximum Number of AAL2 Routes 200

Total Number of Routes 4096

Number of Routes on FG2c/GOUc/UOIc 512



153

Documents

BSC6900 UMTS Initial Configuration Guide(V900R013C00_03)(PDF)-En