top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration

Facebook Login
Site Registration

Recovery IE in GTPC echo message.

+2 votes

Could somebody explain about Recovey IE in GTPC message .I know this is restart counter of GW .Then what is the importance of this IE?

posted Apr 5, 2017 by Naren Nishad

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote

Echo Request Message

Echo Request
Flags: 0x40
    010. .... = Version: 2
    ...0 .... = Piggybacking flag (P): 0
    .... 0... = TEID flag (T): 0
Message Type: Echo Request (1)
Message Length: 14
Sequence Number: 0x00000001 (1)
Spare: 0
Recovery (Restart Counter) : 5
    IE Type: Recovery (Restart Counter) (3)
    IE Length: 1
    0000 .... = CR flag: 0
    .... 0000 = Instance: 0
    Restart Counter: 5

A node shall include the Recovery information element if it is in contact with the peer for the first time or the node has restarted recently and the new Restart Counter value has not yet been indicated to the peer.

The peer receiving the Recovery information element shall handle it as when an Echo Response message is received but shall consider the rest of the message in accordance with the message semantics and parameters.

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.

answer Apr 4, 2018 by Sunder Singh Thakur
Similar Questions
+3 votes

While going through 29.274 specification, I observed "Bearer TFT" is optional in Create Session Request/Response messages while it's presence is mandatory in Create Bearer Request message. Reasons are not explained in the specification. Can someone please explain it ?

+1 vote

GTP tunnel id is a 32-bit long value over one IP address combination. Suppose there are two nodes A and B which has IP addresses X and Y respectively. Is it possible when first GTP tunnel id range gets exhausted then both the nodes starts using different IP address combination and again GTP tunnel id range can be re-used ? If it is impossible then what could be the reason ?

+2 votes


I am working on GTPV2 control plane. I want to implement negative test scenarios for GTPV2-C messages in my project. Can anybody list out the possible negative test case scenarios for GTPV2-C messages.??

Contact Us
+91 9880187415
#280, 3rd floor, 5th Main
6th Sector, HSR Layout
Karnataka INDIA.