Abstract: A bidding service may be used to receive bid information to complete a job request, from processors coupled to a job ticket service center. The processors submit bids in response to posting of job ticket notices at the service center. A work flow controller may post the job ticket notices after receipt of the job request. The job ticket notice may include specific tasks or branches that must be completed to complete the job request. The job ticket notice may include descriptions of specific branches and their interrelationships in sufficient detail to allow the processors to bid for completion of the branches. The bidding service may select bids from the processors based on set criteria. For example, the job request may specify minimum performance requirements (e.g., a maximum cost and a completion deadline). The bidding service may reject any bids that fail to satisfy the minimum performance requirements.

Abstract: To control concurrent access problems, the job ticket service may employ branch locking features, that is, the capability to lock a job ticket at the branch level. The branch locking may be accomplished by one of several methods. The work flow controller may assign one or more specific processors to perform the tasks identified with the branch to be locked. Where more than one processor is authorized access to the same branch, the job ticket service may lock the branch when one of the authorized processors actually acquire the branch. The job ticket service may lock the branches by setting a lock/unlock flag for each branch. Processors accessing the job ticket may then review the lock/unlock flag status to determine if the branch may be accessed. In some circumstances, the job ticket service may allow access only to those branches that are unlocked. A processor that has completed a task defined by the branch may need to have the branch unlocked in order to modify the branch.

Abstract: A job ticket service center includes features to provide security and to control access to a job ticket and related resources. The service center may include programming or servers to authenticate a processor and to authorize the processor to access a particular job ticket. An authentication server receives authentication information from a processor and an authorization server uses the information to check authorization functionality. The authorization or access rights of the processor may be carried as a part of the job ticket. Using these features, the service center may provide trusted authentication information about the processor to the authorization server, and the authorization server then performs its authority check functions. The job ticket maybe signed with an industry standard public key encryption message digest (MD) signature, and may be protected by a public key encryption system.

Abstract: A method and system for exchanging private data over an insecure network using public key encryption is disclosed. The method and system provides for generating a public/private key pair of a network peripheral, exposing the public key of the network peripheral in a network management protocol, receiving encrypted configuration data from a remote network configuration protocol tool, decrypting configuration data with the private key of the network peripheral and applying decrypted network configuration data to the configuration of the network peripheral.

Abstract: A method and an apparatus allow a client to manage job attributes and processes using a job ticket service. The job ticket service allows access and modification of a job ticket by multiple users on a network. The method and apparatus use a network-accessible job ticket to relate to a specific job or content. The content may be stored on the network and maybe accessed by multiple job tickets. Storage and management of the job ticket are transparent to the user. The job ticket is stored in a common location in the network. The job ticket remains in the same location in the network, and users access only that portion of the job ticket required to complete a designated process. Security measures may be added to limit access to those users designated as being allowed to access the job ticket and the job file. The job ticket may include a service ID that relates the job ticket back to the originating job ticket service.

Abstract: A bidding service may be used to receive bid information to complete a job request, from processors coupled to a job ticket service center. The processors submit bids in response to posting of job ticket notices at the service center. A work flow controller may post the job ticket notices after receipt of the job request. The job ticket notice may include specific tasks or branches that must be completed to complete the job request. The job ticket notice may include descriptions of specific branches and their interrelationships in sufficient detail to allow the processors to bid for completion of the branches. The bidding service may select bids from the processors based on set criteria. For example, the job request may specify minimum performance requirements (e.g., a maximum cost and a completion deadline). The bidding service may reject any bids that fail to satisfy the minimum performance requirements.

Abstract: A job ticket service allows clients to define databases, and to store data though the job ticket service. The databases may be used to hold contact lists, addresses, and other personal data. The databases may also be used to store any other generic data. The databases could then be used in conjunction with a variety of e-services provided by the processors. For example, an e-mail processor that provides e-mail services may be used in conjunction with a personal contact list to send e-mail messages, transfer electronic files, or to establish a chat room. The e-mail processor may access the contact list at predefined intervals to send e-mail messages to a select group of e-mail addressees. Furthermore, because the service center provides a single portal to processors that are coupled to the communications network, the client need not have any knowledge of the database structure, or the processing requirements of the processors.

Abstract: To control concurrent access problems, the job ticket service may employ branch locking features, that is, the capability to lock a job ticket at the branch level. The branch locking may be accomplished by one of several methods. The work flow controller may assign one or more specific processors to perform the tasks identified with the branch to be locked. Where more than one processor is authorized access to the same branch, the job ticket service may lock the branch when one of the authorized processors actually acquire the branch. The job ticket service may lock the branches by setting a lock/unlock flag for each branch. Processors accessing the job ticket may then review the lock/unlock flag status to determine if the branch may be accessed. In some circumstances, the job ticket service may allow access only to those branches that are unlocked. A processor that has completed a task defined by the branch may need to have the branch unlocked in order to modify the branch.

Abstract: A job ticket service center includes features to provide security and to control access to a job ticket and related resources. The service center may include programming or servers to authenticate a processor and to authorize the processor to access a particular job ticket. An authentication server receives authentication information from a processor and an authorization server uses the information to check authorization functionality. The authorization or access rights of the processor may be carried as a part of the job ticket. Using these features, the service center may provide trusted authentication information about the processor to the authorization server, and the authorization server then performs its authority check functions. The job ticket maybe signed with an industry standard public key encryption message digest (MD) signature, and may be protected by a public key encryption system.