手机性能测试经验分享PPT课件

1、主叫流程主叫流程第1页/共24页PS主主CSLink channel establishment requestSynchronization burstSynchronization burstSABM CC Call ProceedingRT definition information requestRT definition information acknowledgeSCCHLink channel assignmentSCCHFACCH/SACCHUA FACCH/SACCHCC Setup FACCH/SACCHFACCH/SACCHFACCH/SACCHFACCH/SACCH

2、RT function requestFACCH/SACCHRT function request response链路信道建立请求消息终端链路信道指配消息(信道的频点和时隙的位置)同步突发脉冲,在呼叫建立过程和切换建立时隙的频率和时间同步。启动多帧传输模式，设置异步通信对SABM的响应 多帧通信建立建立呼叫的初始信息（承载能力,设施,主被叫号码）申请接受区域信息(终端切换的参数)向PS通告区域信息通知终端切换模式主叫呼叫流程主叫呼叫流程第2页/共24页对语音是否加密,密钥移动参数,是否需要鉴权,鉴权的算法,寻呼类型鉴权过程释放FACCH信道确认 链路释放主叫屏幕开始进入计时界面和通话有关的硬

3、件被打开,microphone,receiver,ADPCM编码,主叫手机进入等待通话阶段RT encryption key setFACCH/SACCHMM function requestMM function request responseFACCH/SACCHFACCH/SACCHFACCH/SACCHMM authentication request response FACCH/SACCHDISCFACCHFACCHUAMM authentication requestPS主主CSRT encryption key setFACCH/SACCHMM function reques

4、tMM function request responseFACCH/SACCHFACCH/SACCHFACCH/SACCHMM authentication request response FACCH/SACCHDISCFACCHFACCHUAMM authentication requestPS主主CS回铃声通话过程SACCHCC ConnectCC AlteringSACCH主叫呼叫流程主叫呼叫流程第3页/共24页30 0f 00 20 08 1a 57 1a 1a 44 26 80 00 44 RT - L1 pch information paging消息 (8 bytes，从08

5、开始)。最后的44则是CS的RSSI指示0.922 40 33 00 02 44 00 39 35 34 38 bf pm send rssi indication to MMIPM层向MMI层发送RSSI信息2.125 30 0f 00 20 08 1a 57 1a 1a 39 3a a0 00 43 RT - L1 pch information2.125 40 33 00 02 43 00 39 35 34 38 bf pm send rssi indication to MMI2.500 50 2b 00 00 00 0c 00 00 00 80 38 37 35 39 31 35 3

6、0 35 pm get MO call command from MMI ,pm从MMI得到主叫指令(用户在按了talk键)2.500 40 0d 00 51 03 00 pm send tch establish request to MM 2.500 34 02 00 b9 37 MM get TCH establishment req from PM 2.500 33 02 00 31 03 00 MM send TCH establishment request to RR MM向RT发送建立TCH的请求2.500 30 16 00 03 00 RT L1 start monit L1

7、开始找寻基站 2.781 30 4b 00 9e 01 13 2e 50 01 39 RT CS_ID2.781 30 4b 00 9e 01 13 3e 25 01 4a RT CS_ID 这个即是RSSI最好的CS2.953 30 0f 00 20 08 1a 57 18 55 aa 81 60 00 4e RT CS link cch req 手机向基站发送请求分配业务信道的请求3.470 30 0f 00 20 08 00 00 00 00 00 00 00 00 4e RT CS link cch rereq 重发请求4.453 30 0f 00 20 08 00 00 00 00

8、00 00 00 00 4e RT CS link cch rereq5.860 30 04 00 20 07 01 RT - L1 primitive5.953 30 0f 00 20 08 1a 57 1a 1a 7a 34 a0 00 4b RT - L1 pch information6.470 30 0f 00 20 08 1a 57 13 23 a3 81 00 00 4a RT - L1 pch information6.156 30 12 00 04 20 08 01 02 02 12 a0 81 00 00 RT - L1 lch assignment L1向RT发送信道发配

9、成功消息6.188 30 09 00 05 00 RT - L1 Uwave IND L1向RT发送U波检测成功信息6.219 30 20 00 06 RT L2 facch est reqRT向L2发送FACCH建立请求，下面是建业务通道，约定业务信道载频和时隙6.219 26 01 00 3f 81 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 l2 to l1 data req -facch L2向L1发送FACCH数据传送请求6.235 28 01 00 10 02 01 00 from l1 inf facch 从L1收到

10、FACCH 6.297 27 01 00 10 01 01 00 02 73 81 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0from L1 data facch 6.297 30 19 00 06 11 03 RT L2 sacch est reqRT向L2发送SACCH建立请求6.297 26 00 00 3f 09 00 00 l2 to l1 data req sacchL2向L1发送SACCH数据传送请求6.313 28 00 00 10 02 00 00 from l1 inf sacch6.328 27 00 00 10 01 00 0

11、0 02 73 0b 00 00 from L1 data -sacch6.328 30 18 00 07 11 01 RT MM tch est cfm or ind RT向MM发送业务信道建立确认信息6.328 33 03 00 31 04 00 00 00 MM get TCH establishment confirm from RR第6页/共24页6.344 41 16 00 01 pm send cc set up request to cc 发送cc setup请求, 说明pm发给cc setup消息 6.344 35 98 00 00 00 00 03 80 8c a4 00

12、00 00 00 00 00 00 00 00 00 00 00 00 00 . CC CS: SETUP CC向基站发送SETUP消息6.360 2a 01 00 01 24 02 l2 iformat facch 6.360 26 01 00 02 04 00 a2 00 45 01 01 05 04 03 80 8c a4 6c 0e 00 80 30 35 37 l2 to l1 data req -(facch) L2向L1发送数据传输请求,通过FACCH传输6.375 28 01 00 10 02 01 00 from l1 inf facch6.375 26 01 00 02 0

13、4 02 a2 00 38 35 35 38 37 31 34 30 70 09 80 38 37 35 39 31 356.438 27 01 00 10 01 01 00 04 71 81 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 from L1 data facch6.531 27 01 00 10 01 01 00 04 70 c9 00 45 01 81 02 00 00 00 00 00 00 00 00 00 00 00 00 00 from L1 data facch6.531 35 02 00 45 01 81

14、 02 CC PM: CALL-PROCEEDINGCC的建立的建立第7页/共24页RT 消息消息/鉴权鉴权/释放释放FACCH6.547 30 22 00 07 RT CS function req RT function request6.750 30 24 00 43 05 09 10 00 15 17 c0 RT L1 CS enc key set RT encryption key set6.766 31 5f 00 07 RT - PM fun cfm RT向PM发送RT function request确认信息6.781 50 0b 00 51 01 pm send functi

15、on request to MM MM function request6.781 34 00 00 a5 3d MM get function request from PM6.844 32 06 00 MM get auth req from net MM authentication request6.844 32 07 00 MM send auth rsp to net MM authentication request response6.844 34 01 00 51 02 MM send function confirm to PM MM function request 确认

16、信息 鉴权成功后被叫网络开始和被叫进行连接6.938 2b 00 00 11 07 01 04 l2 release indication 6.938 30 23 00 07 01 01 RT PM drel 7.172 2c 00 00 45 01 81 01 1e 02 82 88 l2 send to msg to l3第8页/共24页172 35 01 00 45 01 81 01 1e 02 82 88 CC PM: ALERT7.188 50 4d 00 PM - ADPCM enter commu7.188 27 00 00 10 01 00 00 04 08 4e 51 00

17、from L1 data -sacch7.203 27 00 00 10 01 00 00 04 1a 4f e0 01 from L1 data -sacch7.203 2d 00 00 01 06 00 ff l2 rx all ifrm before sending to l37.203 2c 00 00 45 01 81 07 l2 send to msg to l37.203 26 00 00 d1 0d 00 00 l2 to l1 data req -sacch7.203 35 07 00 45 01 81 07 CC PM: CONNECT当被叫向网络传送CC Alerting

18、时主叫方听到回铃音当被叫向网络传送CC Connect时主被方开始正式通话如被叫没有和网络连接成功则会听到网络提示音根据以上,可以在测试MO时,我们无需听回铃音来判断主叫方是否与网络连接,只要看到计时开始就算成功MO一次.Alerting/connect第9页/共24页切换切换第10页/共24页基本介绍基本介绍1) 基站和手机都有权利发起切换。2) FER是怎么得到的：检验1.2s内即240帧的误帧数，它通过检测UW（识别字）中的16bit或32bit的数据是否正确，还有检验CRC是否正确，在通信信道里CRC是CI (逻辑信道标识) SA + I共180 bit数据产生的16bit的数据，在控

19、制信道里它是由PR(前导码)CAC(公共接入信道)共170bit数据产生的16个bit的数据，其中PR在控制时隙中为了更好的实现位时钟同步，它的数据是固定不便的62bit的数据, 通信信道里的PR为6bit。PS：在待机是FER值永远不会高于1。3) 手机侧如何判断做什么切换：在此以手机侧发起切换为例子，当RSSI值波动不大，但FER很大时，说明收到干扰，但此时离原来的CS的距离没什么变化，只是这个TCH信道不能用，则一般执行TCH切换；当RSSI值下降，此时一般来说FER也会升高，则是说明原CS不能使用需要执行RECALL切换。无缝切换比较特殊，在每个支持无缝切换的手机中会有一系列的参数来确

20、定无缝切换的门限，总的说是还是看RSSI和FER来确定判断：RSSI： 强信号区- RSSI-1 当RSSI在某一瞬间跨区跳变则做无缝 次强区- RSSI-2 切换，3个门限依照不同的手机确定， 次弱区- RSSI-3 228的RSSI-1为40，RSSI-2为36FER:当在1.2秒内FER突然高于一个特定值时，手机做无缝切换。4）3种切换在流程上的区别：recalling切换在流程上和主叫流程相仿，只是少了Alerting和鉴权俩个步骤，而TCH切换因为不需要重新选择基站则不需要进行建链。无缝切换与 recalling 的区别：2 ports status,在新的链路上CC setup之后

21、断开原语音通道，所以无缝切换基本对用户通话不产生影响。第11页/共24页基本介绍基本介绍5)切换的典型log语句:在分析R200协议前,简单介绍一下Sanyo protocol :(1) 06:06 14 00 00 33 03 29 00 1a 40 10 10 RSSI-FER(No.1TCH) RSSI (33)and FER (03),(2) 06:06 77 77 83 01 83 0b 01 33 83 39 35 34 38 2c 18 01 ba 33为RSSI值，83为FER值39为待机切换目标基站电平值，35为待机电平切换值（开始寻找别的基站）34为通话电平切换值（开始寻找

22、别的基站），38为通话切换目标基站电平值(3) 06:07 33 ca 00 TR306P(new CS monitor)T/O handover start(普通切换)(4) 06:07 3f 00 33 9e 01 12 30 12 03 3c 00 Handover CCH Monitor monitor CS, CS-ID(9e 01 12 30 12 03 ) and RSSI(3c)(5) 06:07 12 01 00 19 00 00 9e 01 10 5e 28 03 cch_est_req 切换的目标基站CS-ID(6) 06:09 3e 2e 00 00 00 00 00

23、00 00 U wave testing end display 信道检测,最后一位为00表示此信道没有干扰(7) 06:10 31 07 01 45 01 85 07 1c 06 91 a2 03 02 01 01 Response handover end(成功切换)第12页/共24页基本介绍基本介绍R200 protocol:(1)2971.573 30 2a 00 08 RT do recalling handover 开始做recalling切换(2)9.414 31 5a 00 07 02 RT - PM handover start 9.414 31 ca 00 08 RT PO

24、RT1 - PORT2 monitor req 开始做seamless切换(3)42.151 30 c9 00 20 10 01 RT - L1 tch change completed in seamless 42.151 30 c9 00 07 01 aa RT - L1 tch change completed in seamless 42.161 31 cc 00 07 01 RT PORT1 PM handover switch or recall end 结束切换流程 (5)248.808 30 27 00 08 RT PM handover start 200.168 31 ca

25、 00 08 RT PORT1 - PORT2 monitor req 开始做seamless切换 200.168 40 33 00 05 42 26 37 33 34 38 d5 pm send rssi indication to MMI 200.178 44 3b 00 02 a0 pm send ho start indication to MMI 200.178 30 ca 00 32 01 RT PORT2 - PORT1 monitor req 200.178 80 01 00 01 1a 45 L1 cch monit 寻找新的可用的满足seamless切换的载频没有monit

26、到任何合适基站如果找到会在次列出基站列表 200.418 30 04 00 f2 0d RT - L1 primitive 200.418 31 cc 00 01 00 aa RT PORT1 PM handover switch or recall end 200.428 4b 39 00 60 b6 pm send mmi ho end ind when seamless wait tch 200.428 50 60 00 200.438 49 48 00 52 18 00 01 a0 pm send cc smho end req in global function 200.438 3

27、5 9f 00 00 01 01 00 00 CC CS link cch req 在找到新CS后,向新的CS做业务信道分配请求 886.014 30 0f 00 20 08 00 00 00 00 00 00 00 00 3b RT - L1 pch information 886.054 30 04 00 20 07 01 0a RT - L1 primitive 886.114 30 0f 00 20 08 00 00 00 00 00 00 00 00 3b RT - L1 pch information 886.915 30 0f 00 20 08 00 00 00 00 00 00

28、 00 00 3c RT - L1 pch information 887.016 30 0f 00 20 08 1a 57 18 75 25 85 10 00 3c RT - L1 pch information 887.116 30 11 00 20 08 ff ff ff ff ff 85 10 00 RT - L1 null scch information 887.216 30 0f 00 20 08 00 00 00 00 00 00 00 00 3c RT - L1 pch information 887.266 30 04 00 f2 01 RT CS link cch req

29、 向该基站重新请求业务信道第15页/共24页常见问题常见问题2.TR101P:200ms, 4次超时结束切换Start conditions: Without unwanted signal in the TCH designated by “Link channel assignment”Stop conditions: “Synchronization establishment” reception 887.647 80 0c 00 14 05 29 40 0a L1 indication uwave to RT 887.647 30 04 00 20 02 01 00 RT - L1

30、primitive 887.657 30 09 00 03 00 aa RT - L1 uwave IND 在获得业务信道以后,向该信道发送同步信息. 887.657 80 0a 00 05 4d 00 02 L1 est tch 887.857 30 04 00 f2 02 RT CS link cch rereq 重新请求信道在log中我们能发现在建链中存在大量的TR001和TR101超时,这个是无法避免的,但是他们的存在确实对手机在弱信号区的切换有很大的影响,第16页/共24页常见问题常见问题3.掉话：1.网络主动断线引起掉话, 106.973 2d 00 00 00 02 7e 07

31、l2 rx all ifrm before sending to l3 106.983 27 00 00 00 00 04 06 8e 40 21 from L1 data -sacch 106.983 2d 00 00 00 03 43 01 l2 rx all ifrm before sending to l3 107.003 27 00 00 00 00 04 18 0d 24 00 from L1 data -sacch 107.003 2d 00 00 01 04 04 81 l2 rx all ifrm before sending to l3 107.003 2c 00 00 4

32、5 01 07 45 08 03 02 85 90 l2 send to msg to l3 107.003 26 00 00 00 04 b1 0d l2 to l1 data req -(sacch) 107.003 35 45 00 45 01 07 45 08 03 02 85 90 CC PM: DISCONNECT 此时的掉话往往没有征兆,突然断线,这个现象不是我们软件协议所能控制的,在现实log中此类的断线比例也不是很高,所以我们一般不对这种掉线分析。 第17页/共24页2.新的TCH建立失败而掉话.(切换流程中)1)同步超时: 37.634 30 41 00 0e f2 0d

33、RT TRMONITP Timer Out 37.634 30 4b 00 9e 01 11 ae a6 02 RT CS_ID 37.634 30 4b 00 9e 01 11 ae a6 02 39 RT CS_ID 找到一个合适的基站 37.634 31 57 00 01 02 02 09 00 RT - CS link cch req 向该CS做建TCH请求 37.634 80 1c 00 02 03 L1 ready to tx scch 38.896 30 04 00 f2 01 RT CS link cch req 重新请求 38.896 80 1c 00 05 03 L1 re

34、ady to tx scch 38.976 30 0f 00 20 08 00 00 00 00 00 00 00 00 36 RT - L1 pch information 38.996 80 11 00 07 0a L1 scch tx cfm 38.996 30 04 00 20 07 00 0a RT PM handover switch or recall end 切换停止 39.697 48 39 00 00 47 pm send ho end indication to MMI in HO 40.709 30 04 00 f2 14 RT CS link cch req 向该CS

35、做建TCH请求 195.891 80 1c 00 02 05 L1 ready to tx scch 196.052 30 0f 00 20 08 00 00 00 00 00 00 00 00 3c RT - L1 pch information 196.082 80 11 00 07 0a L1 scch tx cfm . 211.263 80 12 00 04 01 0a aa 14 be 13 14 24 00 a2 18L1 rx NULL msg 211.303 50 63 00 f5 0a 02 00 00 00 04 08 211.303 50 5f 00 211.303 34

36、 0a 00 51 0b 00 00 MM get PM a disc command TCH建立时间太长,超过PM TIMER(15S),从而掉话. 在切换中都要重新建立TCH,所以一半以上的掉话都是由于TCH建立失败而导致.第19页/共24页常见问题常见问题3.switch back失败而掉话(切换不成功而switch back) 444.960 80 01 00 00 37 L1 cch monit 444.960 80 01 00 00 36 L1 cch monit 444.970 30 04 00 f2 0d RT - L1 primitive 444.970 30 41 00 0

37、e f2 0d RT TRMONITP Timer Out 没有合适的基站进行HO切换 444.970 80 0a 00 03 22 02 01 L1 est tch 445.922 30 04 00 f2 0c RT PM handover switch or recall end 445.922 48 39 00 00 22 pm send ho end indication to MMI in HO 445.922 50 60 00 447.023 30 04 00 f2 14 RT - L1 primitive 447.033 30 48 00 0d f2 14 RT TRDLRELP Timer Out Send RT “Radio-channel disconnection complete”在现实中有大半掉线情况由于switch back失败而导致.一般手机在弱信号区因为话音质量的降低而导致连