Skip to content

Voice Verification Use Case

This section describes a voice verification use case, as an example. The das-Peak service can receive queries for a registration or verification request. The enrollment and verification processes are explained below.

Enrollment

During the enrollment process, the customer is asked for an audio recording by reading a random phrase. This audio can be captured through the voice capture SDK provided by VERIDAS (available on iOS and Android platforms) or by other means. The reading of this phrase is done only once and takes a few seconds (about 5s).

Voice capture SDKs do not perform any communication process with third parties, but delegate the recorded content to the APP invoking the SDK. This allows das-Peak’s client to fully control the transfer of its customers' data from the mobile device to the back-end.

After that, the APP communicates the recorded audio to the das-Peak client middleware. This middleware communicates with the VERIDAS cloud to obtain the biometric vector of the new registered user.

Once the biometric vector is received, das-Peak’s client stores the customer biometric information in its database:

  • On the one hand, the biometric vector returned by das-Peak.
  • On the other hand, the registration audio itself. This will allow the biometric vector to be recalculated when improvements are made to the VERIDAS cloud biometric engine.
  • It is also necessary to save the hash of the biometric model used to generate the voice credential. This information is very useful to check if the voice credential needs to be updated.

A proposed architecture scheme for the biometric registration process is presented below.

Alt

Verification

The verification process can be carried out from customer’s mobile APP. As in the enrollment process, it is possible to use VERIDAS voice capture SDKs. After capturing and sending to the middleware the voice captured in the verification process, the client sends to the das-Peak cloud service the content captured during the verification, as well as the biometric vector of that user that was previously stored in the client database during the enrollment phase. When using the capture SDKs, it is necessary to add the calibration parameter "lossless audio" to optimize the result of the biometric comparison.

As a result of this operation, das-Peak returns to the middleware the result of the biometric comparison, obtaining a decimal value between 0 and 1. The higher the score, the greater the certainty to be the same person. A proposed architecture scheme for the biometric verification process is presented below.

Alt