This commit is contained in:
Nicola Baldo
2013-07-29 13:26:01 +02:00
parent a7c242aba7
commit a4a7b6b277
2 changed files with 7 additions and 5 deletions

View File

@@ -2085,11 +2085,13 @@ The simulation user can set two parameters to control the handover decision:
serving cell is less or equal to the servingHandoverThreshold parameter
(i.e. the conditions of the UE in the serving cell are getting bad or
not good enough), then the eNB considers this UE to hand it over to a new
neighbour eNB. The handover will really triggered depending on the
neighbour eNB. The handover will eventually be triggered depending on the
measurements of the neighbour cells.
- neighbourHandoverOffset, if the difference between the best neighbour RSRQ
and the serving cell RSRQ is greater or equal to the neighbourHandoverOffset
- neighbourHandoverOffset, if the UE is considered for handover, and
the difference between the best neighbour RSRQ
and the RSRQ difference between the neighbor and the serving cell
is greater or equal to the neighbourHandoverOffset
parameter, then the handover procedure is triggered for this UE.

View File

@@ -564,8 +564,8 @@ It is to be noted that any mobility model can be used; however, based on the inf
BuildingsHelper::Install (ueNodes);
NetDeviceContainer ueDevs;
ueDevs = lteHelper->InstallUeDevice (ueNodes);
Ptr<BuildingsMobilityModel> mm0 = enbNodes.Get (0)->GetObject<ConstantPositionMobilityModel> ();
Ptr<BuildingsMobilityModel> mm1 = enbNodes.Get (1)->GetObject<ConstantPositionMobilityModel> ();
Ptr<ConstantPositionMobilityModel> mm0 = enbNodes.Get (0)->GetObject<ConstantPositionMobilityModel> ();
Ptr<ConstantPositionMobilityModel> mm1 = enbNodes.Get (1)->GetObject<ConstantPositionMobilityModel> ();
mm0->SetPosition (Vector (5.0, 5.0, 1.5));
mm1->SetPosition (Vector (30.0, 40.0, 1.5));