top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

why not having separate transmitting and receiving RLC entity in RLC AM mode?

+1 vote
311 views

As per very first diagram in LTE RLC specification its having separate transmitting and receiving RLC entites for UM and TM ? why not for AM mode???

posted Jul 25, 2016 by Suchakravarthi Sripathi

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

1 Answer

+1 vote

Hi sripathi,

The diagram says, RLC AM mode need acknoledgement form the recived entity , once recieving entity sents ack then transmitter route thosh ack to RLC control, If it is a DATA PDU then transmitter entity forward those to upper layer.basically It should be coupled to route the Status PDU and data PDU. in case of TM and UM mode routing is not needed becaue there is no uplink response , so what ever you recive in transmitter side it is purely data PDU.

answer Jul 25, 2016 by Jaganathan
"  If it is a DATA PDU then transmitter entity forward those to upper layer." ... what does it mean jaganathan... can you clarify
Hi,

Say there is simultaneous data transfer between UE and ENB (DL/UL), Enb have transmitted some DL packets then he will be waititng for the response(ack / nack), But in the response there can be a data corresponding to UL transmission of UE(because simultaneous transmission is going on) or Status PDU for the corresponding DL transmission. In order differentiate these two type routing is used and routed accordingly.

:)
Similar Questions
+7 votes

While going through specification, a term "window stalling" is mentioned. Can anyone please explain it ?

+6 votes

While going through 3GPP 36.322 specification. I saw a routing box inside the figure. Can anyone please explain the uses of it ?

+1 vote

As per 3gpp 36.322 Release 12.0 RLC specification, Extended RLC LI field = 15 bit is newly included in AM mode.
Can anyone please explain, exactly in what condition this 15-bit LI value will be used.

...