Project

General

Profile

Feature #4472

Intra-domain connection of OsmoPCU to multiple SGSNs

Added by laforge 2 months ago. Updated 2 months ago.

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

0%

Spec Reference:
TS 23.236 Section 5.3.2

Description

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.


Related issues

Related to OsmoBSC - Feature #3682: Intra-domain connection of OsmoBSC to multiple MSCsIn Progress11/06/2018

History

#1 Updated by laforge 2 months ago

  • Related to Feature #3682: Intra-domain connection of OsmoBSC to multiple MSCs added

#2 Updated by ipse 2 months ago

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.

#3 Updated by laforge 2 months ago

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...

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)