# US 2017/0287243 A1 · Entry control system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0287243 A1
- Document ID: US20170287243A1
- Status: Published application
- Kind: A1
- Application number: 15/485,274
- Filed: 2017-04-12
- Published: 2017-10-05
- Earliest claimed: 2003-12-22
- Assignees: Assa Abloy AB
- Applicants: Assa Abloy AB
- Inventors: Dominique Louis Joseph Fedronic; Wu Wen
- Web page: https://patentgrep.com/patent/US20170287243A1

## CPC

- G07C 9/27: with central registration
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 63/10: {for controlling access to devices or network resources}
- G07C: TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

An integrated security system which seamlessly assimilates with current generation logical security systems. The integrated security system incorporates a security controller having standard network interface capabilities including WEE 802.x and takes advantage of the convenience and security offered by smart cards and related devices for both physical and logical security purposes. The invention is based on standard remote authentication dial-in service (RADIUS) protocols or TCP/IP using SSL, TLS, PCT or IPsec and stores a shared secret required by the secure communication protocols in a secure access module coupled to the security controller. The security controller is intended to be a networked client or embedded intelligent device controlled remotely by to an authentication server. In another embodiment of the invention one or more life cycle management transactions are performed with the secure access module. These transactions allow for the updating, replacement, deletion and creation of critical security parameters, cryptographic keys, user data and applications used by the secure access module and/or security token. In another embodiment of the invention a security access module associated with the security controller locally performs local authentication transactions which are recorded in a local access list used to update a master access list maintained by the authentication server.

## Claims

### Claim at position 1

1-36. (canceled)

### Claim 37

A method for physically controlling access to a protected location, comprising:
establishing a secure communications connection over a network between a security controller and an authentication server;
operatively coupling a security token to the security controller;
providing a critical security parameter to the security controller for authentication after using a token remote authentication application on the security token to verify the critical security parameter against one or more reference critical security parameters;
sending the critical security parameter to the authentication server via the secure communications connection;
performing an authentication transaction at the authentication server for the critical security parameter;
sending a result of the authentication transaction from the authentication server to the security controller via one of: the secure communications connection or the security token; and
energizing an electromechanical circuit coupled to and controlled by the security controller if the result of the authentication transaction is successful.

### Claim 38 (depends on 37)

The method according to claim 37 wherein the security controller and electromechanical circuit are in one integral unit.

### Claim 39 (depends on 37)

The method according to claim 37 wherein the secure communications connection includes a shared secret established between the security controller which is securely maintained by a secure access module operatively coupled to the security controller.

### Claim 40 (depends on 37)

The method according to claim 37 wherein the security controller is one of a plurality of security controllers, wherein the plurality of security controllers are networked clients of the authentication server.

### Claim 41 (depends on 37)

The method according to claim 37 wherein at least a portion of the secure communications connection is established over a wireless telecommunications link.

### Claim 42 (depends on 37)

The method according to claim 37 wherein the secure communications connection incorporates a security protocol including SSL, IPsec, PCT, TLS or RADIUS.

### Claim 43 (depends on 37)

The method according to claim 37 wherein the security controller is in secure communications over the network with a life cycle management server.

### Claim 44 (depends on 43)

The method according to claim 43 wherein the life cycle management server is adapted to perform life cycle management functions related to applications, critical security parameters or user data installed in either the security token or the secure access module.

### Claim 45 (depends on 37)

The method according to claim 37 wherein the critical security parameter is provided by the user and the one or more reference critical security parameters are operatively stored on the security token.

### Claim 46 (depends on 37)

The method according to claim 37 wherein the secure communications connection incorporates a shared secret which is maintained by the authentication server and the security controller.

### Claim 47

A method for physically controlling access to a protected location, comprising:
providing one or more critical security parameters to a security controller for authentication after using a token remote authentication application on a security token to verify a critical security parameter against one or more reference critical security parameters;
performing one or more authentication transactions using the one or more critical security parameters;
temporarily maintaining a local access list of the one or more critical security parameters which have been authenticated;
sending the local access list to an authentication server;
updating a master access list maintained by the authentication server; and
energizing an electromechanical circuit coupled to and controlled by the security controller if a result of the one or more authentication transaction is successful.

### Claim 48 (depends on 47)

The method according to claim 47 wherein the local access list is sent to the authentication server via a secure communications channel.

### Claim 49 (depends on 47)

The method according to claim 47 wherein the local access list is sent over an IEEE 802.x standard network arrangement.

### Claim 50 (depends on 47)

The method according to claim 47 wherein the secure communications connection includes a shared secret established between the security controller which is securely maintained by a secure access module operatively coupled to the security controller.

### Claim 51 (depends on 47)

The method according to claim 47 wherein the security controller is one of a plurality of security controllers, wherein the plurality of security controllers are networked clients of the authentication server.

### Claim 52 (depends on 47)

The method according to claim 47 wherein at least a portion of the secure communications connection is established over a wireless telecommunications link.

### Claim 53 (depends on 47)

The method according to claim 47 wherein the secure communications connection incorporates a security protocol including SSL, IPsec, PCT, TLS or RADIUS.

### Claim 54 (depends on 47)

The method according to claim 47 wherein the security controller is in secure communications over the network with a life cycle management server.

### Claim 55 (depends on 54)

The method according to claim 54 wherein the life cycle management server is adapted to perform life cycle management functions related to applications, critical security parameters or user data installed in either the security token or the secure access module.

### Claim 56 (depends on 47)

The method according to claim 47 wherein the critical security parameter is provided by the user and the one or more reference critical security parameters are operatively stored on the security token.

### Claim 57 (depends on 47)

The method according to claim 47 wherein the secure communications connection incorporates a shared secret which is maintained by the authentication server and the security controller.
