Professional Documents
Culture Documents
One important parameter is BTS type and BTS Template Name depending on the hardware
that is there on site we have to select the appropriate template as per template description
mentioned below.
1. Open the output summary file, change the sheet ‘ BTS transport layer’
a. change the BTS type (column C) BTS3900_GSM (Macro) or DBS_3900_GSM (Normal) .
The site type (DBS or Macro), please refer with the updated information from regional swap
manager/coordinator
b. check the BTS Template Name (column D): . to the corresponding one
‘BTS3900_BTS3900_GSM900_S888’ is for BTS3900 Macro site indoor with 3 Sec
‘DBS3900_VIRTUAL_GSM900_S888’ is for DBS3900 site.
c. change the BTS configuration (column F) refer to sheet ‘Cell basic info’ .
i. Refer the sheet ‘Cell basic info’ column B (BTSCONF) and column H (Cell Type)
ii. Rule
Sheet ‘Cell Basic Info’ Sheet ‘BTS Transport Layer’
BTSCONF CELL Type BTS Configuration
Sx GSM900 GSM900 Sx(1RRU3928) SUBRACK80 D
Sx/x GSM900 GSM900 Sx/x(1 RRU3928+1RRU3928) SUBRACK80 B
Sx/x/x GSM900 GSM900 Sx/x/x(1RRU3928+1RRU3928+1 RRU3928) S
SUBRACK80
Sx/x/x/x/x/x GSM900, GSM900 Sx/x/x &GSM1800 Sx/x/x
DCS1800 (1RRU3928+1RRU3928+1RRU3928+1RRU3928+1RR
U3928+1 RRU3928) SUBRACK80
Sx GSM900 GSM900 Sx(1Md) M
Sx/x GSM900 GSM900 Sx/x(1Md+1Md) A
Sx/x/x GSM900 GSM900 Sx/x/x(1Md+1Md+1Md) C
Sx/x/x/x/x/x GSM900, GSM900 Sx/x/x &GSM1800 Sx/x/x R
DCS1800 (1Md+1Md+1Md+1Md+1Md+1Md) O
Before
After
Technical paper Internal
Usually the highlighted sections are the ones that need to be completed. When introducing
the BTS Configuration, please pay attention to the number of TRXs from the Cell Basic Info
sheet.
For 1800 cells, you should choose sran8 TEMPLATE no EDGE – edge should be
deactivated for these cells, unless specified by Vodafone.
Step 1. Create a new planned data area in CME. You have to name your planned area and
make sure you select the corresponding BSC. Ensure that TISO option is unchecked.
This is how you find the OSP code for the transmission file and the NSE Identifier:
Step 2. Next you have to import the BTS Summary Data file you have converted and completed
and the radio file provided (Import NBI data).
Check only “Generate script on validation success”; sometimes you can get some
removal script necessary to run before the addition, but only for special cases – so check
carefully if there is something additional, to make sure it won’t affect other sites in the network;
After we have successfully imported the BTS summary data and the radio file we will have to
export the script for creating actual site.
Once we have the script, we will have to run it. We go to Topology >>> Main Topology and we
search for our BSC. We right click the BSC and select Maintenance Client then run the script in
Batch.
For troubleshooting here is guide for BTS IdleTS calculation for Edge and BTS trx power lock.
2G only scenario
3G only scenario
0 4
UEIU
1
GTMU
UBRI
FAN
UPEUc
3 7
UTRP board will be used if 3G has more than 4 E1 lines, it will be inserted to slot 4.
After VF confirming that E1 has been configured, call the Field Team to do loop C , E and F as shown
below .
Purpose: Cooperate with on-site subcontractor to verify the TDM transmission after swapping.
Precondition: The switch of BTS commissioning has finished by Vodafone D2.
LSTBTSCRC4;
Precondition: The E1 is configured by Vodafone D2 and the Partner has looped the E1 form site.
Operation Guide:
Step 1:
Check the E1 PORT status as follows:
Step 2 :
1.6. In the main window you should see continuous “Send” and “Receive” messages.
Step 2 (optional): After the E1 is looped at site, query form BSC the port number should be Available
Step 3: Ask the on-site subcontractor to remove the loop when the transmission is okay. Connect the E1 cables
and check the LIU LEDS go out on the GTMU , and the BSC port is Available .
You should now have connection to the GTMU and control of the BTS .
The Field team locally commission the BTS by USB stick . This loads the correct files into the GTMU .
After the BTS site is connected to the BSC and ACTIVATED , the RRU software will be updated automatically
and load from the GTMU .
Operation Guide: input DSP BTSBRD MML command to get the status and software version.
Ensure that they look at the correct RRU to ensure the alarms go active and clear on the correct sector!
The result of VSWR should less than 1.5, if bigger than 1.5, please inform the partner to check the connection.
Screen shots of MML output screen needed for good examples of all configurations – update after week
14
Huawei neighbour scripts are provided by HUAWEI RNO,run the provided script when the site is on air and
inform Vodafone D2 RNO run the none Huawei neighbour scripts .
Only BIND if there are no active alarms on the UMTS and GSM sites
After binding, data consistence should be double-check, here is description from CME help document.
1. Configuration --> Multi-Mode Base Station Management --> Multi-Mode Relationship Management
Binding the sites: choose ‘Relationship Management’ sheet, click ‘Bind…’, change the Target MBTS Type
from ‘GUL’ to ‘GU’, choose target GBTS site and NodeB, click ‘>’, click OK.
The data in the current data area is consistent with the data on the live network. For details, see Managing
the Current Data Area.
A planned data area is open and the data in the planned data area is consistent with the data in the current
data area. For details, see Managing a Planned Data Area.
For details about MBTS(GL) data consistency check, see Rules for Checking MBTS Data Consistency
(GL).
For details about MBTS(GU) data consistency check, see Rules for Checking MBTS Data Consistency
(GU).
For details about MBTS(UL) data consistency check, see Rules for Checking MBTS Data Consistency
(UL).
3. Click . The dialog box for creating a consistency check task is displayed.
4. Set the task name in Check Task Name.
5. Select the check mode from the Check Mode drop-down list box, and select the MBTS to be checked
from the MBTS list in the lower part.
The available check modes are GL, GU, UL, and GUL.
6. Open the Select Rules tab page, select the check type from the Check Categories area, and select the
check rules for the check type from the Check Rules area.
NOTE:
You can select Apply To All to apply the preset check types and check rules to all MBTSs of the same
RATs.
7. (Optional) Set the error severity of check rules in the Check Rules area.
By default, the message level for a check rule is Warning. You can change the message level
as required.
Warning: a potential or impending service-affecting fault is detected before services are affected.
Error: a fault that currently does not affect services occurs and that a corrective action must be
taken to prevent a more serious fault.
Major: a service-affecting fault occurs. If the fault is not rectified in time, it will lead to a serious
result.
8. (Optional, applicable when the RATs of the MBTS are GL, GU, or GUL) Set the related attributes of
the TRX board on the Set MBTS Parameter tab page.
Co-Power Amplifier: indicates whether the carriers in GU or GL mode can be configured on one
power amplifier of the RXU.
Power overload: indicates whether the carrier power on the RXU can exceed the maximum
hardware capacity. If an excessive power is allowed, the RXU can support a larger transmit power
through power sharing between carriers.
Temperature: indicates the working temperature of the RXU. The temperature can be set to 50°C
in normal cases, and 30°C in some specific areas with low temperature. The MRRU at the
GSM900 band can support larger transmit power when it works at a low temperature.
9. Click OK. The CME starts the data check and displays check results.
Refresh Double-click the data record. The CME reconfigures the data automatically
according to the primary technology set for the multi-mode base station.
NOTE:
For the conflict result record of the RXU resources, double-click the record. The
dialog box for reconfiguring the RXU resources is displayed. You need to re-
allocate the RXU resources before the CME starts reconfiguring the data
automatically.
You need to adhere to the following principles if a local cell is configured with
two transmit channels:
The local cell does not support double transmit channels and the transmit
diversity mode for the sector that the local cell belongs to is set to common
mode. In this case, if the data of any RF channel on an RXU meets check
rules, the data check is successful.
The local cell supports double transmit channels and the two channels are
configured for different RXUs. In this case, if the data of a transmit
channel on an RXU does not meet check rules, you need to manually
modify the data.
None Manually modify the configuration data according to the error record.
There are three antenna scenarios, TMA with RET, SBT with RET, and RET only.
2. Run the BSC6900 MML command STR BTSALDSCAN to scan antenna devices.
RUN command.
Click Progress on the right top.
Click BTS Progress Information
Wait for result, it should be success
Double click that record, and scan result is shown.
Copy the serial number
3. Run the BSC6900 MML command ADD BTSTMA to add a smart TMA.
ADD BTSTMA: IDTYPE=BYID, BTSID=3, DEVICENO=0, DEVICENAME="TMA",
PWRSUPPLYTYPE=SINGLE_PORT_POWER, CTRLPORTCN=0, CTRLPORTSRN=81,
CTRLPORTSN=0, SUBUNITNUM=1;
4. Run the BSC6900 MML command ADD BTSRET to add an RET antenna.
ADD BTSRET: IDTYPE=BYID, BTSID=3, DEVICENO=1, DEVICENAME="RET", CTRLPORTCN=0,
CTRLPORTSRN=81, CTRLPORTSN=0, CTRLPORTNO=0, RETTYPE=SINGLE_RET,
SCENARIO=REGULAR, VENDORCODE="KA", SERIALNO=" CSC1996991 ";
5. Run the BSC6900 MML command DLD BTSALDFILE to download the ALD software or an RET
antenna configuration file to the OMU from the FTP Server;
6. Run the BSC6900 MML command LOD BTSRETCFGDATA to load the configured RET antenna
files from OMU of BSC to the RCU board of BTS;
1. Run the BSC6900 MML command STR BTSRXUBP to open ALD power switch.
2. Run the BSC6900 MML command STR BTSALDSCAN to scan antenna devices.
RUN command.
Click Progress on the right top.
Click BTS Progress Information
Wait for result, it should be success
Double click that record, and scan result is shown.
Copy the serial number
3. Run the BSC6900 MML command ADD BTSRET to add an RET antenna.
ADD BTSRET: IDTYPE=BYID, BTSID=3, DEVICENO=1, DEVICENAME="RET", CTRLPORTCN=0,
CTRLPORTSRN=81, CTRLPORTSN=0, CTRLPORTNO=0, RETTYPE=SINGLE_RET,
SCENARIO=REGULAR, VENDORCODE="KA", SERIALNO=" CSC1996991 ";
4. Run the BSC6900 MML command DLD BTSALDFILE to download the ALD software or an RET
antenna configuration file to the OMU from the FTP Server;
5. Run the BSC6900 MML command LOD BTSRETCFGDATA to load the configured RET antenna
files from OMU of BSC to the RCU board of BTS;
6. Run the BSC6900 MML command CLB BTSRET to calibrate RET.
7. Run the BSC6900 MML command MOD BTSRETSUBUNIT to modify RET antenna subunit
configuration data
MOD BTSRETSUBUNIT: IDTYPE=BYID, BTSID=3, DEVICENO=1, SUBUNITNO=1, TILT=25;
8. Run the BSC6900 MML command DSP BTSRETSUBUNIT to display RET subunit dynamic
information
9. Confirm current value with the following step.
Refer: 1.2 SET Site Status To "Install Mode" On M2000, the same procedure, just set with normal mode
for the situation that there are 2 E1s in the planning but actually VDF could only provide 1 E1
temporarily. As per the guide, all channels will be assigned to the 1st E1, but please pay attention:
a) Get BTS connect information, and record the E1 port No. in red oblong.
b) Check the time slots status of E1s by command DSP ABISTS. If the state is
idle or occupied that means this E1 is available, once the state is failure that
means the E1 is faulty.
And when you monitor the channel status, you will find nearly half channels are red.
f) Activate the site and check the channel status, all channels should be
available.
g) Add the 2nd E1 back and recover the idle time slot number to original setting.
a. Precondition
3G Hardware Template
Transport planning department is in charge of making 3G hardware template
according to hardware configuration. It should be imported in CME, but it is one time
activity. The process of importing 3G templates is same as 2G. Here is attached
some examples of 3G Templates.
b. Workflow
CME
After receiving the transmission file and the radio (.XUH) file we have to convert the csv file,
using the CSV Convert tool.
After we have converted our transmission file we proceed to completing the newly generated
document.
For 3G the NodeB template we need to select on basis of type hardware on site which can
be DBS3900 or BTS3900 with RRU or RFU and hybrid transmission. So depending on number
of E1’s, type of Ethernet port, no of carriers and power of carrier we need to select the right
NodeB template. Example is shown above.
The most important data that has to be completed has been highlighted. This is how you find
the ATM logic port. We usually choose the next available port – 56 in our case.
This is how you find the IP Logical port, the adjacent node ID and the SAAL links (we
take the next available values, like we did for the ATM logical port):
This is how we choose the subsystem where we will place our NodeB. We have to be
careful to not exceed 3 NodeBs/subsystem. We also need to be sure that the subrack no is
not changed if the SPU slot doesn’t have 3NodeBs/Subsystem. In such a case we need to
change the SPU slot and check the subsystem where we can put the new NodeB to avoid
SPU overload.
We should have the ATM transmission subrack same with the SPU subrack. Ex: for a
site on 0-18-2 , we should choose SPU on SR 0 ; for SN 4 and 8, we can’t choose SSN 0 ,
because that is MPU (ex can’t have 0 4 0, or 1 8 0, but we can have 0 0 0 , or 1 2 0 ).
After all the important data has been completed we have to save the transmission file.
Then, in the transmission file, we go to Add-Ins >>> Generate Site Sheet from Summary.
We save again and this will be the file that we will import to the CME.
Step 1. Create a new planned data area in CME. Be careful to choose the correct RNC. Ensure
that TISO option is unchecked.
After importing the Base Station Summary Data Table we will import the NBI Data (we
select the radio file):
After successfully importing the radio file, we have to do some modification in the site we
just created.
1. Modify the NTP Server IP. It should be set to the M2000 IP.
2.Create the Multicarrier Cell group this is not created in .XUH file sent by Vodafone so we
need to add it manually.
. 2
3
After these 3 modification we export the MML scenario which we will run on the corresponding
RNC. We go to the Topology >>> Main Topology >>> Right clik on our RNC >>> Maintenance
Client >>> Batch. When exporting the MML scenario please ensure that you select the ‘’Export
NodeB Configuration File’’ option.
The .xml file that is created share it with field team for onsite NodeB commissioning.
The old transmission ATM has to be re-used , therefore the old UMTS site has to be off air before connecting
the UMTS WMPT . There will be some delay (60 mins) while the ATM path is modified by VF.
Purpose: Cooperate with on-site subcontractor to verify the ATM/IP transmission after VFD2 have modified
the ATM.
Precondition: The switch of ATM has finished by Vodafone D2. The on-site subcontractor had looped the E1
on NodeB side, and VCL Continuous Check function is enabling for one SAALLNK of site in RNC.
Step 1: If possible, Ask Vodafone D2 transmission engineer to check the transmission status.
Step 2: Before patching E1 cable into BBU, loop one E1, and cooperate with OMC, OMC checks status with
DSP VCLCC.
Step 3: Ask the on-site engineer to remove the loop when Vodafone D2 transmission engineer confirm the
transmission is OK.
Step 4: With all E1’s looped onsite, perform the IMA loop test as shown below . (Needs to be proven in live
network)
Step 2: Ping NodeB Service Gateway (one VRRP IP, two physical IP) after customer update transport
configuration. And ping NodeB service IP after Huawei site is connected into transport network, the source IP
is interface board Dev IP of RNC.
After the change, DSP IPPATH to check the IPPATH is available or not.
1.4.4 OM IP confirmation
Step 1: Login Citrix
Step 2: Ping NodeB Service Gateway (one VRRP IP, two physical IP) after customer update transport
configuration. And ping NodeB service IP after Huawei site is connected into transport network, The source IP
is interface board Dev IP of RNC.
Huawei neighbour scripts are provided by HUAWEI RNO,run the provided script when the site is on air and
inform Vodafone D2 to run the none Huawei neighbour scripts .
Step 2: Active the cell by the command “ACT UCELL” (need type in the cell ID)
Step 3: Active the HSPA by the command “ACT UCELLHSDPA” and “ACT UCELLHSUPA” (need type in
the cell ID)
Step 4: Check the cell status after active the cell by command ”DSP UCELL” (need type in the cell ID)
Step 3: mare sure the value is not zero in Task ID 1-2 for voice call. About PS call, make sure Task ID 1-3
and 1-4 are not zero, one is HSDPA, the other is HSUPA.
Here is an example
Here downtime is end for UMTS part
2- There is 6 cells divided between the two antennas and in this case the power lock
value for both antenna A & B is 20W
3- There is 9 cells and in this case one antenna port power lock will be adjusted to 20W
and the second one no need to adjust
o So after collecting the cells data
We go to the next step
Set power lock value for all RXU of the NodeB by MML. The example like below:
Reset all RXU of the NodeB by MML one by one. The example like below:
After RXU is back to normal, check the power lock value by MML. The example like below:
DSP TXBRANCH;
If the target value is incorrect, confirm your operation and do it again. Other vise, escalate to
Huawei.
It means the external alarms should be connected to the LTE BBU as high priority. Otherwise the priority is
UMTS, then GSM.
Purpose: Configure the external alarm and cooperate with on-site subcontractor to verify the external alarm
Precondition:
1. The swap of GSM or UMTS part had been finished.
2. External alarm site list is presented in OMC and subcontractor sides.
3. External alarm setting list,( there might be external alarm set in RRU)
external
alarm.xls
Procedure:
Step 1: Config external alarm in BSC if there is GSM logic site in this physical site
Step 2: Configure external alarm in NodeB if there is only UMTS logic site in this physical site.
Operation Guide:
Caution: In M2000 first you need to define alarms by adding them to NE type, this will be done only once per
one Site type (for example DBS3900 WCDMA).
Define which NE type you want to add alarms for along with alarm type according to table below.
Step 1: Choose the Menu “NE Alarm Setting” (this will be done only once per one Site type)
Step 2: SET the external alarm according the standard which had agreed with Vodafone D2 (this will be done
only once per one Site type), make sure you click Apply button after setting
Step 3: Configure external alarm input port in BTS, NodeB or eNodeB with MML command, For example,
Command to configure the external alarm trigger in BSC(GSM):
SET BTSENVALMPORT: IDTYPE=BYID, BTSID=1, SRN=0, SN=18, PN=0, SW=OPEN, AID=65530,
PT=BOOL, AVOL= HIGH;
Command to configure the external alarm trigger in NodeB(UMTS):
SET ALMPORT: CN=0, SRN=0, SN=19, PN=0, SW=ON, AID=65230, PT=BOOL, AVOL=HIGH;
Step 4: Cooperate with on-site subcontractor to verify the external alarm by checking the relevant external
alarm on LMT when on-site subcontractor loop the external alarm on site according to external alarm.xls file.
1.4.17 Inventory
Step 1: M2000 client--->Configuration--->Inventory Management, then right-click that root, select Export
item.
Step 2: select NE--->select object to be exported--->select save folder--->select one folder in your laptop---
>click save and export. At last, check report in your laptop when progress is 100%.