| REVISION CONTROL RECORD | |||
|---|---|---|---|
| VER | DATE | DESCRIPTION OF CHANGE | AUTHOR |
| 0.1 | 08/03/2016 | Initial draft | J. Evenson |
| 0.2 | 04/10/2017 | Added CTE device | J. Everson |
| 0.3 | 06/16/2017 | Added Denali | T. Anfield |
| 0.4 | 03/21/2018 | Added CHM block | T. Anfield |
| 0.5 | 6/19/2018 | Cleaned up Title and Headers for ENGAGE 6.1 Release | T. Holt |
| 0.6 | 9/19/2018 | Added NDE 1.1 and LE 1.1 Numbers | J. Evenson |
| 0.7 | 10/26/2018 | Added Control 1.1 and Topaz Numbers | J. Evenson |
| 0.8 | 12/21/2018 | Added note to use SN code in FW package headers | J. Evenson |
Table 1: Serial Number Byte Definition 5
Table 2: Serial Number Device ID Definition 5
Revision History ii
List of Tables iii
Table 1: Serial Number Byte Definition 5
Table 2: Serial Number Device ID Definition 5
Table of Contents iv
1.0 Introduction 5
1.1 Serial Number 5
Appendix A: Abbreviations and Acronyms 6
The purpose of this document is to provide a record of the Serial Number coding for all ENGAGE enabled products as well as other devices which may utilize ENGAGE or ENGAGE related services in the future.
The lock serial number is 16 bytes of hexadecimal information. The first 8 bytes are 0x00’s and are reserved for future use. In ENGAGE, the next two bytes act as an identifier to distinguish between devices in the Neptune architecture. The values defined for the Device Type are shown in Table 4. Development serial numbers have been reserved in the Device Type for future use. The first byte identifies the device as a development device, and the second byte identifies the device type. The device type for a development unit is the first byte for the device type production SN. For example, development NDE serial numbers will have 0xA0A1 as the device type, and production NDE serial numbers will have 0xA100 as the device type. The last 6 bytes are the Device ID. The Device ID is set by the production facility and is the serial number printed on the device label.
The following Serial Number Device Type values are also to be used in the Engage FW Package header for the model value in FW and Package header.
| Serial Number | |||
|---|---|---|---|
| Padding (0x00) | Device Type | Device ID | Total |
| 8 | 2 | 6 | 16 Bytes |
| Device Type | Value |
|---|---|
| Development | 0xA0yy |
| Production | 0xyy00 |
| Product | yy |
| NDE Wireless Lock | A1 |
| NDE 1.1 Wireless Lock | A2 |
| Engage Gateway | B1 |
| Engage Enrollment Reader (MT20) | C1 |
| Engage Enrollment Reader with Wi-Fi (MT20W) | C2 |
| Trident Module | D1 |
| Jaguar Lock | E1 |
| Control 1.1 Lock | E2 |
| Marlin(LE) Lock | F1 |
| LE 1.1 Lock | F2 |
| Raven(EVO) IP Reader | 01 |
| Argos Exit Device | 11 |
| CTE Controller | 21 |
| Denali Lock | 31 |
| CHM - reserved | 40 |
| CHM – CISA | 41 |
| CHM - reserved | 42-4F |
| Topaz - BLE Wall Mount Reader | 50 |
| Abbreviation/ Acronym | Definition |
|---|---|
| AES | Advanced Encryption Standard |
| CBC | Cipher Block Chaining |
| CNTR | Counter variable stored in the AppToken |
| CRI | Cryptography Research Inc. |
| DUID | Device Identifier of mobile hardware |
| FDR | Factory Default Reset |
| FW | Firmware |
| IV | Initialization Vector |
| MGR | Defines the access rights of this user to the lock. |
| PEK | Production Encryption Key |
| SK | Site Key |
| S/N | Serial Number |
| TempK | Temporary Encryption Key |
| USRID | User Identifier of logged in user |