通信人家园

标题: Connect状态下在DRX周期延长有出现的掉话率变化问题  [查看完整版帖子] [打印本页]

时间:  2015-7-21 22:24
作者: matrixff     标题: Connect状态下在DRX周期延长有出现的掉话率变化问题

个人在做测试的时候出现了一下问题:
测试的内容主要是把连接态下的DRX Cycle从80ms延长到2560ms,同时开启short DRX。
具体的参数和细节如果需要再描述。

现在出现了一些性能上的问题想请教各位:
首先是EPC发起的UE Context Release大量上升,从每天7000增加值9000左右
其次是eNB发起的RNL原因的UE Context Release或者ERAB release request从27k减少到16k
但是在UE缓存有数据情况下ERAB应为RNL原因被eNB释放的数量从1k增加到2k
另外还有大量的RRC重建请求被reject

哪位能帮我梳理一下以上变化的原因?感谢!


时间:  2015-7-23 03:33
作者: matrixff

:求答疑
时间:  2015-7-27 17:44
作者: matrixff

自己顶一下
时间:  2015-7-29 04:27
作者: matrixff

今天意外找到了第一个问题(EPC发起的UE Context Release大量上升)的形成原因,属于和制造商配置相关的问题。

本网存在大量national roaming的用户,当这些用户从漫游网回到本网LTE的时候发起TAU时QCI为7(继承漫游网配置),TAU成功后本网EPC发起ERABModifyRequest(因为本网的默认承载QCI6).
但是根据S1 trace,eNB收到ERABModifyRequest之后直接拒绝了修改ERAB,Response给EPC告知ERABModify Failure子原因 Radio Network - Cause unspecified.

因此EPC下发UE Context Release Request,造成了相关counter的增加。

eNB拒绝的原因其实是QCI6和QCI7的配置表里DRX Profile Id不一致,另外如果PDCP Profile Id不一致也会导致ERAB修改失败。产品文档和特性文档里有没有说明。不过问题总算解决了一部分,虽然原因实在有点让人无语。

Ps,诺记产品
时间:  2015-7-29 21:30
作者: childish2012

协议规定一般的重配置确实是不能修改PDCP的相关参数的,比如支持的头压缩算法等,不过可以通过full config方式重配置修改;DRX相关参数应该是支持修改的。
时间:  2015-7-30 16:16
作者: matrixff

childish2012 发表于 2015-7-29 21:30
协议规定一般的重配置确实是不能修改PDCP的相关参数的,比如支持的头压缩算法等,不过可以通过full config方 ...

非常感谢。

有相关协议的章节吗? 想看一下。

Ps, Full Config具体是什么意思?
时间:  2015-8-15 16:08
作者: childish2012

参见36.331 5.3.5.8节,如下:

5.3.5.8        Radio Configuration involving full configuration option
The UE shall:
1>        release/ clear all current dedicated radio configurations except the C-RNTI, the security configuration and the PDCP, RLC, logical channel configurations for the RBs and the logged measurement configuration;
NOTE 1:        Radio configuration is not just the resource configuration but includes other configurations like MeasConfig and OtherConfig.
1>        if the RRCConnectionReconfiguration message includes the mobilityControlInfo:
2>        release/ clear all current common radio configurations;
2>        use the default values specified in 9.2.5 for timer T310, T311 and constant N310, N311;
1>        else:
2>        use values for timers T301, T310, T311 and constants N310, N311, as included in ue-TimersAndConstants received in SystemInformationBlockType2;
1>        apply the default physical channel configuration as specified in 9.2.4;
1>        apply the default semi-persistent scheduling configuration as specified in 9.2.3;
1>        apply the default MAC main configuration as specified in 9.2.2;
1>        for each srb-Identity value included in the srb-ToAddModList (SRB reconfiguration):
2>        apply the specified configuration defined in 9.1.2 for the corresponding SRB;
2>        apply the corresponding default RLC configuration for the SRB specified in 9.2.1.1 for SRB1 or in 9.2.1.2 for SRB2;
2>        apply the corresponding default logical channel configuration for the SRB as specified in 9.2.1.1 for SRB1 or in 9.2.1.2 for SRB2;
NOTE 2:         This is to get the SRBs (SRB1 and SRB2 for handover and SRB2 for reconfiguration after reestablishment) to a known state from which the reconfiguration message can do further configuration.
1>        for each eps-BearerIdentity value included in the drb-ToAddModList that is part of the current UE configuration:
2>        release the PDCP entity;
2>        release the RLC entity or entities;
2>        release the DTCH logical channel;
2>        release the drb-identity;
NOTE 3:         This will retain the eps-bearerIdentity but remove the DRBs including drb-identity of these bearers from the current UE configuration and trigger the setup of the DRBs within the AS in Section 5.3.10.3 using the new configuration. The eps-bearerIdentity acts as the anchor for associating the released and re-setup DRB.
1>        for each eps-BearerIdentity value that is part of the current UE configuration but not part of the drb-ToAddModList:
2>        perform DRB release as specified in 5.3.10.2;





通信人家园 (https://www.txrjy.com/) Powered by C114