Roadmap 2025
Q1: January 2025 – March 2025
Q2: April 2025 – June 2025
Q3: July 2025 – September 2025
Q4: October 2025 – December 2025
Q1
Platform
JAVA 21 Migration - Final Phase of Implementation
🟠 In-progress
1.2.1.0
Q1
Platform/Biometrics
Biometric Quality Enhancement during Registration
🔵 Planned
- Enhance threshold setup for biometric on the region based / specific geographic
- Enhancing the calculation of biometrics
- Enabling system to capture best biometrics on every attempt
Q1
Registration Processor/Biometrics
Enhancing the quality classifier stage:
- Enabling SDK score to be default and process the SDK score in the backend
Q1
IDA
Support for ECC Algorithm during encryption & decryption
Q1
IDA
Support QR Code generation in IDA by sharing CWT
Q2
Registration Processor
Enhancing Manual Adjudication
1. Auto rejection when there is one to one match
2. When more gallery records are sent out for adjudication, system to be intelligent to remove the records which are not possible match
3. Restructure of MA request to accommodate 3 different data to compare
Q2
Registration Processor
Biometric Adaptive Learning
- Child UIN - Checking on updating biometrics of infant/child based on the age; if biometrics isn't updated by the mentioned age; notifying resident on the same and force block
- Store biometric exceptional details in UIN data
Q2
Platform
GraalVM Migration (R&D and Implementation)
Q2
Platform
Revising Error Messages - Phase 1
- Analysis on identifying Aligning error codes and error messages accordingly and updating the error messages with meaningful content
Q2
ID Repository
Array of Handle - Phase 2
- Support addition and deletion of handle value in array of handle feature
- Revocation of handle
- Modify notification service to send notification based on the tags
Q2
ID Authentication
Generating Analytic Metrics
1. Failed authentication & Categorizing the failures
Q3
ID Authentication
Biometric Quality Calculation Enhancement during Authentication
- Measuring the quality score
- Configuring threshold during deployment
- Validating quality of the captured biometric with threshold during authentication
Q3
Admin
Revamp on retrieval of AID
Q3
Registration Processor
Remodeling draft API creation
- Redesigning the draftAPI feature to enhance the feature utilization
Q3
Registration Processor
Update UIN using handle:
- Enabling system to use handle during the update UIN flow
Q3
ID Authentication
Age-Based Credential Attributes:
1. Dynamic Age Verification in Credentials: Implementing support for age attributes in Verifiable Credentials (VC) to enable real-time age-based validations, such as "is_above_18" or "is_above_65," based on the current date.
2. Integration with Wallet and Verified Claims: Ensuring seamless utilization of age attributes for Wallet-based verifications and claims to enhance user experience and compliance with age-specific requirements.
Q4
Platform/Notification Services
Revamping Notification Services (Phase 1)
1. Enabling notification more configurable:
- when a template is updated then new updated templates are fed to the system after the core code changes to wrap the new template
2. Retry sending notification
3. Sending email along with UIN card - currently this feature isn't available in core platform only print service has the facility to send the ID
Q4
Platform
Revising Error Messages - Phase 2
Modifying error codes and error messages accordingly and updating the error messages with meaningful content
Q4
Admin
General ID issuance features
Download PDF card:
- For a citizen, Administrator should be able to search and download card in PDF format.
- QR code standardization. - National ID details
Q4
ID Authentication & Registration Processor & Reg Client
Enabling IDA to deploy without MOSIP Components
Removal of IDA dependency from core MOSIP modules:
1. Operator authentication during onboarding
2. Parent/introducer validation
3. Operator/Supervisor validation during packet processing
Performance Improvement:
Q4
ID Authentication
- Analyse the performance of IDA
- Enhancing the performance
2025
Platform
Enhancement on Filter Algorithm: (Spike)
- Conducting R&D to understand the usage of Bloom filter
- Enabling system to support Bloom filter
2025
Platform
Infrastructure Enhancement: (Spike)
- Conducting R&D to understand the HSM adaptability to the system
- Enabling system to support Nitro HSM
2025
Registration Client
Metadata Enhancement:
Capturing Supervisor Details for the Analytics
2025
Registration Client
Enabling Custom Handles feature
2025
Registration Client
R&D for Morena Replacement
- Support for scanning document
- R&D On replacement for morena Library
2025
Platform (Admin & Reg Processor)
UI based packet reprocessing:
1. Role-Based Admin Portal Enhancements: Introduce a user-friendly interface in the admin portal, enabling authorized roles to reprocess packet statuses directly through the UI.
2. Failed Status Insights and Bulk Actions: Display detailed reasons for packet failure and provide functionality for bulk reprocessing to streamline recovery and error handling processes.
2025
Platform/IDA
Removal of file server dependency
2025
Registration Client
Infrastructure Enhancement:
Sarcose library to be replaced by opencv as sarcose occupies more memory and lowers the performance
2025
Registration Client
Enhancing file compression feature
- Research on the compression algorithm fits to MOSIP
- Introducing new file compression algorithm
2025
Registration Client
Email/Phone number Verification:
- During the registration, enabling immediate verification of email & phone number
2025
Dashboard
Device performance metrics:
- Some devices in the field may be capturing low quality biometrics and sending to server. creating a report in dashboard to measure and report
2025
Platform
Address Structure Management:
- Implementing Rule Engine
- Enabling system to adopt 2 child fields for one parent field
- Use case: country want to include a two child fields for a parent field
2025
Admin
Operator Login Methods:
Enabling login methods for operators through UI instead of updating through DB
2025
Platform
Consent-Based Event Notification Mechanism:
1. Consent-Driven Event Generation and Publishing: Implement an eventing mechanism that respects consent management protocols and adheres to regulatory requirements. Generate and publish events to notify relevant parties of key changes, ensuring compliance with local practices.
2. Subscriber and Response Management Framework: Enable subscribers to listen and respond to events in real-time, ensuring efficient communication across stakeholders (for example, loan updates). Include robust response management for tracking and acknowledgment of event-based notifications.
2025
ID Authentication
Code quality improvement
2025
Registration Processor
Enable configuration of demographic fields for Demo Duplication stage
2025
Registration Processor
Biometric Adaptive Learning
Adult UIN - if a country wants to update the biometrics of the adult on the regular interval, policy to be created for the same and update the biometrics (notification to be sent) -Wishlist
2025
Platform
UI based model for configuration
1. Enabling a UI based configuration model with detailed information
2025
Platform
System adaptation for refugees/stateless identities:
1. Including refugees, stateless individuals, or undocumented populations, as an option in addition to resident/non-resident. Can be used as dynamic fields
2025
Registration Processor
Efficient Print Management
- Probability of Bulk Printing based on the location/center. - check with Nambi on the new print stage
2025
Registration Client
Enabling Saving Draft during Registration
2025
Pre Registration
Enhancing Booking Appointment
1. enabling booking appointments for update & biometric correction in addition to new registration
2025
Platform
Revamping Notification Services (Phase 2)
1. Enabling Un-subscription feature.
2. Re-structuring the notification.
3. Identifying areas to include notification and implementing.
4. Notification to internal/external subscribed systems/partners - for example, when a resident updates their phone number, notification needs to be sent to respective partners (openCRVS) to keep them informed to carry out authentication (websub notification) respective partners
- View the packet status.
- Resume or pause processing packets.
Last updated