This document outlines the plan for testing a Service Control Point (SCP) with the SMS/800 TFN Registry®. Testing will be based on the latest issue of SMS/800 – SCP Interface Specification (TM-STS-00798). Throughout this document, the term Call Management Services Data Base (CMSDB) refers to the application in the SCP that interfaces with the SMS/800 TFN Registry.
This document version replaces all previous versions of TM-STS-000798. This specification was updated for the SMS/800 TFN Registry.
Please Note: SCP will generically refer to any system that provides call control information required for centralized call management capabilities in response to network queries for such information and that adheres to the SMS/800 - SCP interface. The terms ‘SMS’ and ‘SMS/800’ refer to the same system.
Interface testing is done by sending the specified messages between the SMS/800 and the SCP. SMS/800 sends commands to the SCP but does not respond to commands from the SCP(except for the TELL-SRU and RSP-SRU pair of messages). The SCP sends responses to commands and reports to the SMS/800. In all test cases, SMS/800 initiates the commands and the SCP responds. The SMS/800 tester does what is necessary in SMS/800 to send the specified command to the test SCP and must be familiar with the system to perform the tests cases. The SCP tester must be able to generate data needed by report messages and be able to verify the SCP is behaving correctly for each message.
In each test case SMS/800 refers to the SMS/800 tester and SCP refers to the SCP tester. The specific tasks that result in the transfer of a message containing the data required by the test scenario are not part of this document.
1.1 Test Phases
The testing can be categorized into the following phases. Some testing is dependent on the successful completion of one phase before beginning the next. In general the tests are listed in the order that agrees with this dependency. Any exceptions are noted in the test cases.
1.1.1 SCP Initialization Testing
Before any testing can occur between SMS/800 and an SCP certain data must reside in each system. The objective of SCP Initialization testing is to establish that data. Some data is transmitted across the links, so this testing is dependent on successful completion of at least the first UAL test case.
Some of the data is loaded and this interface must be successfully tested. All User Message testing is based on successful completion of SCP Initialization.
SCP Initialization testing is not necessary with an established SCP, although it can be used to establish identical sets of data before starting other test cases.
1.1.2 UAL Testing
With the introduction of TCP/IP, the former X.25 UAL Header is renamed the UPL Header. It is not a part of the TCP/IP protocol, but is encapsulated as data. The test cases identified as specific to TCP/IP are used to test only this implementation. The test cases test the functionality of the following:
- Application-To-Application Confirmation
- Session Initialization – the SCP always initiates the session.
- Message Throttling – In response to an SCP overload condition, SMS/800 controls the flow of messages to an SCP.
- Message Queueing – Messages are queued, if data transfer cannot take place.
- Message De-Queueing – Queued messages are transmitted when data transfer is resumed.
- Planned Shutdown
1.1.3 NODE Message Testing
A description of NODE messages is not found in TM-STS-00798.
Only two NODE messages are used between the SMS/800 and SCP, the RTRV-ISA and RSP-ISA message pair and the REPT-ISA message. These messages must be tested relatively early because other tests depend on their successful functionality.
Definitions of ISA messages can be found in TM-STS-00798, and ISA message are used with TCP/ IP implementation and will be part of TCP/IP testing.
1.1.4 User Message Testing
The user messages can be tested in almost any order and are divided into the following functional groups in the interface specification.
- CPR Data Maintenance: The messages in this group deal with creating, updating and deleting the CPR. Some messages are used for auditing purposes and reporting routing errors.
- Administrative Data Maintenance: The messages in this group are used to keep administrative tables updated.
- Special Studies: These messages create a special study in the SCP and send the data to SMS/800.
- Network Management: The messages in this group are used in managing traffic overloads appearing at the SCP.
- Status and Control: These messages are used in the communications between the SCP and the SMS/800.
- e: The SCP is required to send SMS/800 a response to each command. The SCP is required to be able to process 1200 SMS/800 commands a minute. The test cases for volume testing are meant to simulate this level of processing.