Cipia Vision Ltd.
–
Proprietary & Confidential
Page 20 of 38
▪
Private ID
–
T
he Driver’s ID assigned by the DMS library upon successful
enrollment. This is the ID that is reported by the DMS upon successful driver
identification to the main application.
▪
Face-
ID ‘features vector file’
–
Generated by the DMS library upon
successful enrollment. This file is also reported to the server side, upon
successful enrollment procedure, for later remote driver enrollment into
other installed Cipia-FS10 devices within the fleet operation.
▪
Permission State
–
The permission state:
•
0
–
Blacklist (Unauthorized)
•
1
–
Whitelist (Authorized)
•
2
–
Recognized
–
default permission in case not predefined
A closed enrollment loop means that both the Cipia-FS10 device and the Fleet
management DB hold the global driver ID, the permission state, and the vector file per
each enrolled driver.
When a driver is enrolled from the mobile app, the following flow is supported:
1.
Installer inserts the driver’s license number (Global
Driver ID).
2.
Installer performs the enrollment process in the mobile app.
3.
Installer app uploads the driver license number (Global Driver ID), the photo
and the features vector file, at the end of the installation/enrollment
process, as part of the Installation report data structure.
When a driver is enrolled while seated in the vehicle, through a backend command, the
following flow is supported (this is also applicable when enrolling drivers in the office):
1.
Server sends command to the device with the assigned Global ID and permission
state (this process is only done when the vehicle engine is running and there is a
sync between the driver and the operator) to enroll a new driver.
2.
Once the command is received and executed successfully, Cipia-FS10 sends
the driver’s image (
photo), and the features vector file back to the server.
3.
The FMS app retrieves the image and vector files to close the loop.
When the FMS app enrolls an already enrolled driver, into other vehicles:
1.
Per vehicle (Cipia-FS10 device), the middleware API is called with the Global ID
number, vector file and permission status. This process is not necessarily done
when the vehicle engine is running, and the device might therefore be unavailable
for a period.