版權(quán)說明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請進行舉報或認領(lǐng)
文檔簡介
1、 中國聯(lián)通FDD_LTE的CSFB測試和分析一、 前言本文主要針對聯(lián)通FDD-LTE網(wǎng)絡,使用華星FLY6.0進行CSFB測試和分析;CSFB涉及4G側(cè)(LTE)、3G側(cè)(WCDMA)和MSC核心網(wǎng)側(cè)三方的配合。以下主要是針對測試和事件消息流程進行分析和說明。二、 CSFB測試流程CSFB測試過程主要是主叫4G手機、被叫4G手機分別駐留LTE網(wǎng)絡中,連接FLY6.0測試軟件,進行主叫4G手機撥打被叫4G手機,主叫4G手機和被叫4G手機分別回落至WCDMA網(wǎng)絡進行通話的過程。CSFB測試流程主要分為測試準備、測試過程和測數(shù)據(jù)統(tǒng)計三個部分:步驟工作項目備注測試準備1、測試手機是否支持FDD-LTE
2、和3G雙模;使用中興Q801U測試手機,支持FDDLTE和WCDMA2、測試SIM卡是否具備4G和3G屬性測試卡4G/3G測試都具備;部分老3G卡需增加4G屬性;刪除4G屬性的卡會出現(xiàn)“AU鑒權(quán)失敗,無法駐留4G網(wǎng)絡”現(xiàn)象3、測試手機是否連接FLY6.0 測試軟件,并進行記錄每個小區(qū)都需要記錄CSFB測試log3、測試手機是否開啟"LTE和WCDMA"雙模模式,手機“網(wǎng)絡模式”中4、手機選擇雙模后,是否穩(wěn)定駐留4G;5、無線環(huán)境是否穩(wěn)定?(RSRP>-100dBm,SINR>0dB)6、從空口消息觀察TAC配置,檢查TAC和LAC的對應關(guān)系是否正常; 測試過程1
3、、主叫手機和被叫手機是否穩(wěn)定駐留在4G網(wǎng)絡;2、主叫4G手機撥打被叫4G手機,是否撥通?進行重復多次嘗試;1、若是未撥通,是否聽見回鈴音,判斷主叫信令是否正常;2、若主叫信令正常,判斷被叫尋呼消息和CSFB信令是否正常3、從主被叫的KPI統(tǒng)計中觀測CSFB是否統(tǒng)計正常?4、從主被叫的CSFB信令流程來看,主被叫的CSFB信令流程是否正常?一定要查看主被叫的CSFB的起呼、4G網(wǎng)絡RRC釋放、4G重選至3G、3G的RRCRABAlerting的完整起呼流程。驗證完全完整后,才算合格。數(shù)據(jù)統(tǒng)計1、單站報告中CSFB成功率統(tǒng)計2、CSFB的log記錄備份3、若存在測試不成功現(xiàn)象,可初步按照第4節(jié)指導
4、進行初步分析原因,待調(diào)整后復測分析原因一定要細分類,描述清晰,復測一定要確定故障消除三、 正常CSFB信令流程3.1.主叫主要流程當開機做主叫時,UE首先在FDD_LTE注冊(attach),完成注冊后進行撥號;通過E_nodeB上發(fā)CSFB請求;其主要流程如下:3.1.1開機注冊(attach)注冊請求消息AttachRequest(層三消息 RRCConnectionRequest)由UE發(fā)出(消息屬NAS層),請求中包括UE注冊的小區(qū),UE支持的加密算法和方式;聯(lián)合注冊的4G(TAC)和3G(LAC/RAC)及ClassMark;Attach request MORE: 0 LENGTH
5、: 123 LENGTH: 123 LOG_CODE: B0ED timeStamp: 16:20:28.016 LTE NAS EMM plain OTA outgoing msg LOG_VERSION: 1 STD_VERSION: 9 STD_VERSION_MAJOR: 5 STD_VERSION_MINOR: 0 NAS: Attach request Security Header Type: 0 Protocol Discriminator: 7 Message_Types: 65 NAS key set identifier TSC: 0 - native security
6、context NASkeysetidentifier: 1 EPS attach type EPS attach type value: 2 - combined EPS/IMSI attach EPS mobile identity Length of EPS mobile identity contents: 11 odd_even indic: 0 - even number of identity digits and also when the GUTI is used Type of identity: 6 - GUTI MCC: 460 MNC: 01 MMEGroupID:
7、9A00 MMECode: 206 M_TMSI: 9A00CC345E25 UE network capability EEA0: 1 - supporte 128_EEA1: 1 - supported 128_EEA2: 1 - supported EEA3: 0 - not supported EEA4: 0 - not supported EEA5: 0 - not supported EEA6: 0 - not supported EEA7: 0 - not supported EIA0: 0 - not supported 128_EIA1: 1 - supported 128_
8、EIA2: 1 - supported EIA3: 0 - not supported EIA4: 0 - not supported EIA5: 0 - not supported EIA6: 0 - not supported EIA7: 0 - not supported UEA0: 1 - supported UEA1: 1 - supported UEA2: 0 - not supported UEA3: 0 - not supported UEA4: 0 - not supported UEA5: 0 - not supported UEA6: 0 - not supported
9、UEA7: 0 - not supported UCS2: 0 - not supported UIA1: 1 - supported UIA2: 0 - not supported UIA3: 0 - not supported UIA4: 0 - not supported UIA5: 0 - not supported UIA6: 0 - not supported UIA7: 0 - not supported ACCCSFB: 1 - supported LPP: 0 - not supported LCS: 0 - not supported _1xSRVCC: 0 - not s
10、upported NF: 1 - supported ESM message container Length: 38 ESM message container contents: 02,03,D0,31,27,20,80,80,21,10,01,00,00,10,81,06,00,00,00,00,83,06,00,00,00,00,00,0D,00,00,03,00,00,0A,00,00,10,00 PDN connectivity request Security Header Type: 0 Protocol Discriminator: 2 Message_Types: 208
11、PDN type PDN type value: 3 - IPv4v6 Request type Request type value: 1 - initial request Protocol configuration options Length: 32 ProtocolID 0x: 8021 Length of protocol: 16 code: 1 - Configure-Request Identifier: 0 length: 16 Type: 129 - Primary DNS Server IP Address len: 6 IP Address: 0.0.0.0 Type
12、: 131 - Secondary-DNS-Address len: 6 IP Address: 0.0.0.0 ProtocolID 0x: 0D Length of protocol: 0 Tracking area identity MCC: 460 MNC: 01 TAC: 37135 DRX parameter SPLIT PG CYCLE CODE: 10 CN Specific DRX cycle length coefficient and DRX value for S1 mode: 0 SPLIT on CCCH: 0 - is not supported non-DRX
13、timer: 0 - no non-DRX mode after transfer state MS network capability Length of MS network capability contents: 3 MS network capability value: E5,C0,3E Location area identification MCC: 460 MNC: 10 Lac: 47889 Mobile station class mark 2 Revision level: 2 - Used by mobile stations supporting R99 or l
14、ater versions of the protocol ESIND: 0 - <Controlled Early Classmark Sending> option is not implemented A5/1 algorithm supported: 1 - not available RF Power Capability: reserved PS capability: 0 - not present SS Screening Indicator: 1 defined in GSM 04.80 SM capability: 1 - Mobile station supp
15、orts mobile terminated point to point SMS VBS notification reception: 0 - no VBS capability or no notifications wanted VGCS notification reception: 0 - no VGCS capability or no notifications wanted FC Frequency Capability: 0 - The MS does not support the extension band G1 in addition to the primary
16、GSM band CM3: 1 - The MS supports options that are indicated in class mark 3 IE LCSVA capability: 1 UCS2: 0 - the ME has a preference for the default alphabet over UCS2 SoLSA: 0 - The ME does not support SoLSA CMSP: 1 - Network initiated MO CM connection request supported for at least one CM protoco
17、l A5/3 algorithm supported: 1 - not available A5/2 algorithm supported: 0 - available Spare half octet Length Of Supported Codec list: 8 System Identification: 4 Length Of Bitmap for SysID: 2 Length Of Bitmap for SysID: 60 Length Of Bitmap for SysID: 04 System Identification: 0 Length Of Bitmap for
18、SysID: 2 Length Of Bitmap for SysID: 1F Length Of Bitmap for SysID: 02 Voice domain preference and UE's usage setting Length of Voice domain preference and UE's usage setting contents: 6 UE's usage setting: 0 - Voice centric UE's usage setting: 0 - CS Voice only Voice domain preferen
19、ce and UE's usage setting GUTI type: 0 - Native GUTI MS network feature support Extended periodic timers: 1 - MS support3.1.2注冊(attach)成功 UE收到RRCConnectionSetup消息,進行注冊Attach Accepet(層三消息RRCConnectionSetupComplete),成功消息中包括注冊的小區(qū)MCC,MNC,MME GroupID,MME Code及UE的M_TMSI等信息3.1.3 UE語音業(yè)務請求(CSFB MT START)
20、 UE上發(fā)Ext service request(NAS到 EMM)消息,內(nèi)容為CS fall back業(yè)務請求;Extended service request MORE: 0 LENGTH: 35 LENGTH: 35 LOG_CODE: B0ED timeStamp: 16:20:44.796 LTE NAS EMM plain OTA outgoing msg LOG_VERSION: 1 STD_VERSION: 9 STD_VERSION_MAJOR: 5 STD_VERSION_MINOR: 0 NAS: Extended service request Security Hea
21、der Type: 0 Protocol Discriminator: 7 Message_Types: 76 NAS key set identifier TSC: 0 - native security context NASkeysetidentifier: 1 Service type Service type value: mobile originating CS fall back or 1xCS fall back Mobile identity Odd/even indication: 0 - even number of identity digits and also w
22、hen the TMSI/P-TMSI or TMGI and optional MBMS Session Identity is used Type of identity: 4 - TMSI/P-TMSI Identity digits (0x): DC345E25 EPS bearer context status length: 32 EBI: 03.1.4 E_nodeB指標UE回落E_nodeB在下發(fā)給UE的RRCConnectionRelease中給出重定向的目標(utra_FDD=10713)RRCConnectionRelease MORE: 0 LENGTH: 1993 L
23、ENGTH: 1993 LOG_CODE: B0C0 timeStamp: 16:20:44.928 RRCConnectionRelease VERSION: 7 RRC_REL: 10 RRC_REL: 113 RRC_VER: 1 PHYSICAL_CELL_ID: 368(4G服務小區(qū)) FREQ: 1650 System_Frame_Number: 34 Subframe: 8 PDU_NUM: 6 ENCODED_MSG_LEN: 1964 RRC: DL-DCCH-Message message c1 rrcConnectionRelease rrc_TransactionIde
24、ntifier = 0 criticalExtensions c1 rrcConnectionRelease_r8 releaseCause = other redirectedCarrierInfo(重定向方向) utra_FDD = 10713 nonCriticalExtension nonCriticalExtension cellInfoList_r9 (以下是3G鄰區(qū)擾碼) utra_FDD_r90 physCellId_r9 = 201 utra_FDD_r91 physCellId_r9 = 209 utra_FDD_r92 physCellId_r9 = 233 utra_F
25、DD_r93 physCellId_r9 = 393 utra_FDD_r94 physCellId_r9 = 11 utra_FDD_r95 physCellId_r9 = 35 utra_FDD_r96 physCellId_r9 = 448 utra_FDD_r97 physCellId_r9 = 3 3.1.5UE在3G網(wǎng)絡進行呼叫UE讀取3G網(wǎng)絡系統(tǒng)消息,發(fā)起業(yè)務請求(CM Sercive Request);請求中包括業(yè)務類型,UE能力和支持的加密類型等等CM service request MORE: 0 LENGTH: 31 LENGTH: 31 LOG_CODE: 713A t
26、imeStamp: 16:20:45.832 UMTS NAS Signaling Messages Direction: From UE Length: 14 ChannelType: 5 MessageType: 36 UMTS NAS Signaling Messages: CM service request CM service type Service Type : 0 Ciphering key sequence number key sequence : 1 Mobile station classmark Revision level : 2 - Used by mobile
27、 stations supporting R99 or later versions of the protocol ESIND : 1 - (<Controlled Early Classmark Sending> option is implemented). A5/1 algorithm supported : 0 - (available) RF Power Capability : 7 - reserved PS capability : 1 - (present) SS Screening Indicator : 1(defined in GSM 04.80) SM c
28、apability : 1 - Mobile station supports mobile terminated point to point SMS VBS notification reception : 0 - no VBS capability or no notifications wanted VGCS notificationr eception : 0 - no VGCS capability or no notifications wanted 0 - The MS does not support the extension band G1 in addition to
29、the primary GSM bandClassmark 3(CM3) : 1 - The MS supports options that are indicated in classmark 3 IE LCSVA capability : 1 UCS2 : 0 - the ME has a preference for the default alphabet over UCS2 SoLSA : 0 - The ME does not support SoLSA CMSP : 1 - Network initiated MO CM connection request supported
30、 for at least one CM protocol A5/3 algorithm supported : 1 - (not available) A5/2 algorithm supported : 0 - (available) Mobile identity Type of identity : 4 - TMSI/P-TMSI Odd/even indication : 0 Identity digits : 0x03C3239B3.1.6. RAU和RAB建立在3G網(wǎng)絡進行RAU(ROUTING AREA UPDATE REQUEST),無線承載建立請求(RadioBearerS
31、etupComplete),為UE分配無線資源 RadioBearerSetupComplete MORE: 0 LENGTH: 26 LENGTH: 26 LOG_CODE: 412F timeStamp: 16:20:47.026 RRC: UL_DCCH integrityCheckInfo messageAuthenticationCode = 32, 0xB6 0x11 0x69 0x93 rrc_MessageSequenceNumber = 2 message radioBearerSetupComplete rrc_TransactionIdentifier = 0 start
32、_Value = 20, 0x00 0x00 0110xxxx count_C_ActivationTime = 2083.1.7. 振鈴(Alerting)在3G網(wǎng)絡無線資源分配完成后,網(wǎng)絡發(fā)振鈴消息給UE3.1.8.接通(Connect)被叫摘機,鏈路連通主,被開始通話 3.1.9.掛機(Disconnect)結(jié)束通話后主呼掛機,上發(fā)拆鏈消息(Disconnect), 下(上)行 RRC釋放后,通話結(jié)束;在E_nodeB下發(fā)的RRCConnectionRelease消息中指出了,UE返回4G中心頻率(1650)RRCConnectionRelease MORE: 0 LENGTH: 27 LENGTH: 27 LOG_CODE: 412F timeStamp: 16:21:10.142 RRC: DL_DCCH integrityCheckInfo messageAuthenticationCode = 32, 0x8D 0xAB 0xEB 0x8C rrc_MessageSequenceNumber = 1 message rrcConnectionRelease r3 rrcConnectionRelease_r3 rrc_Tr
溫馨提示
- 1. 本站所有資源如無特殊說明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請下載最新的WinRAR軟件解壓。
- 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
- 3. 本站RAR壓縮包中若帶圖紙,網(wǎng)頁內(nèi)容里面會有圖紙預覽,若沒有圖紙預覽就沒有圖紙。
- 4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
- 5. 人人文庫網(wǎng)僅提供信息存儲空間,僅對用戶上傳內(nèi)容的表現(xiàn)方式做保護處理,對用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對任何下載內(nèi)容負責。
- 6. 下載文件中如有侵權(quán)或不適當內(nèi)容,請與我們聯(lián)系,我們立即糾正。
- 7. 本站不保證下載資源的準確性、安全性和完整性, 同時也不承擔用戶因使用這些下載資源對自己和他人造成任何形式的傷害或損失。
最新文檔
- 2024無人機研發(fā)與飛行服務合同
- 2025年度高檔別墅窗戶定制安裝與維護保養(yǎng)合同3篇
- 二零二五版程海流域生態(tài)保護與可持續(xù)發(fā)展合同2篇
- 中原地產(chǎn)房屋買賣居間協(xié)議(2024年度版)版
- 個人在線醫(yī)療咨詢服務平臺合作協(xié)議(2024版)2篇
- 未來教育趨勢與終身學習規(guī)劃的構(gòu)建
- 個人抵押借款合同書樣例版
- 2025年度金融機構(gòu)與個人消費貸款合同范本4篇
- 2025版壓路機設備租賃及維護管理合同范本3篇
- 現(xiàn)代餐飲業(yè)營銷策略及服務流程優(yōu)化
- 泌尿:膀胱腫瘤病人的護理查房王雪-課件
- 標點符號的研究報告
- 服務器報價表
- 2025年高考化學試題分析及復習策略講座
- 2024-2029年中國制漿系統(tǒng)行業(yè)市場現(xiàn)狀分析及競爭格局與投資發(fā)展研究報告
- 大門封條模板
- 【“凡爾賽”網(wǎng)絡流行語的形成及傳播研究11000字(論文)】
- ppr管件注塑工藝
- 液化氣站其他危險和有害因素辨識及分析
- 高中語文教學課例《勸學》課程思政核心素養(yǎng)教學設計及總結(jié)反思
- 中國農(nóng)業(yè)銀行小微企業(yè)信貸業(yè)務貸后管理辦法規(guī)定
評論
0/150
提交評論