移动公司网络分析和优化总结工作

1、广西移动柳州分公司网络分析和优化总结工作报告 TOC o 1-2 h z t 标题 3,3,标题 4,4,标题 4 + 宋体,4 HYPERLINK l _Toc82492285 一、概述 PAGEREF _Toc82492285 h 2 HYPERLINK l _Toc82492286 二、交换参数以及SIZE的检查和优化 PAGEREF _Toc82492286 h 3 HYPERLINK l _Toc82492287 1、SIZE介绍和检查 PAGEREF _Toc82492287 h 3 HYPERLINK l _Toc82492288 1.1、SIZE介绍 PAGEREF _Toc8

2、2492288 h 3 HYPERLINK l _Toc82492289 1.2、SAE 控制类型 PAGEREF _Toc82492289 h 5 HYPERLINK l _Toc82492290 1.3、对现网的SAE 进行优化，给出优化的流程和方法 PAGEREF _Toc82492290 h 6 HYPERLINK l _Toc82492291 2、交换参数的检查和优化 PAGEREF _Toc82492291 h 9 HYPERLINK l _Toc82492292 2.1MSC交换参数的检查 PAGEREF _Toc82492292 h 9 HYPERLINK l _Toc8249

3、2293 2.2MSC局间切换需注意的数据 PAGEREF _Toc82492293 h 14 HYPERLINK l _Toc82492294 2.3BSC交换参数的检查 PAGEREF _Toc82492294 h 14 HYPERLINK l _Toc82492295 三、无线参数的检查和优化 PAGEREF _Toc82492295 h 16 HYPERLINK l _Toc82492296 1、BSC 一致性检查 PAGEREF _Toc82492296 h 16 HYPERLINK l _Toc82492297 1.1、MSC中错漏的数据 PAGEREF _Toc82492297

4、h 16 HYPERLINK l _Toc82492298 1.2、BSC中错漏的数据 PAGEREF _Toc82492298 h 30 HYPERLINK l _Toc82492299 2、无线参数的检查和优化 PAGEREF _Toc82492299 h 42 HYPERLINK l _Toc82492300 2.1跳频功能的优化 PAGEREF _Toc82492300 h 42 HYPERLINK l _Toc82492301 2.2小区内切的检查和优化 PAGEREF _Toc82492301 h 44 HYPERLINK l _Toc82492302 2.3、SDCCH数量的优化

5、 PAGEREF _Toc82492302 h 44 HYPERLINK l _Toc82492303 2.4、上下行动态功率控制的检查和优化 PAGEREF _Toc82492303 h 47 HYPERLINK l _Toc82492304 2.4、小区定位参数的检查和优化建议 PAGEREF _Toc82492304 h 48 HYPERLINK l _Toc82492305 2.5、其它无线功能的检查和优化建议 PAGEREF _Toc82492305 h 52 HYPERLINK l _Toc82492306 2.6、参数概况 PAGEREF _Toc82492306 h 53 HY

6、PERLINK l _Toc82492307 四、网络指标分析 PAGEREF _Toc82492307 h 58 HYPERLINK l _Toc82492308 1、网络指标的收集 PAGEREF _Toc82492308 h 58 HYPERLINK l _Toc82492309 2、网络指标的分析 PAGEREF _Toc82492309 h 58 HYPERLINK l _Toc82492310 2.1、四个BSC上午忙时（10点）指标分析 PAGEREF _Toc82492310 h 58 HYPERLINK l _Toc82492311 2.2、四BSC指标同时段平均值对比 PA

7、GEREF _Toc82492311 h 61 HYPERLINK l _Toc82492312 2.3、四BSC中1800站统计 PAGEREF _Toc82492312 h 63 HYPERLINK l _Toc82492313 2.3.1、1800站10点指标 PAGEREF _Toc82492313 h 63 HYPERLINK l _Toc82492314 2.3.2、1800站17点指标 PAGEREF _Toc82492314 h 64 HYPERLINK l _Toc82492315 2.3.3、1800站20点指标 PAGEREF _Toc82492315 h 64 HYPE

8、RLINK l _Toc82492316 2.3.4、1800站掉话数走势 PAGEREF _Toc82492316 h 65 HYPERLINK l _Toc82492317 2.3.5、1800站掉话率走势 PAGEREF _Toc82492317 h 65 HYPERLINK l _Toc82492318 2.3.6、1800站话务掉话比走势 PAGEREF _Toc82492318 h 66 HYPERLINK l _Toc82492319 3、1800站与900站的指标对比分析 PAGEREF _Toc82492319 h 66 HYPERLINK l _Toc82492320 五、

9、基站数据以及硬件检查和故障处理 PAGEREF _Toc82492320 h 67 HYPERLINK l _Toc82492321 1、基站数据的收集和检查。 PAGEREF _Toc82492321 h 67 HYPERLINK l _Toc82492322 1.1基站数据的收集 PAGEREF _Toc82492322 h 67 HYPERLINK l _Toc82492323 1.2跳频类型BB与SY的选择 PAGEREF _Toc82492323 h 68 HYPERLINK l _Toc82492324 2、基站故障检查、处理和方法 PAGEREF _Toc82492324 h 6

10、9 HYPERLINK l _Toc82492325 2.1、基站故障的分类 PAGEREF _Toc82492325 h 69 HYPERLINK l _Toc82492326 2.2、基站隐性故障定义 PAGEREF _Toc82492326 h 70 HYPERLINK l _Toc82492327 2.3、发现问题的方法 PAGEREF _Toc82492327 h 70 HYPERLINK l _Toc82492328 2.4、基站隐性故障处理的一般方法 PAGEREF _Toc82492328 h 71 HYPERLINK l _Toc82492329 2.4.1、看基站当前的状态

11、及告警 PAGEREF _Toc82492329 h 71 HYPERLINK l _Toc82492330 2.4.2、检查基站传输的状态 PAGEREF _Toc82492330 h 74 HYPERLINK l _Toc82492331 2.4.3、检查并分析ERROR LOG PAGEREF _Toc82492331 h 76 HYPERLINK l _Toc82492332 2.3.4、 对基站进行检查 PAGEREF _Toc82492332 h 78 HYPERLINK l _Toc82492333 2.3.5、基站故障处理的其它方法 PAGEREF _Toc82492333 h

12、 80 HYPERLINK l _Toc82492334 2.4、关于时隙同步失败（TS SYNC FAULT）问题的分析 PAGEREF _Toc82492334 h 80 HYPERLINK l _Toc82492335 2.4.1、什么是TS SYNC FAULT 告警。 PAGEREF _Toc82492335 h 80 HYPERLINK l _Toc82492336 2.4.2、TS SYNC FAULT 告警产生的原理 PAGEREF _Toc82492336 h 81 HYPERLINK l _Toc82492337 2.4.3、对现网中存在的TS SYNC FAULT 告警的

13、分析 PAGEREF _Toc82492337 h 81 HYPERLINK l _Toc82492338 2.4.4、总结产生时隙同步问题的主要因素和处理方法 PAGEREF _Toc82492338 h 82 HYPERLINK l _Toc82492339 六、路测分析 PAGEREF _Toc82492339 h 83 HYPERLINK l _Toc82492340 1、测试概述 PAGEREF _Toc82492340 h 83 HYPERLINK l _Toc82492341 2、测试问题点及建议 PAGEREF _Toc82492341 h 83 HYPERLINK l _To

14、c82492342 2.1、问题地点1：红碑路木材厂路段 PAGEREF _Toc82492342 h 83 HYPERLINK l _Toc82492343 2.2、问题地点2：北雀路与红碑路交界 PAGEREF _Toc82492343 h 84 HYPERLINK l _Toc82492344 2.3、问题地点3：柳州柳微 PAGEREF _Toc82492344 h 85 HYPERLINK l _Toc82492345 2.4、问题路段4：东环路 PAGEREF _Toc82492345 h 85 HYPERLINK l _Toc82492346 七、总结 PAGEREF _Toc8

15、2492346 h 86一、概述本次柳州工程网优主要工作内容是对近期新开的1800站进行数据查错和参数优化并对相关的900站也进行优化，本次网优工程涉及的BSC有：LZBSC1、LZBSC2、LZBSC10和LZBSC12，涉及的MSC有LZMSC2、LZMSC7。本次网优工程预计用时一个星期左右，从9月1号到9月8号，本次网优工程基本分成四个部分：1、交换参数的检查和优化。2、无线参数的检查和优化。3、基站数据（MO数据）的检查和优化。4、网络指标的收集、优化和分析。5、DT测试的评估已经修改建议。本次网优工程网优的工作安排：日期工作内容天数人员9月1日 工程人员入场，召开项目开工会1项目全

16、体人员9月2日 网络数据的收集，网络属性的检查1陈健康9月3日9月5日网络数据的检查和优化3陈健康、何凌9月6日基站数据的检查和优化1陈健康、李勇9月7日DT测试及建议1何凌、李勇9月8日 网优工作总结报告的编写1陈健康、何凌9月9日 广西柳州工程网优最终工作总结报告会1项目全体人员二、交换参数以及SIZE的检查和优化1、SIZE介绍和检查1.1、SIZE介绍SAE-Size Alteration Event, SAE是AXE系统中一个基本的概念。AXE是一个电信级的多任务处理平台。宏观上看，系统在同一时间处理大量的业务，包括话务和系统的维护任务。在系统处理一个任务的时候，任务需要占用相当的记

17、录(RECORD)或者文件（FILE）,为了管理这些记录和文件，AXE引入了SAE的概念。SAE是为了管理AXE的数据记录和文件的一些事件，对于特定某个记录或者文件，有相应的一个SIZE ALTERATION EVENT与之对应，简称SAE。在系统内对不同的SAE分配一个SAE号。 SAE分两种，GLOBAL SAE和LOCAL SAE， 可以分别理解为全局SAE和局部SAE。对应着AXE系统的APZ和APT, SAE又可以分类为APZ的SAE和APT的SAE。对于一个LOCAL的SAE,需要同时使用功能块号(BLOCK NUMBER)和SAE号来标识，对于GLOBAL SAE,则只需要SAE

18、号就可以唯一标识。 下表是各种不同类型SAE的号码SAE SUB-GROUP每个SAE 有一个与其用途相关的类别(subgroup)。Subgroups 的目的只是SAE 一个的识别。Subgroup 类型包括: 与APZ 相关通常参考带中会定义SAE 的大小。 然而, 一些与APZ 相关的SAEs 有一个建议的标准值,但如果标准值不适合应用系统的要求,这一建议的标准值可以进行修改。 与硬件相关SAE 值的大小直接与交换机配备的某种硬件的数量有关。 与用户相关SAE 值的大小直接取决于用户的数量和用户业务。 与转换功能有关SAE 值的大小是取决于完成转换功能的需要, 如B-number 修正的

19、数量。 在交换机执行此类转换功能前, 这些与转换,翻译功能相关的SAE 必须定义。1.2、SAE 控制类型Software File Congestion Supervision(CONS1)The SAE is controlled by the application block reporting software file congestion。 The logical and physical size of the data files in the SAE arealways equal after a size alteration。 This SAE Control Type

20、 is defined by the system。Congestion Event Control(CONS2)The logical and physical size of the data files in the SAE are controlled by the application block reporting a congestion event。 The logical file size can be increased within the physical file size without operator intervention。 This SAE Contr

21、ol Type is defined in a SAE participant block。Program Control(PROGRAM)An application block controls the data file size by requesting the Size Alteration Event with a specified file size。 The logical and physical size of the data files in the SAE are always equal after a size alteration。 This SAE Con

22、trol Type is defined in a SAE participant block。Threshold ControlThe Audit function, Supervision of Utilization in Files and Memories, supervises the Size Alteration Event。 The logical and physical size of the data files in the SAE are always equal after a size alteration。(THRESH1)If the SAE Control

23、 Type is defined by the system then it is THRESH1。(THRESH2)If the SAE Control Type is defined in a SAE participant block then it is THRESH2。Manual Control(MANUAL)The size alteration of the SAE can only be controlled manually by commands SAAII and SAADI。 The logical and physical size of the data file

24、s in the SAE are always equal after a size alteration。 This SAE Control Type is the default。1.3、对现网的SAE 进行优化，给出优化的流程和方法综合以上的SAE 优化方法，总结的优化流程为：1，SAE 控制类型的检查，确保与话务敏感的SAE 的利用处于系统的监控下。2，对OBJECT TYPE SAE,LOSSROUTE 进行分析,检查其SIZE 利用情况。3，根据前文中的建议值进行相应的调整。以下是所有与话务敏感的SAE：GLOBAL SAE：GLOBAL SAEGLOBAL SAEGLOBAL S

25、AE1236166263267436446454487488493944945948949100110531081LOCAL SAE：SAEBLOCKSAEBLOCKSAEBLOCK500APC500AUIF500C7CLAN500C7CO500C7SRM500CHOF500CHOP500CHSTAT500CLCOF500COHW500COMAIN500COMES500COX500DJAMO500FAUSBUF500GAP500GAP3500GMAPVS500GRI500GRR500GSCTAP500GSMOSAP500GSMS500IA500IWASCAP500IWMOAP500IWSCAP

26、500IWSMS500MABC500MAPTC500MAUTH500MB500MCCC500MCDTMF500MCEDHC500MCISS500MCSE500MEC500MECAP500MFDAP500MHIC500MHO500MHOAP500MHOAP2500MHOC500MHOMH500MIWUC500MLCAP500MMAPVS500MMM500MMMCS500MMMLR500MPAG500MPROIAP500MPSIAP500MRESTAP500MRNAP500MRR500MRRM500MSCCO500MSDAP500MSDH500MSDH1500MSDH2500MSDH3500MSE

27、CAP500MSMMH500MSMO500MSMOAP500MSMPAP500MSMSCH500MSMT500MSMTAP500MSPUAP500MSRAP500MUSSH500MUATAI500MTRAP500MSSNOAP500MUSSPAP500MVLRP500MZONE500OBMAN1500SHTTM500SUPIA500TBLAD500TCECO500TCFICL500TCIA501C7CL501C7CO501MB502CHSTAT504MRNR527MCCMH527MCPPH527MLABT527MRRMH527MSCCL527MSMMH527MSSMH533TRAP600CHV

28、IEW600MCEDHC600SHCHM601CHVIEW601SHCHM602CHVIEW602MTVCF602MTVCUG602MTVIN602SHCHM603MTVCF603MTVCUG603MTVZONE604CHOF604CHOP604COHW604COX604DJAMI604DJAMO604SHCC604SHCG604SHCHM604SHCM604SHEC604SHMCS604SHMM604SHOPSRF604SHPM3604SHRDO604SHTD1604SHTD2604SHTD3604SHTD4604SHTD5604SHTD6604SHTD7604SHTD8604SHTDM60

29、4SHTRI604SHTTM605COX605SHCC605SHCM605SHEC605SHTRI606COHW607COMAIN608COMES622MTVIN645UPUIA647UPCNMHS648UPCNMHR500UPCNPC500UPCNPHM500UPCNPHS700C7TCP700SHINSRF700UPMON701C7TCP701SHOPSRF701UPMON702SHOPSRF703SHOPSRF704SHOPSRF775ASGTB 通过检查，LZ7MSC 局中的话务敏感SAE 中绝大部分为CONS1，CONS2，且状态均为ACTIVE，未发现异常。若在其他局发现有控制类型

30、有误的，可用下述命令进行调整：SADBI；SADBI 执行完后需要重新启动Automatic Size AlterationSAOCS：STATE=ACTIVE;但有几个SAE 是与话务有关的，其控制类型是MANUAL，即没有进行任何监控。具体如下：GLOBAL SAE：SAECNTRTYP166MANUAL454MANUAL LOCAL SAE：SAEBLOCKCNTRTYP500AUIFMANUAL500CHOPMANUAL500CHSTATMANUAL500TBLADMANUAL502CHSTATMANUAL608COMESMANUAL645UPUIAMANUAL700UPMONMANU

31、AL701UPMONMANUAL775ASGTBMANUALBSC几个重要SIZE的检查SAEBLOCKLZBSC1(R8)LZBSC2(R8)LZBSC10(R9)LZBSC12(R9)NINIUNINIUNINIUNINIU29830096320215512149512942994001774501735121365121791133(R9)51205120522RQCD30001182500040286000251860001026523RQCD1500706150097920485852048666从上表看出四个BSC的SIZE值的设置基本是正常的。2、交换参数的检查和优化2.1MSC

32、交换参数的检查 指令:MGEPP:ID=ALL;MSC 中的交换机属性，分别列如下面的表中：通过对两个MSC的参数的收集和对比作出以下调整建议：LZ2MSC:EXCHANGE PROPERTIES 目前 建议MSRNTCNTIME15030LZ7MSCEXCHANGE PROPERTIES 目前 建议MSRNTCNTIME15030HNDRELCHSUBNON10CWSTATETIMER4060从以上两表可见LZ2MSC的参数基本正确且已比较优化，LZ7MSC还有另外两个参数建议进行优化。调整使用的命令：MGEPC：PROP=；涉及到的属性：MSRNTCNTIME: 用于 MT 呼叫的 MSR

33、N 的分配监测时间（秒），如超时将释放呼叫的路由。（单位为1/5秒，300.6 秒）HNDRELCHSUBNON：定义的是在MSC切换时监测时间超时后是否释放原信道（subsequent handover innon-anchor MSC）。(0将不释放原信道并在原信道上继续通话。)CWSTATETIMER: 呼叫等待的时间（秒）。2.2MSC局间切换需注意的数据以下为越局切换需要的数据。EXROP：定义路由数据，这部分数据一般开局时已经定好。MGNMP：定义外部MSC，曾经试过定到这一步就已经能正常做越局切换了。MGLNP：定义Location Number。MGLCP：连接Location

34、 Number。MGCVP：定义协同VLR数据。C7SPP：可查本MSC以及相邻MSC信令点的数据，OWNSP为本MSC的信令点数据，重点检查本MSC内有无相邻MSC的SP DATA以及邻MSC里是否有本MSC的SP DATA。 C7RSP：查DEST通过检查柳州LZMSC2和LZMSC7 MSC局间切换需注意的数据正常2.3BSC交换参数的检查相关于在900M和1800M小区之间的切换功能:BSCSYSTYPETALLOCTURGENASSOCIBHOASSIBHOSICHIHOSICHLZ1GSM90022ONONOFF-ONOFF-ONLZ1GSM18006-24-2ONONONONLZ

35、2GSM90022ONONONONLZ2GSM180022ONONONONLZ10GSM90022ONONOFF-ONOFF-ONLZ10GSM180022ONONOFF-ONOFF-ONLZ12GSM90022OFF-ONONOFF-ONOFF-ONLZ12GSM180022OFF-ONONOFF-ONOFF-ON由上表可知四BSC中只有LZBSC2的BSC定位数据里切换是开启的，其它没开的已经开启ASSOCAssignment to other cell than serving cellIBHOSICHInter BSC handover on signalling channelIHO

36、SICHIntra-cell handover on signalling channelTALLOCTime between allocation attemptsTURGENTime between allocation attempts when urgencyBSC 属性指令：RAEPP:ID=ALL;BSC 中重要属性的解释如下 从上表可知BSC的属性参数是正常的，但还有两个关于半数率的属性需注意：PROP解释TLDTH半数率负荷BSC控制参数HALFRATESUPP半数率BSC开关三、无线参数的检查和优化1、BSC 一致性检查 九月2日和4日分别做了两次一致性检查发现以下错误1.1

37、、MSC中错漏的数据MSC中缺少的内部小区CELLMSCLB16063LZMSC7LB16642LZMSC7LB23942LZMSC7LC13432LZMSC7LC23591LZMSC7LC23592LZMSC7LH33153LZMSC7LH43562LZMSC7LH43563LZMSC7LL13661LZMSC7建议对以下其它MSC中缺少的小区进行检查：LZBSC11 external cell LB13541 is not defined in LZMSC6.LZBSC11 external cell LL16043 is not defined in LZMSC6.LZBSC3 exte

38、rnal cell E13510 is not defined in LZMSC8. LZBSC3 external cell K36183 is not defined in LZMSC8. LZBSC3 external cell LB13673 is not defined in LZMSC8. LZBSC3 external cell LF43492 is not defined in LZMSC8. LZBSC3 external cell LF43493 is not defined in LZMSC8. LZBSC3 external cell LF43503 is not de

39、fined in LZMSC8. LZBSC3 external cell LF43590 is not defined in LZMSC8. LZBSC3 external cell LF63012 is not defined in LZMSC8. LZBSC3 external cell LF63013 is not defined in LZMSC8. LZBSC3 external cell LH23271 is not defined in LZMSC8. LZBSC3 external cell LH23272 is not defined in LZMSC8. LZBSC3 e

40、xternal cell LH33262 is not defined in LZMSC8. LZBSC3 external cell LH33263 is not defined in LZMSC8. LZBSC3 external cell LH53421 is not defined in LZMSC8. LZBSC3 external cell LK13241 is not defined in LZMSC8. LZBSC3 external cell LK13461 is not defined in LZMSC8. LZBSC3 external cell LK13462 is n

41、ot defined in LZMSC8. LZBSC3 external cell LK13463 is not defined in LZMSC8. LZBSC3 external cell LK23163 is not defined in LZMSC8. LZBSC3 external cell LK28232 is not defined in LZMSC8. LZBSC3 external cell LK28233 is not defined in LZMSC8. LZBSC3 external cell LK33571 is not defined in LZMSC8. LZB

42、SC3 external cell LK33572 is not defined in LZMSC8. LZBSC3 external cell LK43072 is not defined in LZMSC8. LZBSC3 external cell LK43320 is not defined in LZMSC8. LZBSC3 external cell LK43360 is not defined in LZMSC8. LZBSC3 external cell LK43751 is not defined in LZMSC8. LZBSC6 external cell LB13011

43、 is not defined in LZMSC4. LZBSC6 external cell LB13071 is not defined in LZMSC4. LZBSC6 external cell LB13621 is not defined in LZMSC4. LZBSC6 external cell LB23981 is not defined in LZMSC4. LZBSC6 external cell LB23983 is not defined in LZMSC4. LZBSC6 external cell LB43250 is not defined in LZMSC4

44、. LZBSC6 external cell LB63081 is not defined in LZMSC4. LZBSC6 external cell LB63082 is not defined in LZMSC4. LZBSC6 external cell LB63083 is not defined in LZMSC4. LZBSC6 external cell LC13261 is not defined in LZMSC4. LZBSC6 external cell LC13431 is not defined in LZMSC4. LZBSC6 external cell LC

45、13432 is not defined in LZMSC4. LZBSC6 external cell LC13501 is not defined in LZMSC4. LZBSC6 external cell LC13503 is not defined in LZMSC4. LZBSC6 external cell LC13721 is not defined in LZMSC4. LZBSC6 external cell LC13722 is not defined in LZMSC4. LZBSC6 external cell LC13812 is not defined in L

46、ZMSC4. LZBSC6 external cell LC18273 is not defined in LZMSC4. LZBSC6 external cell LC23201 is not defined in LZMSC4. LZBSC6 external cell LC23202 is not defined in LZMSC4. LZBSC6 external cell LC23203 is not defined in LZMSC4. LZBSC6 external cell LC23221 is not defined in LZMSC4. LZBSC6 external ce

47、ll LC23391 is not defined in LZMSC4. LZBSC6 external cell LC23392 is not defined in LZMSC4. LZBSC6 external cell LC23480 is not defined in LZMSC4. LZBSC6 external cell LC23592 is not defined in LZMSC4. LZBSC6 external cell LC33141 is not defined in LZMSC4. LZBSC6 external cell LC33142 is not defined

48、 in LZMSC4. LZBSC6 external cell LC33143 is not defined in LZMSC4. LZBSC6 external cell LC33380 is not defined in LZMSC4. LZBSC6 external cell LC33491 is not defined in LZMSC4. LZBSC6 external cell LC33572 is not defined in LZMSC4. LZBSC6 external cell LC33573 is not defined in LZMSC4. LZBSC6 extern

49、al cell LC33600 is not defined in LZMSC4. LZBSC6 external cell LC33770 is not defined in LZMSC4. LZBSC6 external cell LC33941 is not defined in LZMSC4. LZBSC6 external cell LC33942 is not defined in LZMSC4. LZBSC6 external cell LC43350 is not defined in LZMSC4. LZBSC6 external cell LC43482 is not de

50、fined in LZMSC4. LZBSC6 external cell LC43753 is not defined in LZMSC4. LZBSC6 external cell LC53361 is not defined in LZMSC4. LZBSC6 external cell LC53471 is not defined in LZMSC4. LZBSC6 external cell LC53472 is not defined in LZMSC4. LZBSC6 external cell LC53473 is not defined in LZMSC4. LZBSC6 e

51、xternal cell LC63071 is not defined in LZMSC4. LZBSC6 external cell LC63072 is not defined in LZMSC4. LZBSC6 external cell LC63073 is not defined in LZMSC4. LZBSC6 external cell LG13881 is not defined in LZMSC4. LZBSC6 external cell LG23433 is not defined in LZMSC4. LZBSC6 external cell LG23490 is n

52、ot defined in LZMSC4. LZBSC6 external cell LG43140 is not defined in LZMSC4. LZBSC6 external cell LG43883 is not defined in LZMSC4. LZBSC6 external cell LH13831 is not defined in LZMSC4. LZBSC6 external cell LH13832 is not defined in LZMSC4. LZBSC6 external cell LH43111 is not defined in LZMSC4. LZB

53、SC6 external cell LH43112 is not defined in LZMSC4. LZBSC6 external cell LH43113 is not defined in LZMSC4. LZBSC6 external cell LH43730 is not defined in LZMSC4. LZBSC6 external cell LH53421 is not defined in LZMSC4. LZBSC6 external cell LH53422 is not defined in LZMSC4. LZBSC6 external cell LJ13611

54、 is not defined in LZMSC4. LZBSC6 external cell LJ23952 is not defined in LZMSC4. LZBSC6 external cell LJ33190 is not defined in LZMSC4. LZBSC6 external cell LJ43520 is not defined in LZMSC4. LZBSC6 external cell LJ63261 is not defined in LZMSC4. LZBSC6 external cell LK13321 is not defined in LZMSC4

55、. LZBSC6 external cell LK13322 is not defined in LZMSC4. LZBSC6 external cell LK13323 is not defined in LZMSC4. LZBSC6 external cell LK13900 is not defined in LZMSC4. LZBSC6 external cell LK23081 is not defined in LZMSC4. LZBSC6 external cell LK23082 is not defined in LZMSC4. LZBSC6 external cell LK

56、23083 is not defined in LZMSC4. LZBSC6 external cell LK23112 is not defined in LZMSC4. LZBSC6 external cell LK23670 is not defined in LZMSC4. LZBSC6 external cell LK23712 is not defined in LZMSC4. LZBSC6 external cell LK23802 is not defined in LZMSC4. LZBSC6 external cell LK33122 is not defined in L

57、ZMSC4. LZBSC6 external cell LK33571 is not defined in LZMSC4. LZBSC6 external cell LK53161 is not defined in LZMSC4. LZBSC6 external cell LK53162 is not defined in LZMSC4. LZBSC6 external cell LK53163 is not defined in LZMSC4. LZBSC6 external cell LK63842 is not defined in LZMSC4. LZBSC6 external ce

58、ll LL13661 is not defined in LZMSC4. LZBSC6 external cell LL13662 is not defined in LZMSC4. LZBSC6 external cell LL13663 is not defined in LZMSC4. LZBSC7 external cell LB16621 is not defined in LZMSC4. LZBSC7 external cell LB43392 is not defined in LZMSC4. LZBSC7 external cell LB53713 is not defined

59、 in LZMSC4. LZBSC7 external cell LC13431 is not defined in LZMSC4. LZBSC7 external cell LC13432 is not defined in LZMSC4. LZBSC7 external cell LC13472 is not defined in LZMSC4. LZBSC7 external cell LC23151 is not defined in LZMSC4. LZBSC7 external cell LC23152 is not defined in LZMSC4. LZBSC7 extern

60、al cell LC23153 is not defined in LZMSC4. LZBSC7 external cell LC23171 is not defined in LZMSC4. LZBSC7 external cell LC23172 is not defined in LZMSC4. LZBSC7 external cell LC23173 is not defined in LZMSC4. LZBSC7 external cell LC23191 is not defined in LZMSC4. LZBSC7 external cell LC23321 is not de