2-WCDMA RAN Operation_new_P7
- 格式:ppt
- 大小:9.16 MB
- 文档页数:136
WCDMA RNP 切换过程分析(仅供内部使用) For internal use only拟制:臧亮日期: 2003-10-30审核:日期: 审核:日期: 批准:日期:HUAWEI华为技术有限公司Huawei Technologies Co., Ltd.版权所有 侵权必究 All rights reserved修订记录目录1切换的基本概念 (8)2切换的分类 (8)2.1软切换 (8)2.1.1更软切换 (8)2.1.2一般软切换 (9)2.2硬切换 (12)2.2.1异频硬切换 (12)2.2.2同频硬切换 (14)2.2.3系统间硬切换 (15)3切换过程的信令流程及消息分析 (17)3.1测量控制和测量报告 (17)3.1.1测量过程概述 (17)3.1.2测量控制 (19)3.1.3测量报告 (24)3.2软切换过程分析 (26)3.2.1激活集更新过程概述 (26)3.2.2软切换相关信令信息元素分析 (27)3.2.3激活集更新过程处理 (32)a)UE接收ACTIVE SET UPDATE消息后正常处理过程 (33)b) UE对接收到的ACTIVE SET UPDATE中不支持的配置处理(异常过程) (35)c) UE对接收到的ACTIVE SET UPDATE中无效配置的处理(异常过程) (35)e)UTRAN对ACTIVE SET UPDATE COMPLETE消息的接收(UTRAN正常过程) (37)f)UTRAN对ACTIVE SET UPDATE FAILURE消息的接收(UTRAN异常过程) (37)g)无效的ACTIVE SET UPDATE消息(异常过程) (37)h)在错误的状态接收一个ACTIVE SET UPDATE消息(异常过程) (37)3.2.4软切换信令流程分析 (38)1)无线链路增加信令流程分析 (38)2)无线链路删除信令流程分析 (40)3)无线链路增加和删除组合信令流程分析 (42)3.3一般硬切换过程分析 (44)3.3.1一般硬切换过程概述 (45)●定时重建硬切换 (45)●定时保持硬切换 (45)3.3.2一般硬切换信令信息元素分析 (48)1.无线承载建立消息“RADIO BEARER ESTABLISHMENT” (49)2.无线承载重配置消息“ RADIO BEARER RECONFIGURATION” (54)3.无线承载释放消息“RADIO BEARER RELEASE” (58)4.传输信道重配置消息“TRANSPORT CHANNEL RECONFIGURATION” (63)5.物理信道重配置消息“PHYSICAL CHANNEL RECONFIGURATION” (67)3.3.3一般硬切换流程 (70)信令流程分析 (71)3.4系统间切换过程分析 (74)3.4.1系统间切换过程概述 (74)3.4.2系统间硬切换信令信息元素分析 (76)3.4.3系统间硬切换流程 (81)1)系统间切换(来自UTRAN)流程(UTRAN->GSM/BSS) (81)2)系统间切换(到UTRAN)流程(GSM/BSS ->UTRAN) (83)4切换过程的性能分析 (85)4.1软切换的性能指标及分析 (85)4.2硬切换的性能指标及分析 (85)表目录表1 测量控制信息元素表 (20)表2 测量报告信息元素表 (24)表3 测量结果信息元素表 (24)表4 事件结果信息元素表 (25)表5 活动集更新信息元素表 (27)表6 无线链路增加信息元素表 (29)表7 激活集更新完成信息元素表 (30)表8 激活集更新失败信息元素表 (31)表9 激活集更新失败的原因列表 (32)表10 无线承载建立信息元素表 (49)表11 无线承载重配置信息元素表 (54)表12 无线承载释放信息元素表 (58)表13 传输信道重配置信息元素表 (63)表14 物理信道重配置信息元素表 (67)表15 HANDOVER FROM UTRAN COMMAND信息元素表 (76)表16 HANDOVER TO UTRAN COMMAND信息元素表 (77)图目录图 1 更软切换(Node B内不同小区间的同频切换)示意图 (9)图 2 软切换(Node B内不同小区间的同频切换)示意图 (10)图 3 (同一个RNS不同Node B间的同频切换)示意图 (11)图 4 软切换(不同RNS间的同频切换)示意图 (12)图 5 硬切换(Node B内不同小区间的频间切换)示意图 (13)图 6 硬切换(同一个RNS不同Node B间的频间切换)示意图 (13)图7 异频硬切换示意图 (14)图8 同频硬切换(Node B内同一个小区内的同频切换)示意图 ................... 错误!未定义书签。
1.1 小区选择和重选参数1.1.1 基本原理当UE开机后,则首先执行PLMN选择,然后执行小区选择过程。
当选择到合适的小区后,则选择该小区驻留,并向网络侧发起注册等过程。
当驻留到某个服务小区后,随着UE的移动,信道质量的变化,UE将会进行小区重选过程。
(1)PLMN的选择过程PLMN选择的标准是CPICH RSCP值大于或等于-95dBm,UE将读取其搜索到最强信号的小区的PLMN。
如果不满足上述的标准,但能够解出PLMN的标识,则也认为该PLMN是可作为选择接入的PLMN。
(2)小区选择过程选择一个信号最强的小区作为初始接入的小区。
小区选择标准S规则定义如下:其中:(3)小区重选择过程当UE驻留到小区后,则会执行小区重选过程:小区重选包括UE对测量的执行和测量的判决两部分。
下面仅针对小区不属于HCS小区的情况作介绍。
(1)测量规则:在下面的规则中,UE用Squal(FDD 小区)作为Sx :1若Sx > S intrasearch,则UE不需要执行频内测量;若Sx <= S intrasearch,则UE将执行频内测量;若S intrasearch, 未配置,则UE一直进行频内测量;2若Sx > S intersearch,则UE不需进行频间测量;若Sx <= S intersearch,则UE将执行频间测量;若S intersearch未配置,则UE一直进行频间测量;3若Sx > Ssearch RAT m, 则UE不需在不同无线测量技术之间的小区上进行测量;若Sx <= Ssearch RATm, 则UE将对其他RAT m 小区进行测量;若Ssearch RAT m, 未配置,则UE一直对其他RAT m小区进行测量。
(2)小区重选的判决规则:以下小区重选标准用于频内小区,频间小区和inter-RAT 小区:小区排队标准R规则为:其中:其中:Tn是一个定时器,当相邻小区的信号质量比服务小区的信号质量加一个服务小区和该相邻小区的相对偏差(Qoffset1s,n 或者Qoffset2s,n)还要高时,则启动该定时器。
WCDMA RAN原理培训试题一、填空题(每空0.5分,共15分)1、小区搜索分三步,第一步是利用__P-SCH (主同步信道)_______信道的___PSC (主同步码)_____获得时隙同步;第二步是利用__ S-SCH (主同步信道)_______信道的_SSC (从同步码)_______获得帧同步和主扰码组组号;第三步是利用___CPICH(公共导频信道)______信道获得该小区所使用的主扰码。
2、对于同一个业务来说,下行扩频码的SF与上行扩频码SF的关系为_____上行是下行底两倍_____________。
3、WCDMA系统的信道编码方式主要有___卷积编码________和___Turbo__________。
4、软切换在_RNC______进行__选择性_______合并,更软切换在__NodeB_______进行___最大比合并_______合并,这是他们的唯一区别。
5、CPICH信道使用的扩频码为___Cch,256,0________,P-CCPCH信道使用的扩频码____ Cch,256,0________。
6、RNC的资源主要受限于__WFMR_____单板;按照此单板的容量,可以计算得到:华为RNC满配置时,一个RNC最大支持__51200___个等效语音信道,最大支持__2560_____个小区;7、RRM的参数是配置在RNC的___WSPU______单板。
8、华为RNC支持的传输方式有___ATM over E1/T1_______、___ ATM over E1/T1 over SDH________、____ ATM over SDH________等。
9、华为系列化基站设备包括___BTS3812________、__ BTS3806_________、___ BTS3802C________;10、华为NodeB支持灵活的传输组网方式,可以采用_星型______、__树型____、___链型_____、___环型_____和__混合型______等组网方式,链型传输组网的最大级联数为__5____。
WCDMA项目RAN工程师操作细则对于一个RAN工程师来说,我们在一个项目上面主要负责以下:1.RNC加电,RNC的本调2.RNC与CE物理连通,RNC与MGW物理连通,RNC与传输(即到RBS链路)物理联通3.挂好测试站点,对应操作数据4.调测RNC与MGW的信令连通,打通语音,视频电话,测试CS正常5.调测RNC与SGSN的信令连通,手机上网,手机拨号上网,测试PS正常6.OSS物理连接及设置7.以上操作完后就是挂站了一.RNC加电,RNC的本调在我们到达机房时候,首先需要做的就是查看对应机框的连接线路是否正确,然后需要做就是用万用表检测输入电压是48V左右为正常后再插上RNC的电源线做加电操作加电操作完成后,下面我才开始对RNC坐本调操作(操作细则见:RNC安装调试过程文件夹)等我们本调完成后,需要做的就是将对应的RNC的DT数据检测后TRUN DT到对应RNC中,DT如下图二.RNC与CE物理连通,信令联通,RNC与MGW物理连通,信令联通,RNC与传输(即到RBS链路)物理联通,挂站操作1.RNC与CE物理连通这里物理连接好后,我们可以在CE设备上面查看到对应的Mur/Mub口,lub over ip光口是否亮灯正常,因为从EM上面查看的时候对应口都是ENABLE的,所以我们看是否连通,需要和CE人员通过查看CE上面亮灯情况来确定通路是否正常,再就是对应lub口是否亮灯,同时还要查看IP板(即ET-MFX板)上面的对应亮灯情况是否正常,不正常就需要对纤检测,这是为了后面和SGSN联调做好前期准备2.RNC与MGW物理连通物理联通我们主要通过EM查看,然后需要和MGW联调,联调我们主要查看的对应的信令是否正常,不过之前我们需要提供给MGW调测工程师对应的参数和表格,如下图这里MGW需要的参数主要是:RNC ID,OPC(也就是我们表格上面的SPC),LAC号,SAC号(这个是我们确定好测试站后,把对应个CELLID给MGW调测工程师就可以了,如果没有挂站,等挂站时候再给MGW工程师)给出以上参数后,我们还需要和MGW调测工程师核对的就是AAL2地址,可以再ATND得A2EA表中查看到对应RNC的AAL2地址,如下图:同时调测前从PE处获取对应的光口表格,给MGW测试工程师即可,表格如下图3. RNC与MGW联调做完以上操作后,我们就需要通过moshell登陆到RNC上面查看MGW的信令是否ENABLE的,对应操作如下:基本命令为如下:lst iullst srslst mtp3lst mtp3bsr查看信令路由实例操作如下:SQRNC01> lst mtp3090514-22:44:14 10.185.160.1 7.1e RNC_NODE_MODEL_K_9_16 stopfile=/tmp/47736===================================================================================Proxy Adm State Op. State MO===================================================================================254 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1255 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSls=SQRNC02_3-5506_SLS256 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSls=SQRNC02_3-5506_SLS,Mtp3bSlItu=SQRNC02_3-5506_SL_00257 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSls=SQRNC02_3-5506_SLS,Mtp3bSlItu=SQRNC02_3-5506_SL_01258 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSrs=SQRNC02_3-5506_SRS259 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSrs=SQRNC02_3-5506_SRS,Mtp3bSr=SQRNC02_3-5506_SR_01260 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bAp=SQRNC02_Mtp3bAp_Q2630261 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bAp=SQRNC02_Mtp3bAp_SCCP262 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSrs=SQMGW02_3-1507_SRS263 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSrs=SQMGW02_3-1507_SRS,Mtp3bSr=SQMGW02_3-1507_SR_01 264 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bAp=SQMGW02_Mtp3bAp_Q2630265 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSls=SQMGW02_3-1507_SLS266 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSls=SQMGW02_3-1507_SLS,Mtp3bSlItu=SQMGW02_3-1507_SL_00267 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSls=SQMGW02_3-1507_SLS,Mtp3bSlItu=SQMGW02_3-1507_SL_02268 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSls=SQMGW02_3-1507_SLS,Mtp3bSlItu=SQMGW02_3-1507_SL_04269 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSls=SQMGW02_3-1507_SLS,Mtp3bSlItu=SQMGW02_3-1507_SL_06270 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSls=SQMGW02_3-1507_SLS,Mtp3bSlItu=SQMGW02_3-1507_SL_01271 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSls=SQMGW02_3-1507_SLS,Mtp3bSlItu=SQMGW02_3-1507_SL_03272 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSls=SQMGW02_3-1507_SLS,Mtp3bSlItu=SQMGW02_3-1507_SL_05273 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSls=SQMGW02_3-1507_SLS,Mtp3bSlItu=SQMGW02_3-1507_SL_07274 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bAp=NJMSS10_Mtp3bAp_SCCP275 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSrs=NJMSS10_3-239_SRS276 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSrs=NJMSS10_3-239_SRS,Mtp3bSr=NJMSS10_3-239_SR_01277 0 (DISABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSrs=NJSGSN04_3-182_SRS278 0 (DISABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSrs=NJSGSN04_3-182_SRS,Mtp3bSr=NJSGSN04_CP1279 0 (DISABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSrs=NJSGSN04_3-182_SRS,Mtp3bSr=NJSGSN04_CP2281 0 (DISABLED) TransportNetwork=1,Mtp3bSpItu=1,M3uAssociation=NJSGSN04_CP2282 0 (DISABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bAp=NJSGSN04===================================================================================Total: 29 MOs在每台RNC上面查看到以上情况后就能100%肯定我们的RNC和MGW联调成功了,然后用手机测试视频和语音电话就可以了!4.RNC和SGSN联调对通与CE的物理连接后,首先我们要操作的就是解开SGSN对应的参数,然后可以通过moshell在RNC上面PING通我们这边的CP和UP面地址了,实际操作如下:命令主要是一下几个lst hostgpb (需要解锁)lst hostspb (需要解锁)lst IpEthPacketDataRouter (需要解锁)lst giga (需要解锁)实例操作如下:SQRNC02> lst giga090513-19:05:58 10.185.164.1 7.1e RNC_NODE_MODEL_K_9_16 stopfile=/tmp/9704===================================================================================Proxy Adm State Op. State MO===================================================================================2854 0 (LOCKED) 1 (ENABLED) Equipment=1,Subrack=MS,Slot=7,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=12861 0 (LOCKED) 1 (ENABLED) Equipment=1,Subrack=MS,Slot=26,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=15695 0 (DISABLED) Equipment=1,Subrack=MS,Slot=7,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1,IpInterface=MS-7_PS_UP5696 0 (DISABLED) Equipment=1,Subrack=MS,Slot=7,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1,IpInterface=MS-7_SIG5697 0 (DISABLED) Equipment=1,Subrack=MS,Slot=26,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1,IpInterface=MS-26_PS_UP5698 0 (DISABLED) Equipment=1,Subrack=MS,Slot=26,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1,IpInterface=MS-26_SIG===================================================================================Total: 6 MOsSQRNC02> ldeb gigaDeblock following MOs ?===================================================================================2854 Equipment=1,Subrack=MS,Slot=7,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=12861 Equipment=1,Subrack=MS,Slot=26,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1===================================================================================y============================================================================================================Id MO administrativeState Result============================================================================================================2854 Subrack=MS,Slot=7,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1 1 >>> Set.2861 Subrack=MS,Slot=26,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1 1 >>> Set.============================================================================================================Total: 2 MOs attempted, 2 MOs setSQRNC02> lst giga090513-19:06:20 10.185.164.1 7.1e RNC_NODE_MODEL_K_9_16 stopfile=/tmp/9704===================================================================================Proxy Adm State Op. State MO===================================================================================2854 1 (UNLOCKED) 1 (ENABLED) Equipment=1,Subrack=MS,Slot=7,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=12861 1 (UNLOCKED) 1 (ENABLED) Equipment=1,Subrack=MS,Slot=26,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=15695 1 (ENABLED) Equipment=1,Subrack=MS,Slot=7,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1,IpInterface=MS-7_PS_UP 5696 1 (ENABLED) Equipment=1,Subrack=MS,Slot=7,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1,IpInterface=MS-7_SIG5697 1 (ENABLED) Equipment=1,Subrack=MS,Slot=26,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1,IpInterface=MS-26_PS_UP 5698 1 (ENABLED) Equipment=1,Subrack=MS,Slot=26,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1,IpInterface=MS-26_SIG ===================================================================================Total: 6 MOsSQRNC02> ldeb hostspb090513-19:06:43 10.185.164.1 7.1e RNC_NODE_MODEL_K_9_16 stopfile=/tmp/9704===================================================================================5700 IpSystem=1,IpAccessHostSpb=MS-195701 IpSystem=1,IpAccessHostSpb=MS-205702 IpSystem=1,IpAccessHostSpb=MS-215703 IpSystem=1,IpAccessHostSpb=MS-225704 IpSystem=1,IpAccessHostSpb=MS-23===================================================================================y============================================================================================================ Id MO administrativeState Result============================================================================================================ 5700 IpAccessHostSpb=MS-19 1 >>> Set.5701 IpAccessHostSpb=MS-20 1 >>> Set.5702 IpAccessHostSpb=MS-21 1 >>> Set.5703 IpAccessHostSpb=MS-22 1 >>> Set.5704 IpAccessHostSpb=MS-23 1 >>> Set.============================================================================================================ Total: 5 MOs attempted, 5 MOs setSQRNC02> ldeb hostgpb090513-19:07:09 10.185.164.1 7.1e RNC_NODE_MODEL_K_9_16 stopfile=/tmp/9704Deblock following MOs ?===================================================================================5699 IpSystem=1,IpAccessHostGpb=MS-8===================================================================================y============================================================================================================ Id MO administrativeState Result============================================================================================================ 5699 IpAccessHostGpb=MS-8 1 >>> Set.Total: 1 MOs attempted, 1 MOs setSQRNC02> lst ipinterface090513-19:07:31 10.185.164.1 7.1e RNC_NODE_MODEL_K_9_16 stopfile=/tmp/9704===================================================================================Proxy Adm State Op. State MO===================================================================================773 1 (ENABLED) Equipment=1,Subrack=ES-1,Slot=4,PlugInUnit=1,ExchangeTerminalIp=1,InternalEthernetPort=1,IpInterface=Iub_ES-1-4 2010 1 (ENABLED) Equipment=1,Subrack=ES-1,Slot=26,PlugInUnit=1,ExchangeTerminalIp=1,InternalEthernetPort=1,IpInterface=Iub_ES-1-26 5695 1 (ENABLED) Equipment=1,Subrack=MS,Slot=7,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1,IpInterface=MS-7_PS_UP5696 1 (ENABLED) Equipment=1,Subrack=MS,Slot=7,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1,IpInterface=MS-7_SIG5697 1 (ENABLED) Equipment=1,Subrack=MS,Slot=26,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1,IpInterface=MS-26_PS_UP5698 1 (ENABLED) Equipment=1,Subrack=MS,Slot=26,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1,IpInterface=MS-26_SIG===================================================================================Total: 6 MOsSQRNC02> lst IpEthPacketDataRouter090514-22:27:13 10.185.164.1 7.1e RNC_NODE_MODEL_K_9_16 stopfile=/tmp/31388===================================================================================Proxy Adm State Op. State MO===================================================================================5713 0 (LOCKED) 1 (ENABLED) Equipment=1,SpDevicePool=PdrDevice,PdrDevice=1,IpEthPacketDataRouter=MS-19-15714 0 (LOCKED) 1 (ENABLED) Equipment=1,SpDevicePool=PdrDevice,PdrDevice=1,IpEthPacketDataRouter=MS-19-25715 0 (LOCKED) 1 (ENABLED) Equipment=1,SpDevicePool=PdrDevice,PdrDevice=2,IpEthPacketDataRouter=MS-20-15716 0 (LOCKED) 1 (ENABLED) Equipment=1,SpDevicePool=PdrDevice,PdrDevice=2,IpEthPacketDataRouter=MS-20-25717 0 (LOCKED) 1 (ENABLED) Equipment=1,SpDevicePool=PdrDevice,PdrDevice=3,IpEthPacketDataRouter=MS-21-15718 0 (LOCKED) 1 (ENABLED) Equipment=1,SpDevicePool=PdrDevice,PdrDevice=3,IpEthPacketDataRouter=MS-21-25719 0 (LOCKED) 1 (ENABLED) Equipment=1,SpDevicePool=PdrDevice,PdrDevice=4,IpEthPacketDataRouter=MS-22-15720 0 (LOCKED) 1 (ENABLED) Equipment=1,SpDevicePool=PdrDevice,PdrDevice=4,IpEthPacketDataRouter=MS-22-25721 0 (LOCKED) 1 (ENABLED) Equipment=1,SpDevicePool=PdrDevice,PdrDevice=5,IpEthPacketDataRouter=MS-23-15722 0 (LOCKED) 1 (ENABLED) Equipment=1,SpDevicePool=PdrDevice,PdrDevice=5,IpEthPacketDataRouter=MS-23-2===================================================================================090514-22:27:22 10.185.164.1 7.1e RNC_NODE_MODEL_K_9_16 stopfile=/tmp/31388Deblock following MOs ?===================================================================================5713 Equipment=1,SpDevicePool=PdrDevice,PdrDevice=1,IpEthPacketDataRouter=MS-19-15714 Equipment=1,SpDevicePool=PdrDevice,PdrDevice=1,IpEthPacketDataRouter=MS-19-25715 Equipment=1,SpDevicePool=PdrDevice,PdrDevice=2,IpEthPacketDataRouter=MS-20-15716 Equipment=1,SpDevicePool=PdrDevice,PdrDevice=2,IpEthPacketDataRouter=MS-20-25717 Equipment=1,SpDevicePool=PdrDevice,PdrDevice=3,IpEthPacketDataRouter=MS-21-15718 Equipment=1,SpDevicePool=PdrDevice,PdrDevice=3,IpEthPacketDataRouter=MS-21-25719 Equipment=1,SpDevicePool=PdrDevice,PdrDevice=4,IpEthPacketDataRouter=MS-22-15720 Equipment=1,SpDevicePool=PdrDevice,PdrDevice=4,IpEthPacketDataRouter=MS-22-25721 Equipment=1,SpDevicePool=PdrDevice,PdrDevice=5,IpEthPacketDataRouter=MS-23-15722 Equipment=1,SpDevicePool=PdrDevice,PdrDevice=5,IpEthPacketDataRouter=MS-23-2===================================================================================Are you Sure [y/n] ? y============================================================================================================ Id MO administrativeState Result============================================================================================================ 5713 SpDevicePool=PdrDevice,PdrDevice=1,IpEthPacketDataRouter=MS-19-1 1 >>> Set.5714 SpDevicePool=PdrDevice,PdrDevice=1,IpEthPacketDataRouter=MS-19-2 1 >>> Set.5715 SpDevicePool=PdrDevice,PdrDevice=2,IpEthPacketDataRouter=MS-20-1 1 >>> Set.5716 SpDevicePool=PdrDevice,PdrDevice=2,IpEthPacketDataRouter=MS-20-2 1 >>> Set.5717 SpDevicePool=PdrDevice,PdrDevice=3,IpEthPacketDataRouter=MS-21-1 1 >>> Set.5718 SpDevicePool=PdrDevice,PdrDevice=3,IpEthPacketDataRouter=MS-21-2 1 >>> Set.5719 SpDevicePool=PdrDevice,PdrDevice=4,IpEthPacketDataRouter=MS-22-1 1 >>> Set.5720 SpDevicePool=PdrDevice,PdrDevice=4,IpEthPacketDataRouter=MS-22-2 1 >>> Set.5721 SpDevicePool=PdrDevice,PdrDevice=5,IpEthPacketDataRouter=MS-23-1 1 >>> Set.5722 SpDevicePool=PdrDevice,PdrDevice=5,IpEthPacketDataRouter=MS-23-2 1 >>> Set.============================================================================================================090514-22:27:51 10.185.164.1 7.1e RNC_NODE_MODEL_K_9_16 stopfile=/tmp/31388===================================================================================Proxy Adm State Op. State MO===================================================================================5713 1 (UNLOCKED) 1 (ENABLED) Equipment=1,SpDevicePool=PdrDevice,PdrDevice=1,IpEthPacketDataRouter=MS-19-15714 1 (UNLOCKED) 1 (ENABLED) Equipment=1,SpDevicePool=PdrDevice,PdrDevice=1,IpEthPacketDataRouter=MS-19-25715 1 (UNLOCKED) 1 (ENABLED) Equipment=1,SpDevicePool=PdrDevice,PdrDevice=2,IpEthPacketDataRouter=MS-20-15716 1 (UNLOCKED) 1 (ENABLED) Equipment=1,SpDevicePool=PdrDevice,PdrDevice=2,IpEthPacketDataRouter=MS-20-25717 1 (UNLOCKED) 1 (ENABLED) Equipment=1,SpDevicePool=PdrDevice,PdrDevice=3,IpEthPacketDataRouter=MS-21-15718 1 (UNLOCKED) 1 (ENABLED) Equipment=1,SpDevicePool=PdrDevice,PdrDevice=3,IpEthPacketDataRouter=MS-21-25719 1 (UNLOCKED) 1 (ENABLED) Equipment=1,SpDevicePool=PdrDevice,PdrDevice=4,IpEthPacketDataRouter=MS-22-15720 1 (UNLOCKED) 1 (ENABLED) Equipment=1,SpDevicePool=PdrDevice,PdrDevice=4,IpEthPacketDataRouter=MS-22-25721 1 (UNLOCKED) 1 (ENABLED) Equipment=1,SpDevicePool=PdrDevice,PdrDevice=5,IpEthPacketDataRouter=MS-23-15722 1 (UNLOCKED) 1 (ENABLED) Equipment=1,SpDevicePool=PdrDevice,PdrDevice=5,IpEthPacketDataRouter=MS-23-2===================================================================================Total: 10 MOs下面就是对应PING通地址了,需要在这里说明的是,这些IP都是在RNC的SGSN的DT中,我们要用Iups cpa address来PING通CE GW地址,每个RNC各有两个,之后还需要用对应的DT中pdr1和pdr2共10个地址来分别PING通VRRP1 address和VRRP2 address来查看对应的CE上面的操作数据是否正确,不正确找CE调测工程师核对,直到PING通所有地址为止SQRNC01> ipac_ping -z 10.242.205.2 -d 10.242.205.1090514-22:04:37 10.185.160.1 7.1e RNC_NODE_MODEL_K_9_16 stopfile=/tmp/32992$ ipac_ping -z 10.242.205.2 -d 10.242.205.1PING (10.242.205.1) 56(64) bytes of data.64 bytes from 10.242.205.1: icmp_seq=0 ttl=64 time=0.719 ms64 bytes from 10.242.205.1: icmp_seq=1 ttl=64 time=0.642 ms64 bytes from 10.242.205.1: icmp_seq=2 ttl=64 time=0.683 ms--- 10.242.205.1 ping statistics ---round-trip min/avg/max = 0.642/0.681/0.719 ms$SQRNC01> ipac_ping -z 10.242.205.130 -d 10.242.205.129090514-22:04:49 10.185.160.1 7.1e RNC_NODE_MODEL_K_9_16 stopfile=/tmp/32992 $ ipac_ping -z 10.242.205.130 -d 10.242.205.129PING (10.242.205.129) 56(64) bytes of data.64 bytes from 10.242.205.129: icmp_seq=0 ttl=64 time=0.700 ms64 bytes from 10.242.205.129: icmp_seq=1 ttl=64 time=0.680 ms64 bytes from 10.242.205.129: icmp_seq=2 ttl=64 time=0.689 ms--- 10.242.205.129 ping statistics ---3 packets transmitted, 3 received, 0% packet lossround-trip min/avg/max = 0.680/0.689/0.700 ms$SQRNC01> ipac_ping -z 10.242.205.37 -d 10.242.205.33090514-22:05:02 10.185.160.1 7.1e RNC_NODE_MODEL_K_9_16 stopfile=/tmp/32992 $ ipac_ping -z 10.242.205.37 -d 10.242.205.33PING (10.242.205.33) 56(64) bytes of data.64 bytes from 10.242.205.33: icmp_seq=0 ttl=64 time=0.771 ms64 bytes from 10.242.205.33: icmp_seq=1 ttl=64 time=0.759 ms64 bytes from 10.242.205.33: icmp_seq=2 ttl=64 time=0.789 ms--- 10.242.205.33 ping statistics ---3 packets transmitted, 3 received, 0% packet lossround-trip min/avg/max = 0.759/0.773/0.789 ms$SQRNC01> ipac_ping -z 10.242.205.37 -d 10.242.205.34090514-22:07:21 10.185.160.1 7.1e RNC_NODE_MODEL_K_9_16 stopfile=/tmp/32992 $ ipac_ping -z 10.242.205.37 -d 10.242.205.34PING (10.242.205.34) 56(64) bytes of data.64 bytes from 10.242.205.34: icmp_seq=0 ttl=64 time=14.600 ms64 bytes from 10.242.205.34: icmp_seq=1 ttl=64 time=0.743 ms64 bytes from 10.242.205.34: icmp_seq=2 ttl=64 time=0.847 ms--- 10.242.205.34 ping statistics ---3 packets transmitted, 3 received, 0% packet lossround-trip min/avg/max = 0.743/5.396/14.600 ms$注意:以上操作时在对通CE物理连接后就需要操作,为下一步和SGSN连通信令做准备以上完成后,我们也需要给SGSN调测工程师的相关的参数,给的参数和MGW相同,但是不需要给的是SPC号,和对应我们信令面和用户面IP(都在SGSN 的DT里面可以查找到),给其做数据如图:之后对应的SGSN调测工程师也会给出对应SGSN上面的IP和remotePortNumber,如下图:然后,我们等SGSN工程师做完数据后,首先需要查看的就是SGSN的信令有没有活,操作如下:操作命令为:lst sgsnlst m3ualst ranap查看是否能活,没活就需要和SGSN调测工程师核对RNC ID,SGSN信令点码,SGSN端口号(也就是SGSN给出的SGSN侧端口号)实例操作:SQRNC01> lst sgsn090518-10:22:27 10.185.160.1 7.1e RNC_NODE_MODEL_K_9_16 stopfile=/tmp/12236===================================================================================Proxy Adm State Op. State MO===================================================================================149 1 (ENABLED) TransportNetwork=1,SccpSp=1,SccpScrc=1,SccpApRemote=NJSGSN04260 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSrs=NJSGSN04_3-182_SRS261 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSrs=NJSGSN04_3-182_SRS,Mtp3bSr=NJSGSN04_CP1262 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSrs=NJSGSN04_3-182_SRS,Mtp3bSr=NJSGSN04_CP2263 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,Mtp3bAp=NJSGSN04272 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,M3uAssociation=NJSGSN04_CP1283 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,M3uAssociation=NJSGSN04_CP26089 1 (ENABLED) RncFunction=1,CnOperator=46001,IuLink=NJSGSN04,Ranap=NJSGSN04===================================================================================Total: 8 MOsSQRNC01> lst m3ua090518-10:22:57 10.185.160.1 7.1e RNC_NODE_MODEL_K_9_16 stopfile=/tmp/12236===================================================================================Proxy Adm State Op. State MO===================================================================================272 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,M3uAssociation=NJSGSN04_CP1283 1 (ENABLED) TransportNetwork=1,Mtp3bSpItu=1,M3uAssociation=NJSGSN04_CP2===================================================================================Total: 2 MOsSQRNC01> lst ranap090518-10:25:55 10.185.160.1 7.1e RNC_NODE_MODEL_K_9_16 stopfile=/tmp/12356===================================================================================Proxy Adm State Op. State MO===================================================================================6089 1 (ENABLED) RncFunction=1,CnOperator=46001,IuLink=NJSGSN04,Ranap=NJSGSN046091 1 (ENABLED) RncFunction=1,CnOperator=46001,IuLink=NJMSS10,Ranap=NJMSS10_Ranap ===================================================================================Total: 2 MOs操作完后,我们还需要PING通SGSN给出的信令面的IP,实例操作如下:SQRNC01> ipac_ping -z 10.242.205.2 -d 10.242.185.137090514-22:12:19 10.185.160.1 7.1e RNC_NODE_MODEL_K_9_16 stopfile=/tmp/32992$ ipac_ping -z 10.242.205.2 -d 10.242.185.137PING (10.242.185.137) 56(64) bytes of data.64 bytes from 10.242.185.137: icmp_seq=0 ttl=64 time=0.893 ms64 bytes from 10.242.185.137: icmp_seq=1 ttl=64 time=0.864 ms64 bytes from 10.242.185.137: icmp_seq=2 ttl=64 time=0.736 ms--- 10.242.185.137 ping statistics ---3 packets transmitted, 3 received, 0% packet loss$SQRNC01> ipac_ping -z 10.242.205.2 -d 10.242.185.138090514-22:12:26 10.185.160.1 7.1e RNC_NODE_MODEL_K_9_16 stopfile=/tmp/32992 $ ipac_ping -z 10.242.205.2 -d 10.242.185.138PING (10.242.185.138) 56(64) bytes of data.64 bytes from 10.242.185.138: icmp_seq=0 ttl=64 time=0.893 ms64 bytes from 10.242.185.138: icmp_seq=1 ttl=64 time=0.864 ms64 bytes from 10.242.185.138: icmp_seq=2 ttl=64 time=0.736 ms--- 10.242.185.138 ping statistics ---3 packets transmitted, 3 received, 0% packet loss$SQRNC01> ipac_ping -z 10.242.205.130 -d 10.242.185.141090514-22:12:32 10.185.160.1 7.1e RNC_NODE_MODEL_K_9_16 stopfile=/tmp/32992 $ ipac_ping -z 10.242.205.130 -d 10.242.185.141PING (10.242.185.141) 56(64) bytes of data.64 bytes from 10.242.185.141: icmp_seq=0 ttl=64 time=0.893 ms64 bytes from 10.242.185.141: icmp_seq=1 ttl=64 time=0.864 ms64 bytes from 10.242.185.141: icmp_seq=2 ttl=64 time=0.736 ms--- 10.242.185.141 ping statistics ---3 packets transmitted, 3 received, 0% packet loss$SQRNC01> ipac_ping -z 10.242.205.130 -d 10.242.185.142090514-22:12:53 10.185.160.1 7.1e RNC_NODE_MODEL_K_9_16 stopfile=/tmp/32992 $ ipac_ping -z 10.242.205.130 -d 10.242.185.142PING (10.242.185.142) 56(64) bytes of data.64 bytes from 10.242.185.142: icmp_seq=0 ttl=64 time=0.893 ms64 bytes from 10.242.185.142: icmp_seq=1 ttl=64 time=0.864 ms64 bytes from 10.242.185.142: icmp_seq=2 ttl=64 time=0.736 ms--- 10.242.185.142 ping statistics ---3 packets transmitted, 3 received, 0% packet loss$以上操作完后,基本上证明我们的SGSN已经OK了,再之后用手机测试上网即可,等测试上网正常后,就可以说明我们SGSN联调成功。