Direction: E-UTRAN => UE
Signalling Radio Bearer: SRB0
RLC Mode: TM
Logical Channel: CCCH
Transport Channel: DL-SCH
Signalling Radio Bearer: SRB0
RLC Mode: TM
Logical Channel: CCCH
Transport Channel: DL-SCH
The RRC CONNECTION SETUP message is used to establish SRB1. It contains configuration information for SRB1. This allows subsequent signaling to use the DCCH logical channel. The configuration for SRB1 can be a specific configuration or the default configuration.
The RRC CONNECTION SETUP message may also contain configuration for PUSCH, PUCCH, PDSCH channels and information regarding uplink power control, CQI reporting, the SRS, antenna configuration and scheduling requests
Example: RRC CONNECTION SETUP
After eNB sent the RRC connection Setup, it wiat for a time waiting the reply from UE by the RRC Connectione setup complete, and if no reply then there is a fail of the RRC.
ReplyDeletewhat is that timer? and how we can change it?
It is T300 timer
DeleteIt is RRCConnSetupCmp Waiting Timer(s)
Deletethe T300(How much wait time the timer will activate)
DeleteThis is known as the defense mechanism timer and it's usually set to 3 seconds.
ReplyDeleteWhat if we don't receive RRC Setup message? Radio conditions are good.
ReplyDeleteIt needs to be checked on the UE logs where the procedure was stuck. Is RA procedure succesful? at least MSG3 sent out?
DeleteHi, what is the difference between "RRC Connection Setup message" and "Msg-4" in RACH procedure? Thx
ReplyDeleteMsg4 is actually contention resolution. Some NWs transmit RRC Connection Setup message along with Msg4 while the others do it seperately.
DeleteIf it is CCCH type RA, then Contention resolution MAC CE would be expected it will be MSG4, if it is of type DXCH then uplink grant addressed by C-RNTI expected as MSG4, And any grant addressed to C-RNTI if PDCCH order triggered
Deleteis it possible that eNB can send data(RRC CONNECTION SETUP IE's) of REl-10(not rel-8) to UE for SRB-1 setup,but UE has setup of rel-8 to decode that data(from ASN encode/decoder) then how the decode will be successful(As of now eNB might or might not be knowing which release UE is supporting ?.
ReplyDeleteCould you please point to which Rel-10 IEs in RRC Connection Setup message?
DeleteAs far as I can see this message has RRCConnectionSetup-r8-IEs even in release-10. The only change in Rel-10 as compared to rel-8 (initial versions) is the addition of RRCConnectionSetup-v8a0-IEs (contains only non-critical extensions)
i'm talking about RadioResourceConfigDedicated(first IE in RRCConnectionSetup-r8-IEs)in which we have IE's like RLF-TimersAndConstants-r9, MeasSubframePatternPCell-r10 (in this also we have so many) and these two IE's are not present in REL-8, so how will i decode these two in ue(if we have rel-8 asn encode/decoder). in other words i can say i have a UE of rel-8 and eNB of rel-10 then how UE will decode messages which is of rel-10 coming from eNB? and please tell me whethr this case is possible or not ?
DeleteNormally, eNB wouldn't include any non-rel-8 fields, IEs in the setup message itself. I was checking the RRC specification and found the below point which might be useful for you...
DeleteThe UE shall, when receiving an RRC message on any logical channel:
1> if the message includes a field that the UE does not comprehend:
2> treat the rest of the message as if the field was absent;
Thanks for your reply, i got my answer.
DeleteThis comment has been removed by the author.
ReplyDeletecan u tell me the what are the critical extensions & non critical extensions....any one can give the clarification
ReplyDeleteCritical extensions are characterised by a redefinition of the PDU contents and need to be governed by a mechanism for protocol version agreement between the encoder and the decoder of the PDU, such that the encoder is prevented from sending a critically extended version of the PDU type, which is not comprehended by the decoder.
DeleteNon-critical extensions are characterised by the addition of new information to the original specification of the PDU type. If not comprehended, a non-critical extension may be skipped by the decoder, whilst the decoder is still able to complete the decoding of the comprehended parts of the PDU contents
Please refer to 36.331 Annex A for more details...
what will be the timer in between the rrc connection setup and rrc connection setup complete?
ReplyDeleteI am not sure if the timer value is specified any where. But I have checked a vendor and they have a 4 seconds value which still seemed to be very high.
DeleteIt can be configured at enodeB level
DeleteIt completely depends on operator what he wants to set it.
By default I have seen it as 5000ms
why RRC connection setup is sent again after RRC complete message is received ? the scenario that I have is
ReplyDeleteRRC connection request
RRC connection setup
RRC connection setup complete
RRC connection setup ( the message content is exactly like the first setup except for the CFN is different)
At what time of receiving RRC connection setup UE knows it is his RRC connection setup message
ReplyDeleteHow UE will know that this msg is rrc connetion setup msg ?
ReplyDeleteplease can you just explain..
At the time of receiving rrc connection setup how ue knows that its his rrc connection setup
ReplyDeleteWe will get CRNTI as UE specific information in RRC connection setup msg through which UE can check that this RRC connection setup msg is for him only.
DeleteSo does the RRC connection setup message actually include a C-RNTI? I can't seem to find it in the figure above
DeleteCRC of the thsi PDU is scrambled with the c-rnti , hence UE idenifies the recieeved message is intended for him
Delete