1.

1 Site Creation in Nokia BSC
1.1.1 Required Data prior to site creation:
Before proceeding to adding a new site (BCF) under a Nokia BSC, we require the following: 1. Site Configuration Data – These details are received from the RF Planners. The configuration data for a given site shall minimally contain the following: a. BCF data – BSC identification, BCF identification and BCF name. b. BTS data – The BTS data should contain the following sets of parameters. i. BTS identification parameters: BTS identification, BTS name, LAC, CI, MCC, MNC, NCC, BCC, BAND. ii. Hopping parameters (optional): Hopping mode (HOP), MAIO Offset (MO), MAIO Step (MS) and Mobile Allocation frequency List (MAL). iii. GPRS parameters: GPRS enabling (Yes/No), RAC and NSEI. iv. EDGE parameters: EDGE enabling (Yes/No). c. TRX data – BTS identification, TRX identification, TRX frequency, TSC, GPRS enabling (GTRX = Yes/No) and Radio Timeslot type to be assigned to the TRX traffic channels. d. Neighbors – List of neighbors of the given site. 2. Site Transmission Plan: These details are received from the Transmission Department. The information required is a. Transmission plan containing the timeslot mapping for the OMUSIG,TRXSIG links and the radio timeslot allocation to the traffic channels. b. Information whether the given site is to be stand-alone or cascaded with another site.

1.1.2 Operational Procedure to create site
1. Create LAPDs. Each base station has one LAPD link called OMUSIG. It is connected to the OMU of the base station and used for O & M purposes like remote sessions to the BTS, software up- and downloading, transferring of alarms, transferring of configuration information, etc. Each TRX has one LAPD link called TRXSIG and up to eight traffic channels. There can be fewer traffic channels if some of the TRXs' radio interface time slots are used for signaling. The bit rate of the LAPD links can be either 16 or 64 kbit/s. Also 32 kbit/s is possible with TRX links. The MML command to create the LAPDs is: ZDSE:<link_name>:BCSU,<index>:<sapi>,<tei>:<rate>,<pcmtsl>,<sub_tsl>; Where: link_name =Name of the LAPD link .(eg. OMU01, T0101) index =Index of the BCSU controlling the link. (either 0 or 1)

Create BTSs. the value is 1. 3. ( eg. 2) bcc =BTS colour code. (eg.1:16. 2) eg: ZDSE:OM001:BCSU.BCC=<bcc>:MCC=<mcc>. Not obligatory.sapi tei =Service access point identifier. It is connected to the OMUSIG link created earlier.0:0. (eg. ZDSE:T0012:BCSU. KashimiraV1.REF=<bts_nbr >.) ci =Cell identity.HSN1=<hsn_number>:. (eg. 33-25) sub_tsl =The starting bit of the sub time slot in the ETPCM .NAME=<bts_name>. 404) . The MML command for the creation of a BCF is: ZEFC:<bcf_nbr>. A BTS is a logical counterpart of a sector in a base station site. ZDSE:T0011:BCSU.) site_type =The type of the base station.(eg. 11031) band =Frequency band of the cell. D=NOKIA Talk-Family.2.<site_type>:DNAME=<omusig>:<test_eq>:<bbu>.BTS=<bts_nbr>. (eg.) bts_name =Name of the BTS.(eg.2.0:62. 0 for TRXSIG. (eg. (eg.17-3. (16 kbps) pcm-tsl =ETPCM and the time slot used by the link . P=Ultra Site) omusig =The name of the OMUSIG link.3…. For OMU link. Create BCFs.BAND=<band>:NCC=<ncc>.. 0.1 …. Usually the same as the TRX number.1:16. …. It should not be confused with a base station even though they have the same abbreviation.) =Terminal end point identifier.. (not applicable) bbu =Battery back-up procedure. Must the same as defined in the BTS.) bts_nbr =Number of the BTS.:CI=<ci>.LAC=<lac>:HOP=<hop>.MNC=<m nc>. 1.2:16. The BCF parameters can be modified later with the EFM and EFT commands if needed. GSM) ncc =Network colour code. Where: bcf_nbr =Number of the BCF having the cell under creation.2.0 2.0. OMU01…) test_eq =Test equipment of the site. Where: bcf_nbr =Index of the BCF.P:DNAME=OM001:STM:BCCH.(eg. The MML command for the creation of a BTS is: ZEQC:BCF=<bcf_nbr>.(eg. (eg. 1. (not applicable) eg: ZEFC:1. rate =Bit rate of the link. B=NOKIA 2nd Generation.17-1.17-1. (62 for OMUSIG. 7) mcc =Mobile country code..0:0.3…. (eg.

Where: bts_nbr =Number of the BTS.REF=1:CI=1. It is not same as the value given for TRX signalling. EQJ. EQH. (eg. It is connected to the TRXSIG link created earlier.3…. (eg.NAME=BTS1. the TRX sub-time slots starts from 1 onwards. EQF. RF = radio frequency hopping.LAC=125:HOP=RF. The default values given by RF are usually MS=6 for all the three sectors. and EQM commands. 21) =Location area.2. (eg. 1. and MO=0/2/4 for the three sectors.g. EQG. EQK.<train_seq>.TRX=<trx_nbr>:GTRX=<Y/N>:<freq>. (eg.HSN1=6:.3…. Note:After all the 3 BTSs for the BCF are created. =Reference id of an already created BTS.) . You can change the MS and MO using the following command: ZEQA:BTS=<bts_no>:MS=6. (eg. (eg.) freq =Frequency of the TRX in terms of GSM/DCS channels.MO=0/2/4. 125) =Frequency hopping mode for normal layer TRXs: N = no. 35-1. the MAIO step (MS) and the MAIO Offset (MO) is to be changed as per the Change Request given by RF. 1.BC C=0:MCC=404. ARFCN value given by RF) train_seq =Training sequence code. RF) =Hopping sequence number1. change the parameter "RX DIVERSITY" to yes using the command ZEQM:BTS=<bts_nbr>:RDIV=Y:.mnc lac hop hsn Ref Note: =mobile network code.BTS=2. (eg. ZEQC:BCF=1. In case of ULTRA SITE only. BB = base band. A TRX is a logical counterpart of the transmitter receiver equipment in the base station. E.) trx_nbr =Number of the TRX. Create the TRX using the following MML command: ZERC:BTS=<bts_nbr>. (eg.<pc m_tsl>:DNAME=<d_link>:CH0=<ch_type>:.MNC=90. 4.2. as all the BTS parameters are then taken which are required for BPL Mobile Network and not the default parameters which will then have to be changed each time a BTS is created. whereas the TRX signalling sub-time slots start from 25 onwards. BCC value of the BSIC) pcm_tsl =First of the two Abis time slots used by the TRX. 38) as given by RF. Create TRXs. It is very important to give a reference BTS ID during the creation of the BTS. The BTS parameters can be modified later with the EQE. (eg.BAND=1800:NCC=0.

4. Lock the TRX using the command. Deactivating and deleting a cell broadcast message: 1. 3. ZERS:BTS=<bts_id>.TRX=<trx_id>:L:. The TRX parameters can be modified with the ERM command. (eg.1.TSC=0.2 Cell Broadcast Message Handling of a BTS Creating and activating Cell Broadcast Message: The activation of cell broadcast message is done in the following MML commands: 1. Deleting all deactivated messages is done by the command: ZECD:0:.TRX=1::FREQ=541. T0011) ch_type =Type of the channel. 1.3 Modification of the channels assigned to the radio timeslots of a TRX 1. ZERC:BTS=1. 3. .TRX=2::FREQ=543. ZERM:BTS=<bts_id>. Each of the eight radio channels can be assigned a type.PCMTSL=171:DNAME=T0011:CH0=MBCCH. Lock the BTS using the command. 1. tsl_cnt is the number of the Abis time slots used for something else than traffic.ENG:2:. 2. Enter the message and type Ctrl+c to the end the message.TRX=<trx_id>:CH<channel_no>=<channel type>:. Default is TCH. Name of the signalling LAPD. MBCCH or TCH) tsl_cnt =This optional parameter is used if some of the TRX's Abis time slots are used by signalling links.d_link =Name of the TRX link used by the TRX. Eg: ZERC:BTS=1. Change the channels allocated to the radio timeslots as follows.PCMTSL=17-3:DNAME=T0102:CH0=SDCCH.CH1=SDCCB.1 Modification of channels assigned to the radio timeslots on a BCCH TRX: The modification of channel behavior in case of BCCH TRX is done as follows: 1. 2.3.TSC=0. 2. Create Broadcast Message if required: ZECA:50:<next_msg_code>:4:1. ZEQS:BTS=<bts_id>:L:. To activate a message to BTS: ZECS:<msg_id>:BTS=<bts_id>:.(eg. Check if Broadcast Message has been created: ZECP. This is done as follows by the command ZECE:<msg_id>:BTS=<bts_id>:.

MBCCH. ZERM:BTS=<bts_id>. Unlock the TRX using the command. 2. channel_no can take decimal values from 0 to 7.3 Modification of channels assigned to the radio timeslots on a Non-BCCH TRX in hopping BTS The modification of channel behavior in case of BCCH TRX is done as follows: 1. MBCCB. Lock the TRX using the command. Unlock the TRX using the command. Unlock the sector. SDCCH. 5.TRX=<trx_id>:L:. 5. using the command. Lock the TRX using the command. MBCCHC. Lock the BTS using the command.Channel type can be TCH.TRX=<trx_id>:L:. 3. channel_no can take decimal values from 0 to 7. Change the channels allocated to the radio timeslots as follows. SDCCH. Unlock the sector. 4. MPBCCH. SDCCB.Where. SDCCH.3.1 Modification of frequency of a BCCH TRX The modification of frequency in case of BCCH TRX is done as follows: 1. SDCCB.1. SDCCB.Channel type can be TCHF. 1. TCHD. Change the channels allocated to the radio timeslots as follows. Change the frequency as follows. ZEQS:BTS=<bts_id>:U:. ZERM:BTS=<bts_id>.TRX=<trx_id>:CH<channel_no>=<channel type>:. 3. Where.4.TRX=<trx_id>:U:. 3. ZERS:BTS=<bts_id>. 1. ZERS:BTS=<bts_id>. 4.2 Modification of channels assigned to the radio timeslots on a Non-BCCH TRX in a Non-Hopping BTS The modification of channel behavior is done as follows: 1.1. MBCCB.Channel type can be TCH. Unlock the TRX using the command. ZERS:BTS=<bts_id>. ZERS:BTS=<bts_id>. 2. MPBCCH. MBCCHC. MBCCB. ZERM:BTS=<bts_id>. ZERS:BTS=<bts_id>. Lock the TRX using the command.TRX=<trx_id>:L:.4 Modification of the frequency assigned to a given TRX 1. MBCCH. ZEQS:BTS=<bts_id>:U:. MPBCCH.TRX=<trx_id>:U:. using the command.1. Lock the BTS using the command. channel_no can take decimal values from 0 to 7. Where. 1. MBCCH.TRX=<trx_id>:U:. .TRX=<trx_id>:CH<channel_no>=<channel type>:. 2. ZEQS:BTS=<bts_id>:L:. MBCCHC.3. ZEQS:BTS=<bts_id>:L:.TRX=<trx_id>:FREQ=<new_freq_val>:. ZERS:BTS=<bts_id>.

ZEQS:BTS=<bts_id>:L:.1800:<list of frequencies separated by ‘&’>:. ZERM:BTS=<bts_id>. 1. Lock the TRX using the command.3 Modification of frequency of a Non-BCCH TRX in a hopping BTS The modification of frequency is done as follows: 1. using the command. 4. 1. Change the frequency as follows. Lock the TRX using the command. Change the frequency as follows. Unlock the TRX using the command. Unlock the sector. ZERS:BTS=<bts_id>. ZERS:BTS=<bts_id>. create the MAL using the command: ZEBE:<new_mal_id>.5 Frequency Hopping Frequency hopping can be enabled in a given BTS using the following set of commands: 1.4. 3. ZEQS:BTS=<bts_id>:U:. Unlock the TRX using the command.HOP=RF:. 6. ZEQS:BTS=<bts_id>:U:. MAIO Offset (MO).2 Modification of frequency of a Non-BCCH TRX in Non-hopping BTS The modification of frequency is done as follows: 1. using the following command: ZEBI:<mal_id>:.TRX=<trx_id>:FREQ=<new_freq_val>:. 2. 5.1. ZERM:BTS=<bts_id>. Now the parameters MAL.TRX=<trx_id>:L:. Unlock the sector.TRX=<trx_id>:U:. ZERS:BTS=<bts_id>.4. 3. 4. assign the parameters HSN1 and HOP by the command: ZEQE:BTS=<bts_id>:HSN1=<hsn1_value>. . verify that the required mobile frequency allocation list exists. 1.1.TRX=<trx_id>:U:. 5. 5. ZERS:BTS=<bts_id>. using the command. First. Next. MS=<new_ms_val>:. Verify that the values have been correctly assigned by the command: ZEQO:BTS=<bts_id>:HOP:. MAIO Step are assigned to the BTS by the command: ZEQA:BTS=<bts_id:MAL=<mal_id>.TRX=<trx_id>:U:. 3. Lock the BTS using the command. ZERS:BTS=<bts_id>. 2.TRX=<trx_id>:L:.4. 2. Lock the BTS using the following command: ZEQS:BTS=<bts_id>:L:.TRX=<trx_id>:FREQ=<new_freq_val>:.MO=<new_mo_val>. Unlock the TRX using the command. If the required MAL (mobile allocation frequency list) is not present.

.Unlock the BTS using the command: ZEQS:BTS=<bts_id>:U:.