Method and system for delayed allocation of resources

• US 8,086,741 B2
• Filed: 08/15/2003
• Issued: 12/27/2011
• Est. Priority Date: 02/28/2003
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Markaryan, Mark, Kakurin, Dmitry M., Olson, Sean C., Shoroff, Srikanth, Ionescu, Radu
• Primary Examiner(s): Blair, Douglas
• Assistant Examiner(s): Nguyen, Angela
• Application Number:
  US10/641,525
• Publication Number:
  US 20040172474A1
• Time in Patent Office: 3,056 Days
• Field of Search: 709/228
• US Class Current: 709/228
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/1458 Denial of Service
• CPC Class Codes: H04L 67/01 Protocols

Abstract

The present invention allows a server to delay allocating resources to a client'"'"'s request. When the client requests a feature that requires server resources, the server accepts and acknowledges the client'"'"'s request, but the client is prohibited from using the requested feature until further notice from the server. For example, during an authorization process, the server allocates only the minimum resources required to maintain the session and to authorize the client. Thereafter, the server allocates the resources necessary to support the client'"'"'s request only when the resources become available. Until then, the server maintains the communications session without supporting the request. Thus, the server shepherds its resources rather than committing them at the whim of a client. Also, a client need not repeat its request if the server cannot immediately satisfy it; instead, the server accepts the request and then later begins to support it when adequate resources become available.

Claims

1. In a communications environment comprising a server and a client, the server and the client each being a computing device, a method for the server to delay supporting a feature for the client, the feature requiring resources of the server, the method comprising:

receiving from the client a request for the feature; and

determining by the server whether the server supports the requested feature,

when it is determined that the server does not support the requested feature, sending an indication to the client that the request is rejected; and

when it is determined that the server does support the requested feature, sending to the client an indication that the request has been granted;

sending to the client an indication that the requested feature is not yet supported; and

after sending to the client the indication that the requested feature is not yet supported,

determining by the server whether the client is authenticated;

when it is determined that the client is not authenticated, sending to the client an indication that the client is not authenticated; and

when it is determined that the client is authenticated, sending to the client an indication that the client is authenticated;

sending to the client an indication that the requested feature is supported; and

supporting by the server the requested feature for the client by allocating resources required by the requested feature for the client.

2. The method of claim 1 wherein the requested feature is a feature of communications between the client and the server selected from the group consisting of:

compression, a quality of service, bandwidth, a response time guarantee, immunity to error, integrity of message sequence and lack of duplication, and a maximum permissible loss rate.

3. The method of claim 1 wherein receiving a request for the feature comprises receiving from the client an explicit request for the feature.

4. The method of claim 1 wherein receiving a request for the feature comprises receiving from the client an implicit request for the feature.

5. The method of claim 1 wherein receiving a request for the feature comprises receiving a request for a first level of support of the requested feature, and wherein sending to the client an indication that the requested feature is supported comprises sending to the client an indication that the requested feature is supported at a second level of support of the requested feature.

6. The method of claim 1 wherein when the indication that the requested feature is not yet supported is sent to the client, not using the requested feature in communications with the client.

7. The method of claim 1 wherein when the indication that the requested feature is supported is sent to the client, using the requested feature in communications with the client.

8. The method of claim 1 wherein supporting the requested feature for the client comprises allocating resources.

9. The method of claim 1 further comprising:

logging statuses of feature requests as rejected, accepted but not yet supported, or accepted and supported.

10. The method of claim 4 wherein the implicit request for the feature is specified by a communications protocol used by the client and by the server.

11. The method of claim 4 wherein the second level of support of the requested feature is less than the first level of support of the requested feature.

12. The method of claim 5 wherein supporting the requested feature for the client comprises supporting the requested feature at the second level of support of the requested feature.

13. The method of claim 5 further comprising:

after sending to the client the indication that the requested feature is supported at the second level of support of the requested feature, sending to the client an indication that the requested feature is supported at the first level of support of the requested feature.

14. The method of claim 8 wherein allocating resources comprises allocating resources provided by a computing device other than the server.

15. The method of claim 8 further comprising:

checking for an availability of resources for supporting the requested feature; and

delaying the sending to the client the indication that the requested feature is supported until resources for supporting the requested feature are available.

16. The method of claim 9 further comprising:

logging levels of support of feature requests; and

logging resources allocated to support of feature requests.

17. The method of claim 15 further comprising:

maintaining information about resources used and about not-yet-supported feature requests.

18. The method of claim 17 wherein the server supports a plurality of clients and wherein resources become available for supporting the requested feature as they are relinquished by other clients.

19. A computer-readable storage device containing computer-executable instructions for performing a method for a server computing device to delay supporting a feature for a client computing device, the method comprising:

receiving a request for the feature;

indicating to the client that the request has been granted;

indicating to the client that the requested feature is not yet supported without allocating resources to support the requested feature;

after indicating to the client that the requested feature is not yet supported,

performing authentication of the client, the authentication being successful or unsuccessful;

after unsuccessful authentication of the client, indicating to the client that the authentication was unsuccessful;

after successful authentication of the client,

indicating to the client that the requested feature is supported; and

supporting the requested feature for the client including allocating resources to support the requested feature;

upon receiving from the client prior to indicating that requested feature is supported a request to access the requested feature, rejecting the request; and

upon receiving from the client after indicating that the requested feature is supported a request to access the requested feature, granting the request

wherein allocating resources to support a requested feature is delayed until the client is authenticated.

20. In a communications environment comprising a server computing device and a client computing device, a method for the client to obtain support from the server for a feature, the method comprising:

requesting the feature from the server;

receiving an indication that the request has been granted;

receiving an indication that the requested feature is not yet supported;

refraining from using the requested feature; and

after receiving the indication that the requested feature is not yet supported,

sending to the server authentication information of the client;

after the server does not successfully authenticate the client, receiving an indication that the authentication was not successful; and

after the server successfully authenticates the client and allocates resources for the requested feature,

receiving from the server an indication that the requested feature is supported; and

using the requested feature.

21. The method of claim 20 wherein the requested feature is a feature of communications between the client and the server selected from the group consisting of:

compression, a quality of service, bandwidth, a response time guarantee, immunity to error, integrity of message sequence and lack of duplication, and a maximum permissible loss rate.

22. The method of claim 20 wherein requesting the feature comprises sending an explicit request for the feature to the server.

23. The method of claim 20 wherein requesting the feature comprises implicitly requesting the feature.

24. The method of claim 20 wherein requesting the feature comprises requesting a first level of support of the requested feature, and wherein receiving an indication that the requested feature is supported comprises receiving an indication that the requested feature is supported at a second level of support of the requested feature.

25. The method of claim 20 wherein receiving one indication comprises receiving an indication that the request has been granted and receiving an indication that the requested feature is not yet supported.

26. The method of claim 20 wherein receiving an indication that the requested feature is not yet supported comprises receiving communications from the server that do not use the requested feature.

27. The method of claim 20 wherein receiving an indication that the requested feature is supported comprises receiving communications from the server that use the requested feature.

28. The method of claim 20 further comprising:

displaying to a user of the client a status of the feature request as rejected, accepted but not yet supported, or accepted and supported.

29. The method of claim 23 wherein the implicit request, for the feature is specified by a communications protocol used by the client and by the server.

30. The method of claim 24 wherein the second level of support of the requested feature is less than the first level of support of the requested feature.

31. The method of claim 24 wherein using the requested feature comprises using the requested feature at the second level of support of the requested feature.

32. The method of claim 24 further comprising:

after receiving an indication that the requested feature is supported at the second level of support of the requested feature, receiving an indication that the requested feature is supported at the first level of support of the requested feature.

33. The method of claim 28 further comprising:

displaying to a user of the client a level of support of the feature request.

34. A computer-readable storage device containing computer-executable instructions for performing a method for a client computing device to obtain support from a server computing device for a feature, the method comprising:

requesting the feature from the server;

receiving an indication that the request has been granted;

receiving an indication that the requested feature is not yet supported;

refraining from using the requested feature;

after receiving the indication that the requested feature is not yet supported,

sending to the server authentication information of the client;

after the server does not successfully authenticate the client, receiving an indication that the authentication was not successful; and

after the server successfully authenticates the client and allocates resources for the requested feature,

receiving an indication that the requested feature is supported; and

using the requested feature.

35. In a communications environment comprising a server computing device and a client computing device, a method for the server to delay supporting a feature for the client and for the client to obtain support from the server for the feature, the method comprising:

requesting, by the client, the feature from the server;

receiving, by the server, the request for the feature;

indicating, by the server and to the client, that the request has been granted;

receiving, by the client, the indication that the request has been granted;

indicating, by the server and to the client, that the requested feature is not yet supported;

receiving, by the client, the indication that the requested feature is not yet supported;

refraining, by the client, from using the requested feature; and

after indicating, by the server and to the client, that the requested feature is not yet supported,

performing authentication of the client, the authentication being successful or unsuccessful;

after unsuccessful authentication of the client, indicating, by the server and to the client, that the authentication was unsuccessful; and

after successful authentication of the client,

supporting, by the server, the requested feature for the client, the supporting including allocating resources to support the requested feature;

indicating, by the server and to the client, that the requested feature is supported; and

after receiving, by the client, the indication that the requested feature is not yet supported,

receiving, by the client, the indication that the requested feature is supported; and

using, by the client, the requested feature.

36. A computer-readable storage device containing computer-executable instructions for performing a method for a server computing device to delay supporting a feature for a client computing device and for the client to obtain support from the server for the feature, the method comprising:

requesting, by the client, the feature from the server;

receiving, by the server, the request for the feature;

indicating, by the server and to the client, that the request has been granted;

receiving, by the client, the indication that the request has been granted;

indicating, by the server and to the client, that the requested feature is not yet supported;

receiving, by the client, the indication that the requested feature is not yet supported;

refraining, by the client, from using the requested feature; and

after indicating, by the server and to the client, that the requested feature is not yet supported,

performing authentication of the client, the authentication being successful or unsuccessful;

after unsuccessful authentication of the client, indicating, by the server and to the client, that the authentication was unsuccessful; and

after successful authentication of the client,

supporting, by the server, the requested feature far the client, the supporting including allocating resources to subpart the requested feature;

indicating, by the server and to the client, that the requested feature is supported;

after receiving, by the client, the indication that the requested feature is not yet supported,

receiving, by the client, the indication that the requested feature is supported; and

using, by the client, the requested feature.