98
Huawei Confidential. All Rights Reserved BSC6800 TNL data configuration ISSUE 1.0

BSC6800 TNL Data Configuration

Embed Size (px)

DESCRIPTION

BSC6800 TNL Data Configuration

Citation preview

Page 1: BSC6800 TNL Data Configuration

Huawei Confidential. All Rights Reserved

BSC6800 TNL data configuration

ISSUE 1.0

Page 2: BSC6800 TNL Data Configuration

2 Internal Use

ObjectivesObjectives

Upon completion of this course, you will be able to:

Master the principles of data configuration or BSC6800;

Master TNL data configuration of BSC6800

Page 3: BSC6800 TNL Data Configuration

3 Internal Use

ReferencesReferences

《 HUAWEI BSC6800 Operation Manual-Data Configuration》

Page 4: BSC6800 TNL Data Configuration

4 Internal Use

Chapter 1 Basic informationChapter 1 Basic information

Chapter 2 Equipment data configuration

Chapter 3 Iub interface data configuration

Chapter 4 Iu-CS interface data configuration

Chapter 5 Iu-PS interface data configuration

Page 5: BSC6800 TNL Data Configuration

5 Internal Use

Configuration Procedure Configuration Procedure

Start

Equipment dataconf iguration

Interf ace dataconf iguration

Global parameterconf iguration

Cell data conf iguration

End

CBS and SMLCconf iguration

Page 6: BSC6800 TNL Data Configuration

6 Internal Use

Configuration Command Configuration Command

You can carry out the MML commands in two modes on a LMT Batch mode. You may organize multiple MML commands in an

MML command script. This mode is applicable for the initial configuration and mass configuration

One-step mode. You may also input one command at a time and carry it out directly. This mode is applicable for routine configuration and maintenance

Action Meaning

ADD Add an object

SET Set an object

LST Query BAM database configuration information

DSP Query FAM object state or BAM running state

MOD Modify an object

RMV Remove an object

ACT Activate an object

DEA Deactivate an object

RST Reset an object

Page 7: BSC6800 TNL Data Configuration

7 Internal Use

Data Configuration Mode Data Configuration Mode

CMC definition To avoid the data conflict, LMTs and M2000 clients cannot configure

the data at the same time. Through the mechanism of Configuration Management Control (CMC), the BSC6800 controls whether LMT or M2000 has the permission to configure the data at a time

Procedures of obtaining CMC in different cases

If … Then …

M2000 communicates with BSC6800 normally Use the REQ CMCTRL command to request the CMC. If M2000 approves, LMT will get

it.

M2000 cannot communicate with BSC6800 or BSC6800 is not equipped with M2000

Use the FOC CMCTRL command to obtain the CMC forcibly.

Page 8: BSC6800 TNL Data Configuration

8 Internal Use

Data Configuration Mode Data Configuration Mode

Use the LST CMCTRL command to query the CMC Obtaining CMC in different cases

Use the LCK CMCTRL command to lock the CMC Use the ULK CMCTRL command to unlock the CMC

If … Then …

M2000 communicates with BSC6800 normally

Use the REQ CMCTRL command to request the CMC. If M2000 approves, LMT will get it.

M2000 cannot communicate with BSC6800 or BSC6800 is not equipped with M2000

Use the FOC CMCTRL command to obtain the CMC forcibly.

Page 9: BSC6800 TNL Data Configuration

9 Internal Use

Configuration State Configuration State

Offline State In offline state, you will configure data in only the BAM database SET AFLUSH is used to set the flag of updating the .dat files. In o

ffline state, the system determines whether to dynamically update .dat files according to your settings. In online state, the system automatically updates the .dat files

.dat files Boards of FAM

BAM

LMT

Configuration MML commands Database

Loading by resetting

Formatting

Page 10: BSC6800 TNL Data Configuration

10 Internal Use

Configuration State Configuration State

Offline commands of BSC6800 Major commands of the BSC6800 system can run in both online and

offline states. However, the commands in the following Table can run in only the offline state

Offline command Function

ADD RNCBASIC Add BSC6800 basic data

MOD RNCBASIC Change BSC6800 basic data

SET SUBNET Set subnet No.

ADD OPC Add source signalling point

RMV OPC Delete source signalling point

Page 11: BSC6800 TNL Data Configuration

11 Internal Use

Configuration State Configuration State

Online State In online state, you will configure data in both BAM and FAM

databases

.dat files

Boards ofFAM

BAM

LMT

Configuration MML commands

Database

Loading directly

Formatting

Page 12: BSC6800 TNL Data Configuration

12 Internal Use

Data Initialization Data Initialization

The BAM database contains initial settings and LMT configurations. RST DATA will remove all LMT configuration data. After the execution of RST DATA the flag of updating .dat files will be restor

ed to ON and after resetting the system or switch to online mode the configuration status will become online

Page 13: BSC6800 TNL Data Configuration

13 Internal Use

Chapter 1 Basic informationChapter 1 Basic information

Chapter 2 Equipment data configuration

Chapter 3 Iub interface data configuration

Chapter 4 Iu-CS interface data configuration

Chapter 5 Iu-PS interface data configuration

Page 14: BSC6800 TNL Data Configuration

14 Internal Use

Equipment Data Configuration Overview Equipment Data Configuration Overview

RNC equipment data configuration procedure

Start

End

Conf igure sy stem

Conf igure time

Conf igure clock

Conf igure subrack

Conf igure board

Page 15: BSC6800 TNL Data Configuration

15 Internal Use

Configure basic system information carry out SET SYS to configure the RNC system information The basic system information is stored in the BAM database. It

is not sent to FAM

Configure RNC subnet carry out SET SUBNET to configure the RNC internal subnet

No. The default subnet No. is 80

Configure WMPU IP address Carry out SET WMPUIP to configure the IP address for the

WMPU board.

Configuring System

Page 16: BSC6800 TNL Data Configuration

16 Internal Use

Configuring ClockConfiguring Clock

Carry out ADD CLKSRC to add a clock source Carry out SET CLKMODE to configure the clock source

handover strategy

Page 17: BSC6800 TNL Data Configuration

17 Internal Use

Configuring Time Configuring Time

You may apply one of the following as the BSC6800 time: The default time of the BAM Server. You need no time

configuration in this case The time of the operation and maintenance center (OMC).

You need establish communication between BSC6800 and OMC in this case. The OMC acts as a Simple Network Time Protocol (SNTP) Server and the BSC6800 as an SNTP Client. You need configure SNTP Client information for the BSC6800

carry out SET SNTPCLTPARA to configure the SNTP Client information

Page 18: BSC6800 TNL Data Configuration

18 Internal Use

Configuring Time Configuring Time

You may apply one of the following as the time of NodeBs : The local default time. You need no time configuration in this ca

se. The time of the BSC6800.

You need establish an IP Over ATM (IPoA) channel between the NodeB and BSC6800 in this case. The BSC6800 acts as an SNTP Server and the NodeBs as SNTP Clients. You need configure SNTP Server information for the BSC6800

carry out SET SNTPSRVPARA to configure the SNTP Server information

Page 19: BSC6800 TNL Data Configuration

19 Internal Use

Configuring Subrack Configuring Subrack

Subrack numbering rule

WRSS

(2)

WRBS

(5)

WRBS

(8)

WRBS

(11)

WRBS

(14)

WRBS

(17)

BAM

(0)

WRBS

(3)

WRBS

(6)

WRBS

(9)

WRBS

(12)

WRBS

(15)

WRBS

(1)

WRBS

(4)

WRBS

(7)

WRBS

(10)

WRBS

(13)

WRBS

(16)

Cabinet 0 Cabinet 1 Cabinet 2 Cabinet 3 Cabinet 4 Cabinet 5

Page 20: BSC6800 TNL Data Configuration

20 Internal Use

Configuring Subrack Configuring Subrack

Configure active/standby ports

Function Command

Add active/standby port ADD REDPORT

List active/standby port configuration LST REDPORT

Modify standby port MOD REDPORT

Remove active/standby port RMV REDPORT

Page 21: BSC6800 TNL Data Configuration

21 Internal Use

Configuring Subrack Configuring Subrack

Whether to back up the WOSE is dependent on the actual transmission network planning. If [WRBS interface board backup type] is set to ONE_TO_ONE, slot 0 and slot 15 of the WRBS will have an active-standby relation. Hereafter, all data can only be configured to slot 0 (slot 15 will synchronize the data automatically)

A WCDMA RNC Signalling Processing board (WSPU) consists of two subsystems. Subsystem 0 works for the WCDMA RNC radio frame processing boards (WFMRs) in odd-numbered slots. Subsystem 1 works for the WFMRs in even-numbered slots. For sharing between subsystems 0 and 1, you shall balance the WFRMs between the odd-numbered and even-numbered slots.

Function Command

Add WRBS ADD SUBRACK

List subrack LST SUBRACK

Remove WRBS RMV SUBRACK

Modify WRBS MOD SUBRACK

Query board state DSP BRD

Notify board Out-of-position CLR BRD

Page 22: BSC6800 TNL Data Configuration

22 Internal Use

Configuring Subrack Configuring Subrack

Configuring RFN Source Subrack The RFN plays an important role in the radio access network. It

works for coding/decoding between the RNC, NodeBs and UEs.

You shall specify a WRBS as the RFN source subrack carry out SET RFNSRC to configure the RNC source subrack

Page 23: BSC6800 TNL Data Configuration

23 Internal Use

Configuring Board Configuring Board

Configuring Active WHPU carry out SET WHPUAS to configure active WHPUs

Configuring WFSM carry out SET FANSPEED to configure the fan speed adjustme

nt mode

Page 24: BSC6800 TNL Data Configuration

24 Internal Use

Configuring OSPConfiguring OSP

carry out ADD OPC to add an OSP ADD OPC can run in only offline state. To make the

configuration effect, you need reset the system.

Page 25: BSC6800 TNL Data Configuration

25 Internal Use

Chapter 1 Basic informationChapter 1 Basic information

Chapter 2 Equipment data configuration

Chapter 3 Iub interface data configuration

Chapter 4 Iu-CS interface data configuration

Chapter 5 Iu-PS interface data configuration

Page 26: BSC6800 TNL Data Configuration

26 Internal Use

Chapter 3 Iub Interface Data ConfigurationChapter 3 Iub Interface Data Configuration

3.1 Iub Interface Data Configuration

overview

3.2 Iub Interface Data Configuration

MML Commands

3.3 Negotiating data of Iub interface

Page 27: BSC6800 TNL Data Configuration

27 Internal Use

Iub Interface Data Configuration overviewIub Interface Data Configuration overview

Page 28: BSC6800 TNL Data Configuration

28 Internal Use

Iub Interface Data Configuration overviewIub Interface Data Configuration overview

NodeBAAL2Path

RNC

User Plane

NodeBNCP

CCP 1~n RNC

Control Plane ALCAP

Adjnode

Page 29: BSC6800 TNL Data Configuration

29 Internal Use

Iub Physical Connectivity AlternativesIub Physical Connectivity Alternatives

Board Function

WBIE supports ATM over E1/T1 bearer mode. Each board provides 32 E1/T1 ports,

WOSESupporting ATM over E1 over SDH bearer mode. Each (optical) interface board provides 63 E1 ports and 8 E1 electric ports and supports Fractional ATM and CES functions.

WLPUSupporting ATM over SDH bearer mode. Each interface board can support at most 16 STM-1 ports, applicable to high-speed link transmission.

Page 30: BSC6800 TNL Data Configuration

30 Internal Use

Chapter 3 Iub Interface Data ConfigurationChapter 3 Iub Interface Data Configuration

3.1 Iub Interface Data Configuration overvie

w

3.2 Iub Interface Data Configuration

MML Commands

3.3 Negotiating data of Iub interface

Page 31: BSC6800 TNL Data Configuration

31 Internal Use

Iub Interface Data Configuration MML CommandsIub Interface Data Configuration MML Commands

Procedure of Iub configuration Configure Physical Layer Configure ATM Layer Configure SAAL UNI Configure Iub Link Configure Q.AAL2 Configure AAL2 Configure IPoA

Page 32: BSC6800 TNL Data Configuration

32 Internal Use

Configure Physical LayerConfigure Physical Layer

Configure E1/T1 attributes Set E1/T1 link attributes (SET E1T1) Set E1/T1 scramble(SET SCRAMBLE)

Notes: The state of scramble switches between the two ends of

E1/T1 should be set as the same. If several E1/T1s belong to the same IMA group, the state of the switches should be set as the same.

Page 33: BSC6800 TNL Data Configuration

33 Internal Use

Configure Physical LayerConfigure Physical Layer

PHY

PHY

PHY

IMA×éPHY

PHY

PHY

IMA×é

µ¥ATMÐÅÔªÁ÷

´ «Êä·½Ï ò£º°´ Ñ »·µÄ Î Ðò°ÑÐÅÔª· ÖÅäµ½÷Ì õµÍ ËÙµÄÎ ï Àí Á ·½ÓÊÕ·½Ï ò£º°Ñ ÷Ì õµÍ ËÙÎ ï Àí Á · ¹ ýÀ µÄÐÅÔªÖØл㳠ɵ¥¸ öÐÅÔªÁ÷¡ £

µÍ ËÙÎ ï Àí Á ·

µÍ ËÙÎ ï Àí Á ·

µÍ ËÙÎ ï Àí Á ·

£¨ À ×ÔATM² ã£©Ô ATMÐÅÔªÁ÷£¨ È¥ATM² 㣩

A single ATM cell flow (from the ATM layer)

IMA groupLow-speed physical link

Low-speed physical link

Low-speed physical link

IMA group

The original ATM cell flow (to the ATM layer)

At the Tx end: Cells are allocated to each low-speed physical link in a circular order

At the Rx end: The cells transmitted on each low-speed physical link are reassembled to a single cell group

Inverse multiplexing over ATM (IMA)

Page 34: BSC6800 TNL Data Configuration

34 Internal Use

Configure Physical LayerConfigure Physical Layer

User to Network Interface (UNI)

Page 35: BSC6800 TNL Data Configuration

35 Internal Use

Configure Physical LayerConfigure Physical Layer

The Fractional ATM

Page 36: BSC6800 TNL Data Configuration

36 Internal Use

Configure Physical LayerConfigure Physical Layer

Circuit Emulation Service (CES)

Page 37: BSC6800 TNL Data Configuration

37 Internal Use

Configure Physical LayerConfigure Physical Layer

E1/T1 application configuration when using WBIE/WBIEb

Task Step Operation

Add IMA link1 Use the ADD IMAGRP command to add an IMA group.

2 Use the ADD IMALNK command to add an IMA link to the IMA group. To add more IMA links, repeat this step.

Add UNI link 1 Use the ADD UNILNK command to add a UNI link. To add more UNI links, repeat this step.

Add FRA IMA link

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

2Use the ADD FRALNK command to add a FRA IMA link to the IMA group. Set the [Board type] to WBIE/WBIEb. Set th

e [Fractional link type] to FRAIMA. To add more FRA IMA links, repeat this step.

3Use the ADD TSCROSS command to add the timeslot cross connection function in the following case: The 2G equipment does not support timeslot cross connection while the FRA IMA link and the E1 link between the 2G

and BSC6800 equipment use different timeslots for transmission.

Add FRA ATM link

1Use the ADD FRALNK command to add a FRA ATM link. Set the [Board type] to WBIE/WBIEb. Set the [Fractional link

type] to FRAATM. To add more FRA ATM links, repeat this step.

2Use the ADD TSCROSS command to add the timeslot cross connection function in the following case: The 2G equipment does not support timeslot cross connection while the FRA ATM link and the E1 link between the 2G

and BSC6800 equipment use different timeslots for transmission.

Page 38: BSC6800 TNL Data Configuration

38 Internal Use

Configure Physical LayerConfigure Physical Layer

E1/T1 application configuration when using WOSE/WOSEb optical port

Task Step Operation

Add IMA link

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

2Use the ADD IMALNK command to add an IMA link to the IMA group. To add more IMA links, repeat this step.

Add UNI link 1 Use the ADD UNILNK command to add a UNI link. To add more UNI links, repeat this step.

Page 39: BSC6800 TNL Data Configuration

39 Internal Use

Configure Physical LayerConfigure Physical Layer

E1/T1 application configuration when using WOSE/WOSEb electrical port

Task Operation

Add FRA ATM linkUse the ADD FRALNK command to add a FRA ATM link. Set the [Board type] to WOSE/WOSEb. To add more FRA ATM links, repeat this step.

Add SDT CES linkUse the ADD SDTCES command to add an SDT CES link. To add more SDT CES links, repeat this step.

Add UDT CES linkUse the ADD UDTCES command to add a UDT CES link. To add more UDT CES links, repeat this step.

Page 40: BSC6800 TNL Data Configuration

40 Internal Use

Configure Physical LayerConfigure Physical Layer

IMA group and link rules:

RUN

ALMACT

CLK2

E1/T 1

E1/T 1

CLK1

E1/T 1

E1/T 1

RUN

ALMACT

E1/T1

CLK2

CLK1

OPT

0~150~41

16~3142~62

0~7

IMA/UNI/FRAATM/FRA IMA

link No.

IMA/UNIlink No.

IMA group No.

FRA ATM/CESlink No.

0~7

8~15

16~23

24~31

0~31

WBIEWBIEb WOSE/WOSEb

IMA group No.

Page 41: BSC6800 TNL Data Configuration

41 Internal Use

Configure ATM Layer (ADD ATMTRF) In the BSC6800 system, the configuration of ATM PVC attributes

mainly refers to the configuration of ATM traffic resources. After ATM traffic resources configuration is completed, the traffic resources can be directly referenced through [Flow index] during the configuration of SAAL, AAL2 PATH, IPoA.

Configure ATM LayerConfigure ATM LayerConfigure ATM LayerConfigure ATM Layer

Page 42: BSC6800 TNL Data Configuration

42 Internal Use

Configure ATM LayerConfigure ATM Layer

ATM service types

Service typeDescription

Full name Abbreviation

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

Real Time Variable Bit Rate

RT-VBRUsed to describe the service with variable data rates and strict real time

requirement, for example, interactive compressed video such as videoconference.

Non-Real Time Variable Bit Rate

NRT-VBRUsed in timing transmission as E-mail transmission. In such a case,

some delays and variations can be accepted by the application.

Unspecified Bit Rate UBR

No commitment or feedback to congestion. It is suitable for sending IP data. In case of congestion, UBR cells will be discarded. However, neither relevant feedback nor the request for slowing down the transmission speed will be returned to the sender.

The BSC6800 also supports UBR+, which ensures the minimum cell rate.

Page 43: BSC6800 TNL Data Configuration

43 Internal Use

Configure ATM LayerConfigure ATM Layer

ATM traffic descriptions

Parameter

Meaning

Full name Abbreviation

Peak cell rate PCR Max. cell transmission rate

Sustainable cell rate SCR Average cell transmission rate during a long term

Minimum cell rate MCR Min. cell transmission rate

Cell delay variation tolerance CDVT Max. tolerable cell jitter (0.1 s)

Cell loss priority CLPIndicating which cells can be discarded (CLP=1), and which cells had better not be discarded (CLP=0) in the case of network congestion

Tag TAGGING Tagging the cells with CLP=0

Page 44: BSC6800 TNL Data Configuration

44 Internal Use

At least 3 to-NodeB SAAL UNI links should be configured, 1 for NCP, 1 for CCP, and 1 for Q.AAL2.

One WSPUb subsystem can control up to 300 SAAL links. The WRSS can provide other devices with up to 13800 PVCs, includi

ng IPoA PVCs, SAAL links and AAL2 paths

Configure SAAL UNIConfigure SAAL UNI Configure SAAL UNIConfigure SAAL UNI

Page 45: BSC6800 TNL Data Configuration

45 Internal Use

Configure NodeB Configure NCP Configure CCP

Configure Iub portConfigure Iub portConfigure Iub portConfigure Iub port

Page 46: BSC6800 TNL Data Configuration

46 Internal Use

Configure NodeB (ADD NODEB ) NodeB and the corresponding SAAL links (including NCP, CCP and

Q.AAL2) should be configured in the same WSPU subsystem. One WSPUb subsystem can support up to 50 NodeBs and 300 SAA

L links ,One WSPUb subsystem can support up to150 cells.

Configure Iub portConfigure Iub portConfigure Iub portConfigure Iub port

Page 47: BSC6800 TNL Data Configuration

47 Internal Use

Configure NCP(ADD NCP) As NodeB control port, NCP is used to transmit NBAP common pro

cedure messages of the Iub interface. There can be only one NCP in a NodeB, i.e. there exists a one-to-one relationship between NCP and the NodeB.

Notes: The corresponding NodeB should be successfully configured. The SAAL link that accompanies the NCP link should be successfull

y configured and stay in idle status (with the command LST SAALLNK).

The SAAL link should be of UNI type.

Configure Iub portConfigure Iub portConfigure Iub portConfigure Iub port

Page 48: BSC6800 TNL Data Configuration

48 Internal Use

Configure CCP(ADD CCP) As communication control port, CCP is used to transmit NBAP

dedicated procedure messages of the Iub interface. There can be multiple CCPs in a NodeB, i.e. there exists a many-to-one relationship between the CCPs and NodeB.

Notes: To guarantee reliability, you shall configure two or more CCP

links as long as the corresponding SAAL links exist For the same CCP link, its [Port No.] at RNC must be

consistent with that at NodeB, for which the negotiation of RNC with NodeB is needed.

The SAAL link that accompanies the CCP link should be successfully configured and stay in idle status (with the command LST SAALLNK).

The SAAL link should be of UNI type.

Configure Iub portConfigure Iub port

Page 49: BSC6800 TNL Data Configuration

49 Internal Use

Configure Q.AAL2Configure Q.AAL2

Q.AAL2 adjacent node

Page 50: BSC6800 TNL Data Configuration

50 Internal Use

Configure Q.AAL2 adjacent node (ADD AAL2ADJNODE)

Notes: the NodeB corresponding to [NodeB name] must have been configured. It should be noted that NodeBs and adjacent AAL2 nodes of IUB interfac

e are in one-to-one relationship.

Configure Q.AAL2Configure Q.AAL2Configure Q.AAL2Configure Q.AAL2

Page 51: BSC6800 TNL Data Configuration

51 Internal Use

Configure AAL2 PATHConfigure AAL2 PATHConfigure AAL2 PATHConfigure AAL2 PATH

Configure AAL2 PATH Configure AAL2 route

Page 52: BSC6800 TNL Data Configuration

52 Internal Use

The system has the following capability limits for AAL2 path. The BSC6800 can support up to 7360 AAL2 paths. One WSPUb subsystem can control up to 230 AAL2 paths One WBIE/WBIEb can terminate up to 200 AAL2 paths. One WOSE/WOSEb can terminate up to 200 AAL2 paths. One WMUX/WMUXb can terminate up to 60 AAL2 paths. The WRSS can provide other devices with up to 13800 PVCs, including

IPoA PVCs, SAAL links and AAL2 paths

Configure AAL2 PATHConfigure AAL2 PATHConfigure AAL2 PATHConfigure AAL2 PATH

Page 53: BSC6800 TNL Data Configuration

53 Internal Use

Configure AAL2 path ( ADD AAL2PATH ) The adjacent node corresponding to the AAL2 path must have been con

figured (see ADD AAL2ADJNODE). All AAL2 paths of the Iub interface are terminated at WBIE or WOSE . [AAL2 PATH ID] should also be specified to identify the AAL2 path. This

index is to number the AAL2 path of the corresponding adjacent node and should be negotiated with it

Configure AAL2 PATHConfigure AAL2 PATHConfigure AAL2 PATHConfigure AAL2 PATH

Page 54: BSC6800 TNL Data Configuration

54 Internal Use

Configure AAL2 PATHConfigure AAL2 PATH

Configure AAL2 route (ADD AAL2RT) The added AAL2 path can reach the adjacent node, but it might not

reach the destination node . the establishment of an AAL2 route may help it to achieve this object via the other nodes between BSC6800 and the destination node

Even if the destination node is no other than the adjacent node, an AAL2 route is still required

ATM address is used to identify the ATM network node

Page 55: BSC6800 TNL Data Configuration

55 Internal Use

Configure IPoAConfigure IPoAConfigure IPoAConfigure IPoA

Page 56: BSC6800 TNL Data Configuration

56 Internal Use

Configure IPoAConfigure IPoA

Configure IPoA Client (ADD IPOACLIENT)

Configure IPoA PVC(ADD IPOAPVC)

Notes: [IP address] and [Peer IP address] should be in the same subne

t and only one IPoA PVC can exist between them. If [IP address] is for the WMPU, [TX flow index] must be the sa

me as [RX flow index].

Page 57: BSC6800 TNL Data Configuration

57 Internal Use

Configure IPoAConfigure IPoA

Configure IP route Configure BAM route (route add) Configure the IP route of the IPoA path from WMUX to NodeB(ADD

IPRT)

Page 58: BSC6800 TNL Data Configuration

58 Internal Use

Chapter 3 Iub Interface Data ConfigurationChapter 3 Iub Interface Data Configuration

3.1 Iub Interface Data Configuration overvie

w

3.2 Iub Interface Data Configuration

MML Commands

3.3 Negotiating data of Iub interface

Page 59: BSC6800 TNL Data Configuration

59 Internal Use

Negotiating Data of Iub InterfaceNegotiating Data of Iub Interface

Sub itemExample

Negotiation Item

Negotiation data related to PVC:

VPI VCIService

typePCR

(cell/s)Traffic

descriptionCommand

Control plane*

NCP 7 60 CBR 1236 NOCLPNOSCR

ADD ATMTRFADD SAALLNKADD NCP

CCP(with port No. of 1)

7 61 CBR 1236 NOCLPNOSCR

ADD ATMTRFADD SAALLNKADD CCP

Q.AAL2 7 62 CBR 1236 NOCLPNOSCR

ADD ATMTRFADD SAALLNKADD AAL2ADJNODE

User planeAAL2 PATH(with PATH to be negotiated)

9 48 CBR 2473

NOCLPNOSCRCDVT(CDVT102400 s)

ADD ATMTRFADD AAL2PATH

Management plane* IPoA PVC 9 49 CBR 1236 NOCLPNOSCR

ADD ATMTRFADD IPOAPVC

Page 60: BSC6800 TNL Data Configuration

60 Internal Use

Negotiating Data of Iub InterfaceNegotiating Data of Iub Interface

Other negotiation data:

Negotiation item ExampleCommand

Other negotiation items IPoA PVC

BSC6800 ATM Address0x4502030405060708090001020304050607080900NodeB ATM Address0x4507070707070707070707070707070707070707

ADD AAL2RT

IP address & mask

BSC6800 IP Address11.13.1.200, Mask255.255.255.0NodeB IP Address11.13.1.1, Mask255.255.255.0

ADD IPOACLIENTADD IPOAPVCADD IPRT

NodeB local ID* Local CellID0ADD LOCELL

Page 61: BSC6800 TNL Data Configuration

61 Internal Use

Chapter 1 Basic informationChapter 1 Basic information

Chapter 2 Equipment data configuration

Chapter 3 Iub interface data configuration

Chapter 4 Iu-CS interface data configuration

Chapter 5 Iu-PS interface data configuration

Page 62: BSC6800 TNL Data Configuration

62 Internal Use

Chapter 4 Iu-CS Interface Data Chapter 4 Iu-CS Interface Data ConfigurationConfiguration

4.1 Iu-CS Interface Data Configuration overview

4.2 Iu-CS Interface Data Configuration

MML Commands

4.3 Negotiating data of Iu-CS interface

Page 63: BSC6800 TNL Data Configuration

63 Internal Use

Iu-CS Interface Data Configuration overviewIu-CS Interface Data Configuration overview

Page 64: BSC6800 TNL Data Configuration

64 Internal Use

Iu-CS Interface Data Configuration overviewIu-CS Interface Data Configuration overview

Iu-CS interface Board

Board Function

WLPUSupporting the ATM over SDH bearer mode and applicable to high-speed link transmission. Each interface board can support at most 16 STM-1 ports or 4 STM-4 ports.

WBIE supports ATM over E1/T1 bearer mode. Each board provides 32 E1/T1 ports.

WOSESupporting the ATM over E1 over SDH bearer mode. Each interface board provides one 155Mbps optical port.

Page 65: BSC6800 TNL Data Configuration

65 Internal Use

Iu-CS Interface Data Configuration overviewIu-CS Interface Data Configuration overview

OSP

MTP3bLinkSet

MTP3bLink

RNC

DSP1

MSCControl plane

OSPAAL2Path

User plane

DSP1

MSC

AdjNode

Page 66: BSC6800 TNL Data Configuration

66 Internal Use

Chapter 4 Iu-CS Interface Data Chapter 4 Iu-CS Interface Data ConfigurationConfiguration

4.1 Iu-CS Interface Data Configuration overview

4.2 Iu-CS Interface Data Configuration

MML Commands

4.3 Negotiating data of Iu-CS interface

Page 67: BSC6800 TNL Data Configuration

67 Internal Use

Iu-CS Interface Data Configuration MML CommandsIu-CS Interface Data Configuration MML Commands

Procedure of Iu-CS configuration Configure Physical Layer Configure ATM Layer Configure SAAL NNI Configure MTP3-b Configure Q.AAL2 Configure AAL2

Page 68: BSC6800 TNL Data Configuration

68 Internal Use

Configure Physical LayerConfigure Physical Layer

Carry out ADD REDPORT to add an active/standby relationship for the WLPU

Page 69: BSC6800 TNL Data Configuration

69 Internal Use

Configure ATM Layer (ADD ATMTRF) In the BSC6800 system, the configuration of ATM PVC attributes

mainly refers to the configuration of ATM traffic resources. After ATM traffic configuration is completed, the traffic resources can be directly referenced through [Flow index] during the configuration of SAAL, AAL2 PATH, IPoA.

Configure ATM LayerConfigure ATM Layer Configure ATM LayerConfigure ATM Layer

Page 70: BSC6800 TNL Data Configuration

70 Internal Use

See Iub, but when specifying [Interface type] of SAAL, please select "NNI".

Configure SAAL NNIConfigure SAAL NNIConfigure SAAL NNIConfigure SAAL NNI

Page 71: BSC6800 TNL Data Configuration

71 Internal Use

Configure MTP3-bConfigure MTP3-bConfigure MTP3-bConfigure MTP3-b

Adding MTP3B data includes the following: Adding DSP Adding signalling link set Adding signalling link Adding route data

Page 72: BSC6800 TNL Data Configuration

72 Internal Use

Configure MTP3-bConfigure MTP3-bConfigure MTP3-bConfigure MTP3-b

The system has the following limits for MTP3B. The BSC6800 can support up to 608 MTP3B links. One WSPUb subsystem can support up to 50 MTP3B links. The BSC6800 can support up to 76 MTP3B routes

Page 73: BSC6800 TNL Data Configuration

73 Internal Use

Configure MTP3-bConfigure MTP3-bConfigure MTP3-bConfigure MTP3-b

Configure DSP (ADD N7DPC ) The BSC6800 supports six types of DSPs , up to 38 DSPs can be c

onfigured

DSP type Description

IUCSMSC in R99. It has the functions of the control planes of both the radio network layer and

transport network layer on the Iu-CS interface.

IUCS_ALCAPMedia Gateway in R4. It has the functions of the control plane of the transport network lay

er on the Iu-CS interface.

IUCS_RANAPMSC Server in R4. It has the functions of the control plane of the radio network layer on th

e Iu-CS interface.

IUPS Signalling point in the control plane of the Iu-PS interface.

IUR Neighboring RNC

STP Signalling transfer point. The BSC6800 supports up to 2 STP DSPs.

Page 74: BSC6800 TNL Data Configuration

74 Internal Use

Configure MTP3-bConfigure MTP3-bConfigure MTP3-bConfigure MTP3-b

Use the ADD MTP3BLKS command to add an MTP3B signalling link set to the DSP.

Use the ADD MTP3BLNK command to add a signalling link in an MTP3B signalling link set.

Use the ADD MTP3BRT command to add a route to the DSP

[Signalling link selection mask] is used for load sharing of links in a linkset. The result of this value AND the value of [signalling route selection mask] in ADD N7DPC should be 0

Up to 16 signalling links can be added to a signalling linkset

Page 75: BSC6800 TNL Data Configuration

75 Internal Use

See Iub

Configure Q.AAL2Configure Q.AAL2Configure Q.AAL2Configure Q.AAL2

Page 76: BSC6800 TNL Data Configuration

76 Internal Use

Configure AAL2 PathConfigure AAL2 PathConfigure AAL2 PathConfigure AAL2 Path

MSC BSC6800

WSPU subsystem

AAL2 connection 1

AAL2 connection 2

AAL2 connections 3

AAL2 PATH

Configure AAL2 PATH Configure AAL2 route

Page 77: BSC6800 TNL Data Configuration

77 Internal Use

Configure AAL2 PATH See Iub

Configure AAL2 PathConfigure AAL2 PathConfigure AAL2 PathConfigure AAL2 Path

Page 78: BSC6800 TNL Data Configuration

78 Internal Use

Configure AAL2 route see Iub

Configure AAL2 PathConfigure AAL2 PathConfigure AAL2 PathConfigure AAL2 Path

Page 79: BSC6800 TNL Data Configuration

79 Internal Use

Chapter 4 Iu-CS Interface Data Chapter 4 Iu-CS Interface Data ConfigurationConfiguration

4.1 Iu-CS Interface Data Configuration overview

4.2 Iu-CS Interface Data Configuration

MML Commands

4.3 Negotiating data of Iu-CS interface

Page 80: BSC6800 TNL Data Configuration

80 Internal Use

Negotiating data of Iu-CS interfaceNegotiating data of Iu-CS interface Negotiating data of Iu-CS interfaceNegotiating data of Iu-CS interface

Sub Item

Negotiation Item

Example

Negotiation data related to PVC

SLC VPI VCIService

typePCR

(cell/s)Traffic

descriptionCommand

Control plane

MTP3-b link 0 10 54 CBR 3708 NOCLPNOSCRADD ATMTRFADD SAALLNKADD MTP3BLNKMTP3-b link 1 10 55 CBR 3708 NOCLPNOSCR

User plane

AAL2 PATH (AAL2 PATH ID is to be negotiated)

None 7 51 CBR 7434

NOCLPNOSCRCDVT(CDVT102400 s)

ADD ATMTRFADD AAL2PATH

Page 81: BSC6800 TNL Data Configuration

81 Internal Use

Negotiating data of Iu-CS interfaceNegotiating data of Iu-CS interface Negotiating data of Iu-CS interfaceNegotiating data of Iu-CS interface

Other negotiation data

Negotiation itemExample

Command

Other negotiation items

ATM address

BSC6800 ATM Address0x4502030405060708090001020304050607080900 MSC ATM Address0x4507070707070707070707070707070707070707

ADD AAL2RT

Signalling point code

BSC6800 SPC0x900 MSC DPC0xaa

ADD N7DPC

Page 82: BSC6800 TNL Data Configuration

82 Internal Use

Chapter 1 Basic informationChapter 1 Basic information

Chapter 2 Equipment data configuration

Chapter 3 Iub interface data configuration

Chapter 4 Iu-CS interface data configuration

Chapter 5 Iu-PS interface data configuration

Page 83: BSC6800 TNL Data Configuration

83 Internal Use

Chapter 5 Iu-PS Interface Data ConfigurationChapter 5 Iu-PS Interface Data Configuration

5.1 Iu-PS Interface Data Configuration

overview

5.2 Iu-PS Interface Data Configuration

MML Commands

5.3 Negotiating data of Iu-PS interface

Page 84: BSC6800 TNL Data Configuration

84 Internal Use

Iu-PS Interface Data Configuration overviewIu-PS Interface Data Configuration overview

Page 85: BSC6800 TNL Data Configuration

85 Internal Use

Chapter 5 Iu-PS Interface Data ConfigurationChapter 5 Iu-PS Interface Data Configuration

5.1 Iu-PS Interface Data Configuration

overview

5.2 Iu-PS Interface Data Configuration

MML Commands

5.3 Negotiating data of Iu-PS interface

Page 86: BSC6800 TNL Data Configuration

86 Internal Use

Iu-PS Interface Data Configuration MML CommandsIu-PS Interface Data Configuration MML Commands

Procedure of Iu-PS configuration Configure Physical Layer Configure ATM Layer Configure SAAL NNI Configure MTP3-b Configure IPoA

Page 87: BSC6800 TNL Data Configuration

87 Internal Use

See Iu-CS

Configure Physical LayerConfigure Physical LayerConfigure Physical LayerConfigure Physical Layer

Page 88: BSC6800 TNL Data Configuration

88 Internal Use

See Iub

Configure ATM LayerConfigure ATM LayerConfigure ATM LayerConfigure ATM Layer

Page 89: BSC6800 TNL Data Configuration

89 Internal Use

See Iu-CS

Configure SAAL NNIConfigure SAAL NNIConfigure SAAL NNIConfigure SAAL NNI

Page 90: BSC6800 TNL Data Configuration

90 Internal Use

See Iu-CS

Configure MTP3-bConfigure MTP3-bConfigure MTP3-bConfigure MTP3-b

Page 91: BSC6800 TNL Data Configuration

91 Internal Use

Configure IPoAConfigure IPoAConfigure IPoAConfigure IPoA

PVC1

Bind PVC to IPoA client

BSC6800

SGSN gateway

IPoA client

WRSSWHPU

WLPU

SGSN gateway IP Destination IP

SGSN

Configure IPoA Client Bind IPoA PVC Configure IP route

Page 92: BSC6800 TNL Data Configuration

92 Internal Use

Configure IPoAConfigure IPoAConfigure IPoAConfigure IPoA

Configure IPoA Client (ADD IPOACLIENT) Each WHPU has two subsystems, numbered 1 and 2. Each sub

system can hold up to 5 IPoA clients. The WHPUs work by sharing the resource pool.

Page 93: BSC6800 TNL Data Configuration

93 Internal Use

Configure IPoAConfigure IPoAConfigure IPoAConfigure IPoA

configureIPoA PVC(ADD IPOAPVC) Each IPoA Client need be configured with 1 IPoA PVC. The Tx traffic index and Rx traffic index of an IPoA PVC must be

the same.

Page 94: BSC6800 TNL Data Configuration

94 Internal Use

Configure IPoAConfigure IPoAConfigure IPoAConfigure IPoA

Configure IP route (ADD IPRT) Each WHPU subsystem need must be configured with IP route

to SGSN.

Page 95: BSC6800 TNL Data Configuration

95 Internal Use

Chapter 5 Iu-PS Interface Data ConfigurationChapter 5 Iu-PS Interface Data Configuration

5.1 Iu-PS Interface Data Configuration overview

5.2 Iu-PS Interface Data Configuration

MML Commands

5.3 Negotiating data of Iu-PS interface

Page 96: BSC6800 TNL Data Configuration

96 Internal Use

Iu-PS Interface ConfigurationIu-PS Interface Configuration Iu-PS Interface ConfigurationIu-PS Interface Configuration

Sub Item

项Example

Negotiation Item商 项

Negotiation data related to PVC

SLC VPI VCIService

typePCR

(cell/.s)Traffic description Command

Control plane MTP3-b link 0 12 50 CBR 3708 NOCLPNOSCR

ADD ATMTRFADD SAALLNKADD MTP3BLNK

User plane

IPoA PVC None 13 60 UBR 351415

NOCLPNOSCRCDVT(CDVT102400 s)

ADD ATMTRFADD IPOAPVC

IPoA PVC None 13 61 UBR 351415

NOCLPNOSCRCDVT(CDVT102400 s)

ADD ATMTRFADD IPOAPVC

Page 97: BSC6800 TNL Data Configuration

97 Internal Use

Iu-PS Interface ConfigurationIu-PS Interface Configuration Iu-PS Interface ConfigurationIu-PS Interface Configuration

Other negotiation data

Negotiation item ExampleCommand

Other negotiation items

IP address and mask

BSC6800 IP Address172.23.10.68, Mask255.255.255.0BSC6800 IP Address172.23.10.69, Mask255.255.255.0SGSN IP Address172.23.5.217, Mask255.255.255.0SGSN Gateway IP Address172.23.10.80, Mask255.255.255.0

ADD IPOACLIENTADD IPOAPVCADD IPRT

Signalling point code

BSC6800 SPC0x900SGSN SPC0x1500 ADD N7DPC

Network mode of operation* NMOMode1 ADD

CNDOMAIN

Page 98: BSC6800 TNL Data Configuration

98 Internal Use