# ABIS

### Overview

Providing unique identity for a resident is one of key features of any identity platform. To achieve this, MOSIP interfaces with an **Automated Biometric Identification System (ABIS)** to perform de-duplication of a resident's biometric data.

MOSIP is designed to integrate with multiple ABISs to leverage expertise of different ABIS providers. A country may use one ABIS for fingerprint and another for Iris or use multiple ABISs for the same biometric data and evaluate the best ABIS based on de-duplication quality.

The ABIS system never comes to know about resident's identity. Any Personally Identifiable Information (PII) such as demographic details or RID (Request ID for Registration) is not shared with the ABIS system. Internally, MOSIP maintains a mapping between the ABIS specific referenceID and RID of the resident.

{% hint style="info" %}
ABIS is used for 1:N de-duplication. For 1:1 authentication [Biometric SDK](https://docs.mosip.io/1.1.5/biometrics/biometric-sdk) is used. MOSIP does not recommend using an ABIS for 1:1 authentication.
{% endhint %}

![](https://306789431-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1R77ZUwR6XwtPjJIVm%2Fuploads%2Fgit-blob-695d7b5f1c972ad7584e381f4172f52f481c80d2%2Fabis_middleware.png?alt=media)

### ABIS middle-ware

MOSIP's ABIS middle-ware has the following components

* MOSIP ABIS request handler
* Request router (based on routing policy, an ABIS request is routed to the correct ABIS system)
* ABIS response handler

Below is the MOSIP ABIS middle-ware process flow,

![](https://306789431-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1R77ZUwR6XwtPjJIVm%2Fuploads%2Fgit-blob-245acb9a78421004c8f13353a643576d8028ae22%2Fabis_middleware-process_flow.png?alt=media)

### MOSIP-ABIS interface

MOSIP interacts with ABIS only via message queues. JSON format is used for all control messages in the queue. MOSIP ABIS middle-ware sends requests to inbound queue address and receives responses from outbound queue address. For details refer to the [ABIS API Specifications](https://docs.mosip.io/1.1.5/apis/abis-apis).

ABIS must support the following types of biometric images:

* Individual fingerprint images (segmented)
* Iris images (left, right)
* Face image

Biometrics data in MOSIP is exchanged as per formats defined in [Biometric Specification](https://docs.mosip.io/1.1.5/biometrics/biometric-specification).

### ABIS deployment

* ABIS must comply to [ABIS API Specifications](https://docs.mosip.io/1.1.5/apis/abis-apis).
* The queues can be configured in [RegistrationProcessorAbis-env.json](https://github.com/mosip/mosip-config/blob/master/config-templates/RegistrationProcessorAbis-env.json) file.
* ABIS system connects to the queues using a pre-defined user id and password.
* It is recommended that ABIS is deployed in a secure zone (military zone).
* ABIS system is not recommended to connect to any external network.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.mosip.io/1.1.5/biometrics/automated-biometric-identification-system-abis.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.