top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Can MME use entire range of TEID?

+2 votes
417 views

Do carriers limit the size of the TEID pools?

posted Dec 7, 2013 by Kumar Mitrasen

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

2 Answers

+6 votes

Four octets have been used for TEID in GTP-C packet header. TEID value ranges from 2^32 - 1. It's my personal thoughts Ideally no operator would like to use a subset of TEID value space since there are a number of interfaces MME has toward other nodes.
For Example: During attach procedure, when MME sends create session request to SGW then It sends "0" as TEID value. MME doesn't know what value SGW will assign in create session response. SGW can TEID value as 2^32 -1 . In such scenario, MME and all the other nodes which have direct interfaces with MME should apply same configuration in respective application like each application will use value ranges from 2^24-1. But still GTP-C packet format will not be altered.

Please correct me if I am wrong.

answer Dec 7, 2013 by Vimal Kumar Mishra
+1 vote

Yes not just MME but all node can practically use whole TEID. In practice upper bits are used to identify the card/rack/thread etc and lower bit are used to identify the tunnel within the module, though there is no standard to handle TEID in a particular way.

answer Dec 7, 2013 by Salil Agrawal
Similar Questions
0 votes

As per LTE core network architecture, MME shares S11 interface with SGW and SGW has S5/S8 interface with PGW.
I went through Create Session Response message sent by SGW to MME and found PGW-C and PGW-U tunnel ids.
I want to know what MME does with these PGW-C and PGW-U tunnel Ids ?

+1 vote

I know tracking area list is provided by MME to UE to track UE in idle mode. I want to know what is the purpose of having different kind of tracking area type like "consecutive tracking area codes belonging to one plmn" , "non-consecutive tracking area codes belong to one PLMN".

+5 votes

As per 3GPP 36.413 specification, there is a procedure defined i.e. known as "Over load" procedure. As soon as eNodeB receives "OverLoad Start" Message from MME, it takes further actions like not to accept new signalling or may be something else.

Now the query is how it can be avoided as much as possible ?

+1 vote

I just thought of a situation ,

As each ENB does S1 connection with MME.so consider 3 ENBs(those are nearer to each other) did S1-Setup with a particular MME.

After S1-Set up done can we have/add some intelligence (Based on some identity ) at MME to know who all are neighbor for whom?

If we will know about this we can make X2 -relation with neighbor easily ,so that we can reduce the overhead of getting info of neighbor ENBs.

...