Project

General

Profile

Feature #4010

Test RSL CHAN ACT related details for different scenarios

Added by laforge 28 days ago. Updated 26 days ago.

Status:
New
Priority:
Low
Assignee:
Category:
-
Target version:
-
Start date:
05/19/2019
Due date:
% Done:

0%

Spec Reference:

Description

As we have just seen in #4008 and #4009, there are subtle details that need to be handled correctly when performing RSL CHAN ACT in the following different cases:

  • Immediate Assignment
    • nothing really special here
  • Assignment (on same cell, different channel)
    • ensure that TA must be specified here (TA of old lchan)
  • Async / Sync Handover
    • Make sure we don't specify MS Power / TA to ensure SACCH is only transmitted after the Access Burst was received

We should have good test coverage for OsmoBSC in this area.


Related issues

Related to OsmoBTS - Bug #4008: Channel Activation starts SACCH too early in Asynchronous HandoverNew05/19/2019

Related to OsmoBTS - Bug #4009: Channel Activation starts SACCH too early in Synchronous HandoverNew05/19/2019

History

#1 Updated by laforge 28 days ago

  • Related to Bug #4008: Channel Activation starts SACCH too early in Asynchronous Handover added

#2 Updated by laforge 28 days ago

  • Related to Bug #4009: Channel Activation starts SACCH too early in Synchronous Handover added

#3 Updated by laforge 26 days ago

  • Priority changed from High to Low

re-prioritizing. Looking at the code in lchan_fsm_wait_activ_ack_onenter, it actually seems the BSC is doing this quite correctly for the four different activation types (immediate, normal, sync-ho and async-ho). Sure, that's no test. But I think given that OsmoBTS doesn't at all behave as required (see related issues), fixing the BTS is more important than writing BSC tests.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)