ОРДЕНА ТРУДОВОГО КРАСНОГО ЗНАМЕНИ ПРОЕКТНЫЙ ИНСТИТУТ ПРОМСТРОЙПРОЕКТ ПОСОБИЕ 4.91 к СНиП 2.04.05-91 Противодымная защита при пожаре (2 редакция ) Москва , 1992 г. ОРДЕНА ТРУДОВОГО КРАСНОГО ЗНАМЕНИ ПРОЕКТНЫЙ ИНСТИТУТ ПРОМСТРОЙПРОЕКТ ПОСОБИЕ 4.91 к СНиП 2.04.05-91 Противодымная защита при пожаре (2 редакция ) Главный инженер института И. Б. Львовский Главный специалист Б. В. Баркалов ………………….. М о с к в а , 1992 г. Пособие 4.91 к СНиП 2.04.05-91 «Противодымная защита при пожаре» одобрена техническим советом и введена в действие институтом Промстройпроект. Рецензент - доцент кафедры «Пожарной безопасности в строительстве» Высшей инженерной пожарно-технической школы МВД РФ, доктор техн. наук Есин В. М. Редактор - инженер Агафонова Н. В. С введением в действие второй редакции «Пособия 4.91» утрачивает силу первая редакция данного пособия. Настоящее «Пособие к СНиП 2.04.05-91» защищено авторским правом, не должно воспроизводиться или использоваться никаким способом и никакими средствами - электронными или механическими, включая фотокопирование или информационные фонды и системы выдачи, без письменного разрешения института Промстройпроект. ПЕРЕЧЕНЬ ПОСОБИЙ к СНиП 2.04.05-91 «Отопление, вентиляция и кондиционирование» 1.91. Расход и распределение приточного воздуха 2.91. Расчет поступлений теплоты солнечной радиации в помещения 3.91. Вентиляторные установки 4.91. Противодымная защита при пожаре 5.91. Размещение вентиляционного оборудования 6.91. Огнестойкие воздуховоды 7.91. Схемы прокладки воздуховодов в зданиях 8.91. Численность персонала по эксплуатации систем отопления, вентиляции и кондиционирования 9.91. Годовой расход энергии системами отопления, вентиляции и кондиционирования 10.91. Проектирование антикоррозийной защиты вентиляционных систем
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
This document describes the scope of work and the procedures to be followed by Ericsson Authorized Service Provider Radio Engineers during service delivery of Initial Tuning at Telkomsel network.
The document is written to create a common understanding in terms of what steps are needed in order to successfully deliver this service
Initial Tuning consists of the following main activities that are covered by this chapter:
• Preparation
• Data Collection
• Analysis
• Reporting
The prerequisites, activities and results of the initial tuning service are summarized in table below. The prerequisites specified below are the requirements that have major impact on the service performance. The final results of the initial tuning are documented in the initial tuning reports (analysis report and verification report). These reports are used as input to the acceptance sub-process. After presentation of initial tuning reports the customer should issue KPI certificate
INITIAL TUNING
PREREQUISITES ACTIVITIES RESULTS
• Sites integrated, tested and in working condition
• Radio Network Design and Network Data implemented
• New feature have been implemented and verified
• Preparation • Data Collection • Analyzing/Change
proposal • Reporting
• Verification that the critical items have been cleared.
During the preparation phase, the following activities are typically carried out: • Radio Network Audit (Consistency Check) • Defining Drive Test Routes and preparing Drive Test schedule
The purpose of consistency check is to find inconsistencies in the network and fix them prior to drive testing. By fixing inconsistencies, time can be saved and the tuning process can be shortened. In order to perform the design/consistency check, network configuration data should be collected through OSS
3.1.1 New Node B
In general parameter new site integrated will be refer to recommended value of user description Radio network parameter unless new guidline has been published by Telkomsel RNP department. Below are major parameter that should be cheeked :
In Telkomsel project there are a lot of upgrade activity such as IuB Upgrade, CE upgrade and feature upgrade. Below are LKF and parameter that should be cheked on every activity:
3.1.2.1 IuB Upgrade
On IuB Upgrade activity, unless upgrade from IuB over E1 to IuB over IP there is no license to be cheked. Parameter that should be modify when upgrading IuB either VP bandwidth or VC bandwidth. New parameter will be refer to ATDN since every region will have traffic profile each self. Please see ATND read me as file below as reference to do modification :
For every IuB upgrade, need to follow new port assignment to which ET board at which NE (RXI or RNC) this Node B is connected and depends on the final E1 configuration.
VP/VC Numbering
IuB upgrade might lead to different configuration of VC, additional VC might need to be added depends on the final E1 configuration. Example: VP/VC Numbering for IuB upgrade from 4E1 IMA to 8E1 IMA must follow VP/VC table for Node B 8E1 IMA ATM Traffic
Descriptor
Traffic Descriptor
For every IuB upgrade there is an adjustment in the traffic descriptor depends on the final E1 configuration. Example: Traffic Descriptor for IuB upgrade from 4E1 IMA to 8E1 IMA must follow Traffic Descriptor for Node B 8E1 IMA
Other parameter that should be change when doing upgrade is MaxHsRate. New value it will be depend of number of E1. please see table below to find new value of MaxHsrate parameter.
Possible Value Radio Paramater RBS Unit= E1/IP
IuB User/Control Plane MO Class Name Paramater Name
On CE upgrade activity these 2 LKF should be cheek and the value should be refer to PO upgrade.
• FAJ121072 RBS Channel Elements Uplink
• FAJ121073 RBS Channel Elements Downlink
Beside cheek those LKF, CEDH value should be cheek also since upgrade not only software but also hardware. Figure below is snapshoot of CEDH result. Please see value after slash on usedCEdlr or usedCEul
QoS activation feature, LKF that required will be as list below :
• FAJ1211093 Flexible Quality of Service and Allocation/Retention Handl.
• FAJ121425 Max Bit Rate Capacity for QoS Profiling
• FAJ121966 Configurable Transport Bearer QoS Class
• FAJ1211115 HSDPA QoS Scheduler
• FAJ1211091 HSDPA Max Bit Rate for QoS profiling
• FAJ1211094 HSPA Traffic Handling Priority Support
• FAJ1211111 EUL QoS Scheduler
Until this guideline being made thee is a agenda to change parameter schweighting as guideline from RNP. But since not being formal yet, value of parameter schweighting still use default value
Network performance data can be collected from two different sources. The first one comes from TEMS Investigation (drive testing) and the second one comes from OSS
4.1 Drive Testing
Drive test in general, is performed for the following services:
It is important that prior to the start of the drive test, check that all cells in concerned site&neighbours are operational and allowed for access. Ensure that no other activities are planned in the site during the drive testing. Bring along the drive test route map for navigation purpose, or load the drive route in the PC and navigate with the help of GPS. Get the correct frequency number for the scanner to measure on.
Basically, two detailed drives will be performed for each cluster:
Initial drive test. This is the baseline drive which will be used to clean up the pilot environment by making physical changes (e.g. antenna azimuth and tilts), optimize neighbour lists, and resolve system issues. Trouble spots will also be defined. Dropped and blocked call analysis will be conducted.
Verification drive test. This is the comparison drive to evaluate network improvement from the baseline and identify further issues. Detailed Dropped and Blocked call analysis will also be conducted and trouble pots will be refined and focus on.
During drive tests, two types of measurements can be performed:
• For scan mode, the CPICH of the sites in the cluster will be scanned.
• For dedicated mode, different type of calls should be performed:
1 Short periodic calls to evaluate the accessibility performance. The purpose of this test is to ensure that calls can be originated from all cells on the network and to measure the Call Setup Success Rate (CSSR) as well as the Call Complete Success Rate (CCSR). A speech/video call can be set up every 50 seconds, with an interval of 10 seconds.
2 Packet calls with a HSDPA/EUL data card/UE will be used to gather packet data related information from a user perspective e.g. average throughput. This should also include R99 packet services.
The long and short calls can be performed concurrently by means of two or more TEMS UEs per service type. The short call UE has to be configured to make a large number of calls during drive test. If for any reason a call is disconnected, a new call shall be generated immediately. If during the tests the test vehicle is stationary for longer than a few seconds, the log file should be paused or the associated values filtered out during post-processing. It is recommended to perform separate tests for voice and data. Voice drive-test should be performed and visible problem like missing neighbour, RF issues etc. should be implemented before doing the Packet service (R99, HSPA) drive-test.
4.2 Equipment Needed For Drive Testing
During the drive test, the vehicle will be equipped with the measurement hardware. The following equipments will be used for one team during a drive test route for voice, video or packet data:
• TEMS Scanner (including GPS) • 2 TEMS UEs (one for long call, one for short call) • 1 HSPA capable UE (e.g. Qualcomm TM6275) • SIM card for the UE • TEMS investigation/TEMS-Planet license key • Data collection PC - PC with latest TEMS Investigation installed
5 Analysis
The collected data will be post processed in order to simplify analysis and to extract field measurement performance statistics for reporting. The analysis is mainly based on the collected data from TEMS (Scanner and UE logs) and UETR. The analysis can be categorized into RF and UE analysis.
RF analysis is based on the data from the scanner log files. RF properties in the network are focus in the analysis. UE analysis focuses on UE events. It looks into service impact related (e.g. blocked call, dropped call) problems in the network. Analysis phase helps to identify problematic areas in the network. For every problem found during the analysis phase, a solution shall be proposed and/or performed. The analysis work flow is shown in Figure 1.
For change proposal, generally there are soft change (parameter) & hard change (tilting, pan antenna, etc.) A change request co-ordinator is suggested to tracking on the change request issued, 3G/2G neighbour list database, etc.
Analysis phase will be done iteratively with each drive test conducted. This is done till the tuning objective is achieved.
If this service will be followed by acceptance of the network and the acceptance criteria are specified for the customer then the relevant parts of the contract should be used as evaluation values. If the customer acceptance criteria in the contract are missing or are vague, try to find out which performance criteria the customer considers most important.
In the case that, in the contract, acceptance criteria are defined for a loaded network, then the initial tuning should be performed as specified in the contract.
This method involves the following steps:
1. Drive Test analysis: Plot the RSCP and Ec/No plots in MapInfo. Analyzing the MapInfo plots to identify poor RSCP and Ec/No areas.
2. Network Optimization: Review the scanner data along these areas. Devise correction recommendations to improve the poor RSCP and Ec/No areas.
3. Validation: Verify through drive test after implementation of changes.
Prior to evaluating the site changes, it could be good to study the following (together with customer or similar RF person with site knowledge):
• Site photos (panorama) • The height of the antenna/building/surrounding buildings, obstructions or
risk for shadowing (not allowing excessive down tilt), antenna installation drawings and photos.
• The antenna type, currently settings of mechanical and electrical tilt.
Antenna radiation patterns (horizontal and vertical), the antenna radiation patterns are needed, including the maximum antenna gain.
5.1 RF Tuning Solutions
There are many solutions to improve the RF conditions of a network. The geographical areas in the cluster where the coverage or interference targets are not met or where the coverage or interference deviates from the design criteria should be analyzed and suitable recommendations should be devised.
5.1.1 Physical Change
The following are the possible solutions that can be done physically to the antenna to combat overshooting and other coverage and quality problems.
Antenna azimuth change
As the antenna azimuth is changed, the lobe is re-directed towards a new area; Coverage is lost in the main direction but improved in the new direction.
When changing the azimuth it is important to check that lack of coverage in some area is not due to some other obstacle, as an azimuth change will have little effect in such a case.
Interference may increase in cells along the new antenna direction
5.1.2 Pilot pollution
Pilot pollution is defined as having detected too many high power pilots as compared to Best Serving Pilot that do not contribute to the received signal. The UE has the ability to constructively use signals in soft/softer handover, all the other signals received that exceeds the Max Active Set (currently set as 3) act as interferers. This interference degrades the performance of the system. By importing data into MCOM, the output plots can be used to display the number of pilot polluter within certain margin of the best server, for example margin of 3 to 5 dB. MCOM gives also (Scanner or UE) Best Server Ec/No plot over the drive-test route (cluster). This is an easier way to identify area in the cluster suffering from pilot pollution.
There could be cases where RSCP is found to be good in a particular but at the same time poor Ec/No is found. This may be due to too many overlapping cells in the same area. This is illustrated in Figure 2.
If there are only one or two polluting pilots, their coverage area could easily be reduced by down tilting them. However, in some occasions down tilting several cells to remove pilot pollution might not be feasible. Instead, improving the best server cell could possibly be the better choice in this case. This is done by increasing the P-CPICH power of the desired cell. The result is illustrated in Figure 3.
Figure 3, Desired Cell Pilot Power Increased
However, this will create pilot coverage imbalance problem in the area. The UE will transmit higher power in the desired cell as it might not be connected to the closest cell in term of path loss. This will increased the uplink interference level in the carrier.
As the pilot power of the cell increases, the power of the common channels in the desired cell also increases as their settings are relative to the pilot power. This means that overall the control channel power is increased and less power will be available for traffic in that cell. This may lead to admission and congestion issues when the cell load is high.
Overshooting of the desired cell may also occur and thus create another problem. After increasing the P-CPICH power, it is necessary to verify performance both in the area where improvement was intended as well as in the ordinary coverage area of the cell.
5.1.3 The guideline to add neighbours are as follows: • To define neighbours, factors as cell coverage and distance between
sites are taken into consideration. • It is a good design practice to keep the neighbouring cell list per cell not
more than 20.
• Use a SC plan (preferably implemented prior to the scanner
measurements) with as many unique SC as possible. This reduces the time for analyzing and identifying SC of the originating cell.
Instead of adding many neighbours, it might be more beneficial to try to reduce the coverage area of the cell by other methods. While doing so, the need for neighbours will decrease and the interference situation might improve. As new sites are brought into operation, the neighbour list must be reviewed, as new neighbour relations are necessary and old neighbour relations can be removed. When neighbour relations are removed, the consequences should be verified.
5.2 Service Performance Analysis
5.2.1 KPI (Key Performance Indicators)
KPIs are used to correctly reflect network performance as perceived by the subscribers. KPIs also serve a tool in Initial Tuning exercise. Under Service Performance Analysis, KPIs are address under the following three main areas:
Accessibility performance is better analyzed through UE events. Poor accessibility may occur under various circumstances. It may come from
• hardware limitation such as lack of CE (Channel Element),
• Access Transport resources,
• Software Control (i.e. Admission control)
• poor RF conditions.
5.2.1.2 Retainability
Retainability is defined as the ability to retain a connection already established until terminated by the user. During Initial Tuning, drop call rate due to RF conditions will be the main focus. These RF conditions include:
• Poor RSCP and/or Ec/No which might lead to unnecessary high UE Tx Power, out of uplink coverage.
• Drop Call could also take place due to Congestion Control. Under Congestion Control, even guaranteed service such as Voice call could also be dropped. From the drive test, following symptoms will be observed by using TEMS and UETR:
5.2.1.3 Integrity
The common measure of Integrity is PS Throughput performance. The PS R99 throughput performance is measured through uploading and downloading of a file to and from a FTP server. Throughput values vary depending on the layer that is being measured. One of the more common throughput measurements is made on Application level which is also known as the TCP layer. Another common layer to read throughput is the RLC layer..he different layers between the UE and the IP nodes.
TCP Slow start – At the beginning of a new session (or after severe packet losses), TCP will typically set the window size to one. At the arrival of each acknowledgment, the congestion window size is doubled. Thus the transmission rate is increased exponentially at TCP slow start
Congestion avoidance – TCP interprets packet loss as a sign of congestion. As soon as a packet is lost or out of sequence, TCP will reduce its data transmit rate by 50%. The transmission rate is then increased linearly (window size increased by one TCP/IP segment) until further packet loss occurs.
Packet size – The TCP/IP packet payload has a typical maximum size of 512 bytes but is often up to 1460 bytes long. Since an acknowledgement is needed for each packet transmitted, a higher throughput can theoretically be achieved by increasing the packet size. This is mostly due to the increased amount of information that can be sent until an acknowledgement is needed and partially due to the reduced header overhead.
Round trip time – A TCP transmitter will never send more than a limited number of packets (TCP segments) unacknowledged. This number is defined by the congestion window size. The transmitter will then stop transmitting until an acknowledgement of the first packet has been received. This implies that if the round trip time increases, throughput will decrease.
1. Buffer Load: The buffer load is defined as the minimum of the radio link control (RLC) transmission window and the sum of bytes in the SDU buffers and retransmission buffers of some of the RLC instances (each interactive RAB connection consists of five RLC instances.
2. Throughput: Uplink throughput is defined as the number of bits received to the RLC layer from the MAC layer. Downlink throughput is defined as the number of bits transmitted from the RLC layer to the MAC layer. The RLC instances to be considered for the buffer load and throughput measure depends on the UE state and the algorithm using the measure.
3. DL transmitted code power: DL transmitted code power is defined as the downlink power of the pilot bits of the DPCCH field.
In terms of identifying poor throughput performance, plots of both UL and DL throughput can be produced for analysis purpose. The common reasons for low throughput are listed below:
Poor Radio Links
Poor radio links results in more error bits in a packet. In order to recover the packet, AM RLC retransmits the problematic packets. However, too many retransmissions cause longer Round Trip Time (RTT) and the average throughput will consequently decrease. The solution is to improve the coverage and network quality to minimize number of retransmissions.
6 Reporting
When the site has been tuned, a final drive test will be performed. The coverage and network quality performance after initial tuning activity will be presented. All improvement, findings, changes and outstanding changes are documented in a Final Report that will be handed over to the customer. Final report should be consist of :
• Short explanation of the selected radio network performance measurements
• Recommended target levels • The results of the system design check, and which modifications that
were carried out, or that are proposed. This can be presented on a cell level
• Any other proposed, or performed modifications • Tables and figures that illustrate the results (drive tests and OSS-RC
measurements) • Attached signal strength plots (and perhaps BLER plots) from the drive
The initial tuning service shall be conducted and completed for each site independently. The service is considered completed successfully when the the tuning final report on the cluster performance is delivered and KPI certificate has been sign off by Telkomsel representative. Below are the format of KPI certficate