this also removes the entire help text around arguments (that
were very outdated already) and only leaves the actual values with changes.
Change-Id: Icb9e8e7b1c68cf024db3a7273af791f017c32003
this allows, without changing the test case, to use a custom
template, which is useful for development. By default, nothing changes
and the OGT template is used
Change-Id: Ifc43ac41b16813116f2559da5223a6fecc186125
due to internal PDU buffering between PDCP/RLC the poll frequency
needs to be increase to get quicker feedback.
Change-Id: I4114fb36e675b3f91c471558f716276ab24f1db5
this patch adds generic support for custom frequency bands to the ms class.
it then extends the config template for AmariUE to use them.
we set the default values for EARFCNs for DL/UL to the old values.
Change-Id: I7b2250e13fc1161be1a1d73a4348f07b31c0f724
this config option overwrites the EARFCN config that is typically
used to tell the UE the bands to scan for cells. When custom
frequencies are used, this option allows to set them explicitly.
Change-Id: Ice070ea6755e273d916db2dc941068d33bbe206a
this allows to use the lteue to generate DL traffic. the
server listens on the default spgw address.
Change-Id: Iad081e57e2fd9d3cbc3e59e4f729a4721ad778c9
the UEs count param, if specified, is mapped into the config
values of the EPC so it can be used for template rendering.
Since we only have one count parameter, its added to the first
subscriber. 1 is the default value and its used when no count
param is specified.
this allows to run the Amarisoft UE simulator with the Amarisoft EPC
without having to create subscriber entries for each simulated UE.
Change-Id: I29885791f716c204d0b6f18ba134885bae853b6f
Despite open5gs allowing to change the GTP ports in the config file, in
reality changing those values to something else than the standard prot
will fail. Hence, we must use the standard port. As a result, we must
use different IP addresses in each process to avoid ip+port collisions.
Let's use some loopback addresses which shouldn't require extra
configuration on the host, and still only requiring 1 run_node as per
existing EPCs, with the limitation that only 1 open5gs EPC instance can
be run at one in a given run_node.
Related: https://github.com/open5gs/open5gs/issues/897
Change-Id: Id3062c6ad9d6de4c6066547e1e46edad5da285c1
when they are greater than 0 they are written as config paramter.
if they are -1 they are disbaled and automatic gain calibration is
used.
Change-Id: I473ff3ae679784178574d2f76b612dbf77180490
throughput tests require the UE object to have the num_carriers
member. For Android UEs, set it to 1 by default.
Change-Id: I297d24bb578a7db0eb7629be4f2cc0d54624467d
the ltesim_server is part of the UE package but needs to be executed
on the EPC run node. Therefore its handy to have the binary in the epc
trial tgz.
Change-Id: I21ac57d1c1547c1cf4d2394c8593f58ff2c78697
we've provided only all_log_level so far but sometimes it's needed
to select the level per layer. This patch adds the ability
to do so for the NAS layer in the UE.
Change-Id: Iab2bce65e8af81f6d344849c97952e6441cb2846
srsENB now supports PDCP discard so we set it to a sane value.
Also enable status reporting for UL.
Change-Id: Ib6ad0ff57b95a1f220f87c1ede0f6eacc5fb21ff
with many parallel jobs running on one machine we should
relax the timeout a bit to avoid false positives.
Change-Id: Ib32a07559bd5a4b0165f6d3431c5ac57cc050f44
we previously mixed component specific and component agnostic APIs
(stdout vs. log file for example) for setting and retrieving KPI.
This patch propose to use a single abstract get_kpis() method for
all components that can be enriched with component-specific
stuff as desired.
In the case of srsLTE blocks, the main implementation will
remain in srslte_common() and is shared among srsENB/srsUE/srsEPC.
The KPI analyzer in srslte_common() extract and also manages
all three KPI sources (log, csv and stdout) independently.
In addition to the get_kpis() method that always returns a flat
dictionary, it also exposes get_kpi_tree() that return
a dict of KPI dicts that will be used for the Junit.xml generation.
Change-Id: I4bacc6b8a0cb92a581edfb947100b57022265265
osmo-bts.git ae09c8acb4aa93284cdb44f8bbdc14533dc4fa52 modified code to
avoid calling pcu_tx_info_ind() if pcu socket was not connected. Since
osmo-gsm-tester relied on log message sent from within that funtion to
find out whether BTS was able to handle PCUIF connections, that log line
is not printed anymore and hence the function ready_for_pcu() fails to
ever return true.
As a result, gprs tests for sysmo and oc2g bts types always fail with a
timeout.
Other BTS types are not affected (such as osmo-bts-trx) because in there
we simply check whether the osmo-bts process is running.
Change-Id: Ibde4b8b27b8300b4b9197c0f8d82a6ccbf3b0522
we've detected a possible race condition during the Msg3
transmission that caused the thread that sets the Msg3 grant
to be delayed. The PHY worker that executed TTI+2 finished
by that time already and didn't even see the pending UL grant.
This is issue is more likely to happen on loaded system,
for example when running parallel ZMQ jobs. We therefore decided
to reduce the number of parallel PHY workers to 2 so the issue
is circumvented.
Change-Id: Ibdb42a1705d87b6d343201458c8fe397398802bc
we've already incrased the t3413 value in 9c7fd618d2
but realized it may still be too low in some cases.
we set it to 12s now.
Change-Id: I9c3c59c0ff8f539a44b420f8ba31eea016c211ce
Andre Puschmann
Pau Espin