[srslte-users] Bug with PUSCH (Collision) in srsENB

[Kewin Rausch]

Hi all,
my two cents here.

I've just tested last version od srsLTE eNB software with 4 concurrent
commercial UE (Huawei P10 and Nexus 5) performing TCP/UDP iperf testing and
had no issues right now.

Cheers,
Kewin R.

On Thu, Nov 22, 2018 at 10:01 AM Ilshat Shaidullin <ilshat.desu at gmail.com>
wrote:

> Hello SRS Team,
>
> I've noticed strange behavior in srsENB. It occurs when I connect 2 UEs.
> I've attached log files (info level for phy, mac and rrc).
>
> Let the 1st UE be A and the 2nd UE be B.
> [FirstExample.log] I successfully connect A with rnti=0x46. Then I try to
> connect B with rnti=0x47. But after eNB sends RRCConnectionSetup all UL
> transmissions of B are always KO (though SNR is good). B can be
> successfully connected only with next rnti (0x48).
>
> [SecondExample.log] I successfully connect B with rnti=0x46. Then I
> successfully connect A with rnti=0x47. But as soon as A is connected,  B's
> UL transmissions are always KO (though SNR is good). So after some time B
> will perform RACH and connect with new rnti. Only after that B's UL
> transmissions will be OK.
>
>
> I think that in the examples above when eNB sends DCI Format 0 for B, A
> mistakenly uses it and performs UL transmission too. This may happen
> because C-RNTI values are close to each other. If I change C-RNTI
> allocation method ( replace "last_rnti++"  with "last_rnti += 10" in MAC )
> I don't observe this issue.
>
> What can cause such strange behavior?
>
>
> Best regards,
> Ilshat
> _______________________________________________
> srslte-users mailing list
> srslte-users at lists.softwareradiosystems.com
> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>

-- 
--
Le informazioni contenute nella presente comunicazione sono di natura 
privata e come tali sono da considerarsi riservate ed indirizzate 
esclusivamente ai destinatari indicati e per le finalità strettamente 
legate al relativo contenuto. Se avete ricevuto questo messaggio per 
errore, vi preghiamo di eliminarlo e di inviare una comunicazione 
all’indirizzo e-mail del mittente.

--
The information transmitted is 
intended only for the person or entity to which it is addressed and may 
contain confidential and/or privileged material. If you received this in 
error, please contact the sender and delete the material.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20181122/c1188025/attachment.htm>