Project

General

Profile

Actions

Feature #4472

closed

Intra-domain connection of OsmoGBPROXY to multiple SGSNs (pooling)

Added by laforge over 2 years ago. Updated over 1 year ago.

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

100%

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.


Files

sgsn-pool.png View sgsn-pool.png 153 KB laforge, 11/04/2020 11:48 AM
bssgp-pdu-overview.gnumeric bssgp-pdu-overview.gnumeric 57.2 KB laforge, 12/06/2020 11:21 AM
bssgp-pdu-overview.png View bssgp-pdu-overview.png 278 KB laforge, 12/06/2020 11:22 AM

Checklist

  • per-BVC FSM for RESET/BLOCK/UNBLOCK
  • ability to configure multiple SGSN-side NSE in gbproxy
  • TTCN3 test case for RESET/BLOCK/UNBLOCK with two SGSNs in pool
  • NRI configuration in VTY
  • uplink message routing based on NRI extracted from TLLI
  • RADIO-STATUS
  • BVC FLOW CONTROL
  • RIM
  • MS-REGISTRATION-ENQUIRY
  • PS-PAGING-REJECT (requires ISMI cache)

Related issues

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

Actions
Related to osmo-gbproxy - Bug #4897: gbproxy2: Re-introduce handling of NS_AFF_CAUSE_FAILURENewdaniel12/08/2020

Actions
Related to osmo-gbproxy - Feature #4896: gbproxy2: Routing of RIM messagesResolved12/08/2020

Actions
Related to osmo-gbproxy - Bug #4895: gbproxy2: Implement small TLLI cache for SUSPEND/RESUME procedureResolveddaniel12/08/2020

Actions
Related to osmo-gbproxy - Bug #4894: gbproxy2: Revisit information storageResolveddaniel12/08/2020

Actions
Related to osmo-gbproxy - Feature #4893: gbproxy2: Make feature bitmap configurableNew12/08/2020

Actions
Related to osmo-gbproxy - Bug #4892: gbproxy2: Route BSSGP-STATUS based on "Erroneous PDU IE"Resolveddaniel12/08/2020

Actions
Related to osmo-gbproxy - Bug #4891: gbproxy2: Implement processing of BVC-Flow-Control via BVC FSMStalleddaniel12/08/2020

Actions
Related to osmo-gbproxy - Bug #4890: gbproxy2: VTY configuration of NRI / pool related bitsResolveddaniel12/08/2020

Actions
Related to osmo-gbproxy - Bug #4889: implement truncating of BSSGP STATUS when exceeding the FR MTUResolveddaniel12/06/2020

Actions
Related to osmo-gbproxy - Feature #4951: more TTCN3 tests for SGSN poolingIn Progressdaniel01/15/2021

Actions
Related to osmo-gbproxy - Bug #4954: Fix routing of RADIO-STATUS by TMSIResolveddaniel01/17/2021

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)