欢迎来逛逛,聊聊技术,侃侃大山. 本人主要喜欢WCDMA/TD-SCDMA无线侧的技术，如果有何关于无线技术方面的问题，你可以给我留言，我们可以一起讨论，共同提高。

Looking at this, Ericsson log's analysis

2006-09-04 13:20:17

Today, I get some Ericsson log file from my friend, and summarize for you:
also pls refer to this: http://bbs.cnttr.com/viewthread.php?tid=64622&extra=page%3D1

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

The total expended time is 5430ms, and due to execution of "晚指配", thus, UE just wait for RB setup message(here, totally about 2740ms), and UE will spend 760ms to configure RB and reconfigure SRB(decrease the polling times).
+n"rA?p0
We can image, if Ericsson use "早指配", thus, the total time will be 5430-2740+760=3450ms--- which is very good KPI.
T5kZzC$qPq0
c7I?fZ;qIP0 Welcome your discuusion!
James

论坛模式推荐收藏等级(1) 编辑管理 查看(208) 评论(20)

TAG:

renew发布于2006-09-06 09:56:39: 俺还是觉得从用户感受的角度来看，晚指配好！它能更早的使发起呼叫的用户收听到alerting，但是晚指配有一点不好就是接入成功率相对早指配低一些，原因俺就不说啦。
上面有个兄弟发的协议里面也写得比较清楚，的确是依据L3信令来确定，不过通过空口信令进行猜测也是没错的。

James-Ran 发布于2006-09-05 22:02:13: At least, it's my first time to read Ericsson's WCDMA log file, and one kind of execution interest me. And I had never seen this in other vendor's products(maybe not including all). Thus, I summarize this and share with you.
h3@_U#c:AB#p5zwww.cnttr.com
and I create a new topic, pls check this:
http://bbs.cnttr.com/viewthread.php?tid=65212&extra=page%3D1

Enjoy it!
James
2006/9/5 in shanghai

[ 本帖最后由 James-Ran 于 2006-9-5 22:04 编辑 ]

James-Ran 发布于2006-09-05 15:56:22: "唉看来我的英语真的要提高提高了看James楼上10行左右的英文就花了5分多钟。"
It seems that I need express more accurately .

bosunram 发布于2006-09-05 10:57:39: 唉看来我的英语真的要提高提高了看James楼上10行左右的英文就花了5分多钟。

对James的思路表示赞同。
4T#r[E6b"c-H0xwww.cnttr.com
另外：babyfacemeihui 在帖子中提及到
“在3GPP 23108中也没有说根据核心网来确定是早指配还是晚指配”
5a1My1O9f2mTwww.cnttr.com
不知道兄弟是不是误会我之前的意思了，早指配晚指配在华为的MSC中是在MSOFTX3000内完成配置的，具体可以看下面这个知道书。还有里面对早指配和晚指配解释的比较清楚。
#p${+X|8@G5Rwww.cnttr.com

V1R3C01版本早晚指配特性指导书 -20060411-B-1.1.PDF
(2006-09-05 10:59:40, Size: 467 kB, Downloads: 7)

~,y^#R0ZJ[ 本帖最后由 bosunram 于 2006-9-5 16:14 编辑 ]

James-Ran 发布于2006-09-04 21:57:45: Thanks, babyfacemeihui.
8d*R$F1b!\w5c
But I feel we don't need to emphasize this concept. I feel the fundamental reason to define these two methods is balance between performance and resource usage. You can spend more radio resource to get better performance (early assignment) or you can save radio resource(late assignment).
iZ.u:uUm?k!q'R:_-~www.cnttr.com
And for messages flow, I think we don't care it for more. Because if you check Ericsson's RNC log file, you can know, CN will send "RAB assignment" for calling user after the "call confirm" had been received from called user. And I think Ericsson could send "Alerting" on RB , which is itself's implemetation.
7|7c)NP6N
_&s!\
b${www.cnttr.com
Thus, I think it's not reasonable if we only judge "early" or "late" assignment by message flow.
z'U#?6nZjwww.cnttr.com
'J*CS ~V ^N9R1Bwww.cnttr.comLast one, if this belong to "early assignment", it's difficult for you to explain why so long time between "call proceeding" and "RB setup"(2740ms). For other vendors, as I mentioned in previous context, it's only less than 1000ms between these two messages.

babyfacemeihui发布于2006-09-04 21:05:43: 另外不知道James-Ran有没有详细的信令所花费的时间。在《Springer.Design.and.Performance.of.3G.Wireless.Networks.and.Wireless.LANs》这本书中提到了一个例子，统计了3G to 3G call setup delay for circuit switched service
Components Call Setup Procedure from Calling UE to 3G MSC    Delay (ms)
1、RRC connection establishment                                           264.5
2、NAS signaling connection establishment                               85.3
w,M0d3rMwww.cnttr.com3、NAS authentication procedure                                           2005.3
)ZW!y
g.Ge[www.cnttr.com4、Integrity protection procedure                                           244.7
5、NAS call setup procedure                                                    566.2jHlMm
6、Synchronized RAB assignment procedure - circuit switched    512.5
7、NAS alerting/connect procedure - mobile originated             467.0
z/YZ&J!]a E@www.cnttr.com8、Subtotal delay from calling mobile to 3G MSC                      4145.5  Zu6Sy,CG#c7o
这个例子是给的早指配流程。

babyfacemeihui发布于2006-09-04 20:47:48: early assignment and late assignment
early assignment and late assignment－3gpp 3G TS 23.108

23108_320.doc
(2006-09-04 20:47:48, Size: 216 kB, Downloads: 5)

babyfacemeihui发布于2006-09-04 20:45:57: 由James-Ran的log可以看出这是一个早指配的流程。目前我知道华为在WCDMA中同时支持早晚指配的。在3GPP 23108中也没有说根据核心网来确定是早指配还是晚指配，具体协议见我下面发的附件。在7.3.2节中给出了一个Mobile originating call establishment的例子。两者的区别我在上面已经给出了说明。

babyfacemeihui发布于2006-09-04 20:33:31: 个人回答，欢迎讨论
好像目前在wcdma中的协议没有专门提到早晚指配的概念和流程，在3GPP 23108中提到了早晚指配的概念，而且流程都是基于GSM系统的举例。下面给出GSM中的部分消息过程到WCDMA消息过程的映射如下表，便于对应wcdma中的信令。
流程图中所列的GSM消息过程对应的WCDMA消息过程
.{|kVGkDlRR connection establishment RRC连接建立过程
Ciphering mode setting                   Security Mode过程
Assignment of a traffic channel RAB建立过程
下面是早晚指配的流程。
^[ ck1^0EOwww.cnttr.com1、早指配流程
Mobile Station             Network

+-                            -+
│       CHANNEL REQUEST       │  RR connection
~+ZGz#tF5Ew9lwww.cnttr.com│ -------------------------> │          establishment
│    IMMEDIATE ASSIGNMENT    │  (MO)
│ <------------------------ │
+-                            -+
+-                            -+www.cnttr.comu&M]cVV0H
│    CM SERVICE REQUEST       │
9@L*Zzl
N$~awww.cnttr.com│ -------------------------> │  Service request
│                               │2uJb"L|P!`RQ
S
+-                            -+
+-                            -+
│    AUTHENTICATION REQUEST    │  Authentication
│ <------------------------- │
│    AUTHENTICATION RESPONSE │
pm%t)P\@S│ -------------------------->  │www.cnttr.comm7m%V\;C%b7C?U-Q
+-                            -+
+-                            -+
│    CIPHER MODE COMMAND    │
│ <------------------------- │  Ciphering
│    CIPHER MODE COMPLETE    │  mode setting
│ -------------------------->  │
+-                            -+
+-                            -+www.cnttr.com0Cyv
wP"xE[/A n
│             SETUP             │
│ -------------------------->  │  Call initiation
(~3W\V#V4U│       CALL PROCEEDING       │
│ <------------------------- │
+-                            -+www.cnttr.com,s'K.~O"TI
+-                            -+
│       ASSIGNMENT COMMAND    │
│ <--------------------------  │  Assignment of
│       ASSIGNMENT COMPLETE    │  a traffic
|;[/v
MXRIAwww.cnttr.com│ -------------------------->  │  channel
+-                            -+
8Z Uku^7?)f8\'i5Ja+-                            -+
│             ALERTING          │
z6X@M"r$@FM,n│ <--------------------------  │  User alerting
+-                            -+
+-                            -+
│             CONNECT          │
│ <--------------------------  │  Call accepted
│       CONNECT ACKNOWLEDGE    │
│ -------------------------->  │
gpUwx
j*t3C(oy
Jwww.cnttr.com+-                            -+
2、晚指配流程：
3c6`\!B^PMobile Station             Network

+-                            -+
│       CHANNEL REQUEST       │  RR connection
│ -------------------------> │  establishment
,zD]|'yK;V"h
_│    IMMEDIATE ASSIGNMENT    │  (MO)
│ <------------------------ │
#B(P0beF"VLwww.cnttr.com+-                            -+'fi){ [`.A
+-                            -+  Service indication
│       CM SERVICE REQUEST    │
│ -------------------------> │
│                               │
│                               │www.cnttr.comh&DMs/Lv6q0HS%X]
+-                            -+
+-                            -+
│    AUTHENTICATION REQUEST    │  Authentication
│ <------------------------- │
#]p,Fh?Kn&m6o(@
V│    AUTHENTICATION RESPONSE │www.cnttr.com,]
w%m9J9HyO[
│ -------------------------->  │
+-                            -+
+-                            -+
F"m8aL1b!q│    CIPHER MODE COMMAND    │
│ <------------------------- │  Ciphering
│    CIPHER MODE COMPLETE    │  mode settingwww.cnttr.comU;z!J.}k!S8r
│ -------------------------->  │
+-                            -+
+-                            -+
│             SETUP          │
│ -------------------------->  │  Call initiation
2~8dK^7xzs│       CALL PROCEEDING       │
│ <------------------------- │www.cnttr.com
K4qs#v-ahY
+-                            -+
+-                            -+3v GQ;Tbu
│          ALERTING          │i$G.[1x\%p7^h4HX
│ <--------------------------  │  User alerting
+-                            -+www.cnttr.com&g X`0I)o(d.C'_p5J@
+-                            -+
│       ASSIGNMENT COMMAND    │中国通信网－无限分享u*A4X_2T
│ <------------------------- │  Assignment of
│       ASSIGNMENT COMPLETE    │  a traffic
│ -------------------------->  │  channelc4r5Jw}r6ah^
+-                            -+
+-                            -+
│             CONNECT          │www.cnttr.com RwPzAC3pZ
│ <--------------------------  │  Call acceptedY'V0?,j%u(v2\7Gy
│       CONNECT ACKNOWLEDGE    │
│ -------------------------->  │/JO"a8?QPq(}
+-                            -+

m9\b#M2Z两者比较：
1、早指配中的回铃音由网络生成，晚指配中的回铃音由主叫终端生成；
2、早指配，RAB建立过程发生在回铃音响起前；晚指配，RAB建立过程发生在回铃音响起后；
3、晚指配的过程，RAB建立过程发生在振铃后，这样可以节省呼叫开始到听到回铃音的时延；但采用晚指配后可能无法进行彩铃业务（目前彩铃业务的回铃音由MSC发出）。
4、目前，在GSM现网中，采用的全是早指配。

James-Ran 发布于2006-09-04 19:47:31: QUOTE:
原帖由 renew 于 2006-9-4 17:53 发表
晚指配比早指配更早的收到 Alerting 消息，用户感受更好，所以通常我们使用晚指配。但是晚指配会影响接通率，对于实际网络，需要平衡运营商的需求。比如，KPI的要求。

g
AmJYa)ZB`No, I had checked some log files from other vendors, such as, M,N,H,Z,U etc. I think CN will send "RAB assignment" to RNC even no confirmation received from called user. Thus, it should be "早指配".

And the different benefits for them, shorter setup time for "早指配" but more radio resource will be needed. And for "晚指配" can save radio resource(after confirmation from called user, Network start to allocate radio resource), but failure of calling's RB setup will affect the call success ratio.

James

James-Ran 发布于2006-09-04 19:38:27: QUOTE:
原帖由 bosunram 于 2006-9-4 19:33 发表

James，我在3楼已经明确指出仅仅从你给的接入侧的信令跟踪是无法确定是早指配还是晚指配的。
"i'?$A+^h
Gwww.cnttr.com
你上面说的CN在得到被叫侧的相应也就是ALERTING消息返回给主叫侧的MSC后，再建立主叫侧的承载，这个是晚指配的 ...
!KT1RjGq&bN
Agree with you
James

bosunram 发布于2006-09-04 19:33:29: QUOTE:
原帖由 James-Ran 于 2006-9-4 18:05 发表
And I had confirmed again that CN will get acknowledge from called user, then send "RAB assignment" to RNC.
R9fo'g1udL+VC
Thus, this is a case of "晚指配".

James

James，我在3楼已经明确指出仅仅从你给的接入侧的信令跟踪是无法确定是早指配还是晚指配的。www.cnttr.com:I5k/z\gW
L

你上面说的CN在得到被叫侧的相应也就是ALERTING消息返回给主叫侧的MSC后，再建立主叫侧的承载，这个是晚指配的概念我表示赞同。

xingpp根据你的信令跟踪中先 Radio Bearer Setup后收到 Alerting消息判定是早指配，这个是不准确的。具体原因见5楼我的说明www.cnttr.com`0oDI)S

同样，James仅仅根据 Call Proceeding 和 Radio Bearer Setup之间的时间差相差了 2740ms就判定这个是晚指配也是不可取的，无线侧接受到的信号受环境因素也是不可忽略的。当然我们可以猜测这的确是晚指配造成的时延。www.cnttr.com0`9Rs7X!~G

我还是坚持自己的观点早指配晚指配需要从核心网侧的信令来准确判断。

James-Ran 发布于2006-09-04 18:05:35: And I had confirmed again that CN will get acknowledge from called user, then send "RAB assignment" to RNC.@3AD|._A,hs/I

Thus, this is a case of "晚指配".

James

renew发布于2006-09-04 17:53:06: 晚指配比早指配更早的收到 Alerting 消息，用户感受更好，所以通常我们使用晚指配。但是晚指配会影响接通率，对于实际网络，需要平衡运营商的需求。比如，KPI的要求。

James-Ran 发布于2006-09-04 17:48:36: But I still have a puzzle.
Pls notice the red marked part-- the time difference between "call proceeding" and "RB Setup" is about 2740ms.

if we refer to others log files from other vendors, this difference is about less than 1000ms. Why so long time is needed by Ericsson eqipment? Maybe it's "晚指配" because at this time, MSC had gotten the "Alerting" from the called user?
]ve7P+g`!I
Welcome your discussion.
James

James-Ran 发布于2006-09-04 17:32:59: Yes, I correct my viewpoint on resource assignment.
Normally we execute "早指配"

bosunram 发布于2006-09-04 14:54:48: 个人理解：9m&}3G blcz2w
c
“对主叫，早指配是在ALERTING 消息之前就开始指配，晚指配是在ALERTING 消息之后才开始指配”

晚指配中，这个ALERTING 收到到底指的是主叫侧的MSC收到这个消息还是UE收到这个消息？
个人认为是第一个，也就是MSC收到被叫转回来的ALERTING消息后，向主叫指配，然后再向主叫发ALERTING消息。第二种说法里给UE发送了ALERTING消息之后再建立承载？好像有点矛盾。
Wh|
O!B6EW5Nwww.cnttr.com
当然James给出的仅仅是接入侧的一段消息，早晚指配这个概念还是需要在核心网侧监控的
MnE)k
p#S1z
欢迎指出不同意见。

xingpp 发布于2006-09-04 14:41:08: 请问楼上，为什么“James给出的是接入侧的信令，不能看出是早指配还是晚指配”？，首先是主叫，而且指配在alerting之前，不是早指配吗？

}u1k.G,j$}6eeol]www.cnttr.com这样，早指配是5430ms，晚指配多了指配RB建立时间760ms，所以晚指配的时间应该为5430+760ms。

bosunram 发布于2006-09-04 13:52:19: 1. 早指配与晚指配的区别在于 TCH 信道的分配时机不同。对被叫，早指配是指在摘机之前就开始指配，晚指配是指在摘机之后才开始指配；对主叫，早指配是在ALERTING 消息之前就开始指配，晚指配是在ALERTING 消息之后才开始指配。www.cnttr.com!Oa,D{@C)A&W$Q-M
2. 早指配缩短了呼叫接续时延，并提高了呼叫接通率；晚指配能够避免 TCH 资源在振铃期间的闲占, 提高 TCH 资源的利用率
exw*\3oa7l:w@]www.cnttr.com这个是在核心网里呼叫流程的解释。www.cnttr.comf'TkJ
T4o$YK
www.cnttr.com0UXhH0E6lN*md
个人对James的帖子发表理解和解释：www.cnttr.com'?-S1X!l+t_%JqB.{j|

James给出的信令流程应该是主叫侧的早指配流程。

*************James给出的是接入侧的信令，不能看出是早指配还是晚指配，***************

需要说明的：
Yp8O s@4T:Mwww.cnttr.com1、针对主叫而言，早指配情况下，承载的建立是和呼叫信令同步的，也就是说主叫MSC在取被叫漫游号、出局选路、号码分析等等是同步的，所以早指配的时间在整个呼叫流程时间中可以被忽略，这样缩短了呼叫接续时延
2、晚指配情况下，是在Alerting消息之后的，也就是说被叫已经确认空闲，返回Alerting消息之后再建立主叫侧的承载，这个指配时间是跟呼叫信令串行的，这样就相当于增加了呼叫接续时延。但这个好处是避免 TCH 资源在振铃期间的闲占, 提高 TCH 资源的利用率。
3M1d,_+W\I"q!G i$G
[ 本帖最后由 bosunram 于 2006-9-4 13:54 编辑 ]

xingpp 发布于2006-09-04 13:38:14: 查了早指配和晚指配的定义：www.cnttr.com0v(|,m3b+h
早指配TCH信道，即就是正常的指配TCH信道，是在一个呼叫成功地占用SDCCH信道后，系统为它指配TCH信道。之所以称之为早指配是相对于晚指配而言的，因为它是发生在振铃“Alerting ”消息之前。
晚指配TCH信道，也是一个呼叫在成功占用SDCCH信道后，系统为它指配TCH信道。但它是发生在振铃“Alerting ”消息之后因此称之为晚指配。

问题：
似乎楼主所提流程应该是早指配？即先指配，后震铃。

按照上面的定义：
v#Y-V'v+l2nI.Swww.cnttr.com早指配的好处是：响铃后，立即可以接通，缺点是需要等待一段时间后才开始响铃。

3|S&w9T&V/A_`www.cnttr.com[ 本帖最后由 xingpp 于 2006-9-4 13:41 编辑 ]

进入论坛，查看全部评论