Project

General

Profile

Actions

Bug #4895

closed

gbproxy2: Implement small TLLI cache for SUSPEND/RESUME procedure

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

Status:
Resolved
Priority:
High
Assignee:
Target version:
-
Start date:
12/08/2020
Due date:
% Done:

100%

Spec Reference:

Description

  • record a TLLI->BVC mapping in a global hashable on every SUSPEND/RESUME in uplink
  • look-up (and destroy) the hashtable entry on the response in SUSPEND/RESUME-ACK/NACK in downlink
  • have a timer to expire records after a few seconds in case there is no response

Related issues

Related to osmo-gbproxy - Feature #4472: Intra-domain connection of OsmoGBPROXY to multiple SGSNs (pooling)Resolveddaniel03/29/2020

Actions
Actions #1

Updated by laforge almost 2 years ago

  • Related to Feature #4472: Intra-domain connection of OsmoGBPROXY to multiple SGSNs (pooling) added
Actions #2

Updated by laforge almost 2 years ago

BSSGP spec states T3/T4 guard the SUSPEND/RESUME procedure, and they are both maxuimum 10s - so that's a good value to pick for the TLLI cache expiration.

Actions #3

Updated by daniel almost 2 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

This feature is implemented and suspend/resume tests are passing:
https://gerrit.osmocom.org/q/topic:%22tlli-cache%22+(status:open%20OR%20status:merged)

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)