top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Should eNodeB change value of systemInfoValueTag (present inside SIB1) upon changing Pmax value after successful attach?

+3 votes
834 views

Following scenario tested :
UE is attached. Changed the value of Pmax from Zero to 20.

Observations :
eNodeB is sending SIB1 followed by paging message. SIB1 systemInfoValueTag is also changed.
As per 36.331 on modification of any SIB1 parameter, systemInfoValueTag should not be changed.

Questions :
Could you please clarify me, in what scenarios the systemInfoValuetag present in SIB1 should be changed and in which scenarios it should not be changed ?
Also how would the UE decode the system information in these scenarios ?

posted Mar 2, 2015 by anonymous

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

1 Answer

+3 votes
 
Best answer

As per 36.331 systemInfoValueTag is defined as below.
Common for all SIBs other than MIB, SIB1, SIB10, SIB11 and SIB12. Change of MIB and SIB1 is detected by
acquisition of the corresponding message.

If there is any change in MIB, SIB1 SIB10, SIB11 and SIB12 then systemInfoValueTag will not change. If we modify SIB2 to SIB9 then systemInfoValueTag value will be changed.

Suppose paging is happening for change in SIB1 then UE will read the updated SIB1. In this case systemInfoValueTag value will not change so UE will not read any other SIB.

Suppose paging is happening for change in SIB2 to SIB9 then eNodeB needs to changed the systemInfoValueTag value in SIB1, when UE will read the SIB1 then UE will find the change systemInfoValueTag value so UE will read the all relevant SIBs.

answer Mar 2, 2015 by Veer Pal Singh Yadav
Similar Questions
+2 votes

Is it possible, source eNodeB has received "handover command" message from MME and now it want to cancel handover procedure ?
What could be the possible reasons when source eNodeB want to cancel ongoing handover procedure ?

+1 vote

operating band is specified in SIB1 downlink channel upon which ue receives system info..why ? Can any one help on a brief explanation!

+1 vote

During a LTE attach, MME may send the UE a EMM Information message with Universal time and local time zone IE. This IE contains Year, month, day, hour, min, sec.
My problem is that I can not find any reference yet about what should be the value of the year. Is it calculated from 1900 or 2000 or as it is ? or there is some other reference year ?
Any reference spec with this particular information will be highly helpful.

+4 votes

Since Ue can be configured for measure at the time of RRC Connection Setup. What is the probability to get mobility control info inside RRC Connection Reconfiguration as part of initial attach procedure.

+4 votes

I saw a scenario where an Identity is requested by MME after successful Authentication and Security mode complete.. As a Response to this message UE is Sending IMEI? what is the need of checking IMEI number after successful authentication? If IMEI is in block list then ongoing Attach procedure is going to be Terminate...? Identity Request intention is mainly to check the IMEI belongs to any one of Black, while or Green list then why cannt MME check for this before Security Mode?

...