FFR errors

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #7804
    Nakrop Jinaporn
    Participant

    Dear The Vienna Team,

    I am working on FFR. After re-downloading the simulator, I try running Launcher_FFR_performance_simulations.m. There are errors as follows:

    TTI 1/25: +++++*****Operands to the || and && operators must be convertible to logical scalar values.

    Error in network_elements.UE/set_SINRs_according_to_schedule (line 568)
    if DL_signaling.num_assigned_RBs>0 && ~obj.deactivate_UE

    Error in LTE_sim_main (line 466)
    UEs(u_).set_SINRs_according_to_schedule

    Error in Launcher_FFR_performance_simulations (line 107)
    generated_file = LTE_sim_main(currentLTE_config);

    After checking the beta_FR in the new script, I can run the simulator with some values such as 0.5, 0.7, 0.75.

    However, there are errors with other values e.g. beta_FR = 0.01.

    TTI 1/10: +++++Subscript indices must either be real positive integers or logicals.

    Error in schedulers.roundRobinScheduler/get_next_users (line 62)
    obj.last_extracted = to_extract(end);

    Error in schedulers.roundRobinScheduler/schedule_users (line 78)
    RB_grid.user_allocation(:) = obj.get_next_users(size(RB_grid.user_allocation,1));

    Error in schedulers.ffrScheduler/schedule_users (line 172)
    obj.FR_scheduler.schedule_users(FR_UEs,FR_feedback);

    Error in network_elements.eNodeB_sector/schedule_users (line 259)
    obj.scheduler.schedule_users(obj.attached_UEs_vector,obj.last_received_feedback);

    Error in LTE_sim_main (line 442)
    eNodeBs(s_).schedule_users;

    Please let me know if you have any suggestions.

    Best regards,
    Nakrop

    #7892

    Hi Nakrop,

    I could not reproduce your error, it works fine with beta_FR = 0.1.

    You might try to delete all previously generated data files. Also make sure that you simulate at least one full ring of eNodeBs.

    Please let me know, if that solved your problems.

    Best regards,
    Martin

    #7899
    Nakrop Jinaporn
    Participant

    Dear Martin,

    Thanks for your support. My first point is to compare the default (Reuse-1) scheduling with the Reuse-1 from FFR setting. The same results could be obtained. The configuration is summarised as follows:

    LTE_config.simulation_time_tti = 50;
    LTE_config.bandwidth = 20e6;
    LTE_config.nr_eNodeB_rings = 2;
    LTE_config.UE_per_eNodeB = 30;

    LTE_config.nTX = 4;
    LTE_config.nRX = 4;

    LTE_config.macroscopic_pathloss_model = ‘TS36942’;
    LTE_config.shadow_fading_type = ‘none’;
    LTE_config.antenna_gain_pattern = ‘kathreinTSAntenna’;
    LTE_config.antenna.electrical_downtilt = 8;

    LTE_config.scheduler = ‘FFR’;
    LTE_config.scheduler_params.FR_scheduler.scheduler = ’round robin’;
    LTE_config.scheduler_params.PR_scheduler.scheduler = ’round robin’;

    LTE_config.FFR_params.beta_FR = 1;
    LTE_config.FFR_params.SINR_threshold_value = -2;
    % Minimum threshold point at cell edge

    There was error as follows:

    TTI 1/50: +++++*****Operands to the || and && operators must be convertible to logical scalar
    values.

    Error in network_elements.UE/set_SINRs_according_to_schedule (line 568)
    if DL_signaling.num_assigned_RBs>0 && ~obj.deactivate_UE

    Error in LTE_sim_main (line 466)
    UEs(u_).set_SINRs_according_to_schedule

    Another point is that edge throughput with a specific FFR setting (e.g., beta_FR = 0.75 and SINR_threshold_value = 12.75 dB) was significantly lower than the case without FFR (LTE_config.scheduler = ’round robin’). To the best of my knowledge, the edge throughput could be improved by FFR.

    Can we set beta_FR = 0.01 and SINR_threshold_value = -2 dB (Minimum threshold point at cell edge) to analyse Reuse-3 in the Vienna simulator?

    Thanks and best wishes,
    Nakrop

    #7920

    Dear Nakrop,

    Please try to re-download the simulator, there was a bug with locical scalars when using reuse-1 with FFR that is fixed now.

    Regarding reuse factor, yes to analyse the reuse-3 you have to set beta_FR = 0.01 when using a bandwidth of 20MHz.
    Regarding the SINR threshold value, if the SINR (SINR value from the pathloss map) is bigger than the threshold, the UE is set to be a FR UE, and viceversa. Based on the SINR map, try to addapt the value for the SINR threshold in order to simulate your desired setup.

    Best regards,
    Fjolla

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.