Difference between revisions of "Reset"

From ss7api.null.ro
Jump to: navigation, search
(Created page with "==Usage== This message is sent by a HLR that (re)starts after an outage to all VLRs or SGSNs to which subscribers were registered according to the data before the outage. ==...")
 
(Fixed structure for various MAP versions, commercial Yate Rev. 2507)
 
(One intermediate revision by one user not shown)
Line 1: Line 1:
 +
{{DISPLAYTITLE:reset}}
 
==Usage==
 
==Usage==
  
 
This message is sent by a HLR that (re)starts after an outage to all VLRs or SGSNs to which subscribers were registered according to the data before the outage.
 
This message is sent by a HLR that (re)starts after an outage to all VLRs or SGSNs to which subscribers were registered according to the data before the outage.
 +
  
 
==Invoke parameters==
 
==Invoke parameters==
  
* '''hlr-Number''' – HLR identification string / number
+
=== MAP v1 ===
 +
* '''networkResource''' - type of node generating the message, normally '''hlr'''
 +
* '''networkNode-Number''' - node identification number
 +
* ''hlr-List'' - optional list of '''HLR-Id''', each containing an IMSI prefix to which the reset applies
  
* <strike>''hlr-List''</strike> – Not supported
+
=== MAP v2 ===
 +
* '''hlr-Number''' – HLR identification number
 +
* ''hlr-List'' - optional list of '''HLR-Id''', each containing an IMSI prefix to which the reset applies
 +
 
 +
=== MAP v3 ===
 +
* '''sendingNodeNumber''' - choice of one of:
 +
** '''hlr-Number''' – HLR identification number
 +
** '''css-Number''' – CSS identification number
 +
* ''hlr-List'' - optional list of '''HLR-Id''', each containing an IMSI prefix to which the reset applies
 +
* <strike>''reset-Id-List''</strike> – Not supported
 +
* <strike>''subscriptionData''</strike> – Not supported
 +
* <strike>''subscriptionDataDeletion''</strike> – Not supported
 +
 
 +
 
 +
==Result==
 +
This operation is of class '''reportNone''' so no result or error is expected from the MAP layer.
 +
 
 +
It is possible to receive an error from the TCAP layer (dialog or component problem).
 +
 
 +
 
 +
==Examples==
 +
<component localCID=1" type="Invoke" operationCode="reset">
 +
<networkResource>hlr</networkResource>
 +
<networkNode-Number>4970100</networkNode-Number>
 +
</component>
  
==Example==
 
  
 
  <component localCID=1" type="Invoke" operationCode="reset">
 
  <component localCID=1" type="Invoke" operationCode="reset">
Line 15: Line 43:
 
  </component>
 
  </component>
  
==Reference==
 
  
 +
<component localCID=1" type="Invoke" operationCode="reset">
 +
<sendingNodeNumber>
 +
<hlr-Number>4970100</hlr-Number>
 +
</sendingNodeNumber>
 +
<hlr-List>
 +
<HLR-Id>00101</HLR-Id>
 +
<HLR-Id>00102</HLR-Id>
 +
</hlr-List>
 +
</component>
 +
 +
 +
==Reference==
 
* ETSI TS 100 974 V7.15.0 (2004-03) p1059
 
* ETSI TS 100 974 V7.15.0 (2004-03) p1059

Latest revision as of 16:54, 21 September 2020

Contents

[edit] Usage

This message is sent by a HLR that (re)starts after an outage to all VLRs or SGSNs to which subscribers were registered according to the data before the outage.


[edit] Invoke parameters

[edit] MAP v1

  • networkResource - type of node generating the message, normally hlr
  • networkNode-Number - node identification number
  • hlr-List - optional list of HLR-Id, each containing an IMSI prefix to which the reset applies

[edit] MAP v2

  • hlr-Number – HLR identification number
  • hlr-List - optional list of HLR-Id, each containing an IMSI prefix to which the reset applies

[edit] MAP v3

  • sendingNodeNumber - choice of one of:
    • hlr-Number – HLR identification number
    • css-Number – CSS identification number
  • hlr-List - optional list of HLR-Id, each containing an IMSI prefix to which the reset applies
  • reset-Id-List – Not supported
  • subscriptionData – Not supported
  • subscriptionDataDeletion – Not supported


[edit] Result

This operation is of class reportNone so no result or error is expected from the MAP layer.

It is possible to receive an error from the TCAP layer (dialog or component problem).


[edit] Examples

<component localCID=1" type="Invoke" operationCode="reset">
	<networkResource>hlr</networkResource>
	<networkNode-Number>4970100</networkNode-Number>
</component>


<component localCID=1" type="Invoke" operationCode="reset">
	<hlr-Number>4970100</hlr-Number>
</component>


<component localCID=1" type="Invoke" operationCode="reset">
	<sendingNodeNumber>
		<hlr-Number>4970100</hlr-Number>
	</sendingNodeNumber>
	<hlr-List>
		<HLR-Id>00101</HLR-Id>
		<HLR-Id>00102</HLR-Id>
	</hlr-List>
</component>


[edit] Reference

  • ETSI TS 100 974 V7.15.0 (2004-03) p1059
Personal tools
Namespaces

Variants
Actions
MAP & CAMEL XML Interface
Diameter XML Interface
MAP and CAMEL operations
Diameter interfaces
Examples
Resources
Navigation
Toolbox