NodeB Site Creation Script:-

Following files are attached

1. Script for Site Creation
2. RF Parameters
3. 3G FNP Plan

NodeB Site Creation Example of RF 3G

Script.xls Parameters for Site Creation.xls FNP_SITES_Master plan.xls

Detailed function of each command:-

1. Add SAC(ADD USAC)

ADD SAC: CnOpIndex=2, LAC=3, SAC=3;

Function

Use this command to add the service area information to an RNC.

SAC: Service Area Code

Note

1. The corresponding LAC exists in the location area table.

2. The Location Area Code and Service Area Code can be configured in the decimal or
hexadecimal format. In the hexadecimal format, the Location Area Code and Service Area
Codemust be started with H' or h'.

3. The Location Area Code cannot be set to H'0000 (0) or H'FFFE (65334). The two values are
reserved for some special cases.
 2. Add SCTP Link(ADD SCTPLNK)

ADD SCTPLNK: SRN=3, SN=8, SSN=0, SCTPLNKN=3, MODE=SERVER,

APP=M3UA, LOCIPADDR1="1.1.1.1", PEERIPADDR1="1.1.1.1",
LOGPORTFLAG=NO, VLANFlAG=DISABLE, SWITCHBACKFLAG=YES;

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.

3. Add NodeB(ADD UNODEB)

Function

Use this command to add a NodeB.

Note

1. The value range of the Extended Processing Subrack (EPS) No. is 1~11. The number of
the Main Processing Subrack (MPS) is 0.
2. When NodeB is successfully added, you can add NCP and CCP to the NodeB with the
commands ADD UNCP and ADD UCCP, and then, add a local cell belonging to the
NodeB with the command ADD ULOCELL. In addition, in order to identify the NodeB
to which the cell belongs, it is necessary to bind the cell with the NodeB through the
command ADD UCELLSETUP.
3. After being configured, the NodeB is in 'TESTING' state by default. Thirty minutes
later, the NodeB will be set in 'NORMAL' state by system
 4. Add NodeB Algorithm Parameters(ADD
UNODEBALGOPARA)

Function

Use this command to add NodeB algorithm parameters, including NodeB congestion
control parameters,NodeB Max HSDPA User Number,NodeB Max HSUPA User Number
and HSUPA Credit Consume Type.

Note

The command should run before the command ADD UNCP.

5. Add NodeB LDR Algorithm Parameters(ADD UNODEBLDR)

Function

Use this command to add NodeB load reshuffling (LDR) algorithm parameters.

Note

1. DL LDR first action, DL LDR second action, ..., and DL LDR Sixth action meet the
following conditions:
1) If DL LDR ith action is set to NOACT (NO ACTION), the subsequent parameters can
only be set to NOACT (NO ACTION).
2) Except NOACT, the following actions cannot be selected repeatedly.
A typical procedure is as follows:
DL LDR first action can be selected from {NOACT, BERATERED, QOSRENEGO,
CSINTERRATSHOULDBELDHO, PSINTERRATSHOULDBELDHO,
CSINTERRATSHOULDNOTLDHO, PSINTERRATSHOULDNOTLDHO}. Suppose this
parameter is set to BERATERED.
DL LDR second action can only be selected from {NOACT, QOSRENEGO,
CSINTERRATSHOULDBELDHO,
PSINTERRATSHOULDBELDHO,CSINTERRATSHOULDNOTLDHO,
PSINTERRATSHOULDNOTLDHO}. Note that BERATERED cannot be selected any
more.
The rest parameters can be deduced by analog.
2. UL LDR first action, UL LDR second action, ..., and UL LDR Sixth action meet the
conditions similar to the above.
3. Ul LDR Credit SF reserved thresholdThe comparison between the spreading factors
is based on the number following the acronym "SF", for example, SF32>SF8.
4. Dl LDR Credit SF reserved thresholdThe comparison between the spreading factors
is based on the number following the acronym "SF", for example, SF32>SF8

6. Add the NodeB OLC parameters(ADD UNODEBOLC)

Function

Use this command to add the parameters of the OverLoad Control (OLC) algorithm to the
NodeB.
7. Add Adjacent Node(ADD ADJNODE)

Function

Use this command to add an adjacent node. It indicates an adjacent network device of
RNC.

Note

1. If Adjacent Node Type is IUB, IUR, IUCS or IUPS, you can run the ADD ADJMAP
command to configure the associated TRMMAP index, load EQ threshold table index and
factor table index. If ADJMAP is not configured, the system automatically uses the default
TRMMAP, load EQ and factor. You can run the LST TRMMAP, LST LOADEQ, LST
TRMFACTOR command to query default TRMMAP, load EQ and factor table.
2. If Adjacent Node Type is IUB, the corresponding NodeB ID must be configured. You
can run the LST UNODEB command to query the configuration.
3. If Transport Type is ATM, SAAL link No. must be configured. You can run the LST
SAALLNK command to query the configuration.
4. If Adjacent Node Type is IUCS, IUPS, IUR, or NNI_AAL2 SWITCH, the entered
DSP index must be configured. You can run the LST N7DPC command to query the
configuration.
 8. Add NCP Link(ADD UNCP)

Function

Use this command to add a NodeB Control Port (NCP) link between the RNC and a
NodeB, which is used to transmit NodeB Application Part (NBAP) common process
messages of Iub interface. There is only one NCP link between a RNC and a NodeB.

Note

1. The corresponding NodeB must have been successfully configured through the ADD
UNODEB command.
2. Before running this command, add the algorithm parameters through the ADD
UNODEBALGOPARA command, the LDR algorithm parameters through the ADD
UNODEBLDR command, and the overload control parameter NODEBOLC through the
ADD UNODEBOLC command.
3. The SAAL link or SCTP link that bears the NCP link must have been successfully
configured through the ADD SAALLNK or ADD SCTPLNK command and is not
occupied by other links.
4. The SAAL link that bears the NCP link must be of UNI type.
5. The SCTP link that bears the NCP link must be of NBAP type.
6. The NodeB must support the bearer link types (SAAL link type, SCTP link type, and
SAAL-SCTP link type) of NCP.
7. The link that bears the NCP link must be in the same subsystem as NodeB.
8. One NodeB can be configured with only one NCP.

9. Add CCP Link(ADD UCCP)

Function

Use this command to add a Communication Control Port (CCP) link between the RNC
and a NodeB, which used to transmit NodeB Application Part (NBAP) dedicated process
messages of Iub interface. There can be multiple CCP links between one RNC and one
NodeB.

Note

1. The NCP link to the NodeB must have been configured successfully.
2. For the same CCP link, its Port No. at RNC must be consistent with that at NodeB.
3. The SAAL link or SCTP link that carries the CCP link must have been successfully
configured through the ADD SAALLNK or ADD SCTPLNK command and is not
occupied by other links.
4. The SAAL link that bears the CCP link must be of UNI type.
5. The SCTP link that bears the CCP link must be of NBAP type.
6. The NodeB must support the bearer link types of CCP.
7. The link that bears the CCP link must be in the same subsystem as NodeB.

10. Add Adjacent Node Mapping(ADD ADJMAP)

Function

Use this command to add the TRM mapping to an adjacent node and to add the mapping
from interface transmission type to TRMMAP index(see ADD TRMMAP), path load EQ
index(see ADD LOADEQ), and factor index(see ADD TRMFACTOR).

Note

1. When Interface Type is IUB, Resource Management Mode can be SHARE or

EXCLUSIVE.
2. For an adjacent node of the IUB type, only the mapping from the adjacent nodes whose
Resource Management Mode is of the same value is allowed.
3. The adjacent node can be configured with load EQ index only when Interface Type is
IUB, Transport Type is ATM/IP dual stack or hybrid IP. For details, see ADD LOADEQ.

11. Add IP Route(ADD IPRT)

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.
4. The FG2a, GOUa, FG2c, and GOUc boards support Ethernet standby route. The
destination address is the IP segment of the Ethernet port, and the route mask is the mask
of the Ethernet port. When the Ethernet port is faulty, the Ethernet standby route takes
effect. The data is sent through the out port of the Ethernet standby route.
5. The FG2a, GOUa, FG2c, GOUc, UOIa (ATM or IP), and UOIc boards support the
configuration of load-sharing routes. The routes have the same destination address, mask,
and priority, but different next hopping addresses. When the load-sharing routes are
configured, the data is sent through the ports specified by the routes on an equal basis.
When one of the routes is unavailable, the data is sent though the out ports of other load-
sharing routes.
6. A maximum of eight routes can be configured as load-sharing routes and main and
standby routes. That is, a maximum of eight routes with the same destination IP address
and subnet mask can be configured.
7. If an IP path has enabled the IPPM function, it does not support the configuration of
loading sharing routings.
8. For the AEUa, AOUa, UOIa (ATM), UOIc (ATM), and AOUa boards, next hop
address must be set to the IPoA PVC peer address of the active board. For the PEUa,
POUa, UOIa, and POUc boards, next hop address must be set to the PPP peer address or
the MPGRP peer address of the active board. For the FG2a, GOUa, FG2c, and GOUc
boards, next hop address must be set to an IP address in the same network segment of
any FE/GE port address of the active or standby board.
9. If the next hop address of a new routing is the peer IPoA PVC address and the carrier of
the IPoA PVC does not exist, the routing cannot be added.
10. The configured routes must not be on the network segments that have inclusion
relation.
11. The relation of the IP route priorities are: Default > High > Low.
12. When "Global route management switch" is set to "ON(Enable the global route
management)", the global load sharing FG2c, GOUc, UOIc (ATM) boards must be
controlled by the same MPU.
12. Add IP Path(ADD IPPATH)

Function

Use this command to add an IP path.

IP path is an important transmission resource. It carries the user plane data between the
RNC 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 RNC.
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.
7. If Peer subnet mask is not 255.255.255.255, there should be no host route or network-
segment route smaller than Peer IP address and Peer subnet mask to prevent multi-port
path. See ADD IPRT command.
8. The total number of AAL2 paths and IP paths configured on a RNC cannot exceed
13,000.
9. The total number of AAL2 paths and IP paths on the adjacent node of the Iub type
cannot exceed 36. The total number of AAL2 paths and IP paths on the adjacent node of
the Iu-PS type cannot exceed 128. The total number of AAL2 paths and IP paths on the
adjacent node of the Iur or IUCS type cannot exceed 210.
10. The index of the load threshold table (see the ADD TRMLOADTH command) must
exist, and bandwidth values in the load threshold table must be smaller than those
configured for the IP path.
11. The VLAN function is not supported when the bearing port of the IP path is of MLPPP
type. Therefore, the VLAN ID does not need to be configured. not to be configured.
12. The Iu-CS IP path with the same peer IP address and peer subnet mask cannot be
configured on different Iu-CS adjacent nodes.
13. For Iu-CS/Iu-PS IP Path, the total number of peer network segments cannot exceed
256, that is, the number of peer IP addresses and peer subnet masks cannot exceed 256.
14. For FG2a, GOUa, and UOIa(IP) board, because of the limit of the board's capacity, the
SCTP link, NodeBIP and IPPATH numbers on one board should obey the following rules:
(the number of SCTP link + NodeBIP + No-Qos IPPATH + 14*Qos IPPATH) <= 2048.
15. When the global route management switch is ON (set by SET GLOBALROUTESW
command), the interface board where the Local IP address is located, and the interface
board where the IP route out port of Peer IP address is located, must be bound with same
MPU subsystem.

13. Add NodeB IP Address(ADD UNODEBIP)

Function

Use this command to add an IP address for the NodeB which is maintained by the NMS through
the RNC.This command is applicable to the PEUa, AEUa, AOUa, AOUc, UOIa(ATM or IP), FG2a,
GOUa, POUa, UOIc, FG2c, GOUc and POUc boards.

Note

1. The NodeB to which the electronic serial number is to be added must have been configured.

2. Each NodeB can have only one IP TRANS IP address, one ATM TRANS IP address, or have
both.

3. The IP address is of class A, B, or C address determined by the customer according to the

actual network planning. 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. The first byte of the IP address cannot be 0 or 127.

4. The IP address to be added must not be the one that is configured for another NodeB.

5. The IP address for the NodeB must not be the broadcast address or the multicast address.

6. The IP address for the NodeB and the internal IP address for the OMU must not be on the same
network segment, or the two network segments with inclusion relation.

7. The IP address for the NodeB must not be the same with any IP address that has been
configured in the RNC. The IP addresses that have been configured in the RNC include the local
IP address of the PPP link, the local IP address of the MP group, the device IP address, the Trunk
IP address, and the Ethernet port IP address.
14. Add NodeB Electronic Serial Number(ADD UNODEBESN)

Function

Use this command to add an electronic serial number (ESN) so as to response to the
DHCP request from the NodeB. This command is applicable to the FG2a, GOUa, FG2c,
POUa, POUc, PEUa, GOUc and UOIa boards.

Note

1. The NodeB to which the ESN is to be added must have been configured.
2. This command is used only when the NodeB supports the IP transmission. The IUB
Trans Bearer Type can be queried by executing LST UNODEB. The NodeB that the
bearer type is IP_TRANS(IP transmission), ATMANDIP_TRANS(ATM and IP
transmission), HYBRID_IP_TRANS(Hybrid IP transmission) supports the IP
transmission.
3. Only two ESNs that are in active and standby relation can be added to each NodeB.
4. The IP address for the NodeB port must not on the network segment 0 or 127. The IP
address must not be the broadcast address or the multicast address.
5. The IP address for the NodeB port and the internal IP address for the OMU must not be
on the same network segment, or the two network segments with inclusion relation.
6. The IP address for the NodeB port must not be the same with any IP address that has
been configured in the system. The IP addresses include the local/peer IP address of the
PPP link, the local/peer IP address of the MP group, the device IP address, the Ethernet
port IP address, and the peer address of the IPoA PVC.

15. Add IP to VLAN ID Mapping Table(ADD VLANID)

Function

Use this command to add next hop IP to VLAN ID mapping table.

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
16. Start NodeB Detect Function(STR UNODEBDETECT)

Function

Use this command to detect the ID of the VLAN where the NodeB belongs. With the detection
function, the RNC associating with the NodeB detects the number of the VLAN where the NodeB
belongs to implement successful DHCP interaction.This command is applicable to the FG2a,
FG2c, GOUa, GOUc boards.

Note

1. When the detect type is set to ALL, only the current configured NodeBs are detected. However,
if another NodeB is added after the detection, the detection for this added NodeB must be started.

2. Before executing this command, ensure that the VLAN IDs of the OM IP address and the PORT
IP for the NodeB have been configured.

17. Add Local Cell(ADD ULOCELL)

Function

Use this command to add a local cell belonging to a specified NodeB.

Note

1. Local cells are the resources of NodeB, which can be configured.

2. Local cell ID is unique in NodeB. However, it can be unique in UTRAN for the
convenience of management.
3. Local cell ID is obtained through the negotiation with NodeB. The Local cell ID set on
the RNC side must be consistent with that set on the NodeB side.

17. Add Service Priority Group(ADD USPG)

Function

Use this command to add a service priority group (SPG). Through the SPG, different services are
set to different priorities so that the service layers are differentiated. The Service priority group
Identity is specified when a new cell is set up through the ADD UCELLSETUP command. For
example, in the network planning, cell A carries the HSDPA services preferentially, whereas cell B,
which is on a different band but under the same coverage area with cell A, carries the R99 non-
real-time services. In this case, set Service priority of HSDPA service that corresponds to
Service priority group Identity of cell A to a higher priority, whereas set Service priority of R99
NRT service that corresponds to Service priority group Identity of cell B to a higher priority. In
this manner, the service layers of the two cells are differentiated.

18. Add Cell Quickly(ADD UCELLQUICKSETUP)

Function

Use this command to quickly set up a BTS.

The channel specifications in the cell set up by this command are as follows:

(1) One PCCPCH carrying on BCH, one SCH carrying one PSCH and one SSCH, and one
PCPICH.

(2) The common physical channel identifier of the first SCCPCH is 8. The transport channel
identifier of the PCH is 3. The transport channel identifier of the first FACH carrying signaling is 4.
The transport channel identifier of the second FACH carrying services is 5.

(3) One PRACH carrying one RACH.

(4) One PICH and one AICH.

18. Activate Cell(ACT UCELL)

Function

Activate the configuration data of a cell and make them available.

Note

1. Please using CHK UCELL to make sure that the cell data are complete and valid before
activation.

2. When the TRX of a cell is automatically shut down, you need to use the DEA UCELL command
to deactivate the cell if you need to reactivate the cell.

19. Add Intra-frequency Neighboring Cell(ADD

UINTRAFREQNCELL)

Function

Use this command to add an intra-frequency neighboring cell.

Note

1. Intra-frequency neighboring cells need not be configured in pairs. For example, if cell 1 is
configured as the intra-frequency neighboring cell of cell 2, cell 2 need not be configured as the
intra-frequency neighboring cell of cell 1.

2. A maximum of 31 intra-frequency neighboring cells can be configured for a cell. (According to

the related protocols, the maximum number of cells with the same frequency is 32.)

3. Before adding an intra-frequency neighboring cell, check whether this cell belongs to the local
RNC or another RNC. If the cell belongs to another RNC, run the ADD UEXT3GCELL command
to add the information of this cell first.

4. For a single host cell or primary host cell, the RNC ID is the ID of the serving RNC; for a
secondary host cell, the RNC ID is the ID of the RNC that controls the corresponding primary host
cell. (Dual-homed cell refers to the cell that has a peer cell in a RNC pool in the node redundancy
function. Single-homed cell refers to the cell that does not have a peer cell in a RNC pool in the
node redundancy function. Both primary cell and secondary cell are dual-homed cell. For details
on the cell configuration, see the parameter description of ADD UCELLSETUP.)

5. For a dual-homed cell, only the primary cell can be configured with neighboring cells. The
secondary cell cannot be configured with neighboring cells.

6. If Intra RAT Inter Plmn Ho Allowed is set to NO by using the SET

UOPERATORSHARINGMODE command, check whether the cell has the same serving operators
as the target cell. If the cell has the same serving operators as the target cell, neighboring cells
can be added. Otherwise, neighboring cells cannot be added. If inter-PLMN handover is supported
in the WCDMA system, whether the cell has the same serving operators as the target cell is not
taken into consideration.

20. Add Cell HSDPA Parameters(ADD UCELLHSDPA)

Function

Use this command to add high speed downlink packet access (HSDPA) parameters for a cell.

HSDPA: High Speed Downlink Packet Access

As a solution for the high speed DL data transmission, the HSDPA technology has its radio
interface with a maximum rate of 14.4 Mbit/s.

Note

1. Before adding the parameters, ensure that the cell is configured through the command ADD
UCELLSETUP or ADD UCELLQUICKSETUP.

2. When Allocate Code Mode is set to Automatic, Code Max Number for HS-PDSCH cannot be
smaller than Code Min Number for HS-PDSCH.
3. The Offset of HSPA Total Power must be smaller than or equal to the maximum transmit
power of the cell.

21. Activate Cell HSDPA Parameters(ACT UCELLHSDPA)

Function

Use this command to activate the high speed downlink packet access (HSDPA) function of a cell.

Note

1. The cell cannot support HSDPA function if the NodeB's protocol version is R99 or R4.

2. The HSDPA parameters of the cell must have been configured by ADD UCELLHSDPA
command and none of Number of HS-PDSCH codes and Number of HS-SCCH codes is zero.

22. Add Cell HSUPA Parameters(ADD UCELLHSUPA)

Function

Use this command to add the high speed uplink packet access (HSUPA) parameters of a cell.

Note

Before adding the cell HSUPA parameters, ensure that the cell is configured through the command
ADD UCELLSETUP or ADD UCELLQUICKSETUP

23. Activate Cell HSUPA Parameters(ACT UCELLHSUPA)

Function

Use this command to activate the high speed uplink packet access (HSUPA) parameters of a cell.

Note

The cell HSUPA parameters must have been configured.