Project

General

Profile

Feature #3373

Support for SNS auto-configuration (SIZE / SNS-CONFIG procedure)

Added by laforge 5 months ago. Updated 4 months ago.

Status:
Stalled
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
07/01/2018
Due date:
% Done:

60%

Spec Reference:

Description

3GPP TS 48.016 Section 6.2 specifies the "IP Sub-Network Service Protocol" (SNS), which can be used to auto-configure the NS-VCs and their IP addresses/ports between one NSE and the SGSN.

We don't implement this so far, as the spec states that this is an optional protocol and that NS-VCs may also be configured statically.

20180705-gprs-sns.pcap 20180705-gprs-sns.pcap 1.19 KB laforge, 07/05/2018 01:18 AM

Related issues

Related to OsmoPCU - Bug #3372: Support for SNS auto-configuration (SIZE / SNS-CONFIG procedure)In Progress2018-07-01

Related to libosmocore - Bug #3388: NS-RESET / NS-UNBLOCK / NS-BLOCK are not specified over IP/UDPNew2018-07-06

Related to libosmocore - Feature #3617: support routing control and user plane over different NS linksNew2018-10-02

History

#1 Updated by laforge 5 months ago

  • Related to Bug #3372: Support for SNS auto-configuration (SIZE / SNS-CONFIG procedure) added

#2 Updated by laforge 5 months ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 60

#3 Updated by laforge 5 months ago

there's an early/experimental implementation available in the laforge/gb-sns branches of libosmocore.git and osmo-pcu.git.

When running against PCU_Tests.ttcn from the laforge/gb-sns branch of osmo-ttcn3-hacks.git, it produces a full SNS handshake as can be seen in the attached pcap file.

The code needs some clean-up. The pre-existing libosmogb API doesn't really distinguish between NS-Entities (NSE) and NS-VirtualConnections (NSVC). In order to properly suppor this, the following sequence of events should be considered:

  • NS Instance with NS-Entity is created
  • SNS handshake is performed
  • NS-VCs are created from SNS handshake result
  • NS-RESET procedure is initiated for each NS-VC
Right now it's inverted:
  • NS Instance is created
  • NS-VC is created
  • SNS handshake is performed, result ignored
  • NS-RESET procedure is initiated

#4 Updated by laforge 5 months ago

  • Status changed from In Progress to Stalled

#5 Updated by laforge 5 months ago

  • Related to Bug #3388: NS-RESET / NS-UNBLOCK / NS-BLOCK are not specified over IP/UDP added

#6 Updated by laforge 4 months ago

#7 Updated by shawnjasper 4 months ago

#8 Updated by laforge 2 months ago

  • Related to Feature #3617: support routing control and user plane over different NS links added

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)