Project

General

Profile

Actions

Bug #1921

closed

osmo-gsm-manuals: Purge-MS operation doc error?

Added by neels about 7 years ago. Updated over 4 years ago.

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

100%

Spec Reference:

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.

Actions #1

Updated by neels about 7 years ago

  • Description updated (diff)
  • Assignee set to 118
Actions #2

Updated by dexter about 7 years ago

  • 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.

Actions #3

Updated by laforge about 7 years ago

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".

Actions #4

Updated by laforge about 7 years ago

  • Status changed from Feedback to New
  • Assignee changed from 118 to neels
Actions #5

Updated by neels almost 7 years ago

I'm still confused, would probably be good to discuss in person.

Actions #6

Updated by laforge about 6 years ago

  • Assignee changed from neels to daniel
Actions #7

Updated by laforge over 4 years ago

  • Status changed from New to Resolved
  • Assignee changed from daniel to laforge
  • % Done changed from 0 to 100

taking this over after no feedback fro one year. Took about 15 mins to investigate and resolve. https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/16354

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)