Skip to content

Tapkey Lock Control Protocol

The Tapkey Lock Control Protocol (TLCP) defines how entities within Tapkey communicate with each other.

Examples

Trigger Lock

The following sequence diagram shows a simplified overview of the execution of a trigger lock command.

Trust ServiceMobile AppUserLockLock ID, KeyU, enc_L(KeyU), enc_L(CertU), enc_L(RCL)Persist dataUser initiates trigger lockConnectHello Message: Lock ID, rclSerialNo, Nonce(C), current timestampSet clockDirect tunnel via HTTPSopt[ Sync lock time ]Get access logAccess logopt[ Get access log ]enc_L(CertU), enc_L(KeyU)enc_U(CMD)Calculate signaturesig_U(C, KeyU, enc_U(CMD))Verify signatureExecute commandAcknowledgement, Access logAccess logTrust ServiceMobile AppUserLock

Legend

Lock ID := l ⟶ The lock's identification (ID).

KeyU := k_{u} ⟶ The user's symmetrical encrypting and signing key, for example, abc123.

CertU := c_{u} ⟶ The user's certificate.

RCL := (r_{1}, r_{2}, r_{3}) ⟶ The lock's revocation control list.

enc_L := E_{l}(x) ⟶ Function encrypting parameter x using the lock's master key.

sig_U := S_{u}(x) ⟶ Function signin x using the user's symmetrical key.