Demonstrators

The Project so far has developed two demonstrators, exhibiting functionality dealing with user identity management and speaker verification.

The OCTAVE project delivered demonstrators based on the TBAS for internal testing, and for showing the progress of the different versions of the Platform. A demonstrator is currently available for two specific technologies:

  • an Android App to be installed on a smartphone or any other device with the same OS;
  • a Web Application for major browsers (currently, only Chrome and Firefox are supported).

Both demos allow an authorised application provider to enrol its own users. After successful enrolment, a user can access the voice biometrics demo and attempt to be recognized by means of his/her voice.

The entry point for accessing the demonstrator is a web page, as shown below. Upon selecting the “Android App”, an ‘apk file’ is downloaded for installatin on your Android device is downloaded. By selecting the “Web App” you are immediately redirected to the web demo page.

At the moment, demonstrators are only for use by OCTAVE Partners, and are not yet publicly available.demo-001

The demo can be described by this sequence of browser screenshots, showing:

  • a three-step enrolment process (to enable user authentication by his/her voice, by collecting three samples of  voice)
  • the login process (to have users login by means of their voice, instead of conventional means like passwords or tokens)
  • Accessing the System

    Accessing the System

    The Application Provider presents the log-on screen with its credentials to start the enrolment of a new user.

  • Enrolment: step 1 of 3

    Enrolment: step 1 of 3

    The new user provides a user-id and records a sentence.  The user can playback and listen to the recorded sentence, and then confirm with Next

  • Enrolment: step 2 of 3

    Enrolment: step 2 of 3

    The user provides his/her user-id and records a second sentence. The user can play and listen to the recorded sentence, and then confirm with Next.

  • Enrolment: step 3 of 3

    Enrolment: step 3 of 3

    The user provides his/her user-id and records a third (last) sentence. The user can playback and listen to the recorded sentence, and then confirm with Finish.  

  • User Enrolled in the System

    User Enrolled in the System

    The system confirms completion of enrolment. This means that a voice template for the new user has been created and safely stored. From now on, the user can access to the system.  

  • Enrolment completed

    Enrolment completed

    The system confirms completion of enrolment. The user confirms submission of data by pressing OK.  

  • User Login: identity claim

    User Login: identity claim

    The user declares his/her credential (claimed identity) using a personal ID.  

  • User Login: voice presentation

    User Login: voice presentation

    The user records a speech segment ("utterance") for logging in. The user can playback and listen to the recorded sentence, and then hit for Sign in

  • User Login: User Accepted

    User Login: User Accepted

    The user has been recognised by the TBAS as a the genuine speaker registered with the given UserId. The user sees the acceptance decision and hits OK to continue.

  • User Logged In

    User Logged In

    The user is welcome to the system/service

  • User Rejected

    User Rejected

    The user is not recognised as the genuine speaker and the system notifies its rejection decision.

The demo can be described by this sequence of smartphone screenshots, showing:

  • a three-step enrolment process (to enable user authentication by his/her voice, by collecting three samples of the user’s voice)
  • the login process (to have users login by means of their voice, instead of conventional means like passwords or tokens)

Atos Android demo

Atos Web App