Project

General

Profile

Actions

Feature #5927

closed

use "Direct TLLI" method to confirm IMMEDIATE ASSIGNMENT messages towards PCU

Added by dexter about 1 year ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
02/28/2023
Due date:
% Done:

100%

Spec Reference:

Description

To assign downlink TBFs, the PCU sends an IMMEDIATE ASSIGNMENT MAC block through the PCU SOCK interface to the BTS. The BTS confirms the sending of this IMMEDIATE ASSIGNMENT to the PCU by sending the MAC block back to the PCU. The MAC block essentially serves as a reference for the confirmation message. This method has some disadvantages so we decided to replace it.

The new method attaches a TLLI (and a paging group field) to the MAC block when it send to the BTS. The BTS then uses the TLLI instead of the MAC block as an identifier to confirm the sending of the IMMEDIATE ASSIGNMENT. The OsmoPCU already supports the method but OsmoBTS still have to be upgraded.

The related PCU/BTS TTCN3 tests also require an update.


Checklist

  • update TTCN3 tests for osmo-bts (stay compatible)
  • update osmo-bts
  • update TTCN3 tests for osmo-pcu to PCUIF v11
  • drop support for old PCUIF in osmo-pcu (final step)
  • get rid of unusued parameters in PCUIF_data_cnf_dt
  • rename tlli struct member to "msg_id"
  • add "confirm" struct member to struct gsm_pcu_if_pch_dt instead of parsing MAC blocks in osmo-bts/osmo-bsc
  • get rid of _DT/_dt and use _2/2 where it is required (same as with other APIs that get updated)
  • re-add compatibility for PCUIF v.10 to the TTCN3 tests of osmo PCU
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)