Intra-domain connection of OsmoPCU to multiple SGSNs
SGSN pooling is based on splitting the P-TMSI into two parts: A few bits that identify the SGSN in the pool (the so called NRI), and the remainder, which identifies the subscriber within the SGSN.
At time of first contact (random/foreign TLLI), there is a node selection function which chooses the SGSN to use for this request. All follow-up messages are then handled via this SGSN.
This feature would have to be implemented in OsmoPCU, alongside with corresponding test suite in TTCN-3.
Each PCU then has multiple Gb links; at least one to each of the SGSNs in the pool.
On Sun, Mar 29, 2020 at 07:15:37PM +0000, ipse [REDMINE] wrote:
It would be really nice if this feature could be implemented both in OsmoPCU and OsmoGbProxy at the same time - OsmoGbProxy is very helpful in practical installations.
I understand that, and obviously I want that more than anyone else.
The problem with pretty much all 'feature' tickets here is: Who is going to contribute related code /
developer time or funds :) It's not like we're seeing a lot of resources thrown at Osmocom...