Project

General

Profile

Actions

Bug #5277

open

ns2: Allow SNS-CONFIG PDUs from unknown endpoints during config procedure

Added by daniel over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
libosmogb
Target version:
-
Start date:
10/22/2021
Due date:
% Done:

0%

Spec Reference:

Description

Currently the SNS code expects SNS-CONFIG to happen between the primary EPs configured in the VTY.

NS2 with the following configuration

ns
 bind udp sgsn
  listen 10.0.0.2 2157
 nse 1
  ip-sns-remote 10.0.0.1 2157
  ip-sns-bind sgsn

would only handle SNS-CONFIG PDUs from the SGSN that originate from 10.0.0.1:2157

However, 3GPP TS 48.016 Ch. 6.2.5 states:

After completion on the BSS side of the Size procedure having indicated a reset, the BSS NSE shall send an SNS-CONFIG PDU to the same pre-configured SGSN IP endpoint used in the Size procedure.

NOTE: This does not imply that the SNS-CONFIG PDU has to be sent from the same IP endpoint used in the Size procedure

This also seems to apply to the SNS-CONFIG PDU sent from the SGSN to the BSS because some SGSNs send the SNS-CONFIG PDU alreads from the EP that is specified in that same PDU.
So it seems we need to relax our requirements and accept SNS-CONFIG PDUs from any source address as long as there exists an NSE with the NSEI specified in that PDU (on the bind that received the message).

No data to display

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)