Sunteți pe pagina 1din 138

DESCRIPTION 104/1551-AXD 105 03/1 Uen G1

General Performance Event Handling

RNC
Copyright

© Ericsson AB 2008-2010. All rights reserved. No part of this document may be


reproduced in any form without the written permission of the copyright owner.

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 damage of any kind resulting from the use of this document.

Trademark List

All trademarks mentioned herein are the property of their respective owners. These
are shown in the document Trademark Information.

Contents
1 Introduction

2 Events
2.1 RNC-Internal Events
2.2 Inter-Node Events
2.2.1 RRC Events
2.2.2 NBAP Events
2.2.3 RANAP Events
2.2.4 RNSAP Events
2.2.5 PCAP Events
2.2.6 SABP Events

3 Event Parameters
3.1 Disconnection Codes
3.2 UeRc Identities

4 Data File
4.1 Structure
4.2 Records
4.2.1 Header
4.2.2 Recording
4.2.3 Protocol
4.2.4 Body
4.2.5 Link
4.2.6 Footer
4.2.7 Error

1 Introduction
This Description describes the General Performance Event Handling (GPEH) function
and events for the Radio Network Controller (RNC). The RNC can log different types
of events, see Section 2 for more details. The events are collected in GPEH data files,
see Section 4.

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 Operations
Support System Radio and Core (OSS-RC) is used to specify the contents and
activate the scanners. Recording starts at the beginning of the next 15-minute 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).

There are two filter parameters in GPEH to be selected, Ue_Fraction and Cell identity.
Ue_Fraction can be set to any value in the range 1–1000 and is the part per
thousand of the number of active User Equipments (UEs). Based on the specified
Ue_Fraction, an internal algorithm selects which UEs events shall be recorded. If an
event is not related to a specific UE, the event will match the Ue_Fraction filter
anyway and be reported. 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.

The parameter gpehFileSize determines the size of the GPEH files, see RncFunction.
Should the file reach its limit before the ROP has ended, no more events are
recorded in the part of the system corresponding to the full file. The scanner state is,
however, unaffected and reporting from other parts of the system continues. The
event reporting from the affected part of the system will resume with the next ROP.
For each MP, the RNC may store up to 180 files or a total of 100 MB. Once the
storage limit is reached, the oldest file will be removed from the file system.

As long as the storage limit has not been reached, 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 the ROP file. When the recording resumes the internal event
INTERNAL_RECORDING_RECOVERED is written to the ROP file. See Section 2.1 for
details of the internal events.

The following error cases may occur:

Partial Overload The scanners for Event Based Statistics (EBS) are
based on GPEH scanners - GPEH scanner 22 and 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 stops reporting events from the
affected MP. All other MPs continue to report events.
This is called 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. The definition of load here
also includes the file writing queue. An internal
algorithm takes into account both the CPU load and the
length of the file writing queue.
Note:
Event reporting does not negatively impact
traffic in neither a “Partial Overload” situation
nor an “Overload” situation.

Overload The error case Overload is similar to the


case Partial Overload. When the measured
load exceeds an even higher threshold it is
considered as Overload. As a result also
the EBS scanners stops reporting events
on the affected MP, and the internal event
INTERNAL_RECORDING_FAULT is written
to the sub file on the affected MP with the
parameter
EVENT_PARAM_EVENT_TRIGGER =
EVENT_VALUE_OVERLOAD and the
parameter
EVENT_PARAM_AFFECTED_SCANNER_TYPE
= EVENT_VALUE_HIGH_PRIO.

File If it is not possible to use the file system


System on some of the MPs due to some serious
Error fault, events can not be written to the sub
file on that MP and (if it is possible) the file
is closed. Event reporting and file writing
continues on all other MPs.

If it is possible the internal event


INTERNAL_RECORDING_FAULT is written
to the sub file on the affected MP with the
parameter
EVENT_PARAM_EVENT_TRIGGER =
EVENT_VALUE_FILE_SYSTEM_ERROR and
the parameter
EVENT_PARAM_AFFECTED_SCANNER_TYPE
= EVENT_VALUE_ALL. The event
INTERNAL_RECORDING_RECOVERED is
always written when the error situation
ceases, regardless if the event
INTERNAL_RECORDING_FAULT was
written or not.
File Size The parameter highPrioScanReserve
Partially determines the percentage of the GPEH
Exceede files that, together with the parameter
d gpehFileSize, is reserved for high-
prioritized events. Only events from EBS
scanners are written to the file when the
following limit is reached: gpehFileSize –
(highPrioScanReserve/100) * gpehFileSize,
and the internal event
INTERNAL_RECORDING_FAULT is written
to the sub file on the affected MP with the
parameter
EVENT_PARAM_EVENT_TRIGGER =
EVENT_VALUE_FILE_SIZE_PARTIAL_EXCE
EDED and the parameter
EVENT_PARAM_AFFECTED_SCANNER_TYPE
= EVENT_VALUE_LOW_PRIO. Recording
continues on all other MPs. Recording of
events from the affected scanners resumes
on the affected MP with the next ROP.

File Size If the maximum file size is exceeded on an


Exceede MP, reporting of events is suspended for all
d 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_RECORDING_FAULT is written
to the 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.

Restart 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 the possible after the
MP/SP has fully recovered from the restart.
The internal event
INTERNAL_RECORDING_FAULT is written
to the sub file on the affected MP with the
parameter
EVENT_PARAM_EVENT_TRIGGER =
EVENT_VALUE_RESTART and the
parameter
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

2 Events
This section describes the GPEH events. The events are grouped according to the
following:

 RNC-internal events
 Inter-node events

Each section below describes the events that belong to a specific area. Information
about the events is presented in tables.

2.1 RNC-Internal Events

This section describes the RNC-internal events. RNC-internal events are generated
internally in the RNC at specific trigger conditions for each event.

Details of the RNC-internal events are provided in Table 1.

Table 1 RNC-Internal Event Details

Event ID Event Name


384 INTERNAL_IMSI Captured
an intern
385 INTERNAL_RADIO_QUALITY_MEASUREMENTS_UEH Captured
report is
Handling

The para
EVENT_V
EVENT_V
apply to
EVENT_P
event.
386 INTERNAL_RADIO_QUALITY_MEASUREMENTS_RNH Captured
report is
Network

The para
EVENT_V
EVENT_V
EVENT_V
EVENT_V
(5) apply
EVENT_P
event.
387 INTERNAL_CHANNEL_SWITCHING Captured

388 INTERNAL_UL_OUTER_LOOP_POWER_CONTROL Captured


for param
EVENT_P

389 INTERNAL_DL_POWER_MONITOR_UPDATE Captured


for param
EVENT_P

390 INTERNAL_CELL_LOAD_MONITOR_UPDATE Captured


for param
EVENT_P

Value of
TOTAL_D
for this e
EVENT_V
391 INTERNAL_ADMISSION_CONTROL_RESPONSE Captured
function

392 INTERNAL_CONGESTION_CONTROL_CHANNEL_SWITCH_AND_TERMINATE_RC Captured


function
terminat

393 INTERNAL_START_CONGESTION Captured


or uplink
threshold

Either of
EVENT_P
EVENT_P
measure
EVENT_P
measure
downlink
as an inv
EVENT_P
measure
congestio
invalid va
394 INTERNAL_STOP_CONGESTION Captured
or uplink
respectiv

Either of
EVENT_P
EVENT_P
measure
EVENT_P
measure
congestio
invalid va
EVENT_P
measure
395 INTERNAL_DOWNLINK_CHANNELIZATION_CODE_ALLOCATION Captured
for param
EVENT_P
event sh
that is ch

397 INTERNAL_IRAT_HO_CC_REPORT_RECEPTION Triggered


from a U

398 INTERNAL_IRAT_HO_CC_EVALUATION Evaluatio


Measurem
event 3a

If no intr
handove
Inter Rad
Handove
evaluate
EVENT_P
EVENT_P
the hand
value wil

399 INTERNAL_IRAT_HO_CC_EXECUTION Decision


GSM cell
400 INTERNAL_IRAT_CELL_CHANGE_DISCARDED_DATA Triggered
event RA
required
401 INTERNAL_CMODE_ACTIVATE Compres
the Comp

402 INTERNAL_CMODE_DEACTIVATE Compres


Compres

403 INTERNAL_RRC_ERROR Captured


the param

404 INTERNAL_NBAP_ERROR Captured


the param

405 INTERNAL_RANAP_ERROR Captured


the param

406 INTERNAL_SOFT_HANDOVER_REPORT_RECEPTION Captured


received

407 INTERNAL_SOFT_HANDOVER_EVALUATION Evaluatio


measure
event 1x

408 INTERNAL_SOFT_HANDOVER_EXECUTION Action fro


410 INTERNAL_MEASUREMENT_HANDLING_EVALUATION Evaluatio
measure
event 2x

413 INTERNAL_RNSAP_ERROR Captured


the param

414 INTERNAL_RC_SUPERVISION This even


Connecti
is reporte
UEs whe
Furtherm
for the se
connectio
as when

Note 1: W
may be u
non-HS R
one GPEH
both algo

414 INTERNAL_RC_SUPERVISION - continued Note 2: A


supervisi
GPEH ev
OVERALL
though th
signalling
Core Net

Note 3: T
logical er
itself but
monitor R
Note 4: T
logical er
itself, bu
monitor R
415 INTERNAL_RAB_ESTABLISHMENT A RAB ES
"RABs to
(stating a

Note: for
EVENT_P
EVENT_V
RAB Esta
target Ue

415 - Continue INTERNAL_RAB_ESTABLISHMENT - Continue

416 INTERNAL_RAB_RELEASE Either RA


with "RA
COMMAN
establish
both CNs

Note: Th
when at
a signalli

417 INTERNAL_UE_MOVE Sent whe


context,
UE deleti
418 INTERNAL_UPLINK_SCRAMBLING_CODE_ALLOCATION Sent at r
scramblin

419 INTERNAL_MEASUREMENT_HANDLING_EXECUTION Sent to s


measure

420 INTERNAL_IFHO_REPORT_RECEPTION This even


RRC even

Note: Th
be report
not avail

421 INTERNAL_IFHO_EVALUATION This even


event 2b

Note: Th
be report
not avail
422 INTERNAL_IFHO_EXECUTION This even
frequenc

423 INTERNAL_IFHO_EXECUTION_ACTIVE This even


Frequenc

425 INTERNAL_MP_OVERLOAD This even


capacity
426 INTERNAL_RBS_HW_MONITOR_UPDATE This even
RBS hard
control, o
released

427 INTERNAL_SOHO_DS_MISSING_NEIGHBOUR This even


measure
where th
neighbor
The para
to the be
identity p
ranking o

The para
refers to
cell in th
RNC iden
any rank

428 INTERNAL_SOHO_DS_UNMONITORED_NEIGHBOUR Captured


where th
neighbor
set.

429 INTERNAL_UE_POSITIONING_QOS Captured


performe
is sent to
429 Continued INTERNAL_UE_POSITIONING_QOS Continued

429 Continued INTERNAL_UE_POSITIONING_QOS Continued


429 Continued INTERNAL_UE_POSITIONING_QOS Continued

429 Continued INTERNAL_UE_POSITIONING_QOS Continued


429 Continued INTERNAL_UE_POSITIONING_QOS Continued

430 INTERNAL_UE_POSITIONING_UNSUCC Captured


another m

431 INTERNAL_SYSTEM_BLOCK Captured


indicates
rejected.
432 INTERNAL_SUCCESSFUL_HSDSCH_CELL_CHANGE Captured
Channel
Speed Do
cell chan

433 INTERNAL_FAILED_HSDSCH_CELL_CHANGE Captured


DSCH ce
434 INTERNAL_SUCCESSFUL_HSDSCH_CELL_SELECTION_OLD_ACTIVE_SET Captured
a new ce
set.

435 INTERNAL_SUCCESSFUL_HSDSCH_CELL_SELECTION_NEW_ACTIVE_SET Captured


a new ce
handove

436 INTERNAL_HSDSCH_CELL_SELECTION_NO_CELL_SELECTED Captured


no new c
both nor

437 INTERNAL_TWO_NON_USED_FREQ_EXCEEDED Captured


exists on
frequenc
(IEF) Mo
EVENT_P
Downlink
Ec/No fo
Ec/No is
Otherwis
consideri
437 INTERNAL_TWO_NON_USED_FREQ_EXCEEDED - continued EVENT_P
Downlink
active se
measure
to the be
as measu

EVENT_P
Downlink
active se
measure
to the be
as measu

EVENT_P
CPICH Ec
provided
quality. O
best cell
measure
437 INTERNAL_TWO_NON_USED_FREQ_EXCEEDED - continued EVENT_P
cell in ac
as the m
relates to
is used a
softer ha
connectio
CELL_DC
event, no

EVENT_P
second b
RSCP is u
Otherwis
consideri
quality.
437 INTERNAL_TWO_NON_USED_FREQ_EXCEEDED - continued EVENT_P
best cell
used as t
value rel
Ec/No is

EVENT_P
best cell
used as t
value rel
Ec/No is
438 INTERNAL_SYSTEM_RELEASE Captured
stand-alo
the relea

EVENT_P
cell in th
paramete
order.

Note: Mo
specific b
sure to c
Section 3

438 INTERNAL_SYSTEM_RELEASE - continued

438 INTERNAL_SYSTEM_RELEASE - continued


439 INTERNAL_CNHHO_EXECUTION_ACTIVE Captured
performe

440 INTERNAL_PS_RELEASE_DUE_TO_CNHHO Captured


been rele
Handove

441 INTERNAL_PACKET_DEDICATED_THROUGHPUT The even


reports t
RB's on t
RB on th
multiplex
interactiv
transport
is, no rep
FACH/RA
same ord
that it is
442 INTERNAL_SUCCESSFUL_TRANSITION_TO_DCH The even
Reconfig
UE, durin
connectio
Channel/
(E-DCH/
capabiliti
connectio

443 INTERNAL_FAILED_TRANSITION_TO_DCH The even


complete
Enhanced
Downlink
or DCH/H
Channel

444 INTERNAL_RECORDING_FAULT Captured


impacts t
the RNC.

The para
EVENT_P
as invalid
445 INTERNAL_RECORDING_RECOVERED Captured
recovere
RNC.

The para
EVENT_P
as invalid
446 INTERNAL_PACKET_DEDICATED_THROUGHPUT_STREAMING When ac
seconds)
UL/DL th
measure
DSCH sta

447 INTERNAL_MBMS_SESSION_START_FAILED Unsucces


(MTCH) i

448 INTERNAL_MBMS_SESSION_START_SUCCESS Successf


in a cell.

449 INTERNAL_MBMS_SESSION_STOP_SYSTEM Release o


trigger is

450 INTERNAL_MBMS_SESSION_STOP_NORMAL The MBM


message

451 INTERNAL_SYSTEM_UTILIZATION Expiry of


451_Continued INTERNAL_SYSTEM_UTILIZATION Continued

452 INTERNAL_PCAP_ERROR The even


signalling
procedur
error.
453 INTERNAL_CBS_MESSAGE_ORDER_DISCARDED The even
Message
internal c
generate
several S
454 INTERNAL_PACKET_DEDICATED_THROUGHPUT_CONV_UNKNOWN The even
reports t
throughp
data mea
CELL_HS

455 INTERNAL_PACKET_DEDICATED_THROUGHPUT_CONV_SPEECH The even


reports t
throughp
measure
DSCH sta

456 INTERNAL_CALL_SETUP_FAIL The even


attempt
Assignme
setup or
connectio
normal r
detected
Connecti
Transfer
Assignme
setup or
458 INTERNAL_OUT_HARD_HANDOVER_FAILURE The even
case betw
Handove
Execution
–> Term

458 Continued INTERNAL_OUT_HARD_HANDOVER_FAILURE Continued


459 INTERNAL_RES_CPICH_ECNO The even
on RES m
it shall b

459 Continued INTERNAL_RES_CPICH_ECNO Continued

459 Continued INTERNAL_RES_CPICH_ECNO Continued


475 INTERNAL_OUT_HARD_HANDOVER_SUCCESS The even
case betw
Handove
Execution
-> Termi

475 Continued INTERNAL_OUT_HARD_HANDOVER_SUCCESS Continued

(1) The following parameters are common to all events:

 EVENT_PARAM_SCANNER_ID
 EVENT_PARAM_TIMESTAMP_HOUR
 EVENT_PARAM_TIMESTAMP_MINUTE
 EVENT_PARAM_TIMESTAMP_SECOND
 EVENT_PARAM_TIMESTAMP_MILLISEC
 EVENT_PARAM_EVENT_ID
 EVENT_PARAM_UE_CONTEXT
 EVENT_PARAM_RNC_MODULE_ID
 EVENT_PARAM_C_ID_1
 EVENT_PARAM_RNC_ID_1
 EVENT_PARAM_C_ID_2
 EVENT_PARAM_RNC_ID_2
 EVENT_PARAM_C_ID_3
 EVENT_PARAM_RNC_ID_3
 EVENT_PARAM_C_ID_4
 EVENT_PARAM_RNC_ID_4

2.2 Inter-Node Events

This section describes the inter-node events that the RNC can record in GPEH. Inter-
node events are Layer 3 protocol messages as specified by 3rd Generation
Partnership Project (3GPP). Only the protocol messages described below are
supported by the GPEH function. The recorded inter-node events hold only the
information specified in this section. The inter-node events can be recorded with
either header data only, or with the entire message content as received on the RNC
external protocol interfaces.

The parameter gpehDataLevel determines which level of information to record, see


RncFunction. The default setting of the parameter is 0 = 'HEADER_DATA_ONLY'. The
default setting causes less information to be recorded in GPEH - information that can
be used for high-level troubleshooting, such as verifying that all the expected
messages have occurred at the correct times, or checking for failure messages for
procedures. The parameter may be changed from the default setting if more data is
required for more detailed troubleshooting.

The setting of the parameter to 1 = 'ALL_DATA' should be done carefully. The


increased amount of recorded data with this setting will slightly increase the load in
the RNC, and the ROP files will be filled faster. They might become full before the
ROP period ends and subsequent event data will be lost. With a file size of 5 MB, and
with extensive number of external events selected in the recording, it is
recommended to limit the Ue_Fraction to less than 50, and limit the number of
supervised cells to less than 10% of the maximum number of cells supported by the
current RNC configuration.

Note:
The current setting of the parameter gpehDataLevel affects all ongoing GPEH
scanners. Changing the parameter setting takes effect at the beginning of the
next ROP period. The parameter can only be changed by an administrator in
OSS-RC.

The inter-node events are grouped according to the following protocols:

 Radio Resource Control (RRC)


 Node B Application Part (NBAP)
 Radio Access Network Application Part (RANAP)
 Radio Network Subsystem (RNS) Application Part (RNSAP)
 Positioning Calculation Application Part (PCAP)
 Service Area Broadcast Protocol (SABP)
The following parameters are common to all inter-node events:

 EVENT_PARAM_SCANNER_ID
 EVENT_PARAM_TIMESTAMP_HOUR
 EVENT_PARAM_TIMESTAMP_MINUTE
 EVENT_PARAM_TIMESTAMP_SECOND
 EVENT_PARAM_TIMESTAMP_MILLISEC
 EVENT_PARAM_EVENT_ID
 EVENT_PARAM_UE_CONTEXT
 EVENT_PARAM_RNC_MODULE_ID
 EVENT_PARAM_C_ID_1
 EVENT_PARAM_RNC_ID_1
 EVENT_PARAM_C_ID_2
 EVENT_PARAM_RNC_ID_2
 EVENT_PARAM_C_ID_3
 EVENT_PARAM_RNC_ID_3
 EVENT_PARAM_C_ID_4
 EVENT_PARAM_RNC_ID_4
 EVENT_PARAM_PDU_TYPE (only applicable to RRC events,
otherwise reported as invalid)
 EVENT_PARAM_PROTOCOL_ID
 EVENT_PARAM_MESSAGE_DIRECTION
 EVENT_PARAM_MESSAGE_LENGTH
 EVENT_PARAM_MESSAGE_CONTENTS

The first 18 parameters are always reported for all events. The
parameter EVENT_PARAM_MESSAGE_CONTENTS, which provides the
entire message content, is optional to all events and is decided by the
parameter gpehDataLevel. The parameter
EVENT_PARAM_MESSAGE_LENGTH gives the length in bytes of the
ASN.1 coded message given in EVENT_PARAM_MESSAGE_CONTENTS.

2.2.1 RRC Events

This section describes the RRC events, specified in the standard 3GPP
TS 25.331.

Available RRC events are provided in Table 2.

Table 2 RRC Event Details

Event Event Name Comments


Id
0 RRC_ACTIVE_SET_UPDATE
1 RRC_ACTIVE_SET_UPDATE_COMPLETE
Reported as “Not App
2 RRC_ACTIVE_SET_UPDATE_FAILURE for this event
3 RRC_CELL_UPDATE
4 RRC_CELL_UPDATE_CONFIRM
5 RRC_DOWNLINK_DIRECT_TRANSFER
6 RRC_MEASUREMENT_CONTROL
7 RRC_MEASUREMENT_CONTROL_FAILURE
If the Radio Environm
Statistics function is
there will be
RRC_MEASUREMENT
events generates per
The periodicity is con
between 2 and 64 se
The default periodicit
8 RRC_MEASUREMENT_REPORT seconds.
9 RRC_PAGING_TYPE_2
10 RRC_RADIO_BEARER_RECONFIGURATION
11 RRC_RADIO_BEARER_RECONFIGURATION_COMPLETE
12 RRC_RADIO_BEARER_RECONFIGURATION_FAILURE
13 RRC_RADIO_BEARER_RELEASE
14 RRC_RADIO_BEARER_RELEASE_COMPLETE
15 RRC_RADIO_BEARER_RELEASE_FAILURE
16 RRC_RADIO_BEARER_SETUP
17 RRC_RADIO_BEARER_SETUP_COMPLETE
18 RRC_RADIO_BEARER_SETUP_FAILURE
19 RRC_RRC_CONNECTION_RELEASE
20 RRC_RRC_CONNECTION_RELEASE_COMPLETE
21 RRC_RRC_STATUS
22 RRC_SECURITY_MODE_COMMAND
23 RRC_SECURITY_MODE_COMPLETE
24 RRC_SECURITY_MODE_FAILURE
25 RRC_SIGNALLING_CONNECTION_RELEASE
26 RRC_SIGNALLING_CONNECTION_RELEASE_INDICATION
27 RRC_UE_CAPABILITY_INFORMATION
28 RRC_UE_CAPABILITY_INFORMATION_CONFIRM
29 RRC_UPLINK_DIRECT_TRANSFER
30 RRC_UTRAN_MOBILITY_INFORMATION_CONFIRM
31 RRC_INITIAL_DIRECT_TRANSFER
33 RRC_RRC_CONNECTION_REJECT
34 RRC_RRC_CONNECTION_REQUEST
35 RRC_RRC_CONNECTION_SETUP
36 RRC_RRC_CONNECTION_SETUP_COMPLETE
37 RRC_SYSTEM_INFORMATION_CHANGE_INDICATION The
EVENT_PARAM_C_ID
and
EVENT_PARAM_RNC_
parameters are repor
“Not Applicable”.
38 RRC_HANDOVER_FROM_UTRAN_COMMAND
39 RRC_HANDOVER_FROM_UTRAN_FAILURE
40 RRC_PHYSICAL_CHANNEL_RECONFIGURATION
41 RRC_PHYSICAL_CHANNEL_RECONFIGURATION_COMPLETE
42 RRC_PHYSICAL_CHANNEL_RECONFIGURATION_FAILURE
43 RRC_UTRAN_MOBILITY_INFORMATION
44 RRC_UTRAN_MOBILITY_INFORMATION_FAILURE
45 RRC_CELL_CHANGE_ORDER_FROM_UTRAN
46 RRC_CELL_CHANGE_ORDER_FROM_UTRAN_FAILURE
47 RRC_UE_CAPABILITY_ENQUIRY
48 RRC_URA_UPDATE
49 RRC_URA_UPDATE_CONFIRM
50 RRC_TRANSPORT_CHANNEL_RECONFIGURATION
51 RRC_TRANSPORT_CHANNEL_RECONFIGURATION_COMPLETE
52 RRC_MBMS_GENERAL_INFORMATION
53 RRC_MBMS_MODIFIED_SERVICES_INFORMATION
54 RRC_MBMS_UNMODIFIED_SERVICES_INFORMATION
55 RRC_MBMS_COMMON_P_T_M_RB_INFORMATION
56 RRC_MBMS_CURRENT_CELL_P_T_M_RB_INFORMATION
57 RRC_MBMS_NEIGHBOURING_CELL_P_T_M_RB_INFORMATION

2.2.2 NBAP Events

This section describes the NBAP events. The NBAP events are specified
by the standard 3GPP TS 25.433.

Available NBAP events are provided in Table 3.

Table 3 NBAP Event Details

Event Event Name Comment


Id
128 NBAP_RADIO_LINK_SETUP_REQUEST
129 NBAP_RADIO_LINK_SETUP_RESPONSE
130 NBAP_RADIO_LINK_SETUP_FAILURE
131 NBAP_RADIO_LINK_ADDITION_REQUEST
132 NBAP_RADIO_LINK_ADDITION_RESPONSE
133 NBAP_RADIO_LINK_ADDITION_FAILURE
134 NBAP_RADIO_LINK_RECONFIGURATION_PREPARE
135 NBAP_RADIO_LINK_RECONFIGURATION_READY
136 NBAP_RADIO_LINK_RECONFIGURATION_FAILURE
137 NBAP_RADIO_LINK_RECONFIGURATION_COMMIT
138 NBAP_RADIO_LINK_RECONFIGURATION_CANCEL
139 NBAP_RADIO_LINK_DELETION_REQUEST
140 NBAP_RADIO_LINK_DELETION_RESPONSE
141 NBAP_DL_POWER_CONTROL_REQUEST
142 NBAP_DEDICATED_MEASUREMENT_INITIATION_REQUEST
143 NBAP_DEDICATED_MEASUREMENT_INITIATION_RESPONSE
144 NBAP_DEDICATED_MEASUREMENT_INITIATION_FAILURE
145 NBAP_DEDICATED_MEASUREMENT_REPORT
146 NBAP_DEDICATED_MEASUREMENT_TERMINATION_REQUEST
147 NBAP_DEDICATED_MEASUREMENT_FAILURE_INDICATION
148 NBAP_RADIO_LINK_FAILURE_INDICATION
149 NBAP_RADIO_LINK_RESTORE_INDICATION
150 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_ERROR_INDICATION “Not Appli
151 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_COMMON_TRANSPORT_CHANNEL_SETUP_REQUEST “Not Appli
152 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_COMMON_TRANSPORT_CHANNEL_SETUP_RESPONSE “Not Appli
153 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_COMMON_TRANSPORT_CHANNEL_SETUP_FAILURE “Not Appli
154 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_COMMON_TRANSPORT_CHANNEL_RECONFIGURATION_REQUEST “Not Appli
155 NBAP_COMMON_TRANSPORT_CHANNEL_RECONFIGURATION_RESPONSE The
EVENT_PA
and
EVENT_PA
parameter
“Not Appli
156 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_COMMON_TRANSPORT_CHANNEL_RECONFIGURATION_FAILURE “Not Appli
157 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_COMMON_TRANSPORT_CHANNEL_DELETION_REQUEST “Not Appli
158 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_COMMON_TRANSPORT_CHANNEL_DELETION_RESPONSE “Not Appli
159 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_AUDIT_REQUIRED_INDICATION “Not Appli
160 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_AUDIT_REQUEST “Not Appli
161 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_AUDIT_RESPONSE “Not Appli
162 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_AUDIT_FAILURE “Not Appli
163 NBAP_COMMON_MEASUREMENT_INITIATION_REQUEST The
EVENT_PA
and
EVENT_PA
parameter
“Not Appli
164 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_COMMON_MEASUREMENT_INITIATION_RESPONSE “Not Appli
165 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_COMMON_MEASUREMENT_INITIATION_FAILURE “Not Appli
166 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_COMMON_MEASUREMENT_REPORT “Not Appli
167 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_COMMON_MEASUREMENT_TERMINATION_REQUEST “Not Appli
168 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_COMMON_MEASUREMENT_FAILURE_INDICATION “Not Appli
169 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_CELL_SETUP_REQUEST “Not Appli
170 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_CELL_SETUP_RESPONSE “Not Appli
171 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_CELL_SETUP_FAILURE “Not Appli
172 NBAP_CELL_RECONFIGURATION_REQUEST The
EVENT_PA
and
EVENT_PA
parameter
“Not Appli
173 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_CELL_RECONFIGURATION_RESPONSE “Not Appli
174 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_CELL_RECONFIGURATION_FAILURE “Not Appli
175 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_CELL_DELETION_REQUEST “Not Appli
176 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_CELL_DELETION_RESPONSE “Not Appli
177 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_RESOURCE_STATUS_INDICATION “Not Appli
178 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_SYSTEM_INFORMATION_UPDATE_REQUEST “Not Appli
179 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_SYSTEM_INFORMATION_UPDATE_RESPONSE “Not Appli
180 NBAP_SYSTEM_INFORMATION_UPDATE_FAILURE The
EVENT_PA
and
EVENT_PA
parameter
“Not Appli
181 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_RESET_REQUEST “Not Appli
182 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_RESET_RESPONSE “Not Appli
183 NBAP_COMPRESSED_MODE_COMMAND
184 NBAP_RADIO_LINK_PARAMETER_UPDATE_INDICATION
185 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_PHYSICAL_SHARED_CHANNEL_RECONFIGURATION_REQUEST “Not Appli
186 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_PHYSICAL_SHARED_CHANNEL_RECONFIGURATION_RESPONSE “Not Appli
187 The
EVENT_PA
and
EVENT_PA
parameter
NBAP_PHYSICAL_SHARED_CHANNEL_RECONFIGURATION_FAILURE “Not Appli
188 NBAP_MBMS_NOTIFICATION_UPDATE_COMMAND

2.2.3 RANAP Events

This section describes the RANAP events. The RANAP events are
specified by the standard 3GPP TS 25.413.

Available RANAP events are provided in Table 4.

Table 4 RANAP Event Details

Event Event Name Comments


Id
256 RANAP_RAB_ASSIGNMENT_REQUEST
257 RANAP_RAB_ASSIGNMENT_RESPONSE
258 RANAP_IU_RELEASE_REQUEST
The EVENT_PARAM_C_ID_1..4,
and
EVENT_PARAM_RNC_ID_1...4
parameters are reported as “Not
259 RANAP_IU_RELEASE_COMMAND Applicable”.
The EVENT_PARAM_C_ID_1..4,
and
EVENT_PARAM_RNC_ID_1...4
parameters are reported as “Not
260 RANAP_IU_RELEASE_COMPLETE Applicable”.
261 RANAP_SECURITY_MODE_COMMAND
262 RANAP_SECURITY_MODE_COMPLETE
263 RANAP_SECURITY_MODE_REJECT
264 RANAP_LOCATION_REPORTING_CONTROL
265 RANAP_DIRECT_TRANSFER
266 RANAP_ERROR_INDICATION
The parameters
EVENT_PARAM_UE_CONTEXT and
EVENT_PARAM_RNC_MODULE_ID
are reported as invalid.

The EVENT_PARAM_C_ID_1..4,
and
EVENT_PARAM_RNC_ID_1...4
parameters are reported as “Not
267 RANAP_PAGING Applicable”.
268 RANAP_COMMON_ID
269 RANAP_INITIAL_UE_MESSAGE
The parameters
EVENT_PARAM_UE_CONTEXT and
EVENT_PARAM_RNC_MODULE_ID
are reported as invalid.

The EVENT_PARAM_C_ID_1..4,
and
EVENT_PARAM_RNC_ID_1...4
parameters are reported as “Not
270 RANAP_RESET Applicable”.
271 RANAP_RESET_ACKNOWLEDGE The parameters
EVENT_PARAM_UE_CONTEXT and
EVENT_PARAM_RNC_MODULE_ID
are reported as invalid.

The EVENT_PARAM_C_ID_1..4,
and
EVENT_PARAM_RNC_ID_1...4
parameters are reported as “Not
Applicable”.
The parameters
EVENT_PARAM_UE_CONTEXT and
EVENT_PARAM_RNC_MODULE_ID
are reported as invalid.

The EVENT_PARAM_C_ID_1..4,
and
EVENT_PARAM_RNC_ID_1...4
parameters are reported as “Not
272 RANAP_RESET_RESOURCE Applicable”.
The parameters
EVENT_PARAM_UE_CONTEXT and
EVENT_PARAM_RNC_MODULE_ID
are reported as invalid.

The EVENT_PARAM_C_ID_1..4,
and
EVENT_PARAM_RNC_ID_1...4
parameters are reported as “Not
273 RANAP_RESET_RESOURCE_ACKNOWLEDGE Applicable”.
274 RANAP_RELOCATION_REQUIRED
The EVENT_PARAM_C_ID_1..4,
and
EVENT_PARAM_RNC_ID_1...4
parameters are reported as “Not
275 RANAP_RELOCATION_REQUEST Applicable”.
276 RANAP_RELOCATION_REQUEST_ACKNOWLEDGE
277 RANAP_RELOCATION_COMMAND
278 RANAP_RELOCATION_DETECT
279 RANAP_RELOCATION_COMPLETE
280 RANAP_RELOCATION_PREPARATION_FAILURE
281 RANAP_RELOCATION_FAILURE
282 RANAP_RELOCATION_CANCEL
283 RANAP_RELOCATION_CANCEL_ACKNOWLEDGE
284 RANAP_SRNS_CONTEXT_REQUEST
285 RANAP_SRNS_CONTEXT_RESPONSE
286 RANAP_SRNS_DATA_FORWARD_COMMAND
287 RANAP_LOCATION_REPORT
288 RANAP_RANAP_RELOCATION_INFORMATION
289 RANAP_RAB_RELEASE_REQUEST
290 RANAP_MBMS_SESSION_START
291 RANAP_MBMS_SESSION_START_RESPONSE
292 RANAP_MBMS_SESSION_START_FAILURE
293 RANAP_MBMS_SESSION_STOP
294 RANAP_MBMS_SESSION_STOP_RESPONSE

2.2.4 RNSAP Events

This section describes the RNSAP events. The RNSAP events are
specified by the standard 3GPP TS 25.423.

Available RNSAP events are provided in Table 5.

Table 5 RNSAP Event Details

Event Event Name Comme


Id
512 RNSAP_COMMON_TRANSPORT_CHANNEL_RESOURCES_RELEASE_REQUEST
513 RNSAP_COMMON_TRANSPORT_CHANNEL_RESOURCES_REQUEST
514 RNSAP_COMMON_TRANSPORT_CHANNEL_RESOURCES_RESPONSE
515 RNSAP_COMMON_TRANSPORT_CHANNEL_RESOURCES_FAILURE
516 RNSAP_RADIO_LINK_SETUP_REQUEST
517 RNSAP_RADIO_LINK_SETUP_RESPONSE
518 RNSAP_RADIO_LINK_SETUP_FAILURE
519 RNSAP_RADIO_LINK_ADDITION_REQUEST
520 RNSAP_RADIO_LINK_ADDITION_RESPONSE
521 RNSAP_RADIO_LINK_ADDITION_FAILURE
522 RNSAP_RADIO_LINK_RECONFIGURATION_PREPARE
523 RNSAP_RADIO_LINK_RECONFIGURATION_READY
524 RNSAP_RADIO_LINK_RECONFIGURATION_FAILURE
525 RNSAP_RADIO_LINK_RECONFIGURATION_COMMIT
526 RNSAP_RADIO_LINK_RECONFIGURATION_CANCEL
527 RNSAP_RADIO_LINK_DELETION_REQUEST
528 RNSAP_RADIO_LINK_DELETION_RESPONSE
529 RNSAP_DL_POWER_CONTROL_REQUEST
530 RNSAP_DEDICATED_MEASUREMENT_INITIATION_REQUEST
531 RNSAP_DEDICATED_MEASUREMENT_INITIATION_RESPONSE
532 RNSAP_DEDICATED_MEASUREMENT_INITIATION_FAILURE
533 RNSAP_DEDICATED_MEASUREMENT_REPORT
534 RNSAP_DEDICATED_MEASUREMENT_TERMINATION_REQUEST
535 RNSAP_DEDICATED_MEASUREMENT_FAILURE_INDICATION
536 RNSAP_RADIO_LINK_FAILURE_INDICATION
537 RNSAP_RADIO_LINK_RESTORE_INDICATION
538 RNSAP_COMPRESSED_MODE_COMMAND
539 RNSAP_ERROR_INDICATION
540 RNSAP_UPLINK_SIGNALLING_TRANSFER_INDICATION
541 RNSAP_DOWNLINK_SIGNALLING_TRANSFER_REQUEST
542 RNSAP_RADIO_LINK_PARAMETER_UPDATE_INDICATION

2.2.5 PCAP Events

This section describes the PCAP events. The PCAP events are specified
by the standard 3GPP TS 25.453.

Available PCAP events are provided in Table 6.

Table 6 PCAP Event Details

Event Event Name Comments


Id
768 PCAP_ERROR_INDICATION
769 PCAP_POSITION_INITIATION_REQUEST
770 PCAP_POSITION_INITIATION_RESPONSE
771 PCAP_POSITION_INITIATION_FAILURE
772 PCAP_POSITION_ACTIVATION_REQUEST
773 PCAP_POSITION_ACTIVATION_RESPONSE
774 PCAP_POSITION_ACTIVATION_FAILURE

2.2.6 SABP Events

This section describes the SABP events. The SABP events are specified
by the standard 3GPP TS 25.419.

Available SABP events are provided in Table 7.

Table 7 SABP Event Details

Event Event Name Comments


Id
896 SABP_WRITE_REPLACE
897 SABP_WRITE_REPLACE_COMPLETE
898 SABP_WRITE_REPLACE_FAILURE
899 SABP_KILL
900 SABP_KILL_COMPLETE
901 SABP_KILL_FAILURE
902 SABP_RESET
903 SABP_RESET_COMPLETE
904 SABP_RESET_FAILURE
905 SABP_RESTART
906 SABP_ERROR_INDICATION

3 Event Parameters
This section describes the event parameters. Details on event
parameters are provided in Table 8.

The table header contains the following acronyms:

PPS Parameter Packing Size (PPS) in bits. Unless otherwise stated, all
parameters have an extra validity bit. If the most significant bit is
1, the parameter value is invalid.

NV The Numeric Value (NV) of the event parameter

Table 8 Event Parameter Details

Description PPS
EVENT_PARAM_ACT_REASON
Any of the following causes: activation decision triggered by UE 4 EVENT_VALUE_A
measurement report, addition of new RL, reactivation of CM EVENT_VALUE_A
triggered by UE measurement report, other cause.
EVENT_VALUE_R
EVENT_VALUE_O
EVENT_VALUE_I
EVENT_VALUE_G

EVENT_PARAM_ACTION
The action taken when the event was generated. 7 EVENT_VALUE_A
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_N
EVENT_VALUE_O
EVENT_VALUE_R
EVENT_PARAM_ACTION - continued
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_P
EVENT_VALUE_E
EVENT_VALUE_B
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_PARAM_ACTION - continued
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_P
EVENT_VALUE_P
EVENT_VALUE_P
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_PARAM_ACTION - continued
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_S

EVENT_PARAM_ASE_REDUCTION
Number of reduced Air interface Speech Equivalents (ASEs). 17 -

The actual range is 0..500, but with a resolution of 0.01 this


gives a parameter range of 0..50000 in the ROP file.

EVENT_PARAM_NO_OF_CELLS_IN_ACTIVE_SET
Parameter value 0 = one cell 3 -

Parameter value 1 = two cells

...

Parameter value 3 = four cells

EVENT_PARAM_NO_OF_CELLS_IN_REPORT
Number of cells fulfilling the event that are included in the 3 -
report.

Parameter value 0 = one cell

Parameter value 1 = two cells

...

Parameter value 3 = four cells

EVENT_PARAM_CHANNEL_SWITCH_REASON
Reason for channel switch. 5 EVENT_VALUE_C
EVENT_VALUE_T
EVENT_VALUE_I
EVENT_VALUE_C
EVENT_VALUE_S
EVENT_VALUE_U
EVENT_VALUE_E
EVENT_VALUE_T
EVENT_VALUE_T
EVENT_VALUE_T
EVENT_VALUE_E
EVENT_VALUE_U
EVENT_VALUE_L
EVENT_VALUE_O

EVENT_PARAM_CHANNELIZATION_CODE_NORM_MODE
Downlink channelization code number for normal mode. 9 -

EVENT_PARAM_CHANNELIZATION_CODE_COMP_MODE
DL channelization code number for compressed mode. 9 -

EVENT_PARAM_CM_TYPE
Compressed Mode type. 3 EVENT_VALUE_D
EVENT_VALUE_U
EVENT_VALUE_U

EVENT_PARAM_DEACT_REASON
Any of the following reasons: deactivation decision triggered by 4 EVENT_VALUE_D
UE measurement report, addition of new RL, other reason. EVENT_VALUE_A
EVENT_VALUE_O
EVENT_VALUE_I
EVENT_VALUE_G

EVENT_PARAM_DL_POWER
DL power. 11 -

The actual range is 0..100, but with a resolution of 0.1 this


gives a parameter range of 0..1000 in the ROP file.

EVENT_PARAM_EVENT_TRIGGER
Trigger for recording the event. 8 EVENT_VALUE_B
EVENT_VALUE_A
EVENT_VALUE_B
EVENT_VALUE_N
EVENT_VALUE_L
EVENT_VALUE_L
EVENT_VALUE_E
EVENT_VALUE_P
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_A
EVENT_VALUE_A
EVENT_PARAM_EVENT_TRIGGER - continued
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_E
EVENT_VALUE_E
EVENT_VALUE_E
EVENT_VALUE_E
EVENT_VALUE_E
EVENT_VALUE_E
EVENT_VALUE_A
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_U
EVENT_VALUE_C
EVENT_VALUE_C
EVENT_PARAM_EVENT_TRIGGER - continued
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_P
EVENT_VALUE_P
EVENT_VALUE_E
EVENT_VALUE_I
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_O
EVENT_VALUE_E
EVENT_VALUE_E
EVENT_PARAM_EVENT_TRIGGER - continued
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_E
EVENT_VALUE_P
EVENT_VALUE_C
EVENT_VALUE_P
EVENT_VALUE_P
EVENT_VALUE_S
EVENT_VALUE_O
EVENT_VALUE_R
EVENT_VALUE_F
EVENT_VALUE_F
EVENT_VALUE_P
EVENT_PARAM_EVENT_TRIGGER - continued
EVENT_VALUE_F
EVENT_VALUE_U
EVENT_VALUE_P
EVENT_VALUE_1
EVENT_VALUE_H
EVENT_VALUE_P
EVENT_VALUE_I
EVENT_VALUE_L
EVENT_VALUE_G
EVENT_VALUE_P
EVENT_VALUE_P
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_S

EVENT_PARAM_FAILURE_REASON
Failure reason. 8 EVENT_VALUE_B
EVENT_VALUE_U
EVENT_VALUE_D
EVENT_VALUE_D
EVENT_VALUE_D
EVENT_VALUE_T
EVENT_VALUE_T
EVENT_VALUE_T
EVENT_VALUE_C
EVENT_VALUE_O
EVENT_VALUE_A
EVENT_VALUE_R
EVENT_VALUE_D
EVENT_VALUE_A
EVENT_PARAM_FAILURE_REASON - continued
EVENT_VALUE_U
EVENT_VALUE_U
EVENT_VALUE_A
EVENT_VALUE_I
EVENT_VALUE_L
EVENT_VALUE_T
EVENT_VALUE_T
EVENT_VALUE_T
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_C
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_R
EVENT_PARAM_FAILURE_REASON - continued
EVENT_VALUE_I
EVENT_VALUE_L
EVENT_VALUE_I
EVENT_VALUE_R
EVENT_VALUE_U
EVENT_VALUE_U
EVENT_VALUE_U
EVENT_VALUE_L
EVENT_VALUE_L
EVENT_VALUE_L
EVENT_VALUE_E
EVENT_VALUE_E
EVENT_VALUE_R
EVENT_VALUE_A
EVENT_PARAM_FAILURE_REASON - continued
EVENT_VALUE_S
EVENT_VALUE_U
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_S
EVENT_VALUE_R
EVENT_VALUE_P
EVENT_VALUE_F
EVENT_VALUE_H
EVENT_VALUE_T
EVENT_VALUE_N
EVENT_VALUE_C
EVENT_VALUE_N
EVENT_VALUE_P
EVENT_PARAM_FAILURE_REASON - continued
EVENT_VALUE_N
EVENT_VALUE_T
EVENT_VALUE_T
EVENT_VALUE_T
EVENT_VALUE_F
EVENT_VALUE_R
EVENT_VALUE_N
EVENT_VALUE_R
EVENT_VALUE_T
EVENT_VALUE_T
EVENT_VALUE_U
EVENT_VALUE_N
EVENT_VALUE_R
EVENT_PARAM_FAILURE_REASON - continued
EVENT_VALUE_T
EVENT_VALUE_R
EVENT_VALUE_T
EVENT_VALUE_T
EVENT_VALUE_M
EVENT_VALUE_M
EVENT_VALUE_A
EVENT_VALUE_R
EVENT_VALUE_T
EVENT_VALUE_T

EVENT_PARAM_CPICH_EC_NO_CELL_1
Downlink Common Pilot Channel (CPICH) Ec/No for the first 7 -
cell in the active set.

The range for the measured CPICH Ec/Io value is -24..0 dB,
resolution 0.5, giving a range 0..49.

See the 3GPP specification 25.133 for mapping of the reported


and the measured value.

EVENT_PARAM_CPICH_EC_NO_CELL_2
Downlink Common Pilot Channel (CPICH) Ec/No for the second 7 -
cell in the active set.

The range for the measured CPICH Ec/Io value is -24..0 dB,
resolution 0.5, giving a range 0..49

See the 3GPP specification 25.133 for mapping of the reported


and the measured value.

EVENT_PARAM_CPICH_EC_NO_CELL_3
Downlink Common Pilot Channel (CPICH) Ec/No for the third 7 -
cell in the active set.

The range for the measured CPICH Ec/Io value is -24..0 dB,
resolution 0.5, giving a range 0..49

See the 3GPP specification 25.133 for mapping of the reported


and the measured value.

EVENT_PARAM_CPICH_EC_NO_CELL_4
Downlink Common Pilot Channel (CPICH) Ec/No for the fourth 7 -
cell in the active set.

The range for the measured CPICH Ec/Io value is -24..0 dB,
resolution 0.5, giving a range 0..49

See the 3GPP specification 25.133 for mapping of the reported


and the measured value.

EVENT_PARAM_CPICH_EC_NO_EVAL_CELL
Downlink Common Pilot Channel (CPICH) Ec/No for evaluated 7 -
cell.

The range for the measured CPICH Ec/Io value is -24..0 dB,
resolution 0.5, giving a range 0..49

See the 3GPP specification 25.133 for mapping of the reported


and the measured value.

EVENT_PARAM_RSCP_CELL_1
Received Signal Code Power (RSCP) for first cell in the active 8 -
set.

The range for the measured CPICH RSCP value is -115..-25


dBm, where 0 means CPICH RSCP < -115 and 91 means
CPICH RSCP >= -25, resolution: 1, unit: dBm)

See the 3GPP spec 25.133 for mapping of the reported and the
measured value.
EVENT_PARAM_RSCP_CELL_2
Received Signal Code Power (RSCP) for second cell in the 8 -
active set.

The range for the measured CPICH RSCP value is -115..-25


dBm, where 0 means CPICH RSCP < -115 and 91 means
CPICH RSCP >= -25, resolution: 1, unit: dBm)

See the 3GPP spec 25.133 for mapping of the reported and the
measured value.

EVENT_PARAM_RSCP_CELL_3
Received Signal Code Power (RSCP) for third cell in the active 8 -
set.

The range for the measured CPICH RSCP value is -115..-25


dBm, where 0 means CPICH RSCP < -115 and 91 means
CPICH RSCP >= -25, resolution: 1, unit: dBm)

See the 3GPP spec 25.133 for mapping of the reported and the
measured value.

EVENT_PARAM_RSCP_CELL_4
Received Signal Code Power (RSCP) for fourth cell in the active 8 -
set.

The range for the measured CPICH RSCP value is -115..-25


dBm, where 0 means CPICH RSCP < -115 and 91 means
CPICH RSCP >= -25, resolution: 1, unit: dBm)

See the 3GPP spec 25.133 for mapping of the reported and the
measured value.

EVENT_PARAM_SYNCH_INFO_OFF_CELL1
OFF for the best cell in the active set. 9 -

EVENT_PARAM_SYNCH_INFO_OFF_CELL2
OFF for the 2nd best cell in the active set. 9 -

EVENT_PARAM_SYNCH_INFO_OFF_CELL3
OFF for the 3rd best cell in the active set. 9 -

EVENT_PARAM_SYNCH_INFO_OFF_CELL4
OFF for the 4th best cell in the active set. 9 -
EVENT_PARAM_SYNCH_INFO_TM_CELL1
Tm for the best cell in the active set. 17 -

EVENT_PARAM_SYNCH_INFO_TM_CELL2
Tm for the 2nd best cell in the active set. 17 -

EVENT_PARAM_SYNCH_INFO_TM_CELL3
Tm for the 3rd best cell in the active set. 17 -

EVENT_PARAM_SYNCH_INFO_TM_CELL4
Tm for the 4th best cell in the active set. 17 -

EVENT_PARAM_SCRAMBLING_CODE_NCELL_1
DL primary scrambling code for highest ranked cell in 10 -
monitored and detected set, provided that Ec/No is used as the
measured quantity given by the attribute measQuantity1 for
MO class UeMeasControl. Otherwise this value relates to the
best cell considering that RSCP is used as measured quality.

EVENT_PARAM_SCRAMBLING_CODE_NCELL_2
DL primary scrambling code for 2nd highest ranked cell in 10 -
monitored and detected set, provided that Ec/No is used as the
measured quantity given by the attribute measQuantity1 for
MO class UeMeasControl. Otherwise this value relates to the
best cell considering that RSCP is used as measured quality.

EVENT_PARAM_SCRAMBLING_CODE_NCELL_3
DL primary scrambling code for 3rd highest ranked cell in 10 -
monitored and detected set, provided that Ec/No is used as the
measured quantity given by the attribute measQuantity1 for
MO class UeMeasControl. Otherwise this value relates to the
best cell considering that RSCP is used as measured quality.

EVENT_PARAM_SCRAMBLING_CODE_NCELL_4
DL primary scrambling code for 4th highest ranked cell in 10 -
monitored and detected set, provided that Ec/No is used as the
measured quantity given by the attribute measQuantity1 for
MO class UeMeasControl. Otherwise this value relates to the
best cell considering that RSCP is used as measured quality.

EVENT_PARAM_SCRAMBLING_CODE_NCELL_5
DL primary scrambling code for 5th highest ranked cell in 10 -
monitored and detected set, provided that Ec/No is used as the
measured quantity given by the attribute measQuantity1 for
MO class UeMeasControl. Otherwise this value relates to the
best cell considering that RSCP is used as measured quality.

EVENT_PARAM_SCRAMBLING_CODE_NCELL_6
DL primary scrambling code for 6th highest ranked cell in 10 -
monitored and detected set, provided that Ec/No is used as the
measured quantity given by the attribute measQuantity1 for
MO class UeMeasControl. Otherwise this value relates to the
best cell considering that RSCP is used as measured quality.

EVENT_PARAM_CPICH_EC_NO_NCELL_1
DL CPICH Ec/No for highest ranked cell in monitored and 7 -
detected set, provided that Ec/No is used as the measured
quantity given by the attribute measQuantity1 for MO class
UeMeasControl. Otherwise this value relates to the best cell
considering that RSCP is used as measured quality. Note: If no
Soft or Softer HO has been executed for this connection after
the establishment to CELL_DCH state, before the trigger of this
event, no measured values will exist. Resolution 0.5.

EVENT_PARAM_CPICH_EC_NO_NCELL_2
DL CPICH Ec/No for 2nd highest ranked cell in monitored and 7 -
detected set, provided that Ec/No is used as the measured
quantity given by the attribute measQuantity1 for MO class
UeMeasControl. Otherwise this value relates to the best cell
considering that RSCP is used as measured quality. Resolution
0.5.

EVENT_PARAM_CPICH_EC_NO_NCELL_3
DL CPICH Ec/No for 3rd highest ranked cell in monitored and 7 -
detected set, provided that Ec/No is used as the measured
quantity given by the attribute measQuantity1 for MO class
UeMeasControl. Otherwise this value relates to the best cell
considering that RSCP is used as measured quality. Resolution
0.5.

EVENT_PARAM_CPICH_EC_NO_NCELL_4
DL CPICH Ec/No for 4th highest ranked cell in monitored and 7 -
detected set, provided that Ec/No is used as the measured
quantity given by the attribute measQuantity1 for MO class
UeMeasControl. Otherwise this value relates to the best cell
considering that RSCP is used as measured quality. Resolution
0.5.

EVENT_PARAM_CPICH_EC_NO_NCELL_5
DL CPICH Ec/No for 5th highest ranked cell in monitored and 7 -
detected set, provided that Ec/No is used as the measured
quantity given by the attribute measQuantity1 for MO class
UeMeasControl. Otherwise this value relates to the best cell
considering that RSCP is used as measured quality. Resolution
0.5.

EVENT_PARAM_CPICH_EC_NO_NCELL_6
DL CPICH Ec/No for 6th highest ranked cell in monitored and 7 -
detected set, provided that Ec/No is used as the measured
quantity given by the attribute measQuantity1 for MO class
UeMeasControl. Otherwise this value relates to the best cell
considering that RSCP is used as measured quality. Resolution
0.5.

EVENT_PARAM_RSCP_NCELL_1
RSCP for highest ranked cell in monitored and detected set, 8 -
provided that RSCP is used as the measured quantity given by
the attribute measQuantity1 for MO class UeMeasControl.
Otherwise this value relates to the best cell considering that
Ec/No is used as measured quality. Note: If no Soft or Softer
HO has been executed for this connection after the
establishment to CELL_DCH state, before the trigger of this
event, no measured values will exist.

EVENT_PARAM_RSCP_NCELL_2
RSCP for 2nd highest ranked cell in monitored and detected 8 -
set, provided that RSCP is used as the measured quantity
given by the attribute measQuantity1 for MO class
UeMeasControl. Otherwise this value relates to the best cell
considering that Ec/No is used as measured quality.

EVENT_PARAM_RSCP_NCELL_3
RSCP for 3rd highest ranked cell in monitored and detected 8 -
set, provided that RSCP is used as the measured quantity
given by the attribute measQuantity1 for MO class
UeMeasControl. Otherwise this value relates to the best cell
considering that Ec/No is used as measured quality.

EVENT_PARAM_RSCP_NCELL_4
RSCP for 4th highest ranked cell in monitored and detected 8 -
set, provided that RSCP is used as the measured quantity
given by the attribute measQuantity1 for MO class
UeMeasControl. Otherwise this value relates to the best cell
considering that Ec/No is used as measured quality.

EVENT_PARAM_RSCP_NCELL_5
RSCP for 5th highest ranked cell in monitored and detected 8 -
set, provided that RSCP is used as the measured quantity
given by the attribute measQuantity1 for MO class
UeMeasControl. Otherwise this value relates to the best cell
considering that Ec/No is used as measured quality.

EVENT_PARAM_RSCP_NCELL_6
RSCP for 6th highest ranked cell in monitored and detected 8 -
set, provided that RSCP is used as the measured quantity
given by the attribute measQuantity1 for MO class
UeMeasControl. Otherwise this value relates to the best cell
considering that Ec/No is used as measured quality.

EVENT_PARAM_SYNCH_INFO_OFF_NCELL1
OFF for the highest ranked cell in monitored and detected set. 9 -

EVENT_PARAM_SYNCH_INFO_OFF_NCELL2
OFF for the 2nd highest ranked cell in monitored and detected 9 -
set.

EVENT_PARAM_SYNCH_INFO_OFF_NCELL3
OFF for the 3rd highest ranked cell in monitored and detected 9 -
set.

EVENT_PARAM_SYNCH_INFO_OFF_NCELL4
OFF for the 4th highest ranked cell in monitored and detected 9 -
set.

EVENT_PARAM_SYNCH_INFO_OFF_NCELL5
OFF for the 5th highest ranked cell in monitored and detected 9 -
set.

EVENT_PARAM_SYNCH_INFO_OFF_NCELL6
OFF for the 6th highest ranked cell in monitored and detected 9 -
set.

EVENT_PARAM_SYNCH_INFO_TM_NCELL1
Tm for the highest ranked cell in monitored and detected set. 17 -

EVENT_PARAM_SYNCH_INFO_TM_NCELL2
Tm for the 2nd highest ranked cell in monitored and detected 17 -
set.

EVENT_PARAM_SYNCH_INFO_TM_NCELL3
Tm for the 3rd highest ranked cell in monitored and detected 17 -
set.
EVENT_PARAM_SYNCH_INFO_TM_NCELL4
Tm for the 4th highest ranked cell in monitored and detected 17 -
set.

EVENT_PARAM_SYNCH_INFO_TM_NCELL5
Tm for the 5th highest ranked cell in monitored and detected 17 -
set.

EVENT_PARAM_SYNCH_INFO_TM_NCELL6
Tm for the 6th highest ranked cell in monitored and detected 17 -
set.

EVENT_PARAM_HHO_TARGET_ID_1
In general the HO type is determined by the combination of 17 -
the parameters EVENT_PARAM_EVALUATION_CASE and
EVENT_PARAM_PROCEDURE_INDICATOR. For applicable
parameter values, see their respective parameter description.
This parameter represents PLMN Identity.

EVENT_PARAM_HHO_TARGET_ID_2
In general the HO type is determined by the combination of 25 -
the parameters EVENT_PARAM_EVALUATION_CASE and
EVENT_PARAM_PROCEDURE_INDICATOR. For applicable
parameter values, see their respective parameter description.
This parameter represents Location Area Code (LAC).

EVENT_PARAM_HHO_TARGET_ID_3
In general the HO type is determined by the combination of 17 -
the parameters EVENT_PARAM_EVALUATION_CASE and
EVENT_PARAM_PROCEDURE_INDICATOR. For applicable
parameter values, see their respective parameter description.
This parameter represents Cell Id.

EVENT_PARAM_HHO_TARGET_ID_4
In general the HO type is determined by the combination of 13 -
the parameters EVENT_PARAM_EVALUATION_CASE and
EVENT_PARAM_PROCEDURE_INDICATOR. For applicable
parameter values, see their respective parameter description.

Parameter representation for IRATHO: N/A for IRATHO

Parameter representation for IRATCC: N/A for IRATCC.

Parameter representation for GAN HO: N/A for GAN HO.


Parameter representation for CNHHO: This parameter
represents RNC Id.

Parameter representation for IFHO: This parameter represents


RNC Id.

EVENT_PARAM_DL_QUALITY_MEAS1_TARGET_CELL
In general the HO type is determined by the combination of 7 -
the parameters EVENT_PARAM_EVALUATION_CASE and
EVENT_PARAM_PROCEDURE_INDICATOR.
For applicable parameter values, see their respective
parameter description.

Parameter representation for IRATHO:


This parameter represents RSSI (Range: 0..63, Resolution:
See 3GPP spec, Unit: See 3GPP spec). 3GPP spec 45.008
specifies the mapping between the reported value and the
actual physical measured value, where RXLEV corresponds to
RSSI. The measured signal level shall be mapped to an RXLEV
value between 0 and 63, as follows (where SCALE equals '0'
when ordering a 3a measurement, therefore excluded below):
RXLEV 0 = less than 110 dBm
RXLEV 1 = 110 dBm to 109 dBm
RXLEV 2 = 109 dBm to 108 dBm
:
:
RXLEV 62 = 49 dBm to 48 dBm
RXLEV 63 = greater than 48 dBm

Parameter representation for IRATCC:


This parameter represents RSSI. Same definition as for
IRATHO

Parameter representation for GAN HO:


This parameter represents RSSI. Same definition as for
IRATHO

Parameter representation for CNHHO:


This parameter represents CPICH Ec/N0 (Range: 0..49,
Resolution: 0.5, Unit: dB (the physical measured value is in
dB). See 3GPP spec 25.133 for mapping between reported
value and the actual physical measured value. The reporting
range is for CPICH Ec/Eo is from -24 ...0 dB, resolution 0.5.)

Parameter representation for IFHO:


This parameter represents CPICH Ec/N0, same definition as for
CNHHO.

EVENT_PARAM_DL_QUALITY_MEAS2_TARGET_CELL
In general the HO type is determined by the combination of 8 -
the parameters EVENT_PARAM_EVALUATION_CASE and
EVENT_PARAM_PROCEDURE_INDICATOR.
For applicable parameter values, see their respective
parameter description.

Parameter representation for IRATHO:


This parameter is N/A.

Parameter representation for IRATCC:


This parameter is N/A.

Parameter representation for GAN HO:


This parameter is N/A.

Parameter representation for CNHHO:


This parameter represents CPICH RSCP (Range: 0..91,
Resolution: 1, Unit: dBm (the physical measured value is in
dBm)). See 3GPP spec 25.133 for mapping between reported
value and the actual physical measured value. The reporting
range is for CPICH RSCP is from -115 ...-25 dBm, resolution 1.

Parameter representation for IFHO:


This parameter represents CPICH RSCP, same definition as for
CNHHO.

EVENT_PARAM_RSCP_EVAL_CELL
Received Signal Code Power (RSCP) for evaluated cell. 8 -

The range for the measured CPICH RSCP value is -115..-25


dBm, where 0 means CPICH RSCP < -115 and 91 means
CPICH RSCP >= -25, resolution: 1, unit: dBm)

See the 3GPP spec 25.133 for mapping of the reported and the
measured value.

EVENT_PARAM_SCRAMBLING_CODE_CELL_1
Downlink primary scrambling code number for the first cell in 10 -
the active set.

EVENT_PARAM_SCRAMBLING_CODE_CELL_2
Downlink primary scrambling code number for the second cell 10 -
in the active set.

EVENT_PARAM_SCRAMBLING_CODE_CELL_3
Downlink primary scrambling code number for the third cell in 10 -
the active set.

EVENT_PARAM_SCRAMBLING_CODE_CELL_4
Downlink primary scrambling code number for the fourth cell in 10 -
the active set.

EVENT_PARAM_SCRAMBLING_CODE_EVAL_CELL_1
Downlink primary scrambling code number for first evaluated 10 -
cell.

EVENT_PARAM_SCRAMBLING_CODE_EVAL_CELL_2
Downlink primary scrambling code number for the second 10 -
evaluated cell.

EVENT_PARAM_SCRAMBLING_CODE_EVAL_CELL_3
Downlink primary scrambling code number for the third 10 -
evaluated cell.

EVENT_PARAM_SCRAMBLING_CODE_EVAL_CELL_4
Downlink primary scrambling code number for the fourth 10 -
evaluated cell.

EVENT_PARAM_IMSI
International Mobile Subscriber Identity 60 -

EVENT_PARAM_MEAS_REPORTS_IN_BUFFER_1A_1C
Number of measurement reports in the 1a/1c buffer waiting for 5 -
processing.

EVENT_PARAM_MEAS_REPORTS_IN_BUFFER_1B
Number of measurement reports in the 1b buffer waiting for 5 -
processing.

EVENT_PARAM_MEAS_REPORTS_IN_BUFFER_1D
Number of measurement reports in the 1d buffer waiting for 5 -
processing.

EVENT_PARAM_MEAS_REPORTS_IN_BUFFER_3A
Number of measurement reports in the 3a buffer waiting for 5 -
processing.

EVENT_PARAM_MEASURED_ENTITY
Measured entity used for 4 EVENT_VALUE_U
INTERNAL_RADIO_QUALITY_MEASUREMENTS_UEH and EVENT_VALUE_D
INTERNAL_RADIO_QUALITY_MEASUREMENTS_RNH.
EVENT_VALUE_U
EVENT_VALUE_D
EVENT_VALUE_N
EVENT_VALUE_H

EVENT_PARAM_MEASURED_VALUE
Measured value for the related measurement type according to 11 -
the parameter EVENT_PARAM_MEASURED_ENTITY (SIR error,
DL Tx code power, UL interference, DL Tx CarrierPower, Non
HighSpeed Power, HSDSCH Required Power).

See 3GPP TS 25.133 for updated definitions. The figures here


are taken from 3GPP TS 25.133 V5.17.0 (2005-12), 25133-
5h0.

Ranges for the reported values per measurement type are as


follows:

• SIR Error range: 0..125 (measurement range -31..31,


unit: dB, resolution: 0.5)
• DL Tx code power, range: 0..127 (measurement range
-10..46, unit: dBm, resolution: 0.5. Reported values
below 10 shall be mapped to -10 dBm while reported
values above 122 shall be mapped to 46 dBm)
• UL interference range: 0..621 (Received total wideband
power = RTWP), measurement range: -112..-50 dBm,
(unit: dBm, resolution: 0.1)
• DL Tx CarrierPower range: 0..100 (unit: %, resolution:
0.1)
• HSDSCH_REQUIRED_POWER, range: 0..100 (unit: %,
resolution: 0.1)
• NON_HS_POWER, range: 0..100 (unit: %, resolution:
0.1)

EVENT_PARAM_NR_OF_CONNECTIONS_SF8
Number of downlink connections for spreading factor 8. 8 -

EVENT_PARAM_NR_OF_CONNECTIONS_SF16
Number of downlink connections, apart from HS, for spreading 8 -
factor 16.

EVENT_PARAM_NR_OF_CONNECTIONS_SF32
Number of downlink connections for spreading factor 32. 8 -

EVENT_PARAM_RESULT
Result value. 3 EVENT_VALUE_S
EVENT_VALUE_F
EVENT_VALUE_F
EVENT_VALUE_F

EVENT_PARAM_RLC_BUFFER_VOLUME
Volume of data in downlink Radio Link Control (RLC) buffer. 16 -

EVENT_PARAM_URA_ID
The identity of the URA. 17 -

EVENT_PARAM_CELL_UPDATE_CAUSE_VALUE
The cause for a cell update. 4 EVENT_VALUE_C
EVENT_VALUE_P
EVENT_VALUE_U
EVENT_VALUE_P
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R

EVENT_PARAM_STATE_CHANGE_NODE
3 EVENT_VALUE_F
EVENT_VALUE_F
EVENT_VALUE_B
EVENT_VALUE_A

EVENT_PARAM_TOTAL_ASE_DL
Total Air interface Speech Equivalents (ASEs) downlink at the 17 -
time of event generation.

The range is 0..500 with a resolution of 0.01. This gives a


reported range of 0..50000.

EVENT_PARAM_TOTAL_ASE_UL
Total Air interface Speech Equivalents (ASEs) uplink at the 17 -
time of event generation.

The range is 0..500 with a resolution of 0.01. This gives a


reported range of 0..50000.

EVENT_PARAM_TOTAL_DL_CHAN_CODE_TREE_CONSUMPTION
Total downlink channelization code tree consumption. 16 -

EVENT_PARAM_UE_CONTEXT
Initial UE context number (the global UE Context reference 16 -
should be used).

EVENT_PARAM_UL_INTERFERENCE
Uplink interference. Also referred to as Received Total 11 -
Wideband Power (RTWP).

UL interference range: 0..621, measurement range: -112..-50


dBm, (unit: dBm, resolution: 0.1)

See 3GPP spec 25.133 for mapping of the reported and the
measured value.

EVENT_PARAM_UL_SIR_TARGET
Actual Signal-to-Interference Ratio (SIR) target. 9 -

Measurement range: -8.2..17.3, resolution 0.1.

EVENT_PARAM_VALUE_AT_FAILURE
This parameter is related to EVENT_PARAM_FAILURE. That 24 -
parameter specifies the type of failure and this parameter the
corresponding value for the failure. Possible values for different
failure reasons:

• cngstState = range: [UL, DL, UL+DL]


• totAseUl = Uplink ASE load in the cell, range: [0 - 2000
• totAseDl = Downlink ASE load in the cell, range: [0 -
2000]
• current SF = range: [8, 16, 32]
• dlChCodeTreeUsage = Number of links with SF = x in
the cell, range: [0-x]
• (filteredDlPower+estimatedDlPwrDelta)
• Consumed DL capacity credits if blocked by DL RBS HW
resources or UL and DL RBS HW resources. Range: [0 -
131071]
• Consumed UL capacity credits if blocked due to only UL
RBS HW resources. Range: [0 - 131071]
EVENT_PARAM_VALUE_AT_FAILURE - continued
• EVENT_VALU E_TOO_MANY _USERS_ON_ HSPDSCH
Range: [0 - 1000]
• Represents the number of E-DCH users in the serving
cell in case of failure reason=EVENT_VALU
E_TOO_MANY_ SERVING_CELL_USERS_EUL. Range: [0
- 100]
• Represents the number of E-DCH users in the non-
serving cell in case of failure reason=EVENT_VALU
E_TOO_MANY_ NON_SERVING_CELL_USERS_EUL.
Range: [0 - 100]
• EVENT_VALUE_BLOCKED_BY_CONGESTION_CTRL.
Range: [1-9], where:
1 = UL_OVERLOAD
2 = DL_DCH_OVERLOAD
3 = UL_AND_DL_DCH_OVERLOAD
4 = HSDSCH_OVERLOAD
5 = UL_AND_HSDSCH_OVERLOAD
8 = HSDSCH_AND_DL_DCH_OVERLOAD
9 = UL_AND_DL_DCH_AND_HSDSCH_OVERLOAD
• TN_IUB failure reasons: Range [0-19900], Unit 100
kbit/s

EVENT_PARAM_RNC_MODULE_ID
Identity of the RNC module from which the event is reported. 7 -
It represents the rncModuleResourceId attribute of the
RncModule MO class in the RNC MOM.

EVENT_PARAM_EVENT_ID
Event identity. 11 -

EVENT_PARAM_TIMESTAMP_HOUR
Time in hour when the event was generated. 5 -

EVENT_PARAM_TIMESTAMP_MINUTE
Time in minutes when the event was generated. 6 -

EVENT_PARAM_TIMESTAMP_SECOND
Time in seconds when the event was generated. 6 -

EVENT_PARAM_TIMESTAMP_MILLISEC
Time in milliseconds when the event was generated. 11 -

EVENT_PARAM_ERROR_TYPE
Error type. 6 EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_PARAM_ERROR_TYPE - continued
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R

EVENT_PARAM_PROTOCOL_ERROR_CAUSE
Protocol error cause. 16 -

EVENT_PARAM_RRC_TRANSACTION_IDENTIFIER
RRC transaction identifier. 16 -

EVENT_PARAM_PROCEDURE_CODE
Procedure code of the message. 16 -

EVENT_PARAM_RECEIVED_MESSAGE_TYPE
Message type received by the UE. 16 -

EVENT_PARAM_IE_NAME
Information Element (IE) id of the message parameter. 17 -

EVENT_PARAM_ERROR_LOCATION
An additional textual description (of up to 32 characters) of the 256 -
location of the problem. A function name should be given, then
any extra information, such as line number, if additional
pinpointing in the code is needed. If shorter than 32
characters, the text string shall be terminated by a null
character (’\0’).

EVENT_PARAM_ASN1_AVAILABILITY
Undecoded message available or not. 2 EVENT_VALUE_A
EVENT_VALUE_A

EVENT_PARAM_MESSAGE_LENGTH
Number of bytes in the ASN.1-encoded message. 12 -

EVENT_PARAM_MESSAGE_DISCRIMINATOR
Message discriminator. 16 -

EVENT_PARAM_CN_DOMAIN_INDICATOR
CN domain indicator (if present). 16 -

EVENT_PARAM_HANDOVER_TYPE
Handover type after action. 3 EVENT_VALUE_A
EVENT_VALUE_R
EVENT_VALUE_R

EVENT_PARAM_PDU_TYPE
Direction and logical channel used for RRC messages. 5 EVENT_VALUE_D
EVENT_VALUE_U
EVENT_VALUE_D
EVENT_VALUE_U
EVENT_VALUE_P
EVENT_VALUE_D
EVENT_VALUE_U
EVENT_VALUE_B
EVENT_VALUE_B

EVENT_PARAM_MESSAGE_DIRECTION
Direction of message (sent or received). 2 EVENT_VALUE_R
EVENT_VALUE_S

EVENT_PARAM_MESSAGE_CONTENTS
The message content has variable length. This parameter has a 16384 -
limit of 4 KB according to 3GPP. The actual size used varies,
since the recording functions use only the space required by
the message with no wasted space. Thus, even if the size is 4
KB, this will only be fully used if the message contents are
actually 4 KB long. The undecoded ASN.1 contents, if available,
should be dumped here; otherwise, a null terminated string
describing the problem, followed by a binary dump of any
variables, is reported.

EVENT_PARAM_NO_OF_CM_USERS
Number of compressed mode users. 8 -

EVENT_PARAM_REQUEST_TYPE
Type of request for admission control response. 3 EVENT_VALUE_H
EVENT_VALUE_N

EVENT_PARAM_TRAFFIC_CLASS
Traffic class of requesting connection. 3 EVENT_VALUE_G
EVENT_VALUE_N
For the event INTERNAL_RAB_ESTABLISHMENT, the
EVENT_VALUE_INVALID is reported, in case the RAB
Establishment attempt failed to select a target UeRc.

EVENT_PARAM_TRAFFIC_CLASS_UL
Traffic class on UL in SRNC. Set as NotValid in DRNC. 3 EVENT_VALUE_G
EVENT_VALUE_N

EVENT_PARAM_C_ID_1
Id of the best cell in the Active Set, where best cell refers to 17 -
the measured quantity, which can be either Ec/No or RSCP.

For the INTERNAL_SYSTEM_RELEASE event:

The reported value represents the value available at the


reporting time.

EVENT_PARAM_C_ID_2
Id of the 2nd best cell in the Active Set, where 2nd best cell 17 -
refers to the measured quantity, which can be either Ec/No or
RSCP.

For the INTERNAL_SYSTEM_RELEASE event:

The reported value represents the value available at the


reporting time.

EVENT_PARAM_C_ID_3
Id of the 3rd best cell in the Active Set, where 3rd best cell 17 -
refers to the measured quantity, which can be either Ec/No or
RSCP.

For the INTERNAL_SYSTEM_RELEASE event:

The reported value represents the value available at the


reporting time.

EVENT_PARAM_C_ID_4
Id of the 4th best cell in the Active Set, where 4th best cell 17 -
refers to the measured quantity, which can be either Ec/No or
RSCP.

For the INTERNAL_SYSTEM_RELEASE event:

The reported value represents the value available at the


reporting time.

EVENT_PARAM_C_ID_EVALUATED
Cell identity of the cell that caused the measurement report 17 -
(added, replacing, deleted, or causing disconnection).

EVENT_PARAM_RNC_ID_1
Identity of the controlling RNC (CRNC) for the first cell in the 13 -
active set.

EVENT_PARAM_RNC_ID_2
Identity of the controlling RNC (CRNC) for the second cell in 13 -
the active set.

EVENT_PARAM_RNC_ID_3
Identity of the controlling RNC (CRNC) for the third cell in the 13 -
active set.

EVENT_PARAM_RNC_ID_4
Identity of the controlling RNC (CRNC) for the fourth cell in the 13 -
active set.

EVENT_PARAM_RNC_ID_EVALUATED
Identity of the controlling RNC (CRNC) for the cell that caused 13 -
the measurement report (added, replacing, deleted, or causing
disconnection).

EVENT_PARAM_IRAT_C_I
For IRATHO to GSM, Cell identity (cId) of the ExternalGsmCell. 17 -
For IRATHO to GAN, Cell identity (ganCId) of the GanC.

EVENT_PARAM_IRAT_LAC
For IRATHO to GSM, Location area code (lac) of the 25 -
ExternalGsmCell. For IRATHO to GAN, Location area code (lac)
of the GanC.

EVENT_PARAM_IRAT_PLMN_ID
For IRATHO to GSM, Public Land Mobile Network identity 17 -
(plmnId = mcc+mnc) of the ExternalGsmCell. For IRATHO to
GAN, Public Land Mobile Network identity (plmnId) of the
GanC.

EVENT_PARAM_IRAT_RSSI
For IRATHO to GSM, Received Signal Strength Indicator (RSSI) 7 -
value for evaluated GSM cell. For IRATHO to GAN, Received
Signal Strength Indicator (RSSI) value for evaluated GAN cell.

EVENT_PARAM_IRAT_CELL_ID_1
Inter-Radio Access Technology (IRAT) cell identity for the first 6 -
GSM cell in the report.

EVENT_PARAM_IRAT_CELL_ID_2
Inter-Radio Access Technology (IRAT) cell identity for the 6 -
second GSM cell in the report.

EVENT_PARAM_IRAT_CELL_ID_3
Inter-Radio Access Technology (IRAT) cell identity for the third 6 -
GSM cell in the report.

EVENT_PARAM_IRAT_CELL_ID_4
Inter-Radio Access Technology (IRAT) cell identity for the 6 -
fourth GSM cell in the report.

EVENT_PARAM_RLS_ID_1
Identity of the first Radio Link Set, unique within a UE. 6 -

EVENT_PARAM_RLS_ID_2
Identity of the second Radio Link Set, unique within a UE. 6 -

EVENT_PARAM_RLS_ID_3
Identity of the third Radio Link Set, unique within a UE. 6 -
EVENT_PARAM_RLS_ID_4
Identity of the fourth Radio Link Set, unique within a UE. 6 -

EVENT_PARAM_RLS_TAG_1
Tag of the first Radio Link Set (OK or failed). 2 EVENT_VALUE_O
EVENT_VALUE_F

EVENT_PARAM_RLS_TAG_2
Tag of the second Radio Link Set (OK or failed) 2 EVENT_VALUE_O
EVENT_VALUE_F

EVENT_PARAM_RLS_TAG_3
Tag of the third Radio Link Set (OK or failed) 2 EVENT_VALUE_O
EVENT_VALUE_F

EVENT_PARAM_RLS_TAG_4
Tag of the fourth Radio Link Set (OK or failed) 2 EVENT_VALUE_O
EVENT_VALUE_F

EVENT_PARAM_UL_SCRAMBLING_CODE
Uplink scrambling code allocated. 25 -

EVENT_PARAM_SPREADING_FACTOR_NORM_MODE
Spreading factor for normal mode. 10 -

EVENT_PARAM_SPREADING_FACTOR_COMP_MODE
Spreading factor for compressed mode. 10 -

EVENT_PARAM_CHANGED_NODE_SPREADING_FACTOR
Changed code tree node spreading factor. 10 -

EVENT_PARAM_CHANGED_NODE_CODE_NUMBER
Changed code tree node code number. 9 -

EVENT_PARAM_CODE_TREE_LOAD
Code tree load; value to be divided by 256. 10 -

EVENT_PARAM_SCRAMBLING_CODE_REP_CELL_1
Scrambling code number of the first cell in the report. 10 -
EVENT_PARAM_UARFCN_DL_REP_CELL_1
Downlink frequency of the first cell in the report. See the 3GPP 16 -
specification TS 25.104 for details about frequencies.

UARFCN = UTRA Absolute Radio Frequency Channel

EVENT_PARAM_UARFCN_UL_REP_CELL_1
Uplink frequency of the first cell in the report. See the 3GPP 16 -
specification TS 25.104 for details about frequencies.

UARFCN = UTRA Absolute Radio Frequency Channel

EVENT_PARAM_SCRAMBLING_CODE_REP_CELL_2
Scrambling code number of the second cell in the report. 10 -

EVENT_PARAM_UARFCN_DL_REP_CELL_2
Downlink frequency of the second cell in the report. See the 16 -
3GPP specification TS 25.104 for details about frequencies.

UARFCN = UTRA Absolute Radio Frequency Channel

EVENT_PARAM_UARFCN_UL_REP_CELL_2
Uplink frequency of the second cell in the report. See the 3GPP 16 -
specification TS 25.104 for details about frequencies.

UARFCN = UTRA Absolute Radio Frequency Channel

EVENT_PARAM_SCRAMBLING_CODE_REP_CELL_3
Scrambling code number of the third cell in the report 10 -

EVENT_PARAM_UARFCN_DL_REP_CELL_3
Downlink frequency of the third cell in the report. See the 3GPP 16 -
specification TS 25.104 for details about frequencies.

UARFCN = UTRA Absolute Radio Frequency Channel

EVENT_PARAM_UARFCN_UL_REP_CELL_3
Uplink frequency of the third cell in the report. See the 3GPP 16 -
specification TS 25.104 for details about frequencies.

UARFCN = UTRA Absolute Radio Frequency Channel

EVENT_PARAM_SCRAMBLING_CODE_REP_CELL_4
Scrambling code number of the fourth cell in the report. 10 -
EVENT_PARAM_UARFCN_DL_REP_CELL_4
Downlink frequency of the fourth cell in the report. See the 16 -
3GPP specification TS 25.104 for details about frequencies.

UARFCN = UTRA Absolute Radio Frequency Channel

EVENT_PARAM_UARFCN_UL_REP_CELL_4
Uplink frequency of the fourth cell in the report. See the 3GPP 16 -
specification TS 25.104 for details about frequencies.

UARFCN = UTRA Absolute Radio Frequency Channel

EVENT_PARAM_MEAS_REPORTS_IN_BUFFER_2B
Number of reports in the event 2b buffer. 2 -

EVENT_PARAM_C_ID_NU_FREQ
Cell identity for the proposed unused frequency cell. 17 -

EVENT_PARAM_RNC_ID_NU_FREQ
RNC identity for the proposed unused frequency cell. 13 -

EVENT_PARAM_CPICH_EC_NU_FREQ_CELL
Common Pilot Channel (CPICH) Ec/No for the proposed unused 7 -
frequency cell.

EVENT_PARAM_RSCP_NU_FREQ_CELL
Common Pilot Channel (CPICH) Received Signal Code Power 8 -
(RSCP) for the proposed unused frequency cell.

EVENT_PARAM_RNC_MP_ID
The identity of the Main Processor (MP) where an error 7 For RNC 3810 se
situation has impact on ongoing event recordings. The MP can
be of type Module, Central, RANAP, RNSAP and O&M For RNC 3820 se

EVENT_PARAM_SCRAMBLING_CODE_TRIGGER_CELL
For INTERNAL_SOHO_DS_MISSING_NEIGHBOUR: Downlink 10 -
primary scrambling code number for the cell that triggered the
measurement report, that is, the best cell in event results, not
the best cell in the Active Set. For
INTERNAL_SOHO_DS_UNMONITORED_NEIGHBOUR: Downlink
primary scrambling code number for the cell that triggered the
event, that is, the detected and reported unmonitored neighbor
cell.
EVENT_PARAM_CPICH_EC_NO_TRIGGER_CELL
For INTERNAL_SOHO_DS_MISSING_NEIGHBOUR: Downlink 7 -
Common Pilot Channel (CPICH) Ec/No for the cell that
triggered the measurement report, that is, the best cell in
event results, not the best cell in the Active Set. For
INTERNAL_SOHO_DS_UNMONITORED_NEIGHBOUR: Downlink
CPICH Ec/No for the cell that triggered the event, that is, the
detected and reported unmonitored neighbor cell.

See 3GPP spec 25.133 for mapping between reported value


and the actual physical measured value. The reporting range
for CPICH Ec/Io is from -24..0 dB, resolution 0.5.

EVENT_PARAM_RSCP_TRIGGER_CELL
For INTERNAL_SOHO_DS_MISSING_NEIGHBOUR: Received 8
Signal Code Power (RSCP) for the cell that triggered the
measurement report, that is, the best cell in event results, not
the best cell in the Active Set. For
INTERNAL_SOHO_DS_UNMONITORED_NEIGHBOUR: RSCP for
the cell that triggered the event, that is, the detected and
reported unmonitored neighbor cell.

See 3GPP spec 25.133 for mapping between reported value


and the actual physical measured value. The reporting range
for Common Pilot Channel (CPICH) RSCP is from -115..-25
dBm, resolution 1.

EVENT_PARAM_SCRAMBLING_CODE_ADDITIONAL_CELL1
DL primary scrambling code for the cell that was last added to 10 -
the AS or is currently being added to the AS.

EVENT_PARAM_CPICH_EC_NO_ADDITIONAL_CELL1
Downlink Common Pilot Channel (CPICH) Ec/No for additional 7 -
cell 1 in the measured results.

See 3GPP spec 25.133 for mapping between reported value


and the actual physical measured value. The reporting range
for CPICH Ec/Io is from -24..0 dB, resolution 0.5.

EVENT_PARAM_RSCP_ADDITIONAL_CELL1
Received Signal Code Power (RSCP) for the additional cell 1 in 8 -
the measured results.

See 3GPP spec 25.133 for mapping between reported value


and the actual physical measured value. The reporting range
for Common Pilot Channel (CPICH) RSCP is from -115..-25
dBm, resolution 1.
EVENT_PARAM_SCRAMBLING_CODE_ADDITIONAL_CELL2
Downlink primary scrambling code number for cell 2 in the 10 -
measured results.

EVENT_PARAM_CPICH_EC_NO_ADDITIONAL_CELL2
Downlink Common Pilot Channel (CPICH) Ec/No for additional 7 -
cell 2 in measured results.

See 3GPP spec 25.133 for mapping between reported value


and the actual physical measured value. The reporting range
for CPICH Ec/Io is from -24..0 dB, resolution 0.5.

EVENT_PARAM_RSCP_ADDITIONAL_CELL2
Received Signal Code Power (RSCP) for additional cell 2 in the 8 -
measured results.

See 3GPP spec 25.133 for mapping between reported value


and the actual physical measured value. The reporting range
for Common Pilot Channel (CPICH) RSCP is from -115..-25
dBm, resolution 1.

EVENT_PARAM_C_ID_TRIGGER_CELL
Cell identifier of the unmonitored cell. 17 -

EVENT_PARAM_RNC_ID_TRIGGER_CELL
Controlling RNC (C-RNC) identifier for the unmonitored cell. 13 -

EVENT_PARAM_UE_POS_METHOD
Selected positioning method. 3 EVENT_VALUE_C
EVENT_VALUE_C
EVENT_VALUE_C
EVENT_VALUE_A

EVENT_PARAM_NR_GPS_SATELLITES
The total number of satellites sent to the UE when the A-GPS 6 -
positioning measurements were started.

EVENT_PARAM_MEASUREMENT_TIME
UE positioning measurement time for a UE. The time starts 10 -
when the RNC receives the Location Reporting Control (RANAP)
message from the Core Network, and stops when the RNC
sends the Location Report (RANAP) message to the Core
Network.
EVENT_PARAM_REQUIRED_HORIZONTAL_ACCURACY
Accuracy Code according to the Location Reporting Control 8 -
(RANAP) message.

EVENT_PARAM_ACHIEVED_HORIZONTAL_ACCURACY
If the Cell Id method is selected, this parameter is calculated 8 -
based on the estimated Cell Id area; in other words, equal to
round(ln(1+1/10*sqrt (area/pi))/ln(1.1)). If the A-GPS method
is selected this parameter is equal to the calculated
uncertaintyCode or horizontalUncertainty parameters. If
neither of these parameters are available, the event parameter
must be set to invalid.

EVENT_PARAM_REQUIRED_VERTICAL_ACCURACY
Vertical Accuracy Code according to the Location Reporting 8 -
Control (RANAP) message.

EVENT_PARAM_ACHIEVED_VERTICAL_ACCURACY
Uncertainty Altitude according to the Measurement Report 9 -
(RRC) message. The value 128 means that the configurable
parameter AgpsPositioning.uncertaintyAltitude is used instead
of the IE in the RRC message.

EVENT_PARAM_UE_REFERENCE_POSITION
Indicates if the UE reference position is based on a Cell Id 2 EVENT_VALUE_P
preestimate or the configurable parameter EVENT_VALUE_C
AgpsPosition.utranRnsPosition.

Reported as 'Not Applicable' for SAS Centric UE Positioning.

EVENT_PARAM_LATITUDE_SIGN
Latitude sign (North, South) for the reported Position Format 2 EVENT_VALUE_N
Point or Point with Uncertainty Circle. EVENT_VALUE_S

EVENT_PARAM_LATITUDE
Latitude value (N), derived by the formula: N <= (2^23) * 24 -
(X / 90) < (N + 1), where X is the latitude in degrees
(0°..90°). This is the latitude degrees for the reported Position
Format Point or Point with Uncertainty Circle.

EVENT_PARAM_LONGITUDE_SIGN
Longitude sign (East, West) for the reported Position Format 2 EVENT_VALUE_E
Point or Point with Uncertainty Circle. EVENT_VALUE_W
EVENT_PARAM_LONGITUDE
If Longitude sign is equal to East, the Longitude value (N) is 25 -
derived by the formula N <= (2^24)*(X/360) < N+1, where X
is the longitude in degrees (0°..180°). If Longitude sign is
equal to West, the Longitude value (N) is derived by the
formula N <= (2^24)*(-X/360) < N+1, where X is the
longitude in degrees (-180°..0°). This is the longitude degrees
for the reported Position Format Point or Point with Uncertainty
Circle.

EVENT_PARAM_ALTITUDE_DIRECTION
Direction of altitude. 2 EVENT_VALUE_H
EVENT_VALUE_D

EVENT_PARAM_ALTITUDE
Altitude. 16 -

EVENT_PARAM_UNCERTAINTY_SEMI_MAJOR
Uncertainty semi-major. The uncertainty "r" in meters is 8 -
derived from the value N by r=10*(1.1^N-1).

EVENT_PARAM_UNCERTAINTY_SEMI_MINOR
Uncertainty semi-minor. The uncertainty "r" in meters is 8 -
derived from the value N by r=10*(1.1^N-1).

EVENT_PARAM_ORIENTATION_MAJOR_AXIS
Orientation of major axis. The relation between the value (N) 9 -
and the angle (a) in degrees it describes is 2N <= a <
2*(N+1) .

EVENT_PARAM_CONFIDENCE
Confidence. See the 3GPP specification TS 23.032 Universal 8 -
Geographical Area Description (GAD) for confidence values
greater than 100.

EVENT_PARAM_HS_DSCH_PHYSICAL_LAYER_CATEGORY
High Speed Downlink Shared Channel (HS-DSCH) physical 8 EVENT_VALUE_N
layer category, for details see 3GPP TS 25.331 and 3GPP TS EVENT_VALUE_C
25.306. Note that for RAB Establishments of other RABs than
PS Interactive/Background RABs, the "INVALID_VALUE" is There are 64 par
recorded for this parameter. EVENT_VALUE_C

EVENT_PARAM_E_DCH_AND_OR_HS_DSCH_CELL_SELECTION_RESULT
Result of the Serving HS-DSCH cell selection. 4 EVENT_VALUE_N
EVENT_VALUE_H
Note that for RAB Establishments of other RABs than PS
Interactive/Background RABs, the "INVALID_VALUE" shall be EVENT_VALUE_H
recorded for this parameter. EVENT_VALUE_N
EVENT_VALUE_N

EVENT_PARAM_E_DCH_PHYSICAL_LAYER_CATEGORY
HS-DSCH physical layer category, for details see 3GPP TS 8 EVENT_VALUE_N
25.331 and 3GPP TS 25.306. EVENT_VALUE_C

Note that for RAB Establishments of other RABs than PS There are 64 par
Interactive/Background RABs, the "INVALID_VALUE" shall be EVENT_VALUE_C
recorded for this parameter.

EVENT_PARAM_E_DCH_AND_OR_HS_DSCH_CELL_ID
For RAB Establishment: Cell ID of the serving E-DCH/HS-DSCH 17
cell at the conclusion of the RAB Establishment. Only valid if
the value of "Serving E-DCH/HS-DSCH cell selection result" is 1
or 2. For RAB Release: Cell ID of the serving E-DCH/HS-DSCH
cell at the time of the RAB Release.

EVENT_PARAM_REQUESTED_SERVICE_CLASS
Requested service class (guaranteed, non-guaranteed). Traffic 3 EVENT_VALUE_G
class on DL in SRNC or traffic class for whole connection in EVENT_VALUE_N
DRNC.

EVENT_PARAM_REQUESTED_SETUP_CLASS
Requested setup class (non-handover, handover). 2 EVENT_VALUE_H
EVENT_VALUE_N

EVENT_PARAM_REQUESTED_ORIGIN
Origination of the request (Iur or non-Iur). 2 EVENT_VALUE_I
EVENT_VALUE_N

EVENT_PARAM_REQUESTED_SF_DL
Requested downlink spreading factor. 10 -

EVENT_PARAM_REQUESTED_SF_UL
Requested uplink spreading factor. 10 -

EVENT_PARAM_REQUESTED_COMPRESSED_MODE
Request for compressed mode or not. 2 EVENT_VALUE_Y
EVENT_VALUE_N
EVENT_PARAM_REQUESTED_RAB_STATE
Reserved for future, the current value is 6 EVENT_VALUE_I
‘EVENT_VALUE_INVALID’. There are 32 diff
EVENT_VALUE_I

EVENT_PARAM_CURRENT_SF_DL
Current downlink spreading factor. 10 -

EVENT_PARAM_CURRENT_SF_UL
Current uplink spreading factor. 10 -

EVENT_PARAM_CURRENT_RAB_STATE
Reserved for future, the current value is 6 EVENT_VALUE_I
‘EVENT_VALUE_INVALID’. There are 32 diff
EVENT_VALUE_I

EVENT_PARAM_BLOCKING_PROCEDURE
Procedure which is blocked (‘RRC’ or ‘Other’). 4 EVENT_VALUE_R
EVENT_VALUE_O
EVENT_VALUE_I
EVENT_VALUE_I
EVENT_VALUE_I
EVENT_VALUE_I
EVENT_VALUE_I
EVENT_VALUE_I

EVENT_PARAM_BLOCK_REASON
Main failure reason for cell admission request. 6 EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_N
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_PARAM_BLOCK_REASON - continued
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_M
EVENT_VALUE_M
EVENT_VALUE_R
EVENT_VALUE_T
EVENT_VALUE_T

EVENT_PARAM_BLOCK_TYPE
Reserved, current value is ‘EVENT_VALUE_INVALID’. 4 EVENT_VALUE_I
EVENT_VALUE_I
EVENT_VALUE_I
EVENT_VALUE_I
EVENT_VALUE_I
EVENT_VALUE_I
EVENT_VALUE_I
EVENT_VALUE_I

EVENT_PARAM_BLOCK_ADMISSION_POLICY_LEVEL
Relevant admission policy level (that is BLOCK_REASON 16 -
value).

EVENT_PARAM_LOCAL_CELL_GROUP_ID
The Local Cell Group ID represents resources in the Node B, 29 -
which have been pooled from a capacity point of view.

See the NBAP 3GPP specification for a detailed parameter


description.

EVENT_PARAM_RBS_ID
Iub connection identity (rbsId). 32 -

Note: The value is not used by RNC. It is used in OSS-RC for


correlation between RNC and RBS.
EVENT_PARAM_CAPACITY_CREDITS_UL
Local cell group capacity in UL. 17 -

EVENT_PARAM_CAPACITY_CREDITS_DL
Local cell group capacity in DL. 17 -

EVENT_PARAM_CONSUMED_CREDITS_UL
Consumed credits after update for local cell group in UL. 18 -

EVENT_PARAM_CONSUMED_CREDITS_DL
Consumed credits after update for local cell group in DL. 18 -

EVENT_PARAM_C_ID_SOURCE
Source Cell identity. 17 -

EVENT_PARAM_CPICH_EC_NO_SOURCE_CELL
Common Pilot Channel (CPICH) Ec/No in source cell. 7 -

The range for the measured CPICH Ec/Io value is -24..0 dB,
resolution 0.5, giving a range 0..49.

See the 3GPP specification 25.133 for mapping of the reported


and the measured value.

EVENT_PARAM_CPICH_RSCP_SOURCE_CELL
Common Pilot Channel (CPICH) Received Signal Code Power 8 -
(RSCP) in source cell.

The range for the measured CPICH RSCP value is -115..-25


dBm, where 0 means CPICH RSCP < 115 and 91 means CPICH
RSCP >= -25, resolution: 1, unit: dBm).

See the 3GPP spec 25.133 for mapping of the reported and the
measured value.

EVENT_PARAM_C_ID_TARGET
Target cell identity. 17 -

EVENT_PARAM_CPICH_EC_NO_TARGET_CELL
Common Pilot Channel (CPICH) Ec/No in target cell. 7 -

The range for the measured CPICH Ec/Io value is -24..0 dB,
resolution 0.5, giving a range 0..49.
See 3GPP specification 25.133 for mapping of the reported and
the measured value.

EVENT_PARAM_CPICH_RSCP_TARGET_CELL
Common Pilot Channel (CPICH) Received Signal Code Power 8 -
(RSCP) in target cell.

The range for the measured CPICH RSCP value is -115..-25


dBm, where 0 means CPICH RSCP < 115 and 91 means CPICH
RSCP >= -25, resolution: 1, unit: dBm)

See the 3GPP spec 25.133 for mapping of the reported and the
measured value.

EVENT_PARAM_SELECTED_CELL
Best cell or not. 2 EVENT_VALUE_B
EVENT_VALUE_N

EVENT_PARAM_PATHLOSS
Pathloss used by Serving HS-DSCH Cell Selection. If selected 10 -
cell is best cell, pathloss is set to invalid value
(EVENT_VALLUE_INVALID).

The value is reported in the range 15..170 dB with a resolution


of 1.

EVENT_PARAM_UARFCN_SOURCE
Source cell for downlink frequency. 15 -

See the 3GPP spec. 25.104 for a description of possible


reported values.

EVENT_PARAM_UARFCN_TARGET
Target cell for downlink frequency. 15 -

See the 3GPP spec. 25.104 for a description of possible


reported values.

EVENT_PARAM_UL_SYNC_STATUS_RLS1
Uplink synch status. 2 EVENT_VALUE_R
EVENT_VALUE_R

EVENT_PARAM_NUMBER_OF_USERS_ASSIGNED_TO_PHYS_HS_CHAN
Number of users assigned to the physical HSDPA channels. 10 -
EVENT_PARAM_NUMBER_OF_EDCH_USERS_IN_SERVING_CELL
Number of E-DCH users in the serving cell. 8 -

EVENT_PARAM_NUMBER_OF_EDCH_USERS_IN_NON_SERVING_CELL
Number of E-DCH users in the non-serving cell. 10 -

EVENT_PARAM_NR_OF_CONNECTIONS_SF4_UL
Number of admitted radio links using uplink spreading factor 4. 8 -

EVENT_PARAM_PROTOCOL_ID
Protocol identifier. 4 -

The protocol identifier represented as: 0=RRC "3GPP TS


25.331 V8.6.0", 1=NBAP "3GPP TS 25.433 V8.4.0", 2=RANAP
"3GPP TS 25.413 V7.8.0", 4=RNSAP "3GPP TS 25.423 V7.7.0",
or 5=INTERNAL_EVENT, 6=PCAP "3GPP TS 25.453 V7.6.0", or
7=SABP "3GPP TS 25.419 V6.2.0".

EVENT_PARAM_UE_POS_UNSUCC_CAUSE
Part of the A-GPS positioning attempt sequence that was 5 EVENT_VALUE_H
unsuccessful. EVENT_VALUE_N
EVENT_VALUE_I
EVENT_VALUE_R
EVENT_VALUE_G
EVENT_VALUE_G
EVENT_VALUE_G
EVENT_VALUE_G
EVENT_VALUE_G
EVENT_VALUE_N

EVENT_PARAM_UARFCN_DL_NON_USED_FREQ_1
Downlink UTRA Absolute Radio Frequency Channel (UARFCN) 15 -
for the first frequency of inter-frequency neighbors.

See the 3GPP specification TS 25.104 for details about


frequencies.

EVENT_PARAM_UARFCN_DL_NON_USED_FREQ_2
Downlink UTRA Absolute Radio Frequency Channel (UARFCN) 15 -
for the second frequency of inter-frequency neighbors.

See the 3GPP specification TS 25.104 for details about


frequencies.

EVENT_PARAM_UARFCN_DL_NON_USED_FREQ_3
Downlink UTRA Absolute Radio Frequency Channel (UARFCN) 15 -
for the third frequency of inter-frequency neighbors. This
corresponds to the first not accepted non-used frequency.

See the 3GPP specification TS 25.104 for details about


frequencies.

EVENT_PARAM_TRIGGER_POINT
Point in sequence where this GPEH event was triggered. 3 EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_S

EVENT_PARAM_UTRAN_RANAP_CAUSE
Cause value sent in RANAP RAB Assignment Response, RANAP 11 -
IU Release Request or RANAP Local RAB Release.

EVENT_PARAM_DATA_IN_DL_RLC_BUFFERS
Number of released RABs (acknowledged mode) with payload 6 -
data in the downlink RLC buffers when the release was
triggered.

EVENT_PARAM_RAN_DISCONNECTION_CODE
Code indicating the reason of the drop. For disconnection code 6 -
details, see Table 11.

EVENT_PARAM_RAN_DISCONNECTION_SUBCODE
Sub-code indicating further details about the reason of the 5 -
drop.

EVENT_PARAM_RAN_ID_PARAMETER
Additional information about the disconnection. 17 -

EVENT_PARAM_CPM
Indicates whether compressed mode was activated or not. 3 EVENT_VALUE_O
EVENT_VALUE_H
EVENT_VALUE_S

EVENT_PARAM_SCRAMBLING_CODE_ADDED_CELL
Downlink primary scrambling code for the cell that was last 10 -
added to the Active Set or is currently being added to the
Active Set.

EVENT_PARAM_CPICH_EC_NO_ADDED_CELL
Common Pilot Channel (CPICH) Ec/No for the cell that was last 7 -
added to the Active Set, or is currently being added to the
Active Set.

The range for the measured CPICH Ec/Io value is -24..0 dB,
resolution 0.5, giving a range 0..49.

See the 3GPP specification 25.133 for mapping of the reported


and the measured value.

EVENT_PARAM_RSCP_CELL_1_ADDED_CELL
Common Pilot Channel (CPICH) Received Signal Code Power 8 -
(RSCP) for the cell that was last added to the Active Set, or is
currently being added to the Active Set.

The range for the measured CPICH RSCP value is -115..-25


dBm.

See the 3GPP specification 25.133 for mapping of the reported


and the measured value.

EVENT_PARAM_CNHHO_TYPE
The type of Core Network Hard Handover (CNHHO) 2 EVENT_VALUE_I
EVENT_VALUE_I

EVENT_PARAM_IUR_STATUS
The state of the Iur connection when making Core Network 2 EVENT_VALUE_I
Hard Handover (CNHHO). EVENT_VALUE_I

EVENT_PARAM_UL_THROUGHPUT
Uplink (UL) Radio Link Control (RLC) throughput including 15 -
retransmissions.

EVENT_PARAM_DL_THROUGHPUT
Downlink (DL) Radio Link Control (RLC) throughput including 15 -
retransmissions.
EVENT_PARAM_NR_OF_CONNECTIONS_SF8_UL
Number of radio links with uplink (UL) spreading factor (SF) = 8 -
8.

EVENT_PARAM_NR_OF_CONNECTIONS_SF16_UL
Number of radio links with uplink (UL) spreading factor (SF) = 8 -
16.

EVENT_PARAM_SOURCE_CONF
The UeRc identity of the source state. 8 -

Reported as 'Not Applicable' for MBMS, which indicates that the


event is captured due to MBMS.

See Section 3.2 for details about UeRc identities.

EVENT_PARAM_TARGET_CONF
The UeRc identity of the target state. 8 -

Related to INTERNAL_OUT_HARD_HANDOVER_SUCCESS is
that this parameter represents the UeRc which is configured
when the HHO fails, which for example could be fall back to the
source state.

Reported as 'Not Applicable' for MBMS, which indicates that the


event is captured due to MBMS.

See Section 3.2 for details about UeRc identities.

EVENT_PARAM_TARGET_CAP
Specifies the capabilities of the target cell for the cell selection. 2 EVENT_VALUE_D
EVENT_VALUE_E

EVENT_PARAM_UEPOS_INITIAL_CONF
The UeRc identity when initiating the positioning attempt. 8 -

See Section 3.2 for details about UeRc identities.

EVENT_PARAM_UEPOS_FINAL_CONF
The UeRc identity when the positioning attempt has been 8 -
completed, or when the attempt has failed and another method
is attempted instead.

See Section 3.2 for details about UeRc identities.


EVENT_PARAM_MEASUREMENT_TYPE
Defines the measurement type, which is either of "Transport Not -
Channel BER", "UL DCH BLER" or "RLC Buffer Information". bitpacked
(1 byte)

EVENT_PARAM_MEASUREMENT_LENGTH
Length, in bytes, of the following encoded protocol message. Not -
bitpacked
(2 bytes)

EVENT_PARAM_UL_INT_CELL1
Last used uplink interference measurement (equals "Received 11 -
Total Wideband Power value") for Cell 1 in the active set, which
is the best cell.

EVENT_PARAM_UL_INT_CELL2
Last used uplink interference measurement (equals "Received 11 -
Total Wideband Power value") for Cell 2 in the active set.

EVENT_PARAM_UL_INT_CELL3
Last used uplink interference measurement (equals "Received 11 -
Total Wideband Power value") for Cell 3 in the active set.

EVENT_PARAM_UL_INT_CELL4
Last used uplink interference measurement (equals "Received 11 -
Total Wideband Power value") for Cell 4 in the active set.

EVENT_PARAM_C_ID_SERV_HSDSCH_CELL
Cell identity of the serving High Speed Downlink Shared 17 -
Channel (HS-DSCH) cell.

EVENT_PARAM_C_ID_1_SECONDARY_SERV_HSDSCH_CELL
Indicates the Cell Id of the first secondary HS-DSCH cell for 17 -
Multi Carrier connections.

EVENT_PARAM_CRNC_ID_SERV_HSDSCH_CELL
Controlling RNC (CRNC) identity of the serving High Speed 13 -
Downlink Shared Channel (HS-DSCH) cell.

EVENT_PARAM_EC_NO_SERV_HSDSCH_CELL
Common Pilot Channel (CPICH)-Ec/N0 of the serving High 7 -
Speed Downlink Shared Channel (HS-DSCH) cell.

The range for the measured CPICH Ec/Io value is -24 ...0 dB,
resolution 0.5, giving a range 0..49.

See the 3GPP specification 25.133 for mapping of the reported


and the measured value.

EVENT_PARAM_RSCP_SERV_HSDSCH_CELL
Common Pilot Channel Received Signal Code Power (CPICH- 8 -
RSCP) of the serving High Speed Downlink Shared Channel
(HS-DSCH) cell.

The range for the measured CPICH RSCP is -115 ...-25 dBm,
resolution 1.

See the 3GPP specification 25.133 for mapping of the reported


and the measured value.

EVENT_PARAM_AFFECTED_SCANNER_TYPE
Type of scanner affected by a recording interruption. 3 EVENT_VALUE_L
EVENT_VALUE_H
EVENT_VALUE_A

EVENT_PARAM_EXCEPTION_CLASS
- 9 EVENT_VALUE_P
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_T
EVENT_VALUE_T
EVENT_VALUE_I
EVENT_VALUE_I
EVENT_VALUE_U
EVENT_VALUE_N
EVENT_VALUE_R
EVENT_VALUE_P
EVENT_VALUE_I
EVENT_VALUE_I
EVENT_VALUE_U
EVENT_VALUE_S

EVENT_PARAM_CAUSE_VALUE
- 9 EVENT_VALUE_C
EVENT_VALUE_R
EVENT_VALUE_N
EVENT_VALUE_A
EVENT_VALUE_N
EVENT_VALUE_C
EVENT_VALUE_I
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_P
EVENT_VALUE_E
EVENT_VALUE_C
EVENT_VALUE_N
EVENT_VALUE_A
EVENT_VALUE_C
EVENT_VALUE_C
EVENT_PARAM_CAUSE_VALUE - continued
EVENT_VALUE_A
EVENT_VALUE_N
EVENT_VALUE_A
EVENT_VALUE_A
EVENT_VALUE_R
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_D
EVENT_VALUE_E
EVENT_VALUE_A
EVENT_VALUE_H
EVENT_VALUE_M
EVENT_VALUE_M
EVENT_PARAM_CAUSE_VALUE - continued
EVENT_VALUE_C
EVENT_VALUE_F
EVENT_VALUE_F
NOT_USED
NOT_USED
EVENT_VALUE_I
EVENT_VALUE_N
EVENT_VALUE_I
EVENT_VALUE_I
EVENT_VALUE_N
EVENT_VALUE_I
EVENT_VALUE_N
EVENT_VALUE_R
EVENT_VALUE_O
EVENT_VALUE_I
EVENT_VALUE_A
EVENT_PARAM_CAUSE_VALUE - continued
EVENT_VALUE_G
EVENT_VALUE_L
EVENT_VALUE_P
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_I
EVENT_VALUE_A
EVENT_VALUE_R
EVENT_VALUE_N
EVENT_PARAM_CAUSE_VALUE - continued
NOT_USED
NOT_USED
NOT_USED
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
NOT_USED
NOT_USED
NOT_USED
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
NOT_USED
NOT_USED
EVENT_VALUE_M
EVENT_VALUE_H
NOT_USED
EVENT_VALUE_C
EVENT_VALUE_C
EVENT_VALUE_C
EVENT_PARAM_CAUSE_VALUE - continued
EVENT_VALUE_N
NOT_USED
EVENT_VALUE_N
EVENT_VALUE_U
EVENT_VALUE_C
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_U
EVENT_VALUE_R
NOT_USED
EVENT_VALUE_R
EVENT_VALUE_P
EVENT_VALUE_C
EVENT_VALUE_S
EVENT_VALUE_S
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_I
EVENT_PARAM_CAUSE_VALUE - continued
EVENT_VALUE_I
EVENT_VALUE_N
NOT_USED
EVENT_VALUE_N
NOT_USED
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
NOT_USED
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_P
NOT_USED
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_C
EVENT_VALUE_C
EVENT_PARAM_CAUSE_VALUE - continued
EVENT_VALUE_F
EVENT_VALUE_F
EVENT_VALUE_E
EVENT_VALUE_C
EVENT_VALUE_M
EVENT_VALUE_H

EVENT_PARAM_EXTENDED_CAUSE_VALUE
- 9 EVENT_VALUE_E
EVENT_VALUE_E
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_C
EVENT_VALUE_C
EVENT_VALUE_I
EVENT_VALUE_I
NOT_USED
NOT_USED
NOT_USED
NOT_USED
EVENT_VALUE_N
EVENT_VALUE_R
EVENT_PARAM_EXTENDED_CAUSE_VALUE - continued
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_T
EVENT_VALUE_N
EVENT_VALUE_M
EVENT_VALUE_M
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_T
EVENT_PARAM_EXTENDED_CAUSE_VALUE - continued
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_C
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_C
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_M
EVENT_PARAM_EXTENDED_CAUSE_VALUE - continued
EVENT_VALUE_R
EVENT_VALUE_N
EVENT_VALUE_R
EVENT_VALUE_U
EVENT_VALUE_P
EVENT_VALUE_C
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_U
EVENT_VALUE_P
EVENT_VALUE_N
EVENT_VALUE_U
EVENT_PARAM_EXTENDED_CAUSE_VALUE - continued
EVENT_VALUE_D
EVENT_VALUE_U
EVENT_VALUE_D
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_P
EVENT_VALUE_H
EVENT_VALUE_I
EVENT_VALUE_R
EVENT_VALUE_A
EVENT_VALUE_R
EVENT_VALUE_C
EVENT_VALUE_C
EVENT_VALUE_R
EVENT_PARAM_EXTENDED_CAUSE_VALUE - continued
EVENT_VALUE_G
EVENT_VALUE_U
EVENT_VALUE_N
EVENT_VALUE_R
EVENT_VALUE_T
EVENT_VALUE_F
EVENT_VALUE_N
EVENT_VALUE_T
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_A
EVENT_VALUE_N
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_I
EVENT_VALUE_S
EVENT_PARAM_EXTENDED_CAUSE_VALUE - continued
EVENT_VALUE_C
EVENT_VALUE_H
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_U
EVENT_VALUE_U
EVENT_VALUE_D
EVENT_VALUE_R
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_I
EVENT_VALUE_I
EVENT_VALUE_T
EVENT_VALUE_O
EVENT_VALUE_O
EVENT_VALUE_C
EVENT_VALUE_C
EVENT_VALUE_E
EVENT_VALUE_E
EVENT_PARAM_EXTENDED_CAUSE_VALUE - continued
EVENT_VALUE_R
EVENT_VALUE_H

EVENT_PARAM_SEVERITY_INDICATOR
- 2 -

EVENT_PARAM_CN_RANAP_CAUSE
RANAP Cause received Iu Release Command or RAB 11 -
Assignment Request (see 3GPP TS 25.413).

EVENT_PARAM_ARP
ARP priority level of: 5 -

- Established RAB

- Admission request

- Switched RAB

EVENT_PARAM_PREEMPT_CAP
ARP preemption capability of the established RAB. 2 EVENT_VALUE_M
EVENT_VALUE_S

EVENT_PARAM_NO_OF_NGUAR_CONN_TARGETED
Number of best effort users to be switched or terminated. 8 -

EVENT_PARAM_NO_OF_NGUAR_CONN_TARGETED_IUR
Number of best effort users to be terminated over Iur. 8 -

EVENT_PARAM_NO_OF_GUAR_CONN_TARGETED
Number of guaranteed connections, not originating over Iur, 8 -
targeted due to overload resolve actions.

EVENT_PARAM_NO_OF_GUAR_CONN_TARGETED_IUR
Number of guaranteed connections originating over Iur 8 -
targeted due to overload resolve actions, or number of PS
streaming parts terminated due to a congestion resolve action.

EVENT_PARAM_FILTERED_POWER
RNC filtered DL power. 11 -

The range for the measured power value is 0..100%, resolution


0.1, giving a range 0..1000.

EVENT_PARAM_SCANNER_ID
- 24 -

EVENT_PARAM_RNC_ID_SOURCE
Identity of the CRNC of the source High Speed (HS) serving 13 -
cell.

EVENT_PARAM_RNC_ID_TARGET
Identity of the CRNC of the target High Speed (HS) serving 13 -
cell.

EVENT_PARAM_PREVIOUS_DOWNLINK_STATE
When starting congestion, this indicates the DL congestion 3 EVENT_VALUE_D
state before congestion state change. EVENT_VALUE_H
EVENT_VALUE_H
EVENT_VALUE_N

EVENT_PARAM_CURRENT_DOWNLINK_STATE
When starting congestion, this indicates the DL congestion 3 EVENT_VALUE_D
state after congestion state change. EVENT_VALUE_H
EVENT_VALUE_H
EVENT_VALUE_N

EVENT_PARAM_PREVIOUS_UPLINK_STATE
When starting congestion, this indicates the UL congestion 2 EVENT_VALUE_U
state before congestion state change. EVENT_VALUE_N

EVENT_PARAM_CURRENT_UPLINK_STATE
When starting congestion, this indicates the UL congestion 2 EVENT_VALUE_U
state after congestion state change. EVENT_VALUE_N

EVENT_PARAM_GBR_UL
Guaranteed Bit Rate (GBR) for Uplink. 15 -

EVENT_PARAM_GBR_DL
Guaranteed Bit Rate (GBR) for Downlink 15 -

EVENT_PARAM_UL_USER_THROUGHPUT
Uplink RLC user throughput. 15 -

EVENT_PARAM_DL_USER_THROUGHPUT
Downlink RLC user throughput. 15 -

EVENT_PARAM_TMGI_PLMN_ID
PLMN ID is part of the TMGI which is an identifier received in 25 -
RANAP MBMS SESSION START.

EVENT_PARAM_TMGI_SERVICE_ID
SERVICE ID is part of the TMGI which is an identifier received 25 -
in RANAP MBMS SESSION START.

EVENT_PARAM_SESSION_ID
Session identifier which may be received in RANAP MBMS 9 -
SESSION START.

EVENT_PARAM_MBMS_CONF
Specifies the MBMS Id. The MBMS Id indicates the bit rate. 4 -
Possible values: 2,3, and 4 where 2=64.8 kbps, 3=129.6 kbps,
4=259.2 kbps.

EVENT_PARAM_NBAP_CAUSE
Cause value received in NBAP COMMON TRANSPORT CHANNEL 16 -
SETUP FAILURE.

EVENT_PARAM_FIRST_START
The parameter indicates whether the MBMS session is started 2 EVENT_VALUE_F
on the first attempt (true) or after a reestablishment (false). EVENT_VALUE_T

EVENT_PARAM_SESSION_STATUS
Indicates the status history for the affected MBMS cell session. 3 EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_O

EVENT_PARAM_UE_POS_CELLID_UNSUCC_CAUSE
The cause of the failure of a Cell_Id attempt. 3 EVENT_VALUE_P
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_S

EVENT_PARAM_UE_POS_RTT_UNSUCC_CAUSE
The cause of the failure of an RTT attempt. 5 EVENT_VALUE_P
EVENT_VALUE_C
EVENT_VALUE_N
EVENT_VALUE_U
EVENT_VALUE_R
EVENT_VALUE_E
EVENT_VALUE_U
EVENT_VALUE_R
EVENT_VALUE_S

EVENT_PARAM_UE_POS_AGPS_UNSUCC_CAUSE
The cause of the failure of an A-GPS attempt. 5 EVENT_VALUE_P
EVENT_VALUE_N
EVENT_VALUE_G
EVENT_VALUE_R
EVENT_VALUE_G
EEVENT_VALUE_
EVENT_VALUE_G
EVENT_VALUE_N
EVENT_VALUE_I
EVENT_VALUE_H
EVENT_VALUE_S
EVENT_VALUE_G
EVENT_VALUE_G

EVENT_PARAM_UE_POS_METHOD_1
The positioning method selected for the first positioning 3 EVENT_VALUE_N
attempt. EVENT_VALUE_C
EVENT_VALUE_R
EVENT_VALUE_A
EVENT_PARAM_UE_POS_METHOD_2
The positioning method selected for the second positioning 3 EVENT_VALUE_N
attempt. EVENT_VALUE_C
EVENT_VALUE_R
EVENT_VALUE_A

EVENT_PARAM_UE_POS_METHOD_3
The positioning method selected for the third positioning 3 EVENT_VALUE_N
attempt. EVENT_VALUE_C
EVENT_VALUE_R
EVENT_VALUE_A

EVENT_PARAM_REQUIRED_MEASUREMENT_TIME
The required measurement time of the whole positioning 18 -
transaction.

Note: resolution is equal to 100.

EVENT_PARAM_UERXTX_TYPE1_MEASUREMENT
In case RTT method is attempted in the positioning 12 -
transaction, this parameter shall be equal to the value of the
UE RxTx Type 1 measurement, obtained from UE via RRC.

EVENT_PARAM_RTT_MEASUREMENT
In case RTT method is attempted in the positioning 16 -
transaction, this parameter shall be equal to the value of the
RTT measurement, obtained from RBS over NBAP or RNSAP.

EVENT_PARAM_EXTENDED_RANGE_RTT_MEASUREMENT
In case RTT method is attempted in the positioning transaction 18 -
and the RTT measurement by the RBS is an extended range
value, this parameter shall be equal to the value of the
extended range RTT measurement, obtained from RBS over
NBAP or RNSAP.

EVENT_PARAM_RTT_OVER_RNSAP
In case RTT method is attempted in the positioning 2 EVENT_VALUE_F
transaction, this parameter shall indicate if the RTT EVENT_VALUE_T
measurement result comes via NBAP or RNSAP.

EVENT_PARAM_INNER_RADIUS
In case the reported shape is Ellipsoid Arc, this parameter shall 17 -
be set equal to the coded radius of that Ellipsoid Arc.
EVENT_PARAM_UNCERTAINTY_RADIUS
The encoded thickness of a reported ellipsoid arc. Encoded 8 -
according to the formula 10(1.1^code-1), which gives the
thickness in meters.

Note: The value before shape conversion is reported.

EVENT_PARAM_OFFSET_ANGLE
In case the reported shape is Ellipsoid Arc, this parameter shall 10 -
be set equal to the coded offset angle of the Ellipsoid Arc.

EVENT_PARAM_INCLUDED_ANGLE
In case the reported shape is Ellipsoid Arc, this parameter shall 10 -
be set equal to the included angle of that Ellipsoid Arc.

EVENT_PARAM_SHAPE_BEFORE_CONVERSION
Applied only for the attempt whose result is selected to be 4 EVENT_VALUE_E
reported to CN, this parameter shows the name of the shape EVENT_VALUE_E
before shape conversion (that is, the measured shape).
EVENT_VALUE_E
EVENT_VALUE_E
EVENT_VALUE_E
EVENT_VALUE_P
EVENT_VALUE_E

EVENT_PARAM_SHAPE_AFTER_CONVERSION
Applied only for the attempt whose result is selected to be 4 EVENT_VALUE_E
reported to CN, this parameter shows the name of the reported EVENT_VALUE_E
shape.
EVENT_VALUE_E
EVENT_VALUE_E
EVENT_VALUE_E
EVENT_VALUE_P
EVENT_VALUE_E

EVENT_PARAM_POSITION_DATA
The value of the IE "Position data" in the message LOCATION 25 -
REPORT. Represented as a binary string of up to 24 bits (3
octets).

EVENT_PARAM_ACCURACY_FULFILMENT_INDICATOR
The value of the IE "accuracy fulfilment indicator" in the 2 EVENT_VALUE_R
message LOCATION REPORT. EVENT_VALUE_R
EVENT_PARAM_UEPOS_INITIAL_CONFIDENCE
The a pripiory confidence of the positioning method whose 8 -
measurement is chosen to be reported.

Reported as 'Not Applicable' for SAS Centric UE Positioning.

EVENT_PARAM_UEPOS_FINAL_CONFIDENCE
The confidence of the reported result. 8 -

Reported as 'Not Applicable' for SAS Centric UE Positioning.

EVENT_PARAM_ANTENNA_POSITION_LAT_SIGN
Latitude sign (North, South) of the antenna where the RTT 2 EVENT_VALUE_N
measurement is made. EVENT_VALUE_S

Reported as 'Not Applicable' for SAS Centric UE Positioning.

EVENT_PARAM_ANTENNA_POSITION_LAT_DEGREES
Latitude degrees of the antenna where the RTT measurement 24 -
is made. Latitude value (N), derived by the formula: N <=
(2^23) * (X / 90) < (N + 1) where X is the latitude in degrees
(0°..90°).

Reported as 'Not Applicable' for SAS Centric UE Positioning.

EVENT_PARAM_ANTENNA_POSITION_LONG_SIGN
Longitude sign (East, West) of the antenna where the RTT 2 EVENT_VALUE_E
measurement is made. EVENT_VALUE_W

Reported as 'Not Applicable' for SAS Centric UE Positioning.

EVENT_PARAM_ANTENNA_POSITION_LONG_DEGREES
Longitude degrees of the antenna where the RTT measurement 25 -
is made. If Longitude sign is equal to East, the Longitude value
(N) is derived by the formula N <= (2^24)*(X/360) < N+1,
where X is the longitude in degrees (0°..180°). If Longitude
sign is equal to West, the Longitude value (N) is derived by the
formula N <= (2^24)*(-X/360) < N+1, where X is the
longitude in degrees (-180°..0°).

Reported as 'Not Applicable' for SAS Centric UE Positioning.

EVENT_PARAM_NUMBER_OF_POLYGON_CORNERS
In case the Cell_Id method is attempted in the positioning 5 -
transaction, this parameter shall be equal to the number of
corners of the cell polygon.
EVENT_PARAM_POLYGON_CORNER_1_LAT_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_N
transaction, this parameter shall be equal to the latitude sign EVENT_VALUE_S
(North, South) of the first polygon corner.

EVENT_PARAM_POLYGON_CORNER_1_LAT_DEGREES
In case the Cell_Id method is attempted in the positioning 24 -
transaction, this parameter shall be equal to the degrees of
latitude of the first polygon corner. Latitude value (N), derived
by the formula: N <= (2^23) * (X / 90) < (N + 1) where X is
the latitude in degrees (0°..90°).

EVENT_PARAM_POLYGON_CORNER_1_LONG_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_E
transaction, this parameter shall be equal to the longitude sign EVENT_VALUE_W
(East, West) of the first polygon corner.

EVENT_PARAM_POLYGON_CORNER_1_LONG_DEGREES
In case the Cell_Id method is attempted in the positioning 25 -
transaction, this parameter shall be equal to the degrees of
longitude of the first polygon corner. If Longitude sign is equal
to East, the Longitude value (N) is derived by the formula N
<= (2^24)*(X/360) < N+1, where X is the longitude in
degrees (0°..180°). If Longitude sign is equal to West, the
Longitude value (N) is derived by the formula N <= (2^24)*(-
X/360) < N+1, where X is the longitude in degrees (-
180°..0°).

EVENT_PARAM_POLYGON_CORNER_2_LAT_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_N
transaction, this parameter shall be equal to the latitude sign EVENT_VALUE_S
(North, South) of the 2nd polygon corner.

EVENT_PARAM_POLYGON_CORNER_2_LAT_DEGREES
In case the Cell_Id method is attempted in the positioning 24 -
transaction, this parameter shall be equal to the degrees of
latitude of the 2nd polygon corner. Latitude value (N), derived
by the formula: N <= (2^23) * (X / 90) < (N + 1) where X is
the latitude in degrees (0°..90°).

EVENT_PARAM_POLYGON_CORNER_2_LONG_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_E
transaction, this parameter shall be equal to the longitude sign EVENT_VALUE_W
(East, West) of the 2nd polygon corner.
EVENT_PARAM_POLYGON_CORNER_2_LONG_DEGREES
In case the Cell_Id method is attempted in the positioning 25 -
transaction, this parameter shall be equal to the degrees of
longitude of the 2nd polygon corner. If Longitude sign is equal
to East, the Longitude value (N) is derived by the formula N
<= (2^24)*(X/360) < N+1, where X is the longitude in
degrees (0°..180°). If Longitude sign is equal to West, the
Longitude value (N) is derived by the formula N <= (2^24)*(-
X/360) < N+1, where X is the longitude in degrees (-
180°..0°).

EVENT_PARAM_POLYGON_CORNER_3_LAT_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_N
transaction, this parameter shall be equal to the latitude sign EVENT_VALUE_S
(North, South) of the 3rd polygon corner.

EVENT_PARAM_POLYGON_CORNER_3_LAT_DEGREES
In case the Cell_Id method is attempted in the positioning 24 -
transaction, this parameter shall be equal to the degrees of
latitude of the 3rd polygon corner. Latitude value (N), derived
by the formula: N <= (2^23) * (X / 90) < (N + 1) where X is
the latitude in degrees (0°..90°).

EVENT_PARAM_POLYGON_CORNER_3_LONG_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_E
transaction, this parameter shall be equal to the longitude sign EVENT_VALUE_W
(East, West) of the 3rd polygon corner.

EVENT_PARAM_POLYGON_CORNER_3_LONG_DEGREES
In case the Cell_Id method is attempted in the positioning 25 -
transaction, this parameter shall be equal to the degrees of
longitude of the 3rd polygon corner. If Longitude sign is equal
to East, the Longitude value (N) is derived by the formula N
<= (2^24)*(X/360) < N+1, where X is the longitude in
degrees (0°..180°). If Longitude sign is equal to West, the
Longitude value (N) is derived by the formula N <= (2^24)*(-
X/360) < N+1, where X is the longitude in degrees (-
180°..0°).

EVENT_PARAM_POLYGON_CORNER_4_LAT_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_N
transaction, this parameter shall be equal to the latitude sign EVENT_VALUE_S
(North, South) of the 4th polygon corner.

EVENT_PARAM_POLYGON_CORNER_4_LAT_DEGREES
In case the Cell_Id method is attempted in the positioning 24 -
transaction, this parameter shall be equal to the degrees of
latitude of the 4th polygon corner. Latitude value (N), derived
by the formula: N <= (2^23) * (X / 90) < (N + 1) where X is
the latitude in degrees (0°..90°).

EVENT_PARAM_POLYGON_CORNER_4_LONG_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_E
transaction, this parameter shall be equal to the longitude sign EVENT_VALUE_W
(East, West) of the 4th polygon corner.

EVENT_PARAM_POLYGON_CORNER_4_LONG_DEGREES
In case the Cell_Id method is attempted in the positioning 25 -
transaction, this parameter shall be equal to the degrees of
longitude of the 4th polygon corner. If Longitude sign is equal
to East, the Longitude value (N) is derived by the formula N
<= (2^24)*(X/360) < N+1, where X is the longitude in
degrees (0°..180°). If Longitude sign is equal to West, the
Longitude value (N) is derived by the formula N <= (2^24)*(-
X/360) < N+1, where X is the longitude in degrees (-
180°..0°).

EVENT_PARAM_POLYGON_CORNER_5_LAT_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_N
transaction, this parameter shall be equal to the latitude sign EVENT_VALUE_S
(North, South) of the 5th polygon corner.

EVENT_PARAM_POLYGON_CORNER_5_LAT_DEGREES
In case the Cell_Id method is attempted in the positioning 24 -
transaction, this parameter shall be equal to the degrees of
latitude of the 5th polygon corner. Latitude value (N), derived
by the formula: N <= (2^23) * (X / 90) < (N + 1) where X is
the latitude in degrees (0°..90°).

EVENT_PARAM_POLYGON_CORNER_5_LONG_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_E
transaction, this parameter shall be equal to the longitude sign EVENT_VALUE_W
(East, West) of the 5th polygon corner.

EVENT_PARAM_POLYGON_CORNER_5_LONG_DEGREES
In case the Cell_Id method is attempted in the positioning 25 -
transaction, this parameter shall be equal to the degrees of
longitude of the 5th polygon corner. If Longitude sign is equal
to East, the Longitude value (N) is derived by the formula N
<= (2^24)*(X/360) < N+1, where X is the longitude in
degrees (0°..180°). If Longitude sign is equal to West, the
Longitude value (N) is derived by the formula N <= (2^24)*(-
X/360) < N+1, where X is the longitude in degrees (-
180°..0°).
EVENT_PARAM_POLYGON_CORNER_6_LAT_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_N
transaction, this parameter shall be equal to the latitude sign EVENT_VALUE_S
(North, South) of the 6th polygon corner.

EVENT_PARAM_POLYGON_CORNER_6_LAT_DEGREES
In case the Cell_Id method is attempted in the positioning 24 -
transaction, this parameter shall be equal to the degrees of
latitude of the 6th polygon corner. Latitude value (N), derived
by the formula: N <= (2^23) * (X / 90) < (N + 1) where X is
the latitude in degrees (0°..90°).

EVENT_PARAM_POLYGON_CORNER_6_LONG_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_E
transaction, this parameter shall be equal to the longitude sign EVENT_VALUE_W
(East, West) of the 6th polygon corner.

EVENT_PARAM_POLYGON_CORNER_6_LONG_DEGREES
In case the Cell_Id method is attempted in the positioning 25 -
transaction, this parameter shall be equal to the degrees of
longitude of the 6th polygon corner. If Longitude sign is equal
to East, the Longitude value (N) is derived by the formula N
<= (2^24)*(X/360) < N+1, where X is the longitude in
degrees (0°..180°). If Longitude sign is equal to West, the
Longitude value (N) is derived by the formula N <= (2^24)*(-
X/360) < N+1, where X is the longitude in degrees (-
180°..0°).

EVENT_PARAM_POLYGON_CORNER_7_LAT_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_N
transaction, this parameter shall be equal to the latitude sign EVENT_VALUE_S
(North, South) of the 7th polygon corner.

EVENT_PARAM_POLYGON_CORNER_7_LAT_DEGREES
In case the Cell_Id method is attempted in the positioning 24 -
transaction, this parameter shall be equal to the degrees of
latitude of the 7th polygon corner. Latitude value (N), derived
by the formula: N <= (2^23) * (X / 90) < (N + 1) where X is
the latitude in degrees (0°..90°).

EVENT_PARAM_POLYGON_CORNER_7_LONG_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_E
transaction, this parameter shall be equal to the longitude sign EVENT_VALUE_W
(East, West) of the 7th polygon corner.
EVENT_PARAM_POLYGON_CORNER_7_LONG_DEGREES
In case the Cell_Id method is attempted in the positioning 25 -
transaction, this parameter shall be equal to the degrees of
longitude of the 7th polygon corner. If Longitude sign is equal
to East, the Longitude value (N) is derived by the formula N
<= (2^24)*(X/360) < N+1, where X is the longitude in
degrees (0°..180°). If Longitude sign is equal to West, the
Longitude value (N) is derived by the formula N <= (2^24)*(-
X/360) < N+1, where X is the longitude in degrees (-
180°..0°).

EVENT_PARAM_POLYGON_CORNER_8_LAT_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_N
transaction, this parameter shall be equal to the latitude sign EVENT_VALUE_S
(North, South) of the 8th polygon corner.

EVENT_PARAM_POLYGON_CORNER_8_LAT_DEGREES
In case the Cell_Id method is attempted in the positioning 24 -
transaction, this parameter shall be equal to the degrees of
latitude of the 8th polygon corner. Latitude value (N), derived
by the formula: N <= (2^23) * (X / 90) < (N + 1) where X is
the latitude in degrees (0°..90°).

EVENT_PARAM_POLYGON_CORNER_8_LONG_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_E
transaction, this parameter shall be equal to the longitude sign EVENT_VALUE_W
(East, West) of the 8th polygon corner.

EVENT_PARAM_POLYGON_CORNER_8_LONG_DEGREES
In case the Cell_Id method is attempted in the positioning 25 -
transaction, this parameter shall be equal to the degrees of
longitude of the 8th polygon corner. If Longitude sign is equal
to East, the Longitude value (N) is derived by the formula N
<= (2^24)*(X/360) < N+1, where X is the longitude in
degrees (0°..180°). If Longitude sign is equal to West, the
Longitude value (N) is derived by the formula N <= (2^24)*(-
X/360) < N+1, where X is the longitude in degrees (-
180°..0°).

EVENT_PARAM_POLYGON_CORNER_9_LAT_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_N
transaction, this parameter shall be equal to the latitude sign EVENT_VALUE_S
(North, South) of the 9th polygon corner.

EVENT_PARAM_POLYGON_CORNER_9_LAT_DEGREES
In case the Cell_Id method is attempted in the positioning 24 -
transaction, this parameter shall be equal to the degrees of
latitude of the 9th polygon corner. Latitude value (N), derived
by the formula: N <= (2^23) * (X / 90) < (N + 1) where X is
the latitude in degrees (0°..90°).

EVENT_PARAM_POLYGON_CORNER_9_LONG_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_E
transaction, this parameter shall be equal to the longitude sign EVENT_VALUE_W
(East, West) of the 9th polygon corner.

EVENT_PARAM_POLYGON_CORNER_9_LONG_DEGREES
In case the Cell_Id method is attempted in the positioning 25 -
transaction, this parameter shall be equal to the degrees of
longitude of the 9th polygon corner. If Longitude sign is equal
to East, the Longitude value (N) is derived by the formula N
<= (2^24)*(X/360) < N+1, where X is the longitude in
degrees (0°..180°). If Longitude sign is equal to West, the
Longitude value (N) is derived by the formula N <= (2^24)*(-
X/360) < N+1, where X is the longitude in degrees (-
180°..0°).

EVENT_PARAM_POLYGON_CORNER_10_LAT_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_N
transaction, this parameter shall be equal to the latitude sign EVENT_VALUE_S
(North, South) of the 10th polygon corner.

EVENT_PARAM_POLYGON_CORNER_10_LAT_DEGREES
In case the Cell_Id method is attempted in the positioning 24 -
transaction, this parameter shall be equal to the degrees of
latitude of the 10th polygon corner. Latitude value (N), derived
by the formula: N <= (2^23) * (X / 90) < (N + 1) where X is
the latitude in degrees (0°..90°).

EVENT_PARAM_POLYGON_CORNER_10_LONG_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_E
transaction, this parameter shall be equal to the longitude sign EVENT_VALUE_W
(East, West) of the 10th polygon corner.

EVENT_PARAM_POLYGON_CORNER_10_LONG_DEGREES
In case the Cell_Id method is attempted in the positioning 25 -
transaction, this parameter shall be equal to the degrees of
longitude of the 10th polygon corner. If Longitude sign is equal
to East, the Longitude value (N) is derived by the formula N
<= (2^24)*(X/360) < N+1, where X is the longitude in
degrees (0°..180°). If Longitude sign is equal to West, the
Longitude value (N) is derived by the formula N <= (2^24)*(-
X/360) < N+1, where X is the longitude in degrees (-
180°..0°).
EVENT_PARAM_POLYGON_CORNER_11_LAT_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_N
transaction, this parameter shall be equal to the latitude sign EVENT_VALUE_S
(North, South) of the 11th polygon corner.

EVENT_PARAM_POLYGON_CORNER_11_LAT_DEGREES
In case the Cell_Id method is attempted in the positioning 24 -
transaction, this parameter shall be equal to the degrees of
latitude of the 11th polygon corner. Latitude value (N), derived
by the formula: N <= (2^23) * (X / 90) < (N + 1) where X is
the latitude in degrees (0°..90°).

EVENT_PARAM_POLYGON_CORNER_11_LONG_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_E
transaction, this parameter shall be equal to the longitude sign EVENT_VALUE_W
(East, West) of the 11th polygon corner.

EVENT_PARAM_POLYGON_CORNER_11_LONG_DEGREES
In case the Cell_Id method is attempted in the positioning 25 -
transaction, this parameter shall be equal to the degrees of
longitude of the 11th polygon corner. If Longitude sign is equal
to East, the Longitude value (N) is derived by the formula N
<= (2^24)*(X/360) < N+1, where X is the longitude in
degrees (0°..180°). If Longitude sign is equal to West, the
Longitude value (N) is derived by the formula N <= (2^24)*(-
X/360) < N+1, where X is the longitude in degrees (-
180°..0°).

EVENT_PARAM_POLYGON_CORNER_12_LAT_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_N
transaction, this parameter shall be equal to the latitude sign EVENT_VALUE_S
(North, South) of the 12th polygon corner.

EVENT_PARAM_POLYGON_CORNER_12_LAT_DEGREES
In case the Cell_Id method is attempted in the positioning 24 -
transaction, this parameter shall be equal to the degrees of
latitude of the 12th polygon corner. Latitude value (N), derived
by the formula: N <= (2^23) * (X / 90) < (N + 1) where X is
the latitude in degrees (0°..90°).

EVENT_PARAM_POLYGON_CORNER_12_LONG_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_E
transaction, this parameter shall be equal to the longitude sign EVENT_VALUE_W
(East, West) of the 12th polygon corner.
EVENT_PARAM_POLYGON_CORNER_12_LONG_DEGREES
In case the Cell_Id method is attempted in the positioning 25 -
transaction, this parameter shall be equal to the degrees of
longitude of the 12th polygon corner. If Longitude sign is equal
to East, the Longitude value (N) is derived by the formula N
<= (2^24)*(X/360) < N+1, where X is the longitude in
degrees (0°..180°). If Longitude sign is equal to West, the
Longitude value (N) is derived by the formula N <= (2^24)*(-
X/360) < N+1, where X is the longitude in degrees (-
180°..0°).

EVENT_PARAM_POLYGON_CORNER_13_LAT_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_N
transaction, this parameter shall be equal to the latitude sign EVENT_VALUE_S
(North, South) of the 13th polygon corner.

EVENT_PARAM_POLYGON_CORNER_13_LAT_DEGREES
In case the Cell_Id method is attempted in the positioning 24 -
transaction, this parameter shall be equal to the degrees of
latitude of the 13th polygon corner. Latitude value (N), derived
by the formula: N <= (2^23) * (X / 90) < (N + 1) where X is
the latitude in degrees (0°..90°).

EVENT_PARAM_POLYGON_CORNER_13_LONG_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_E
transaction, this parameter shall be equal to the longitude sign EVENT_VALUE_W
(East, West) of the 13th polygon corner.

EVENT_PARAM_POLYGON_CORNER_13_LONG_DEGREES
In case the Cell_Id method is attempted in the positioning 25 -
transaction, this parameter shall be equal to the degrees of
longitude of the 13th polygon corner. If Longitude sign is equal
to East, the Longitude value (N) is derived by the formula N
<= (2^24)*(X/360) < N+1, where X is the longitude in
degrees (0°..180°). If Longitude sign is equal to West, the
Longitude value (N) is derived by the formula N <= (2^24)*(-
X/360) < N+1, where X is the longitude in degrees (-
180°..0°).

EVENT_PARAM_POLYGON_CORNER_14_LAT_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_N
transaction, this parameter shall be equal to the latitude sign EVENT_VALUE_S
(North, South) of the 14th polygon corner.

EVENT_PARAM_POLYGON_CORNER_14_LAT_DEGREES
In case the Cell_Id method is attempted in the positioning 24 -
transaction, this parameter shall be equal to the degrees of
latitude of the 14th polygon corner. Latitude value (N), derived
by the formula: N <= (2^23) * (X / 90) < (N + 1) where X is
the latitude in degrees (0°..90°).

EVENT_PARAM_POLYGON_CORNER_14_LONG_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_E
transaction, this parameter shall be equal to the longitude sign EVENT_VALUE_W
(East, West) of the 14th polygon corner.

EVENT_PARAM_POLYGON_CORNER_14_LONG_DEGREES
In case the Cell_Id method is attempted in the positioning 25 -
transaction, this parameter shall be equal to the degrees of
longitude of the 14th polygon corner. If Longitude sign is equal
to East, the Longitude value (N) is derived by the formula N
<= (2^24)*(X/360) < N+1, where X is the longitude in
degrees (0°..180°). If Longitude sign is equal to West, the
Longitude value (N) is derived by the formula N <= (2^24)*(-
X/360) < N+1, where X is the longitude in degrees (-
180°..0°).

EVENT_PARAM_POLYGON_CORNER_15_LAT_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_N
transaction, this parameter shall be equal to the latitude sign EVENT_VALUE_S
(North, South) of the 15th polygon corner.

EVENT_PARAM_POLYGON_CORNER_15_LAT_DEGREES
In case the Cell_Id method is attempted in the positioning 24 -
transaction, this parameter shall be equal to the degrees of
latitude of the 15th polygon corner. Latitude value (N), derived
by the formula: N <= (2^23) * (X / 90) < (N + 1) where X is
the latitude in degrees (0°..90°).

EVENT_PARAM_POLYGON_CORNER_15_LONG_SIGN
In case the Cell_Id method is attempted in the positioning 2 EVENT_VALUE_E
transaction, this parameter shall be equal to the longitude sign EVENT_VALUE_W
(East, West) of the 15th polygon corner.

EVENT_PARAM_POLYGON_CORNER_15_LONG_DEGREES
In case the Cell_Id method is attempted in the positioning 25 -
transaction, this parameter shall be equal to the degrees of
longitude of the 15th polygon corner. If Longitude sign is equal
to East, the Longitude value (N) is derived by the formula N
<= (2^24)*(X/360) < N+1, where X is the longitude in
degrees (0°..180°). If Longitude sign is equal to West, the
Longitude value (N) is derived by the formula N <= (2^24)*(-
X/360) < N+1, where X is the longitude in degrees (-
180°..0°).
EVENT_PARAM_MAX_DL_POWER
Maximum DL power. 11 -

Note: The resolution is equal to 0.1.

EVENT_PARAM_DL_TX_POWER
Transmitted carrier power. 11 -

A parameter not having a valid valid value to report at the time


of event reporting is filled with 1's, also referred to as the
value EVENT_VALUE_INVALID.

Note: For HS capable cell EVENT_VALUE_INVALID appears. In


this case check value of parameters
EVENT_PARAM_DL_NON_HS_TX_POWER and
EVENT_PARAM_DL_HS_REQ_POWER.

EVENT_PARAM_DL_NON_HS_TX_POWER
Transmitted carrier power of all codes not used for HS-PDSCH 11 -
or HS-SCCH transmission.

Note: For not HS capable cell


EVENT_PARAM_DL_NON_HS_TX_POWER includes invalid data.
In this case check value of parameter
EVENT_PARAM_DL_TX_POWER.

EVENT_PARAM_DL_HS_REQ_POWER
HS-DSCH required power. 11 -

The range for the measured power value is 0..100%, resolution


0.1, giving a range 0..1000.

Note: For not HS capable cell


EVENT_PARAM_DL_HS_REQ_POWER includes invalid data. In
this case check value of parameter
EVENT_PARAM_DL_TX_POWER.

EVENT_PARAM_NUMBER_OF_MCCH_MICH
This parameter will indicate 0 or 1, that is either one MCCH 2 -
and one MICH is established or none of them are established.
They go as a pair.

EVENT_PARAM_NUMBER_OF_MTCH_64
The number of MTCH´s established with rate 64. 5 -

EVENT_PARAM_NUMBER_OF_MTCH_128
The number of MTCH´s established with rate 128. 5 -

EVENT_PARAM_NUMBER_OF_MTCH_256
The number of MTCH´s established with rate 256. 5 -

EVENT_PARAM_UERXTX_TYPE2_MEASUREMENT
In case RTT method is attempted in the positioning transaction 14 -
with Rx-Tx Time Difference Type 2 measurement, this param
shall be equal to the value of the UE RxTx Type 2
measurement, obtained from UE via RRC. The parameter is
only applicable for this event for SAS Centric UE Positioning.

See the 3GPP specification TS 25.133 for a description of the


reported values.

Note that value 0 reported by RNC corresponds to RX-


TX_TIME_0000 in 3GPP TS 25.133, 1 corresponds to RX-
TX_TIME_0001, .., 8191 corresponds to RX-TX_TIME_8191.

EVENT_PARAM_PCAP_ERROR_TYPE
Indicates the reason for the PCAP signalling protocol error. 4 EVENT_VALUE_T
EVENT_VALUE_P
EVENT_VALUE_P
EVENT_VALUE_P
EVENT_VALUE_P
EVENT_VALUE_S

EVENT_PARAM_SELECTED_POSITION_METHOD
Indicates the selected UE position method. Reflects the value 4 EVENT_VALUE_U
of IE 'Selected Position Method' in PCAP Position Activation EVENT_VALUE_U
Request.
EVENT_VALUE_U
EVENT_VALUE_U
EVENT_VALUE_U

EVENT_PARAM_ADDITIONAL_METHOD_TYPE
Indicates additional position method information for A-GPS 3 EVENT_VALUE_U
positioning. Reflects the value of IE 'Additional Method Type' in EVENT_VALUE_U
PCAP Position Activation Request
EVENT_VALUE_U
EVENT_VALUE_U

EVENT_PARAM_RNC_RESPONSE_TIME
Indicates supervision time PCAP Position Activation procedure. 5 EVENT_VALUE_R
Reflects the value of IE 'RNC Response Time' in PCAP Position EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
Activation Request.
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_R

EVENT_PARAM_UE_POS_CAPABILITY_STAND_ALONE
Indicates UE Capability 'Standalone location method(s) 2 EVENT_VALUE_F
supported' EVENT_VALUE_T

EVENT_PARAM_UE_POS_CAPABILITY_UE_BASED_OTDOA
Indicates UE Capability 'UE based OTDOA supported'. 2 EVENT_VALUE_F
EVENT_VALUE_T

EVENT_PARAM_UE_POS_CAPABILITY_NETWORK_AGPS
Indicates UE Capability 'Network Assisted GPS support'. 3 EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N
EVENT_VALUE_N

EVENT_PARAM_UE_POS_CAPABILITY_GPS_TIMING
Indicates UE Capability 'Support for GPS timing of cell frames 2 EVENT_VALUE_F
measurement' EVENT_VALUE_T

EVENT_PARAM_UE_POS_CAPABILITY_IPDL
Indicates UE Capability 'Support for IPDL' 2 EVENT_VALUE_F
EVENT_VALUE_T

EVENT_PARAM_UE_POS_CAPABILITY_RXTX_TYPE2
Indicates UE Capability 'Support for Rx-Tx time difference type 2 EVENT_VALUE_F
2 measurement' EVENT_VALUE_T
EVENT_PARAM_UE_POS_CAPABILITY_GPS_PCH
Indicates UE Capability 'Support for UE assisted GPS 2 EVENT_VALUE_F
measurement validity in CELL_PCH and URA_PCH states' EVENT_VALUE_T

EVENT_PARAM_UE_POS_CAPABILITY_SFNTYPE2
Indicates UE Capability 'Support for SFN-SFN observed time 2 EVENT_VALUE_F
difference type 2 measurement'. EVENT_VALUE_T

EVENT_PARAM_MESSAGE_SENT_WHEN_TIMER_EXPIRES
Indicates the PCAP message sent before timer 2 EVENT_VALUE_P
T_POS_SAS_RESP expires. This parameter is only valid if EVENT_VALUE_P
EVENT_PARAM_PCAP_ERROR_TYPE indicates timer
T_POS_SAS_RESP expired.

EVENT_PARAM_T_POS_SAS_EXPIRED
Indicates if timer T_POS_SAS expired. This timer supervises 2 EVENT_VALUE_F
the PCAP Position Activation procedure. EVENT_VALUE_T

EVENT_PARAM_AMOUNT_OF_REPORTING
Indicates amount of reporting specified in PCAP Position 4 EVENT_VALUE_A
Activation Request. Reflects the value of IE 'Amount of EVENT_VALUE_A
Reporting'
EVENT_VALUE_A
EVENT_VALUE_A
EVENT_VALUE_A
EVENT_VALUE_A
EVENT_VALUE_A

EVENT_PARAM_NUMBER_OF_TTI2EDCH_USERS_IN_SERVING_CELL
The number of 2 ms TTI users in serving cell. 8 -

EVENT_PARAM_NUMBER_OF_TTI2EDCH_USERS_IN_NON_SERVING_CELL
The number of 2 ms TTI users in non serving cell. 8 -

EVENT_PARAM_UL_TN_IUB_USAGE
The Iub utilization/load in the UL. 16 -

EVENT_PARAM_DL_TN_IUB_USAGE
The Iub utilization/load in the DL. 16 -

EVENT_PARAM_NR_OF_OPENED_SF256_FOR_FDPCH_SYSTEM_UTILIZATION
Number of open SF256 DL Channelization Codes allocated for 9 -
F-DPCH.

EVENT_PARAM_NR_OF_ALLOCATED_TIMEPOSITIONS_FOR_FDPCH_SYSTEM_UTILIZATION
Total number of allocated F-DPCH TimePositions on SF256 DL 13 -
Channelization Codes.

EVENT_PARAM_EVENT_NR_OF_CS_SPEECH_USERS
The number of speech users in the cell, not multiRAB, only CS 8 -
originating.

EVENT_PARAM_SOURCE_CONNECTION_PROPERTIES
This parameter will be presented as a bit map value. Only the 16 -
first 13 bits (LSB) are used.

Bit 0 (LSB) indicates if CM in DL is used: 0=CM DL not used,


1=CM DL used.

Bit 1 indicates if CM in UL is used: 0=CM UL not used, 1=CM in


UL used.

Bit 2 indicates TTI length if E-DCH is used: 0=10ms TTI


(default value for non E-DCH connections), 1=2ms TTI.

Bit 3 indicates if the connection is using EL2: 0=Fixed size RLC


and MAC-hs used on HS-DSCH (non-EL2), 1=Flexible or fixed
size RLC and MAC-ehs on HS-DSCH (EL2).

Bit 4 is reserved for 64QAM usage indication.

Bits 5 and 6 are used to represent "speech category", where:


0="single-mode 12.2" (bit pattern ’00’) 1="AMR-NB MM Multi-
rate". (bit pattern ’01’) 2="AMR-NB MM Single-rate 12.2" (bit
pattern ’10’).

Bit 7 is reserved for MIMO; 1=MIMO activated, 0=MIMO


deactivated.

Bit 8 is reserved for SrbOnHs where: 0=SRB on X/DCH, 1=SRB


on X/HS

Bit 9 is reserved for SrbOnEul where: 0=SRB on DCH/X,


1=SRB on EUL/X

Bit 10 indicates if the connection is a Multi Carrier: 0= Multi


Carrier is not present in the connection, 1= Multi Carrier is
present in the connection.

Bit 11 is spare.

Bit 12 indicates the usage of CPC: 0=CPC not used, 1=CPC


used.

Bit 13-15 are spare.

The rest of the bits are just spare bits and will always be 0.

EVENT_PARAM_TARGET_CONNECTION_PROPERTIES
This parameter will be presented as a bit map value. Only the 16 -
first 13 bits (LSB) are used.

Bit 0 (LSB) indicates if CM in DL is used: 0=CM DL not used,


1=CM DL used.

Bit 1 indicates if CM in UL is used: 0=CM UL not used, 1=CM in


UL used.

Bit 2 indicates TTI length if E-DCH is used: 0=10ms TTI


(default value for non E-DCH connections), 1=2ms TTI.

Bit 3 indicates if the connection is using EL2: 0=Fixed size RLC


and MAC-hs used on HS-DSCH (non-EL2), 1=Flexible or fixed
size RLC and MAC-ehs on HS-DSCH (EL2)s.

Bit 4 is reserved for 64QAM usage indication.

Bits 5 and 6 are used to represent "speech category", where:


0="single-mode 12.2" (bit pattern ’00’) 1="AMR-NB MM Multi-
rate". (bit pattern ’01’) 2="AMR-NB MM Single-rate 12.2" (bit
pattern ’10’).

Bit 7 is reserved for MIMO; 1=MIMO activated, 0=MIMO


deactivated.

Bit 8 is reserved for SrbOnHs where: 0=SRB on X/DCH, 1=SRB


on X/HS

Bit 9 is reserved for SrbOnEul where: 0=SRB on DCH/X,


1=SRB on EUL/X

Bit 10 indicates if the connection is a Multi Carrier: 0= Multi


Carrier is not present in the connection, 1= Multi Carrier is
present in the connection.

Bit 11 is spare.

Bit 12 indicates the usage of CPC: 0= CPC not used, 1= CPC


used.

Bit 13-15 are spare.

The rest of the bits are just spare bits and will always be 0.
The Connection Properties of the UeRc reported in
EVENT_PARAM_WANTED_CONF. This parameter is not
applicable for IRATHO, IRATCC or GAN HO. For CNHHO this
parameter shall report the Connection Properties of the wanted
target UeRc for the CNHHO.

EVENT_PARAM_SOURCE_C_ID_1_SECONDARY_SERV_HSDSCH_CELL
Indicates the source Cell Id of the first secondary HS-DSCH cell 17 -
for Multi Carrier connections.

EVENT_PARAM_TARGET_C_ID_1_SECONDARY_SERV_HSDSCH_CELL
Indicates the target Cell Id of the first secondary HS-DSCH cell 17 -
for Multi Carrier connections.

EVENT_PARAM_HS_DSCH_PHYSICAL_LAYER_CATEGORY_EXT
HS-DSCH physical layer category, for details see 3GPP TS 6 -
25.331 and 3GPP TS 25.306. The range is 1 to 20. Note that
for RAB Establishments of other RABs than PS
Interactive/Background RABs, the INVALID_VALUE shall be
recorded for this parameter.

EVENT_PARAM_HS_DSCH_PHYSICAL_LAYER_CATEGORY_EXT2
HS-DSCH physical layer category, for details see 3GPP TS 6 -
25.331 and 3GPP TS 25.306. The range is 21 to 24. Note that
for RAB Establishments of other RABs than PS
Interactive/Background RABs, the INVALID_VALUE shall be
recorded for this parameter.

EVENT_PARAM_PROPAGATION_DELAY
Propagation delay sent to RBS at first RL Setup. Only to be 11 -
reported in the first instance of the event after first RL set up,
either at RRC connection set up or after reconfiguration from
CELL_FACH to CELL_DCH. For all other instances of the event,
the parameter shall be populated with N/A or equivalent.

EVENT_PARAM_WANTED_CONF
The UeRc identity of the wanted configuration (last tried) if the 8 -
failure was triggered during a reconfiguration. This parameter
is not applicable for IRATHO, IRATCC or GAN HO. For CNHHO
this parameter shall report the wanted target UeRc for the
CNHHO.

EVENT_PARAM_WANTED_CONNECTION_PROPERTIES
This parameter will be presented as a bit map value. Only the 16 -
first 13 bits (LSB) are used.
Bit 0 (LSB) indicates if CM in DL is used: 0=CM DL not used,
1=CM DL used.

Bit 1 indicates if CM in UL is used: 0=CM UL not used, 1=CM in


UL used.

Bit 2 indicates TTI length if E-DCH is used: 0=10ms TTI


(default value for non E-DCH connections), 1=2ms TTI.

Bit 3 indicates if the connection is using EL2: 0=Fixed size RLC


and MAC-hs used on HS-DSCH (non-EL2), 1=Flexible or fixed
size RLC and MAC-ehs on HS-DSCH (EL2)s.

Bit 4 is reserved for 64QAM usage indication.

Bits 5 and 6 are used to represent "speech category", where:


0="single-mode 12.2" (bit pattern ’00’) 1="AMR-NB MM Multi-
rate". (bit pattern ’01’) 2="AMR-NB MM Single-rate 12.2" (bit
pattern ’10’).

Bit 7 is reserved for MIMO; 1=MIMO activated, 0=MIMO


deactivated.

Bit 8 is reserved for SrbOnHs where: 0=SRB on X/DCH, 1=SRB


on X/HS

Bit 9 is reserved for SrbOnEul where: 0=SRB on DCH/X,


1=SRB on EUL/X

Bit 10 indicates if the connection is a Multi Carrier: 0= Multi


Carrier is not present in the connection, 1= Multi Carrier is
present in the connection.

Bit 11 is spare.

Bit 12 indicates the usage of CPC: 0=CPC not used, 1=CPC


used.

Bit 13-15 are spare.

The rest of the bits are just spare bits and will always be 0.

The Connection Properties of the UeRc reported in


EVENT_PARAM_WANTED_CONF. This parameter is not
applicable for IRATHO, IRATCC or GAN HO. For CNHHO this
parameter shall report the Connection Properties of the wanted
target UeRc for the CNHHO.

EVENT_PARAM_PROCEDURE_INDICATOR
Procedure where the failure was triggered. 6 EVENT_VALUE_N
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_C
EVENT_VALUE_R
EVENT_VALUE_M
EVENT_VALUE_S
EVENT_VALUE_O
EVENT_VALUE_I
EVENT_VALUE_I
The design base values as defined below applies: EVENT_VALUE_C
EVENT_VALUE_C
GAN HO is represented by the same values as for IRATHO.
EVENT_VALUE_I
For IRATHO and GAN HO: EVENT_VALUE_S
=EVENT_VALUE_IRAT_HANDOVER_TO_GSM EVENT_VALUE_U
EVENT_VALUE_R
For IRATCC:
=EVENT_VALUE_IRAT_CELL_CHANGE EVENT_VALUE_I
EVENT_VALUE_S
For CNHHO:

EVENT_PARAM_EVALUATION_CASE
Evaluation case related to the procedure indicator. 6 EVENT_VALUE_N
EVENT_VALUE_O
The following Evaluation Cases applies when Procedure
Indicator=EVENT_VALUE_IRAT_HANDOVER_TO_GSM (applies EVENT_VALUE_R
to GAN HO as well): EVENT_VALUE_R
= EVENT_VALUE_COVERAGE_BASED EVENT_VALUE_I
= EVENT_VALUE_SERVICED_BASED
EVENT_VALUE_D
= EVENT_VALUE_DIRECT_RETRY
= EVENT_VALUE_LOAD_BASED EVENT_VALUE_I
= EVENT_VALUE_GAN_MOBILITY EVENT_VALUE_D
EVENT_VALUE_I
The following Evaluation Cases applies when Procedure
Indicator=EVENT_VALUE_IRAT_CELL_CHANGE: EVENT_VALUE_H
= EVENT_VALUE_COVERAGE_BASED EVENT_VALUE_H
EVENT_VALUE_D
The following Evaluation Cases applies when Procedure
Indicator=EVENT_VALUE_CN_RELOCATION_FROM_RNC: EVENT_VALUE_U
= EVENT_VALUE_COVERAGE_BASED EVENT_VALUE_D
= EVENT_VALUE_LOAD_BASED EVENT_VALUE_F
= EVENT_VALUE_PS_CONNECTION_RELEASE
EVENT_VALUE_C
The following Evaluation Cases applies when Procedure EVENT_VALUE_S
Indicator=EVENT_VALUE__INTERFREQUENCY_HANDOVER: EVENT_VALUE_R
=EVENT_VALUE_COVERAGE_BASED
=EVENT_VALUE_LOAD_BASED
=EVENT_VALUE_HARD_HANDOVER_AT_RAB_ESTABLISHMENT
=EVENT_VALUE_HARD_HANDOVER_AT_RAB_RELEASE
=EVENT_VALUE_HARD_HANDOVER_AT_CHANNEL_SWITCHING
EVENT_PARAM_EVALUATION_CASE - Continued
EVENT_VALUE_R
EVENT_VALUE_R
EVENT_VALUE_H
EVENT_VALUE_H
EVENT_VALUE_P
EVENT_VALUE_D
EVENT_VALUE_D
EVENT_VALUE_H
EVENT_VALUE_H
EVENT_VALUE_H
EVENT_VALUE_L
EVENT_VALUE_G
EVENT_VALUE_L
EVENT_VALUE_L

EVENT_PARAM_MESSAGE_ID
Discarded CB Message Identifier. 17 -

EVENT_PARAM_MESSAGE_SERIAL_NO
Discarded CB Message Serial Number 17 -

EVENT_PARAM_TRIGGER
Trigger for recording of event. 3 EVENT_VALUE_M
EVENT_VALUE_M
EVENT_VALUE_S

EVENT_PARAM_CN_ID
Core Network domain identifier. 2 EVENT_VALUE_C
EVENT_VALUE_P

EVENT_PARAM_ORIGINATING_STATE
Originating state at indication of CS or PS call setup. 4 EVENT_VALUE_N
EVENT_VALUE_I
EVENT_VALUE_U
EVENT_VALUE_C
EVENT_VALUE_C
EVENT_VALUE_U

EVENT_PARAM_RRC_ESTABLISHMENT_CAUSE
RRC Establishment Cause received in RRC Connection Request 6 EVENT_VALUE_O
or RRC Cell Update. EVENT_VALUE_O
EVENT_VALUE_O
EVENT_VALUE_O
EVENT_VALUE_O
EVENT_VALUE_T
EVENT_VALUE_T
EVENT_VALUE_T
EVENT_VALUE_T
EVENT_VALUE_E
EVENT_VALUE_I
EVENT_VALUE_I
EVENT_VALUE_R
EVENT_VALUE_D
EVENT_VALUE__
EVENT_VALUE_O
EVENT_VALUE_C
EVENT_VALUE_T
EVENT_VALUE_T
EVENT_VALUE_T
EVENT_VALUE_M
EVENT_VALUE_M

EVENT_PARAM_CELLO_AAL2NCI_REJECT_REASON
Cello AAL2 reject reason if failure relates to Node or TN failure. 5 EVENT_VALUE_N
EVENT_VALUE_C
EVENT_VALUE_C
EVENT_VALUE_C
EVENT_VALUE_C
EVENT_VALUE_C
EVENT_VALUE_C
EVENT_VALUE_C
EVENT_VALUE_C
EVENT_VALUE_C
EVENT_VALUE_C

Any Invalid Parameter


A parameter not having a valid value to report at the time of #FFFFFFFF
event reporting is filled with 1's, also referred to as the value
EVENT_VALUE_INVALID.
Table 9 RNC 3810 MP ID Mappings
Unique
Value of MP
Processor
EVENT_PARAM_RNC_MP_ID Type
Number
Main 0 000800 SCCP
Subrack (A- 1 000900 SCCP Standby
node)
2 001000 Central
3 001100 Central
Standby
4 001200 O&M
5 001300 O&M Standby
6 001400 Module
7 001500 Module
8 001600 Module
9 001700 RANAP/RNSAP
10 001800 RANAP/RNSAP
Extension 11 011200 Module
Subrack 1 12 011300 Module
(B-Node)
13 011400 Module
14 011500 Module
15 011600 Module
16 011700 Module
Extension 17 021200 Module
Subrack 2 18 021300 Module
(C-Node)
19 021400 Module
20 021500 Module
21 021600 Module
22 021700 Module
(1)
Extension 23 111200 031200 Module
Subrack 3 24 111300 031300 (1)
Module
(D-Node) (1)
25 111400 031400 Module
(1)
26 111500 031500 Module
(1)
27 111600 031600 Module
(1)
28 111700 031700 Module
(1)
Extension 29 121200 041200 Module
Subrack 4 30 121300 041300 (1)
Module
(E-Node) (1)
31 121400 041400 Module
(1)
32 121500 041500 Module
(1)
33 121600 041600 Module
(1)
34 121700 041700 Module
Extension 35 091200 Module
Subrack 5 36 091300 Module
37 091400 Module
38 091500 Module
(F-Node) 39 091600 Module
40 091700 Module
(1) The alternative number applies to nodes which are HW configured when RNC P3 SW
was installed, but might be upgraded to later SW.

Table 10 RNC 3820 MP ID Mappings

Unique
Value of MP
Processor
EVENT_PARAM_RNC_MP_ID Type
Number
Main 0 000800 SCCP
Subrack (A- 1 000900 SCCP Standby
node)
2 001000 Central
3 001100 Central
Standby
4 001200 O&M
5 001300 O&M Standby
6 001400 Module
7 001500 Module
8 001600 Module
9 001700 RANAP/RNSAP
10 001800 RANAP/RNSAP
Extension 11 011200 Module
Subrack 1 12 011300 Module
(B-Node)
13 011400 Module
14 011500 Module
15 011600 Module
16 011700 Module
Extension 17 021200 Module
Subrack 2 18 021300 Module
(C-Node)
19 021400 Module
20 021500 Module
21 021600 Module
22 021700 Module

3.1 Disconnection Codes

Table 11 describes how to interpret the disconnection code parameters


EVENT_PARAM_RAN_DISCONNECTION_CODE and
EVENT_PARAM_RAN_DISCONNECTION_SUBCODE.
Table 11 Disconnection Codes

Cause Disconnection Disconnection Trigger


Name Cause Code Cause Sub-
Code
Unspecified 0 0 Unspecified - all cases which will result in -
abnormal RAB disconnection and do not
map to any of the ones described below.
Radio 1 0 Other Radio Link Control (RLC) -
Connection unrecoverable error.
Supervision
(RCS)

Radio 1 1 Radio Link Control (RLC) unrecoverable -


Connection error in UTRAN (maximum number of RLC
Supervision retransmissions is reached).
(RCS)
Radio 1 2 Radio Connection Supervision - expiry of -
Connection timer (rcsAllRlLostTimer or
Supervision rcsCchWaitCuTimer or hsDschRcLostT)
(RCS)
Radio 1 3 Radio link failure indication leading to a -
Connection release with Cause = transport.
Supervision
(RCS)
Radio 1 4 Radio link failure indication leading to a -
Connection release with cause other than transport.
Supervision
(RCS)
Congestion 2 1 Congestion action - release triggered by C
congestion.
Transport 3 0 Transport network failure – All other -
CELLO_AAL2NCIFAILURE.
Transport 3 1 Transport network failure - -
CELLO_AAL2NCI_TEMP_FAILURE.
Transport 3 2 Transport network failure - -
CELLO_AAL2NCI_MANAGEMENT_INDUCED.
Transport 3 3 Transport network failure - -
CELLO_AAL2NCI_OTHER_DC_IND_CAU
O&M 4 1 Cell lock indication. C
Measurement 5 1 MEASUREMENT CONTROL FAILURE that -
control triggers a connection release - intra-
failure frequency.
Measurement 5 2 MEASUREMENT CONTROL FAILURE that -
control triggers a connection release - inter-radio
failure access technology.
Measurement 5 3 MEASUREMENT CONTROL FAILURE that -
control triggers a connection release - inter-
failure frequency.
Measurement 5 4 MEASUREMENT CONTROL FAILURE that
control triggers a connection release - traffic
failure volume measurement setup.
Soft 6 1 Active Set Update complete message not S
Handover received - addition. C
R
t
a
Soft 6 2 Active Set Update complete message not S
Handover received - deletion. C
R
t
d
Soft 6 3 Active Set Update complete message not S
Handover received - replacement. C
R
t
r
Soft 6 4 Handover Evaluation release events - S
Handover _EVENT_BUFFER_EXCEEDED. C
R
t
a
r
Soft 6 5 Due to ReleaseConnOffset (for a cell not in S
Handover the neighbor set). C
c
Soft 6 6 High Speed-Downlink Shared Channel (HS- -
Handover DSCH) Cell Change failure after A-DCH
removal.
Soft 6 0 Other Handover Evaluation failure reasons: S
Handover (_UNSPECIFIED_RELEASE_CAUSE, C
_BUFFER_TIME_EXCEEDED, c
_CELL_SYNC_INFO_NOTAVAILABLE)
Inter Radio 7 1 IRAT outgoing failure - Timer G
Access T_reloc_overall expires.
Technology
(IRAT)
Inter Radio 7 2 Cell change outgoing failure Timer G
Access T_cellchange expires.
Technology
(IRAT)
Inter- 8 1 IFHO failure - reception of PHYSICAL T
Frequency CHANNEL RECONFIGURATION FAILURE I
Handover with cause other than physical channel
(IFHO) failure received from the UE on the source
frequency.
Inter- 8 2 IFHO failure - at expiry of timer Timer RRC T
Frequency T-PCR. I
Handover
(IFHO)
Inter- 8 3 IFHO failure - if ciphering is ongoing, and if T
Frequency RBs mapped on TM-RLC entities have been I
Handover established, and if a PHYSICAL CHANNEL
(IFHO) RECONFIGURATION COMPLETE message is
received that does not include one or both
of the IEs COUNT-C activation time and
Uplink counter synchronization info
Channel 9 1 Transition to a DCH connection has been
Switching initiated but can not be completed
High Speed 10 1 Selection of HS-DSCH connection, including
Hard a Hard HO has been initiated, but can not
Handover be completed
CN Hard 11 1 timeRelocoverall (MO: Handover) expires.
Handover
CN Hard 11 2 Relocation preparation procedure fails in
Handover source RNC due to either of the following:

• RELOCATION PREPARATION
FAILURE received
• timeRelocPrep (MO: Handover)
expires
• ERROR INDICATION with procedure
code "Relocation Preparation"
Iu User Plane 12 1 CN Triggered Initialisation Failure
Control

3.2 UeRc Identities

The event parameters EVENT_PARAM_SOURCE_CONF and


EVENT_PARAM_TARGET_CONF report an integer value which represents
the UE radio connection identity (UeRcId). For description of the UeRcId
values refer to WCDMA RAN document Connection Handling.

4 Data File
This section describes GPEH data files.

The recorded data consists of Layer 3 protocol messages, in this


description called inter-node events, and internal events. The protocol
messages are taken from the RNC external protocol interfaces in ASN.1-
encoded format and converted to bit-packed binary format. The internal
event is also stored in bitpacked binary format.

The events are collected in GPEH data files, also called GPEH ROP files.
The events are written to file in the order they appear in the buffers and
are not ordered chronologically. For each 15-minute ROP period, the
following two types of file are generated:

Main File The main file contains administrative information about the GPEH
recording and links to subfiles. The file storage location of the
main file is decided by the attribute performanceDataPath on the
CPP managed object ManagedElementData. Default value at node
start up is either /p001200/ or /p001300, depending on whether
the O&M MP functionality executes on board 12 or 13 in the main
subrack at start up. It is not recommended to change this value.

Subfile A subfile contains recorded events for all active scanners. The
main file contains link records which points out the file path to
the subfiles.

One main file generated on the O&M MP, one subfile on the O&M MP,
and one subfile per Module MP conclude each ROP. Each file has a
unique name according to the file name convention described in Table
12.

Table 12 GPEH File Naming

File Name:

Main file: <Type><Date>.<StartTime>-<EndTime>_gpehfile:2.lnk.gz

Subfile: <Type><Date>.<StartTime>-<EndTime>_GPEH.lnk.gz
Type Always set to "A" - single Network Element and single
recording/granularity period
Date YYYYMMDD
Starttime HHMM
Endtime HHMM

For an example of a file name, see Example 1.

Example 1 GPEH File Name

Main File: A20081128.1515-1530_gpehfile:2.lnk.gz


Subfile: A20081128.1515-1530_GPEH.lnk.gz

4.1 Structure

This section describes the structure of the GPEH data files.


Each file comprises the following records:

Header Administrative information about the file.

Recording Scope of the recording.

Protocol The name and version of the protocol from which messages can
be recorded.

Body The body contains event records. The event record contains
details about inter-node events and RNC-internal events. It is
only the subfile that has a body record.

Link A link from the main file to a GPEH subfile on another MP.

Footer Administrative information about the time of normal termination


of the ROP file.

Error Contains the time and cause of an abnormal termination of a


recording. The error record replaces the footer record if the file is
terminated abnormally.

The GPEH data file structure and the relation between the main file and
the subfiles are displayed in Figure 1.

Figure 1 GPEH Data File Structure


The file starts with a header record followed by one or more recording
records, one for each active scanner.

Then there are a number of protocol records. They appear in the file
regardless of whether there are messages from that protocol in the file.

Then there are a number of optional link records, each pointing to a


subfile, which contains a body record.

Finally, the footer record appears, unless the main file is terminated
abnormally. In case of abnormal termination an error record replaces
the footer record.

4.2 Records

This section describes the GPEH data file records.

4.2.1 Header

Details of the header record layout are provided in Table 13.

Table 13 Header Record Layout Details

Pos Description Size (bytes) Type Value/Range


Record unsigned
0 Length 2 short [2..65535]
unsigned
1 Record Type 1 char 0
File Format
(1)
2 Version 5 char[]
Year (four unsigned
3 digits) 2 short [2000..]
unsigned
4 Month 1 short [1..12]
unsigned
5 Day 1 short [1..31]
unsigned
6 Hour 1 short [0..23]
unsigned
7 Minute 1 short [0..59]
unsigned
8 Second 1 short [0..61](2)
9 NE user label 200 char[] The value of the
attribute
’userLabel’ of the
Managed Object
(MO)
’ManagedElement’
The value of the
attribute
’logicalName’ of
the Managed
NE logical Object (MO)
10 name 200 char[] ’ManagedElement’
File
information
(3)
11 version 5 char[]
(1) File format version "X-Y" should be updated as follows: Increment "X", whenever a
new record is introduced to the file format - Incompatible change of the WRAN product
release. Increment "Y", whenever a change is made to the existing record structure for a
product - Incompatible change of the WRAN product release. In W10 the file format
version (FFV) is according to the following: W10.0 and on: FFV= 7-1 Note: Addition of
new events, measurements or event attributes will NOT cause a change to file format
version.

(2) Range 0..61 to handle leap seconds.

(3) File information Version (FIV) is represented as an ASCII string: [:SPACE:]*[A-Z]*[0-


9]*. Some samples on valid combinations of the five characters ( _ symbolizes space):
____A , ___AB , __AB1 , _AAB1 , AAAAA .

For an example of the header record, see Example 2.

Example 2 Header Record

HEADER
FileFormatVersion: 7- 1
Year: 2009 Month: 1 Day: 12 Hour: 15 Minute: 15
Second: 0
NEUserLabel: ak0ru32
NetworkElementName: 032
FileInformationVersion: __AB1

4.2.2 Recording

Details of the recording record layout are provided in Table 14.

Table 14 Recording Record Layout Details

Pos Description Size (bytes) Type Value/Range


0 Record 2 unsigned [2..65535]
Length short
1 Record Type 1 unsigned 1
char
(1)
2 Filter Type 1 unsigned [0..2]
char
(2)
3 Filter - char[]
(1) 0 - PM recording type UETR, 1 - PM recording type CTR, 2 - PM recording type GPEH

(2) Holds the filter setting for this scanner. Recording type UETR: Holds IMSI value as an
ASCII string, Recording type CTR: Holds Access Cell Identity as an ASCII string. Cells are
identified using the LDN of the access cell, Recording type GPEH: Holds UE fraction and
recording area (cells). The filter setting included as a list of name-value pairs, the list is
represented as a sequence of NULL-terminated strings as: String: 0 - name 0, 1 - value 0,
2 - name 1, 3 - value 1, . . n - name n/2, n + 1 - value n/2

For an example of the recording data record, see Example 3.

Example 3 Recording Data Record

RECORDING
UE_FRACTION: 1000
CELL:
ManagedElement=1,RncFunction=1,UtranCell=201093

4.2.3 Protocol

Details of the protocol record layout are provided in Table 15.

Table 15 Protocol Record Layout Details

Size
Pos Description (bytes) Type Value/Range
0 Record length 2 unsigned short [2..65535]
1 Record Type 1 unsigned char 2
2 Protocol id 1 unsigned char [0..7](1)
(2)
3 Protocol name 50 char[]
(3)
4 Object Identifier 30 char[]
(1) The "Protocol id" represented as: 0=RRC "3GPP TS 25.331 V8.6.0", 1=NBAP "3GPP
TS 25.433 V8.4.0", 2=RANAP "3GPP TS 25.413 V7.8.0", or 4=RNSAP "3GPP TS 25.423
V7.7.0", 5=INTERNAL_EVENT (RNC internal protocol ID including RNC internal events and
RNC internal measurements), 6=PCAP "3GPP TS 25.453 V7.6.0" or 7=SABP "3GPP TS
25.419 V6.2.0".

(2) The "Protocol name" represented as an ASCII string: RANAP, NBAP, RNSAP, RRC,
PCAP, SABP or INTERNAL_EVENT.

(3) The "Object identifier" of standard ASN.1 data type definition for the messages from
this protocol, represented as an ASCII string: "a,b,c,d,ee,f,g,h", where: a=itu-t(0),
b=identified-organization(4), c=etsi(0), d=mobileDomain(0), ee=umts-Access(20),
f=modules(3), g=ranap(0),nbap(2) or rnsap(1), h=version1(1). Whereas the RRC, PCAP,
SABP protocols, the "Number and Version" of the 3GPP specification is instead
represented as an ASCII string: RRC: "3GPP TS 25.331 V8.6.0", PCAP: "3GPP TS 25.453
V7.6.0", SABP: "3GPP TS 25.419 V6.2.0", or "N/A" if Protocol ID="5" (INTERNAL_EVENT).

For an example of the protocol record, see Example 4.


Example 4 Protocol Record

PROTOCOL
Protocol id: 1
Protocol name: NBAP
Object identifier: 0.4.0.0.20.3.2.1

4.2.4 Body

The body record can contain event records.

4.2.4.1 Event

The event record holds an event of any kind (inter-node or RNC-internal


events).

Details of the event record layout are provided in Table 16.

Table 16 Event Record Layout Details

Size
Pos Description (bytes) Type Value/Range
0 Record Length 2 unsigned short [2..65535]
1 Record Type 1 unsigned char 4
2 Bitpacked part - unsigned char[]

Bitpacking

All information in the event record, except for the Record Length and
Record Type fields, are bit-packed in order to save space. The bit-
packed part is organized as a sequence of bitfields of variable length.
The length of the bit-packed part is always a multiple of 32-bit words.
Unused bits in the last word are set to zero. The most significant bit
(msb) appears first in each bitfield. The outline of the bit-packed part of
the event records is shown in Figure 2.

Figure 2 Bitpacked Part of Event Record

The bit-packed part is further divided in common fields, included for all
events, and specific fields, specific per event. The common parts are
described in Table 17. The Pos column in the table only indicates the
order in which the bit-fields appear.

Table 17 Common Part in Bitpacked Layout

Size
Pos Description (bits) Encoding Value/Range
0 Scanner ID 24 binary integer [0,1](1)
1 Hour 5 binary integer [0..23]
2 Minute 6 binary integer [0..59]
[0..61]

The value 61
represents a leap
3 Second 6 binary integer second.
4 Millisecond 11 binary integer [0..999]
(2)
5 Event ID 11 binary integer
(1) The scanner ID field consists of a sequence of bits (24 bits), each bit corresponding to
a particular scanner ID (0-23 scanners GPEH, 0-15 scanners UETR, 0-1 scanners CTR).
“0” is used in the corresponding bit location to indicate when an event is NOT part of a
particular scanner. “1” will be used in the corresponding bit location to indicate that an
event is part of a particular scanner. Note that the same event could be part of one,
several, or all scanners. Event presence for each scanner will be indicated with “1” in the
scanner ID field.

(2) Unique identifier for an RNC event.

The RNC-internal event-specific fields are bit-packed, see Section 3 for


bitpacking for each parameter. Additional common fields in the
bitpacked part of the event record for RNC external and RNC internal
events are listed in Table 18.

Table 18 Additional Common Fields in Bitpacked Part of an Event Record

Pos Description Size Type Value/Range(1)


15
0 ueContextId 16 bits binary integer [-1 .. 2 - 1](2)
1 rncModuleId 7 bits binary integer [1 .. 26 – 1](3)
2 cellID1 17 binary integer [0...65535]
3 rncID1 13 binary integer [0..4095]
4 cellID2 17 binary integer [0...65535]
5 rncID2 13 binary integer [0..4095]
6 cellID3 17 binary integer [0...65535]
7 rncID3 13 binary integer [0..4095]
8 cellID4 17 binary integer [0...65535]
9 rncID4 13 binary integer [0..4095]
(1) All bitpacked parameters are represented with an additional bit. The additional bit,
which is the most significant bit, indicates whether the reported value is valid or not. A
parameter not having a valid value to report at the time of event reporting is filled with
1's (including the additional bit) also referred to as the value EVENT_VALUE_INVALID.

(2) EVENT_VALUE_INVALID used for messages not related to a specific UE.

(3) EVENT_VALUE_INVALID used for messages not related to a specific RNC Module
identity.

The RNC external event specific fields to be bit packed are listed in
Table 19.

Table 19 External Event Specific Fields

Pos Description Size Type Value/Range


(1)
0 PDU type 5 bits binary integer [1..9]
1 Protocol id 4 bits binary integer [0..4](2)
2 Direction 2 bits binary integer [0..1](3)
Message
3 length 12 bytes unsigned short [0..x](4)
Encoded unsigned
4 message - char[] [message length (bytes) x 8 bits](5)
All unused bits in the last word (32-
Padding bits bit word) are set to zero
(1) 1:DL-DCCH-MSG, 2:UL-DCCH-MSG, 3:DL-CCCH-MSG, 4:UL-CCCH-MSG, 5:PCCH-
MSG, 6:DL-SHCCH-MSG, 7:UL:SHCCH-MSG, 8:BCCH-FACH-MSG, 9:BCCH-BCH-MSG (DL
= Downlink, UL = Uplink, MSG = Message, DCCH = Dedicated Control Channel, CCCH =
Common Control Channel, PCCH = Paging Control Channel, SHCCH = Shared Control
Channel, BCCH = Broadcast Control Channel), EVENT_VALUE_INVALID used for messages
where no PDU type is available.

(2) Protocol ID as previously defined in protocol record.

(3) The value 0 indicates received, and the value 1 indicates sent.

(4) x is the length in bytes of the following encoded protocol message.

(5) Actual protocol message, encoded as transferred on the external RNC interface and
previously defined in the protocol record. For the encoding format, refer to the protocol
specifications.

For an example of the event record, see Example 5 for RNC-internal


events, and Example 6 for inter-node events..

Example 5 Event Record, RNC-Internal Event

EVENT
Hour: 15 Minute: 19 Second: 57 Millisecond: 104
Event_ID: 444
Name: INTERNAL_RECORDING_FAULT
UE_CONTEXT: Not Applicable
RNC_MODULE_ID: Invalid
C_ID_1: Not Applicable
RNC_ID_1: Not Applicable
C_ID_2: Not Applicable
RNC_ID_2: Not Applicable
C_ID_3: Not Applicable
RNC_ID_3: Not Applicable
C_ID_4: Not Applicable
RNC_ID_4: Not Applicable
RNC_MP_ID: 6
EVENT_TRIGGER: 57
AFFECTED_SCANNER_TYPE: Invalid

Example 6 Event Record, Inter-Node event

EVENT
Hour: 15 Minute: 26 Second: 51 Millisecond: 422
Event_ID: 145
UeContextID: 268
RncModuleID: 4
C_ID_1: 1093
RNC_ID_1: 32
C_ID_2: 1093
RNC_ID_2: 32
C_ID_3: 1093
RNC_ID_3: 32
C_ID_4: 1093
RNC_ID_4: 32
PDU-type: -1
ProtocolID: 1
Direction:RECEIVED
Message length: 34
EncodedMessage:
value NBAP-PDU ::= initiatingMessage : {
procedureID {
procedureCode 18,
ddMode common
},
criticality ignore,
messageDiscriminator dedicated,
transactionID shortTransActionId : 57,
value DedicatedMeasurementReport : {
protocolIEs {
{
id 44,
criticality ignore,
value CRNC-CommunicationContextID :
189
},
{
id 133,
criticality ignore,
value MeasurementID : 300
},
{
id 67,
criticality ignore,
value
DedicatedMeasurementObjectType-DM-Rprt : all-RL : {
rL-InformationList-DM-Rprt {
{
id 202,
criticality ignore,
value RL-InformationItem-DM-
Rprt : {
rL-ID 0,

dedicatedMeasurementValueInformation
measurementAvailable : {
dedicatedmeasurementValue
transmittedCodePowerValue : 69
}
}
}
}
}
}
}
}
}

4.2.5 Link

Details of the link record layout are provided in Table 20.

Table 20 Link Record Layout Details

Size
Pos Description (bytes) Type Value/Range
0 Record Length 2 unsigned short [2..65535]
1 Record Type 1 unsigned char 8
(1)
2 File Path 256 char[]
(1) Absolute path, including the name of the file in the node filesystem.

For an example of the link record, see Example 7.

Example 7 Link Record


LINK
file: /p001400/A20031128.1515-1530_GPEH.lnk

4.2.6 Footer

Details of the footer record layout are provided in Table 21.

Table 21 Footer Record Layout Details

Size
Pos Description (bytes) Type Value/Range
0 Record Length 2 unsigned short [2..65535]
1 Record Type 1 unsigned char 7
2 Year (four digits) 2 unsigned short [2000..]
3 Month 1 unsigned char [1..12]
4 Day 1 unsigned char [1..31]
5 Hour 1 unsigned char [0..23]
6 Minute 1 unsigned char [0..59]
[0..61]

The value 61
represents a leap
7 Second 1 unsigned char second.

For an example of the footer record, see Example 8.

Example 8 Footer Record

FOOTER
Year:2003 Month: 11 Day: 28 Hour: 15 Minute: 30
Second: 0

4.2.7 Error

The error record is included only if the file is terminated abnormally in


the RNC. It contains the cause and the time of the abnormal
termination.

Details of the error record layout are provided in Table 22.

Table 22 Error Record Layout Details

Size
Pos Description (bytes) Type Value/Range
0 Record Length 2 unsigned short [2..65535]
1 Record Type 1 unsigned char 6
2 Hour 1 unsigned char [0..23]
3 Minute 1 unsigned char [0..59]
[0..61]

The value 61
represents a leap
4 Second 1 unsigned char second.
5 Millisecond 2 unsigned short [0..999]
6 Error type 1 unsigned char [0..4](1)
(1) Value: 0 - File system error, 1 - Communication error (=restart), 2 - Not used, 3 -
Not used, 4 - Other

For an example of the error record, see Example 9.

Example 9 Error Record

ERROR
Hour: 15 Minute: 5 Second: 52 Millisecond: 164
ErrorType: Other

S-ar putea să vă placă și