top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

What can be done to minimize chances of MME overload conditions?

+5 votes
215 views

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 ?

posted Oct 17, 2014 by Varun Kumar

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
+3 votes
Can OverloadStop message be sent from MME to eNB?

Can OverloadStop message also be sent from MME to eNB when the eNB establishes SCTP connection to the MME.

+1 vote
How many eNodeBs can be there in a MME pool area ?

Is there any strategy or relation holding the number of eNodeBs that can be connected to a particular MME?

+1 vote
Can same TAC be planned in two different MME?

Can same TAC be planned in two different MMEs, if yes will it have and service impact?

+1 vote
What will be the behaviour of EnodeB with MME after receiving RRC Connection Reestablishment Complete message???

Which message EnodeB will communicate to MME after Receiving the Reestablishment Complete message from UE. what else messages will transverse between EnodeB and MME, before sending Reconfiguration message to UE from EnodeB after Reestablishment complete message has been received at EnodeB.

+4 votes
Does the S1-handover procedure always has to be change in MME?

Does the S1-handover procedure always has to be change in MME ? As per spec it is mentioned MME changes during the S1 handover. But in a case where the source and target enodeB is served by same MME , but let say because of some network problem X2 interface is not available and source enodeB initiates a S1 handover procedure. How do we validate this scenario, as I don't see any call flow in the spec for this?

...