Feature #1970
closed
separate SQN for CS and PS domain
Added by neels about 7 years ago.
Updated about 7 years ago.
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?
- 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.
- 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.
- Is duplicate of Feature #1969: add IND for proper UMTS auth resync added
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF
