WCDMA优化案例

nullnull覆盖优化及控制 案例 全员育人导师制案例信息技术应用案例心得信息技术教学案例综合实践活动案例我余额宝案例 介绍覆盖优化及控制案例介绍1. 不合理的小区覆盖将会给网络带来诸多的实际问题，如： 覆盖盲区 网络不连续覆盖，局部区域服务品质差，无法保证服务的完整性，及系 统资源的浪费。 导频污染 5dB的窗口内，3~4个小区重复覆盖情况，或者说满足软切换门限的导频 信号，受限于软切换集容量而无法进入软切换状态，就成了导频干扰。 导频污染会降低下行覆盖的信号质量，无法保证服务的完整性，造成系 统资源的浪费。 优化思路： 确定并增强主控小区覆盖 减弱非主控小区覆盖 3. 主要 措施 《全国民用建筑工程设计技术措施》规划•建筑•景观全国民用建筑工程设计技术措施》规划•建筑•景观软件质量保证措施下载工地伤害及预防措施下载关于贯彻落实的具体措施 ： 天线的物理参数优化（天线方位角，俯仰角，天线挂高等） 导频功率的调整（需谨慎）覆盖盲区优化典型案例 覆盖盲区优化典型案例 中心基站华福(ID=51017)关闭以后，对覆盖区的路线进行了测试，测试发现网络中存在的覆盖相关问题主要在图中红圈标出地区发生。 1243null 华福站关闭以后狮山路上原来由51017B、C 覆盖的区域失去了主覆盖小区，形成覆盖空洞，周围小区从远处覆盖过来的信号电平很低且Ec/Io也比较差，如图所示： null弥补覆盖空洞的思路是寻找主覆盖，从图可以看出，可能为该区域提供覆盖的小区是573A，596C或5993C。1.首先排除573A，因为狮山路南侧有很多高层建筑遮挡，573A的信号只有在建筑物的间隙中漏出零星的信号。2.其次排除596C小区，因为勘查发现596在正对51017（华福）的方向被狮山路北侧密集的高层建筑遮挡，无 法改善该路段的覆盖。3.最后考虑改变5993的小区方向，有两种 方案 气瓶 现场处置方案 .pdf气瓶 现场处置方案 .doc见习基地管理方案.doc关于群访事件的化解方案建筑工地扬尘治理专项方案下载 可以考虑： 一、调整5993C小区到300度左右，然后把5993B小区天线转到原来5993C小区的方向来弥补5993C原来的覆盖区。 二、调整5993A小区到300度左右，然后逆时针方向适当调整5993B小区的天线来弥补原来5993A小区的覆盖区。 考虑到5993B小区仍然需要覆盖河对岸部分区域，不合适做大幅度天线方向改动，因此采用第二种方案。调整天线方向以后，该路段复测结果如下图所示： nullnull优化方案列 表 关于同志近三年现实表现材料材料类招标技术评分表图表与交易pdf视力表打印pdf用图表说话 pdf null优化前：优化后：新开站后导频污染 新开站后导频污染 开启51017基站以后，在该基站的覆盖区内存在较多的导频污染，需要优化解决。以下是路测中发现导频干扰区域的示意图： 1237456导频污染优化列表导频污染优化列表导频污染优化续表导频污染优化续表 通过以上优化，经测试，七个导频污染区域基本上已不存在导频污染问题。 开站优化前后性能指标对比开站优化前后性能指标对比优化前：优化后：覆盖空洞优化结论覆盖空洞优化结论 闭站后网络的主要问题在于覆盖的空洞，其它诸如切换、导频等问题也是源于覆盖的不足，通过覆盖调整、导频污染消除以及切换优化后，网络的总体覆盖情况（RSCP&Ec/Io）可以得到改善。 开站后网络的主要问题在于在提高覆盖的同时，还增加了系统的干扰，反而降低了网络的整体性能，造成严重的导频污染，可以通过基站方位角/俯仰角调整、导频功率优化以及切换优化来提高网络的整体质量。 因此，WCDMA网络覆盖空洞优化效果最为明显的为天线方向角和倾角（机械、电子）调整、导频功率参数修改以及切换优化等手段。 null邻区关系优化案例介绍Generally, 3 kinds of problem are associated with Neighboring Relations : Missing Neighboring Cell Definition (Real DN) Missing Neighbor Due to Truncated Neighbor List (only happen during soft HO and DN not reported) Corrupted Neighboring Relation Definition (in RNC) Any Neighbor Problem caused by any of above mentioned reasons can degrade system service quality. Optimization On Neighboring Relation is a very important part amid WCDMA RAN Tuning.Missing Neighbor Detection In TI 9.0 (using Scanner)Missing Neighbor Detection In TI 9.0 (using Scanner)Once a cell definition file has been loaded, Generation of an event detecting (probable) missing neighbors become available in application.Triggered in the following cases: A cell not defined as a neighbor of the strongest cell is more than 3 dB stronger than at least one neighbor of the strongest cell. A cell not defined as a neighbor of the strongest cell is within 3 dB of the strongest cell. (The event is then triggered regardless of the strength of defined neighbors.) No cell from the strongest cell's neighbor list is detected, but at least one cell is detected besides the strongest cell. (The event is then triggered regardless of the strength of that cell.) Example: Detecting Missing Neighbor (using TI)Example: Detecting Missing Neighbor (using TI)In TI, when you load in the Cell file (with complete Neighbor Relation information), And conduct a drive test with SCANNER- Missing Neighbor Events will be generated if the Scanner detects a SC which is >= 3 dB of any of the measured Neighbors of the Strongest SC.1. Strongest SC:2882. SC 48 is defined as Neighbor to 288 BUT SC 0 if >=3dB than SC 48 causing a Missing Neighbour Event This ‘Missing Neighbour Event’ may be misleadingnull1. Detected Neighbor Case2. 456 is measured by the Scanner but is not in the Monitored Set of the UE. Could be a missing neighbour.or a not monitored Neighbour.3. Missing Neighbour Event We have to view ‘Event Report’ to see the SC of missing neighbour.Detected Neighbor (DN)nullWhat is “Truncated Neighboring List”? The Network will send a list of SCs for the UE to scan-This list in called the MONITORED SET list (in TI its noted as Monitor Neighbour (MN) )SCaSCcSCbASSC_aSC_bSC_cMonitored SetMAX 461. Remove Active set SCs2. Remove duplicatesCreating Monitored setnullMissing Neighbor CasenullMissing Neighbor (Corrupted Neighbor Relation Case)This HO problem existed between 2 cells which belong to same RNC, neighbor relations between 2 cells were carefully checked and confirmed, and also no hardware fault found… This problem lasted for pretty long time, and finally solved by finding of above showed “corrupted neighbor relation definition”.This HO problem existed between 2 cells which belong to same RNC, neighbor relations between 2 cells were carefully checked and confirmed, and also no hardware fault found… This problem lasted for pretty long time, and finally solved by finding of above showed “corrupted neighbor relation definition”.null4.3.3 UE Issues (ASUC not sent)nullLayer 3 Message案例介绍1、系统消息 2、呼叫建立 3、软切换 4、异频切换 5、IRAT切换 6、HSDPA Cell Change 7、Channel Switchingnull系统消息Layer 3 Message AnalysisLayer 3 Message Analysis无线连接建立鉴权加密无线承载建立呼叫建立软切换 流程 快递问题件怎么处理流程河南自建厂房流程下载关于规范招聘需求审批流程制作流程表下载邮件下载流程设计 软切换发起事件Event 1a/1c软切换发起事件Event 1a/1c软切换成功标志-Measurement Control软切换成功标志-Measurement Control异频切换-启动压缩模式异频切换-启动压缩模式异频切换-切换执行异频切换-切换执行IRAT切换IRAT切换HSDPA 主小区切换HSDPA 主小区切换UP SwitchingUP SwitchingDown SwitchingDown SwitchingBlock CallBlock CallDropped CallDropped CallThanks! Any questions?Thanks! Any questions?