top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

What is the minimum and maximum time for T3-RESPONSE timer used in GTP-U path management messages

+3 votes

Reference 3gpp TS 29.281 and TS 29.060

posted Mar 3, 2014 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button
I hope you are talking about the echo time interval (T3 Response time). As far as I remember it can be anything between 1-65535. Check the following link if it is useful.

1 Answer

0 votes

The timer T3-RESPONSE holds the maximum wait time for a response of a request message.

T3-timer has not as such defined values, but there is a method to count the T3-response timer value.

Actually it means that after the request message GTP-U peer will start the timer and if peer is not getting the response within that timer expires, it has to send request message again.

The T3-RESPONSE timer shall be started when a signalling request message (for which a response has been defined) is sent. A signalling message request or response has probably been lost if a response has not been received before the T3-RESPONSE timer expires. At the expiry of the timer the request is re-transmitted if the total number of request attempts is less than N3-REQUESTS times.

Now if i come to your query how can we calculate that timer value.
We know a GTP-U peer may send an Echo Request on a path to the other GTP-U peer to find out if it is alive. Echo Request messages may be sent for each path in use. So from here it will find out the shortest path of other GTP-U peer and will note down the time that in how much time it has got the Echo response . This time will be the T3-timer value. So for the next request message that will path will be the dedicated path and T3-timers will expect the response with in that time

answer Mar 3, 2014 by Hiteshwar Thakur
Similar Questions
+5 votes

Sequence numbers are required in a handful of message types (handover, etc.), but I need to know if they are usually present even when they are optional in the message definitions. Can you point me to a publically available pcap trace of live traffic?

+3 votes

I have REST based interface to SDN controller (OpenDaylight) through which I want to enable GTP-U encapsulation and de-capsulation for an UE based on UE IP address. What all things I need to do and how ?

+1 vote

This is regarding the scenario where GTP-U peer got restarted and again came to service. However,the other GTP-U entity could not detect the restart of peer GTP-U entiity as it keep receving Echo Response. I had read the Restart Counter/(Recovery IE), is used to detect such restarts. But, as per spec 29.281, Restart counter is no longer use and ignored. In such case how such quick GTP-U restarts are detected by peer GTP-U? Is it so that in this case no recovery action needed for User Plane ?

I do see that we have Private Extension IE but again that is vendor specific so that can not be used for interconnection with devices with other Vendors.