Project

General

Profile

Bug #4894

gbproxy2: Revisit information storage

Added by laforge 3 months ago. Updated 20 days ago.

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

0%

Spec Reference:

Description

We keep the RA in each BVC and in the CELL and in each BVC-FSM. Can we do better?


Related issues

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

Associated revisions

Revision ee0cc81a (diff)
Added by laforge 3 months ago

gbproxy: Copy RA-ID from BSS side BVC to CELL and SGSN-side BVC

Change-Id: I18669f269c4a959fcfa51885aafb719b662a7f8a
Related: OS#4894

Revision 55a22b8b (diff)
Added by dexter 18 days ago

gb_proxy_ctrl: use mcc-mnc-lac-rac notation instead mcc,mnc,lac,rac

The notation for the RAI used in the log is not compliant to the spec.

Change-Id: I6c8c3f3c017918fe847bfbcc153a12cf5f408bdb
Related: OS#4894

Revision da3af94b (diff)
Added by dexter 17 days ago

gb_proxy: simplify raid data storage

Instead of storing the raw ra_id in its unparsed binary form, store it
as a parsed struct. Also store the cell-id on cell allocation for later
use.

Change-Id: Ib58b9188e3ce4bd3fdadb03f158d56b29778387c
Related: OS#4894

History

#1 Updated by laforge 3 months ago

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

#2 Updated by daniel 23 days ago

Consolidated gbproxy_bvc and _cell storage here.

https://gerrit.osmocom.org/c/osmo-gbproxy/+/22653

This also stores the cell_id so we can route RIM

#3 Updated by laforge 20 days ago

  • Assignee changed from laforge to daniel

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)