| Crates.io | bss-oss-server |
| lib.rs | bss-oss-server |
| version | 0.2.5 |
| created_at | 2025-11-16 21:27:47.923239+00 |
| updated_at | 2025-11-19 18:51:54.270479+00 |
| description | BSS/OSS Rust ecosystem server application |
| homepage | |
| repository | https://github.com/rabbittrix/BSS-OSS-Rust-Ecosystem.git |
| max_upload_size | |
| id | 1935932 |
| size | 116,816 |
🌍 A high-performance, memory-safe BSS/OSS ecosystem in Rust, fully compliant with TM Forum Open APIs (TMF). Built for telecom operators who need interoperability, safety, and performance.
BSS (Business Support Systems) and OSS (Operations Support Systems) are critical software platforms for telecommunications companies. They handle:
This project provides a complete, production-ready implementation of TM Forum's standardized APIs, enabling seamless integration between different telecom systems.
✅ 17 TM Forum APIs Implemented:
✅ Production-Ready Features:
sqlx✅ Memory Safety: Rust's compile-time guarantees prevent common bugs that could lead to billing errors or security vulnerabilities.
# Clone the repository
git clone https://github.com/rabbittrix/BSS-OSS-Rust-Ecosystem.git
cd BSS-OSS-Rust-Ecosystem
# Start PostgreSQL and the application
docker-compose up -d
# Or run manually
cargo run --release --bin bss-oss-rust
// The server automatically starts with all TMF APIs enabled
// Access Swagger UI at: http://localhost:8080/swagger-ui/
// Example: Create a product catalog
curl -X POST http://localhost:8080/tmf-api/productCatalogManagement/v4/catalog \
-H "Authorization: Bearer <your-token>" \
-H "Content-Type: application/json" \
-d '{
"name": "5G Services Catalog",
"description": "Catalog for 5G service offerings",
"version": "1.0.0",
"lifecycle_status": "ACTIVE"
}'
This is a Cargo workspace with modular crates:
bss-oss-rust/
├── crates/
│ ├── tmf-apis/ # Individual TMF API implementations
│ │ ├── core/ # Shared models and error types
│ │ ├── tmf620_catalog/
│ │ ├── tmf622_ordering/
│ │ └── ... (17 total APIs)
│ ├── server/ # Main application server
│ ├── pcm-engine/ # Product Catalog Engine
│ └── utils/ # Common utilities
└── migrations/ # Database schema migrations
All APIs follow TM Forum Open API standards and are accessible via REST:
| API | Endpoint | Description |
|---|---|---|
| TMF620 | /tmf-api/productCatalogManagement/v4 |
Product catalog management |
| TMF622 | /tmf-api/productOrderingManagement/v4 |
Product order management |
| TMF637 | /tmf-api/productInventoryManagement/v4 |
Product inventory tracking |
| TMF629 | /tmf-api/customerManagement/v4 |
Customer profile management |
| TMF678 | /tmf-api/customerBillManagement/v4 |
Customer billing |
| TMF679 | /tmf-api/customerUsageManagement/v4 |
Usage records (CDRs) |
| TMF688 | /tmf-api/appointmentManagement/v4 |
Appointment scheduling |
| TMF641 | /tmf-api/serviceOrderingManagement/v4 |
Service order management |
| TMF638 | /tmf-api/serviceInventoryManagement/v4 |
Service inventory |
| TMF640 | /tmf-api/serviceActivationAndConfiguration/v4 |
Service activation |
| TMF702 | /tmf-api/resourceActivationAndConfiguration/v4 |
Resource activation |
| TMF639 | /tmf-api/resourceInventoryManagement/v4 |
Resource inventory |
| TMF645 | /tmf-api/resourceOrderingManagement/v4 |
Resource order management |
| TMF635 | /tmf-api/usageManagement/v4 |
Usage management |
| TMF668 | /tmf-api/partyRoleManagement/v4 |
Party role management |
| TMF632 | /tmf-api/partyManagement/v4 |
Party management |
| TMF669 | /tmf-api/identityManagement/v4 |
Identity & credential mgmt |
http://localhost:8080/swagger-ui/ (when server is running)Contributions are welcome! This project aims to be a community-driven implementation of TM Forum standards.
This project is licensed under the MIT License - see the LICENSE file for details.
Roberto de Souza - rabbittrix@hotmail.com
Built with ❤️ in Rust for the telecom industry