6.6 去附着功能

tobino1

回复 爱卫生 的帖子

实际中看到好多 网络发起的detach，cause为MS reachable timer expiry 这个说明什么？

tobino1

回复 爱卫生 的帖子

哦 我找到相关描述：
In the case of a periodic GPRS Routing Area Update, the procedure is controlled in the MS by the Periodic RAU T3312 timer. The network supervises the procedure with the Mobile Reachable timer which is longer than the RA update timer. When the Mobile Reachable timer expires, the network stops sending paging messages to the MS and starts a Standby timer. After the timer expires, the network performs an implicit Detach. If a Routing Area Update Request message is recieved during the Standby timer, the Mobile Reachable timer is started and the Standby timer is reset. In GSM, the Mobile Reachable timer is reset and started with its initial value when the READY timer stops or expires. The Mobile Reachable timer is stopped and set to its initial value for the next time the READY timer is started. If the READY timer value is set to zero after a READY timer negotiation, the Mobile Reachable timer is reset and started with its initial value. If the initial READY timer value is zero, the Mobile Reachable timer is reset and started with its initial value when the Routing Area Update Request message is received.

cause process 为Implicitly detached
cause code为0x33

tobino1

回复 爱卫生 的帖子

哦 我找到了：
In the case of a periodic GPRS Routing Area Update, the procedure is controlled in the MS by the Periodic RAU T3312 timer. The network supervises the procedure with the Mobile Reachable timer which is longer than the RA update timer. When the Mobile Reachable timer expires, the network stops sending paging messages to the MS and starts a Standby timer. After the timer expires, the network performs an implicit Detach. If a Routing Area Update Request message is recieved during the Standby timer, the Mobile Reachable timer is started and the Standby timer is reset. In GSM, the Mobile Reachable timer is reset and started with its initial value when the READY timer stops or expires. The Mobile Reachable timer is stopped and set to its initial value for the next time the READY timer is started. If the READY timer value is set to zero after a READY timer negotiation, the Mobile Reachable timer is reset and started with its initial value. If the initial READY timer value is zero, the Mobile Reachable timer is reset and started with its initial value when the Routing Area Update Request message is received.

cause process 为Implicitly detached
cause code为0x33