Emil LTE Profile User Manual I

Emil LTE Profile User Manual

© Nokia Siemens Networks Networks Confidential


Only for Internal use, do not distribute outside NSN

© Nokia Siemens Networks, Networks, Proprietary & Confidential Confidential


Only for Internal use, do not distribute outside NSN


Contents

Contents

1 1.1 1.2

Emil installation.... installation............. ................. ................ ................. ................. ................. ................. ............. ..... 5 Emil installation installation from iSource installation installation file ................. ......................... ........ 5 Changing Changing Emil configuration configuration or platform platform version ................. ................... .. 6

2 2.1 2.2 2.3 2.4 2.4.1 2.4.2 2.5 2.6 2.7 2.7.1 2.7.2 2.7.3 2.8 2.8.1 2.8.2 2.9

Emil Views ................ ......................... ................. ................. ................. ................ ................. ................. .......... 7 Trigger view.................................. view.............. ......................................... .......................................... ..................... 8 LTE Streaming/BTS connections view............................ view....... .......................... ..... 10 LTE Streaming/Monito Streaming/Monitoring ring profile view ................ ......................... ................ ....... 13 Main view ................ ......................... ................. ................. ................. ................. ................. ................ .......... .. 17 Options view................................. view............. ......................................... ........................................ ................... 22 Columns Columns ................. .......................... ................. ................ ................. ................. ................. ................. ........... ... 24 Scenario/Trace view....................................... view.................. .......................................... ....................... 26 Source view.................................. view.............. ......................................... ........................................ ................... 37 Message Message view ................. ......................... ................ ................. ................. ................. ................. ........... ... 39 Parameter Parameter view ................. .......................... ................. ................. ................. ................ ................. ......... 44 Protocol Protocol view.................... view............................ ................. ................. ................. ................. ................ .......... .. 47 Graphs Graphs view ................. ......................... ................. ................. ................ ................. ................. .............. ...... 48 Trace view..................... view.............................. ................. ................ ................. ................. ................. ............. .... 50 Sequence Sequence view..................... view.............................. ................. ................ ................. ................. .............. ...... 52 L3 view ................ ......................... ................. ................. ................. ................ ................. ................. .............. ...... 53 Call statistics statistics view ................ ......................... ................. ................ ................. ................. .............. ...... 53

3

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

4

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

© Nokia Siemens Networks Networks


Summary of changes Version

Date

Author

Changes

1.0

10.11.2010

Antti Reijonen

First version, LTE Profile tested only against RL10 traces

1.1

24.11.2010

Antti Reijonen

Trigger view location changed, RL20 correction to LTE Profile (Graphs are only for RL10). Additional columns to fields2.ini

4 (60)

© Nokia Siemens Networks, Proprietary & Confidential

Emil installation

1

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

1.1 Emil installation from iSource installation file Off-line Emil can be installed to any PC with Windows XP or newer Windows OS  On-line

Emil used for tracing must be installed in PC using same IP sub network as traced BTS. NetAct PC platform with removable USB hard rive is one preferred option, when accepted by network owners

 Install

Emil from Emil.msi file located at https://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\sacks folder 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 and

profile  If

needed, updated traced BTS instances from File -> Connect to LTE BTSs -> File -> Import new BTS list

© Nokia Siemens Networks

5 (60)


1.2 Changing Emil configuration or platform version 

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



When BTS instances or monitoring profiles need to be changed to match another existing BTS instance and monitoring profile set, delete or rename old existing LteConn.dat file and copy new LteConn.dat file in that directory Emil is installed. New BTS instances and monitoring profiles 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 from Environment -> Change sack and profile…

 Delete

or rename old existing .ini file and copy new .ini file to profile folder. 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 Reload current sack and profile (F5) to take new xxxUser.ini file into use

6 (60)


Emil Views

2

Emil Views Emil functionality is implemented in different views. Different views are used for configuring Emil or for analyzing traced data. Multiple views can share same window or are located in a separate window. Emil views/windows are shown as separate object in Windows taskbar. 

Emil views functionality 

E-UTRAN / BTS management: With LTE Streaming/BTS connections view BTS Tech Reports can be fetched and BTS SW information checked. More E-UTRAN/BTS management functionality will be implemented later



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



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



E-UTRAN/BTS scenario and troubleshooting analysis: Traced messages can be grouped into scenarios and analyzed in Emil Main/Scenario view. Analysis can be done both on-line as well as off-line. Analysis can be drilled down in more detailed level in Message and Trace view. Information can be analyzed further in different data and graphical formats in Sequence, Graph and L3 analyzer views



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



User and Cell load and capacity: User Plane messages used for reporting User and Cell load and capacity are grouped as own scenarios. Degreased load and capacity may act as problem and fault symptoms


7 (60)


 Call

mobility: Control Plane messages used for call establishment, call termination and HOs are grouped as own scenarios. Dropped calls, failed calls, RL failures, signalling errors, delayed HO and synchronization times, un-specified signalling behaviour may act as problem and fault symptoms

 E-UTRAN/BTS

call statistics analysis: Scenarios are used for creating data and graphs HO duration, HO amount, HO success rate, Call drop rate, Call duration etc. E-UTRAN KPI values. Not yet implemented in Emil LTE version

 Additional

BTS log fetching in problem or fault situations: Based on traced scenario additional logs can be triggered to be fetched 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 Tech Report, when problem or fault situation is detected from Emil trace. BTS SC freeze logs to prevent over writing, when fetch snapshot command is received. Emil trigges use same remote TCP port as site Manager and thus Emil triggers are functional only when BTS Site Manager connection is not active Currently trigger functionality is rather limited, but it will be developed more flexible in coming releases. NOTE! Emil TechReport zip file size with TTI trace is approx 10 Mbytes and all fetched TechReports do not necessarily contain any fault information -> TechReports will create easily hidden cost from IT support and consume limited storing capacity if copied to network drives or repositories, like Electra or Pronto reports, without checking their validity first. It is recommended that triggered TechReport are linked to correct context with proper explanation based on Emil scenario analyze before sending 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 is released because of Radiolink failure by eNB. Typically Radiolink failures are symptoms of poor UL signal conditions. (Scenario view Out cause=Radiolink Failure)

8 (60)


Emil Views



Unexpected EPC Release: BTS Tech Report is fetched, when call is released by EPC during Radiolink failures. Typically Unexpected EPC Release is a symptom when a call has dropped from cell unaware and has established a new connection in another cell. (Scenario view Out cause=EPC Release)



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



UE Signalling missing: BTS Tech Report is fetched, when call is released because UE is not replying to RRC signalling. Typically UE Signalling 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 is released because EPC is not replying to S1AP signalling. (Scenario view Out cause=No UE Messages)



RAB Setup Failure: BTS Tech Report is fetched, when eNB fails in RAB Setup procedure. Typically UE is not responding to RrcConnectionReconfiguration or SecurityModeCommand messages

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


9 (60)


2.2 LTE Streaming/BTS connections view LTE Streaming/BTS connections view is used for managing BTS for tracing and log collection. View accessed by File -> Connect to LTE BTSs. When tracing is started Emil saves message traces under user defined path under BTS named folder in .emil format, maximum trace file size is defined by user. Starting trace sends each CPU defined in active Monitoring profile the filter message with user defined task and user defined monitored messages to CC&S, which forwards information to LOM. Stopping trace sends each CPU defined in active Monitoring profile the filter message with user defined task and empty monitoring messages field. LOM handles message tracing to different eNB System Components i.e. starts and stop filtering according filter messages received from Emil/CC&S. LOM sends trace data via CC&S managed TCP remote Aa Test port 15004 to Emil. BTS instances can be removed and edited by right mouse click. With right mouse click BTS can be connected, when it open BTS remote port and starts 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 version and tech report and pinged the BTS IP address for verifying connection. Connected BTS can be seen from connection status column, Data rate column reveals streamed data rate for connected CPUs. Double clicking connected BTS will open active monitoring profile parameters and traced data rates for each CPU. Settings are automatically saved in LteConn.dat file. 

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



Or by importing BTSs from .csv list by File -> Import new BTS list, .csv file 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

10 (60)


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 following rows the parameter values must be separated with “,”



Exit: Closes LTE Streaming window



Edit



View



Debug window: Opens debug dialog with a log of detailed Emil actions



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 parameter message according to active filter profile(s) to selected BTS(s)



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



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



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



Disable: Disable selected BTS(s) to ignore commands, even if they were 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 Site Manager fetched technical logs



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



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



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


11 (60)


 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 BTS list, where original BTS instances existed

 Remove

all but selected: Removes all but 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 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 …

12 (60)


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 only with limited amount of User load ->Start to ramp up the tracing gradually and newer start the tracing for whole E-UTRAN without first 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 Mbps tracing load. NOTE2! If monitoring profiles are missing some needed messages, inform Emil LTE Profile maintenance ([email protected]) and they will be added in the profiles for next Emil releases. NOTE3! Monitoring profiles will be separated in coming Emil release from LteConn.dat files, so that Emil installation will include default monitoring profiles and not overwrite BTS instances or user specific monitoring profiles.  View

accessed by File -> Connect LTE -> Monitoring Profiles

 Create

monitoring profile manually by right mouse click -> Add new profile…

 Or

create duplicate Monitoring profile from existing Monitoring profile and edit it

 Or

copy LteConn.dat file to Program files\Emil root and reload Emil (It will 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 by sending or receiving CPU. Sender marks traced messages, which are not traced anymore by receiver



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


13 (60)


 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 MsgTask 0x061A MsgTask 0x060A MsgTask 0x061C MsgTask 0x0620 MsgTask 0x0622 MsgTask 0x0623

[FSM_CTRL_MCU [FSM_1_FCM_BTSOM] [FSM_1_FCM_HWAPI] [FSM_1_FCM_LOM] [FSM_1_FCM_RROM] [FSM_1_FCM_ENBC] [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 connections view

 Right

mouse click commands

 Copy

row: Copies selected row

 Copy

column (Ctrl+C): Copies selected column

 Copy

cell: Copies selected cell

 Edit…:

Activates Monitoring profile edit dialog for setting Monitoring profile 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 is changed as Copy_[Profile_name]

 Remove

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

14 (60)


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 by replacing LteConn.dat file, where original Monitoring profile instances existed



Add new profile…: Creates new Monitoring profile instance with blank parameters

 Currently

implemented default monitoring profiles



CP+UP_Light (Default Profile): Raw Alarms, PM counters, Control Plane, Management Plane, Platform and User Plane messages related to Call or HO setup/releases procedures, cell and eNB states and configuration or general error or failure indications. In case more detailed UP information is needed for call failures, it can be verified from call failure TechReports. Profile causes low load if no user are present and can be used for longer time traces. This profile is the recommended default profile especially for bigger networks.



CP+UP_MeasRep: Includes CP+UP_Light (Default Profile) profile messages and UP Measurement report messages used for drawing graphs. Measurement reports are filtered so that they are sent at 1 s interval for cell and user. Profile creates load also when no users are present due to cell interference measurement reports. Profile is recommended, when traced eNB amount is limited and there exists enough tracing capacity both in E-UTRAN and Tracing PC platform, e.g. in SyVe and FiVe test, and early phase low load Trials and Pilots.



CP+UP_AckNack_MeasRep: Includes CP+UP_MeasRep profile messages and CP & UP PDU Ack Nack messages. Ack Nack messages are not filtered and are sent approx 50 ms interval per user -> Profile causes heavy load and is recommended to be used only for limited time testing periods for limited amount of eNBs, when Ack Nack information specifically is needed for troubleshooting purposes



Only RawAlarms: Includes only RawAlarm messages. Profile is light and can be used for large amount of eNBs for triggering purposes (when related trigger is implemented in future Emil profile version). e.g. when certain raw alarms precedes failure situation like FSP/eNB crash or call failure


15 (60)


 Only

PM Counters: Includes only PM counter messages. Profile is light and can be used for large amount of eNBs for drawing KPI graphs (when KPI graphs are implemented in future Emil profile version). In the future can be used also for triggering TechReports fetching and remote UDP print tracing

 Only

RawAlarms & PM Counters: Includes only PM counter messages. Profile is light and can be used for large amount of eNBs when both Raw Alarms and PM counters are wanted to be monitored at the same time.

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

16 (60)


Emil Views

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

File 

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



Connect to RNC…: RNC…: Opens new view for establishing RNC log traces



Connect to LTE BTSs…: BTSs…: Opens new view for creating eNB instances, establishing eNB log traces and performing BTS Manager actions



Close: Close: Closes all open logs and clears the trace grid



Recent files: files: Lists recently opened Emil files, which can be reopened



Recent directories: directories: Lists directories where files have been recently opened. Selecting directory will show directory file content to be opened



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



Edit 

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



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



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



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


17 (60)




Toggle Bookmark (Ctrl+F2): Marks or unmarks selected scenario row into bookmarks, background is changed to light green



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 next bookmark and selects it



Clear All Bookmarks: 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…: session…: Opens SSH-dialog for creating SSH connections to defined IP address.



Find messages in files (Ctrl+Shift+F): Opens Find messages in files dialog. Source files can be selected from directory or from already opened files in Emil. Update button will list available files and prints message name from sack information. Find button creates list of files and order, where selected message is traced. Message content can be opened by doubleclicking message.



File converter and splitter:



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



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



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

 Environment 

18 (60)

Change sack and profile (Ctrl+F5): Shows available sacks and profiles 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: Fields2.ini: Opens Fields2.ini C# source code in a new window. Fields2.ini is written by Emil maintenance for creating scenario columns content



Edit current Fields2User.ini: Fields2User.ini: Opens Fields2.ini C# source code in Emil editor for editing. Fields2User.ini allows Emil users to create additional scenario columns



Do profiling for trace scripts: scripts: Opens profiling dialog for fields2.ini and Fields2User.ini scripts, which prints how much each 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: SourceProfile.ini: Opens SourceProfile.ini C# source code in a new window. SourceProfile.ini is written by Emil maintenance for defining source file printable information, font and background color in source view



Edit current SourcePofileUser.ini: SourcePofileUser.ini: Opens SourceProfileUser.ini C# source code in Emil editor for editing. SourceProfileUser.ini allows Emil users to add additional information, font and background colours in source view



Do profiling for source scripts: scripts: Opens profiling dialog for SourceProfile2.ini and SourceProfileUser.ini scripts, which prints how much each message is using processing power in these trace scripts. Can be used, when the source information printing seems to be to heavy for the PC



Show current MessageView.ini: MessageView.ini: Opens MessageView.ini C# source code in a new window. MessageView.ini is written by Emil maintenance for defining Message User data content, font and background colour in Trace view



Edit current MessageViewUser.ini: 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 and background colours in Trace view



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


19 (60)


prints how much each message is using processing power in these message view scripts. Can be used, when opening the message view seems to be to heavy for the PC 

Show current DataDecoder.ini: Opens DataDecoder.ini C# source code in a new window. DataDecoder.ini is written by Emil maintenance for decoding messages that support encode/decode. Code must be written with C#, but external DLL:s written in other languages can be called. Not supported in Emil LTE profile



Edit current DataDecoderUser.ini: Opens DataDecoderUser.ini C# source code in Emil editor for editing. DataDecoderUser.ini allows Emil users to add additional decoders and encoders. Not supported in Emil LTE profile



Do profiling for data scripts: Opens profiling dialog for DataDecoder.ini and DataDecoderUser.ini scripts, which prints how much each message is using processing power in these data scripts. Not supported in Emil LTE profile



Show current AsciiDecoder.ini: Opens AsciiDecoder.ini C# source code in a new window. AsciiDecoder.ini is written by Emil maintenance for decoding Radio and Interface protocols. All ASCII decoders must be written in C# or the called for DLLs for decoders written in other languages. Currently external DLL based decoders are called for ASCII Decoding



Edit current AsciiDecoderUser.ini: Opens AsciiDecoderUser.ini C# source code in Emil editor for editing. AsciiDecoderUser.ini allows Emil users to add additional ASCII decoders



Do profiling for ASCII scripts: Opens profiling dialog for AsciiDecoder.ini and AsciiDecoderUser.ini scripts, which prints how much each message is using processing power in these decoding scripts. Can be used, when protocol decoding in message view seems to be too heavy for the PC. In tracing the DLL decoders can not be used, because they will cause Emil crash due to too extensive processer load



Explore the profile folder: Opens Windows explorer in active profile directory

 Filter 

20 (60)

Activate filters: Not supported in Emil LTE profile


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 color in 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, except main view




Help 

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



Content…: Opens Help dialogs search tab for browsing help content



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



About…: Prints used Emil version



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



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


21 (60)


 GC:

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

2.4.1 Options view Most of static Emil setup is done via Options view

22 (60)



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



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



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



Address to WWW-PDE: Link to parameter WWW data base, from where parameter descriptions can be checked in Message View. Not supported in Emil LTE version



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



Open files into "Message view" by default: Makes Emil function like IDA2 so that all logs that are opened are straight away opened in a Message by message window without any parsing. If parsing is later wanted for some specific log then Source->- >Parse source can 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 any calls, then the log is automatically opened into a Message view window, like IDA2. Any file can always be opened into a Message view


Emil Views

from Source->- >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 text editor window. Can be done for any file from Source->>Open as text. Not supported in Emil LTE profile



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



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



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



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 Emil LTE profile



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



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



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



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


23 (60)


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

2.4.2 Columns In many Emil views the information is printed into cell matrix, in where each column represents a specific information and data type. Column content 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

24 (60)


Emil Views

defined a value format, e.g. Boolean, MultiValue, Time or Integer. Right mouse click activates commands for columns; available commands depend on column properties. For detail column content see Emil view descriptions.



Secondary sort: Sorts scenario rows according to selected column value inside primary sort limits. Primary sort is performed by double clicking column name.



Hide: Hides columns from Scenario view



Count summary of values: Opens Summary view, in where is calculated statistics for select column values, like Sum, Min, Max and Average values



Summary: Opens Summary view, in where is calculated absolute and percentage 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 of numerical presentation


25 (60)




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 data types 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 column is 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 to selected column

Figure 5 Summary view, accessed by right mouse click on top of selected column -> 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 .ini scripts. Traces can be opened in message view by double-clicking the scenario.

26 (60)


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 releases typically are not tested as much and might be suffering from parser limitation in the beginning of development cycle 

TraceParser.ini 

Parses messages from each BTS trace separately for creating scenarios

 Each



message returns a value



All messages with same value are included in the same scenario line in 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 no longer active in the cell



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



Closing trace closes all scenario and starting trace for same BTS will create 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 be decoded for limited amount of messages in message view)

Fields2.ini 

Parses all messages inside one scenario for creating scenario information

 Defines

what columns are visible



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



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 be decoded for limited amount of messages in message view)


27 (60)


 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 related columns



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:  Trace

28 (60)

Scenario duration = Stop Time-Start Time

Type: Prints is the scenario type



Call: Scenario includes call related CP, DL UP and Protocol messages. UP measurement report messages can be used for drawing data graphs for user DL MSC, if UP messages are selected active in the monitoring profile



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



S1Paging & X2HoRequest: Scenario includes S1 Paging and Target cell X2 HandoverRequest messages. In future releases Target cell X2 HandoverRequest messages will be included in call scenarios



Cell UP: Scenario includes UL UP Measurement reports, which can be used for drawing data graphs for user UL MSC and cell interference, if UP messages are selected active in the monitoring profile



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



eNB CP: Scenario includes eNB related CP messages and rawalarms (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, when it is visible in signalling



MMEGI: Prints MME Group Id used in GUTI during call establishment, 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 ID value for identifying the UE during call establishment. Usually IMSI is not used by MME because security purposes. Depending MME setting the TMSI can be changed every time the UE establishes a new 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 Equipment Category

Maximum L1 datarate Downlink

Maximum number of DL MIMO layers

Maximum L1 datarate Uplink

Category Category Category Category Category

9.8 Mbits/s 48 Mbits/s 97 Mbits/s 143 Mbits/s 292 Mbits/s

1 2 2 2 4

4.9 Mbit/s 24 Mbit/s 48 Mbit/s 48 Mbit/s 71 Mbit/s

1 2 3 4 5



Max Agr DL: Prints UE maximum allowed average aggregated DL data rate in kbps received in InitialContextSetupRequest or HandoverRequest 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 UL data rate in kbps received in InitialContextSetupRequest or HandoverRequest 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 in BTS connections BTS list



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


29 (60)


 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 MME allocates one MME_APID for one UE, until the UE has been out of RRC connected state longer than the MME internal timer allows. This is the only feasible identifier to be used for tracing calls during mobility (TMSI or IMSI are not informed during HOs)

 Source

UeID/X2ID: Prints either UeID (Intra eNB HO) or X2ID (Intra eNB HO) of source cell during HO. Can be used aside the Ue_MME_APID for tracing calls during mobility. Note that UeID is unique 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 (Inter eNB HO) of target cell during HO. Can be used aside the Ue_MME_APID for tracing calls during mobility. Note that UeID is unique 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 System Component use CRNTI, UeID or both for identifying calls, in case more detailed call analysis from TechReports are needed

 UeID:

Prints UE Id for call scenarios. During Intra eNB HO UeId=Source UeID/X2ID. Note that UeID is unique only for one cell and has typically different value than CRNTI. From message parameters can be checked does a System Component use CRNTI, UeID or both for identifying calls, in case more detailed call analysis from TechReports are needed

 TMSI/MISN:

Prints UE S-TMSI value in Hex or MSIN value in decimal format depending what ID format MME is using, visible in Column 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

30 (60)


Emil Views

failures “Radiolink Failure”, “eNB Release”, “EPC release”, “No UE Messages” or “No EPC Messages”. See Triggers and colour descriptions 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 in RrcConnectionRequest message 

Emergency: UE sends RrcConnectionRequest for setting an emergency call with SRB and DRB. Emergency calls have highest priority



HighPriorityAccess: UE sends RrcConnectionRequest for setting a high priority call with SRB and DRB. High priority calls have higher priority than normal calls



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



mo-Signalling: UE sends RrcConnectionRequest for RRC setting a signalling link with SRB e.g. for Tracking Area Update or Attach procedure. Note that some UEs use mo-siganalling cause also when they setup a DRB for data transfer



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



S1 Rel Cause: Call release cause in S1AP MME intiated: UEContextReleaseCommand eNB initieated: InitialContextSetupFailure or UEContextReleaseRequest



Failure Phase: Prints in which phase of new Call establishment or HO 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 plane signalling)


31 (60)


 Errors:  First

Prints Error cause as defined in sack

RLs_Failure: Prints first active RL failure cause as defined in

sack  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 changed between active and cancelled. High number indicates poor signal conditions for the UE

 Preamble

sequence: Prints detected preambles sequence number during call establishment

 UL

Sync Time: Time it takes the BTS to get UL synchronization during HO, calculated as time difference between PDCP Enable and first detected RACH impulse response

 Target

Intra HO Prep Time: Time between received HandoverRequest and RrcConnectionReconfiguration signalling when UE enters cell by Intra eNB HO

 Target

Intra HO Access Time: Time between RrcConnectionReconfiguration and release source cell Ids (=ENBC_ID_DEALLOCATION_RESP_MSG) signalling when UE enters cell by Intra eNB HO

 Target

Inter HO Prep Time: Time between received HandoverRequest and RrcConnectionReconfiguration signalling when UE enters cell by Inter eNB HO

 Target

Inter HO Access Time: Time between RrcConnectionReconfiguration and release source cell Ids (=ENBC_ID_DEALLOCATION_RESP_MSG) signalling when UE enters cell by Inter eNB HO

 RRC

Setup Time: Time between RrcConnectionRequest and RrcConnectionSetupComplete signalling when a new call is established, i.e. how long it takes for the UE to establish a working RRC connection towards eNB

 RRC

Access Time: Time between RrcConnectionSetupComplete and InitialContextSetupRequest or RRC release signalling when a new call is established, i.e. how long it takes for the eNB to establish a working RRC connection towards EPC

32 (60)


Emil Views



RAB Setup Time: Time between InitialContextSetupRequest and RrcConnectionReconfiguratioComplete signalling when a new call is established, i.e. how long it takes for the eNB to establish a working RAB connection towards UE



RAB Access Time: Time between RrcConnectionReconfiguratioComplete and InitialContextSetupResponse signalling when a new call is established, i.e. how long it takes for the eNB to establish a working RAB connection towards EPC



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



Source Intra HO Prep Time: Time between sent HandoverRequest and received HandoverRequestAck signalling when UE exits cell by Intra eNB HO



Source Intra HO Access Time: Time between received HandoverRequestAck and call termination when UE exits cell by Intra eNB HO, i.e. how long it takes to perform HO execution + HO completion in source cell



Source Inter HO Prep Time: Time between sent HandoverRequest and received HandoverRequestAck signalling when UE exits cell by Inter eNB HO



Source Inter HO Access Time: Time between sent HandoverRequest and received HandoverRequestAck signalling when UE exits cell by Inter eNB HO, i.e. how long it takes to perform HO execution + HO completion in source cell



eNB Name: Same as eNB column value, column duplicated so that information is visible also for eNB CP and Cell UP/CP trace related columns



Cell Id: Same as Cell column value, column dublictaed so that information is visible also for eNB CP and Cell UP/CP trace related columns



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


33 (60)


 #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 during tracing (e.g. by user or blocking fault)

 #BTS

Start-up: Prints how many times BTS has been attempted to be 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 misinterpretation from interference

 DarkPink:

No UE Messages -> UE doesn’t reply to eNB RRC

messages  Red:

No EPC messages -> MME doesn’t reply to eNB S1AP messages

 Coral:

Radiolink Failure -> Call released due to Radiolink failures by

eNB  LightPink:

ECP Release -> Call released due to Radiolink failures by eNB (probably because UE has dropped and established a new call in another cell)

 OrangeRed:

eNB Release -> eNB releases call with UEContextReleaseRequest due to failures or errors detected by some of the eNB System Components

34 (60)


Emil Views







LighCoral: RAB Setup Failure -> eNB can not setup E-RAB according to InitialContextSetupRequest parameters and replies with InitialContextSetupFailure, e.g. because UE doesn’t reply to RrcConnectionReconfiguration 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 Radiolink failures don’t necessarily indicate faults in the network, if the call is not failed



Blue: Error is active for a Call trace, overwrites violet colour from Radiolink failure. Note that Errors don’t necessarily indicate faults in the 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 the Emil installation package


35 (60)




Right mouse click commands for scenarios

 Copy


 Copy


 Copy


 Remove

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

 Remove

all but selected: Removes all but selected trace row(s) from Scenario view. Removed Scenario row(s) can be returned to view 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) includes comments and bookmarks

 Save

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

 Save

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

 Save

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

36 (60)


Emil Views



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



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

2.6 Source view Source view is included in Main view. It shows the files and their content used for parsing the scenarios by TraceParser.ini and Fields2.ini. On-line (.emil file) trace files are opened automatically for each traced BTS separately. In Off-line analysis easiest way is to drag and drop the folder, where .emil (Emil recorded or saved trace) or .bin (BTSLog recorded trace) files exist. Emil will ignore irrelevant files, like .zip, .mpg, .exe. Double clicking source file will open the traced messages in a new Message 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 next available 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 row: Copies selected row



Copy column: Copies selected column



Copy cell: Copies selected cell


37 (60)


 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 and comments

 Parse/Reparse:

Parses source files according to TraceParser.ini

code  Delete:

Deletes selected source file(s) from hard disk

 Message

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

window  Convert

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

 Find

messages: Opens Find messages in files dialog. Source files can be selected from directory or from already opened files in Emil. Update button will list available files and prints message name from sack information. Find button creates list of files and order, where selected message is traced. Message content can be opened by double-clicking message

 Open

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

 Find:

Opens Find-dialog for finding matches from scenario 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 word and selects all those rows. Bookmark searches for all occurrences of the specified search word and bookmarks all those rows

38 (60)


Emil Views

Figure 6 Main view, including Scenario and Soure views. Light green row is bookmarked and with right mouse click are opened additional commands for editing, saving or opening the scenario in either Trace view or message view

2.7 Message view Message view is used for analyzing traced messages and their parameters and possible protocol content. Message view can be accessed by double clicking scenario or source in main view (if Message view is selected as default view in Options) or by right mouse click. Active message is indicated with Dark blue back ground NOTE! Currently traces can be opened into message view only in off-line mode 

Upper bar commands 

File


39 (60)




Stop:



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



Save: Saves selected open scenario as [Trace id].emil file to source file directory. Saved file includes comments and bookmarks



Save as…: Saves open trace as .emil format with user defined name 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 from scenario 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 word and selects all those rows. Bookmark searches for all occurrences of the specified search word and bookmarks all those rows



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



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



Toggle Bookmark (Ctrl+F2): Marks or unmarks selected scenario row into bookmarks, background is changed to light green



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 next bookmark and selects it



Clear All Bookmarks: Clears all created bookmarks in the view

 Columns 

40 (60)

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 color in Message view



Show: Returns hidden column back into view

View 

Auto row height:



Message tree: Shows for selected message Parameter and Protocol views



Graphs: Shows available graphs created in Graphs.ini and GraphsUser.ini files and adds selected graphs view to Message view

Memory Monitoring 

Automatically activate: Not yet supported in Emil LTE profile



Filter Memory Monitoring Messages: Not yet supported in Emil 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 LTE profile

Tools 

Reload MessageView.ini files: Reloads MessageView.ini and MessageViewUser.ini files, e.g. when .ini file content has been changed



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 and background colors in Trace view



Show MessageView.ini: Opens MessageView.ini C# source code in a new window. MessageView.ini is written by Emil maintenance for defining Message User data content, font and background color in Trace view



Reload Graphs.ini files: Reloads MessageView.ini and MessageViewUser.ini files, e.g. when .ini file content has been changed


41 (60)




Edit GraphsUser.ini: Opens GraphsUser.ini C# source code in Emil editor for editing. MessageUser.ini allows Emil users to add additional info user data info, font and background colors in Trace view



Show GraphsView.ini: Opens Graphs.ini C# source code in a new window. Graphs.ini is written by Emil maintenance for defining what kinds of graphs are printed from traced message content

 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 for defining Message User data content, font and background color in Trace view by Emil maintenance



Edit current 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 and background colors in Trace view

 Window 

Rename form: Enables user to rename the window for identifying opened scenario, e.g. “Radiolink failure CRNTI 56428”

 Help  

Content: Shows Help dialog

Right mouse click commands  Copy


 Copy


 Copy

column: Copies selected column

 Remove

selected: Removes selected trace row(s) from Scenario view. Removed Scenario row(s) can be returned to view by reloading profile (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 to view by reloading profile (F5) or MessageView.ini files

42 (60)


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 in Message view



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



Messages by selected Time: Opens all messages from selected source(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 source scenario 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 by MessageView.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. CPU names 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. CPU names are not yet implemented in Emil LTE profile


43 (60)


 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. This time 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 following order messages in scenario or source

 Comment:  Length:  SFN: 

User manually added comment

Message Length in bytes read from traced message header

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:  Coral: 

TUPC_L3X2 message including L3X2 protocol content

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 and their values. Parameters can be pointed in .ini file code based on their name, Hex/Dec value, byte value, byte offset, constant value, data type and length. 

Parameter fields  Name:

44 (60)

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

Right mouse click commands 

Copy path: Copies selected child parameter name and related main parameter name(s) separared with a comma for creating explicit path pointer. E.g. parameter “board” is pointing to both receiver and sender 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 for WWW-PDE pages defined in options settings. Not supported in Emil LTE version


45 (60)


 Copy


 Copy


 Copy


 Show

as ASCII: Opens parameter data value in Emil editor as ASCII characters

 Show

as other data type: Opens dialog for presenting parameter

data

 Show

as decimals: Opens parameter data value in Emil editor as decimals, 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 bytes separated with space

 Show

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

 Show

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

 Show

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

 Show

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

46 (60)


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 and adds 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 of parameter view. Note: Protocol decoders are too heavy to be used in trace parser .ini files, thus Protocol content can be used by decoders only when messages are opened via message view. 

RRC: Prints RRC protocol content in ASN1 format from TUP_SRB message payload content using external dll based decoder files. See 3GPP 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. See 3GPP TS 36.413 S1 Application Protocol (S1AP) for protocol details



X2AP: Prints S1AP protocol content in ASN1 format from TUPC_L3X2 message payload content using external dll based decoder files. See 3GPP 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


47 (60)


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 bottom of 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. It is accessed by clicking View -> Graphs in Message view or Sequence view icon in Trace view. Available Graphs are defined by Emil maintenance in Grahps.ini file or by Emil users in GraphsUser.ini file. Graph can be zoomed and location changed in both X and Y axis direction by pressing left mouse button on top of the arrow icons and moving the mouse at the same time on X or Y axis direction. NOTE! Currently Graphs are defined only from RL10. With default UP monitoring profile measurement report samples are received as one

48 (60)


Emil Views

second snapshot interval, i.e. peak snapshot results may give wrong expression about average value since graph results are not average but one sample snapshot values 

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

Cell UP_UL Signal Strength: Draws cell interference calculated from 20 PRB distance samples and user RSSI marked with CRNTI identifier.



Cell UP_Cell UL MCS: Draws from Cell UP trace UL cell PRB consumption, data rate, average modulation and amount of scheduled users per TTI



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



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



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



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


49 (60)


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

2.8 Trace view Trace view is used for enabling Scenario/trace message analysis through multiple parallel views in same window Trace view window. Different sub views are L3 analyzer, Message view, Sequence view and Graphs view. These views can be added from Trace view icons. Clicking a message active in one view also activates the same message in other views Note! Currently traces can be opened into Trace view only in off-line mode 

Upper bar commands  File

50 (60)


Emil Views







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



Save: Saves selected open scenario/trace as [Trace id].emil file to source file directory. Saved file includes comments and bookmarks



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



Save as HTML…: Saves L3 view as HTML format



Save as CSV…: Saves trace content as .csv file

View 

Message view: Adds Message view to Trace view. Functionality is similar as in separate message view window



L3 Analyzer: Adds L3 Analyzer view to Trace view



Graphs: Shows available graphs created in Graphs.ini and GraphsUser.ini files and adds selected graphs view to Trace view

Window 


 When

message view is active, also message view commands: Edit, Columns, View, Memory Monitoring, Tools, Window, Help



Icon bar commands 

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



Send as mail attachment: Opens outlook mail with trace messages attached as .emil file



L3 Analyzer: Adds L3 Analyzer view to Trace view



Message view: Adds Message view to Trace view. Functionality is similar as in separate message view window



Sequence view: Adds Sequence view to Trace View.



Graphs: Shows available graphs created in Graphs.ini and GraphsUser.ini files and adds selected graphs view to Trace view


51 (60)


2.8.1 Sequence view Sequence view displays scenario message flow based on sender and receiver board and CPU information. Board and CPU Ids will be displayed also as names, like FSP1 and Faraday1 Core1, in the future. It is accessed by clicking Sequence view icon in Trace view

Figure 9 Sequence view, accessed by double clicking scenario in main view and then sequence view icon (if Trace view is selected as default view in Options) or by right mouse click -> Trace view and then sequence view icon

52 (60)


Emil Views

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

Figure 10 L3 analyzer view on bottom of Trace view, accessed by double clicking scenario in main view and then L3 analyzer view icon (if Trace view is selected as default view in Options) or by right mouse click -> Trace view and then L3 analyzer view icon

2.9 Call statistics view Will be implemented later


53 (60)


3

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

54 (60)



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



AsciiDecodersUser.ini: Emil users can ad additional functionality for ASCII 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 and information inside the column cells are printed in Main view for scenarios parsed by TraceParser.ini file



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



Graphs.ini: Defines what graphs can be drown when a scenario is opened 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 colours and information inside the column cells are printed in Message view



MessageViewUser.ini: Emil users can ad additional columns in Message view and print additional information to fields2.ini defined columns



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 into scenarios by returning a trace id for captured messages. Each eNB trace stream is handled as an own trace entity. Messages with same trace id are included in same scenario


55 (60)


4

Emil IDA2 Tool Env Sack files The sack team produces aside the Sack tags also Test tool Sack env folder, which has the message definitions used by IDA2 and Emil test tools. The folder is also referred as IDA2 sack. Test Env sack includes Types.dat file, which defines Message Names, Messages Id, Message parameters and names, Parameter lengths, Parameter constants and Parameter data types. Currently there is no support for dynamic parameters, e.g. payload parameters for Protocol content, and the dynamic parameters are not visible for most part in Emil Message view. Sack definitions can be checked from Emil parameter functions located in Column and Message view commands. Or then directly by opening Types.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 from [email protected]

56 (60)


Appendix

Appendix


57 (60)


References

58 (60)


Glossary

Glossary


59 (60)

Emil LTE Profile User Manual I

Recommend Documents