Ericsson Counter : GPRS/EGPRS Traffic Load counters for the downlink per cell.


TRAFFDLGPRSSCAN Total number of scans (accumulations).

TBFDLGPRS Accumulated number of Basic and GPRS mode DL TBFs (active users), for all types of traffic, including effective streaming PDCH and PDCH used for EIT, in the cell.

TBFDLEGPRS Accumulated number of EGPRS mode DL TBFs (active users), for all types of traffic, including effective streaming PDCH and PDCH used for EIT, in the cell.

DLBPDCH Accumulated number of B-PDCH that carried one or more DL TBFs of any mode in the cell (a B-PDCH used on the DL). Valid for all types of traffic, including effective streaming PDCH and PDCH used for EIT.

DLGPDCH Accumulated number of G-PDCH that carried one or more DL TBFs of any mode in the cell (a G-PDCH used on the DL). Valid for all types of traffic, including effective streaming PDCH and PDCH used for EIT.

DLEPDCH Accumulated number of E-PDCH that carried one or more DL TBFs of any mode in the cell (an E-PDCH used on the DL). Valid for all types of traffic, including effective streaming PDCH and PDCH used for EIT.

DLTBFPBPDCH Accumulated number of simultaneous DL TBFs of any mode per used B-PDCH in the cell. Valid for all types of traffic, including effective streaming PDCH and PDCH used for EIT.

DLTBFPGPDCH Accumulated number of simultaneous DL TBFs of any mode per used G-PDCH in the cell. Valid for all types of traffic, including effective streaming PDCH and PDCH used for EIT.

DLTBFPEPDCH Accumulated number of simultaneous DL TBFs of any mode per used E-PDCH in the cell. Valid for all types of traffic, including effective streaming PDCH and PDCH
used for EIT. With Flexible Abis the counter values will be slightly higher.

DLACTBPDCH Accumulated number of B-PDCH that carried one or more DL active TBFs of any mode in the cell (an active B-PDCH on the DL). Valid for all types of traffic, including effective streaming PDCH and PDCH used for EIT.

DLACTGPDCH Accumulated number of G-PDCH that carried one or more active DL TBFs of any mode in the cell (an active G-PDCH on the DL). Valid for all types of traffic, including effective streaming PDCH and PDCH used for EIT.


DLACTEPDCH Accumulated number of E-PDCH that carried one or more active DL TBFs of any mode in the cell (an active E-PDCH on the DL). Valid for all types of traffic, including effective streaming PDCH and PDCH used for EIT.

Ericsson Counter : Hierarchical Cell Structure


HOTOHCS  : Number of handover attempts due to HCS.

LOCEVAL:  Accumulated number of locating evaluations.

BRHILAYER : Accumulated number of locating evaluations where HCS ranking differs from basic ranking.

TIMEHCSOUT : Accumulated time in seconds when the servings cells  channel availability is below or equal to HCSOUT. Please, note that the counter is only stepped it the feature HCS Traffic Distribution is active.

HOATTHR : Number of handover attempts at high handover rate.

HOSUCHR : Number of successful handovers at high handover rate

Ericsson Counter: handovers between underlaid and overlaid subcell


HOAATOL : Number of handover attempts from underlaid to overlaid subcell. The corresponding counter for handover to underlaid subcell is called HOAATUL.

HOSUCOL : Number of successful assignment attempts to overlaid subcell. The corresponding counter for underlaid subcell is called HOSUCUL.

HOATTULMAXIHO : Number of handover attempts from overlaid to underlaid subcell due to maximum number of intra-cell handovers in overlaid subcell.

HOSUCULMAXIHO : Number of successful handover attempts from overlaid to underlaid subcell due to maximum number of intra-cell handovers in overlaid subcell.

HOATTOLMAXIHO :  Number of handover attempts from underlaid to overlaid subcell due to maximum number of intra-cell handovers in underlaid subcell.

HOSUCOLMAXIHO :  Number of successful handover attempts from underlaid to overlaid subcell due to maximum number of intra-cell handovers in underlaid subcell.


EBS (Event Based Statistics)

The data in this database will act as a complement to the STS database but it is of more detailed character than the STS statistics. The data can either be stored in the database or in a Bulk Copy format file that can be distributed to other postprocessing tools. The monitors (counters) that can be stored must be activated in the GUI by the user, the user must have the correct authority to perform this action. The user must also select if the counters are to be collected for all cells in a specific BSC or several/all BSCs. The user can schedule the start and stop of data storage. The aggregation time, i.e. how often data is accumulated, can be decided by the user.
The data can later be postprocessed and reports can be created from monitors stored as counters by using the Business Objects tool. EBS and STS data can preferrably be combined into the same Business Objects report.
Note:  In order to combine STS and EBS data in the same report, it is important that the data is stored with the same periodicity




R-PMO (Realtime Performance MOnitoring)

R-PMO was the first application that was introduced in the family. Its main purpose is to present data in real-time. Realtime is achieved by letting the event data stream continuously to the OSS from the BSCs,and updating the OSS GUI once every minute.
The performance data that can be evaluated in real-time includes traffic load, service quality, hand over, GPRS/EGPRS cell reselection performance, GPRS/EGPRS data throughput and more. The measures are called Monitors.
The monitors are combined into reports. Several pre-defined Ericsson Standard Reports for both circuit switched and packet switched traffic performance monitoring are available. The user can also assemble monitors into own reports by using drag and drop.

A wide range of filters can be used on monitors, depending on the nature of the monitor. As an example the performance information for circuit switched traffic can be filtered per MS manufacturer and type, and the dropped calls can be filtered per drop reason.

FFAX (Find Faulty Antenna eXpert)

The purpose of FFAX is to provide an efficient way to remotely identify RF paths and antenna installations that are not performing according to expectations.
This is done by monitoring the difference in received signal strength from different RX paths in the BTS.

FFAX in OSS is applicable for the uplink and requires the BSS feature Find Faulty Antenna Data (FFAD). FFAX enables managing of cell sets to monitor, presentation of results in real-time and database storage functionality. For each reported TRX, key values are presented representing the accumulated receiver signal strength difference, during the measurement period, and when relevant an indication of the most likely fault or no fault found. The report will be updated every minute, and can be viewed in table as well as graph format (sliding window displaying data for the last hour). This is ideal during site visits where results of changes to the RF paths can be immediately seen in OSS.

BTS Fault Alarm

Types of Fault Map
Internal Class 1A
Internal to BTS, affecting MO, within MO
Internal Class 1B
Internal to BTS, affecting MO, within MO environment
Internal Class 2A
Internal to BTS, not affecting MO, within MO
External Class 1
External to BTS and affecting MO
External Class 2
External to BTS not affecting MO


The alarm slogan is the description of the current alarm situation for an MO or TG. The alarm slogans 'BTS INTERNAL' and 'BTS EXTERNAL' each describe more than one alarm situation. The remaining alarm slogans each describe a unique alarm situation. This section describes how each alarm slogan should be interpreted.
TGC FAULT No active TGC application exists in the Transceiver Group.
PERMANENT FAULT A managed object is classified as being permanently faulty when fault situations have occurred, and have been cleared, a certain number of times within a certain period of time. Manual intervention is required to bring such equipment back into operation.
LOCAL MODE The BTS equipment is in Local Mode or the BTS equipment has changed from Local to Remote Mode and a fault exists in the communication link between the BSC and the BTS. Communication between the BSC and the BTS is not possible.
LMT INTERVENTION Local maintenance activities are being performed in the BTS.
LOOP TEST FAILED Test of the traffic carrying capabilities of the TS has failed.
BTS INTERNAL There is a fault internal to the BTS.
MAINS FAILURE There is a fault in the power supply to the BTS or one or more items of equipment within the BTS. Battery backup (where available) is in use. Escalation may occur if corrective action is not taken.
BTS EXTERNAL There is a fault external to the BTS.
OML FAULT There is a fault in the communications link between the BSC and BTS.
ABIS PATH UNAVAIL No transmission device exists between the BSC and BTS.
CON QUEUE CONGESTION At least one of the LAPD Concentrator concentration outlet queues has reached an unacceptable filling level.
TS SYNC FAULT Synchronization lost on uplink or downlink TRA or PCU channels.
FORLOPP RELEASE A fault has occurred within the BSC software leading to a Forlopp release. Automatic recovery procedures are taking place. Report to your Ericsson Support Office. Alternatively, this alarm is issued as an advisory following a command ordered Forlopp release of a TG. In either case, the alarm is automatically ceased following successful recovery.
OPERATOR CONDITION A condition has arisen due to operator intervention
BSC
Base Station Controller
BTS
Base Transceiver Station
CF
Central Functions
CON
LAPD Concentrator
DP
Digital Path
IS
Interface Switch
LAPD
Link Access Protocol for the D channel
LMT
Local Maintenance Terminal
MO
Managed Object
OML
Operation and Maintenance Link
PCU
Packet Control Unit
RBS
Radio Base Station
RX
Receiver
TF
Timing Function
TG
Transceiver Group
TGC
Transceiver Group Controller
TRA
Transcoder Rate Adaptor
TRXC
Transceiver Controller
TS
Timeslot
TX
Transmitter