Open Source Telecom Signaling

Efficiency starts with openness. Open source code enables sustainable savings for mobile operators, platform providers & system integrators.

Delivering Ownership

The Open Source Strategic Advantage

Maximizing ROI & Margins

The Challenge

Mobile operators generate massive revenues, but profit margins are shrinking.

The Solution

PAiCore delivers highly standardized open source signaling solutions at a lower cost base.

Free from Vendor Lock-in

The Challenge

The vendor lock-in model keeps OPEX costs up, even when value diminishes.

The Solution

PAiCore open source solutions offer the freedom to scale up or down, without transactional limits.

Telecom Innovation

The Challenge

Telecom innovation is vendor-driven, so services are becoming generic.

The Solution

For innovation to be customer-focused, it has to come from the companies serving the customers.

Our Core Network Portfolio

Messaging

SMSC

Scalable, Future-Proof Open Source SMSC.

USSD Gateway

Ubiquitous, Interactive & Secure Messaging.

IP-SM-GW

Interworking, Intelligent & IP-Optimized SMS.

SMSF-5G

Native SMS for 5G Standalone Networks.

Geolocation

GMLC

Responsible Monetization of Geolocation.

Geolocation API

Optimized, Secure & Internet-Free Geolocation.

E-SMLC Q4-26

High-Accuracy Network-Based Location Intelligence.

LMF-5G Q4-26

Native Location Function for 5G Networks.

Signaling

Diameter Routing Agent

Open Source 4G & non-standalone 5G Orchestration.

jSS7-STP

Powering Seamless Signaling Network Messaging.

Signaling Gateway

Simplifying Multi-protocol Interworking.

SCP-5G Q4-26

Scalable Service Communication Proxy for 5G Core.

VAS Platforms

SDP

Service Delivery Platform for rapid application deployment.

CNA

Core Network Applications & custom routing logic.

Top-up System

Real-time balance, recharge and voucher management.

TAS

Telephony Application Server for advanced call control.

Open Source Documentation

PAiCore SMSC

Technical documentation, architecture, and deployment guidelines.

Introduction

SMSC (Short Message Service Center) is a telecommunications network platform responsible for handling the SMS operations of a wireless network. When a subscriber sends an SMS message from a mobile phone, the message first reaches the SMS Center which then forwards the message to the desired destination. The SMS Center is responsible for routing the SMS messages and regulating the process. If the recipient is not reachable (the phone is switched off or out of coverage area etc.) the SMS Center will store the message to a database and forward it to the recipient when available. Messages that are delivered successfully and messages that fail to be delivered are stored in an archive database for logging purposes.

PAiC BD's high-performance and robust SMSC solution is designed to handle the complexities of modern messaging services, providing a reliable and scalable platform for SMS communication. Built on the Java Spring Boot framework, PAiC BD's SMSC is not only robust but also benefits from the extensive Spring ecosystem. It is also designed to utilize the latest technologies, being compatible with Java 21, offering developers access to the latest language features and optimizations for enhanced performance.

To ensure rapid and efficient message processing, our SMSC relies on Redis for its message queue processing logic. This choice of technology facilitates seamless handling of messaging tasks, contributing to the overall responsiveness of the system. Critical management settings and Call Detail Records (CDRs) are stored in a PostgreSQL database. This choice of database ensures data integrity and reliability, providing a robust foundation for managing configuration settings and recording transaction details.

With the capability to handle up to 15,000 Transactions Per Second (TPS), our SMSC application excels in high transaction environments. This high level of transactionality guarantees efficient and rapid processing of messages, meeting the demands of today's dynamic messaging landscape.

A sophisticated balance management system is included, allowing for precise control and monitoring of user balances. This feature is crucial for maintaining fair and transparent communication services. Implementation of routing rules and traffic control mechanisms empowers administrators to customize and optimize message routing based on specific criteria. This flexibility ensures efficient utilization of resources and improves overall system performance.

PAiC BD's SMSC adopts a modular approach, with independent components designed for scalability and flexibility. This modular architecture allows for easy customization, expansion, and integration of new features to meet evolving business requirements.

As part of our commitment to continuous improvement, our roadmap includes plans for achieving even higher TPS. Additionally, we are working on expanding protocol support to include HTTP, GSM MAP, and Diameter protocols, further enhancing the versatility of our SMSC application.

Architecture

SMSC High Level Architecture overview detailing the interactions between services.

[High Level Architecture Diagram Placeholder]

Core Services

DB Insert Data

The service db-insert-data is responsible for inserting data into a PostgreSQL database. It retrieves data from Kafka and inserts it into the database based on a predefined configuration.

Main Responsibilities:

Fetch data from Kafka.
Batch data insertion into PostgreSQL.
Manage connection pools and worker threads.
Automated database migrations using Flyway.
Configurable via environment variables.

SMSC Routing

The smsc-routing-module is a Docker service responsible for routing messages in an SMSC environment. This service interacts with Kafka, processes different types of messages (SMPP, HTTP, SS7), and manages delivery statuses (DLR). It is highly configurable with support for multi-threaded processing, WebSocket communication, and integration with a backend for tracking service provider credits.

Retries

The retries-module manages the retry mechanisms. When messages fail to be delivered (e.g., due to absent subscribers or network errors), this module queues them for retrying at specified intervals. It supports various protocols (SMPP, HTTP and SS7) and uses Kafka for storing message lists and states, incorporating a WebSocket server for real-time monitoring.

SMPP Server

The smpp-server-module is designed for handling SMPP operations, managing the communication between the SMSC and external systems or service providers over the SMPP protocol. It provides a highly configurable SMPP server, integrates with Kafka for queue management, and includes WebSocket and JMX monitoring capabilities.

SMPP Client

The smpp-client-module establishes and maintains SMPP connections with external gateways, manages message submissions, and handles retries for undelivered messages. It interacts with Kafka for queue management and supports WebSocket communication for real-time interaction.

HTTP Server

The http-server-module manages HTTP-based communication. It handles HTTP requests, especially interactions with external systems such as service providers, integrating with Kafka for efficient queue management. It supports WebSocket for real-time communication, offers JMX, and uses thread pooling for optimization.

HTTP Client

The http-client-module serves as a client-side component responsible for managing outbound HTTP communication and handling retries for message delivery. It integrates tightly with Kafka for managing message queues and interacting with gateways and routing rules.

SS7 Client

The ss7-client-module is a crucial component specifically designed for handling SS7 (Signaling System No. 7) communications. This module facilitates the signaling and transport of messages between the SMSC and telecommunication networks, ensuring efficient and reliable message delivery.

Diameter

The diameter-module is an essential component designed to handle Diameter protocol communications. It is primarily used for online charging through OCS integration and for managing SMS over LTE flows, ensuring reliable and standards-compliant signaling within modern mobile networks.

Docker Deployment

Follow these instructions to quickly deploy the PAiCore SMSC ecosystem using Docker and Docker Compose.

1. Prerequisites

Docker Engine installed (v20.10.0 or higher).
Docker Compose installed (v2.0.0 or higher).
Minimum of 8GB RAM available for the host machine.

2. Deploying the Stack

Navigate to the directory where your docker-compose.yml file is located. This file defines all the necessary services including Kafka, Redis, PostgreSQL, and all SMSC modules.

Start the containers in detached mode:

docker-compose up -d

Verify that all services are running properly:

docker-compose ps

3. Admin Panel Access

Once the services are fully initialized, the SMSC Management Backend and Frontend will be accessible. Navigate to the Admin Panel in your web browser:

URL: http://localhost:8080 (or your server's IP address)

The default credentials are defined in the SMSC Management BE's compose configuration. By default they are set as:

Username: admin Password: admin

Access Full Documentation

For full operational manuals, and advanced routing configurations, please request access to our secure client portal.

Related Repositories

paicoretech/smsc paicoretech/smsc-routing-module

Release Notes

View All Releases →

Open Source Telecom Signaling

Delivering Ownership

Maximizing ROI & Margins

Free from Vendor Lock-in

Telecom Innovation

Our Core Network Portfolio

Messaging

SMSC

USSD Gateway

IP-SM-GW

SMSF-5G

Geolocation

GMLC

Geolocation API

E-SMLC Q4-26

LMF-5G Q4-26

Signaling

Diameter Routing Agent

jSS7-STP

Signaling Gateway

SCP-5G Q4-26

VAS Platforms

SDP

CNA

Top-up System

TAS

Resources & Knowledge Base

Open Source Hub

PAiCore SMSC

PAiCore SDP

PAiCore GMLC

Products Documentation

Knowledge Base

Evolution from SS7 to SIGTRAN

Understanding the 5G Location Management Function (LMF)

Mitigating SMS Spoofing in Modern Networks

Engineering Tools

Diameter Simulator

SS7 Simulator

SMPP Simulator

PAiCore SMSC

Introduction

Architecture

Core Services

DB Insert Data

SMSC Routing

Retries

SMPP Server

SMPP Client

HTTP Server

HTTP Client

SS7 Client

Diameter

Docker Deployment

1. Prerequisites

2. Deploying the Stack

3. Admin Panel Access

Access Full Documentation

Related Repositories

Release Notes