bsssts

User Description, BSS File Definitions - STS and Recording Functions

Copyright

©Ericsson AB 2001-2002, all rights reserved.

Disclaimer

The contents of this document are subject to revision without notice due to continued progress in methodology, design, and manufacturing. Ericsson shall have no liability for any error or damages of any kind resulting from the use of this document.

Trademark List

Contents

USER DESCRIPTION 79/1553-HSC 103 12/3 Uen B

1 Introduction 2

Glossary

2.1 Concepts 2.2 Abbreviations and acronyms 3

BSC Recording Functions

3.1 Definition of Files 3.2 File Removal Time 3.3 Main changes in Ericsson GSM System R9.1/BSS R9.1 4

STS - IOG

4.1 Introduction 4.2 Definition of STFIOPFILES 4.3 Subfile Collection Interval - Transmission of STS Files 4.4 FPU Removal Time 4.5 Main changes in Ericsson GSM System R9.1/BSS R9.1 5

STS on APG

5.1 Definition of STS files 5.2 Transmission of STS files 5.3 AFP Removal Time 5.4 Main changes in Ericsson GSM System R9.1/BSS R9.1 6

References

of 8User Description, BSS File Definitions - STS and Recording Functions

1/3/2013http://10.81.2.49/cgi-bin/alexserv?UZ=127.0.0.1:9229&ID=27439&DB=bssr10mdr2b.alx&...

http://www.pdfcomplete.com/cms/hppl/tabid/108/Default.aspx?r=q8b3uige22

1 Introduction

This document is presenting how to define the output files for STS and Recording functions in the IOG and APG in BSC.

The amount of resources, such as hard disk space, processing capacity and data link throughput, in IOG is limited. This is especially valid for IOG11, but also for IOG20. One of the problems is that the file definition parameter settings (in command INFII) stated in the current version of the Application Information for the BSC Recording Functions all together will result in too much hard disk memory allocation in the IOG EXCHVOLUME.

This document also includes information dimensioning and set up for STS .

For IOG this document will focus on the hard disk memory usage for the output files for the recording functions and for STS in the BSC, and give recommendations how to define the output files to appropriate number, size and expansion factor.

APG40 provides a more modern file system that does not require dimensioning of recording and STS output files. This document points to the operation procedures that are used for an APG equipped BSC.

2 Glossary

2.1 Concepts

2.2 Abbreviations and acronyms

Expansion factor

The expansion factor (EXP) specifies how many records a file will expand when the file is full.

Subfile Collection Interval

The subfile collection interval defines the length of time a subfile is active for storing of STS file output reports. After each interval the subfile is closed and the subfile is reported to FPU, and a new subfile is created.

AFP Adjunct Processor File Processing APG Adjunct Processor Group BAR BA-List Recording CER Channel Event Recording CTR Cell Traffic Recording FAS Frequency Allocation Support FOX Frequency Optimization eXpert




3 BSC Recording Functions

3.1 Definition of Files

3.1.1 Background

For IOG the properties of the files should reflect the expected usage of the files, and should be chosen carefully especially initial SIZE and EXPANSION factor. The output files from the BSC recording functions and from STS are allocated to one or several volumes. The size of each volume is limited, thus the sum of the occupied disk space from the included files have to be within the limit. The definitions of files are made by the command INFII.

For APG it is not possible to specify the initial size or expansion factors. It is only necessary to specify the record length.

3.1.2 Recommendation for IOG

The recommendations for defining files (command INFII [5]) are described in reference [3], however the following values are recommended:

FPU File Processing Utility NCS Neighbouring Cell Support NOX Neighbouring Cell Optimization Expert MRRMeasurement Result Recording MTR Mobile Traffic Recording PMR Performance Recording STS Statistics and Measurement Subsystem RIR Radio Interference Recording RNR Radio Network Recording

Table 1 Function # of files SIZE [no. of

records] EXP [no. of

records] Total size [Mbyte] Related OSS

App. MTR 64 50 150 3.2 + x*y*0.15 PMR (RNR) CTR 1 750 1500 0.8 + x*y*1.5 PMR (RNR)

CER (1) 16 1000 2000 16 + x*y*2 PMR (RNR) RIR 10 500 200 5 + x*y*0.2 FAS/FOX BAR 32 2000 600 16 + x*y*1 NCS /NOX MRR 10 1300 500 13 + x*y*0.5 MRR




NOTE (1) To avoid too frequent file expansion when using Cell Event Recording for very large cells the expansion factor may be assigned a greater value than 2000, see reference [7].

Explanations for the column Hard Disk Total Size:

x - number of active recordings (value range: 0 - max.) Max. number is the same as "# of files" for all recording functions, except for MTR where the maximum number of active recordings are 4.

y - number of file expansions

The record length is 512 bytes for all the Recording functions.

Two subfiles are created when the files are inserted into the infinite sequential table (command IOIFI). This is the reason to why , for example, minimum 16 Mbytes are needed for BAR recording and not 8 Mbytes that you get when you just multiply 32*2000*512.

3.1.3 Recommendation for APG

For APG it is not necessary to define the initial size or expansion factors. It is only necessary to create the recording files.

The record length is 512 bytes for all recording files.

The operation procedure about how to create the recording files is described in the cpfmkfile command description [13] .

3.2 File Removal Time

3.2.1 Background

On IOG the File processing Unit (FPU) provides functionality to automatically remove a file after transmission to the OSS

The FPU removal time (parameter REMOVE in Command INFCC) specifies how long time the subfile will remain on the IOG hard disk after the subfile has been reported to FPU.

On APG the Automatic File Processing utility provides similar functionality. The AFP removal time (parameter remove_delay) in commands AFPDEF and AFPCHD specifies how long time the subfile will remain on the APG hard disk after the subfile has been reported to AFP.

3.2.2 Recommendation for IOG

The recommendations for FPU removal time and other FPU conditions are described in reference [3], however 1 hour is recommended for the BSC recording functions.

3.2.3 Recommendation for APG

The recommendation for APG is to use 4 hour removal time.

3.3 Main changes in Ericsson GSM System R9.1/BSS R9.1




The APG 40 is introduced as IO processor . This gives possibility to store the recording files for a longer period to minimize risk of loosing recording data.

4 STS - IOG

4.1 Introduction

The STS User Guide [4] and the STS configuration Spreadsheet [2] present guidelines and recommendations how to set-up the STS file definitions on IOG. However, in this section some specific guidelines and recommendations, regarding the definition of STFIOPFILEs are given.

4.2 Definition of STFIOPFILES

4.2.1 Background

For every STS file report (command SDFOI) a file on the IOG Hard Disk have to be defined (command INFII). To avoid file expansion (which cause unnecessary processing load) the correct initial file size should be specified. The number of files and the initial size of the files are dependent on the included object types and the number of objects per object type for each file. Connection of Object Types to a STFIOPFILE is made by command (STFOI), and the number of objects per Object Type is dependent on the size of the BSC (for instance number of cells in the BSC).

4.2.2 How to estimate the initial size of STFIOPFILES

The occupied space on the hard disk for the STFIOPFILEs are not critical. In IOG11 the STFIOPFILEs together will result in (at maximum) 6 Mbytes and in IOG20 15 Mbytes. (The estimation is based upon that four parallel subfiles are assumed, 10 bytes per counter and max. no. of Counters in IOG11 is 120000 and in IOG20 300000). However, to avoid file expansion the exact size of the files must be calculated. By using the BSC STS Configuration Spreadsheet [2] the initial file size and the expansion factor will be calculated. The procedure is also described in the STS User Guide [4], but look like this:

1. Decide which object types that shall be included in each STFIOPFILE 2. Estimate the number of objects per object type (predicted value one year ahead) 3. Estimate the total number of counters per object type 4. Sum up all the counters for the file and calculate the size of the file.

The BSC STS Configuration Spreadsheet [2] will be useful in the steps 2, 3 and 4. By entering data (or using defaults) for step1 and 2, the number of records for each file will be calculated by the spreadsheet. The record length for the files is 2048 bytes.

If the correct initial size is defined, which implies that there will be no expansions of the file, the value of the expansion factor is not critical. However, to be safe the expansion factor must be set to a reasonable value, greater than zero but not greater than 100 records.

4.2.3 Recommendation

It is recommended to estimate the size of the STS output files (STFIOPFILES) by using the STS Configuration Spreadsheet [2]. The purpose of doing the calculation in advance is to avoid file expansions that cause unnecessary processor load.




The expansion factor must be set to a reasonable value. One way is to choose an arbitrary value, e.g. 25% of the initial file size. Another way is to set the expansion factor to the difference between the absolute maximum size of the file (i.e. when the number of objects for the included object types are set to their highest value) and the defined initial file size.

Regardless of method, the condition: "0 < expansion factor < 101" is recommended to be fulfilled.

4.3 Subfile Collection Interval - Transmission of STS Files

4.3.1 Background

The Subfile collection interval determines the duration when the subfiles are active. When the interval has ended the subfile is closed and reported to FPU. FPU will transmit the contents of the subfile to OSS. So, a short subfile collection interval will result in an earlier transfer to OSS. On the other hand we have to assure that the storing of the data into the subfile not will be interrupted by the closing of the subfile. This means that the subfile interval (for hourly measurements) will be in the range of 15 to 60 minutes.

For instance, if it is acceptable to delay the sending of the STS hourly file report by 30 minutes, the subfile collection period shall be set to 30 minutes (i.e. SDFSC: FILE=STFIOPFILEnn, INTM=30;). This means that the hourly STS file reports will be output every hour but with an "offset" of 30 minutes (e.g. 8.00 - 9.00 report will be output 9.30, 9.00 - 10.00 report will be output 10.30, and so on).


The recommendation is to set the subfile collection interval, for hourly reports, to 30 minutes if there are no requirements for an early transfer to OSS. If there are requirements to have an early transfer to OSS, 15-minute subfile collection interval should be chosen.

4.4 FPU Removal Time

4.4.1 Background

The FPU removal time (parameter REMOVE in Command INFCC) specifies how long time the subfile will remain on the IOG hard disk after the subfiles have been reported to FPU.


For STS reports the FPU removal time is recommended to be set to 2 hours.


-

5 STS on APG

5.1 Definition of STS files




5.1.1 Introduction

STS on APG provides new commands for initiation and administration of STS measurements. For more details read the STS user guide [12] .

When using APG it is not necessary to specify size or create the STS output files. This is done automatically by STS.

5.2 Transmission of STS files

5.2.1 Introduction

The STS files are transferred by usage of AFP. The files are available for transfer shortly after the end of the measurement report interval. The transfer can be initiated from the receiver or by the APG itself. The files are transferred by usage of FTP.

5.3 AFP Removal Time

5.3.1 Background

The AFP removal time (parameter remove_delay) in commands AFPDEF and AFPCHD specifies how long time the subfile will remain on the APG hard disk after the subfile has been reported to AFP


For STS reports the AFP removal time is recommended to be set to 4 hours. This too decrease the risk of loosing reports in case of failure and the possibility to store large amount of data on APG hard disk.


The APG 40 is introduced as IO processor . This gives possibility to store the STS files for a longer period to minimize risk of loosing statistics data.

6 References

1. 6/1553 APT 210 09 Uen. User Guide. STS Configuration Spreadsheet 2. 7/1553 APT 210 09 Uen. STS Configuration Spreadsheet 3. AXE-IOG11/IOG20 Setup 1/1531-41/AOM201 02 Uen 4. STATISTICS AND TRAFFIC MEASUREMENT SUBSYSTEM (STS) GUIDE 1553-ANT 227 02 Uen 5. Command INFII: IO Subsystem Functions File Administration, Initiate 6/190 82-CNZ 213

1010 Uen 6. Application Information, Block ROBAR 2/155 18-CNT 248 1086Uen 7. Application Information, Block ROCER 2/155 18-CNT 248 1062 Uen 8. Application Information, Block ROCTR 2/155 18-CNT 248 1089Uen 9. Application Information, Block ROMTR 2/155 18-CNT 248 1058 Uen

10. Application Information, Block ROMRR 2/155 18-CNT 248 1060 Uen 11. Application Information, Block RORIR 2/155 18-CNT 248 1054 Uen 12. User gide, Statistics and Measurement Administration on APG, 198 17-ANT 227 20/10 Uen




13. AP manual page, Central Processor File System, File, Create, 1/190 80-CNZ 217 3012 Uen 14. AP manual page, Adjunct procssor File Processing, File, Define, 1/19080-CNZ217 3013 Uen 15. AP manual page, Adjunct procssor File Processing, File, Change, 519080-CNZ217 3013 Uen




bsssts

Documents