Nokia Mediation Migration
Nokia Mediation offers modern billing mediation for digital telcos. It reliably collects and refines usage data and delivers it to OSS/BSS systems (billing, fraud management, revenue assurance etc.) in real-time.
Case Details
Period: March 2023 – December 2024
Tags: Telecom, Mediation
Project Duration: 12+ months
Let’s Work Together
Call us directly, submit a sample or email us!
The Story
Nokia Mediation offers modern billing mediation for digital telcos. It reliably collects and refines usage data and delivers it to OSS/BSS systems (billing, fraud management, revenue assurance etc.) in real-time. 1000+ off-the-shelf interfaces enable fast and vast data integration. It comes with Reports module, which provides extended support for operational reports.
The existing MQTT/EMI system, operating on Eventlink (Legacy Nokia Mediation version) R7.2.1, is currently active and fully functional, facilitating MQTT data collection and EMI streams. This infrastructure supports the generation and availability of performance management reports for the Hytera EMI/MQTT network. However, Eventlink R7.2.1 has reached the end of its support lifecycle. Therefore, extended support and an upgrade to version R22 are essential to maintain full SLA compliance and ensure uninterrupted service continuity in the coming years.
The Challenges
The migration strategy for upgrading to Nokia Mediation (NM) R22 involves deploying the new system alongside the existing Eventlink (EL current) solution to enable a non-zero downtime (NZDT) migration. This parallel deployment allows for thorough verification by comparing outputs from both systems before fully transitioning to the new solution.
Software Requirements:
• Operating System upgrade.
Solution Requirements:
• No changes to current functional/non-functional requirements for EMI/MQTT streams;
• Functional behavior should remain unchanged post-upgrade.
Integration requirements include:
• Pancras (Paging) and Semafonie via SFTP/CSV integration;
• HiveMQ MQTT broker (Hytera) using MQTT over TCP/TLS integration;
• Reporting DB using JDBC over TCP.
Alarm Management Change:
• Event management and alarm dispatcher modules are no longer available in NM22, requiring re-engineering of alarm management.
Migration Steps
1. Resource Setup – Define and allocate vResources and vLANs for NM R22.
2. Instance Deployment – Instantiate NM R22 (VM1-3) and configure streams.
3. Southbound Integration – Connect NM R22 to southbound systems.
4. Northbound Integration – Integrate NM R22 with ReportDB and add a temporary DB schema for data storage and verification.
5. Validation Period – Compare stream outputs between EL current and NM R22 for consistency.
6. Transition Completion – Disable EL current streams, flush data, and fully switch to NM R22 after successful validation.
Key Assumptions
C2000 counter information can be collected simultaneously by both systems with minor configuration changes.
Additional Considerations
- The plan assumes that NM R22 can operate alongside EL current without major infrastructure changes.
This phased approach ensures a controlled migration with minimal disruption and thorough validation before full deployment.
This plan ensures that the upgraded system maintains operational integrity while addressing current hardware, software, and performance needs.