In this section:
SCCP Management (SCMG) services and primitives are used in conjunction with Connectionless primitives to coordinate the transfer of traffic between replicated systems and reports the status of local and remote subsystems and remote point codes. The following table lists and describes the SCMG primitives. Indication, response, and confirmation messages are sent by SCCP and request messages are sent by the SCCP user application.
SCMG Primitives
| Message Type | Direction | Description |
|---|---|---|
| N-REGISTER-APPID | Request Response | Registration of an application using an identifier. |
| N-DEREGISTER-APPID | Request Response | Deregistration of an application using an identifier. |
| N-REGISTER-SSN | Request Response | Registration of an application using a PC-SSN. |
| N-DEREGISTER-SSN | Request Response | Deregistration of an application using a PC-SSN. |
| N-PCSTATE | Indication | Reports the status of a local or remote point code. |
| N-STATE | Request Indication | Reports the status of a local or remote subsystem. |
| N-COORD | Indication Confirmation | Coordinates the transfer of traffic between replicated systems. Request and response types are not supported. |
| N-VERSION | Indication | Indicates the supported version of SCCP and the user application depending on sender. SCCP and user application versions do not have to match. The lowest version from either the SCCP or user application is used. |
| N-MTP3-NA-CONFIGURATION | Indication | Indication provided by SCCP to the user application as received from MTP3. |
| N-CONNECTION-SETUP | Indication | Indication provided by the user application to indicate the supported connection setup. |
N-REGISTER-APPID
This primitive registers an SCCP user application with the SCCP. The DSC Platform ensures delivery of messages to the proper registered application-based on the associated application ID string.
Up to 1024 application ID registrations are supported with the DSC Platform on a single socket interface.The following table lists and describes the N-REGISTER-APPID parameters.
N-REGISTER-APPID Parameters
| Parameter | Request | Response | Description |
|---|---|---|---|
| SCCP-APPID-NAME | M | M | The application ID name is a 16 byte string including NULL characters, case insensitive, alphanumeric, and can include dashes (-) and underscores (_). |
| SCCP-KEY-STATUS | N/A | M | Registration result status. |
| SCCP-APPID-REFERENCE | N/A | O | The application ID reference is a ubit16 uniquely assigned by the SNM for a specific application ID name registration. |
| SCCP-APPID-REGISTRATION MODE | O | N/A | The application ID registration mode is used to determine the loadshare type for the given application ID. Applicable to the user interface (UI) only. GT Interface support is reserved for future use. If this parameter is not present, the registration is defined as UNIQUE. If this parameter is present and is set to 0, a round-robin implementation is used between the corresponding registered local user connections. Values 1 to 255 are reserved for future use. |
N-DEREGISTER-APPID
The N-DEREGISTER-APPID primitive deregisters an SCCP application ID from the SCCP. The following table lists and describes the N-DEREGISTER- APPID parameters.
N-DEREGISTER-APPID Parameters
| Parameter | Request | Response | Description |
|---|---|---|---|
| SCCP-APPID-NAME | M | M | The application ID name is a 16 byte string including NULL characters, case insensitive, alphanumeric, and can include dashes (-) and underscores (_). |
| SCCP-KEY-STATUS | N/A | M | Deregistration result status. |
N-REGISTER-SSN
This primitive registers an SCCP user application with the SCCP using an associated point code and subsystem number. The DSC Platform ensures delivery of messages to the proper registered application on a point code and subsystem basis.
Up to 1024 PC-SSN registrations are supported with the DSC Platform on a single socket interface. When an SCCP user application successfully registers, the corresponding SCCP procedures are initiated to broadcast the availability of the PC-SSN. The following table lists and describes the N-REGISTER-SSN parameters
N-REGISTER-SSN Parameters
| Parameter | Request | Response | Description |
|---|---|---|---|
| SCCP-PCSSN-KEY | M | M | SCCP user point code and subsystem. |
| SCCP-KEY-STATUS | N/A | M | Registration result status. |
Note
In previous versions of the SCCP, the SCCP-REGISTER-USER and SCCP-REGISTER-USER-ACK parameters were used instead of the SCCP-PCSSN-KEY and SCCP-KEY-STATUS. Although these parameters are still available, the parameters are now obsolete.
N-DEREGISTER-SSN
This primitive deregisters an SCCP user application from the SCCP using an associated point code and subsystem number. Upon deregistration, the proper SCCP procedures are initiated to broadcast the status change of the PC-SSN. The parameters used in this message are the same as those found in the N-REGISTER-SSN message.
Note
In previous versions of the SCCP, the SCCP-DEREGISTER-USER and SCCP-DEREGISTER-USER-ACK parameters were used instead of SCCP-PCSSN-KEY and SCCP-KEY-STATUS. Although these parameters are still available, the parameters are now obsolete.
N-PCSTATE
This primitive informs an SCCP user application about the status of a signaling point. The following table lists and describes the N-PCSTATE parameters.
N-PCSTATE Parameters
| Parameter | Indication | Description |
|---|---|---|
| SCCP-AFFECTED-DPC | M | Affected user point code (PC). |
| SCCP-SP-STATUS | M | Affected PC status. |
| SCCP-AUDIT-RESPONSE | O | Present if the primitive is a response to a destination audit request. |
N-STATE
This primitive informs the SCCP user application about the status of a locally or remotely affected user. The following table lists and describes the N-STATE parameters.
N-STATE Parameters
| Parameter | Request | Indication | Description |
|---|---|---|---|
| SCCP-AFFECTED-USER | M | M | Affected user (PC-SSN). |
| SCCP-USER-STATUS | M | M | Affected user status. |
| SCCP-SS-MULTI-IND | N/A | M | Subsystem multiplicity indicator. |
| SCCP-AUDIT-RESPONSE | N/A | O | Present if the primitive is a response to a destination audit request. |
N-COORD
This primitive coordinates the transfer of traffic between replicated systems in the event of failures. The following table lists and describes the N-COORD parameters.
N-COORD Parameters
| Parameter | Req | Resp | Conf | Ind | Description |
|---|---|---|---|---|---|
| SCCP-AFFECTED-USER | M | M | M | M | Affected user (PC-SSN). |
| SCCP-USER-STATUS | N/A | N/A | M | N/A | Affected user status. |
| SCCP-SS-MULTI-IND | N/A | N/A | M | M | Subsystem multiplicity indicator. |
Note
Request and response are currently not supported.
N-VERSION
This primitive identifies the version of the interface used. The following table lists and describes the N-VERSION parameter.
N-VERSION Parameter
| Parameter | Indication | Description |
|---|---|---|
| SCCP-VERSION | M | Indicates the supported version of SCCP and the user application depending on sender. |
N-MTP3-NA-CONFIGURATION
This primitive identifies the MTP3 NA Configuration options. The following table lists and describes the N-MTP3-NA-CONFIGURATION parameters.
N-MTP3-NA-CONFIGURATION Parameters
| Parameter | Indication | Description |
|---|---|---|
| SCCP-AFFECTED-DPC | M | Affected user point code (PC). |
| SCCP-MTP3-SS7-VARIANT | M | Relevant SS7 variant (see Table SS7 Variant Values) |
| SCCP-MTP3-NI | M | Relevant NI (see Table Network Indicator Values) |
N-CONNECTION-SETUP
This primitive identifies the connection setup options. The following table lists and describes the N-CONNECTION-SETUP parameter.Should be sent as soon as the connection is established.
N-CONNECTION-SETUP Parameter
| Parameter | Indication | Description |
|---|---|---|
| REASSEMBLY-SUPPORT | O | Provides the XUDT reassembly support, where 0 indicates that reassembly is disabled and 1 indicates that reassembly is enabled. |
Note
SCCP supports reassembly by default so this message is only required to disable the feature.
Overview
Content Tools