[srslte-users] Band 71 - Srslte

Tue Jul 9 09:19:37 UTC 2019

Hey Mathieu,

Try to add the extensions to the "cfg" at the srsenb rrc::init(). Something
like this:

  cfg.sib1.non_crit_ext_present = true;
>   cfg.sib1.non_crit_ext.late_non_crit_ext_present = true;
>   asn1::rrc::sib_type1_v8h0_ies_s ext_v8h0;
>   ext_v8h0.non_crit_ext_present = true;
>   ext_v8h0.non_crit_ext.freq_band_ind_v9e0_present = true;
>   ext_v8h0.non_crit_ext.freq_band_ind_v9e0 = 71;
>   srslte::unique_byte_buffer_t buffer =
> srslte::allocate_unique_buffer(*pool);
>   asn1::bit_ref bref(buffer->msg, buffer->get_tailroom());
>   ext_v8h0.pack(bref);
>   buffer->N_bytes = bref.distance_bytes();
>   cfg.sib1.non_crit_ext.late_non_crit_ext.resize(buffer->N_bytes);
>   memcpy(cfg.sib1.non_crit_ext.late_non_crit_ext.data(), buffer->msg,
> buffer->N_bytes);

I am not sure this is the cause for your problem, but may be worth
checking. If it doesn't work, you may try to take a look at MIB/SIB
messages that work with your UE when you use another eNB, and see if there
is any field that is missing in the srseNB. Maybe the srsue can help you
with the process.

Also, one minor thing, can you keep the srs mailing list in cc when you
answer my emails? Others might have similar issues.

Regards,
Francisco

On Mon, Jul 8, 2019 at 5:12 PM Mathieu Châteauvert <
mathieu.chateauvert at hotmail.com> wrote:

> Hi,
>
> I am looking for the first time at the rrc.cc file, and I was wondering
> how do I active the v9e0 flag. Do I need to go through the "rrc_asn1.h"
> file and put to "true" every v9e0 values associated and then recompile ?
>
> I am looking to help you and forward to achieve this. I am just looking
> for some guidance ahah.
>
> Thanks,
>
> Mathieu
>
> ------------------------------
> *De :* Francisco Paisana <francisco.paisana at softwareradiosystems.com>
> *Envoyé :* 8 juillet 2019 04:48
> *À :* Mathieu Châteauvert; srslte-users
> *Objet :* Re: [srslte-users] Band 71 - Srslte
>
> I am not sure what else needs to be changed. Maybe you have to activate
> the extension fields (v9e0) in the SIB1 for the phone to recognize the cell
> as "valid". Can you try to activate these flags in the enb rrc.cc
> "generate_sibs()" function and see if it works?
>
> On Mon, Jul 8, 2019 at 2:33 PM Mathieu Châteauvert <
> mathieu.chateauvert at hotmail.com> wrote:
>
> Hi,
>
> Thanks for the thorough answer about band 71. If it is not supported for
> now, that is ok.
>
> I actually can't get any cots ue (Iphone Xr, Pixel3) to connect to srslte
> enb when I set the frequency with dl_freq and ul_freq. The initial logs are
> the exact same as when I set trough dl_earfcn, but the phones can't see the
> network. The only difference between the files are (dl_freq, ul_freq) and
> (dl_earfcn). Do I need to change something else ?
>
> Thanks a lot,
>
> Mathieu
>
> ------------------------------
> *De :* Francisco Paisana <francisco.paisana at softwareradiosystems.com>
> *Envoyé :* 8 juillet 2019 01:46
> *À :* Mathieu Châteauvert
> *Cc :* Ralph A. Schmid, dk5ras;
> srslte-users at lists.softwareradiosystems.com
> *Objet :* Re: [srslte-users] Band 71 - Srslte
>
> Hey Mathieu,
>
> Regarding the change you made in the phy_common.cc, that error message
> tells that 71 is not a valid value for the freq band indicator. Looking at
> the TS 36.331, the SIB1 has a freqBandIndicator field of type
> "FreqBandIndicator". Also, in the same TS:
>
> FreqBandIndicator ::=  INTEGER (1..maxFBI)
> maxFBI                        INTEGER ::= 64 -- Maximum value of fequency
> band indicator
>
> So, 71 is not a supported value for that field (max is 64). To use 71, you
> probably have to use one of the SIB1 extensions (v9e0 I believe).
> Unfortunately, it seems srsLTE does not have this extension option being
> handled at the moment.
>
> Can you share the logs when you set the frequency manually? Also, are you
> changing the UL frequency accordingly?
>
> Regards,
> Francisco
>
>
> On Fri, Jul 5, 2019 at 8:42 PM Mathieu Châteauvert <
> mathieu.chateauvert at hotmail.com> wrote:
>
> Hi,
>
> Yes, when I set the direct frequency (634.5 MHz) with Srslte, the phone
> was not able to connect to srslte. With the same settings, the phone was
> able to connect to Amarisoft on the same exact frequency.
>
> When I added that band on the phy_common.c, the error :
>
> The condition lb <= n <= ub (1 <= 71 <= 64) was not met
> [/home/chateam/Documents/lte/srsLTE/lib/src/asn1/rrc_asn1.cc][20028]
> Encoding failure.
> [/home/chateam/Documents/lte/srsLTE/lib/src/asn1/rrc_asn1.cc][20328]
> Encoding failure.
> [/home/chateam/Documents/lte/srsLTE/lib/src/asn1/rrc_asn1.cc][20208]
> Encoding failure.
> [/home/chateam/Documents/lte/srsLTE/lib/src/asn1/rrc_asn1.cc][20358]
> Encoding failure.
>
> That is why I wonder if Band 71 is supported with srslte.
>
> Thanks,
> Mathieu
>
> ------------------------------
> *De :* Ralph A. Schmid, dk5ras <ralph at schmid.xxx>
> *Envoyé :* 4 juillet 2019 21:09
> *À :* 'Mathieu Châteauvert'; srslte-users at lists.softwareradiosystems.com
> *Objet :* RE: [srslte-users] Band 71 - Srslte
>
>
> Hi,
>
>
>
> Why not just using direct frequency entry, in MHz? Then any band should be
> possible...
>
>
>
> Ralph.
>
>
>
> *From:* srslte-users [mailto:
> srslte-users-bounces at lists.softwareradiosystems.com] *On Behalf Of *Mathieu
> Châteauvert
> *Sent:* Thursday, July 4, 2019 3:29 PM
> *To:* srslte-users at lists.softwareradiosystems.com
> *Subject:* [srslte-users] Band 71 - Srslte
>
>
>
> Hi,
>
>
>
> I wonder if Band 71 is supported in srsLte. It is using the 600Mhz to 700
> Mhz range.
>
>
>
> When trying to use it, we get the error that it is an invalid DL_EARFCN.
> In the phy_common.c file, it says that band 71 is " dummy band to bound
> band70 earfcn".
>
>
>
> Thanks,
>
>
>
> Mathieu
> _______________________________________________
> srslte-users mailing list
> srslte-users at lists.softwareradiosystems.com
> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20190709/c68019f3/attachment.htm>