Patent Grant
11494137
The present invention relates to a system of private and public servers that implement policy-based printing operations. The system includes a public and private server that implement the policy used for printing operations using personal identification numbers.
Existing policy-based printing systems mostly operate within a closed private domain environment. Print data submitted by users may be only accessible within a single domain environment. Some users, such as on-the-go users including insurance and real estate agents, sales executives, lawyers, and company executives, require the capability to access printing data beyond an office environment. These users travel extensively and find themselves needing to print in public locations, such as convenience stores, libraries, airports, copy and printing service stores, and the like. At these locations, the users may not reliably access the printing data. Further, these public locations may not support policy-based printing.
A method for implementing a policy-based printing system is disclosed. The method includes generating a corporate personal identification number (PIN) for a document stored in a private server. The method also includes authenticating a printing device at the public server. The method also includes receiving the corporate PIN at the public server. The method also includes retrieving a policy for accessing the document from the private server associated with the corporate PIN. The method also includes determining whether the document is deliverable to the printing device according to the policy. The method also includes generating a public PIN from the public server. The public PIN corresponds to the corporate PIN. The method also includes inputting the public PIN at the printing device. The method also includes retrieving the document according to the public PIN to deliver to the printing device.
A policy-based printing system is disclosed. The policy-based printing system is configured to generate a corporate personal identification number (PIN) for a document stored in private server. The policy-based printing system also is configured to authenticate a printing device at a public server. The policy-based printing system also is configured to receive the corporate PIN at the public server. The policy-based printing system also is configured to retrieve a policy for accessing the document from the private server. The policy-based system also is configured to determine whether the document is deliverable to the printing device according to the policy. The policy-based system also is configured to generate a public PIN from the public server. The public PIN corresponds to the corporate PIN. The policy-based system also is configured to input the public PIN at the printing device. The policy-based system also is configured to retrieve the document according to the public PIN to deliver to the printing device.
A printing system having a public domain and a private domain is disclosed. The printing system includes a printing device having a device identification. The printing system also includes a public server accessible by the printing device in the public domain. The printing system also includes a private server to provide a policy to the public server corresponding to a user in the private domain. The private server includes a document having a corporate personal identification number (PIN). The printing system also includes a user device connected to the public server. The user device authenticates the printing device to the public server using the device identification. The user device provides the corporate PIN to the public server. The public server generates a public PIN corresponding to the corporate PIN to the user device. The public PIN is received by the printing device. The public server provides the document to the printing device according to the policy and the public PIN.
Various other features and attendant advantages of the present invention will be more fully appreciated when considered in conjunction with the accompanying drawings.
Reference will now be made in detail to specific embodiments of the present invention. Examples of these embodiments are illustrated in the accompanying drawings. Numerous specific details are set forth in order to provide a thorough understanding of the present invention. While the embodiments will be described in conjunction with the drawings, it will be understood that the following description is not intended to limit the present invention to any one embodiment. On the contrary, the following description is intended to cover alternatives, modifications, and equivalents as may be included within the spirit and scope of the appended claims. Numerous specific details are set forth in order to provide a thorough understanding of the present invention.
The disclosed embodiments use an authentication server, a policy server, a file server, a network enabled printing device, and a public domain server. At the printing device, a user may provide authentication information, such as a username or password. The authentication information is transmitted from the device to a public domain server that processes the username for domain information. The domain information is matched to a domain on record and a private server is identified that can handle the domain authentication. The public domain server, through a direct connection to the private server, will go through a series of steps to obtain an authentication token, a policy applicable to the user, a job list of the user, and the job binary data for printing a print job on the printing device.
System 100 include public domain 110 and private domains 120 and 130. Public domain 110 may represent a collection of public servers and devices linked to network 102. In some embodiments, these servers are cloud servers. Public domain 110 also may be known as a public network of the public servers. Public domain 110 is accessible by printing device 104. Additional printing devices may connect to public domain 110, such shown by printing device 105. The printing devices may be located in public places, such as convenience stores, libraries, printing and copying stores and kiosks, and the like. Users may access the printing devices and, in turn, the servers within public domain 110. The users may need to validate their ability to access public domain 110 through a connected printing device.
Public domain 110 includes public policy server 112. Public policy server 112 interacts with private domains 120 and 130 as well as printing devices 104 and 105. Public policy server 112 may act as the middle man between public domain 110 and the private domains. Public policy server 112 may generate and store tokens used to implement the policy-based operations disclosed below. It also may store and allow access to a policy 142 received from a private domain, upon request. Policy 142, disclosed in greater detail below, outlines what a user can and cannot do when printing to printing device 104 from a private domain.
Public file server 114 is connected to public policy server 112. Public file server 114 may store or host binary data 140 for print job from a private domain. Printing device 104 may retrieve binary data 140 securely for a print job. In some embodiments, printing device 104 does so through public policy server 112. Public file server 114 also may receive binary data 140 from a server in a private domain, as disclosed below.
System 100 includes private domains 120 and 140. System 100 may include additional private domains, not shown here. Each private domain may include a plurality of private servers that are protected by a firewall from access from network 102. For example, private domain 120 includes firewall 122. Firewall 122 may be a software or hardware device that filters data and information coming over network 102 to private domain 120 for malicious or unauthorized access. If an incoming packet of data is flagged by the filters in firewall 122, then it is not allowed through to private domain 120. Firewall 132 may serve the same function for private domain 130.
Private domain 120 includes private authentication server 124, private job server 126, and private policy server 128. Private domain 130 includes private authentication server 134, private job server 126, and private policy server 128. The servers for private domain 120 are disclosed below, but their functionality may apply to the servers in private domain 130. Further, additional servers may be in a private domain and used securely to exchange information over network 102.
Private authentication server 124 is a private domain server that will provide authentication and authorize a user to prove his/her identify. Private authentication server 124 may be the main server that connects the private and public domain information exchange. In some embodiments, private authentication server 124 establishes a protocol connection 144 with public policy server 112 to provide a domain list 146 for access to private domain 120. Private authentication server 124 also verifies a user trying to access private domain 120 using public policy server 112.
Private job server 126 is a private domain server that stores all the binary data for the job files, or print jobs. When a user wants to print out a job file at printing device 104, private job server 126 should be queried in order to retrieve binary data 140 to generate the print job. Private job server 126 may forward binary data 140 to public file server 114 according to policy 142.
Private policy server 128 is a private domain server that hosts or stores all the policies, such as policy 142, related to a user. When printing device 104 attempts to perform any function, it should request private policy server 128 determine whether the user is allowed to do so. Private policy 128 may do the determination via public policy server 112.
The disclosed embodiments allow access to private servers from a public domain or to print on printing device 104 within a public network. An intranet application may do the authentication and job spooling so users need to authenticate printing device 104 before use. A policy may be associated with where a user can print, what kind of paper, number of pages, and the like. For example, some users may want to print from a public location, such as a convenience store, and want to access a private server that stores the print jobs. They would need access from network 102.
In some embodiments, public policy server 112 is a cloud server. Public policy server 112 may not be able to do accounting policy management to determine whether a user is allowed to print at printing device 104. Private domains 120 and 130 can operate over the cloud. Public policy server 112 may enforce the rules of the policy but management of the policy is still at a private server. Public policy server 112 also needs to distinguish between the private servers and private domains. Thus, if a user is outside the private network for a private domain, public policy server 112 will find the correct private domain to connect. That private domain will validate the user and access or use of the print job.
Printing device 104 includes a computing platform 201 that performs operations to support these functions. Computing platform 201 includes a computer processing unit (CPU) 202, an image forming unit 204, a memory unit 206, and a network communication interface 210. Other components may be included but are not shown for brevity. Printing device 104, using computing platform 201, may be configured to perform various operations, such as scanning, copying, printing, receiving or sending a facsimile, or document processing. As such, printing 104 may be a printing device or a multi-function peripheral including a scanner, and one or more functions of a copier, a facsimile device, and a printer. To provide these functions, printing device 104 includes printer components 220 to perform printing operations, copier components 222 to perform copying operations, scanner components 224 to perform scanning operations, and facsimile components 226 to receive and send facsimile documents. CPU 202 may issue instructions to these components to perform the desired operations.
Printing device 104 also includes a finisher 211 and one or more paper cassettes 212. Finisher 211 includes rotatable downstream rollers to move papers with an image formed surface after the desired operation to a tray. Finisher 211 also may perform additional actions, such as sorting the finished papers, binding sheets of papers with staples, doubling, creasing, punching holes, folding, and the like. Paper cassettes 212 supply paper to image the various components 220, 222, 224, and 226 to create the image formed surfaces on the papers. Paper cassettes 212 may include papers having various sizes, colors, composition, and the like. Paper cassettes 212 may be removed to refill as needed.
Document processor input feeder tray 230 may be the physical components of printing device 104 to receive papers and documents to be processed. A document is placed on or in document processor input feeder tray 230, which moves the document to other components within printing device 104. The movement of the document from document processor input feeder tray 230 may be controlled by the instructions input by the user. For example, the document may move to a scanner flatbed for scanning operations. Thus, document processor input feeder tray 230 provides the document to scanner components 220. As shown in
Memory unit 206 includes memory storage locations 214 to store instructions 215. Instructions 215 are executable on CPU 202 or other processors associated with printing device 104, such as any processors within components 220, 222, 224, or 226. Memory unit 206 also may store information for various programs and applications, as well as data specific to printing device 104. For example, a storage location 214 may include data for running an operating system executed by computing platform 201 to support the components within printing device 104. According to the disclosed embodiments, memory unit 206 may store the tokens and codes used in performing the authentication operations for printing device 104.
Memory unit 206 may comprise volatile and non-volatile memory. Volatile memory may include random access memory (RAM). Examples of non-volatile memory may include read-only memory (ROM), flash memory, electrically erasable programmable read-only memory (EEPROM), digital tape, a hard disk drive (HDD), or a solid-state drive (SSD). Memory unit 206 also includes any combination of readable or writable volatile memories or non-volatile memories, along with other possible memory devices.
Computing platform 201 may host one or more processors, such as CPU 202. These processors are capable of executing instructions 215 stored at one or more storage locations 214. By executing these instructions, the processors cause printing device 104 to perform various operations. The processors also may incorporate processing units for specific purposes, such as application-specific integrated circuits (ASICs) and field programmable gate arrays (FPGAs). Other processors may be included for executing operations particular to components 220, 222, 224, and 226. In other words, the particular processors may cause printing device 104 to act as a printer, copier, scanner, and a facsimile device.
Printing device 104 also includes an operations panel 208, which may be connected to computing platform 201. Operations panel 208 may include a display unit 216 and an input unit 217 for facilitating interaction with a user to provide commands to printing device 104. Display unit 216 may be any electronic video display, such as a liquid crystal display (LCD). Input unit 217 may include any combination of devices that allow users to input information into operations panel 208, such as buttons, a touch screen, a keyboard or keypad, switches, dials, and the like. Preferably, input unit 217 includes a touch-screen digitizer overlaid onto display unit 216 that senses touch to receive inputs from the user. By this manner, the user interacts with display unit 216. Using these components, one may enter an identification code 138 generated by mobile application 110 into printing device 104.
Printing device 104 also includes network communication processing unit 218. Network communication processing unit 218 may establish a network communication, such as a wireless or wired connection with one or more other image forming apparatuses and a server in an image forming system. CPU 202 may instruct network communication processing unit 218 to transmit or retrieve information over a network using network communication interface 210. As data is received at computing platform 201 over a network, network communication processing unit 218 decodes the incoming packets and delivers them to CPU 202. CPU 202 may act accordingly by causing operations to occur on printing device 104. CPU 202 also may retrieve information stored in memory unit 206, such as settings for printing device 104.
Printing device 104 also includes engine 106. Engine 106 may be a combination of hardware, firmware, or software components that act accordingly to accomplish a task. For example, engine 106 is comprised of the components and software to print a document. It may receive instructions from computing platform 201 after user input via operations panel 208. Alternatively, engine 106 may receive instructions from other attached or linked devices.
Engine 106 manages and operates the low-level mechanism of the printing device engine, such as hardware components that actuate placement of toner onto paper. Engine 106 may manage and coordinate the half-toner, toner cartridges, rollers, schedulers, storage, input/output operations, and the like. Raster image processor (RIP) firmware 290 that interprets the page description languages (PDLs) would transmit and send instructions down to the lower-level engine 106 for actual rendering of an image and application of the toner onto paper during operations on printing device 104.
The processes disclosed by flow diagram 300 seek to solve the problem of how to authenticate a user in one location, such as a convenience store with printing services, that he/she is within an organization that has a policy applicable to the user. Further, the policy is stored in a private domain not readily accessible from the printing device at the convenience store. The printing device is connected to a public network and may be part of a public domain, such as public domain 110. The disclosed embodiments enable the user and the organization to implement the policy, which is applicable to the private domain, within the public domain of the printing device located in the convenience store.
Operation 302 executes by private authentication server 124 sending an initialization request to public policy server 112. As disclosed above, private authentication server 124 is within private domain 120 and public policy server 112 is within public domain 110. To send the initialization request, an administrator enter information about public policy server 112. Such information may include server network address, location, server capabilities, and the like. Once the information is entered, private authentication server 124 generates a verification token 502 which verifies that public policy server 112 is acceptable to receive information and communicate with the private authentication server.
Operation 304 executes by returning acceptance of the initialization request and establishing a protocol connection 144 between private authentication server 124 and public policy server 112. Protocol connection 144 may stay established as long as public policy server has verification token 502. Verification token 502 may be stored on public policy server 112 and presented whenever verification is required by private authentication server 124. Protocol connection 144 provides a persistent connection between private authentication server 124 and public policy server 112 that allows the servers to send data at any time. Protocol connection 144 preferably may be known as a WebSocket connection, which provides a full-duplex communication channel over a single connection. Preferably, protocol connection 144 uses a secure protocol.
Operation 306 executes by providing a domain list 400 from private authentication server 124 to public policy server 112. This operation also may include providing the information about the private authentication server. Action 308 executes by setting domain list 400 at public policy server 112 to include domain information for private authentication server 124. Public policy server 112 may refer to domain list 400 whenever a user attempts to print from a private domain. Public policy server 112 may use information provided by the user to determine which domain to obtain policy 142. For example, public policy server 112 may be connected to more than one private domain. Domain list 400 determines which private domain applies to a user trying to print.
As can be seen, companies, firms, and colleges have an interest in keeping their network domains private. Further, these entities may wish to limit use of printing devices within public domains according to a policy. Domain list 400 also may include an entry for a public domain, such as public domain X. In some instances, a public domain also may include policies to limit capabilities of a user on a printing device 104. These policies, however, may not be within a private domain and available for retrieving through a public network connection. An email domain of “@website.com” may direct public policy server 112 to a public domain for the associated policy 142. Referring back to
Operation 312 executes when a user wants to print a document at printing device 104 coupled to public policy server 112. Authentication information 504 is provided from public policy server 112 to private authentication server 124. In some embodiments, the user enters a username and password that is captured by public policy server 112. For example, the user may enter this information at printing device 104 which forwards it to public policy server 112. Alternatively, the user may connect to public policy server 112 through an application on a mobile device or the like to provide authentication information 504.
In other embodiments, the user may enter a code, such as a personal identification number (PIN), that retrieves this information to provide it to public policy server 112. Public policy server 112 receives the code and matches the user information when the code is provided. Other embodiments may use a graphical code or identification card having a number that provides this information. Operation 312 sends this authentication information 504, such as username, password and PIN, to private authentication server 124.
Action 314 executes by authenticating the user with authentication information 504. Thus, user information is not stored on public policy server 112. Authentication still occurs in private domain 120 behind firewall 122. If the user is authenticated, then action 314 also includes private authentication server 124 generating authentication token 506. Operation 316 executes by indicating that the user has been validated and providing authentication token 506 to public policy server 112. Public policy server 112 may assign authentication token 506 to the user. Using the PIN example, the entered PIN may be associated with authentication token 506.
Private authentication server 124 also may provide an email address or the email domain, such as email domains 402-412 shown in
Once validated, public policy server 112 now retrieves a policy 142 from private policy server 128. Operation 318 executes by getting policy 142. The email domain is compared against domain list 400 to determine which private domain to query for the policy. In this example, user@example1.com is the email provided to public policy server 112. It compares the email to domain list 400 to determine the applicable policy is within private domain 120. Public policy server 112 sends determined domain 508, such as example1.com, along with authentication token 506 to private policy server 128 in operation 318. If the next user has an email domain of @company.com, then public policy server 112 determines that domain 508 is company.com and that the applicable policy is located in private domain 130.
Action 320 executes by identifying policy 142 as being applicable to the user based on domain 508. Authentication token 506 may be associated with the user and this information provided from private authentication server 124. Policy 142 may be a file having flags or other information to indicate what the user can do within a public network. For example, limitations may be set as to what type of printing can be done, the number of pages may be printed, and the like.
Policy 142 may include policy information 448. Policy information 448 may include a title of the policy, document information, and private domain information. Policy 142 includes data, such as flags, that indicates what can and cannot be performed in public domain 110. This data may be known as parameters in policy 142. Examples of parameters that limit printing operations are shown in
Color parameter 450 may indicate whether the user can do color printing in public domain 110. If no, then the user may be limited to only black and write printing. The user may be allowed to do color printing at printing devices in private domain 120 but not allowed to do so in a public domain setting.
Pages parameter 452 may set a limit on the number of pages that a user can print. The administrators of private domain 120 do not want unlimited printing to occur outside the private domain. Pages parameter 452 may limit the number of pages printed per day, week, month, hour, year, and the like. Alternatively, pages parameter 452 may cap the number of pages printed to have the user check with the administrators of public domain 120 to reset this parameter. Once the user hits a limit, he/she requests that the number of pages printed be reset to allow further operations. Costs parameter 454 may be similar to pages parameter 452 except to limit the amount of fees that the user may incur before printing is stopped. Costs parameter 454 helps prevent the user from running up large bills at a convenience store. It also may cap the amount of costs incurred on a periodic basis or as a total cost.
Security level parameter 456 may indicate that the user can only access documents from a job list provided from private job server 126 having a certain security or access level. Security level parameter 456 may help prevent accidental or intentional printing of sensitive documents at printing device 104. Further, the user may have access to sensitive documents when printing within private domain 120 but not so when printing using public domain 110. Policy 142 may limit exposure to such documents.
Location parameter 458 may indicate whether the user can print at certain locations. Policy 142 may place geographic or other limitations on where the user can print using a public domain. Location parameter 458 also may indicate the type of locations to allow printing operations. For example, the administrators of private domain 120 may not allow printing in a convenience store but may allow printing in a library. Device parameter 460 may act similar to location parameter 458 except limit printing on certain devices. For example, policy 142 may not allow printing on a printing device 104 that does not have legal sized paper capability or stores the data from the job file in a memory on the device. Device parameter 460 also may limit printing operations to known printing devices having a serial number or IP address.
Operation 322 executes by providing policy 142 to public policy server 112. Public policy server 112 may configure policy 142 to determine whether the user can print using public domain 110 and what limits on the printing operations may be enforced. Policy 142 may apply to all users of private domain 120. Alternatively, policy 142 may treat users differently. Some users may have unlimited printing privileges according to parameters 452 or 454 while others are prevented from exceeding a cap set forth by these parameters. Public policy server 112 configures the determinations using policy 142 accordingly.
Using the parameters within policy 142, operation 324 executes by getting a job list from private job server 126. Public policy server 112 may generate a job token 510. Job token 510 is presented to private job server 126 to obtain a job list 511 of print jobs available to the user. In some embodiments, job token 510 may include data that specifies what print jobs can be added to job list 511 based on the parameters set forth in policy 146. Job list 511 includes those print jobs that meet the specifications of policy 146. For example, color print jobs will not be included in job list 511 of policy 146 does not allow color printing for the user in a public domain. Action 326 executes by generating job list 511 in response to job token 510. Operation 322 executes by sending the print jobs in job list 511 to public policy server 112 from private job server 126.
The user then may select a print job from job list 511. The user may select from an interface provided on printing device 104 that is then communicated to public policy server 112. Alternatively, an application may execute on a device of the user that presents the job list and allows for selection from the list. The selection is sent to public policy server 112. Operation 330 executes by sending a command to private job server 126 to prepare a selected print job along with a uniform resource locator (URL) address from public policy server 112. The URL address is one associate with public policy server 112 and accessible from public domain 110.
Action 332 executes by retrieving and preparing the data for the print job. Preferably, the data is binary data that represents the document for the print job. This may be shown as binary data 140 in
Operation 334 executes by uploading binary data 140 to the URL address provided in operation 330. Thus, private job server 126 puts the data for the print job outside private domain 120 for the first time at this point. The URL address may be valid for only a specified period of time, such as two hours, one day, a week, and the like. After that point, the URL address may expire. The URL address to download binary data 140 for the print job is provided to public file server 114.
Public policy server 112 now retrieves binary data 140 and sends the data to printing device 104. Before that occurs, however, the disclosed embodiments may confirm whether the user has enough funds to pay for processing and completing the print job. Operation 336 executes by generating a confirmation token 514 at public policy server 112 once it is confirmed that the user or user's account has enough money to cover expenses to print. Public policy server 112 may compare the funds available to the cost to complete the print job. If there are enough funds, then confirmation token 514 is generated and sent to public file server 114. If not, then the user may be alerted to add more funds to his/her account.
Action 338 executes by obtaining uploaded binary data 140 from the URL address. Public file server 114 may send a call to the URL address which then sends binary data 140 to the public file server. Public file server 114 may store binary data 140 until confirmation token 514 is received. If a confirmation token 514 is not received within a specified time frame, then binary data 140 may be deleted from public file server 114. This feature prevents print jobs from private domain 120 from being stored indefinitely in public domain 110. Other factors may be used to determine when to delete any stored files of binary data.
Operation 340 executes by sending binary data 140 for the print job from public file server 114 to public policy server 112. Operation 342 executes by sending binary data 140 from public policy server 112 to printing device 104. Printing device 104 may process the print job accordingly. The user's account for printing on public domain 110 may be charged accordingly as well. In some embodiments, public file server 114 may send binary data 140 to printing device 104.
The disclosed embodiments allow a private domain, or network, to print to a public domain using a policy applicable to the public domain. Internal policies to the private domain are not material to printing in the public domain. Further, job data is kept private as long as possible. The data for the print job is provided to the public domain when requested by the user and approved according to the policy. This feature allows the user to print anywhere. The print job is not automatically sent outside the private domain or from the private servers until printing actually occurs. The disclosed embodiments provide greater flexibility for companies and users to access documents in a secure, private location and use devices and resources in a public setting.
Step 602 executes by establishing a protocol connection 144 between private authentication server 124 and public policy server 112. The protocol connection allows communication between the servers, one in private domain 120 and another one in public domain 110. Step 604 executes by providing a domain list 146 from private authentication server 124 to public policy server 112. Domain list 146 may include applicable private domains and associated email domains that are accessible by public policy server 112. Step 606 executes by entering user data 504 within public network 110 and providing the data to public policy server 112. Step 608 executes by sending user data 504 to private authentication server 124.
Step 610 executes by validating the user at private authentication server 124. Private authentication server 124 checks the provided user data 504 against its stored authentication records for the user. If the user is validated, then step 612 executes by generating authentication token 506. Step 614 executes by receiving authentication token 506 at public policy server 112. Step 616 executes by determining the applicable private domain for the user according to domain list 146. Preferably, public policy server 112 uses the email address for the user to determine which private domain to access for the policy for the user.
Step 618 executes by retrieving policy 142 from private policy server 128 based on the receipt of authentication token 506 and domain 508 from public policy server 112. Private policy server 128 is identified according to the applicable domain 508 and queried by public policy server 112. Once verified, private policy server 128 sends policy 142 to public policy server 112.
Step 620 executes by determining the parameters for policy 142. This process is disclosed above. As shown in
Step 624 executes by determining whether the user is allowed to access printing device 104 using public domain 110 according to the policy. Further, step 624 determines what print jobs are available to the user according to policy 142. The determination also may include reviewing policy 142 for allowing other operations on printing device 104 such as scanning, editing, faxing, and the like. If no, then step 626 executes by sending a message to the user or public policy server 112 that the operation on printing device 104 is not allowed.
If step 624 is yes, then step 628 executes by retrieving the print job from private job server 126. A job list 511 may be provided. The print job is selected from job list 511. Job token 510 is generated by public policy server 112. Public policy server 112 sends job token 510 to private job server 126 to obtain job list 511. Upon selection of the print job, private job server 126 uploads binary data 140 for the print job to a location accessible by public file server 114. Step 630 executes by confirming access to binary data 140 for the print job by checking to see if the user has enough money to pay for using printing device 104. Other restrictions also may be checked, such as time of day, location, and the like, to confirm whether the print job should be released to printing device 104.
Step 632 executes by sending binary data 140 to printing device 104 upon confirmation in step 630. Public policy server 112 generates a confirmation token 514 to confirm that the user is allowed to print. Public policy server 112 may send confirmation token 514 to public file server 114. Upon receipt of the confirmation token, public file server 114 may forward binary data 140 for the print job to public policy server 112, which provides the data file to printing device 104.
As disclosed above, public policy server 112 may interact with a plurality of private domains. Public policy server 112 may retrieve and implement more than one policy for printing or processing print jobs in public domain 110. In some embodiments, public policy server 112 may implement policies for a plurality of public domains as well. Further, a plurality of printing devices may be connected to public policy server 112. Flowchart 700 discloses some embodiments that have public policy server 112 interacting with more than one private domain.
Step 702 executes by validating users within public domain 110 at private authentication server 124. As disclosed above, a protocol connection may be established between public policy server 112 and private authentication server 124 to exchange user information to perform the validation.
Step 704 executes by determining a private policy server for each user according to a domain for the user at public policy server 112. The domains for each user are private domains. Preferably, the email domain for each user indicates the applicable private domain for that user. With two or more users, different email domains may indicate more than one private domain. Step 706 executes by retrieving a policy 142 for each user according to the respective domain from private policy server 128.
Step 708 executes by determining the parameters for each policy 142. All of the policies are received at public policy server 112. Public policy server 112 configures the treatment of printing requests for each private domain according to the corresponding policy. The policy sets forth the parameters for printing from the private domain via the public domain. For example, the parameters for one policy may only allow 100 pages to be printed per user a month from private domain 120 while the parameters for another policy may only allow 20 pages to be printed per user from private domain 130. Public policy server 112 is configured accordingly.
Step 710 executes by determining whether the user is allowed to print according to the applicable policy. If no, then step 712 executes by sending an alert to public policy server 112 or to the user. No printing operations using public domain 110 are allowed. If yes, then step 714 executes by receiving a job list according to the applicable policy from private job server 126. Step 716 executes by making the print jobs in the job list available to the user. Step 718 executes by selecting a print job from the job list. Binary data 140 for the selected print job is retrieved from private job server 126 and made available to public file server 114.
Step 720 executes by confirming whether the print job may be sent to printing device 104. Public policy server 112 confirms that the user has enough funds or credits to perform the request task on printing device 104. If yes, then step 722 executes by sending the print job as binary data 140 to printing device 104. If no, then step 724 executes by denying the print job. The user may be prompted to provide additional funds or credits to perform the requested task.
Step 802 executes by generating authentication token 506 at private authentication server 124. This step occurs once private authentication server 124 validates a user attempting to print using public domain 110. Public policy server 112 sends user information 504 including an email address, username, password, or PIN to private authentication server 124. Private authentication server 124, being in private domain 120, may securely store this information for the user. The secure user information is not made available in public domain 110. Authentication token 506 indicates that the user may access private domain 120. Step 804 executes by sending authentication token 506 to public policy server 112.
Step 806 executes by sending authentication token 506 and domain 508 to private policy server 128. Public policy server 112 sends authentication token 506 and domain 508 after the domain is determined using domain list 146. An email address may indicate an email domain that is used as domain 508. Domain 508 indicates which private domain to access for the applicable policy. For example, referring to
Step 808 executes by retrieving policy 142 from private policy server 128. Authentication token 506 confirms that the user corresponds to the policy. Authentication token 506 may include data provided by private authentication server 124 that identifies the user as able to use private domain 120 and, therefore, policy 142 for the private domain should be used in printing on public domain 110. Private policy server 128 sends policy 142 to public policy server 112. Public policy server 112 then configures itself to apply the parameters of the policy to using public domain for the user.
Step 810 executes by generating job token 510 at public policy server 112 after applying the parameters of policy 142. The parameters may detail what the user can do using public domain 110. These parameters may not necessarily correspond to what the user can do using private domain 120. Limitations are placed on the user on how he/she can use printing device 104. Job token 510 may reflect the parameters to compile the job list of print jobs available to the user according to policy 142.
Step 812 executes by sending job token 510 to private job server 126. Private job server 126 may store the print jobs available to the user or to users in private domain 120. In some embodiments, a plurality of print jobs may be available such that a job list 511 is generated based on the parameters for the user in using public domain 110. Job token 510 may be used in generating job list 511 in that it includes information to select the appropriate print jobs to include in the print job list.
Step 814 executes by providing print job list 511 to public policy server 112. The user may select a print job from print job list 511. Alternatively, the desired print job may already be selected such that public policy server 112 receives data for the selection, such as from an application on a mobile device, that corresponds to the print job in job list 511. Public policy server 112 then requests the print job data from private job server 126. Step 816 executes by sending job binary data 140 for the selected print job from private job server 126 to public file server 114.
Step 818 executes by confirming whether the user may print or process the print job at printing device 104. For example, public policy server 112 may confirm that the user has enough funds in an account to pay for printing on printing device 104. If step 818 is no, then step 820 executes by sending an alert to the user or to public policy server 112 that printing operations are to be stopped until the condition is met. Using the above example, the user may be asked to provide additional funds to his/her account to print the document.
If step 818 is yes, then step 822 executes by generating confirmation token 514 by public policy server 112. Confirmation token 514 indicates that the processing of binary data 140 at printing device 104 may proceed. Step 824 executes by sending confirmation token 514 to public file server 114 to obtain binary data 140, which is stored thereon. Public file server 114 may send binary data 140 to public policy server 112 upon receipt of confirmation token 514.
Step 826 executes by providing binary data 140 to printing device 104. Public policy server 112 may send binary data 140 once a connection is established with printing device 104. Public policy server 112 may have to wait until printing device 104 is available before forwarding binary data 140. Thus, the data from private job server 126 is not made available on printing device 104 until the operations are ready to commence. Although the current embodiments discuss printing on printing device 104, other operations also may occur, such as scanning, editing, faxing, and the like.
As disclosed above, different policies apply to different to users and prints jobs from different private domains. One private domain may not allow color printing while another private domain may not allow unlimited printing. Thus, public policy server 112 configures itself to resolve the different requirements set forth in a plurality of policies from various private policy servers. Further, public policy server 112 may manage different job lists and print jobs from the plurality of private domains. Alternatively, a private domain may have different domains related to it, such as example1.com and example2.com for private domain 120 shown in
Step 902 executes by generating verification token 502 at private authentication server 124. Private authentication server 124 receives information about public policy server 112 in order to establish a protocol connection. Verification token 502 helps to establish a connection between private authentication server 124 and public policy server 112. Private authentication server 134 also may generate a verification token 502 to establish protocol connection to public policy server 112.
Step 904 executes by sending verification token 502 to public policy server 112. Step 906 executes by storing verification token 502 at public policy server 112. As long as public policy server 112 can present verification token 502 when requested or when submitting a print request for a user, the connection is established with private authentication server 124. Step 908 executes by providing domain list 146 from private authentication server 124 to public policy server 112. Domain list 146 may include information pertaining to a plurality of domains for a plurality of private domains, as disclosed by
Step 910 executes by generating a first authentication token 506. Step 912 executes by generating a second authentication token 506. The first authentication token may be generated in response to a first user providing user information at public policy server 112. The second authentication token may be generated in response to a second user providing user information at public policy server 112. Public policy server 112 may access the appropriate private authentication server to validate the user information for each user. In some embodiments, private authentication server 124 may validate both users and generate both authentication tokens. Alternatively, private authentication server 124 may generate the first authentication token while private authentication server 134 may generate the second authentication token. Public policy server 112 may have instructions when to use the different private authentication servers.
Step 914 executes by sending the first authentication token and a first domain to a first private policy server. Step 916 executes by sending the second authentication token and a second domain to a second policy server. Public policy server 112 determines which private domain is applicable to each user. The determination of the private domain may be based on the email address for each user. In some embodiments, public policy server 112 may send this data to a single private policy server, which stores different policies for different domains that use a single private domain. Alternatively, the authentication tokens and domains may be sent to separate private policy servers. For example, the first authentication token and first domain are sent to a first private policy server, such as private policy server 128. The second authentication token and the second domain are sent to a second private policy server, such as private policy server 138.
Flowchart 900 proceeds to steps A1 and A2 for steps 914 and 916, respectively. Steps A1 and A2 then proceed to steps 918 and 920, respectively. Step 918 executes by retrieving a first policy, such as policy 142, in response to the first authentication token and the first domain. Step 920 executes by retrieving a second policy, such as policy 142, in response to the second authentication token and the second domain. In some embodiments, the first policy is stored on private policy server 128 and the second policy is stored on private policy server 138. Alternatively, both policies may be stored on private policy server 128 or 138. The first policy may apply to the first user and the second policy may apply to the second user.
Step 922 executes by receiving the first and second policies at public policy server 112. Step 924 executes by determining access to a first print job according to the first policy and access to a second print job according to the second policy. Public policy server 112 may configure the parameters of each policy to determine what type of print jobs may be made available to each user. For example, the first print job may not be available to the second user according to the second policy. The determination of access may relate to what print jobs are available to the users over public domain 110.
Step 926 executes by generating first and second job tokens, such as job token 510, based on the first and second policies at public policy server 112. A first job token is generated for the first policy and a second job token for the second policy. In some embodiments, the first job token may be sent to private job server 126 and the second job token may be sent to private job server 136. The different private job servers are in separate private domains. Alternatively, the job tokens may be sent to private job server 126 or 136.
Step 928 executes by retrieving a first job list, such as job list 511, based on the first policy and the received first job token and retrieving the second job list, such as job list 511, based on the second policy and the received second job token. The applicable private job server or servers provide the job lists to public policy server 112. The first user may select a first print job from the first print job list. The second user may select a second print job from the second print job list. These requests are communicated back to the application private job server or servers. The binary data for the first and second print jobs are sent to public file server 114.
Step 930 executes by generating confirmation tokens, such as confirmation token 514, at public policy server 112 to indicate that the print jobs may be processed at printing device 104. Public policy server 112 may confirm that each user has enough funds in his/her account to perform operations on printing device 104, as disclosed above. A first confirmation token for the first print job is presented to public file server 114. A second confirmation token for the second print job is presented to public file server 114. Public file server 114 provides the binary data for each print job to public policy server 112. Step 932 executes by sending the binary data for the first and second print jobs to printing device 104.
The reasons for such features include not entering a corporate PIN for the document in a public place. The input of PINs at the printing device may be observed by others or copied by another user to gain access to the document or private servers. Corporate PINs should only be used on corporate machines or those devices in the private domain. The disclosed embodiments allow the public server between the private server and the printing device to issue a public PIN for use to retrieve the document. In a sense, the public server acts as the printing device according to the private server. Management of accessing and delivering the document to the printing device also may be improved.
Public server 1004 may refer to any of the servers in the public domain, such as public file server 114 and public policy server 112 of public domain 110 shown in
Printing device 1006 may receive documents from public server 1004 as well as other sources to print, copy, store, modify, and the like. The features of printing devices according to the disclosed embodiments are disclosed above. Printing device 1006 may include device identification 1018 that indicates a unique identifier within system 1000. In some embodiments, device identification 1018 may be a number, alphanumeric characters, or a combination thereof. Public server 1004 may send documents and files to printing device 1006 based on device identification 1018. Graphical code 1019 may correspond to device identification 1018. Graphical code 1019 may be a quick response (QR) code or a barcode that is scanned by user device 1008. Graphical code 1019 also may uniquely identify printing device 1006.
User device 1008 may be a mobile device, tablet, computer, and the like. User device 1008 may move between the private domain and the public domain, as separated by firewall 1011. It also may access private server 1002 as well as public server 1004. A user may send and receive data from the servers at user device 1008. User device 1008 also may include a scanning device, such as a camera, to capture items such as graphical code 1019.
Private server 1002 may upload document 1012. Document 1012 may be similar to the print jobs disclosed above. Document 1012 includes data and information that is transmitted to devices within the private domain. The user of user device 1008 may upload document 1012. Private server 1002 generates corporate PIN 1014 in response to the uploading of document 1012. Within the private domain, corporate PIN 1014 may be used to access and retrieve document 1012.
Policy 1010 also may be used to determine how and if document 1012 is used within system 1000. Along with corresponding with the user, policy 1010 also may correspond to corporate PIN 1014 in that the policy is used to determine access to document 1012 when the corporate PIN is received at private server 1002. For example, if corporate PIN 1014 is received from public server 1004, then private server 1002 will use policy 1010 to determine whether document 1012 may be provided to the public server. Private server 1002 may deny access to document 1012 if policy 1010 does not allow so.
Corporate PIN 1014 may be stored on user device 1008. User device 1008, however, does not immediately provide corporate PIN 1014 when the user desires access to document 1012. Instead, public server 1004 generates public PIN 1020 for use on printing device 1006 according to the disclosed embodiments.
The user may authenticate user device 1008 to public server 1004 according to the disclosed embodiments. For example, user device 1008 may provide verification data 1016, such as a user/account name and password, to verify the user to public server 1004. This process may be disclosed above with regard to verification between public policy server 112 and private authentication server 124. Alternatively, verification data 1016 may be a token used by user device to authenticate the user in a public domain. The user may not authenticate access to private server 1002 directly using corporate PIN 1014.
To obtain public PIN 1020, user device 1008 obtains device identification 1018 of printing device 1006. In some embodiments, user device 1008 scans graphical code 1019 which provides the device identification or directs the user device to printing device 1006 to retrieve the identification information. User device 1008 provides device identification 1018 to public server 1004. Receipt of device identification 1018 serves to authenticate printing device 1006 to public server 1004. Public server 1004 may add printing device 1006 to a list of recognized devices within the public domain.
User device 1008 also provides corporate PIN 1014 to public server 1004. Public server 1004 verifies corporate PIN 1014 as acceptable then queries private server 1002 as to the availability of document 1012 corresponding to the corporate PIN. Document 1012 may be provided to public server 1004 if acceptable according to policy 1010. At this time, policy 1010 may be checked to determine if the user may access and print document 1012 to the public domain. The actual printing device does not need to be provided. Instead, public server 1004 acts as the “printing device” for policy determinations. Use of a policy to determine whether to access a document is disclosed above.
If policy 1010 allows access to document 1012, then private server 1002 may copy the document file to public server 1004. Alternatively, private server 1002 may send an instruction to public server 1004 that document 1012 is available and will be provided when requested. Because document 1012 is made available to public server 1004, it generates public PIN 1020 specifically for printing device 1006, which is pre-authenticated. The timing of the generation of public PIN 1020 is important in that it is not generated if access to document 1012 is not allowed by policy 1010.
Public PIN 1020 is sent to user device 1008. In some embodiments, public PIN 1020 only will work with pre-authenticated printing device 1006. It will not work on other printing devices within the public domain. This feature allows for better management of printing devices within the public domain. Public server 1004 will not need to track incoming public PINs to document 1012 but to whether the PIN is used on the appropriate printing device. It also prevents fraud and other security issues that might arise using the PIN on a plurality of devices. Printing device 1006 is pre-authenticated by user device 1008.
When printing, the user may input public PIN 1020 into printing device 1006. Printing device 1006 communicates public PIN 1020 to public server 1004. Public server 1004 verifies the validity of public PIN 1020 and associates it with the appropriate corporate PIN 1014 issued by private server 1002. Public server 1004 then may make document 1012 available to printing device 1006 based on the PINs. If document 1012 is stored on private server 1002, then public server 1004 may retrieve the document from the private domain server. Policy 1010 also may be checked to apply any new policies or updates to the accounting for the user. For example, the user may have printed pages at other printing devices since public PIN 1020 was issued. At the time, the user met the terms of policy 1010. Now, policy 1010 is checked again to ensure that the user may still access document 1012.
If allowable, then document 1012 is sent to printing device 1006. Document 1012 may be processed or printed such that statistics are generated for the action on printing device 1006. These statistics should be provided to private server 1002 to update any accounting related the user's policy limitations. These changes are reflected on private server 1002. Public server 1004 then may delete document 1012 from its memory along with the PINs associated with the document. Private server 1002 also may delete document 1012 as well as the corporate PIN generated for the document. This action prevents further access to document 1012.
Step 1102 executes by accessing private server 1002 by the user, preferably through user device 1008. User device 1008 is within the private domain side of firewall 1011. User device 1008 queries private server 1002 as to whether it may access the server to upload or retrieve documents and files stored thereon. Private server 1002 validates the credentials for the user of user device 1008.
Step 1104 executes by uploading document 1012 to private server 1002. The document is stored on private server 1002 and made available within the private domain of system 1000. When in the private domain, the user may access document 1012 from private server 1002. Such access may or may not be subject to policy 1010.
Step 1106 executes by generating corporate PIN 1014 related to document 1012. Use of corporate PIN 1014 with private server 1002 will allow access to document 1012, subject to policy 1010. Corporate PIN 1014 may be provided to user device 1008 in that it is stored thereon. In some embodiments, corporate PIN 1014 may be an alphanumeric code, such as 9999 or AB1234. Corporate PIN 1014 should be able to be input into a keypad on user device 1008. In other embodiments, corporate PIN 1014 may be a token, as disclosed above, that is presented to a server or other device in system 1000 to access document 1012. Step 1108 executes by transmitting corporate PIN 1014 to user device 1008.
Step 1110 executes by the user entering and accessing the public domain side of system 100. The public domain may include public server 1004 on the public side of firewall 1011. User device 1008 may connect with a network in the public domain to link to public server 1004. Step 1112 executes by authenticating the user to public server 1004 via user device 1008. This process is disclosed in greater detail above. User device 1008 may provide credentials to verify or validate the user to public server 1004. Public server 1004 then may query private server 1002 to authenticate the user and potential access to the private domain.
Step 1114 executes by scanning graphical code 1019 or retrieving device identification 1018 for printing device 1006. As disclosed above, printing device 1006 may be connected to public server 1004 within the public domain. User device 1008 obtains the information to identify printing device 1006 to public server 1004. Preferably, user device 1008 scans a QR code on the printing device that provides the information of the device identification.
Step 1116 executes by authenticating printing device 1006 at public server 1004 using user device 1008. User device 1008 provides device identification for the printing device to public server 1004. Public server 1004 may include a list of previously cleared printing devices accessible within the public domain. Any criteria may be used to place a printing device on such a list, such as licensing or business agreements, security checks, appropriate cybersecurity measures, and the like. If acceptable, then public server 1004 authenticates printing device 1006 as the destination for print jobs requested by the user.
Step 1118 executes by providing corporate PIN 1014 to public server 1004 from user device 1008. For example, the user may input corporate PIN 1014 when prompted by public server 1004. Alternatively, user device 1008 may send the corporate PIN to public server 1004. Step 1120 executes by determining whether to allow access to document 1012 based on corporate PIN 1014. As disclosed above, corporate PIN 1014 is associated with document 1012. Policy 1010 may be used in this step to determine whether the user may access document 1012. For example, the user may be limited to no color printing when using public server 1004 in the public domain. Upon receiving the request via corporate PIN 1014, private server 1002 may check with policy 1010 to deny any color printing if requested by the user. Alternatively, the user may have met his/her quota for printing in the public domain so that receipt of the corporate PIN will result in a denial of the request. Thus, if step 1120 is no, then step 1122 executes by sending an alert or other notice that the request is denied.
If step 1120 is yes, then step 1124 executes by forwarding document 1012 from private server 1002 to public server 1004. Preferably, the document is copied to the public server. Public server 1004 may store document 1012 thereon so that it is available to printing device 1006 when requested by the user. Step 1126 executes by generating public PIN 1020 at public server 1004. Public server 1004 forwards public PIN 1020 to user device 1008, where it is stored or made available to the user. Public PIN 1020 also may be a group of alphanumeric characters or a token of data. Public server 1004 associates corporate PIN 1014 with public PIN 1020 and keeps track of this relationship on the server. In a sense, public PIN 1020 replaces corporate PIN 1014 when accessing document 1012 in the public domain.
Step 1128 executes by considering public server 1004 as the printing device from the perspective of private server 1002. Private server 1002 does not directly connect with printing device 1006. No data is exchanged between these two components of system 1000. Thus, private server 1002 will consider public server as the printing device when it comes to determining access to document 1012 according to policy 1010. Further, policy 1010 may be provided to public server 1004. Thus, policy 1010 may be reviewed for authorization of any print jobs at public server 1004. Alternatively, this activity may occur at the time of printing.
Step 1202 executes by inputting public PIN 1020 at printing device 1006. The user may input the code for the public PIN into a pad or operations panel on the printing device. Alternatively, user device 1008 may forward the data for public PIN 1020 to printing device 1006. Step 1204 executes by printing device 1006 forwarding public PIN 1020 to public server 1004. The data for public PIN may be sent by printing device 1006. As disclosed above, printing device 1006 may be pre-authenticated so that public server 1004 will receive data therefrom.
Step 1206 executes by associating public PIN 1020 to corporate PIN 1014. In doing so, public server 1004 identifies document 1012 as corresponding to the request from printing device 1006. Step 1208 executes by determining whether access to document 1012 is allowed. This step may check policy 1010 again to see if anything has changed since public PIN 1020 was issued. For example, policy 1010 may have changed to deny the user access or printing options that were available in public PIN 1020 was generated. Alternatively, the user may have reached his/her maximum page printing output for the day, week, month, and the like. Public server 1004 may apply policy 1010 itself or may query private server 1002 to determine access in view of the policy. The processes for applying a policy to a print job is disclosed in greater detail above.
If step 1208 is no, then step 1210 executes by sending an alert to user device 1008. If step 1208 is yes, then step 1212 executes by providing document 1012 to printing device 1006. The data for the document is sent in the public domain to printing device 1006. Step 1214 executes by processing document 1012 as requested by the user. For example, printing device 1006 may print out pages for document 1012. Alternatively, the user may modify the document on printing device. The operations available to printing devices according to the disclosed embodiments are disclosed in greater detail above.
Step 1216 executes by generating statistics 1022 and an indication of the success of printing or processing document 1012. Printing device 1006 may generate statistics 1022 of how many pages were printed, costs per page, and any other information that would be need to update the account for the user and policy 1010 at private server 1002. Step 1218 executes by sending statistics 1022 to private server 1002, preferably via public server 1004. Public server 1004 may act as the printing device to private server 1002. Any data regarding the processing and completion of printing document 1012 should come from public server 1004 to have it acknowledged by private server 1002. Further, private server 1002 is not required to directly communicate with a plurality of printing devices.
Step 1220 executes by confirming success of the requested print job at printing device 1006. The confirmation may be sent with statistics 1022. Step 1222 executes by deleting document 1012 and associated PINs from public server 1004. There is no need to further access document 1012 so it is removed from public server 1004 so that no one can access document within the public domain. In some embodiments, document 1012 also is deleted from private server 1002. Corporate PIN 1014 and public PIN 1020 also may be deleted. If the user wishes to print document 1012 again or at another printing device, then the disclosed embodiments would repeat the processes disclosed above. New PINs would be issued.
As will be appreciated by one skilled in the art, the present invention may be embodied as a system, method or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, the present invention may take the form of a computer program product embodied in any tangible medium of expression having computer-usable program code embodied in the medium.
Any combination of one or more computer usable or computer readable medium(s) may be utilized. The computer-usable or computer-readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a transmission media such as those supporting the Internet or an intranet, or a magnetic storage device. Note that the computer-usable or computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.
Computer program code for carrying out operations of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a,” “an” and “the” are intended to include plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specific the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
Embodiments may be implemented as a computer process, a computing system or as an article of manufacture such as a computer program product of computer readable media. The computer program product may be a computer storage medium readable by a computer system and encoding a computer program instructions for executing a computer process. When accessed, the instructions cause a processor to enable other components to perform the functions disclosed above.
The corresponding structures, material, acts, and equivalents of all means or steps plus function elements in the claims below are intended to include any structure, material or act for performing the function in combination with other claimed elements are specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill without departing from the scope and spirit of the invention. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for embodiments with various modifications as are suited to the particular use contemplated.
One or more portions of the disclosed networks or systems may be distributed across one or more multi-functional printer (MFP) systems coupled to a network capable of exchanging information and data. Various functions and components of the MFP system may be distributed across multiple client computer platforms, or configured to perform tasks as part of a distributed system. These components may be executable, intermediate or interpreted code that communicates over the network using a protocol. The components may have specified addresses or other designators to identify the components within the network.
It will be apparent to those skilled in the art that various modifications to the disclosed may be made without departing from the spirit or scope of the invention. Thus, it is intended that the present invention covers the modifications and variations disclosed above provided that these changes come within the scope of the claims and their equivalents.
| Number | Name | Date | Kind |
|---|---|---|---|
| 7861282 | Kakigi | Dec 2010 | B2 |
| 9207897 | Takatsu et al. | Dec 2015 | B2 |
| 9230078 | Hirata | Jan 2016 | B2 |
| 9461820 | Dall | Oct 2016 | B1 |
| 20070107048 | Halls et al. | May 2007 | A1 |
| 20070156659 | Lim | Jul 2007 | A1 |
| 20160212131 | Nishida | Jul 2016 | A1 |
| 20190196761 | Minakawa et al. | Jun 2019 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20210397389 A1 | Dec 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16820979 | Mar 2020 | US |
| Child | 17464226 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16452038 | Jun 2019 | US |
| Child | 16820979 | US | |
| Parent | 16451913 | Jun 2019 | US |
| Child | 16452038 | US | |
| Parent | 16452041 | Jun 2019 | US |
| Child | 16451913 | US |
