Secure identity binding (SIB)
First Claim
1. A method comprising:
- receiving, through a short range communication channel, an identifier from a tag associated with a device;
communicating the identifier from the tag to the device in response to the receiving;
responsive to the identifier from the tag matching an identifier stored in the device, receiving, from the device, a verification of the identifier from the tag; and
responsive to the identifier from the tag being different from the identifier stored in the device, receiving, from the device, a notification that the device is being placed in a hold state.
2 Assignments
0 Petitions
Accused Products
Abstract
A system includes a tag having a machine readable tag identifier (Tag ID) configured to be read by a reader; and a device to be identified by the tag, in which: the device is configured to communicate with the reader; the device has access to a secure Tag ID; and the device communicates a verification to the reader if the machine readable Tag ID communicated to the device from the reader matches the secure Tag ID. A method includes: reading a Tag ID from a tag attached to a device; communicating the Tag ID read from the tag to the device; comparing a secure Tag ID of the device to the Tag ID read from the tag; and responding with a “match” or “no-match” message from the device, according to which the device is either trusted or not trusted as being identified by the Tag ID. A method of verifying a trusted agent (TA) on a device includes: storing a digital signature of the TA in a secure vault of the device; and verifying the TA by verifying the digital signature of the TA each time the TA is used.
37 Citations
20 Claims
-
1. A method comprising:
-
receiving, through a short range communication channel, an identifier from a tag associated with a device; communicating the identifier from the tag to the device in response to the receiving; responsive to the identifier from the tag matching an identifier stored in the device, receiving, from the device, a verification of the identifier from the tag; and responsive to the identifier from the tag being different from the identifier stored in the device, receiving, from the device, a notification that the device is being placed in a hold state. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A mobile device system, comprising:
-
a non-transitory memory storing an identifier; and one or more hardware processors coupled to the non-transitory memory and configured to read instructions from the non-transitory memory to cause the system to perform the steps of; receiving, through a short range communication channel, the identifier from a tag associated with a device; communicating the identifier from the tag to the device in response to the receiving; responsive to the identifier from the tag matching the identifier stored in the non-transitory memory, receiving, from the device, a verification of the identifier from the tag; and responsive to the identifier from the tag being different from the identifier stored in the non-transitory memory, receiving, from the device, a notification that the device is being placed in a hold state. - View Dependent Claims (11, 12, 13, 14, 15, 16, 17, 18)
-
-
19. A system comprising:
-
a first device including; a communication application installed on the first device that accesses an identifier from a tag associated with a second device and stores a verification of the identifier from the tag associated with the second device, and a non-transitory memory comprising the identifier from the tag associated with the second device and the verification; and a communication interface, the communication interface configured to; receive, through a short range communication channel, the identifier from the tag associated with the second device; communicate the identifier from the tag to the second device in response to receiving the identifier from the tag; responsive to the identifier from the tag associated with the second device matching an identifier stored in a memory of the second device, receive, from the second device, the verification of the identifier from the tag associated with the second device; and responsive to the identifier from the tag associated with the second device being different from the identifier stored in the memory of the second device, receive, from the second device, a notification that the second device is being placed in a hold state. - View Dependent Claims (20)
-
Specification