中国联通CSFB测试的主要流程信令

中国联通FDD_LTE的CSFB测试和分析

一、前言

本文主要针对联通FDD-LTE网络，使用华星FLY6.0进行CSFB测试和分析；CSFB 涉及4G侧(LTE)、3G侧（WCDMA）和MSC核心网侧三方的配合。以下主要是针对测试和事件消息流程进行分析和说明。

二、CSFB测试流程

CSFB测试过程主要是主叫4G手机、被叫4G手机分别驻留LTE网络中，连接FLY6.0测试软件，进行主叫4G手机拨打被叫4G手机，主叫4G手机和被叫4G手机分别回落至WCDMA网络进行通话的过程。

CSFB测试流程主要分为测试准备、测试过程和测数据统计三个部分：

4、从主被叫的CSFB信令流程来看，主被叫的CSFB信令流程是否正常？一定要查看主被叫的CSFB的起呼、4G 网络RRC释放、4G重选至3G、3G的RRC\RAB\Alerting的完整起呼流程。验证完全完整后，才算合格。

数据统计1、单站报告中CSFB成功率统计

2、CSFB的log记录备份

3、若存在测试不成功现象，可初步按照

第4节指导进行初步分析原因，待调整后

复测

分析原因一定要细分类，描述清晰，复

测一定要确定故障消除

三、正常CSFB信令流程

3.1.主叫主要流程

当开机做主叫时，UE首先在FDD_LTE注册（attach）,完成注册后进行拨号；

通过E_nodeB上发CSFB请求；其主要流程如下：

3.1.1开机注册（attach）

注册请求消息Attach Request(层三消息RRCConnectionRequest)由UE发出（消息属NAS层），请求中包括UE注册的小区，UE支持的加密算法和方式；联合注册的4G（TAC）和3G(LAC/RAC)及ClassMark;

Attach request MORE: 0 LENGTH: 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 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: 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_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

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 supported 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 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: 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 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