ONO005602 GENEX Nastar V600R014 LTE Performance Analysis ISSUE2.00

iManager Nastar V600R014 LTE Performance Analysis

Confidential Information of Huawei. No Spreading Without Permission

P-1



P-2




NASTAR = Network Analysis Star


P-3




Radio Access Network(RAN) 



The UTRAN NodeB and RNC provides MR and CHR data on the UMTS RAN side for the Nastar system. LTE eNodeB provides data on the LTE RAN side for the Nastar system to analyze

Core Network (CN) 

The SGSN provides call history record (CHR) data on the PS Core side for the Nastar system. The MME provides CHR data for the Nastar system to analyze.



M2000



Trace Server



Service Aware Unit (SAU)









The SAU is a service aware unit. It is installed as an SAUc or ESAUa board in a BSC on a GSM network or in an RNC on a UMTS network, and pre-processes raw data generated by the BSC or RNC into analysis data that meets the Nastar's requirements. The LTE SAU is a service aware unit for LTE. It is a functional module of the Nastar system, and is independently deployed on an RH2288 server on the operations support system (OSS) side. The LTE SAU collects raw data generated by eNodeBs through the TS, and preprocesses the data into analysis data that meets the Nastar's requirements. The PS SAU is a service aware unit on the CN side. It is a functional module of the Nastar system, and is independently deployed on an RH2288 server in the CN equipment room. The PS SAU collects control plane data from the CN, and pre-processes the data into analysis data that meets the Nastar's requirements.

Evolved Service Aware Unit (eSAU) 



The Trace Server (TS) is a functional module of the U2000 or M2000. It collects CHR data from eNodeBs on an LTE network.

PS SAU 



The U2000/M2000 provides performance data, and configuration data for the Nastar system.

LTE SAU 



P-4

The eSAU is a data aggregation unit. It is a functional module of the Nastar system. The eSAU is deployed as a board in an ATAE cluster system, or is deployed on an HP PC server together with the Nastar, on the OSS side. The eSAU centrally correlates, combines, and aggregates data pre-processed by the SAUs, LTE SAU, and PS SAU from multiple dimensions, and then provides the processed MR and CHR data and the control plane data from the CN side for the Nastar server.

Nastar server 

The Nastar server is deployed in an ATAE cluster system as a board, or is deployed together with the eSAU on an HP PC server, on the OSS side. The Nastar server analyzes data and generates analysis results for users to view on their Nastar client.



P-5



Coverage analysis: The MR report contains the radio link information when subscribers in a cell are making calls. It directly reflects the coverage, quality, and subscriber distribution of carriers and cells. Analysing MR helps in solving multiple network problems such as poor coverage, cross coverage, strong interference, and imbalance between uplink and downlink.



VIP analysis: The Nastar can filter CHRs of VIP subscribers from all the CHRs to analyze KPIs of voice and data services, including call drop rate, call setup delay, and UL and DL data rates. By monitoring the quality of service (QoS) of the VIP, the Nastar enables you to identify and solve the network problems that may cause VIP complaints, improving QoS and subscriber satisfaction. It can trend the periodical analysis results. In addition, the Nastar can identify the regions and cells where the VIP subscribers are active. You are obligated to comply with the laws of the countries concerned and the user privacy policies of your company, to ensure that the personal data of users is fully protected.



Complaint analysis support: After receiving subscriber complaints, this function can analyze call records, analyze the causes, and locate and solve the problems such as access failure, handover failure, and abnormal call drops. It improves the efficiency of handling complaints and increasing subscriber satisfaction. It provides combined complaint analysis of multiple RATs and CN scenarios like the LTE CSFB.



P-6



Terminal analysis: The Nastar obtain the CHRs of the network and analyze statistics on call drop rate, access success rate, and handover success rate by terminal model. By comparing the performance of terminals, the Nastar provides volumes and proportions of CS traffic, uplink PS traffic, and downlink PS traffic generated on frequency bands. This provides basis for users to formulate refarming policies. It helps operators identify the terminals with poor performance so that the operators can motivate terminal vendors to upgrade their terminal products or they can provide guidance for subscribers to purchase terminals with better performance.



Network geographic observation: The Nastar geographically locates and displays network coverage, traffic, users, and unusual events after collecting the entire network data, intuitively displaying general network conditions and problem areas



Cell performance analysis: The Nastar helps network O&M personnel locate cell problems. Through the cell performance analysis function, the Nastar obtains the data of abnormal calls in problematic cells. By analyzing and displaying the obtained data, it helps identify the causes of cell exceptions.





The Nastar system includes servers, clients, and SAU boards. The Nastar system servers can be deployed by using the HP DL580 server solution or the ATAE cluster solution.





The RAN SAU software is installed on the SAU board that is deployed in a base station controller



The LTE SAU and PS SAU software can be deployed on a Tecal RH2288 server that functions as a component of the Nastar system.





The LTE SAU software can be deployed on multiple Tecal RH2288 servers and functions as a component of the Nastar system.





The Nastar mainly uses the following three types of data during LTE network analysis: 

LTE configuration data 



LTE engineering parameters 

 

Basic information for network optimization, used for the Nastar to correctly retrieve data of each cell from data sources. Basic information for network optimization, including longitudes and altitudes of sites, and azimuths and down tilt angles of antennas. Used for displaying the analysis data geographically.

data related to Nastar analysis 

eNodeB single-subscriber all-signaling data



MME CHR data



eNodeB Call History Record (CHR) data: This data is also referred to as cell trace data.





SAU: The SAU performs control command interaction with the eSAU, and collects and preprocesses the CHR/MR data from the GSM/UMTS network as required.



LTE SAU: The LTE SAU performs control command interaction with the eSAU, and collects and preprocesses the CHR data from the LTE network as required.



PS SAU : The PS SAU performs control command interaction with the eSAU, and collects and preprocesses analysis data from the CN.



eSAU: The eSAU performs command interaction with the Nastar server, SAU, M2000, and PS SAU, collects and aggregates the configuration data and CHR/MR data.



Nastar server: The Nastar server performs command interaction with the Nastar client and eSAU, and implements service analysis based on the aggregated data.



Nastar client: The Nastar client performs command interaction with the Nastar server and displays the service analysis results.




P-12



P-13




P-14

The Nastar operations are divided into the following three phases: 1. Preparation phase: In this phase, we configure the OSS, eSAU, SAU, LTE SAU, PS SAU and NE in Nastar system to enable communication, in order to collect the basic data, such as configuration data and engineering parameters. This is peeformed by the administrator. 2. Data acquisition phase:In this phase, users have to subscribe data for analysis. This step ensures successful collection of data by Nastar. After data subscription, we need to verify integrity of data. This is an administrator task. 3. Analysis phase: In this phase, users create analysis tasks based on the obtained data and view the analysis result on the client. This is a task done by the network optimization engineers.





Start the Nastar client.



In the Login dialog box, configure the server where you want to log in:

P-16

If the server list does not exist in the Server drop-down list : 

Click “…” icon on the right of Server drop-down list.



In the Server List dialog box, click Add.







In the Add Server Information dialog box, set the Name, Server Name (or IP Address), Port and Mode.(Attention: If the Nastar client accesses the Nastar server by using the IP address of the firewall where the network address translation (NAT) is performed, type the IP address converted by the NAT. ) Click OK to go back to the Server List dialog box. In the Server List dialog box, the server that you set is selected by default.

In the Server List dialog box, click OK.

If servers are listed in the Server drop-down list: 

Select a server from the Server drop-down list.



In the Login dialog box, enter the user name and password.



Click Login.



1: Menu bar 2: Toolbar 3: Navigation tree 4: Output pane 5: Window bar 6: Task list pane 7: Task result pane 8: Status bar


P-17


1:Toolbar 2: Layer navigation tree 3: Chart area 4: Grid details area 5: Legend details area


P-18




P-19

The Nastar collects RAN and CN data from entities such as the M2000, eSAU, LTE SAU, SAU, and PS SAU. Therefore, you need to configure OSS and NE information so that these entities can identify and communicate with each other. Then, data can be obtained successfully. The information to be configured includes IP address, user name, password, and FTP information :  







Pre-Aconfiguration preparation : obtain information about OSS and NEs. Configuring eSAU information : configure the IP address, port number, and FTP information of the server running the eSAU software. Configuring OSS information : configure the IP address, software version, networking mode, and FTP information of the OSS server. Selecting RAN NEs managed by an OSS : select the RAN NEs managed by an OSS, such as BSC, RNC, and eNodeB. Setting SAU or LTE SAU information : configure the SAU information before you use the analysis function of the SAU board.




P-20


P-21



eSAU aggregates analysis data preprocessed by the xSAU and exports the data to the Nastar server. You can configure OSS and NE information only after you have configured information about eSAU.



Procedure: 1. Choose Maintenance > OSS Information Management. 2. In the upper area of the right pane, set basic eSAU server information so that the system can identify the server. 3. In the lower area of the right pane, set FTP information so that the system can collect data from the eSAU server using FTP.





Procedure: 1. Choose Maintenance > OSS Information Management. 2. Click NE Management in the navigation tree in the OSS Information Management window. 3. Click ADD OSS in the lower-right of the window. 4. Set basic OSS information and OSS FTP information. 5. Configure the Trace Server information.


P-22




P-23

Procedure: 1. Choose Maintenance > OSS Information Management. 2. Select an OSS from the navigation tree in the OSS Information Management window. 3. Click the RAN NE List tab in the right pane. 4. Click Select NE. The Select NE dialog box is displayed. 5. Select NEs managed by the selected OSS. 6. Click OK.





P-24

Procedure: 1. Choose Maintenance > OSS Information Management 2. In the navigation tree in the left pane of the OSS Information Management window, select an OSS node 3. Click the RAN NE List tab in the right pane 4. Set SAU parameters





P-25

Procedure: 1. Choose Maintenance > OSS Information Management 2. In the navigation tree in the left pane of the OSS Information Management window, select an OSS node 3. Click the PS Core NE List tab in the right pane 4. Set the PS SAU parameters





P-26

Configuration data 

Configuration data contains the basic information for network optimization, which is used for the Nastar to correctly retrieve data of each cell from data sources.



The Nastar automatically retrieves the configuration data from a specific path of the M2000 or OMC after users have configured the OSS information.



Engineering parameters 



Map files 



Electronic maps help Nastar to achieve accurate geographic display for desired regions.

NE group information 



Engineering parameters, which contain basic information for network optimization such as the longitude and latitude of a site, antenna azimuth, and tilt angle, help Nastar to achieve accurate geographic display.

LTE analysis is based on NE group or cell group.

Other data 

For some related Nastar analysis features



P-27

Procedure: 1. Choose Maintenance > Data Maintenance Management to open the Data Maintenance Management window. 2. In the Data Maintenance Management window, set Data Type on the left navigation tree. Choose System Type > *** Configuration Data. 3. Set Select Condition. Set Query type. Set a time segment only after you select Is time limit required. If no time limit is required for the query, you need not set this parameter. Select the NE object to be queried in the NE object navigation tree. 4. Select the NE object to be queried in the NE object navigation tree.

5. Click Query.





P-28

Procedure: 1. Double-click System Function > Engineering Parameter Management from the navigation tree in the Analysis Task Management window. 2. In the Engineering Parameter Management window, click the *** engineering parameters tab and then click Import. In the name of the tab, *** refers to the network system such as GSM, UMTS, or LTE. 3. In the displayed Open dialog box, select an engineering parameter file, and then click Open. 4. Configure the column headers. At the header of each column, right-click and choose the title of the current column. The column headers marked with the * character must be configured. Otherwise, the import operation is not allowed. 5. Click OK. 6. In the OK dialog box, check the number of added records, updated records, and failed records. Then, click OK. 7. Perform the operations as following. If the imported engineering parameter data is correct, Click Close. If the imported engineering parameter data is abnormal, Click Export Failed Records. You can modify error data and then complete the import operation. Click Close to complete the import operation. 8. View the synchronization status of the SAU to check whether the engineering parameters have been synchronized to the SAU.



P-29



By this function, we can check whether the existing engineering parameter data is consistent with the configuration data.



Procedure: 1. Double-click System Function > Engineering Parameter Management from the navigation tree in the Analysis Task Management window. 2. In the Engineering parameter management window, click the *** engineering parameters tab. 3. Click Check Configuration. The Nastar displays the check results. 4. Click Export Checking Results. 5. Select the saving path, saving name, and saving format of the check results in the Save dialog box.

6. Optional: Click Configuration Synchronize to synchronize engineering parameter data with configuration data.





Currently, the Nastar can display the following analysis results on a map: 

LTE VIP analysis results



LTE terminal analysis results



LTE complaint analysis support results



LTE geographic observation results.


P-30




P-31

Principles behind displaying the Nastar data on the Google Earth are : 

After importing engineering parameters, the geographic data is displayed on the scale of 2,600 meters at heights and with the last cell in the engineering parameter list being in the center by default.





The Nastar data can be displayed on the Google Earth synchronously.

Procedure: 1. Choose Tools > Google Earth. The EarthViewWindow window is displayed. The system loads the Google Earth through the Internet. After loading, the system reads the engineering parameters in the sever and displays the engineering parameters as labels on the Google Earth 2. Enable the Google Earth to display the Nastar data synchronously. After we click a cell in the analysis results, the Google Earth regards the selected cell as a center, and then displays the geographic data on the scale of 2,600 meters at heights. 3. View the cell information. After you click a cell, the Google Earth displays the engineering parameter information about the cell in a message box.



P-32



It takes a long time to import a WOR or TAB map file. If users on multiple clients attempt to import the same map file, the work efficiency is low.



To solve this problem, the Nastar allows users to convert a WOR or TAB map file to an SXWU map file and import the file because the Nastar can quickly identify and import SXWU map files and allows multiple users to share the SXWU map files.



This greatly improves the efficiency of importing map files. It is recommended that the map files be converted by one person, and then be shared to others.



Procedure: 1. Choose Tools > Convert Map on the menu bar. 2. In the displayed Parameter Config dialog box, set the conversion parameters. Maps Path: selects a WOR or TAB map file.

Save Path: sets the save path after format conversion. Save Name: sets the file name after format conversion. 3. Click OK.





P-33

Procedure: 1. Click

on the toolbar. The Geographic Observation window is displayed.

2. Click

on the toolbar. The Open the map dialog box is displayed.

3. Select a wor, tab, or sxwu map file. 4. Click Open.




P-34




P-35

Procedure: 1. In the navigation tree of the Analysis Task Management window, double-click the System Function > NE Group Management node. The NE Group Management window is displayed. 2. Select the *** NE Group tab, and click New. The New NE Group dialog box is displayed. 3. Set relevant parameters. 4. Click OK.





P-36

For LTE analysis both basic data subscription and application data subscription are needed.





P-37

Procedure of basic data subscription: 1. Choose Maintenance > Data Subscription Management. The Data Subscription Management window is displayed. 2. Click a tab for an RAT in the Data Subscription Management window. 3. In the NE object navigation tree, select the required NEs. On the Basic Subscription Settings tab page, data switch status of the selected NEs is displayed. During the initial setting, all data switches are in the OFF or Unknown state. 4.Choose the Basic Subscription Settings tab page. 5. Click Set on the Basic Subscription Settings tab page. The Basic Subscription Settings dialog box is displayed. 6.Set the data switch status of each analysis theme to ON. Click Confirm.



Procedure of application data subscription: 1. Choose Maintenance > Data Subscription Management. The Data Subscription Management window is displayed. 2. Click a tab for an RAT in the Data Subscription Management window. 3. In the NE object navigation tree, select the required NEs. On the *** Analysis tab page, application subscription status of the selected NEs is displayed. During the initial setting, all application subscription status is OFF or Unknown. 4.Choose the *** Analysis tab page. 5. Click ON on the tab page. The *** Analysis Parameter Setting dialog box is displayed. Set application subscription parameters. 6. Set application subscription parameters. 7. Click Confirm.





P-38

Procedure: 1. Choose Maintenance > Data Maintenance Management. The Data Maintenance Management window is displayed. 2. In the Data Maintenance Management window, set Data Type on the left navigation tree. 3. Set Select Condition on the Query Data tab page. Select Condition is optional. You can set a time segment only after you select Is time limit required. If no time limit is required for the query, you need not set this parameter. 4. Select specific nodes in the NE objects navigation tree. 5. Click Query in the bottom left corner of the window.





P-39

Procedure: 1. Double-click a theme node from the navigation tree on the Analysis Task Management window to open New Task dialog box. 2. Set the basic task information such as Task Name, Task Type, and Note. 3. Click Next and set the task parameters.





P-40

Procedure: 1. Choose Theme Function > *** Analysis Task from the navigation tree on the left of the Analysis Task Management window. If you choose Theme Function, the task list on the right displays all the performance analysis tasks. 2. Select a task from the task list in the upper right pane. 3. Select an analysis result from the result list on the lower right of the Analysis Task Management window. 4. Double click or right-click the analysis result, and then choose View Analysis Result. The analysis results window is displayed.




P-41


P-42



LTE coverage analysis function enables the Nastar to analyze the measurement reports reported by MSs



This help us to locate wireless network problems, such as weak cell coverage, cross coverage, and poor QoS



Information about the indicators such as UE Tx power, Timing Advance (TA), and number of uplink and downlink retransmissions are collected and processed by the eNodeB. UE Tx power is converted from the Power Headroom (PH) reported by UEs.



Key events including RRC connection setup requests, RRC connection setup failures, abnormal E-RAB releases, UL retransmissions, DL retransmissions, and Intra-RAT HO failures.



The analysis results are displayed in the format of a 2D chart, 3D chart, and overview table. The analysis results can be exported as a .csv, .xls, or .xlsx file.





P-43

Analysis scope and the range of analysis time specifications.

Item

Service Specifications

Execution type

One-time task

Network scale for one analysis task

<= 10,000 cells

Number of allowed analysis tasks

<= 50

Time range for data in one analysis task

<= 7 days

Duration of one analysis task

≤ 85 minutes

Default duration for storing analysis data

15 days

Maximum duration for storing analysis data 15 days



P-44

Check the integrity of LTE coverage analysis data 1. Navigation path: Choose Maintenance > Data Maintenance Management 2. Set Data Type to LTE FDD Coverage Analysis Data or LTE TDD Coverage Analysis Data. 3. Set the query time period. 4. Select the NEs to be queried. 5. Click Query. The query results are displayed in the right pane of the window.  

If analysis data exists, create an analysis task. If analysis data does not exist, request the administrator to subscribe to the data



P-45

Procedure 1. In the Data Subscription Management window, click the LTE FDD or LTE TDD tab. NOTE: If you want to subscribe to data related to LTE FDD coverage analysis, click the LTE FDD tab; if you want to subscribe to data related to LTE TDD coverage analysis, click the LTE TDD tab. 2. Select the NEs to be configured from the left navigation tree. 3. On the Basic Subscription Settings tab page, click Set. 4. In the Basic Subscription Settings dialog box, set Coverage Analysis Data to ON. By default, The default subscription switch status is No Modification. 5. Click Confirm.



P-46

Procedure: 1. In the Data Subscription Management window, click LTE FDD or LTE TDD tab. 2. Select the NEs to be configured from the left navigation tree. 3. On the Coverage Analysis tab page, click ON. 4. Set threshold parameters in the displayed Coverage Analysis Parameter Setting dialog box. 5. Click Confirm Coverage Analysis Parameters Parameter UltraOverlapping Coverage Cell Definition

Description DL RSRP difference between serving cell and neighboring cell <=A number of neighboring cells meeting previous conditions >=B and serving cell RSRP >C

Specifies the threshold value for a ultra-overlapping coverage cell. This parameter enables the Nastar to obtain only the data that shows the DL RSRP difference between the serving cell and its neighboring cell less than or equal to A, the number of neighboring cells meeting the previous condition greater than or equal to B, and the RSRP of the serving cell greater than C. •Value range: A, [0,10] •B, [1,6] •C, [-140,-43]

Overshooting RSRP of neighboring cell Cell Definition as evaluated object — Serving cell RSRP >K, and Serving cell RSRP > L

Specifies the threshold value for a overshooting coverage cell. This parameter enables the Nastar to obtain only the data that shows the difference between the RSRP of a neighboring cell as the evaluated object and the RSRP of the serving cell greater than D and the RSRP of the serving cell greater than E. •Value range: D, [-10,0] •E, [-140,-43]





P-47

Create an LTE coverage analysis task. 1. In the left navigation tree of the Analysis Task Management window, choose Theme Function > Basic Network Optimization > LTE Coverage Analysis. 2. Double-click the LTE Coverage Analysis or ‘New’ icon to create new analysis. 3. Set the task name and task remarks. Click Next. 4. On the Select NE(s) tab page, select the analysis type and NEs to be analyzed. 5. On the Parameter Settings tab page, set filter criteria. 6. Select Numbers and set the report number. Click Next.

7. Select the analysis time period. The Nastar obtains the relevant analysis data in the time period.



P-48

Specific Parameters. Parameter

Description

Analysis indicator

Sets the filter criteria for analysis data. Two filter criterias : 2D model : Filter cells by a single counter. The counter can be TA, UE_TxPower, RSRP, or RSRQ. •2D: DLRSRP < -110, ratio > 5% indicates the serving cells Number of MRs which DL RSRP < -110 dBm accounts for more than 5% of Total MRs are filtered. That is, cells with weak coverage problems are filtered. •3D: DL RSRP < -110 OR DL RSRQ > -10, ratio > 5% indicates that the serving cells Number of MRs which DL RSRP is less than -110 dBm or Number of MRs in which the DL RSRQ is greater than -10 accounts for more than 5% of Total MRs are filtered. That is, cells with weak coverage problems are filtered. Nastar allows to set filter criteria based on OverLappingCell and OverShootingCell. •OverLappingCell:[MRPercent > 0] > 5% indicates that the ratio of overlapping coverage MRs of the cell > 5%, and the number of MRs of the cell > 3000. That is, the cell is an overlapping cell. •OverShootingCell:[(CorrelativeRatio > 0.01) and (CorrelativeCellNum > 8)] > 0% indicates that the correlation coefficient between the object to be evaluated when serving as a neighboring cell and the corresponding primary serving cell > 1, and the number of MRs of the object to be evaluated when serving as the primary serving cell is 3000, and the number of primary serving cells that meet the preceding two conditions is ≥ 8. That is, the cell is an overshooting cell.

Numbers

Filters cells based on the size of the traffic amount, that is, filters cells based on the total number of reports of an indicator. After the filter criteria are set, analysis results only meeting the filter criteria can be displayed. It ranges from 10 to 100000.

MR RSRP Coverage Rate

The RSRP value ranges from -140 to -43 dBm. The default value is -110 dBm.



P-49

You can enter the result window using either of the following : 

Select an executed LTE coverage analysis task and double-click a result of the task in the Task Result area.



Select an executed LTE coverage analysis task, right-click a result of the task in the Task Result area, and choose View Analysis Result from the dropdown menu.

Display Panes of the analysis window as per above illustration : 1:

Export analysis result;

2:

Analysis object;

3:

Analysis result;

PDF / CDF 

: Probability and Cumulative Distribution Functions

You can perform the following operations in the chart area:  



You can double-click a chart to zoom in/out the chart. You can use the mouse to drag the border of the chart or right-click the chart and choose Zoom In or Zoom Out from the shortcut menu to adjust the size of the chart. You can also use the shortcut menu items to query, save, or print the chart.



P-50



PDF: Probability Distribution Function



CDF: Cumulative Distribution Function



PDF/CDF service have four KPIs: TA, RSRP, RSRQ, UE TXPOWER, and CQI. Following describes how each KPI is mapped to the coordinate system:  



The horizontal axis indicates the value of each KPI. The left vertical axis is a bar chart value, indicating the percentage of the MRs of each KPI. The right vertical axis is a line chart value, indicating the total percentage of the MRs of all KPIs whose value is less than or equal to a KPI value on the horizontal axis.



P-51



3-dimensional analysis can provide the joint distribution of RSRP/RSRQ, TA/UE Tx power, TA/RSRP, TA/RSRQ.



The description of the chart area is as follows:  



The horizontal and vertical axes indicate the values of two different KPIs. The colour of each cell indicates the percentage of the KPI layout in the case of a certain KPI pair. Legends are provided on the right. Each number indicates a specific percentage value. You can use the mouse to drag the border of the chart or right-click the chart and choose Zoom In or Zoom Out from the shortcut menu to adjust the size of the chart.





P-52

Timing Advance is used to control Uplink signal transmission timing. Network (eNodeB in this case) keep measuring the time difference between PUSCH/PUCCH/SRS reception and the subframe time and can send a 'Timing Advance' command to UE to change the PUSCH/PUCCH transmission to make it better aligned with the subframe timing at the network side. If PUSCH/PUCCH/SRS arrives at the network too early, network send a Timing Advance command to UE saying "Transmit your signal a little bit late", If PUSCH/PUCCH/SRS arrives at the network too late, network send a Timing Advance command to UE saying "Transmit your signal a little bit early".



the UL transmit timing is controlled by following equation: 

UL Transmission Time = (UL Transmission Time for Previous subframe) + (TA value - 31) x 16 samples 

where 1 sample is about 0.033 us and 16 samples is about 0.52 us.




P-53




VIP Report Analysis 



Traditionally you will manually process periodic analysis and then trends specific KPIs, which is inefficient. By contrast, this function is very efficient.

VIP All-Signaling Analysis 



This function allows analysis of CHR of a VIP subscriber if the KPIs of the VIP subscriber deteriorates for problems that cannot be isolated onsite. You can find for example cause of abnormal release, MR prior to radio link release, mobility, and key signalling procedures during each call.

VIP Trend Analysis 



Nastar periodically collects statistics and analyzes various user assurance KPIs (success rates, delays etc) of VIP subscribers and VIP groups, generating different service assurance reports.

VIP In-depth Analysis 



P-54

If a VIP subscriber's control plane is normal but service quality problems occur during a call or if complicated exceptions require analysis on complete signaling procedures, this function helps you solve such problems.

VIP Active Cells Displayed on the GIS 

This feature geographically display and render active cells and KPIs on map.




P-55




P-56

Procedure of managing VIP users: 1. Double-click System Function > VIP Group Management in the navigation tree on the left of the Analysis Task Management window. 2. Click the VIP User tab. 3. Create VIP users and then add them to VIP groups. We can create a VIP user directly or by importing a file.



Procedure of managing VIP groups: 1. Double-click System Function > VIP Group Management in the navigation tree on the left of the Analysis Task Management window. 2. Click the VIP Group tab. 3. Create a VIP group. We can create a VIP group directly or by importing a file.



P-57

Check whether analysis data is integrated 1. Navigation path: Choose Maintenance > Data Maintenance Management 2. Choose Data Type > User Assurance > *** VIP Analysis Data. *** indicates the network type. 3. (Optional) Specify a period for querying data integrity. 4. Select the NEs and VIP groups for which the data integrity needs to be queried. 5. Click Query. The query results are displayed in the right pane of the window.  

If analysis data exists, create an analysis task. If analysis data does not exist, request the administrator to subscribe to the data



P-58

Procedure 1.

In the Data Subscription Management window, click the *** tab. *** indicates the network type.

2.

In the left navigation tree, select the NEs to be configured.

3.

On the Basic Subscription Settings tab page, click Set.

4.

In the displayed Basic Subscription Settings dialog box, set the switch of VIP analysis data to ON. In the LTE FDD, and LTE TDD network, the switch name is VIP Analysis Data (CHR).

5.

Click Confirm.



P-59

Procedure: 1. In the Data Subscription Management window, click the *** tab. *** indicating the RAT. 2. In the left navigation tree, select the NEs to be configured. 3. On the VIP analysis tab page, choose Group Level, and click ON. 4. Select VIP groups and NEs. If you want to perform all-signaling analysis on a subscriber, check that VIP subscriber and the VIP group has been selected. 5. Click Confirm.



Procedure 1. In the Analysis Task Management window, select Theme Function > User Assurance > VIP Analysis. 2. Double-click the VIP Analysis or ‘New’ icon to create new analysis. 3. Set the task name and task remarks. Click Next.


P-60


4. On the Analysis Type tab page, set the net type and the data types. 5. On the Select NE(s) tab page, select a NE.


P-61


P-62

6. On the VIP Group tab page, select the VIP groups to be analyzed. 7. On the Result Threshold tab page, set the abnormal threshold of each KPI. 8. On the Process Threshold tab page, set the abnormal threshold of each KPI. Click Next. 9. Choose the task type, and set the analysis time segment. The Nastar will obtain the relevant analysis data in the time period. Click Next. NOTE: To obtain accurate subscriber information, you are advised to set Execute on to 1 hour.

Parameter

Description

Service Type or Flow Type or Service/Flow Type

•When only analyzing the RAN data, the parameter is displayed as Service Type, such as NET, Call, and so on.

Indicator Name

Indicates the name of a KPI process threshold.

Criterion

Indicates the relationship between the KPI value and KPI abnormal threshold.

Threshold

Indicates the abnormal threshold of a KPI. If the KPI value of a subscriber reaches the threshold, this KPI is considered as a problematic KPI or deteriorating KPI.



P-63

10. Optional: On the Sending Analysis Reports Setting tab page, set the values of multiple parameters for automatically sending an analysis report through email.

11. Click Finish.



P-64



Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finished state. In the lower right of the Task Result area, select a result record of the task.



Procedure: 1. Double-click an analysis result of the task. 2. In the displayed VIP Analysis window, click the User Level Results tab to view the VIP summary analysis results.



Above illustration is analysis on ‘User level Results’. Selected on the tab.



Further Deep Analysis triggered by the clicking the icon.



P-65






Procedure: 1. Double-click an analysis result of the task. 2. In the displayed VIP Analysis window, click the Network Level Results: Active Cell tab to view the analysis results of cells where VIP subscribers are active



Above illustration is analysis on ‘Networl level Results – Active Cell’. Selected on the tab.



P-66



Navigation path: In the upper right area of the Analysis Task Management window, select a periodic task in the Finished state. In the lower right of the Task Result area, select a result record of the task.



Procedure: 1. Right-click the analysis result of the task, and choose Trend Analysis from the shortcut menu. 2. In the displayed *** VIP Trend Analysis window, view the trend analysis results.

 Alternatively on the toolbar, click the ‘trend analysis’ icon.




P-67


P-68



You are obligated to take measures, in compliance with the laws of the countries concerned and the user privacy policies of your company, to ensure that the personal data of users is fully protected.



CHR: Call History Record. On the LTE network, the CHR data includes the eNodeB CHR data and the MME CHR data. The MME CHR data provides the IMSI and IMEI information.



In case of user complaint, a one-off complaint analysis support task is created on the Nastar. Then the SAU connected to the Trace server retrieves abnormal call records occurring in the specified period and specified cell from call records based on the IMSI of the complaining user.




P-69


P-70

Procedure 1. In the Data Subscription Management window, click the *** tab. *** indicates the network type. 2. In the left navigation tree, select the NEs to be configured. 3. On the Basic Subscription Settings tab page, click Set. 4. In the displayed Basic Subscription Settings dialog box, set complaint analysis support data to ON. In the LTE FDD, and LTE TDD network, the switch name is Complaint Analysis Support Data(CHR). 5. Click Confirm.



P-71



Navigation path: Choose Theme Function > User Assurance > Complaint Analysis Support in the navigation tree of the Analysis Task Management window.



Procedure: 1. Double-click the Complaint Analysis Support node. 2. Set the task name and task remarks. Click Next.



P-72

3. On the Set Analysis Type tab page, set a net type and a data type. 4. On the Select NE(s) tab page, click Select to select the NEs located in an area where subscribers complained about.



P-73

5. On the Select Complaining User tab page, click Add or Import to set the IMSI information (user alias, IMSI, and remark), STMSI, MSISDN, or peer MSISDN of the complaining subscriber. 

IMSI: Supported by every network.



STMSI: Only supported by the LTE network.

6. On the Set KPI Threshold tab page, set the abnormal threshold of each KPI. Click Next. 7. Choose an analysis time segment. The Nastar obtains the relevant analysis data in the time period. To obtain accurate subscriber information, you are advised to set Execute on to 1 hour. 8. Click Finish



P-74






Procedure: 1. Double-click an analysis result of the task. 2. In the displayed Complaint Analysis Support window, view the complaint analysis support results



Bottom third (from left) pane is Theme analysis area. Here you can use the tab to display three more analysis panes: 1. Measurement Information

2. E-RAB Analysis 3. Mobility Analysis





P-75

The naming convention for the tab page is ***_Serial Number. *** indicating the user.





P-76

Signaling information table – (1) Lists interactive signalling flow between NEs in the call process, with time stamp, direction, type, and content. The chart displays the corresponding information when you select the information in the table.



Signaling flowchart – (2) Illustrates signalling interactions between of NEs during a call. The chart displays the corresponding information when you select the information in the table. 

Time stamp of each signalling is displayed on format is hh:mm:ss.ms



NEs are displayed on the upper part.





Words in the figure are names and numbers of each signalling. The dashed line indicates the signalling. The arrow indicates the direction.

This window shows the signalling process prior to call release





P-77

Detailed MR information table (1) Lists detailed MR information. The information includes time, measurement object type, and detailed counter information



Change trend chart of measurement counter values (2) The change trend of measurement counter values is displayed in charts. Each trend chart consists of four parts. They are as follows from left to right:  Title  Y-axis, displaying the maximum and minimum values.  Counter change trend chart, displaying the change of counter values for a maximum of 20 MRs on the interface by default. You can view the more MRs through the scroll bar.  Legend



Prior to call release, detailed MR information tables and the change trend chart of measurement counters value can be viewed here.




P-78




Basic Operations icon Area (1)



Navigation tree (2)



Geographic observation area (3)



Grid detail area (4)



Legend area (5)



Information area (6)


P-79



P-80


P-81



To ask the UE report IMEI, we must verify that the IMEI switch is enabled on MME.



This analysis function analyse KPIs based on the call records of subscribers reflecting the access performance, service retainability, and mobility .



It helps operators identify the terminals with poor performance. Therefore helping the operators provide subscribers with stable services and improve the subscriber satisfaction.



You are obligated to take considerable measures, in compliance with the laws of the countries concerned and the user privacy policies of your company, to ensure that the personal data of users is fully protected.




P-82




P-83

We can create a terminal attributes by importing a file using Import icon in the lower right corner. Terminal attribute files in .csv, .xls, .xlsx or .tac format can be imported and exported.





P-84

Procedure: 1. Choose System Function > Terminal Type Management from the navigation tree in the Analysis Task Management window and right-click Open. The Terminal Type Management window is displayed. 2. Create terminal types directly or by importing a terminal type file. 

Click New in the lower right corner. The Terminal Type Management-New dialog box is displayed.



Set following parameters. The asterisk means mandatory. 

    



 

IMEI-TAC - first eight digits of the IMEI that identifies the type of a terminal Mandatory Vendor - Mandatory Terminal Model - Mandatory Chip Model - Optional Terminal Technology – Indicate RAT - Optional Data Transfer - PS transfer mode. Example GPRS/EDGE, GPRS/EDGE/HSDPA. Optional Terminal Type - Example Feature Phone, Smartphone, Data Card, Wireless Landline, Family Gateway. - Optional Support Wi-Fi - Optional

Click OK.



Check whether analysis data is integrated 1. Navigation path: Choose Maintenance > Data Maintenance Management 2. Set Data Type to LTE FDD Terminal Analysis Data or LTE TDD Terminal Analysis Data. 3. Set the query time period. 4. Select the NEs to be queried. 5. Click Query.


P-85


P-86

Procedure 1. Choose Maintenance > Data Subscription Management 2. In the Data Subscription Management window, click the LTE FDD or LTE TDD tab. 3. Select the NEs to be configured from the left navigation tree. 4. On the Basic Subscription Settings tab page, click Set. 5. In the Basic Subscription Settings dialog box, set the switch of Terminal Analysis Data to ON. 6. Click Confirm



P-87

Procedure: 1. Choose Maintenance > Data Subscription Management 2. In the Data Subscription Management window, click the LTE FDD or LTE TDD tab. 3. Select the NEs to be configured from the left navigation tree. 4. On the Terminal Analysis tab page, click ON. 5. In the Terminal Analysis Parameter Setting dialog box, set the threshold value for exceptions. 6. Click Confirm.




P-88


P-89

To Display above window : 1. In the upper right area of the Analysis Task Management window, select an analysis task in the Finished state. In the lower right of the Task Result area, select a result record of the task. 2. Double-click the result record of the task. 3. The results of the LTE terminal analysis task are displayed in the LTE Terminal Analysis window as illustrated above. 4. Analysis results are displayed in the form of tab page. a) The Market Share tab page is used to analyze the occupation of terminals on the live network by different dimensions. b) The Capability tab page is used to analyze the proportion of different terminal capabilities supported by the terminals on the live network. c) The Performance tab page is used to analyze the performance counters of one type of terminals in a cell and of a specific bearer type



Terminal Market Share analysis: This function collects statistics on the distribution of terminals on the existing network from dimensions, such as terminal vendor and terminal type, and then provide guidance for future network deployment and marketing strategies.





P-90

Terminal capability: This function calculates the number of terminals with a specific capability on a network and then provide basis for operators to deploy networks that support terminals with such a capability.





P-91

Terminal performance analysis: This function identifies certain types of terminal that impose large signaling load on the network and then provide solution to signaling storm. It also enables users to aggregate cell- and bearer-level KPIs. By aggregating cell-level KPIs, the users can perform joint analyses on the query results and the actual conditions of cells, and then determine whether the poor performance of terminals are caused by the defects of the terminals themselves or by the impacts from certain cells. By aggregating bearer-level KPIs, the users can perform joint analyses on the query results and the services, and then determine which service is not supported enough due to certain defects of the terminals on the existing network.




P-92


P-93



This feature provides data about subscribers experiencing abnormal calls in problematic cells and helps to analyze the root causes of these abnormal calls triggering optimisation process on those cells.



This function can be used to quickly locate and resolve problems. Normally there is no way to avoid that some user data such as IMSI will be used during the troubleshooting. However, this function provides an anonymous data processing method.



You are obligated to take considerable measures, in compliance with the laws of the countries concerned and the user privacy policies of your company, to ensure that the personal data of users is fully protected.




P-94


Check whether analysis data is integrated 1. Navigation path: Choose Maintenance > Data Maintenance Management 2. Set Data Type to LTE Cell Performance Analysis Data. 3. Set the query time period. 4. Select the NEs to be queried. 5. Click Query.


P-95




P-96

During creating LTE cell performance analysis task, some parameters need to be set like Analysis Type and NE as per above example



P-97



Thia window is displayed when you select a finished LTE cell performance analysis task and double-click (or right click and then use context menu) a result record in the Task Result area.



The aggregated cell performance analysis results are displayed in tables, including the table of exception types, table of exception causes, and table of bottomN users, terminal models, or cells.





P-98

Further analysis can show the details of every exception based on exception types or exception users.





P-99

In-depth analysis interface where you can analyze abnormal call records based on problematic cells




P-100




P-101

In the geographic analysis on problem network coverage, the following performance counters can be geographically rendered: Proportion of Poor Coverage, Proportion of Coverage Holes, Proportion of Cross-district Coverage, and Proportion of No Dominant Pilot. Function: The Nastar replaces the traditional emulation tool and truly displays the coverage problems of the serving cell, helping the operator to intuitively locate problem areas with problems such as poor coverage.



In the geographic analysis on network coverage, the following performance counters can be geographically rendered: RSRP, RSRQ, UL Demodulation RS RxPower, UL Demodulation RS SINR, UE TxPower and Primary Serving Cell.



In the geographic analysis on network traffic, the following performance counters can be geographically rendered: Total Traffic Volume, UL Traffic Volume, DL Traffic Volume, UL Average Throughput, DL Average Throughput, and Average Number of RRC_Connected Subscribers.




P-102


P-103

Check whether analysis data is integrated 1. Navigation path: Choose Maintenance > Data Maintenance Management 

Choose Data Type > Network Analysis > *** Network Geographic Observation Data. *** indicates the network type including LTE TDD and LTE FDD.

1. Set the query time period. 2. Select the NEs to be queried. 3. Click Query.



P-104



1

- Operation icon area



2 KPI

- Navigation tree to activate display of Site Layer, Polygon Areas and - Themes to analyse on the MAP view.



3

- Geographic observation area



4

- Detailed grill information list area



5

- Legend detail area





P-105

Once you select a polygon then Nastar provides an entry for further traffic analysis on the selected area. The results show detailed information about traffic indicators in the polygon areas in charts and tables




P-106



P-107

ONO005602 GENEX Nastar V600R014 LTE Performance Analysis ISSUE2.00

Recommend Documents