Generation and distribution of named, definable, serialized tokens

Patent metadata

Field	Value
Publication number	US-9848064-B2
Application number	US-201514933231-A
Country	US
Kind code	B2
Filing date	Nov 5, 2015
Priority date	Nov 5, 2015
Publication date	Dec 19, 2017
Grant date	Dec 19, 2017

Abstract

A method for generating and distributing serialized tokens is provided. The method may include receiving a request from at least one client. The method may further include determining whether the received at least one request is a request for generating names and definitions for a group of serialized tokens, deleting a names and definitions, and/or receiving a group of serialized tokens. Additionally, the method may include enabling the at least one client to generate names and definitions for a group of serialized tokens. The method may also include storing the names and definitions on a server. The method may also include deleting the names and definitions from the server. The method may also include formatting and distributing serialized tokens based on the names and definitions for the serialized tokens. The method may further include sending a response to the client based on the received request.

First claim

What is claimed is:

1. A method for generating and distributing a plurality of serialized tokens, the method comprising:
receiving at least one request from at least one client;
determining whether the received at least one request is a request for generating at least one name and at least one definition for a group of serialized tokens;
in response to the determination that the received at least one request is a request for generating the at least one name and the at least one definition for the group of serialized tokens, enabling the at least one client to generate the at least one name and the at least one definition for the group of serialized tokens;
storing the generated at least one name and the generated at least one definition on at least one server;
determining whether the received at least one request is a request for deleting at least one second name and at least one second definition for a second group of serialized tokens;
in response to the determination that the received at least one request is a request to delete the at least one second name and the at least one second definition for the second group of serialized tokens, deleting the at least one second name and the at least one second definition for the second group of serialized tokens from the at least one server;
determining whether the received at least one request is a request for receiving the second group of serialized tokens based on the at least one second name and the at least one second definition;
in response to the determination that the received at least one request is a request for receiving the second group of serialized tokens, formatting and distributing the second group of serialized tokens based on the at least one second name and the at least one second definition; and
sending a response to the client based on the received at least one request.

2. The method of claim 1 , wherein the received at least one request comprises a plurality of data selected from a group comprising JavaScript Object Notation (JSON) data and Extensible Markup Language (XML).

3. The method of claim 1 , wherein the generated at least one definition comprises at least one counter to determine a sequence to distribute the group of serialized tokens.

4. The method of claim 1 , wherein the generated at least one name and the generated at least one definition comprises a plurality of symbols selected from a group comprising a plurality of numeric symbols and a plurality of non-numeric symbols.

5. The method of claim 1 , wherein formatting and distributing the second group of serialized tokens further comprises:
bookmarking a position of at least one counter to determine a next available serialized token associated with the second group of serialized tokens.

6. The method of claim 1 , wherein sending the response to the client comprises sending at least one of an indication that the generated at least one name and the generated at least one definition are generated and stored, a confirmation that the at least one second name and the at least one second definition for a second group of serialized tokens are deleted, at least one serialized token, and an error message.

7. The method of claim 6 , wherein the error message is selected from a group comprising an indication that a plurality of serialized tokens associated with the second group of serialized tokens do not remain, and an indication that a name associated with the group of serialized tokens is in use.

8. A computer system for generating and distributing a plurality of serialized tokens, comprising:
one or more processors, one or more computer-readable memories, one or more computer-readable storage devices, and program instructions stored on at least one of the one or more computer-readable storage devices for execution by at least one of the one or more processors via at least one of the one or more memories, wherein the computer system is capable of performing a method comprising:
receiving at least one request from at least one client;
determining whether the received at least one request is a request for generating at least one name and at least one definition for a group of serialized tokens;
in response to the determination that the received at least one request is a request for generating the at least one name and the at least one definition for the group of serialized tokens, enabling the at least one client to generate the at least one name and the at least one definition for the group of serialized tokens;
storing the generated at least one name and the generated at least one definition on at least one server;
determining whether the received at least one request is a request for deleting at least one second name and at least one second definition for a second group of serialized tokens;
in response to the determination that the received at least one request is a request to delete the at least one second name and the at least one second definition for the second group of serialized tokens, deleting the at least one second name and the at least one second definition for the second group of serialized tokens from the at least one server;
determining whether the received at least one request is a request for receiving the second group of serialized tokens based on the at least one second name and the at least one second definition;
in response to the determination that the received at least one request is a request for receiving the second group of serialized tokens, formatting and distributing the second group of serialized tokens based on the at least one second name and the at least one second definition; and
sending a response to the client based on the received at least one request.

9. The computer system of claim 8 , wherein the received at least one request comprises a plurality of data selected from a group comprising JavaScript Object Notation (JSON) data and Extensible Markup Language (XML).

10. The computer system of claim 8 , wherein the generated at least one definition comprises at least one counter to determine a sequence to distribute the group of serialized tokens.

11. The computer system of claim 8 , wherein the generated at least one name and the generated at least one definition comprises a plurality of symbols selected from a group comprising a plurality of numeric symbols and a plurality of non-numeric symbols.

12. The computer system of claim 8 , wherein formatting and distributing the second group of serialized tokens further comprises:
bookmarking a position of at least one counter to determine a next available serialized token associated with the second group of serialized tokens.

13. The computer system of claim 8 , wherein sending the response to the client comprises sending at least one of an indication that the generated at least one name and the generated at least one definition are generated and stored, a confirmation that the at least one second name and the at least one second definition for a second group of serialized tokens are deleted, at least one serialized token, and an error message.

14. The computer system of claim 13 , wherein the error message is selected from a group comprising an indication that a plurality of serialized tokens associated with the second group of serialized tokens do not remain, and an indication that a name associated with the group of serialized tokens is in use.

15. A computer program product for generating and distributing a plurality of serialized tokens, comprising:
one or more computer-readable storage devices and program instructions stored on at least one of the one or more computer-readable storage devices,

Assignees

• IBM

Inventors

• Dixon Bret W
• Horwood Benjamin T

Classifications

• G06F13/37

  using a physical-position-dependent priority, e.g. daisy chain, round robin or token passing · CPC title

• G06F21/335

  for accessing specific resources, e.g. using Kerberos tickets · CPC title

• H04L63/0807

  using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213) · CPC title

• G06F9/466

  Transaction processing · CPC title

• B65D83/12

  for tickets or tokens · CPC title