openairinterface5G issueshttps://gitlab.eurecom.fr/oai1B/openairinterface5g/-/issues2018-12-07T12:59:16Zhttps://gitlab.eurecom.fr/oai1B/openairinterface5g/-/issues/50ULSCH consecutive error2018-12-07T12:59:16ZGhost UserULSCH consecutive errorUE is removed by eNodeB because ULSCH consecutive error count is reached.
We have eNB compiling and running on LMSSDR, however we still have issues achieving and maintaining attach complete with UE.
Below were the error appeared in eNB...UE is removed by eNodeB because ULSCH consecutive error count is reached.
We have eNB compiling and running on LMSSDR, however we still have issues achieving and maintaining attach complete with UE.
Below were the error appeared in eNB…
[MAC][I][eNB_dlsch_ulsch_scheduler] UE rnti 5452 : in synch, PHR 40 dB
[RRC][I]UE rnti 5452 failure timer 0/20000 [PHY][I]UE 0 : rnti 5452
[MAC][I][eNB_dlsch_ulsch_scheduler] UE rnti 5452 : in synch, PHR 40 dB [RRC][I]UE rnti 5452 failure timer 0/20000
[PHY][W][eNB 0, CC 0] frame 310, subframe 2, UE 0: ULSCH consecutive error count reached 20, triggering UL Failure
[MAC][I][UL_failure_indication] [eNB 0][UE 0/5452] Frame 310 subframeP 2 Signaling UL Failure for UE 0 on CC_id 0 (timer 0)
[PHY][E]ERROR: Format 1A: rb_alloc (1ff) > RIV_max (144) [PHY][E]ERROR: Format 1A: rb_alloc (1ff) > RIV_max (144)
[PHY][E]ERROR: Format 1A: rb_alloc (1ff) > RIV_max (144) [PHY][E]ERROR: Format 1A: rb_alloc (1ff) > RIV_max (144)
[PHY][E]ERROR: Format 1A: rb_alloc (1ff) > RIV_max (144)
[MAC][I][eNB_dlsch_ulsch_scheduler] UE 0 rnti 5452: UL Failure after repeated PDCCH orders: Triggering RRC [RRC][I]Frame 330, Subframe 1: UE 5452 UL failure, activating timer MAC: remove UE 0 rnti 5452
[MAC][I][rrc_mac_remove_ue] Removing UE 0 from Primary CC_id 0 (rnti 5452)
[RRC][I]UE rnti 5452 failure timer 6940/20000
[RRC][I]UE rnti 5452 failure timer 17180/20000
[RRC][I]Removing UE 5452 instance
[RRC][W][eNB 0] Removing UE RNTI 5452 MAC: cannot remove UE rnti 5452
[MAC][W][rrc_mac_remove_ue] rrc_mac_remove_ue: UE 5452 not found
[S1AP][W][s1ap_ue_context_release_req] Failed to find ue context associated with eNB ue s1ap id: 0
[S1AP][E][s1ap_eNB_task] Failed to find ue context associated with eNB ue s1ap id: 0
[RRC][I][FRAME 00000][eNB][MOD 00][RNTI 5452] Removed UE context [INFO] L 4266779680 [INFO] L 4343611520
Can u please share us how did u solved this problemhttps://gitlab.eurecom.fr/oai1B/openairinterface5g/-/issues/49automatize UE network settings2017-08-29T16:52:25ZCédric Rouxcedric.roux@eurecom.frautomatize UE network settingsThere could be a command-line option to setup network:
- set IP address
- set route
- set DNS (/etc/resolv.conf)
This should be done in a separate thread, not the realtime one
(the IP setting is don;, at some point it was done in the r...There could be a command-line option to setup network:
- set IP address
- set route
- set DNS (/etc/resolv.conf)
This should be done in a separate thread, not the realtime one
(the IP setting is don;, at some point it was done in the realtime
thread, I don't know how it is as of today).https://gitlab.eurecom.fr/oai1B/openairinterface5g/-/issues/48add logs to UE_IP kernel module2017-08-29T16:52:25ZCédric Rouxcedric.roux@eurecom.fradd logs to UE_IP kernel moduleThe module calls kernel functions (like netif_rx) which return something (I did not analyse exactly what).
We should check the returned value to ease development/debugging.The module calls kernel functions (like netif_rx) which return something (I did not analyse exactly what).
We should check the returned value to ease development/debugging.https://gitlab.eurecom.fr/oai1B/openairinterface5g/-/issues/40Initial synchronization2017-08-29T16:52:25ZThomas Laurentlaurent.thomas@open-cells.comInitial synchronizationFrom my understanding of the file lte-ue.c
A main thread: UE_thread
always acquire I/Q from the RF board and keep it synchronous
This thread calls other threads to process the I/Q
In the case of this report, the UE is not yet synchrono...From my understanding of the file lte-ue.c
A main thread: UE_thread
always acquire I/Q from the RF board and keep it synchronous
This thread calls other threads to process the I/Q
In the case of this report, the UE is not yet synchronous with the serving eNB
So, the thread calls the dedicated thread to sync (with a full frame of I/Q samples)
Waiting the result, it continues to read frame per frame (and trash it), until it gets the result of the sync detection thread
When the result is done and positive, it shifts of the right number of I/Q the buffers to be sync with the eNB
A thread: UE_thread_synch try to decode the PBCH in a acquired full frame
But, this thread manipulate the RF board: it starts and stop it
So, the main thread acquisition become completely corruptedhttps://gitlab.eurecom.fr/oai1B/openairinterface5g/-/issues/39UE Periodic DL Throughput drop2017-08-29T16:52:25ZGhost UserUE Periodic DL Throughput dropUE periodic throughput drop on downlink (Band7 5MHz MCS28, --phy-test AND noS1 modes)
Period is about 490ms
**Version of OAI UE : v1B0.7**
**Frequency : each run**
**Configuration :**
* OAI UE : USRP B210
* OAI eNB : USRP B2...UE periodic throughput drop on downlink (Band7 5MHz MCS28, --phy-test AND noS1 modes)
Period is about 490ms
**Version of OAI UE : v1B0.7**
**Frequency : each run**
**Configuration :**
* OAI UE : USRP B210
* OAI eNB : USRP B210
**Attached files :**
* --phy-test
![UE_5MHz_MCS28_Throughput_phytest](/uploads/5018d273da86eccff9db7834cc4bcbde/UE_5MHz_MCS28_Throughput_phytest.png)
* noS1 (iperf)
![UE_5MHz_MCS28_Throughput_iperf](/uploads/3f54fe8bb377806dc833440180625f29/UE_5MHz_MCS28_Throughput_iperf.png)https://gitlab.eurecom.fr/oai1B/openairinterface5g/-/issues/38UE Segmentation Fault after EnodeB stopped first2017-08-29T16:52:25ZGhost UserUE Segmentation Fault after EnodeB stopped firstThis is a segmentation fault at UE when eNodeB stopped first after a RRC connection.
**Version of OAI UE : v1B0.7**
**Frequency : each run**
**Configuration**
* OAI UE : USRP B210
* OAI eNB : USRP B210
**Backtrace from gdb...This is a segmentation fault at UE when eNodeB stopped first after a RRC connection.
**Version of OAI UE : v1B0.7**
**Frequency : each run**
**Configuration**
* OAI UE : USRP B210
* OAI eNB : USRP B210
**Backtrace from gdb**
`Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffda4d7700 (LWP 3389)]
0x00007ffff6a01113 in ?? () from /usr/lib/x86_64-linux-gnu/libuhd.so.003
backtrace:
#0 0x00007ffff6a01113 in ?? () from /usr/lib/x86_64-linux-gnu/libuhd.so.003
No symbol table info available.
#1 0x00007fffdc46902a in trx_usrp_read (device=0x7ffff7edcc48, device@entry=<error reading variable: Cannot access memory at address 0xff5cfff5ff2b010e>, ptimestamp=0x7fffdc46902a <trx_usrp_read(openair0_device*, openair0_timestamp*, void**, int, int)+1226>, buff=0x1605ad00, nsamps=196612, cc=1) at /home/yanbo/openair5g/oai161201v1B0.7/openairinterface5g/targets/ARCH/USRP/USERSPACE/LIB/usrp_lib.cpp:262`https://gitlab.eurecom.fr/oai1B/openairinterface5g/-/issues/31eNB TDD mode Segmentation FAult2017-08-29T16:52:25ZROBERT BenoiteNB TDD mode Segmentation FAultThere is a segmentation fault at eNB start-up that prevent run it
#### Version of OAI eNB : v1B0.4
#### frequency : each run
#### configuration : see issue #27
#### backtrace from gdb
`
got sync (eNB_thread_single)
Program received sig...There is a segmentation fault at eNB start-up that prevent run it
#### Version of OAI eNB : v1B0.4
#### frequency : each run
#### configuration : see issue #27
#### backtrace from gdb
`
got sync (eNB_thread_single)
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffce43b700 (LWP 26645)]
trx_usrp_read (device=<optimized out>, ptimestamp=0x7ffff00c8020, buff=0x7fffce43ae10, nsamps=7680,
cc=1) at /tmp/oai_develop1B_tdd/openairinterface5g/targets/ARCH/USRP/USERSPACE/LIB/usrp_lib.cpp:270
270 ((__m256i *)buff[i])[j] = _mm256_srai_epi16(buff_tmp[i][j],4);
`https://gitlab.eurecom.fr/oai1B/openairinterface5g/-/issues/30eNB TDD mode configuration file error2020-10-30T14:27:17ZROBERT BenoiteNB TDD mode configuration file errorThere is a parsing error in config file : enb.band39.tm1.usrpb210.conf
#### Version of OAI eNB : v1B0.4
#### frequency : each run
#### configuration : see issue #27
#### extract from log file
`log init done
Set ULSCH_max_conse...There is a parsing error in config file : enb.band39.tm1.usrpb210.conf
#### Version of OAI eNB : v1B0.4
#### frequency : each run
#### configuration : see issue #27
#### extract from log file
`log init done
Set ULSCH_max_consecutive_errors = 10
num component carrier 1
WARNING: setting 'node_function' not found in configuration file
Assertion (0) failed!
In enb_config_init() /tmp/oai_develop1B_tdd/openairinterface5g/openair2/ENB_APP/enb_config.c:900
Failed to parse eNB configuration file /tmp/oai_develop1B_tdd/openairinterface5g/targets/PROJECTS/GENERIC-LTE-EPC/CONF/enb.band39.tm1.usrpb210.conf, Component Carrier 0!
`
please find as attached file a configuration file with new format
[enb.band39.tm1.usrpb210.syr.conf](/uploads/d423d1bc673b5de670b9b4abb941f76e/enb.band39.tm1.usrpb210.syr.conf)
@rohit.gupta : can you check configuration file for band 39https://gitlab.eurecom.fr/oai1B/openairinterface5g/-/issues/29UE not sending RRC connexion request in TDD mode2017-08-29T16:52:25ZROBERT BenoitUE not sending RRC connexion request in TDD modeWhen running UE in TDD mode, UE synchronize to the cell decode MIB Information but do not start RRC connexion procedure (see log below)
#### Version of OAI UE : v1B0.4
#### frequency : each run
#### configuration : see issue #27
...When running UE in TDD mode, UE synchronize to the cell decode MIB Information but do not start RRC connexion procedure (see log below)
#### Version of OAI UE : v1B0.4
#### frequency : each run
#### configuration : see issue #27
#### extract from log
`lte_parms.c: Setting N_RB_DL to 25, ofdm_symbol_size 512
[PHY][I][initial_sync] [UE0] In synch, rx_offset 63760 samples
[PHY][I][initial_sync] [UE0] Sending synch status to higher layers
[RRC][I][openair_rrc_ue_init] [FRAME 00000][ UE][MOD 00][RNTI 0] Init...
[RRC][I][openair_rrc_on] [FRAME 00000][ UE][MOD 00][RNTI 0] OPENAIR RRC IN....
pcfich_reg : 0,12,25,37
Ngroup_PHICH 1 (phich_config_common.phich_resource 1,phich_config_common.phich_duration normal, NidCell 0,Ncp 0, frame_type 1), smallest pcfich REG 0, n0 46, n1 75 (first PHICH REG 0)
phich_reg :0 => 1,17,33
[PHY][I][initial_sync] [UE 0] Frame 812 RRC Measurements => rssi -78.8 dBm (dig 46.2 dB, gain 125), N0 -129 dBm, rsrp -103.6 dBm/RE, rsrq 9.0 dB
[PHY][I][initial_sync] [UE 0] Frame 812 MIB Information => TDD, NORMAL, NidCell 0, N_RB_DL 25, PHICH DURATION 0, PHICH RESOURCE 1/6, TX_ANT 1
[PHY][I][initial_sync] [UE 0] Frame 812 Measured Carrier Frequency 1910003071 Hz (offset 0 Hz)
[HW][I][UE_thread_synch] Got synch: hw_slot_offset 16
[PHY][I][UE_thread] Resynchronizing RX by 63760 samples (mode = 0)
[PHY][I][ue_pbch_procedures] [UE 0] frame 814, subframe 0: Adjusting frame counter (PBCH ant_tx=1, frame_tx=815, phase 3, rx_offset 76798) => new frame 815`
--> missing RRC connexion procedure log here
`AUTOTEST Metric : UE_DLSCH_BITRATE = 0.00 kbps (frame = 900)
AUTOTEST Metric : UE_DLSCH_BITRATE = 0.00 kbps (frame = 900)
AUTOTEST Metric : UE_DLSCH_BITRATE = 0.00 kbps (frame = 900)
AUTOTEST Metric : UE_DLSCH_BITRATE = 0.00 kbps (frame = 900) `https://gitlab.eurecom.fr/oai1B/openairinterface5g/-/issues/28UE --phytest SegFault in TDD mode2017-08-29T16:52:25ZROBERT BenoitUE --phytest SegFault in TDD modeWhen running --pht-test mode on UE in TDD mode a SIGSEGV, Segmentation fault is raised just after the cell synch
#### Version of OAI UE : v1B0.4
#### frequency : each run
#### configuration : see issue #27
#### Backtrace from ...When running --pht-test mode on UE in TDD mode a SIGSEGV, Segmentation fault is raised just after the cell synch
#### Version of OAI UE : v1B0.4
#### frequency : each run
#### configuration : see issue #27
#### Backtrace from gdb
`phich_reg :0 => 1,17,33
[PHY][I][initial_sync] [UE 0] Frame 193 RRC Measurements => rssi -78.8 dBm (dig 46.2 dB, gain 125), N0 -107 dBm, rsrp -103.6 dBm/RE, rsrq 9.0 dB
[PHY][I][initial_sync] [UE 0] Frame 193 MIB Information => TDD, NORMAL, NidCell 0, N_RB_DL 25, PHICH DURATION 0, PHICH RESOURCE 1/6, TX_ANT 1
[PHY][I][initial_sync] [UE 0] Frame 193 Measured Carrier Frequency 1910003118 Hz (offset 0 Hz)
[HW][I][UE_thread_synch] Got synch: hw_slot_offset 16
[PHY][I][UE_thread] Resynchronizing RX by 65036 samples (mode = 0)
[PHY][I][ue_pbch_procedures] [UE 0] frame 195, subframe 0: Adjusting frame counter (PBCH ant_tx=1, frame_tx=196, phase 0, rx_offset 76798) => new frame 196
[PHY][E][subframe2harq_pid] subframe2_harq_pid, Illegal subframe 1 for TDD mode 3
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffdd67a700 (LWP 24687)]
0x000000000047cd97 in ue_ulsch_uespec_procedures (ue=ue@entry=0x7ffff7e9f010,
proc=proc@entry=0x7ffff7e9f1f8, eNB_id=eNB_id@entry=0 '\000',
abstraction_flag=abstraction_flag@entry=0 '\000')
at /tmp/oai_develop1B_tdd/openairinterface5g/openair1/SCHED/phy_procedures_lte_ue.c:1211
1211 if (ue->ulsch[eNB_id]->harq_processes[harq_pid]->subframe_scheduling_flag == 1) {`https://gitlab.eurecom.fr/oai1B/openairinterface5g/-/issues/27Feature UE TDD status2017-08-29T16:52:25ZROBERT BenoitFeature UE TDD status# UE TDD mode support
Since new scheduling from 'harmony' branch, TDD mode on UE is broken (reported by Wilson form ASTRI). This issue will collect status information and comparison on TDD mode for UE.
## related issues
- #28
...# UE TDD mode support
Since new scheduling from 'harmony' branch, TDD mode on UE is broken (reported by Wilson form ASTRI). This issue will collect status information and comparison on TDD mode for UE.
## related issues
- #28
- #29
- #30 (eNB related)
- #31 (eNB related)
## status report
OK: means functional but there are some stability and performances issues
#### UE Pre-harmony <> eNB Pre-harmony -> **Reference configuration for a functional noS1 TDD configuration**
- cell synchronization : OK
- phy-test Ok : [PHY][I][phy_procedures_UE_RX] Throughput 1584.0 kbps
- RRC connexion : OK
- ping test in both directions : OK but icmp packets lost
- iperf downlink : OK 1Mbps Rx for 2Mbps Tx
#### UE Post-harmony <> eNB Pre-harmony
- cell synchronization : OK (*[PHY][I][initial_sync] [UE 0] Frame 193 MIB Information => TDD, NORMAL, NidCell 0, N_RB_DL 25, PHICH DURATION 0, PHICH RESOURCE 1/6, TX_ANT 1*)
- phy-test Ok : NOK -> cell synch and SIGSEGV (issue #28 )
- RRC connexion : NOK -> cell synch but no RRC connexion request send to eNB (issue#29)
- ping test in both directions : INC -> not RRC connexion
- iperf downlink : INC -> not RRC connexion
#### UE Post-harmony <> eNB Post-harmony
OAI eNB is not running in TDD mode (so not much tests)
#30 : configuration file for band39 shall be updated for new OAI versions
#31 : eNB Segmentation Fault at stratup
## Test setup
- OAI UE : USRP B210
- OAI eNB : USRP B210
- RF link : 2 RF cables with 60dB Att on both links (uplink & downlink)
- uncomment openair1/SCHED/phy_procedures_lte_ue.c (~ line 3250) for printing PHY downlink Throughput
```
if ((frame_rx % 100 == 0)) {
LOG_I(PHY,"Throughput %5.1f kbps\n",(float) phy_vars_ue->bitrate[eNB_id]/1000.0);
}
```
### OAI Pre-harmony configuration
- OAI version : 23822ea203e00f2100fa41c7ee3084ec55b884fe
- eNB configuration
* git clone https://gitlab.eurecom.fr/oai/openairinterface5g.git
* cd openairinterface5g
* git checkout develop
* git checkout 23822ea203e00f2100fa41c7ee3084ec55b884fe
* source oaienv
* ./cmake_targets/build_oai -c -C -w USRP --eNB --noS1
* source ./cmake_targets/tools/init_nas_nos1 eNB
- UE configuration
* git clone https://gitlab.eurecom.fr/oai/openairinterface5g.git
* cd openairinterface5g
* git checkout develop
* git checkout 23822ea203e00f2100fa41c7ee3084ec55b884fe
* source oaienv
* ./cmake_targets/build_oai -c -C --UE -w USRP --noS1 --eNB
* source targets/bin/init_nas_nos1 UE
### OAI Post-harmony configuration
- OAI version : develop1B v1B0.4
- eNB configuration
* git clone https://gitlab.eurecom.fr/oai1B/openairinterface5g.git
* cd openairinterface5g
* git checkout v1B0.4
* source oaienv
* ./cmake_targets/build_oai -c -C -w USRP --eNB --noS1
* source ./cmake_targets/tools/init_nas_nos1 eNB
- UE configuration
- UE configuration
* git clone https://gitlab.eurecom.fr/oai1B/openairinterface5g.git
* cd openairinterface5g
* git checkout v1B0.4
* source oaienv
* ./cmake_targets/build_oai -c -C --UE -w USRP --noS1 --eNB
* source targets/bin/init_nas_nos1 UE
### Cmd lines for running tests
#### Cmd line UE for phy-test
`#> sudo ./cmake_targets/lte_noS1_build_oai/build/lte-softmodem-nos1 -U -C 1910000000 -r25 --ue-scan-carrier --ue-txgain 85 -A 20 --ue-rxgain 125 -S -T --phy-tes`t
#### Cmd line eNB for phy-test
`#> sudo ./cmake_targets/lte_noS1_build_oai/build/lte-softmodem-nos1 -O $OPENAIR_TARGETS/PROJECTS/GENERIC-LTE-EPC/CONF/enb.band39.tm1.usrpb210.conf --ulsch-max-errors 10 -m 27 --phy-test`
#### Cmd line UE for other
`#> sudo ./cmake_targets/lte_noS1_build_oai/build/lte-softmodem-nos1 -U -C 1910000000 -r25 --ue-scan-carrier --ue-txgain 85 -A 20 --ue-rxgain 125 -S -T`
#### Cmd line eNB for other
`#> sudo ./cmake_targets/lte_noS1_build_oai/build/lte-softmodem-nos1 -O $OPENAIR_TARGETS/PROJECTS/GENERIC-LTE-EPC/CONF/enb.band39.tm1.usrpb210.syr.conf --ulsch-max-errors 10 -m 19`https://gitlab.eurecom.fr/oai1B/openairinterface5g/-/issues/22Feature_UE_PDCPDiscard2017-08-29T16:52:25Zcalvin.wang18202157099@139.comFeature_UE_PDCPDiscardStabilization L2 PDCP discard featureStabilization L2 PDCP discard featureFeature UE L2calvin.wang18202157099@139.comcalvin.wang18202157099@139.com2016-11-30https://gitlab.eurecom.fr/oai1B/openairinterface5g/-/issues/21BugFix_UE_DRB2017-08-29T16:52:26Zcalvin.wang18202157099@139.comBugFix_UE_DRBUE DRB feature bug fixUE DRB feature bug fixFeature UE L2calvin.wang18202157099@139.comcalvin.wang18202157099@139.com2016-11-30https://gitlab.eurecom.fr/oai1B/openairinterface5g/-/issues/16Feature UE Paging2017-09-15T11:49:35ZGhost UserFeature UE PagingIssue for tracking test and integration of feature UE Paging delivered from develop branch wk40Issue for tracking test and integration of feature UE Paging delivered from develop branch wk40Feature UE Layer X2016-11-04https://gitlab.eurecom.fr/oai1B/openairinterface5g/-/issues/10Throughput drops to 02017-08-29T16:52:26ZGhost UserThroughput drops to 0From SYRTEM : In "--phy-test" mode, RX throughput drops to 0 (no more data traffic) on UE side. It does not happen regularly, as well after 25minutes as after 5hours. Note : After UE re-start, throughput stays unchanged from its last val...From SYRTEM : In "--phy-test" mode, RX throughput drops to 0 (no more data traffic) on UE side. It does not happen regularly, as well after 25minutes as after 5hours. Note : After UE re-start, throughput stays unchanged from its last value. After eNodeB re-start (and also UE re-start), throughput comes back to its maximum value.UE Robustnesshttps://gitlab.eurecom.fr/oai1B/openairinterface5g/-/issues/9Throughput not stable at MCS282017-08-29T16:52:26ZGhost UserThroughput not stable at MCS28From SYRTEM : Throughput is not stable at MCS28 (BW 5MHz) in "--phy-test" mode.From SYRTEM : Throughput is not stable at MCS28 (BW 5MHz) in "--phy-test" mode.UE Robustnesshttps://gitlab.eurecom.fr/oai1B/openairinterface5g/-/issues/7UE is removed by eNodeB because ULSCH consecutive error count is reached2017-08-29T16:52:26ZGhost UserUE is removed by eNodeB because ULSCH consecutive error count is reachedFrom SYRTEM : In "noS1" mode (BW 5MHz), UE is removed by eNodeB after 1 minute to 30 minutes because ULSCH consecutive error count is reached (eNodeB is running with "--ulsch-max-errors 10" in our tests).From SYRTEM : In "noS1" mode (BW 5MHz), UE is removed by eNodeB after 1 minute to 30 minutes because ULSCH consecutive error count is reached (eNodeB is running with "--ulsch-max-errors 10" in our tests).UE Robustnesshttps://gitlab.eurecom.fr/oai1B/openairinterface5g/-/issues/5Exit on "resource type 1 not supported for N_RB_DL=100"2017-08-29T16:52:26ZGhost UserExit on "resource type 1 not supported for N_RB_DL=100"From SYRTEM: In "--phy-test" mode (BW 10MHz), UE exists on "[conv_rballoc] resource type 1 not supported for N_RB_DL=100" (ie. N_RB_DL=50).From SYRTEM: In "--phy-test" mode (BW 10MHz), UE exists on "[conv_rballoc] resource type 1 not supported for N_RB_DL=100" (ie. N_RB_DL=50).UE Robustnesshttps://gitlab.eurecom.fr/oai1B/openairinterface5g/-/issues/3Real-Time scheduling - UE Thread maximum period until 15,1ms2017-08-29T16:52:26ZGhost UserReal-Time scheduling - UE Thread maximum period until 15,1msFrom F. Robinet, SYRTEM: The "UE_thread" period, that shall be 1ms, could reach 15,1ms. Note : lte-softmodem application can not capture error above 10ms of delay in reason of modulo implementation .From F. Robinet, SYRTEM: The "UE_thread" period, that shall be 1ms, could reach 15,1ms. Note : lte-softmodem application can not capture error above 10ms of delay in reason of modulo implementation .UE Robustness