top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

LTE : how to handle when UE sends second connection request with same IMSI ??

+1 vote
431 views

If UE shutdown appropriately then context will not be deleted at network. after some time when UE switch on UE will send attach request with the IMSI, but with same IMSI ENB have already an context. Spec says reject the second UE if already old context present but the second UE is valid and first UE is not valid then how to handle.

posted Mar 30, 2017 by Rohit Verma

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

1 Answer

+1 vote

Hi Rohit,

EnodeB does not identify an UE based on IMSI, it means eNodeB can't identify new connection request is same as already existing UE connection.
If MME receives attach request with an IMSI for which it already has UE context then first it check whether this request is from genuine UE or not. For this it performs authentication and security procedure. If authentication/security gets passed then MME proceeds with Create Session Procedure . If SGW already has context then it will delete the context locally and proceed with Create Session Procedure.

If you have specification reference which states "MME sends reject in this case", please share.

Thanks,
Harshita

answer Mar 31, 2017 by Harshita
Similar Questions
+1 vote

Usually, I always saw when UE sends "S-TMSI" in RRC connection Request message then it definitely sends "Registered MME Information " in RRC Connection Setup Complete message.

I am looking for a scenario on which UE sends "Random number" in RRC Connection Request message and "Registered MME Information" in RRC Connection Setup Complete message.

+1 vote

I saw RRC Connection Reject message in specification. There is an IE "deprioritisationReq" within the RRCConnectionReject message. I want to know when eNodeB includes this IE while rejecting a rrc connection request for an UE.

+2 votes

Please can anyone explain me,
In which Scenario, eNB send Idlemodemobilitycontrolinfo IE with release cause "other" inside RRC CONNECTION RELEASE message to UE???

+3 votes

what is difference between UEID IE of rrc connection request and IMSI ?

+2 votes

It may be an easy question but still I have some doubt.
How RRC Connection setup procedure gets impacted with the presence of "S-TMSI" as an UE-Identity within the RRC Connection Request message ?
Note: RRC Connection request message can carry either 5 bytes long (S-TMSI) or 5 bytes long random value.

...