New AI Features Notes

New Features

Control Center 3.5.5

Hello all, In a few days we hope to make an internal release for our new amazing firmware...There are a lot of new cool stuffs and I think that you guys (especially US team) should be familiarized in advanced with them. In this email I would like to show you how these new features are reflected in Control Center.

You can find a new CC (3.5.5) in Idrive Downloads section. There is also a new Idrive Player (3.5.10) able to play a new format of our existing events + 3 new types of events: - face recognized event (extension .137) - face unrecognized event (.136) - safe distance warning event (.135)

Facial Recognition

As you can easily deduce, the face recognized event is trigger when a driver is recognized by camera, a face unrecognized event is triggered when the camera is unable to recognize the driver for an amount of time and the safe distance warning event is triggered when the vehicle is following too close other vehicle (the front vehicle). However, the face unrecognized event is not implemented yet in the firmware and it will be available in a future version.

Below is a small description about how the facial recognition is implemented from the Control Center's point of view. In a future email I will explain in detail how the camera is making the recognition (with some help from Idrive Cloud).

From the CC perspective the facial recognition is very similar with the driver key identification. The corespondent of the driver key is a global unique identification field (I will name it "guid") automatically generated by CC when a driver is added in the system (the existing drivers have this field). As you can imagine, this field is synced together with the other driver's fields, so Idrive Cloud (this is a better term for Global Center or GC) also knows the guid for each driver.

If you want to learn more about guid (or uuid), take a look at: https://en.wikipedia.org/wiki/Universally_unique_identifier

During the facial recognition process, the Idrive Cloud is sending the guid of the recognized driver to the camera. The camera is triggering the "face recognized" event and it is also placing the guid in all next events and in the gps file (just as it does with the driver key).

The recognition process in CC is also similar with the driver key identification: during the transfer, the CC is searching the guid field in all events / gps files and placing the recognized driver, like below:

Events & Reviews:

(the yellow icon notify the user that the driver has been identified during the facial recognition process).

Gps data and the map:

There is also a small change in Fleet Manager (see the driving side field from the image below):

The driving side field is uploaded on the camera during the Wi-Fi transfer and it is used by the camera in order to identify the position of the driver. "Middle" option should be used for inter-modal clients when only one person can appear in the image (usually a small vehicle or a cabin).

And now the cool stuff: Take a look at the attached event. You have 2 options to play it:

- with Idrive Player (not recommended): when the event is loaded, click on the video->click on "Face recognition info"

- with CC (recommended): make sure that your location belongs to Idrive Inc Company (not Demo Idrive or other), use Import Viewer->Browse and Import immediately; go to Events&Reviews section, play the event and click on the face pictogram (see below)