Systems and methods for a credential including multiple access privileges

• US 10,572,645 B2
• Filed: 12/05/2017
• Issued: 02/25/2020
• Est. Priority Date: 06/02/2014
• Status: Active Grant

• Current Assignee: Schlage Lock Company LLC (Allegion PLC)
• Original Assignee: Schlage Lock Company LLC (Allegion PLC)
• Inventors: Eberwine, Todd, Beene, Donald L., Sharp, Daniel R., Vickrey, Michelle
• Primary Examiner(s): Savusdiphol, Paultep
• Application Number:
  US15/832,206
• Publication Number:
  US 20180225441A1
• Time in Patent Office: 812 Days
• Field of Search: 235380, 235382, 2353825, 235492
• CPC Class Codes: G06F 21/34 involving the use of external additional devices, e.g. dongles or smart cards
• CPC Class Codes: G06F 2221/2113 Multi-level security, e.g. mandatory access control
• CPC Class Codes: G07C 9/00 Individual registration on entry or exit
• CPC Class Codes: G07C 9/20 involving the use of a pass
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/0853 using an additional device, e.g. smartcard, SIM or a different communication terminal cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04W 12/068 using credential vaults, e.g. password manager applications or one time password [OTP] applications
• CPC Class Codes: H04W 12/08 Access security

Abstract

A credential for use in an access control system may include a first sector including first data of a first database type, and a second sector including second data of a second database type. The credential may further include a third sector including third data related to the second data. The first database type and the second database type may be different types.

Claims

1. A credential for use in an access control system, comprising:

a first sector including first data of a first database type;

a second sector including second data of a second database type that is different from the first database type; and

a third sector including third data.

2. The credential of claim 1, wherein the second data further includes a look-up table for the third data stored in the third sector.

3. The credential of claim 2, wherein the third data includes access privileges for a user.

4. The credential of claim 3, wherein the access privileges include the fields of a personal identification number (PIN), function, user type, activation, deactivation and door/group identifier.

5. The credential of claim 1, wherein the second data includes a facility code and a unique identifier (UID) for a user.

6. The credential of claim 5, wherein the second data further includes a replacement UID.

7. The credential of claim 1, wherein the first data includes access privileges for a user.

8. The credential of claim 1, wherein a first lock is configured to read the first data of the first database type, wherein a second lock is configured to read the second data of the second database type, wherein the first lock is not configured to read the second data of the second database type, and wherein the second lock is not configured to read the first data of the first database type.

9. The credential of claim 1, wherein the third sector includes a plurality of sub sectors;

and

wherein each subsector of the plurality of subsectors includes a first set of access privilege data and a second set of access privilege data; and

wherein each of the first set of access privilege data and the second set of access privilege data is arranged by fields associated with an indication of whether a personal identification number is required.

10. The credential of claim 1, wherein the first sector includes fields associated with an application type, interface data, and binary-coded decimal data.

11. The credential of claim 10, wherein the binary-coded decimal data comprises a site code and a badge identification.

12. The credential of claim 10, wherein the interface data includes Wiegand interface data.

13. The credential of claim 1, wherein the second data includes user data that is arranged by fields associated with a facility code, a badge identifier, an extended unlock delay, a replacement badge identifier, and an expiration date of the replacement badge identifier.

14. A method, comprising:

reading, with a first lock, first data of a first database type from a first sector of a credential; and

reading, with a second lock, second data of a second database type from a second sector of the credential, the second database type being different from the first database type, and the second data including a look-up table for third data stored in a third sector of the credential.

15. The method of claim 14, wherein the first lock cannot read data from the second sector, and wherein the second lock cannot read data from the first sector.

16. The method of claim 14, further comprising authenticating the credential based on the first data of the first database type;

and

authenticating the credential based on the second data of the second database type.

17. The method of claim 14, wherein the first database type is an access database and the second database type is a void database.

18. A credential card for use in an access control system, the credential card comprising:

a memory having stored thereon an access permission data structure that includes;

a first sector including first data of a first database type accessible by a first reader device to authenticate the credential card; and

a second sector including second data of a second database type that is different from the first database type and accessible by a second reader device to authenticate the credential card but inaccessible to the first reader device.

19. The credential card of claim 18, wherein the first database type is an access database and the second database type is a void database.

20. The credential card of claim 18, wherein a first lock is configured to read the first data of the first database type and not configured to read the second data of the second database type;

and

wherein a second lock is configured to read the second data of the second database type and not configured to read the first data of the first database type.