Method for establishing an agency relationship to perform delegated computing tasks

A method is disclosed for establishing an agency relationship to perform delegated computing tasks. The method provides for initiation of the agency relationship, establishment of credentials to perform a delegated computing task, and performance of the delegated computing task. Benefits of establishing an agency relationship in a computing environment include improved security, efficiency, and reliability in performing delegated computing tasks.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates to performance of computing tasks and more particularly relates to establishing an agency relationship to perform delegated computing tasks.

2. Description of the Related Art

There are many reasons that a need may arise for one computing device to delegate computing tasks to another computing device. Network resource management, hardware resource management, process scheduling, and security, and the like are examples of processes for which task delegation is desirable. When one computing device, network component, or component of a computing device requires assistance from another such device for improving efficiency, the need for delegation arises. Delegation as used herein means the assignment of responsibility for performing a computing task from one computing module or device (hereinafter node) to another node.

One example of an area in which delegation of computing tasks may be beneficial is network resource management. If one node on the network is operating under a disproportionately heavy load, when compared with other nodes on the network, the need for delegation arises. The overloaded node may delegate some of the tasks to be done to another network node that is not overloaded. In such an instance, the tasks can be accomplished more efficiently through the use of task delegation.

In a similar example, delegation provides more efficient use of computing device resources. A server may have multiple processors. If one of the processors is heavily loaded with a set of computing tasks, it may be beneficial to offload some of the computing tasks to one of the other processors. Delegation is therefore, a useful tool in balancing the amount of work to be done in both a network scope and a local machine scope.

Despite the usefulness of computing task delegation, currently some limitations exist. Security is an extremely important aspect of today's computing environment. In many situations, one node on a network may be burdened with a heavy task load, because that node is the only node authorized to perform the given tasks. Passwords and log-in ID are an important aspect of computer security. In many cases, a specific password is required to perform certain computing tasks. In order to maintain a secure computing environment, these passwords are often carefully protected. For delegation to work successfully, multiple nodes must possess the authorization required to perform a given set of delegated tasks. Therefore, it is often difficult to provide multiple nodes capable of performing delegated tasks and simultaneously maintain strict security policies.

One common solution to the authorization problem is to have a common password that a predetermined set of nodes possess, which can be used to perform a given set of computing tasks. By this method, known as masquerading, any one of the nodes possessing the password can perform the tasks. It is desirable that work performed for a delegated task be identified according to the node originally assigned the task. The problem with masquerading is that the individual identity of the node that performed the task is lost. This may be problematic if attempts are made to identify the node that performed the task. For example, when trouble shooting an error associated with the delegated task, it is important to know the identity of all nodes involved. With a common password, it is difficult to differentiate one node from another.

One example of a situation in which masquerading is often used is network node backup. Data from multiple network nodes must be backed up onto a single backup server. In most cases, access to data on a backup server is password protected for security. Generally, a predetermined set of backup nodes are given access, using a common password, to the backup server. There are several problems with this architecture.

One problem is backup process scheduling. Some backup servers, such as Tivoli™ Storage Management, use a single-tasked model. A named node can only have one backup process running at a time and only has one address for the server to contact to start a backup process. Consequently, this makes it difficult for a single task to be split up between several nodes to take advantage of delegating portions of the single task.

Another problem associated with masquerading is password management. It is difficult to distribute a common password across several nodes. In most cases, the password cannot be automatically updated upon expiration. In many cases, the password must be manually updated for each of the predetermined nodes.

As explained above, it is also difficult to determine which node was originally assigned to backup the data to be backed up and which node actually performed the backup, because of masquerading. Additionally, if an error occurs, it is extremely difficult to trace the source of the error, because under masquerading, the identities of the nodes performing the tasks are hidden due to the shared password and log-in ID.

From the foregoing discussion, it should be apparent that a need exists for an apparatus, system, and method that establish an agency relationship to perform delegated computing tasks. Beneficially, such an apparatus, system, and method would allow for delegation of computing tasks while eliminating problems that arise from the complexities of process scheduling and authorization management.

SUMMARY OF THE INVENTION

The present invention has been developed in response to the present state of the art, and in particular, in response to the problems and needs in the art that have not yet been fully solved by currently available computing task delegation techniques. Accordingly, the present invention has been developed to provide an apparatus, system, and method for establishing an agency relationship to perform a delegated computing task that overcome many or all of the above-discussed shortcomings in the art.

The apparatus to establish an agency relationship to perform delegated computing tasks is provided with a logic unit containing a plurality of modules configured to functionally execute the necessary steps of initiating an agency relationship between an independent agent and a principal to perform a delegated computing task, establishing credentials of the agent to perform the delegated computing task on behalf of the principal, and performing the delegated computing task of the agent on behalf of the principal. These modules in the described embodiments include an agent initiation module, a credentials module, and a computing module.

Preferably, the agent initiation module is configured to initiate an agency relationship between an agent and a principal to perform a delegated computing task. In one embodiment, the agent initiation module also includes a communication module configured to communicate an agency request between a first logical node representative of the principal, and a second logical node representative of the agent, and communicate acceptance of the agency request. In one further embodiment, the apparatus includes an agent delegation module configured to delegate responsibility to a second agent for performing the delegated computing task on behalf of the agent, wherein the identity of the first agent, the second agent, and the principal are recorded in association with the delegated computing task. In one embodiment, the initiation module is further configured to request a list of principals for which the agent is authorized to perform tasks.

Preferably, the credentials module is configured to establish credentials of the agent to perform a delegated computing task on behalf of the principal. In one embodiment, the credentials module also includes an authentication module configured to authorize the agent to perform delegated computing tasks with a target node, wherein the agent uses agency credentials separate from the credentials of the principal. The credentials module may also include an agent authorization module configured to authorize, with agency credentials, the agent to perform delegated computing tasks with the target node on behalf of the principal, wherein the identity of the agent and the principal are recorded in association with the delegated computing task.

Preferably, the computing module is configured to perform delegated computing tasks of the agent on behalf of the principal. In one embodiment, the computing module includes an execution module of an agent computing device configured to execute the delegated computing task in cooperation with a target node. The apparatus may also include a configuration module configured to apply configuration information to the agent that governs the delegated computing task, the configuration information corresponding to configuration information of the principal. In one embodiment, the delegated computing task is selected from a group consisting of data storage management, file management, processor load balancing, and network load balancing.

In one embodiment, the apparatus may be located on the principal. In such an embodiment, the apparatus is provided with a logic unit containing a plurality of modules configured to functionally execute the necessary steps of initiating an agency relationship between an agent and a principal to perform a delegated computing task, registering, with a designated computing device, agents authorized to perform a delegated computing task on behalf of the principal, and delegating a delegated computing task to an agent. These modules in the described embodiments include a principal initiation module, a credentials registration module, and a principal delegation module.

A system of the present invention is also presented to establish an agency relationship to perform delegated computing tasks. The system may include a principal configured to delegate a delegated computing task to an agent, a target node upon which the delegated computing task is performed, and an agent which includes an agent initiation module, a credentials module, and a computing module.

A method of the present invention is also presented for establishing an agency relationship to perform delegated computing tasks. The method in the disclosed embodiments substantially includes the steps necessary to carry out the functions presented above with respect to the operation of the described apparatus and system.

DETAILED DESCRIPTION OF THE INVENTION

Reference to a signal bearing medium may take any form capable of generating a signal, causing a signal to be generated, or causing execution of a program of machine-readable instructions on a digital processing apparatus. A signal bearing medium may be embodied by a transmission line, a compact disk, digital-video disk, a magnetic tape, a Bernoulli drive, a magnetic disk, a punch card, flash memory, integrated circuits, or other digital processing apparatus memory device.

FIG. 1depicts a schematic block diagram of a system100for establishing an agency relationship to perform delegated computing tasks. In one embodiment, the system100includes a principal102, an agent104, and a target node106. In such an embodiment, the principal102delegates a computing task to be performed in cooperation with the target node106to the agent104. The agent104then performs the delegated computing task with the target node106on behalf of the principal102.

As used herein, the term agency refers to the delegation of responsibility for performance of a specific task from a principal102to an agent104. The agent104has the authority to associate the principal102with tasks performed on behalf of the principal102by the agent104. In one embodiment, this association is accomplished by recording the identity of both the principal102with information (metadata) regarding the performed task. Such a recording may be performed by the target node106. In this manner, the principal102remains accountable for the work performed for the computing task. Preferably, the identity of the agent104is also recorded with the metadata such that errors caused by the agent104can be properly traced. Additionally, once the agent104has accepted responsibility for performance of the task, that responsibility remains with the agent104until the task is complete, or the task is delegated to another agent104.

In one embodiment, the principal102is a node on a network. A node may be a logical construct representative of a group of data, a network device, a cluster of network devices, or the like. In various embodiments, the principal102may comprise a server, workstation, database, storage disk, tape drive, or the like. In an alternative embodiment, the principal102may be a network routing device. In such embodiments, the principal102delegates some or all of the principal's work load to an agent104. The principal102may actively delegate the tasks to the agent104. Alternatively, the principal102may schedule with the agent104delegation of certain tasks in advance.

In one embodiment, the agent104initiates an agency relationship between the agent104and the principal102, establishes credentials, and performs the delegated computing task. The agent104may be a server, workstation, database, storage disk, tape drive, network routing device, or the like. In one embodiment, the agent104accepts responsibility for performing the delegated task on behalf of the principal102. The agent104may perform the computing task in communication with the target node106. In an alternative embodiment, the agent104may perform a computing task locally.

In one embodiment, the target node106hosts the computing task performed by the agent104. The target node106may be a physical computing device. Alternatively the target node106may be a logical group of data. One example of a target node106is a Tivoli™ Storage Management (TSM) system. The TSM system facilitates network data backup and restore. In one embodiment, the agent104may perform a backup task with the TSM system on behalf of the principal102. In another embodiment, the agent104may restore data representing the principal102from data stored on the TSM system.

In one example of the system100, the principal102may be responsible to backup a set of data on a target node106. If the work load of the principal102is too great, the principal102may delegate a portion of the work load to an agent104. The agent104then shares in the responsibility of backing up the data set on the target node106. The principal102and the agent104preferably use independent passwords and log-in IDs to gain access to the target node106. In this manner, the identity of both the agent104and the principal102may be stored, with the data set, on the target node106. Backup errors may then be readily attributed to the principal102or the agent104.

FIG. 2is a schematic block diagram illustrating one embodiment of a system environment200for establishing an agency relationship to perform delegated computing tasks. The system200includes a principal102, an agent104, a backup server206, and data groups208A-C. In one embodiment, the system components communicate via a communications bus202. Additional communications may include communication of an agency request204, agent authentication210, agent authorization212, application of configuration information214, and execution of a computing task216.

In one embodiment, the principal102may have the responsibility to backup data from the data groups208A-C to the backup server206. If the work load of the principal102becomes too great, the principal104may initiate delegation of a portion of the task. Consequently, the principal102may send an agency request204to the agent104. In one example, the principal102may retain responsibility to backup the first data group208A, and the second data group208B, but delegate responsibility for backing up the third data group208C to the agent104. Accordingly, the agency request204includes a request to backup the third data group208C. Preferably, the agent104acknowledges and accepts the request204.

In one embodiment, the agent104establishes credentials to backup the third data group208C on the backup server206on behalf of the principal102. The agent104may log on210to the backup server using authentication credentials. The authentication credentials establish the identity of the agent104. Typically, the authentication credentials comprise the agent's user-ID and password. The agent104may then request authorization212from the backup server206to perform the backup of the third data group208C on behalf of the principal102. The authorization request212may comprise agency credentials. Agency credentials represent an agency relationship between the principal102and the agent104. The agency relationship may be predefined or dynamically defined by the principal102communicating with the backup server206. Various structures may be used to represent agency credentials including a list, a stack, a queue, or the like.

In one embodiment, the backup server206stores agency credentials as a list of agents104authorized to perform computing tasks on behalf of the principal102. The principal102may periodically register agents104authorized to perform delegated tasks. In another embodiment, the backup server206may send a message to the principal102requesting authorization for the agent104to perform the delegated tasks. In a further embodiment, the backup server206may store a lookup table of agents104authorized to perform tasks on behalf of certain principals102. One benefit of authorizing an agent104to perform tasks on behalf of a specific principal102, is that the identity of both the agent104and the principal102are retained in association with the delegated task.

In one embodiment, the backup server206may apply214configuration information and computing policies to the agent104. Applying the configuration information214to the agent104imposes the same restrictions and permissions on the agent104that the principal102would have. Restricting the agent104in this manner ensures that unshared data does not get recorded in a shared storage space. Application of the configuration information214also maintains security by ensuring that the agent104does not access data that the principal102is not authorized to access, thereby maintaining consistency.

In such an embodiment, the agent104performs216the backup of the third data group208C upon successful authorization212and application214of configurations. If an error occurs during the backup of the third data group208C, the identity of the third data group208C, the agent104, and the principal102are known. Beneficially, the problem could be traced back throughout the chain to identify the source of the error.

FIG. 3is a schematic block diagram illustrating one embodiment of an apparatus300to establish an agency relationship to perform delegated computing tasks. In one embodiment, the apparatus300is located on an agent104. The apparatus300includes an agent initiation module302, a credentials module304, and a computing module306. In an alternative embodiment, the apparatus300may comprise a separate device in communication with the agent104.

In one embodiment, the agent initiation module302initiates an agency relationship between an agent104and a principal102to perform a delegated computing task. The agent initiation module302may initiate the relationship responsive to a request message from the principal102. In an alternative embodiment, the agent initiation module302may initiate the relationship according to a predetermined schedule. Alternatively, the agent104may request a list of principals102for which the agent is authorized to perform tasks. The list may be collocated with the authorization information on the server106. In such an embodiment, the agent104initiates delegation of tasks with any of the principals102on the list.

In another alternative embodiment, the agent initiation module302may initiate the relationship responsive to a threshold set for the principal102. One example of a threshold may be a data quantity threshold. If the principal102processes a predetermined quantity of data, the agent initiation module302may initiate the agency relationship. Another example may be a processor usage threshold. Alternatively, if the agent104has a low work load, the agent initiation module302may initiate an agency relationship for work load balancing with a principal102.

In one embodiment, the credentials module304establishes credentials of the agent104to perform a delegated computing task on behalf of the principal102. The credentials module304may provide a password or set of passwords and user-IDs to identify the agent104and authorize the agent104to perform tasks on behalf of the principal102. Alternatively, the credentials module304may use a network identifier, such as a hardware address of the agent104, as the credentials for the agency relationship. In one embodiment, the agent104may contain a lookup table of principals for which the agent104is authorized to perform tasks.

In one embodiment, the computing module306performs a delegated computing task of the agent104on behalf of the principal102. In one embodiment, the computing module306may communicate with a target node106to perform the computing task. In another embodiment, the computing module306may communicate with other nodes in a network via a communications bus202(seeFIG. 2). Alternatively, the computing module306may perform computations locally and communicate the results to the target node106.

One example of a computing module306is a processor on a server. The processor may perform calculations on data on behalf of a principal102and communicate the results to a target node106. Another example computing task is a backup operation. The computing module306may collect the data from the data group208C and place data in a specified location on a backup server206(seeFIG. 2).

FIG. 4is a detailed schematic block diagram illustrating one embodiment of an apparatus400to establish an agency relationship to perform delegated computing tasks. The apparatus400may be located on the agent104. In one embodiment, the apparatus includes the agent initiation module302, credentials module304, and computing module306. Additionally, the apparatus may include a communication module402, an authentication module404, an authorization module406, an execution module408, a configuration module410, and an agent delegation module412.

The agent initiation module302may include a communication module402. Once the agent initiation module302initiates a request204for an agency relationship, the communication module402communicates the agency request204. In one embodiment, the agency request204is communicated to the principal102. In an alternative embodiment, the communication module402may receive an agency request204from a principal102. In such an embodiment, the agent initiation module302initiates the agency relationship responsive to receiving an agency request from a principal102via the communication module402. In an alternative embodiment, the communication module402may send an agency request204to a principal102responsive to a scheduled agency initiation.

In one embodiment, the credentials module304includes an authentication module404. The authentication module404establishes the identity of the agent104using credentials separate from the credentials of the principal102. The credentials of the principal102are not shared or communicated to the agent104. This maintains the integrity and security of the principal's credentials. In one example, the authentication module404uses a unique password and user-ID that identifies the agent104to logon to a server. The server recognizes the password as an identifier of the agent104and allows access to the agent104. In another embodiment, the authentication module404uses a hardware address as authentication credentials.

The credentials module304may also include an authorization module406. In one embodiment, the authorization module406sends an agency authorization request212to a target node106. The agency authorization request112may include agency credentials, the identity of the principal102, and the like. In one embodiment, the agency credential is an agency specific password. In another embodiment, the target node106may look up agency authorization information for the agent104in a local lookup table of authorized agents. Authorizing the agent104to perform tasks on behalf of a given principal102allows the agent104to perform the tasks as if it were the principal102, while still maintaining security and the identity of both the agent104and the principal102.

In one embodiment, the computing module306includes an execution module408. The execution module408executes delegated tasks in cooperation with a target node106. One embodiment of a task that may be performed by the execution module408is a data backup operation. In this example, the execution module408may execute a backup routine which copies data from a given data set to the target node106. In alternative examples, the execution module408may execute computations or file transfers in cooperation with the target node106. In another alternative embodiment, the execution module may execute an internal task and return results to a target node106or to the principal102.

In one embodiment, the configuration module410applies configuration information. The configuration information may define computing policies and guidelines for interactions between the agent104and the target node106. In one embodiment, the configuration information may restrict the actions of the agent104to comply with the configurations of the principal102. In another embodiment, a set of agency configuration information may be applied. Agency configuration information may be a standard set of computing policies that all agents104must follow when performing tasks with the target node106on behalf of principals. One example of configuration information is a restriction of access to a secure area of the target node106. An alternative example of configuration information is the data compression ratio for data backup performed by the agent104.

There may be a need for the agent104to delegate the computing task to another agent104. In one embodiment, the agent delegation module412may delegate the computing task to another agent104. In one embodiment, the agent delegation module may trigger the agent initiation module302to initiate an agency relationship with another agent104. Alternatively, the agent delegation module412may send an agency request204to the agent initiation module302of another agent104. In one example, the agent104may not be authorized to perform computing tasks on a target node106on behalf of a principal102. The agent delegation module412may delegate the task to another agent104that is authorized to perform the computing task. In another embodiment, the agent104may become heavily burdened with tasks. In such an example, the agent delegation module412may accept the computing task and then delegate the computing task to another agent104to balance the work load.

FIG. 5is a schematic block diagram illustrating an alternative embodiment of an apparatus500to establish an agency relationship to perform delegated computing tasks. In one embodiment, the apparatus500may be located on a principal102node. The apparatus500may include a principal initiation module502, a credentials registration module504, and a principal delegation module506.

In one embodiment, the principal initiation module502initiates an agency relationship between an agent104and a principal102to perform a delegated computing task. The principal initiation module502may initiate an agency relationship responsive to local thresholds including processor usage, disk volume, and the like. The principal initiation module502may also initiate an agency relationship responsive to a predetermined schedule. In one example, the principal initiation module502initiates an agency relationship with an agent104to balance work load due to backup tasks.

The credentials registration module504may register, with a designated target node106, a list of agents authorized to perform delegated computing tasks on behalf of the principal102. The credentials registration module504may periodically update a lookup table of authorized agents stored on the target node106.

Alternatively, the credentials registration module504may authorize an agent104to perform tasks responsive to an authorization registration request from the target node106. An authorization registration request may be sent by the target node106to the credentials registration module504responsive to an authorization request from the authorization module406of an agent104. In one embodiment, the credentials registration module504identifies authorized agents104with an agency password. In another embodiment, the credentials registration module504identifies authorized agents104with a unique identifier of the agent.

In one embodiment, the principal delegation module506delegates a computing task to an agent104. Delegation may include data collection, data communication, execution of an executable module, communication address redirection, and the like. In one embodiment, the principal delegation module506interfaces with the agent104to ensure complete hand-off of the computing task. The principal delegation module506may also manage delegated tasks. In one embodiment, the principal delegation module may request status reports from an agent104on the progress of a delegated computing task.

FIG. 6is a schematic flow diagram illustrating one embodiment of a method600for establishing an agency relationship to perform delegated computing tasks. The method600starts602when the agent initiation module302or the principal initiation module502initiates604an agency relationship. In one embodiment, the credentials module304then establishes606credentials of the agent104to perform a delegated computing task on behalf of the principal102. The computation module306may then perform608the delegated task in cooperation with a target node106. The method600then ends610upon successful completion of the delegated task. One advantage of this method is that both the principal102and the agent104are separately identifiable.

FIG. 7is a detailed schematic block diagram illustrating one embodiment of a method700for establishing an agency relationship to perform delegated computing tasks. The method700may start702when an agency relationship is initiated704by either the agent initiation module302or the principal initiation module502. In one embodiment, the communications module402then communicates706an agency request204between the agent102and the principal104. The communication module402may use a wired connection to communicate706the agency request. Alternatively, a wireless communication channel may be used to communicate706the agency request204.

In one embodiment, a decision708is made whether to delegate to another agent104. If the agent104delegates708to another agent104, then another agency relationship is initiated704by the agent initiation module302. The communications module402may then communicate706an agency request to the next agent104. This process of agent delegation may continue until an agent104is selected that can perform the task.

In one embodiment, the authentication module404then authenticates710the agent on a target node106. The authorization module406may then authorize712the agent104to perform computing tasks on behalf of the principal102. In one embodiment, if the credentials are not valid714, a new agency relationship may be initiated704and the process repeats until an agent104is selected with valid714credentials. If the credentials are valid714, then the configuration module410may apply716an execution configuration to the agent104. The computing task may then be executed718by the execution module408, and the process ends720. In one alternative embodiment, the agent104may perform several tasks on behalf of the principal102upon successful establishment of credentials710,712with the target node106.