Toolpack:Create an SCCP Route

From TBwiki
(Difference between revisions)
Jump to: navigation, search
(initial content)
 
(more clean-up)
Line 70: Line 70:
  
  
−
*The '''Replicate mode''' parameter specifies the mode of replicated nodes/subsystems. Allowable values:
+
*The SCCP '''Replicate mode''' parameter specifies the mode of replicated nodes/subsystems. Allowable values:
  
  
 
{| class="wikitable" border="1"
 
{| class="wikitable" border="1"
−
! width="150" style="background:#efefef;" |Connection mode
+
! width="150" style="background:#efefef;" |Replicate mode
 
! width="350" style="background:#efefef;" |Description
 
! width="350" style="background:#efefef;" |Description
 
|-
 
|-
−
| Normal|| MTP2 layer is used in conjunction with an above MTP3 layer
+
| Dominant|| In this mode, each backup node/subsystem is assigned a unique priority. The node/subsystem on this route is the primary node/subsystem and is selected as the preferred node/subsystem when accessible. On failure of the preferred node/subsystem the next higher priority available backup node/subsystem is selected as the preferred node/subsystem.
 +
|-
 +
| Loadshare ||  In this mode, each backup node/subsystem together with the node/subsystem configured on the route is assigned equal priority and load is distributed among nodes/subsystems on the basis of: 1) SLS for class1 traffic, and 2) in round-robin fashion for class 0 traffic. Loadshare mode is applicable in TELCORDIA only.
 
|-
 
|-
−
| HSL|| MTP2 layer high speed link is used in conjunction with an above MTP3 layer
+
| Dominant alternate|| This mode is significant only for class 0 traffic. In this mode, class 0 traffic is prevented from reaching an accessible but congested node. For class 1 traffic, this mode is same as DOMINANT mode. In this mode, each backup node/subsystem is assigned a unique priority. The node/subsystem configured on the route is selected as the primary node/subsystem and is the preffered node/subsystem when accessible and not congested. On failure or congestion of the preferred node/subsystem the next higher priority available and uncongested backup node/subsystem is selected as the preferred node/subsystem. This mode of operation is applicable only in ANSI96 and TELCORDIA.
 +
|-
 +
| Loadshare alternate|| This mode is significant only for class 0 traffic. In this mode, class 0 traffic is prevented from reaching an accessible, but congested node. For class 1 traffic, this mode is same as LOADSHARE mode. In this mode, each backup node/subsystem together with the node/subsystem configured on the route is assigned equal priority and load is distributed among nodes/subsystems on the basis of: 1) SLS for class 1 traffic, and 2) in round-robin fashion for class 0 traffic. For class 0 traffic, a node/subsystem is selected when it is accessible and uncongested. On failure or congestion of the node, next available and uncongested node/subsystem is selected. This mode of operation is applicable only in TELCORDIA.
 
|}
 
|}
  
  
−
Table  SEQ Table \* ARABIC 76 - SCCP replicate mode
+
'''Note:''' Only used with ANSI96 and TELCORDIA.
  
−
Replicate Mode
 
  
−
Description
+
----
  
−
TB640_SS7_SCCP_ROUTE_REPLICATED_MODE_DOMINANT
 
  
−
In this mode, each backup node/subsystem is assigned a unique priority. The node/subsystem on this route is the primary node/subsystem and is selected as the preferred node/subsystem when accessible. On failure of the preferred node/subsystem the next higher priority available backup node/subsystem is selected as the preferred node/subsystem.
+
*The '''Destination point code'''  ([[DPC]]) parameter specifies the point code of the node where the route is terminating.  Proper point code length is described in see Table 3 - DPC Length 08D0C5F005200650066003100320034003000360030003200310033000000 .
  
−
TB640_SS7_SCCP_ROUTE_REPLICATED_MODE_LOADSHARE
 
  
−
In this mode, each backup node/subsystem together with the node/subsystem configured on the route is assigned equal priority and load is distributed among nodes/subsystems on the basis of: 1) SLS for class1 traffic, and 2) in round-robin fashion for class 0 traffic. Loadshare mode is applicable in TELCORDIA only.
+
'''Note:''' Default routing: Note that destination point code 0.0.0 is reserved for default routing. When no explicit route exists for a destination point code and default route 0.0.0 is present, the message is passed to MTP 3 for delivery in place of being dropped. If the MTP 3 layer is unable to deliver the message for any reason, the message is dropped and no notification is given to the application that originated the message.
−
 
+
−
TB640_SS7_SCCP_ROUTE_REPLICATED_MODE_DOMINANT_ALTERNATE
+
−
 
+
−
This mode is significant only for class 0 traffic. In this mode, class 0 traffic is prevented from reaching an accessible but congested node. For class 1 traffic, this mode is same as DOMINANT mode. In this mode, each backup node/subsystem is assigned a unique priority. The node/subsystem configured on the route is selected as the primary node/subsystem and is the preffered node/subsystem when accessible and not congested. On failure or congestion of the preferred node/subsystem the next higher priority available and uncongested backup node/subsystem is selected as the preferred node/subsystem. This mode of operation is applicable only in ANSI96 and TELCORDIA.
+
−
 
+
−
TB640_SS7_SCCP_ROUTE_REPLICATED_MODE_LOADSHARE_ALTERNATE
+
−
 
+
−
This mode is significant only for class 0 traffic. In this mode, class 0 traffic is prevented from reaching an accessible, but congested node. For class 1 traffic, this mode is same as LOADSHARE mode. In this mode, each backup node/subsystem together with the node/subsystem configured on the route is assigned equal priority and load is distributed among nodes/subsystems on the basis of: 1) SLS for class 1 traffic, and 2) in round-robin fashion for class 0 traffic. For class 0 traffic, a node/subsystem is selected when it is accessible and uncongested. On failure or congestion of the node, next available and uncongested node/subsystem is selected. This mode of operation is applicable only in TELCORDIA.
+
−
 
+
−
?      Only used with ANSI96 and TLECORDIA.
+
−
 
+
−
 
+
−
----
+
−
 
+
−
-          The destination point code parameter (Dpc) specifies the point code of the node where the route is terminating. This field is not reconfigurable. Proper point code length is: see Table 3 - DPC Length 08D0C9EA79F9BACE118C8200AA004BA90B02000000080000000E0000005F005200650066003100320034003000360030003200310033000000 .
+
−
 
+
−
?      Default routing: Note that destination point code 0.0.0 is reserved for default routing. When no explicit route exists for a destination point code and default route 0.0.0 is present, the message is passed to MTP 3 for delivery in place of being dropped. If the MTP 3 layer is unable to deliver the message for any reason, the message is dropped and no notification is given to the application that originated the message.
+
  
  
Line 122: Line 106:
  
 
{| class="wikitable" border="1"
 
{| class="wikitable" border="1"
−
! width="150" style="background:#efefef;" |Connection mode
+
! width="150" style="background:#efefef;" |Route Options
 
! width="350" style="background:#efefef;" |Description
 
! width="350" style="background:#efefef;" |Description
 
|-
 
|-
Line 129: Line 113:
 
| HSL|| MTP2 layer high speed link is used in conjunction with an above MTP3 layer
 
| HSL|| MTP2 layer high speed link is used in conjunction with an above MTP3 layer
 
|}
 
|}
−
Table  SEQ Table \* ARABIC 77 - SCCP route options
 
  
−
Route Options
 
−
 
−
Description
 
  
−
TB640_SS7_SCCP_ROUTE_OPTIONS_NONE
 
  
−
None (no options).
+
None        None (no options).
  
 
TB640_SS7_SCCP_ROUTE_OPTIONS_ONLINE_BY_DEFAULT
 
TB640_SS7_SCCP_ROUTE_OPTIONS_ONLINE_BY_DEFAULT
Line 162: Line 141:
  
  
−
*The '''Broadband support flag''' parameter. Flag to indicate whether the peer SCCP on the route has broadband support. This parameter is reconfigurable. Allowable values: TBX_TRUE or TBX_FALSE.
+
*The '''Broadband support flag''' parameter. Flag to indicate whether the peer SCCP on the route has broadband support. Allowable values are 'True' or 'False'.
 +
 
  
 
'''Note:''' For ITU88, ITU92, ANSI88, ANSI92 and ANSI96 network this flag should always be TBX_FALSE.
 
'''Note:''' For ITU88, ITU92, ANSI88, ANSI92 and ANSI96 network this flag should always be TBX_FALSE.
Line 174: Line 154:
  
 
{| class="wikitable" border="1"
 
{| class="wikitable" border="1"
−
! width="150" style="background:#efefef;" |Connection mode
+
! width="150" style="background:#efefef;" |Route SLS Mask
 
! width="350" style="background:#efefef;" |Description
 
! width="350" style="background:#efefef;" |Description
 
|-
 
|-
Line 182: Line 162:
 
|}
 
|}
  
−
Table  SEQ Table \* ARABIC 78 - SCCP route SLS mask
 
  
−
Route SLS Mask
 
−
 
−
Description
 
  
 
TB640_SS7_SCCP_ROUTE_SLS_MASK_5BITS
 
TB640_SS7_SCCP_ROUTE_SLS_MASK_5BITS
Line 210: Line 186:
  
 
*The '''Array of priority of backup point code entries''' parameter specifies the list of priority of each backup point code for this route. Allowable values are from 0 to 255.
 
*The '''Array of priority of backup point code entries''' parameter specifies the list of priority of each backup point code for this route. Allowable values are from 0 to 255.
 +
  
 
'''Note:''' Zero being the lowest priority.
 
'''Note:''' Zero being the lowest priority.
Line 356: Line 333:
  
 
{| class="wikitable" border="1"
 
{| class="wikitable" border="1"
−
! width="150" style="background:#efefef;" |Connection mode
+
! width="150" style="background:#efefef;" |Route Options
 
! width="350" style="background:#efefef;" |Description
 
! width="350" style="background:#efefef;" |Description
 
|-
 
|-
Line 363: Line 340:
 
| HSL|| MTP2 layer high speed link is used in conjunction with an above MTP3 layer
 
| HSL|| MTP2 layer high speed link is used in conjunction with an above MTP3 layer
 
|}
 
|}
−
Table  SEQ Table \* ARABIC 80 - SCCP SSN options
 
  
−
Route Options
 
  
−
Description
+
Table  SEQ Table \* ARABIC 80 - SCCP SSN options
 +
 
  
 
TB640_SS7_SCCP_SSN_OPTIONS_ACCESSIBLE_BY_DEFAULT
 
TB640_SS7_SCCP_SSN_OPTIONS_ACCESSIBLE_BY_DEFAULT
Line 383: Line 359:
  
  
−
*The '''Replicate mode''' parameter specifies the mode of replicated nodes/subsystems. Allowable values: see Table 76 - SCCP replicate mode 08D0C9EA79F9BACE38000000 .
+
*The '''Replicate mode''' parameter specifies the mode of replicated nodes/subsystems. Allowable values: see Table 76 - SCCP replicate mode 08D0C9EA79F9BACE380.
 
*The ''Number backup point code''' parameter specifies the number of backup point code entries in the arrays aBpc[ ] and aPrioBpc[ ].
 
*The ''Number backup point code''' parameter specifies the number of backup point code entries in the arrays aBpc[ ] and aPrioBpc[ ].
 
*The '''Array of backup point code entries''' parameter specifies the list of backup point code for this SSN.
 
*The '''Array of backup point code entries''' parameter specifies the list of backup point code for this SSN.
 +
 +
 +
----
 +
 +
 
*The '''Array of priority of backup point code entries''' parameter specifies the list of priority of each backup point code for this SSN. Allowable values are from 0 to 255.
 
*The '''Array of priority of backup point code entries''' parameter specifies the list of priority of each backup point code for this SSN. Allowable values are from 0 to 255.
 +
  
 
'''Note:''' Zero being the lowest priority.
 
'''Note:''' Zero being the lowest priority.

Revision as of 23:36, 2 September 2009

This step is used to create a route to a specific DPC


WALKTHROUGH AND SCREENSHOT CONTENT ARE OUTSTANDING


Description of parameters

General explanation of the parameters of configuration:

  • The Handle SCCP LSAP parameter specifies the handle of the SCCP LSAP



  • The Protocol variant parameter specifies the SCCP route protocol variant for this destination point code. Allowable values:


Connection mode Description
Normal MTP2 layer is used in conjunction with an above MTP3 layer
HSL MTP2 layer high speed link is used in conjunction with an above MTP3 layer

Table SEQ Table \* ARABIC 75 - SCCP route protocol variant

Route Protocol Variant

Description

TB640_SS7_SCCP_ROUTE_PROTOCOL_VARIANT_ANSI88

Used for ANSI88.

TB640_SS7_SCCP_ ROUTE_PROTOCOL_VARIANT_ANSI92

Used for ANSI92.

TB640_SS7_SCCP_ ROUTE_PROTOCOL_VARIANT_ANSI96

Used for ANSI96.

TB640_SS7_SCCP_ ROUTE_PROTOCOL_VARIANT_TELCORDIA

Used for TELCORDIA.

TB640_SS7_SCCP_ ROUTE_PROTOCOL_VARIANT_ITU88

Used for ITU88.

TB640_SS7_SCCP_ ROUTE_PROTOCOL_VARIANT_ITU92

Used for ITU92.

TB640_SS7_SCCP_ ROUTE_PROTOCOL_VARIANT_ITU96

Used for ITU96.

TB640_SS7_SCCP_ ROUTE_PROTOCOL_VARIANT_GSM0806

Valid in both ITU and ANSI networks.



  • The SCCP Replicate mode parameter specifies the mode of replicated nodes/subsystems. Allowable values:


Replicate mode Description
Dominant In this mode, each backup node/subsystem is assigned a unique priority. The node/subsystem on this route is the primary node/subsystem and is selected as the preferred node/subsystem when accessible. On failure of the preferred node/subsystem the next higher priority available backup node/subsystem is selected as the preferred node/subsystem.
Loadshare In this mode, each backup node/subsystem together with the node/subsystem configured on the route is assigned equal priority and load is distributed among nodes/subsystems on the basis of: 1) SLS for class1 traffic, and 2) in round-robin fashion for class 0 traffic. Loadshare mode is applicable in TELCORDIA only.
Dominant alternate This mode is significant only for class 0 traffic. In this mode, class 0 traffic is prevented from reaching an accessible but congested node. For class 1 traffic, this mode is same as DOMINANT mode. In this mode, each backup node/subsystem is assigned a unique priority. The node/subsystem configured on the route is selected as the primary node/subsystem and is the preffered node/subsystem when accessible and not congested. On failure or congestion of the preferred node/subsystem the next higher priority available and uncongested backup node/subsystem is selected as the preferred node/subsystem. This mode of operation is applicable only in ANSI96 and TELCORDIA.
Loadshare alternate This mode is significant only for class 0 traffic. In this mode, class 0 traffic is prevented from reaching an accessible, but congested node. For class 1 traffic, this mode is same as LOADSHARE mode. In this mode, each backup node/subsystem together with the node/subsystem configured on the route is assigned equal priority and load is distributed among nodes/subsystems on the basis of: 1) SLS for class 1 traffic, and 2) in round-robin fashion for class 0 traffic. For class 0 traffic, a node/subsystem is selected when it is accessible and uncongested. On failure or congestion of the node, next available and uncongested node/subsystem is selected. This mode of operation is applicable only in TELCORDIA.


Note: Only used with ANSI96 and TELCORDIA.



  • The Destination point code (DPC) parameter specifies the point code of the node where the route is terminating. Proper point code length is described in see Table 3 - DPC Length 08D0C5F005200650066003100320034003000360030003200310033000000 .


Note: Default routing: Note that destination point code 0.0.0 is reserved for default routing. When no explicit route exists for a destination point code and default route 0.0.0 is present, the message is passed to MTP 3 for delivery in place of being dropped. If the MTP 3 layer is unable to deliver the message for any reason, the message is dropped and no notification is given to the application that originated the message.



  • The Options parameter specifies the route options. Allowable values:


Route Options Description
Normal MTP2 layer is used in conjunction with an above MTP3 layer
HSL MTP2 layer high speed link is used in conjunction with an above MTP3 layer


None None (no options).

TB640_SS7_SCCP_ROUTE_OPTIONS_ONLINE_BY_DEFAULT

Node is online by default.

TB640_SS7_SCCP_ROUTE_OPTIONS_TRANSLATOR_NODE

Translator node.

TB640_SS7_SCCP_ROUTE_OPTIONS_ADJACENT_NODE

Adjacent node.

TB640_SS7_SCCP_ROUTE_OPTIONS_INS_CAPABLE_NODE

INS capable. Only in TELCORDIA.


Note: These values can be ORed together.



  • The Broadband support flag parameter. Flag to indicate whether the peer SCCP on the route has broadband support. Allowable values are 'True' or 'False'.


Note: For ITU88, ITU92, ANSI88, ANSI92 and ANSI96 network this flag should always be TBX_FALSE.



  • The Signaling link selector mask parameter specifies, in ANSI and TELCORDIA networks, if the SLS can be either 5 bits or 8 bits. Allowable values:


Route SLS Mask Description
Normal MTP2 layer is used in conjunction with an above MTP3 layer
HSL MTP2 layer high speed link is used in conjunction with an above MTP3 layer


TB640_SS7_SCCP_ROUTE_SLS_MASK_5BITS

Networks SLS is 5 bits.

TB640_SS7_SCCP_ROUTE_SLS_MASK_8BITS

Networks SLS is 8 bits.

Note: For ANSI and TELCORDIA only.



  • The Number backup point code parameter specifies the number of backup point code entries in the arrays aBpc[ ] and aPrioBpc[ ].
  • The Array of backup point code entries parameter specifies the list of backup point code for this route



  • The Array of priority of backup point code entries parameter specifies the list of priority of each backup point code for this route. Allowable values are from 0 to 255.


Note: Zero being the lowest priority.



  • The Number subsystem number parameter specifies the number of subsystem number entries in the array aSsn[ ]
  • The Array of subsystem number entries parameter specifies the list of subsystem number for this route.


Description of SSN specific parameters

General explanation of the parameters of SSN specific configuration:

  • The Subsystem number parameter specifies a subsystem number for this route. Allowable values are from 1 to 255.


Connection mode Description
Normal MTP2 layer is used in conjunction with an above MTP3 layer
HSL MTP2 layer high speed link is used in conjunction with an above MTP3 layer

Table SEQ Table \* ARABIC 79 - SCCP SSN value to identify SCCP user

SSN value to identify SCCP user

Description

TB640_SS7_SCCP_SSN_VALUE_UNKNOWN

SSN not known or not used.

TB640_SS7_SCCP_SSN_VALUE_SCCPMNGT

SCCP management.

TB640_SS7_SCCP_SSN_VALUE_ISUP

ISDN user part.

TB640_SS7_SCCP_SSN_VALUE_OMAP

Operation, Maintenance and Administration Part.

TB640_SS7_SCCP_SSN_VALUE_MAP

Mobile Application Part.

TB640_SS7_SCCP_SSN_VALUE_HLR

Home Location Register.

TB640_SS7_SCCP_SSN_VALUE_VLR

Visitor Location Register.

TB640_SS7_SCCP_SSN_VALUE_MSC

Mobile Switching Center.

TB640_SS7_SCCP_SSN_VALUE_EIR

Equipment Identifier Register.

TB640_SS7_SCCP_SSN_VALUE_AC

Authentication Center.

TB640_SS7_SCCP_SSN_VALUE_ISDNSUPP

ISDN Supplementary services.

TB640_SS7_SCCP_SSN_VALUE_BISDNE2EAPP

Broadband ISDN Edge-to-Edge Application.

TB640_SS7_SCCP_SSN_VALUE_TCTR

TC Test Responder.

TB640_SS7_SCCP_SSN_VALUE_RANAP

Radio Access Network Application Part.

TB640_SS7_SCCP_SSN_VALUE_RNSAP

Radio Network Subsystem Application Part.

TB640_SS7_SCCP_SSN_VALUE_GMLC

Gateway Mobile Location Centre (MAP).

TB640_SS7_SCCP_SSN_VALUE_CAP

CAMEL application part.

TB640_SS7_SCCP_SSN_VALUE_GSMSCF

Global System for Mobile Service Control Function (MAP).

TB640_SS7_SCCP_SSN_VALUE_SIWF

Shared Interworking Functions (MAP).

TB640_SS7_SCCP_SSN_VALUE_SGSN

Serving GPRS Support Node (MAP).

TB640_SS7_SCCP_SSN_VALUE_GGSN

Gateway GPRS Support Node (MAP).

TB640_SS7_SCCP_SSN_VALUE_BSC_PCAP

Positioning Calculation Application Part.

TB640_SS7_SCCP_SSN_VALUE_BSC_BSSAP

BSC Base Station System Application Part (BSSAP-LE).

TB640_SS7_SCCP_SSN_VALUE_MSC_BSSAP

MSC Base Station System Application Part (BSSAP-LE).

TB640_SS7_SCCP_SSN_VALUE_SMLC

Serving Mobile Location Center (BSSAP-LE).

TB640_SS7_SCCP_SSN_VALUE_BSSOM

Base Station System Operation & Maintenance (A-interface).

TB640_SS7_SCCP_SSN_VALUE_BSSAP

Base Station System Application Part (A-interface).



  • The Subsystem number options parameter specifies the subsystem number options. Allowable values:


Route Options Description
Normal MTP2 layer is used in conjunction with an above MTP3 layer
HSL MTP2 layer high speed link is used in conjunction with an above MTP3 layer


Table SEQ Table \* ARABIC 80 - SCCP SSN options


TB640_SS7_SCCP_SSN_OPTIONS_ACCESSIBLE_BY_DEFAULT

Subsystem is accessible by default.

TB640_SS7_SCCP_SSN_OPTIONS_NORMAL_ROUTED

Subsystem normal routed - valid in ANSI and TELCORDIA network only.

Note: These values can be ORed together.



  • The Replicate mode parameter specifies the mode of replicated nodes/subsystems. Allowable values: see Table 76 - SCCP replicate mode 08D0C9EA79F9BACE380.
  • The Number backup point code' parameter specifies the number of backup point code entries in the arrays aBpc[ ] and aPrioBpc[ ].
  • The Array of backup point code entries parameter specifies the list of backup point code for this SSN.



  • The Array of priority of backup point code entries parameter specifies the list of priority of each backup point code for this SSN. Allowable values are from 0 to 255.


Note: Zero being the lowest priority.



  • The number concerned point code parameter (un32NbConPc) specifies the number of concerned point code entries in the array aConPc[ ].
  • The Array of concerned point code entries parameter specifies the list of concerned point code for this SSN
Retrieved from "https://docs.telcobridges.com/mediawiki/index.php?title=Toolpack:Create_an_SCCP_Route&oldid=2567"
Personal tools