GPEH

138 

Loading.... (view fulltext now)

Loading....

Loading....

Loading....

Loading....

Full text

(1)

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

(2)

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

(3)

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 System Error

If it is not possible to use the file system on some of the MPs due to some serious 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.

(4)

File Size Partially Exceede d

The parameter highPrioScanReserve determines the percentage of the GPEH files that, together with the parameter 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

Exceede d

If the maximum file size is exceeded on an MP, reporting of events is suspended for all GPEH scanners on that MP for the duration of the current ROP. Recording continues on all other MPs. Recording resumes on the affected MP with the next ROP. The internal event

INTERNAL_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.

(5)

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 when a new mobile is associated with

an internal User Equipment (UE) pointer.

385 INTERNAL_RADIO_QUALITY_MEASUREMENTS_UEH Captured whenever a radio measurement

report is received in the RNC subsystem UE Handling (UEH).

The parameter values

EVENT_VALUE_UL_SIR_ERROR (0) and EVENT_VALUE_DL_TX_CODE_POWER (1) apply to the parameter

EVENT_PARAM_MEASURED_ENTITY for this event.

386 INTERNAL_RADIO_QUALITY_MEASUREMENTS_RNH Captured whenever a radio measurement

report is received in the RNC subsystem Radio Network Handling (RNH).

The parameter values

EVENT_VALUE_UL_INTERFERENCE (2),

EVENT_VALUE_ DL_TX_CARRIER_POWER (3), EVENT_VALUE_NON_HS_POWER (4) and EVENT_VALUE_HSDSCH_REQUIRED_POWER (5) apply to the parameter

EVENT_PARAM_MEASURED_ENTITY for this event.

(6)

387 INTERNAL_CHANNEL_SWITCHING Captured whenever a channel switch occurs.

388 INTERNAL_UL_OUTER_LOOP_POWER_CONTROL Captured whenever one of the conditions listed

for parameter

EVENT_PARAM_EVENT_TRIGGER occurs.

389 INTERNAL_DL_POWER_MONITOR_UPDATE Captured whenever one of the conditions listed

for parameter

EVENT_PARAM_EVENT_TRIGGER occurs.

390 INTERNAL_CELL_LOAD_MONITOR_UPDATE Captured whenever one of the conditions listed

for parameter

EVENT_PARAM_EVENT_TRIGGER occurs. Value of parameter

TOTAL_DL_CHAN_CODE_TREE_CONSUMPTION for this event is always set to

(7)

391 INTERNAL_ADMISSION_CONTROL_RESPONSE Captured whenever the admission control function responds to an admission request.

392 INTERNAL_CONGESTION_CONTROL_CHANNEL_SWITCH_AND_TERMINATE_RC Captured whenever the congestion control function switches any user channels or terminates any connections.

393 INTERNAL_START_CONGESTION Captured whenever transmitted carrier power

or uplink interference exceeds its respective threshold value.

Either of the parameters EVENT_PARAM_DL_POWER or

EVENT_PARAM_UL_INTERFERENCE reports a measurement value. The parameter

EVENT_PARAM_DL_POWER reports a measurement value if the cell goes into downlink congestion; otherwise, it is reported as an invalid value. The parameter

EVENT_PARAM_UL_INTERFERENCE reports a measurement value if the cell goes into uplink congestion; otherwise, it is reported as an invalid value.

394 INTERNAL_STOP_CONGESTION Captured whenever transmitted carrier power

or uplink interference has fallen below its respective threshold value.

Either of the parameters EVENT_PARAM_DL_POWER or

EVENT_PARAM_UL_INTERFERENCE reports a measurement value. The parameter

EVENT_PARAM_DL_POWER reports a

measurement value if the cell exits downlink congestion; otherwise it is reported as an

(8)

invalid value. The parameter

EVENT_PARAM_UL_INTERFERENCE reports a measurement value if the cell exits uplink

395 INTERNAL_DOWNLINK_CHANNELIZATION_CODE_ALLOCATION Captured whenever one of the conditions listed

for parameter

EVENT_PARAM_EVENT_TRIGGER occurs. The event shall be sent for each code tree node that is changed.

397 INTERNAL_IRAT_HO_CC_REPORT_RECEPTION Triggered by reception of Measurement Report

from a UE, triggered by event 3a.

398 INTERNAL_IRAT_HO_CC_EVALUATION Evaluation of a newly received or buffered

Measurement Report from a UE, triggered by event 3a.

If no intra-frequency or inter-frequency

handover has been done for this UE before the Inter Radio Access Technology (IRAT)

Handover/IRAT Cell Change trigger is evaluated, the value of the parameters EVENT_PARAM_CPICH_EC_NO_CELL_x and EVENT_PARAM_RSCP_CELL_x is not known to the handover evaluation functionality, and the value will then be set to zero.

399 INTERNAL_IRAT_HO_CC_EXECUTION Decision to hand over or do a cell change to

(9)

400 INTERNAL_IRAT_CELL_CHANGE_DISCARDED_DATA Triggered by ordering a UE disconnection. The event RANAP_IU_RELEASE_COMPLETE is also required to be activated.

401 INTERNAL_CMODE_ACTIVATE Compressed mode activation order received by

the Compressed Mode Control function.

402 INTERNAL_CMODE_DEACTIVATE Compressed mode deactivation received by the

Compressed Mode Control function.

403 INTERNAL_RRC_ERROR Captured whenever one of the errors listed for

the parameter "Error type" occurs.

404 INTERNAL_NBAP_ERROR Captured whenever one of the errors listed for

the parameter "Error type" occurs.

(10)

the parameter "Error type" occurs.

406 INTERNAL_SOFT_HANDOVER_REPORT_RECEPTION Captured when a measurement report is

received from a UE, triggered by event 1x.

407 INTERNAL_SOFT_HANDOVER_EVALUATION Evaluation of a newly received or buffered

measurement report from a UE, triggered by event 1x.

(11)

410 INTERNAL_MEASUREMENT_HANDLING_EVALUATION Evaluation of a newly received or buffered measurement report from a UE, triggered by event 2x.

413 INTERNAL_RNSAP_ERROR Captured whenever one of the errors listed for

the parameter "Error type" occurs.

414 INTERNAL_RC_SUPERVISION This event is reported in relation to the Radio

Connection Supervision algorithms for UEs. It is reported for events in the RCS algorithms for UEs when in CELL_FACH and CELL_DCH states. Furthermore, when in CELL_DCH, it is reported for the separate algorithms used for

connections using an HS-DSCH channel as well as when not using this channel.

Note 1: When in CELL_DCH , a received trigger may be used as a trigger for both the HS and non-HS RCS algorithms. In such cases, only one GPEH event will be generated even though both algorithms are affected.

414 INTERNAL_RC_SUPERVISION - continued Note 2: At timeout of the RCS timer

supervising an HS- DSCH connection, the GPEH event will indicate the action OVERALL_CONNECTION_RELEASE, even though the action taken by the algorithm is a signalling connection release towards the PS Core Network.

Note 3: The event can monitor both RNSAP logical errors and the RNSAP protocol message itself but it must be activate in order to

(12)

Note 4: The event can monitor both RNSAP logical errors and the RNSAP protocol message itself, but must be activated in order to

monitor RNSAP syntactical errors.

415 INTERNAL_RAB_ESTABLISHMENT A RAB ESTABLISHMENT REQUEST with the

"RABs to be setup or modified" IE present (stating an existing RAB ID) is received. Note: for the parameter

EVENT_PARAM_TRAFFIC_CLASS, the value EVENT_VALUE_INVALID is reported in case the RAB Establishment attempt failed to select a target UeRc.

415 - Continue INTERNAL_RAB_ESTABLISHMENT - Continue

416 INTERNAL_RAB_RELEASE Either RAB ASSIGNMENT REQUEST received

with "RABs to be released" or IU RELEASE COMMAND received from a CN with an established RAB when the UE is connected to both CNs.

Note: This means that the event is triggered when at least one RAB is released and at least a signalling connection remains to a CN.

(13)

context, at initial activation of the event and at UE deletion.

418 INTERNAL_UPLINK_SCRAMBLING_CODE_ALLOCATION Sent at request for normal or reduced UL

scrambling code.

419 INTERNAL_MEASUREMENT_HANDLING_EXECUTION Sent to set up or release inter-frequency

measurements.

420 INTERNAL_IFHO_REPORT_RECEPTION This event is to handle the reception of the

RRC event 2b.

Note: The C_ID and RNC_ID parameters will be reported as invalid, since that information is not available in this release.

421 INTERNAL_IFHO_EVALUATION This event is to handle the evaluation of RRC

event 2b.

Note: The C_ID and RNC_ID parameters will be reported as invalid, since that information is not available in this release.

(14)

422 INTERNAL_IFHO_EXECUTION This event handles the proposal of an inter-frequency handover.

423 INTERNAL_IFHO_EXECUTION_ACTIVE This event handles the result of an

Inter-Frequency Handover (IFHO) execution.

425 INTERNAL_MP_OVERLOAD This event is captured when a request for

capacity from the load control function fails.

426 INTERNAL_RBS_HW_MONITOR_UPDATE This event is captured when either additional

RBS hardware (HW) is requested by admission control, or when claimed resources are

released from the RBS HW monitor.

427 INTERNAL_SOHO_DS_MISSING_NEIGHBOUR This event is captured at reception of a

measurement report for event 1a or event 1c, where the triggering cell is not included in neighbor set.

(15)

The parameter EVENT_PARAM_C_ID_1 refers to the best cell in the Active Set. The other cell identity parameters are not provided in any ranking order.

The parameter EVENT_PARAM_RNC_ID_1 refers to the Controlling RNC where the best cell in the Active Set, is allocated. The other RNC identity parameters are not provided in any ranking order.

428 INTERNAL_SOHO_DS_UNMONITORED_NEIGHBOUR Captured when handover proposal is received,

where the proposed cell is included in the neighbor set, but not included in the monitored set.

429 INTERNAL_UE_POSITIONING_QOS Captured when the UE has successfully

performed a positioning attempt and the result is sent to the Core Network.

(16)

429 Continued INTERNAL_UE_POSITIONING_QOS Continued

(17)

429 Continued INTERNAL_UE_POSITIONING_QOS Continued

(18)

429 Continued INTERNAL_UE_POSITIONING_QOS Continued

430 INTERNAL_UE_POSITIONING_UNSUCC Captured whenever the execution fails and

another method is selected instead.

431 INTERNAL_SYSTEM_BLOCK Captured when the Admission Control response

indicates that the admission request is rejected.

(19)

432 INTERNAL_SUCCESSFUL_HSDSCH_CELL_CHANGE Captured after reception of RRC Physical Channel Reconfiguration Complete after a High Speed Downlink Shared Channel (HS-DSCH) cell change.

433 INTERNAL_FAILED_HSDSCH_CELL_CHANGE Captured in different failure cases after an

(20)

434 INTERNAL_SUCCESSFUL_HSDSCH_CELL_SELECTION_OLD_ACTIVE_SET Captured during HS-DSCH cell selection when a new cell has been selected in the old active set.

435 INTERNAL_SUCCESSFUL_HSDSCH_CELL_SELECTION_NEW_ACTIVE_SET Captured during HS-DSCH cell selection when a new cell has been selected after hard

handover.

436 INTERNAL_HSDSCH_CELL_SELECTION_NO_CELL_SELECTED Captured during HS-DSCH cell selection when

no new cell has been selected. This contains both normal and failure cases.

437 INTERNAL_TWO_NON_USED_FREQ_EXCEEDED Captured when inter-frequency neighbors

exists on more than two different non-used frequencies when creating an Inter Frequency (IEF) Monitored Set.

(21)

EVENT_PARAM_CPICH_EC_NO_CELL_1: Downlink Common Pilot Channel (CPICH) Ec/No for best cell in active set, provided that Ec/No is used as the measured quality. Otherwise this value relates to the best cell considering that Received Signal Code Power

437 INTERNAL_TWO_NON_USED_FREQ_EXCEEDED - continued EVENT_PARAM_CPICH_EC_NO_CELL_2:

Downlink CPICH Ec/No for second best cell in active set, provided that Ec/No is used as the measured quality. Otherwise this value relates to the best cell considering that RSCP is used as measured quality.

EVENT_PARAM_CPICH_EC_NO_CELL_3: Downlink CPICH Ec/No for third best cell in active set, provided that Ec/No is used as the measured quality. Otherwise this value relates to the best cell considering that RSCP is used as measured quality.

EVENT_PARAM_CPICH_EC_NO_CELL_4: DL CPICH Ec/No for fourth best cell in active set, provided that Ec/No is used as the measured quality. Otherwise this value relates to the best cell considering that RSCP is used as measured quality.

437 INTERNAL_TWO_NON_USED_FREQ_EXCEEDED - continued EVENT_PARAM_RSCP_CELL_1: RSCP for best

cell in active set, provided that RSCP is used as the measured quality. Otherwise this value relates to the best cell considering that Ec/No is used as measured quality. Note: If no soft or softer handover 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_CELL_2: RSCP for second best cell in active set, provided that RSCP is used as the measured quality. Otherwise this value relates to the best cell considering that Ec/No is used as measured quality.

437 INTERNAL_TWO_NON_USED_FREQ_EXCEEDED - continued EVENT_PARAM_RSCP_CELL_3: RSCP for third

best cell in active set, provided that RSCP is used as the measured quality. Otherwise this

(22)

value relates to the best cell considering that Ec/No is used as measured quality.

EVENT_PARAM_RSCP_CELL_4: RSCP for fourth best cell in active set, provided that RSCP is used as the measured quality. Otherwise this value relates to the best cell considering that Ec/No is used as measured quality.

438 INTERNAL_SYSTEM_RELEASE Captured each time one or several RABs or a

stand-alone RRC connection is released, and the release is not a normal release.

EVENT_PARAM_C_ID_1 represents the best cell in the Active Set. The order other cell parameters are not ranked in any quality order.

Note: Most of the parameters have a very specific behavior for this particular event. Be sure to check the event parameter details in Section 3

438 INTERNAL_SYSTEM_RELEASE - continued

(23)

439 INTERNAL_CNHHO_EXECUTION_ACTIVE Captured when a CNHHO Execution is performed (successful or unsuccessful).

440 INTERNAL_PS_RELEASE_DUE_TO_CNHHO Captured when the Packet Switched RAB has

been released due to a Core Network Hard Handover (CNHHO).

441 INTERNAL_PACKET_DEDICATED_THROUGHPUT The event periodically (every two seconds)

reports the UL/DL data rate separately for all RB's on the transport channel (more than one RB on the transport channel in case of MAC-d multiplexing). The UL/DL throughput for PS interactive data only reported for these

transport channels DCH/E-DCH/HS-DSCH (that is, no reporting when the PS RB is carried over

(24)

FACH/RACH). The events are scheduled in the same order each time (every 2 seconds) so that it is possible to follow the throughput per

442 INTERNAL_SUCCESSFUL_TRANSITION_TO_DCH The event is generated when Radio Bearer

Reconfiguration Complete is received from the UE, during an attempt to do a transition from a connection using Enhanced Dedicated

Channel/High Speed Downlink Shared Channel (E-DCH/ HS-DSCH) or DCH/HS-DSCH

capabilities to a Dedicated Channel (DCH) connection.

443 INTERNAL_FAILED_TRANSITION_TO_DCH The event is generated after a failure to

complete a transition from a connection Enhanced Dedicated Channel/High Speed Downlink Shared Channel (E-DCH/ HS-DSCH) or DCH/HS-DSCH capabilities to a Dedicated Channel (DCH) connection..

444 INTERNAL_RECORDING_FAULT Captured every time an error occurs which

impacts the event recording on some entity in the RNC.

The parameter

EVENT_PARAM_RNC_MODULE_ID are reported as invalid.

(25)

445 INTERNAL_RECORDING_RECOVERED Captured every time an error situation has recovered in relation to event recording in RNC.

The parameter

EVENT_PARAM_RNC_MODULE_ID are reported as invalid.

446 INTERNAL_PACKET_DEDICATED_THROUGHPUT_STREAMING When activated, the event periodically (every 2

seconds) reports the UL/DL data rate and the UL/DL throughput for PS Streaming data measured in CELL_DCH/E-DCH and CELL_HS-DSCH states.

447 INTERNAL_MBMS_SESSION_START_FAILED Unsuccessful establishment of a ptm RB

(MTCH) in a cell due to any failure.

448 INTERNAL_MBMS_SESSION_START_SUCCESS Successful establishment of a ptm RB (MTCH)

in a cell.

449 INTERNAL_MBMS_SESSION_STOP_SYSTEM Release of a ptm RB (MTCH) in a cell when the

trigger is any system internal event.

450 INTERNAL_MBMS_SESSION_STOP_NORMAL The MBMS Session Stop is triggered by RANAP

message MBMS SESSION STOP.

(26)

451_Continued INTERNAL_SYSTEM_UTILIZATION Continued

452 INTERNAL_PCAP_ERROR The event is triggered by a failure in the PCAP

signalling protocol, for example, PCAP procedure failure, timeout, or PCAP protocol error.

(27)

453 INTERNAL_CBS_MESSAGE_ORDER_DISCARDED The event is triggered whenever a CBS Message order is discarded by RNC due to internal congestion. One event per cell is generated if the CBS message is broadcast in several Service Areas (cells).

454 INTERNAL_PACKET_DEDICATED_THROUGHPUT_CONV_UNKNOWN The event periodically (every 2 seconds)

reports the UL/DL data rate and the UL/DL throughput for PS Conversational Unknown data measured in CELL_DCH/E-DCH and CELL_HS-DSCH states when activated.

455 INTERNAL_PACKET_DEDICATED_THROUGHPUT_CONV_SPEECH The event periodically (every 2 seconds)

reports the UL/DL data rate and the UL/DL throughput for PS Conversational Speech data measured in CELL_DCH/E-DCH and CELL_HS-DSCH states when activated.

456 INTERNAL_CALL_SETUP_FAIL The event will capture each time a call setup

attempt fails, either at sending of RAB Assignment Response indicating failure to setup or modify RABs, or when a signalling connection is released and the release is not a normal release. A call setup attempt can be detected from the establishment cause in RRC Connection Request, Cell Update, Initial Direct Transfer or through reception of RAB

Assignment Request with the IE RABs to be setup or modified.

(28)

458 INTERNAL_OUT_HARD_HANDOVER_FAILURE The event shall be triggered for any failure case between the following points for a Hard Handover (IRATHO/CC, IFHO, CNHHO): Execution proposal from Handover evaluation –> Termination of procedure

(29)

459 INTERNAL_RES_CPICH_ECNO The event shall be triggered periodically based on RES measurement periodicity. Additionally it shall be triggered at call set up.

459 Continued INTERNAL_RES_CPICH_ECNO Continued

(30)

475 INTERNAL_OUT_HARD_HANDOVER_SUCCESS The event shall be triggered for any successful case between the following points for a Hard Handover (IRATHO/CC, IFHO, CNHHO): Execution proposal from Handover evaluation -> Termination of procedure.

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

(31)

 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)

(32)

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 Id

Event Name Comments

0 RRC_ACTIVE_SET_UPDATE

1 RRC_ACTIVE_SET_UPDATE_COMPLETE

2 RRC_ACTIVE_SET_UPDATE_FAILURE Reported as “Not Applicable” for this event

3 RRC_CELL_UPDATE

(33)

5 RRC_DOWNLINK_DIRECT_TRANSFER

6 RRC_MEASUREMENT_CONTROL

7 RRC_MEASUREMENT_CONTROL_FAILURE

8 RRC_MEASUREMENT_REPORT

If the Radio Environment Statistics function is active there will be

RRC_MEASUREMENT_REPORT events generates periodically. The periodicity is configurable between 2 and 64 seconds. The default periodicity is 16 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_1..4, and EVENT_PARAM_RNC_ID_1...4

(34)

parameters are reported as “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

Id Event Name Comments

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

(35)

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 NBAP_ERROR_INDICATION The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 151 NBAP_COMMON_TRANSPORT_CHANNEL_SETUP_REQUEST The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 152 NBAP_COMMON_TRANSPORT_CHANNEL_SETUP_RESPONSE The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 153 NBAP_COMMON_TRANSPORT_CHANNEL_SETUP_FAILURE The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 154 NBAP_COMMON_TRANSPORT_CHANNEL_RECONFIGURATION_REQUEST The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”.

155 NBAP_COMMON_TRANSPORT_CHANNEL_RECONFIGURATION_RESPONSE The

EVENT_PARAM_C_ID_1..4, and

(36)

EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 156 NBAP_COMMON_TRANSPORT_CHANNEL_RECONFIGURATION_FAILURE The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 157 NBAP_COMMON_TRANSPORT_CHANNEL_DELETION_REQUEST The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 158 NBAP_COMMON_TRANSPORT_CHANNEL_DELETION_RESPONSE The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 159 NBAP_AUDIT_REQUIRED_INDICATION The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 160 NBAP_AUDIT_REQUEST The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 161 NBAP_AUDIT_RESPONSE The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 162 NBAP_AUDIT_FAILURE The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”.

163 NBAP_COMMON_MEASUREMENT_INITIATION_REQUEST The

EVENT_PARAM_C_ID_1..4, and

EVENT_PARAM_RNC_ID_1...4 parameters are reported as

(37)

“Not Applicable”. 164 NBAP_COMMON_MEASUREMENT_INITIATION_RESPONSE The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 165 NBAP_COMMON_MEASUREMENT_INITIATION_FAILURE The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 166 NBAP_COMMON_MEASUREMENT_REPORT The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 167 NBAP_COMMON_MEASUREMENT_TERMINATION_REQUEST The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 168 NBAP_COMMON_MEASUREMENT_FAILURE_INDICATION The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 169 NBAP_CELL_SETUP_REQUEST The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 170 NBAP_CELL_SETUP_RESPONSE The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 171 NBAP_CELL_SETUP_FAILURE The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”.

(38)

EVENT_PARAM_C_ID_1..4, and

EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 173 NBAP_CELL_RECONFIGURATION_RESPONSE The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 174 NBAP_CELL_RECONFIGURATION_FAILURE The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 175 NBAP_CELL_DELETION_REQUEST The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 176 NBAP_CELL_DELETION_RESPONSE The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 177 NBAP_RESOURCE_STATUS_INDICATION The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 178 NBAP_SYSTEM_INFORMATION_UPDATE_REQUEST The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 179 NBAP_SYSTEM_INFORMATION_UPDATE_RESPONSE The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”.

180 NBAP_SYSTEM_INFORMATION_UPDATE_FAILURE The

EVENT_PARAM_C_ID_1..4, and

(39)

EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 181 NBAP_RESET_REQUEST The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 182 NBAP_RESET_RESPONSE The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 183 NBAP_COMPRESSED_MODE_COMMAND 184 NBAP_RADIO_LINK_PARAMETER_UPDATE_INDICATION 185 NBAP_PHYSICAL_SHARED_CHANNEL_RECONFIGURATION_REQUEST The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 186 NBAP_PHYSICAL_SHARED_CHANNEL_RECONFIGURATION_RESPONSE The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”. 187 NBAP_PHYSICAL_SHARED_CHANNEL_RECONFIGURATION_FAILURE The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”.

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

(40)

256 RANAP_RAB_ASSIGNMENT_REQUEST 257 RANAP_RAB_ASSIGNMENT_RESPONSE 258 RANAP_IU_RELEASE_REQUEST 259 RANAP_IU_RELEASE_COMMAND The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”.

260 RANAP_IU_RELEASE_COMPLETE

The EVENT_PARAM_C_ID_1..4, and

EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not 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 267 RANAP_PAGING 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”. 268 RANAP_COMMON_ID 269 RANAP_INITIAL_UE_MESSAGE 270 RANAP_RESET 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”.

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

(41)

EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not Applicable”.

272 RANAP_RESET_RESOURCE

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”.

273 RANAP_RESET_RESOURCE_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”. 274 RANAP_RELOCATION_REQUIRED 275 RANAP_RELOCATION_REQUEST The EVENT_PARAM_C_ID_1..4, and EVENT_PARAM_RNC_ID_1...4 parameters are reported as “Not 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

(42)

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

Id Event Name Comments

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

(43)

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

Id Event Name Comments

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

Id Event Name Comments

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

(44)

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 measurement report, addition of new RL, reactivation of CM triggered by UE measurement report, other cause.

4 EVENT_VALUE_ACT_BY_UE_MEAS_REP EVENT_VALUE_ADD_NEW_RL EVENT_VALUE_REACT_BY_UE_MEAS_REP EVENT_VALUE_OTHER EVENT_VALUE_IFLBHO EVENT_VALUE_GSMLBHO EVENT_PARAM_ACTION

The action taken when the event was generated. 7 EVENT_VALUE_ADD_CELL_PROPOSAL

EVENT_VALUE_REMOVE_CELL_PROPOSAL EVENT_VALUE_REPLACE_CELL_PROPOSAL EVENT_VALUE_RELEASE_DUE_TO_OLDEST_1D_REPORT_TOO_OLD EVENT_VALUE_RELEASE_DUE_TO_NONVALID_CELL_REPORTED EVENT_VALUE_RELEASE_DUE_TO_FULL_1B_BUFFER EVENT_VALUE_RELEASE_DUE_TO_FULL_1D_BUFFER EVENT_VALUE_START_GSM_MEASUREMENTS_CM EVENT_VALUE_STOP_GSM_MEASUREMENTS_CM EVENT_VALUE_START_GSM_MEASUREMENTS_NON_CM EVENT_VALUE_STOP_GSM_MEASUREMENTS_NON_CM EVENT_VALUE_NO_ACTION EVENT_VALUE_OVERALL_CONNECTION_RELEASE EVENT_VALUE_RCS_CU_TIMER_STARTED EVENT_PARAM_ACTION - continued

(45)

EVENT_VALUE_RCS_CU_TIMER_CANCELLED EVENT_VALUE_RLS_TAG_CREATED EVENT_VALUE_RLS_TAG_DELETED EVENT_VALUE_RLS_FLAG_CHANGE_TO_FAIL_NO_ACTION EVENT_VALUE_RLS_FLAG_CHANGE_TO_FAIL_RCS_WAIT_STARTED EVENT_VALUE_RLS_FLAG_REMAINS_FAIL_NO_ACTION EVENT_VALUE_RLS_FLAG_CHANGE_TO_OK_NO_ACTION EVENT_VALUE_RLS_FLAG_CHANGE_TO_OK_RCS_WAIT_CANCELLED EVENT_VALUE_PROPOSED_HO_OR_CC_TO_GSM EVENT_VALUE_EVALUATION_OF_REPORT EVENT_VALUE_BUFFERING_OF_REPORT EVENT_VALUE_START_IEF_MEASUREMENTS_PROP EVENT_VALUE_STOP_IEF_MEASUREMENTS_PROP EVENT_VALUE_START_GSM_MEASUREMENTS_PROP EVENT_VALUE_STOP_GSM_MEASUREMENTS_PROP EVENT_PARAM_ACTION - continued EVENT_VALUE_START_IEF_MEASUREMENTS_CM EVENT_VALUE_STOP_IEF_MEASUREMENTS_CM EVENT_VALUE_START_IEF_MEASUREMENTS_NON_CM EVENT_VALUE_STOP_IEF_MEASUREMENTS_NON_CM EVENT_VALUE_PROPOSED_IFHO EVENT_VALUE_PROPOSED_INTRA_CNHHO EVENT_VALUE_PROPOSED_INTER_FREQ_CNHHO EVENT_VALUE_START_SBHO_MEASUREMENTS_NON_CM EVENT_VALUE_START_SBHO_MEASUREMENTS_CM EVENT_VALUE_STOP_SBHO_MEASUREMENTS_NON_CM EVENT_VALUE_STOP_SBHO_MEASUREMENTS_CM EVENT_VALUE_START_EMERCALL_MEASUREMENTS_NON_CM EVENT_VALUE_START_EMERCALL_MEASUREMENTS_CM EVENT_PARAM_ACTION - continued EVENT_VALUE_STOP_EMERCALL_MEASUREMENTS_NON_CM EVENT_VALUE_STOP_EMERCALL_MEASUREMENTS_CM EVENT_VALUE_START_LBHO_MEASUREMENTS_NON_CM EVENT_VALUE_START_LBHO_MEASUREMENTS_CM EVENT_VALUE_STOP_LBHO_MEASUREMENTS_NON_CM EVENT_VALUE_STOP_LBHO_MEASUREMENTS_CM EVENT_VALUE_START_GAN_MEASUREMENTS EVENT_VALUE_STOP_GAN_MEASUREMENTS EVENT_VALUE_START_GSM_GAN_MEASUREMENTS_CM EVENT_VALUE_START_GSM_GAN_MEASUREMENTS_NON_CM

(46)

EVENT_VALUE_STOP_GSM_GAN_MEASUREMENTS_CM EVENT_VALUE_STOP_GSM_GAN_MEASUREMENTS_NON_CM

EVENT_PARAM_ASE_REDUCTION

Number of reduced Air interface Speech Equivalents (ASEs). 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.

17

EVENT_PARAM_NO_OF_CELLS_IN_ACTIVE_SET Parameter value 0 = one cell

Parameter value 1 = two cells ...

Parameter value 3 = four cells

3

EVENT_PARAM_NO_OF_CELLS_IN_REPORT

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

Parameter value 0 = one cell Parameter value 1 = two cells ...

Parameter value 3 = four cells

3

EVENT_PARAM_CHANNEL_SWITCH_REASON

Reason for channel switch. 5 EVENT_VALUE_CONGESTION_CONTROL

EVENT_VALUE_TRAFFIC_VOLUME_MEAS_INIT EVENT_VALUE_INTERNALLY_INITIATED_RNC EVENT_VALUE_COVERAGE_TRIGGERED EVENT_VALUE_SOFT_HANDOVER EVENT_VALUE_UNAVAILABLE_DL_CODE_POWER_MEASUREMENT EVENT_VALUE_EXPIRY_HS_DSCH_INACTIVITY_TIMER EVENT_VALUE_TRAFFIC_VOLUME_MEAS_INIT_UL EVENT_VALUE_THROUGHPUT_DOWNSWITCH_DL EVENT_VALUE_THROUGHPUT_DOWNSWITCH_UL EVENT_VALUE_ENHANCED_SOFT_CONGESTION_CONTROL EVENT_VALUE_UE_POSITIONING EVENT_VALUE_LOAD_CONTROL=x

(47)

EVENT_VALUE_OVERLOAD_CONTROL=y

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_DL_ONLY

EVENT_VALUE_UL_AND_DL EVENT_VALUE_UL_ONLY

EVENT_PARAM_DEACT_REASON

Any of the following reasons: deactivation decision triggered by UE measurement report, addition of new RL, other reason.

4 EVENT_VALUE_DEACT_BY_UE_MEAS_REP EVENT_VALUE_ADD_NEW_RL EVENT_VALUE_OTHER EVENT_VALUE_IFLBHO EVENT_VALUE_GSMLBHO EVENT_PARAM_DL_POWER DL power.

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.

11

EVENT_PARAM_EVENT_TRIGGER

Trigger for recording the event. 8 EVENT_VALUE_BELOW_NEG_UL_SIR_GUARD

EVENT_VALUE_ABOVE_POS_UL_SIR_GUARD EVENT_VALUE_BETWEEN_POS_NEG_UL_SIR_GUARD EVENT_VALUE_NON_HSDSCH_POWER EVENT_VALUE_LOAD_INCREASE EVENT_VALUE_LOAD_DECREASE EVENT_VALUE_EVENT_TRIGGERED_REPORT EVENT_VALUE_PERIODIC_REPORT EVENT_VALUE_REQUEST_FOR_DL_CODES_FOR_NORMAL_MODE EVENT_VALUE_RELEASE_OF_DL_CODES_IN_NORMAL_MODE EVENT_VALUE_ALLOC_FAILED_EXCESS_RATE_REQUEST EVENT_VALUE_ALLOC_FAILED_NO_SUITABLE_CODE_FREE EVENT_PARAM_EVENT_TRIGGER - continued EVENT_VALUE_REQUEST_FOR_DL_CODES_NORM_TREE_COMP_MODE

(48)

EVENT_VALUE_REQUEST_FOR_DL_CODES_ALT_TREE_COMP_MODE EVENT_VALUE_RELEASE_OF_DL_CODES_IN_COMP_MODE EVENT_VALUE_EVENT_1A EVENT_VALUE_EVENT_1B EVENT_VALUE_EVENT_1C EVENT_VALUE_EVENT_1D EVENT_VALUE_EVENT_2D EVENT_VALUE_EVENT_2F EVENT_VALUE_ADD_CELL_PROPOSAL EVENT_VALUE_REMOVE_CELL_PROPOSAL EVENT_VALUE_REPLACE_CELL_PROPOSAL EVENT_VALUE_UE_LEAVES_DCH_STATE EVENT_VALUE_CELL_UPDATE_RECEIVED EVENT_VALUE_CELL_UPDATE_CONFIRMED_SENT EVENT_PARAM_EVENT_TRIGGER - continued EVENT_VALUE_RCS_CU_TIMER_EXPIRED EVENT_VALUE_RL_SETUP_OR_ADDITION_RESPONSE_RECEIVED EVENT_VALUE_RL_RESTORE_RECEIVED EVENT_VALUE_RL_FAILURE_RECEIVED EVENT_VALUE_RL_DELETION_RESPONSE_RECEIVED EVENT_VALUE_RCS_WAIT_TIMER_EXPIRED EVENT_VALUE_PROPOSED_HO_TO_GSM EVENT_VALUE_PROPOSED_CC_TO_GSM EVENT_VALUE_EVENT_3A EVENT_VALUE_IU_RELEASE_COMMAND EVENT_VALUE_RAB_ASSIGNMENT_REQUEST EVENT_VALUE_REQ_FOR_NORMAL_UL_SCRAMBLING_CODE EVENT_VALUE_REQ_FOR_REDUCED_UL_SCRAMBLING_CODE EVENT_VALUE_OTHER_TRIGGER EVENT_VALUE_EVENT_6A EVENT_VALUE_EVENT_6B EVENT_PARAM_EVENT_TRIGGER - continued EVENT_VALUE_START_IEF_MEASUREMENTS_PROP EVENT_VALUE_STOP_IEF_MEASUREMENTS_PROP EVENT_VALUE_START_GSM_MEASUREMENTS_PROP EVENT_VALUE_STOP_GSM_MEASUREMENTS_PROP EVENT_VALUE_EVENT_2B EVENT_VALUE_PROPOSED_IFHO EVENT_VALUE_COMPLETED_IFHO_ATTEMPT EVENT_VALUE_PROPOSED_SBHO_TO_GSM

(49)

EVENT_VALUE_POOR_QUALITY_DETECTED EVENT_VALUE_SERV_HS_CELL_CHANGE_NOT_POSSIBLE EVENT_VALUE_OVERLOAD EVENT_VALUE_RESTART EVENT_VALUE_FILE_SIZE_EXCEEDED EVENT_VALUE_FILE_SYSTEM_ERROR EVENT_VALUE_PARTIAL_OVERLOAD EVENT_PARAM_EVENT_TRIGGER - continued EVENT_VALUE_FILE_SIZE__PARTIAL_EXCEEDED EVENT_VALUE_URA_UPDATE_RECEIVED EVENT_VALUE_PROPOSED_EMERCALL_TO_GSM EVENT_VALUE_1D_RNC EVENT_VALUE_HSDSCH_REQUIRED_POWER EVENT_VALUE_PROPOSED_LBHO_TO_GSM EVENT_VALUE_IFLBHO EVENT_VALUE_LOSS_OF_FDPCH EVENT_VALUE_GSMLBHO EVENT_VALUE_PROPOSED_HO_TO_GAN EVENT_VALUE_PROPOSED_CC_TO_GAN EVENT_VALUE_START_GAN_MEASUREMENTS_PROP EVENT_VALUE_STOP_GAN_MEASUREMENTS_PROP EVENT_VALUE_START_GSM_GAN_MEASUREMENTS_PROP EVENT_VALUE_STOP_GSM_GAN_MEASUREMENTS_PROP EVENT_PARAM_FAILURE_REASON

Failure reason. 8 EVENT_VALUE_BLOCKED_BY_CONGESTION_CTRL

EVENT_VALUE_UL_ASE_LOAD_INCREASE_TOO_HIGH EVENT_VALUE_DL_ASE_LOAD_INCREASE_TOO_HIGH EVENT_VALUE_DL_CODE_USAGE_TOO_HIGH EVENT_VALUE_DL_POWER_INCREASE_TOO_HIGH EVENT_VALUE_TOO_MANY_USERS_WITH_SF8 EVENT_VALUE_TOO_MANY_USERS_WITH_SF16 EVENT_VALUE_TOO_MANY_USERS_WITH_SF32 EVENT_VALUE_COMP_MODE_LIMIT EVENT_VALUE_OTHER EVENT_VALUE_ASU_FAILURE EVENT_VALUE_RL_SETUP_FAILURE EVENT_VALUE_DL_CHANNEL_CODE_REJECTED EVENT_VALUE_ADMISSION_REJECTED EVENT_PARAM_FAILURE_REASON - continued

(50)

EVENT_VALUE_UNSUPPORTED_RADIO_CONF_IN_UTRAN EVENT_VALUE_UNSUPPORTED_RADIO_CONF_IN_UE EVENT_VALUE_AAL2_FAILED_OVER_IU EVENT_VALUE_IU_UP_PROCEDURE_FAILED EVENT_VALUE_LACK_OF_RESOURCES_IN_SRNC EVENT_VALUE_TIMEOUT_ON_NBAP EVENT_VALUE_TIMEOUT_ON_RNSAP EVENT_VALUE_TIMEOUT_ON_RRC EVENT_VALUE_RADIO_LINK_RECONFIGURATION_FAILURE_RECEIVED EVENT_VALUE_RADIO_LINK_SETUP_FAILURE_RECEIVED EVENT_VALUE_CELL_UPDATE_FAILS EVENT_VALUE_NO_RESPONSE_OVER_IUR EVENT_VALUE_NO_RESPONSE_FROM_UE EVENT_VALUE_RADIO_BEARER_RELEASE_FAILURE_RECEIVED EVENT_PARAM_FAILURE_REASON - continued EVENT_VALUE_INVALID_RAB_ID EVENT_VALUE_LOAD_SHARING EVENT_VALUE_INSUFFICIENT_UE_CAPABILITIES EVENT_VALUE_RC_QUALITY_GOOD EVENT_VALUE_UE_FAILURE_TO_SYNCHRONIZE EVENT_VALUE_UE_FAILURE_OTHER EVENT_VALUE_UE_CIPHERING_FAILURE EVENT_VALUE_LOGICAL_ERROR_NBAP EVENT_VALUE_LOGICAL_ERROR_RNSAP EVENT_VALUE_LOGICAL_ERROR_RRC EVENT_VALUE_ERRORIND_NBAP EVENT_VALUE_ERRORIND_RNSAP EVENT_VALUE_RL_ADDITION_FAILURE EVENT_VALUE_ADMISSION_REJECT_USAAL_CONGESTION EVENT_PARAM_FAILURE_REASON - continued EVENT_VALUE_SP0_UNSUPPORTED_RADIO_CONF_IN_UE EVENT_VALUE_UNSUPPORTED_IUR_CCH EVENT_VALUE_NO_UL_RBS_HW_RESOURCES EVENT_VALUE_NO_DL_RBS_HW_RESOURCES EVENT_VALUE_SOFTCONGESTION EVENT_VALUE_RADIO_BEARER_SETUP_FAILURE_RECEIVED EVENT_VALUE_PHYSICAL_CHANNEL_RECONFIGURATION_FAILURE_RECEIVED EVENT_VALUE_FORCED_PROCEDURE_ABORT EVENT_VALUE_HRNTI_ALLOC_FAILURE EVENT_VALUE_TN_RES_ALLOC_IUB_FAILURE

(51)

EVENT_VALUE_NO_CANDIDATE EVENT_VALUE_CANDIDATE_NOT_ENABLED EVENT_VALUE_NO_PATHLOSSVALUE EVENT_VALUE_PATHLOSS_TOO_HIGH EVENT_PARAM_FAILURE_REASON - continued EVENT_VALUE_NO_CELLS_PARAMS EVENT_VALUE_TOO_MANY_USERS_ON_HSPDSCH EVENT_VALUE_TOO_MANY_USERS_WITH_SF4 EVENT_VALUE_TOO_MANY_G_USERS_WITH_SF16 EVENT_VALUE_FAULTY_STATE EVENT_VALUE_RELOCATION_TIMEOUT EVENT_VALUE_NOT_SUCCESSFUL_RELEASE EVENT_VALUE_RELOCATION_FAILURE EVENT_VALUE_TOO_MANY_USERS_WITH_UL_SF8 EVENT_VALUE_TOO_MANY_USERS_WITH_UL_SF16 EVENT_VALUE_UNKNOWN_RNC_RESOURCE_STATUS EVENT_VALUE_NBAP_FAILURE EVENT_VALUE_RRC_FAILURE EVENT_PARAM_FAILURE_REASON - continued EVENT_VALUE_TOO_MANY_G_USERS_WITH_SF8 EVENT_VALUE_RADIO_BEARER_RECONFIGURATION_FAILURE_RECEIVED EVENT_VALUE_TOO_MANY_SERVING_CELL_USERS_EUL EVENT_VALUE_TOO_MANY_NON_SERVING_CELL_USERS_EUL EVENT_VALUE_MAX_NO_OF_PL_SESSIONS_REACHED EVENT_VALUE_MAX_NO_OF_NON_PL_SESSIONS_REACHED EVENT_VALUE_ABNORMAL_SESSION_STOP_DUE_TO_CN EVENT_VALUE_RN_UL_TOO_MANY_SERVING_CELL_USERS_TTI2EUL EVENT_VALUE_TN_IUB_DL_ADM_BLOCK EVENT_VALUE_TN_IUB_UL_ADM_BLOCK EVENT_PARAM_CPICH_EC_NO_CELL_1

Downlink Common Pilot Channel (CPICH) Ec/No for the first 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.

7

EVENT_PARAM_CPICH_EC_NO_CELL_2

(52)

-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 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.

7

EVENT_PARAM_CPICH_EC_NO_CELL_4

Downlink Common Pilot Channel (CPICH) Ec/No for the fourth 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.

7

EVENT_PARAM_CPICH_EC_NO_EVAL_CELL

Downlink Common Pilot Channel (CPICH) Ec/No for evaluated 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.

7

EVENT_PARAM_RSCP_CELL_1

Received Signal Code Power (RSCP) for first cell in the 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.

(53)

EVENT_PARAM_RSCP_CELL_2

Received Signal Code Power (RSCP) for second cell in the 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.

8

EVENT_PARAM_RSCP_CELL_3

Received Signal Code Power (RSCP) for third cell in the 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.

8

EVENT_PARAM_RSCP_CELL_4

Received Signal Code Power (RSCP) for fourth cell in the 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.

8

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

(54)

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

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.

10

EVENT_PARAM_SCRAMBLING_CODE_NCELL_2

DL primary scrambling code for 2nd highest ranked cell in 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.

10

EVENT_PARAM_SCRAMBLING_CODE_NCELL_3

DL primary scrambling code for 3rd highest ranked cell in 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.

10

EVENT_PARAM_SCRAMBLING_CODE_NCELL_4

DL primary scrambling code for 4th highest ranked cell in 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.

10

EVENT_PARAM_SCRAMBLING_CODE_NCELL_5

DL primary scrambling code for 5th highest ranked cell in 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

(55)

-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 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.

10

EVENT_PARAM_CPICH_EC_NO_NCELL_1

DL CPICH Ec/No for highest ranked cell in 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. 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.

7

EVENT_PARAM_CPICH_EC_NO_NCELL_2

DL CPICH Ec/No for 2nd highest ranked cell in 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. Resolution 0.5.

7

EVENT_PARAM_CPICH_EC_NO_NCELL_3

DL CPICH Ec/No for 3rd highest ranked cell in 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. Resolution 0.5.

7

EVENT_PARAM_CPICH_EC_NO_NCELL_4

DL CPICH Ec/No for 4th highest ranked cell in 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. Resolution 0.5.

7

EVENT_PARAM_CPICH_EC_NO_NCELL_5

DL CPICH Ec/No for 5th highest ranked cell in monitored and detected set, provided that Ec/No is used as the measured quantity given by the attribute measQuantity1 for MO class

(56)

-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 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.

7

EVENT_PARAM_RSCP_NCELL_1

RSCP for highest ranked cell in monitored and detected 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. 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.

8

EVENT_PARAM_RSCP_NCELL_2

RSCP for 2nd highest ranked cell in monitored and detected 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.

8

EVENT_PARAM_RSCP_NCELL_3

RSCP for 3rd highest ranked cell in monitored and detected 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.

8

EVENT_PARAM_RSCP_NCELL_4

RSCP for 4th highest ranked cell in monitored and detected 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.

8

EVENT_PARAM_RSCP_NCELL_5

RSCP for 5th highest ranked cell in monitored and detected set, provided that RSCP is used as the measured quantity given by the attribute measQuantity1 for MO class

(57)

-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 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.

8

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

set. 9

EVENT_PARAM_SYNCH_INFO_OFF_NCELL3

OFF for the 3rd highest ranked cell in monitored and detected

set. 9

EVENT_PARAM_SYNCH_INFO_OFF_NCELL4

OFF for the 4th highest ranked cell in monitored and detected

set. 9

EVENT_PARAM_SYNCH_INFO_OFF_NCELL5

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

9

EVENT_PARAM_SYNCH_INFO_OFF_NCELL6

OFF for the 6th highest ranked cell in monitored and detected

set. 9

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

set. 17

EVENT_PARAM_SYNCH_INFO_TM_NCELL3

Tm for the 3rd highest ranked cell in monitored and detected set.

(58)

EVENT_PARAM_SYNCH_INFO_TM_NCELL4

Tm for the 4th highest ranked cell in monitored and detected

set. 17

EVENT_PARAM_SYNCH_INFO_TM_NCELL5

Tm for the 5th highest ranked cell in monitored and detected

set. 17

EVENT_PARAM_SYNCH_INFO_TM_NCELL6

Tm for the 6th highest ranked cell in monitored and detected

set. 17

EVENT_PARAM_HHO_TARGET_ID_1

In general the HO type is determined by the combination of 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.

17

EVENT_PARAM_HHO_TARGET_ID_2

In general the HO type is determined by the combination of 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).

25

EVENT_PARAM_HHO_TARGET_ID_3

In general the HO type is determined by the combination of 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.

17

EVENT_PARAM_HHO_TARGET_ID_4

In general the HO type is determined by the combination of 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.

Figure

Updating...

Related subjects :