100.2 GSM/WCDMA/LTE Events

Events in this category are generated by devices supporting at least one of the technologies GSM, WCDMA and LTE.
The following is to be noted:
Call events also encompass VoIP calls. For convenience, this is covered in the present section rather than in section "Data Service Testing Events", ""Data Service Testing Events"".
Regarding call events, see also the documents "TEMS Investigation CS Call Event Definitions" and "TEMS Investigation PS Call Event Definitions", which are found in the TEMS Investigation documentation package.
The asterisk column uses the following codes:

Code

Meaning

c

Requires that a cell file has been loaded.

e

Generated in EDGE mode.

g

Generated in GSM mode.

lte

Generated in LTE mode.

ps

Generated for packet-switched (specifically, VoIP calls).

sg

Generated during GSM scanning.

sw

Generated during WCDMA scanning.

w

Generated in WCDMA mode.
Event List

Event Name

Symbol

*

Description/Extra Information

Refined

Answer End

 

An Answer activity completed.

Extra information: Service status.

Serving Radio Technology

✔

Answer Start

 

An Answer activity started.

Extra information:

Serving Radio Technology

✔

Answer Error

 

An Answer activity failed.

Extra information:

Error Cause

Serving Radio Technology

✔

Authentication Failure

g
w

The authentication or ciphering failed.

Can be generated for both packet-switched and circuit-switched.

Extra information: GMM/MM cause (if available).

✔

Call events (Blocked Call; Call*; Dropped Call): Some of these events are also generated for VoIP. They are marked "ps" in the asterisk column. The extra information sent with VoIP call events does not include or block/drop type or any cause values; it does however include certain other items listed below.

Most of these events have pieces of extra information namely "Call Domain", which is either "Circuit Switched" or "Packet Switched", and "Serving Radio Technology" which holds the radio technology responsible for generating the event. These are not repeated for the individual events below.

Voice Bearer Established


(red)

lte

Voice Bearer Established

Extra information:

Serving Radio Technology

QCI

Bearer Setup Time, measured from "Call Established"

Serving Radio Technology

✔

Blocked Call


(red)

g
w
ps

GSM/WCDMA: Call abnormally ended prior to "Call Established" event (for example because all traffic channels were busy).

Extra information:

Block type

CC cause

RR cause

Call time (time since "Call Initiation" event)

Call direction (MO/MT)

✔

Call Attempt


(gray)

g
w
ps

GSM: A traffic channel was requested (through the Layer 3 message Channel Request). (Note that the request could also be for a signaling channel, in which case no call is actually attempted; the two types of request cannot be distinguished.)

WCDMA: An RRC Connection Request was sent following initiation of an MO or MT call.

PS: Triggered by SIP Invite Request.

Extra information:

Initial RRC State

✔

Call Attempt Retry


(gray)

g
w

A call attempt (see the event "Call Attempt") was repeated. Triggered by Channel Request/RRC Connection Request.

Extra information:

Initial RRC State

✔

Call End

g
w
ps

This event is normally triggered by

CS: the CC message Release

PS: the message SIP Bye.

Extra information:

Call end cause (usually one of "MS initiated release", "NW initiated release", "User busy")

Call duration

PS: Media type (Audio/Video/Mixed)

✔

Call Established


(green)

g
w
ps

The event is triggered by

GSM/WCDMA: the Layer 3 message Connect (MO call) or Connect Acknowledge (MT call)

PS: the message SIP Invite Response with status code 200 = OK.

✔

Call Failure MO

g
w
ps

A mobile-originated call was either blocked or dropped.

 

Call Failure MT

g
w
ps

A mobile-terminated call was either blocked or dropped.

 

Call Initiation

g
w
ps

An MO call was initiated by a script (the equivalent of the "call" command being given in the handset GUI). This event is normally triggered by a report from the PC communication protocol, never by a Layer 3 message.

This event precedes "Call Attempt".

Extra information:

Initial RRC State

✔

Call Leg Attempt

g
w
ps

Conference call. A new secondary leg has been attempted.

  

Call Leg End

g
w
ps

Conference call. A secondary call leg has ended.

  

Call Leg Established

g
w
ps

Conference call. A secondary call leg has been established.

  

Call Leg Rejected

g
w
ps

Conference call. An attempt to establish a secondary call leg has failed.

  

Call Leg Setup

g
w
ps

Conference call. A secondary call leg is being set up.

  

Call Off Hold

g
w
ps

Conference call. Call is being taken off hold by another party.

  

Call On Hold

g
w
ps

Conference call. Call is being put on hold by another party.

  

Call Off Hold Requested

g
w
ps

Conference call. Call is being taken off hold by this party.

  

Call On Hold Requested

g
w
ps

Conference call. Call is being out on hold by this party.

  

Call Re-established


(green)

g
w

Following a radio link failure, a call was re-established (a drop thus being prevented).

Technology-specific details:

GSM: New traffic channel assigned within 20 s. ► 3GPP 45.008, section 6.7.2

WCDMA: New traffic channel assigned before T314 timer expired. ► 3GPP 25.331, section 8.3.1.13

This event can occur only if call re-establishment is enabled in the network. If it is not, a call will be automatically dropped in this situation.

✔

Call Setup

g
w
ps

This event is triggered by

GSM/WCDMA: one of the Layer 3 messages Alerting or Connect

PS: the message SIP Invite Response with status code 180 = Ringing.

Extra information:

Call direction (MO/MT)

Call setup time (measured from "Call Attempt", i.e. the first call attempt)

User setup time (measured from "Call Initiation", thus more accurately reflecting the user-perceived setup time; obtained only for MO calls in scripts)

✔

Cell Change Order From UTRAN

g

Successful cell change order: handover from UTRAN to GSM packet data channel. Generated after entering GSM mode.

Only occurs when the change takes place from Cell_DCH mode. If it takes place from a Common channel, the event "Cell Reselection From UTRAN" is generated instead.

 

Cell Change Order From UTRAN Failure

w

Cell change order from UTRAN failed.

 

Cell Reselection

g
w

Cell reselection within GSM or within UTRAN (intra-frequency).

Extra information (GSM): BCCH ARFCN and BSIC of new cell.

✔

Cell Reselection From UTRAN

g

Cell reselection from UTRAN to GSM. Generated after entering GSM mode.

 

Cell Reselection To EUTRAN

lte

Cell reselection from UTRAN or GSM to EUTRAN. Generated after entering LTE mode.

Extra information:

New cell EARFCN and PCI

Old cell UARFCN and SC (WCDMA) or ARFCN and BSIC (GSM)

 

Cell Reselection To UTRAN

w

Cell reselection from GSM to UTRAN. Generated after entering WCDMA mode.

 

Channel Switch From HSDPA

w

Successful switch from HS-PDSCH to DPCH.

 

Channel Switch From HSDPA Failure

w

Switch from HS-PDSCH to DPCH failed.

 

Channel Switch To HSDPA

w

Successful switch from DPCH (3GPP Release 99) to HS-PDSCH.

 

Channel Switch To HSDPA Failure

w

Switch from DPCH to HS-PDSCH failed.

 

Compressed Mode Entered

w

The device entered compressed mode.

 

Compressed Mode Exited

w

The device left compressed mode.

 

CS Call Initiated on IP Call Request (Incoming)

g
w

A VoIP (IP) call was requested by the user, but instead a CS voice call was initiated by the UE.

 

CS Call Initiated on IP Call Request (Outgoing)

g
w

Answering of a VoIP (IP) call was intended by the user, but instead the UE answered it by initiating a CS voice call.

 

CSFB events: Some of these events have a piece of extra information "Call Domain", which however always takes the value "Circuit Switched". The CS fallback events are generated only in the CS domain.

Most of these events have a piece of extra information "Serving Radio Technology", which holds the radio technology responsible for generating the event. This is not repeated for the individual events below.

CSFB Blocked Call


(red)

g
w
lte

A CS fallback call was blocked. This can happen in several ways:

The Extended Service Request timed out without any response from network, or the network responded with Service Reject. In this case the CS fallback procedure never reaches the RAT change stage.

RAT change to UTRAN/GERAN failed, as indicated by the event "EUTRAN RRC Connection Release Redirected Failure".

After successful RAT change to UTRAN/GERAN, the CS call setup failed (CS "Blocked Call" event generated).

Extra information:

Call direction (MO/MT)

Block type

Regarding CS fallback in general, see ► 3GPP 23.272.

✔

CSFB Call Attempt


(gray)

lte

A CS fallback call attempt was made. Triggered by the Layer 3 message NAS Extended Service Request.

Extra information:

Call direction (MO/MT)

Initial RRC State

✔

CSFB Call Established


(green)

g
w

A CS fallback call was established. Triggered by the Layer 3 message Connect (MO call) or Connect Acknowledge (MT call).

Extra information:

Call direction (MO/MT)

Target technology (WCDMA/GSM)

✔

CSFB Call Setup

g
w

A CS fallback call was set up. Triggered by the Layer 3 message Alerting.

Extra information:

Call direction (MO/MT)

Target technology (WCDMA/GSM)

Call setup time (measured from "CSFB Call Attempt", i.e. the first call attempt)

User setup time (measured from "Call Initiation", thus more accurately reflecting the user-perceived setup time. Obtained only for MO calls in scripts. If no "Call Initiation" event was generated, the user setup time cannot be computed.)

✔

CSFB During IP Call Setup

g
w

The call setup procedure was initiated as a VoIP (IP) call, but before the call setup was completed, the call setup procedure was handed over to the CS domain.

 

Datalink Failure

g

Datalink failure caused by unsolicited Disconnected Mode response or sequence error.

 

Dedicated Mode

g

The device entered dedicated mode.

Extra information: BCCH ARFCN and BSIC.

 

Dial End

 

A Dial activity completed.

Extra information: Service status.

✔

Dial Start

 

A Dial activity started.

Extra information: Phone number dialed.

✔

Dropped Call

g
w
ps

Call abnormally ended after "Call Established" event.

Extra information:

Drop type

Cause

CC cause

Call duration (time since "Call Established" event)

Call direction (MO/MT)

PS: Media type (Audio/Video/Mixed)

✔

EGPRS MS Out Of Memory

e

The device's status buffer filled up, so that the device was no longer able to use Incremental Redundancy on the downlink for link quality control. Consequently it was forced to switch to using Link Adaptation.

 

eMBMS events: Generated for Qualcomm chipset devices only.

eMBMS Bearer Activated

lte

An eMBMS bearer was activated.

✔

eMBMS Bearer Deactivated

lte

An eMBMS bearer was deactivated.

✔

EPS events: Some of these, tagged "lg" below, are unique to LG chipset devices. Others, tagged qc, are unique to Qualcomm chipset devices.

EPS NAS Timer Expiry

lte

An EPS NAS timer expired.

Extra information: "Timer T<nnnn> expired", where <nnnn> = 3411, 3402, etc.

 

EPS RACH Contention Resolution MSG4

lte
qc

 

Contention Resolution Message (MSG4) of the LTE NB RACH procedure has been received by the UE.

 

EPS RACH Failure

lte

An EPS random access procedure failed.

 

EPS RACH Preamble MSG1

lte
qc

MSG1 of the LTE NB RACH procedure has been sent from the UE.

 

EPS RACH Response MSG2

lte
qc

 

MSG2 of the LTE NB RACH procedure has been received by the UE.

 

EPS RACH Success

lte

An EPS random access procedure succeeded.

 

EPS RACH UE Identification MSG3

lte
qc

 

Identification Message (MSG3) of the LTE NB RACH procedure has been sent from the UE.

 

EPS RRC Timer Expiry

lte

An EPS RRC timer expired.

Extra information: "Timer T<nnn> expired", where <nnn> = 300, 301, 304, etc.

 

EPS TDD UL/DL Configuration Changed

lte

TDD subframe configuration changed. ► 3GPP 36.211, table 4.2-1

Extra information:

Old subframe configuration

New subframe configuration

Each subframe configuration is represented as a string where U = uplink, D = downlink, and S = special subframe. Example: "D:S:U:U:U:D:S".

 

EPS Transmission Mode Changed

lte

Change of EPS transmission mode. Generated when the value of the "Transmission Mode" information element changes.

 

EUTRAN ANR Neighbor Reported

lte

The device reported CGI for a cell identified as a missing neighbor by the Automatic Neighbor Relation mechanism. ► 3GPP 36.300, sections 22.3.2a, 22.3.3–22.3.4; 3GPP 36.331, section 5.5

Extra information: Type of ANR neighbor: intra-frequency, inter-frequency, or Inter-RAT.

 

EUTRAN Attach Complete

lte

The device successfully attached to EUTRAN. Triggered by EPS Attach Complete.

Extra information:

Attach type: EPS attach result in Attach Accept message

Attach time: Time from Attach Request to Attach Complete

✔

EUTRAN Attach Failure

lte

Attach to EUTRAN failed. Triggered by Attach Reject or timeout.

Extra information:

Attach type

Failure cause

✔

EUTRAN Detach Accept

lte

The device successfully detached from EUTRAN. Triggered by EPS Detach Accept.

Extra information:

Attach type detached from

Detach time: Time from Detach Request to Detach Accept

 

EUTRAN Handover Details

lte

Triggered after an EUTRAN handover and more information is received.

Extra information:

  • Handover ID
  • Source and Target Cell Name
  • Source and Target EARFCN
  • Source and Target PCI
  • Source and Target RRC Cell ID
  • Source and Target eNodeB ID
  • Source and Target TAC

✔

EUTRAN Handover Start

lte

Triggered by the Layer 3 message RRC Connection Reconfiguration.

Extra information:

Source EARFCN, Target EARFCN

Source PCI, Target PCI

✔

EUTRAN Inter-frequency Handover

lte

Intra-RAT, inter-frequency handover signaled by the eNodeB. ► 3GPP 36.331, section 5.3.5.4

Triggered by the Layer 3 message RRC Connection Reconfiguration with targetPhyCellId differing from serving cell ID, and on different EARFCN.

Extra information:

Old EARFCN, new EARFCN

Old cell ID, new cell ID

Handover interruption time

✔

EUTRAN Inter-frequency Handover Failed

lte

Intra-RAT, inter-frequency handover failed. Triggered by expiry of the T304 timer configured in the RRC Connection Reconfiguration message. ► 3GPP 36.331, section 5.3.5.6

Extra information:

Old EARFCN, new EARFCN

Old cell ID, new cell ID

Handover interruption time

✔

EUTRAN Intra-frequency Handover

lte

Intra-RAT, intra-frequency handover signaled by the eNodeB. ► 3GPP 36.331, section 5.3.5.4

Triggered by the Layer 3 message RRC Connection Reconfiguration with targetPhyCellId differing from serving cell ID, but on same EARFCN.

Extra information:

EARFCN

Old cell ID, new cell ID

Handover interruption time

✔

EUTRAN Intra-frequency Handover Failed

lte

Intra-RAT, intra-frequency handover failed. Triggered by expiry of the T304 timer configured in RRC Connection Reconfiguration message. ► 3GPP 36.331, section 5.3.5.6

Extra information:

EARFCN

Old cell ID, new cell ID

Handover interruption time

✔

EUTRAN Reselection Time After CSFB Call

lte

This event carries performance information on the switch back to LTE after hangup of a CS fallback call.

Extra information:

Idle to LTE time: Time in seconds from entering idle mode (in UMTS) to reception of System Information Block on LTE.

SIB 19 to LTE time: Time in seconds from reception of System Information Block Type 19 (UMTS) to reception of System Information Block on LTE.

✔

EUTRAN RRC A1 Event

lte

Measurement Report containing A1 event sent from device: serving cell is better than threshold. ► 3GPP 36.331, section 5.5.4.2

Extra information: Serving cell readings.

 

EUTRAN RRC A2 Event

lte

Measurement Report containing A2 event sent from device: serving cell is worse than threshold. ► 3GPP 36.331, section 5.5.4.3

Extra information: Serving cell readings.

 

EUTRAN RRC A3 Event

lte

Measurement Report containing A3 event sent from device: neighbor is offset better than PCell/PSCell. ► 3GPP 36.331, section 5.5.4.4

Extra information: PCell/PSCell and neighbor readings.

 

EUTRAN RRC A4 Event

lte

Measurement Report containing A4 event sent from device: neighbor is better than threshold. ► 3GPP 36.331, section 5.5.4.5

Extra information: Neighbor readings.

 

EUTRAN RRC A5 Event

lte

Measurement Report containing A5 event sent from device: PCell/PSCell is worse than threshold1 and neighbor is better than threshold2. ► 3GPP 36.331, section 5.5.4.6

Extra information: PCell/PSCell and neighbor readings.

 

EUTRAN RRC A6 Event

lte

Measurement Report containing A6 event sent from device: neighbor is offset better than SCell. ► 3GPP 36.331, section 5.5.4.6a

Extra information: Neighbor and PCell/PSCell readings.

 

EUTRAN RRC B1 Event

lte

Measurement Report containing B1 event sent from device: inter-RAT neighbor is better than threshold. ► 3GPP 36.331, section 5.5.4.7

Extra information: Inter-RAT neighbor readings.

 

EUTRAN RRC B2 Event

lte

Measurement Report containing B2 event sent from device: PCell is worse than threshold1 and inter-RAT neighbor is better than threshold2. ► 3GPP 36.331, section 5.5.4.8

Extra information: PCell and inter-RAT neighbor readings.

 

EUTRAN RRC Connection Drop

lte

The RRC Connection Reestablishment procedure was unsuccessful (rejected or timed out).

 

EUTRAN RRC Connection Reject

lte

An RRC connection was rejected.

✔

EUTRAN RRC Connection Re-establishment

lte

The RRC Connection Reestablishment procedure was successful and the RRC State is "Connected" again.

 

EUTRAN RRC Connection Release Redirected Attempt

lte

An RRC connection was redirected. Triggered by EPS RRC Connection Release message with redirection flag.

Extra information: Redirection control information from RRC Connection Release message.

✔

EUTRAN RRC Connection Release Redirected Failure

lte

Redirection of RRC connection failed; the device returned to EUTRAN without successful new connection setup.

✔

EUTRAN RRC Connection Release Redirected Success

lte
w
g
1

Successful new connection setup following EPS RRC Connection Release message with redirection flag. Triggered by one these messages:

WCDMA: RRC Connection Setup Complete

GSM: Immediate Assignment

GPRS/EDGE: Packet Uplink/Downlink Assignment

EV-DO: Traffic Channel Complete

1x: Service Connect

Extra information:

Technology and cell to which the device was redirected.

Redirection control information from RRC Connection Release message.

RRC Reconnect Time, measured from RRC Connection Release to the relevant message above.

✔

EUTRAN RRC Established


(green)

lte

An RRC connection was established. Triggered by RRC Connection Setup Complete message.

Extra information: Establishment cause.

✔

Group Call Entered

g
w
ps

Conference call. The current call has been transformed into a group call (conference call)

  

Group Call Exited

g
w
ps

Conference call. This party is leaving a group call (conference call).

  

Group Call Modified

g
w
ps

Conference call. Members have been added to or removed from the current group call (conference call).

  

Handover

g

Successful inter-cell handover in GSM.

✔

Handover Failure

g

Inter-cell handover in GSM failed.

✔

Handover From EUTRAN

w

Successful handover from EUTRAN to UTRAN. Generated after entering WCDMA mode.

Extra information:

Handover type: PS or SRVCC

Source RAT, target RAT

Handover interruption time, measured from Mobility From EUTRA Command (with Handover To UTRAN indication) to Handover To UTRAN Complete.

 

Handover From EUTRAN Failure

lte

Handover from EUTRAN to UTRAN failed.

 

Handover From UTRAN

g

Successful handover from UTRAN to GSM. Generated after entering GSM mode.

 

Handover From UTRAN Failure

w

Handover from UTRAN to GSM failed.

 

Handover Intracell

g

Successful intra-cell handover in GSM.

✔

Handover Intracell Failure

g

Intra-cell handover in GSM failed.

✔

Handover To EUTRAN

lte

Successful handover from UTRAN to EUTRAN. Generated after entering LTE mode.

Extra information: Handover interruption time, measured from "Handover From UTRAN Command-EUTRA" to "RRC Reconfiguration Complete".

 

Handover To EUTRAN Failure

w

Handover from UTRAN to EUTRAN failed.

 

Handover To UTRAN

w

Successful handover from GSM to UTRAN. Generated after entering WCDMA mode.

 

Handover To UTRAN Failure

g

Handover from GSM to UTRAN failed.

 

HS Serving Cell HO

w

Successful HSPA serving cell handover.

The same symbol is used as for "Scanned Adjacent ARFCN –2", since HSPA serving cell handover is handled in a similar way (and differently from UMTS soft handover).

 

HS Serving Cell HO Failure

w

HSPA serving cell handover failed.

The same symbol is used as for "Inter-frequency Handover Failure" (compare "HS Serving Cell HO").

 

Idle Mode

g

The device entered idle mode.

Extra information: BCCH ARFCN and BSIC.

 

Inter-frequency Cell Reselection

w

Successful WCDMA inter-frequency cell reselection.

Extra information: New UARFCN; new SC.

✔

Inter-frequency Handover

w

Successful inter-frequency handover in WCDMA.

Extra information: New UARFCN.

✔

Inter-frequency Handover Failure

w

Inter-frequency handover in WCDMA failed.

✔

Inter-System Handover To GSM/LTE/WCDMA

g
lte
w

Inter-RAT, inter-frequency handover signaled by the eNodeB. ► 3GPP 36.331, section 5.3.5.4

Triggered by the Layer 3 message RRC Connection Reconfiguration with targetPhyCellId differing from serving cell ID, and on different ARFCN/EARFCN/UARFCN.

Extra information:

Source RAT, target RAT

Old ARFCN/EARFCN/UARFCN, new ARFCN/EARFCN/UARFCN

Old cell ID, new cell ID

Handover interruption time

✔

Inter-System Handover to GSM/LTE/WCDMA Failure

g
lte
w

Inter-RAT, inter-frequency handover failed. Triggered by expiry of the T304 timer configured in the RRC Connection Reconfiguration message. ► 3GPP 36.331, section 5.3.5.6

Extra information:

Source RAT.

✔

Intra-frequency Hard Handover

w

Successful intra-frequency hard handover in WCDMA.

✔

Intra-frequency Hard Handover Failure

w

Intra-frequency hard handover in WCDMA failed.

✔

Limited Service Mode

g

GSM: The device entered limited service mode (emergency calls only).

✔

Location Area Update

g
w

The device changed location areas.

Extra information: Location update type (LUT).

 

Location Area Update Failure

g
w

The device failed to change its location area.

Extra information: Cause; location update type (LUT).

 

Measurement Report 1

w

Intra-frequency measurement report sent from device (UMTS reporting events "1A", "1B", etc.). ► 3GPP 25.331, section 14.1

Extra information: Type of UMTS event.

 

Measurement Report 2

w

Inter-frequency measurement report sent from device (UMTS reporting events "2A", "2B", etc.). ► 3GPP 25.331, section 14.2

Extra information: Type of UMTS event.

 

Measurement Report 3

w

Inter-RAT measurement report sent from device (UMTS reporting events "3A", "3B", etc.). ► 3GPP 25.331, section 14.3

Extra information: Type of UMTS event.

 

Measurement Report 4

w

Traffic volume measurement report sent from device (UMTS reporting events "4A", "4B"). ► 3GPP 25.331, section 14.4

Extra information: Type of UMTS event.

 

Measurement Report 5

w

Quality measurement report sent from device (UMTS reporting event "5A"). ► 3GPP 25.331, section 14.5

Extra information: Type of UMTS event.

 

Measurement Report 6

w

UE-internal measurement report sent from device (UMTS reporting events "6A", "6B", etc.). ► 3GPP 25.331, section 14.6

Extra information: Type of UMTS event.

 

Measurement Report 7

w

UE positioning measurement report sent from device (UMTS reporting events "7A", "7B", etc.). ► 3GPP 25.331, section 14.7

Extra information: Type of UMTS event.

 

Missing GSM Neighbor


(yellow bar on the right)

sg

This is a GSM event based on scan data that includes decoded BSIC and System Information. The event does not require a cell file.

It is assumed that the strongest cell with decoded BSIC is the serving cell. Among other cells with decoded BSIC, the six strongest ones are looked up in the strongest cell's neighbor list (which is extracted from System Information messages). For each cell that is not in the neighbor list, an instance of this event is generated.

The event is only generated once for each combination of assumed serving cell (ARFCN + BSIC) and missing neighbor (ARFCN).

Extra information: BCCH ARFCN and BSIC of serving cell; ARFCN, BSIC, and signal strength (in dBm) of missing neighbor.

 

Missing GSM Neighbor, GSM Symmetry


(yellow bar on the right)

g

This is a GSM event based on UE data. It does not require a cell file.

Triggered in when the source cell of a handover is not in the target cell's neighbor list.

Cells are compared with respect to ARFCN and BSIC. If BSIC is not available, the event will not be triggered.

The event triggering is delayed two seconds after the handover to ensure that the entire neighbor list of the target cell has been received.

Extra information: Serving cell ARFCN and BSIC (i.e. new serving cell after handover); missing neighbor ARFCN and BSIC (i.e. old serving cell prior to handover).

 

Missing LTE Neighbor


(yellow bar on the right)

 

This event is based on LTE scan data. It requires that a cell file is loaded and that the currently strongest cell has a neighbor list defined in that file.

Triggered in the following cases:

A cell not defined as a neighbor of the strongest cell is more than n dB stronger than at least one neighbor of the strongest cell. The margin n dB is set in the Options dialog tab LTE Options.

A cell not defined as a neighbor of the strongest cell is within n dB of the strongest cell. (The event is then triggered regardless of the strength of defined neighbors.)

No cell from the strongest cell's neighbor list is detected, but at least one cell is detected besides the strongest cell. (The event is then triggered regardless of the strength of that cell.)

The signal power measure used in the comparisons is RSRQ.

Extra information:RSRQ Margin, Type, Serving Cell, Defined Neighbor, Undefined Neighbor

For each cell the following information is shown if available, "Cell Name", "Cell", "RSRQ", where "Cell" is (EARFCN-PCI)

 

Missing WCDMA Intra-frequency Neighbor


(yellow bar on the right)

w

This is a WCDMA event based on UE data. The event does not require a cell file.

Triggered in the following cases:

The strongest active set member lies between –18 dB and –12 dB, and the strongest detected neighbor is stronger than –12 dB.

The strongest active set member is stronger than –12 dB, and the strongest detected neighbor is stronger than –12 dB.

A detected neighbor exists, although no active set member or monitored neighbor exists.

The signal strength measure used in the comparisons is CPICH Ec/N0.

Extra information:

Cases 1 and 2 above: Priority ("1" and "2" respectively); strongest active set member SC and Ec/N0; missing neighbor SC and Ec/N0.

Case 3: Missing neighbor SC and Ec/N0.

 

Missing WCDMA Neighbor


(yellow bar on the right)

(c)
sw

This event is based on WCDMA scan data. It requires that a cell file is loaded and that the currently strongest cell has a neighbor list defined in that file.

Triggered in the following cases:

A cell not defined as a neighbor of the strongest cell is more than n dB stronger than at least one neighbor of the strongest cell. The margin n dB is set in the Options dialog tab WCDMA Options.

A cell not defined as a neighbor of the strongest cell is within n dB of the strongest cell. (The event is then triggered regardless of the strength of defined neighbors.)

No cell from the strongest cell's neighbor list is detected, but at least one cell is detected besides the strongest cell. (The event is then triggered regardless of the strength of that cell.)

The signal power measure used in the comparisons is Aggr Ec/I0.

Extra information:Ec/Io Margin, Type, Serving Cell, Defined Neighbor, Undefined Neighbor

For each cell the following information is shown if available, "Cell Name", "Cell", "RSRQ", where "Cell" is (EARFCN-PCI)

For each cell the following information is shown if available, "Cell Name", "Cell", "Ec/Io", where "Cell" is (UARFCN-SC)

 

More Than 3 Strong SCs


(red bar on the right)

sw

This event is based on WCDMA scan data.

The information element "Poss No of AS Members" (with argument = power threshold n dB governed by the Missing Neighbor Margin setting in the General window under WCDMA) is larger than 3, and all the detected scrambling codes are stronger than –100 dBm.

Extra information: UARFCN.

 

NB-IoT Cell Reselection Delay

lte

Delay for Cell Reselection.

✔

NB-IoT Idle Mode Access Delay

lte

Delay for Access in Idle Mode.

✔

NB-IoT RRC Connected Mode Cell Selection Delay

lte

Delay for Cell Selection in Connected Mode.

✔

No Service Mode

g

The device entered no service mode, since it could not find a control channel.

✔

Packet Mode

g

The device entered packet mode (switched to a PDCH).

Extra information: BCCH ARFCN and BSIC.

 

PDP Context Activation 2

g
w

A PDP context was successfully activated.

Extra information:

Setup time, counted from the first RRC Connection Request message to Activate PDP Context Accept.

PDP context completion time, counted from the first Activate PDP Context Request message to Activate PDP Context Accept.

✔

PDP Context Activation Failure "GSM/WCDMA/LTE Events"

g
w

Activation of a PDP context failed.

Extra information: Failure cause.

✔

PDP Context Deactivation "GSM/WCDMA/LTE Events"

g
w

An active PDP context was deactivated.

✔

PDSCH 256QAM In Use

lte

Generated when Physical Downlink Shared Channel modulation 256QAM is reported for the first time.

 

PDSCH 256QAM Out Of Use

lte

Generated when no Physical Downlink Shared Channel modulation 256QAM samples have been received during 1 second for the involving cell, unless the RRC state changes to idle.

 

PDSCH Modulation Table Change to 256QAM

lte

Generated when Physical Downlink Shared Channel Modulation Table change from 64QAM to 256QAM.

 

PDSCH Modulation Table Change to 64QAM

lte

Generated when Physical Downlink Shared Channel Modulation Table change from 256QAM to 64QAM.

 

PDU Error

g

Protocol Data Unit error caused by syntax error in a Layer 3 message.

 

PS Attach "GSM/WCDMA/LTE Events"

g
w

The device successfully attached to the packet service.

Extra information: Attach type; attach completion time.

✔

PS Attach Failure "GSM/WCDMA/LTE Events"

g
w

The device failed to attach to the packet service.

Extra information: Attach type; failure cause.

✔

PS Channel Type Switch Complete

w

A switch between a dedicated data channel and a common data channel succeeded.

Extra information: Direction of switch: "Dedicated to Common" or "Common to Dedicated".

 

PS Channel Type Switch Failure

w

A switch between a dedicated data channel and a common data channel failed.

Extra information: Direction of switch: "Dedicated to Common" or "Common to Dedicated".

 

PS Data Interruption Time Due To CSFB

g
w

This event reports the IP interruption time during RAT change to UTRAN/GERAN due to initiation of a CS fallback call.

Always generated in conjunction with the "IP Interruption Time" event.

Extra information: Interruption time in ms. Measured from last received IP packet in EUTRAN to first received IP packet in UTRAN/GERAN.

✔

PS Detach

g
w

The device successfully detached from the packet service.

✔

PS RAB Channel Rate Switch Complete

w

The spreading factor, and hence the data rate, was changed successfully for the radio access bearer.

Extra information: Uplink and downlink spreading factors.

 

PS RAB Channel Rate Switch Failure

w

A change of spreading factor failed for the radio access bearer.

Extra information: Uplink and downlink spreading factors.

 

Radio Bearer Reconfiguration Failure

w

The device could not reconfigure the radio bearer.

Extra information: Cause value.

 

Radio Bearer Setup Failure

w

The device could not set up the radio bearer.

Extra information: Cause value.

 

Radio Link Addition

w

One or several radio links were added.

Extra information: Added scrambling codes; soft handover type; event type.

 

Radio Link Addition Failure

w

Addition of one or several radio links failed.

Extra information: Failure cause.

 

Radio Link Removal

w

One or several radio links were removed.

Extra information: Removed scrambling codes; event type.

 

Radio Link Removal Failure

w

Removal of one or several radio links failed.

Extra information: Failure cause.

 

Radio Link Replacement

w

Combined addition and removal of radio links.

Extra information: Added scrambling codes; removed scrambling codes; soft handover type; event type.

 

Radio Link Replacement Failure

w

Addition or removal of one or several radio links failed.

Extra information: Failure cause.

 

Ringing

g

The GSM device started emitting a ringing signal.

 

Routing Area Update

g
w

The device changed routing areas.

 

Routing Area Update Failure

g
w

The device failed to change its routing area.

Extra information: Failure cause.

 

RRC Connection Abnormal Release

w

An RRC connection was abnormally released.

Extra information: Failure cause.

✔

RRC Connection Reject

w

An RRC connection was rejected.

Extra information: Failure cause. ► 3GPP 25.331, section 10.3.3.31

✔

RRC Connection Request events: See ► 3GPP 25.331, section 10.3.3.11 regarding values of Establishment cause.

RRC Connection Request Detach

w

An RRC Connection Request was sent with Establishment cause = "Detach".

✔

RRC Connection Request Emergency Call

w

An RRC Connection Request was sent with Establishment cause = "Emergency Call".

✔

RRC Connection Request Originating Signaling

w

An RRC Connection Request was sent with Establishment cause beginning with "Originating".

✔

RRC Connection Request Registration

w

An RRC Connection Request was sent with Establishment cause = "Registration".

✔

RRC Connection Request Terminating Signaling

w

An RRC Connection Request was sent with Establishment cause beginning with "Terminating".

✔

RRC Established


(green)

w

An RRC connection was established. Triggered by the message RRC Connection Setup Complete.

Extra information: Establishment cause.

✔

RRC Protocol Error


(red)

w

An RRC protocol error occurred.

Extra information: Failure cause.

✔

Scanning Mode

sg

The GSM device entered scanning mode, i.e. it started some type of scanning.

 

Secondary Cell Addition

lte

A secondary LTE cell was added.

Extra information: Event info carries what index (secondary, tertiary), if possible physical cell id and DLCarrierFrequency and the duration in between RRC Reconfiguration -> Complete.

 

Secondary Cell Reconfiguration

lte

A secondary cell was reconfigured.

Extra information: Event info carries what index (secondary, tertiary), if possible physical cell id and DLCarrierFrequency and the duration in between RRC Reconfiguration -> Complete.

 

Secondary Cell Removal

lte

A secondary LTE cell was removed.

Extra information: Event info carries what index (secondary, tertiary), if possible physical cell id and DLCarrierFrequency and the duration in between RRC Reconfiguration -> Complete.

 

Security Mode Failure

w

A security mode command failed.

Extra information: Cause value.

 

SHO Procedure Complete

w

Soft handover: Active set update procedure completed with Measurement Control message.

✔

SHO Procedure Complete Without Measurement Control

w

Soft handover: Active set update procedure completed without a Measurement Control message (because another soft handover procedure started).

Extra information: One of "Addition", "Removal", "Replacement".

 

Silent Call

g
w

A silent call was detected by the AQM algorithm: all system signaling was OK, but the audio was not transferred in both directions. The event is triggered 27.5 s after the last Stop DTMF Acknowledge message.

See the document "AQM in TEMS Products".

✔

SMS Error

g
w

Transfer of an SMS message failed (during either sending or receiving).

 

SMS Received

g
w

An SMS message was successfully received.

✔

SMS Sent

g
w

Sending of an SMS message was successfully completed.

✔

VCC Handover From EUTRAN

w
g
"GSM/WCDMA/LTE Events"

Voice Call Continuity handover of VoLTE call from EUTRAN to UTRAN/GERAN.

Extra information: Handover type: SRVCC (Single Radio VCC) or DRVCC (Dual Radio VCC).

 

Video Accept Start

lte

A Video Accept activity started.

 

Video Accept End

lte

A Video Accept activity completed.

Extra information: Service status, Call Index.

 

Video Add Start

lte

A Video Add activity started.

 

Video Add End

lte

A Video Add activity completed.

Extra information: Service status, Call Index.

 

Video Answer Start

lte

A Video Accept activity started.

 

Video Answer End

lte

A Video Accept activity completed.

Extra information: Service status, Call Index.

 

Video Dial Start

lte

A Video Dial activity started.

 

Video Dial End

lte

A Video Dial activity completed.

Extra information: Service status, Call index.

 

Video Remove Start

lte

A Video Remove activity started.

 

Video Remove End

lte

A Video Remove activity completed.

Extra information: Service Status, Call Index.

 

EPSFB events: Some of these events have a piece of extra information "Call Domain", which however always takes the value "Packet Switched". The EPSFB fallback events are generated only in the PS domain.

All of these events have a piece of extra information "Serving Radio Technology", which holds the radio technology responsible for generating the event. This is not repeated for the individual events below.

EPSFB Blocked Call


(red)

lte

A EPS fallback call was blocked. This can happen in several ways:

The Extended Service Request timed out without any response from network, or the network responded with Service Reject. In this case the EPS fallback procedure never reaches the RAT change stage.

RAT change to UTRAN/GERAN failed, as indicated by the event "EUTRAN RRC Connection Release Redirected Failure".

Call direction (MO/MT)

Block type

✔

EPSFB Call Attempt


(gray)

lte

A EPS fallback call attempt was made. Triggered by the Layer 3 message NAS Extended Service Request.

Extra information:

Call direction (MO/MT)

Initial RRC State

✔

EPSFB Call Established


(green)

lte

A EPS fallback call was established. Triggered by the Layer 3 message Connect (MO call) or Connect Acknowledge (MT call).

Extra information:

Call direction (MO/MT)

✔

EPSFB Call Setup

g
w

A EPS fallback call was set up. Triggered by the Layer 3 message Alerting.

Extra information:

Call direction (MO/MT)

✔