# US 11,310,216 B2 · Apparatus and method for predictive token validation > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,310,216 B2 - Document ID: US11310216B2 - Status: Granted - Kind: B2 - Application number: 15/929,965 - Filed: 2020-05-31 - Published: 2020-09-17 - Granted: 2022-04-19 - Earliest claimed: 2017-03-01 - Assignees: Futurewei Technologies, Inc. - Applicants: Futurewei Technologies, Inc. - Inventors: Karun Kumar Chennuri - Web page: https://patentgrep.com/patent/US11310216B2 ## CPC - H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)} - G06F 21/41: where a single sign-on provides access to a plurality of computers - G06F 21/604: {Tools and structures for managing or administering access control systems} - H04L 63/0815: {providing single-sign-on or federations} - H04L 63/102: {Entity profiles} - H04W 12/06: Authentication - H04W 12/08: Access security - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract An apparatus and method are provided for predictive token validation. In use, a database stores service usage information relating to usage of at least one service hosted by at least one server. Before at least one request for service is received from a user at the at least one server, the service usage information in the database is accessed. Further, based on the service usage information, a token associated with the user is sent to the at least one server for being validated by the at least one server, such that the at least one server allows access to the at least one service by the user, in response to the at least one request for service being received from the user with an identifier that is different from the token. ## Claims ### Claim 1 A processing device, comprising: a non-transitory memory comprising instructions; and one or more processors in communication with the memory, wherein the one or more processors execute the instructions to: before receiving a request for service from a user device with an identifier, receive a token that is different from the identifier, the token identifying a combination of the user device and service usage information, the service usage information relating to past usage by the user device of a service hosted by a server; validate the token based on the combination and based on a prediction that the user device will access the service; after validating the token, receive the request for service from the user device; and permit access to the service by the user device, in response to the request for service from the user device and based on validating the token. ### Claim 2 (depends on 1) The processing device of claim 1, wherein the identifier includes a universally unique identifier (UUID). ### Claim 3 (depends on 1) The processing device of claim 1, wherein the service usage information identifies the user device and the service. ### Claim 4 (depends on 1) The processing device of claim 1, wherein the service usage information identifies a time associated with the user device. ### Claim 5 (depends on 1) The processing device of claim 1, wherein the service usage information identifies a location associated with the user device. ### Claim 6 (depends on 1) The processing device of claim 1, wherein the service usage information further relates to a user role associated with a user of the user device during the past usage. ### Claim 7 (depends on 1) The processing device of claim 1, wherein the one or more processors execute the instructions to: receive another request for service from the user device in connection with another service hosted by the server; in response to the another request for service from the user device, determine whether the token has been validated in connection with the another service; and if it is determined that the token has not been validated in connection with the another service, sending the identifier for requesting the token so that the token can be validated. ### Claim 8 (depends on 1) The processing device of claim 1, wherein the prediction is generated using the service usage information. ### Claim 9 (depends on 1) The processing device of claim 1, wherein the token includes an indication of the service hosted by the server. ### Claim 10 (depends on 9) The processing device of claim 9, wherein the one or more processors execute the instructions to: validate the token based on the service in the indication matching the service identified by the request. ### Claim 11 A computer-readable medium storing computer instructions for performing token validation within a communication network, wherein the instructions when executed by one or more processors of a computing device within the communication network, cause the one or more processors to: before receiving a request for service from a user device with an identifier, receive a token that is different from the identifier, the token identifying a combination of the user device and service usage information, the service usage information relating to past usage by the user device of a service hosted by a server; validate the token based on the combination and based on a prediction that the user device will access the service; after validating the token, receive the request for service from the user device; and permit access to the service by the user device, in response to the request for service from the user device and based on validating the token. ### Claim 12 (depends on 11) The computer-readable medium of claim 11, wherein the identifier includes a universally unique identifier (UUID). ### Claim 13 (depends on 11) The computer-readable medium of claim 11, wherein the service usage information identifies at least one of: the user device and the service; a time associated with the user device; and a location associated with the user device. ### Claim 14 (depends on 11) The computer-readable medium of claim 11, wherein the service usage information further relates to a user role associated with a user of the user device during the past usage. ### Claim 15 (depends on 11) The computer-readable medium of claim 11, wherein the prediction is generated using the service usage information. ### Claim 16 (depends on 11) The computer-readable medium of claim 11, wherein the token includes an indication of the service hosted by the server. ### Claim 17 (depends on 16) The computer-readable medium of claim 16, wherein the instructions further cause the one or more processors to: validate the token based on the service in the indication matching the service identified by the request. ### Claim 18 A computer-implemented method, comprising: before receiving a request for service from a user device with an identifier, receiving a token that is different from the identifier, the token identifying a combination of the user device and service usage information, the service usage information relating to past usage by the user device of a service hosted by a server; validating the token based on the combination and based on a prediction that the user device will access the service; after validating the token, receiving the request for service from the user device; and permitting access to the service by the user device, in response to the request for service from the user device. ### Claim 19 (depends on 18) The computer-implemented method of claim 18, wherein the identifier includes a universally unique identifier (UUID). ### Claim 20 (depends on 18) The computer-implemented method of claim 18, wherein the service usage information identifies at least one of: the user device and the service; a time associated with the user device; and a location associated with the user device.