欢迎来逛逛,聊聊技术,侃侃大山.
本人主要喜欢WCDMA/TD-SCDMA无线侧的技术，如果有何关于无线技术方面的问题，你可以给我留言，我们可以一起讨论，共同提高。
Thinking more on Ericsson Log file(WCDMA)
2006-09-06 14:24:59
As we have a discussion about Ericsson's log file, pls refer to this:
http://bbs.cnttr.com/viewthread.php?tid=64963&extra=page%3D1
Here, I have more thinking on this topic. Firstly, let's check the normal AMR log file from Ericsson.
*******************************************************************************************************
A normal AMR call:
10:57:31.73 MS1 Not Valid UL RRC Connection Request (UL-CCCH) Call Attempt
10:57:31.91 MS1 Not Valid DL RRC Connection Setup (DL-CCCH)
10:57:32.15 MS1 Not Valid UL RRC Connection Setup Complete (UL-DCCH) RRC Established
10:57:32.25 MS1 Not Valid UL Initial Direct Transfer (UL-DCCH)
10:57:32.31 MS1 Not Valid DL Measurement Control (DL-DCCH)
10:57:32.42 MS1 Not Valid DL Downlink Direct Transfer (DL-DCCH)
10:57:32.42 MS1 Not Valid DL Authentication Request
10:57:32.58 MS1 Not Valid UL Authentication Response
10:57:32.58 MS1 Not Valid UL Uplink Direct Transfer (UL-DCCH)
10:57:32.75 MS1 Not Valid DL Security Mode Command (DL-DCCH)
10:57:32.75 MS1 Not Valid UL Security Mode Complete (UL-DCCH)
10:57:32.85 MS1 Not Valid UL Setup
10:57:32.86 MS1 Not Valid DL Downlink Direct Transfer (DL-DCCH)
10:57:32.86 MS1 Not Valid UL Uplink Direct Transfer (UL-DCCH)
10:57:32.86 MS1 Not Valid DL Identity Request
10:57:32.87 MS1 Not Valid UL Identity Response
10:57:32.87 MS1 Not Valid UL Uplink Direct Transfer (UL-DCCH)
10:57:32.97 MS1 Not Valid DL Downlink Direct Transfer (DL-DCCH)
10:57:32.98 MS1 Not Valid DL Call Proceeding
10:57:35.72 MS1 Not Valid DL Radio Bearer Setup (DL-DCCH)
10:57:36.13 MS1 Not Valid UL Radio Bearer Setup Complete (UL-DCCH)
10:57:36.45 MS1 Not Valid DL Radio Bearer Reconfiguration (DL-DCCH)
10:57:36.48 MS1 Not Valid UL Radio Bearer Reconfiguration Complete (UL-DCCH)
10:57:37.16 MS1 Not Valid DL Downlink Direct Transfer (DL-DCCH)
10:57:37.16 MS1 Not Valid DL Alerting Call Setup
*******************************************************************************************************
Pls notice the red marked part.
As we had discussed this on the previous article, and I had confrimed that CN will send the "RAB assignment" to RNC after the "call confirmed" had been received. From here, we can know Ericsson's CN will assign the resources for calling user after the response gotten from called user.
Here, what I want to say is the assignment of radio resource.
Normally, CN will send "RAB assignment" to RNC after the "SETUP" message(or "Identity Response") is received from calling user. Thus, the calling user will hold the radio resources of service(such as, SF128 for AMR) to wait for the acknowledge from called user.
----- for this, I had checked some log files from other verndors's implementation.
But for Ericsson, this is different.
Here, one topic bring to us--- How to balance the usage of radio resources and performance?
If you perform as Ericsson, you will face to the increase of drop call. Because if called user is ok, but fail to establish for calling user. Or you can do as other vendors's, but more radio resources will be needed. (becuase during the calling wating for the acknowledge from called user, only signalling is sent on this channel without user data) with better performance on drop call rate.
My suggestion is we need use this method under different case.
For example,
a) If you(in China) will dial a mobile or PSTN which locate in USA. Thus, it's worth to assign radio resources to calling user as eraly as you can.
b) If you will dial a local number, maybe CN could send the "RAB assignment" to RNC after the confirmation from called user.
From here, it's should be a skill of CN part, which should judge how far between calling and called user.
The key for this issue is dependent on the cost for local resource and long-distance resource as you judge.
If you think local resource is cheaper than long-distance one, the assignment on local resource will be first. Or vice versa.
This is similar with the introducation of Pre-paging in UMTS. Pls refer to the attached file. (because this doc is wroten by me in several year ago,maybe some mistakes, if you find it, pls let me know).
http://bbs.cnttr.com/viewthread.php?tid=64963&extra=page%3D1
Here, I have more thinking on this topic. Firstly, let's check the normal AMR log file from Ericsson.
*******************************************************************************************************
A normal AMR call:
10:57:31.73 MS1 Not Valid UL RRC Connection Request (UL-CCCH) Call Attempt
10:57:31.91 MS1 Not Valid DL RRC Connection Setup (DL-CCCH)
10:57:32.15 MS1 Not Valid UL RRC Connection Setup Complete (UL-DCCH) RRC Established
10:57:32.25 MS1 Not Valid UL Initial Direct Transfer (UL-DCCH)
10:57:32.31 MS1 Not Valid DL Measurement Control (DL-DCCH)
10:57:32.42 MS1 Not Valid DL Downlink Direct Transfer (DL-DCCH)
10:57:32.42 MS1 Not Valid DL Authentication Request
10:57:32.58 MS1 Not Valid UL Authentication Response
10:57:32.58 MS1 Not Valid UL Uplink Direct Transfer (UL-DCCH)
10:57:32.75 MS1 Not Valid DL Security Mode Command (DL-DCCH)
10:57:32.75 MS1 Not Valid UL Security Mode Complete (UL-DCCH)
10:57:32.85 MS1 Not Valid UL Setup
10:57:32.86 MS1 Not Valid DL Downlink Direct Transfer (DL-DCCH)
10:57:32.86 MS1 Not Valid UL Uplink Direct Transfer (UL-DCCH)
10:57:32.86 MS1 Not Valid DL Identity Request
10:57:32.87 MS1 Not Valid UL Identity Response
10:57:32.87 MS1 Not Valid UL Uplink Direct Transfer (UL-DCCH)
10:57:32.97 MS1 Not Valid DL Downlink Direct Transfer (DL-DCCH)
10:57:32.98 MS1 Not Valid DL Call Proceeding
10:57:35.72 MS1 Not Valid DL Radio Bearer Setup (DL-DCCH)
10:57:36.13 MS1 Not Valid UL Radio Bearer Setup Complete (UL-DCCH)
10:57:36.45 MS1 Not Valid DL Radio Bearer Reconfiguration (DL-DCCH)
10:57:36.48 MS1 Not Valid UL Radio Bearer Reconfiguration Complete (UL-DCCH)
10:57:37.16 MS1 Not Valid DL Downlink Direct Transfer (DL-DCCH)
10:57:37.16 MS1 Not Valid DL Alerting Call Setup
*******************************************************************************************************
Pls notice the red marked part.
As we had discussed this on the previous article, and I had confrimed that CN will send the "RAB assignment" to RNC after the "call confirmed" had been received. From here, we can know Ericsson's CN will assign the resources for calling user after the response gotten from called user.
Here, what I want to say is the assignment of radio resource.
Normally, CN will send "RAB assignment" to RNC after the "SETUP" message(or "Identity Response") is received from calling user. Thus, the calling user will hold the radio resources of service(such as, SF128 for AMR) to wait for the acknowledge from called user.
----- for this, I had checked some log files from other verndors's implementation.
But for Ericsson, this is different.
Here, one topic bring to us--- How to balance the usage of radio resources and performance?
If you perform as Ericsson, you will face to the increase of drop call. Because if called user is ok, but fail to establish for calling user. Or you can do as other vendors's, but more radio resources will be needed. (becuase during the calling wating for the acknowledge from called user, only signalling is sent on this channel without user data) with better performance on drop call rate.
My suggestion is we need use this method under different case.
For example,
a) If you(in China) will dial a mobile or PSTN which locate in USA. Thus, it's worth to assign radio resources to calling user as eraly as you can.
b) If you will dial a local number, maybe CN could send the "RAB assignment" to RNC after the confirmation from called user.
From here, it's should be a skill of CN part, which should judge how far between calling and called user.
The key for this issue is dependent on the cost for local resource and long-distance resource as you judge.
If you think local resource is cheaper than long-distance one, the assignment on local resource will be first. Or vice versa.
This is similar with the introducation of Pre-paging in UMTS. Pls refer to the attached file. (because this doc is wroten by me in several year ago,maybe some mistakes, if you find it, pls let me know).
Pre-page in UMTS.pdf
(2006-09-06 14:24:59, Size: 84.8 kB, Downloads: 11)
论坛模式 推荐 收藏 等级(1) 编辑 管理 查看(72) 评论(4)
TAG:
-
James-Ran
发布于2006-09-07 23:39:06
-
"大公司对网络的理解可以说是到了出神入化的境界。这就是积累"
Agree!
-
James-Ran
发布于2006-09-07 23:38:33
-
QUOTE:
原帖由 brightxing 于 2006-9-7 23:30 发表
这是一个机会游戏。如果你用3G手机，你会发现呼叫建立时间可能达到3－6S，这远长于GSM网络。这对QoE影响很大。
RB建立过程也是很花费时间的，为了提高QoE,就必须一点一点的挖掘，大公司对网络的理解可以说是到 ...
Normally M-M call is about 5-8s. We had make a test for GSM, and it's similar setup time with WCDMA.
I(at least) don't find longer time for GSM than WCDMA.
-
brightxing发布于2006-09-07 23:30:20
-
这是一个机会游戏。如果你用3G手机，你会发现呼叫建立时间可能达到3－6S，这远长于GSM网络。这对QoE影响很大。
RB建立过程也是很花费时间的，为了提高QoE,就必须一点一点的挖掘，大公司对网络的理解可以说是到了出神入化的境界。这就是积累。
-
my_lcl发布于2006-09-07 22:27:05
-
thank James-Ran (WCDMA) very much,