1. Manuals
  2. Brands
  3. Squire Manuals
  4. Gateway
  5. SVI STP SSME
  6. User manual

Squire SVI STP SSME User Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
SVI STP SSME User Guide
Document SQ-UG-019
Version 3.1
© Squire Technologies
This document is the property of Squire Technologies. Information contained herein is confidential. This document, either in whole or in
part, must not be reproduced or disclosed to others or used for purposes other than that for which it has been supplied, without Squire
Technologies prior written permission, or, if any part hereof is furnished by virtue of a contract with a third party, as expressly
authorised under that contract.
Page 1 of 57

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the SVI STP SSME and is the answer not in the manual?

Questions and answers

Summary of Contents for Squire SVI STP SSME

  • Page 1 This document is the property of Squire Technologies. Information contained herein is confidential. This document, either in whole or in part, must not be reproduced or disclosed to others or used for purposes other than that for which it has been supplied, without Squire Technologies prior written permission, or, if any part hereof is furnished by virtue of a contract with a third party, as expressly authorised under that contract.
  • Page 2 SVI-STP SSME Squire Technologies - Confidential Document Change History Version Change Made Author Authorised Date Document Created 2014 Document Updated 2017 Content Updated 08.11.2019 Images Updated 08.11.2019 Corporate formatting applied 12.11.2019 Removed Squire footer page. 12.11.2019 Spelling & Grammar checked 12.11.2019...

  • Page 3: Table Of Contents

    SVI-STP SSME Squire Technologies - Confidential Document Contents Introduction ........................5 References ........................ 5 Overview ........................6 Overview ........................6 SSME Overview ......................7 XML Overview ......................8 2.3.1 Profiles ......................8 2.3.2 Routing Criteria ....................8 2.3.3 Outbound Routing ....................8 2.3.4...
  • Page 4 SVI-STP SSME Squire Technologies - Confidential Document Overview ........................ 43 Global Title Translations ....................45 Overview ........................ 45 7.1.1 GTTMatch ......................46 Examples ........................ 47 7.2.1 Removing Leading Digits ..................47 7.2.2 Prefixing Digits ....................48 7.2.3 Replacing Leading Digits ..................48 7.2.4...

  • Page 5: Introduction

    SVI-STP SSME Squire Technologies - Confidential Document 1 Introduction The SSME is designed to allow a flexible configuration for the routing, translation and message manipulation for the STP:  It uses an XML format for the configuration with a published schema allowing validation of the XML before configuration ...

  • Page 6: Overview

    SVI-STP SSME Squire Technologies - Confidential Document 2 Overview 2.1 Overview The STP SSME on receipt of an incoming message attempts to be the following actions in order:  Determine whether there is a STP SSME configuration set against the incoming linkset.

  • Page 7: Ssme Overview

    SVI-STP SSME Squire Technologies - Confidential Document Message Recv Process Ssme Cfg for Std MTP Linkset? Routing SSME Routing Engine Discard Ssme Rtn Message Ignore Send UDTS if Ssme Rtn applicable Reject Ssme Rtn Translatio Route Forward Process Std MTP...

  • Page 8: Xml Overview

    Global Title Translations Global Title Translation For more details on the XML contents refer to the Squire Technologies STP SSME Syntax Reference 2.3.1 Profiles The XML elements used to select the list of entry points based on the linkset ...

  • Page 9: Global Title Translation

    SVI-STP SSME Squire Technologies - Confidential Document  Specifies a selection of routes that can be used Routeset 2.3.4 Global Title Translation The XML elements used for selecting an outbound route are as follows:  Defines a list of matches to be performed EntryPoint ...

  • Page 10: Profiles

    SVI-STP SSME Squire Technologies - Confidential Document 3 Profiles 3.1 Overview When a message is received by the SVI-STP the SSME engine from the linkset will determine the routing criteria profile which is then used to determine what the SSME will do with the message From the linkset the SSME will check the XML configuration and find a match against the <Linkset>...

  • Page 11: Linkset

    SVI-STP SSME Squire Technologies - Confidential Document Multiple profiles may be stored with in the same configuration file. 3.1.2 <Linkset> This element is used to either for incoming linksets, SUA AS or an API Server: Define a linkset profile using the profile attribute Or set-up a specific routing algorithm the same as the linkset profile There should be a linkset element for each linkset or SUA AS in the SVI-STP configuration.

  • Page 12: Entry Points

    SVI-STP SSME Squire Technologies - Confidential Document 4 Entry Points The <Ep> (EntryPoint) element is used the hub of the SSME, they are used as decision making engine and can also manipulate the incoming message updating elements of the incoming message.

  • Page 13: Overview

    SVI-STP SSME Squire Technologies - Confidential Document destination has been found but there are no routes available to that destination Example - Routing: Example - GT Translation 4.1 Overview An entry point on receipt of an incoming message will perform the following actions: ...

  • Page 14: Matching And Translation

    SVI-STP SSME Squire Technologies - Confidential Document 4.2 Matching and Translation A match is made with a Match element if all its attributes match the incoming address, if an attribute is not present then it is not required as part of the match Translations occur after the best match element has been selected;...

  • Page 15: Match

    SVI-STP SSME Squire Technologies - Confidential Document 4.2.1 <Match> This element is used to perform matches and translations throughout an <Ep>. The <Match> Element references all its attributes by the following Attribute Type Incoming Outgoing ic.mtp.<attr> og.mtp.<attr> SCCP ic.sccp.<attr> og.sccp.<attr>...

  • Page 16: Mtpmatch

    SVI-STP SSME Squire Technologies - Confidential Document </Match> In this case the OPC and DPC are not changed if DPC matches but the OPC fails to match Example – match incoming DPC 9987 translate to DPC 1234, and if OPC matches “1234” change to “2345”...

  • Page 17: Sccpmatch

    SVI-STP SSME Squire Technologies - Confidential Document 4.2.3 <SCCPMatch> The <SCCPMatch> Element references all its attributes by the following Attribute Type Incoming Outgoing ic.mtp.<attr> og.mtp.<attr> SCCP ic.sccp.<attr> og.sccp.<attr> <attr> TCAP tcap.operationCode map.routing_expr map.Translate map.cnts Examples Incoming MTP DPC ic.mtp.dpc Incoming SCCP Called Party Digits cdpn.digits...

  • Page 18: Gttmatch

    SVI-STP SSME Squire Technologies - Confidential Document </SCCPMatch> Example – match incoming SCCP Called Address Prefix 12345 or 456 for Map Operation Update Location <SCCPMatch tcap.opCode="Update Location"> <SCCPMatch cdpn.digits="12345" /> <SCCPMatch cdpn.digits="456" /> </SCCPMatch> 4.2.3.2 Translations Example – match incoming SCCP Called Address Prefix 12345 or 456 and Translation Type, update Translation Type <SCCPMatch...

  • Page 19: Nesting

    SVI-STP SSME Squire Technologies - Confidential Document <GTTMatch digits="12345" tt="10"/> 4.2.4.2 Translations The Translation of digits is performed in slightly different manner that the translation of other attributes, instead of replacing the whole digit string; it is required to state the new prefix and the...
  • Page 20 SVI-STP SSME Squire Technologies - Confidential Document As matches become more complicated and there are attempts to match and translate multiple attributes. Consider match all the elements of an SCCP Called on a single match element and different actions occur if the translation type is different...
  • Page 21 SVI-STP SSME Squire Technologies - Confidential Document With nesting <Ep name="at-tvltable"> <SCCPMatch cdpn.digits="0"> <SCCPMatch cdpn.digits="00"> <SCCPMatch cdpn.digits="000"> <SCCPMatch cdpn.digits="001"> <SCCPMatch cdpn.digits="002"> <SCCPMatch cdpn.digits="003"> <SCCPMatch cdpn.digits="004"> </SCCPMatch> </SCCPMatch> <SCCPMatch cdpn.digits="0"> <SCCPMatch cdpn.digits="01"> <SCCPMatch cdpn.digits="010"> <SCCPMatch cdpn.digits="011"> <SCCPMatch cdpn.digits="012"> <SCCPMatch cdpn.digits="013"> <SCCPMatch cdpn.digits="014">...

  • Page 22: Ordering Using First Match

    SVI-STP SSME Squire Technologies - Confidential Document <SCCPMatch cdpn.digits="992"> <SCCPMatch cdpn.digits="993"> <SCCPMatch cdpn.digits="994"> <SCCPMatch cdpn.digits="999"> </SCCPMatch> </SCCPMatch> </Ep> Again the performance is improved dramatically:  Without nesting to find any number would require 1000 attempted matches for each message ...

  • Page 23: Instructions

    SVI-STP SSME Squire Technologies - Confidential Document <MTPMatch dpc="2-185-30" pc_format="ansi888" route="2-185-30/24"/> <MTPMatch dpc="2-185-32" pc_format="ansi888" route="2-185-32/24" /> <MTPMatch dpc="2-185-45" pc_format="ansi888" route="2-185-45/24" /> <MTPMatch pc_format="ansi888" route="2-185-49/24" /> </MTPMatch/> </Ep> If the dpc “1-44-30” is the highest expected dpc to be received on an incoming message (with say 33%) of the traffic then each of the others have 5% of the expected traffic, all the rest is going to default then having “1-44-30”...

  • Page 24: Command

    SVI-STP SSME Squire Technologies - Confidential Document <Command jump="mxr-tt-0-routing" mode="Action"/> <Command jump="mxr-tt-0-post-conversion" mode="GttTranslation"/> </CommandList> All three commands in this list will be processed in turn so a Pre-Conversion will be performed of the Called Number then an attempt at the Routing will be performed if this returned a Route then the Post-Conversion will still be performed.

  • Page 25: Routing Types

    SVI-STP SSME Squire Technologies - Confidential Document 4.4 Routing Types The types of routing normally performed by the STP are as follows:  Screening – This is normally used to screen all the messages that the SVI-STP should reject/ignore before performing any other actions.
  • Page 26 SVI-STP SSME Squire Technologies - Confidential Document </SCCPMatch> <SCCPMatch cgpn.digits="974" action="Reject"/> <SCCPMatch cgpn.digits="975" cdpn.digits="4565" action="Reject"/> <SCCPMatch cdpn.digits="689" tcap.opCode="Update Location" action="Reject"/> </Ep> The above example shows the screening for the following: etsi-screening-mtp o Messages originating from MTP point code 6999 are ignored...

  • Page 27: Map Layer Routing

    SVI-STP SSME Squire Technologies - Confidential Document 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.
  • Page 28 SVI-STP SSME Squire Technologies - Confidential Document 4.4.2.2.3 SendRoutingInfoForSM (22) SCAddress o Address digits SCAddress.addr=<digits> o Numbering plan SCAddress.npi=<numbering plan> o Nature of Address SCAddress.noa=<nature of address> MSISDN o Address digits MSISDN.addr=<digits> o Numbering plan MSISDN.npi=<numbering plan> o Nature of Address MSISDN.noa=<nature of address>...
  • Page 29 SVI-STP SSME Squire Technologies - Confidential Document 4.4.2.2.6 AlertServiceCentre (64) / AlertServiceCentreNoResult (49)/ ReportSMDelivery (47) SCAddress o Address digits SCAddress.addr=<digits> o Numbering plan SCAddress.npi=<numbering plan> o Nature of Address SCAddress.noa=<nature of address> 4.4.2.2.7 AnytimeInterrogation (71) GsmSCF o Address digits GsmSCF.addr=<digits>...
  • Page 30 SVI-STP SSME Squire Technologies - Confidential Document ("MSISDN.addr=61[0-9]*"==True) Match an MSISDN not starting with digits 61 only ("MSISDN.addr=61[0-9]*"==False) imsi containing digits 901 ("imsi.digits=[0-9]*901[0-9]*"==True) imsi ending digits 222 ("imsi.digits=[0-9]*222*"==True) Ussd String starting with "This" ("UssdStr.decodedString=This*"==True) Ussd String starting with "This" and MSISDN starting with 55 (("UssdStr.decodedString=This*"==True) &amp;&amp;...
  • Page 31 SVI-STP SSME Squire Technologies - Confidential Document To add a default route for the rest of the SCCP attributes all that would need to be added is the following <Ep name="etsi-map-layer-routing"> <SCCPMatch cdpn.digits="6" tcap.opCode="Cancel Location" route="ETSI-Cancel-Location- route" /> <SCCPMatch cdpn.digits="7" tcap.opCode="Cancel Location" route="ETSI-Cancel-Location- route-2"...

  • Page 32: Map Layer Translations

    SVI-STP SSME Squire Technologies - Confidential Document 4.4.3 Map Layer Translations Map layer translations can be performed on incoming messages based on the map.cnts (map.routing_expr) attribute and the map.translate attribute. The following translations can be performed Map Operation Code (for MAP routing this can be set to the following options):...
  • Page 33 SVI-STP SSME Squire Technologies - Confidential Document SCAddress For AnytimeInterrogation the following options are available: GsmSCF For SendAuthenticationInfo the following options are available: imsi For UpdateGprsLocation the following options are available: imsi For ProcessUnstructedSSRequest the following options are available: MSISDN...
  • Page 34 SVI-STP SSME Squire Technologies - Confidential Document MSISDN=186442111 SCAddress=31221334 The outgoing parameters for the MO-SMS would be set as: MSISDN=2442111 SCAddress=831221334 Multiple Map translations are always comma separated. 4.4.3.2 Examples 4.4.3.2.1 Simple Translation To perform a simple translation for a message the following can be performed: <Ep...

  • Page 35: Global Title Routing

    SVI-STP SSME Squire Technologies - Confidential Document 4.4.4 Global Title Routing This type of routing is generally based on the SCCP attributes of a message such as the SCCP Cdpn digits, this type of routing will generally allow to determine which destination the message should go based on the SCCP attributes.

  • Page 36: Sccp Best Match Matrix

    SVI-STP SSME Squire Technologies - Confidential Document <MTPMatch dpc="1230" route="ETSI-ETSI-SP1-VIA-STP-TST-1-ONLY"/> </Ep> 4.4.5.2 MTP Routing – Match DPC – and update DPC and OPC To match the DPC only at MTP Routing and update the DPC and OPC <Ep name="etsi-global-title-routing"> <MTPMatch dpc="1230"...

  • Page 37: Route Selection

    SVI-STP SSME Squire Technologies - Confidential Document Match Current Match = Current Match has Both current and Current Match Current Best more digits in current best Match ic.sccp.cdpn.digits match have than current Best map.cnts Match Current Match = Current Match has...

  • Page 38: Routeset

    SVI-STP SSME Squire Technologies - Confidential Document The processing occurs in the following manner:  If a Routeset child element exists then find the highest priority routes within the routeset, check the availability of each of this routes. If only a single route of this priority exists then send the message on this route.

  • Page 39: Route Selection

    SVI-STP SSME Squire Technologies - Confidential Document If a point code is specified in the destination attribute then the SSME will automatically send to this destination as long as the linkset is available. The linkset must be a named destination.

  • Page 40: Complex Routing Example

    SVI-STP SSME Squire Technologies - Confidential Document This would then be routed to destination “1-3-1” with the DPC set to “2073”, the pc_format field informs the SSME whether it is ANSI/ETSI This would then need to be configured in the MTP routing to give a linkset for the destination <Ep...
  • Page 41 SVI-STP SSME Squire Technologies - Confidential Document <RouteEp name="Route-1"> <Routeset> <Route destination="SP1-ETSI" priority="1" weight="1" linkset="STP0-STP-TST-1- ETSI"/> <Route destination="SP1-ETSI" priority="2" weight="1" linkset="STP0-STP-TST-2- ETSI"/> </Routeset> </RouteEp> 5.4.2.2 Loadsharing This is done using the RouteEp Element which is selected via the match shown above, the RouteEp for simple loadsharing would be as follows: <RouteEp...
  • Page 42 SVI-STP SSME Squire Technologies - Confidential Document <RouteEp name="Route-1"> <Routeset> <Route destination="SP1-ETSI" priority="1" weight="1" linkset="STP0-STP-TST-1- ETSI"/> <Route destination="SP2-ETSI" priority="1" weight="1" linkset="STP0-STP-TST-2- ETSI"/> <Route destination="SP3-ETSI" priority="2" weight="4" linkset="STP0-STP-TST-1- ETSI"/> <Route destination="SP4-ETSI" priority="2" weight="2" linkset="STP0-STP-TST-3- ETSI"/> <Route destination="SP1-ETSI" priority="3" weight="1" linkset="STP0-STP-TST-4- ETSI"/>...

  • Page 43: Api Server

    SVI-STP SSME Squire Technologies - Confidential Document 6 API Server 6.1 Overview The STP SSME is capable of routing messages to an external API for examination and routing decision based on the XML configuration. (See section 9 for details of the Python SDK) The attribute apiserver in the <route>...
  • Page 44 SVI-STP SSME Squire Technologies - Confidential Document o The API server for example is checking the MSISDN contained in the Send Routing Info and either return a message LS-ETSI-OPC-8000-DPC-7100 (if the SCCP Called address matches) or LS-ETSI-OPC-8000-DPC-7200 if the Map operating is “Send Routing Info”...

  • Page 45: Global Title Translations

    SVI-STP SSME Squire Technologies - Confidential Document 7 Global Title Translations The global title translations are configured by a Linkset/LinksetProfile Element attribute for all messages received on that linkset. Within the Global Title Translations entry points there are CommandLists that will discriminate message based on the incoming DPC and the outgoing OPC.

  • Page 46: Gttmatch

    SVI-STP SSME Squire Technologies - Confidential Document The Elements used for GT Translations are:  EntryPoint  CommandList  Command  GTTMatch 7.1.1 GTTMatch The Global Title Translation Match Elements will either be present as a sub-element of a Command Node or as a sub-element of an EntryPoint Node pointed to the Command Node attribute “jump”.

  • Page 47: Examples

    SVI-STP SSME Squire Technologies - Confidential Document 7.2 Examples Global Title Translation can occur during the Routing Criteria as first instance, or more often once the route has been selected It is always part of an entry point element and should be set up as follows: <Ep...

  • Page 48: Prefixing Digits

    SVI-STP SSME Squire Technologies - Confidential Document 7.2.2 Prefixing Digits A simple example showing the prefixing number starting 443 with 74 <Ep name="Etsi-Translation-1"> <GTTMatch digits="443" og.prefixDigits="74"/> </Ep> 7.2.3 Replacing Leading Digits A simple example showing the prefixing number replacing 443 with 74 <Ep...

  • Page 49: Debug

    SVI-STP SSME Squire Technologies - Confidential Document 8 Debug 8.1 Description From version 15.8.0 onwards of the svi-stp process, it is now possible to only print debug for specific messages which are received by the STP-SSME-XML engine. The debug profile to use is set on the Linkset element.

  • Page 50: Internal Testing

    SVI-STP SSME Squire Technologies - Confidential Document 9 Internal Testing 9.1 Description In the XML it is possible to create a set of tests to be run against the configuration at point of validation. The XSD defines an element called Test. This is used to create an internal test to be run when the SVI-STP loads a new XML file.
  • Page 51 SVI-STP SSME Squire Technologies - Confidential Document If any of the Output does not match the ExpectedOutput then the test will fail. Other sub-elements include: DestinationOOS which sets the destination to be considered out of service for the test LinksetOOS which sets the linkset to be considered out of service for the test...
  • Page 52 SVI-STP SSME Squire Technologies - Confidential Document For example testing the following endpoint <Ep id="instance-3-gtt-selector-3E164" name="instance-3-gtt-selector-3E164"> <SCCPMatch firstMatch="true"> <SCCPMatch cdpn.digits="0"> <SCCPMatch cdpn.digits="06"> <SCCPMatch cdpn.digits="069"> <SCCPMatch cdpn.digits="0690" destination="11500" id="instance-3-gtt-selector-sm-186" og.sccp.cdpn.ri="RouteOnGT"/> <SCCPMatch cdpn.digits="0694" destination="11500" id="instance-3-gtt-selector-sm-187" og.sccp.cdpn.ri="RouteOnGT"/> <SCCPMatch cdpn.digits="0696" destination="11500" id="instance-3-gtt-selector-sm-188" og.sccp.cdpn.ri="RouteOnGT"/> </SCCPMatch>...

  • Page 53: Python Sdk

    SVI-STP SSME Squire Technologies - Confidential Document 10 Python SDK 10.1 Overview The SVI-STP SSME comes with a python software development kit that allows developers to create applications that can connect to the SVI-STP SSME using the API Server 6.

  • Page 54: Schema Validation And Configuration

    SVI-STP SSME Squire Technologies - Confidential Document 11 Schema Validation and Configuration 11.1 Configuration The XML file is loaded and validated via the GUI for the SVI-STP Before starting the new configuration the GUI will perform the following actions against the XML configuration file: ...

  • Page 55: Load Xml File

    SVI-STP SSME Squire Technologies - Confidential Document 11.2 Load XML File Create a new resource for the XML and add the following information The File name should match the location of the XML file to be loaded. Default location should be /home/squire/ssme...
  • Page 56 SVI-STP SSME Squire Technologies - Confidential Document Once the information has been entered select the Configure option this will load the following screen Select file allows the user to select the file they will to load into the SVI-STP Configure allows the user to Run Tests Validate –...

  • Page 57: Configure Linkset

    SVI-STP SSME Squire Technologies - Confidential Document 11.3 Configure Linkset Using the Wizard MTP Layer 3 Linkset (A-link), or MTP Layer 3 Linkset (F-link) wizard. For SUA this configuration setting will be on the Sigtran SCTP Socket wizard. Page 57 of 57...

Table of Contents