Guide to obtaining bts3900 information(v1.0.2)

Guide to Obtaining BTS3900 Information Confidentiality
Level
Guide to Obtaining BTS3900 Information
Prepared by BTS3900 Maintenance Team Date 2011-03-04
Reviewed by Date
Approved by Date
Huawei Technologies Co., Ltd.
All Rights Reserved
2013-8-25 Huawei Confidential Page 1 of 69
Product Name Confidentiality Level
BTS3900 INTERNAL
Product Version Total 43 Pages

Level
Change History
Date Revision
Version
CR
ID
Section
Number
Description Author
2011-04-29 Draft completed Li Lijun

Level
Content
1 Accessing the BSC OMU.................................................................................................................5
1.1 Querying the Installation Directory of the Main Workspace of the OMU...........................6
1.2 Accessing the OMU by using the File Manager on the Web LMT .....................................6
2 Basic Operations..............................................................................................................................7
2.1 Querying the Custom Message.............................................................................................7
2.2 Querying COM Redirection................................................................................................10
3 Obtaining Common Information....................................................................................................15
3.1 Obtaining the BTS Log.......................................................................................................15
3.2 Obtaining the Board Log.....................................................................................................16
3.3 Obtaining the service logs of a TRX...................................................................................16
3.4 Obtaining Data Configuration (CFGMML).......................................................................17
3.5 Obtaining Inner Data Configuration (CFGMML)..............................................................18
3.6 Obtaining History Alarms of the BSC................................................................................19
3.7 Obtaining the Operation Log..............................................................................................20
3.8 Obtaining the Original Traffic Measurement File..............................................................22
3.9 Enabling the Single Pass Check Function..........................................................................23
3.10 Obtaining the Single Pass Log..........................................................................................24
3.11 SCP Mail Trace..................................................................................................................25
3.12 Obtaining Net List Information(Net)................................................................................26
3.13 Performing DSP Recording...............................................................................................27
3.14 Performing PD Recording.................................................................................................28
3.15 Performing TC Recording.................................................................................................29
3.16 Performing Uplink Frequency Scanning..........................................................................31
3.17 Querying Forward Power and Reverse Power..................................................................35
3.18 Querying the Interference Band........................................................................................38
3.19 Querying the GTMU A/B Board.......................................................................................39
3.20 Querying the RRU V1/V2 Module...................................................................................41
3.21 Querying the RFU V1/V2 Module...................................................................................42
3.22 Querying the Mapping Between Internal TRX Number and External TRX Number......42
3.23 Obtaining the Failure Log.................................................................................................44
3.24 Obtaining the TMU Alarm Log........................................................................................44
3.25 Tracing the CBUS2 Message............................................................................................45
3.26 Tracing the CBUS3 Message............................................................................................46
3.27 Single User Resource Check.............................................................................................46
3.28 Querying Information About the BTS Port Timeslot Distribution...................................48
3.29 Querying Version NO. and Internal Version NO..............................................................48
3.30 Obtaining CFG MML of single BTS................................................................................50
3.31 Obtaining Signaling..........................................................................................................50
4 Performing Related Operations......................................................................................................59
4.1 Performing Loopback Tests................................................................................................59

Level
4.2 Modifying the BTS Soft Parameters...................................................................................64
4.3 Reducing the Interference Band Software Parameters......................................................64

Level
1 Accessing the BSC OMU
The following figure shows the structure of the OMU directory:
XPU RUN log
DSP RUN message
DEBUG/GCSR/GPSR/GCHR/UCHR log
Configure files
PMF
Alarm log
Operation log

Level
1.1 Querying the Installation Directory of the Main Workspace of the OMU
You can run the LST OMUAREA command to query the workspace of the OMU and the current
running version.
1.2 Accessing the OMU by using the File Manager on the Web LMT
Click File Manager. The following window is displayed:
Note:
The File Manager can show a maximum of 1,000 pieces of data. If the number of files in the
directory exceeds 1,000, some log files may not be displayed. Therefore, you must use other
methods to obtain required information.

Level
2 Basic Operations
2.1 Querying the Custom Message
(1) Start the BSC6900, enter the super user mode, and click About.
(2) Click 0, 3, 1, 4, 2, and 0 in sequence.

Level
(3) Choose Device Maintenance > BTS Maintenance > Internal Maintenance > Custom
Message.
(4) The Custom Message window is displayed. Specify Site and Message Type.

Level
(5) Send a transparent transmission command of a custom message. The custom message may be
as follows:
D4-00-FF-FF-FF-81-00-FF-01-35

Level
(6) Query the current cell number and TRX number:
(1) Run the LST GCELL command to query the current cell number
(2) Run the LST GTRX command to query the TRX number
2.2 Querying COM Redirection
(1) Click About at the upper right corner of the BSC LMT.

Level
(2) Click 0, 3, 1, 4, 2, and 0 in sequence.
(3) Click BTS Maintenance and choose Internal Maintenance > COM Redirection.

Level
(4) On the COM Redirection page, specify Site and set Message Type to Transparent.

Level
(5) In the Custom Message text box, send a redirStart message to redirect the COM port of the
TMU. An OK dialog box is displayed.
(7) Send the following two messages to redirect the COM port of the RRU.
iSend2TrxShell "redirStart",0 (0 is the board number)
iSend2TrxShell "redirRestart",0 (0 is the board number)
(8) Right-click a target board and choose Query Board Information from the shortcut menu to
query the board number.

Level
The following figure shows the queried board number.

Level
3 Obtaining Common Information
3.1 Obtaining the BTS Log
(1) Run the STR BTSLOG command to obtain the BTS log. Specify BTS Index and set Board
Type to TMU(TMU/DTMU).
(2) After the command is executed completely, click File Manager, choose a log file from the
directory bamversion_aftpbtsbtscmplog (When BSC6900 version is R11) or
bamcommonftpbtsbtscmplog（When BSC6900 version is R12）, and click Download.

Level
3.2 Obtaining the Board Log
(1) Run the STR BTSLOG command to obtain log information and specify BTS Index, Board
Type, and Board No.
directory bamversion_aftpbtsbtscmplog, and click Download.
3.3 Obtaining the service logs of a TRX
(1) Run the STR BTSLOG command to obtain log information and specify BTS Index, Board
Type, and Board No. Here, set Command Parameter to mfs:/GSMLOG/GSMLOGS.lps.

Level
3.4 Obtaining Data Configuration (CFGMML)
(1) Run the EXP CFGMML command to export the current configuration file.
(2) Click File Manager, choose a log file from the directory
bamversion_aftpexport_cfgmml, and click Download.

Level
Note:
The rules for naming files (if no file name is specified) are as follows:
For example: CFGMML-BSC0-20091202184237.zip
CFGMML BSC0 2009 12 02 18 42 37 .zip
CFGMML + BSC0 + year + month + day + hour + minute + second + suffix of the file name
3.5 Obtaining Inner Data Configuration (CFGMML)
(1) Use the following MML command
EXP INNERCFGMML:;

Level
(2) Click File Manager, choose a log file from the directory
bamversion_aftpexport_cfgmml, and click Download.
3.6 Obtaining History Alarms of the BSC
(1) On the Web LMT, click Alarm, specify Alarm Type and Alarm Severity, and set Return
Amout to 4000 and Filter By BTS to a target site. Then, click Query.

Level
(2) After the alarms are filtered successfully, right-click an alarm and choose Save All from the
shortcut menu to save the result in the .csv format.
3.7 Obtaining the Operation Log
(1) Run the COL LOG command and set Log File Type to OPT_LOG.

Level
The rules for processing time are as follows: If Start Time and End Time are not set, logs
recorded from the earliest time to the latest time are exported by default. If Start Time is set but
End Time is not set, all logs recorded from the start time to the latest time are exported. If Start
Time is not set but End Time is set, logs recorded from the earliest time to the end time are
exported.
(2) Click File Manager and find the OperateLog.zip file from the directory
bamversion_aftpCOLLOGINFOOPT-LOG.

Level
3.8 Obtaining the Original Traffic Measurement File
Click File Manager and obtain the traffic measurement file from the directory
bamcommonMeasResult.
The rules for naming files are as follows:
A date.start time + time zone – end time + time zone period flag
date start time time zone end time period flag
Period calculation: end time – start time = traffic measurement period
Period flag:
Traffic measurement in a common period: EMS-NORMAL traffic measurement for 30
minutes or 60 minutes
A20100915.0300+0800-0400+0800_EMS-NORMAL.mrf.bz2
A20101126.1330+0800-1400+0800_EMS-NORMAL.mrf.bz2

Level
Traffic measurement in a short period: EMS-SHORTPERIOD traffic measurement for 15
minutes, 5 minutes, or 1 minute.
A20100811.0000+0100-0015+0100_EMS-SHORTPERIOD.mrf.zip
A20100811.0000+0100-0015+0100_EMS-SHORTPERIOD.mrf.zip
Traffic measurement of 24 hours:
A20100916.0000+0800-0000+0800_EMS-1440.mrf.bz2
Note:
You can extract only the traffic measurement files of the EMS-NORMAL type because the traffic
measurement period of the frequently used original file is 60 minutes.
3.9 Enabling the Single Pass Check Function
Run the SET GCELLSOFT command to enable the single pass check function and specify
parameters.

Level
3.10 Obtaining the Single Pass Log
(1) Click File Manager. The single pass log is stored in the directory
bamcommonfamfamlogfmt, and the prefix of the single pass log is [CDIG].
(2) The following table lists the formats for recording log file names:
Serial
Number
Item
1 Single pass time (format: YYYYMMDDHHMMSS)
2 Single pass check point
0: Uplink single pass
1: Downlink single pass
3 Single pass check result
0: No single pass
1: Single pass
2: Crosstalk
4 Total number of frames checked during the primary single pass check
5 Percentage of bad frames to checked frames
6 Site number, cell number, TRX number, and channel number of the call
7 Phone number (or TMSI/IMSI) being called and phone number (or TMSI/IMSI) of the peer party (record the
called number and the TMSI or IMSI information of the calling MS when the current call is an outgoing call;

Level
record the calling number and the TMSI and IMSI information of the called MS when the current call is an
incoming call), and record the phone number and IMSI/TMSI if they exist.
8 Transmission mode of the Abis interface
0: TDM
1: IP
2: HDLC
9 Subrack number, slot number, port number, timeslot number, and sub timeslot number of the Abis interface
board occupied by the current call, IP address and port of the Abis interface board (recorded if the Abis
interface is based on IP), HDLC port, and sub port (recorded if the Abis interface uses HDLC for
transmission)
10 Subrack number, slot number, port number, timeslot number, and sub timeslot number of the GEIUT of the
BM subrack (not required when the TC subrack and the BM subrack are integrated)
11 Subrack number, slot number, port number, timeslot number, and sub timeslot number of the GEIUT of the
TC subrack (not required when the TC subrack and the BM subrack are integrated)
12 Subrack number, slot number, DSP number, and DSP timeslot number of the DPU
13 CIC number of the A interface
14 Group number of the DPC
15 DTX switch (uplink and downlink switches)
16 Service type
3.11 SCP Mail Trace
(1) Run the following two commands to redirect the COM port to the local end.
iSend2TrxShell "redirStart",0
iSend2TrxShell "redirRestart",0
The value 0 is the board number Set the board number according to the actual condition.
(2) Trace the mail message.
//Open the downlink trace
iSend2TrxShell "MAILBOX_OpenDownTrace",0
//Close the downlink trace
iSend2TrxShell "MAILBOX_CloseDownTrace",0

Level
//Open the uplink trace
iSend2TrxShell "MAILBOX_OpenUpTrace",0
//Close the uplink trace
iSend2TrxShell "MAILBOX_CloseUpTrace",0
The value 0 is the board number Set the board number according to the actual condition.
3.12 Obtaining Net List Information(Net)
(1) Run the DSP BTSNET command to query the TMU net list and set NET Object Type to
TMU Net.
(2) Run the DSP BTSNET MML command to query the BTS upper-layer net list, set NET
Object Type to TRX, and choose a target site.
(3) Query the lower-layer net list of the BTS by sending custom messages.
Open the Custom window, set Message Type to Transparent, and send the following
command to transparently transmit custom messages to the remote end:
D4-00-FF-FF-FF-81-00-FF-01-35
Then, send the following custom messages:
D4-00-ff-ff-ff-81-00-ff-05-99-01-00-00-ff
D4-00-ff-ff-ff-81-00-ff-05-99-01-01-00-ff
D4-00-ff-ff-ff-81-00-ff-05-99-01-02-00-ff

Level
D4-00-ff-ff-ff-81-00-ff-05-99-01-03-00-ff
D4-00-ff-ff-ff-81-00-ff-05-99-01-08-00-ff
D4-00-ff-ff-ff-81-00-ff-05-99-01-09-00-ff
D4-00-ff-ff-ff-81-00-ff-05-99-01-0A-00-ff
D4-00-ff-ff-ff-81-00-ff-05-99-01-0B-00-ff
D4-00-ff-ff-ff-81-00-ff-05-99-01-0C-00-ff
D4-00-ff-ff-ff-81-00-ff-05-99-01-0D-00-ff
D4-00-ff-ff-ff-81-00-ff-05-99-01-0E-00-ff
D4-00-ff-ff-ff-81-00-ff-05-99-01-0F-00-ff
D4-00-ff-ff-ff-81-00-ff-05-99-01-10-00-ff
D4-00-ff-ff-ff-81-00-ff-05-99-01-11-00-ff
D4-00-ff-ff-ff-81-00-ff-05-99-01-12-00-ff
D4-00-ff-ff-ff-81-00-ff-05-99-01-13-00-ff
D4-00-ff-ff-ff-81-00-ff-05-99-01-14-00-ff
D4-00-ff-ff-ff-81-00-ff-05-99-01-15-00-ff
D4-00-ff-ff-ff-81-00-ff-05-99-01-16-00-ff
D4-00-ff-ff-ff-81-00-ff-05-99-01-17-00-ff
D4-00-ff-ff-ff-81-00-ff-05-99-01-18-00-ff
D4-00-ff-ff-ff-81-00-ff-05-99-01-19-00-ff
D4-00-ff-ff-ff-81-00-ff-05-99-01-1A-00-ff
Save the query results in .txt files and send the files to R&D engineers.
3.13 Performing DSP Recording
DSP recording must be tested when the tested MS is in a conversation process.
(1) Run the SET UMRECORDPARA command, specify TRXID and CHNO according to the
data found in section 3.24 "Single User Resource Check", and set SUBCHNO to the channel
occupied by the call, that is, FULLRATEORPDCH, HALFRATE0 , or HALFRATE1.
SET UMRECORDPARA: UMRECCMDCODE=STARTREC, SERVICETYPE=CS,
TRXID=468, CHNO=3, SUBCHNO=FULLRATEORPDCH, RECDIR=DLONLY,
RECMAXTIME=20;

Level
(2) After the recording is completed, run the SET UMRECORDPARA command and specify
UMRECCMDCODE to STRULDRECDATA. View the progress, and after the progress reaches
100%, perform Step 3. An example of the command is as follows:
SET UMRECORDPARA: UMRECCMDCODE=STRULDRECDATA, TRXID=468;
(3) Run the STR BTSLOG command, set Log Type to CMPLOG and Index Type to BYID, and
enter mfs:/DSPTRAU in Command Parameter. View the progress, and after the progress
reaches 100%, perform Step 4.
(5) After all the preceding steps are completed, search the path mbscbamversion_a or
version_b)ftpbtslogbtscmplog for compressed logs whose names are similar to the name of
the recording BTS.
(6) Run the RMV CALLRESRECORD command to delete all records.
RMV CALLRESRECORD: RECINDEX=0;
3.14 Performing PD Recording
（1）Start PD recording
Use the following MML command:
SET UMRECORDPARA: UMRECCMDCODE=STARTREC, SERVICETYPE=PS,
TRXID=1850, CHNO=3, RECDIR=BIDIR, RECLINECNT=ALLLINK, RECMAXTIME=5;
（2） Stop PD recording
SET UMRECORDPARA: UMRECCMDCODE=STOPREC, TRXID=1850;
（3） Collect record data to Flash
SET UMRECORDPARA: UMRECCMDCODE=STRULDRECDATA, TRXID=1850;

Level
（4） Stop collect record data to Flash
SET UMRECORDPARA: UMRECCMDCODE=STPULDRECDATA, TRXID=1850;
（5）Collect BTS log
STR BTSLOG: LOGTYPE=CMPLOG, IDTYPE=BYID, BTSID=18, SDATE=2011&07&15,
STIME=18&15&36, EDATE=2011&07&15, ETIME=18&15&38, BRDTYPE=GRRU,
BRDNO=1, SUBCMD="mfs:/DSPTRAU";
（6）Collect log file
After all the preceding steps are completed, search the path mbscbamversion_a or
version_b)ftpbtslogbtscmplog for compressed logs whose names are similar to the name of
the recording BTS.
(7) Run the RMV CALLRESRECORD command to delete all records.
RMV CALLRESRECORD: RECINDEX=0;
3.15 Performing TC Recording
Before performing a call test, specify parameters related to TC recording. The setting method is as
follows:
（1） Run the ADD CALLRESRECORD command to add a recording point. An input
window is displayed. Set the related parameters. Perform TC recording for both the
calling party and the called party.
ADD CALLRESRECORD: RECINDEX=0, USERIDTYPE=BYMSISDN,
MSISDN="13908881006", RECORDTYPE=TC; (calling party)

Level
ADD CALLRESRECORD: RECINDEX=1, USERIDTYPE=BYMSISDN,
MSISDN="13908881005", RECORDTYPE=TC; (called party)
Note:
All commands of the function are internal commands and are not described in the help document.
The value of RECINDEX ranges from 0 to 5. Each added recording point is identified by a
unique index.
USERIDTYPE includes four values, as described in the following table:
TMSI Temporary mobile subscriber identity
Indicates the TMSI of an MS.
Value range on the interface: 0–4294967295
Actual value range: 0–4294967295
Unit: none
Default value: none
Recommended value: none
IMSI International mobile subscriber identity Indicates the value of the IMSI.
Value range on the interface: none
Actual value range: 1–15 characters
Unit: none
Default value: none
MSISDN Mobile station international ISDN number Indicates the value of the MSISDN.
Unit: none
Default value: none

Level
IMEI International mobile equipment identity Indicates the value of the IMEI.
Unit: none
Default value: none
Note:
Because recording of up to four MSs can be performed simultaneously under the BSC, the value
of RECINDEX ranges from 0 to 3. If the message "The data to be added conflicts with the
existing data" is displayed when the command is executed, it indicates that the number of
recording MSs reaches the maximum value. In this case, you can run the following command to
delete the previous recording:
RMV CALLRESRECORD: RECINDEX=0; (Specify RECINDEX according to the actual
condition)
(2) Perform dialing tests and call tests. After all call tests are completed, extract the TC recording
file from the directory mbscbamcommonfamtc_file.<0
3.16 Performing Uplink Frequency Scanning
（1） On the BSC6900 LMT, right-click a tested cell and choose Configure Frequency Scan
from the shortcut menu.

Level
（2） Specify parameters in the Configure Frequency Scan window and click Start to perform
the test. Note:
The start time must be later than the current time; otherwise, the test cannot be performed.

Level
(3) After the configuration is successful, right-click the tested cell and choose Query Frequency
Scan from the shortcut menu. Then, choose the names of the tested site and cell. Note:
Open the Query Frequency Scan window immediately after the frequency configuration is
successful, and then wait for the query results; otherwise, the query results cannot be reported.

Level
(4) Observe the query results. After the results are reported, record the data of each frequency,
press Ctrl + A to select all, press Ctrl + C to copy the data, and paste the data to an excel file.
Note:
The reporting time is long and may take 5–6 minutes.

Level
3.17 Querying Forward Power and Reverse Power
3.17.1 Use MML Command to Query
Use the following MML command:
TST BTSPERF:IDTYPE=BYID,BTSID=140,TRXID=1148;
NOTE:This is a inner command and some BSC version don’t support.So if it don’t work,please
use customer message to query.
3.17.2 Use Customer Message to Query
（1） Test the idle timeslots of all TRXs in the cell and enable all TRXs to transmit signals at
full power.

Level
（2） By using the method described in section 2.1, open the Custom Message window and
send the following message:
D4-00-FF-FF-FF-81-00-FF-01-35
(3) Send the following custom messages according to TRX types:
(1) When the module type is Mrfu v1, send the following custom messages:
Common cell:
Forward power (before compensation):
D4-04-cell number-TRX number-FF-90-00-0c-87-TRX number-09-16-C4-00-F0-80-12-10-00-04
Forward power (after compensation):
Reverse power (before compensation):
Reverse power (after compensation):
D4-04-cell number-TRX number-FF-90-00-0c-87-TRX number-09-16-C4-00-F0-80-04-0a-00-04
(2) When the module type is Mrru 900m/1800m v1, send the following commands:
Common cell:
Forward power over channel A (after compensation):

Level
Forward power over channel B (after compensation):
D4-04-cell number-TRX number-FF-90-00-0c-87-TRX number-09-16-C4-00-F0-00-00-af-00-03
Reverse power over channel A (before compensation):
Reverse power over channel B (before compensation):
D4-04-cell number-TRX number-FF-90-00-0c-87-TRX number-09-16-C4-00-F0-00-00-b2-00-03
Reverse power over channel A (after compensation):
Reverse power over channel B (after compensation):
D4-04-cell number-TRX number-FF-90-00-0c-87-TRX number-09-16-C4-00-F0-00-00-b7-00-03
Co-cell:
Forward power over channel A (after compensation):
D4-04-cell number-TRX number-FF-91-00-0c-87-board number-09-16-C4-00-F0-00-00-31-00-03
Forward power over channel B (after compensation):
D4-04-cell number-TRX number-FF-91-00-0c-87-board number-09-16-C4-00-F0-00-00-af-00-03
Reverse power over channel A (before compensation):
Reverse power over channel B (before compensation):
D4-04-cell number-TRX number-FF-91-00-0c-87-board number-09-16-C4-00-F0-00-00-b2-00-03
Reverse power over channel A (after compensation):
Reverse power over channel B (after compensation):
D4-04-cell number-TRX number-FF-91-00-0c-87-board number-09-16-C4-00-F0-00-00-b7-00-03
(3) When the module type is Mrfu v2, send the following commands:
Common cell:
D4-04-cell number-TRX number-FF-90-00-0c-87-TRX number-09-16-C4-00-F0-00-8c-02-00-04
D4-04-cell number-TRX number-FF-90-00-0c-87-TRX number-09-16-C4-00-F0-00-8c-06-00-04

Level
D4-04-cell number-TRX number-FF-90-00-0c-87-TRX number-09-16-C4-00-F0-00-8c-0a-00-04
D4-04-cell number-TRX number-FF-90-00-0c-87-TRX number-09-16-C4-00-F0-00-8c-0e-00-04
Co-cell:
D4-04-cell number-TRX number-FF-91-00-0c-87-board number-09-16-C4-00-F0-00-8c-02-00-04
D4-04-cell number-TRX number-FF-91-00-0c-87-board number-09-16-C4-00-F0-00-8c-06-00-04
D4-04-cell number-TRX number-FF-91-00-0c-87-board number-09-16-C4-00-F0-00-8c-0a-00-04
D4-04-cell number-TRX number-FF-91-00-0c-87-board number-09-16-C4-00-F0-00-8c-0e-00-04
3.18 Querying the Interference Band
（1） Right-click a site and choose Monitor Channel Interference Band from the shortcut
menu.

Level
(2) Click Start to view the interference band and send a snapshot to R&D engineers.
3.19 Querying the GTMU A/B Board
Two methods for querying the GTMU A/B board are as follows:
（1） Query the hardware version in the running parameters of the board. Where, the
61 series indicates board A, and the 67 series indicates board B. As shown in

Level
the following figure, the query result indicates board B.
(2) Run the DSP BTSELABEL command to query the bar code of the TMU board.

Level
If the obtained bar code contains HNK, the GTMU A board is queried. If the obtained
bar code contains LPM, the GTMU B board is queried.
BarCode=030LPM4MA6222046 board B
BarCode=030HNK1083000149 board A
3.20 Querying the RRU V1/V2 Module
Two methods for querying the RRU V1/V2 module are as follows:
(1) Query the hardware version in the running parameters of the TRX. Where, C
indicates the V1 module and X indicates the V2 module.
for example,
Hardware version MRRU.HUAWEI.CS2420100

Level
Hardware version MRRU.HUAWEI.x4A120002
Note:◆
In special cases, the hardware version in the running parameters of the MRRU V1
1800M module is displayed as "x3…".
In conclusion, when the hardware version in the running parameters of the MRRU
module is displayed as "x3…", the MRRU module can be confirmed as a V1 1800M
module.
(2) Run the DSP BTSELABEL command to query the RRU V1/V2 module. If the
module version is V2, the following information in red is displayed. If the module
version is V1, no information is displayed.
Description=DBS3900,WD5MJRUAC8E,MRRU V2,Multi-mode Multi-carriers Remote Radio
3.21 Querying the RFU V1/V2 Module
Run the DSP BTSELABEL command to query the execution result. If the module
version is V2, the following information in red is displayed. If the module version is
V1, no information is displayed.
The electronic label of the V1 module is described as follows: BTS3900/A,WD5MMRFU88B,Multi-
Mode Transceiver Unit,900M RX890-915MHz/TX935-960MHz;
The electronic label of the V2 module is described as follows: BTS3900/A,WD5MMRFU78B,V2,
Multi-Mode Transceiver Unit,900M RX890-915MHz/TX935-960MHz;
3.22 Querying the Mapping Between Internal TRX Number and External TRX
Number
（1） Right-click a board on the BTS device panel and choose Query Board
Information from the shortcut menu to query the board number.

Level
（2） Run the LST GTRX command to query the external TRX number.
（3） Open the COM Redirection page by referring to section 2.2.
（4） Query the mapping between the internal TRX number and the external TRX
number and send the following command on the COM Redirection page:
iSend2TrxShell "RRM_vShowTrxBindInfo",0 (0 is the board number)
The printed results are as follows:

Level
Note:
ucTrxno indicates the external TRX number, and ucTrxIndex indicates the internal TRX number
3.23 Obtaining the Failure Log
（1） Run the STR BTSLOG command, set Board Type to TMU and Command
Parameter to CFLTLOG, , and wait for the execution of the command.
3.24 Obtaining the TMU Alarm Log
（1） Run the STR BTSLOG command. Set Board Type to TMU and Command
Parameter to ALMLOG, as shown in the following figure:

Level
(2) After the command is executed completely, click File Manager, choose a log file from
the directory bamversion_aftpbtsbtscmplog, and click Download.
3.25 Tracing the CBUS2 Message
（1） Open the Custom Message window by referring to section 2.1.
（2） Send D1-00-FF-FF-FF-87-02-FF in the Custom Message window.
Note:
If a time-out occurs, resend the message. Send the printed message in the window to R&D
engineers.

Level
3.26 Tracing the CBUS3 Message
（1） Open the Custom Message window by referring to section 2.1.
Send D1-00-FF-FF-FF-87-03-FF in the Custom Message window.
Note:
If a time-out occurs, resend the message. Send the printed message in the window to R&D
engineers.
3.27 Single User Resource Check
Run the DSP CALLRES command to query the TRX number, channel number, and
E1 timeslot number used by the tested MS.
The execution results are as follows:
Cell No.=3 ， Trx No.=3010 ， Ch No.=2.The preceding information indicates the
distributed cell index, TRX index, and channel number.

Level
SubRack No. =0 ， Slot No. =18 ， Port No. = 2 ， Ts No. =1.The preceding
information indicates the subrack number, slot number, port number, and timeslot
number of the E1 port.

Level
3.28 Querying Information About the BTS Port Timeslot Distribution
Run the LST BTSPORTTS command to query information about the BTS port
timeslot distribution, as shown in the following figure:
3.29 Querying Version NO. and Internal Version NO.
1> Querying Version NO.
In the panel of “BTS Device Panel”，Select the target TMU board or TRX board，right
click“Query Board Information”，appear the following picture, select“Basic Information”，you
can query the Version NO. in ”Software version”, For example:V100R012C00SPC039。

Level
2> Querying Internal Version NO.
In the panel of “BTS Device Panel”，Select the target TRX board，right click“Query Board
Information”， appear the following picture, select ”Running Parameters” ，you can query the
Internal Version NO. in ”Software version”, For example: 13.394.10.009.

Level
3.30 Obtaining CFG MML of single BTS
Execute the following MML command in “Batch” window:
exp btsmml:BTSIDLIST="0"; //“0”is BTSID
The output file is stored in the directory bamversion_aftpexport_cfgmml.
3.31 Obtaining Signaling
3.31.1 Tracing Signaling over the A Interface
You can trace the A interface BSSAP message, A interface MTP3 message, A

Level
interface MTP2 message, A interface SCCP message, A interface SCTP message, and
A interface M3UA message.
Click Trace on the LMT to open the Trace tab. In Trace Navigation Tree,
choose Trace > GSM Services and double-click A Interface Trace.In the A
Interface Trace dialog box, specify parameters on the Basic tab, then specify
parameters on the tab corresponding to the type of the signaling to be traced, and click
Submit. The traced message is displayed.
3.31.2 Tracing CS Signaling over the Um Interface
You can trace layer-3 signaling messages on the CS Um interface and trace the messages by
TRX and cell. You can trace the Um interface messages in up to 16 cells.
Click Trace on the LMT to open the Trace tab. In Trace Navigation Tree, choose Trace
> GSM Services and double-click Um Interface CS Trace. In the Um Interface CS Trace
dialog box, specify parameters and click Submit.The traced message is displayed.

Level
3.31.3 Tracing PS Signaling over the Um Interface
You can trace various PS Um interface messages, including the DUMMY message, system
message, dummy paging message, and data block message.
Click Trace on the LMT to open the Trace tab. In Trace Navigation Tree, choose Trace
> GSM Services and double-click Um Interface PS Trace.In the Um Interface PS Trace dialog
box, specify parameters and click Submit.The traced message is displayed.

Level
3.31.4 Tracing CS Signaling over the Abis Interface
You can trace various CS Abis interface signaling messages, including the Abis interface RSL
message, Abis interface ESL message, Abis interface EML message, Abis interface OML message,
and Abis interface LAPD message.

Level
Click Trace on the LMT to open the Trace tab. In Trace Navigation Tree, choose Trace >
GSM Services and double-click Abis Interface CS Trace. In the Abis Interface CS Trace
dialog box, specify parameters on the Basic tab, then specify parameters on the tab
corresponding to the type of the signaling to be traced, and click Submit. The traced
message is displayed.
(1) The following figures show the process of tracing OML messages:

Level
(2) The following figures show the process of tracing RSL messages:

Level
3.31.5 Tracing PS Signaling over the Abis Interface
You can trace PS Abis interface signaling messages and trace the messages by TRX and cell.
GSM Services and double-click Abis Interface PS Trace.In the Abis Interface PS Trace dialog
box, specify parameters and click Submit.The traced message is displayed.
3.31.6 Tracing CS Signaling of a Single User
You can trace the A/Abis/Um standard interface signaling messages of specified users. You
can use the IMSI, IMEI, TMSI, MSISDN, CELLID, or channel to specify the traced users. Single
user CS trace enables you to differentiate different user signaling by call number and locate
problems effectively. In the single user CS trace, you can choose CDT Mode to trace internal
signaling and locate signaling problems more accurately. You can trace the signaling of all single
users in up to 16 cells and differentiate the signaling of each user by call number.
GSM Services and double-click Single User CS Trace. In the Single User CS Trace dialog box,
specify parameters and click Submit.The traced message is displayed.

Level
If you set Trace Object Symbol Type to MSISDN, you must set MSISDN to the peer number.
(1) (Recommended) If the calling user is traced, MSISDN indicates the called number. For
example, if the user dials 12345, MSISDN must be set to 12345.
(2) If the called user is traced, MSISDN indicates the calling number. For example, if the
calling number displayed on the called MS is 54321, MSISDN must be set to 54321.
If you set Trace Object Symbol Type to TMSI or IMSI, you must confirm the reallocation
policy of the MSC as follows:
(1) If the MS initiates a TMSI call, the TMSI tracing function can be enabled.
(2) If the MS initiates an IMSI call, the IMSI tracing function can be enabled.
If you set Trace Object Symbol Type to IMEI, you must confirm whether the MSC has enabled
the function of obtaining the IMEI.
3.31.7 Tracing PS Signaling of a Single User
You can trace the Gb/Abis/Um standard interface messages of specified users and internal
messages or Um data blocks. You can use the IMSI or TLLI to specify the traced users.

Level
GSM Services and double-click Single User PS Trace. In the Single User PS Trace dialog box,
specify parameters and click Submit.The traced message is displayed.
You can choose Trace Um Datablock Message only when Trace Interface Type is set to
UM Interface. If you set Trace Object Symbol Type to IMSI, you must confirm the reallocation
policy of the MSC: If the MS initiates an IMSI call, the IMSI tracing function can be enabled.
If you set Trace Object Symbol Type to TLLI, you must first run the DSP MSCONTEXT
command to view the TLLI value of the MS that is in the PS service process. When the MS is in
the PS service process, the TLLI may be reallocated. In this case, you can continue the query to
obtain a new TLLI and continue the tracing.

Level
4 Performing Related Operations
4.1 Performing Loopback Tests
4.1.1 Performing Interface Board Port Timeslot Loopback
You can perform interface board port timeslot loopback on any one of the following boards:
GE(O)IUA, GE(O)IUB, GE(O)IUT, and GE(O)IUP. There are two loopback modes: remote
loopback and local loopback.
Remote loopback: The signal received in the timeslot is not processed but directly sent out in
the TX direction of the timeslot. During the loopback, the interface board still continues to receive
the signal sent in the timeslot.
Local loopback: The signal that needs to be sent in the timeslot is not sent out but directly
taken back in the RX direction of the timeslot. During the loopback, the interface board still
continues to receive the signal sent in the timeslot.
Abis interface board timeslot loopback is frequently used in voice troubleshooting. A
interface timeslot loopback can be replaced by external voice loopback.
The procedure for performing interface board port timeslot loopback is as follows:
(1) Click Device Maintenance, choose BSC Maintenance > Interface Board Port Timeslot
Loopback, and specify Subrack No. and Slot No.
(2) Click Query, select the timeslot number to be looped back, and click Start.

Level
Note:
During the Abis /Ater interface board timeslot loopback, you must set the loopback timeslot
correctly. You can calculate the E1 timeslot by using the timeslot queried in section 3.24 "Single
User Resource Check".
4.1.2 Performing BTS Voice Loopback
You can perform the BTS voice loopback test on a traffic channel to verify whether the voice
channel of the TRX from the air interface to the internal DBUS of the BTS is connected normally.
During the test, the TMU board loops back the DBUS timeslot corresponding to the tested voice
channel and the connection can be checked according to whether the users occupying the channel
can hear their own voices. If the users can hear their own voices, the connection is normal;
otherwise, the connection is abnormal.
After a voice problem such as noise occurs, a BTS voice loopback test can be performed. If
the users can hear noise, the voice problem may be located in the downlink direction of the Abis
interface; otherwise, the voice problem is located in the uplink direction of the Abis interface.
The procedure for performing BTS voice loopback is as follows:
(1) Click Device Maintenance, choose BTS Maintenance > Maintain TRX > Test Channel

Level
Loopback, specify Site, Cell, TRX No., and Channel, and set Test Project to BTS Voice Loop
Test.
(2) Read the three precautions in Description, specify Duration, and click Start to perform the
test.
Note:
You can set TRX No. and Channel to the TRX number and channel number queried in section
3.24 "Single User Resource Check".
4.1.3 Performing TRX Voice Loopback
You can perform the TRX voice loopback test on a traffic channel to verify whether the voice
channel of the TRX from the air interface to the codec of the baseband DSP is connected normally.
During the test, the baseband DSP directly encodes the decoded data of the traffic channel and
sends the data out, and the connection can be checked according to whether the users occupying
the channel can hear their own voices. If the users can hear their own voices, the loopback is
correct.

Level
After a voice problem, such as noise, occurs, a TRX voice loopback test can be performed. If
the users can hear noise, the voice problem may be located in the downlink direction of the DBUS
(and TRX); otherwise, the voice problem is located in the uplink direction of the TRX.
The procedure for performing TRX voice loopback is similar to the procedure for performing
BTS voice loopback. The procedure for performing TRX voice loopback is as follows:
(1) Click Device Maintenance, choose BTS Maintenance > Maintain TRX > Test Channel
Loopback, specify Site, Cell, TRX No., and Channel, and set Test Project to TRX Voice Loop
Test.
(2) Read the three precautions in Description, specify Duration, and click Start to perform the
test.
4.1.4 Performing BIU Loopback
You can perform the BIU loopback test on only idle channels. On the LMT, choose BTS
Maintenance > Maintain TRX > Test Channel Loopback and specify Site, Cell, TRX No., and
Channel. Set Test Project to BIU Loop Test. Click Start to perform the test. After the test is

Level
complete, the test results are returned.
Note:
You must perform BIU loopback on all channels of the target TRX, four times per channel.
The loopback test results are returned in a table. An example of the loopback test results is listed
as follows:
Loopback Mode/Test MS MS A at a Problem Site MS B at a Normal Site
Local Abis Interface
Loopback
Cannot hear A and B Can hear A and B
Remote Abis Interface
Loopback
Can hear A but cannot hear
B
Can hear A but cannot
hear B
BTS Loopback Can hear A and B Cannot hear A and B
TRX Loopback Cannot hear A but can hear
B
Cannot hear A but can
hear B
Note:
Prepare the table for recording test results before the test. To ensure the accuracy of test results,

Level
perform each loopback for at least four times.
4.2 Modifying the BTS Soft Parameters
Run the SET GCELLBTSSOFT command to modify the BTS software parameters. For
example,
SET GCELLBTSSOFT: IDTYPE=BYID, CELLID=112, ITEMINDEX=39, ITEMVALUE=254;
4.3 Reducing the Interference Band Software Parameters
No help or auxiliary information about modifying the software parameters of the cell can be
obtained from the Web LMT because the BSC hides the command for modifying the software
parameters of the cell. The procedure for modifying the interference band software parameters is
as follows:
1> Open the MML window.
2> Use 200K filter bandwidth to calculate the interference band of the MRFU V2. Run the
following command in the MML window or batch processing window:
SET GCELLBTSSOFT: IDTYPE=BYID, CELLID=Cell index value, ITEMINDEX=56,
ITEMVALUE=127;

Level
Note:
Bit 7 of software parameter 56 indicates that the 200K filter switch is used to calculate the
interference band of the MRFU V2. If bit 7 is set to 0, the switch is enabled. If bit 7 is set to
1, the switch is disabled. When the software parameter is used, you need to query the value of
the software parameter before setting the software parameter because each bit has its own
meaning. In this way, other function switches will not be affected when this function is
enabled.
LST GCELLBTSSOFT: IDTYPE=BYID, CELLID=Cell index value;
After the bit occupation of the software parameter is determined, set bit 7 to 0 to recalculate
the value of the software parameter.
If the queried value of software parameter 56 is 223, namely 0xDF (corresponding to the
binary code 11011111), bit 5 has been set to 0. In this case, the 200K filter bandwidth switch
BIT7 must be enabled, namely, bit 7 must be set to 0. Therefore, the recalculated value of
software parameter 56 is 0x5F, namely 95.
ITEMVALUE=95;
3> Select an interference band reporting combination algorithm (applicable to all modules
except MRRU V2):
ITEMVALUE=239;
Note:
Bit 5 and bit 4 of software parameter 59 indicate the interference band reporting combination
algorithm. When the two bits are set to 10, it means selecting the average value. When the
two bits are set to 01, it means selecting the minimum value. When the two bits are set to 00
or 01, it means selecting the maximum value. The default value is 11. The following table
shows the details.
BIT5 BIT4 Algorithm

Level
1 1 The maximum value of each antenna is used in
interference band reporting by default.
1 0 The average value of each antenna is used in interference
band reporting.
0 1 The minimum value of each antenna is used in
interference band reporting.
0 0 The maximum value of each antenna is used in
interference band reporting.
When the software parameter is used, you need to query the value of the software parameter
before setting the software parameter because each bit has its own meaning. In this way,
other function switches will not be affected when this function is enabled.
LST GCELLBTSSOFT: IDTYPE=BYID, CELLID=Cell index value;
After the bit occupation of the software parameter is determined, set bit 5 and bit 4 to the
corresponding value to recalculate the value of the software parameter.
[Example] The value of software parameter 59 queried above is 254, namely, 0xDF, and bit 5
is already 0. In this case, the average value must be used in interference band reporting,
namely, bit 5 and bit 4 must be set to 10. Therefore, the recalculated value of software
parameter 59 is 0xEE, namely, 238.
ITEMVALUE=238;
4> Set the interference band reduction factor (applicable to all modules except MRRU V2):
ITEMVALUE=255;
Bit 5 to bit 2 of software parameter 19 indicate a reduction factor. The value 1111 is the default
value and the factor is not used.
1010–1110 are invalid values and can be normalized to 1001, namely, reducing 9 dB. The
following table lists the possible parameter values:
BIT5 BIT4 BIT3 BIT2 Meaning
0 0 0 0 Reducing 0

Level
dB
0 0 0 1 Reducing 1
dB
0 0 1 0 Reducing 2
dB
0 0 1 1 Reducing 3
dB
0 1 0 0 Reducing 4
dB
0 1 0 1 Reducing 5
dB
0 1 1 0 Reducing 6
dB
0 1 1 1 Reducing 7
dB
1 0 0 0 Reducing 8
dB
1 0 0 1 Reducing 9
dB
1 0 1 0 Invalid
1 0 1 1 Invalid
1 1 0 0 Invalid
1 1 0 1 Invalid
1 1 1 0 Invalid
1 1 1 1 Invalid
【例1】 To reduce the interference band by 3 dB when bit 5 to bit 2 of software
parameter 19 are set to 0011, run the following command:
SET GCELLBTSSOFT: IDTYPE=BYID, CELLID=Cell index value,
ITEMINDEX=19, ITEMVALUE=204;
Note:
The following command for modifying the IF filter bandwidth affects the performance of the
service and is not recommended when being used to reduce the interference band.
5> Run the following command to modify level-1 filter bandwidth for the MRFU V1/MRRU

Level
V1:
ITEMVALUE=251;
Software parameter 91 is set to 255 by default. For the M series and D series, different bits
are used to configure the IF filter.
The method for configuring IF filters of M series and the meanings of bits are as follows
Bit 0 of software parameter 91 has other purposes. Bit 2 and bit 1 are used to configure the
coefficient of the IF filter.
The following table lists the meanings of bit 2 and bit 1.
BIT2-BIT1 00 01 10 11
Filter
bandwidth
260K 200K Reserved 260K
6> Run the following command to modify level-1 filter bandwidth for the DRRU/DRFU:
ITEMVALUE=239;
Bit 4 and bit 3 of software parameter 91 are used to configure the coefficient of the IF filter.
The following table lists the meanings of bit 4 and bit 3.
BIT4-BIT3 00 01 10 11
Filter
bandwidth
260K 200K Reserved 200K
Note:
1. When the IF filter coefficients of D series and M series are configured, use different bits of the
same software parameter.
The default values (10 and 11) in the IF filter coefficient configuration of D series and M series
are different. The default value of D series is 200K bandwidth, and the default value of M series is
260K bandwidth. The reserved value 10 cannot be configured.

Level

Guide to obtaining bts3900 information(v1.0.2)

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

En vedette

En vedette (20)

Similaire à Guide to obtaining bts3900 information(v1.0.2)

Similaire à Guide to obtaining bts3900 information(v1.0.2) (20)

Dernier

Dernier (20)

Guide to obtaining bts3900 information(v1.0.2)