SVI-STP SSME
Squire Technologies - Confidential Document
Page
27
of
57
4.4.2
Map Layer Routing
4.4.2.1
Overview
This aspect is generally looking at the MAP layer including MAP OPCode and the contents of some of
the MAP fields
All the MAP messages supported by the standard STP are supported in the tcap.opcode attribute of
the SCCP message.
It is also possible to use the regular expressions to set Map Layer Routing checking the contents of
some of the Map Attributes , again this format is the same as the standard SVI-STP TCAP label regular
expression matching
The following is supported
Map Operation Code (for MAP routing this can be set to the following options):
-
UpdateLocation
-
ProvideRoamingNumber
-
SendRoutingInfoForSM
-
MoForwardShortMsg
-
MtForwardShortMsg
-
AlertServiceCentre
-
AlertServiceCentreNoResult
-
ReportSMDeliveryStatus
-
AnytimeInterrogation
-
SendAuthenticationInfo
-
UpdateGprsLocation
-
MapProcessUnstructedRequest
4.4.2.2
Supported MAP Parameters
4.4.2.2.1
Update Location (2)
-
mscNumber
o
Address digits
-
mscNumber.addr=<digits>
o
Numbering plan
-
mscNumber.npi=<numbering plan>
o
Nature of Address
-
mscNumber.noa=<nature of address>
-
vlrNumber
o
Address digits
-
vlrNumber.addr=<digits>
o
Numbering plan
-
vlrNumber.npi=<numbering plan>
o
Nature of Address
-
vlrNumber.noa=<nature of address>
-
Imsi
o
Digits
-
imsi.digits=<digits>
4.4.2.2.2
ProvideRoamingNumber (3)
-
vlrNumber
o
Address digits
-
vlrNumber.addr=<digits>
o
Numbering plan
-
vlrNumber.npi=<numbering plan>
o
Nature of Address
-
vlrNumber.noa=<nature of address>
-