[srslte-users] Pi 4 srsLTE

mark h markremington47 at gmail.com
Wed May 20 21:56:24 UTC 2020


SRS Users List,
I have been able to replicate Kenny's experiment using 2 Pi-4's and 2 Ettus
B210's. I have been seeing upload rates around 2-3 Mbps, Download around
500 Kbps. I have however been unable to get either the LimeUSB or LimeMini
to work on the UE side with the PI-4's. the Pi-4+B210 when running ue
consumes 3 cores around %75.

I have been able to make a good connection with the Limes using an Up^2
board (Intel® Celeron™ N3350 (up to 2.4 GHz) and Lime USB as both ENB and
UE, but it is far more unstable than the b210's. based upon my observations
it appears a faster processor is required to support the Limes especially
as UE. I have also been unable to utilize more than 15 resource blocks when
using the Limes.

My questions are:
Has anyone had good results with the lime SDR's as UE?
Does UE require a faster processor than ENB?

On Tue, May 12, 2020 at 1:59 PM Andre Puschmann <
andre.puschmann at softwareradiosystems.com> wrote:

> Hey Mark,
>
> thanks a lot for your input.
>
> On 12/5/20 17:54, mark h wrote:
> > Andre,
> > I feel there are two areas of documentation.
> >
> > 1: tested and working to be included in your documented use cases
> > "Application notes"
> >
> > 2: "In the works" More of a forum/COI (Community of Interest) that
> > others could comment and easily contribute to.
>
> I agree. Those two types are different and should be handled differently.
>
> >
> > Then we could use "in the works" to feed tested and working
> > configurations/documented use cases. I am not sure what the best
> > platform would be for the second part if that is a Wiki or what. How
> > would we create a guide and submit it to be included in the application
> > notes? I am still new to GIT and open source documentation.
>
> I don't think there is "the" approach to open source software
> documentation that fits all projects. What we currently use is the list
> we are currently on, Github issues, and docs.srslte.com. Other projects
> also use IRC, Slack, Matrix or similar tools.
>
> Wikis can be useful too. But, ultimately, they require someone who
> curates them in order to sustain that usefulness. Since the team behind
> srsLTE already maintains the three above mentioned means for user
> interaction and already spends significant resources in doing so, we
> won't be able to host such a Wiki ourselves.
>
> For content that has more tutorial character, documents a feature or
> provides general useful information we would suggest and encourage users
> to use Github pull-request feature to submit new or extend existing
> pages in the srsLTE docs repository. For content of type two a possible
> approach perhaps is to self-host a wiki or blog and inform the list
> about new articles or entries. Needless to say, that we are happy to
> promote useful content ourselves as well.
>
> Also, if there is content or topics that users would like to see covered
> in the docs, please don't hesitate to propose that here so we can
> plan and allocate resources to enlighten those dark corners.
>
>
> Thanks
> Andre
>
>
>
> >
> > Just my thoughts.
> >
> > On Tue, May 12, 2020 at 1:09 AM Andre Puschmann
> > <andre.puschmann at softwareradiosystems.com
> > <mailto:andre.puschmann at softwareradiosystems.com>> wrote:
> >
> >     Kenny, Mark, all,
> >
> >     first of all thanks for the digging into this. It looks really good.
> >
> >     On 11/5/20 21:57, mark h wrote:
> >     > Kenny,
> >     > I agree, and would be more than happy to help document getting
> >     srsLTE up
> >     > and running on Low-cost SBC's and SDR's. There has been a lot of
> >     > disaggregated work done and there are a LOT of emails to dig
> through.
> >
> >     Yes, I agree. Also there is quite some info on Github (closed issues)
> >     available that might also be useful for users.
> >
> >     >
> >     > Andre,
> >     > Would you be interested in a WIKI like Kenny suggest?
> >
> >     We are definitely interested in improving the user experience. In
> order
> >     to keep the work load manageable on our side, we would however
> prefer to
> >     use the existing mechanisms for documenting the project. The official
> >     srsLTE docs are publicly hosted [1] and we are happy to
> >     review/test/accept pull requests from our side. They are published
> under
> >     [2].
> >
> >     Maybe there is content that one could put inside a Wiki but that
> >     wouldn't fit into this "docs format". The "Running srsLTE on Pi4"
> >     walk-through, however, is amazing and would perfectly fit under the
> >     application notes in [3].
> >
> >     What are your thoughts on this?
> >
> >     Thanks
> >     Andre
> >
> >     [1] https://github.com/srsLTE/srsLTE_docs
> >     [2] https://docs.srslte.com/en/latest/
> >     [3] https://docs.srslte.com/en/latest/app_notes/source/index.html
> >
> >
> >
> >     >
> >     > On Mon, May 11, 2020 at 12:54 PM Kenneth Barlee
> >     > <kenneth.barlee at strath.ac.uk <mailto:kenneth.barlee at strath.ac.uk>
> >     <mailto:kenneth.barlee at strath.ac.uk
> >     <mailto:kenneth.barlee at strath.ac.uk>>> wrote:
> >     >
> >     >     Sorry, emails got a little out of sync here..____
> >     >
> >     >     ----____
> >     >
> >     >     Mark____
> >     >
> >     >     Sure, I tend to write a setup guide when I do this sort of
> thing.
> >     >     Copied below. It would be good if there was a
> community-editable
> >     >     wiki on the srsLTE git for people to share things like this!
> ____
> >     >
> >     >     Its been running for over 2 hours now with x2 phones attached
> and
> >     >     streaming live internet radio. B210 in 2x2, tm=2. CPU and
> memory
> >     >     utilization is not horrendous.____
> >     >
> >     >     cid:part1.4922EE7C.92DAB34B at strath.ac.uk____
> >     >
> >     >     __ __
> >     >
> >     >
> >     >         Pi4 Ubuntu image____
> >     >
> >     >
> >
> http://cdimage.ubuntu.com/releases/20.04/release/ubuntu-20.04-preinstalled-server-arm64+raspi.img.xz
> >     >
> >     >     ____
> >     >
> >     >
> >     >         UHD____
> >     >
> >     >     sudo add-apt-repository ppa:ettusresearch/uhd|____|
> >     >
> >     >     sudo apt-get update|____|
> >     >
> >     >     sudo apt-get install libuhd-dev libuhd3.15.0 uhd-host|____|
> >     >
> >     >     sudo /usr/lib/uhd/utils/uhd_images_downloader.py____
> >     >
> >     >     sudo uhd_usrp_probe____
> >     >
> >     >     __ __
> >     >
> >     >
> >     >         SoapySDR____
> >     >
> >     >     git clone https://github.com/pothosware/SoapySDR.git|____|
> >     <https://github.com/pothosware/SoapySDR.git%7C____%7C>
> >     >
> >     >     cd SoapySDR|____|
> >     >
> >     >     git checkout a489f3dca9d3ccd9b276b95a608ac3ef0299f635|____|
> >     >
> >     >     mkdir build && cd build|____|
> >     >
> >     >     cmake ..|____|
> >     >
> >     >     make|____|
> >     >
> >     >     sudo make install|____|
> >     >
> >     >     sudo ldconfig____
> >     >
> >     >     __ __
> >     >
> >     >
> >     >         LimeSuite____
> >     >
> >     >     sudo add-apt-repository -y ppa:myriadrf/drivers|____|
> >     >
> >     >     sudo apt-get update|____|
> >     >
> >     >     sudo apt-get install git g++ cmake libsqlite3-dev|____|
> >     >
> >     >     sudo apt-get install libi2c-dev libusb-1.0-0-dev____
> >     >
> >     >     __ __
> >     >
> >     >     git clone https://github.com/myriadrf/LimeSuite.git|____|
> >     <https://github.com/myriadrf/LimeSuite.git%7C____%7C>
> >     >
> >     >     cd LimeSuite|____|
> >     >
> >     >     mkdir build && cd build|____|
> >     >
> >     >     cmake ../|____|
> >     >
> >     >     make|____|
> >     >
> >     >     sudo make install|____|
> >     >
> >     >     sudo ldconfig____
> >     >
> >     >     __ __
> >     >
> >     >     cd ..|____|
> >     >
> >     >     cd udev-rules|____|
> >     >
> >     >     sudo ./install.sh____
> >     >
> >     >     __ __
> >     >
> >     >     LimeUtil --find|____|
> >     >
> >     >     LimeUtil --update|____|
> >     >
> >     >     SoapySDRUtil --find____
> >     >
> >     >     __ __
> >     >
> >     >
> >     >         srsLTE____
> >     >
> >     >     sudo apt-get install cmake libfftw3-dev libmbedtls-dev
> >     >     libboost-program-options-dev libconfig++-dev libsctp-dev____
> >     >
> >     >     git clone https://github.com/srsLTE/srsLTE.git|____|
> >     <https://github.com/srsLTE/srsLTE.git%7C____%7C>
> >     >
> >     >     cd srsLTE|____|
> >     >
> >     >     git checkout d045213fb9cbf98c83c06d7c17197a9dcbfddacf|____|
> >     >
> >     >     mkdir build &&  cd build|____|
> >     >
> >     >     cmake ../|____|
> >     >
> >     >     make|____|
> >     >
> >     >     sudo make install|____|
> >     >
> >     >     sudo ldconfig____
> >     >
> >     >     __ __
> >     >
> >     >     |sudo srslte_install_configs.sh user|____
> >     >
> >     >     __ __
> >     >
> >     >
> >     >         Run software / edit configs____
> >     >
> >     >     sudo nano /root/.config/srslte/enb.conf
> >     >     sudo nano /root/.config/srslte/epc.conf
> >     >     sudo nano /root/.config/srslte/ue.conf
> >     >     |s|udo nano /root/.config/srslte/user_db.csv
> >     >     sudo srsenb||sudo srsepc||sudo srsue____
> >     >
> >     >     # eNB conf:
> >     >     # device_name = UHD / soapy
> >     >     # device_args = auto < leave as is or it wont connect!
> >     >
> >     >
> >     >     ____
> >     >
> >     >
> >     >         Pi CPU____
> >     >
> >     >     sudo apt install linux-tools-common
> >     >     sudo apt install linux-tools-raspi
> >     >     sudo systemctl disable ondemand____
> >     >
> >     >     sudo nano /etc/default/cpufrequtils
> >     >     * GOVERNOR="performance"____
> >     >
> >     >     reboot____
> >     >
> >     >     sudo cpupower frequency-info
> >     >     sudo cat
> /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor____
> >     >
> >     >     __ __
> >     >
> >     >     __ __
> >     >
> >     >     __ __
> >     >
> >     >     __ __
> >     >
> >     >     On 11/05/2020 19:37, mark h wrote:____
> >     >
> >     >     Kenny,____
> >     >
> >     >     __ __
> >     >
> >     >     Great to hear that you got it working. I am beginning to
> wonder if
> >     >     part of the problem I am having is due to the SoapySDR driver
> >     >     combined with Limesuite. I have been using Soapy because UHD
> has a
> >     >     lot of overhead. I share your sentiment regarding hardware
> access,
> >     >     similar situation here where I have been home and have limited
> >     >     hardware, but I do have an ettus N210 on hand so I would like
> to
> >     >     give it a try. Would you mind sharing your Pi software
> >     >     build/versions so I can try to replicate your results? After
> >     seeing
> >     >     that the Pi is capable I am going to dive back into them. I
> >     will let
> >     >     you know how it goes when I try the LimeSDR with the UHD
> >     driver this
> >     >     afternoon.____
> >     >
> >     >     __ __
> >     >
> >     >     Take care____
> >     >
> >     >     Mark____
> >     >
> >     >     __ __
> >     >
> >     >     __ __
> >     >
> >     >     __ __
> >     >
> >     >     On Mon, May 11, 2020 at 11:02 AM Kenneth Barlee
> >     >     <kenneth.barlee at strath.ac.uk
> >     <mailto:kenneth.barlee at strath.ac.uk>
> >     <mailto:kenneth.barlee at strath.ac.uk
> >     <mailto:kenneth.barlee at strath.ac.uk>>>
> >     >     wrote:____
> >     >
> >     >     Hey Mark____
> >     >
> >     >     Good shout on the governor. Changing that to performance, I
> >     can run
> >     >     a 2x2 cell with the USRP B210 on the Pi4, and am now getting
> >     ~10Mbit
> >     >     downlink and ~3Mbit uplink (srsLTE v19.12). It seems to
> struggle
> >     >     with dynamic reconfiguration of resource blocks though, so if
> >     >     another UE appears it kills the first one - you have to toggle
> >     >     flight mode to get the two running happily.____
> >     >
> >     >     One of the things Pi people have been complaining about is
> >     that the
> >     >     USB3 bus on the Pi4 is not full USB3. Seems to be ok for the
> USRP
> >     >     though, which does point to the USB/Soapy/LimeSuite interface
> >     >     introducing too much latency. I don't have any other higher
> >     spec dev
> >     >     boards to hand, so can't really try anything else. There are
> some
> >     >     Intel STK1AW32SC compute sticks on my desk in the office, but I
> >     >     haven't been allowed into the office for over 2 months now!
> Quad
> >     >     core 1.92GHz/ 2GB RAM and USB3.1; so you never know, they may
> work
> >     >     well.____
> >     >
> >     >     I have just received a USRP E320 - may have a shot with that
> too.
> >     >     Not sure how it will cope though with running srsLTE as it has
> a
> >     >     lower spec CPU and less RAM than the Pi4! It does have a big
> >     FPGA to
> >     >     play with though... potential project in trying to split the
> >     PHY off
> >     >     and push it down onto the FPGA fabric. ____
> >     >
> >     >     Cheers____
> >     >
> >     >     Kenny____
> >     >
> >     >     __ __
> >     >
> >     >     __ __
> >     >
> >     >     *From:*mark h <markremington47 at gmail.com
> >     <mailto:markremington47 at gmail.com>
> >     >     <mailto:markremington47 at gmail.com
> >     <mailto:markremington47 at gmail.com>>>
> >     >     *Sent:* 11 May 2020 17:19
> >     >     *To:* Andre Puschmann
> >     <andre.puschmann at softwareradiosystems.com
> >     <mailto:andre.puschmann at softwareradiosystems.com>
> >     >     <mailto:andre.puschmann at softwareradiosystems.com
> >     <mailto:andre.puschmann at softwareradiosystems.com>>>
> >     >     *Cc:* Kenneth Barlee <kenneth.barlee at strath.ac.uk
> >     <mailto:kenneth.barlee at strath.ac.uk>
> >     >     <mailto:kenneth.barlee at strath.ac.uk
> >     <mailto:kenneth.barlee at strath.ac.uk>>>; srslte-users
> >     >     <srslte-users at lists.softwareradiosystems.com
> >     <mailto:srslte-users at lists.softwareradiosystems.com>
> >     >     <mailto:srslte-users at lists.softwareradiosystems.com
> >     <mailto:srslte-users at lists.softwareradiosystems.com>>>
> >     >     *Subject:* Re: [srslte-users] Pi 4 srsLTE____
> >     >
> >     >     __ __
> >     >
> >     >     Kenny,____
> >     >
> >     >     I have been trying to get SRSUE and ENB to run on Pi-4's and
> have
> >     >     been experiencing the same issue. When I moved to a faster SBC
> >     >     (UP^2) board I was able to get both ENB and UE to work with
> >     the same
> >     >     settings. If I had to guess I feel the latency on the Pi
> >     introduces
> >     >     timing issues and it cannot establish the scheduling
> >     connection. We
> >     >     are trying to compile a real-time Kernel to reduce the latency
> >     so we
> >     >     will see what happens.____
> >     >
> >     >     __ __
> >     >
> >     >     I have also been struggling to get higher bandwidths using the
> >     >     LimeUSB's with i7 and i5 laptops but get a real stable
> connection
> >     >     that runs for hours at 1-2 MBPS. one thing I have found is
> >     that the
> >     >     signal cleans up significantly when I put the governor in
> >     >     performance mode rather than on demand. I also no longer get
> late
> >     >     errors. I have attached a couple of images that show a change
> >     in the
> >     >     signal when the governor is changed. You can see the
> significant
> >     >     jump in SNR. I also see a bandwidth increase when running a
> IPERF3
> >     >     test. ____
> >     >
> >     >     __ __
> >     >
> >     >     Summery of things I have found got me closer:____
> >     >
> >     >     Cool and overclock the Pi____
> >     >
> >     >     Set cpu governor to "performance"____
> >     >
> >     >     Ensure the Pi has plenty of power____
> >     >
> >     >     power the LimeSDR externally____
> >     >
> >     >     Build SRSLTE and dependencies from source____
> >     >
> >     >     __ __
> >     >
> >     >     setup-1: Not working fails at the same point yours is but ENB
> >     signal
> >     >     looks good on the SPEC-AN____
> >     >
> >     >     Pi-4____
> >     >
> >     >     LimeUSB (on an externally powered USB)____
> >     >
> >     >     Raspian latest Distro____
> >     >
> >     >     __ __
> >     >
> >     >     Built from source:____
> >     >
> >     >     SRSLTE 20.04____
> >     >
> >     >     SoapySDR 0.7.01 (I had issues building the mos recent release
> they
> >     >     changed a variable type and SRSLTE no longer builds)____
> >     >
> >     >     LimeSuite 20.01____
> >     >
> >     >     __ __
> >     >
> >     >     Setup-2: working at Nprb=15____
> >     >
> >     >     Up^2 SBC____
> >     >
> >     >     LimeUSB (on an externally powered USB)____
> >     >
> >     >     ubuntu 18.04____
> >     >
> >     >     __ __
> >     >
> >     >     Built from source:____
> >     >
> >     >     SRSLTE 20.04____
> >     >
> >     >     SoapySDR 0.7.01 (I had issues building the mos recent release
> they
> >     >     changed a variable type and SRSLTE no longer builds)____
> >     >
> >     >     LimeSuite 20.01____
> >     >
> >     >       ____
> >     >
> >     >     __ __
> >     >
> >     >     Hope this helps.____
> >     >
> >     >     __ __
> >     >
> >     >     Mark____
> >     >
> >     >     __ __
> >     >
> >     >     __ __
> >     >
> >     >     __ __
> >     >
> >     >     On Wed, May 6, 2020 at 11:51 AM Andre Puschmann
> >     >     <andre.puschmann at softwareradiosystems.com
> >     <mailto:andre.puschmann at softwareradiosystems.com>
> >     >     <mailto:andre.puschmann at softwareradiosystems.com
> >     <mailto:andre.puschmann at softwareradiosystems.com>>> wrote:____
> >     >
> >     >         Kenneth,
> >     >
> >     >         frankly speaking we don't do much over-the-air testing
> >     ourselves
> >     >         with
> >     >         the Pi4. All success or failure stories so far have been
> from
> >     >         users on
> >     >         the list.
> >     >
> >     >         Anyway, we'll have a look into this over the next days.
> >     >
> >     >         Thanks
> >     >         Andre
> >     >
> >     >         On 6/5/20 15:49, Kenneth Barlee wrote:
> >     >         > Hey guys
> >     >         >
> >     >         > I have been having a play with a Pi 4B /4GB rev 1.2
> running
> >     >         the new
> >     >         > Ubuntu Pi Server 20.04 x64 image, and trying to get
> srsLTE
> >     >         working. I
> >     >         > know several others have been talking about trying this,
> but
> >     >         haven't
> >     >         > noticed my issue coming up elsewhere.
> >     >         >
> >     >         > I started with the latest versions of UHD, SoapySDR,
> >     >         LimeSuite, srsLTE
> >     >         > (commit ID e3e38482100f5bf13f15af3bc09df882e937bc60).
> >     Everything
> >     >         > compiles happily (no need to change those lines in
> >     >         CMakeLists.txt), and
> >     >         > the srsenb/srsepc software runs successfully (after an
> >     initial
> >     >         wait of
> >     >         > ~5 mins after first launch for any change in n_prb).
> >     However,
> >     >         no phone
> >     >         > is able to fully connect when using a USRP B210/
> >     LimeSDR-USB/
> >     >         > LimeSDR-Mini. It seems to start the attach, and there is
> >     a core
> >     >         > handshake, but the core reports that the "UE is not ECM
> >     >         connected" and
> >     >         > the UE never shows the signal bars.
> >     >         >
> >     >         > Decided to roll the Pi back to srsLTE v19.12, commit ID
> >     >         > d045213fb9cbf98c83c06d7c17197a9dcbfddacf, as I have been
> >     >         running this on
> >     >         > my desktop for a while now, and know it is stable.
> >     Again, this
> >     >         compiles
> >     >         > without issue. With this version, a phone will join a
> USRP
> >     >         B210 (not the
> >     >         > LimeSDRs, but that is probably another issue). It seems
> >     relatively
> >     >         > stable, and can continue running for several hours with a
> >     >         phone attached
> >     >         > running internet ping tests.
> >     >         >
> >     >         > I have attached logs and PCAPs for the two setups.
> >     >         >
> >     >         > A potentially related sidenote, with both srsenb
> >     versions, and all
> >     >         > radios, "SCHED: Could not transmit RAR within the window
> (RA
> >     >         TTI=2591,
> >     >         > Window=10, Now=2608)" type messages appear repeatedly in
> the
> >     >         terminal.
> >     >         > Running cellmapper on the phone, the LTE timing advance
> is
> >     >         estimated to
> >     >         > be '~250m' when using the USRP, but over '3.5km' with the
> >     >         LimeSDRs. This
> >     >         > is likely one of the reasons the LimeSDRs do not work
> with
> >     >         srsLTE v19.12.
> >     >         >
> >     >         > For reference, the UE used was a Samsung S20 Ultra 5G;
> >     LTE B3
> >     >         earfcn
> >     >         > 1934, n_prb=15, SISO tm=1 nof_ports = 1.
> >     >         >
> >     >         > Has anybody experienced similar? Happy to do more
> testing if
> >     >         it helps
> >     >         > with debugging!
> >     >         >
> >     >         > Thanks
> >     >         >
> >     >         >
> >     >         > Kenny Barlee | Research Associate
> >     >         > Software Defined Radio Research Laboratory
> >     >         > Department of Electronic and Electrical Engineering
> >     >         > University of Strathclyde
> >     >         >
> >     >         > _______________________________________________
> >     >         > srslte-users mailing list
> >     >         > srslte-users at lists.softwareradiosystems.com
> >     <mailto:srslte-users at lists.softwareradiosystems.com>
> >     >         <mailto:srslte-users at lists.softwareradiosystems.com
> >     <mailto:srslte-users at lists.softwareradiosystems.com>>
> >     >         >
> >     >
> >      http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
> >     <
> https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.softwareradiosystems.com%2Fmailman%2Flistinfo%2Fsrslte-users&data=02%7C01%7Ckenneth.barlee%40strath.ac.uk%7Cdce4540fc8864ebbe62d08d7f5c70421%7C631e0763153347eba5cd0457bee5944e%7C0%7C0%7C637248107424662945&sdata=LqFjpVkTAhHFdyHYlYumo2QX8QlJR4u%2Fj3sYUWu9llY%3D&reserved=0
> >
> >     >         >
> >     >
> >     >         _______________________________________________
> >     >         srslte-users mailing list
> >     >         srslte-users at lists.softwareradiosystems.com
> >     <mailto:srslte-users at lists.softwareradiosystems.com>
> >     >         <mailto:srslte-users at lists.softwareradiosystems.com
> >     <mailto:srslte-users at lists.softwareradiosystems.com>>
> >     >
> >      http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
> >     <
> https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.softwareradiosystems.com%2Fmailman%2Flistinfo%2Fsrslte-users&data=02%7C01%7Ckenneth.barlee%40strath.ac.uk%7Cdce4540fc8864ebbe62d08d7f5c70421%7C631e0763153347eba5cd0457bee5944e%7C0%7C0%7C637248107424672939&sdata=LmWWWjBg5jGROr5O6aYWfcZ%2BscuvXb3skmI3PgNPzqU%3D&reserved=0
> >____
> >     >
> >
> >
> >     --
> >     Andre Puschmann
> >
> >     Software Radio Systems (SRS)
> >     http://www.softwareradiosystems.com
> >
> >     PGP/GnuPG key: 6C42AB31
> >     fingerprint: 137A AE49 785B A445 257C 8AD7 D877 A498 6C42 AB31
> >
>
>
> --
> Andre Puschmann
>
> Software Radio Systems (SRS)
> http://www.softwareradiosystems.com
>
> PGP/GnuPG key: 6C42AB31
> fingerprint: 137A AE49 785B A445 257C 8AD7 D877 A498 6C42 AB31
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20200520/792fe87d/attachment.htm>


More information about the srsran-users mailing list