- Dec 21, 2017
-
-
shahab SHARIAT BAGHERI authored
-
- Dec 15, 2017
-
-
Navid Nikaein authored
-
- Dec 14, 2017
-
-
shahab SHARIAT BAGHERI authored
-
Navid Nikaein authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
- lock with mutexes - don't start ENB_APP task, but Agent directly and wait in case of reconfiguration
-
Robert Schmidt authored
-
Robert Schmidt authored
- {restart,stop}_L1L2() in lte-softmodem.c - add function start_phy_rrc() in enb_app.{c,h}, accessible from outside - will be used to restart PHY and RRC when lte-softmodem is restarted use only one FlexRAN wait function
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Navid Nikaein authored
-
Robert Schmidt authored
-
- Dec 13, 2017
-
-
Navid Nikaein authored
-
- Dec 12, 2017
-
-
Navid Nikaein authored
*Fix the issue with the PDCP UE ID/RNTI management
-
shahab SHARIAT BAGHERI authored
-
Navid Nikaein authored
-
Navid Nikaein authored
-
- Dec 11, 2017
-
-
Navid Nikaein authored
-
- Dec 10, 2017
-
-
shahab authored
-
shahab SHARIAT BAGHERI authored
-
- Dec 09, 2017
-
-
shahab authored
-
- Dec 08, 2017
-
-
Navid Nikaein authored
-
- Nov 17, 2017
-
-
Navid Nikaein authored
-
- Aug 09, 2017
-
-
shahab SHARIAT BAGHERI authored
-
shahab SHARIAT BAGHERI authored
-
- Aug 08, 2017
-
-
Cedric Roux authored
protobuf-c does not compile anymore. Let's handle this a bit better. We now install protobuf and protobuf-c only for the flexran agent. That is, if you want to use the flexran agent, you need to install protobuf/protobuf-c and you do it this way: ./build_oai -I -a (you add -a) Other targets don't need protobuf nor protobuf-c, so it's not installed by the -I command of build_oai, unless you pass -a with -I. Also, we now use protobuf 3.3.0, not 2.6.1. The code has been adapted, a quick test seems to indicate that the system works, but it has not been intensively tested.
-
- Aug 04, 2017
-
-
Anta Huang authored
-
Anta Huang authored
-
shahab SHARIATBAGHERI authored
-
shahab SHARIATBAGHERI authored
-
shahab SHARIATBAGHERI authored
-
- Jul 27, 2017
-
-
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
-
- Jul 25, 2017
-
-
shahab SHARIATBAGHERI authored
-
- Jul 20, 2017
-
-
Anta Huang authored
-
- Jun 29, 2017
-
-
fnabet authored
-
- Jun 08, 2017
-
-
shahab SHARIATBAGHERI authored
-
- Jun 02, 2017
-
-
Frank A. Zdarsky authored
Signed-off-by:
Frank A. Zdarsky <fzdarsky@redhat.com>
-
Cedric Roux authored
- rename UE_NO_LOG to DISABLE_LOG_X because the name is misleading. The full software is impacted, not only the UE part - same for compilation option ---ue-no-log that becomes --disable-log - keep LOG_X for the standard case, that is the case without DISABLE_LOG_X where printf has been put. Two reasons: * printf is not realtime friendly * keep behavior similar for other users who may be troubled by different logs that don't add any benefit to previous logs
-