X2 restrictions

This topic contains 1 reply, has 2 voices, and was last updated by  Presenter 4 years, 1 month ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #292


    Thank you for your presentation! I have a few questions to your simulations:
    – In Scenario 1, why is the number of reserved RBs (red-dashed) larger than the number of requested RBs (green-solid) even if X2 latency is 0ms?
    – In Scenario 2, can you please provide some intuition why the delay increases so much stronger when going from 10ms latency to 20ms as compared to going from 0ms to 10ms?




    1) the considered coordination algorithm divides the entire available bandwidth (50 RBs in our simulations) between eNBs, proportionally to their requests. Thus, if the sum of the requested RBs is smaller than 50 RBs, the coordinator has to allocate more RBs than those requested from eNBs so as to fill up the whole bandwidth (still maintaining the proportion between RBs requested by eNBs)

    2) in that scenario, increasing X2 latency results in having bad interference conditions for longer time. In that case, UEs require more RBs to be served (since they have small CQI), increasing the load at the eNB (as shown in Fig.13 of the paper). In this condition, it is likely that users’ data are buffered at the eNB for a longer time and experience more queueing delay, which comes on top of the increased communication latency on the X2.

    Hope this answers your questions!


Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.