大数跨境

今日分享:TAU失败导致UE无法正常使用4G网络

今日分享:TAU失败导致UE无法正常使用4G网络 嘉誉数字化科技
2018-02-09
2
导读:因篇幅所限,为了给您更好的体验,我们使用二维码扫码查看和保存文件的方式呈现。

TAU失败导致UE无法正常使用4G网络

 

1     问题现象

用户为CSFB手机,在1月6日18点左右由4G网络掉至3G网络,并且在一天内跨越多个位置区,经过22小时的时间内一直无法回到4G网络,直到1月7日16点左右进行重新开关机后才回到4G网络。

2     信令分析

2.1    S1-MME信令

通过信令跟踪平台S1-MME信令分析,发现用户在2016-1-6 17:51:34进行了一次CSFB业务,并在完成业务后返回4G网络发起连续5次TAU,之后就没有4G侧信令,直至2016-1-7 16:10:06间隔22小时后重新在4G网络发起Attach,并在4G网络正常驻留。

2.2    SGs信令

分析SGs信令,发现用户在2016-1-6 17:52:00发起TAU的同时连续发起了5次联合位置更新,并且都失败,失败原因码为22,之后就没有信令,直至2016-1-7 16:10:07重新发起联合位置更新,并成功。

2.3    CSFB信令

分析CSFB侧信令,用户在挂机前发起了一个短信流程,导致用户挂机后系统没有发送clear command命令,UE无法进行FR;在后续进行的短信流程中,首先由UE向网络侧发起了一次主动短信流程,在网络侧等待CP-ACK的过程中,网络侧又向UE发送了一条短信,但未得到UE的响应,此后UE发起了一次CP-ACK,在完成后释放资源进入空闲态,并重选至4G网络进行联合位置更新

2G网络侧此时由于短信流程还未完成,认为UE还在2G网络中,并在随后对UE发起了1次被叫通话及被叫短信业务,但均为成功;UE在4G最后一次联合位置更新发生2016-01-06 17:52:40,早于2G网络侧下发clear command命令的时间2016-01-06 17:52:43,相当于UE在回到4G进行联合位置更新的同时,2G侧网络认为业务流程还未完成,导致连续5次联合位置更新失败

正常短信流程,UE在回应CP-ACK后返回空闲态

系统最后在定时器超时后下发clear command命令,命令中所携带的原因值为Radio interface failure,相当于系统判断由于得不到UE回应而导致的一次异常释放。

3     问题分析

3.1    失败原因值分析

通过3GPP TS 24.301协议分析原因码22的解释如下,该问题主要由MME问题导致。

协议描述:

Cause #22 –Congestion

       This EMM causeis sent to the UE because of congestion in the network (e.g. no channel,facility busy/congested etc.)

 

3.2   失败处理流程分析

发生该问题后的处理策略,协议描述如下,一共尝试5次TAU请求,每次间隔为T3411(10s),当达到5次后,根据终端类型是CS/PSmode 1还是CS/PS mode 2进行不同的流程。

如果终端是是CS/PSmode 1,并且不支持IMS voice,终端将选至2G/3G网络,并关闭4G网络功能,保证语音业务。

如果终端是CS/PSmode 2,终端等待T3402(12min),然后重新发起联合TA/LA更新。

协议描述:

Combinedtracking area updating successful for EPS services only

#22   (Congestion)

     The UE shall stop timer T3430 if still running. The trackingarea updating attempt counter shall be incremented, unless it was already setto 5.

     If the tracking area updating attempt counter is less than 5:

-   the UE shall start timer T3411, shall set the EPS update status toEU1 UPDATED and shall enter state EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM. Whentimer T3411 expires the combined tracking area updating procedure indicating"combined TA/LA updating with IMSI attach" is triggered again.

     If the tracking area updating attempt counter is equal to 5:

-   a UE operating in CS/PS mode 2 of operation shall starttimer T3402, shall set the EPS update status to EU1 UPDATED and shall enterstate EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM. When timer T3402 expires thecombined tracking area updating procedure indicating "combined TA/LAupdating with IMSI attach" is triggered again;

-   a UE operating in CS/PS mode 1of operation with "IMS voice not available" shall attempt to selectGERAN or UTRAN radio access technology and proceed with appropriate MM or GMMspecific procedures. The UE shalldisable the E-UTRA capability (see subclause 4.5). If the UE isin the EMM-CONNECTED mode, the UE shall locally release the established NASsignalling connection and enter the EMM-IDLE mode before selecting GERAN orUTRAN radio access technology.

TIMER NUM.

TIMER VALUE

STATE

CAUSE OF START

NORMAL STOP

ON
  EXPIRY

T3411

10s

EMM-DEREGISTERED.   ATTEMPTING-TO-ATTACH

 

EMM-REGISTERED. ATTEMPTING-TO-UPDATE

At attach failure   due to lower layer failure, T3410 timeout or attach rejected with other EMM   cause values than those treated in subclause 5.5.1.2.5.

At tracking area   updating failure due to lower layer failure, T3430 timeout or TAU rejected   with other EMM cause values than those treated in subclause 5.5.3.2.5.

ATTACH REQUEST sent

TRACKING AREA UPDATE   REQUEST sent

Retransmission of   the ATTACH REQUEST or TRACKING AREA UPDATE REQUEST

T3430

15s

EMM-TRACKING-AREA-UPDATING-INITIATED

TRACKING AREA UPDATE   REQUEST sent

TRACKING AREA UPDATE   ACCEPT received

TRACKING AREA UPDATE   REJECT received

Start T3411 or T3402   as described in subclause 5.5.3.2.6

T3402

Default 12 min.

NOTE 1

EMM-DEREGISTERED

EMM-REGISTERED

At attach failure   and the attempt counter is equal to 5.

At tracking area   updating failure and the attempt counter is equal to 5.

ATTACH REQUEST sent

TRACKING AREA UPDATE   REQUEST sent

Initiation of the   attach procedure or TAU procedure

 

3.3   终端模式分析

协议中关于终端模式的描述如下,目前UE的工作模式主要有4种:PS mode 1 、PS mode 2、CS/PS mode 1、CS/PS mode 2,CS fallback终端工作在CS/PS mode 1、CS/PS mode 2,其主要区别在于CS/PS mode 1是语音优先(voice centric)、CS/PS mode 2是数据优先(data centric)。

根据协议,voice centric的终端,必须支持voice功能,如果注册到的LTE网络不支持CSFB,以及IMS等语音业务,那么终端应该关闭LTE的功能,重选回落2G/3G网络,用以保证语音业务使用。如果LTE网络支持CSFB/IMS语音业务,那么可以继续停留在LTE网络上。data centric的终端,如果注册到的LTE网络,既不支持CSFB,也不支持IMS业务,可以继续驻留在LTE网络。

协议描述:

A UE attached for EPS services shalloperate in one of thefollowing operation modes:

-   PS mode 1 ofoperation: the UE registers only to EPS services, and UE's usage setting is "voice centric";

-   PS mode 2 ofoperation: the UE registers only to EPS services, and UE's usage setting is "data centric" orthe UE has no CS voice capability;

-   CS/PS mode 1 of operation: theUE registers to both EPS and non-EPS services, and UE's usage setting is "voice centric"; and

-   CS/PS mode 2 of operation: the UE registers to both EPS andnon-EPS services, and UE's usage setting is "datacentric" or the UE has no CS voice capability.

A UE configured to use CS fallback, shall operate inCS/PS mode 1 or CS/PS mode 2. Such UE may also be configured to use IMS, in which case thevoice domain preference as defined in 3GPP TS 24.167 [13B] shallbe used for theselection of the domain for originating voice communication services.

A UEconfigured to use SMS over SGs, but not configured to use CS fallback, shalloperate in CS/PS mode 1 or CS/PS mode 2.

Thebehaviour of the UE in CS/PS mode 1 of operation, upon failure to access the CSdomain, will depend on the availability of voice over IMS. In the presentdocument, "IMSvoice not available" refers to one of the following conditions:

-   the UE is notconfigured to use IMS;

-   the UE is notconfigured to use IMS voice, i.e. when the voice domain preference, as definedin 3GPP TS 24.167 [13B], indicates that voice communication services areallowed to be invoked only over the CS domain;

-   the UE is configuredto use IMS voice, but the network indicates in the ATTACH ACCEPT message or theTRACKING AREA UPDATE ACCEPT message that IMS voice over PS sessions are notsupported; or

-   the UE is configuredto use IMS voice, the network indicates in the ATTACH ACCEPT message or theTRACKING AREA UPDATE ACCEPT message that IMS voice over PS sessions aresupported, but registration to IMS has failed.

当终端发起attach附着请求,或者TAU更新求时,会携带ue_usage_setting参数,说明终端是语音优先(voice centric)还是是数据优先(data centric)。通过信令跟踪平台,用户的终端为voicecentric,即CS/PS mode 1,且仅支持CS Voice only,不支持IMS voice。根据协议描述,当发生cause#22的联合位置更新失败时,终端将选至2G/3G网络,并关闭4G网络功能

3.4   返回4G网络方式

根据协议描述,当终端关闭4G网络后,只能通过模式改变、开关机、PLMN选网才可以恢复4G功能;因此用户长时间无法从2G/3G返回4G网络,只能通过开关机或飞行模式才能解决。

Disabling andre-enabling of UE's E-UTRA capability

Whenthe UE supporting the A/Gb and/or Iu mode together with the S1 mode needs tostay in A/Gb or Iu mode, in order to prevent unwanted handover or cellreselection from UTRAN/GERAN to E-UTRAN, the UE shall disable the E-UTRAcapability.

-   The UE shall not set the E-UTRA support bits of the MS Radio Access capabilityIE (see 3GPP TS 24.008 [13], subclause 10.5.5.12a),the E-UTRA support bits of Mobile Station Classmark3 IE (see 3GPP TS 24.008 [13],subclause 10.5.1.7) and the ISR support bit of the MS network capabilityIE (see 3GPP TS 24.008 [13],subclause 10.5.5.12)inthe ATTACH REQUEST message and the ROUTING AREA UPDATE REQUEST message after it selectsGERAN or UTRAN; and

-   the UE NAS layer shall indicate theaccess stratum layer(s) of disabling of the E-UTRA capability.

TheUE shall enable the E-UTRA capability again in the following cases:

-   the UEmode of operation changes from CS/PS mode 1 of operation to CS/PS mode 2 of operation;

-   the UEmode of operation changes from PS mode 1 of operation to PS mode 2 of operation;

-   the UEpowers off and powers on again; or

-   forthe PLMN selection purpose.

4     问题小结

通过上述的分析可以看出,此次UE从4G异常脱网的情况为用户在2G侧挂机的同时有多条短信业务发生,由于流程冲突,导致联合位置更新失败,由于UE为语音优先模式,按照协议规定,UE在5次联合位置更新失败后自动关闭4G功能,最终使UE脱离4G网络,并只能通过开关机或重选选网的方式恢复。

5     现网情况分析

5.1   联合TAU失败现状

受限于平台一次只能导出10万行数据的限制,只能对1个小时内出现的联合TAU失败进行分析,目前主要失败的原因有三种:已分析的原因值#22的TAU失败占整体的69%,#17的占23%,#12的占8%

5.2   #22原因值TAU失败影响分析

对1月15日全网用户数据进行分析:

一天内发生联合位置更新失败且原因值为22的次数约为:56万次,涉及26.2万个用户,其中符合上述分析情况(连续5次失败且间隔10s)的用户为:6332个,占全网566万个CSFB用户的0.11%,这些用户根据终端类型的不同,对用户及网络的影响也不同:

  • 数据优先:等待T3402(12min),然后重新发起联合TA/LA更新,在等待时长内用户可能无法被寻呼(待确认),直至重新TAU成功;对应影响的网络指标为寻呼成功率

  • 语音优先:终端将选至2G/3G网络,并关闭4G网络功能,直至手机进行开关机或重新选网操作(在已经分析的部分用户中,目前发现最长脱离4G网络的用户已超过5天);对应影响的网络指标为4G驻留比

目前NSN已推出一个针对MSS中AIF程序块(AIF_SSMX18.27-0)的补丁,此补丁是针对前期在国外发现的一种案例:UE掉话后,在等待呼叫重建超时(北京未开呼叫重建)期间拒绝联合位置更新情况,而这个补丁的作用是无论什么情况,只要MSS还没释放A接口资源,而此时收到UE的联合位置更新请求,那么MSS将立即释放A接口资源并及时处理联合位置更新请求,刚好也适应于解决本次发生的这种案例,这样就可以避免由于连续位置更新失败导致UE脱离4G网络,。

 

 

 

因篇幅所限,为了给您更好的体验,我们使用二维码扫码查看和保存文件的方式呈现

打开方式】:长按上图二维码,点击“识别图中二维码”,即可在线预览和下载该文档。




多个朋友多条路,随手分享给好友!

嘉誉网优十余年,无一例薪资拖欠,信用与实力的保障!

如需要了解详情,也可以在页尾点击“写留言”留下您的信息。

(点击“阅读原文”获取更详细信息)

【声明】内容源于网络
0
0
嘉誉数字化科技
本公号从战略、人才、技术等方面切入,由浅入深地介绍数字化转型的背景、目标和实现的路径,提供企业数字化转型的思路、工具、方法及案例。 嘉誉助力于企业在数字化转型这道必答题上找到最优解!
内容 93
粉丝 0
嘉誉数字化科技 本公号从战略、人才、技术等方面切入,由浅入深地介绍数字化转型的背景、目标和实现的路径,提供企业数字化转型的思路、工具、方法及案例。 嘉誉助力于企业在数字化转型这道必答题上找到最优解!
总阅读65
粉丝0
内容93