- 在线时间
- 241 小时
- 最后登录
- 2015-12-10
- 威望
- 241
- 金钱
- 118937
- 贡献
- 3011
- 注册时间
- 2011-1-20
- 阅读权限
- 200
- 主题
- 1529
- 帖子
- 4004
- 分享
- 3
- 精华
- 8
- 积分
- 126474
- 相册
- 32
|
本帖最后由 爱卫生 于 2011-7-9 17:37 编辑
回复 天高云淡ah 的帖子
实在是不好意思。上面的答案可能误导你了。其实24.008中关于发送非空LLC帧Start Ready Timer没说错,如果没有启动的话,就启动。如果已经启动了,则是Reset还是Restart在24.008中并没有说。
我重新找了下,发现在23060里有关于这部分的详细说明:“The READY timer shall be reset and begin running in the MS when an LLC PDU is transmitted, and in the SGSN when an LLC PDU is correctly received”。它用的是过去式。也就是说MS在发送了一个LLC PDU时,就应该将T3314进行Reset并保证是running状态,同样,SGSN在收到这个LLC PDU后,也应将T3314进行reset并继续running。
也就是说,举个例子。手机在第1秒,发了第一个LLC PDU,ready timer启动,从44秒计时。到了第2秒,T3314计时为43秒,手机发了第二个LLC PDU,这时按照23060的规定,应将43秒重置为44秒并继续往下计时。也就是说,只要这个手机不断的发LLC PDU,则T3314应该一直处于40夺秒的样子(假设无线环境好的情况下),而不是说等到Ready Timer降到0的时候,MS将MM状态切换到Standby状态,然后又被一个LLC PDU的发送切换到Ready状态,并重新启动Ready Timer。这样子反而是不合适的。
因此,纠正一下我前面说的。请以23060的为准。而且这个说法和24008的讲法并不矛盾。24008只是说要启动,没提reset。我觉得24008说start ready timer,是不是就是要保证ready timer在running的状态呢?
所以说,你之前的说法应该就是对的。不断的LLC PDU发送会不断导致Ready Timer被重启。但我想了下这是没有办法的是啊,除非Ready Timer处于not running的状态才不会消耗资源。但Ready状态下T3314是一定要运行的。那要么就是被不断的重置,要么就是从44往下一直数到0,后面这种方式也得耗资源啊。这两种方式应该差不多的。而且如果是后一种方式,如果ready timer超时了,手机和网络侧将MM状态切换到standby,然后重新再将ready timer启动也是多了一道程序,也很麻烦啊。所以我觉得这也是没有办法的事啊!
第二个问题,原语有啊。在LLC规范44064中定义。一个用于确认,一个是非确认模式。摘录如下:
7.2.2.5 LL-DATA
The LL-DATA primitives shall only be used for LLEs in ABM. The following operations are defined:
- LL-DATA-REQ shall be used to request the confirmed transmission of an L3 PDU to the peer. QoS Parameters in the SGSN includes precedence class, delay class, and peak throughput. QoS Parameters in the MS includes peak throughput. QoS Parameters is defined as part of the Quality of Service information element in 3GPP TS 24.008 [8a]. Radio Priority indicates the radio priority level to be used by RLC/MAC.
- LL-DATA-IND shall be used to deliver a correctly received L3 PDU to layer 3.
- LL-DATA-CNF shall be used to confirm the delivery of an L3 PDU to layer 3 in the peer. The Reference parameter shall be set to the same value as the Reference parameter received in the corresponding LL-DATA-REQ.
7.2.2.6 LL-UNITDATA
LL-UNITDATA-REQ shall be used to request the unconfirmed transmission of an L3 PDU to the peer. QoS Parameters in the SGSN includes precedence class, delay class, reliability class, and peak throughput. QoS Parameters in the MS includes peak throughput and reliability class. Reliability class indicates whether the UI frame carrying the L3 PDU shall be transmitted in protected or unprotected mode, and whether RLC/MAC acknowledged or unacknowledged mode shall be used. Radio Priority indicates the radio priority level to be used by RLC/MAC. Cipher indicates whether the UI frame shall be ciphered or not.
LL-UNITDATA-IND shall be used to deliver an L3 PDU received in a UI frame to layer 3. Cipher indicates whether the received UI frame was ciphered or not.
|
|