- Jul 03, 2018
-
-
WEI-TAI CHEN authored
-
- Jun 27, 2018
-
-
WEI-TAI CHEN authored
-
WEI-TAI CHEN authored
-
- Jun 26, 2018
-
-
WEI-TAI CHEN authored
-
- Jun 15, 2018
-
-
WEI-TAI CHEN authored
- It coulde be build, but there are "implicit declaration of function" warnings in MAC layer. Since we re-use the MAC layer function. - Maybe it is already could be test for configuration module.
-
WEI-TAI CHEN authored
-
- Jun 14, 2018
-
-
WEI-TAI CHEN authored
- Create task for GAB_APP and GAN_RRC - Create the NR FAPI for P5 interface - *It could be build, but still have a lot of warning need to maintain
-
- May 28, 2018
-
-
WEI-TAI CHEN authored
-
- May 18, 2018
-
-
WEI-TAI CHEN authored
2.NR RRC do_SERVINGCELLCONFIGCOMMON for all of common config. will be transmit to lower layer by rrc_mac_config_req_gNB"
-
- May 03, 2018
-
-
WEI-TAI CHEN authored
-
- Apr 26, 2018
-
-
WEI-TAI CHEN authored
1. Modify the wrong name file ans1c to asn1c 2.Update the do_MIB function 3.Update the gNB initial parameter for non-standalone
-
- Apr 13, 2018
-
-
WEI-TAI CHEN authored
-
- Apr 08, 2018
-
-
Raymond Knopp authored
-
- Apr 06, 2018
-
-
root authored
Conflicts: cmake_targets/build_oai openair1/PHY/LTE_TRANSPORT/prach.c openair1/SCHED/phy_procedures_lte_ue.c targets/ARCH/COMMON/common_lib.h targets/RT/USER/lte-softmodem.c
-
- Mar 27, 2018
-
-
Bi-Ruei, Chiu authored
This feature requires an un-official version of asn1c : https://github.com/velichkov/asn1c/tree/s1ap
-
- Feb 22, 2018
-
-
Cedric Roux authored
-
- Feb 14, 2018
-
-
Cedric Roux authored
Doing airplane mode off to connect a cots UE followed by airplane mode on to disconnect it gives very bad results (bad disconnection with lots of UL failures followed by lots of logs in the eNB). It used to work properly after the work done by Xu Bo. It turns out that in 2018.w04 things were still working okay. But in 2018.w05 no. So I ran: git diff 2018.w04 2018.w05 And I checked all the modifications that I thought were relevant (everything related to the UE, oaisim, if4 and fapi has not been checked). This commits takes back the version of 2018.w04. The modifications in openair2/RRC/LITE/rrc_eNB.c are necessary, I think. The other modifications may not be necessary or even wrong. To be checked at some point.
-
- Feb 12, 2018
-
-
Robert Schmidt authored
-
Robert Schmidt authored
-
- Feb 08, 2018
-
-
Robert Schmidt authored
-
- Feb 05, 2018
-
-
Cedric Roux authored
The following compilation did not work anymore: ./build_oai --eNB -w USRP -r Rel10 -c (Rel8 still does not work.)
-
- Jan 31, 2018
-
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
- Jan 25, 2018
-
-
Raymond Knopp authored
-
- Jan 22, 2018
-
-
Cedric Roux authored
As reported by Emad Alizade: According to "Issue255 256 257 paging reesta release" that has been merged in develop version, we have a question: In rrc_eNB_free_UE() function only all ulsch related memory of user has been cleaned, but I think not only ulsch memory but also dlsch memory must be cleaned. I tested the latest develop version and with repetition UE attach-detach procedures we find that the dlsch memory has not been cleaned and after repeat this sequence (45 times) assertion with cause UE_id!=-1 (no free or exiting dlsch_context, dci_tools.c: fill_dci_and_dlsch() ) occurred and no UE will be attached to system. The fixes in this commit are from Emad Alizade.
-
- Jan 21, 2018
-
-
Rohit Gupta authored
fixes after merge with develop. Partial UE/eNB separation in build to avoid problems with NFAPI in oaisim UE/RRU. tested with simulator.
-
- Jan 15, 2018
-
-
bruno mongazon authored
Fix #582, RTAI, RTAI_ENABLED, ENABLE_RTAI_CLOCK, RTAI_ISNT_POSIX, _RTAI_MATH_H, CELLULAR, TIMER_ONESHOT_MODE, EMOS, EMOS_CHANNEL, OAI_EMU, OPENAIR_EMU, PHY_ABSTRACTION, PHY_ABSTRACTION_UL removed
-
Cedric Roux authored
This commit fixes issues introduced by the previous commit. Summary of work: - cleanup: - fix LOG_XX to be less verbose - fix cmake_targets/CMakeLists.txt - fix oaienv - remove dead code - bug fixes: - in openair1/SCHED/fapi_l1.c we had: eNB->pdcch_vars[subframe&1].num_dci = number_dci; should be: eNB->pdcch_vars[subframe&1].num_dci = 0; This bug let the PHY send more DCIs than what should have been sent because num_dci is incremented later on in the code. This fix may be a problem for fapi mode, to be checked. - add new T VCD traces - revert openair1/PHY/TOOLS/file_output.c to 'develop' version - remove thread_id in logRecord/logRecord_mt - revert (and adapt) configuration files - be careful when doing frame++, we need to % 1024 - revert target_rx_power in openair2/LAYER2/MAC/eNB_scheduler_ulsch.c - NFAPI: - the open-nFAPI code has been included in the repository. See nfapi/README. Maybe we should "git clone" the Cisco repository instead. We have to be careful of availability though. What has been tested: - monolithic eNB FDD 5/10MHz with one UE, iperf UDP/TCP uplink/downlink Anything else may fail to work, especially the FAPI mode, which has not been tested at all.
-
Cedric Roux authored
It has been chosen to not include the full history of commits from David. He included a binary version of wireshark, probably a modified one that understands NFAPI. Wireshark is released under the GPL license, we cannot include it in the repository. We could have done a next commit to remove this binary. But then it would still be present in the history of commits, which may not be allowed. And it would take space on disk. We could edit the history to remove wireshark entirely. But this operation is too complicated. There was also a pcap capture file, which has nothing to do in the history of commits and would take space on disk. There again, it's too difficult to edit the history to remove it. There was a file .gitignore that was also removed. The original history can be found on David's repository: https://gitlab.eurecom.fr/daveprice/openairinterface5g/ The branch is: nfapi-ru-rau-split. A copy of that branch has been included in the internal OAI repository, for those who have access to it. The branch is the same. The last commit ID is 9106438239e0bc626ff1fa1d97d911caadd0fbb9. You can compare the current commit with the commit 9106... to see what differs. The current commit has to be considered non-working. The commit following the current commit will fix problems with the work in the current commit. If you use git bisect, don't spend time analyzing the current commit.
-
- Jan 14, 2018
-
-
Rohit Gupta authored
-
- Jan 11, 2018
-
-
bruno mongazon authored
-
- Jan 09, 2018
-
-
Xu Bo authored
-
- Jan 08, 2018
- Dec 28, 2017
-
-
Raymond Knopp authored
-
- Dec 21, 2017
-
-
shahab SHARIAT BAGHERI authored
-
- Dec 14, 2017
-
-
Robert Schmidt authored
-
- Dec 12, 2017
-
-
Navid Nikaein authored
*Fix the issue with the PDCP UE ID/RNTI management
-
- Nov 27, 2017
-
-
Xu Bo authored
merge the implemention of Paging, RRCConnectionRelease, RRCConnectionReestablishment, E-RAB Modify, E-RAB Release
-