GPEH

Administration

GPEH Administration

Events to be recorded are specified in scanners, also called performance

monitorings. The RNC provides 24 scanners (0-23) at node startup, all empty.

The RBS provides only one scanner at node startup. OSS-RC is used to specify

the contents and activate the scanners. Recording starts at the beginning of

the next 15-minutes Result Output Period (ROP) after activation from OSS-

RC. The recorded data from all active scanners is collected in a common data

file per Main Processor (MP).

All Subscription Profiles are persistently stored in the OSS-RC node to

ensure that user settings are not lost during planned or unplanned downtime.

There are two filter parameters in GPEH to be selected:

UE_Fraction

Cell Identity

ACTIVATING GPEH IN OSS-RC

GPEH Administration

It can be set to any value in the range 1-1000 and is the part per thousand of

the number of active Ues. Based on the value entered, an internal algorithm

selects which UEs events shall be recorded. If an event is not related to a

specific UE, the event will match and recorded anyway.

Mod (UE Context ID, 1000) 500 NO

Mod (1500,1000) =500 = 500 YES

Mod (1511,1000) =511 > 500 NO

UE_Fraction

GPEH Administration

The cell identity filter specifies in which cells in the RNC events shall be

recorded. Events which do not include any cell identifier, also known as

common events, will match the filter anyway and be reported.

This parameter is useful while filtering GPEH Events for specific cells

excluding some.

CELL IDENTITY

GPEH Administration

As long as the storage limit has not been rached, the files may be stored

indefinitely in the file system. A GPEH recording can be interrupted in

different error situations. An error situation is indicated with the Internal

Event INTERNAL_RECORDING_FAULT written to ROP file. The

recording resumes when the internal event

INTERNAL_RECORDING_RECOVERED is emerged. The following errors

may occur:

1. Partial Overload

2. Overload

3. File System Error

4. File Size Partially Exceeded

5. File Size Exceeded

6. Restart

GPEH ERROR SITUATIONS

GPEH Administration

GPEH scanners 22-23 are used for EBS-and they have higher priority than

other GPEH scanners in the RNC. In case the load exceeds a certain threshold

for partial overload, all scanners except EBS scanners stop recording events

from affected MPs. All other MPs continue to report events. This is acalled

partial overload and is indicated by writing the internal event

INTERNAL_RECORDING_FAULT to the sub-file on the affected MP with

the parameter:

EVENT_PARAM_EVENT_TRIGGER = EVENT_VALUE_PARTIAL_OVERLOAD

and the parameter:

EVENT_PARAM_AFFECTED_SCANNER_TYPE=EVENT_VALUE_LOW_PRIO

GPEH ERROR SITUATIONS:PARTIAL OVERLOAD

GPEH Administration

The error case Overload is similar to the Partial Overload. When the

measured load exceeds an even higher threshold it is considered as an

Overload. In this case also EBS scanners stops reporting events on the affected

MP, and the internal event INTERNAL_RECORDING_FAULT is written to sub-file on

the afftected MP with the parameter:

EVENT_PARAM_EVENT_TRIGGER=EVENT_VALUE_OVERLOAD

and the parameter:

EVENT_PARAM_AFFECTED_SCANNER_TYPE=EVENT_VALUE_HIGH_PRIO

GPEH ERROR SITUATIONS: OVERLOAD

GPEH Administration

If it is not possible to use the file system on some of the MPs due to some

serious fault, events cannot be written to sub-file on that MP and the file is

closed if possible. Event reporting and file writing continues on all other MPs.

The internal event INTERNAL_RECORDING_FAULT is written to sub-file on the

afftected MP with the parameter:

EVENT_PARAM_EVENT_TRIGGER=EVENT_VALUE_FILE_SYSTEM_ERROR

and the parameter:

EVENT_PARAM_AFFECTED_SCANNER_TYPE=EVENT_VALUE_HIGH_ALL

GPEH ERROR SITUATIONS: FILE SYSTEM ERROR

GPEH Administration

If it is not possible to use the file system on some of the MPs due to some

serious fault, events cannot be written to sub-file on that MP and the file is

closed if possible. Event reporting and file writing continues on all other MPs.

The internal event INTERNAL_RECORDING_FAULT is written to sub-file on the

afftected MP with the parameter:

EVENT_PARAM_EVENT_TRIGGER=EVENT_VALUE_FILE_SYSTEM_ERROR

and the parameter:

EVENT_PARAM_AFFECTED_SCANNER_TYPE=EVENT_VALUE_ALL

GPEH ERROR SITUATIONS: FILE SIZE PARTIALLY EXCEEDED

GPEH Administration

If the maximum file size is exceeded on an MP, reporting of events is

suspended for all GPEH scanners on that MP for the duration of the current

ROP. Recording continues on all other MPs. Recording resumes on the

affected MP with the next ROP. The internal event

INTERNAL_RECORD_FAULT is written to sub file on the affected MP with

the parameter

EVENT_PARAM_EVENT_TRIGGER=EVENT_VALUE_FILE_SIZE_EXCEEDED

and the parameter:

EVENT_PARAM_AFFECTED_SCANNER_TYPE=EVENT_VALUE_ALL

GPEH ERROR SITUATIONS: FILE SIZE EXCEEDED

GPEH Administration

If any MP or special purpose processor (SP) restarts, reporting of events is

suspended for all event-based scanners on the affected entity in the RNC.

Recording continues on all other MPs. Recording is resumed as soon as

possible after the MS/SP has fully recovered from the restart. The internal

event INTERNAL_RECORDING_FAULT is written to the sub file on the

affected MP with parameter:

EVENT_PARAM_EVENT_TRIGGER=EVENT_VALUE_RESTART

And also:

EVENT_PARAM_AFFECTED_SCANNER_TYPE=EVENT_VALUE_ALL

In case the O&M MP or the complete node restarts, all scanners are

suspended and scanner definitions are lost. In these cases, OSS-RC must re-

specify the scanner.

GPEH ERROR SITUATIONS: RESTART

GPEH Administration

In the GPEH recording, it is possible to define all events, all cells, and

all UEs for the same GPEH recording. However, in order to avoid

extensive CPU load and prevent large amount of unnecessary GPEH

data being recorded for each ROP, a filter containing limited number

of events and/or limited number of cells shall be applied to exactly

map particular recording need to prevent recording interruption due

to load or file size control.

DEFINING GPEH PROFILES IN OSS-RC

GPEH Administration

Step-1

GPEH RECORDING PROFILES CAN BE ACTIVATED FROM OSS-RC USING WCDMA-RAN MEASUREMENTS AS SHOWN.

GPEH Administration

Step-2

GPEH Administration

Step-3

GPEH Administration

Step-4

GPEH Administration

Step-5

DEFINITION OF PROFILE NAME AND COMMENTS FOR PROFILE DESCRIPTION.

GPEH Administration

Step-6

GPEH Administration

Step-7

ONLY ONE RNC CAN BE SELECTED FOR GPEH PROFILE. IF CELLS CONNECTED TO DIFFERENT RNCs ARE INVESTIGATED, A GPEH

RECORDING FOR EACH RNC INVOLVED HAS TO BE DEFINED. THE DATA

CAN BE COMBINED LATER.

GPEH Administration

Step-8

SELECTION OF CELLS FOR GPEH RECORDING:

GPEH Administration

Step-9

SELECTION OF EVENTS FOR RECORDING:

GPEH Administration

SELECTION OF UE-FRACTION: BY MEANS OF LOWER UE FRACTION, THE AMOUNT OF DATA TO BE RECORDED CAN BE REDUCED. FOR EXAMPLE

UE FRACTION SET TO 500 MEANS THAT THE EVENTS OF EVERY SECOND

ACTIVE UE ARE RECORDED.

GPEH Administration

SELECTION OF SCHEDULE TYPE.

USED WHEN RECORDING SHOULD BE STARTED AT THE NEXT POSSIBLE ROP. (RECORDING OUTPUT PERIOD=15-MIN INTERVAL)

GPEH Administration

ACTIVATION OF SCHEDULE TYPE SCHEDULED

For More Information

+90.232.2820265

support@innovile.com

info@innovile.com

Visit us at

www.innovile.com

Contact