[srslte-users] srsue crc ko when decoding PDSCH

César Augusto García Pérez garciacesaraugusto at lcc.uma.es
Fri Mar 18 10:40:22 UTC 2016


Hi Ismael,

Thank you very much, we have tried with different bandwidths (all the 
supported) and also in different bands (1, 3, 4, 7 , 13 and 20) we are 
now looking in signalling generated by the emulator.

I don't have many experience with the PHY and MAC layers, but analyzing 
the log I think that the BS is emitting the SIB2 with window length of 
20ms, a subframe offset of 15 but the periodicity that we have says rf16 
or rf32 (I don't know if this is the same periodicity that you 
mentioned). Anyway I still have to study if we can find a way of 
changing this parameters.

Regarding the interoperability the connection was with a cell of a 
commercial deployment of Yoigo (is a spanish operator, I think that they 
are currently using Ericsson). In our laboratory we have also tried with 
Pixie Small Cells (they were provided by Athena Wireless now part of 
Google) but we don't receive the SIB1 (indicates PDCCH errors), anyway 
we haven't dedicated a lot of time to this issue. In the following 
months we will be probably integrating with cells from other vendors, we 
will let you know any advances.

Best regards,
César
---
César Augusto García Pérez
Mobile Networks and Software Reliability Lab
Universidad de Málaga
http://morse.uma.es
Tel.: (+34) 9519 52965

El 17.03.2016 19:09, Ismael Gomez escribió:
> Hi Cesar, 
> 
> Apparently it decodes SIB1 successfully but not SIB2. Have you tried
> with different system BW? Can you change the SIB2 scheduling? There
> could be a bug in how the scheduling (or rv index for instance) is
> calculated, but I did the manual calculations and seems ok: 
> 
> It seems like SIB2 is scheduled with window 20 ms and period 8 frames.
> It looks like the eNodeB transmits SIB2 on subframe 15 of the window
> then according to 5.3.1 in 36.321 k=15 mod 4 = 1 and rv=ceil(3/2*k)
> mod 4 = 1. Am I right? 
> 
> Can you try with some different parameters and see if it works? Or can
> you tell from the eNodeB which is the real SIB2 scheduling and with
> which rv idx? 
> 
> Also, just out of curiosity, what commercial BS you have been able to
> connect to? You mean from real LTE commercial networks or in lab
> environment?
> 
> Thanks and best regards, 
> 
> Ismael 
> 
> On Thu, 17 Mar 2016 at 15:08 César Augusto García Pérez
> <garciacesaraugusto at lcc.uma.es> wrote:
> 
>> Hi,
>> 
>> First of all congratulations and thanks for the project, it is
>> really
>> cool.
>> 
>> I'm running some tests with srsUE over an USRP B210 connecting to
>> conformance equipment by Keysight
>> 
> (http://www.keysight.com/en/pd-2219656-pn-T4110S/lte-protocol-test-system?nid=-35141.1039393&cc=ES&lc=eng
>> [1] and
>> 
> http://www.home.agilent.com/agilent/campaign.jspx?cc=ES&lc=spa&ckey=2421060&id=2421060&cmpid=zzfinduxm
>> [2]) but I get an error after receiving the SIB1 message (I have
>> attached the traces):
>> 
>> 13:48:50.102 [PHY ] Info    [00175] PDSCH: l_crb= 3, harq=0,
>> tbs=32,
>> mcs=8, rv=1, crc=KO, snr=14.1 dB, n_iter=4, dec_time=  25 us
>> 
>> Any hints on what could be the problem? I am also trying with
>> commercial
>> BS by operators and it goes further (it get the SIB2 and sometimes
>> reach
>> RRC Connected).
>> 
>> Thank you very much, best regards,
>> César
>> 
>> --
>> César Augusto García Pérez
>> Mobile Networks and Software Reliability Lab
>> Universidad de Málaga
>> http://morse.uma.es [3]
>> Tel.: (+34) 9519
>> 52965_______________________________________________
>> srslte-users mailing list
>> srslte-users at lists.softwareradiosystems.com
>> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>> [4]
> 
> 
> Links:
> ------
> [1]
> http://www.keysight.com/en/pd-2219656-pn-T4110S/lte-protocol-test-system?nid=-35141.1039393&cc=ES&lc=eng
> [2]
> http://www.home.agilent.com/agilent/campaign.jspx?cc=ES&lc=spa&ckey=2421060&id=2421060&cmpid=zzfinduxm
> [3] http://morse.uma.es
> [4] http://www.softwareradiosystems.com/mailman/listinfo/srslte-users



More information about the srsran-users mailing list