You are here: CSP Developer’s Guide: Common Channel Signaling > 2 Introduction to SS7 > Software Modifications
Purpose
The following summarizes the changes to the software to support this feature with links to the detailed formats.
HMDT PPL Information
Configuration Bytes
The HMDT (Message Distribution) component of MTP3 uses configuration bytes to allow you to program which SS7 user parts will remain local to the CSP and which user parts will reside in a remote host. The default is to have all the user parts in the CSP.
Refer to MTP3 HMDT Configuration Bytes.
PPL Event Indications
There is a PPL Event Indication from the HMDT component to the host. The events reports TRANSFER IND and sends the corresponding data to the host.
Refer to MTP3 HMDT PPL Event Indications .
TSFC PPL Information
PPL Event Indications
There are three PPL event indication from the component TSFC (Traffic Signaling Flow Control) to the host. These events report the STATUS of a DPC or Pause and RESUME indications for an affected DPC.
Refer to MTP3 TSFC PPL Event Indications.
HMRT PPL Information
PPL Event Request
There is a PPL event request, TRANSFER, from the host to the HMRT (Message Routing) component.
The default sequence of these events is from the corresponding MTP3 component to a specific SS7 user part of the CSP. However, if you configure the HMDT configuration bytes, then the events flow to a remote user part resident in a remote host. You can achieve this process on a per user part basis. Also, there might be multiple remote hosts. In this case, the port number of the remote hot is stored in a specific HMDT configuration byte.
Refer to MTP3 HMRT PPL Event Requests (AIB: Stack/Link 0x08).
Below is the ICB for MTP to remote UP.
0x002B MTP3 User Part Parameter
Used in:
PPL Event Request message
PPL Event Indication message
ICB Type |
0x03 (Extended Data) |
ICB Subtype |
0x002B MTP3 User Part Parameter |
ICB Length |
Length of parameters, in bytes |
Data[0] |
Parameter 1 Type ID |
Data[1] |
Length of parameter 1data in bytes |
Data[2] |
Parameter 1 Value Variable size |
: |
|
Data[:] |
Parameter n Type ID |
Data[:] |
Length of parameter n data in bytes |
Data[:] |
Parameter n Value Variable size |
PPL Parameters
ICB Type |
0x03 (Extended Data) |
ICB ID |
0x0424 |
Data Length 2 bytes |
0x000D |
Data[0-3] |
DPC - Destination Point Code |
Data[4-7] |
OPC - Originating Point Code |
Data[8-9] |
CIC - Circuit ID Code |
Data[10] |
SI - Service Indicator |
Data[11] |
MP - Message Priority |
Data[12] |
NI - Network Indicator |
ICB Type |
0x03 (Extended Data) |
ICB ID |
0x0425 |
Data Length 2 bytes |
0x000C |
Data[0-3] |
DPC - Destination Point Code |
Data[4-7] |
OPC - Originating Point Code |
Data[8] |
SI - Service Indicator |
Data[9] |
MP - Message Priority |
Data[10] |
NI - Network Indicator |
Data[11] |
SLS - Signaling Link Set |
ICB Type |
0x03 (Extended Data) |
ICB ID |
0x0426 |
Data Length 2 bytes |
Up to 0x010E |
Data[0-1] |
Length - Length of MSU Data |
Data[4-n] |
MSU Data - Length up to 0x010C |
ICB Type |
0x03 (Extended Data) |
ICB ID |
0x0427 |
Data Length 2 bytes |
0x0006 |
Data[0-3] |
Affected DPC |
Data[4] |
Cause Value Value 0 - congestion level 0 Value 1 - congestion level 1 Value 2 - congestion level 2 Value 3 - congestion level 3 Value 4 - User Part Unavailable Value 5 - User Part Unequipped Value 6 - User Part Inaccessible Value 7 - Signaling Link Congestion level 0 Value 8 - Signaling Link Congestion level 1 Value 9: Signaling Link Congestion level 2 Value 10: Signaling Link Congestion level 3 Value 11: Signaling Link Congestion level 4 |
Data[5] |
User Information Octet value |