top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Who does radio bearer mapping during UTRAN to E-UTRAN handover where source RNC is pre-release 8

+5 votes
430 views

Who does radio bearer mapping during UTRAN to E-UTRAN handover where source RNC is pre-release 8 ? From the spec what I can see is if the source RNC is pre release 8, then it sends Source RNC to Target RNC transperant container (which I believe carries all the radio bearer related information). The EPC will transperantly forward it to the Target enodeB. Does the target EnodeB do the mapping from RNC container for the radio bearer in the new RAT ?

posted Dec 28, 2015 by anonymous

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button
could you let us know the spec and secton please ?
commented Dec 28, 2015 by anonymous
TS 23401: rel 9f0 sec 5.5.2.2.2 Also checked in rel 13 ver d50. It says "relocation required" message contains Source RNC to Target RNC transparent container.

TS 25413 ver 7a0 section 8.6.2 about "relocation required" message does not mentioned anything about handover to E-UTRAN.

However TS 25413 Ver 9a0 sec 8.6.2. or any release 8 ver, do mention about sending Source eNB to Target eNB Transparent container.
commented Dec 30, 2015 by Jyoti Prasad

Similar Questions
+5 votes
LTE: Why presence of Tracking Area Identity (TAI) and E-UTRAN CGI (ECGI) IEs is mandatory in Uplink NAS Transport ?

Uplink NAS transport message is used between eNodeB and MME to pass NAS messages between UE and MME transparently.
Since eNodeB has already communicated TAI and E-CGI as part of "Initial UE message" and MME knows current serving (cell and tai ) of UE then why both IEs are mandatory in Uplink NAS transport. I think it should be optional and it should be included in the message when there is a change in serving (cell or tai or both).

+2 votes
LTE: Why "Handover Type" IE is included in both handover messages i.e Handover Required and Handover Request ?

I was looking into IEs of handover required and handover command messages defined in 36.413 specification.
Sending "handover type" in handover required message towards the MME make sense but again get back the same IE in handover command message from MME in the handover command message, I could not make out the reason behind it.
Can someone please explain the reason of presence of "Handover Type" IE in the handover command message when eNodeB already knows which type of request it sent to MME for an UE ?

Is there any possibility MME can change the type of Handover in handover command message ? If yes then what could be the scenarios ?

...