Feature #3750
closedExtension of BTS_Tests.ttcn test coverage
100%
Description
Extension of the BTS Tests.ttcn test suite as well as its dependencies to extend the test coverage to cover the following scenarios, for which currently no automatic test coverage exists
Checklist
- RSL channel activation with timing advance from initial activation onwards.
- RSL MODE MODIFY with encryption parameter IE and/or multirate configuration IE.
- RSL DEACTIVATE slow associated control channel (“SACCH”)
- Handover Detection
- Mobile station (“MS”) Power Control
- Base station (“BS”) Power Control
- Common control channel (“CCCH”) LOAD INDICATION for random access channel (“RACH”)
- Cell broadcast channel (“CBCH”) LOAD INDICATION
- RF RESOURCE INDICATION
- Error handling, such as discriminator error, type error, sequence error, duplicated IE
- Packet control unit (“PCU”) interface
- SACCH INFO as part of RSL CHAN ACT
- SACCH transmission rules in the context of special CHAN ACT (HO)
Related issues
Updated by laforge almost 5 years ago
- Checklist item Error handling, such as discriminator error, type error, sequence error, duplicated IE set to Done
Tests related to error handling have been submitted in https://gerrit.osmocom.org/#/c/osmo-ttcn3-hacks/+/14086/
which triggered osmo-bts bug-fixes in https://gerrit.osmocom.org/#/c/osmo-bts/+/14083/, https://gerrit.osmocom.org/#/c/osmo-bts/+/14084/ and https://gerrit.osmocom.org/#/c/osmo-bts/+/14085/
Meanwhile, a related wireshark dissector bug has been discovered: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15789
Updated by laforge almost 5 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 10
Updated by laforge almost 5 years ago
- Checklist item SACCH INFO as part of RSL CHAN ACT added
https://gerrit.osmocom.org/#/c/osmo-ttcn3-hacks/+/14089/ for SACH INFO as part of RSL CHAN ACT. Testcase immediately found an error in osmo-bts which is fixed in https://gerrit.osmocom.org/#/c/osmo-bts/+/14087/
Updated by laforge almost 5 years ago
- Related to Bug #4008: Channel Activation starts SACCH too early in Asynchronous Handover added
Updated by laforge almost 5 years ago
- Related to Bug #4009: Channel Activation starts SACCH too early in Synchronous Handover added
Updated by laforge almost 5 years ago
- Related to Bug #4011: BTS_Tests.ttcn coverage for SMSCB/CBCH added
Updated by laforge almost 5 years ago
- Checklist item SACCH transmission rules in the context of special CHAN ACT (HO) set to Done
- % Done changed from 10 to 20
tests for SACCH related transmission rules on hand-over related channel activation in https://gerrit.osmocom.org/#/c/osmo-ttcn3-hacks/+/14094
Updated by laforge almost 5 years ago
- Checklist item Cell broadcast channel (“CBCH”) LOAD INDICATION set to Done
Updated by laforge almost 5 years ago
- Related to Bug #1622: OsmoBTS power control incompliant to TS 05.08 and TS 08.58 added
Updated by Hoernchen almost 5 years ago
- Checklist item RSL channel activation with timing advance from initial activation onwards. set to Done
Updated by laforge almost 5 years ago
- Checklist item Common control channel (“CCCH”) LOAD INDICATION for random access channel (“RACH”) set to Done
- % Done changed from 20 to 50
https://gerrit.osmocom.org/#/c/osmo-ttcn3-hacks/+/14169 contains tests for RACH load indications. There were several fixes required in osmo-bts in order to make it pass: https://gerrit.osmocom.org/14158, https://gerrit.osmocom.org/#/c/osmo-bts/+/14159/ and https://gerrit.osmocom.org/#/c/osmo-bts/+/14160/
The initial TA from RSL CHAN ACT has been implemented by Hoernchen in https://gerrit.osmocom.org/#/c/osmo-ttcn3-hacks/+/14151/
Updated by laforge almost 5 years ago
- Related to Bug #4023: Missing coverage of PCU interface in osmo-bts added
Updated by laforge almost 5 years ago
- Checklist item deleted (
TIME_IND from BTS → PCU) - Checklist item deleted (
DATA_IND from BTS → PCU) - Checklist item deleted (
PCU-originated DATA_REQ arrival on Um/MS side)
moving PCU related checlist items to #4023
Updated by Hoernchen almost 5 years ago
- Checklist item RSL MODE MODIFY with encryption parameter IE and/or multirate configuration IE. set to Done
- Checklist item RSL DEACTIVATE slow associated control channel (“SACCH”) set to Done
Updated by laforge almost 5 years ago
- Related to Bug #4031: OML part of BTS has no TTCN-3 tests added
Updated by laforge almost 5 years ago
- Related to Bug #4035: LAPDm implementation truncates L3 messages at 200 bytes added
Updated by laforge almost 5 years ago
- Checklist item Handover Detection set to Done
- % Done changed from 50 to 70
handover detection has been implemented in http://git.osmocom.org/osmo-ttcn3-hacks/commit/bts?id=7c2c10cbf0c837082040f80c463be97b729a7dda
Updated by Hoernchen almost 5 years ago
- Checklist item Mobile station (“MS”) Power Control set to Done
- % Done changed from 70 to 60
Updated by laforge almost 5 years ago
- Assignee changed from 4368 to Hoernchen
- Priority changed from Urgent to Normal
Updated by Hoernchen almost 5 years ago
- Checklist item Base station (“BS”) Power Control set to Done
Updated by Hoernchen almost 5 years ago
There is currently no reasonable way to test the RF RESOURCE INDICATION, osmo-bts does currently not use the parameters from TS 100 623 (9.4.24 Intave 9.4.25 Interference level Boundaries), and while osmo-trx can be polled for noise measurements those measurements are currently done by averaging 20 idle bursts, while intave is specified as average of # sacch frames (480ms), and even if all that was not the case it would still not be possible to test all of that without creating artificial noise to trigger a interference level change which in turn would trigger the sending of a RF RESOURCE INDICATION message.
Updated by Hoernchen almost 5 years ago
- Related to Feature #1569: Report RF interference levels as part of RF RESOURCE INDICATION added
Updated by fixeria over 4 years ago
There is currently no reasonable way to test the RF RESOURCE INDICATION [...]
Please see https://gerrit.osmocom.org/c/osmo-bts/+/15989. I believe this change would facilitate getting the actual (not averaged) interference levels. Since TRXDv1, OsmoTRX sends us IDLE indications (basically measurements during IDLE frames) and NOPE indications (when a burst was expected, but has not been received / detected).
[...] and even if all that was not the case it would still not be possible to test all of that without creating artificial noise to trigger a interference level change [...]
We can simulate pretty much everything with a virtual Um-interface - FakeTRX. The problem is that sending of IDLE / NOPE indications is still missing there :/ If I had time, I would implement this in a few days.
Updated by laforge over 4 years ago
- Status changed from In Progress to New
- Assignee deleted (
Hoernchen)
Updated by laforge almost 4 years ago
- Checklist item Packet control unit (“PCU”) interface set to Done
- % Done changed from 60 to 90
PCU socket is tested for most parts (and has a separate issue #4023).
So RF RESOURCE IND is the only untested message.
Updated by laforge almost 4 years ago
- Status changed from New to Resolved
marking as resolved; RF_RES_IND tests should be implemented in #1569
Updated by fixeria almost 3 years ago
- Checklist item RF RESOURCE INDICATION set to Done
- % Done changed from 90 to 100
For the sake of completeness:
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/24567 BTS: add a test case for RF RESource INDication [WIP]
The progress can be tracked in #1569.