Bug #3099
closed
dynamic timeslots not tested by BSC_Tests.ttcn
Added by laforge about 6 years ago.
Updated about 6 years ago.
Description
we should have some test cases that test the various scenarios of dynamic timeslots (both IPA style and Osmocom style).
- Related to Bug #1853: validate dynamic TCH/PDCH support in osmo-bts-trx added
- Related to Bug #3131: dynamic timeslots not tested by BTS_Tests.ttcn added
- Related to Feature #1902: unify/refactor dynamic timeslot code added
- Related to Bug #1841: Dynamic PDCH / TCH switching assumes RSL link is up added
- Status changed from New to In Progress
- Assignee changed from 4368 to laforge
- % Done changed from 0 to 20
This is relatively difficult without infrastructural changes in RSL_Emulation.ttcn.
The reason is that, as soon as any TS is a dynamic PDCH, the BSC will send the PDCH activation command immediately upon RSL start-up. At this point, the related chan_nr is not yet (and cannot possibly be) registered with RSL_Emulation, and hence RSL_Emulation fails to dispatch it to the respective ConnHdlr.
Possible options are:
- suspend processing incoming RSL messages at RSL connection time until the testcase actively enables it, basically delaying the processing of the PDCH ACT messages until we've had a chance to register ConnHdlrs
- implement DYN PDCH tests without RSL_Emulation, instead directly on top of a RSL_CodecPort
- handle PDCH activation inside RSL_Emulation, similar to how we handle RSL CHAN ACT, keeping the state about the activation somewhere and permitting this state to be accessed via a procedure port.
- this has the disadvantage that we cannot easily simulate failure scenarios without modifying RSL_Emulation :(
- % Done changed from 20 to 80
- Status changed from In Progress to Resolved
- % Done changed from 80 to 100
Also available in: Atom
PDF