Hi all,
I was planning to do this long time ago, but somehow kept leaving this
for later. Today I revisited the state of ttcn3-bts-test, which shows
quite a few regressions. I believe they need to be investigated and
eventually fixed, so I created several tickets for tracking these
regressions in Osmocom's Redmine:
* OS#5951: TC_early_immediate_assignment,
* OS#5952: TC_ho_physical_info,
* OS#5953: TC_ms_pwr_ctrl_{constant,pf_ewma},
* OS#5954: TC_pcu_data_ind_lqual_cb,
* OS#5955: TC_pcu_[ext_]rach_content, TC_pcu_ptcch,
* OS#5956: TC_rsl_rf_resource_ind.
The following tickets already existed prior to my checkup:
* OS#4023: TC_pcu_oml_alert,
* OS#5242: TC_ipa_crcx_ack_addr,
* OS#5517: TC_tx_power_ramp_adm_state_change.
So far this is all about non-hopping configuration:
https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/lastCompl…
The freq. hopping configuration exhibits slightly more red TCs:
https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/lastCompl…
92% vs 84% passing TCs to be precise, but this is kinda expected because
of the limitations we have in fake_trx: FAKE_* CTRL commands are applied
to just one transceiver, not affecting others, which are also part of
the Mobile Allocation. Mostly the meas related TCs are affected.
The following TC groups are quite stable and mostly all green:
https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/lastCompl…https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/lastCompl…https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/lastCompl…https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/lastCompl…
The following two TC groups have never been stable/all green, AFAICT:
https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/lastCompl…https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/lastCompl…
We may want to create more tickets for those, maybe less granular (i.e.
one ticket per group). I am not familiar with these two TC groups, so
would be nice to get some input from those who write them. What would
it take to get them fixed? Are there any tickets already? If could not
find any, but I only did a quick search.
Best regards,
Vadim.
--
- Vadim Yanitskiy <vyanitskiy at sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
Dear Osmocom community,
we're happy to announce the next incarnation of OsmoDevCall.
when:
March 15, 2023 at 20:00 CET
where:
https://osmocom.org/OsmoDevCall (Big Blue Button)
This time, @laforge be presenting on
Long range communications in the HF band
CSD is the mechanism by which circuit-switched data calls can be made
over classic GSM/2G (and later also UMTS/3G) networks. They resembled
the modem call of circuit-switched networks, but of course no voiceband
modem is involved. For more information, see our CSD wiki page at
https://osmocom.org/projects/cellular-infrastructure/wiki/CSD
This meeting will have the following schedule:
20:00 meet + greet
20:10 presentation as outlined above
21:00 unstructured supplementary social event [*]
Attendance is free of charge and open to anyone with an interest
in Osmocom or open source cellular technologies.
More information about OsmoDevCall, including the schedule
for further upcoming events can be found at
https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall
Looking forward to meeting you soon!
Best regards,
Harald
[*] this is how we started to call the "unstructured" part of osmocom
developer conferences in the past, basically where anyone can talk about
anything, no formal schedule or structure.
--
- Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)