Fixed Short Message Service Centre – F-SMSC represents hardware and software installed into fixed phone network whose role is to accept and forward short messages to fixed phones and to exchange short messaged with other SMS centers.

F-SMSC is a combination of software and hardware which is modular, scalable, reliable and based on Client/Server architecture. Its responsibility is primarily based on reception, archiving and forwarding of short messages between entities which have the capability of manipulating (reception, archiving and forwarding) of short messages (Short Message Entities – SMEs)

F-SMSC is located in PSTN networks and it manages processes of sorting messages into waiting queues, such as billing the sender or sending status report if requested. F-SMSC enables transmission of alphanumeric or binary messaged from or to fixed subscriber. Its main purpose is short messages, but it can also be used for other purposes. Message exchange between F-SMSC and fixed users that use analogue phone is done with FSK modulation according to ETSI standard  ES 201 912 V.1.1.1, ES 201 986 V.1.1.2 and TS 103 912 V.1.2.1.

F-SMSC is reliable in terms of mistake detection, 24/7 availability, on-line configuration, active database maintenance, robust and reliable hardware components that do not take a lot of space.

Integration of F-SMSC platform with STP nodes is done with connecting E1 links (one on each station) which creates logical connection between platform and STP nodes.

Integration with VAS and MSMS platforms is done with SMPP connection which creates logical connection between F-SMSC platforms, mobile SMSC and other VAS platforms. F-SMSC platform is integrated with Billing through Intranet network. 

Picture 1 – Scheme of F-SMSC platform

Picture 2 –SMS network architecture

F-SMSC platform supports the following interfaces:

SS7 through:

  • E1/T1 

Interfaces and protocols to external applications with appropriate licenses are:

  • SMPP 
  • SS7
  • DSS1
  • R1.5
  • R2
  • FTP
  • XML
  • NBI (North Bound Interface) through SNMP-a v2 standard

Connections of F-SMSC systems with other network elements are unchanged.

SMS network architecture with interfaces and protocols is shown on Picture 2.

General SMSC characteristics

  • Reception and sending SMS from/to fixed phone
  • Reception and sending SMS from WEB
  • Connected messages
  • Message archiving
  • Resending messages
  • Delivering status report for sent messages
  • Activation/deactivation of services via SMS
  • Black and white lists
  • Mass message sending
  • Priority messages
  • Delayed sending
  • Traffic management
  • Redundancy Billing
  • Control, administration and statistics

Functionalities that can be used are:

  • Backup & restore 
  • Defining of user categories (user that can use SMS service only via phone, user that can use SMS services only via web and user that can use SMS service via both phone and web);
  • User administration (adding, deleting, activation/deactivation, blocking, category changing, changing main setting etc.);
  • Review of daily activities (logs) ( about users and sent and received messages);
  • Keeping of log files for 6 month period;
  • Search and review of messages (i.e. according to A/B number, send/delivery date, message status etc.);
  • Configuration of time period in which the unsent messages will be kept with retry mechanism according to the appropriate algorithm; 
  • Manual deletion of undelivered messages from the system;
  • Administration of black and white lists for receiving and sending SMS;
  • Administration of routing messages depending on A and B numbers;
  • Defining translation of alphanumeric characters in source and target addresses (A and B number) in numeric characters;
  • Mass user creation with bulk procedures;
  • Sending and receiving messages via XMP protocol;
  • System monitoring via alarm console for all HW/SW components of the system;
  • View of daily, weekly and monthly activities;
  • NBI (North Bound Interface) access to central monitoring system of BH Telecom wit support; for SNMP v2;