An error occurred fetching the project authors.
- 27 Nov, 2017 1 commit
-
-
Cedric Roux authored
Even if the old UE is not found, we have to cancel the random access.
-
- 09 Nov, 2017 1 commit
-
-
Xu Bo authored
-
- 04 Nov, 2017 1 commit
-
-
Raymond Knopp authored
changing of notation for Random-Access procedure to match documentation. Function remains the same. Indentation (-kr) run on all files in LAYER2/MAC
-
- 25 Oct, 2017 1 commit
-
-
Cedric Roux authored
- remove global variables in the function lte_est_timing_advance_pusch - do the smoothing logic that was in lte_est_timing_advance_pusch in rx_sdu (is it necessary? is it correct?) - put back the value 100 in prach_procedures for the test on prach energy - change the value of timing_advance_update it was: timing_advance_update = sync_pos - eNB->frame_parms.nb_prefix_samples/4; //to check it is now: timing_advance_update = sync_pos; // - eNB->frame_parms.nb_prefix_samples/4; //to check this should be checked somehow. The computation looked suspicious. Maybe the new one is wrong.
-
- 23 Oct, 2017 1 commit
-
-
Cedric Roux authored
-
- 19 Oct, 2017 1 commit
-
-
Cedric Roux authored
phy_init_lte_ue_signal was renamed init_lte_ue_signal in openair1/PHY/INIT/defs.h maybe it's the opposite that should have been done? Functions used in one file and defined in another may have been declared in the wrong header file.
-
- 18 Oct, 2017 1 commit
-
-
Cedric Roux authored
TODO: if the UE did random access (followed by a MAC uplink with CRNTI) because none of its scheduling request was granted, then according to 36.321 5.4.4 the UE's MAC will notify RRC to release PUCCH/SRS. According to 36.331 5.3.13 the UE will then apply default configuration for CQI reporting and scheduling requests, which basically means that the CQI requests won't work anymore and that the UE won't do any scheduling request anymore as long as the eNB doesn't reconfigure the UE. We have to take care of this. As the code is, nothing is done and the UE state in the eNB is wrong.
-
- 17 Oct, 2017 1 commit
-
-
Cedric Roux authored
-
- 16 Oct, 2017 1 commit
-
-
Cedric Roux authored
- change target values - change upper/lower limit to trigger a tpc - don't use ul_cqi from SR The value of ul_cqi is not convincing, for both PUSCH and PUCCH, more work/analysis is required.
-
- 15 Oct, 2017 1 commit
-
-
Raymond Knopp authored
-
- 14 Oct, 2017 1 commit
-
-
Raymond Knopp authored
added deactivation of ULSCH harq process after 3rd retransmission. Avoids problem of accumulating failed RA processes.
-
- 12 Oct, 2017 2 commits
-
-
Raymond Knopp authored
-
Cedric Roux authored
this is not handled correctly as of now, let's crash
-
- 11 Oct, 2017 1 commit
-
-
Cedric Roux authored
-
- 10 Oct, 2017 2 commits
-
-
Cedric Roux authored
-
Cedric Roux authored
- re-use ta_timer - when ta_timer is running: - no TA sent to UE - no TA from UE (for UE to have time to apply previous TA command) - decrease ta_timer every TTI - be careful to use correct value of ta_update (31 means no TA) Maybe not correct, to be checked.
-
- 08 Oct, 2017 1 commit
-
-
Raymond Knopp authored
put 50 PRB back in default enb configuration. added handling of UE release in L1/L2. detection of stale ULSCH configuration
-
- 07 Oct, 2017 1 commit
-
-
Raymond Knopp authored
removal of LOG_I put for debugging.
-
- 04 Oct, 2017 1 commit
-
-
Cedric Roux authored
- don't use o_flip anymore in ulsch_decoding - remove dl_cqi from eNB_UE_STATS - put dl_cqi[NFAPI_CC_MAX] in UE_sched_ctrl - adapt code for this dl_cqi change (from eNB_UE_STATS to UE_sched_ctrl) - extract_pusch_csi has been fixed for CQI_ReportModeAperiodic_rm30, the others need to be done. Program will exit if one uses them. Not sure if setting sched_ctl->dl_cqi[CC_idP] has to be done in this function...
-
- 03 Oct, 2017 1 commit
-
-
Cedric Roux authored
-
- 01 Oct, 2017 2 commits
-
-
Raymond Knopp authored
-
Raymond Knopp authored
fixed various bugs in NFAPI interface and DCI CCE allocations (eNB_scheduler_primitives.c:allocate_CCEs())
-
- 27 Sep, 2017 1 commit
-
-
Cedric Roux authored
not finished, UE may not work, many things bad/to fix properly
-
- 25 Sep, 2017 2 commits
-
-
Raymond Knopp authored
-
Francois TABURET authored
-
- 24 Sep, 2017 3 commits
-
-
Raymond Knopp authored
-
Raymond Knopp authored
-
Raymond Knopp authored
-
- 21 Sep, 2017 1 commit
-
-
Raymond Knopp authored
-
- 19 Sep, 2017 1 commit
-
-
Raymond Knopp authored
-
- 14 Sep, 2017 1 commit
-
-
Raymond Knopp authored
-
- 30 Aug, 2017 1 commit
-
-
Cedric Roux authored
-
- 24 Aug, 2017 1 commit
-
-
Cedric Roux authored
This commits contains several fixes to improve a multi-UE scenario. This is not the end of the story. Summary of work: ================ 1 - improve SR (scheduling requests): We configured n1pucch == 3 for scheduling requests, for all UEs. We now use 71 - UE_id/10. For it to work, it is vital that pucch_nRB_CQI in the configuration file is set to 0, otherwise the SR will go to an RB used for PUSCH and uplink decoding will fail whenever an UE does SR. Note that we will have problems with 20MHz when we use a CCE that let the UE send the ACK/NACK using a n1pucch allocated for SR, because when the PDCCH is of size 3, we can have 87 CCEs and it may lead to an n1pucch colliding with one for SR. The work done in this patch is a quick solution, seems to work with 10MHz. The real solution is to disable the use of those CCEs that would lead an UE to use a n1pucch colliding with an SR n1pucch. Then we can use whatever n1pucch we want for SR, as long as the scheduler protects them. Impacted files: configuration files openair2/RRC/LITE/MESSAGES/asn1_msg.c 2 - some fixes for uplink scheduling: - Do not use PRACH for PUSCH, that leads to too many false PRACH detection. Plus the PUSCH receiving may fail if one UE uses the PRACH at the same time. - Take care of retransmissions. That was not done at all, so we could allocate one RB to several UEs. The current design of the code makes it hard to do it properly, so we chose a quick and dirty solution, which is to increase "first_rb" to skip any RB used for retransmission. In this process we may skip a lot of free RBs. A proper solution is needed here. - Do not allocate the last RB. This one is used for PUCCH. It was sometimes allocated to PUSCH. - In the pre-processor we didn't pre-allocate RBs to UEs with an empty buffer status. We didn't check if the UE sent an SR. For example in a three UEs scenario, we could have the third UE never scheduled in the uplink. - rb_table_index was not decreased properly, so we allocated too much RBs to some UEs and thus not enough to others. Impacted files: openair2/LAYER2/MAC/eNB_scheduler_ulsch.c openair2/LAYER2/MAC/pre_processor.c openair1/SCHED/phy_procedures_lte_eNb.c 3 - some fixes for downlink scheduling: - The check on CCE allocation was not correct. We did something like: if (cce allocation is possible) { prepare } We should have done: save current cce allocation if (cce allocation is possible) { allocate cce prepare } reset current cce allocation Basically, when we scheduled several UEs, they were checked separately, and the totality of them was not checked. Impacted file: openair2/LAYER2/MAC/eNB_scheduler_dlsch.c - The retransmissions are probably not handled correctly. Check in openair2/LAYER2/MAC/pre_processor.c, near the comment "// control channel or retransmission", the case "round > 0" was added. It's probably not enough, even maybe not correct. - Change SF05_LIMIT with SF0_LIMIT. We accept to use central blocks in SF 5. The code was also not correct, vrb_map was not set properly because the loop on j was wrong for the last RBG (which can have one less RB than the others). This is not satisfying. The real solution is to use the central RBs and check that the MCS used is compatible with the numbers of resource elements allocated (we don't want to put too more data bits than what fits). 4 - some fixes in PUCCH decoding: See: openair1/PHY/LTE_TRANSPORT/pucch.c Probably not enough. Some more work and analysis is required for a proper use of the PUCCH. What we see is that the PUCCH constellation gets wrong when there are several UEs, meaning the received ACK/NACK is not properly decoded (this, or something else...). 5 - several fixes/checks added here and there: - The final allocate_CCEs in eNB_dlsch_ulsch_scheduler is checked and we brutally exit if it fails. - We exit in get_num_pdcch_symbols in case of failure (this should never happen anyway, no big deal normally). - Some logs added or changed to error/warning instead of debug. - In dlsch_scheduler_pre_processor an abort() was added. The code here looks suspicious. - In assign_max_mcs_min_rb, rb_table_index was not set to 2, the value 0 was used. This was not correct. What remains to be done: ======================== - Correct CCE allocation (take into account SR n1pucch, check that all the n1pucch that will be used are "compatible"). - Take into account the PHICH when scheduling uplink. As of today it is very possible to have two UEs use the same PHICH group and PHICH sequence index. We can use n_DMRS in the DCI to have uniqueness (see 36.213 table 9.1.2-2). We can drop an allocation if there is no free PHICH group/sequence index for a given UE. - When there is an uplink retransmission in the PRACH, we have to disable PRACH detection. It is possible that one UE does PRACH at the same time, but then what to do? We could use DCI0-based retransmission in this specific case maybe... - Handle free RBs in uplink in a much better way in case of a retransmission. We may have a lot of free unused RBs with the current code. - Check downlink retransmissions. Not much has been done there. - Surely more stuff not clear yet. In some situations we don't have a good behavior of the system. Hard to describe more precisely at this point.
-
- 17 Aug, 2017 1 commit
-
-
Raymond Knopp authored
-
- 13 Aug, 2017 1 commit
-
-
Raymond Knopp authored
complete programming of Msg2/Msg4 procedures for eMTC. Addition of skeleton for PUCCH UCI (NFAPI) in L1. Some cleanup of eNB_scheduler.c
-
- 10 Aug, 2017 1 commit
-
-
Raymond Knopp authored
-
- 27 Jul, 2017 1 commit
-
-
Cedric Roux authored
This bug happens when we detect uplink failure for one UE. In this case, a DCI format 1A is sent to the UE to ask it to do random acces. The way this DCI is generated was not compatible with how the software is organized. It was expected that the DCI are added (with add_ue_spec_dci and add_common_dci) in a very specific order: first all DCIs in common space are added (with add_common_dci) then all DCIs in UE specific space are added (with add_ue_spec_dci). The problem was that the DCI format 1A DCI sent to the UE for it to do random access is added (with add_ue_spec_dci) before the DCIs in common space. That totally messed up the logic in add_common_dci and add_ue_spec_dci. The solution is to get rid of Num_common_dci and Num_ue_spec_dci, replace those two counters by only one (Num_dci) and add "search_space" in the dci_alloc structure to be used later by the function "allocate_CCEs" when calling "get_nCCE_offset". The software had to be adapted to the new variables, everywhere. I am not sure that the simulators work. It seems that some of them didn't use Num_common_dci and Num_ue_spec_dci to decide on what space (common or UE specific) to put the DCI, but relied on the rnti (comparing with SI_RNTI). To be tested properly. The modified simulators are: - openair1/SIMULATION/LTE_PHY/dlsim.c - openair1/SIMULATION/LTE_PHY/dlsim_tm4.c - openair1/SIMULATION/LTE_PHY/dlsim_tm7.c - openair1/SIMULATION/LTE_PHY/framegen.c - openair1/SIMULATION/LTE_PHY/pdcchsim.c - openair1/SIMULATION/LTE_PHY/syncsim.c
-
- 19 Jul, 2017 1 commit
-
-
Raymond Knopp authored
-
- 06 Jul, 2017 1 commit
-
-
Raymond Knopp authored
Note: this commit is work in progress. Contains initial integration of NFAPI data structures which are tested for TX path. RX path to follow.
-
- 04 Jun, 2017 1 commit
-
-
Raymond Knopp authored
-