emil lte profile user manual i

8/9/2019 Emil LTE Profile User Manual I

http://slidepdf.com/reader/full/emil-lte-profile-user-manual-i 1/60

© Nokia Siemens Networks Confidential

Emil LTE ProfileUser Manual



Emil LTE Profile User Manual

© Nokia Siemens Networks, Proprietary & Confidential

Only for Internal use, do not distribute outside

NSN



Contents

© Nokia Siemens Networks

Contents

1 Emil installation.................................................................... 5

1.1 Emil installation from iSource installation file ......................... 5

1.2 Changing Emil configuration or platform version ................... 6

2 Emil Views ............................................................................ 7

2.1 Trigger view............................................................................ 8

2.2

LTE Streaming/BTS connections view................................. 10 2.3 LTE Streaming/Monitoring profile view ................................ 13

2.4 Main view ............................................................................. 17

2.4.1 Options view......................................................................... 22

2.4.2 Columns ............................................................................... 24

2.5 Scenario/Trace view............................................................. 26

2.6 Source view.......................................................................... 37

2.7 Message view ...................................................................... 39

2.7.1

Parameter view .................................................................... 44

2.7.2 Protocol view........................................................................ 47

2.7.3

Graphs view ......................................................................... 48

2.8 Trace view............................................................................ 50

2.8.1

Sequence view..................................................................... 52

2.8.2 L3 view................................................................................. 53

2.9 Call statistics view................................................................ 53

3 Emil .ini configuration files ............................................... 54

4 Emil IDA2 Tool Env Sack files .......................................... 56




4 (60) © Nokia Siemens Networks, Proprietary & Confidential

Summary of changes

Version Date Author Changes

1.0 10.11.2010 Antti Reijonen First version, LTEProfile tested onlyagainst RL10traces

1.1 24.11.2010 Antti Reijonen Trigger viewlocation changed,RL20 correction toLTE Profile

(Graphs are onlyfor RL10).Additionalcolumns tofields2.ini



Emil installation

© Nokia Siemens Networks 5 (60)

1 Emil installation

Emil is installation is preferred from installation file. Configurations filesand exe files can be changed after installation, in case Emil profile orplatform versions have to be changed.

1.1 Emil installation from iSource installationfile

Off-line Emil can be installed to any PC with Windows XP or newerWindows OS

On-line Emil used for tracing must be installed in PC using same IPsub network as traced BTS. NetAct PC platform with removable USBhard rive is one preferred option, when accepted by network owners

Install Emil from Emil.msi file located athttps://isource.access.nokiasiemensnetworks.com/projects/emil/ , if older Emil version exist it can be removed during installation

If Emil was installed the first time, create Program files\Emil\sacksfolder and copy latest available LN IDA sack (whole folder) under it

Start Emil and select correct path for sacks and profiles from Tools ->Options…

Select used sack and profile from Environment -> Change sack andprofile

If needed, updated traced BTS instances from File -> Connect to LTEBTSs -> File -> Import new BTS list





1.2 Changing Emil configuration or platform

version

When Emil platform changes are needed, e.g. version has to bedowngraded or new knife version taken into use, re-name old emil.exefile and copy new emil.exe file in that directory Emil is installed. Newplatform is taken into use, when Emil is run. Note that emil.exeversions may be incompatible with used Emil profile

When BTS instances or monitoring profiles need to be changed tomatch another existing BTS instance and monitoring profile set, delete

or rename old existing LteConn.dat file and copy new LteConn.dat filein that directory Emil is installed. New BTS instances and monitoringprofiles is taken into use, when Emil is run.

When Emil profile needs to be changed

Copy new profile folder under profiled folder, and change profile fromEnvironment -> Change sack and profile…

Delete or rename old existing .ini file and copy new .ini file to profilefolder. Reload current sack and profile (F5) to take new .ini file into

use Create new profile functionality with xxxUser.ini files. When

xxxUser.ini file has been edited and saved to profile folder Reloadcurrent sack and profile (F5) to take new xxxUser.ini file into use



Emil Views


2 Emil Views

Emil functionality is implemented in different views. Different views areused for configuring Emil or for analyzing traced data. Multiple views canshare same window or are located in a separate window. Emilviews/windows are shown as separate object in Windows taskbar.

Emil views functionality

E-UTRAN / BTS management: With LTE Streaming/BTSconnections view BTS Tech Reports can be fetched and BTS SWinformation checked. More E-UTRAN/BTS management functionalitywill be implemented later

BTS message remote tracing: With LTE Streaming/BTSconnections and Monitoring profile view the BTS message remotetracing can be configured, started and stopped. Depending is tracingcovering only Control Plane or also User Plane messages, 70-200 3sector LTE BTS can be traced at the same time

BTS UDP print remote tracing: BTS UDP prints can be tracedremotely on top of TCP. Not yet implemented in Emil LTE profile

E-UTRAN/BTS scenario and troubleshooting analysis: Tracedmessages can be grouped into scenarios and analyzed in EmilMain/Scenario view. Analysis can be done both on-line as well asoff-line. Analysis can be drilled down in more detailed level inMessage and Trace view. Information can be analyzed further indifferent data and graphical formats in Sequence, Graph and L3analyzer views

BTS and Cell states: Control Plane messages used for BTS andCell configuring are grouped as own scenarios. Raw alarms, BTSand Cell restarts and signalling errors may act as problem and faultsymptoms

User and Cell load and capacity: User Plane messages used forreporting User and Cell load and capacity are grouped as ownscenarios. Degreased load and capacity may act as problem andfault symptoms





Call mobility: Control Plane messages used for call establishment,

call termination and HOs are grouped as own scenarios. Droppedcalls, failed calls, RL failures, signalling errors, delayed HO andsynchronization times, un-specified signalling behaviour may act asproblem and fault symptoms

E-UTRAN/BTS call statistics analysis: Scenarios are used forcreating data and graphs HO duration, HO amount, HO successrate, Call drop rate, Call duration etc. E-UTRAN KPI values. Not yetimplemented in Emil LTE version

Additional BTS log fetching in problem or fault situations:Based on traced scenario additional logs can be triggered to befetched from BTS

2.1 Trigger view

Emil triggers can be set from Filter -> Set snapshot filter for TCP menu.Triggers are used for fetching more logs from BTS, mainly BTS TechReport, when problem or fault situation is detected from Emil trace. BTS

SC freeze logs to prevent over writing, when fetch snapshot command isreceived. Emil trigges use same remote TCP port as site Manager andthus Emil triggers are functional only when BTS Site Manager connectionis not active Currently trigger functionality is rather limited, but it will bedeveloped more flexible in coming releases.

NOTE! Emil TechReport zip file size with TTI trace is approx 10 Mbytesand all fetched TechReports do not necessarily contain any faultinformation -> TechReports will create easily hidden cost from IT supportand consume limited storing capacity if copied to network drives orrepositories, like Electra or Pronto reports, without checking their validity

first. It is recommended that triggered TechReport are linked to correctcontext with proper explanation based on Emil scenario analyze beforesending them to SW implementation or attaching them to fault reports.

Emil LTE triggers (currently included in fields2.ini)

Radiolink Failure: BTS Tech Report is fetched, when call isreleased because of Radiolink failure by eNB. Typically Radiolinkfailures are symptoms of poor UL signal conditions. (Scenario viewOut cause=Radiolink Failure)



Emil Views


Unexpected EPC Release: BTS Tech Report is fetched, when call

is released by EPC during Radiolink failures. Typically UnexpectedEPC Release is a symptom when a call has dropped from cellunaware and has established a new connection in another cell.(Scenario view Out cause=EPC Release)

Unexpected eNB Release: BTS Tech Report is fetched, when callis released by eNB, without UE or EPC requests. TypicallyUnexpected EPC release is a symptom for eNB System Componentreported errors. (Scenario view Out cause=eNB Release)

UE Signalling missing: BTS Tech Report is fetched, when call isreleased because UE is not replying to RRC signalling. Typically UESignalling missing is a symptom of poor DL signal conditions.(Scenario view Out cause=No UE Messages)

EPC Signalling missing: BTS Tech Report is fetched, when call isreleased because EPC is not replying to S1AP signalling. (Scenarioview Out cause=No UE Messages)

RAB Setup Failure: BTS Tech Report is fetched, when eNB fails inRAB Setup procedure. Typically UE is not responding toRrcConnectionReconfiguration or SecurityModeCommandmessages

Figure 1 Emil Trigger view, accessed by Filter -> Set snapshot filter forTCP





2.2 LTE Streaming/BTS connections view

LTE Streaming/BTS connections view is used for managing BTS fortracing and log collection. View accessed by File -> Connect to LTEBTSs. When tracing is started Emil saves message traces under userdefined path under BTS named folder in .emil format, maximum trace filesize is defined by user.

Starting trace sends each CPU defined in active Monitoring profile thefilter message with user defined task and user defined monitoredmessages to CC&S, which forwards information to LOM. Stopping trace

sends each CPU defined in active Monitoring profile the filter messagewith user defined task and empty monitoring messages field. LOMhandles message tracing to different eNB System Components i.e. startsand stop filtering according filter messages received from Emil/CC&S.LOM sends trace data via CC&S managed TCP remote Aa Test port15004 to Emil.

BTS instances can be removed and edited by right mouse click. With rightmouse click BTS can be connected, when it open BTS remote port andstarts to trace BTS internal messages from CPUs defined in Active Profile(left corner window). In similar manner the remote port is closed and

tracing is stopped. With right mouse click can be also fetched SW versionand tech report and pinged the BTS IP address for verifying connection.Connected BTS can be seen from connection status column, Data ratecolumn reveals streamed data rate for connected CPUs. Double clickingconnected BTS will open active monitoring profile parameters and traceddata rates for each CPU. Settings are automatically saved in LteConn.datfile.

BTS instances can be created manually by right mouse click -> Addnew BTS

Or by importing BTSs from .csv list by File -> Import new BTS list, .csvfile has to have correct format for fed parameters

Or creating duplicate BTS from existing BTS instance and editing it

Or copying LteConn.dat file to Program files\Emil root and reload Emil(It will replace existing BTS instances and Monitoring profiles)

Or by

Upper bar commands

File



Emil Views


Import BTS list…: Imports BTS instances from a ready made .csv

file. BTS parameter types must be listed in first row and in followingrows the parameter values must be separated with “,”

Exit: Closes LTE Streaming window

Edit

View

Debug window: Opens debug dialog with a log of detailed Emilactions

Window

Rename form: Enables user to rename the window Right mouse click commands

Copy row: Copies selected row

Copy column (Ctrl+C): Copies selected column

Copy cell: Copies selected cell

Connect: Opens remote test port and sends trace filter parametermessage according to active filter profile(s) to selected BTS(s)

Disconnect: Sends empty trace filter parameter message (stopstracing) to selected BTS(s) and closes remote test port

Send ping: Shows ping dialog for selected BTS(s) for verifying IPconnections

Enable: Enables selected BTS(s) to accept commands, if they weredisabled

Disable: Disable selected BTS(s) to ignore commands, even if theywere selected or command was allocated to all BTSs

Fetch technical logs: Fetches technical logs (Tech report) from

selected BTS(s). Format is a bit different compared to BTS SiteManager fetched technical logs

Fetch SW version: Shows main SW build information for selectedBTS(s)

Fetch detailed SW versions: Shows System Component SWinformation for selected BTS(s)

Edit…: Activates BTS edit dialog for setting BTS information, e.g.BTS name, BTS IP address and active Monitoring profile





Duplicate: Creates new BTS instance with selected BTS instance

parameters. BTS name is changed as Copy_[BTS_name] Remove selected: Removes selected BTS instance row(s) from

Streaming/BTS connections view. Removed BTS instance row(s)can be returned back by replacing LteConn.dat file or importing BTSlist, where original BTS instances existed

Remove all but selected: Removes all but selected BTS instancerow(s) from Streaming/BTS connections view. Removed BTSinstance row(s) can be returned back by replacing LteConn.dat fileor importing BTS list, where original BTS instances existed

Add new bts…: Creates new BTS instance with blank parameters

Figure 2 LTE Streaming/BTS Connections view, accessed by File ->Connect to LTE BTSs …



Emil Views


2.3 LTE Streaming/Monitoring profile view

LTE Streaming/Monitoring profile view is used for managing filter profiles,e.g. what messages are traced and how the traced messaged are filtered.Monitoring profiles can be removed and edited by right mouse click.

NOTE1! Profile tracing load to E-UTRAN network has been tested onlywith limited amount of User load ->Start to ramp up the tracinggradually and newer start the tracing for whole E-UTRAN withoutfirst testing the profile load with limited amount of eNBs! Possible bottle necks for tracing can be eNB processing power (KPI drop due to

processing load), E-UTRAN IP architecture (UL bandwidth, firewalls,etc.), monitoring PC processing power & network card capacity.Estimation is that one Emil trace PC should handle at least 80 Mbpstracing load.

NOTE2! If monitoring profiles are missing some needed messages,inform Emil LTE Profile maintenance ([email protected]) and theywill be added in the profiles for next Emil releases.

NOTE3! Monitoring profiles will be separated in coming Emil release fromLteConn.dat files, so that Emil installation will include default monitoring

profiles and not overwrite BTS instances or user specific monitoringprofiles.

View accessed by File -> Connect LTE -> Monitoring Profiles

Create monitoring profile manually by right mouse click -> Add newprofile…

Or create duplicate Monitoring profile from existing Monitoring profileand edit it

Or copy LteConn.dat file to Program files\Emil root and reload Emil (Itwill replace existing BTS instances and Monitoring profiles)

Monitoring profile parameters

Message filter: Defines individual messages IDs, message pair IDs(;) or messages range IDs (-) in hex, which are traced either bysending or receiving CPU. Sender marks traced messages, whichare not traced anymore by receiver

Heavy loaded messages: Define the interval BTS forwards tracedmessage to tracing test tool. Note that many UP messages will crashBTS and cause excessive transmission load unless filtered





Monitored units: Define to which CPUs (FSM MCU, FSP MCU,

Faradays) the filtering message is send RF Module messages are not possible to trace at the moment

System Components support following filtering tasks:

Board 0x10, CPU 0x11 [FSM_CTRL_MCUMsgTask 0x061A [FSM_1_FCM_BTSOM]MsgTask 0x060A [FSM_1_FCM_HWAPI]MsgTask 0x061C [FSM_1_FCM_LOM]MsgTask 0x0620 [FSM_1_FCM_RROM]MsgTask 0x0622 [FSM_1_FCM_ENBC]MsgTask 0x0623 [FSM_1_FCM_TUPC]

Boards 0x12-0x14, CPU 0x0D [FSP_CTRL_MCU]MsgTask 0x060A [FSM_1_FSP_HWAPI]MsgTask 0x061C [FSM_1_FSP_LOM]MsgTask 0x061B [FSM_1_FSP_UMFSP]MsgTask 0x0625 [FSM_1_FSP_CELLC]MsgTask 0x0624 [FSM_1_FSP_UEC]

Upper bar commands are same as in LTE Streaming/BTS connectionsview

Right mouse click commands




Edit…: Activates Monitoring profile edit dialog for setting Monitoringprofile information, e.g. Profile name, Traces messages and traced

CPUs Duplicate: Creates new Monitoring profile instance with selected

Monitoring profile instance parameters. Monitoring profile name ischanged as Copy_[Profile_name]

Remove selected: Removes selected Monitoring profile instancerow(s) from Streaming/ Monitoring profile view. Removed Monitoringprofile instance row(s) can be returned back by replacingLteConn.dat file, where original Monitoring profile instances existed



Emil Views


Remove all but selected: Removes all but selected Monitoring

profile instance row(s) from Streaming/ Monitoring profile view.Removed Monitoring profile instance row(s) can be returned back byreplacing LteConn.dat file, where original Monitoring profileinstances existed

Add new profile…: Creates new Monitoring profile instance withblank parameters

Currently implemented default monitoring profiles

CP+UP_Light (Default Profile): Raw Alarms, PM counters, ControlPlane, Management Plane, Platform and User Plane messages

related to Call or HO setup/releases procedures, cell and eNB statesand configuration or general error or failure indications. In case moredetailed UP information is needed for call failures, it can be verifiedfrom call failure TechReports. Profile causes low load if no user arepresent and can be used for longer time traces. This profile is therecommended default profile especially for bigger networks.

CP+UP_MeasRep: Includes CP+UP_Light (Default Profile) profilemessages and UP Measurement report messages used for drawinggraphs. Measurement reports are filtered so that they are sent at 1 sinterval for cell and user. Profile creates load also when no users are

present due to cell interference measurement reports. Profile isrecommended, when traced eNB amount is limited and there existsenough tracing capacity both in E-UTRAN and Tracing PC platform,e.g. in SyVe and FiVe test, and early phase low load Trials andPilots.

CP+UP_AckNack_MeasRep: Includes CP+UP_MeasRep profilemessages and CP & UP PDU Ack Nack messages. Ack Nackmessages are not filtered and are sent approx 50 ms interval peruser -> Profile causes heavy load and is recommended to be used

only for limited time testing periods for limited amount of eNBs, whenAck Nack information specifically is needed for troubleshootingpurposes

Only RawAlarms: Includes only RawAlarm messages. Profile islight and can be used for large amount of eNBs for triggeringpurposes (when related trigger is implemented in future Emil profileversion). e.g. when certain raw alarms precedes failure situation likeFSP/eNB crash or call failure





Only PM Counters: Includes only PM counter messages. Profile is

light and can be used for large amount of eNBs for drawing KPIgraphs (when KPI graphs are implemented in future Emil profileversion). In the future can be used also for triggering TechReportsfetching and remote UDP print tracing

Only RawAlarms & PM Counters: Includes only PM countermessages. Profile is light and can be used for large amount of eNBswhen both Raw Alarms and PM counters are wanted to bemonitored at the same time.

Figure 3 LTE Streaming/Monitoring profiles view, accessed by File ->Connect LTE -> Monitoring Profiles



Emil Views


2.4 Main view

Main View opens first when Emil application is started. Main view showsthe parsed trace scenarios in Scenario/Trace view and the traced on-lineor off-line files is Source view Upper bar Emil main commands

File

Open (Ctrl+O): Opens a file dialog from which new logs may beopened. Open function can also be performed by Drag and Drop

Connect to RNC…: Opens new view for establishing RNC logtraces

Connect to LTE BTSs…: Opens new view for creating eNBinstances, establishing eNB log traces and performing BTSManager actions

Close: Closes all open logs and clears the trace grid

Recent files: Lists recently opened Emil files, which can be re-opened

Recent directories: Lists directories where files have been

recently opened. Selecting directory will show directory filecontent to be opened

Exit: Exits Emil and closes all open child views/windows

Edit

Copy (Crtl+C): Copies selected content, like one scenario row

Find…(Ctrl+F): Opens Find-dialog for finding matches fromscenario values or message name from all traces. Find searches for the first occurrence of the specified search word.

Select searches for all occurrences of the specified search wordand selects all those rows. Bookmark searches for alloccurrences of the specified search word and bookmarks allthose rows

Find Next (F3): Proceeds to next match according to Find-dialog settings

Find Previous (Ctrl+F3): Proceeds to previous match accordingto Find-dialog settings





Toggle Bookmark (Ctrl+F2): Marks or unmarks selected

scenario row into bookmarks, background is changed to lightgreen

Select Bookmarked (Ctrl+Shift+F2): Select all rows that arebookmarked

Next Bookmark (F2): Proceeds to next bookmark and selects it

Previous Bookmark (Alt+F2): Proceeds previous nextbookmark and selects it

Clear All Bookmarks: Clears all created bookmarks in the view

Tools Options (Ctrl+O): Opens Options-dialog for defining sack,

profile and Emil view settings

SSH session…: Opens SSH-dialog for creating SSHconnections to defined IP address.

Find messages in files (Ctrl+Shift+F): Opens Find messagesin files dialog. Source files can be selected from directory orfrom already opened files in Emil. Update button will listavailable files and prints message name from sack information.

Find button creates list of files and order, where selectedmessage is traced. Message content can be opened by double-clicking message.

File converter and splitter:

NAS converter: Opens dialog where NAS message Hex dumpcan be copied and converted into NAS text format

Copy Sacks: Shows available sacks from options definedsource to be copied under Emil sack folder

PAC builder: This feature is not supported in Emil LTE profileand is only available if McBED is installed on the computer. Thisis a tool that makes it very easy to e.g. fetch, edit or compilePAC files. Normally no editing is needed to the PAC beforecompiling by using the check boxes visible in the lower half ofthe window by pressing Advance. These options can be hiddenby pressing Simple

Environment

Change sack and profile (Ctrl+F5): Shows available sacks andprofiles to be loaded into use. Profile .ini files are also re-loaded



Emil Views


Reload current sack and profile (F5): Reloads currently active

sack profile .ini files, e.g. if .ini file content has been changed Reload actions (Shift+F5): Reloads action commands from .ini

files, e.g if .ini file content has been changed

Show current Fields2.ini: Opens Fields2.ini C# source code ina new window. Fields2.ini is written by Emil maintenance forcreating scenario columns content

Edit current Fields2User.ini: Opens Fields2.ini C# sourcecode in Emil editor for editing. Fields2User.ini allows Emil usersto create additional scenario columns

Do profiling for trace scripts: Opens profiling dialog forfields2.ini and Fields2User.ini scripts, which prints how mucheach message is using processing power in these trace scripts.Can be used, when the tracing seems to be to heavy for the PC

Show current SourceProfile.ini: Opens SourceProfile.ini C#source code in a new window. SourceProfile.ini is written byEmil maintenance for defining source file printable information,font and background color in source view

Edit current SourcePofileUser.ini: Opens

SourceProfileUser.ini C# source code in Emil editor for editing.SourceProfileUser.ini allows Emil users to add additionalinformation, font and background colours in source view

Do profiling for source scripts: Opens profiling dialog forSourceProfile2.ini and SourceProfileUser.ini scripts, which printshow much each message is using processing power in thesetrace scripts. Can be used, when the source information printingseems to be to heavy for the PC

Show current MessageView.ini: Opens MessageView.ini C#

source code in a new window. MessageView.ini is written byEmil maintenance for defining Message User data content, fontand background colour in Trace view

Edit current MessageViewUser.ini: OpensMessageViewUser.ini C# source code in Emil editor for editing.MessageUser.ini allows Emil users to add additional info userdata info, font and background colours in Trace view

Do profiling for message view scripts: Opens profiling dialogfor MessageView.ini and MessageViewUser.ini scripts, which



Emil Views


Set snapshot filter for TCP: Open Trigger View for setting

snapshot (TechReport) triggers Traces

Resize columns: Fits scenario column width to fit content

No sort: Remove sort from scenario view rows

Sort by colour: Sorts scenario rows based on background colorin scenario view

Show: Returns hidden column back into view

Sources

Resize columns: Fits source column width to fit content

No sort: Remove sort from source view rows

Sort by colour: Sorts source rows based on background color

Window

Close all child forms: Closes all Emil window/views, exceptmain view

Rename form: Enables user to rename the window

Help Search…: Opens Help dialogs search tab for typing search

words

Content…: Opens Help dialogs search tab for browsing helpcontent

Index…: Opens Help dialogs Index tab for browsing helpcontent in alphabetical order

About…: Prints used Emil version

Release information…: Prints added new functionality ofcurrent and past Emil versions

Show logs: Opens new window, in where Emil actions areprinted. Can be used also for debugging .ini files by adding logprints in the C# code





GC: Runs a garbage collection that will free any memory resourcesthat are not needed anymore. This is done automatically every timeEmil think it is needed but it can be manually started from here tofree some memory if Emil consumes a lot of memory

2.4.1 Options view

Most of static Emil setup is done via Options view

Sack path: Defines directory where available sacks can be chosenfrom Environment -> Change sack and profile…

Profile path: Defines directory where available sacks can be chosenfrom Environment -> Change sack and profile…

From where to copy sacks when selecting ‘Tools -> Copysacks…’: Defines network drive where latest sack can be updatedunder sack path

Address to WWW-PDE: Link to parameter WWW data base, fromwhere parameter descriptions can be checked in Message View. Notsupported in Emil LTE version

Address to ee_pdeswb: Defines path where PDE SW builds arestored. Not supported in Emil LTE version

Open files into "Message view" by default: Makes Emil function likeIDA2 so that all logs that are opened are straight away opened in aMessage by message window without any parsing. If parsing is laterwanted for some specific log then Source-><file name>- >Parse sourcecan be selected from the Main screen

Automatically show all messages in the log if no calls were found:If a file is opened and it includes no messages associated with anycalls, then the log is automatically opened into a Message viewwindow, like IDA2. Any file can always be opened into a Message view



Emil Views


from Source-><file name>- >Open messages. Not supported in Emil

LTE profile Automatically show file as text if no messages were found: Any

files that include no messages at all are automatically open into a texteditor window. Can be done for any file from Source-><file name>->Open as text. Not supported in Emil LTE profile

Automatically try to determine sack version: Emil defines activesack automatic. Not supported in Emil LTE profile

Auto merge files with same physical computer: Not supported inEmil LTE profile

Max number of files to read simultaneously: Defined how many filesare processed at the same time, when folders or files are dragged anddropped

Show grid lines in “L3 analyzer”: Ads grid lines to L3 analyzer view.Not supported in Emil LTE profile

Tool tips in the “L3 analyzer” includes only messaged header:Defines tool tips functionality in L3 analyzer view. Not supported in EmilLTE profile

Data part in "Tree view" starts from offset zero: The messageheader always starts from offset zero when investigated in MessageTree view. With check box can be desired if also the data part shouldstart from offset zero or from the offset after the header.

Automatically use big-endian if pointer is 8 bytes or sack is forLTE: Emil checks parameter values for big and little endianessaccording to explained conditions

Big-endian mode: Emil checks always parameter values for big andlittle endianess. Not used in Emil LTE version

Double clicking a call in the "Main screen" opens: With this can beselected into which view a trace should be opened when double clickedin the Main screen





Figure 4 Options view, accessed by Tools -> Options…

2.4.2 Columns

In many Emil views the information is printed into cell matrix, in whereeach column represents a specific information and data type. Columncontent depends on both on .ini file C# code and hard coded Emil code ->different Emil views have different types of columns. For each columns is



Emil Views


defined a value format, e.g. Boolean, MultiValue, Time or Integer. Right

mouse click activates commands for columns; available commandsdepend on column properties. For detail column content see Emil viewdescriptions.

Secondary sort: Sorts scenario rows according to selected column

value inside primary sort limits. Primary sort is performed by doubleclicking column name.

Hide: Hides columns from Scenario view

Count summary of values: Opens Summary view, in where iscalculated statistics for select column values, like Sum, Min, Max andAverage values

Summary: Opens Summary view, in where is calculated absolute andpercentage value distribution for selected column

Summary of selected: Opens Summary view, in where is calculated

absolute and percentage value distribution for selected columns

Copy: Copies whole column values

Copy selected: Copies selected column cells from selected rows

Hex/Dec view: Shows column values in either hex or decimal format.Command visible only if column is defined as integer value format

Show constants: Prints constant values in text format instead ofnumerical presentation





Constants for xxx: Prints available constants from sack for the data

type used in column. No type selected: Prints available all available data types and

constants from sack. Command visible only if column has no datatypes used

Expose as: In case of MultiValue and MultiText column value format,the information can be printed in one line or multiple lines

Show time: Shows time without date. Command visible only if columnis defined as time value format

Show date: Shows time without date. Command visible only if column

is defined as time value format

View Scripts: Opens in Emil viewer .ini C# code, which is related toselected column

Figure 5 Summary view, accessed by right mouse click on top of selectedcolumn -> Summary

2.5 Scenario/Trace view

Scenario/Trace view combines traced messages into different scenarios.It is included in Main view. Scenarios are built from opened Sources(traced message logs) either On-line or Off-line based on trace .iniscripts. Traces can be opened in message view by double-clicking thescenario.



Emil Views


Note1! There will be only one LTE Profile for all RL releases. Scenarios

are build to support different RL releases gradually -> Newer RL releasestypically are not tested as much and might be suffering from parserlimitation in the beginning of development cycle

TraceParser.ini

Parses messages from each BTS trace separately for creatingscenarios

Each message returns a value

All messages with same value are included in the same scenario linein the main View until scenario is closed -> Messages with same

return value, e.g. CRNTI, from two BTS is shown in separate lines

Call scenarios are closed, when can be assumed that the call is nolonger active in the cell

BTS and Cell scenarios are not closed -> All BTS and Cell relatedmessages in related scenarios during the whole tracing period(source file remains the same). If IP connection is broken, e.g. due toBTS reset, Emil tries to reconnect to the BTS and continue tracinginto same source file

Closing trace closes all scenario and starting trace for same BTS willcreate a new source file

Only sack defined message parameters can be used for parsing,because ASN.1 and NAS decoder are too heavy (they can bedecoded for limited amount of messages in message view)

Fields2.ini

Parses all messages inside one scenario for creating scenarioinformation

Defines what columns are visible

Defines what information is printed in Scenario view column cells,mostly based on included messages and their parameters inside thescenario

Defines what background and font colours are used in Scenario view

Only sack defined message parameters can be used for parsing,because ASN.1 and NAS decoder are too heavy (they can bedecoded for limited amount of messages in message view)





Defines triggering conditions for tech report fetching, trigger is

activated when profile is loaded Based on scenarios the call can be traced based , BTS, Cell and

Ue_MME_APID column information

Call and HO failures are printed Out Cause and Errors columns

Cell and BTS states and related raw alarm are printed in relatedcolumns

Columns (currently included in fields2.ini)

Trace id: Created automatically for every scenario, index increases

as long Emil is active Source id: Shows from which source file the scenario is build

Start time: Prints time, when first message to scenario is received

Stop time: Prints time, when last message to scenario is received

Duration: Scenario duration = Stop Time-Start Time

Trace Type: Prints is the scenario type

Call: Scenario includes call related CP, DL UP and Protocolmessages. UP measurement report messages can be used for

drawing data graphs for user DL MSC, if UP messages areselected active in the monitoring profile

Paging & Preamble: Scenario includes Paging and RACHPreamble messages for each cell. In future releases RACHPreamble messages will be included in call scenarios

S1Paging & X2HoRequest: Scenario includes S1 Paging andTarget cell X2 HandoverRequest messages. In future releasesTarget cell X2 HandoverRequest messages will be included incall scenarios

Cell UP: Scenario includes UL UP Measurement reports, whichcan be used for drawing data graphs for user UL MSC and cellinterference, if UP messages are selected active in themonitoring profile

Cell CP: Scenario includes Cell related CP messages andrawalarms (e.g. Setup, Delete, Blocking)

eNB CP: Scenario includes eNB related CP messages andrawalarms (e.g. Re-start, configure, S1 states)



Emil Views


eNB PM: Scenario collects PM counter messages, which can be

used for drawing KPI graphs un future Emil LTE profiles Network: Prints PLMN name based CC and MNC

MMEI: Prints MME Id used in GUTI during call establishment, whenit is visible in signalling

MMEGI: Prints MME Group Id used in GUTI during callestablishment, when it is visible in signalling

GW IP: Prints used SAE GW IP address

GW ID: Prints used unique Call ID used by SAE GW

ID Type: Prints is MME using IMSI, GUTI/S-TMSI or Random IDvalue for identifying the UE during call establishment. Usually IMSI isnot used by MME because security purposes. Depending MMEsetting the TMSI can be changed every time the UE establishes anew call or kept the same for limited amount of call establishments -> UE HW tracking may be limited due to MME settings

UE Category: Prints UE category according to below table

User EquipmentCategory

Maximum L1datarate Downlink

Maximum number ofDL MIMO layers

Maximum L1datarate Uplink

Category 1 9.8 Mbits/s 1 4.9 Mbit/s

Category 2 48 Mbits/s 2 24 Mbit/s




Max Agr DL: Prints UE maximum allowed average aggregated DLdata rate in kbps received in InitialContextSetupRequest orHandoverRequest messages according to subscriber HSS profile.Note that peak bit rate can be higher than average bit rate

Max Agr UL: Prints UE maximum allowed average aggregated ULdata rate in kbps received in InitialContextSetupRequest orHandoverRequest messages according to subscriber HSS profile.Note that peak bit rate can be higher than average bit rate

eNB: Prints the source eNB IP address or name, if it is defined inBTS connections BTS list

Target eNB: In case of HO prints the target eNB IP address orname, if it is defined in BTS connections BTS list





Cell: Prints LNCEL ID (Cell Id) as defined in RNW commissioning

parameters Target cell: In case of HO prints target Cell Id.

Ue_MME_APID: MME allocated ID for each call. NSN MMEallocates one MME_APID for one UE, until the UE has been out ofRRC connected state longer than the MME internal timer allows.This is the only feasible identifier to be used for tracing calls duringmobility (TMSI or IMSI are not informed during HOs)

Source UeID/X2ID: Prints either UeID (Intra eNB HO) or X2ID (IntraeNB HO) of source cell during HO. Can be used aside the

Ue_MME_APID for tracing calls during mobility. Note that UeID isunique only for one cell and has typically different value than CRNTI.X2ID is unique for one eNB

Target UeID/X2ID: Prints either UeID (Intra eNB HO) or X2ID (IntereNB HO) of target cell during HO. Can be used aside theUe_MME_APID for tracing calls during mobility. Note that UeID isunique only for one cell and has typically different value than CRNTI.X2ID is unique for one eNB

CRNTI: Prints CRNTI identifier for call scenarios. Note that CRNTI is

unique only for one cell and has typically different value than UeID.From message parameters can be checked does a SystemComponent use CRNTI, UeID or both for identifying calls, in casemore detailed call analysis from TechReports are needed

UeID: Prints UE Id for call scenarios. During Intra eNB HOUeId=Source UeID/X2ID. Note that UeID is unique only for one celland has typically different value than CRNTI. From messageparameters can be checked does a System Component use CRNTI,UeID or both for identifying calls, in case more detailed call analysisfrom TechReports are needed

TMSI/MISN: Prints UE S-TMSI value in Hex or MSIN value indecimal format depending what ID format MME is using, visible inColumn ID Type. IMSI can be calculated from formula IMSI = MCC(3 digits)+MNC (2 digits) +MSIN (10 digits)

In Cause: Prints reason how the UE has entered the cell, either as“New Call”, “Re-establishment”, “Ghost Call”, “Inter eNB HO” or“Intra eNB HO”

Out Cause: Prints reason how the UE has exit the cell, either as“Re-est Reject”, “Ghost Call”, “Inter eNB HO”, “Intra eNB HO” or call



Emil Views


failures “Radiolink Failure”, “eNB Release”, “EPC release”, “No UE

Messages” or “No EPC Messages”. See Triggers and colourdescriptions for details

HO Attempt: Prints is either Inter or Intra eNB HO initiated for a call.

Source RSRP: UE reported serving cell RSRP in dBm

Target RSRP: UE reported first neighbour cell RSRP in dBm

Target2 RSRP: UE reported second neighbour cell RSRP in dBm

RRC Est Cause: Call establishment cause inRrcConnectionRequest message

Emergency: UE sends RrcConnectionRequest for setting anemergency call with SRB and DRB. Emergency calls havehighest priority

HighPriorityAccess: UE sends RrcConnectionRequest forsetting a high priority call with SRB and DRB. High priority callshave higher priority than normal calls

mt-Access: EPS has data to sent to UE and pages it. UEreplies with RrcConnectionRequest for setting a call with SRBand DRB

mo-Signalling: UE sends RrcConnectionRequest for RRCsetting a signalling link with SRB e.g. for Tracking Area Updateor Attach procedure. Note that some UEs use mo-siganallingcause also when they setup a DRB for data transfer

mo-Data: UE has data to send and it sendsRrcConnectionRequest for a setting call with SRB and DRB

S1 Rel Cause: Call release cause in S1APMME intiated: UEContextReleaseCommandeNB initieated: InitialContextSetupFailure or

UEContextReleaseRequest

Failure Phase: Prints in which phase of new Call establishment orHO a failure has occurred, check Time columns for phase details

Cause Det: Additional information and notes related to a scenario.Can be added also by Fields2User.ini

Error Source: Prints System Component detecting error, either as“TUP”, “MAC” or “CP” (Error cause printed by control planesignalling)





Errors: Prints Error cause as defined in sack

First RLs_Failure: Prints first active RL failure cause as defined insack

Last RLs_Failure: Prints last RL failure (can be also failure cancel)as defined in sack

#RLs_Failures: Prints how many times RL failure has been changedbetween active and cancelled. High number indicates poor signalconditions for the UE

Preamble sequence: Prints detected preambles sequence numberduring call establishment

UL Sync Time: Time it takes the BTS to get UL synchronizationduring HO, calculated as time difference between PDCP Enable andfirst detected RACH impulse response

Target Intra HO Prep Time: Time between receivedHandoverRequest and RrcConnectionReconfiguration signallingwhen UE enters cell by Intra eNB HO

Target Intra HO Access Time: Time betweenRrcConnectionReconfiguration and release source cell Ids(=ENBC_ID_DEALLOCATION_RESP_MSG) signalling when UEenters cell by Intra eNB HO

Target Inter HO Prep Time: Time between receivedHandoverRequest and RrcConnectionReconfiguration signallingwhen UE enters cell by Inter eNB HO

Target Inter HO Access Time: Time betweenRrcConnectionReconfiguration and release source cell Ids(=ENBC_ID_DEALLOCATION_RESP_MSG) signalling when UEenters cell by Inter eNB HO

RRC Setup Time: Time between RrcConnectionRequest andRrcConnectionSetupComplete signalling when a new call isestablished, i.e. how long it takes for the UE to establish a workingRRC connection towards eNB

RRC Access Time: Time between RrcConnectionSetupCompleteand InitialContextSetupRequest or RRC release signalling when anew call is established, i.e. how long it takes for the eNB to establisha working RRC connection towards EPC



Emil Views


RAB Setup Time: Time between InitialContextSetupRequest and

RrcConnectionReconfiguratioComplete signalling when a new call isestablished, i.e. how long it takes for the eNB to establish a workingRAB connection towards UE

RAB Access Time: Time betweenRrcConnectionReconfiguratioComplete andInitialContextSetupResponse signalling when a new call isestablished, i.e. how long it takes for the eNB to establish a workingRAB connection towards EPC

RAB Active Time: In case of New call time betweenInitialContextSetupResponse and call termination orHandoverRequest signalling. In case of HO time between releasesource cell Ids and call termination or HandoverRequest signalling.I.e. how long the Radiolink is allocated sending and receiving data inthe cell without mobility.

Source Intra HO Prep Time: Time between sent HandoverRequestand received HandoverRequestAck signalling when UE exits cell byIntra eNB HO

Source Intra HO Access Time: Time between receivedHandoverRequestAck and call termination when UE exits cell by

Intra eNB HO, i.e. how long it takes to perform HO execution + HOcompletion in source cell

Source Inter HO Prep Time: Time between sent HandoverRequestand received HandoverRequestAck signalling when UE exits cell byInter eNB HO

Source Inter HO Access Time: Time between sentHandoverRequest and received HandoverRequestAck signallingwhen UE exits cell by Inter eNB HO, i.e. how long it takes to performHO execution + HO completion in source cell

eNB Name: Same as eNB column value, column duplicated so thatinformation is visible also for eNB CP and Cell UP/CP trace relatedcolumns

Cell Id: Same as Cell column value, column dublictaed so thatinformation is visible also for eNB CP and Cell UP/CP trace relatedcolumns

#Cell Delete: Prints how many times cell has been deleted duringtracing (e.g. by user or blocking fault).





#Cell Setup: Prints how many times Cell has been attempted to be

setup Cell State: Prints current/last cell state as “Configuring”, “On Air”,

“Blocked” and “FSP reset”

Cell rawAlarms: Prints 20 last cell related raw alarm incidents(Start, Cancel, Event) and corresponding time stamps

#BTS Reset: Prints how many times BTS has been reset duringtracing (e.g. by user or blocking fault)

#BTS Start-up: Prints how many times BTS has been attempted tobe configured during tracing

BTS State: as “Configuring”, “Link Down”, “Blocked” and “Active”

BTS rawAlarms: Prints 20 last Non-cell related raw alarm incidents(Start, Cancel, Event) and corresponding time stamps

Row background colours (currently defined in fields2.ini)

Light Green: Scenario bookmarked

Dark Blue: Scenario selected

Silver: Re-establishment ->UE tries to re-connect after drop via

unsupported Re-establishment procedure) Dark Grey: Ghost Call -> Misinterpret RACH Preamble either due to

UE transmission “leak” to PRACH PRBS or eNB misinterpretationfrom interference

DarkPink: No UE Messages -> UE doesn’t reply to eNB RRCmessages

Red: No EPC messages -> MME doesn’t reply to eNB S1APmessages

Coral: Radiolink Failure -> Call released due to Radiolink failures byeNB

LightPink: ECP Release -> Call released due to Radiolink failuresby eNB (probably because UE has dropped and established a newcall in another cell)

OrangeRed: eNB Release -> eNB releases call withUEContextReleaseRequest due to failures or errors detected bysome of the eNB System Components



Emil Views


LighCoral: RAB Setup Failure -> eNB can not setup E-RAB

according to InitialContextSetupRequest parameters and replies withInitialContextSetupFailure, e.g. because UE doesn’t reply toRrcConnectionReconfiguration message

Row font colours (currently defined in fields2.ini)

Grey: Call Scenario is open

Red: Cell or BTS have dropped in non-operational state

Orange: Cell or BTS are configuring to operational state

Green: Cell or BTS are in operational state

Braun: Cell User Plane trace type Olive: Paging & Preambles trace type

DarkRed: S1Paging & X2HoRequest trace type

Turquoise: eNB PM trace type

Violet: Radiolink failure is active for a Call trace. Note that Radiolinkfailures don’t necessarily indicate faults in the network, if the call isnot failed

Blue: Error is active for a Call trace, overwrites violet colour from

Radiolink failure. Note that Errors don’t necessarily indicate faults inthe network, if the call is not failed

Fields2User.ini

User can add more column on the right side on Main View

Code is in similar format as in Fields2.ini (C#)

File is not over written like Fields2.ini, if LTE profile is included in theEmil installation package





Right mouse click commands for scenarios




Remove selected: Removes selected trace row(s) from Scenarioview. Removed Scenario row(s) can be returned to view by reloadingprofile (F5)

Remove all but selected: Removes all but selected trace row(s)from Scenario view. Removed Scenario row(s) can be returned toview by reloading profile (F5)

Trace View: Opens selected scenario row in Trace view

Message View: Opens selected scenario row in Message view

Send as mail attachment: Opens outlook mail with selected

Scenario row(s) attached as .emil file(s). Attached file(s) includescomments and bookmarks

Save (Ctrl+S): Saves selected Scenario row(s) as [Trace id].emilfile(s) to source file directory. Saved file(s) includes comments andbookmarks

Save as…: Saves selected Scenario row(s) as one.emil file to userselected directory. Saved file includes comments and bookmarks

Save as HTML…: Save selected scenario row(s) as L3 view HTMLformat



Emil Views


Save to directory…: Saves selected Scenario row(s) as .emil file(s)

to user selected directory. Saved file includes comments andbookmarks

Save as CSV…: Saves selected Scenario row(s) as .csv file(s) touser selected directory

2.6 Source view

Source view is included in Main view. It shows the files and their contentused for parsing the scenarios by TraceParser.ini and Fields2.ini. On-line(.emil file) trace files are opened automatically for each traced BTSseparately. In Off-line analysis easiest way is to drag and drop the folder,where .emil (Emil recorded or saved trace) or .bin (BTSLog recordedtrace) files exist. Emil will ignore irrelevant files, like .zip, .mpg, .exe.Double clicking source file will open the traced messages in a newMessage View window Off-line Sources can be added also via File->Open (.emil or .bin trace file)

Columns (currently included Sourview.ini)

Source id: Id number for source file, index is started from nextavailable number every time new source file is loaded or profile is – re-loaded for open source files

Source name: Open source file name and directory

Start time: Time when tracing was started

Stop time: Time when tracing was stopped

Duration: Duration of trace

Trace count: How many scenarios where build from trace visible in

Main view

Message count: How many messages were captured in trace file

Right mouse click commands for sources


Copy column: Copies selected column






Send as mail attachment: Opens outlook mail with selected source

file(s) attached as .emil file. File includes bookmarks and comments Save as…: Saves selected source file(s) as .emil format file with

user defined name and directory. File includes bookmarks andcomments

Parse/Reparse: Parses source files according to TraceParser.inicode

Delete: Deletes selected source file(s) from hard disk

Message view: Opens selected source file(s) in new Message viewwindow

Convert or Split: Opens Convert or Split dialog for creatingcombined .emil or ASCII logs from existing source files. Target filescan be combined using Split and Combined functions to include orexclude only certain Families (Program blocks) or Processes(Message Process Id)

Find messages: Opens Find messages in files dialog. Source filescan be selected from directory or from already opened files in Emil.Update button will list available files and prints message name fromsack information. Find button creates list of files and order, where

selected message is traced. Message content can be opened bydouble-clicking message

Open as text: Opens a complete file into a text editor. This is onlysuitable for a ASCII files. File converter can be used for convertingfiles to ASCII mode if needed.

Find: Opens Find-dialog for finding matches from scenario values ormessage name from all traces. Find searches for the first occurrenceof the specified search word. Select searches for all occurrences ofthe specified search word and selects all those rows. Bookmark

searches for all occurrences of the specified search word andbookmarks all those rows



Emil Views


Figure 6 Main view, including Scenario and Soure views. Light green row

is bookmarked and with right mouse click are openedadditional commands for editing, saving or opening thescenario in either Trace view or message view

2.7 Message view

Message view is used for analyzing traced messages and theirparameters and possible protocol content. Message view can beaccessed by double clicking scenario or source in main view (if Messageview is selected as default view in Options) or by right mouse click. Activemessage is indicated with Dark blue back ground

NOTE! Currently traces can be opened into message view only in off-linemode

Upper bar commands

File





Stop:

Send as mail attachment: Opens outlook mail with open tracemessages attached as .emil file

Save: Saves selected open scenario as [Trace id].emil file tosource file directory. Saved file includes comments andbookmarks

Save as…: Saves open trace as .emil format with user definedname and directory

Save selected: Saves selected messages from Emil trace as.emil format with user defined name and directory

Exit: Closes Message view window

Edit

Find…(Ctrl+F): Opens Find-dialog for finding matches fromscenario values or message name from all traces. Find searches for the first occurrence of the specified search word.Select searches for all occurrences of the specified search wordand selects all those rows. Bookmark searches for alloccurrences of the specified search word and bookmarks allthose rows

Find Next (F3): Proceeds to next match according to Find-dialog settings

Find Previous (Ctrl+F3): Proceeds to previous match accordingto Find-dialog settings

Toggle Bookmark (Ctrl+F2): Marks or unmarks selectedscenario row into bookmarks, background is changed to lightgreen

Select Bookmarked (Ctrl+Shift+F2): Select all rows that are

bookmarked

Next Bookmark (F2): Proceeds to next bookmark and selects it

Previous Bookmark (Alt+F2): Proceeds previous nextbookmark and selects it

Clear All Bookmarks: Clears all created bookmarks in the view

Columns

Resize columns: Fits Message view column width to fit content



Emil Views


No sort: Remove sort from Message view rows

Sort by color: Sorts Message rows based on background colorin Message view

Show: Returns hidden column back into view

View

Auto row height:

Message tree: Shows for selected message Parameter andProtocol views

Graphs: Shows available graphs created in Graphs.ini and

GraphsUser.ini files and adds selected graphs view to Messageview

Memory Monitoring

Automatically activate: Not yet supported in Emil LTE profile

Filter Memory Monitoring Messages: Not yet supported inEmil LTE profile

Activate: Not yet supported in Emil LTE profile

Deactivate: Not yet supported in Emil LTE profile

Show all variables for process: Not yet supported in Emil LTEprofile

Tools

Reload MessageView.ini files: Reloads MessageView.ini andMessageViewUser.ini files, e.g. when .ini file content has beenchanged

Edit MessageViewUser.ini: Opens MessageViewUser.ini C#source code in Emil editor for editing. MessageUser.ini allows

Emil users to add additional info user data info, font andbackground colors in Trace view

Show MessageView.ini: Opens MessageView.ini C# sourcecode in a new window. MessageView.ini is written by Emilmaintenance for defining Message User data content, font andbackground color in Trace view

Reload Graphs.ini files: Reloads MessageView.ini andMessageViewUser.ini files, e.g. when .ini file content has beenchanged





Edit GraphsUser.ini: Opens GraphsUser.ini C# source code in

Emil editor for editing. MessageUser.ini allows Emil users to addadditional info user data info, font and background colors inTrace view

Show GraphsView.ini: Opens Graphs.ini C# source code in anew window. Graphs.ini is written by Emil maintenance fordefining what kinds of graphs are printed from traced messagecontent

Help…:Opens Help dialog

Decode ASCII for all messages: Opens ASCII protocol content

of all messages in message view into Emil editor Show current MessageView.ini: Opens MessageView.ini C#

source code in a new window. MessageView.ini is used fordefining Message User data content, font and background colorin Trace view by Emil maintenance

Edit current MessageViewUser.ini: OpensMessageViewUser.ini C# source code in Emil editor for editing.MessageUser.ini allows Emil users to add additional info userdata info, font and background colors in Trace view

Window

Rename form: Enables user to rename the window foridentifying opened scenario, e.g. “Radiolink failure CRNTI56428”

Help

Content: Shows Help dialog




Copy column: Copies selected column

Remove selected: Removes selected trace row(s) from Scenarioview. Removed Scenario row(s) can be returned to view by reloadingprofile (F5) or MessageView.ini files

Remove all but selected: Removes all but selected trace row(s)from Scenario view. Removed Scenario row(s) can be returned toview by reloading profile (F5) or MessageView.ini files



Emil Views


Save selected: Saves selected messages from Emil trace as .emil

format with user defined name and directory Comment…: Open Emil editor for adding comment to Message view

comment column

Remove comment: Clear comments for selected messages inMessage view

Make TNSDL code: Opens selected messages in Emil editor inTNSDL format

Messages by selected Time: Opens all messages from selectedsource(s) from the time frame that is defined by the messages that

are selected at the moment in the current grid

Compare messages: Not yet implemented in Emil LTE profile

Parent search: Open Emil Main/Scenario view and selects sourcescenario active

MessageView.ini

Defines what information is printed in User data column

Defines background and font color

Columns (currently defined in MessageView.ini) Order: In which order message has been traced or parsed into

scenario

Message: Message Id in hex read from traced message header

Message Name: Message name defined in sack types.dat file

User Data: Additional message information defined to be printed byMessageView.ini and MessageViewUser.ini files

Protocol: Traced message protocol. Not yet implemented in Emil

LTE profile Send board: Sending board read from traced message header.

Board names are not yet implemented in Emil LTE profile

Send CPU: Sending CPU read from traced message header. CPUnames are not yet implemented in Emil LTE profile

Send task: Sender task read from traced message header

Rec CPU: Sending CPU read from traced message header. CPUnames are not yet implemented in Emil LTE profile





Rec board: Receiving board read from traced message header.

Board names are not yet implemented in Emil LTE profile Rec task: Receiver task read from traced message header

Processor IP: Traced BTS IP address

Time: Time stamp when message was captured by tracing PC. Thistime value is currently used in Emil time calculations

Target time: Time stamp when message was sent from traced BTS

Time diff: Time difference of first captured message and followingorder messages in scenario or source

Comment: User manually added comment Length: Message Length in bytes read from traced message header

SFN: Message System Frame Number

Row font colors (currenly defined in MessageView.ini)

Blue: TUP_SRB message including RRC protocol content

DarkBlue: UEC and ENBC Handover messages

LightGreen: TUPC_L3X2 message including L3X2 protocol content

Coral: TUPC_L3S1 message including L3S1 protocol content Row background colors (currently defined in MessageView.ini)

Coral: Error indication in message

Violet: Radiolink Failure indication in message

LightGreen: Radiolink Failure cancellation in message

2.7.1 Parameter view

Parameter view shows message structure and related parameters andtheir values. Parameters can be pointed in .ini file code based on theirname, Hex/Dec value, byte value, byte offset, constant value, data typeand length.

Parameter fields

Name: Message name as defined in sack

Hex value: Parameter value in hex after little and big endian check

Dec value: Parameter value in decimal



Emil Views


Constants: Parameter value in constant, if defined in sack

Data type: Parameter type as defined in sack Offset: Parameter starting byte offset from message header

Length: Parameter length in bytes


Copy path: Copies selected child parameter name and related mainparameter name(s) separared with a comma for creating explicitpath pointer. E.g. parameter “board” is pointing to both receiver andsender board parameters, unless pointed with copied path

“msgHeader.receiver.board” Show all constants: Prints all constant values defined in sack for

selected data type

Search from WWW-PDE…: Searches parameter description forWWW-PDE pages defined in options settings. Not supported in EmilLTE version






Copy column (Ctrl+C): Copies selected column Copy cell: Copies selected cell

Show as ASCII: Opens parameter data value in Emil editor as ASCIIcharacters

Show as other data type: Opens dialog for presenting parameterdata

Show as decimals: Opens parameter data value in Emil editor asdecimals, bytes separated with space

Show as bits: Opens parameter data value in Emil editor as bits,bytes separated with space

Show as bytes: Opens parameter data value in Emil editor as bytesseparated with space

Show as words: Opens parameter data value in Emil editor aswords (=2 bytes) separated with space

Show as aligned words: Opens parameter data value in Emil editoras aligned words (=2 bytes) separated with space

Show as dwords: Opens parameter data value in Emil editor asdouble words (=4 bytes) separated with space

Show as aligned dwords: Opens parameter data value in Emileditor as aligned double words (=4 bytes) separated with space



Emil Views


Add to MessageViewUser.ini: Opens MessageView.ini in Emil

editor and adds parameter in Fields2User.ini suitable syntax e.g.[Actions]MessageNbr:23B7, Action:Column(User data) += "cellId = " + cellId+ " "

Add to Fields2User.ini: Opens Fields2User.ini in Emil editor andadds parameter in Fields2User.ini suitable syntax e.g.[Actions]MessageNbr:23B7, Action:Column(cellId) = cellId

[Columns]

ColumnName:cellId, ValueType:IntegerValue Parent search: Returns back to main view and select scenario, from

which Message view has be opened

Edit: Find functions for searching parameter name and values

2.7.2 Protocol view

In case message payload includes data for Radio, Interface or NAS

protocols, the protocol content is printed as own view right side ofparameter view.

Note: Protocol decoders are too heavy to be used in trace parser .inifiles, thus Protocol content can be used by decoders only whenmessages are opened via message view.

RRC: Prints RRC protocol content in ASN1 format from TUP_SRBmessage payload content using external dll based decoder files. See3GPP TS 36.331 Radio Resource Control (RRC) Protocol specification and 3GPP TS 36.322 Radio Link Control (RLC) protocol specification

for protocol details S1AP: Prints X2AP protocol content in ASN1 format from TUPC_L3S1

message payload content using external dll based decoder files. See3GPP TS 36.413 S1 Application Protocol (S1AP) for protocol details

X2AP: Prints S1AP protocol content in ASN1 format from TUPC_L3X2message payload content using external dll based decoder files. See3GPP TS 36.423 X2 Application Protocol (X2AP) protocol details

NAS: Prints NAS protocol content in ASN1 format from TUPC_L3S1(and TUPC_L3X2) message payload content using external dll based





decoder files. See 3GPP TS 24.301 Non-Access-Stratum (NAS)

protocol for Evolved Packet System (EPS) Stage 3 for protocol details

Figure 7 Message view, accessed by double clickin source files in bottomof Main view or by right mouse click -> Message view

2.7.3 Graphs view

Graphs view is used for analyzing traced scenarios in graphical format. Itis accessed by clicking View -> Graphs in Message view or Sequenceview icon in Trace view. Available Graphs are defined by Emilmaintenance in Grahps.ini file or by Emil users in GraphsUser.ini file.Graph can be zoomed and location changed in both X and Y axisdirection by pressing left mouse button on top of the arrow icons andmoving the mouse at the same time on X or Y axis direction.

NOTE! Currently Graphs are defined only from RL10. With default UPmonitoring profile measurement report samples are received as one



Emil Views


second snapshot interval, i.e. peak snapshot results may give wrong

expression about average value since graph results are not average butone sample snapshot values

Graphs (currently included in Graphs.ini only for RL10)

Cell UP_UL Signal Strength: Draws cell interference calculatedfrom 20 PRB distance samples and user RSSI marked with CRNTIidentifier.

Cell UP_Cell UL MCS: Draws from Cell UP trace UL cell PRBconsumption, data rate, average modulation and amount ofscheduled users per TTI

Cell UP_UL PRB: Draws from Cell UP trace UL cell total PRBconsumption and user PRB allocation marked with CRNTI identifier

Cell UP_UL Data Rate: Draws from Cell UP trace UL cell total datarate and user data rate marked with CRNTI identifier

Cell UP_UL Modulation: Draws from Cell UP trace UL averagemodulation and modulation marked with CRNTI identifier

Call_DL MCS: Draws from Call trace DL PRB allocation, averagemodulation, average spatial mode and data rate





Figure 8 Graphs view, accessed by clicking View -> Graphs in Messageview or Sequence view icon in Trace view

2.8 Trace view

Trace view is used for enabling Scenario/trace message analysis throughmultiple parallel views in same window Trace view window. Different subviews are L3 analyzer, Message view, Sequence view and Graphs view.These views can be added from Trace view icons. Clicking a messageactive in one view also activates the same message in other views

Note! Currently traces can be opened into Trace view only in off-linemode

Upper bar commands

File



Emil Views


2.8.2 L3 view

L3 view shows signaling flow in Network element level based onTraceView.ini and TraceViewUser.ini files. It is accessed by clicking L3Analyzer view icon in Trace view. Not yet implemented in Emil LTE profile

Figure 10 L3 analyzer view on bottom of Trace view, accessed by doubleclicking scenario in main view and then L3 analyzer viewicon (if Trace view is selected as default view in Options) or

by right mouse click -> Trace view and then L3 analyzerview icon

2.9 Call statistics view

Will be implemented later





3 Emil .ini configuration files

Emil profile functions are based on .ini files, which are located under theEmil profile folder. Profile is included in the Emil installation file, andnewer Emil version will overwrite older .ini files. Additional profilefunctionality can be added by Emil user with xxxUser.ini files, which arenot overwritten by newer Emil version installation.

AsciiDecoders.ini: Defines how Radio protocols, Interface protocolsand NAS protocol is decoded from related message payload. For LTEactual decoding is done by external .dll files which are called by theAsciiDecoders.ini file.

AsciiDecodersUser.ini: Emil users can ad additional functionality forASCII decoding

DataDecoders.ini: Defines how compressed messages are opened.Not used in LTE

DataDecodersUser.ini: Not used in LTE

familyList.ini: Trace parser functionality in RNC. Not used in LTE

fields2.ini: Defines what columns, row font/background colours andinformation inside the column cells are printed in Main view forscenarios parsed by TraceParser.ini file

Fields2User.ini: Emil users can ad additional columns in Main viewand print additional information to fields2.ini defined columns

Graphs.ini: Defines what graphs can be drown when a scenario isopened from Main view to either Message view or Trace view

GraphsUser.ini: Emil users can ad additional graphs to scenarios

MessageView.ini: Defines what columns, row font/background coloursand information inside the column cells are printed in Message view

MessageViewUser.ini: Emil users can ad additional columns inMessage view and print additional information to fields2.ini definedcolumns

ScenView.ini: Describes of the look of Trace view



Emil .ini configuration files


SourceProfile.ini: Defines what columns, row font/background colours

and information inside the column cells are printed in Source view TraceView.ini: Not used in LTE

TraceViewUser.ini: Not used in LTE

TraceParser.ini: Defines how traced messages are parsed intoscenarios by returning a trace id for captured messages. Each eNBtrace stream is handled as an own trace entity. Messages with sametrace id are included in same scenario





4 Emil IDA2 Tool Env Sack files

The sack team produces aside the Sack tags also Test tool Sack envfolder, which has the message definitions used by IDA2 and Emil testtools. The folder is also referred as IDA2 sack. Test Env sack includesTypes.dat file, which defines Message Names, Messages Id, Messageparameters and names, Parameter lengths, Parameter constants andParameter data types. Currently there is no support for dynamicparameters, e.g. payload parameters for Protocol content, and thedynamic parameters are not visible for most part in Emil Message view.

Sack definitions can be checked from Emil parameter functions located inColumn and Message view commands. Or then directly by openingTypes.dat file in suitable editor application, like UltraEdit or Notepad ++.

The tool env are located at

\\Nsn-intra.net\dfs\RAN_BSENV\ida2_PDEs

Access right for sack drive can be requested with proper explanations

[email protected]



Appendix


Appendix





References



Glossary


Glossary

emil lte profile user manual i

Documents