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

BSC6900 UMTS V900R013C00

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 written consent 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.

Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase 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 representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd. Address:

Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website:

http://www.huawei.com

Email:

[email protected]

Issue 03 (2011-08-31)

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

i

BSC6900 UMTS Initial Configuration Guide

About This Document

About This Document Purpose This document describes the initial configuration of BSC6900.

Product Version The following table lists the product version related to this document. Product Name

Product Version

BSC6900

V900R013C00

Intended Audience This document is intended for: l

Field engineers

l

Network operators

l

System engineers

Organization 1 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 negotiation with other network elements. The negotiated data includes the global data, equipment data, interface data, base station data, and cell data. 4 Initial Configuration Procedures Issue 03 (2011-08-31)


ii


About This Document

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 the BSC6900. The typical configuration scripts concern global data, equipment data, network interfaces, base stations, and cells. 6 Configuring the Global Information This chapter describes how to configure the global information. The global data configuration provides a basis for all the other configurations, and therefore must be determined during network planning. After the BSC6900 global data configuration takes effect, do not modify it unless the network 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 configure the NodeB, UMTS cell, intra-frequency neighboring cell, inter-frequency neighboring cell, and neighboring GSM cell. 10 Configuration Reference Information This chapter describes the concepts, principles, rules, and conventions related to data configuration.

Conventions Symbol 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 not avoided, will result in death or serious injury. Indicates a hazard with a medium or low level of risk, which if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation, which if not avoided, could result in equipment damage, data loss, performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save time.

Issue 03 (2011-08-31)


iii


About This Document

Symbol

Description Provides additional information to emphasize or supplement important 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 in boldface. For example, log in as user root.

Italic

Book titles are in italics.

Courier New

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

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

Description

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 by vertical bars. One item is selected.

[ x | y | ... ]

Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected.

{ x | y | ... }*

Optional items are grouped in braces and separated by vertical bars. A minimum of one item or a maximum of all items can be selected.

[ x | y | ... ]*

Optional items are grouped in brackets and separated by vertical 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.

Issue 03 (2011-08-31)


iv


About This Document

Convention

Description

Boldface

Buttons, menus, parameters, tabs, window, and dialog titles are 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 means the two keys should be pressed in turn.

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

Issue 03 (2011-08-31)

Action

Description

Click

Select and release the primary mouse button without moving the pointer.

Double-click

Press the primary mouse button twice continuously and quickly without moving the pointer.

Drag

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


v


Contents

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.........................................................................................7 6.1 Configuring the Basic Information.....................................................................................................................8 6.2 Configuring the OPC and DPC..........................................................................................................................8 6.3 Configuring the Area Information....................................................................................................................10 6.4 Configuring the M3UA Local and Destination Entities...................................................................................10

7 Configuring the Equipment Data.............................................................................................11 7.1 Configuring the System Information................................................................................................................13 7.2 Configuring a Cabinet......................................................................................................................................13 7.3 Configuring a Subrack......................................................................................................................................13 7.4 Configuring a Board.........................................................................................................................................14 7.5 Configuring an EMU........................................................................................................................................15 7.6 Configuring the Clocks.....................................................................................................................................15 7.7 Configuring the Time.......................................................................................................................................17 7.8 Configuring the IP Address of the EMS Server...............................................................................................17 7.9 Configuring BSC Custom Alarm.....................................................................................................................17

8 Configuring the Interfaces.........................................................................................................19 8.1 Configuring the Iub Interface (over ATM).......................................................................................................21 8.1.1 Configuring the Physical Layer (over ATM)..........................................................................................21 8.1.2 Configuring the ATM Traffic Resources................................................................................................24 8.1.3 Configuring the Control Plane of the Iub Interface (over ATM)............................................................24 8.1.4 Configuring the Mapping Between Service Types and Transmission Resources...................................25 8.1.5 Configuring the User Plane of the Iub Interface (over ATM).................................................................25 8.1.6 Configuring the OM Channel over the Iub Interface (over ATM)..........................................................26 8.2 Configuring the Iub Interface (over IP)............................................................................................................26 Issue 03 (2011-08-31)


vi


Contents

8.2.1 Configuring the Physical Layer and Data Link Layer (over IP).............................................................27 8.2.2 Configuring the Control Plane for the Iub Interface (over IP)................................................................30 8.2.3 Configuring the Mapping Between Service Types and Transmission Resources...................................31 8.2.4 Configuring the User Plane over the Iub Interface (over IP)...................................................................32 8.2.5 Configuring an OM Channel over Iub Interface (over IP)......................................................................32 8.3 Configuring the Iub Interface (over ATM and IP)...........................................................................................33 8.4 Configuring the Iu-CS Interface (over ATM)..................................................................................................34 8.4.1 Configuring the Physical Layer (over ATM)..........................................................................................35 8.4.2 Configuring the Traffic Resource at the ATM Layer..............................................................................37 8.4.3 Configuring the Control Plane over the Iu-CS Interface (over ATM)....................................................38 8.4.4 Configuring the Mapping Between Service Types and Transmission Resources...................................39 8.4.5 Configuring the User Plane over the Iu-CS Interface (over ATM).........................................................39 8.5 Configuring the Iu-CS Interface (over IP)........................................................................................................39 8.5.1 Configuring the Physical Layer and Data Link Layer over IP................................................................40 8.5.2 Configuring the Control Plane over the Iu-CS Interface (over IP)..........................................................44 8.5.3 Configuring the Mapping Between Service Types and Transmission Resources...................................45 8.5.4 Configuring the User Plane over the Iu-CS Interface (over IP)..............................................................45 8.6 Configuring the Iu-PS Interface (over ATM)...................................................................................................46 8.6.1 Configuring the Physical Layer for the UOIa/UOIc Board.....................................................................46 8.6.2 Configuring the Traffic Resource at the ATM Layer..............................................................................46 8.6.3 Configuring the Control Plane over the Iu-PS Interface (over ATM).....................................................47 8.6.4 Configuring the Mapping Between Service Types and Transmission Resources...................................47 8.6.5 Configuring the User Plane over the Iu-PS Interface (over ATM).........................................................48 8.7 Configuring the Iu-PS Interface (over IP)........................................................................................................48 8.7.1 Configuring the Physical Layer and Data Link Layer over IP................................................................49 8.7.2 Configuring the Control Plane over the Iu-PS Interface (over IP)..........................................................53 8.7.3 Configuring the Mapping Between Service Types and Transmission Resources...................................54 8.7.4 Configuring the User Plane over the Iu-PS Interface (over IP)...............................................................54 8.8 Configuring the Iur Interface (over ATM).......................................................................................................55 8.8.1 Configuring the Physical Layer (over ATM)..........................................................................................55 8.8.2 Configuring the Traffic Resource at the ATM Layer..............................................................................58 8.8.3 Configuring the Control Plane over the Iur Interface (over ATM).........................................................58 8.8.4 Configuring the Mapping Between Service Types and Transmission Resources...................................59 8.8.5 Configuring the User Plane over the Iur Interface (over ATM)..............................................................59 8.8.6 Configuring a Static Transfer Path..........................................................................................................60 8.9 Configuring the Iur Interface (over IP).............................................................................................................61 8.9.1 Configuring the Physical Layer and Data Link Layer over IP................................................................61 8.9.2 Configuring the Control Plane over the Iur Interface (over IP)...............................................................65 8.9.3 Configuring the Mapping Between Service Types and Transmission Resources...................................66 8.9.4 Configuring the User Plane over the Iur Interface (over IP)...................................................................66 8.9.5 Configuring a Static Drift Path................................................................................................................67 8.10 Configuring the Iu-BC Interface (over ATM)................................................................................................68 Issue 03 (2011-08-31)


vii


Contents

8.10.1 Configuring the Physical Layer (over ATM)........................................................................................68 8.10.2 Configuring the Traffic Resource at the ATM Layer............................................................................71 8.10.3 Configuring the IPoA Data....................................................................................................................71 8.10.4 Configuring the CBS Address...............................................................................................................72 8.11 Configuring the Iu-BC Interface (over IP).....................................................................................................72 8.11.1 Configuring the Physical Layer and Data Link Layer over IP..............................................................72 8.11.2 Configuring the CBS Address...............................................................................................................76

9 Configuring the Cell Data.........................................................................................................77 9.1 Configuring a NodeB........................................................................................................................................79 9.2 Configuring a UMTS Cell................................................................................................................................79 9.3 Configuring an Intra-Frequency Neighboring Cell..........................................................................................80 9.4 Configuring an Inter-Frequency Neighboring Cell..........................................................................................81 9.5 Configuring a Neighboring GSM Cell.............................................................................................................82 9.6 Configuring a Neighboring LTE Cell...............................................................................................................82

10 Configuration Reference Information...................................................................................84 10.1 Data Configuration Principles for Equipment................................................................................................85 10.1.1 Configuration Rules of the Cabinets.....................................................................................................85 10.1.2 Configuration Rules of the Subracks.....................................................................................................85 10.1.3 Configuration Rules of the Boards........................................................................................................85 10.1.4 Configuration Rules of the Clock..........................................................................................................87 10.1.5 Introduction to Time Synchronization...................................................................................................88 10.2 Data Configuration Principles for Transmission............................................................................................88 10.2.1 Physical Layer Data Configuration Principles......................................................................................88 10.2.2 ATM Transport Modes..........................................................................................................................94 10.2.3 PVC Parameters of the ATM Layer......................................................................................................99 10.2.4 ATM Traffic Resource Configuration Principles................................................................................102 10.2.5 AAL2 Configuration Principles...........................................................................................................103 10.2.6 MTP3/M3UA Configuration Principles..............................................................................................104 10.2.7 TRM Configuration Principles............................................................................................................105 10.2.8 Activity Factor Configuration Principles............................................................................................106 10.3 Data Configuration Principles for Interfaces................................................................................................106 10.3.1 Data Configuration Principles for the Iub Interface (over ATM)........................................................106 10.3.2 Data Configuration Principles for the Iub Interface (over IP).............................................................110 10.3.3 Data Configuration Principles for the Iub Interface (over ATM and IP)............................................118 10.3.4 Data Configuration Principles for the Iu-CS Interface (over ATM)...................................................122 10.3.5 Data Configuration Principles for the Iu-CS Interface (over IP).........................................................127 10.3.6 Data Configuration Principles for the Iu-PS Interface (over ATM)....................................................133 10.3.7 Data Configuration Principles for the Iu-PS Interface (over IP).........................................................137 10.3.8 Data Configuration Principles for the Iur Interface (over ATM)........................................................138 10.3.9 Data Configuration Principles for the Iur Interface (over IP)..............................................................141 10.3.10 Data Configuration Principles for the Iu-BC Interface (over ATM).................................................144 10.3.11 Data Configuration Principles for the Iu-BC Interface (over IP)......................................................147 Issue 03 (2011-08-31)


viii


Contents

10.4 Data Configuration Principles for Cells.......................................................................................................149 10.4.1 Definitions of Sector, Carrier, and Cell...............................................................................................149 10.4.2 Definitions of Local Cell and Logical Cell.........................................................................................150 10.4.3 Logical Cell Model..............................................................................................................................151 10.4.4 Areas of Logical Cells.........................................................................................................................151 10.4.5 Definition of Neighboring Cell............................................................................................................152 10.5 Data Configuration Guidelines for Specifications........................................................................................152

Issue 03 (2011-08-31)


ix


1

1 Changes in the BSC6900 UMTS Initial Configuration Guide

Changes in the BSC6900 UMTS Initial Configuration 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 be configured 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: Issue 03 (2011-08-31)


1


1 Changes in the BSC6900 UMTS Initial Configuration Guide

Content

Description

UMTS Data Preparation for the Initial Configuration

The recommended configurations of some parameters are added.

Configuring the Clocks

The procedure for configuring the external clock, 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 new topics. Compared with issue 04 (2010-11-30) of V900R012C01, this issue incorporates the following changes: Content

Description

10.5 Data Configuration Guidelines for Specifications

The specifications are updated.

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

Issue 03 (2011-08-31)


2


2

2 Introduction to Initial Configuration

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 after the BSC6900 starts operating, see the RAN Reconfiguration Guide.

l

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

Issue 03 (2011-08-31)


3


3

3 Data Preparation for Initial Configuration

Data Preparation for Initial Configuration In the BSC6900 initial configuration, some data is obtained from the data sheets after negotiation with 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 for the Initial Configuration. For the restrictions on the parameter settings in MML commands, see BSC6900 UMTS MML Command Reference.

Issue 03 (2011-08-31)


4


4 Initial Configuration Procedures

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 UMTS Commissioning Guide.

Issue 03 (2011-08-31)


5


5 Typical Configuration Script

5

Typical Configuration Script

The typical configuration scripts used in this document derive from the documents related to the BSC6900. The typical configuration scripts concern global data, equipment data, network interfaces, base stations, and cells. For details of the BSC6900 typical configuration scripts, see the UMTS Typical Configuration Scripts.

Issue 03 (2011-08-31)


6


6

6 Configuring the Global Information

Configuring the Global Information

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

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

2.

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

3.

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

4.

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

Issue 03 (2011-08-31)


7



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

Prerequisite l

All the subracks are switched to the ineffective mode by running the SET CFGDATAINEFFECTIVE command.

l

The basic data is not configured.

Procedure Step 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, set Operator Type to PRIM(Primary Operator). Step 3 Optional: To configure more secondary UMTS operators, run the ADD UCNOPERATOR command 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 network number, run the SET SUBNET command to set the subnet number according to the network planning. Step 6 Optional: When the BSC6900 acts as the SCTP server, run the SET SCTPSRVPORT command to set the SCTP service listening ports. Step 7 Optional: Run the LST GLOBALROUTESW command to query the setting of the global route management switch. If the global route management function is not required but the global route management switch is set to ON, run the SET GLOBALROUTESW command to set the switch to OFF. ----End

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

Prerequisite l

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

l

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

Context

Issue 03 (2011-08-31)


8



routing between signaling links within that signaling link set. The result of the signaling route 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 all desired 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 the DSP 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). 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 the DSP 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 MGWs configured. The result of the bit AND operation on Signalling route mask and Signalling link mask, 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. Issue 03 (2011-08-31)


9



– Set DSP bear type to M3UA. ----End

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

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

Context l

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 tag range 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 command repeatedly. Step 4 Run the ADD UURA command to add a URA. To add more URAs, run this command repeatedly. 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 Entities This section describes how to configure the local and destination M3UA entities. You need to configure the M3UA entities when the IP-based networking is used.

Prerequisite The 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 Issue 03 (2011-08-31)


10


7

7 Configuring the Equipment Data

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.

Context Familiarize yourself with 10.1 Data Configuration Principles for Equipment before performing the operations described in this chapter. 1.

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

2.

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

3.

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

4.

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

5.

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

6.

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

7.

7.7 Configuring the Time This 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.

8.

7.8 Configuring the IP Address of the EMS Server

Issue 03 (2011-08-31)


11



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

Issue 03 (2011-08-31)

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


12



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


Context The system information consists of the system description, system ID, contact information of the vendor, system location, and system services.

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

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


Context The Main Processing Rack (MPR) is configured by default. You do not need to add it through the MML command.

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

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

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

Issue 03 (2011-08-31)


13



Context The Main Processing Subrack (MPS) is configured by default. You do not need to add this subrack by running an MML command.

Procedure Step 1 To add an Extended Processing Subrack (EPS) for the BSC6900, run the ADD SUBRACK command. 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 port on the SCU board in the MPS. Step 3 Run the SET CFGDATAEFFECTIVE command to set the subrack to effective mode. ----End

Follow-up Procedure To 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 power distribution 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. NOTE

If 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 switch on the PDB for input alarms.

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

Context l

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 this command repeatedly. Step 2 Optional: When the boards work in active/standby mode, run the SET MSP command to set the attributes of the Multiplex Section Protection (MSP). ----End Issue 03 (2011-08-31)


14



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

Prerequisite The subrack for housing the EMU is already configured.

Context l

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 Clocks This section describes how to configure the BSC6900 clocks. You need to configure the clock source of interface boards, clock source of the system, and work mode of the system clock source.


Context NOTE

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 local oscillator as default.

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

External clock An external clock can be a BITS clock or an external 8 kHz clock. When the clock source is an external clock, the BSC6900 receives the external clock from CLKIN0 or CLKIN1 on the GCUa/GCGa board.

l

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

l

GPS clock The GPS clock is the satellite synchronization clock. When the GCGa board is configured with a satellite card, the BSC6900 can use the satellite antenna port on the GCGa board to receive GPS clock signals.

Issue 03 (2011-08-31)


15



Procedure l

Configuring the external clock 1.

Run the ADD CLKSRC command to add a system clock source and the clock source priority. 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 to be set to BITS1-2MHZ or BITS2-2MHZ. l If the clock signals are extracted from the CN by the interface board in the MPS and then sent to the GCUa/GCGa board through the backplane of the MPS, Clock source type should be set to LINE1_8KHZ or LINE2_8KHZ. l If the clock signals are provided by the external BITS, Clock source type should be set 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, Clock source type should be set to GPS. l If the clock signals are provided by the external 8 kHz clock, Clock source type should be set to 8KHZ. l Clock source priority 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, and 4.

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) so that the system can switch to the highest-priority clock source when the current clock source is 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 clock sources.

2.

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

3.

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


l

Issue 03 (2011-08-31)

Configuring the GPS clock 1.

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

2.

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

3.

Run the SET CLKMODE command to set the work mode of the system clock source. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

16


7 Configuring the Equipment Data NOTE


----End

Follow-up Procedure To reconfigure the system clock source and clock source priority, run the SET CLKMODE command.

7.7 Configuring the Time This 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 SNTP synchronization 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 Server This section describes how to configure the IP address for the EMS server. The EMS server is used 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 Alarm This section describes how to configure alarm ports, alarm IDs, and alarm names of the BSC.

Prerequisite l Issue 03 (2011-08-31)

An environment monitoring unit and the sensor regarding environment alarms are installed. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

17


l


Data of the environment monitoring unit is configured. For details, see Configuring an EMU.

Context Each environment alarm is allocated a unique alarm ID. The IDs of the BSC environment alarms range 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, Alarm Severity, and Event Type. ----End

Issue 03 (2011-08-31)


18


8 Configuring the Interfaces

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.

Context Familiarize yourself with 10.2 Data Configuration Principles for Transmission before performing 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 Iub interface 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 interface between 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 over ATM/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-CS interface 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-CS interface 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-PS interface 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-PS interface between the BSC6900 and the PS domain. 8.8 Configuring the Iur Interface (over ATM) Issue 03 (2011-08-31)


19



This section describes how to configure the transport network layer of the ATM-based Iur interface 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 interface between 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-BC interface on the BSC6900 side. Perform this task only when the BSC6900 is directly connected to 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 interface between BSC6900 and the CBC. Perform this task only when the BSC6900 is directly connected to the CBC.

Issue 03 (2011-08-31)


20



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


Context Familiarize yourself with Interface Boards Applicable to Terrestrial Interfaces and Data Configuration Principles for the Iub Interface (over ATM) before performing the operations described in this section. This task configures only the transport network layer of the Iub interface. 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 side in ATM transmission mode. Before the configuration, specify the type of interface board according to network planning. Different interface boards are recommended for different interfaces. For details, see Interface Boards Applicable to Terrestrial Interfaces.

Configuring the Physical Layer for the AEUa Board This section describes how to configure the physical layer for the AEUa board, which is used as the interface board of the BSC6900.


Context When the AEUa board is used as the interface board of the BSC6900, the E1/T1 link can carry only one type of the following links: IMA link, UNI link, fractional IMA link, fractional ATM link, 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.

Issue 03 (2011-08-31)


21



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

Then...

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, perform this 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 command repeatedly. 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 is complete.

Step 6 Run the ADD FRALNK command to add a fractional ATM link. To add more fractional ATM links, 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 add a 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 is used as the interface board of the BSC6900.


Context l

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. Issue 03 (2011-08-31)

Run the LST E1T1 command to list the attributes of an E1/T1 link. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

22


2.



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 the interface board. Step 4 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 5.

UNI link

Go to Step 6.

Fractional IMA link

Go to Step 7.

Fractional ATM link

Go to Step 8.

Step 5 Add an IMA group and add IMA links to the IMA group. To add more IMA groups, perform the 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 is complete.

Step 6 Run the ADD UNILNK command to add a UNI link. To add more UNI links, repeat this command until all desired UNI links are added. Now this task is complete. Step 7 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 AOUc.

2.


Step 8 Run the ADD FRALNK command to add a fractional ATM link. To add more fractional ATM links, repeat this command until all desired fractional ATM links are added . Now this task is complete. ----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 is used as the interface board of the BSC6900.

Prerequisite The basic data of the BSC6900 is configured. For details, see Configuring the Basic Data. Issue 03 (2011-08-31)


23



Procedure Step 1 Set the optical port attributes. 1.


2.


----End

8.1.2 Configuring the ATM Traffic Resources This section describes how to configure the ATM traffic resources. You need to add the traffic record 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 traffic records, 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 BSC6900 in ATM transmission mode. You need to configure the SAAL UNI link, basic data and algorithm parameters of the NodeB, adjacent node, NCP, and CCP.

Prerequisite l

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.

l

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 interface must be controlled by the same CPUS subsystem.

l

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

Context

Procedure Step 1 Run the ADD SAALLNK command to add an SAAL link. Set Interface type to UNI. To add more SAAL links, run this command repeatedly. Issue 03 (2011-08-31)


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 more CCPs, run this command repeatedly. ----End

8.1.4 Configuring the Mapping Between Service Types and Transmission Resources This section describes how to configure the mapping between the service types and transmission resources for the adjacent node. You can configure the TRM mapping table and activity factor table for users with different priorities.


Procedure Step 1 Run the ADD TRMMAP command to add a TRM mapping table. To add more TRM mapping tables, 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 the ADD LOADEQ command to add a threshold table for load balancing between the primary and secondary paths. Step 4 Run the ADD ADJMAP command to configure the TRM mapping table and activity factor table for 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 in ATM transmission mode. You need to configure the logical port, AAL2 path, and AAL2 route.

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

Procedure Step 1 Optional: When the ATM traffic shaping and backpressure-based congestion control functions are enabled, run the ADD ATMLOGICPORT command to add an ATM logical port. Issue 03 (2011-08-31)


25



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

8.1.6 Configuring the OM Channel over the Iub Interface (over ATM) This section describes how to configure the OM channel over the Iub interface on the BSC6900 side in ATM transmission mode. You need to configure the device IP address of an interface board, the IPoA PVC between the BSC6900 and a NodeB, and the OM IP address of the NodeB.

Prerequisite l

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, see Configuring the Control Plane of the Iub Interface (over ATM).

l

The user plane of the ATM-based Iub interface is configured. For details, see Configuring the 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 NodeB TransType 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 interface between the BSC6900 and a NodeB.


Context Familiarize yourself with Interface Boards Applicable to Terrestrial Interfaces and Data Configuration Principles for the Iub Interface (over IP) before performing the operations described in this section. This task configures only the transport network layer on the Iub interface. To enable the cells under the NodeB to provide services, you also need to set the cellrelated parameters. Issue 03 (2011-08-31)


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 interface on the BSC6900 in IP transmission mode. Before the configuration, specify the type of interface board according to network planning. Different interface boards are recommended for different interfaces. For details, see Interface Boards Applicable to Terrestrial Interfaces.

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 the 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 of the 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 case of logical IP networking. Step 4 Check whether the link aggregation function is required and then perform the corresponding step. 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 the Ethernet port. When multiple VLAN gateways are planned, repeat this step until all the IP addresses are added. Step 6 Optional: Run the ADD VLANID command to add an IP address to the VLAN ID mapping table. 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.

Issue 03 (2011-08-31)


27


2.


Run the ADD ETHTRKLNK command to add a link to the link aggregation group. To add more links to the link aggregation group, repeat this step until all desired links are added. NOTE

l You can run the DSP ETHTRKLNK command to query the status of a link in a link aggregation group 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 in active/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 peer end. 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 are added.

----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 and device IP address, and configure the PPP link, MP link group, and MP link.


Context The MP link group is also referred to as PPP link group. Either a PPP link or an MP link group must be configured.



2.


Step 2 Optional: Run the ADD DEVIP command to add the device IP address of the board in the case of logical IP networking. Step 3 Determine the type of link carried on the E1/T1 link (PPP link or MP link group) and perform the 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. Issue 03 (2011-08-31)


28



Run the ADD PPPLNK command to add a PPP link. To add more PPP links, run this command repeatedly. 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 this command repeatedly. Set Board type to PEUa.

----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/T1 attributes, optical port attributes, and attributes of a channelized optical port. In addition, you need to configure the PPP link, MP link group, and MP link.





2.




2.


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 the interface board. Step 4 Run the ADD DEVIP command to add the device IP address of the interface board. Step 5 Determine the type of link carried on the E1/T1 link (PPP link or MP link group) and perform the corresponding step. Issue 03 (2011-08-31)


29



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

Then...

PPP link

Go to Step 6.

MP link group

Go to Step 7.

Step 6 Configure a PPP link. Run the ADD PPPLNK command to add a PPP link. To add more PPP links, run this command repeatedly. In this step: l Set Board type to POUa or POUc. l It is recommended that Borrow DevIP be set to YES. Step 7 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 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.




2.


Step 2 Run the ADD DEVIP command to add the device IP address of the interface board. Step 3 Run the ADD PPPLNK command to add a PPP link. To add more PPP links, run this command repeatedly. 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 BSC6900 in 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. Issue 03 (2011-08-31)


30



Prerequisite The 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).

Context l

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 links should increase with the number of CCP links.

l

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

Procedure Step 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 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 mode is used between the BSC6900 and the NodeB. To add more IP routes, repeat this step until all desired 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 to SCTP. Step 6 Run the ADD UCCP command to add a CCP link. In this step, set Bearing link type to SCTP. To add more CCP links, repeat this step until all desired CCP links are added. ----End



Issue 03 (2011-08-31)


31



Procedure Step 1 Run the ADD TRMMAP command to add a TRM mapping table. To add more TRM mapping tables, 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 the ADD LOADEQ command to add a threshold table for load balancing between the primary and secondary paths. Step 4 Run the ADD ADJMAP command to configure the TRM mapping table and activity factor table for users with different priorities. ----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 in IP transmission mode. You need to configure the logical port, IP path, and IP route.

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

Procedure Step 1 Optional: When the RAN sharing function is used, run the ADD IPLOGICPORT command to add a logical port. Step 2 Run the ADD IPPATH command to add an IP path. To add more IP paths, run this command repeatedly. Step 3 Optional: Run the ADD IPRT command to add an IP route when the layer 3 networking mode is used between the BSC6900 and the NodeB. To add more IP routes, run this command repeatedly. Step 4 Optional: Run the LST GLOBALROUTESW command to query the value of the global route management switch. If the global route management function is not required but the global route management switch is set to ON, run the SET GLOBALROUTESW command to set the global route 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 the BSC6900 in IP transmission mode. You need to configure the OM IP address for the NodeB, electrical serial number (ESN), and detection function.

Prerequisite The control plane of the IP-based Iub interface is configured. For details, see Configuring the Control Plane of the Iub Interface (over IP). Issue 03 (2011-08-31)


32



Context l

Dynamic Host Configuration Protocol (DHCP) is a client-server networking protocol. A DHCP server provides configuration parameters specific to the request of the DHCP client host, such as, information required by the host to access the Internet. DHCP also provides a mechanism for allocating addresses to hosts.

l

This function enables the NodeB to know the VLAN ID broadcast by the BSC6900 on the network when the NodeB starts operating or becomes faulty. As a result, the NodeB can start 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 the BSC6900 and the NodeB, run the STR UNODEBDETECT command to start the NodeB detection 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 over ATM/IP dual stack between the BSC6900 and a NodeB.


Context l

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

l

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

l

All the data of a NodeB, including data associated with cells and links, should be controlled by 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 the Physical Layer (over ATM).

2.

Configure the ATM traffic resources. For details, see Configuring the ATM Traffic Resources.

Issue 03 (2011-08-31)


33



Step 2 Configure the physical layer and the data link layer in IP transmission mode. For details, see Configuring 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 the Iub Interface (over ATM). l If IP transport is applied to the control plane, see Configuring the Control Plane of the Iub Interface (over IP). Step 4 Configure the TRM mapping for the adjacent nodes. For details, see Configuring the Mapping Between 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 Iub Interface (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 following steps: – Run the ADD DEVIP and ADD IPOAPVC commands to set up an IPoA PVC, which is 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 the Iub Interface (over ATM). l If IP transport is applied to the OM channel, see Configuring the OM Channel over the Iub Interface (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-CS interface between the BSC6900 and the CS domain.


Context l

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 Data Configuration Principles for the Iu-CS Interface (over ATM) before performing the operations described in this section. This task configures only the transport network layer of the ATM-based Iu-CS interface.

Issue 03 (2011-08-31)


34









2.



Then...

IMA link

Go to Step 3.

UNI link

Go to Step 4.

Fractional IMA link

Go to Step 5.

Fractional ATM link

Go to Step 6.


Go to Step 7.



2.


Step 4 Run the ADD UNILNK command to add a UNI link. To add more UNI links, run this command repeatedly. Now this task is complete. Step 5 To add a fractional IMA link, perform the following steps: Issue 03 (2011-08-31)


35



1.


2.





Context l


l




2.




2.



Then...

IMA link

Go to Step 5.

UNI link

Go to Step 6.

Fractional IMA link

Go to Step 7.

Issue 03 (2011-08-31)


36




Then...

Fractional ATM link

Go to Step 8.



2.




2.







2.


----End

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



37




8.4.3 Configuring the Control Plane over the Iu-CS Interface (over ATM) This section describes how to configure the control plane of the Iu-CS interface on the BSC6900 in ATM transmission mode. You need to configure the SAAL link, MTP3 data, adjacent node, and CN node.

Prerequisite l

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, see Configuring the Physical Layer (over ATM).

l


Procedure Step 1 Run the ADD SAALLNK command to add an SAAL link. Set Interface type to NNI. To add more 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 this command repeatedly. Step 4 Run the ADD MTP3LNK command to add an MTP3 link. To add more MTP3 links, run this command repeatedly. Step 5 Run the ADD ADJNODE command to add an adjacent node and set the appropriate TRM mapping 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 to CS_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

Issue 03 (2011-08-31)


38





Procedure Step 1 Run the ADD TRMMAP command to add a TRM mapping table. To add more TRM mapping tables, run this command repeatedly. Step 2 Run the ADD TRMFACTOR command to add an activity factor table. Step 3 Run the ADD ADJMAP command to configure the TRM mapping table and activity factor table for users with different priorities. ----End

8.4.5 Configuring the User Plane over the Iu-CS Interface (over ATM) This section describes how to configure the user plane of the Iu-CS interface on the BSC6900 in ATM transmission mode. You need to configure the AAL2 path and AAL2 route.

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

Procedure Step 1 Run the ADD AAL2PATH command to add an AAL2 path. To add more AAL2 paths, repeat this step until all desired AAL2 paths are added. Step 2 Run the ADD AAL2RT command to add an AAL2 route. In this step, set Destination ATM address to the ATM address of the MGW. To add more AAL2 routes, repeat this step until all desired 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-CS interface between the BSC6900 and the CS domain.

Prerequisite The OPC is configured. For details, see Configuring the OPC and DPC. Issue 03 (2011-08-31)


39



Context l

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 operations described in this section. This task configures only the transport network layer of the IPbased Iu-CS interface.

8.5.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 interface on the BSC6900 in IP transmission mode. Before the configuration, specify the type of interface board according to network planning. Different interface boards are recommended for different interfaces. For details, see Interface Boards Applicable to Terrestrial Interfaces.





2.



Then...


Go to Step 5.


Go to Step 7.

Step 5 In link non-aggregation mode, run the ADD ETHIP command to add the IP address of the Ethernet port. When multiple VLAN gateways are planned, repeat this step until all the IP addresses are added. Issue 03 (2011-08-31)


40



Step 6 Optional: Run the ADD VLANID command to add an IP address to the VLAN ID mapping table. Step 7 In link aggregation mode, complete the following steps: 1.



2.



3.


----End






2.


Step 2 Optional: Run the ADD DEVIP command to add the device IP address of the board in the case of logical IP networking. Step 3 Determine the type of link carried on the E1/T1 link (PPP link or MP link group) and perform the corresponding step. Issue 03 (2011-08-31)


41



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. Run the ADD PPPLNK command to add a PPP link. To add more PPP links, run this command repeatedly. 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.


2.


----End






2.




2.


Issue 03 (2011-08-31)


42



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 the interface board. Step 4 Run the ADD DEVIP command to add the device IP address of the interface board. Step 5 Determine the type of link carried on the E1/T1 link (PPP link or MP link group) and perform the corresponding step. If the E1/T1 link carries a/an...

Then...

PPP link

Go to Step 6.

MP link group

Go to Step 7.



2.


----End





2.


Step 2 Run the ADD DEVIP command to add the device IP address of the interface board. Step 3 Run the ADD PPPLNK command to add a PPP link. To add more PPP links, run this command repeatedly. In this step: l Set Board type to UOIa. l It is recommended that Borrow DevIP be set to YES. ----End Issue 03 (2011-08-31)


43



8.5.2 Configuring the Control Plane over the Iu-CS Interface (over IP) This section describes how to configure the control plane of the Iu-CS interface on the BSC6900 in IP transmission mode. You need to configure the SCTP link, M3UA data, adjacent node, CN domain, and CN node.

Prerequisite l


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 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. 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 Local entity type is set to M3UA_ASP and Destination entity type is not set to M3UA_SP, Work mode 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 running the 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 this step 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 mode is used between the BSC6900 and the CS domain. To add more IP routes, repeat this step until all desired IP routes are added. Step 6 Run the ADD ADJNODE command to add an adjacent node and set the appropriate TRM mapping 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 to CS_DOMAIN. Step 8 Run the ADD UCNNODE command to add a CN node. In this step: l Set CN domain ID to CS_DOMAIN. Issue 03 (2011-08-31)


44



l Set IU trans bearer type to IP_TRANS. ----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 the BSC6900 side. You need to configure the IP path and IP route.

Prerequisite The control plane is configured over the IP-based Iu-CS interface. For details, see Configuring the 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 subnet mask be set to 255.255.255.0. To add more IP paths, repeat this step until all desired IP paths are added. Step 2 Optional: Run the ADD IPRT command to add an IP route when the layer 3 networking mode is used between the BSC6900 and the CS domain. To add more IP routes, repeat this step until all desired IP routes are added. Step 3 Optional: Run the LST GLOBALROUTESW command to query the value of the global route management switch. If the global route management function is not required but the global route management switch is set to ON, run the SET GLOBALROUTESW command to set the global route management switch to OFF. ----End Issue 03 (2011-08-31)


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-PS interface between the BSC6900 and the PS domain.


Context l

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 the operations described in this section. This task configures only the transport network layer of the ATM-based Iu-PS interface.

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




2.


----End



Procedure Step 1 Run the ADD ATMTRF command to add an ATM traffic record. To add more ATM traffic records, run this command repeatedly. ----End Issue 03 (2011-08-31)


46



8.6.3 Configuring the Control Plane over the Iu-PS Interface (over ATM) This section describes how to configure the control plane of the Iu-PS interface on the BSC6900 in ATM transmission mode. You need to configure the SAAL link, MTP3 data, adjacent node, and CN node.

Prerequisite l


l

The physical layer of the ATM-based Iu-PS interface is configured. For details, see Configuring the Physical Layer (over ATM).

l


Procedure Step 1 Run the ADD SAALLNK command to add an SAAL link. In this step, set Interface type to NNI. 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. NOTE

When 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, repeat this 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, repeat this step until all desired MTP3 links are added. Step 5 Run the ADD ADJNODE command to add an adjacent node and set the appropriate TRM mapping 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 ID to PS_DOMAIN. Step 7 Run the ADD UCNNODE command to add a CN node. In this step, set CN domain ID to PS_DOMAIN. ----End




47




8.6.5 Configuring the User Plane over the Iu-PS Interface (over ATM) This section describes how to configure the user plane of the ATM-based Iu-PS interface on the BSC6900 side. You need to configure the device IP address, IPoA PVC, IP path, and IP route.

Prerequisite The control plane is configured over the ATM-based Iu-PS interface. For details, see Configuring the 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 carries the 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 subnet mask be set to 255.255.255.0. To add more IP paths, run this command repeatedly.

CAUTION When the IP path is carried on the IPoA PVC, the bandwidth of the IP path cannot be higher than 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 mode is used between the BSC6900 and the PS domain. To add more IP routes, run this command repeatedly. ----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-PS interface between the BSC6900 and the PS domain. Issue 03 (2011-08-31)


48



Prerequisite l

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.

l

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 operations described in this section. This task configures only the transport network layer of the IPbased Iu-PS interface.

Context






2.



Then...


Go to Step 5.

Issue 03 (2011-08-31)


49



If you select...

Then...


Go to Step 7.




2.



3.


----End






50


2.




Then...

PPP link

Go to Step 4.

MP link group

Go to Step 5.



2.


----End






51


2.





2.



Then...

PPP link

Go to Step 6.

MP link group

Go to Step 7.



2.


----End





2.


Issue 03 (2011-08-31)


52




8.7.2 Configuring the Control Plane over the Iu-PS Interface (over IP) This section describes how to configure the control plane of the Iu-PS interface on the BSC6900 in IP transmission mode. You need to configure the SCTP link, M3UA data, adjacent node, CN domain, and CN node.

Prerequisite l


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).

Procedure Step 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. 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 Local entity type is set to M3UA_ASP and Destination entity type is not set to M3UA_SP, Work mode of the M3UA link set must be set to M3UA_ASP. NOTE


Step 3 Run the ADD M3RT command to add an M3UA route. 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 mode is used between the BSC6900 and the PS domain. To add more IP routes, repeat this step until all desired IP routes are added. Step 6 Run the ADD ADJNODE command to add an adjacent node and set the appropriate TRM mapping table and activity factor table for users with different priorities. In this step: Issue 03 (2011-08-31)


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 ID to PS_DOMAIN. Step 8 Run the ADD UCNNODE command to add a CN node. In this step, set CN domain ID to PS_DOMAIN. ----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 the BSC6900 side. You need to configure the IP path and IP route.

Prerequisite The control plane is configured over the IP-based Iu-PS interface. For details, see Configuring the 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 subnet mask be set to 255.255.255.0. Peer IP address is set to the IP address of the SGSN. To add more 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.

Issue 03 (2011-08-31)


54



Step 2 Optional: Run the ADD IPRT command to add an IP route when the layer 3 networking mode is used between the BSC6900 and the PS domain. To add more IP routes, repeat this step until all desired IP routes are added. Step 3 Optional: Run the LST GLOBALROUTESW command to query the value of the global route management switch. If the global route management function is not required but the global route management switch is set to ON, run the SET GLOBALROUTESW command to set the global route management switch to OFF. ----End

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


Context l

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 Data Configuration Principles for the Iur Interface (over ATM) before performing the operations described in this section. This task configures only the transport network layer of the ATMbased Iur interface.




Context When the AEUa board is used as the interface board of the BSC6900, the E1/T1 link can carry only one type of the following links: IMA link, UNI link, fractional IMA link, fractional ATM link, and timeslot cross connection. Issue 03 (2011-08-31)


55





2.



Then...

IMA link

Go to Step 3.

UNI link

Go to Step 4.

Fractional IMA link

Go to Step 5.

Fractional ATM link

Go to Step 6.


Go to Step 7.



2.




2.





Issue 03 (2011-08-31)


56



Context l


l




2.




2.



Then...

IMA link

Go to Step 5.

UNI link

Go to Step 6.

Fractional IMA link

Go to Step 7.

Fractional ATM link

Go to Step 8.



2.




2.


Issue 03 (2011-08-31)


57








2.


----End




8.8.3 Configuring the Control Plane over the Iur Interface (over ATM) This section describes how to configure the control plane of the ATM-based Iur interface. You need to configure the SAAL link, basic data of the neighboring BSC6900, MTP3 data, and adjacent node.

Prerequisite l


l

The physical layer of the ATM-based Iur interface is configured. For details, see Configuring the Physical Layer (over ATM).

Issue 03 (2011-08-31)


58


l



Procedure Step 1 Run the ADD SAALLNK command to add an SAAL link. Set Interface type to NNI. To add more SAAL links, run this command repeatedly. Step 2 Run the ADD UNRNC command to add the basic data of the neighboring BSC6900. To configure 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 this command repeatedly. Step 5 Run the ADD MTP3LNK command to add an MTP3 link. To add more MTP3 links, run this command repeatedly. Step 6 Run the ADD ADJNODE command to add an adjacent node and set the appropriate TRM mapping 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




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 in ATM transmission mode. Issue 03 (2011-08-31)


59



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

Procedure Step 1 Run the ADD AAL2PATH command to add an AAL2 path. To add more AAL2 paths, repeat this step until all desired AAL2 paths are added. ----End

8.8.6 Configuring a Static Transfer Path This section describes how to configure a path for SRNC relocation. To reduce the bandwidth occupied by the Iur interface and the transmission delay on the user plane, static SRNC relocation can be performed.

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

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 the SGSN. 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.

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

Issue 03 (2011-08-31)


60



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


Context l

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 operations described in this section. This task configures only the transport network layer of the IPbased Iur interface.






2.


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 case of logical IP networking. Issue 03 (2011-08-31)


61



Step 4 Check whether the link aggregation function is required and then perform the corresponding step. If you select...

Then...


Go to Step 5.


Go to Step 7.




2.



3.


----End



Context The MP link group is also referred to as PPP link group. Either a PPP link or an MP link group must be configured. Issue 03 (2011-08-31)


62





2.



Then...

PPP link

Go to Step 4.

MP link group

Go to Step 5.



2.


----End



Context The MP link group is also referred to as PPP link group. Either a PPP link or an MP link group must be configured. Issue 03 (2011-08-31)


63





2.




2.



Then...

PPP link

Go to Step 6.

MP link group

Go to Step 7.



2.


----End



Procedure Step 1 Set the optical port attributes. Issue 03 (2011-08-31)


64



1.


2.



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 BSC6900 in IP transmission mode. You need to configure the SCTP link, basic data of the neighboring BSC6900, M3UA data, and adjacent node.

Prerequisite l


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 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. Step 2 Run the ADD UNRNC command to add the basic data of the neighboring BSC6900. In this step: l Set Iur Interface Existing Indication to TRUE. l Set IUR trans bearer type to IP_TRANS. Step 3 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 Local entity type is set to M3UA_ASP and Destination entity type is not set to M3UA_SP, Work mode of the M3UA link set must be set to M3UA_ASP. NOTE


Issue 03 (2011-08-31)


65



Step 4 Run the ADD M3RT command to add an M3UA route. Step 5 Run the ADD M3LNK command to add an M3UA link. To add more M3UA links, repeat this step 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 mode is used between BSC6900s. To add more IP routes, repeat this step until all desired IP routes are added. Step 7 Run the ADD ADJNODE command to add an adjacent node and set the appropriate TRM mapping 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




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 the BSC6900 side. You need to configure the IP path and IP route.

Prerequisite The control plane is configured over the IP-based Iur interface. For details, see Configuring the Control 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 subnet mask be set to 255.255.255.0. To add more IP paths, repeat this step until all desired IP paths are added. Issue 03 (2011-08-31)


66



Step 2 Optional: Run the ADD IPRT command to add an IP route when the layer 3 networking mode is used between BSC6900s. To add more IP routes, repeat this step until all desired IP routes are added. Step 3 Optional: Run the LST GLOBALROUTESW command to query the value of the global route management switch. If the global route management function is not required but the global route management switch is set to ON, run the SET GLOBALROUTESW command to set the global route management switch to OFF. ----End

8.9.5 Configuring a Static Drift Path This section describes how to configure a path for SRNC relocation. To reduce the bandwidth occupied by the Iur interface and the transmission delay on the user plane, static SRNC relocation can be performed.

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

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 the SGSN. 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.

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

Issue 03 (2011-08-31)


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-BC interface on the BSC6900 side. Perform this task only when the BSC6900 is directly connected to the CBC.


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







2.


Step 2 Determine the type of link carried on the E1/T1 link. Issue 03 (2011-08-31)


68




Then...

IMA link

Go to Step 3.

UNI link

Go to Step 4.

Fractional IMA link

Go to Step 5.

Fractional ATM link

Go to Step 6.


Go to Step 7.



2.




2.





Context l


l


Procedure Step 1 Set the E1/T1 link attributes. Issue 03 (2011-08-31)


69



1.


2.




2.



Then...

IMA link

Go to Step 5.

UNI link

Go to Step 6.

Fractional IMA link

Go to Step 7.

Fractional ATM link

Go to Step 8.



2.




2.






70





2.


----End




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

Prerequisite l

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.

Context For details about principles for IPoA configuration on the Iu-BC interface, see IPoA Data Configuration 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 the SGSN. 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. Issue 03 (2011-08-31)


71



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

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

Context The CBS address is an IP address used for the communication between the CBC and the BSC6900.

Procedure Step 1 Run the ADD UCBSADDR command to add the data related to cell broadcast, such as the CBS address. ----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 interface between BSC6900 and the CBC. Perform this task only when the BSC6900 is directly connected to the CBC.

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

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


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 the Issue 03 (2011-08-31)


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 of the link aggregation group, and add the device IP address.




2.



Then...


Go to Step 5.


Go to Step 7.




2.



Issue 03 (2011-08-31)


73


3.



----End






2.



Then...

PPP link

Go to Step 4.

MP link group

Go to Step 5.



Issue 03 (2011-08-31)


74


2.



----End






2.




2.



Then...

PPP link

Go to Step 6.

MP link group

Go to Step 7.

Step 6 Configure a PPP link. Run the ADD PPPLNK command to add a PPP link. To add more PPP links, run this command repeatedly. In this step: l Set Board type to POUa or POUc. l It is recommended that Borrow DevIP be set to YES. Issue 03 (2011-08-31)


75



Step 7 Add an MP link group. 1.


2.


----End





2.



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

Context The CBS address is an IP address used for the communication between the CBC and the BSC6900.

Procedure Step 1 Run the ADD UCBSADDR command to add the data related to cell broadcast, such as the CBS address. ----End Issue 03 (2011-08-31)


76


9 Configuring the Cell Data

9

Configuring the Cell Data

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

Context l

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 Initial Configuration in the M2000-CME document disk.

l

Familiarize yourself with 10.4 Data Configuration Principles for Cells before performing the operations described in this chapter. NOTE

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

1.

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

2.

9.2 Configuring a UMTS Cell This 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.

3.

9.3 Configuring an Intra-Frequency Neighboring Cell This section describes how to configure an intra-frequency neighboring cell. This task is required when intra-frequency neighboring cells are planned for the local cell during BSC6900 initial configuration.

4.

9.4 Configuring an Inter-Frequency Neighboring Cell This section describes how to configure an inter-frequency neighboring cell. This task is required when inter-frequency neighboring cells are planned for the local cell during BSC6900 initial configuration.

5.

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

Issue 03 (2011-08-31)


77


6.

Issue 03 (2011-08-31)


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


78



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

Prerequisite l

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 (over ATM).

l

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

l

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

Context This 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 the NodeB. Step 4 Run the ADD UNODEBOLC command to add overload algorithm parameters for the NodeB. ----End

9.2 Configuring a UMTS Cell This 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.

Prerequisite l

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 the Equipment Data.

l

The transport layer of the BSC6900 is configured.

Issue 03 (2011-08-31)


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 Cell This section describes how to configure an intra-frequency neighboring cell. This task is required when intra-frequency neighboring cells are planned for the local cell during BSC6900 initial configuration.

Prerequisite l


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 performing this task.

l

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 an intra-frequency neighboring cell of cell B. If yes, configure cell A as an intra-frequency neighboring cell of cell B on the BSC6900 that controls cell B.

l

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

l

If a specified cell and the local cell are controlled by the same BSC6900, perform the following step:

Context

Procedure

1. l

Issue 03 (2011-08-31)

Run the ADD UINTRAFREQNCELL command to add the specified cell as an intrafrequency neighboring cell of the local cell.

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 UNRNCURA command to add the URA information of the intra-frequency neighboring BSC6900. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

80


3.


Run the ADD UINTRAFREQNCELL command to add the specified cell as an intrafrequency neighboring cell of the local cell.

----End

9.4 Configuring an Inter-Frequency Neighboring Cell This section describes how to configure an inter-frequency neighboring cell. This task is required when inter-frequency neighboring cells are planned for the local cell during BSC6900 initial configuration.

Prerequisite l


l

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

l

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

l

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 inter-frequency neighboring cell of cell A, check whether cell A should also be an inter-frequency neighboring cell of cell B. If yes, configure cell A as an inter-frequency neighboring cell of cell B on the BSC6900 that controls cell B.

l

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

l

If a specified cell and the local cell are controlled by the same BSC6900, perform the following step:

Context

Procedure

1. l

Run the ADD UINTERFREQNCELL command to add the specified cell as an interfrequency neighboring cell of the local cell.

If a specified cell and the local cell are controlled by different BSC6900s, perform the following steps: 1.

Run the ADD UEXT3GCELL command to add a cell.

2.

Optional: If the URA information is not configured for the inter-frequency neighboring BSC6900 that controls the specified cell, run the ADD UNRNCURA command to add the URA information of the inter-frequency neighboring BSC6900.

3.

Run the ADD UINTERFREQNCELL command to add the specified cell as an interfrequency neighboring cell of the local cell.

----End Issue 03 (2011-08-31)


81



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

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

Context l

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

l

In the BSC6900, the neighbor relation is unidirectional. Therefore, after the configuration in 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 serving cell. ----End

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

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

Context l

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 the configuration in this task, LTE 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 LTE cell B.

Procedure Step 1 Run the ADD ULTECELL command to add a LTE cell. Issue 03 (2011-08-31)


82



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

Issue 03 (2011-08-31)


83


10

10 Configuration Reference Information

Configuration Reference Information

About This Chapter This chapter describes the concepts, principles, rules, and conventions related to data configuration. 10.1 Data Configuration Principles for Equipment This section describes the configuration rules and reference information related to the BSC6900 equipment. 10.2 Data Configuration Principles for Transmission This section describes the configuration rules and reference information related to the data transmission of the BSC6900. 10.3 Data Configuration Principles for Interfaces This section describes the configuration rules and reference information related to the BSC6900 interfaces. 10.4 Data Configuration Principles for Cells This section describes the configuration rules and reference information related to a cell. 10.5 Data Configuration Guidelines for Specifications This document describes the specifications of the BSC6900.

Issue 03 (2011-08-31)


84



10.1 Data Configuration Principles for Equipment This section describes the configuration rules and reference information related to the BSC6900 equipment.

10.1.1 Configuration Rules of the Cabinets This 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 the MML command.

l

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

10.1.2 Configuration Rules of the Subracks This section describes the configuration rules and reference information related to the BSC6900 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 this subrack by running the MML command.

l

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

l

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

l

The actual board type in a subrack must be consistent with the configured type. The subrack number 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 the SCU board in the MPS.

l

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

10.1.3 Configuration Rules of the Boards This section describes the configuration rules and reference information related to the BSC6900 boards.

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

Issue 03 (2011-08-31)


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

Operation and Maintenance Unit (OMU)

OMUa/OMUc

OAM

Service Aware Unit (SAU)

SAUa/SAUc

SAU

RUCP

Functions of boards The BSC6900 boards provide different functions when being loaded with different software, as described in Table 10-2. Table 10-2 Functions of boards

Issue 03 (2011-08-31)


Description

OAM

Operation and maintenance management

UCP

All the subsystems are configured as CPU for Service (CPUS) subsystems, which are used to process the services in the control plane of the UMTS RNC.

RUCP

Subsystem 0 is configured as the MPU subsystem, which is used to manage resources. All the other subsystems are configured as CPUS subsystems, which are used to process the services in the control plane of the UMTS RNC.

UUP

UMTS RNC user plane processing

ATM

ATM interface processing

IP

IP interface processing


86




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 subsystem in 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 is recommended that you configure one SPUb board of the RGCP type out of every two pairs of XSPUb boards. l It is recommended that service processing boards and interface boards be evenly distributed in each subrack to reduce data exchanging between subracks. l It is recommended that interface boards, XPU boards, and DPU boards be evenly distributed in each subrack.

10.1.4 Configuration Rules of the Clock This section describes the configuration rules and reference information related to the BSC6900 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 be turned on at the same time.

l

If both data and voice services are carried by the board, the clock source for the two types of services must be the same in the core network. Otherwise, the data or voice service may fail.

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, and 4.

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 board through the line clock signal cable, Clock source type should be set to BITS1-2MHZ or BITS2-2MHZ. – If the clock signals are extracted from the CN by the interface board in the MPS and then sent to the GCUa/GCGa board through the backplane of the MPS, Clock source type should be set to LINE1_8KHZ or LINE2_8KHZ. – If the clock signals are provided by the external BITS, Clock source type should be set to 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, Clock source type should be set to GPS.

Issue 03 (2011-08-31)


87



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

10.1.5 Introduction to Time Synchronization The time synchronization function enables the time synchronization of the nodes of the RAN system. Synchronization is critical for identifying faults. For example, if an E1 link between the BSC6900 and the base station is broken, time synchronization between the BSC6900 and the base station ensures that the same fault is reported to the M2000 by the BSC6900 and by the base station at the same time point. The Simple Network Time Protocol (SNTP) is used to synchronize the time of the nodes of the RAN 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 broadcasts time synchronization information to the SNTP clients. Either the BSC6900 or the M2000 functions as an SNTP server. You can configure an SNTP server by taking the field condition into consideration. SNTP works on Greenwich Mean Time (GMT). Therefore, when setting the time at different nodes, you need to set the time zone where the node is located and decide whether to set Daylight Saving Time (DST). If DST is set, you need to configure the start date/time and end date/time of DST and the time offset.

10.2 Data Configuration Principles for Transmission This section describes the configuration rules and reference information related to the data transmission of the BSC6900.

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

Interface Boards Applicable to Terrestrial Interfaces Before planning the configuration data, you need to select the appropriate interface boards based on the features of terrestrial interfaces.

ATM Interface Boards Table 10-3 lists the recommended interface boards for ATM-based interfaces. Table 10-3 Recommended ATM interface boards

Issue 03 (2011-08-31)

Interface

Recommended ATM Interface Board

Iub

AOUa/AOUc, UOIa (UOIa_ATM)/UOIc, and AEUa

Iu-CS

UOIa (UOIa_ATM)/UOIc Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

88



Interface

Recommended ATM Interface Board

Iu-PS

UOIa (UOIa_ATM)/UOIc

Iur


Iu-BC


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 for the 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


Iur


Iu-BC


Upper-Layer Applications Supported by Interface Boards This section describes the upper-layer applications supported by each interface board you need to 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

Issue 03 (2011-08-31)

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


AOUc

IMA, UNI, Fractional IMA, and Fractional ATM

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


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 that of common SDH transmission equipment. The methods used by companies or organizations for numbering transmission equipment are as follows: 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 the interface board and the transmission equipment numbers. Table 10-7 Relationship between link numbers of optical ports and transmission equipment numbers

Issue 03 (2011-08-31)

Number of TUG3 Blocks

Number of TUG2 Columns

Number of TU12 Lines

Huawei Transmis sion Equipme nt

Lucent Transmis sion Equipme nt

ITU-T Standard

Link Number of Optical Port

1

1

1

1

1

1

0


90


Issue 03 (2011-08-31)







ITU-T Standard


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


Issue 03 (2011-08-31)







ITU-T Standard


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








ITU-T Standard


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, fractional ATM links, and fractional IMA links.

l

For a single link or links carried on a single port, the link type cannot be changed from E1 to 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 cannot work 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 fractional ATM 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 IMA link.

l

The configurations of frame structure, line code, and scrambling switch must be identical at 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 or fractional IMA link.

l

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

l

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

Issue 03 (2011-08-31)


93


l


Links carried on different optical ports of the AOUa board cannot be in the same IMA group.

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

Port Compatibility When 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 they occupy different timeslots.

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

Application Compatibility If 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 added to the group. In a fractional IMA group, each fractional IMA link occupies the same number of timeslots. If an E1/T1 port carries a UNI link, it cannot carry any IMA link, fractional IMA link, fractional ATM link, or timeslot cross connection.

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

UNI Mode The UNI mode is a transport mode at the Transmission Convergence (TC) sublayer of the physical layer. In UNI mode, an ATM cell is directly carried on an E1/T1 frame and the bits of the ATM cell are sequentially mapped to the valid timeslots on the E1/T1 frame. Figure 10-1 shows the mapping between the ATM cell and the E1 timeslots in UNI mode. The 53 bytes of the ATM cell are sequentially carried on E1 timeslots. Each E1 frame provides 31 timeslots (with slot 0 unavailable) for carrying the ATM cell.

Issue 03 (2011-08-31)


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 physical layer. This section describes the principles and functions of fractional mode, introduces two implementation modes (that is, fractional IMA and fractional ATM), and provides the guidelines for 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 used to transmit an ATM cell. At the transmission end, an ATM cell is mapped to multiple timeslots among the 31 timeslots on an E1/T1. At the reception end, the ATM cell is restored from the associated timeslots on the E1/T1. Figure 10-2 shows the fractional ATM mode. An E1 frame has timeslots numbered from 0 to 31. All the timeslots except timeslot 0 are available for service data transmission. A T1 frame has timeslots numbered from 1 to 24. All the timeslots are available for service data transmission. The timeslots to which the ATM cell is not mapped can transmit other data. Figure 10-2 Fractional ATM mode

Issue 03 (2011-08-31)


95



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

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

Two Modes of the Fractional Function There are two implementation modes of the fractional function on the Iub interface: l

Fractional ATM In 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 IMA In fractional IMA mode, multiple fractional IMA links are logically gathered into a group with 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 Mode The timeslot cross connection function implements cross connections between timeslots on two E1/T1s at the physical medium (PM) sublayer of the physical layer. This section describes the principles and functions of timeslot cross connection. Issue 03 (2011-08-31)


96



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

Function of Timeslot Cross Connection The AEUa board supports timeslot cross connection. Through the configured timeslot cross connection, 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 2G equipment or NodeB monitoring equipment. Figure 10-5 shows implementation of timeslot cross connection. Figure 10-5 Implementation of timeslot cross connection

Issue 03 (2011-08-31)


97



NOTE

l Neither the source timeslot nor the target timeslot of a timeslot cross connection can be used by other applications, 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 UNI link. The other timeslots on this E1 link can carry fractional ATM or fractional IMA links.

IMA Mode IMA 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 links or fractional IMA links. This section describes the principles, clock modes, and characteristics of IMA mode.

Principles of IMA Mode Figure 10-6 shows the principles of the IMA mode based on the assumption that each IMA group contains three E1/T1 links. l

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

l

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

The physical layer provides high-speed transport channels for ATM cells from the perspective of 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 frame to implement necessary controlling functions. The length of an IMA frame, m, is defined during the setup of an IMA group. Figure 10-7 shows an IMA frame. The mapping between the ATM cell and the physical link (that is, the E1/T1 link) is similar to that in UNI mode.

Issue 03 (2011-08-31)


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 than a 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 a link.

l

Independent Transmit Clock (ITC): In ITC mode, the clocks used by the links within an IMA group are derived from at least two clock sources. The loopback clock mode is a special 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/T1s must be identical.

l

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

l

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

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

VPI and VCI The main characteristics of the ATM technology are multiplexing, switching, and transmitting of ATM cells. All these operations are performed over Virtual Channels (VCs). A VC and a Issue 03 (2011-08-31)


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 the channel for transmitting ATM cells between two or more nodes. The VC is used for the data transmission between mobile terminals, between networks, or between mobile terminal and network.

l

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

Figure 10-8 Relationship between VC and VP

Service Type The 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

Issue 03 (2011-08-31)

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 with variable-rate data streams and strict real-time requirements, for example, interactive compressed video (video telephony).

Non-Real-Time Variable Bit Rate

NRT-VBR

Rate of a delay-tolerant service. A service of this type, such as e-mail, is relatively insensitive to delivery time or delay.


100



Type of Service

Abbreviation

Description

Unspecified Bit Rate

UBR

Rate of a service with no commitment to transmission and no feedback on congestion. This type of service is ideal for the transmission of IP datagrams. In congestion, UBR cells are discarded, and no feedback or request for slowing down the data rate is delivered to the transmission end.

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

Bandwidth guarantee

Yes

Yes

Yes

No

Applicability to real-time communication

Yes

Yes

No

No

Applicability to bursts of communication

No

No

Yes

Yes

Feedback on congestion

No

No

No

No

Traffic Parameters Traffic parameters refer to the parameters used by each PVC for flow control. The traffic parameters include traffic rate and delay variation. Table 10-10 describes the ATM traffic parameters. Table 10-10 ATM traffic parameters

Issue 03 (2011-08-31)

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 over ATM. CBR and RT-VBR indicate real-time services, which are usually carried on the user planes of the Iur, Iub, and Iu-CS interfaces. NRT-VBR and UBR indicate non-real-time services, which are usually carried on the user plane 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 transmitting ATM cells.

Sustainable cell rate

SCR

Indicates the average rate of transmitting ATM cells over a long time.

Minimum cell rate

MCR

Indicates the minimum rate of transmitting ATM cells.

Max burst size

MBS

Indicates the maximum number of continuous ATM cells.

Cell delay variation tolerance

CDVT

Indicates the maximum tolerable variation in the unit of 0.1 μs.

Traffic use description

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 Principles This section provides suggestions for configuring service types during configuration of ATM traffic 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

Issue 03 (2011-08-31)

Link

Type of Service (In Descending Order by Priority)

NCP/CCP

RTVBR, NRTVBR, CBR

AAL2 path

RTVBR, NRTVBR, CBR, UBR

IPoA PVC (user plane)

UBR


102



Link

Type of Service (In Descending Order by 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 depending on the traffic model in use. l When configuring ATM traffic resources for links, you need to consider the traffic on the interface boards of the BSC6900.

10.2.5 AAL2 Configuration Principles This 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 connections between the BSC6900 and the peer end. The peer end can be a NodeB, a CS CN node, or a neighboring 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 Iub interface. 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, AAL2 routes can be configured to reach the destination node. Figure 10-10 shows an example of the AAL2 route. Issue 03 (2011-08-31)


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 Principles This section describes the types of and specifications for MTP3/M3UA DSPs, the signaling route mask, and the signaling link mask.

Types of MTP3/M3UA DSPs This section describes the configuration rules and reference information related to destination signaling points (DSPs).

DSP Type Table 10-12 describes the DSPs supported by the BSC6900. Table 10-12 Types of DSP

Issue 03 (2011-08-31)

DSP Type

Description

IUCS

R99 MSC DSP. The IUCS DSP has the control plane functions of both radio network layer and transport network layer on the IuCS interface.

IUPS

Signaling point in the control plane of the IuPS interface

IUR

Other BSC6900 signaling points

IUCS_RANAP

R4 MSC server DSP. The IUCS_RANAP DSP has the control plane functions of the radio network layer on the Iu-CS interface.

IUCS_ALCAP

R4 MGW DSP. The IUCS_ALCAP DSP has the control plane functions of the transport network layer on the Iu-CS interface.

AAL2SWITCH

AAL2 transfer point


104



DSP Type

Description

STP

Signaling transfer point

Signaling Route Mask and Signaling Link Mask This section describes configurations and examples of the signaling route mask and signaling link mask. The number (represented by n) of 1s in a signaling route mask determines the maximum number of routes (2n) that participate in load sharing. For example, B0000 indicates that there is at most one 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 number of links (2n) that participate in load sharing. For example, B0000 indicates that there is at most one 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 mask must 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 Principles The Transmission Resource Management (TRM) of the BSC6900 manages the transmission resources of the interfaces, improving the transmission resource utilization and guaranteeing the Quality of Service (QoS). The BSC6900 determines which type of bearer should be used for current services, depending on certain conditions. These conditions are the service type, the preset mapping between service types and transmission resources, and the utilization of the transmission resources.

Background Information Different types of service have different QoS requirements. For example, voice services require high QoS but PS background services do not. Therefore, mapping services with different QoS requirements onto different transmission resources helps achieve high resource utilization.

Configuration Principles Before transport bearers are set up for radio links on the interfaces, the BSC6900 applies for transmission resources, makes admission decisions based on transmission resources, and allocates transmission resources. Issue 03 (2011-08-31)


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 case of ATM transport, the BSC6900 applies for Connection IDs (CIDs) and AAL2 path bandwidth resources. For IP transport, the BSC6900 applies for UDP ports and IP path bandwidth resources.

TRM Configuration Description You can run the related MML command to configure the mapping between service types and transmission resources over a specific interface.

CAUTION The primary and secondary paths for a type of service must be different.

10.2.8 Activity Factor Configuration Principles The configuration of activity factors can increase the resource utilization.

Background Information Transmission resources may not be fully utilized because services are not always active. For the purpose of resource multiplexing, transmission resources should be reserved according to service bandwidth x activity factor when a service is initiated. The value of an activity factor affects the number of services admitted.

Activity Factor Configuration Policies for Different Service Types The following policies should be used to reserve transmission resources irrespective of the type of 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. MBR indicates the maximum bit rate. GBR indicates the minimum bit rate.

10.3 Data Configuration Principles for Interfaces This section describes the configuration rules and reference information related to the BSC6900 interfaces.

10.3.1 Data Configuration Principles for the Iub Interface (over ATM) Related information is required for performing data configurations on the ATM-based Iub interface. This information refers to the protocol stack, links on the Iub interface, and OM channel configuration principles.

Issue 03 (2011-08-31)


106



Protocol Structure for the Iub Interface (over ATM) When ATM transport is applied to the Iub interface, the sequence of configuring Iub interface data should be consistent with the protocol structure, that is, from the bottom layer to the top layer 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 three areas 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 the Communication 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 the ATM PVC. Under the control of Q.AAL2, AAL2 connections can be dynamically set up or released for upper-layer services. Therefore, each AAL2 path must have its corresponding controlling Q.AAL2.

Links on the Iub Interface (over ATM) This section describes the links on the ATM-based Iub interface. Issue 03 (2011-08-31)


107



Links on the Iub Interface There are three types of links on the ATM-based Iub interface: SAAL link of User-Network Interface (UNI) type, AAL2 path, and IPoA PVC. The SAAL link of UNI type is used to carry NCP, 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 involve the internal information of the NodeB. l The RINT shown in Figure 10-13 refers to the ATM interface boards of the BSC6900. For the recommended ATM interface boards of the Iub interface, see Interface Boards Applicable to Terrestrial Interfaces.

SAAL Link of UNI Type An SAAL link of UNI type carries signaling messages on the Iub interface. The signaling messages carried on the SAAL links are classified into NCP, CCP, and ALCAP, as described in Table 10-13. Table 10-13 Data carried on SAAL links of UNI type

Issue 03 (2011-08-31)

Data Type

Description

NCP

The NCP carries common process messages of NBAP over the Iub interface. An Iub interface has only one NCP.


108



Data Type

Description

CCP

A CCP carries dedicated process messages of NBAP over the Iub interface. An Iub interface may have multiple CCPs. The number of CCPs depends on network 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 other attributes of the PVC must be negotiated between the BSC6900 and the NodeB.

AAL2 Path An AAL2 path is a group of connections between the BSC6900 and the NodeB. An Iub interface has 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 the PVC must be negotiated between the BSC6900 and the NodeB.

IPoA PVC IPoA 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 the Iub interface are used to transmit the OM information of a NodeB. In this case, the IPoA PVC is 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 PVC Figure 10-14 shows the IPoA PVCs from the BSC6900 to NodeBs. Figure 10-14 IPoA PVCs from the BSC6900 to NodeBs

Issue 03 (2011-08-31)


109



NOTE

The RINT shown in Figure 10-14 refers to the ATM interface boards of the BSC6900. For the recommended ATM interface boards of the Iub interface, see Interface Boards Applicable to Terrestrial Interfaces.

Network Segments Each 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 and the 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 board and the NodeBs. When setting this network segment, you need to take field conditions into consideration.

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 route configuration, 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 should be consistent with the protocol structure, that is, from the bottom layer to the top layer and from the control plane to the user plane. Figure 10-15 shows the protocol stack for the IP-based Iub interface.

Issue 03 (2011-08-31)


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 Interface There are two types of links on the IP-based Iub interface: SCTP link and IP path. The SCTP link is used to carry NCP and CCP, as shown in Figure 10-16.

Issue 03 (2011-08-31)


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 involve the internal information of the NodeB. l The RINT shown in Figure 10-16 refers to the IP interface boards of the BSC6900. For the recommended IP interface boards of the Iub interface, see Interface Boards Applicable to Terrestrial Interfaces.

SCTP Links An SCTP link carries signaling messages on the Iub interface. The signaling messages carried on the SCTP links are classified into NCP and CCP, as described in Table 10-14. Table 10-14 Data carried on SCTP links Data Type

Description

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. An Iub interface may have multiple CCPs. The number of CCPs depends on network planning.

The SCTP link can work in two modes, SERVER and CLIENT, on the BSC6900 and NodeB sides. On the BSC6900 side, the differences between the two working modes are as follows: l

Issue 03 (2011-08-31)

SERVER: The local end enables only the listening port and the peer end sends the initialization request. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

112



In SERVER mode, all SCTP links use the listening port as a local port. The listening port also becomes the local port of NCP or CCP on the control plane. On the NodeB side, a port number 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 that a local port number is added to each NCP and CCP. On the NodeB side, only one port number needs to be configured.

It is recommended that the working mode of the BSC6900 be set to SERVER when you configure an SCTP link.

IP Path An IP path is a group of connections between the BSC6900 and the NodeB. An Iub interface has 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 3 networking. Compared with layer 3 networking, layer 2 networking is simple because the port IP addresses of the BSC6900 and NodeB are located on the same network segment and no route is 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

Issue 03 (2011-08-31)


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 IP interface board. IP5 and IP6 are gateway IP addresses on the BSC6900 side. IP7 is the gateway IP address on 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 of IP addresses of Ethernet ports, local IP addresses of PPP links, local IP addresses of MLPPP groups, 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 an Ethernet port

Required when the FG2a/ FG2c/GOUa/GOUc board functions as the interface board

l Each Ethernet port can be configured with only one primary IP address and five secondary IP addresses. l The IP address of an Ethernet port and the internal IP address of the BAM must be located on different network segments. For these network segments, one cannot cover another. l In the BSC6900, the IP addresses of different Ethernet ports must be located on different network segments. For these network segments, one cannot cover another.

Issue 03 (2011-08-31)


114



IP Address

Configuration Scenario

Configuration Restriction

Local IP address of a PPP link

Required when the PEUa, POUa/POUc, or UOIa (UOIa_IP) board functions as the interface board

Each PPP link can be configured with only one local IP address.

Local IP address of an MLPPP group

Required when the PEUa or POUa/POUc board functions as the interface board

Each MLPPP group can be configured with only one local IP address.

Device IP address

Required in layer 3 networking

l Each interface board can be configured with a maximum of five device IP addresses. l The IP addresses of any two different devices must be located on different subnets.

Route on the Iub Interface On the Iub interface where layer 2 networking is applied, no route is required. On the Iub interface where 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 Interface Board

The route travels from the BSC6900 to the network segment where the NodeB is located. You can configure the route on the BSC6900. Destination IP address is the address of the network segment where the NodeB or NodeB IP address is located, and Next Hop Address is the gateway IP address, for example, IP5 or 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 between the M2000 and the NodeB through the BSC6900 and the other is the routing between the M2000 and the NodeB not through the BSC6900.

Routing Between the M2000 and the NodeB Through the BSC6900 Figure 10-19 shows an example of the routing between the M2000 and the NodeB through the BSC6900. Table 10-17 describes the routes.

Issue 03 (2011-08-31)


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 networking is applied to the Iub interface, the IP interface board and the NodeB communicate with each other through a router. l The RINT shown in Figure 10-19 refers to the IP interface boards of the BSC6900. For the recommended IP interface boards of the Iub interface, see Interface Boards Applicable to Terrestrial Interfaces.

Table 10-17 Routes between the M2000 and the NodeB through the BSC6900

Issue 03 (2011-08-31)

Equipment

Forward Route

Reverse Route

M2000

From the M2000 to the NodeB OM network segment 19.19.19.X, with Forward route address to be the external virtual IP address of the BAM, that is, 172.121.139.200

-

BSC6900

From the BAM to the NodeB OM network segment 19.19.19.X, with Forward route address to be the internal IP address of the IP interface board at the BSC6900, that is, 80.168.3.66

From the IP interface board of the BSC6900 to the M2000 IP network segment 172.121.139.X You can configure the route on the BSC6900 side. When you run this command, set EMS IP Address to the IP address of the M2000, set Subnet mask to the subnet mask of the M2000, and specify the values of BAM External Network Virtual IP and BAM External


116


Equipment


Forward Route

Reverse Route

l If layer 2 networking is applied, add a route to the OM IP address of the NodeB. Forward route address must be the IP address of the NodeB interface board.

Network Mask. In this example, EMS IP Address is 172.121.139.56, and BAM External Network Virtual IP is 172.121.139.200.

l If layer 3 networking is applied, add a route to the OM IP address of the NodeB. Forward route address must be the gateway IP address on the BSC6900 side. NodeB

-

From the NodeB to the M2000 IP network segment 172.121.139.X l If layer 2 networking is applied to the Iub interface, Forward route address is the IP address of the IP interface board at the BSC6900, that is, 16.16.16.1. l If layer 3 networking is applied to the Iub interface, Forward route address is the gateway IP address on the NodeB side.

Routing Between the M2000 and the NodeB Not Through the BSC6900 If the OM subnet where the M2000 is located is connected to the IP network that covers the NodeB, routes can be configured between the M2000 and the NodeB not through the BSC6900. Figure 10-20 shows an example of routing between the M2000 and the NodeB not through the BSC6900. Table 10-18 describes the routes. Figure 10-20 Example of the routes between the M2000 and the NodeB not through the BSC6900

Issue 03 (2011-08-31)


117



Table 10-18 Routes between the M2000 and the NodeB not through the BSC6900 Equipment

Forward Route

Reverse Route

M2000

From the M2000 to the NodeB OM network segment 19.19.19.X, with Forward route address being the port IP address of router 1, that is, 10.161.215.200

Router 1

From router 1 to the NodeB OM network segment 19.19.19.X, with Forward route address being the port IP address of router 2, that is, 172.16.16.10

Router 2

From router 2 to the NodeB OM network segment 19.19.19.X, with Forward route address being the IP address of the IP interface board at the NodeB, that is, 16.16.16.2

From router 2 to the M2000 network segment 10.161.215.100, with Forward route address being the port IP address of router 1, that is, 172.16.16.9

NodeB

-

From the NodeB to the M2000 network segment 10.161.215.100, with Forward route address being the port IP address of router 2, that is, 16.16.16.20

10.3.3 Data Configuration Principles for the Iub Interface (over ATM and IP) Related information is required for performing data configuration on the ATM/IP dual stackbased Iub interface. This information refers to the ATM/IP hybrid transport, hardware configuration 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 on ATM over E1, however, increases high costs. Data services produce a decreasing efficiency for operators. Therefore, the operators require a low-cost Iub transmission solution, which leads to the introduction of the ATM/IP hybrid transport. It reduces the data transmission costs on the Iub interface, while maintaining the proper running of services. Issue 03 (2011-08-31)


118



Based on the Quality of Service (QoS) and bandwidth requirements, ATM/IP hybrid transport implements 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 the impact of IP transport on the ATM networks, and meets the requirements of operators for costeffective data transmission and flexible networking.

Hardware Configuration Principles for ATM/IP Hybrid Transport on the Iub Interface This section describes the hardware configuration principles for ATM/IP hybrid transport on the Iub interface in terms of board configuration, cable connections, and hardware-related precautions.

Hardware Configuration Principles for ATM/IP Hybrid Transport To implement ATM/IP hybrid transport, insert ATM and IP interface boards into the slots of the MPS and EPS. In this way, an ATM/IP dual stack-based NodeB can be connected to an ATM interface board and an IP interface board at the same time. The two interface boards can be located in different subracks. NOTE

Though the BSC6900 ATM and IP interface boards for one NodeB can be located in different subracks, it is recommended that the interface boards be located in the same subrack if possible.

Interface Board Configuration for ATM/IP Hybrid Transport All 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 board and the GOUa functions as the IP interface board.

Issue 03 (2011-08-31)


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 Connections When ATM/IP hybrid transport is applied, the ATM interface at the BSC6900 connects to the NodeB through an ATM network, and the IP interface at the BSC6900 connects to the NodeB through an IP network.

Data Configuration Principles for ATM/IP Hybrid Transport on the Iub Interface This section describes the data configuration principles for ATM/IP dual stack-based transport on the Iub interface in terms of VLAN planning, transmission resource allocation, and traffic distribution.

VLAN Planning Virtual Local Area Network (VLAN) helps shield the BSC6900 from network storms and improve the security of layer 2 networking. The priorities in VLAN tags are used for service Issue 03 (2011-08-31)


120



differentiation. The specifications for VLANs in ATM/IP hybrid transport are the same as those in IP transport on the Iub interface. There are two types of VLAN settings: VLAN setting in layer 2 networking and VLAN setting in 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, it is recommended that an identical VLAN ID be allocated to the NodeBs whose traffic is converged to the same layer 2 transmission device, for example, a LAN switch. If the layer 2 transmission device supports the setting of VLAN priorities, the priorities of services need to be mapped onto those of VLANs. If the layer 2 transmission device identifies the priorities based on the VLAN IDs, the priorities of services need to be mapped onto VLAN IDs 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 that supports configuration of VLAN priorities, the interface board at the BSC6900 can map the priorities of services either onto the priorities of VLANs or onto the VLAN IDs based on the service types. In layer 3 networking, the VLANs configured at the BSC6900 apply to the BSC6900 and the layer 3 transmission device only. Therefore, VLAN IDs and priorities 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, take the following suggestions into consideration: ATM transport, IP transport, or ATM/IP hybrid transport is applicable to control plane data. It is recommended that ATM/IP hybrid transport be applied to control plane data for security purposes. In other words, the SAAL and SCTP links together carry an NCP or a CCP, and the active link is the SAAL link. ATM transport, IP transport, or ATM/IP hybrid transport is applicable to user plane data. It is recommended that: l

ATM transport be applied to signaling, voice services, CS conversational services, CS streaming services, PS conversational services, and PS streaming services.

l

IP transport be applied to PS interactive services, PS background services, HSDPA conversational services, HSDPA streaming services, HSDPA interactive services, HSDPA background 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 IP transport be applied.

Traffic Distribution For the ATM traffic distribution principles and the relationship between interface links and service types, see ATM Traffic Resource Configuration Principles. Issue 03 (2011-08-31)


121



10.3.4 Data Configuration Principles for the Iu-CS Interface (over ATM) Related information is required for performing data configuration on the ATM-based Iu-CS interface. This information refers to the protocol stack, links on the Iu-CS interface, and the differences 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 interface data should be consistent with the protocol structure, that is, from the bottom layer to the top layer 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 areas can be carried on common physical links. Issue 03 (2011-08-31)


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 CN side: 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 boards recommended 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 to 15. The configuration of MTP3 links between the BSC6900 and the MSC server depends on the network 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 required for the MSC server (IUCS_RANAP signaling point). It is recommended that more than one 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.

Issue 03 (2011-08-31)


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 MTP3 link. 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 other attributes of the PVC must be negotiated between the BSC6900 and the peer end.

AAL2 Path An AAL2 path is a group of connections to the adjacent node. The path IDs range from 1 to 4294967295. An Iu-CS interface has at least one AAL2 path. It is recommended that two or more AAL2 paths be configured. An AAL2 path is carried over an ATM PVC. The PVC identifier (VPI/VCI) and other PVC attributes must be negotiated between the BSC6900 and the peer end.

Differences of the Iu-CS Interface Between R99 and R4/R5/R6/R7/R8 In 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 server and MGW.

Iu-CS Interface Defined in the 3GPP R4/R5/R6/R7/R8 Figure 10-26 shows the Iu-CS interface in the 3GPP R4/R5/R6/R7/R8.

Issue 03 (2011-08-31)


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 forwarded between the MSC server and the BSC6900 through the routes configured on the MGW. Figure 10-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 IuCS interfaces respectively. Issue 03 (2011-08-31)


125



Figure 10-28 Protocol stack for the ATM-based Iu-CS interface

Figure 10-29 Protocol stack for the IP-based Iu-CS interface

Issue 03 (2011-08-31)


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 as follows: 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 C shown in Figure 10-28. On the IP-based Iu-CS interface, the MGW implements the functions 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 signaling point, that is, the MSC. In the 3GPP R4/R5/R6/R7/R8, the BSC6900 needs to be configured with the following two types 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 in R4/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-CS ALCAP signaling point

Iu-CS signaling point

Quantity

More than one

One

10.3.5 Data Configuration Principles for the Iu-CS Interface (over IP) Related information is required for performing data configuration on the IP-based Iu-CS interface. This information refers to the protocol stack, links on the Iu-CS interface, and the differences 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 data should be consistent with the protocol structure, that is, from the bottom layer to the top layer and from the control plane to the user plane. Figure 10-30 shows the protocol stack for the Iu-CS interface. Issue 03 (2011-08-31)


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 CN side: M3UA link and IP path.

Links on the Iu-CS Interface Figure 10-31 shows the links on the IP-based Iu-CS interface.

Issue 03 (2011-08-31)


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 interface boards recommended for the Iub 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 0 to 15. The configuration of M3UA links depends on the network structure between the MSC server and the BSC6900. l

If the MSC server is directly connected to the BSC6900, at least one M3UA link is required for the MSC server (IUCS_RANAP signaling point). It is recommended that more than one M3UA link be configured.

l

If the MSC server is connected to the BSC6900 through the MGW, you need to configure the M3UA links only between the BSC6900 and the MGW. The MGW is responsible for forwarding signaling to the MSC server. It is recommended that more than one M3UA link be 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 the MSC server (IUCS_RANAP signaling point). You can also configure the M3UA links between the BSC6900 and the MGW, which is responsible for forwarding signaling to the MSC server. Or you can configure the M3UA links between the BSC6900 and the MSC server and the M3UA links between the BSC6900 and the MGW at the same time. It is recommended that more than one M3UA link be configured.

Issue 03 (2011-08-31)


129



Figure 10-32 Example of connections between the MSC server and the BSC6900

IP Path An 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 be configured.

Differences of the Iu-CS Interface Between R99 and R4/R5/R6/R7/R8 In 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 server and MGW.

Iu-CS Interface Defined in the 3GPP R4/R5/R6/R7/R8 Figure 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

Issue 03 (2011-08-31)


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 forwarded between the MSC server and the BSC6900 through the routes configured on the MGW. Figure 10-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 MGW Figure 10-35 and Figure 10-36 show the protocol stacks for the ATM-based and IP-based IuCS interfaces respectively.

Issue 03 (2011-08-31)


131



Figure 10-35 Protocol stack for the ATM-based Iu-CS interface


Issue 03 (2011-08-31)


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 as follows: 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 C shown in Figure 10-35. On the IP-based Iu-CS interface, the MGW implements the functions 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 signaling point, that is, the MSC. In the 3GPP R4/R5/R6/R7/R8, the BSC6900 needs to be configured with the following two types 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 in R4/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-CS ALCAP signaling point

Iu-CS signaling point

Quantity

More than one

One

10.3.6 Data Configuration Principles for the Iu-PS Interface (over ATM) Related information is required for performing data configuration on the ATM-based Iu-PS interface. This information refers to the protocol structure, links on the ATM-based Iu-PS interface, 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 interface data should be consistent with the protocol structure, that is, from the bottom layer to the top layer and from the control plane to the user plane. Figure 10-37 shows the protocol stack for the Iu-PS interface. Issue 03 (2011-08-31)


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 user plane (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 can be 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 CN side: MTP3 link and IPoA PVC.

Links on the Iu-PS Interface Figure 10-38 shows the links on the Iu-PS interface.

Issue 03 (2011-08-31)


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 boards recommended for the Iu-PS 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 to 15. An Iu-PS interface requires at least one MTP3 link. It is recommended that more than one MTP3 link 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 other attributes of the PVC must be negotiated between the BSC6900 and the peer end.

IPoA PVC The 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 IPoA PVC 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 Plane Figure 10-39 shows the IPoA PVC on the Iu-PS user plane. Issue 03 (2011-08-31)


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 boards recommended 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 IuPS 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 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 and the gateway on the SGSN side

-

Route between the interface board carrying the IPoA PVC and the network segment of the peer SGSN

If the IP address of the interface board carrying the IPoA PVC and the IP address of the SGSN are located on different subnets, routes to the destination IP address need to be configured at the BSC6900. Destination IP address is the IP address of the SGSN, and Forward route address is the IP address of the gateway on the SGSN side.

CAUTION On the Iu-PS interface, the SGSN must be configured with routes to the network segment where the IP address of the BSC6900 interface board is located. Forward route address is the IP address of the gateway on the BSC6900 side. Otherwise, PS services cannot be provided.

Issue 03 (2011-08-31)


136



10.3.7 Data Configuration Principles for the Iu-PS Interface (over IP) Related information is required for performing data configuration on the IP-based Iu-PS interface. This information refers to the protocol structure and links on the IP-based Iu-PS interface.

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 data should be consistent with the protocol structure, that is, from the bottom layer to the top layer and 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 user plane (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 areas can 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 CN side: M3UA link and IP path.

Links on the Iu-PS Interface Figure 10-41 shows the links on the IP-based Iu-PS interface. Issue 03 (2011-08-31)


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 interface boards 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 0 to 15. An Iu-PS interface requires at least one M3UA link. It is recommended that more than one M3UA 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 be configured.

10.3.8 Data Configuration Principles for the Iur Interface (over ATM) Related information is required for performing data configuration on the ATM-based Iur interface. This information refers to the protocol structure, links on the ATM-based Iur interface, and configuration of paths for static SRNS reallocation.

Issue 03 (2011-08-31)


138



Protocol Stack on the Iur Interface (over ATM) If ATM transport is applied to the Iur interface, the sequence of configuring Iur interface data should be consistent with the protocol structure, that is, from the bottom layer to the top layer and 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 Interface Figure 10-43 shows the links on the ATM-based Iur interface.

Issue 03 (2011-08-31)


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 ATM interface boards recommended for the Iur 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 to 15. The configuration of MTP3 links depends on the network structure between the BSC6900 and the neighboring BSC6900. The specifics are as follows: l

If the BSC6900 is directly connected to the neighboring BSC6900, the Iur interface requires at 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 Transfer Point (STP), no MTP3 link is required.

MTP3 links are carried on the SAAL links of Network-to-Network Interface (NNI) type. It is recommended 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 the CPUS subsystems. An SAAL link of NNI type is carried over an ATM PVC. The PVC identifier (VPI/VCI) and other attributes of the PVC must be negotiated between the BSC6900 and the peer end.

AAL2 Path An AAL2 path is a group of connections to the adjacent node. The path IDs range from 1 to 4294967295. Issue 03 (2011-08-31)


140



An Iur interface has at least one AAL2 path. It is recommended that more than one AAL2 path be configured. An AAL2 path is carried over an ATM PVC. The PVC identifier (VPI/VCI) and other PVC attributes must be negotiated between the BSC6900 and the peer end.

Configuration Principles for Static Relocation Routes over Iur The IP routes on the Iur interface are used to forward the PS data during Serving Radio Network Subsystem (SRNS) relocation. During the SRNS relocation, the PS data is transferred from the local BSC6900 to the SGSN and then to the neighboring BSC6900. Therefore, the prerequisites for configuring IP routes on the Iur interface are that the IP paths between the local BSC6900 and the SGSN, between the neighboring BSC6900 and the SGSN, and between the serving BSC6900 and the drift BSC6900 are configured. Figure 10-44 shows the configuration of IP routes on the Iur interface. The IP routes configured in 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 interface boards and IP interface boards recommended for the Iur interface, see Interface Boards Applicable to Terrestrial 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, and configuration 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 should be consistent with the protocol structure, that is, from the bottom layer to the top layer and from the control plane to the user plane. Figure 10-45 shows the protocol stack for the Iur interface. Issue 03 (2011-08-31)


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 layer user 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 IP path.

Links on the Iur Interface Figure 10-46 shows the links on the Iur interface.

Issue 03 (2011-08-31)


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 interface boards 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 0 to 15. The configuration of M3UA links depends on the network structure between the BSC6900 and the neighboring BSC6900. The specifics are as follows: l

If the BSC6900 is directly connected to the neighboring BSC6900, the Iur interface requires at 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 Transfer Point (STP), no M3UA link is required.

M3UA links are carried on SCTP links. It is recommended that the SCTP links be evenly distributed to the CPUS subsystems in the MPS/EPS so that the signaling exchange can be reduced 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 be configured.

Issue 03 (2011-08-31)


143



Configuration Principles for Static Relocation Routes over Iur The IP routes on the Iur interface are used to forward the PS data during Serving Radio Network Subsystem (SRNS) relocation. During the SRNS relocation, the PS data is transferred from the local BSC6900 to the SGSN and then to the neighboring BSC6900. Therefore, the prerequisites for configuring IP routes on the Iur interface are that the IP paths between the local BSC6900 and the SGSN, between the neighboring BSC6900 and the SGSN, and between the serving BSC6900 and the drift BSC6900 are configured. Figure 10-47 shows the configuration of IP routes on the Iur interface. The IP routes configured in 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 interface boards and IP interface boards recommended for the Iur interface, see Interface Boards Applicable to Terrestrial Interfaces.

10.3.10 Data Configuration Principles for the Iu-BC Interface (over ATM) Related information is required for performing data configuration on the Iu-BC interface. This information refers to the protocol structure, network structure, links on the Iu-BC interface, and the 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 interface data should be consistent with the protocol structure, that is, from the bottom layer to the top layer. Figure 10-48 shows the protocol stack for the Iu-BC interface.

Issue 03 (2011-08-31)


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 the physical transport resources on the Iu-PS interface. Figure 10-49 shows the network structure on the Iu-BC interface. Figure 10-49 Connection between the BSC6900 and CBC through an SGSN

Issue 03 (2011-08-31)


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 Interface Figure 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 ATM interface boards recommended for the Iu-BC interface, see Interface Boards Applicable to Terrestrial Interfaces.

IPoA PVC An IPoA PVC must be configured on the Iu-BC interface for connecting the BSC6900 to the SGSN gateway because the CBC usually connects to the BSC6900 through an SGSN. In this situation, the data on the Iu-BC interface is transmitted to the SGSN through the IPoA PVC and then 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 to the CBC.

IPoA PVC on the Iu-BC Interface On the Iu-BC interface, the BSC6900 connects to the CBC through an SGSN, as shown in Figure 10-51.

Issue 03 (2011-08-31)


146



Figure 10-51 IPoA configuration on the Iu-BC interface (through an SGSN)

NOTE

The RINT shown in Figure 10-51 refers to the ATM interface boards of the BSC6900. For the ATM interface boards recommended for the Iu-BC interface, see Interface Boards Applicable to Terrestrial Interfaces.

IPoA Data on the Iu-BC Interface Table 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 interface board 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 and the gateway on the SGSN side

-

Route between the interface board carrying the IPoA PVC and the network segment of the peer SGSN

If the IP address of the interface board carrying the IPoA PVC and the destination IP address of the SGSN are located on different subnets, routes to the destination IP address of the SGSN must be configured at the BSC6900.

10.3.11 Data Configuration Principles for the Iu-BC Interface (over IP) Related information is required for performing data configuration on the IP-based Iu-BC interface. This information refers to the protocol structure and network structure on the Iu-BC interface.

Issue 03 (2011-08-31)


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 interface data should be consistent with the protocol structure, that is, from the bottom layer to the top layer. 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 IP transport 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 backup of FG2a/FG2c. Figure 10-53 shows the network structure based on a data transport network. IP transport is applied on the FE/GE ports.

Issue 03 (2011-08-31)


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 access the IP bearer network, which enables connections over the Iu-BC interface. An Iu-BC interface can share an FE/GE port at the BSC6900 with an Iu interface, because of the low traffic on the Iu-BC interface.

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

10.4.1 Definitions of Sector, Carrier, and Cell A 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 smallest serving unit for UE access. There are two types of sectors: omnidirectional sector and directional sector. The omnidirectional sector provides coverage for small traffic. It covers the 360º circle area with the omnidirectional antenna in the center of the circle. As the traffic grows, the omnidirectional sector is split into three or six directional sectors. The directional sectors are covered by directional 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 is overlap between the sectors. The number of cells supported by a NodeB is equal to the number of sectors multiplied by the number of carriers in each sector. Figure 10-54 shows the typical 3 x 2 configuration. The whole circle 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 scrambling codes are used in neighboring cells of different sectors that use the same frequency. The different downlink primary scrambling codes lower the interference between cells. Figure 10-54 shows the relations between sector, frequency, and cell.

Issue 03 (2011-08-31)


149



Figure 10-54 Relations between sector, frequency, and cell

10.4.2 Definitions of Local Cell and Logical Cell In the 3GPP, a service-providing cell is referred to as a local cell when referring to implementations, and as a logical cell when referring to logical resource management.

Local Cell A local cell is a combination of physical resources, such as hardware resources and software resources, 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 can control the radio resources in certain cells through the standard Iub interface. These cells are carried on NodeBs from different vendors.

Logical Cell A logical cell is a standard logical model that helps the BSC6900 control the radio resources in a cell. The model is independent of local cell implementation and ensures that the Iub interface is 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 of a logical cell are configured at and managed by the BSC6900. There is a one-to-one mapping between a logical cell and a local cell. Issue 03 (2011-08-31)


150



10.4.3 Logical Cell Model This 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 the quantity of the entities that serve as lower-level nodes. The number below the square is the quantity 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 Cells A 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.

Issue 03 (2011-08-31)


151



10.4.5 Definition of Neighboring Cell A neighboring cell is associated with a specific cell. There are three types of neighboring cell for UMTS cells: intra-frequency neighboring cell, inter-frequency neighboring cell, and neighboring GSM cell. l

An intra-frequency neighboring cell is a cell that has overlapping coverage with the serving cell 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 serving cell 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 Specifications This document describes the specifications of the BSC6900. Table 10-23 lists the specifications of the BSC6900. Table 10-23 BSC6900 specifications

Issue 03 (2011-08-31)

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 Cell Relationships

163200

Maximum Number of Inter-Frequency Neighboring Cell Relationships

326400

Maximum Number of Intra-Frequency Neighboring UMTS Cells Supported by a UMTS Cell

32 (including the local cell)

Maximum Number of Inter-Frequency Neighboring UMTS Cells Supported by a UMTS Cell

64

Maximum Number of Neighboring GSM Cells Supported by 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


Issue 03 (2011-08-31)


Item

Specification

Maximum Number of MTP (MTP3 & MTP3b) Links Supported 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 a CPUS

125

Maximum Number of SAAL NNI Links Supported by a CPUS

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

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

Recommend Documents