Parsec ACS#
Supports ParsecNET 3 ACS version: 3.11.629 39.
Интеграция возможна только в режиме 2ф, где первый фактор (карта) происходит на стороне СКУД, а второй фактор (лицо) поступает от Access.
The service allows you to process requests from access control systems, such as:
- transfer the list of employees to the local person storage,
- adding/editing/deleting employees in the local person storage,
- receiving detection events from devices.
The service executes the following requests to the ACS:
- sending url address of ONVIF services;
- getting access point IDs.
When starting the service, access point identifiers are first requested and their names are generated.
The ACS queries Access for detections and generates a response containing the employee ID and the access point ID.
As soon as a valid face detection occurs, the service returns a response to the ACS.
To integrate with Parsec, you must specify the names of access points automatically generated by the service in the device settings. They are generated in the format 'access point name - identifier'. For example: 'Turnstile exit - 907EFA78-CB2F-4F46-b374-785c7f9901a5'
The resulting access point names must be inserted into the appropriate fields:
- When using internal Access devices (HikvisionTerminal, Panda ...), indicate in the "name" field.
- When using LunaStream, indicate in the "source" field.
Supported integration options for Parsec 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 the ACS to LP5 occurs using two mechanisms:
- replication - the mechanism for the initial transfer of user data;
- synchronization - the mechanism for periodic transfer of user data when the composition/data of users changes.
For the synchronization/replication settings, see the service settings.
Each integration with LP5 (Table 45) uses the Luna service.
If the terminal does not have data output facilities (e.g., a screen), the SendToDevice pipeline is not required.
Table 45. LP5 integration options
Each integration with CBS (Table 46) uses the CBS service.
Table 46. CBS integration options
| Service | Device | Pipeline |
|---|---|---|
| CbsMts + Parsec | Beward | MatchByPhoto + SendToDevice + SendToParsec |
| Dahua | MatchByPhoto + SendToParsec | |
| HikvisionCamera | MatchByPhoto + SendToParsec | |
| LunaFast4A1 | MatchByPhoto + SendToDevice + SendToParsec | |
| UniUbi | MatchByPhoto + SendToDevice + SendToParsec |
Standard integration using Parsec#
When integrating with Parsec, standard Access components (Figure 77) and (Table 47) are used.
Table 47. 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. More than one passage point can be connected, limited by the ACS license. A passage point can be used for both entry and exit. Each direction uses its own reader and video data source. |
| Controller | Passage point control board. |
| Turnstile | A barrier device for access control |
| Parsec ACS | Central software for working with Parsec. Stores employee data and makes decisions about granting access. |
| SendToParsec Pipeline | Access component for exchanging data with ACS |
| Parsec Service | Access component for processing information from the ACS |
| MatchByPhoto pipeline | Access component for interaction with the BS. When working with a biometric terminal (for displaying messages and photos on the screen), it is necessary to additionally connect the SendToDevice pipeline |
| SendToController pipeline | Access component for interaction with the CBS |
| Video 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 LunaStream. |
| Device ... | Access component for receiving data from a video data source. It is selected based on the device used. |
| Biometric system | A system for comparing a reference photo of a person and the best frame received from a video data source. It can be either Luna or CBS MTS. |
Configuring Access and Parsec ACS integration#
To launch and configure the Parsec ACS software, install Parsec.NET and run the Administration program and check the settings (Figure 78):
1․ Make sure that the ""Advanced Mode"" is running (File→Advanced Mode).
2․ Go to the “Equipment editor” section and make sure that the controllers are connected .
3․ For each required controller, set the following settings in the “Access Modes” tab (Figure 79).
4․ Go to the “System settings editor” section, then open the “Face Recognition (ONVIF)” tab (Figure 80).
5․ In the “Face recognition (ONVIF)” window, click the “Change” button and make sure that the “Use FRS” item is enabled, and the “FRS type” is set to “ONVIF face recognition”.
6․ In the “IP Address” and “Port” fields, enter the Access server data.
The IP address of all components must point to the Access server.
7․ Click the “Check connection” button only after configuring Access, this will require the “Integration key”.
8․ After clicking on the “Check connection” button, the fields in the “Face recognition system services” block will be filled in automatically.
9․ Click the “Save” button.
10․ Replicate employees to the Luna list by clicking the “Transfer employees and visitors” button. Before, make sure that all staff members are correctly added in the "Staff Editor" section, see «Adding staff to Parsec ACS»
Example of displaying staff member unloaded from Parsec ACS to LUNA PLATFORM list (Figure 81).
Configuring access groups in Parsec ACS#
1․ Click the «Access group editor» section.
2․ Add a new access group.
3․ Add an access territory where the access points are included (Figure 82).
4․ Click the Save button.
Adding staff to Parsec ACS#
Adding staff members to Parsec ACS is necessary for their subsequent upload to LUNA PLATFORM (Figure 83).
1․ Click the «Staff Editor» section.
2․ Click the button of adding a new staff member.
3․ Fill in the «Last Name» and «First Name» fields.
4․ Add a photo of the staff member.
5․ Fill in the «Card code» field. The «PIN» field will be filled in automatically.
If card access is not provided at the facility or the staff member does not have a card, enter any value in the «Card code» field.
6․ Select the staff member's access group.
7․ Click the Save button.
If you add staff members correctly, all new or changed data will be added to the LUNA PLATFORM database automatically.
Methods of interaction with Parsec#
Access acts as a server and a client (Table 48).
Sending ONVIF methods to Access occurs at the POST endpoint /vl-access/webhook/service/onvif/{component_id}.
Table 48. Parsec methods
| Task | Method | Description |
|---|---|---|
| Get access points | POST /onvif/ accesscontrol | Request to ACS. Getting access point (controller) IDs for manual matching of cameras/terminals and access points |
| Get a list of ONVIF services | POST /onvif/ device_service | Getting a list of component_id ONVIF Access services for connection |
| Create user | CreateCredential | ONVIF method |
| Update user | ModifyCredential | ONVIF method |
| Delete user | DeleteCredential | ONVIF method |
| Create subscription | CreatePullPoint Subscription | ONVIF method. Subscribe to events. |
| Get detection events | PullMessages | Receiving an employee detection event. The request is sent every 10 seconds and waits 10 seconds until a frame appears. |
Parsec interaction process diagrams#
Connecting the Parsec service#
Sequence diagram (Figure 84).
1․ The user added the Parsec service to Access. 2․ Access sends a request to the ACS to obtain access points. The obtained access points are displayed in the info field of the service properties. The request is used to check the availability of the ACS. 3․ The ACS returns the access points. 4․ The ACS sends a request to Access to obtain a list of Access services that support the ONVIF protocol. 5․ Access returns the component_id of the ONVIF services. 6․ The ACS sends a POST /vl-access/webhook/service/onvif/{component_id} CreateCredential request to Access to transfer employees to the Access repository. 7․ Access sends a request with employee photos to the BS to retrieve descriptor_id (face_id). 8․ The BS returns descriptor_id. 9․ Access saves information on each employee to local storage. 9․ The ACS sends a request to Access to open a subscription to receive events (the best shots of a person at the terminal).
Parsec event processing with 2 factors#
Sequence diagram (Figure 85).
1․ ACS sends a POST /vl-access/webhook/service/onvif/{component_id} PullMessages request every 10 seconds to wait for a passage event. 2․ Access receives the best photo of the employee at the terminal. 3․ Access sends a photo of the employee to the Biometric System. 4․ BS compares the photos from the terminal and the one saved in the database. 5․ BS returns to Access a decision on granting access. 6․ Access returns a passage event to ACS. 7․ ACS makes a decision on opening the terminal.