Server-Coordinated Anti-Passback Across Multiple Access Controllers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing anti-passback systems are limited in their ability to enforce anti-passback functions across multiple access controllers in large office buildings, as they can only control a few doors and lack the capability to manage routes between multiple access controllers.
Innovation Solution
A server-connected anti-passback method that communicates with multiple access controllers to determine valid routes for door opening requests, ensuring compliance with preset lists of routes and updating reader and controller identifiers to maintain accurate records.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If access controllers are used to implement anti-passback functions, then anti-passback control can be achieved for doors under their control, but the system can only manage a limited number of doors and cannot achieve anti-passback across multiple access controllers in large office buildings
Solution Approach 1:
The system is divided into multiple access controllers, each managing a subset of doors. Each access controller maintains an anti-passback record for its local doors, while a server coordinates anti-passback validation across multiple controllers. This segmentation allows the system to scale to large office buildings with numerous doors and controllers while maintaining manageable local complexity at each controller.
Solution Approach 2:
A server acts as an intermediary between multiple access controllers to coordinate anti-passback validation. When a cardholder swipes at a door controlled by one access controller, the system checks anti-passback records not only at that controller but also at other controllers through the server. This intermediary enables cross-controller anti-passback enforcement without requiring each controller to directly manage all doors in the building.
2Adaptability or versatility
If route lists are configured in access controllers to enforce anti-passback rules, then route compliance can be monitored, but the route list is limited to routes between a few doors under one controller
Solution Approach 1:
Route information is segmented and distributed across multiple access controllers and the server. Each access controller stores route lists relevant to its local doors, while the server maintains a comprehensive view of all routes across the entire building. This segmentation allows route information to be complete building-wide while keeping local storage requirements manageable.
Solution Approach 2:
Route lists are pre-configured and stored in advance in both the server and relevant access controllers. When anti-passback validation is needed, the system performs preliminary checks against these pre-stored route lists rather than calculating routes in real-time. This preliminary action enables fast validation while maintaining comprehensive route information across the distributed system.
Data Source
Figure 1~2
Figure 3~4
Figure 5~7
AI summary
Embodiments of the present application disclose an anti-passback method, apparatus and system. A plurality of access controllers are communicatively connected to a server. After detecting that a card reader has successfully read an identifier of an access card, an access controller sends the identifier of the access card, an identifier of the card reader, and its own identifier to the server. The server searches for the identifier of the card reader that read the access card last time, and the identifier of the access controller corresponding to the card reader, and determines a route for the door opening request. When the determined route exists in a preset list of routes, the sever sends a door opening instruction to the access controller. The route list may include routes between doors under the control of the plurality of access controllers. When a user swipes on a card reader on any of the doors with an access card, the access controller that controls the card reader will transmit information to the server. The server determines whether to allow the passing based on the route list. As can be seen, such solution achieves the anti-passback feature among a plurality of access controllers.