Skip to content
Failed

#284 (Oct 21, 2020, 1:11:43 PM)

Started 5 yr 4 mo ago
Took 8 min 2 sec on osmo-gsm-tester-prod
Build Artifacts
trial-284-bin.tgz96.94 MiB view
trial-284-run.tgz181.00 KiB view

Started by user Pau Espin Pedrol

Revision: fbb8611381c6572a282aeb785c5c48cb4cb16a04
Repository: https://gerrit.osmocom.org/osmo-gsm-tester
  • refs/remotes/origin/master
Tests (1 failure / +1)
enb-cells-2ca: fix config to match cell-id and cc idx

add comment explaining how the sceneario can be used.
also adopt cell IDs to match the CC index of the eNB.
This makes sure the cell_gain command of srsENB works with the config.

Change-Id: I1d14485df700ef3ba9220507f72c50b819d5e334
andre at
enb/ue: Assign zmq binding ports dynamically at runtime

ports are assigned increasingly in blocks in the range 2000-2200.

Change-Id: If2abddeb2ad6819de4f3ce64daaf00d2f527f9d2
Pau Espin Pedrol at
ms: Fix and use ms msisdn() getter

The getter method was named the same as the itnernal field, and hence
when used it would fail since the intenral field would be sleect and
fail to be called.

Change-Id: I2f631eb6256eb0e065f41d5b7531395c4a054cd8
Pau Espin Pedrol at
4g: Introduce ZMQ GnuRadio stream broker

srsENB currently creates 1 zmq stream (1 tx, 1 rx) for each cell (2 if
MIMO is enabled). Each cell transceives on a given EARFCN (and several
cells can transmit on same EARFCN).

However, for handover test purposes, we want to join all cells operating
on the same EARFCN to transceive on the same ZMQ conn, so that an srsUE
can interact with them at the same time (same as if the medium was shared).
Furthermore, we want to set different gains on each of those paths
before merging them in order to emulate RF conditions like handover.

In order to do so, a new element called the Broker is introduced, which
is placed in between ENBs and UEs ZMQ conenctions, multiplexing the
connections on the ENB side towards the UE side.

A separate process for the broker is run remotely (ENB run host) which
listens on a ctrl socket for commands. An internal Broker class is used
in osmo-gsm-tester to interact with the remote script, for instance to
configure the ports, start and stop the remote process, send commands to
it, etc.
On each ENB, when the rfemu "gnuradio_zmq" rfemu implementation is selected
in configuration, it will configure its zmq connections and the UE ones to
go over the Broker.

As a result, that means the UE zmq port configuration is expected to be
different than when no broker is in used, since there's the multiplexing
per EARFCN in between.

In this commit, only 1 ENB is supported, but multi-enb support is
planned in the future.

The handover test passes in the docker setup with this config:
"""
OSMO_GSM_TESTER_OPTS="-T -l dbg -s 4g:srsue-rftype@zmq+srsenb-rftype@zmq+" \
"mod-enb-nprb@6+mod-enb-ncells@2+mod-enb-cells-2ca+suite-4g@10,2+" \
"mod-enb-meas-enable -t =handover.py"
"""

and in resources.conf (or scenario), added:
"""
enb:
  ...
  cell_list:
    - dl_rfemu:
       type: gnuradio_zmq
    - dl_rfemu:
        type: gnuradio_zmq
"""

Note that since the broker is used, there's not need for mod-srsue-ncarriers@2
since the broker is joining the 2 enb cells into 1 stream on the UE side.

Change-Id: I6282cda400558dcb356276786d91e6388524c5b1
Pau Espin Pedrol at
ms: Allocate default msisdn internally

Don't wait until adding it to the subscriber data base, since the msisdn
may be needed beforehand (for instance in follow up patch to be passed
to osmo-msc configuration to route emergency calls).

Change-Id: I0d6902687e4beb3d6cdcefd4e343f21496100504
Pau Espin Pedrol at
sysmocom: Introduce suite to test emergency calls

Change-Id: I2e851c94311ded0abd4ff072b8cc72316d972750
Pau Espin Pedrol at
sysmocom: Enable emergency call testing in default-suites.conf

Change-Id: I9524ed9bc4f2d5f8e29313565400e90c64820988
Pau Espin Pedrol at
sysmocom: Introduce test to verify emergency call preemption

Change-Id: I59993e65b3fd34fb2c3e5b002ab9666db9b7bad5
Pau Espin Pedrol at
enb: add basic TDD config option

this patch adds the basic notion of FDD and TDD duplexing modes
to the eNB object. So far we've always assume FDD.

Since only Amarisoft eNB supports TDD, the required config
template changes, etc. are only applied there.

The patch also adds a scenario to enable the default TDD config.

Change-Id: I37216b5bfdf527d221913283b6c41d3c8fd6b500
Pau Espin Pedrol at
mod-enb-cell-2ca: fix EARFCN

this scenario for 2xCA needs to have both cells on different EARFCN

Change-Id: I3cd12da5453aa659839862775e23d4a308b92c8e
Pau Espin Pedrol at
rfemu_gnuradio_zmq: fix amplitude conversion

fix dB to amplitude conversion and adjust max attenuation value

Change-Id: I5a94d5d31e7dc85ab37bd281f95374ad825a41ff
Pau Espin Pedrol at
mod-gr-broker: add scenario to easily enable the GR broker

Change-Id: I4397e26713778721b7138b03b7a5f8f63f780d44
Pau Espin Pedrol at
intra-freq-ho{-sameport}.conf: add scenarios for intra-freq HO cells

we need to use two different configs for Amarisoft and srsENB.
Amarisoft combines the two cells and transmits them on the same
RF port, whereas srsENB sends them on a single port each.

Change-Id: I3a2a8ae7bf4ed2dab6efba8550f442a741ad92e0
Pau Espin Pedrol at
gnuradio zmq broker refactoring

First step towards support everal ENBs and installing the remote script
at runtime:

* The gnuradio broker class is moved to its own file, to decouple it
  from RFemu.
* The ENBs are registered earlier in the test so that the GrBroker knows
  when to start (delay start + setup until all ENBs have been configured).
* Handle ENBs internally as a list.

Change-Id: I4f1095bbc7ed0a816fe47caef44f7becadd9d737
Pau Espin Pedrol at
Changes in dependency
  1. osmo-gsm-tester_build-osmo-bsc  ? → (detail)
  2. osmo-gsm-tester_build-osmo-trx  ? → (detail)
  3. osmo-gsm-tester_build-osmo-mgw  ? → (detail)
  4. osmo-gsm-tester_build-osmo-ggsn  ? → (detail)
  5. osmo-gsm-tester_build-osmo-pcu-oc2g  ? → (detail)
  6. osmo-gsm-tester_build-osmo-stp  ? → (detail)
  7. osmo-gsm-tester_build-osmo-sgsn  ? → (detail)
  8. osmo-gsm-tester_build-osmocom-bb  ? → (detail)
  9. osmo-gsm-tester_build-osmo-pcu-sysmo  ? → (detail)
  10. osmo-gsm-tester_build-osmo-pcu  ? → (detail)
  11. osmo-gsm-tester_build-osmo-bts  ? → (detail)
  12. osmo-gsm-tester_build-osmo-hlr  ? → (detail)
  13. osmo-gsm-tester_build-osmo-bts-oc2g  ? → (detail)
  14. osmo-gsm-tester_build-osmo-msc  ? → (detail)
  15. osmo-gsm-tester_build-osmo-bts-sysmo  ? → (detail)