Project

General

Profile

Feature #1970

separate SQN for CS and PS domain

Added by neels 17 days ago. Updated 4 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
03/07/2017
Due date:
% Done:

100%


Description

According to 3GPP TS 33.102, separate SQN ranges should be used for CS and PS domains.
Clarify what that means and whether the HLR needs to change its behavior, e.g. use only odd-numbered SQN for PS?
Require to be told via GSUP what domain the current request is for? Derive CS or PS otherwise?


Related issues

Duplicates OsmoHLR - Feature #1969: add IND for proper UMTS auth resync Resolved 03/07/2017

History

#1 Updated by neels 17 days ago

  • Status changed from New to Feedback
  • Assignee changed from neels to laforge

At least with the sysmoUSIM-SJS1, no such separation seems to be necessary.
There are 1024 SQN slots available (which practically means unlimited).
When the MSC and asks for 5 vectors, and then the SGSN asks for 5 vectors, all of those will work.
If one of MSC or SGSN goes far ahead of the other (beyond the 1024), an AUTS resync will be performed.
So the separation will come naturally from asking for more vectors.

I would resolve this if you agree.

#2 Updated by neels 10 days ago

  • Status changed from Feedback to In Progress
  • Assignee changed from laforge to neels

Above comment is ignorant of the implications of the SQN = SEQ || i scheme.
Indeed we need separate SQN for CS and PS, or in other words separate indexes per HLR client.

#3 Updated by neels 10 days ago

  • Duplicates Feature #1969: add IND for proper UMTS auth resync added

#4 Updated by neels 4 days ago

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

Also available in: Atom PDF