Bug #4894
gbproxy2: Revisit information storage
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
Associated revisions
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
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
gbproxy: Copy RA-ID from BSS side BVC to CELL and SGSN-side BVC
Change-Id: I18669f269c4a959fcfa51885aafb719b662a7f8a
Related: OS#4894