MOSIP Docs
LTS
LTS
  • Home
  • Overview
  • ID Lifecycle Management
    • ID Schema
    • Identifiers
  • ID Authentication
  • Privacy and Security
    • Data Protection
    • Keys
    • Privacy
  • Biometrics
    • ABIS
    • ABIS API
    • Biometric SDK
    • Biometric Devices
    • SBI
    • Biometric Image Specification
    • FTM
  • Partners
  • Modules
    • Pre-registration
      • Pre-registration User Guide
    • Registration Processor
    • Registration Client
      • Operator Onboarding
      • Registration Client User Guide
      • Registration Client Home Page
      • Registration Client Configuration
      • Registration Client UI Spec
    • Commons
    • ID Repository
    • Partner Management
    • Data Share
    • Packet Manager
    • WebSub
    • Resident Services
    • Administration
      • Admin Portal User Guide
    • ID Authentication Services
    • Reporting
    • Automation Testing
    • Storage
  • Deployment
    • Sandbox Deployment
    • Server Hardware Requirements
    • Country Implementation
    • Masterdata Guide
  • APIs
  • Community
    • Contributions
    • Code of Conduct
  • License
Powered by GitBook
On this page
  • Overview
  • Stages and services
  • Build and deploy
  • APIs
  • Configurations

Was this helpful?

  1. Modules

Registration Processor

PreviousPre-registration User GuideNextRegistration Client

Last updated 3 years ago

Was this helpful?

Overview

Registration Processor (Regproc) is a backend processing engine to enable the ID Lifecycle management. The diagram below shows the Registration Processor along with the other modules that contribute in issuing a Unique Identification Number(UIN) for an individual. Internally, Regproc follows the SEDA architecture where data flows via multiple stages till the UIN is issued.

The relationship of Regproc with other services is explained here. NOTE: The numbers do not signify sequence of operations or control flow

  1. Registration packets are uploaded by Registration Client to Packet Receiver.

  2. User pre-registration data is downloaded using the pre-registration datasync service.

  3. Quality of biometrics is checked using an external biometric SDK. This is done in Regproc's Quality Classifier stage.

  4. Regproc shares biometric data with ABIS and Manual adjudication System. The policy for sharing this data is fetched from PMS.

  5. The above data is shared by providing a URL that partners use to fetch data. This URL is obtained from Datashare service.

  6. Regproc's ABIS Middleware stage communicates with ABIS via Activemq. The ABIS performs deduplication and sends back result to the Q.

Stages and services

The Registration Processor contains several stages and services.

The registration packet flows through the various stages depending on the type of flow. Refer flows

Build and deploy

Refer to repo

APIs

Configurations

Refer to Configuration Guide