Project

General

Profile

Actions

Bug #3099

closed

dynamic timeslots not tested by BSC_Tests.ttcn

Added by laforge almost 6 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
03/22/2018
Due date:
% Done:

100%

Spec Reference:

Description

we should have some test cases that test the various scenarios of dynamic timeslots (both IPA style and Osmocom style).


Related issues

Related to OsmoBTS - Bug #1853: validate dynamic TCH/PDCH support in osmo-bts-trxResolvedpespin11/18/2016

Actions
Related to OsmoBTS - Bug #3131: dynamic timeslots not tested by BTS_Tests.ttcnResolvedlaforge04/04/2018

Actions
Related to OsmoBTS - Feature #1902: unify/refactor dynamic timeslot codeNew01/05/2017

Actions
Related to OsmoBSC - Bug #1841: Dynamic PDCH / TCH switching assumes RSL link is upResolvedlaforge11/16/2016

Actions
Actions #1

Updated by laforge almost 6 years ago

  • Related to Bug #1853: validate dynamic TCH/PDCH support in osmo-bts-trx added
Actions #2

Updated by laforge almost 6 years ago

  • Related to Bug #3131: dynamic timeslots not tested by BTS_Tests.ttcn added
Actions #3

Updated by laforge almost 6 years ago

  • Related to Feature #1902: unify/refactor dynamic timeslot code added
Actions #4

Updated by laforge almost 6 years ago

  • Related to Bug #1841: Dynamic PDCH / TCH switching assumes RSL link is up added
Actions #5

Updated by laforge almost 6 years ago

  • Status changed from New to In Progress
  • Assignee changed from 4368 to laforge
  • % Done changed from 0 to 20
Actions #6

Updated by laforge almost 6 years ago

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 :(
Actions #7

Updated by laforge almost 6 years ago

  • % Done changed from 20 to 80

Initial 4 testcases in https://gerrit.osmocom.org/7664

I chose the option to "go without RSL_Emulation" and use RSL_CodecPort directly.

Actions #8

Updated by laforge almost 6 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 80 to 100

patch merged

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)