You are on page 1of 4

Iu Call Setup Failure Discriminated Event Query

This topic builds on the Throughput By Application protocol example and the Target Level Before Handover drive test event query example. If necessary, you may want to work through those topics before continuing with this example. In the Throughput By Application example, we saw how to create a crosstab query that provides a summary overview of the protocol data. In this topic we will learn how to create a query that enables the user to drill down into the actual sessions in order to attempt to establish the causes of a problem. This is done using a discriminated event query. This is an event query for which a discriminator has been specified. The discriminator is an attribute that is used to identify the messages that belong to a particular a call or session. Running the query at load time triggers the tracking and indexing of the messages for each separate call or session, so that they can subsequently be loaded into Analyzer as a separate stream for detailed analysis. The discriminated event query acts as a "de-multiplexer" of the data. For a general introduction to discriminated event queries, see About Event Queries. Here are the results of the Iu Call Setup example event query in Statistics Explorer:

Notice that the Analyze tool (circled in red) is enabled in the toolbar. This tool is automatically enabled when you define a discriminator on the first page of the Event Query Wizard and you create a statistic that uses the same expression. When you select a row in the query and click the Analyze tool, Analyzer creates a substream that represents the selected session and displays it in the Attribute Explorer.

The user can then investigate the session by using the Replay tool, displaying the substream in the Message Browser and Protocol Stack Browser, dragging attributes onto charts and tables, etc. Creating a substream in this way is possible only when the event query has a discriminator and a statistic based on the discriminator attribute. It's possible, because when the query is evaluated, a list of message numbers and their file positions are stored internally for each discrete value of the discriminator attribute (Iu_Call_ID in this example). Now let's create the query: Because we need to run the query at load time in order to trigger the tracking and indexing of the sessions, start by selecting Minimal load mode. How Create a new event query defined as follows: General event query settings. The following table describes the settings on the first page of the Event Query Wizard. Option Trigger How do you want to define your window? Milliseconds before event Milliseconds after event Discriminator Setting Iu_OutgoingCallSetupFail Based on time 0 0 Iu_Call_Id

Show/hide first page of the Event Query Wizard

Dimensions. Retain the default EventTime dimension, which creates one row that shows the time in milliseconds relative to the start of the file for each outgoing call setup failure. Statistics. Create one statistic based on the discriminator attribute as shown in the following table. Name Iu Call ID Expression Iu_Call_Id Aggregation Method Last Value Format Unsigned 64-bit Integer

Click OK to close the Event Query Wizard. On the Existing Analyses tab in Analysis Manager, select the query and then select Execute at Load Time. Click OK to close the Analysis Manager. Load a suitable Iu protocol link log file.

Right-click the query in the Attribute Explorer and choose Display the Statistics Explorer. Related Topics Writing Queries For Protocol Data About Event Queries Query Performance

Send feedback on this topic