Bug 2777 - bearer differentiation after handover
bearer differentiation after handover
Status: RESOLVED FIXED
Product: ns-3
Classification: Unclassified
Component: lte
unspecified
All All
: P3 normal
Assigned To: Biljana Bojović
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-25 09:58 UTC by Tom Henderson
Modified: 2017-08-30 05:57 UTC (History)
2 users (show)

See Also:


Attachments
Patch for bug 2777 (656 bytes, patch)
2017-08-29 16:44 UTC, Zoraze Ali
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Henderson 2017-08-25 09:58:16 UTC
A user (Sahawat Namwanta) provided the following report.

"Hello, I'm using NS-3.26 and face the problem with the bearer differentiation after handover.

When the UEs first attach to the first eNB, the scheduler was able to differentiate between each bearer just fine.
However, when the first handover occurred, the scheduler sees all UEs as the same bearer (NGBR_VIDEO_TCP_DEFAULT)."
Comment 1 Zoraze Ali 2017-08-29 16:44:02 UTC
Created attachment 2909 [details]
Patch for bug 2777
Comment 2 Zoraze Ali 2017-08-29 16:46:14 UTC
The bug was in UeManager::SetupDataRadioBearer (EpsBearer bearer, uint8_t bearerId, uint32_t gtpTeid, Ipv4Address transportLayerAddress) in lte-enb-rrc. The "bearer" parameter contains an updated EPS bearer related specification, which in the current code is not used to update the default m_epsBearer member of drbInfo. Thus the call to AddDataRadioBearerInfo (drbInfo) is saving drbInfo with default bearer QCI into m_drbMap map.  

This map is later accessed by source eNB to retrieve the EPS bearer related info to be included in handover request to the target eNB.

Please find the attached patch which was tested by the reported user and has resolved the problem. 

Kind regards,
Zoraze
Comment 3 Zoraze Ali 2017-08-30 05:57:45 UTC
Fixed in changeset 13053 c4eff6091564