Rusguard ACS#
Software integrations of Rusguard ACS with biometric systems are implemented to ensure the passage of recognized persons through the turnstile.
The service replicates employees from the ACS to its database by requesting the descriptor ID in the CBS based on the employee's photo. To update the data, the replication session is restarted 5 seconds after completion.
- Supports versions: System - 3.3.1, Database - 3.3.1
Supported integration options for Rusguard ACS#
The face recognition device generates an event, Access passes the event to LP5, LP5 processes the event and returns the result to Access for further processing.
Transfer of user data from ACS to LP5 occurs using replication - the mechanism for the initial transfer of user data.
For the replication settings, see the service settings.
Each integration with LP5 (Table 52) uses the Luna service.
If the terminal does not have data output facilities (e.g., a screen), the SendToDevice pipeline is not required.
Table 52. LP5 integration options
Each integration with CBS (Table 53) uses the CBS service.
Table 53. CBS integration options
Standard integration using Rusguard#
When integrating with Rusguard, standard Access components (Figure 89) and (Table 54) are used.
Table 54. Integration description
| Component | Description |
|---|---|
| Person | A person wishing to pass through a passage point. |
| Passage point | A set of components used to control human access. |
| Video data source | A device for extracting a frame of a person's face. It can be either a biometric terminal (LUNA FAST 4A1 and others) or a camera connected via FaceStream (then the LunaStreams service is required). |
| Turnstile | A barrier device for restricting access. |
| Rusguard ACS | Central software for working with Rusguard. Stores employee data and makes a decision on granting access. |
| Rusguard service | An Access component for sending requests and processing data from the ACS. |
| Device | An Access component for receiving data from a video data source. |
| Controller | Access point control board. |
| SendCardToR20Face Pipeline | Access Component for data exchange with ACS |
| BS Service | Access Component for interaction with BS: for LP5 it is Luna, for CBS - the corresponding CBS service. |
| MatchByPhoto Pipeline | Access Component for interaction with BS. When working with a biometric terminal, it is necessary to additionally connect the SendToDevice pipeline |
| Biometric System | A system for comparing a reference photo of a person and the best frame received from a video data source. Can be either Luna or supporting KBS. |
| Storage | A database within Access for storing information about employees. |
Methods of interaction with Rusguard#
An API is used тo exchange data with the ACS (Table 55).
Table 55. Rusguard methods
| Task | Method | Description |
|---|---|---|
| Get card types | GET /GetCardTypes | Get card types in ACS. Used to check the connection with ACS |
| Get information about employee photos | GET /GetAcsEmployeePhotoInfos | Get information about employee photos in ACS |
| Get a list of employee groups | GET /GetAcsEmployeeGroups | Get a list of employee groups in ACS |
| Get a list of employees from a group | GET /GetAcsEmployeesInGroup | Get a list of employees from a group in ACS |
| Get an employee photo by ID | GET /GetPhotoEmployee?PersonGuidId= employee_id&photoNumber=photo_number | Get employee photo in base64 format by his/her ID |
Diagram of interaction between Rusguard ACS and Access#
Sequence diagram (Figure 90).
1․ The user added the Rusguard service to Access. 2․ Access sends a GET /GetCardTypes request to obtain card types in the ACS, to check the connection. 3․ The ACS returns an array of card_types. 4․ Access sends a GET /GetAcsEmployeePhotoInfos request to obtain information about the availability of employee photos and the dates of their last changes in the ACS. 5․ The ACS returns an array of photos. 6․ Access sends a GET /GetAcsEmployeeGroups request to obtain a list of employee groups in the ACS. 7․ The ACS returns an array with group data (ID and group name). 8․ Access sends a GET /GetAcsEmployeesInGroup request to get employees from a group, for each group from the previous request. 9․ ACS returns an array with data for each employee. 10․ Access checks if the employee photo is out of date 11․ Access sends a GET /GetPhotoEmployee?PersonGuidId=employee_id&photoNumber=photo_number request to get a photo for each employee from the previous request, where:
- employee_id - employee identifier
- photo_number - photo number in ACS
12․ ACS returns a response with an employee photo in base64 format for each employee. 13․ Access saves employee data to the storage.
Diagram of interaction between Access and the biometric system#
Sequence diagram (Figure 91).
1․ An employee at the biometric terminal at the checkpoint. 2․ The terminal sends the best shot of the employee to Access. 3․ Access sends a photo of the employee to the Biometric System. 4․ The BS compares the photo from the terminal and the one stored in the database. 5․ The BS returns to Access a decision on granting access. 6․ Access sends a signal to the controller to open the access point.