Driving test solution Part 2: Testing with Nemo Outdoor 1. Overview 2. Software and tools 3. Testing with Nemo Outdoor Part 3: Handy solution 1. Overview of driving test tools Part of all phases of Mobile Network life circle: planning, turn up, maintaining, optimizing, troubleshooting. QoS parameters: Configuration Services. Nemo Outdoor supports more than test terminals and scanners. Patented Multi-Data functionality in Nemo Outdoor empowers the user to connect up to 6 terminals to one laptop.
Comprehensive and cost-efficient Drive testing, QoS and benchmarking measurements can all be carried out on a single platform. Base software works for all technologies Look and feel always the same. Handlers are all optional and can be selected depending on technology and terminals required. Can also be used for indoor testing. Use case examples Voice quality benchmarking in parks and pedestrian zones Roll-out LTE service KPI verification at shopping malls Multi-technology and multi-operator benchmarking on trains, buses, and boats.
Wire-free mobility Three hot-swappable Li-ion batteries Up to 36 hrs of usage without an external power supply. With Nemo Outdoor it is possible to perform mobile-to-mobile and mobile-to-fixed-to-mobile voice quality measurements The measurement is based on the ITU-T recommendations P. The information provided by Nemo Outdoor assists in the verification and troubleshooting of new services reducing the time-to-market.
Available parameters: Video codec Video frame rate Video protocol Video quality degradation due to compression Video quality MOS Video quality MOS degradatation Video quality jitter Video quality packet error rate Video quality degradation due to packet errors Video quality type Video preview can be seen during the measurement. Pilot and frequency scanning can be performed on Nokia terminals. Hence, there is no need to use a separate fast frequency scanner to perform scanning and missing neighbor detection on both GSM and WCDMA bands simultaneously, which adds to costeffectiveness and increases user convenience.
Also called sleeping cell detection. UE is automatically locked to neighbor cells and test call is made. Surrounding cells can be tested from a single location. User can select parameters to be decoded from signaling messages and show them in the UI during measurements and playback. No conversion or parsing of the files A detailed description of the file format is included in the product user documentation.
The file format description contains all recorded events and their parameters. Can be used to create Conditional scripts where the type of the detected packet technology determines how the script proceeds.
The Loop script command enables scripts where a portion of the script is repeated a number of times before proceeding with the rest of the script. With the Wait script command, the user can create scripts that are not activated before a certain system or bandwidth is active. Messages from events, L3, etc. Route planning - measurement route can be planned beforehand Parameter-based route coloring Active cell information can be plotted along the routes Base station icons, site names, and cell information displayed on map Color set to color BTS icons based on different parameters Find cell - possibility to search cells on the map Possibility to plot the same measurement several times on a map to easily correlate different parameters.
Nemo Outdoor with Indoor option is suited for indoor measurements. Standard Graphics formats. Powerful platform-based tool All the latest customer needs can be met through additions of options to the flexible and expandable Nemo Outdoor platform. Comprehensive and cost-efficient : one platform with support for different terminal vendors and more than different test devices.
Centralized solution All of the test devices among the extensive selection can be connected to a single laptop. Extremely easy to set up, configure and use with Autodetect devices, automated test with advantage script function. Nemo Multi Handy is the most portable and cost-effective benchmarking solution in the market Multiple Handy terminals collecting syncronized measurement data that enable benchmarking with up to seven terminals.
Summary Handy Solution: Handy-Symbian, Handy-Android, Handy-Window Phone Ease of use Intuitive user interface makes all operations from timeslot testing to creating complex measurement scripts time-effective and easy Multi Handy functionality A centralized solution for conducting large-scale measurements.
This channel is coded with the scrambling code of the cell that it belongs to, therefore the UE can use this channel to determine the received signal strength of this particular cell. The downlink common control channels have to reach all UEs in the cell and should not be too loud to disturb other cells.
As the cell size is often adjusted, it may occur that the power level of all control channels must be readjusted. To simplify this, the power level of all control channels are expressed in relation to the power that is used by the Pilot Channel of a cell. If this is the case, the UE is informed about this by higher layer signaling. It has a fixed spreading factor of This allows for up to 15 parallel channels.
The transmit power is set by the scheduler, that is, it is constant during one transmit time interval. This channel uses a spreading factor of Typically, the PRACH is used when a mobile user wishes to initiate a call and requests radio resources. UEs receive information on what access slots are available in the current cell over the broadcast channel BCH. The access slots have time offsets that are spaced 1.
Introduction The transport channels convey data from the MAC layer to the physical layer and there are mapped to physical channels. The physical layer offers the transport channels different bitrates, depending on the spreading factor used. Several transport channels are multiplexed on one physical channel. The common transport channels may be used by multiple users, the dedicated transport channel to one single UE only.
The Node B has the power control for this channel to minimize uplink interference levels. Currently identified information types are paging and notification. Introduction A set of logical channel types is defined for different kinds of data transfer services as offered by MAC. Each logical channel type is defined by the type of information transferred as opposed to transport channels which define how data is transported.
This channel is used when the network does not know the location cell of the UE, or, the UE is in the cell connected state utilising UE sleep mode procedures. This channel is commonly used by the UEs having no RRC connection with the network and by the UEs using common transport channels when accessing a new cell after cell reselection. This channel is established through RRC connection setup procedure. A DTCH can exist in both uplink and downlink.
Channel mapping The following figure illustrates the logical channels and their corresponding transport channels that MAC is responsible for mapping Medium Access Control The MAC model maps the transport channels it receives from the physical layer to the logical channels it passes on to the Radio Link Control protocol and vice versa.
Each transport channel can have different bit rates. Thus, the MAC model is responsible for transporting blocks of data according to the specified channel bit rate. The illustration shows the position of the MAC protocol. Selection of Given the Transport Format Combination Set assigned by RRC, appropriate MAC selects the appropriate transport format within an assigned Transport Format transport format set for each active transport channel depending for each Transport on source rate.
The control of transport formats ensures efficient Channel depending use of transport channels. Transport format selection may also take into account transmit power indication from layer 1. Since the MAC layer handles the access to, and multiplexing onto, the transport channels, the identification functionality is naturally also placed in MAC. Traffic volume Measurement of traffic volume on logical channels and reporting monitoring. Based on the reported traffic volume information, RRC performs transport channel switching decisions.
Ciphering This function prevents unauthorised acquisition of data. This service does not provide any data segmentation. MAC parameters. The data transfer type depends on whether a MAC header is attached to the packet. Depending on the logical to transport mapping relationship, all, a selection or none of the above parameters may be used.
There may be several simultaneous RLC links per User Equipment; each link is identified by a bearer id. How to perform the segmentation is decided upon when the service is established. The RLC also decides which logical channel should be used. The number of logical channels that is needed is decided upon when the service is established. The length of the PDUs is decided upon when the service is established.
The retransmission buffer also receives acknowledgements from the receiving side, which are used to indicate retransmissions of PDUs and when to delete a PDU from the retransmission buffer. Proper setting and optimisation of these parameters is vital to provide packet-switched RABs with the required quality of service QoS.
Once the acknowledgement arrives, data flow can recommence. The RRC manages the configuration of layer 2 and layer 1 protocols with direct links to each of the lower layers. The following illustration shows the lower layer interactions of the RRC. The system information is normally repeated on a regular basis.
Higher layers on the network side can request paging and notification. The two peer entities are synchronized. Connected mode Connected mode is entered when the RRC connection is established. Signaling connection An acknowledged-mode link between the UE and the CN to transfer higher layer information between the entities in the non-access stratum. Such signaling messages could be for example, session management messages, such as a PDP context request; or Mobility Management messages, such as those used in handover signaling.
Radio Link Setup Request 3. Radio Link Setup Response 4. Downlink Synchronization 6. Uplink Synchronization 7. The request for the set-up of an Iub data transport bearer is acknowledged by the Node B. Then the Node B starts downlink transmission. The following illustration shows the newly created signaling radio bearers after the creation of the RRC connection.
Radio access bearer The service that the access stratum provides to the non-access stratum for transfer of user data between UE and CN. Consists of radio bearer service and Iu bearer service. Radio Access Bearer establishment This example shows the steps involved in the establishment of a Radio Access Bearer. FP UL Synchron. The Commit message indicates the Frame number at which the change should occur. Radio Access Bearer establishment The following illustration shows the newly created radio bearer after the creation of the Radio Access Bearer.
Contents Iub protocol structure Protocols of the Iub interface Iur interface Iu-cs interface Iub protocol structure The following illustration shows the protocol structure of the Iub interface. The radio network layer consists of a radio network control plane and a radio network user plane. Therefore, the radio network signaling and Iub data streams are separated from the data transport resource and traffic handling.
This resource and traffic handling is controlled by the transport signaling. The transport signalling is carried by a signalling bearer over the Iub interface. ALCAP is not responsible for signaling bearers, ensuring the separation of the two domains. User data is ultimately transmitted over these data bearers. Also SAAL connection management, link status and remote processor status mechanisms are provided. SSCOP provides mechanisms for the establishment and release of connections and the reliable exchange of signaling information between signaling entities.
It adapts the upper layer protocol to the requirements of the Lower ATM cells. AAL2 links are used to carry user plane data circuit and packet. AAL5 links are used to carry control plane data.
This topic provides a short explanation for each of them. Purpose This lesson describes when optimization is performed during a network lifecycle and the phases of the optimization process. Contents Network lifecycle Optimization process phases Planning and preparation site readiness Drive test optimization before live traffic Information gathering Information analysis The design is typically created using RF design software.
This translates the design in equipment in the real environment. This can mean that there are differences between the design and the planned site. The data from the planned site is used as input for optimization. This can mean that there are differences between the planned site and the completed site. The data from the completed site is used as input for optimization.
Data from the drive tests, together with installation and parameter data from the site, is used as input for optimization. If the customer accepts the network, the network goes live and commercial use can begin. In service optimization can result in the need to update the network design to include new cells, thus restarting this process. Purpose This topic shows the stages of the optimization process in a live network. Site readiness checks must have been performed before optimization starts.
Optimization process flow Optimization process flow: Begin Gather information Analyze information Optimization N problem? Y Sufficient N information? Result: Use automated computer tools to handle large quantities of complex data.
Result: For example, make sure the problem is not a fault. Result: Typically there are multiple solutions to solve a problem. Implement only one solution at a time. Focus on the problem and the solution that was implemented. Optimization starts when a network goes live and never stops. Circumstances in a live network always change and therefore optimization can not stop.
After an optimization problem has been solved, the optimization cycle continues, detecting and solving other optimization problems. Introduction Before optimization is performed, site readiness checks should be performed. These checks ensure that all cells are operating as required. Important: Site readiness checks are usually performed after a new network or new cells are deployed and before the network goes operational. When they have been performed and satisfactory performance can be guaranteed, the checks do not have to be made anymore.
Spectrum clearance Spectrum clearance ensures no external interference is present and sufficient guard bands are obeyed. Detection of interference can be very time-consuming and difficult once the UMTS system is up and running.
It is desirable to have a high degree of confidence that the spectrum is cleared prior to any testing. Antenna check Antenna checks ensure that the antenna system is properly installed. This includes basic call processing and handovers. Measurements are made on UMTS signal levels to verify that each sector is transmitting with the appropriate power levels and the correct scrambling code.
The sector verification tests are used to detect hardware, software, configuration and parameter errors. The sector tests are performed using measurement software including a UMTS test terminal. Once all data from the sector tests have beencollected, the measurement data can be post-processed.
If sector problems do occur, they need to be remedied and the tests repeated until they are successful. Baseline existing system The objective of baselining the existing system is to collect the RF performance metrics of the existing UMTS system equipment. Baseline driving should be performed prior to any RF optimization activity and involves measuring the Key Performance Indicators.
It is important to keep the drive routes and KPIs identical for performance validation and comparison purposes. Purpose Before a network takes on live traffic, an optimization using drive tests is usually performed. These drive tests are performed to correct problems and to prove that the network meets customer requirements.
Stages This illustrates optimization steps that are performed before a network is commercially deployed This ensures all cells are operating as required. Ensure the system and tools are ready and available for drive test optimization. Result The network is now ready for live traffic testing which leads into commercial service. Information sources As much information as possible should be used as input for optimization, so multiple sources of information are needed.
Information from one of these sources, can trigger further investigation. During the more detailed investigation information from other sources is gathered.
Key performance indicators Key performance indicators KPI are used to determine if the network complies to the levels of performance that are needed. Changes in values of the key performance indicators, especially reaching thresholds are often the first indication of an optimization problem.
Drive tests Drive tests can be used to gather information in the network. A drive test can be performed to gather information about a specific problem or problem area. Drive tests can also be performed to gather general information about the network performance.
Customer complaints Customer complaints can provide an indication of problems. Purpose Analysis of the information determines: 1. Whether there is an optimization problem 2. The source of the problem 3. Possible solutions for the problem 4. Consequences of implementing a solution. Role of an engineer The knowledge and experience of an engineer is an important tool in analyzing data. An experienced optimization engineer has detailed knowledge of how processes and protocols in a network work.
This allows the engineer to link information and events to a common source. An experienced engineer can even relate events to a single source, that do not seem to relate to each other. The engineer can identify possible sources of a problem, solutions that can solve the problem and predict consequences of a solution in a general way. Data analysis software tools Because of the scale and complexity of a network, engineers are not able to handle the large volumes of detailed information that is available.
Engineers can use software tools to handle the information and determine if there are problems. Software tools can also be used to determine the consequences of implementing a solution in the network. Using models, software can simulate the impact on the network of implementing a solution. Commercially available and proprietary tools are available to analyze information and determine impacts. Purpose Contents Drive test optimization process Planning and preparation site readiness Optimization planning Perform cluster optimization Perform system verification Purpose Before a network takes on live traffic, optimization using drive tests is usually performed.
Stages The following is the optimization process that is performed prior to a network being commercially deployed Introduction The optimization planning phase ensures system and tool readiness for RF optimization before beginning the actual drive testing. Validate initial neighbor lists An important step in the RF optimization planning phase is neighbor list verification. The complete neighbor lists in the UMTS network are required to compare the neighbor relations with network design plots.
Neighbor relations need to be verified for recent updates, validity and appropriateness. The recommended strategy is to have a minimum number of neighbor relations in the neighbor lists. Tool readiness The drive test and post-processing tools need to be prepared for optimization.
Define clusters Approximately cell sites should be combined into one cluster. The actual number used is based on network expansion as well as on the topographical environment. The clusters are selected to provide a center cell site with two rings of surrounding cell sites as shown in the figure below. It may be worthwhile to utilize natural barriers such as hills and water bodies for cluster separation to minimize overlap and influence between the clusters.
A little cell site overlap should remain between each cluster to ensure continuity across the boundaries. The following figure shows Planning drive routes for Sector Verification Each cell site is driven approximately around the entire cell site. Sector drive routes usually do not require customer approval. Planning drive routes for Cluster Optimization The routes for Cluster Optimization should consist of major roads, highways and hotspots.
Total time to drive all routes in a typical cluster should be approximately 6 to 8 hours. One control route per cluster is chosen to verify system performance. A control route is a subset of the optimization route and should be limited to about 1 to 2 hours.
Additional border routes are chosen to verify system performance on overlapping cluster regions. A border route is chosen by the way it crosses the cluster borders without going into the cluster areas. Planning drive routes for System Verification. The System Verification drive routes are used to collect the metrics for the Exit Criteria. The routes are a combination of the cluster control routes and routes between the individual clusters.
Introduction RF optimization execution consists of drive tests, problem area identification, verification drives, and final drives to ensure completion of exit criteria. The core activity is to provide system tuning, as well as data collection and reporting. Design changes relating to cell site layout modifications or adding a new cell site may be considered if critical coverage holes are discovered during optimization. Antennae corrective actions are more frequent for new deployments, such as Greenfield or Overlay scenarios.
Fine tuning of the transmit powers is the most effective procedure in already optimized networks. Cluster size Cluster optimization consists of procedures performed on geographical groupings of cell sites that are large enough to have meaningful multi-cell site optimization.
Several factors make it worthwhile to optimize the system in manageable sized clusters. There is a better focus on the area optimized, as smaller sector numbers make it easier to track the parameter changes and the impact of their performance. Another benefit to smaller cluster optimization is that multiple teams can optimize different clusters simultaneously.
Each team is able to maintain focus on its cluster with minimal impact from other teams. In addition, smaller cluster optimization aids in speeding up the system tests for commercial operation. Optimization in equipped clusters can proceed simultaneously with installation of other clusters.
When to perform cluster optimization Cluster optimization should be performed for network sections that are fully deployed.
This avoids a re-testing of already optimized clusters in case cell sites are later integrated. All cell sites in the network or a network section are switched on. Each cluster is tested under unloaded and loaded conditions. If live traffic exists, cells in the tested clusters must be barred for all users except for the test users optimization team.
It is recommended to finish the unloaded cluster tests for all clusters within the network or network sections before continuing with the loaded cluster tests. After a small set of adjacent clusters pass the exit criteria, a border exit drive must be performed. The border exit drive is performed under loaded conditions in order to verify and confirm the exit criteria at the borders of the clusters.
In addition to the phone-based tool kit, the scanner-based tool Agilent can be used during cluster optimization. The Agilent scanner is an important tool due to its multiple pilot measurement capability, which is especially useful for more in depth coverage analysis e. Once the data from the first phase is collected, problem spots are identified and optimized.
The unloaded drive test identifies coverage holes, handover regions and multiple pilot coverage areas. It also spots possible overshooting sites where interference is minimal from areas belonging to neighbor clusters. The drive test information highlights fundamental flaws in the RF design under best-case conditions. Loaded cluster optimization The second cluster optimization phase is performed under loaded conditions. The drive routes for the loaded cluster optimization are exactly the same routes as those used for the unloaded measurement drives.
The objective is to fix the problems observed by the field teams. This involves the fine-tuning of RF parameters such as the transmit power or handover parameters. Antenna re-adjustments e. Problematic cluster Problem areas may be re-driven after implementing changes.
It is not recommended to drive a problem area more than three times. If the problem cannot be solved after three test drives, either a root cause analysis is performed or cluster optimization proceeds with the next cluster.
It is generally not recommended to attempt resolution of complex, time-intensive performance issues, such as location-specific problems like cell site equipment failures. For such problems, it is advisable to report the behavior and proceed with the next cluster. The problem cluster can be verified at a later stage.
Cluster performance verification In the third phase, the cluster performance is measured against the cluster exit criteria. The final statistics from the cluster exit drive are presented to the customer for approval. These statistics contain plots as well as data in tabular form.
The approval to exit the cluster is based on the terms of the contract. Approval with exceptions allows the cluster to be exited under the condition that any problems will be resolved during system wide optimization. If the cluster is not approved, loaded cluster optimization must be continued until the troubles are resolved.
A report specifying the reasons why the exit drive did not pass the exit criteria is required. The final phase System verification is the final phase of the RF Drive Test Based Optimization activity and it focuses specifically on collecting overall performance statistics.
System verification begins after all clusters in the UMTS network have been tested. It is performed under loaded conditions with all cells activated. System verification involves fusion of the previously optimized clusters and once again is required to demonstrate that Exit Criteria are met system-wide. A comprehensive drive test System verification is a comprehensive drive test covering the major highways and primary roads in the defined coverage area.
There is a focus on the problem areas identified during the Cluster Optimization system verification driving routes. The procedures and analysis are identical to those used in Cluster Performance Verification. Performance data will be collected and statistics will be made to characterize coverage and performance over the entire network.
The system drive routes should not be used for optimization. System drives do not allow changing parameters due to side effects. Optimizing a system route can result in very good performance on the system verification driving routes but poor performance elsewhere.
System optimization is a continuation of Cluster Performance Verification. The main difference is the larger contiguous area of coverage. Problem areas Specific problem areas identified by the system verification will be addressed on a case-by-case basis after the entire drive has been completed. Individual Cluster Optimization drives are used to fix existing coverage problems by adjusting transmit powers and neighbor lists. In extreme situations, handover thresholds, channel power parameters or other low tuning parameters may require modification.
After any parameter changes are made, another drive test must be completed to ensure the surrounding regions are still performing properly.
Ready for live traffic The final statistics from the system verification phase are presented for approval. The same tools that were used for Cluster Optimization are used for the system verification phase. At the end of the system-wide drive test phase, the RF Optimization procedure is considered complete.
The UMTS network is ready for live traffic testing leading into commercial service. Once significant loading with live traffic is present on the It is possible for problem areas to remain after system verification is complete. An example would be a coverage hole that will be fixed by a future cell site addition.
Such items must be well documented with alternative solutions proposed. Purpose Contents Chapter 7, UTRAN key performance indicators Chapter 8, Call availability optimization and troubleshooting Chapter 9, Call reliability optimization and troubleshooting Chapter 10, Call quality optimization and troubleshooting Chapter 11, Call mobility optimization and troubleshooting Chapter 12, Throughput optimization and troubleshooting What are Performance Counters?
The Performance Counters are metrics that may be used to assess the performance of process steps within a UMTS network. Performance Management Performance Management PM is used to schedule the collection and transfer of performance data.
Performance Measurement scheduling The measurement schedule specifies the time frames during which the measurement job will be active. What are Key Performance Indicators?
Such assessments may be used as a general health check on a network, or in a warranty situations where it is important to ascertain whether the deployed network is achieving a level of performance consistent with the customer design requirements. The Key Performance Indicators are clear, simple, unambiguous and measurable metrics on which the vendor can commit with the customer during the contracts definition and can be asked to demonstrate their validity on live networks.
PM counters and KPIs are powerful measure to evaluate the performance of wireless networks. They are subtracted from the attempts. Fail to the MSC. It determines the quantity to be used for measurements of the UMTS. SuccOutCS are incremented accordingly. Handover is triggered too early. A handover to GSM is performed Call may drop. This is necessary to regard for the time that is required to execute the handover to GSM and the movement of the UE.
Handover is triggered too late. How can I optimize the network access procedure for both, minimum delay times and minimum interference. What is the optimum configuration of the different RLC counter and timer values e.
Max-DAT, timerPoll, transmissionWindowSize, … to provide the best possible service for transparent, unacknowledged and acknowledged operation modes. Network operator staff who are involved in the optimization of UTRA and who need to continuously improve the network performance. System vendors who are involved in second and third level troubleshooting activities. TEMS is desirable.
0コメント