# US 2012/0254943 A1 · Methods for controlling a traffic of an authentication server

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0254943 A1
- Document ID: US20120254943A1
- Status: Published application
- Kind: A1
- Application number: 13/436,118
- Filed: 2012-03-30
- Published: 2012-10-04
- Earliest claimed: 2011-03-31
- Assignees: Hangzhou H3C Technologies Co., Ltd.
- Inventors: Wei Li
- Web page: https://patentgrep.com/patent/US20120254943A1

## CPC

- H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)}
- H04L 47/215: using token-bucket
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 63/1458: {Denial of Service}
- H04W 12/12: Detection or prevention of fraud
- H04L 63/0876: {based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A method for controlling the traffic of an authentication server and an authentication access apparatus, wherein a local area network token bucket including a high priority token bucket and a low priority token bucket is set according to the capability of the authentication server in processing the request message, and the request message sent by the authentication client is redirected to the authentication server after allocating a token to the authentication client, thus the traffic of the authentication server is controlled, so that the authentication server will not receive more request messages than it can handle. Meanwhile, the tokens in the high priority token bucket are reserved specially for authentication clients of a high priority, and they cannot be used by authentication clients that are not of a high priority, so the quality of service for authentication clients of a high priority is improved.

## Claims

### Claim 1

A method for controlling a traffic of an authentication sever, said method comprising:
setting a local area network token bucket including a high priority token bucket and a low priority token bucket for a local area network, wherein the number of tokens in said local area network token bucket is equal to or less than the number of request messages which can be processed by the authentication server;
detecting whether an authentication client in said local area network that sends a request message is of a high priority or not;
allocating a token from the high priority token bucket to the authentication client that sends the request message and redirecting the request message to the authentication server, when the authentication client has been detected to be of a high priority;
allocating a token from the low priority token bucket to the authentication client that sends the request message and redirecting the request message to the authentication server, when the authentication client has been detected to be not of a high priority; and
recovering the allocated token after a successful authentication of the authentication client that sends the request message.

### Claim 2 (depends on 1)

The method as claimed in claim 1, wherein said local area network comprises more than one sub local area network;
the setting a local area network token bucket including a high priority token bucket and a low priority token bucket for the local area network further comprising:
setting a sub local area network token bucket corresponding respectively to each sub local area network in the local area network token bucket; and
setting a high priority token bucket and a low priority token bucket in each sub local area network token bucket, wherein the number of tokens in the high priority token bucket is not more than the number of the authentication clients which are configured to have the high priority in the sub local area network, and the sum of the numbers of tokens in the high priority token bucket and the low priority token bucket is equal to the number of tokens in the sub local area network token bucket.

### Claim 3 (depends on 2)

The method as claimed in claim 2, wherein the detecting whether an authentication client that sends a request message in said local area network is of a high priority or not further comprises:
detecting which sub local area network the authentication client that sends the request message belongs to and the priority of the authentication client;
when the authentication client has been detected to be of a high priority, determining the sub local area network token bucket corresponding to the sub local area network to which the authentication client that sends the request message belongs before allocating a token, and taking the high priority token bucket in the sub local area network token bucket as the token bucket for allocating tokens;
when the authentication client has been detected to be not of a high priority, determining the sub local area network token bucket corresponding to the sub local area network to which the authentication client that sends the request message belongs before allocating a token, and taking the low priority token bucket in the determined sub local area network token bucket as the token bucket for allocating tokens; and
when the authentication client has been detected to be not of a high priority, discarding the request message if there is no token in the token bucket for allocating tokens.

### Claim 4 (depends on 3)

The method as claimed in claim 3, wherein said setting a high priority token bucket and a low priority token bucket in each sub local area network token bucket further comprises: setting one high priority token bucket and more than two low priority token buckets in each sub local area network token bucket, wherein different low priority token buckets correspond to authentication clients which are configured to have different levels of low priorities in the sub local area network, and the sum of the numbers of tokens in the high priority token bucket and in all the low priority token buckets is equal to the number of tokens in the sub local area network token bucket; and
said taking a low priority token bucket in the determined sub local area network token bucket as the token bucket for allocating tokens further comprising: searching the determined sub local area network token bucket for a low priority token bucket which corresponds to the level of the authentication client that sends the request message and taking the found low priority token bucket as the token bucket for allocating tokens.

### Claim 5 (depends on 4)

The method as claimed in claim 4, wherein when the authentication client has been detected to be not of a high priority, and if there is no token in the token bucket for allocating tokens, then first judging whether there is a token in other low priority token buckets whose level is lower than that of the token bucket for allocating tokens, if yes, then preempting one token from said other low priority token buckets for the authentication client that sends the request message and redirecting the request message to the authentication server, otherwise, discarding the request message.

### Claim 6 (depends on 5)

The method as claimed in claim 5, wherein when there is a token in said other low priority token buckets, further judging whether the number of tokens preempted from said other low priority token buckets has reached a set threshold, if yes, discarding the request message; otherwise, preempting one token from said other low priority token buckets.

### Claim 7 (depends on 3)

The method as claimed in claim 3, wherein while the setting sub local area network token buckets corresponding respectively to each the sub local area network in a local area network token bucket, further setting a shared token bucket in the local area network token bucket, wherein the, sum of the numbers of tokens in each of said sub local area network token buckets and in said shared token bucket is equal to the number of tokens in said local area network token bucket; and
before said discarding the request message, further judging whether there is a token in said shared token bucket, if yes, allocating one token from the shared token bucket to the authentication client that sends the request message and redirecting the request message to the authentication server, otherwise, discarding the request message.

### Claim 8 (depends on 3)

The method as claimed in claim 3, wherein said detecting which sub local area network the authentication client that sends the request message belongs to and the priority of the authentication client further comprises:
determining a sub local area network to which the authentication client that sends the request message belongs and the corresponding priority of the authentication client according to the IP address and configuration information of the authentication client; or,
determining which sub local area network the authentication client that sends the request message belongs to and the corresponding priority of the authentication client according to the MAC address and configuration information of the authentication client,
wherein said configuration information comprises:
an IP address network field corresponding to each of said sub local area networks and the corresponding priority of each IP address in each IP address network field when the authentication client is identified with an Internet Protocol (IP) address; and
a corresponding MAC address network field of each of said sub local area networks and the corresponding priority of each MAC address in each MAC address network field when the authentication client is identified with an media access control (MAC) address.

### Claim 9

An authentication access apparatus, the authentication access apparatus comprising: a token bucket setting unit and a detecting and allocating unit;
wherein said token bucket setting unit is to set a local area network token bucket including a high priority token bucket and a low priority token bucket for a local area network, wherein the number of tokens in said local area network token bucket is equal to the number of request messages which can be processed by an authentication server; and
wherein said detecting and allocating unit is to detect whether an authentication client that sends a request message is of a high priority or not, and,
when the authentication client has been detected to be of a high priority, to allocate a token from the high priority token bucket to the authentication client that sends the request message and redirect the request message to the authentication server; and
when the authentication client has been detected to be not of a high priority, to allocate a token from the low priority token bucket to the authentication client that sends the request message and redirect the request message to the authentication server; and
to recover the allocated token after a successful authentication of the authentication client that sends the request message.

### Claim 10 (depends on 9)

The apparatus as claimed in claim 9, wherein said token bucket setting unit comprises: a setting execution module and a storage module;
wherein said setting execution module is to set a local area network token bucket, wherein the number of tokens in said local area network token bucket being equal to the number of request messages which can be processed by the authentication server; to set sub local area network token buckets corresponding respectively to each sub local area network in the local area network token bucket; to set a high priority token bucket and a low priority token bucket in each sub local area network token bucket, wherein the number of tokens in the high priority token bucket is equal to the number of authentication clients which are configured to be of a high priority in the sub local area network and the sum of the numbers of tokens in the high priority token bucket and low priority token bucket is equal to the number of tokens in the sub local area network token bucket; and
said storage module is to store the result of setting of said setting execution module.

### Claim 11 (depends on 10)

The apparatus as claimed in claim 10, wherein said detecting and allocating unit further comprises: a detecting execution module, a first allocating module, a second allocating module and a recovering module;
wherein said detecting execution module is to detect which sub local area network the authentication client that sends the request message belongs to and the priority of the authentication client;
wherein said first allocating module is to, when said detecting execution module has detected that the authentication client is of a high priority, determine a sub local area network token bucket corresponding to the sub local area network to which the authentication client that sends the request message belongs, and take the high priority token bucket in the determined sub local area network token bucket as a token bucket for allocating tokens, and to allocate a token to the authentication client that sends the request message and redirect the request message to the authentication server;
wherein said second allocating module is to, when said detecting execution module has detected that the authentication client is not of a high priority, determine the sub local area network token bucket corresponding to the sub local area network to which the authentication client that sends the request message belongs, and take the low priority token bucket in the determined sub local area network token bucket as a token bucket for allocating tokens, and to allocate a token to the authentication client that sends the request message and redirect the request message to the authentication server, and to discard the request message if there is no token in the token bucket for allocating tokens; and
wherein said recovering module is to recover the allocated token after a successful authentication of the authentication client that sends the request message.

### Claim 12 (depends on 11)

The apparatus as claimed in claim 11, wherein said setting execution module sets one high priority token bucket and more than two low priority token buckets in each sub local area network token bucket; and
said second allocating module is further to search the determined sub local area network token bucket for a low priority token bucket corresponding to the level of the authentication client that sends the request message and take the found low priority token bucket as the token bucket for allocating tokens.

### Claim 13 (depends on 12)

The apparatus as claimed in claim 12, wherein said second allocating module is to, when there is no token in the token bucket for allocating tokens, first judge whether there is a token in other low priority token buckets whose level is lower than that of the token bucket for allocating tokens, if yes, to preempt one token from said other low priority token buckets for the authentication client that sends the request message and redirect the request message to the authentication server, otherwise, to discard the request message.

### Claim 14 (depends on 13)

The apparatus as claimed in claim 13, wherein said second allocating module is further to, when there is a token in said other low priority token buckets, first judge whether the number of tokens preempted from said other low priority token buckets has reached a set threshold, if yes, to discard the request message, otherwise, to preempt one token from said other low priority token buckets.

### Claim 15 (depends on 11)

The apparatus as claimed in claim 11, wherein said setting execution module is further to set a shared token bucket in said local area network token bucket, wherein the sum of the numbers of tokens in each of said sub local area network token buckets and in said shared token bucket is equal to the number of tokens in said local area network token bucket; and
said second allocating module is further to judge whether there is a token in said shared token bucket before discarding the request message, if yes, then to allocate a token from the shared token bucket to the request message and redirect the request message to the authentication server, otherwise, to discard the request message.

### Claim 16 (depends on 11)

The apparatus as claimed in claim 11, wherein said detecting execution module comprises a configuration information acquiring sub-module and a detecting sub-module;
wherein said configuration information acquiring sub-module is to provide configuration information of said authentication client of a high priority and said authentication client of a low priority to the detecting sub-module; and said configuration information comprises: an IP address network field corresponding to each of said sub local area networks and the corresponding priority of each IP address in each IP address network field when the authentication client is identified with an Internet Protocol (IP) address; and a corresponding MAC address network field of each of said sub local area networks and the corresponding priority of each MAC address in each MAC address network field when the authentication client is identified with an media access control (MAC) address; and
wherein said detecting sub-module is to determine which sub local area network the authentication client that sends the request message belongs to and the corresponding priority of the authentication client according to the IP address and configuration information of the authentication client; or, to determine which sub local area network a authentication client that sends the request message belongs to and the corresponding priority of the authentication client according to the MAC address and configuration information of the authentication client.
