30.01.2015 Views

Picture Perfect 4.6 User Manual - UTCFS Global Security Products

Picture Perfect 4.6 User Manual - UTCFS Global Security Products

Picture Perfect 4.6 User Manual - UTCFS Global Security Products

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

170<br />

<strong>Picture</strong> <strong>Perfect</strong> <strong>4.6</strong><br />

<strong>User</strong> <strong>Manual</strong><br />

Here are the transactions in order with resulting current area after each:<br />

Table 77. Anti-passback example transactions<br />

Person/Badge<br />

Last Access<br />

Area<br />

Transaction<br />

Person/<br />

Badge<br />

Current<br />

Area<br />

Controller 1<br />

Person Area<br />

(Host Broadcast<br />

to Controllers)<br />

Controller 2<br />

Person Area<br />

(Host<br />

Broadcast to<br />

Controllers)<br />

Controller 1<br />

Person Area<br />

(Controller<br />

Requests<br />

from Host)<br />

Controller 2<br />

Person Area<br />

(Controller<br />

Requests from<br />

Host)<br />

Neutral Initial State Neutral Neutral Neutral Neutral Neutral<br />

Neutral<br />

Area A<br />

Area B<br />

Area C<br />

Badge at<br />

Reader 1,<br />

enters Area A<br />

Badge at<br />

Reader 3,<br />

enters Area B<br />

Badge at<br />

Reader 5,<br />

enters Area C<br />

Badge at<br />

Reader 7,<br />

enters Area A<br />

Area A Area A Area A Area A Neutral<br />

Area B Area B Area B Area A Area B<br />

Area C Area C Area C Area A Area C<br />

Area A Area A Area A Area A Area C<br />

Nested APB Configurations<br />

The following APB configurations are supported:<br />

<strong>Global</strong> Nested APB - Host Broadcasts to Controllers<br />

The current area status of a badge is synchronized across all relevant controllers on a server (for<br />

example, in an Enterprise system at a subhost, but not to the nethost or other subhost controllers).<br />

On all valid APB legacy and nested transactions (VALID_APB_IN, VALID_APB_OUT,<br />

PASSIVE_APB_IN, PASSIVE_APB_OUT, VALID_NESTED_APB, PASSIVE_NESTED_APB,<br />

FAIL_SAFE) that occur, all controllers (except dial-up) that know the badge and have at least one<br />

Host Broadcasts to Controllers type, <strong>Global</strong> Nested APB reader are notified of the Current Area of<br />

the badge.<br />

<strong>Global</strong> Nested APB - Controller Requests from Host<br />

When <strong>Global</strong> Nested APB is configured to Controller Requests from Host, every controller requests<br />

the “Current Area” for the person the badge belongs to (since the person's current area may have<br />

been set from a different badge on that person) from the host for each nested APB transaction that is<br />

about to occur before evaluating access, when the badge is presented to a reader.<br />

This approach has the least overhead at the host, but incurs longer wait times on badge learn<br />

transactions at a Nested APB reader.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!