Method of managing token and server for performing the same
A method of managing a token and a server for performing the same are provided. According to the embodiments of the present disclosure, it is possible to easily authenticate a counterpart device using a one-time key H N (T) for a D2D communication between a first device and a second device, without using a separate secure channel (e.g., secure sockets layer (SSL), transport layer security (TLS), or the like) in an environment where it is difficult to synchronize the first device with the second device without intervention of a server.
1. A server comprising:
at least one hardware processor configured to implement:
a token manager configured to:
generate, upon receiving an policy, a key token associated with a validity period, and
obtain a plurality of first hash values by hashing the key token a number of times up to a maximum count;
a first device manager configured to transmit the plurality of first hash values and information about the maximum count to a first device; and
a second device manager configured to transmit an initial hash value of the key token and the information about the maximum count to a second device,
wherein the token manager is further configured to, based on at least one of the validity period, a value of the maximum count, and the policy: discard either or both of the key token and the maximum count.
2. The server of claim 1 , wherein the first device manager is further configured to transmit the plurality of first hash values to the second device one by one in a reverse order of a generation of the plurality of first hash values, and
wherein the token manager is further configured to:
receive, when a value of a first maximum count stored at the first device is smaller than or equal to a set value and the validity period is more than a set period, a request from the first device to update the key token and the first maximum count, and to update the key token and the first maximum count at the first device in response to the request for update.
3. The server of claim 2 , wherein the token manager is further configured to: receive a request from the first device to discard the key token, and discard the key token in response to the request.
4. The server of claim 1 , wherein the token manager is further configured to discard the key token when a current time indicates that the validity period is expired.
5. The server of claim 1 , wherein the at least one hardware processor is further configured to implement: a policy manager configured to receive the policy, wherein the token manager is further configured to update, when the policy received by the policy manager is changed, either or both of the key token and the maximum count.
6. The server of claim 1 , wherein the first device manager is further configured to receive, from the first device, information about a first maximum count stored at the first device, and
wherein the second device manager is further configured to receive, from the second device, information about a second maximum count stored at the second device, and wherein the token manager is further configured to compare the first maximum count with the second maximum count to determine whether a hash code synchronization has completed successfully.
7. A method of managing a token, comprising:
generating, at a token manager upon receiving an policy, a key token associated with a validity period;
obtaining, by the token manager, a plurality of first hash values by hashing the key token a number of times up to a maximum count;
transmitting, by a first device manager, the plurality of first hash values and information about the maximum count to a first device;
transmitting, by a second device manager, an initial hash value of the key token and the information about the maximum count to a second device; and
discarding, by the token manager based on at least one of the validity period, a value of the maximum count, and the policy, either or both of the key token and the maximum count.
8. The method of claim 7 , wherein: the transmitting by a first device manager further comprises:
transmitting the plurality of first hash values to the second device one by one in a reverse order of generation of the plurality of first hash values, deleting, after transmitting an Nth first hash value among the plurality of first hash values, the Nth first hash value, and wherein the discarding by the token manager comprises receiving a request from the first device to update the key token and the maximum count, and updating the key token and the maximum count at the first device in response to the request for update.
9. The method of claim 8 , wherein the discarding by the token manager further comprises: receiving a request from the first device to discard the key token, and discarding the key token.
10. The method of claim 7 , wherein the discarding by the token manager comprises discarding the key token when the validity period is expired.
11. The method of claim 7 , further comprising:
after the transmitting by the second device manager: receiving, by the first device manager from the first device, second information about a first maximum count stored at the first device;
receiving, by the second device manager from the second device, third information about a second maximum count stored at the second device; and
comparing, at the token manager, the first maximum count with the second maximum count to determine whether a hash code synchronization has completed successfully.
12. A method of managing a token, comprising:
generating, at a token manager upon receiving an policy, a key token associated with a validity period;
obtaining, by the token manager, a plurality of first hash values by hashing the key token a number of times up to a maximum count;
transmitting, by a first device manager, the plurality of first hash values and information about the maximum count to a first device;
transmitting, by a second device manager, an initial hash value of the key token and the information about the maximum count to a second device; and
updating, by the token manager based on at least one of the validity period, a value of the maximum count, and the policy, either or both of the key token and the maximum count, wherein a server comprises the token manager, the first device manager, the second device manager, and a policy manager.
13. The method of claim 12 , further comprising receiving, prior to the generating of the key token at the token manager, an policy, wherein the updating by the token manager comprises updating either or both of the key token and the maximum count when the policy received by the policy manager is changed.