Systems and methods for a credential including multiple access privileges

• US 9,870,460 B2
• Filed: 06/02/2015
• Issued: 01/16/2018
• 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 Lee, Sharp, Daniel R., Vickrey, Michelle
• Primary Examiner(s): Savusdiphol, Paultep
• Application Number:
  US14/728,508
• Publication Number:
  US 20150347729A1
• Time in Patent Office: 959 Days
• Field of Search: 235382, 235380, 2353825, 235492, 726 5, 726 7, 726 9
• 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 he different types.

Claims

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

a first sector, a second sector, and a third sector;

wherein the first sector includes first data and is associated with a first database type;

wherein the second sector includes second data and is associated with a second database type different from the first database type, the second data including user data and a look-up table that references data stored in the third sector based on at least one of a group/door identifier or a sector number; and

wherein the third sector includes access privilege data for a user arranged by fields associated with an indication of whether a personal identification number is required, a personal identification number, a credential function type, an activation date of the access privilege, an expiration date of the access privilege, and a door/group identifier.

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

3. The credential of claim 2, wherein the second data further includes a replacement UID.

4. 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.

5. The credential of claim 1, wherein the credential is a card credential.

6. The credential of claim 1, wherein the credential is a smartphone.

7. The credential of claim 1, wherein the third section includes a plurality of subsectors;

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 the fields associated with the indication of whether a personal identification number is required, the personal identification number, the credential function type, the activation date of the access privilege, the expiration date of the access privilege, and the door/group identifier.

8. The credential of claim 7, wherein the credential function type identifies one of a normal use credential, a toggle credential, a freeze credential, or a pass-through credential.

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

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

11. The credential of claim 9, wherein the interface data includes Wiegand interface data.

12. The credential of claim 1, wherein the user data of the section sector 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.

13. A method, comprising:

reading, with a first lock, first data from a first sector of a credential, wherein the first sector is associated with an access database;

reading, with a second lock, second data from a second sector of the credential, wherein the second sector is associated with a void database; and

reading, with the second lock, third data from a third sector of the credential based on the second data; and

wherein the first database type and the second database type are different.

14. The method of claim 13, wherein the first lock cannot read data from the second or third sectors, and wherein the second lock cannot read data from the first sector.

15. The method of claim 13, wherein the second data further includes a look-up table for the third data stored in the third sector.

16. The method of claim 15, wherein the third data includes access privileges for a user.

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

18. 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; and

a third sector including third data related to the second data; and

wherein the second data further includes a look-up table for the third data stored in the third sector;

wherein the third data includes access privileges for a user;

wherein the access privileges include the fields of a personal identification number (PIN), function, user type, activation, deactivation, and door/group identifier;

wherein the second data includes a facility code and a unique identifier (UID) for the user; and

wherein the first database type and the second database type are different.

19. The credential of claim 18, wherein the credential is a plastic card credential.

20. The credential of claim 18, wherein the credential is a smartphone.