Project

General

Profile

Actions

Bug #2908

closed

OsmoMSC doesn't suppress duplicate L3 messages

Added by laforge about 6 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
-
Target version:
-
Start date:
02/03/2018
Due date:
% Done:

100%

Resolution:
Spec Reference:

Description

According to TS 24.007 Section 11.2.3.2.3, it is possible that uplink L3 messages are duplicated in some scenarios, particularly during assignment/handover procedure.

To avoid L3 entities from seeing duplicated messages, there's a modulo-2 or modulo-4 message sequence counter, baesd on which the MSC can detect and suppress such duplicate messages.

OsmoMSC doesn't contain any related code AFAICT.


Checklist

  • generate proper sequence number in ttcn-3 osmo-msc tests
Actions #1

Updated by laforge about 6 years ago

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

I have some related libosmocore and osmo-msc patches:

Daniel has implemented a related TTCN3 test case, not sure if it's yet in some brnach

Actions #2

Updated by laforge about 6 years ago

  • Checklist item generate proper sequence number in ttcn-3 osmo-msc tests added
  • % Done changed from 60 to 90

patch merged. TTCN-3 test cases in osmo-msc testsuite may need adaptation!

Actions #3

Updated by laforge about 6 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100

patch merged

Actions #4

Updated by daniel about 6 years ago

  • Checklist item generate proper sequence number in ttcn-3 osmo-msc tests set to Done
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)