BA list recordings (BAR) Recordings

BAR recordings should be performed during three to five consecutive working days. The BAR recording is activated by the: RNO interface (if available) BSC command interface To perform BAR recordings using the RNO interface: Log in to OSS. Start RNO. Go to File ->New Recording ->NCS. Name the recording session. Set the Relative SS Threshold to -12db. Set the Absolute SS Threshold to -80dbm. Set the BA List Change interval to 15 minutes. Set the number of test frequencies to add to each interval to 10. Enter a start date. Enter a repeat value (set to daily) and a number of repetitions (set to 5). Enter a date type, working days only (Monday to Friday five consecutive working days, for example). Enter an hour range (Four hours should be defined to include the network busy hour). Select the cell set or BSC (including every cell in the entire network). Set the Cell Filter to a desired (available) frequency band (The recorded cell set should be limited to a specified frequency band.) Select Frequencies. Create a Frequency Set for BAR recordings, including all frequencies used for BCCH in the desired band for the entire network. Save and schedule the recording.

Notes: In a dual band network, recordings should be made separately, based on the cell band. However, in order to provide full functionality of handover optimization, inter-band recordings should be performed. Each band cell set should record a frequency set with the BCCH frequencies for both bands. Multi Band Cells Reported (MBCR), is a cell parameter that defines the number of neighbors from each frequency band are reported in the measurement report. The recommended setting is either 2 or 3 in a multi-band network in order for mobiles to report measurements from the opposite band. While BAR files can also be generated with the Frequency Allocation Support (FAS), the Neighboring Cell Support (NCS) should be used if possible. The NCCPERM defines the allowed NCCs on the BCCH carriers for which the MSs are permitted to send measurement reports. Hence if all NCCs are used NCCPERM should be set accordingly (i.e., all NCCs included in the NCC parameter) so that all NCCs are reported. NCCPERM has no impact on idle mode behavior, since Idle mode cell reselection is based on CGI, and not ARFCN/BSIC). The Active BA list Recording result may sometimes contain measurement results with unexpected, disallowed BSICs, (e.g., 00 or 77). This occurs when some MSs report irrelevant BSICs initially, before decoding actual BSIC information and is not related to a fault in the BA List recordings feature. If an operator has not purchased the RNO application to activate BAR recordings through NCS, the BAR recordings can be activated by using the BSC command line interface, as follows: RABRE:RID=RARID00; Terminate an NCS recording. RABIE:RID=BARID00; Delete a recording. RABII; Initiate a new recording.

RABRP:RID=BARID00; Print a BAR recording status (optional). RABDC:RID=BARID00, CELL=ALL; All cells of a BSC are recorded. RABDC:RID=BARID00,TMBCCHNO=50&&124; Frequencies to measure 50 to 124.* RABDC:RID=BARID00,NUMFREQ=10; The number of test frequencies at each interval. RABDC:RID=BARID00,SEGTIME=15; The recording segment time in minutes. RABDC:RID=BARID00,RELSSN=12; Negative signal strength thresholds. RABDC:RID=BARID00,RELSS2P=0; Positive signal strength thresholds. RABDC:RID=BARID00, ABSS=80; Absolute signal strength (means negative dBm). RABDP:RID=BARID00; View recording properties. files for each BSC on FTP. If this is not done within 48 hours after the recording, it will be deleted from the system. Binary BARFILs files are located in the following OSS directories: R8: o /var/opt/ehpt/eac/data/fs/BSC_NAME/ R9/R10 and later with IOG20: o /root/var/opt/ericsson/nms_eam_eac/data/fs/BSC_NAME/ R9/R10 and later with APG40: o /root/var/opt/ericsson/brf/data/db/tmpfileStore/BSC_NAME/ Note: When BARFILs are transferred from UNIX to Windows via FTP, the binary transfer method should be used. All BARFILs recorded on the same day should be stored in the same directory. The Appendix contains instructions on troubleshooting situations in which BAR files are not created.