GB2385693A

GB2385693A - Database Comprising Job Ticket Service for Managing Tasks

Info

Publication number: GB2385693A
Application number: GB0310467A
Authority: GB
Inventors: Ward S Foster; Kenneth L Oakeson; Brian A Volkoff; Shell S Simpson
Original assignee: Hewlett Packard Co
Current assignee: HP Inc
Priority date: 2001-06-05
Filing date: 2002-05-20
Publication date: 2003-08-27
Anticipated expiration: 2022-05-20
Also published as: GB0310467D0; GB2385693B; GB2385694B; GB0310468D0; GB2385694A

Abstract

A job ticket service allows clients to define databases, and to store data through the job ticket service. The databases may be used to hold contact lists, addresses, and other personal data as well as control data (69). 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 (80). 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, as a series of tasks. 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 (80), 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 (80). The database may be an XML database.

Description

1 Use of a Job Ticket as a Generic XML Database 2 Technical Field 3 The technical field is the integration and control of services in a networked 4 environment.

5 Background 6 Services may be provided by one or more operating units in a computer-based 7 network. Users of the network may generate specific tasks and send the tasks into the 8 network to be assigned to one of the operating units. For example, a user at a computer 9 terminal may generate a printing order using a printer driver installed on the terminal.

10 The pinter driver is used to control the printing request. In another example, a user at a 11 computer terminal may generate a printing order and send the printing order into a 12 computer network so that the printing order is completed by a printing service. The 13 printing order may be related to a company brochure. The printing order may contain 14 unique requirements such as paper type, font size, layout, graphics, color, and other 15 requirements. The user may specify that a specific printing service, such as Kinkos, 16 prepare the company brochure. Alternatively, the computer network may include 17 programs that suggest printing services to the user.

18 To control the printing job, the user's computer terminal may generate a job 19 ticket. The job ticket mcludes the requirements, such as the requirements listed above, 20 and an identification of the specific job that allows the job status to be tracked through the 21 computer network.

22 Use of the job ticket allows printing and similar services to be allocated to those 23 resources (i. e. , the operating units) that are best suited to completing the services. 24 Unfortunately, current computer systems do not allow access to the wide variety of 25 services existing in networked computer systems, such as the Internet. In addition, 26 current systems require users to have some knowledge of the existing resources, and may 27 require users to include applicable programming to communicate with the services.

28 Furthermore, current systems do not allow a job request to be split among several 29 processors. As a result, completion of the job request may take longer than necessary, 30 and may not be completed in the most efficient, lowest-cost manner.

31 Summary 32 To overcome these and other problems related to use of a job ticket, a method and 33 an apparatus allow a client to manage job attributes and processes using an electronic 34 service center. The service center includes a job ticket service that allows access and

1 modification of a job ticket by multiple users on a network. The method and apparatus 2 use a network-accessible job ticket to relate to a specific job or content. The job ticket 3 may be an object, such as an XML object, comprising routines and data. The content 4 may be stored on the network and may be accessed by multiple job tickets. Storage and 5 management of the job ticket are transparent to the user. The job ticket is stored in a 6 common location in the network. The job ticket remains in the same location in the 7 network, and users access only that portion of the job ticket required to complete a 8 designated process. Security measures may be added to limit access to those users 9 designated as being allowed to access the job ticket and the job file. The job ticket may 10 include a service ID that relates the job ticket back to the originating job ticket service. In 11 this way, a user who acquires all or part of the job ticket can refer back to the originating 12 job ticket service (and the original, or as-modified, job ticket) to verify any changes and 13 to ensure that the job ticket being accessed is up-to-date. The job ticket also includes a 14 job ID to refer the job ticket to a specific job.

15 The service center is coupled through a communications network to a front end 16 service. The front end service allows a user to generate a service or job request. The 17 communications network may be the Internet, or a local area network, for example.

18 The service center includes a service bus, to which are coupled a job store, the job 19 ticket service, and a work flow controller. Also coupled to the service center are one or 20 more processors that may be controlled to complete processes and tasks defined in the job 21 tickets.

22 The job ticket service may generate and store the job tickets. Job content (e. g. , a 23 PDF file) is stored in the job store. With this structure, the user does not have b manage 24 storage of the job content or to know which job store holds the job content. The job ticket 25 service controls access to the job tickets, and, through the use of the job tickets, also 26 controls access to job content in the job store, or elsewhere in the network. The job ticket 27 service may create a reference to the job ticket, and may use the reference to control 28 access to the job ticket.

29 The use of job tickets allows clients to define databases, and to store data though 30 the job ticket service. The databases may be used to hold contact lists, addresses, and 31 other personal data. The databases may also be used to store any other generic data. The 32 databases could then be used in conjunction with a variety of services provided by the 33 processors For example, an e-mail processor that provides mail services may be used 34 in conjunction with a personal contact list to send e-mail messages, transfer electronic

1 files, or to establish a chat room. The e-mail processor may access the contact list at 2 predefined intervals to send e-mail messages to a select group of e-mail addressees.

3 Furthermore, because the service center provides a single portal to processors that are 4 coupled to the communications network, the client need not have any knowledge of the 5 database structure, or the processing requirements of the processors.

6 In an embodiment, the job ticket may be used as a generic database in conjunction 7 with an e-mail service. A client may have established a list of e-mail contacts. The 8 contacts database may then be stored in the job store. A corresponding job ticket may be 9 stored at the job ticket service. The job ticket includes control data needed to send and 10 receive email through the service center. In an embodiment, the generic database may be 11 an XML or HTML database, or any other markup language database. The database may 12 also be a structured query language (SQL) database 13 The use of the job ticket also allows for parsing, searching and updating the 14 contacts database. For example, the client may desire to search the contacts database for 15 phone numbers by name. This search functionality is included in the job ticket, and 16 allows the job ticket service to provide the client with a list of phone numbers for all 17 entries in the contacts database by name 18 Description of the Drawings 19 The detailed description will refer to the following figures in which hke numeral 20 refer to like items, and in which.

21 Figure 1 is a block diagram showmg a prior art use of a job ticket; 22 Figure 2 is a tree diagram showing the processes in an example job ticket; 23 Figure 3 is a block diagram of a digital image work flow network ; 24 Figure 4 is a block diagram of a service center used with the network of Figure 3; 25 Figures 5A-5D illustrate an exemplary job ticket; 26 Figure 6 is a diagram of functions controlled by a job ticket service; 27 Figure 7 is a diagram showing access functions controlled by the job ticket 28 service, 29 Figure 8 is a block diagram illustrating additional control features of the job ticket 30 service ; 31 Figure 9 is a flow chart illustrating one of the processes controlled by the job 32 ticket service; and

33 Figures 10-16 are flow charts showing sub-processes in the overall process 34 illustrated in Figure 9.

1 Detailed Description 2 Figure 1 is a block diagram showing a prior art application of a job ticket service.

3 Job tickets are often associated with a printing standard, the job definition format (JDF).

4 The JDF is described in detail in JDF Specification Draft Spiral 4.0, available at 5 www. hpopensource. com, which is hereby incorporated by reference. In Figure 1, a user 6 1 generates a job request and sends the job request through a portal 4 to a processor 5.

7 The job request may include a job ticket data file 2 and a content file 3. The user 1 may 8 be a computer terminal in a networked computer system and the processor 5 may be a 9 networked printer. The job request may involve printing a document The document may 10 be represented by the content 3, which is a digital representation of text and images to be 11 printed. The intended format of the printed document may be described in the job ticket 12 file 2, which is simply a digital file that specifies how the printer is to print the document.

13 For example, the job ticket file 2 may require that the document be printed on back-to- 14 back pages.

15 In a specific application, the functions of the job ticket file 2 may be carried out 16 by a printer driver. The printer driver encodes control data related to printing the 17 document, and sends the control data and the content 3 to the printer (i. e, the processor 18 5). The printer accesses the control data and the content 3 to print the document.

19 While the application shown in Figure I works well to print a document, the 20 application has many drawbacks. In particular, if multiple processors are involved in 21 producing the document, each such processor will require access to the job ticket file 2 22 This access brings problems related to security, modification control and workflow 23 control. For example, each processor requiring access to the job ticket file 2 may ha\e to 24 wait on processing until a prior processor has completed use of the job ticket file 2. Thus, 25 the prior art application may result in unwanted delays in completing the job request.

26 Prior art applications of job ticket services also suffer because the user may not 27 know anything about the processors, including capabilities and availabilities of the 28 processors, or even if the processors exist. Thus, the user may not know which portal to 29 use to connect to a specific processor.

30 These and other problems are solved by a method and an apparatus that controls 31 access to a job ticket and associated content through use of a job ticket service. The job 32 ticket service includes mechanisms that arbitrate access to the job ticket among multiple 33 users of the job ticket, limit access to the job ticket by incorporating security features, and 34 ensure modifications made by one processor or user are reflected in the job ticket and the

content. In effect, the apparatus includes a generic database that couples input data from 2 clients as job requests with output services such as processors that perform tasks or 3 processes to complete the job requests. The database may have has the features of a 4 generic XML database in that it is extensible, and in that the clients need not have any 5 knowledge of the individual processes to be performed, or the internal programming 6 requirements of the processors. Thus, the clients may submit job requests to a service 7 center that will ensure that an appropriate processor or processors are assigned to 8 complete the job request. Other database formats may also be used.

9 Before describing the apparatus and method in detail, a review of a job ticket is 10 provided. Figure 2 is a node-tree diagram (or simply a node tree) 10 that illustrates II processes defined in a job ticket for printing a brochure. The brochure may be printed on 12 a commercial press, and may use digital content to generate plates for printing the 13 brochure. Within the node tree 10, the nodes specify a product, process, or group of 14 processes. Each node may modify, consume or create resources. Each node may contain 15 further nested nodes, or sub-nodes. The arrangement of nodes and sub-nodes may be 16 likened to a tree, and each node and sub-node may be referred to as a branch. A brochure 17 node 11 defines the features and parameters of the brochure. A cover node 12 defines the 18 parameters for producing the brochure cover. Inside pages node 13 includes the 19 parameters to produce the inside pages. The inside pages node 13 is shown with several 20 sub-nodes, including a sub-node 14 for digital plate making. The digital plate making 21 sub-node 14 itself includes two additional sub-nodes, a ripping sub-node 16 and a plate 22 making sub-node 18.

23 Each of the nodes and sub-nodes shown in Figure 2 has associated with it input 24 resources and at least one output resource. A resource may be described by parameters or 25 logical entities. The resource may be a physical entity such as a component, a handling 26 resource, or a consumable. A component resource may be the output of a node or sub- 27 node, such as a printed sheets. A handling resource is used during a process, but is not 28 consumed by the process. A consumable resource may be partly or wholly consumed by 29 the process. Examples of consumable resources include inks, plates, and glue Other 30 resources may be a digital file or representation of a physical object. For example, the 31 ripping sub-node 16 may include as input resources a run list, media, RIP parameters, and 32 layout. The run list resource describes the pages, including the files in which the pages 33 occur, and which pages are to be used. The media resource describes the media that will 34 be used to make plates, and is needed to describe the dimensions of the media. The RIP

1 parameters resource describes all device-specific parameters of the ripping process. The 2 layout resource describes placement of source pages onto the plates, and eventually onto 3 press sheets. As an output resource, the ripping sub-node 16 may provide ripped flats.

4 Other resources include parameter resources, which define the details of processes, as 5 well as other non-physical computer files used by a process.

6 The node tree 10 shown in Figure 2 is intended to apply to printing a document.

7 However, node-tree diagrams may be used to represent job tickets for other services 8 besides printing. For example, a job ticket may be used for data processing, image 9 processing, creating and maintaining a database, electronic publishing, e-mail, and 10 various e-commerce services. Moreover, the job ticket may be used to allow different o 11 commerce services to interact with each other.

12 Figure 3 is a block diagram of a digital imaging work flow (DIW) network 20 that 13 incorporates a service center and a job ticket service to control tasks submitted by clients.

14 The service center may operate as a single portal through which the clients connect to one 15 or more e-services including e-mail, e-commerce and online shopping, e-printing, and 16 data services, including database searching and database construction, population and 17 maintenance. Using a single portal, such as the service center, allows the clients to select 18 from a wide variety of & services, such as those noted above, without requiring the clients 19 to have any prior knowledge of the e-services.

20 The service center may include components that receive information in the form 21 of job requests, and using the information, create a job ticket that specifies tasks and 22 resources. The job ticket may be stored in a job ticket service, and notices may be posted 23 to indicate when a job ticket is available. Processors coupled to the service center may 24 bid on completion of the job ticket, and the service center may include a bidding service 25 that evaluates bids. The service center may select one or more processors to assign to the 26 job ticket based on client-supplied criteria, or based on a set of standard criteria, including 27 industry standard criteria. The service center may provide mechanisms to control access 28 to the job ticket, or to portions (branches) of the job ticket. The mechanisms include 29 branch locking, and authorization and authentication servers that use public key 30 encryption, or similar processes.

31 The service center may include hardware components such as servers, computers, 32 central processing units, communications interfaces, and memory devices to provide the 33 processing capability and data storage required to carry out the above-described 34 functions.

1 The DIW network 20 includes a front end service 30 that allows a client 31 to 2 generate and submit a service or job request. In an embodiment, the front end service 30 3 may be an Internet web browser. Alternatively, the front end service 30 may be a web 4 application or a port monitor. The job request may contain detailed information about 5 how the job is to be executed, and may be formatted according to the job definition 6 format standard. Alternatively, the job request may include only basic information, 7 which will be used by another component to finalize the job definition, or work flow.

8 Finally, the job request may include the content, or job, that is to be processed. The 9 content could be one or more digital files, text files, and other files. The front end service 10 30 is coupled to a communications network 35, which may be the Internet or a local area 11 network, for example. Coupled to the communications network 35 is a service center 40 12 that links one or more processors 80. to the communications network 35. Each of the 13 processors 80, may include a cache 811 that may be used to store information related to a 14 job request, including information related to job tickets. In an embodiment, the service 15 center 40 may be an Internet web site that includes data storage and control functions. In 16 another embodiment, the service center 40 is a node in a local area network.

17 The service center 40 allows a broad spectrum of communications between 18 entities coupled to the service center 40. In particular, the service center 40 allows 19 different e-services to interact programmatically with one another using specific protocols 20 and generic protocols (e. g., TCP/IP). This programmatic interaction allows different 21 services and processes that are coupled to the network to exchange data and files, and to 22 modify the data and files. The programmatic interaction may be completed by use of a 23 remote procedure call (RPC) between entities coupled to the service center 40. Other 24 methods for providing the programmatic interaction include CORBA, UDDI, and e- 25 speak.

26 Figure 4 is a diagram of the service center 40. The service center 40 includes a 27 service bus 41 in communication with the communications network 35 and the processors 28 8 of Figure 3. Coupled to the service bus 41 is a job store 50, a job ticket service 60, a 29 work flow controller 70, an optional bidding service 90, an authorization server 92 and an 30 authentication server 94. The job store 50 may store one or more job content files 51,.

31 The job ticket service 60 may control one or more job tickets 61.. The work flow 32 controller 70 may use one or more agents 71, to control processes on the service bus 41.

33 The job store 50, job ticket service 60 and work flow controller 70 function to 34 accept information from the clients 31, and to use the information to control the actions of

1 the processors 80i. The processors 80 : performs specific tasks or processes as determined 2 by the service center 40.

3 The job store 50 may be a node on the service bus 41, and may include 4 programming to allow the job store 50 to cany out its functions. The job store 50 may be 5 used to store the content 51, which may be in the form of one or more large files. In the 6 context of printing a document using a service or process coupled to the service bus 41, 7 the job store 50 may store the document content in one or more PDF files, for example.

8 The content 51 may include graphics and text The content 51 for a specific document 9 may include several files. For example, a brochure may have a separate file for the cover 10 and another file for the inside pages. Text for the inside pages may be in one file and 11 images in yet another file. The content 51 may also include links to other resources or 12 entities on the service bus 41. The job store 50 provides for mass storage of the content 13 51, so that a user (client 31 or processor 80) does not have to provide the mass storage 14 required for the job content 51. By using the mass storage capabilities of the job store 50, 15 the content 51 may be made to persist in the network 20, and may be made accessible to 16 users at any time. That is, the job store 50 may store the content 51 for an extended time.

17 The job store 50 also manages and controls the content so that the user (client 31 or 18 processor 80) does not have to manage the content 51. Management functions include 19 maintaining configuration or version control of the content 51, controlling access to the 20 content 51, and maintaming the content 51 in storage.

21 The job ticket service 60 holds job tickets 61. The job ticket service 60 controls 22 access to and may manage configuration of the job tickets 61. For example, the job ticket 23 service 60 may allow users (clients 311 and processors 80,) to access a portion or branch 24 of a job ticket 61 rather than passing the job ticket 61 among multiple users. Access to 25 the job ticket portion may be effectuated by use of an application programming interface, 26 a scriptable interface, or a similar feature. As noted above, the job ticket 61 does not 27 include the content 51 (e. g. , the graphical and text files of a document), but the job ticket 28 61 relates to content 51 (e. g. , a PDF file) stored in the job store 50. The user does not 29 have to manage storage of the job content or to know which job store 50 holds the job 30 content. The job ticket service 60 instead passes a reference in the job ticket 61. This 31 allows multiple clients 31 and processors 8Q to access the content 51. Furthermore, the 32 content 51 may relate to more than one job ticket 61. The job ticket service 60, and its 33 interrelationships with other entities coupled to the service bus 41, will be described later 34 in detail.

1 Some job tickets 61 may be accessed by multiple processors 80, in either serial, 2 overlapping, or simultaneous fashion. The multiple access processing could result in 3 problems with use of the job ticket 61. For example, a first processor may acqmre the job 4 ticket 61 (or a portion or branch thereof), and perform a process specified in the work 5 flow, which may modify the branch. Such modification may be to indicate a branch as 6 complete, use up input resources, or create new output resources, for example. A second 7 processor could attempt to acquire the branch, but might not"know"that the first 8 processor had modified the branch. Alternatively, if two processors compete for the same 9 branch, a deadlock situation might occur.

10 One solution to the above problems may be to lock the job ticket 61 whenever a 11 processor 80 acquires the job ticket 61. Unfortunately, locking the job ticket 61 may 12 prevent concurrent or parallel processing and may slow down completion of the job 13 request 32.

14 The job ticket service 60 shown in Figure 4 overcomes these and other problems 15 by having the capability to lock the job ticket 61 at the branch level. The branch locking 16 may be accomplished by one of several methods. The work flow controller 70 may 17 assign one or more specific processors 8Q to perform the tasks identified with the branch 18 to be locked. Where only one processor 80 is authorized access to the branch, branch 19 locking may not be required. Where more than one processor 80 is authorized access to 20 the same branch, the job ticket service 60 may lock the branch vhen one of the authorized 21 processors 80 actually acquire the branch.

22 If the work flow controller 70 has not assigned processors 8Q to branches (i. e., 23 any processor 80 may access a branch at any time), the job ticket service 60 may lock the 24 branch when a processor 80 acquires the branch.

25 The job ticket service 60 may lock the branches by setting a lock/unlock flag for 26 each branch. Processors 80, accessing the job ticket 61 may then review the lock/unlock 27 flag status to determine if the branch may be accessed. In some circumstances, the job 28 ticket service 60 may allow access only to those branches that are unlocked. A processor 29 80 that has completed a task defined by the branch may need to have the branch unlocked 30 in order to modify the branch.

31 The work flow controller 70 may be used to create the job tickets 61 that are 32 stored in the job ticket service 60. The work flow controller 70 may review the job 33 requests 32 submitted by the clients 31, and may then use a job ticket template to prepare

1 the job ticket 61. The work flow controller 70 may then send the job ticket 61 to the job 2 ticket service 60 for storage and processing.

3 The work flow controller 70 also controls completion of tasks among the 4 processors 80i. In an embodiment, the work flow controller 70 determines which of the 5 processors 80 have the necessary and available resources to begin the processes listed in a 6 specific job ticket 61. The work flow controller 70 then designates the appropriate 7 processors 80, to complete the tasks referenced by he job ticket 61. For example, if a job 8 ticket 61) requires color printing, the work flow controller 70 may determine that only 9 processor 803 is a color printer with the capacity to begin the job specified in the job 10 ticket 611. This embodiment in which the work flow controller 70 determines which 11 processors 80, to assign to a specific job ticket 61 may be especially appropriate when the 12 network 35 is a local area network and all processors 801 are directly coupled to the local 13 area network 35.

14 Alternatively, the work flow controller 70 may receive bid information from 15 Internet-connected processors z and may use the bid infonnation to select the 16 processors 80i to complete the job request 32.

17 The work flow controller 70 may also be used to designate the various nodes, 18 input and output resources, and other features of the node tree used to complete the job 19 request. That is, the work flow controller 70 may be used to create a construct, or work 20 flow, such as the node tree 10 shown in Figure 2. To accomplish these tasks, the work 21 flow controller 70 may include one or more agents 71, that write a job definition file, 22 based on control data contained in the job request 32. Alternatively, a separate 23 management information system (not shown) may be used to create the nodes, and to 24 control flow of tasks to the processors z and other entities. In yet another embodiment, 25 the job definitions may be written by the client 31 that originated the job request 32.

26 Referring again to the node tree 10 of Figure 2, many output resources of the 27 individual nodes serve as input resources for other nodes. These other nodes may not be 28 able to begin executing until all input resources are complete and available, which means 29 that the nodes may need to execute in a well-defined sequence. For example, a process 30 for making plates will produce press plates as an output resource that is required by a 31 printing process. In the hierarchical organization of the node tree 10, nodes that occur 32 higher in the node tree 10 represent higher-bvel, more abstract operations, while lower 33 order nodes represent more detailed, specific processes. Moreover, nodes near the top of 34 the node tree 10 may represent only intent regarding the components or assemblies that

comprise the product, and lower level nodes provided the detailed instructions to a 2 processor 80 to perform a specific process.

3 Because two node trees may not be similar, the work flow controller 70 may 4 determine processes to be completed, the order in which the processes are completed, and 5 the processors 8Q that are to complete the processes. The work flow controller 70 may 6 use the agents 71 to determine an actual work flow, considering factors such as control 7 abilities of the processors 80, that complete the processes, transport distances between 8 processors 8010 load capabilities of the processors, and time constrains in the job request, 9 for example. The agents 71 may define the overall process using serial processing, which 10 involves subsequent production and consumption of resources by the processors 8Q, 11 overlapping processing, which involves simultaneous consumption and production of 12 resources by more than one processor 80t, parallel processing, which involves sharing 13 resources among processors 80, and iterative processing, which involves a back and forth 14 processing scheme to develop resources.

15 Returning to Figure 4, the processors 80, may be used to provide data services to 16 the clients 31. However, each processor 80 can have a unique interface, data format, 17 query syntax, security protocol, and the like. For example, the processor 80 I may be 18 configured as a web server and so responds to hypertext transfer protocol (HTTP) request 19 packets and generates responses formatted as hypertext markup language (HTML) web 20 pages. In contrast other processors 80. may use file transfer protocol (FTP) or other

21 available transfer protocols, both public and private. In a particular example, each 22 of the processors 80. - 803 implements a database web server that hosts a"website" 23 having a predefined structure and access syntax and protocol In general each website is 24 designed to provide information about its database content response to queries (job 25 requests) communicated through network 20. Because each processor 80, may be created 26 and maintained by a separate organization, there is no uniform interface provided for 27 interacting with the various processors 80,. For example, the databases may relate to 28 customer lists in an e-commerce application, and the processor 801 may enable searches 29 by last name, phone number, zip code, or other searchable fields whereas the processor 30 8 (k may enable searches only by last name. Accordingly, and in the absence of the 31 service center 40, the job requests 32 must differ in content to evoke the desired response 32 from each processor 80,. Also, the processor 801 may require that a query be processed 33 through a series of pages before a response is generated. In contrast, the processor 80. 2 34 may allow direct, one-page access to submit queries and generate responses. Hence, the

1 processor 801 will require a series of communication packets to be received before the 2 desired response is generated whereas the processor 802 is potentially accessed with a 3 single communication packet that encapsulates the desired query data.

4 The service center 40 serves as an interface between the client 31 and the various 5 processors SO), and allows the client to submit data queries (job requests) without having 6 any prior knowledge of the database being searched, and its associated search engines.

7 In determining which of the processors 801 to assign to complete a particular job 8 request, the work flow controller 70 may poll the processors 80j that are coupled to the 9 service center 40. As noted above, the processors 8Q may be coupled directly to the 10 service bus 41, or may be coupled indirectly through another communications bus, such 11 as the Internet, for example. The polling may occur whenever a job ticket 61 is created 12 by the job ticket service 60. Alternatively, the polling and corresponding information 13 collection may occur on a periodic basis, and the work flow controller 70 may store 14 information related to the processors 80 15 As an alternative to polling, processors 80, coupled to the service center 40 may 16 monitor the job ticket service 60. The job ticket service 60 may periodically post, in a 17 bulletin board fashion, for example, notices for job tickets that are available for 18 processing. The processors 80, may then submit a bid for the tasks and processes defined 19 in the job ticket notice The work flow controller 70, or the separate, optional bidding 20 service 90, may review the bids, and determine which single processor 80 or combination 21 of processors 8Q would be best suited to complete the tasks and processes defined in the 22 job ticket notice.

23 The service center 40 may include several features to provide security and to 24 control access to the job ticket 61. As discussed above, the job ticket service 60 may 25 include a provision for branch locking In addition, servers may be used to authorize and 26 authenticate a processor 80 and maintain the authorization and authentication during 27 completion of a job request 32. The authentication server 92 receives authentication 28 information from a processor 80 and the authorization server 94 uses the information to 29 check authorization functionality. The authorization or access rights of the processor 80 30 may be carried as a part of the job ticket 61. The servers 92 and 94 may be hardware 31 devices, but need not exist in the same hardware platform, and the servers 92 and 94 reed 32 not be tightly coupled. Alternatively, the functions of the servers 92 and 94 may be 33 performed in programming stored in one of the components of the service center 40, such 34 as the work flow controller 70, for example. Using the above-described features, the

1 service center 40 may provide trusted authentication information about the processor 80 2 to the authorization server 94, and the authorization server 94 then performs its authority 3 check functions.

4 The job ticket 61 may be signed with an industry standard public key encryption 5 message digest (MD) signature, and may be protected by a public key encryption system.

6 Hence, any user that has the public key may validate the job ticket 61 without having to 7 communicate with the authentication server 92. These features reduce communication 8 between distributed server applications. The features also allow the job ticket 61 to be 9 passed from one processor 80 to another processor 80, maintaining security, without 10 communicating with the service center 40.

11 In an alternative embodiment, the job ticket 61 holds authentication/access data, 12 allowing controlled access within the service center 40 infrastructure Resources may be 13 protected by passwords and other mechanisms. Access to the job ticket 61 may be 14 similarly protected. Furthermore, processors 801 with access authorization may have such 15 access authorization invoked by listing the processors in the job ticket. The listing may 16 be effectuated by recording a network address for the processors 80"for example. The 17 network address may be incorporated in the bid information recorded in the job ticket 61.

18 Although the above description refers to development by the work flow controller 19 70, other components in the network 20 may be used to develop an overall work flow to 20 complete the job request 32. For example, the job ticket service 60 may be used to 21 develop the overall work flow.

22 As discussed above, the bidding service 90 may be used to receive bid information 23 from processors 80i coupled to the service center 40. The processors 8Q submit bids in 24 response to posting of job ticket notices at the service center 40. In an embodiment, the 25 job ticket notice is a separate object stored in the service center 40. In another 26 embodiment, the job ticket 61 itself serves the notice function. The work flow controller 27 70 may post the job ticket notices after receipt of the job request 32. Whether the bidding 28 service 90 or the work flow controller 70 receives the bids, the bid evaluation and 29 selection process may be the same.

30 The job ticket notice posted by the work flow controller 70 may include specific 31 tasks or processes (branches) that must be completed to complete the job request 32 (see 32 Figure 7). A simple job request 32 may have only one branch. More complex job 33 requests 32, such as the job request illustrated in Figure 2 (i. e. , print a brochure) may have 34 many branches. Furthermore, some branches may be so interrelated that they can only be

1 completed in a specific sequence, while other branches can be completed in a parallel or 2 an overlapping fashion. This interrelationship may often be the result of one branch 3 producing an output resource that is an input resource for one or more other branches.

4 The job ticket notice may include descriptions of specific branches and their 5 interrelationships in sufficient detail to allow the processors 8Q to bid for completion of 6 the branches. The job ticket notice may persist in the service center 40 for a specified 7 time to allow the processors 80, to send bids. The time may be a set value (e. g. , one hour) 8 or may be based on a completion deadline specified in the job request 32.

9 The bidding service 90 may select bids 91 from the processors 80. based on set 10 criteria. For example, the job request 32 may specify minimum performance 11 requirements (e. g. , a maximum cost and a completion deadline). The bidding service 90 12 may reject any bids that fail to satisfy the minimum performance requirements. Where 13 the work flow controller 70 has established multiple branches, each such branch may 14 include minimum performance requirements. The branch-specific performance 15 requirements may be established by the work flow controller 70 based on overall 16 performance requirements for the job ticket 61. A processor 80 that bids on a particular 17 branch may be rejected by the bidding service 90 if the processor 80 fails to meet the 18 minimum performance requirements.

19 If the client 31 does not specify any minimum performance requirements, the 20 bidding service 90 may apply a standard set of criteria (e. g. , an industry standard). In 21 addition, the bid must satisfy any requirements for producing output resources. In this 22 way, bids that are made in error, or that would otherwise likely be rejected, can be 23 screened out. For example, a bid for printing inside pages of the brochure may indicate a 24 one year completion date. Such a bid may be rejected, even in the absence of any 25 specified performance requirements from the client 31.

26 In addition to submitting performance requirements, the client 31 may specify an 27 evaluation algorithm for evaluating bids. For example, the client 31 may specify that cost 28 is to be weighted twice as much as any other performance requirement.

29 In the absence of a client-specified evaluation algorithm, the bidding service 90 30 may apply a standard evaluation algorithm in order to rank bids for each branch in the 31 work flow. The evaluation algorithm may apply weighting criteria, or may apply a 32 default rule. For example, bids may be ranked based on a maximum score, where points 33 are awarded for cost estimates below a maximum and for completion times below a 34 maximum. Once the evaluation algorithm has been applied, the bidding service 90 ranks

1 the bids for each branch. If only one processor 80 survives the process, that processor 80 2 may be automatically selected and assigned to the branch. If multiple processors 8Q 3 survive, the bidding service 90 may provide a list of such processors 8Q to the work flow 4 controller 70, which will then select the processors 80, to be assigned to the branches.

5 Alternatively, the list may be provided to the client 31, and the client 31 may select the 6 processor (s) 8Q to complete the tasks defined in the work flow.

7 The work flow controller 70 may associate winning bids with corresponding 8 branches, and may store the bid information with the job ticket 61. The stored bid 9 information may include identification information that allows the authorization server 94 10 and the authentication server 92 to permit access to job ticket branches or to the entire job 11 ticket 61. Because the bid information is stored with the job ticket 61, a processor 80 12 may access those branches for which the processor 80 is authorized access without having 13 to communicate directly with the job ticket service 61. This feature allows the job ticket 14 60 to be passed from one processor 80 to another processor 80, which improves 15 processing time and efficiency.

16 In an embodiment, the work flow controller 70 accesses control data of the job 17 ticket 61 to determine which processor (s) 80, should be assigned to the specific task 18 identified in the job ticket The work flow controller 70 may also identify which of the 19 processors 80, would be able to meet the criteria specified m the control data, and may

20 provide a list of such processors 80, to the client through the front end service 30. The 21 client 31 may then select a processors) 8Q from the list.

22 The job ticket service may, in an alternative embodiment, be implemented in 23 whole or in part by storing program instructions on a computer-readable medium, such as 24 a CD-ROM, for example. A computer processor may then implement method steps to 25 provide the job ticket service by reading and executing the program instructions.

26 Figure 5A illustrates an exemplary job ticket 61. The job ticket 61 may include 27 two parts. A first part includes a framework 62 and an optional client extension 64. The 28 framework 62 includes information, files and programming necessary to control tasks 29 defined in the job ticket 61. The client extension 64 may include information related to a 30 specific client (machine) and to a user of the machine. A second part includes a security 31 module 67 that protects the job ticket 61 from unauthorized access.

32 The framework 62 may include a job identification (ID) 63, a service ID 65, a task 33 section 68, and control data 69. The job ID 63 includes a reference to a specific job, or 34 content 51 that is stored in the job store 50. The job ID 63 also includes a reference to a

I particular job store 50 that is used to store the content 51. An entity that acquires a 2 reference to the job ticket 61 can use the job ID 63 to access the corresponding content 3 51. Thus, die network 20 shown in Figure 3 may include multiple job stores 50, and the 4 job ID 63 may be used to correlate the job ticket 61 to a specific job store 50. The service 5 ID 65 identifies a specific job ticket service 60 that stores the job ticket 61. For example, 6 the network 20 may include multiple job ticket services 60 (not shown in Figure 3). The 7 service ID 65 is used to correlate the job ticket 61 to the appropriate job ticket service 60.

8 The tasks section 68 (Figure 5B) may include branch definitions, and other 9 information needed to control completion of the branches. The tasks section 68 may be 10 structural so that each branch or node in a node tree is represented by one or more 11 branches 66 ; in the tasks section 68. In this embodiment, each node in the node tree (e. g., 12 the mode tree 10 of Figure 2) can have associated with the node, the description 95, 13 resources 96, lock/unlock flag 97, and security Matures 99. In this way, the job ticket 61 14 reflects a hierarchical database structure. The control data 69 includes the specific 15 instructions, parameters, and criteria for completing the task identified by the job ticket 16 61. The control data 69 may also include specific data required to complete tasks defined 17 m the job ticket 61. The control data 69 may also be associated with each node in a node 18 tree.

19 The security module 67 controls access to a specific job ticket. The security 20 module 67 may be implemented using standard encryption and access techniques, 21 including public/private key infrastructures, for example.

22 The client extension 64 may contain"custom"information, such as user age, 23 credit card number and zip code. Information provided in the client extension 64 may be 24 protected by use of a public key signature, or similar feature. Hence, all client extension 25 information will automatically be included in a Message Digest Protocol (MDP) and will 26 affect the signature of the job ticket 61. With the above-describe job ticket architecture, 27 many Internet-related security issues are addressed, including IP spoofing, time controlled 28 sessions, job ticket alterations, varymg authorization levels, and client-dependent 29 persistent data storing.

30 The job ticket 61 shown in Figure 5A may be used to refer to a specific content 51 31 in the job store 50. Alternatively, multiple job tickets 61 may be used to refer a specific 32 content 51, or one job ticket 61 may be used to refer to multiple contents 51. Thus, for 33 example, one job ticket 61 may specify a repetitive printing task to be completed on 34 similar documents, each of which has a different content 51.

1 Using the network 20 shown in Figure 3, and the corresponding job ticket shown 2 in Figure 5A, a client 31 may request and have completed many different electronic 3 services. For example, the client 31 may use the network 20 as an e-mail application.

4 Figure 5B shows the tasks section 68 in detail. The tasks section 68 may include 5 one or more branch descriptors 66 that include information related to processing for that 6 branch. A description segment 95 may define the tasks to be completed for each branch.

7 Alternatively, the description segment 95 may provide a link, or handle, to a file that 8 contains the branch description. The resources segment 96 lists input and output 9 resources associated with the tasks defined for the branch. The lock/unlock flag segment 10 97 allows a flag to be set to lock and unlock a branch. A bid information segment 98 11 includes bid information gathered, for example, by the bidding service 90. The bid 12 information 98 may include detailed information such as the IP address of the processors 13 authorized access to the branch, estimated performance information (e. g. , estimated cost, 14 delivery time), and other information. Alternatively, the bid information 98 may contain 15 a link to another file containing the detailed bid information. The security segment 99 16 may indicate authorized security levels, and may be used as part of a public 17 key/private key infrastructure.

18 Figure 5C illustrates an embodiment of the control data 69. The control data 69 19 includes a client address, which may be a machine address, such as an Internet protocol 20 (IP) address. An expiration date/time segment may be used to terminate active status of 21 the ticket 61. Once terminated, the ticket may be deleted from the job ticket service, and 22 the corresponding content 51 may be de-referenced. That is, the contents may no longer 23 be referenced by a specific job ticket 61. This feature may help eliminate stale data, and 24 free up resources for other job requests 32 (see Figure 7). Finally, the control data 69 25 may include specific performance requirements, such as cost an delivery, warranty, 26 required materials, price reductions based on quantity, and other requirements, for 27 example.

28 The use of job tickets as XML objects allows clients to define databases, and to 29 store data through the job ticket service 60 and the job store 50. The databases may be 30 used to hold contact lists, addresses, and other personal data. The databases may also be 31 used to store any other generic data. The databases could then be used in conjunction 32 with a variety of e-services provided by the processors 8Q. For example, an e-mail 33 processor 80 that provides e-mail services may be used in conjunction with a personal 34 contact list to send e-mail messages, transfer electronic files, or to establish a chat room.

1 The 6-mail processor 80 may access the contact list at predefined intervals to send 6-mail 2 messages to a select group of email addressees. Furthermore, because the service center 3 40 provides a single portal to processors 80 that are coupled to the communications 4 network 35, the client 31 need not have any knowledge of the database structure, or the 5 processing requirements of the processors 80.

6 In the specific application of the generic XML database to an email service, the 7 client 31 may have established, as a generic database, a list of e-mail contacts. The 8 contacts database may then be stored in the job store 50 as a content file 51. A 9 corresponding job ticket 61 may be stored at the job ticket service 61. The job ticket 61 10 includes control data needed to send and receive e-mail through the service center 40. 11 Furthermore, the job ticket 61 serves as a pointer to data in the content file 51. In 12 particular, the job ticket 61 may store XML data that is related to other data stored in the

13 content file 51.

14 Alternatively, the job ticket 61 may store the contacts data. This alternative takes 15 advantage of the fact that the job ticket 61 includes a vocabulary that can be extended to 16 include the contact data, and that the vocabulary can be further extended to include 17 properties for each contact in the contact data. For example, the job ticket 61 may specify 18 that a contact is a business contact or a personal contact. Other properties may also be 19 included, such as whether the contacts in the contact database use mobile phones, land 20 line phones, facsimile machines, and e-mail addresses.

21 The use of the job ticket 61 also allows for parsing, searching and updating the 22 contacts database. For example, the client 31 may desire to search the contacts database 23 for phone numbers for all persons whose first name is Joe. This search functionality is 24 included in the job ticket 61, and allows the job ticket service 60 to provide the client with 25 a list of phone numbers for all entries in the contacts database where the person's first 26 name is Joe. That is, the contacts database includes entries having the property of Joe, 27 and he job ticket service is able to search the contacts database for this property, and to 28 return a list of those entries to the client 31.

29 The properties function of the job ticket 61 also allows the job ticket service 60 to 30 control specific tasks desired by the client 31, or to indicate to the client that a desired 31 task cannot be completed. Staying with the example of the contacts database, the client 32 31 may desire to send a facsimile transmission to all entries in the contact list that have a 33 specific zip code. The job ticket service 60 can search the contacts database by 34 properties, looking for zip code. The job ticket service 60 can also search the contacts

I database to determine if any entry does not have a facsimile machine. For those entries 2 that do not have a facsimile machine, the job ticket service 60 can originate a message to 3 send back to the client 31, informing the client 31 that the facsimile transmission was 4 undeliverable. Using this functionality, the client 31 need not know anything about the 5 intended recipients of the facsimile transmission.

6 Returning to the example of an e-mail service, at the client 31, an e-mail 7 application may be launched in order to send an e-mail message, using the Internet, to one 8 or more contacts in the contact database. However, the client 31 need not subscribe to 9 any one Internet service provider. Instead, the service center 40 determines which 10 processor 80 best suits the client's needs for sending the e-mail message. That is, the 11 service center 40 may select a e-mail service provider (a processor 80) to send the e-mail 12 message to a chosen destination address. Furthermore, the service center 40 may 13 determine, based on infonnation maintained in the contact database (i. e. , the content 51 in 14 the job store 50), which delivery options are desired by a user at the destination address.

15 For example, the destination address user may desire that all e-mail messages be sent to 16 an e-mail box, or that an alert be provided whenever an e-mail message is sent. These 17 delivery features may be stored in the contact database in the job ticket 61. Alternatively, 18 the delivery features may be stored in a separate database (content file 51) in the job store 19 50, and the service center may retrieve information form this separate database when 20 detennming how to deliver the e-mail message. Specifically, the separate database may 21 include a variety of users, along with the user's Internet address By comparing the 22 Internet address provided with the out going e-mail to the Internet addresses in the 23 separate database, the service center 40 can determine desired delivery options of the 24 addressee. This process for determining delivery options is transparent to the client 31 25 that onginated the e-mail message. All that the client 31 need know is the contact 26 information (e. g. , the Internet address or a contact name).

27 The client 31 may use the job ticket service 60 to specify a number of 28 performance features related to the email service. For example, the client 31 may want 29 the service center 40 to attempt a specified number of delivery attempts, and if delivery 30 does not occur, to send a return message to the client 31 indicating non-delivery of the e 31 mail message.

32 In another application, the service center 40 may operate as a focal point for a 33 client's messaging systems. The service center may receive and store messages in the job 34 store 50, or within a job ticket 61. Preferably, a separate content file 51 or job ticket 61 is

1 established for each client 31 having an account on the service center 40 so that all of the 2 messages for a single client 31 will be stored in the same directory.

3 The network 20 shown in Figure 4 may include the necessary communications 4 interfaces to support voice, e-mail, and facsimile transmissions. When a call arrives at 5 the service center 40, a central processor (not shown in Figure 4) may read an incoming 6 address signal from the originating user, and use the address to store the message in the 7 appropriate job ticket 61.

8 In addition to handling incoming calls and storing the messages, the service center 9 may coordinate a response from the client 31. For example, the client may request a 10 specific response (e. g. , and out of office notice) to an e-mail message from a user The 11 responses may be stored as part of the client's content file 51. The job ticket service 60 12 may access the content file 51, and download an appropriate response message. The job 13 ticket service 60 may then use a processor 80 to deliver the response back to the 14 originating user.

15 The job ticket service 60 may also mclude software to transform incoming 16 messages (voice, facsimile) into XML files for storage in the content file 51 The job 17 ticket 61 or the content file 51 may contain the data indicating the preferences of the 18 client 31. Thus, for example, when a facsimile message in the TIFF/F format is retrieved 19 by the service center 40, the job ticket service 60 may ascertain from the data in job ticket 20 61 the preferred option of displaying the facsimile message and would generate the 21 appropriate HTML files. The service center 40 may be 22 connected to a paging system processor 80. Upon the arrival of a new message, in 23 addition to sending an e-mail message to the client's mailbox, the service center 40 may 24 also activate the paging system processor 80 so that a pager (not shown) would be 25 activated. In this manner, the client 31 could receive almost instantaneous notification 26 that a message has arrived.

27 The service center 40 may use the data m the job ticket 61 to provide other 28 information and alerts to the client. For example, the service center 40 may send a 29 message to the client to indicate upcoming appointments, and special dates, such as 30 birthdays. The client 31 may designate in the control data section of the job ticket 61 that 31 birthday greeting be automatically sent to specific individuals whose information is stored 32 in the job ticket 61 33 The service center 40, when supporting client communications, may operate 34 according an asynchronous manner. In an asynchronous mode of operation, information

1 requested by the client 31 may not be available and may have to be generated after the job 2 request 32. The asynchronous mode of operation is preferred since fewer files are 3 generated, thereby reducing the required amount of storage. Because the information 4 requested by a client 31 may not be available, some anchors cannot specify the filename, 5 such as"2. html," but will instead contain a command for the file. For instance, an anchor

6 may be defined as < AHREF=/faxweb/clients/2496801l viewpage. cgi ? FAX. sub. - 7 NUM=l & PAGE=l & VIEW. sub.- MODE=FULL > for causing a CGI to run a viewpage 8 program so that page 1 of facsimile message 1 will be displayed in a full size image. The 9 CGI will generate the requested information when the information has not been 10 generated, otherwise the CGI will retrieve the information and relay the information for 11 transmission to the client 31. The service center 40 can reliably 12 receive voice, facsimile, and data messages for a plurality of clients 31 and can receive 13 more than one message for a client 31 at a single time. The messages are stored by the 14 service center 40 and can be retrieved at the client's convenience at any time by 15 connecting to the service center 40. This use of the service center 40 16 provides a great number of benefits. 1k client 31 would not need a facsimile machine, 17 voice mail system, or a machine dedicated for receiving data messages The client 31 18 also need not worry about losing part of the message or violating the confidential nature 19 of the messages. The client 31, of course, can still have a facsimile machine and 20 dedicated computer for data messages. The service center 40, however, will permit the 21 client 31 to use the telephone company's call forwarding feature so that messages may be 22 transferred to the service center 40 at the client's convenience, such as when the client 31 23 is away from the office. Furthermore, the client 31 may be 24 provided with a greater or fewer number of options m displaying or retrieving messages.

25 The options may permit the client 31 to review or retrieve the messages in other formats.

26 The options may also permit a client 31 to join two or messages into a single message, to 27 delete portions of a message, or to otherwise alter the contents of the messages. The 28 service center 40 may restrict a client 31 to only certain types of messages. For example, 29 a client 31 may want the service center 40 to store only facsimile messages in order to 30 reduce costs of using the service center 40. In such a situation, the service center 40 31 would perform an additional step of checking that the type of message received for a 32 client 31 is a type of message that the service center 40 is authorized to receive on the 33 client's behalf. When the message is an unauthorized type of message, the service center 34 40 may ignore the message entirely or the service center 40 may inform the client 31 that

1 a user attempted to send a message to the service center 40. The service center 40 2 has been described as converting the messages into XML and transmitting the XML files 3 to the client 31. The XML format, however, is only one format for exchanging

4 information on the Internet and is actually only one type of a Standard Generalized Mark- 5 Up Language. The service center 40 is therefore not limited to the XML format but may 6 be practiced with any type of mixed media page layout language that can be used to 7 exchange information on the Internet. According to an embodiment, the 8 service center 40 may be used as a file repository serving as an archive for a particular 9 client 31 or group of clients 31 As described above, the service center 40 may maintain a 10 list of all messages for a particular client 31, which is displayed to the client 31 when the 11 client 31 accesses a mailbox. The service center 40 may store all messages, whether they 12 are voice, facsimile, or data, for a client 31 in the database indefinitely. The service 13 center 40 may therefore be relied upon by a client 31 to establish the authenticity of a 14 message and the existence or absence of a particular message. Through the service center 15 40, a client 31 can therefore mamtain an accurate record of all received email messages, 16 facsimile messages, and data transfers. In addition to serving as a file 17 depository, the service center 40 may also function as a document management tool.

18 When the service center 40 receives a message, the service center 40 updates a database 19 (content file 51) with information on the message This information includes the type of 20 message, whether it is a facsimile message, voice message, or data message, the time and 21 date at which the message was received, the size of the file, such as in bytes, the 22 telephone number of the caller leaving the message, as well as other information, such as 23 the number of pages of a facsimile message. Because the address (e. g. , a telephone 24 number or e-mail address) called is unique for each client 31, the information also 25 includes the mtended recipient of the message.

26 As noted above, the job ticket 61, in conjunction with other components of the 27 service center 40, may also be used to create a persistent, generic object-based data 28 structure, such as an XML database. An example of the use of a job ticket 61 for this 29 purpose is illustrated in Figure 5D The job ticket 61 includes a contacts list 84, which 30 may be in the form of an XML database, or some other generic database. The contacts 31 list 84 may include a structure with entries for business 85 and personal 86 use. The 32 business 85 and personal 86 contacts structures may include entries of individuals 87, as 33 shown Each of the entries 87 may include specific properties, as defined above. In

1 addition, or alternatively, each of the entries 87 may include links to other databases that 2 provide additional information and properties about the individual.

3 While the use of the job ticket 61 as a XML database has generally been described 4 with reference to an e-mail and messaging service, the job ticket 61 is not so limited.

5 Any data that is capable of being stored in a database may be accesses and controlled 6 using the job ticket 61.

7 The features described above, and shown in Figures 5A-5D may be replicated in 8 another embodiment of a job ticket 61 in which all data related to a specific node or 9 branch is located with that node or branch. Using the example node-tree 10 shown in 10 Figure 2, each node (branch) may include detailed information, and features such as 11 resources, authorized processors 8Q, lock/unlocked Sag, bid information, branch 12 description, and other information.

13 Figure 6 is a diagram of functions of the job ticket service 60. The primary 14 functions of the job ticket service 60 are to store 73 the job tickets 611 and to provide 15 access 75 to the job tickets 61, to users such as the client 31 and to the processors 8 (\. To 16 accomplish these storage and access functions, the job ticket service 60 may create a job 17 ticket reference 72 and a job resource reference 74. The job ticket service 60 also 18 controls job content access 76, updates 77 the job tickets 61, as processes are completed 19 and reported by the processors 8Q, completes the job tickets 61, and reports 78 when all 20 processes are completed for a specific job ticket 61, and provides an approval process 79 21 to allow a client 31 to approve completion of the tasks designated in the job ticket 61.

22 The job ticket reference 72 includes a specific reference to a corresponding job 23 ticket 611. The job ticket reference 72 may be used by the job ticket service 60 to allow 24 one or processors 80, and clients 31, to access the job ticket 61. That is, instead of 25 passing the pb ticket 61 to a processor 80, the job ticket service 60 passes the job ticket 26 reference 72. With the job ticket reference 72, the processor 80 may access all or a part 27 of a job ticket 61 so that the processor 80 may complete one or more processes. Unlike 28 conventional job ticket services, the job ticket service 60 retains the job ticket in storage 29 73, and only permits users (clients 31 and processors 80) to access the job ticket 61. This 30 feature allows multiple processors 80 to simultaneously complete processes for the 31 specific job request 32 related to the job ticket 61.

32 The job ticket service 60 may also create a resources reference 74, and may 33 provide the resources reference 74 to the processors 80 and the clients 31 in a manner 34 similar to that of the job ticket reference 72. As noted above with the description

u 1 accompanying Figure 2, the resources may include physical devices and materials, and 2 may include digital files. Use of the resources reference 74 may simplify data included in 3 the job ticket 61.

4 Alternatively, information contained in the resources reference 74 may be 5 included in the job ticket 61, or may be included in other files accessed by the clients 3 !.

6 and the processors 80i.

7 Figure 7 is a diagram showing operation of selected functions of the job ticket 8 service 60. As shown in Figure 7, the job ticket service 60 includes a job ticket 611, 9 which may be a programming object such as that represented in Figure 2, and described 10 above. The job ticket 611 is shown supplied to the job ticket =vice 60 by the client 311. 11 The client 311 may be a networked computer or similar device that is capable of 12 transmitting me digital information representing the job ticket 6] to the job ticket service 13 60. To ensure the job ticket 61j arrives at the job ticket service 60, the job ticket 611 may 14 contain a reference to the job ticket service 60, such as the service ID 65 illustrated in 15 Figure 5A. The service ID 65 may include a network address of the job ticket service 60.

16 For example, the service ID 65 may include a universal resource locator (URL) if the job 17 ticket service 60 is an Internet web site.

18 Also shown in Figure 7 are client 312 and processors 80 ;-80. The processors 1 9 8%-8ON may include networked resources such as networked printers, electronic- 20 commerce entities, such as Internet web sites, and"brick and mortar"entities, such local 2 I print shops that are coupled to the job ticket service 60 using the service bus 41.

22 The client 31 generates a job request 32 (content 51 and job ticket data). Using 23 the front end service 30 (not shown in Figure 7) and the service bus 41, the client 311 24 sends the job ticket data to the job ticket service 60 and the content 51 (not shown in 25 Figure 7) to the job store 50. The job ticket service 60 may pass the pb ticket data to the 26 work flow controller 70, which will create a job ticket 61. The content 511 and the job 27 ticket 611 are related by the job ill 63. The job ID 63 also includes an identification of 28 the job store 50, and a location within the job store 50 in which the content 5It is stored.

29 In an alternate embodiment, the content 51, may be stored at the client 311, and may then 30 be accessed by other users through the service bus 41 and the front end service 30.

31 The job ticket 611 specifies processes that must be completed to finish the job 32 request 32. As noted above, Figure 2 illustrates processes required to print a brochure, 33 including the inside pages and the cover. More that one processor 8Q may be required to 34 complete such a job request, or to complete the job request in the most cost-efficient

I andlor timely manner. The work flow controller 70 (not shown in Figure 7) can 2 determine which of the processors 801-80N should complete a specific process, and, if 3 necessary, the order in which such processes should be completed. The work flow 4 controller 70 may poll the various processors 80, to determine which may be used to 5 complete the job request. The work flow controller 70 may then notify selected 6 processors 80, that a job request has been registered with the job ticket service 60.

7 For each job ticket 611 received, the job ticket service 60 creates a reference 72. to 8 the job ticket 61,. The processor 80 ; may request access to the job ticket 61 in order to 9 complete one or more processes. In response, the job ticket service 60 provides the 10 processor 801 with the job ticket reference 72]. The job ticket reference 721 is then used II as an index to the job ticket 611. The job ticket reference 72] may also be provided to 12 other processors, such as the processor 802, and to other clients, such as the client 3h.

13 The processor 8Q2 and the client 312 may then access the job ticket 61] at the same time as 14 the processor 80] accesses the job ticket 61]. This simultaneous access allows different 15 processes to be completed in parallel. In the example illustrated in Figure 2, the 16 processor 80 I may complete some or all the processes for the inside pages, and the 17 processor 80 may complete the processes for the cover.

18 Figure 8 is a block diagram illustrating an example application of the control 19 features of the job ticket service 60. The job ticket 611 is referenced to the job content 20 5h by the job ticket ID 63, and information related to the job ticket 611 and the job 21 content 511 is passed over the service bus 41. The processors 8Q can access the job 22 content 511 and the job ticket 61] using the service bus 41. In the illustrated example, the 23 job ticket 61] refers to a job request 32 to print a brochure using the processes- outlined in 24 Figure 2. The processor 80] is designated by the work flow processor 70 to produce the 25 inside pages of the brochure and the processor 802 is designated to produce the brochure 26 cover. The processor 80] passes a job ticket access request to the job ticket service 60.

27 The access request may include security information that allows the processor 80] to 28 access the job ticket 61] and the corresponding content 511 or job. In response, the job 29 ticket service 60 provides a job ticket reference 621 that is used by the processor 80] to 30 access the job ticket zu The processor 801 may use information in the job ticket 611 to 31 access the content 5 h stored in the job store 50. Since the processor 8 1 will produce 32 only the inside pages, the processor 80] will not need access to all the information 33 contained in the job ticket 61]. Furthermore, because the job ticket 61] remains in the job

1 ticket service 60, other entities, such as the processor 802, may continue to access the job 2 ticket.

3 As the processor 80) completes various processes, the processor 80t may update 4 the content 511 and the job ticket 611. Thus, the job ticket 61) may reflect the latest status 5 of the job request 32. The status reports may indicate when a node in the node tree 10 is 6 completed, when an interim deadline is completed, when another processor may be used 7 to complete a process, and when all processing is complete. The status report may be 8 included in a digital file that is used by the work flow controller 70, for example. The 9 status report may also be included in a human-readable format, such as a pop-up window 10 on a computer display screen. The processor 801 may receive the job ticket reference 72), 11 and may complete all scheduled processes, returning the job ticket reference 72) to the 12 job ticket service 60. The processor 80) may also send a copy of the job ticket reference 13 721 to the processor 802, so that the processor 802 may access the job ticket 61 h and the 14 content z and produce the brochure cover.

15 Figure 9 is a flowchart illustrating an operation 100 of the job ticket service 60.

16 The operation 100 is based on completing the inside pages nodes shown in Figure 2. The 17 operation 100 may be at least partly under the control of the work flow controller 70, or 18 some equivalent device. The operation 100 assumes that a job request 32 (job ticket data 19 and content) have been passed to the service center 40, and that a job ticket service 60 has 20 been created. The operation 100 begins at start block 101. In review and assign 21 processors block 105, the work flow controller 70 determines which processors 80, are 22 able and available to complete the job. The work flow controller 70, or the optional 23 bidding service 90 may use polling or bidding features to make the determination. If 24 more than one processor 80, is available, and can satisfy the requirements of the job ticket 25 61, the work flow controller 70 may assign one specific processor 80 to the job.

26 Alternatively, the work flow controller 70 may provide a list of processors 8Q to the 27 client 31, and allow the client 31 to select one or more processors 80,.

28 In request job ticket block 110, a processor 80, having been authorized access to a 29 job ticket 61, sends an access request to the job ticket service 60 using the service bus 41.

30 In block 115, the job ticket service verifies that the processor 80 may access the job ticket 31 61. Access may be controlled by a password, an identification, and a public key/private 32 key security system, for example. In block 115, if the processor 80 is denied access, an 33 error signal may be sent to the processor and/or the client 31, block 120.

1 In block 115, if access is authorized, the job ticket service 60 provides the 2 processor 80 with a copy of the job ticket reference 72 corresponding to the job ticket 61, 3 block 125. The job ticket reference 72 allows the processor 80 to access the job ticket at 4 any time. By accessing the job ticket 61 at any time, the processor 80 is able to view an 5 updated version of the job ticket 61 as changes are made to the job ticket 61 by other 6 entities, including other processors 80.

7 In block 130, the job store 50 provides access to the job content 51 that is 8 referenced by the job ticket 61. Only that part of the content 51 that may be needed by 9 the processor 80 may be supplied by the job store 50. For example, if the processor 80 is 10 only to generate the inside pages of the brochure, the job store 50 may not provide access 11 to the content required to produce the brochure cover. After receiving the job ticket 12 reference 72 and the content 51, the processor 80 may perform one or more tasks using 13 input resources to produce an interim or final output resource. With completion of each 14 node in the node tree 10, the processor 80 may provide an input to the job ticket service 15 60 to allow modification of the job ticket 61, block 135. If the processor 80 completes all 16 required processes, the processor 80 may provide a final status report to the job ticket 17 service 60, block 140, along with any final modifications to the job ticket 61.

18 In block 145, the job ticket service 60 and the work flow controller 70 determine 19 if any additional tasking may be required If additional tasks are required, the work flow 20 controller 70 will ensure the appropriate processors 80 are assigned, and the operation 21 returns to block 110. If no additional processes are required, the operation moves to 22 block 150 and ends.

23 Figure 10 is a flowchart illustrating the routine 105 for developing a work flow 24 and assigning processors to the work flow. The process starts in block 200. In block 205, 25 the service center 40 receives a job request 32. The job request 32 may specify 26 performance requirements, resources, and other parameters, and may include content 51, 27 or a link to the content 51. In block 210, the work flow controller 70 defines a work flow 28 to accomplish the tasks specified in the job request 32. The work flow may be 29 represented by a node tree, such as the node tree 10 shown in Figure 2.

30 In block 230, the work flow controller 70 generates a job ticket 61 using the 31 information provided by the job request 32, the work flow generated in block 210, and an 32 appropriate job ticket template. The job ticket 61 is then stored in the job ticket service 33 60. Any content 51 may be stored in the job store 50.

The work flow controller 70 or the job ticket service 60 may create a job ticket 2 notice, or other object, and may post the notice, block 250, at the service center 40 so that 3 outside entities (e. g., the processors 80) may acquire sufficient information to bid on 4 completion of the job ticket 61, or a branch 66 of the job ticket 61. In an alternative 5 embodiment, the job ticket 61 may be posted at the service center 40. If the job ticket 61 6 is posted, the job ticket 61 may include mechanism to limit access to the job ticket or to 7 limit access to certain portions of the job ticket 61. For example, the client extension 64 8 may not be accessible to the processors 80.

9 In block 270, the service center 40 receives bids from specific processors 80 and 10 in block 290, the service center 40 evaluates the bids. In block 295, the service center 40 11 detennines if the client 31 submitting the job request 32 intends to select the winning 12 bid (s), or if the service center 40 makes the selection. If the client is to make the 13 selections, in block 300, the service center 40 provides the bid information to the client 14 31. Then, in block 305, the service center 40 receives the selections from the client 31. If 15 the service center 40 is to make the selections, in block 310, the service center 40 selects 16 the winning bid (s). In block 315, the service center notifies the winning processors. The 17 service center may also store the bid information with the corresponding job ticket 61. In 18 block 320, the routine 105 ends.

19 Figure 11 is a flowchart illustrating the sub-routine 210 for definmg a work flow 20 The sub-routine 210 starts in block 350. In block 355, the work flow controller 70 21 determines if the work flow will contain multiple branches. If the work flow will contain 22 multiple branches, the work flow controller 70 defines the branches, block 360. In block 23 365, the work flow controller 70 selects a branch for which resources and processes are to 24 be defined. In block 370, the work flow controller 70 defines mput resources for a first 25 process, or node. In block 375, the work flow controller 70 defines the tasks to be 26 completed for the first process. In block 380, the work flow controller 70 determines the 27 output resources of the first process. In block 385, the work flow controller 70 28 determines if another process is required for the work flow or branch. In no additional 29 processes are required, the work flow controller 70 determines if another branch is to be 30 defined, block 390. If another branch is to be defined, the work flow controller 70 selects 31 another branch, block 365, and the sub-routine 210 continues. If another branch is not to 32 be defined, the sub-routine 210 ends, block 395. The results of the work flow definition 33 may be incorporated into the job ticket 61 (see Figure 10, block 230).

1 Figure 12 is a flow chart illustrating the sub-routine 250 of posting a job ticket 2 notice or job ticket The sub-routine 250 starts in block 400. In block 405, the work flow 3 controller 70 determines if the work flow associated with the job ticket 61 includes 4 multiple branches. If the work flow does not include multiple branches, the work flow 5 controller posts the job ticket notice listing the single branch, block 410. If the work flow

6 mcludes multiple branches, the work flow controller 70 posts the job ticket notice with 7 multiple branches, block 420. The sub-routine 250 then ends.

8 Figure 13 is a flow chart illustrating the sub-routine 290 for evaluating bids. The 9 sub-routine starts in block 440. In block 445, the bidding service 90 selects a first bid for 10 analysis. In block 450, the bidding service 90 determines if the client 31 has supplied any 11 evaluation criteria or requirements. If the client has not supplied evaluation requirements, 12 the biddmg service 90 compares the selected bid to a set of standard, minimum 13 performance requirements, which may be industry-standard requirements, block 455. In 14 block 460, the bidding service 90 determines if the bid meets the minimum performance 15 requirements. If the bid does not meet the minimum performance requirements, the bid is 16 rejected, block 475. If the bid is rejected, the bidding service 90 determines if additional 17 bids were submitted, block 495. If additional bids were submitted, the bidding processor 18 90 returns to block 445 and selects the next bid for evaluation.

19 If in block 450, the client 31 has supplied performance requirements, the biddmg 20 service 90 compares the selected bid to the client-supphed performance requirements, 21 block 465. In block 470, the bidding service 90 determines if the selected bid meets the 22 minimum criteria of the chent-supplied performance requirements. If the minimum 23 critena are not met, the biddmg service 90 rejects the bid, block 475.

24 In blocks 470 and 460, if the minimum cntena are met, the bidding service 90 25 detennmes if the client 31 has supplied an evaluation algorithm If the client 31 has not 26 supplied an evaluation algorithm, the bidding service applies a standard evaluation 27 algorithm, which may be an industry-standard algorithm, block 485 If the chent has 28 supplied an evaluation algorithm, the bidding service 90 applies the client-supplIed 29 evaluation algorithm, block 490 The bidding service 90 may then store the results of the 30 algorithm pending evaluation of all bids.

31 In block 495, the bidding service 90 determines if any bids remain to be evaluated 32 If additional bids remain, the subroutine 290 returns to block 445, and the bidding 33 service selects the next bid for evaluation. In block 495, if no additional bids remain for

1 evaluation, the bidding service 90 ranks the bids, block 500. The sub-routine 290 then 2 ends, block 505.

3 Figure 14 is a flowchart illustrating the routine 130 for providing access to a job 4 ticket 61. The routine 130 begins in block 510. In block 515, the job ticket service 60 5 receives a job ticket reference 72 from a processor 80, and retrieves the corresponding job 6 ticket 61, block 520.

7 In block 525, the job ticket service 60 compares the processor identification to 8 processors listed in the job ticket 61 or branches 66 of the job ticket 61. The job ticket 9 service 60 determines if the selected branches 66 are locked, block 530. If the selected 10 branches 66 are not locked, the job ticket service 60 copies the selected branches 66 to the 11 processor 80, block 535. In block 550, the job ticket service 60 then determines if the 12 selected branches 66 require locking. If the selected branches do not require locking, the 13 routine 130 ends, block 560. If the selected branches 66 require locking, the job ticket 14 service 60 locks the selected branches 66, block 555. The routine 130 then ends, block 15 560.

16 In block 530, if the selected branches 66 are locked, the job ticket service 60 17 determines if the processor 80 intends to modify information in the selected branches 66, 18 block 540. If the processor 80 will not modify the selected branches 66, the job ticket 19 service 60 may provide an error message, block 545. If the selected branches 66 will be 20 modified, the job ticket service 60 may unlock the selected branches 66, block 547.

21 Figure 15 is a flow diagram of a method for allowing access to a job ticket 61 22 The method may execute as part of the routine 115 shown in Figure 9 The method starts 23 with block 600. In block 605, the authentication server 94 receives authentication 24 information from a processor 80 and retrieves a job ticket 61 corresponding to a job ticket 25 reference 72 possessed by the processor 80. At this stage of the process, the job ticket 61 26 (excluding the public key signature field 67) contains two Information fields, the 27 framework 62 and the client extension 64. The framework 62 contains information such 28 as the service ID, client IP address, expiration date and time, and processor authorization, 29 as previously described The client extension 64 contains information such as credit card 30 number and zip code, also previously described The information in the job ticket 61 31 (excluding the public key signature field 67) is then, for example, optionally hashed 32 using, for example, MD5 protocol, and encrypted with a public key encryption system, 33 block 610, generating a hash number, block 615. Other hashing or encryption techniques 34 may also be used. The hash number is representative of the specific information

contained in the job ticket 61. The hash number generated in block 615 is then encrypted 2 using a standard public key ernyption system, block 620. Encrypting the hash number 3 with a private key prevents any user without knowledge of the public key from modifying 4 the job information. In block 625, the job ticket 61 and the encrypted hash number are 5 concatenated to generate the completed job ticket 61. Hence, the completed job ticket 61 6 infonnation fields ; 1) the framework 62,2) the client extension 64, and 3) the public key 7 signature (encrypted hash number) 67. The method then ends, block 630.

8 Figure 16 illustrates a process 700 for using the service center 40 for document 9 management purposes, with reference to Figure 4. The process starts in block 705. A 10 client 31 sends a search request to the service center 40 for a particular document or set of 11 documents, block 710. The client 31 may issue this request with the job request 32 by 12 clicking on a link, such as a link to"Search Documents,"which may be presented to the 13 client 31 by the service center 40 after the client 31 has been granted accesses to the 14 client's mailbox The service center 40 may present the client 31 with the option to 15 search the document archives at other times, such as when the client 31 first attempts to 16 access the mailbox, or when the URL received by the service center 40 points toward the 17 document archives. In response to this request, the service center 40 sends the client 31 18 a search query form at block 715 to allow the client 31 to define a desired search. The 19 search query form may mclude an entry for each of the data fields in the content Be 51.

20 For example, the client 31 may input one or more names for a recipient and have the 21 service center 40 search for all messages or files directed to just those recipients. The 22 client 31 may also indicate the type of document, such as whether it is a facsimile, voice 23 message or data file. The search query form also has entries for the date or time, which 24 preferably accept ranges of times and dates, and an entry for the telephone number of the 25 caller to the service center 40. The search query form rmy also include an entry for the 26 size of the file or for the number of pages, which is relevant if the message is a facsimile 27 message. The search query form may also include an entry for the document number, 28 which may accept a range of document numbers, and also an entry for another field. 29 At block 720, the client 31 enters the search parameters in the search query form 30 and returns the information to the service center 40. The client 31 may define the search 31 about any one data field or may define the search about a combination of two or more 32 data fields. For example the client 31 may define a search by designating the document 33 type as a facsimile and the calling number as (XXX) 249-6801. Once the client 31 has 34 finished defining the search, the client 31 then selects the"SEARCH"link shown at the

1 bottom of the screen whereby the client would send the completed search query form to 2 the service center 40. At block 725, the service center receives the completed search 3 query form and, through a CGI, invokes one or more of the application programs 31 for 4 performing the desired search for any files or messages falling within the parameters of 5 the search. The results of the search are passed from the service center 40 through the 6 CGI, at block 730, and returned to the client 31. The service center 40 may return the 7 search results in the form of a listing of all files or messages contained within the search 8 parameters. At block 735, the client 31 selects the desired file or message from the 9 listing of messages and files. For example, by clicking on the first listed document, the 10 client 31 sends a request to the service center 40 for a viewing of that document and, in 11 response, the service center 40 provides a viewing of the document according to the 12 defined preferences of the client 31. The client 31 may receive a reduced size image of 13 the first page, a full size image of the first page, reduced size images of all pages, or full 14 size images of all pages of the facsimile message. At block 735, the client 31 may also 15 have the service center 40 save the search results. For example, the client 31 may input 16 the name of JOE's FACSIMILES as the name for the search. By clicking on a"SAVE 17 SEARCH AS"link, the name of the search is provided from the client 31 to the service 18 center 40. At the service center 40, the CGI invokes an application program 31 to store 19 the results of the search in the content file 51 under the designated name. The invoked 20 application program preferably does not store the contents of all messages but rather 21 stores a listing of the search results in the content file 51.

22 In the illustrated embodiments, the service center 40, and its sub-components, 23 including the work flow controller 70 and the job ticket service 60, for example, may be 24 implemented as a single, special purpose integrated circuit (e. g. , an ASIC) having a main 25 or central processor section for overall, system-level control, and separate circuits 26 dedicated to performing various different computations, functions and other processes 27 under control of the central processor section. Those skilled in the art will appreciate that 28 the service center 40 may also be implemented using a plurality of separate, dedicated or 29 programmable integrated or other electrical circuits or devices (e. g. , hardwired electronic 30 or logic circuits such as discrete element circuits, or programmable logic devices such as 31 PLDs, PLAs, or PALs). The service center 40 may also be implemented using a suitably 32 programmed general purpose computer, e. g. , a microprocessor, microcontroller or other 33 processor device (CPU or MPU), either alone or in conjunction with one or more 34 peripheral (e. g. , integrated circuit) data and signal processing devices. In general, any

1 device or assembly of devices on which a finite state machine capable of implementing 2 the flowcharts shown in Figures 9-16 can be used as the service center 40, or its sub- 3 components.

4 The terms and descriptions used herein are set forth by way of illustration only 5 and are not meant as limitations. Those skilled in the art will recognize that many 6 variations are possible within the spirit and scope of the invention as defined in the 7 following claims, and their equivalents, in which all terms are to be understood in their 8 broadest possible sense unless otherwise indicated.

9

Claims

In the claims:

1. A generic database structure that stores job identities and job content in a networked environment, comprising: a job ticket service that receives a request for a job from an entity coupled to the environment, comprising: a job identification section that stores an identity of the job, a control data section that stores data related to the job, and a task section that defines individual tasks required to complete the job.

2. The database structure of claim 1, wherein the database is a XML database.

3. The database structure of claim 1, further comprising links to one or more databases coupled to the job ticket service.

4. A job ticket, comprising: a user extension, the user extension storing user information; a framework, comprising: a job identification, control data that includes information related to performance of the job, and a task section that defines tasks to be completed for the job; and a security section that controls access to the job ticket.

5. The job ticket of claim 4, wherein the job ticket is structured as a generic XML database.

6. The job ticket of claim 5, wherein the generic XML database comprises a tree, and wherein the defined tasks exist as nodes in the tree.