Security for TCP/IP message traffic between the SMS/800 and SCP will be provided via the following facilities:
- Dedicated Wide Area Network (WAN) links: dedicated links will be used for message traffic.
- IP address checking: The SCPs’ IP address will be maintained in the SMS/800 system. When an SCP attempts to make a socket connection to the SMS/800, the SCP’s IP address will be verified. The SCP shall also check the source address of all incoming messages to make sure that it came from the SMS/800.
- Port address assignment: each SCP will be assigned specific TCP port numbers to make connection into. Message coming into each port will be verified that they indeed came from the pre-assigned SCP.
Recovery processing depends on the availability of communication links.
- SCP unavailable: When communication links to an SCP are down, or when an SCP is not available, messages for that SCP will be queued in the SMS/800. When the communication links or the SCP is restored, the queued messages will be sent to the SCP. The SMS/800 is sized to queue messages for an SCP up to a maximum of three days.
- SMS/800 unavailable: When communication links to the SMS/800 or the SMS/800 is not available, the SCPs shall queue all messages for SMS/800 and send them when service is restored.
The TCP/IP communication between the SMS/800 and the SCPs shall be designed for 24 by 7 Operations.
The TCP/IP Communication shall be designed to process 20 messages per second continuously.
9.5 Link Sizing
The message load between the SMS/800 and the SCPs does not spread out evenly during the day. In addition, the message load varies significantly based on the SCP’s Area-of- Service, the customers’ record content and mass change activities. The links shall be sized to provide extra capacity to handle the high peak of messages.