51学通信技术论坛

标题: 3GPP哪个规范是讲参数的 [打印本页]

作者: fengyijiu008 时间: 2015-5-10 12:21:15 标题: 3GPP哪个规范是讲参数的

recovery (restart counter) 是在哪个3GPP规范定义的，麻烦给指导一下，谢谢！！

作者: admin 时间: 2015-5-10 14:55:10

GTPV1的吗？TS29.060里啊。携带在echo response消息里。

作者: fengyijiu008 时间: 2015-5-10 17:40:26

admin 发表于 2015-5-10 14:55
GTPV1的吗？TS29.060里啊。携带在echo response消息里。

GTPV2的吧 APN重定向时,携带在MME想SGW发送的create session request 里面的，也是在29.060吗？谢谢

作者: admin 时间: 2015-5-10 22:32:51

fengyijiu008 发表于 2015-5-10 17:40
GTPV2的吧 APN重定向时,携带在MME想SGW发送的create session request 里面的，也是在29.060吗？谢谢
...

GTPV2是29.274，create session request消息里没有restart counter，都是在echo消息里的。

作者: fengyijiu008 时间: 2015-5-11 12:54:13

admin 发表于 2015-5-10 22:32
GTPV2是29.274，create session request消息里没有restart counter，都是在echo消息里的。

[attach]4154[/attach]
recovery=250 不知有没有特殊的含义，没查出来！多谢指教！

作者: admin 时间: 2015-5-11 22:07:46

fengyijiu008 发表于 2015-5-11 12:54
recovery=250 不知有没有特殊的含义，没查出来！多谢指教！

帮你查了下规范，如下：
Across GTP-C based interfaces an SGSN, GGSN, MME, SGW, PGW and ePDG utilize either GTPv1-C or GTPv2-C Echo Request and Echo Response messages or GTP-C messages containing the Recovery Information Element to detect and handle a restart.
A GTP-C entity shall maintain two Restart counters:
-       in volatile memory a remote Restart counter of a peer with which the entity is in contact;
-       in non-volatile memory own, or local Restart counter that was sent to a peer.
After a GTP-C entity has restarted, it shall immediately increment all local Restart counters and shall clear all remote Restart counters.
A GTP-C entity may have a common local Restart counter for all peers, or it may have a separate local Restart counter for each peer.
A GTP-C entity may probe the liveliness of each peer with which it is in contact by sending an Echo Request message (see clause 20 "Path management procedures") . The presence of the Restart counter in Echo Request or in a GTP-C message depends on the GTP-C version and therefore is specified in 3GPP TS 29.060 [8] and 3GPP TS 29.274 [13], respectively.
The GTP-C entity that receives a Recovery Information Element in an Echo Response or in another GTP-C message from a peer, shall compare the received remote Restart counter value with the previous Restart counter value stored for that peer entity.
-       If no previous value was stored the Restart counter value received in the Echo Response or in the GTP-C message shall be stored for the peer.
-       If the value of a Restart counter previously stored for a peer is smaller than the Restart counter value received in the Echo Response message or the GTP-C message, taking the integer roll-over into account, this indicates that the entity that sent the Echo Response or the GTP-C message has restarted. The received, new Restart counter value shall be stored by the receiving entity, replacing the value previously stored for the peer.
-       If the value of a Restart counter previously stored for a peer is larger than the Restart counter value received in the Echo Response message or the GTP-C message, taking the integer roll-over into account, this indicates a possible race condition (newer message arriving before the older one). The received new Restart counter value shall be discarded and an error may be logged.

翻译过来就是，
一个GTP-C的网元需要维护两个restart counter，一个是对端的，一个是自己的。当自己发生重启，将把本地restart counter值+1，然后发给对方。
对方如何处理呢？
- 每次受到echo response消息里的restart counter值（假设是值1）都保存下来，存到本地，然后后续还会继续受到GTP-C消息里的restart counter（假设值1）和进行比对，如果值1大于本地保存的值2，则判断出来对方发生了重启。

作者: fengyijiu008 时间: 2015-6-27 10:30:41

admin 发表于 2015-5-11 22:07
帮你查了下规范，如下：
Across GTP-C based interfaces an SGSN, GGSN, MME, SGW, PGW and ePDG utiliz ...

十分感谢！！！

欢迎光临 51学通信技术论坛 (http://51xuetongxin.com/bbs/)