Method and system for delayed allocation of resources

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.

1 - 43 . (canceled) 
     
     
         44 . A method performed by a server to delay supporting a feature for a client until the client is authenticated, the method comprising:
 receiving from the client a request to use the feature;   after receiving the request to use the feature, sending to the client an indication that the feature is not yet supported; and   after sending to the client the indication that the feature is not yet supported, determining whether the client is authenticated;
 upon determining that that client is not authenticated, suppressing allocation of resources to support the feature; and 
 upon determining that that client is authenticated,
 allocating resources to support the feature; and 
 sending to the client an indication that the feature is now supported. 
 
   
     
     
         45 . The method of  claim 44  wherein the sending to the client an indication that the feature is not yet supported includes indicating that the request is granted. 
     
     
         46 . The method of  claim 44  including upon determining that the client cannot be authenticated, sending to the client an indication that the client is not authenticated. 
     
     
         47 . The method of  claim 44  including upon determining that the client can be authenticated, sending to the client an indication that the client is authenticated. 
     
     
         48 . The method of  claim 44  wherein the received request to use the features indicates a first level of support, and wherein the indication sent to the client that the feature is now supported indicates that the feature is supported at a second level of support. 
     
     
         49 . The method of  claim 48  wherein the second level of support is less than the first level of support. 
     
     
         50 . The method of  claim 49  further comprising after sending to the client the indication that the feature is supported at the second level of support, sending to the client an indication that the feature is supported at the first level of support. 
     
     
         51 . The method of  claim 44  wherein the feature is 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. 
     
     
         52 . A computer-readable storage device storing computer-executable instructions for controlling a client to obtain support from a server for a feature, by a method comprising:
 sending to the server authentication information of the client;   sending to the server a request to use the feature; and   after sending to the server the request to use the feature,
 receiving from the server an indication that the feature is not yet supported; and 
 after receiving from the server the indication that the feature is not yet supported, refraining from using the feature until receiving from the server an indication that the feature is now supported. 
   
     
     
         53 . The computer-readable storage device of  claim 52  wherein the receiving from the server of the indication that the feature is not yet supported includes receiving an indication that the request is granted. 
     
     
         54 . The computer-readable storage device of  claim 52  including receiving from the server an indication that the client is not authenticated when the server is unable to authenticate the client based on the authentication information of the client. 
     
     
         55 . The computer-readable storage device of  claim 52  including receiving from the server an indication that the feature is now supported and after receiving the indication that the feature is now supported, using the feature. 
     
     
         56 . The computer-readable storage device of  claim 52  wherein the sent request to use the feature indicates a first level of support, and the received indication that the feature is now supported indicates a second level of support of the feature that is less than the first level of support. 
     
     
         57 . The computer-readable storage device of  claim 56  after receiving the indication that the feature is supported at the second level of support, receiving from the server indication that the feature is supported at the first level of support. 
     
     
         58 . The computer-readable storage device of  claim 52  wherein the feature is 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. 
     
     
         59 . A server that delays allocating resources for a feature requested by a client until the client is authenticated, the method comprising:
 a memory storing computer-executable instructions of:
 a component that receives from the client a request to use the feature and authentication information of the client; 
 a component that, after receiving the request to use the feature, sends to the client an indication that the request is granted but that the feature is not yet supported so that the client will refrain from using the feature until the client is sent an indication that the feature is now supported; and 
 a component that, after sending to the client the indication that the feature is not yet supported,
 when the client cannot be authenticated based on the received authentication information, suppresses allocation of the feature; and 
 when the client is authenticated based on the received authentication information,
 allocates resources to support the feature; and 
 sends to the client an indication that the feature is now supported; and 
 
 
 a processor that executes the computer-readable instructions stored in memory. 
   
     
     
         60 . The server of  claim 59  including a component that, when the client cannot be authenticated based on the received authentication information, sends to the client an indication that the client is not authenticated. 
     
     
         61 . The server of  claim 59  wherein the received request to use the feature indicates a first level of support of the feature, and wherein the indication sent to the client indicating that the feature is not yet supported indicates that the feature is supported at a second level of support. 
     
     
         62 . The server of  claim 61  further comprising after sending to the client the indication that the feature is supported at the second level of support, sending to the client an indication that the feature is now supported at the first level of support. 
     
     
         63 . The server of  claim 62  wherein the feature is 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.