Project

General

Profile

Bug #4895

gbproxy2: Implement small TLLI cache for SUSPEND/RESUME procedure

Added by laforge about 1 month ago. Updated 8 days 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)In Progress03/29/2020

History

#1 Updated by laforge about 1 month ago

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

#2 Updated by laforge about 1 month 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.

#3 Updated by daniel 8 days 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)

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)