An error occurred fetching the project authors.
- 09 May, 2018 1 commit
-
-
jftt_wangshanshan authored
-
- 26 Apr, 2018 1 commit
-
-
jftt_wangshanshan authored
-
- 25 Apr, 2018 1 commit
-
-
jftt_wangshanshan authored
-
- 23 Apr, 2018 1 commit
-
-
jftt_wangshanshan authored
-
- 10 Apr, 2018 1 commit
-
-
wujing authored
-
- 09 Apr, 2018 2 commits
-
-
Masayuki HARADA authored
-
Masayuki HARADA authored
-
- 04 Apr, 2018 1 commit
-
-
jftt_wangshanshan authored
-
- 26 Mar, 2018 1 commit
-
-
Masayuki HARADA authored
・Delete double BSR calculation. ・change TBS for mcs setting bit to byte. (cherry picked from commit 39cd022424ebe98c95be32cbb4127aa9d0e0ff3b)
-
- 12 Mar, 2018 2 commits
-
-
jftt_wangshanshan authored
-
jftt_wangshanshan authored
-
- 08 Mar, 2018 1 commit
-
-
wujing authored
-
- 06 Mar, 2018 1 commit
-
-
wujing authored
-
- 01 Mar, 2018 1 commit
-
-
naoi authored
-
- 28 Feb, 2018 1 commit
-
-
naoi authored
Fix: Random access information is not released when Msg3(response to PDCCH order) re-transmission fails.
-
- 22 Feb, 2018 1 commit
-
-
naoi authored
eNB should be keep UE context longer than T311 timer after UL failure is detected in layer2. Configuration file(GENERIC-LTE-EPC) sets T311 to 10s, so eNB keep UE context up to 20s.
-
- 12 Feb, 2018 2 commits
-
-
wujing authored
-
jftt_wangshanshan authored
-
- 11 Feb, 2018 1 commit
-
-
Xu Bo authored
-
- 08 Feb, 2018 3 commits
-
-
jftt_wangshanshan authored
-
jftt_wangshanshan authored
-
wujing authored
-
- 05 Feb, 2018 2 commits
-
-
Xu Bo authored
-
jftt_wangshanshan authored
-
- 01 Feb, 2018 2 commits
- 27 Jan, 2018 1 commit
-
-
Xu Bo authored
-
- 15 Jan, 2018 2 commits
-
-
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.
-
- 13 Jan, 2018 1 commit
-
-
Xu Bo authored
-
- 27 Dec, 2017 1 commit
-
-
Xu Bo authored
-
- 28 Nov, 2017 1 commit
-
-
Xu Bo authored
merge the implemention of Paging, RRCConnectionRelease, RRCConnectionReestablishment, E-RAB Modify, E-RAB Release
-
- 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
-