OMC331400 BSC6900 GSM V900R014 Data Configuration Based o

BSC6900 GSM V900R014 Data Configuration Based
on LMT
Confidential Information of Huawei. No Spreading Without Permission

on LMT

on LMT

on LMT

on LMT

on LMT

on LMT

on LMT

on LMT
When the OMU is installed for the first time, the CM right is disabled by default, and the
CM right is not checked if you run a configuration command. You can enable the CM right
through the SET CMCTRLSW command. Before you run a configuration command, you
should run this command to apply for CM right.
By default, the control switch of the data configuration rights is set to OFF. In this
case, all users can perform data configuration of the BSC6900 through the LMT or
M2000.
If the CM control right is in idle state or belongs to the current user, REQ CMCTRL
can be executed successfully. If the CM control right belongs to other users, this
command cannot be executed successfully.
When the control switch of the data configuration rights is ON, only one user has the data
configuration rights at a time.
After the data configuration is complete, you can release the data configuration rights by
running the REL CMCTRL command. In this way, another user can run the REQ CMCTRL
command to obtain the data configuration rights.
If the user with the data configuration rights exits the LMT, the data configuration rights
are released automatically. In this case, another user can also run the REQ CMCTRL
command to obtain the data configuration rights.
Example:
FOC CMCTRL:;
REQ CMCTRL:;
SET CMCTRLSW: CTRLSW=OFF;
LST CMCTRLSW:;
LCK CMCTRL: RSNDES=UPGRADE;
ULK CMCTRL:;

on LMT
In effective mode
the data configured takes effect immediately on the subrack.

In ineffective mode
the data configured for the subrack takes effect only in the OMU and not on the
subrack.
In this case, you can run the SET CFGDATAEFFECTIVE command to set the mode
to effective mode, run the FMT DATA command to generate the data
configuration file for the subrack, and then run the RST SUBRACK command to
reset the subrack. In this way, the subrack can load the data configuration from
the OMU so that the data takes effect on the subrack.
When a subrack is in ineffective mode, you cannot query, compare, or perform

CRC check on the data between the host and the OMU. In addition, you cannot
configure the host data of the subrack.
When all the subracks are in non-effective mode, license verification is not
performed. When a subrack is switched from the non-effective mode to the
effective mode, the OMU checks whether the data configuration exceeds the
limitations of the license. If the data configuration exceeds the limitations of the
license, the mode switching is not allowed.
If the OMU is newly installed, subrack 0 is in ineffective mode by default. If a

subrack is newly added, it is in ineffective mode by default.
Example:
SET CFGDATAINEFFECTIVE: SRN=0;
SET CFGDATAEFFECTIVE:;

on LMT
Be careful with this command. After the operation, all data configured previously
can not be restored.
After execute this command, license will be initialized so user should configure
data and activate the license file again.
It is general used in the data configuration for the first time for adding or
modifying the BSC with a big batch of data.

on LMT

on LMT

on LMT
NOTE
1. For a BSC configured with a 1800 MHz cell, you cannot set the value of
"Freq.Band" to "PSC1900". For a BSC configured with a 1900 MHz cell, you
cannot set the value of "Freq.Band" to "DCS1800".
2. After the value of Service mode is changed, the service modes of all subracks
are changed accordingly at the same time. Therefore, you must reset all the
subracks.
3. For Interface tag, if the BSC needs to support GPRS services, EDGE services,
AMR services, eMLPP services, inter-RAT handover, and A over IP mode,
"GSM_PHASE_2Plus" is recommended.
Example
To set basic attributes of a BSC (Area Code = 021; CC = 86), run the following command:
SET BSCBASIC: AreaCode=021, CC=86;

on LMT
Function
Use this command to add a GSM operator.

Example:
ADD GCNOPERATOR: OperatorType=PRIM, OPNAME=BH01", MCC="460",

MNC="08", MSCPOOLALLOW=NO, SGSNPOOLALLOW=NO;

on LMT
Signal point data format
When this parameter is set to "WNF", the SPC is expressed in the form of an integer number.
When this parameter is set to "DNF", the SPC is expressed in three segments. The number of bits
included in each segment depends on the setting of the signaling point code bits parameter.
When the signaling point code bits parameter is set to "BIT16", the number of bits
included in each segment is 4, 8, and 4.
Assume that the signaling point code bits parameter is set to "BIT14" and the SPC is expressed in
three segments 5-7-2. You can perform the following steps to convert this SPC to an integer:
1. Convert the value in each segment to a binary number and fill 0s into a segment if the
number of bits included in that segment does not meet the requirements. The binary
number of value 5 in the first segment is 101, which is of three bits. Thus, you need not
to fill 0s into the first segment. The binary number of value 7 in the second segment is
111. As previously stated, when the signaling point code bits parameter is set to "BIT14",
eight bits must be included in the second segment. Thus, the second segment is put as
00000111. Accordingly, you can calculate the binary number of the value in the third
segment. The binary number of 5-7-2 is 101 00000111 010.
2. Convert this binary number to a decimal number. The decimal form of this binary
number is 10,298.
Example:
ADD OPC: NAME="MBSC NO1", SPX=0, NI=NATB, SPCBITS=BIT14, SPDF=WNF, SPC=H'A00,

RSTFUN=OFF, HOSTTYPE=SINGLEHOST;

on LMT
DPC is used to address the peer element of BSC in SSN.7 network.

For one BSC:
A DSP can be configured only when the Originating signaling Point (OSP) is configured.
The DSP code must be unique and cannot be the same as OSP code.
DSP type:
IUCS: indicates the IU interface CS control plane and user plane signaling point.
IUPS: indicates the signaling point of the IU interface PS control signaling plane.
IUR: indicates the signaling point of the base station controller that is connected to the RNC.
IUCS_ALCAP: indicates the signaling point of the IU interface CS user signaling plane.
IUCS_RANAP: indicates the signaling point of the IU interface CS control plane.
STP: indicates the signaling transfer point.
AAL2SWITCH: indicates the ATM switch.
A: indicates the signaling point of the A interface control signaling plane.
IUR_G: indicates the signaling point of the base station controller that is connected to the
BSC.
LB: indicates the signaling point of the LB interface.

Signaling route mask
For example, B0000 indicates that up to one route is used for the load sharing, B0001 and
B1000 indicate that up to two routes are used for the load sharing. The additional routes
are not used for the load sharing.
The AND operation between this value and Signaling Link mask in the link set is equal to 0.
Example:
ADD N7DPC: NAME="TEST NO1", DPX=3, SPX=1, SPDF=WNF, DPC=H'AB, DPCT=IUR,

SLSMASK=B0010, NEIGHBOR=YES, STP=OFF, BEARTYPE=M3UA, PROT=ITUT;

on LMT
If we adopt IP transfer mode in Iu-CS, Iu-PS ,Iur or A interface, we must define the M3UA
local entity and destination entity.
Before running this command, you must have configured the OSP.
The default value of the routing context is 4294967295, which indicates that the routing
context is not configured. The value of the routing context varies with the type of the local
entity. If the routing context is configured, the value must be negotiated with that
configured on the peer NE.
Local entity type
M3UA_ASP: suggested to use when there is a signaling transfer point (STP)

between the local entity and the destination entity
M3UA_IPSP: suggested to use when there is no signaling transfer point (STP)

Example:
ADD M3LE: LENO=0, SPX=0, ENTITYT=M3UA_ASP, RTCONTEXT=0, NAME="Test";

on LMT

on LMT
If we adopt IP transfer mode in Iu-CS, Iu-PS, Iur or A interface, we must define the M3UA
local entity and destination entity.
The DSP corresponding to DSP index must exist.
The local entity corresponding to Local entity No. must exist.
The default value of Routing Context is 4294967295(0xFFFFFFFF), which indicates that
the routing context is not configured. If the routing context is configured, the value must
be negotiated with the peer NE.
Destination entity type
M3UA_ASP: suggested to use when there is a signaling transfer point (STP)

M3UA_IPSP: suggested to use when there is no signaling transfer point (STP)

M3UA_SS7SP: suggested to use when the destination entity is a narrowband

signaling point
M3UA_SP: represents all types of the destination entity

Example:
ADD M3DE: DENO=0, LENO=0, DPX=1, ENTITYT=M3UA_IPSP, RTCONTEXT=1,

NAME="MSC";

on LMT

on LMT

on LMT
System description
Description of the Base Station Controller

NE Name
Name of the Base Station Controller of Network Element

Contact mode of the manufacturer
Contact way of the Base Station Controller supplier

System Location
Location of the Base Station Controller

System services
Services provided by the Base Station Controller

Example:
SET SYS: SYSDESC="HUAWEI MBSC", SYSOBJECTID="BSC ONLY",

SYSCONTACT="8008302118", SYSLOCATION="LOCAL", SYSSERVICES="BSC";

on LMT
Remote cabinet is used for TransCoder Rack (TCR) for GSM.

Function
Use ADD SUBRACK to add a subrack during system initialization and capacity
expansion of the system.
Note
1. The Main Processing Subrack (MPS) applies the default system configuration.
You do not need to add this subrack by running the MML command.
2. Before adding a subrack, ensure that the cabinet where the subrack is added
exits, and that the MPS works properly.
3. Each Extended Processing Subrack (EPS) needs to be equipped with a fan

monitoring communication board. The power distribution monitoring board can be
configured as required. Generally, only one EPS in a cabinet can be connected to
the power distribution monitoring board.
4. The actual board type in the subrack must be consistent with the configured
type.The subrack number of the EPS/TCS must be consistent with that indicated by
the DIP switches.
5. The port on the SCU in the central subrack that is connected to the added
subrack must be enabled.
6. The relation between the parameter Subrack No. and the parameter Cabinet No.
is described as follows: Cabinet No. = Subrack No./3. Cabinet No. is the quotient of
that formula.
Example:
ADD CAB: CN=1, CABT=NO;
ADD SUBRACK: SRN=2, SRName="test2", CONNPWR=NO, TYPE=EPS;


on LMT
Note
1. This command cannot be used by port 0 and port 1 on the SCUa board configured in
the EPS subrack.
2. When configuring the OMU board in external mode, one can only enable the attributes
of one port, either port 10 or port 11, on the SCUa board in subrack 0. In other cases,
when the attributes of an even numbered port are set, the attributes of the neighboring
odd numbered port will be automatically set according to the attributes of the even
numbered port. For example, if the attributes of port 2 on the SCUa board are set, the
attributes of port 3 on the same board will be set accordingly.
3. When configuring the OMU board in external mode, one can only enable the attributes
of one port, either port 6 or port 7, on the SCUb board in subrack 0. In other cases, when
the attributes of an even numbered port are set, the attributes of the neighboring odd
numbered port will be automatically set according to the attributes of the even numbered
port. For example, if the attributes of port 2 on the SCUb board are set, the attributes of
port 3 on the same board will be set accordingly.
4. You can perform settings in batches by running this command. If the subrack number,
port number, and port switch are specified, you can modify the attributes of a specified
port on an SCUa/SCUb board. If only the subrack number and port switch are specified,
you can modify the attributes of all ports on the specified SCUa/SCUb board. If the
attributes of a port on an SCUa/SCUb board cannot be modified, batch setting does not
take effect on this port. In addition, when the external OMU is used, setting the ports on
the SCUa board in subrack 0 in batches does not affect ports 10 and port 11, and setting
the ports on the SCUb board in subrack 0 in batches does not affect ports 6 and 7.
5. For the active and standby SCUa/SCUb boards, if you set the attributes of the port on
one SCUa/SCUb board, those of the port on the other SCUa/SCUb boards are also set.
6. When the SCUa and SCUb board are installed in the same subrack, this command can
only be used to set the attributes of the ports on the board located in a specified slot.

on LMT
Please configure the boards in the following sequence: XPU, TNU, INT/DPU, NIU,OMU.
The SCUa boards are automatically added according to the addition of subracks and
cannot be removed.
The GCUa and GCGa boards are automatically configured in the MPS and cannot be
removed.
Board class:
INT: interface board
DPU: data processing unit
XPU/SPU: signaling processing unit
OMU: Operation and maintenance unit
SAU: Service Aware Unit

The SAU board is optional. One SAU board occupies two slots and a
maximum of one SAU board can be configured. The SAU board filters and
takes statistics of the data reported by NEs and then reports the result to
the Nastar server.
TNU: TDM switching Networking Unit

Example:
ADD BRD: SRN=0, BRDCLASS=XPU, BRDTYPE=XPUa, LGCAPPTYPE=RGCP, SN=0;

on LMT
OAM: Operation And Maintenance Process

TDM_ Switching:TDM switching process
GCP:All the GCP subsystems are configured as CPUS to act as the control plane processing
subsystems for GSM BSC
UCP:All the UCP subsystems are configured as CPUS to act as the control plane processing
subsystems for UMTS BSC
RGCP:Subsystem 0 of RGCP is configured as the MPU subsystem to act as the resource
management subsystem. The other seven subsystems are configured as CPUS to act as the
control plane processing subsystems for GSM BSC
RUCP:Subsystem 0 of RUCP is configured as the MPU subsystem to act as the resource
management subsystem. The other seven subsystems are configured as CPUS to act as the
control plane processing subsystems for UMTS BSC
MCP:Interference Based Channel Allocation
GTC:GSM BSC TC Process
GPCU:GSM BSC PCU Process
UUP:UMTS BSC User plane Process

on LMT
Example:
SET CLK: SRT=MPS, SN=14, BT=EIUa, REF2MCLKSRC=30, REF2MCLKSW1=ON;
ADD CLKSRC: SRCGRD=2, SRCT=LINE1_8KHZ;
SET CLKMODE: MODE=AUTO;
SET CLKTYPE: CLKTYPE=GCUa;

on LMT
The number of SNTP servers cannot exceed 16.

If multiple SNTP servers are configured, the OMU selects the best SNTP server as the clock
source according to the algorithm defined in the Network Time Protocol (NTP).
Example:
SET TZ: ZONET=GMT-0800, DST=YES, SM=WEEK, SMONTH=MAR, SWSEQ=LAST,

SWEEK=SUN, ST=02&00&00, EM=WEEK, EMONTH=OCT, EWSEQ=LAST,
EWEEK=SUN, ET=03&00&00, TO=60;
ADD SNTPSRVINFO:IP="10.161.38.207",PT=123;

on LMT
Example:
ADD EMSIP: EMSIP="10.171.35.123", MASK="255.255.255.0",

OMUIP="10.161.204.203", OMUMASK="255.255.255.0";

on LMT

on LMT

on LMT
If we use BM/TC separated mode, we should configure Ater interface data.

If the TCS is configured locally:
Configure an Ater connection path.
Run the ADD ATERCONPATH command to add an Ater connection path

between the MPS and the TCS.
Optional: In TC pool mode, run the ADD ATERE1T1 command to add an

Ater connection path between the BSC6900 and the TC.
The Ater connection path is established on the EIUa/OIUa board of the BM subrack and
the EIUa/OIUa board of the TC subrack. The Ater connection path connects the BM
subrack to the TC subrack in the BSC. The Ater connection path exchanges the signaling
data, service data, and OM data between the BM subrack and the TC subrack.
Example:
ADD ATERCONPATH: BMSRN=0, BMSN=24, BMPN=0, TCSRN=3, TCSN=16,

TCPN=0;

on LMT
If the TCS is configured on the CN side, the Ater connection path, Ater OML, and Ater
signaling link must be configured.
Note
1. Only the remote TCS can be configured with the OML on the Ater interface.
2. Before configuring the OML on the Ater interface, you must configure the Ater
connection path.
3. The Ater OML only configured between the local switching subrack and the
remote main subrack. The BM and TC subracks used for the OML on the Ater
interface must be main subracks.
4. Except for timeslot 1, The timeslots of the Ater OML must be consecutive and
the Ater OML must contain at lease four timeslots. In the case of optical port
convergence (the optical cables of the BM and that of the remote TC are
connected through the optical cable connector), the Ater OML can be configured
at timeslots 3 to 31; in other cases, the Ater OML can be configured at timeslots 2
to 31.
5. At most two OMLs on the Ater interface can be configured in the entire system.
ADD ATEROML: ATEROMLINX=0, ATERPIDX=0, TSMASK=TS1-0&TS2-1&TS3-1&TS41&TS5-1&TS6-1&TS7-1&TS8-1&TS9-0&TS10-0&TS11-0&TS12-0&TS13-0&TS14-0&TS150&TS16-0&TS17-0&TS18-0&TS19-0&TS20-0&TS21-0&TS22-0&TS23-0&TS24-0&TS250&TS26-0&TS27-0&TS28-0&TS29-0&TS30-0&TS31-0;

on LMT
Function
Use this command to add a signaling link on the Ater interface.This command
applies only to the BM/TC separated configuration mode.
Note
1. Before running this command, you must configure the Ater connection path.
2. When the TC pool function is enabled, you can run this command to add an
Ater signaling link between the BM subrack and the TC subrack on the active
BSC6900.
3. In the BM subrack, the XPU board processes the most data carried in the Ater
signaling link. In the TC subrack, the A interface board processes the most data
carried in the Ater signaling link.
ADD ATERCONSL: ATERIDX=0, ATERMASK=TS1-1&TS2-0&TS3-0&TS4-0&TS5-0&TS60&TS7-0&TS8-0&TS9-0&TS10-0&TS11-0&TS12-0&TS13-0&TS14-0&TS15-0&TS16-0&TS170&TS18-0&TS19-0&TS20-0&TS21-0&TS22-0&TS23-0&TS24-0&TS25-0&TS26-0&TS270&TS28-0&TS29-0&TS30-0&TS31-0, TNMODE=TRRS;

on LMT

on LMT
UDP: User Datagram Protocol
The UDP is a connectionless and unreliable transmission protocol.
The UDP provides simple services for the application layer. With the UDP, the data packet is
transmitted from one end to the other end, but the data packet may not be transmitted to
the destination successfully. Any reliability required must be provided by the application
layer.
The UDP is a simple data packet-oriented protocol at the transport layer. The UDP is widely
used because it features low cost and high real-time performance during the transmission.
The UDP is applied to scenarios that do not require high reliability.
SCTP: Stream Control Transmission Protocol
The SCTP is a reliable transmission protocol applied to network layers above the
connectionless network (such as IP network).The functions of the SCTP are similar to those
of the TCP.
The SCTP is designed to transmit Public Switched Telephone Network (PSTN) signaling in
the IP network. In addition, the SCTP can be applied to other scenarios. Currently, the SCTP
is used as the reliable transmission protocol to transmit signaling in the IP network.
The SCTP is the enhancement and optimization of the TCP with regard to signaling
transmission. Compared with the SCTP, the TFP has the following disadvantages: The TCP
does not support the SCTP multi-homing function, which affects the availability; the TCP is
subject to distributed denial of service (DDoS) attack, which affects the security; The TCP
processes the packet in a strict sequence, but the delay is increased when processing
packets that are out of sequence. The SCTP supports the multi-homing function, which
improves the link availability. In addition, the SCTP provides optimal performance in security
and packet processing.
The SCTP provides a reliable transmission of messages between equivalent SCTP users. The
SCTP is an end-to-end and connection-oriented protocol, which transmits data in
independent sequenced streams through the SCTP association between two SCTP
endpoints.

on LMT

on LMT
M3UA Link
M3UA links are contained in an M3UA link set. The numbers of M3UA links range
from 0 to 63.
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. It is recommended that the SCTP links are
evenly distributed to the SPUa subsystems in the RSS subrack or an RBS subrack so
that the signaling exchange can be reduced between the SPUa subsystems.
IP Path
An IP path is a group of connections to the adjacent node. The path IDs range
from 0 to 65535.

on LMT
Function
Use this command to add a GSM CN node and a signaling group. After the
mapping between the DPC and GSM CN node is determined, the signaling group
where the signaling point belongs is also determined.
Note
Each CN connected to the BSC6900 must be configured with necessary

information so that calls can be routed to this CN.
ADD GCNNODE: CNNODEIDX=0, DPC=1, DPCGIDX=0, OPNAME="MBSC", MSCCAP=0,
CNID=0, MSCSTATUE=NORMAL, DFDPC=YES, FORBIDNO7FLASHDISC=15;

on LMT
Function
Auto negotiation
When the FG2a/FG2c board is used and the port type is GE, the default of the local self-negotiation
mode is adopted.
If the self-negotiation mode is adopted, the FE port rate, working mode and flow control mode
must be in accordance with the negotiation result. If the self-negotiation mode is not adopted, the
FE port rate, working mode and flow control mode must be specified. Make sure that the specified
attributes are the same as that of the peer. Otherwise, transmission failure must be incurred.
If the self-negotiation mode is adopted on the local system, the peer must use the self-negotiation
mode.
Note
Use this command to set attributes of an Ethernet port on the FG2a, GOUa, FG2c, and GOUc boards.
1. For the FG2a board, only Ethernet ports 0 and 4 can be set to GE ports. If Port type of port 0 is
set to "GE", you cannot configure attributes of ports 1-3; if Port type of port 4 is set to "GE", you
cannot configure attributes of ports 5-7.
2. For the FG2c board in non-auto negotiation mode, if Port type is set to "FE", the value range of
Port No. is 0-11; if Port type is set to "GE", the value range of Port No. is 0-3. In auto negotiation
mode, the value range of Port No. is 0-11.
3. For the FG2a board, If ports 1-3 and ports 5-7 are configured with IP addresses, you cannot set
Port type of port 0 and port 4 to GE.
4. If the board works in active/standby mode, Slot No. can only be the logic slot number of the
active board.
5. This command is not mandatory. After the board is started, parameters of this command are
configured by default. Either this command or the command ADD ETHIP can be executed first.
SET ETHPORT: SRN=0, SN=24, BRDTYPE=FG2a, PTYPE=FE, PN=0, AUTO=ENABLE, MTU=1500;

on LMT
Function
Use this command to add active and standby Ethernet ports. This command is
applicable to the FG2a, GOUa, FG2c, and GOUc boards.
After active and standby Ethernet ports are added, you can perform the protection
switchover. That is, if an active port is faulty, the standby port takes over all the
services processed by the active port. This avoids service interruption.
Note
1. Boards in this slot must work in active/standby mode.
2. If at least one of two ports to be configured in active/standby mode is added to

the Trunk group, such two ports cannot work in active/standby mode.
3. Only two ports with the same attributes can be configured to be active/standby
ports.
4. After active and standby Ethernet ports are configured, corresponding ports of
active and standby boards become active and standby ports.
5. The standby port cannot be used; however, the gateway connectivity check can
be started.
6. The two ports can not be configured with IP address, or they can not be the
active/standby mode.
ADD ETHREDPORT: SRN=0, SN=18, PN=0;

on LMT
Function
Use this command to add an IP address for an Ethernet port. This command is
The IP address is used to communicate with peer devices.

Note
1. For an independent port of the FG2a, FG2c, GOUa or GOUc board, Slot No. is
the physical slot number of the board or the logical slot number of the active
board(even slot number).
2. For the FG2a board, only port 0 and port 4 can set to be GE ports. If port 0 is
set to a GE port, ports 0-3 cannot be used. If port 4 is set to a GE port, ports 5-7
cannot be used.
3. Each Ethernet port can be configured with six IP addresses.

ADD ETHIP: SRN=3, SN=20, PN=0, IPINDEX=0, IPADDR="10.171.35.123",
MASK="255.255.255.0";

on LMT
Function
Use this command to add a trunk group. A trunk group consists of multiple
aggregated links that work in load balancing mode. Through load sharing on the
member links, a trunk group improves the reliability of connections, this command
applies to the FG2a/GOUa/FG2c/GOUc boards.
Note
1. A trunk group can be created only in the active logical slot.
2. The member links can reside only at the active or standby board where the trunk
group reside. For the FG2a and GOUa board, a trunk group can support a
maximum of eight FE ports or two GE ports.For the FG2c and GOUc board, a trunk
group can support a maximum of eight ports(not differentiate between FE and GE).
3. The links of a trunk group have the same rate and run in full-duplex mode.
4. Logical ports can be added to a trunk group.

ADD ETHTRK: SRN=0, SN=18, TRKN=0, LACPMODE=STATIC_LACP, OAMFLOWBW=1,
FLOWCTRLSWITCH=ON, FCINDEX=1;

on LMT
Function
Use this command to add a link to a trunk group. This command applies to the
FG2a/GOUa/FG2c/GOUc boards.
A trunk group consists of multiple links.

Note
1. The trunk links can be carried on only the ports of the active and standby boards
in the slot configured with the trunk group.
2. The member ports in the same trunk group work in full-duplex mode at the
same rate. No IP address is configured on the ports, and no logical ports or
standby ports or ETHMEP are configured.
3. For the FG2a and GOUa board, a trunk group can support a maximum of eight
FE ports or two GE ports.For the FG2c and GOUc board, a trunk group can support
a maximum of eight ports(not differentiate between FE and GE).
ADD ETHTRKLNK: SRN=0, SN=18, TRKN=0, TRKLNKSN=18, TRKLNKPN=0;

on LMT
Function
Use this command to add the IP address of a trunk group. To implement load
sharing among multiple links, you need to set the IP address for the trunk group,
this command applies to the FG2a/GOUa/FG2c/GOUc boards.
Note
1. Each aggregation group can be configured with six IP addresses.
2. The IP address must be an address in class A, class B, or class C. The IP address

consists of the network address and host address, where the host address cannot
be all 0s or 1s. When the CIDR is used, the IP address must be a valid address of
class A, B, or C.
3. If the global route switch of the system is OFF, the IP address of the trunk group
cannot be in the same network segment with IP addresses of other Ethernet ports,
IP addresses of the trunk group, and device IP addresses of the board.
4. If the global route switch of the system is ON, the IP address of the trunk group
cannot be in the same network segment with any other IP addresses.
5. The IP address of the trunk group must not be in the same network segment
with the internal IP addresses of the OMU.
ADD ETHTRKIP: SRN=0, SN=8, TRKN=0, IPINDEX=0, IPADDR="9.9.9.9",
MASK="255.255.255.0";

on LMT
Function
Use this command to add a device IP address for a board.
The device IP address is the logical IP address of the board. As an expansion of the
port IP address, the logical IP address is used to communicate with peer devices.
Note
1. Device IP addresses can only be configured on the interface board. Each

interface board can be configured with a maximum of 16 device IP addresses.
2. The IP address can be an address in class A, class B, or class C. An IP address

consists of the network prefix and the host number. The host number cannot be all
0 or all 1. The first byte of the IP address cannot be 0 or 127.
3. Device IP addresses and internal IP addresses of the OMU cannot be in the same
network segment, or the two network segments cannot have any inclusion relation.
4. Device IP addresses must be different from the IP addresses that are configured
in the BSC6900.
5. Device IP addresses configured for the same slot cannot be in the same network
segment.
ADD DEVIP: SRN=0, SN=24, DEVTYPE=LOGIC_IP, IPADDR="10.171.35.123";

on LMT
Example:
SET ETHPORT: SRN=0, SN=24, BRDTYPE=FG2a, PTYPE=FE, PN=0, AUTO=ENABLE,

MTU=1500;
SET OPT: SRN=3, SN=15, BT=AOUa, PS=ALL, OPTM=SDH;
SET COPTLNK: SRN=3, SN=15, BT=AOUa, LS=PORT, PN=0, J2MODE=16BYTE,

J2BYTE_FORMAT=Character_String;
SET E1T1: SRN=3, SN=15, BT=AOUa, LS=ALL, WORKMODE=E1,

LNKT=E1_CRC4_MULTI_FRAME,SCRAMBLESW=ON;
ADD ETHIP: SRN=3, SN=20, PN=0, IPTYPE=PRIMARY, IPADDR="10.171.35.123",

MASK="255.255.255.0";
ADD ETHTRK: SRN=0, SN=18, TRKN=0, LACPMODE=STATIC_LACP,

OAMFLOWBW=1, FLOWCTRLSWITCH=ON, FCINDEX=1;

MASK="255.255.255.0";
ADD DEVIP: SRN=3, SN=20, IPADDR="10.171.35.123", MASK="255.255.255.0";
ADD PPPLNK: SRN=1, SN=26, BRDTYPE=POUa, PPPLNKN=1, DS1=2,

TSBITMAP=TS1-1&TS2-1, LOCALIP="5.5.5.5", MASK="255.255.255.0",
PEERIP="5.5.5.6", PPPMUX=Enable, AUTHTYPE=NO_V, FLOWCTRLSWITCH=ON;
ADD MPGRP: SRN=4, SN=26, BRDTYPE=PEUa, LGCAPPTYPE=IP, MPGRPN=1,

MPTYPE=MCPPP, BORROWDEVIP=No, LOCALIP="9.9.9.99",
MASK="255.255.255.0", PEERIP="9.9.9.98", MHF=LONG, PPPMUX=Enable,
FLOWCTRLSWITCH=ON, AUTHTYPE=NO_V;
ADD MPLNK: SRN=4, SN=26, BRDTYPE=PEUa, MPGRPN=1, PPPLNKN=10, DS1=1,

TSBITMAP=TS1-1&TS2-0;

on LMT
Function
Use this command to add an SCTP link.

Note
1. The VLAN function is not supported when the local IP address of the SCTP link is
the same as that of the MP Group. In this case, VLAN ID. is invalid.
2. The subrack where the board with the first local IP address is located, the
subrack where the board with the second local IP address is located, and the
subrack where the XPU board is located cannot be three different subracks.
3. It is recommended to use different local port No. for each client mode SCTP link.
Example:
ADD SCTPLNK: SRN=1, SN=2, SCTPLNKN=1, MODE=SERVER, APP=NBAP,

LOCIP1="11.11.11.11", PEERIP1="11.11.11.111", PEERPN=58081,
LOGPORTFLAG=NO, VLANFlAG=DISABLE, SWITCHBACKFLAG=YES;

on LMT
Function
Use this command ADD M3LKS to add an M3UA(MTP3 User Adaption Layer) link
set. This command applies only to IP mode.
Note
1. The M3UA link set is assigned to an adjacent M3UA destination entity of the
BSC6900.
2. The destination entity corresponding to Destination entity No. must exist and
must be an adjacent destination entity.
3. An adjacent destination entity can be configured with only one signaling link set.
4. Signalling link mask is used for load sharing among links in the link set. The
conjunction result of the value of Signalling link mask and the value of
Signaling route mask provided in the ADD N7DPC command should be zero.
5. It is recommended that at least two M3UA links should be configured in this link
set and distributed in different XPU or SPU boards.
Example
ADD M3LKS: SIGLKSX=0, DENO=1, LNKSLSMASK=B1001,

TRAMODE=M3UA_LOADSHARE_MOD, WKMODE=M3UA_ASP, PDTMRVALUE=6,
NAME="SGSN";
ADD M3RT: DENO=1, SIGLKSX=2, PRIORITY=1, NAME="SGSN";

on LMT
Function
Use this command ADD M3LNK to add an M3UA(MTP3 User Adaption Layer) link.
This command applies only to IP mode.
Use this command ADD ADJNODE to add an adjacent node. It indicates an

adjacent network device of BSC6900.
Adjacent Node Type
IUB(Iub Interface), IUR(Iur Interface), IUCS(Iu-CS Interface), IUPS(Iu-PS Interface),

UNI_AAL2SWITCH(the adjacent node of the ATM switch on the Iub interface),
NNI_AAL2SWITCH(the adjacent node of ATM switch on Iur or Iu-CS interface),
ABIS(Abis Interface), A(A Interface), BSC(Ater Interface on BSC), TC(Ater Interface
on TC), IUR_G(IUR_G Interface)
Note
1. The specified link set must already exist. The link set contains a maximum
number of 16 links.
2. The SCTP link specified by SCTP Link No. should be configured in the specified
XPU board of Control slot No. and Subrack No. and must be unused.
ADD ADJNODE: ANI=1, NAME="NODEB1", NODET=IUB, NODEBID=1, TRANST=IP;
ADD ADJNODE: ANI=2, NAME="MSC1", NODET=IUCS, DPX=1, TRANST=ATM,
IsROOTNODE=YES;

on LMT
Function
Use this command to add an IP path.
IP path is an important transmission resource. It carries the user plane data

between the BSC6900 and other NEs.
Note
1. The IP path cannot be configured on the adjacent node whose transmission type
is ATM (except the adjacent node of the IUPS type).
2. The IP address cannot be all 0s, all 1s, 127.0.0.1. The same restriction also
applies to the IP address described in other commands.
3. The adjacent node must be already configured through the ADD ADJNODE
command.
4. The local IP address must be the address configured for MBSC (including the IP
address of the interface board and the port IP address). The peer IP address cannot
be same as the local IP address configured for the BSC6900.
5. No two IP paths have the same Local IP address, Peer IP address, Peer IP
address mask and IP path type.
6. If the IP path supports the check function, you must enter the peer IP address.
The peer IP address (no matter whether the peer IP address is an IP address of a
network segment or a host IP address ) must be an IP address in the specified
network segment. The peer IP address cannot be the same as the local IP address.
ADD IPPATH: ANI=0, PATHID=1, ITFT=IUB, TRANST=IP,PATHT=BE, IPADDR="80.1.1.1",
PEERIPADDR="10.161.0.1", PEERMASK="255.255.255.0", TXBW=1000, RXBW=1000;

on LMT
Function
Use this command to add an IP route to the PEUa, AEUa, AOUa, UOIa (ATM or IP),
FG2a, GOUa, POUa, AOUc, UOIc (ATM), FG2c, GOUc, or POUc board.
Note
1. The Destination IP address AND Subnet Mask is the destination IP address.
2. The whole system supports a maximum of 1,024 routes.
3. The FG2a, GOUa, UOIa (IP), FG2c, and GOUc boards support the configuration
of main and standby routes. The routes have the same destination address and
mask, but different next hop addresses and priorities. When the route with high
priority is available, it is the only effective route and data is sent through the port
specified by the route. When the route with high priority is unavailable and the
route with low priority is available, the system switches to the route with low
priority and data is sent through the port specified by this route.
ADD IPRT: SRN=3, SN=20, DSTIP="35.35.35.35", DSTMASK="255.255.255.255",
NEXTHOP="26.26.26.28", PRIORITY=HIGH;

on LMT
Function
Use this command to set the TC resource type of the DPUa/DPUb/DPUc/DPUf

board. The TC resource type can be GTC, ITC, or UTC.
The type of TC resource
GTC: TC resources that support normal voice coding/decoding and packet

conversion.The TC resource support packet conversion In BM/TC separated mode
,when abis interface transmission mode is abis over IP or HDLC.It's different from
ITC.
UTC: TC resources that support only the optimized handover on the Iur-g interface.
ITC: TC resources that support only packet conversion.It is only used in A over IP.

on LMT
By default, 12 transport resource mappings (the index ranges from 0 to 11) are added. In
addition, the 12 transport resource mappings cannot be modified and deleted.
By default, the activation factor table with index 0 is configured in the BSC6900. In
addition, this index cannot be modified and removed.
Example:
ADD TRMMAP: TMI=12, ITFT=IUB, TRANST=ATM;
ADD TRMFACTOR: FTI=1, REMARK="For Iub Gold User";
ADD ADJMAP: ANI=10, ITFT=IUB, TRANST=HYBRID_IP, CNMNGMODE=SHARE,

TMIGLD=12, TMISLV=12, TMIBRZ=12, FTI=13, LEIGLD=14, LEISLV=14, LEIBRZ=14;

on LMT

on LMT
Function
Note


on LMT
Function
Use this command to add an E1/T1 link on the A interface. The E1/T1 link on the A
interface is used to carry the control-plane data and user-plane data over the A
interface.
Note
1. Before running the command, you need to configure the POUc, EIUa or OIUa
board.
2. The CICs of the two E1/T1 timeslots on the A interface with the same OSP
index and DPC Group Index must be different. In practice, however, running this
command always fails due to the same CIC of the two timeslots. In this case, you
need to adjust the Start CIC to ensure that the CIC of an E1/T1 timeslot on the A
interface differs from that of another timeslot.
Note that you can run the LST AE1T1 command to view the CIC of E1/T1
timeslots on the A interface.
3. In the BM/TC combined configuration mode or BM/TC separated and non-TC

pool configuration mode, a maximum of 768 E1/T1 links can be configured on the
A interface. In BM/TC separated and TC pool configuration mode, a maximum of
1280 E1/T1 links can be configured on the A interface on TC side, and a maximum
of 768 E1/T1 links can be configured on the A interface of each BSC.
ADD AE1T1: SRN=0, SN=14, PN=0, DPCGIDX=0, OPCIDX=0, ALLTSTYPE=ALLCIC,
BSCFLAG=MAINBSC, STCIC=100;

on LMT
Function
Use this command to add an MTP3 signaling link set.

Note
1. The DSP specified by DSP index must exist, and it must be an adjacent DSP.
2. One adjacent DSP can be configured with only one signaling link set.
3. The signaling link mask specified by Signalling link mask is used to share loads
between links in the link set. This mask AND the value of Signalling route mask
specified by ADD N7DPC must be zero.
4. It is recommended that at least two MTP3 links should be configured in this link
ADD MTP3LKS: SIGLKSX=0, DPX=1, LNKSLSMASK=B0001, EMERGENCY=OFF,
NAME="NAME1";

on LMT
Function
Use this command to add an MTP3 signaling link, and add it into a specified MTP3
signaling link set.
Note
1. The link set to be used must exist.
2. Signalling Link Code must be set to the same value at the two ends of the
signaling link.
3. The total number of MTP3 signaling links cannot exceed 2992.
4. If the underlying link of the MTP3 link is MTP2 and the MTP2 is configured on
the EIU, Link rate type of the MTP3 link must be consistent with Link rate type
of the first MTP2 link added to the EIU after the EIU startup. Otherwise, the link
fails to be added. If the EIU is first configured with an MTP2 of one rate type, you
must delete the MTP2 and reset the EIU before adding an MTP2 of another rate
type.
ADD MTP3LNK: SIGLKSX=0, SIGSLC=1, BEARTYPE=SAAL, SRN=1, SN=2, SAALLNKN=10,
PRIORITY=0, TCLEN=12, TC=31, NAME="name1";

on LMT
Function
Use this command to add an MTP3 signaling route.
MTP3 signaling route refers to a link set through which a signaling message is
transmitted from an OSP to a DSP.
Note
1. DSP index and Signalling link set index must exist.
2. If the DSP specified by DSP index is inconsistent with that specified by

Signalling link set index, you need to check whether the DSP specified by
Signalling link set index has a transfer function.
3. In addition to a direct route, it is recommended to add an alternative route as a

backup.
4. At most 374 MTP3 routes can be configured for the BSC6900.

ADD MTP3RT: DPX=1, SIGLKSX=2, PRIORITY=0, NAME="name1";

on LMT

on LMT
Function
Note


on LMT
Function
Use this command to set attributes of an Ethernet port on the FG2a, GOUa, FG2c, and
GOUc boards.
Auto negotiation
When the FG2a/FG2c board is used and the port type is GE, the default of the local selfnegotiation mode is adopted.
If the self-negotiation mode is adopted, the FE port rate, working mode and flow control
mode must be in accordance with the negotiation result. If the self-negotiation mode is not
adopted, the FE port rate, working mode and flow control mode must be specified. Make
sure that the specified attributes are the same as that of the peer. Otherwise, transmission
failure must be incurred.
If the self-negotiation mode is adopted on the local system, the peer must use the selfnegotiation mode.
Note
1. For the FG2a board, only Ethernet ports 0 and 4 can be set to GE ports. If Port type of
port 0 is set to "GE", you cannot configure attributes of ports 1-3; if Port type of port 4 is
set to "GE", you cannot configure attributes of ports 5-7.
2. For the FG2c board in non-auto negotiation mode, if Port type is set to "FE", the value
range of Port No. is 0-11; if Port type is set to "GE", the value range of Port No. is 0-3.
In auto negotiation mode, the value range of Port No. is 0-11.
3. For the FG2a board, If ports 1-3 and ports 5-7 are configured with IP addresses, you
cannot set Port type of port 0 and port 4 to GE.
4. If the board works in active/standby mode, Slot No. can only be the logic slot number
of the active board.
5. This command is not mandatory. After the board is started, parameters of this command
are configured by default. Either this command or the command ADD ETHIP can be
executed first.
SET ETHPORT: SRN=0, SN=24, BRDTYPE=FG2a, PTYPE=FE, PN=0, AUTO=ENABLE, MTU=1500;

on LMT
Function
Use this command to add active and standby Ethernet ports. This command is
After active and standby Ethernet ports are added, you can perform the protection
switchover. That is, if an active port is faulty, the standby port takes over all the
services processed by the active port. This avoids service interruption.
Note
1. Boards in this slot must work in active/standby mode.
2. If at least one of two ports to be configured in active/standby mode is added to

the Trunk group, such two ports cannot work in active/standby mode.
3. Only two ports with the same attributes can be configured to be active/standby
ports.
4. After active and standby Ethernet ports are configured, corresponding ports of
active and standby boards become active and standby ports.
5. The standby port cannot be used; however, the gateway connectivity check can
be started.
6. The two ports can not be configured with IP address, or they can not be the
active/standby mode.
ADD ETHREDPORT: SRN=0, SN=18, PN=0;

on LMT
Function
Use this command to add an IP address for an Ethernet port. This command is
The IP address is used to communicate with peer devices.

Note
1. For an independent port of the FG2a, FG2c, GOUa or GOUc board, Slot No. is
the physical slot number of the board or the logical slot number of the active
board(even slot number).
2. For the FG2a board, only port 0 and port 4 can set to be GE ports. If port 0 is
set to a GE port, ports 0-3 cannot be used. If port 4 is set to a GE port, ports 5-7
cannot be used.
3. Each Ethernet port can be configured with six IP addresses.

ADD ETHIP: SRN=3, SN=20, PN=0, IPINDEX=0, IPADDR="10.171.35.123",
MASK="255.255.255.0";

on LMT
Function
Use this command to add a trunk group. A trunk group consists of multiple
aggregated links that work in load balancing mode. Through load sharing on the
member links, a trunk group improves the reliability of connections, this command
applies to the FG2a/GOUa/FG2c/GOUc boards.
Note
1. A trunk group can be created only in the active logical slot.
2. The member links can reside only at the active or standby board where the trunk
group reside. For the FG2a and GOUa board, a trunk group can support a
maximum of eight FE ports or two GE ports.For the FG2c and GOUc board, a trunk
group can support a maximum of eight ports(not differentiate between FE and GE).
3. The links of a trunk group have the same rate and run in full-duplex mode.
4. Logical ports can be added to a trunk group.

ADD ETHTRK: SRN=0, SN=18, TRKN=0, LACPMODE=STATIC_LACP, OAMFLOWBW=1,
FLOWCTRLSWITCH=ON, FCINDEX=1;

on LMT
Function
Use this command to add a link to a trunk group. This command applies to the
FG2a/GOUa/FG2c/GOUc boards.
A trunk group consists of multiple links.

Note
1. The trunk links can be carried on only the ports of the active and standby boards
in the slot configured with the trunk group.
2. The member ports in the same trunk group work in full-duplex mode at the
same rate. No IP address is configured on the ports, and no logical ports or
standby ports or ETHMEP are configured.
3. For the FG2a and GOUa board, a trunk group can support a maximum of eight
FE ports or two GE ports.For the FG2c and GOUc board, a trunk group can support
a maximum of eight ports(not differentiate between FE and GE).

on LMT
Function
Use this command to add the IP address of a trunk group. To implement load
sharing among multiple links, you need to set the IP address for the trunk group,
this command applies to the FG2a/GOUa/FG2c/GOUc boards.
Note
1. Each aggregation group can be configured with six IP addresses.
2. The IP address must be an address in class A, class B, or class C. The IP address

consists of the network address and host address, where the host address cannot
be all 0s or 1s. When the CIDR is used, the IP address must be a valid address of
class A, B, or C.
3. If the global route switch of the system is OFF, the IP address of the trunk group
cannot be in the same network segment with IP addresses of other Ethernet ports,
IP addresses of the trunk group, and device IP addresses of the board.
4. If the global route switch of the system is ON, the IP address of the trunk group
cannot be in the same network segment with any other IP addresses.
5. The IP address of the trunk group must not be in the same network segment
with the internal IP addresses of the OMU.
MASK="255.255.255.0";

on LMT
Function
Use this command to add next hop IP to VLAN ID mapping table. This command is
applicable to the FG2a/GOUa/FG2d/FG2c/GOUd/GOUc boards.
Note
1.The first byte of the destination IP address cannot be 0 or 127 and also cannot be the
RNC's interior Mask number.
2.After executing the command, all IP package send to the specific IP address will be
tagged with the VLAN ID.
3. ARP request of the destination IP address will be tagged with the VLAN ID too.
ADD VLANID: SRN=0, SN=14, IPADDR="10.10.10.11", VLANID=5;

on LMT
Function
Use this command to add a device IP address for a board.
The device IP address is the logical IP address of the board. As an expansion of the
port IP address, the logical IP address is used to communicate with peer devices.
Note
1. Device IP addresses can only be configured on the interface board. Each

interface board can be configured with a maximum of 16 device IP addresses.
2. The IP address can be an address in class A, class B, or class C. An IP address

consists of the network prefix and the host number. The host number cannot be all
0 or all 1. The first byte of the IP address cannot be 0 or 127.
3. Device IP addresses and internal IP addresses of the OMU cannot be in the same
network segment, or the two network segments cannot have any inclusion relation.
4. Device IP addresses must be different from the IP addresses that are configured
in the BSC6900.
5. Device IP addresses configured for the same slot cannot be in the same network
segment.
ADD DEVIP: SRN=0, SN=24, DEVTYPE=LOGIC_IP, IPADDR="10.171.35.123";

on LMT
Function
Use this command to add a policy-based route based on the source IP address. Policybased routing is a technology that forwards packets based on pre-defined policies. After
policy-based routing is applied, the source IP address in an IP packet is compared with the
source IP address in the pre-defined routing policy. If the source IP address in a packet is
the same as the source IP address in the defined routing policy, the packet matches the
defined routing policy. If the source IP address in a packet differs from the source IP
address in the pre-defined routing policy, the packet is routed according to its destination
IP address.

on LMT
Function
Use this command to add a Transmission Resource Pool. A Transmission Resource Pool can
provide shared IP addresses and balance the load among different IP addresses.
Note
A BSC supports a maximum of 16 Transmission Resource Pools.
ADD IPPOOL: IPPOOLINDEX=0, IPPOOLNAME="IPPOOLNAME";

on LMT
Function
Use this command to add an IP address to a Transmission Resource Pool.
Note
1. Only the device IP addresses of the FG2d, FG2c, GOUd and GOUc boards can be added
to a Transmission Resource Pool.
2. Only those IP addresses that are quoted by policy-based routes as source IP addresses
can be added to a Transmission Resource Pool.
3. A maximum of 24 IP addresses can be added to a Transmission Resource Pool.
4. A maximum of 8 IP addresses on a board or a pair of active and standby boards can be
added to a Transmission Resource Pool.
5. A maximum of 128 IP addresses can be added to the Transmission Resource Pools for a
BSC.
6. An IP address can be added only to one Transmission Resource Pool.
7. An IP address used by an IP path over A interface as its source IP address cannot be
added to any Transmission Resource Pool.
ADD IPPOOLIP: IPPOOLINDEX=0, SRN=0, SN=26, IPADDR="26.26.26.26";

on LMT
Function

Note
Example:


on LMT
Function
Note
BSC6900.
Example

NAME="SGSN";

on LMT
Function
Use this command to add an M3UA(MTP3 User Adaption Layer) link. This command
applies only to IP mode.
Note
1. The specified link set must already exist. The link set contains a maximum number of 16
links.
2. If multiple routes (each corresponds to a link set) to the same DSP are configured, it is
recommended that you add equal number of available links to each link set to achieve load
balance between links.
ADD M3LNK: SIGLKSX=2, SIGLNKID=1, SRN=1, SN=2, SCTPLNKN=2, PRIORITY=2,
LNKREDFLAG=M3UA_SLAVE_MOD, NAME="MBSCMSC";

on LMT
Function
Use this command to add an adjacent node. It indicates an adjacent network device of
BSC.
Note
1. If Adjacent Node Type is ABIS, A, BSC, TC or IUR_G, you can run the ADD ADJMAP
command to configure the associated TRMMAP index and factor table index. If ADJMAP is
not configured, the system automatically uses the default TRMMAP and factor. You can
run the LST TRMMAP, LST TRMFACTOR command to query the default TRMMAP and
factor table.
2. If Adjacent Node Type is ABIS, the corresponding Site Index must be configured. You
can run the LST BTS command to query the configuration.
3. The total number of adjnode configured on a BSC cannot exceed 4600.
4. If Adjacent Node Type is set to A, and IS IP Pool is set to YES, the operator
corresponding to CN Operate index must have been configured. (Run the LST
GCNOPERATOR command to check whether an operator has been configured.) The
operator corresponding to CN Operate index must be GSM.
ADD ADJNODE: ANI=3, NAME="BTS-1", NODET=ABIS, BTSID=1;

on LMT
Function
Use this command to set the TC resource type of the DPUa/DPUb/DPUc/DPUf

board. The TC resource type can be GTC, ITC, or UTC.
The type of TC resource
GTC: TC resources that support normal voice coding/decoding and packet

conversion.The TC resource support packet conversion In BM/TC separated mode
,when abis interface transmission mode is abis over IP or HDLC.It's different from
ITC.
UTC: TC resources that support only the optimized handover on the Iur-g interface.
ITC: TC resources that support only packet conversion.It is only used in A over IP.

on LMT
By default, 12 transport resource mappings (the index ranges from 0 to 11) are added. In
addition, the 12 transport resource mappings cannot be modified and deleted.
By default, the activation factor table with index 0 is configured in the BSC6900. In
addition, this index cannot be modified and removed.
Example:
ADD TRMMAP: TMI=12, ITFT=IUB, TRANST=ATM;
ADD TRMFACTOR: FTI=1, REMARK="For Iub Gold User";
ADD ADJMAP: ANI=10, ITFT=IUB, TRANST=HYBRID_IP, CNMNGMODE=SHARE,

TMIGLD=12, TMISLV=12, TMIBRZ=12, FTI=13, LEIGLD=14, LEISLV=14, LEIBRZ=14;

on LMT

on LMT

on LMT
SET BSCPCUTYPE: TYPE=INNER;

ADD SGSN: SGSNNAME="SGSN02", IPADDR1="10.161.100.196",
IPADDR2="192.168.1.196";
ADD NSE: NSEI=0, SRN=0, SN=0, PT=GB_OVER_IP, OPNAME="46000", CNID=0;

on LMT
Function
Use this command to add a local network service virtual link (NSVL). This command
applies to the FG2a, GOUc or FG2c board of the Gb over IP type.
Note
1. The BSC can be configured with up to 256 local NSVLs.
2. Local IP Address and Local UDP Port No. must be unique in BSC. Local IP
Address is the device IP address, the ethernet port IP address or the TRUNKIP
address of the Gb interface board.
3. This command can be used in built-in PCU mode only.

ADD NSVLLOCAL: LOCALNSVLI=0, NSEI=180, IP="1.2.3.4", UDPPN=55555, SRN=0,
SN=22;

on LMT
Function
Use this command to add a remote network service virtual link (NSVL). This
command applies to the FG2a, GOUc or FG2c board of the Gb over IP type.
Note
The remote NSVL is configured only when the Gb interface adopts the IP
transmission in built-in PCU mode and the network service entity (NSE) is in static
configuration mode.
ADD NSVLREMOTE: REMOTENSVLI=1, NSEI=180, IP="2.2.2.2", UDPPN=55555;

on LMT
Function
Use this command to add a PTP BSSGP virtual connection (PTP BVC) to a GPRS cell.
Note
1. When the SGSN pool function is disabled, a cell can be configured with only one
PTP BVC. When the SGSN pool function is enabled, a cell can be configured with
up to 32 PTP BVCs.
2. An NSE can support up to 2048 PTP BVCs.
3. This command can be used only in built-in PCU mode.

ADD PTPBVC: NSEI=181, BVCI=5, IDTYPE=BYID, CELLID=0;
ADD PTPBVC: NSEI=181, BVCI=6, IDTYPE=BYNAME, CELLNAME="cell-11";

on LMT

on LMT
The Gb interface (Gb interface is the interface between the SGSN and PCU in Huawei GPRS
network) is used to implement packet data transmission, mobility management and session
management between the SGSN and the BSS/MS. The Gb interface is mandatory for the GPRS
networking.
Physical layer protocol L1

The several physical layer configurations and protocols defined in GSM 08.14
are available here. The physical resources shall be configured through the
Operation and Maintenance (O&M) process.
FR (NS layer subnet service protocol)
The Frame Relay (FR) sub-layer of the Gb interface belongs to the NS SubNetwork Service protocol. The FR module enables the interworking of subnetwork so that the PCU may connect to the SGSN through point-to-point
connection or the frame relay network. The point-to-point connection refers to
the direct connection between the PCU and SGSN. Generally the PCU acts as
the DTE and the SGSN the DCE. You may flexibly set the network features of
the PCU and SGSN. Huawei PCU supports the above two connection modes.
The link layer protocol of the Gb interface is based on the FR and defined in
the GSM 08.16. Establish a FR virtual circuit between the SGSN and BSS,
which is to be multiplexed by the LLC PDU from multiple subscribers. This
virtual circuit may be multi-hop and traverse the network consisting of FR
switching nodes. The frame relay is used for signaling and data transmission.

on LMT

on LMT

on LMT
DCE: Data Circuit-terminating Equipment

DTE: Data Terminal Equipment
On each NS-VC, data are transferred in order by the Sub-Network Service
When the Sub-Network Service entity detects that an NS-VC becomes unavailable
(e.g. upon failure detection), or when the NS-VC becomes available again (e.g.
after failure recovery), the Network Service Control entity shall be informed
Frame Relay shall be the network used on the Gb interface. The Sub-Network
Service entity is the Frame Relay entity

on LMT
Load sharing of subscriber data.
One of the most important functions of the NS layer is to perform

load sharing of the subscriber data. When upper layer subscribers
transmit data to the NS layer, the system allocates an LSP for each
subscriber and encapsulates it to the data packet. The NS layer
ensures the sequence of subscriber data transmission based on the
LSPs. The NS layer selects one or several available NS-VCs to
transmit the subscriber data packets based on the LSP and BVCI so
that the load is shared among all unblocked NS-VCs of the same
NSE.

on LMT
BVCI
This parameter is not part of the BSSGP PDU across the Gb interface, but is
used by the network service entity across the Gb
A BVCI needs not to be unique within an SGSN, a BVCI is unique within an
NS Entity. BVCI together with NSEI uniquely identify a BVC within an SGSN
(the global identifier within an SGSN is BVCI+NSEI)
Each BVC is identified by means of a BSSGP Virtual Connection Identifier
(BVCI) which has end-to-end significance across the Gb interface. Each
BVCI is unique between two peer Network Service Entities
peer point-to-point (PTP) functional entities : PTP user data transmission.
There is one PTP functional entity per cell. A cell is identified by a BVCI
unless it is explicitly stated otherwise
peer point-to-multipoint(PTM) functional entities: PTM user data
transmission. There is one or more PTM functional entities per BSS
peer signalling functional entities : Signaling transmission, such as: PAGING
message. Each NSE corresponds a SIG BVC. There is one or more NSEs per
BSS

on LMT

on LMT
The configuration principles are as follows.
A BSC can be connected to several SGSNs.
A BSC can be configured with several NSEs.
An SGSN can correspond to several NSEs in a BSC, but all the NSVCs and PTPBVCs in
one NSE can only serves for one SGSN. In the FR mode, the NSVC ID in the BSC must
be identical with the NSVC ID in the SGSN.
One cell corresponds to one PTPBVC.
A BSC can be configured with cells that belong to different SGSNs.If the BSC and the
SGSN is connected directly point-to-point, the timeslots on the same
E1 cable should be bound as many to one bearer channel.
Principles for Configuring the Links on the Gb Interface
No limit is set on the number of the NSVCs to be configured on one BC. It is

recommended that you do not configure more than two NSVCs serving the same NSE
on the same BC so that the NSVCs can be evenly distributed in the system.

on LMT

on LMT
Function
Use this command ADD SGSNNODE to add a node of serving GPRS support node
(SGSN).
Note
This command can be used in built-in PCU mode only.

SET BSCPCUTYPE: TYPE=INNER;
ADD SGSN: SGSNNAME="SGSN02", IPADDR1="10.161.100.196",
IPADDR2="192.168.1.196";

on LMT
Function
Use this command to add a network service entity (NSE).

Note
1. The NSE must be configured in the MPS or EPS.
2. A BSC can be configured with up to 32 NSEs.
3. When Subnet Protocol Type is set to GB_OVER_IP and Subnetwork

Configure Mode is set to DYNAMIC, then Server IP and Server UDP Port are
determined by the serving GPRS support node (SGSN). If Subnetwork Configure
Mode is set to STATIC, then Server IP and Server UDP Port need not be set.
ADD NSE: NSEI=0, SRN=0, SN=0, PT=GB_OVER_FR, OPNAME="46000", CNID=0;

on LMT
Function
Use this command to add a bearer channel (BC) in Gb over frame relay (FR) mode.
A certain number of timeslots on the E1/T1 are bound as a BC to provide the
physical bearer in FR mode. This command applies to the PEUa or POUc board.
Note
Bearing Timeslot and Frame Relay Protocol Type must be consistent with
those on the Serving GPRS Support Node (SGSN) side.
ADD BC: SRN=0, SN=14, PN=7, BCID=7, TS=TS1-1&TS2-1&TS3-0&TS4-0&TS5-0&TS60&TS7-0&TS8-0&TS9-0&TS10-0&TS11-0&TS12-0&TS13-0&TS14-0&TS15-0&TS16-0&TS170&TS18-0&TS19-0&TS20-0&TS21-0&TS22-0&TS23-0&TS24-0&TS25-0&TS26-0&TS270&TS28-0&TS29-0&TS30-0&TS31-0, PROT=Q933;

on LMT
Function
Use this command to add a network service virtual connection (NSVC) at the
network service (NS) layer. This command applies to the PEUa or POUc board.
Note
1. An NSVC is carried on a bearer channel (BC) on the E1/T1 link. A BC can be

configured with several NSVCs (differentiated by The Identifier of Data Link
Connection). An NSVC can belong to only one BC and only one NSE, whereas an
NSE can correspond to several NSVCs.
2. NSE Identifier, NSVC Identifier, and The Identifier of Data Link

Connection must be consistent with those on the SGSN side.
ADD NSVC: NSVCIDX=0, NSVCI=123, NSEI=181, SRN=0, SN=14, BCID=0, DLCI=16;

on LMT
Function
Use this command to add a PTP BSSGP virtual connection (PTP BVC) to a GPRS cell.
Note
1. When the SGSN pool function is disabled, a cell can be configured with only one
PTP BVC. When the SGSN pool function is enabled, a cell can be configured with
up to 32 PTP BVCs.
2. An NSE can support up to 2048 PTP BVCs.
3. This command can be used only in built-in PCU mode.

ADD PTPBVC: NSEI=181, BVCI=5, IDTYPE=BYID, CELLID=0;
ADD PTPBVC: NSEI=181, BVCI=6, IDTYPE=BYNAME, CELLNAME="cell-11";

on LMT

on LMT
SET BSCPCUTYPE: TYPE=OUTER;

ADD PCU: NAME="PCU01", PCUINDEX=2, OPNAME="46000";

on LMT
Function
Use this command to add an E1/T1 link on the Pb interface. This command is
applicable to an external PCU.
Note
1. At least one PCU must be configured.
2. It must be configured on the POUc, EIUa or OIUa interface board.
3. The value of Start PCIC must be the multiple of 128.
4. In E1 mode, time slots 0, 1, 2, and 3 are used for synchronization and cannot be
used by the service.
ADD PBE1T1: SRN=0, SN=24, PN=0, PCUNO=1, SPCIC=128, ALLTSTYPE=ALLCIC;
ADD PBE1T1: SRN=0, SN=24, PN=1, PCUNO=2, SPCIC=256, ALLTSTYPE=ALLCIC;

on LMT
Function
Use this command to add a Pb signaling link. This command is applicable to an

external PCU.
Note
1. The Pb signaling link can be configured in the specified subrack, slots, and ports
only when the E1/T1 of Pb interface is configured, and the E1/T1 of the Pb
interface must have idle timeslots.
2. The value of Congestion Start Threshold must be greater than that of

Congestion End Threshold.
3. If the Pb interface uses the E1 link, the timeslot ranges from 1 to 31. If the Pb
interface uses the T1 link, the timeslot ranges from 1 to 24.
ADD PBSL: SRN=0, SN=24, PN=0, TSNO=5, TEI=63, CGST=90, CGET=80;

on LMT

on LMT
Function

Note
Example:


on LMT
Function
Note
BSC6900.
Example

NAME="SGSN";

on LMT
Function
Use this command to add an M3UA(MTP3 User Adaption Layer) link. This command
applies only to IP mode.
Note
1. The specified link set must already exist. The link set contains a maximum number of 16
links.
2. If multiple routes (each corresponds to a link set) to the same DSP are configured, it is
recommended that you add equal number of available links to each link set to achieve load
balance between links.
ADD M3LNK: SIGLKSX=2, SIGLNKID=1, SRN=1, SN=2, SCTPLNKN=2, PRIORITY=2,
LNKREDFLAG=M3UA_SLAVE_MOD, NAME="MBSCMSC";

on LMT
Function
Use this command to add a neighboring RNC.
Note
1. The number of neighboring RNCs must be less than or equal to 16.
2. The number of added RNCs sharing the MBSC must be smaller than or equal to 1. The RNC sharing the
MBSC is the RNC that configured together with the BSC in the BSC6900.
3. The name of each neighboring RNC must be unique.
4. If the neighboring RNCs are not co-MBSC RNCs, you must specify a DSP index. In addition, the DSP type
must be Iur-g. Each neighboring RNC must correspond to a unique destination signaling point.
5. If the neighboring RNC shares the MBSC, then the OPC of the RNC needs to be specified. The OPC acts as
the basis for reporting of the traced signaling messages, not as the basis for connection setup.
6. Once the information about the co-MBSC, OSP index, and DSP index is configured, the information cannot
be modified.
7. The measurement period is the period for reporting the common measurement report to the peer RNC. It is
defined in the common measurement request message.
8. The resume timer indicates the retry period after the BSC fails to initiate the common measurement. If the
period is zero, the BSC does not try to initiate the common measurement again after the failure.
9. The timeout timer indicates the validity period of data in a common measurement report after the BSC
receives the report from the RNC. After the timeout timer expires, the data in the report becomes invalid and
will be updated according to the newly received measurement report.
10.The Allow Common Measurement at Iur-g parameter is controlled by any of the following License items:
BSC Load Balancing Based on Iur-g Function (per TRX), MBSC Load Balancing, Handover Based on Load on
Iur-g Function (per TRX), MBSC Handover Based on Load, and Iur-g Function between GSM and TD-SCDMA
(per TRX).
11. When Info Exchange Content is set to NACC Info, one of the following License items must be enabled:
NACC Procedure Optimization Based on Iur-g Function (per TRX) and NACC Procedure Optimization.
12. When Co-MBSC is set to YES, one of the following License items must be enabled: MBSC Load Balancing,
MBSC Handover Based on Load, and NACC Procedure Optimization.
13.When Co-MBSC is set to NO, one of the following License items must be enabled: BSC Load Balancing
Based on Iur-g Function (per TRX), Handover Based on Load on Iur-g Function (per TRX), NACC Procedure
Optimization Based on Iur-g Function (per TRX), and Iur-g Function between GSM and TD-SCDMA (per TRX).
Example
ADD GNRNC: RNCINDEX=0, RNCNAME="RNC001", INTRAMBSC=YES, OPX=0, SPTCOMMMEAS=PERIODIC,
MEASPERIOD=3, SPTINFOEXCHG=YES, INFOEXCHGLIST=CELLCAPCLASS-1&NACCRELATED-1,
Confidential
Information of Huawei. No Spreading Without Permission
RESUMETIMER=5,
OUTTIMER=10;
ADD GNRNC: RNCINDEX=1, RNCNAME="RNC002", INTRAMBSC=NO, DPX=1, SPTCOMMMEAS=YES,
MEASPERIOD=5, SPTINFOEXCHG=YES, INFOEXCHGLIST=CELLCAPCLASS-1&NACCRELATED-1,

on LMT
Function
Use this command to add a 3G external cell.
Note
1. The name and CI of the added cell must be different from the names and CIs of the
configured cells.
2. Cell Index can be automatically allocated by the system. If you manually type the
parameter value, ensure that the typed value is unique.
Example
ADD GEXT3GCELL: EXT3GCELLID=7572, EXT3GCELLNAME="Cell_0", MCC="460",
MNC="10", LAC=10, CI=60, RNCID=0, DF=50, SCRAMBLE=200,
DIVERSITY=NO,OPNAME="main";;

on LMT
Function
Use this command to add a 3G neighboring cell. The source cell is a 2G internal cell and
the neighboring cell is a 3G external cell.
Note
3G neighboring cells can only be target cells.
Example
ADD G3GNCELL: IDTYPE=BYNAME, SRC3GNCELLNAME="BTS3036",
NBR3GNCELLNAME="UMTS_1-0", RSCPOFF=48, ECNOOFF=48;

on LMT
Function
Use this command to add an Iur-g connection.
Note
1. Ensure that the relevant neighboring RNC has been configured before an Iur-g
connection is added.
2. The Connection Type parameter information in the added Iur-g connection must match
the Co-MBSC parameter information of the relevant neighboring RNC. Internal RNC
corresponds to Yes, and External RNC corresponds to No.
3. The parameters "Subrack No.", "Slot No.", and "Subsystem No." determine the number
of the CPU whose logical function type is RGCP or GCP. This CPU is used by the BSC to
actively set up a connection. If the Iur-g connection needs to be established for multiple
RNCs, it is recommended that the connections are allocated on different CPUs. It is not
allowed to configure subsystem 0 for the board of RGCP type.
4. If the value of the parameter "Connection Type" is "INNER(Internal )", the values of
"Peer Subrack No.", "Peer Slot No.", "Peer Subsystem No.", and number of the CPU of
RUCP or UCP type need to be specified. This configuration needs to be negotiated with
the RNC. It is not allowed to configure subsystem 0 for the board of RUCP type.
Example
ADD GIURGCONN: RNCINDEX=0, CONNTYPE=INNER, SRN=0, SN=0, SSN=1, DESTSRN=0,
DESTSN=2, DESTSSN=1;
ADD GIURGCONN: RNCINDEX=1, CONNTYPE=EXTERNAL, SRN=0, SN=0, SSN=2;

on LMT

on LMT

OMC331400 BSC6900 GSM V900R014 Data Configuration Based o

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OMC331400 BSC6900 GSM V900R014 Data Configuration Based o

Uploaded by

Copyright:

Available Formats

BSC6900 GSM V900R014 Data Configuration Based

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GSM V900R014 Data Configuration Based

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GSM V900R014 Data Configuration Based

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GSM V900R014 Data Configuration Based

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GSM V900R014 Data Configuration Based

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GSM V900R014 Data Configuration Based

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GSM V900R014 Data Configuration Based

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GSM V900R014 Data Configuration Based

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GSM V900R014 Data Configuration Based

SET CMCTRLSW: CTRLSW=OFF;

LCK CMCTRL: RSNDES=UPGRADE;

BSC6900 GSM V900R014 Data Configuration Based

the data configured takes effect immediately on the subrack.

When a subrack is in ineffective mode, you cannot query, compare, or perform

If the OMU is newly installed, subrack 0 is in ineffective mode by default. If a

SET CFGDATAINEFFECTIVE: SRN=0;

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GSM V900R014 Data Configuration Based

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GSM V900R014 Data Configuration Based

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GSM V900R014 Data Configuration Based

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GSM V900R014 Data Configuration Based

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GSM V900R014 Data Configuration Based

Use this command to add a GSM operator.

ADD GCNOPERATOR: OperatorType=PRIM, OPNAME=BH01", MCC="460",

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GSM V900R014 Data Configuration Based

Signal point data format

ADD OPC: NAME="MBSC NO1", SPX=0, NI=NATB, SPCBITS=BIT14, SPDF=WNF, SPC=H'A00,

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GSM V900R014 Data Configuration Based

DPC is used to address the peer element of BSC in SSN.7 network.

IUCS_RANAP: indicates the signaling point of the IU interface CS control plane.

STP: indicates the signaling transfer point.

AAL2SWITCH: indicates the ATM switch.

A: indicates the signaling point of the A interface control signaling plane.

LB: indicates the signaling point of the LB interface.

ADD N7DPC: NAME="TEST NO1", DPX=3, SPX=1, SPDF=WNF, DPC=H'AB, DPCT=IUR,

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GSM V900R014 Data Configuration Based

M3UA_ASP: suggested to use when there is a signaling transfer point (STP)

M3UA_IPSP: suggested to use when there is no signaling transfer point (STP)

ADD M3LE: LENO=0, SPX=0, ENTITYT=M3UA_ASP, RTCONTEXT=0, NAME="Test";

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GSM V900R014 Data Configuration Based

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 GSM V900R014 Data Configuration Based

M3UA_ASP: suggested to use when there is a signaling transfer point (STP)

M3UA_IPSP: suggested to use when there is no signaling transfer point (STP)

M3UA_SS7SP: suggested to use when the destination entity is a narrowband

M3UA_SP: represents all types of the destination entity

ADD M3DE: DENO=0, LENO=0, DPX=1, ENTITYT=M3UA_IPSP, RTCONTEXT=1,