Bug #1921
closed
osmo-gsm-manuals: Purge-MS operation doc error?
Added by neels over 7 years ago.
Updated over 4 years ago.
Description
In the GSUP docs, currently OsmoSGSN manual 13.4.5 Purge MS,
it looks like this is a GSUP message between two SGSNs,
but the ladder diagram shows SGSN <-> Network Peer (HLR).
Verify that this should be another SGSN and fix the diagram.
- Description updated (diff)
- Assignee set to 118
- Status changed from New to Feedback
I think the diagramm in our manual is definittly correct. A purge-ms message is sent by an SGSN or VLR to inform the HLR that there was no radio contact to the MS for some time. The HLR than sets the purged flag. The MS is then threaded as unreachable. The only way to recover from this state is a location update.
http://www.etsi.org/deliver/etsi_gts/03/0312/05.00.00_60/gsmts_0312v050000p.pdf (3.5.1.5 Mobile subscriber purging procedure)
With
"Using the Purge MS procedure, the SGSN can request purging of MS related state from a previous SGSN during an inter-SGSN
location update."
I am not sure. Purge MS between SGSN seems a bit odd to me.
On Mon, Feb 27, 2017 at 12:21:25PM +0000, dexter [REDMINE] wrote:
With
"Using the Purge MS procedure, the SGSN can request purging of MS
related state from a previous SGSN during an inter-SGSN location
update."
I am not sure. Purge MS between SGSN seems a bit odd to me.
This "purging of state from previous SGSN/VLR" is probably the "Cancel
Location" operation and not "Purge MS".
- Status changed from Feedback to New
- Assignee changed from 118 to neels
I'm still confused, would probably be good to discuss in person.
- Assignee changed from neels to daniel
- Status changed from New to Resolved
- Assignee changed from daniel to laforge
- % Done changed from 0 to 100
Also available in: Atom
PDF
