This section contains a definition of the messages transmitted between SMS/800 and the SCP NODE application.
NOTE The only SCP NODE messages supported by SMS/800 are ISA messages. In order to document all SMS/800-SCP interface messages in one document (TM-STS-000798).
8.1 Retrieve Indicated Status Application (RTRV-ISA)
This message is used by SMS/800 to get the status of the indicated SCP application subsystem from the SCP Node application.
Source - SMS
Throttling - Normal
Confirmation - A
Queueing - YES
Response - RSP-ISA
Route ID - GSA
Message Format:
RTRV-ISA::::::TYPE=type
Parameter Description:
type: Application ID
- 3 bytes decimal numeral (in numeric digits, without quotation marks)
- Valid values:
- 254 CMSDB application
- 255 SCP Node application
Frequency:
SMS/800 will send RTRV-ISA message after reconnection. Otherwise, the SCP is responsible for sending REPT-ISA to SMS/800 regarding status changes.
SCP Action:
The SCP must first validate the command’s syntax. An error response must be returned for all unexecutable or failed requests. For all correct requests, the SCP should validate the request and report the status of the specific subsystem.
8.2 Indicated Status Application (RSP-ISA, REPT-ISA)
Indicate Status Application (ISA) message is used by the SCP to notify SMS/800 of the status of a specific application subsystem (specified in ISA) and the overload status of the SCP.
Source - SCP
Throttling - N/A
Confirmation - N/A
Queueing - L(1)
Response - N/A
Route ID - RSA (solicited) or ISA (unsolicited)
Message Format:
Solicited ISA
RSP- ISA:clli,date,time:::term_rpt,error_cd::TYPE=type,VERS=version,MII=mii,ASTA=status1, OSTA=status2;
Unsolicited ISA
REPT-ISA:clli,date,time:::::TYPE=type,VERS=version,MII=mii,ASTA=status1,OSTA=status2;
Parameter Description:
|
clli |
clli = 11 byte COMMON LANGUAGE Location Identifier of the SCP in the format: ccccssbbuuu |
|
|
|
|
where: |
||
|
|
cccc = 4-character city,town or locality code |
||
|
|
ss = 2-character state or province code |
||
|
|
bb = 2-character building code |
||
|
|
uuu = 3-character traffic unit identifier that uniquely identifes the SCP’s physical location |
||
|
date |
See Section 5.2 |
||
|
time |
See Section 5.2 |
||
|
term_rept |
Termination Report Code |
||
|
|
6 byte identifier |
||
|
|
COMPLD |
= Message Request Completed |
|
|
|
DENIED |
= Message Request Denied |
|
|
error_cd |
2 byte decimal numeral |
|
|
|
00 |
no error |
|
|
01 |
syntax error |
|
|
02 |
invalid option |
|
type |
Subsystem ID 3 bytes decimal numeral (in numeric digits, without quotation marks) |
|
|
|
254 |
CMSDB application |
|
|
255 |
SCP Node application |
version The release/version number of the SCP application software (e.g., 1.2 for Release 1 Version 2).
- 7 bytes text.
- Note: SMS/800 displays the Version field on the SID screen Version column.
mii The Message Interface Identifier (e.g., TM-STS-000798-nnr)
- where nn equals the issue number of the document and r equals the revision number.
- 17 bytes text.
- If your SCP is based on issue 22 of this specification, set the mii value to: TM-STS-000798-220
- If your SCP is based on issue 23 of this specification, set the mii value to: TM-STS-000798-230
- Note: Document “revisions” are editorial documentation changes or clarifications.
- If there is no document “revision” number listed on the cover page of TM-STS-000798, set “r” in the “nnr” code to “0”.
- Note: SMS/800 displays the mii field on the SID screen Manual Number column. SMS/800 CR Output (“CRO”, which is the download subsystem to SCPs) uses the Mii field to determine the format of the UPD-UCR message to generate and send to each SCP.
status 1 SCP application status
- 2 bytes decimal numeral
- 00 application in DISABLE state
- 01 application in INACTIVE state
- 02 application in ACTIVE state
- 03 application in ACTIVE state and handling the call processing for its mate
|
status 2 |
SCP overload status |
|
|
|
2 bytes decimal numeral |
|
|
|
00 |
overload level 0 |
|
|
01 |
overload level 1 |
|
|
02 |
overload level 2 |
|
|
03 |
overload level 3.1 |
|
|
04 |
overload level 3.2 |
|
|
05 |
overload level 3.3 |
|
|
06 |
overload level 3.4 |
|
|
07 |
overload level 3.5 |
|
|
08 |
overload level 3.6 |
|
|
09 |
overload level 3.7 |
|
|
10 |
overload level 3.8 |
|
|
11 |
overload level 4 |
|
|
12 |
overload level 5 |
|
|
13 |
overload level 6 |
Frequency:
This message will be issued by the SCP Node application to each supporting system under the following conditions:
- As a response message to the RTRV-ISA message which is sent by SMS.
- As an unsolicited message whenever an SCP application status changes or SCP overload status changes.
8.2.1 Tell NODE Update Complete (TELL-NUC)
NODE Update Complete message is used by the SMS/800 to notify the SCP NODE Application that all the queued messages (if any) have already been sent. SMS/800 will start to empty its queued messages for the NODE whenever the NODE application is ready to receive messages.
Source - SMS
Throttling - Normal
Confirmation - N/A
Queueing - NO
Response - N/A
Route ID - NUC
Message Format:
TELL-NUC:::::;
Parameter Description:
Not Applicable.
Maximum Message Length: 14 bytes.
Frequency:
This message is issued by the SMS/800 when all the queued NODE messages are transmitted (if any) to the NODE.
SCP Action:
The SCP should resume normal operation.
8.2.2 Protocol Testing Request Message 1 (RTRV-PT1)
This message can be sent by SMS/800 to the SCP to verify the protocol implementation at the SCP. The receiving SCP system should echo back, to SMS/800, the value in the "DATA" field and "SQN" field so the sending system can verify the protocol implementation.
Source - SMS
Throttling - CRI
Confirmation - A
Queueing - No
Response - RP1
Route ID - PT1
Message Format:
RTRV-PT1:clli,date,time:::::SQN = sequence,DATA = data
Parameter Description:
clli = 11 bytes Common Language Location Identifier (CLLI) code of the SCP. date = 8 bytes composed of a 4-digit year and 2-digit month and 2-digit day.
time = 9 bytes composed of 2-digit hour, 2-digit minute, 2-digit seconds, and 3-character time zone (e.g., AST, ADT, CST, CDT, EST, EDT, HST, HDT, PST, PDT, YST, YDT).
SQN (sequence) =4 bytes decimal numeral
data = a binary data string in the format $(integer)(bin_data), where the integer is a 4-byte integer representing the number of bytes of binary data in bin_data.
Frequency:
This message is issued manually by the SMS/800 platform as a test message when requested by SCP Software Support.
SCP Action:
The SCP should first validate the command’s syntax. An error response must be returned for all unexecuted or failed requests. For all correct requests, the SCP should echo back the same values that were sent by SMS/800 in the "DATA" and "SQN" fields.
8.2.3 Protocol Testing Response Message 1 (RSP-PT1)
This message is an optional message that is sent by the SCP to SMS/800 in response to SCP receiving a RTRV-PT1 message from SMS/800. The SCP system should echo back, to SMS/800, the value in the "DATA" field and "SQN" field that were sent in the associated RTRV-PT1 message.
Source - SMS
Throttling - CRI
Confirmation - S or No
(optional) Queueing - No
Response - N/A
Route ID - RP1
Message Format:
RSP-PT1:clli,date,time:::term_rpt,error_cd::SQN = sequence, DATA = data;
Parameter Description:
clli, date, time, SQN, DATA - refer to the RTRV-PT1 message for the format term_rpt = Termination Report Code. 6 byte ID.
Values may be: "COMPLD" - Message Request Completed, or "DENIED". error_cd -
Error code: 2 byte decimal numerals.
Values may be: "00" (OK, no error), "01" (syntax error), or "02" (invalid).
Frequency:
This message is to be sent by the SCP in response to the RTRV-PT1 message.
SMS/800 Action:
SMS/800 should verify receipt of the RSP-PT1 message and verify that the DATA and SQN values are identical to the associated RTRV-PT1 message.
8.2.4 Protocol Testing Request Message 2 (RTRV-PT2)
This message can be sent by SMS/800 to the SCP to verify the protocol implementation at the SCP. The receiving SCP system should echo back, to SMS/800, the value in the "DATA" field and "SQN" field so the sending system can verify the protocol implementation.
Source - SMS
Throttling - CRI
Confirmation - A
Queueing - No
Response - RP2
Route ID - PT2
Message Format:
RTRV-PT2:clli,date,time:::::SQN = sequence,DATA = data;
Parameter Description:
clli = 11 bytes Common Language Location Identifier (CLLI) code of the SCP. date = 8 bytes composed of a 4-digit year and 2-digit month and 2-digit day.
time = 9 bytes composed of 2-digit hour, 2-digit minute, 2-digit seconds, and 3-character time zone (e.g., AST, ADT, CST, CDT, EST, EDT, HST, HDT, PST, PDT, YST, YDT).
SQN (sequence) =4 bytes decimal numeral
data = a binary data string in the format $(integer)(bin_data), where the integer is a 4-byte integer representing the number of bytes of binary data in bin_data.
Frequency:
This message is issued manually by the SMS/800 platform as a test message when requested by SCP Software Support.
SCP Action:
The SCP should first validate the command’s syntax. An error response must be returned for all unexecuted or failed requests. For all correct requests, the SCP should echo back the same values that were sent by SMS/800 in the "DATA" and "SQN" fields.
8.2.5 Protocol Testing Response Message 2 (RSP-PT2)
This message is an optional message that is sent by the SCP to SMS/800 in response to SCP receiving a RTRV-PT2 message from SMS/800. The SCP system should echo back, to SMS/800, the value in the "DATA" field and "SQN" field that were sent in the associated RTRV-PT2 message.
Source - SMS
Throttling - CRI
Confirmation - S or No
(optional) Queueing - No
Response - N/A
Route ID - RP2
Message Format:
RSP-PT2:clli,date,time:::term_rpt,error_cd::SQN = sequence, DATA = data
Parameter Description:
clli, date, time, SQN, DATA - refer to the RTRV-PT1 message for the format term_rpt = Termination Report Code. 6 byte ID.
Values may be: "COMPLD" - Message Request Completed, or "DENIED".
error_cd - Error code. 2 byte decimal numerals.
Values may be: "00" (OK, no error), "01" (syntax error), or "02" (invalid).
Frequency:
This message is to be sent by the SCP in response to the RTRV-PT1 message.
SMS/800 Action:
SMS/800 should verify receipt of the RSP-PT2 message and verify that its DATA and SQN
values are identical to the associated RTRV-PT2 message.