Вы находитесь на странице: 1из 35

R&S ROMES 4.

65 New Features

R&S ROMES Coverage Measurement Software


Order-No. 1117.6885.04

New Features of ROMES 4.65 1 1 2 3 4 5 CONTENTS

Contents

09/12/2011

6 7 8 9

Introduction ........................................................................................................................ 3 Installation.......................................................................................................................... 4 BCH Views ........................................................................................................................ 5 Layer 3 View...................................................................................................................... 5 LTE Scanner....................................................................................................................... 7 5.1 Wideband and MIMO Measurements.......................................................................... 8 5.1.1 Driver Configuration .......................................................................................... 8 5.1.2 Signals and Events............................................................................................ 13 5.1.3 Views ................................................................................................................ 13 5.1.4 File Information ................................................................................................ 15 5.2 LTE Scanner Channel Impulse Response Raw Export.............................................. 16 5.3 LTE Scanner Raw Export .......................................................................................... 21 GSM NWS Driver............................................................................................................ 22 UMTS PNS Driver ........................................................................................................... 23 TETRA Scanner ............................................................................................................... 23 8.1 Driver ......................................................................................................................... 23 8.2 ROMES Signals ......................................................................................................... 25 KPI Generator .................................................................................................................. 26 9.1 Introduction ................................................................................................................ 26 9.2 KPI Definition Files ................................................................................................... 26 9.2.1 Trigger Point Definitions.................................................................................. 28 9.2.2 KPI Definitions / KPI Export Definition .......................................................... 28 9.3 Views ......................................................................................................................... 28 9.3.1 KPI Generator View ......................................................................................... 28 9.3.2 KPI Export Result View ................................................................................... 30 9.4 Currently Supported Technologies ............................................................................ 31 9.5 Limitation of the current version................................................................................ 33 9.5.1 DQA Sessions only........................................................................................... 33 9.5.2 Multiple Services in one DQA Session ............................................................ 33 9.5.3 Generic RAT Trigger Points............................................................................. 33 9.5.4 Merger / Splitter................................................................................................ 33 9.5.5 Switching Measurement Mode ......................................................................... 33 9.6 Compatibility / Differences to earlier Versions ......................................................... 34 9.6.1 General.............................................................................................................. 34 9.6.2 ROMES Signals................................................................................................ 34 9.6.3 DQA.................................................................................................................. 34 9.6.3.1 All Jobs ............................................................................................................. 34 9.6.3.2 DQA Job HTTP with IE / WEB2.0 .................................................................. 34 9.6.3.3 DQA Job FTP Multi ......................................................................................... 34 9.6.3.4 DQA Job FTP Download / Upload................................................................... 34 9.6.3.5 KPI First Round Trip Time............................................................................... 35

page ii of 35

New Features of ROMES 4.65

December 2011

1 Introduction
A lot of improvements and enhancements of existing features have been included in the recent release of ROMES 4.65. The table below summarizes the most important features and their benefits. Feature New Installation wizard Export of BTS lists from BCH view Detail filter for L3 view LTE Scanner Wideband measurements LTE Scanner MIMO measurements LTE channel impulse response export Automatic channel selection for GSM NWS Higher measurement rate for UMTS in High Dynamic Mode Benefit Easy installation and guideline where to find useful documents on the ROMESDVD When new BTSs have been found by the Position Estimator, resulting BTS lists can be generated easily. Any details from the decoded L3 messages can be searched for easily. Any interferences on the band edges can be detected now by scanner measurements. Additional measurement parameters allow a much better interpretation of measurement results. The correlation between different MIMO paths can be measured to check if MIMO should work or not. Easy troubleshooting in terms of MIMO and low data rates. LTE channel impulse responses can be exported with a higher measurement rate now. Useful for driving channel and fading emulators. If only one or few operators should be measured, the relevant channels can be selected easily from the BTS list. Now up to 12 measurements/sec in UMTS and High Dynamic Mode are possible with TSMU, TSML and TSMQ. This means more dynamic and more measurements. Section 2 3 4 5.1

5.1

5.3

TETRA scanner faster By selecting different measurement methods, the user and more sensitive may select between faster or more sensitive TETRA measurements. Customized KPI generator

Beside the standard ETSI KPIs the user can define own 9 KPIs to be measured. Measurement and KPI Calculation are independent from each other which gives more flexibility.

Order-No. 1117.6885.04

page 3 of 35

New Features of ROMES 4.65

December 2011

2 Installation
A new installation wizard has been added to the ROMES DVD. The wizard contains links to documents, web sites and installers for ROMES and related utilities. With autorun enabled, the wizard starts automatically after mounting the DVD into the DVD drive. If autorun is not enabled, you can start the wizard by double clicking on the file start.hta in the root directory of the DVD. The wizard needs the MS Internet Explorer to be installed on the PC.

Note:

The directory structure of the DVD has changed since ROMES 4.63. The installer for ROMES setup.exe has been moved to the subdirectory ROMES and has been renamed to e,g, ROMES_setup-04-65.exe. It will contain the version number in the file name from now on. page 4 of 35

Order-No. 1117.6885.04

New Features of ROMES 4.65

December 2011

3 BCH Views
BCH Views for all technologies can now export the database file (produced by the ROMES Position Estimator ROMES4LOC) automatically after a measurement was finished. To do so, check the corresponding check box in the Export dialog of any technology. Note: the settings are stored in the registry and valid for all technologies. The automatic export is done with the parameters as specified in the Base Station Export dialog. However, it is done always separately for the technologies, so that the check box Export All Technology is ignored for the automatic export. The export dialog offers now also the possibility to store the settings without creating an export by pressing the Save & Close button.

The output view informs about the executed exports of BCH Views:

4 Layer 3 View
It is now possible to move elements from the Details Window directly into the Layer 3 View by Drag&Drop. The view automatically enables the details filter and adds the corresponding filter. The filter is the selected item in the details tree. The right part of the text will be removed until the first space or (, whatever is more to the left hand side. The details have a light yellow background by default.

Order-No. 1117.6885.04

page 5 of 35

New Features of ROMES 4.65 The selected Details can be removed by the Context Menu of the View.

December 2011

The Context Menu Remove Detail Filter only appears, if the mouse cursor is over a detail item and the Detail Filter is activated in the configuration. If you select this menu item ROMES checks the currently active detail filters. If only one is matching the selected detail item, it will be removed automatically. If more filters are matching the Details Filter Dialog opens the matching detail items are preselected - and the user has to remove manually the corresponding detail item.

Note: The items can be edited in the list now. The view has got also a new configuration item which allows the user to enable and disable the automatic view refreshment whenever the configuration concerning filters or mark ups has Order-No. 1117.6885.04 page 6 of 35

New Features of ROMES 4.65

December 2011

been changed. The button on the left upper corner and a context menu are available to trigger the refresh view process at any time. Whenever it is necessary to initiate a refresh view process e.g. the automatic refresh is disabled and a detail item was dropped onto the view, the icon gets an exclamation mark.

Press the button and the view will be refreshed and the exclamation mark will disappear.

The behaviour of the details window has been improved. The window now gets invisible if the corresponding Layer 3 Message List gets invisible (by selecting another device or another sheet), unless the window is pinned.

5 LTE Scanner
The R&S LTE Scanner now supports wideband and MIMO measurements for LTE FDD. Note: For TD-LTE these measurements will be released in a later ROMES version. The configuration is done in the drivers configurations dialogs, which were extended. New views, adapted views and new signals can be used to visualize the new measurement data. Order-No. 1117.6885.04 page 7 of 35

New Features of ROMES 4.65

December 2011

5.1 Wideband and MIMO Measurements


5.1.1 Driver Configuration
The layout of the channel table changed slightly. An additional column Measurement was added. The user can select the desired measurements by opening the combo box and checking the corresponding check boxes. Note: MIMO requires the corresponding option TSMW-K30 on the connected TSMW.

For most standard measurement applications the default values are perfect. However, if the user wishes to adapt them, this can be done by opening the advanced configuration pages. Three pages allow the user to fine tune the measurement task: Note: The driver has to be associated to both front ends in order to measure values on Rx2 or MIMO. Advanced Options: Details for narrow band measurement Wideband Measurements: Details of the configuration for wideband measurements MIMO Measurements: Details of the configuration for MIMO measurements

Order-No. 1117.6885.04

page 8 of 35

New Features of ROMES 4.65

December 2011

Wideband (WB) Measurements settings (default values) Average Speed(1): the measurement speed of WB measurements is slower than narrowband (NB) measurements. Maximum is 2.0 meas./sec. Length of the signal that is captured to perform the WB measurements RSRP, RS-SINR and MIMO. If the length is increased, e.g. averaging over a longer period of time for RSSI is performed. For RS-CINR more accumulations of time sections improve the RS-CINR accuracy for weak cells. The default of 50ms is a good balance between accuracy and short enough to reduce impact on receiver resources. If configured for one measurement per second per channel, the scanner will use 50/1000*100% = 5% of the receiver resources. The longer the requests are, the less measurements can be done on other technologies or frequencies in parallel. Bandwidth(Auto): The bandwidth of the LTE band to be measured. It can be detected by decoding the bandwidth from the MIB (must be activated in the BCH-Demod. Settings, near the frequency selection). If an automatic detection is not page 9 of 35

Length of Signal(50):

Order-No. 1117.6885.04

New Features of ROMES 4.65

December 2011 possible or desired (e.g. because of a weak signal), it can be set the corresponding value manually.

Channel Model(4/100):

The parameters for the channel model set the maximum delay spread (time difference of arrival of the different paths of one signal) and the maximum expected mobile speed that can be expected during the drive. The larger these values, the longer the computation time for RSCINR. If the maximum delay spread or the speed is bigger than set, the measurement results accuracy will be degraded or the results even gets wrong.

RSSI Measurement Time(50): The time that is used to collect samples for measuring the RSSI. It must be shorter or equal than length of signal above. It may be selected shorter than the time for the WB measurements to have more variation in the result, e.g. for a lightly loaded cell. If it is equal, more data is averaged (i.e. less variance in the measurement result). If yes and more than one frontend is used, the RSSI power and spectrum power of both frontends will be averaged (in Watt, power combining). If no, the values for each frontend will be measured separately. Selects which frontend(s) is/are used for RSSI and spectrum measurements. It also shows the assignment of names (FE1=Rx0 and FE2=Rx1) in the LTE Scanner Subband View. Normal is always selected for LTE FDD. For TDD, normal means that measurements are performed all the time, i.e. during uplink and downlink period, while TDD UL or TDD DL may be selected for the single periods, respectively. The number of resource blocks (RBs) used for RS-SINR calculation. For LTE FDD 1 is recommended. For TDLTE with a low number of DL RBs the accuracy may improve, if a value of >1 is set. If this number of RBs is not a divider of the total number of RBs then a gap in the middle of the subbands remains and includes the DC carrier. The maximum number of RBs to be selected is 5. page 10 of 35

Average(No):

Frontends(FE1;FE2):

Mode(Normal):

RS-SNIR measurement Min. number of RBs(1):

Order-No. 1117.6885.04

New Features of ROMES 4.65 Force no gap(Yes):

December 2011 Set to yes to avoid the gap mentioned under min. number of RBs above. A larger subband is calculated to realize this. With no, the gap occurs. Defines the minimum number of Reference Symbols (RS) used to measure RS-SINR. Increasing the number improves the maximum possible accuracy, however more computation time is required and measuring very high RS-SINRs is more difficult. Valid numbers between 20 and 200, recommended 80 for FDD and 120 for TDD. This value gives the number of captured data sequences that are used to calculate the RS-SINR. If more reference symbols in these sequences are available than required for calculating the RS-SINR, these can be accumulated. The more sequences are accumulated, the higher the measurement accuracy (due to reduced noise and interference), however calculation time increases. Values from 1 to 20. Example: For FDD the default of 1 resource block per subband and 80 reference symbols, there is no extra data for any accumulation (accumulation count is 0). If 2 resource blocks per subband and 80 reference symbols, then 1 accumulation is possible. Selects which frontend(s) is/are used for RS-SINR and RSRP/Q measurements. It also shows the assignment of names (FE1=Rx0 and FE2=Rx1) in the LTE Scanner Subband View. Selects, which TX antenna ports of the eNodeB are used to measure RS-SINR.

Min. number of RSs(80):

Max Accumulations(4):

Frontends(FE1;FE2):

TX-Antennas(0-3):

The following four parameters may be changed to get a compromise between a higher measurements rate and more accurate measurements or measurements under worse radio conditions (weak signal etc.): Max. eNodeBs(5): Min. RSRP(-130): Min. SSS SINR(1): The maximum number for how many eNodeBs on one frequency the RS-SINR measurement should be done. The minimum NB RSRP from which RS-SINR measurements should be done. The minimum NB S-SYNC SINR from which RS-SINR measurements should be done.

Max. Delta RSRP best cell(10):The maximum delta between the NB RSRP of the currently measured cell and the NB RSRP of the cell received best, from which RS-SINR measurements should be done. Order-No. 1117.6885.04 page 11 of 35

New Features of ROMES 4.65

December 2011

MIMO measurements Mode(2x2): 2x2 results: MIMO mode, currently only 2x2 is supported. Matrix: MIMO channel matrix (H-matrix) Condition number(CN): condition number for the Hmatrix Rank: theoretical rank of the H-matrix compared to a minimum SINR of a specified rank. Resolution: The MIMO measurements are calculated per resource block at a given time position within the captured data. This parameter defines the time interval between MIMO measurements within the captured data. For example, in the case that 50 ms of data are captured and the time resolution is 5 ms, the MIMO results are calculated up to 10 times and returned. For TDD the time resolution has to be a multiple of 10ms LTE frame duration. A value of 0 is used to calculate just one MIMO result per acquisition. This value must be less or equal the measurement time of the WB measurements above.

Order-No. 1117.6885.04

page 12 of 35

New Features of ROMES 4.65

December 2011

5.1.2 Signals and Events


A bunch of new signals and events were implemented for wideband and MIMO measurements. Where applicable signals are available separately for each tx-antenna/rxantenna combination. Antenna combinations are identified by the appendix (tx/rx). TX here means the TX antenna of the eNodeB, RX means the RX antenna of the TSMW. MIMO signals are currently available for the 2x2 antenna configuration. For numeric signals events were defined. Note: The signal WB Subband SINR allows to display or export the complete subband values. The signal #Outliers gives the number of outliers within the subband values. The signal Outliers displays the position and values of outliers within the subband values.

5.1.3 Views
5.1.3.1 LTE Scanner Subband View This new view works analogue to the already known LTE Scanner Cell ID Tracer View. The view shows the measured subband SINR values of one cell. The cell can be specified either by a physical cell id or a certain TopN Member. The upper bar allows the user to choose the LTE channel, the zoom factor and the combinations of tx and rx antennas, which shall be displayed.

The view displays the SINR value of the measured block in colour. The selected antenna combinations are displayed side by side. A tool tip shows detailed information about the point below the mouse cursor. Active and passive coupled focus is supported. Example: in case the LTE scanner RX1 antenna was faulty, the two columns RX1/TX1 and RX1/TX2 would show rather bad (=red) SINR values. Similarly, defect eNodeB antennas could be determined. Also its visible, if in a rather empty band any traffic is ongoing, and on which subbands it has been assigned. Order-No. 1117.6885.04 page 13 of 35

New Features of ROMES 4.65

December 2011

5.1.3.2 LTE Scanner MIMO View The MIMO view displays the colour-coded Condition Numbers per transmitted Resource Block. The view shows the measured Condition Numbers of one cell. The cell can be specified either by a physical cell id or a certain TopN Member. Each line represent one measurement over all resource blocks. One to n measurements are done by evaluating a IQ data block. A IQ data block is x seconds, concerning what is configured as measurement speed in the Wideband Configuration Page of the scanner. N depends on the length of Measurement Signal and the MIMO Measurement Resolution. The default values are 50ms for the length of signal and 10ms for the resolution, which results in 4 measurements per IQ block. The view can show the condition numbers for the 2x2 MIMO configuration. A cursor displays details of the pixels. Active and passive coupled focus is supported.

The lower part is a presentation of the H-Matrix. The graph shows the Condition Number and the elements of the Matrix HH*H per resource block. During the measurement and replay, the H-Matrix of the last measurement is displayed. When using the cursor in the waterfall diagram, the graph of the H-Matrix will be updated. 5.1.3.3 LTE Scanner TopN View The default layout of the TopN View has been changed to the following:

Order-No. 1117.6885.04

page 14 of 35

New Features of ROMES 4.65

December 2011

However, the user still can enable all columns which were shown by default in earlier versions. The wideband columns show the maximum values of all antennas or antenna combinations. The display antenna / combination is given in parentheses. E.g. a WB RSSI of 95.8 (2) means, that on antenna 2 this RSSI value of -95,8 dBm was measured, and that the RSSI value of antenna 1 is less or equal -95.8 dBm. The bar chart was extended to show the wideband values, if available. In this case for each cell Power/RSSI and SINR/WB-SINR is displayed. The narrow band values are displayed in the exact colour of the cell. The colour of the columns for the wideband values differs slightly from the default colour. On the left side the bars show: RSSI Rx1, Narrow Band Power, RSSI Rx2 The right bar cluster shows: SINR Rx1:Tx1, SINR Rx1:Tx2, Narrow Band SINR, SINR Rx2:Tx1, SINR Rx2:Tx2

5.1.4 File Information


The file information shows, if a wideband and/or a MIMO measurement was done.

Order-No. 1117.6885.04

page 15 of 35

New Features of ROMES 4.65

December 2011

5.2 LTE Scanner Channel Impulse Response Raw Export


The LTE Scanner CIR View now can export the raw channel impulse responses, which means one CIR per up to every 5ms.

Note: This export does not depend on the update rate of the lists. All data will be exported. The reconstruction of the spectral Channel Impulse Response is done as follows: The fading channel is measured as an amount of single paths. Each path has an amplitude a(i)=sqrt(p(i)), phase phi(i), doppler frequency fd(i) and a delay tau(i). The CIR is measured on a bandwidth of 1.08MHz and a 95ms long IQ data block, which starts at Tcir. In this block the LTE frame starts at the time tau_min (minimum of the delays of all peaks), thus the temporal relation of the position of the reference symbols is given implicitly. The reconstruction is done for each transmit antenna (Port 0,..,Port3) separately, because the transmit channels are different. The reconstruction of the 12*6=72 resource elements r(t,k*15kHz) {k=-36...-1,1,...,36} is the impulse response in spectral range at time t for the bandwidth of 1.08MHz, which is given as TransferFunction. An IQ Block normally has a length of 100ms, which results in (100ms / 5ms) - 1 = 19 TransferFunctions. Note: It is important to know, that the phases of the exported results are only in relation to each other within one exported IQ block, called Single Measurement. The CIRs are exported into an XML file with the name <RSCMDfilename>_LTE_CIR_Raw.xml, which is created in the ExportResult directory.

Order-No. 1117.6885.04

page 16 of 35

New Features of ROMES 4.65

December 2011

The XML file will be written and closed whenever the replay was stopped. The XML file has the following tags and attributes: ScannerResult: Measurement_Time_s: Receiver_Time_s: Device: SpectralCIR: Port: PortNumber: CountOfTransferFuntions: TransferFunction: TransferFunctionNumber: Receiver_Time_s: Point: Power_dBm: Arg_Radiant: Server: PCI: Order-No. 1117.6885.04 A bunch of measurement results reported by the scanner start time of the measurement in seconds from start of the measurement (PC time) receiver internal start time of the measurement in seconds id of the ROMES receiver device driver Spectral Channel Impulse Response Antenna Port number of the port 0..3 number of transfer function for this single measurement on this port 0..19 transfer function as explained above number of the transfer function 0..19 receiver internal time for the transfer function in seconds point of the transfer function power in dBm phase in radiant a LTE eNodeB Physical Cell Identity page 17 of 35

New Features of ROMES 4.65 NumberOfSymbolsPerSlot: 7 for normal CP, 6 for extended CP SSSToPSSRatioInDB:

December 2011

measured power ratio power(SSS)/power(PSS) in dB LTE Scanner Signals due to observation of the arrival time of the strongest BS signals we can calculate an expected time drift against the receiver time.

ExpectedTimeDriftInNsPerSec:

SigmaTimeDriftInNsPerSec: expected standard deviation of the value above. CenterRSRPinDBm: Gives the RSRP value based on the reference signal power measurement of the 6 innermost resource blocks. (1MHz BW around center frequency at symbols used for the PBCH). It is a combination of noise clipping and non noise clipping results. (See the explanation for the OfdmBased and the CirBased values) RSRQ value based on CenterRSRPinDBm and the total inband power in resource blocks used to transmit the PBCH within the 100 ms IQ data block analyzed with the scanner. number of resource elements used for RSRP measurement. OfdmBasedCenterRSRPinDBm100: Gives the RSRP value based on the reference signal power measurement of the 6 innermost resource blocks. (1MHz BW around center frequency at symbols used for the PBCH). The power measurement is done from the OFDM symbol without clipping of noise. CirBasedCenterRSRPinDBm100: Gives the RSRP value based on the reference signal power measurement based on CIR measurement and noise clipping of the 6 innermost resource blocks. (1MHz BW around center frequency) at symbols used for the PBCH. PowerValues: PowerValue: Measured power of signal One power value

PBCHbasedRSRQinDB:

CntResourceElementsForRSRP:

TimeFromStartOfBlockInNs: Time in ns of the first IQ value for the SSS power measurement from the IQ block start. This is normally within the CP of the OFDM symbol containing the SSS. Order-No. 1117.6885.04 page 18 of 35

New Features of ROMES 4.65

December 2011 In the case that not a single symbol has been used the value is reported.

PowerInDBm:

Power of SSS signal in dBm. The PSS power may be retrieved indirect using the measured SSS / PSS power ratio. If TimeFromStartOfBlockInNs is not reported then the power is measured for 19..20 SSS OFDM Symbols (calculated from the CIR). If we have a valid time value than the power is measured for one SSS symbol only. CINR value in dB for the sync signals. If TimeFromStartOfBlockInNs is not reported then the CINR is measured for 19..20 S-Sync OFDM Symbols (calculated from the CIR). If we have valid values in CinrDetails for S-Sync and P-Sync than this is the average of P-SYNC and S-SYNC but if in CinrDetail only S-Sync CINR is valid than this is the S-Sync CINR. For details see CinrDetailTable which is parallel to this record. CINR of the PSS in dB CINR of the SSS in dB

CinrDB:

CinrPSyncInDB: CinrSSyncInDB:

AmpBasedCinrPSyncInDB: CINR of the PSS in dB based on amplitude noise. The measurement performed for this result value reduces noise contributes produced by transmitter or receiver phase noise. If either receiver or transmitter phase noise contributes are not neglectable then the amplitude based CINR is higher than the CINR based on the regular CINR measurement. Using a TSMW as receiver with low phase noise contributes limiting the regular CINR measurement to a value typically higher than 40dB a high transmitter phase noise is indicated when the amplitude based CINR value is permanent significantly higher (> 3dB) than the regular CINR value and both values are lower than 40dB. AmpBasedCinrSSyncInDB: CINR of the SSS in dB based on amplitude noise. CIR_PowerDelay: PowerDelayProfile: SamplingTimeInSec: InbandPowerInDBm: Channel Impulse Response and Power Delay Power Delay Profile Sampling time or time distance between CIR samples. Inband power during the CIR measurement in dBm. The inband power is measured within the same band or frequency range and one or more time intervals as occupied by a special transmitted signal sequence which is used to calculate the CIR. For example, in LTE up to page 19 of 35

Order-No. 1117.6885.04

New Features of ROMES 4.65

December 2011 20 SSS signals are used to calculate the CIR and the power delay profile. Each SSS Signal is defined by 62 subcarriers which define the band or frequency range for the inband power measurement and the symbol time slots of the 20 SSS signals define the used time intervals. So the minimum value of the inband power measurement is the aggregate power of all components in the power delay profile. If no interference signal is present, both aggregate power and inband power are equal, measurement errors neglected.

AggregatePowerInDBm:

Received power from all paths in dBm. Note that this is not necessary the peak power son or the sum of the power values in the power delay profile. Due to higher resolution in time delays and doppler frequency with respect to the measured bandwidth and length of the analyzed signal the value is different. The aggregate power is defined a the RMS power of the used signals (e.g. SSS or reference signal for LTE) of all signals used to calculate the CIR. It corresponds to the same section as the inband power. In some cases the aggregate power may be higher than the inband power. This is when noise contributes will disturb the algorithm is a way, that the reconstructed signals have a higher power than the actually received signals. this is an estimated noise floor for the CIR. Reported values below or next to the noise floor are caused or significantly influenced by noise. Point of the Power Delay Profile Here the time discrete power values (power samples) of the power delay profile in dBm are reported. Some power values may not have a valid value. At the corresponding delays the power measurement was not done or not successful. I.e. we have not been able to measure a delayed power with the methods for CIR measurement. Complex Channel Impulse Response For complex values we need some scaling for the delayed power in dBm which is 10 * log10(re^2 + im^2) + PowerOf1InDBm. Point of the Complex CIR real part page 20 of 35

NoiseFloorInDBm:

Point: PowerInDBm:

ComplexCIR: PowerOf1InDBm:

Point: re: Order-No. 1117.6885.04

New Features of ROMES 4.65 im: Peaks: NumberOfPeaks: Peak: InbandPowerInDBm: PeakPowerInDBm: MainDopplerInHz: CountOfGuardPeriods: imaginary part List of peaks of the CIR number of peaks in the list a Peak of the CIR inband power for this peak in dBm power of the peak in dBm

December 2011

This is a main component for a doppler frequency in Hz. CountOfGuardPeriods is a number of guard periods checked for the CIR peak. CountOfMatchingGuardPeriods = 0..CountOfGuardPeriods is a number of guard periods checked for the CIR peak and the signal of the peak is within the guard period. If 0 < CountOfMatchingGuardPeriods < CountOfGuardPeriods then there are some guard periods where the peak is in and others where the peak is outside. This happens when the guard period position is shifted between the measured OFDM symbols.

CountOfMatchingGuardPeriods:

DopplerPhaseIn2P16:

Main doppler phase in 2^-16 (2^16 = 360) at the first sample or 0. To get a better resolution of the doppler frequency we can store the sub Hz part in this variable. The Doppler frequency is than MainDopplerInHz + 2^-16 * MainDopplerFractionIn2Pm16Hz.

MainDopplerFractionIn2Pm16Hz:

DelayInSec:

delay in seconds from the first sample. This may be in a better resolution than the sampling time from the power delay profile.

5.3 LTE Scanner Raw Export


The LTE scanner module can now export the raw data of the scanner. The ASCII Export offers the additional signals: Power Raw SINR Raw SINR PSS Raw page 21 of 35

SINR SSS Raw Order-No. 1117.6885.04

New Features of ROMES 4.65 These values are the values, which the LTE Scanner Power View displays.

December 2011

6 GSM NWS Driver


The GSM NWS driver main setup page settings has a new section for selecting the scanned channels: Channel selection with GSM transmitter database. This function allows the user to extract the actually used channels from a database and to transfer this list to the Scanned channels list. The file path of the current database is shown und two buttons are available: 1) Get channels from current database: Copy the channels of the current database into the Scanned channels list. 2) Get channels from other database: Load another GSM transmitter database and copy the channels into the Scanned channels list. The benefit of the function is to optimize the scanning by skipping the channels of the GSM bands which are not used by the provider in question. The same function was already available in the GSM NWS wizard and has now been ported here.

Order-No. 1117.6885.04

page 22 of 35

New Features of ROMES 4.65

December 2011

7 UMTS PNS Driver


The max. measurement rate in the high dynamic mode has been increased from 1.6/s to 12/s for TSMU, TSMQ and TSMW. The default value has been set to 8/s. Highest real measurement rates can be expected with: UMTS synchronization All demodulation requests off Measuring only one channel.

8 TETRA Scanner
8.1 Driver
It is now possible to disable the internal Frequency Correction and the internal Equalizer of the TETRA Scanner module. Additionally a threshold can be set, which disables the analysis of signals which are close to the noise floor. To reduce the CPU load, the scanner can be forced to analyze only a certain amount of signals in parallel. Two new options are available in the Measurement Data section. The option Extended Sensitivity will increase the sensitivity of the scanner. The option Normal Burst Measurements enables additional quality measurements on the normal burst. This will increase the measurement speed for quality parameters significantly, especially in networks with high load.

Order-No. 1117.6885.04

page 23 of 35

New Features of ROMES 4.65 All settings are done in the Configuration Page of the TETRA Scanner:

December 2011

The TETRA Scanner now also measures the block error (Reed-Muller error correction failed) rate on the AACH channel and the modulation error ratio. The settings are reported in the measurement file info:

Order-No. 1117.6885.04

page 24 of 35

New Features of ROMES 4.65

December 2011

8.2 ROMES Signals


The new measurement parameters AACH BLER and MER are available in the signal tree of the TETRA Scanner.

Order-No. 1117.6885.04

page 25 of 35

New Features of ROMES 4.65

December 2011

9 KPI Generator
9.1 Introduction
In former versions all KPIs were calculated during the measurement by several ROMES drivers. The KPIs were stored in the measurement file. If a definition of a KPI has changed later on, it was not possible to correct the KPI values in the measurement file. The calculation of the KPIs from the trigger points was hard coded in the corresponding ROMES modules. This code covered specific KPIs which are clearly specified by technical bodies, e.g. ETSI. If more than one method of a KPI was defined (e.g. ETSI A or ETSI B), the user had to decide before the measurement, which method shall be applied. Only the KPIs of the selected method were calculated and stored into the measurement file. Now ROMES separates the measurement of trigger points and the postponed KPI calculation which is based on them. This means: Only the trigger points are stored in the measurement file, the KPIs are calculated by the new KPI generator which sends the result to the KPI Generator View. The calculation method is adaptable and extensible for specific customer requests. This calculation method is defined in a KPI definition file in XML format. A basic definition file is delivered for calculating all common KPIs, which ROMES has calculated in previous versions. The calculated KPIs can be exported to a CSV file. In a KPI export definition file in XML format it can be defined which KPIs should be exported. Calculation of averages, minimum, maximum over sessions and the whole measurement is possible in the export. The export result is visualized in the KPI Export Result View. To use an own KPI definition file or a KPI export definition file (edit or change definition to specific customer requests) the option ROMES4KPI (order no. 1117.6885.66) is necessary. Without that option the KPIs can be generated during measurement and replayed later, but only based on the basic definition files. Changing and editing is not allowed. However if a measurement was done on a machine with that option available and this measurement file is replayed later on a machine without that option, the behavior will be fully featured, means the same as with the option.

9.2 KPI Definition Files


For calculating and exporting KPIs two definition files in XML format are necessary, the KPI.XML and the KPIExport.XML. Default files with basic definitions are delivered with the ROMES installation located in the directory: [RomesApplicationData]\configuration To make changes, these files should be copied to another location, e.g. MyRomes for not to be overwritten with a later ROMES version (for changes the option ROMES4KPI is necessary). The used definition files during runtime (replay and measurement) is defined in the Technology Module for QosTester configuration. Order-No. 1117.6885.04 page 26 of 35

New Features of ROMES 4.65

December 2011

The default setting is [RomesApplicationData]\configuration, where these files are located after the installation. When changes are made in a definition file, an open measurement must be closed and reloaded to see the resulting changes in the views. If the option ROMES4KPI is not available these edit boxes and browse buttons are disabled. To use an own KPI definition file or a KPI export definition file (edit or change definition to specific customer requests) the option ROMES4KPI is necessary. Without that option the KPIs can be generated during measurement and replayed later, but only based on the basic definition files. Changing and editing is not allowed, any editing of the basic definition files will be detected and result in unusable files. The button Restore default will overwrite the actual KPI definition file settings with the default settings. Templates can be saved. Loading a template is only possible if the option ROMES4KPI is available.

Order-No. 1117.6885.04

page 27 of 35

New Features of ROMES 4.65

December 2011

9.2.1 Trigger Point Definitions


The KPI calculation is based on trigger points. All trigger points provided by ROMES are described in the document Trigger Point Definitions.doc, which can be found on the ROMES DVD in the subfolder \Documents\Manuals.

9.2.2 KPI Definitions / KPI Export Definition


The definition of KPIs and the definition of KPI export is described in the document KPI Definition File.doc , which can be found on the ROMES DVD in the subfolder \Documents\Manuals. An example is described in the document KPI Definition HOWTO define a KPI.doc , which can be found on the ROMES DVD in the subfolder \Documents\Manuals.

9.3 Views
9.3.1 KPI Generator View
The KPI Generator View looks similar to the old KPI View. When a session was defined (normally a connect disconnect sequence), all KPIs of a session are shown under the session tree node. Only these KPIs are displayed for which the KPI generator has found any trigger points.

Order-No. 1117.6885.04

page 28 of 35

New Features of ROMES 4.65

December 2011

Column description: KPI: Service: The KPI name defined in the KPI definition The service on which the trigger points were measured. If the service of start and stop trigger points are not identical, the service of the KPI is taken from the stop trigger point.

Order-No. 1117.6885.04

page 29 of 35

New Features of ROMES 4.65 Value:

December 2011

The value of the KPI and the trigger points. The value types (units) of the KPI and its trigger points can be different. This has the following reason: For example KPI FTP Mean User Data Rate is calculated by the amount of bytes between start and stop trigger point divided by the time span between start and stop trigger point. The result value of the KPI has the unit kbit/s, the values of the trigger points have the unit bytes to calculate the amount of bytes between start and stop trigger point. A trigger point can have meta data such as an URL, IP Address (see Trigger Point Definitions.doc for available meta data keys). This meta data information is displayed here. The KPI displays the meta data both of start and stop trigger points. The timestamps of the KPIs and its trigger points. The timestamp of the KPI is equal to the timestamp of the start trigger point.

Info:

Timestamp:

9.3.2 KPI Export Result View


The KPI Export View shows the result of the exported csv File from the KPI export definition. Every row of type <header> is a tree node for the rows of type <session> (see KPI Definition File.doc). The rows and columns depend on the KPI export definition.

Order-No. 1117.6885.04

page 30 of 35

New Features of ROMES 4.65

December 2011

9.4 Currently Supported Technologies


The following table shows the availability of trigger points from the DQA Jobs. DQA Job Connect Service / Protocol Service Independent Service Independent Application Trigger Points Yes TCP/IP Trigger Points No Remarks IP Tracer start is after successful connection IP Tracer stop is before disconnect request

Disconnect

Yes

No

FTP DL FTP UL FTP DL/UL

FTP FTP FTP

Yes Yes Yes

Yes Yes No IP Tracer can only detect TPs page 31 of 35

Order-No. 1117.6885.04

New Features of ROMES 4.65

December 2011 for one action per job

FTP Multi

FTP

Yes

No

IP Tracer can only detect TPs for one action per job

HTTP DL HTTP with IE WEB 2.0 Email DL Email DL Email UL Outlook

HTTP HTTP HTTP POP3 IMAP SMTP POP3

Yes Yes Yes Yes Yes Yes Yes

Yes Yes Yes Yes No Yes Yes Application Trigger points are the same as TCP/IP Trigger Points Application Trigger points are the same as TCP/IP Trigger Points Planned for a later ROMES release TCP/IP planned for a later ROMES release n.a. Planned for a later ROMES release Planned for a page 32 of 35 TCP/IP Planned for 4.66 or 4.67

Outlook

SMTP

Yes

Yes

Outlook

IMAP

No

No

Ping Ping

ICMP ICMPv6

Yes Yes

Yes No

VLC Run External Process Auto Dial

VLC -

Yes No No

No -

SMS

No

Order-No. 1117.6885.04

New Features of ROMES 4.65

December 2011 later ROMES release

DQA Multi Service (Flow)

Several Services

Yes

No

IP Tracer cannot detect TPs for parallel running jobs

9.5 Limitation of the current version


9.5.1 DQA Sessions only
The current version only visualizes trigger points related to a DQA session. This leads to the limitations, that no KPIs for circuit switched services are displayed. This limitation will be removed in the next version.

9.5.2 Multiple Services in one DQA Session


When more than one equal service is defined in a DQA Job List (eg. 2 FTP DL), the KPI Export can only show the KPI result (duration, data rate, ratio) of one of the defined services. However the min, max and average values per session and measurement are shown correctly.

9.5.3 Generic RAT Trigger Points


Currently Generic RAT Trigger Points based on Layer 3 Messages are supported for GSM and UMTS only. It is planned to extend those trigger points for the following technologies: LTE cdma2000, EV-DO TETRA

9.5.4 Merger / Splitter


In this version it is not possible to merge DQA measurements of ROMES 4.65.

9.5.5 Switching Measurement Mode


Currently the KPI Generator and its views have problems during measurement to handle switching from recording to measuring and vice versa. The relation of the KPIs to their sessions cannot be displayed correctly.

Order-No. 1117.6885.04

page 33 of 35

New Features of ROMES 4.65

December 2011

9.6 Compatibility / Differences to earlier Versions


9.6.1 General
In ROMES version 4.65 additional to the new KPI calculation the old KPI calculation is still available. It will be removed in 4.66. The old KPI View and the DQA Object View will be still available as legacy views in later versions for the replay of files from version 4.64 and earlier.

9.6.2 ROMES Signals


There are no ROMES Signals for the new KPIs available. The KPI signals were used to export the results of the measurement file. This should be done now via the Export View.

9.6.3 DQA

9.6.3.1All Jobs
In earlier versions, the results in the DQA Report View, KPI View and Object View depended on the selected ETSI version. The selection of the ETSI method is still available in 4.65, because the old KPIs are still available in this version. When the parameter Calculate KPIs from IP Tracer was activated, the results were taken from the IP Tracer KPI calculation. Now this parameter is not available anymore, because the TCP/IP trigger points are always available for new KPI Generator when the IP tracer is running. So TCP/IP KPIs are not stored in the measurement file anymore. The DQA Report View, the old KPI View and the Object View show only the results of application based old KPI calculation. In version 4.66 the ETSI selection will be also removed. Then the results in the DQA Report View will show results like ETSI B would have been selected.

9.6.3.2DQA Job HTTP with IE / WEB2.0


There can be greater differences between the application and TCP/IP trigger points. This is because the internet explorer mostly does not set events at the right time. You should trust the exact results of the TCP/IP calculation.

9.6.3.3DQA Job FTP Multi


In the old KPI logic, the session time was the sum of all FTP actions. In the provided KPI definition file the session time is calculated for every action separately.

9.6.3.4DQA Job FTP Download / Upload


In the old KPI logic, the session time was the sum of download and the upload. In the provided KPI definition file the session time is calculated for download and upload separately.

Order-No. 1117.6885.04

page 34 of 35

New Features of ROMES 4.65

December 2011

9.6.3.5KPI First Round Trip Time


In the old KPI logic the first RTT was equal to the IP Service Setup Time. This was not correct. In the provided KPI definition file the first RRT has the Trigger points data socket connect request and data socket connect completed (see ETSI TS 102 250-2).

Order-No. 1117.6885.04

page 35 of 35

Оценить