Project

General

Profile

Actions

Feature #4896

closed

gbproxy2: Routing of RIM messages

Added by laforge almost 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
12/08/2020
Due date:
% Done:

100%

Spec Reference:

Description

As we are just introducing RIM to osmo-pcu + osmo-sgsn, we also need to add RIM routing to osmo-gbproxy.

  • uplink messages can probably go to any SGSN (within the pool)
  • routing between BSS within the same proxy should be routed locally, not via the SGSN
  • downlink messages from any SGSN can be routed by destination cell-id

Related issues

Related to osmo-gbproxy - Feature #4472: Intra-domain connection of OsmoGBPROXY to multiple SGSNs (pooling)Resolveddaniel03/29/2020

Actions
Actions #1

Updated by laforge almost 2 years ago

  • Related to Feature #4472: Intra-domain connection of OsmoGBPROXY to multiple SGSNs (pooling) added
Actions #2

Updated by laforge almost 2 years ago

  • Status changed from New to Stalled

waiting for any RIM parsing/encoding code in libosmocore being worked on by dexter

Actions #3

Updated by laforge almost 2 years ago

  • % Done changed from 0 to 20

TTCN3 test for various RIM scenarios are in https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/22246

Actions #4

Updated by daniel almost 2 years ago

  • % Done changed from 20 to 40

There's incomplete support for RIM in

https://gerrit.osmocom.org/c/osmo-sgsn/+/22314

Actions #5

Updated by daniel almost 2 years ago

  • Status changed from Stalled to Resolved
  • % Done changed from 40 to 100

RIM routing has been implemented and is being tested in ttcn3

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)