top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

When does transfer syntax error come after initial context setup request?

+1 vote
873 views

After initial context setup request,enodeb sends transfer syntax error.
What could be it reason
Does extended Bit set as true makes any difference.

posted Jan 7, 2016 by anonymous

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

Similar Questions
+2 votes

I have a use case in which
ENodeB sends "S1-Setup Request" message to MME. TAC within the request is unknown for MME but at least one PLMN from the list of broadcasted PLMN is known by MME. How MME shall react ?

+3 votes

Need clarity on following items:
1. What is the use of "UE selected plmn" information for an eNodeB ?
2. Is the ECGI/TAI constructed based on the primary plmn (PLMN broadcasted in 0th index in SIB1 ) or based on the UE selected PLMN ?

+1 vote

Generally MME serves a group of tracking areas and belongs to at least one PLMN.
Lets assume, MME receives S1-setup request from eNodeB with the list of supported TAs.
Now, there are three possibilities as captured below.
1. All supported TAIs match at MME
2. Not even a single TAI match at MME
3. Few TAIs match at MME

I want to know, what MME will do for case 2 and case 3 ? How it will respond to eNodeB ?
If MME responds with S1-setup failure then what would be the cause value ? I did not find any reference in 36.413 for these scenarios.

+1 vote

In S1-Setup Request message, eNodeB tells max # (6) of broad casted PLMNs. In S1-Setup response message, MME responds back to eNodeB with maxnoofPLMNsPerMME(32) IE. I am not able to find the reason that why maxnoofPLMNsPerMME is 32 even eNodeB can broadcast maxium of 6 ?

...