Project

General

Profile

Feature #3778

Support CSFB "Fast Return"

Added by laforge 10 months ago. Updated 10 months ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
SGs Interface
Target version:
-
Start date:
02/03/2019
Due date:
% Done:

100%

Resolution:

Description

In order to help the MS/UE to return fast[er] to LTE, OsmoMSC should implement the following bit:

  1. The MSC sends the "CSFB indication" IE as part of BSSMAP CLEAR COMMAND on the A interface (see TS 48.008 3.2.2.121)

This will be used by the BSC to then trigger the inclusion of related IEs in the RR RELEASE


Checklist

  • CSFB indication in BSSMAP CLEAR CMD

Related issues

Related to OsmoBSC - Feature #3777: Support CSFB "Fast Return"Resolved02/02/2019

Related to OsmoMSC - Bug #3805: OsmoMSC sends invalid BSSMAP length field on CSFB CLEAR COMMANDResolved02/18/2019

History

#1 Updated by laforge 10 months ago

#2 Updated by laforge 10 months ago

  • Assignee set to dexter
  • Priority changed from Normal to High

Assigning this for dexter to implement as separate patch on top of his SGs patch/branch. OsmoBSC already has the implementation [pending master merge], see #3777.

#3 Updated by dexter 10 months ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 10

In order to support this, we first need to add the CSFB Indication IE to the BSSMAP CLEAR COMMAND:

https://gerrit.osmocom.org/#/c/libosmocore/+/12829 gsm0808: Add CSFB indication IE to BSSMAP CLEAR COMMAND

#4 Updated by dexter 10 months ago

We are about to merge the SGs Interface code, I have added the CSFB Indication IE within a separate patch:

https://gerrit.osmocom.org/#/c/osmo-msc/+/12830 a_iface: Include CSFB Indication into BSSMAP CLEAR COMMAND

#5 Updated by dexter 10 months ago

  • Checklist item CSFB indication in BSSMAP CLEAR CMD set to Done

#6 Updated by laforge 10 months ago

  • % Done changed from 10 to 70

Both libosmocore and omso-msc change have been merged. What's missing is testing it as part of our TTCN-3 testsuite.

#7 Updated by laforge 10 months ago

  • Status changed from In Progress to Stalled
  • Assignee changed from dexter to laforge

I've tried to create a TTCN-3 test for this, but it appears that TITAN doesn't correctly parse/decode the CSFB Indicator of the BSSMAP Clear Command. I've posted a related message to the TITAN forum: https://www.eclipse.org/forums/index.php/m/1802832

#8 Updated by laforge 10 months ago

My TTCN3 test modifications are in the laforge/msc-csfb-fast-return branch of osmo-ttcn3-hacks.git see http://git.osmocom.org/osmo-ttcn3-hacks/log/?h=laforge/msc-csfb-fast-return

Until the presumed TITAN bug is fixed, we cannot use that patch :/

#9 Updated by laforge 10 months ago

  • Related to Bug #3805: OsmoMSC sends invalid BSSMAP length field on CSFB CLEAR COMMAND added

#10 Updated by laforge 10 months ago

  • Status changed from Stalled to In Progress

As seen in #3805, the bug was ours, not one of TITAN.

I've pushed the extended TTCN-3 test as https://gerrit.osmocom.org/#/c/osmo-ttcn3-hacks/+/12935

#11 Updated by laforge 10 months ago

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

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)