Systems and Methods of Processing Print Jobs at an Imaging Device

A system and method of processing a print job at an imaging device that includes sending the document to the imaging device, receiving an identifier associated with the document from the imaging device, transmitting the identifier with a purchase request for a number of pages to print to a payments service via a messaging application on a mobile device, requesting a proof of payment for the purchase from a receipt service, and transmitting the proof of payment to the imaging device. The proof of payment includes the identifier and is received by the receipt service from the payments service via a chatbot.

REFERENCE TO SEQUENTIAL LISTING, ETC.

BACKGROUND

1. Technical Field

The present invention relates to a system and methods for releasing print jobs stored in imaging devices and, more particularly, to a system and methods for printing a document at an imaging device based upon successful payment of one or more pages of the document.

2. Description of the Related Art

Messaging applications in mobile devices often have payment methods embedded into their code space or ecosystem. These payment methods allow messaging application users or account holders to transfer money from their bank accounts to a bank account associated with another account holder in the messaging application (i.e., peer to peer). Account holders in messaging applications may include consumers and business owners wishing to connect to the consumers by pushing notifications to the mobile devices ranging from discount coupons, events, and other promotional or marketing materials. Business owners may employ the use of chatbots to manage their accounts in the messaging application. For example, chatbots may be configured to generate canned responses to any question received from an account holder, present the account holder with one or more web URL links upon user request and/or ask questions. Chatbots may also be configured to collect and/or store data based upon inputs of the account holder, such as payment for goods or services that were rendered.

A few payment methods for delivering goods or services to consumers using messaging applications in mobile devices are known in the art. One example system involves sending payment for processing a document using a messaging application in the mobile device, storing the document in a web-based service, generating a QR code associated with the document stored in the web-based service and using the QR code in retrieving the document from the web-based service and printing the document at a printing kiosk linked to the web-based service. Another example system involves sending payment to a web-based service for printing a photo document, directly sending the document via a messaging application from the mobile device to a printing kiosk located close to the mobile device and connected to the web-based service, and using the printing kiosk to customize the photo document prior printing. In both of these example paid printing methods, a connection of the printing kiosk to the Internet may be required in order to confirm payment of the document prior to its release for printing. Yet another example payment method involves the purchasing of vending machine products using a standalone application in the mobile device while the user of the mobile device is within Bluetooth-detectable range of the vending machine. Still, this example method requires the vending machine to include additional hardware so users can discover and establish a connection with the vending machine.

While the aforementioned solutions allow payment and release of a document from the user's mobile device, these solutions require at least one of an Internet connection or additional hardware and/or software configurations to the device. Accordingly, it is desirable to have a system and methods for releasing paid print job pages sent from a mobile device in an imaging device for printing with lesser or without additional configurations to the imaging device.

SUMMARY

Example mobile printing systems including an imaging device and example methods for releasing stored print jobs for printing based upon payment are disclosed. A print job may be sent from a mobile device communicatively connected to the imaging device via a connector application in the mobile device. Payment for printing one or more pages in the imaging device may be made via a messaging application in the mobile device, the messaging application being communicatively connected to an Internet-based messaging and payments service. A software program such as a chatbot may be used to transfer payment information generated by the messaging and payments service to a receipt service associated with an owner of the imaging device for tracking receipts. The connector application may request a receipt from the receipt service and send the receipt to the imaging device for verification of the imaging device prior to performing a printing operation.

One example embodiment of a method of printing a document at an imaging device includes sending the document to the imaging device, receiving an identifier associated with the document from the imaging device, transmitting the identifier with a purchase request for a number of pages to print to a payments service via a messaging application on a mobile device, requesting a proof of payment for the purchase from a receipt service, and transmitting the proof of payment to the imaging device. The proof of payment includes the identifier and is received by the receipt service from the payments service via a chatbot.

One example embodiment of a method of sending one or more pages of a print job to an imaging device includes sending the print job to the imaging device using a connector application installed on a mobile device, the mobile device communicatively connected to the imaging device; receiving from a receipt service a receipt indicating payment for printing the one or more pages of the print job; and transmitting the receipt to the imaging device, the receipt indicating a number of the one or more pages to print.

Other example embodiments, objects, features and advantages of the disclosure will become apparent to those skilled in the art from the detailed description, the accompanying drawings and the appended claims.

DETAILED DESCRIPTION OF THE DRAWINGS

It is to be understood that the disclosure is not limited to the details of construction and the arrangement of components set forth in the following description or illustrated in the drawings. The disclosure is capable of other example embodiments and of being practiced or of being carried out in various ways. For example, other example embodiments may incorporate structural, chronological, process, and other changes. Examples merely typify possible variations. Individual components and functions are optional unless explicitly required, and the sequence of operations may vary. Portions and features of some example embodiments may be included or substituted for those of others. The scope of the present disclosure encompasses the appended claims and all available equivalents. The following description is, therefore, not to be taken in a limited sense, and the scope of the present disclosure is defined by the appended claims.

Also, it is to be understood that the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. The use herein of “including”, “comprising”, or “having” and variations thereof is meant to encompass the items listed thereafter and equivalents thereof as well as additional items. Further, the use of the terms “a” and “an” herein do not denote a limitation of quantity but rather denote the presence of at least one of the referenced item.

In addition, it should be understood that example embodiments of the disclosure include both hardware and electronic components or modules that, for purposes of discussion, may be illustrated and described as if the majority of the components were implemented solely in hardware.

It will be further understood that each block of the diagrams, and combinations of blocks in the diagrams, respectively, may be implemented by computer program instructions. These computer program instructions may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions which execute on the computer or other data processing apparatus may create means for implementing the functionality of each block or combinations of blocks in the diagrams discussed in detail in the description below.

Accordingly, blocks of the diagrams support combinations of means for performing the specified functions, combinations of steps for performing the specified functions, and program instruction means for performing the specified functions. It will also be understood that each block of the diagrams, and combinations of blocks in the diagrams, may be implemented by special purpose hardware-based computer systems that perform the specified functions or steps, or combinations of special purpose hardware and computer instructions.

Disclosed is a system including example methods for releasing stored print jobs in an imaging device. The print jobs may be sent from a mobile device communicatively connected to the imaging device via a connector application in the mobile device. Payment may be made via a messaging application in the mobile device connected to the Internet. Different methods for determining, in an imaging device which may have no connection to the Internet, whether payment for a print job has been made and for releasing the print job will be discussed in greater detail below.

FIG. 1shows an example system100for releasing a print job, according to one example embodiment. Example system100includes at least one imaging device105and at least one mobile device110communicatively connected to imaging device105. Mobile device110may include a messaging application115and a connector application120. Connector application120may be communicatively connected to imaging device105via a network125. Messaging application115may be communicatively connected to a messaging and payments service130via Internet135. Messaging and payments service130may be communicatively connected to a chatbot140. Chatbot140may be communicatively connected to a receipt service145. Receipt service145may be communicatively connected with connector application120via Internet135. Receipt service145may include a receipt160which may be referred to by imaging device105as a proof of payment prior releasing a stored print job.

Imaging device105may be a single function printer or a multi-function device capable of printing, scanning, faxing, copying, e-mailing, and/or other functions. Imaging device105may be communicatively connected to mobile device110via a communications link established using connector application120, such as network125. Network125may allow mobile device110to communicate with and to send print jobs directly to imaging device105. An identifier of imaging device105(e.g., IP address, hostname, URL) may be provided in connector application120for network125to be established. In one example embodiment, an identifier of imaging device105may be manually entered into connector application120. In another example embodiment, an identifier of imaging device105may be searched in network125and automatically added to a list of printers that are connected with connector application120. In other example embodiments, imaging device105may be communicatively connected to connector application120via the Internet (not shown). Imaging device105may be able to receive and print documents from other mobile devices in addition to or in lieu of mobile device110. Imaging device105may include a queue of documents for printing. In one example embodiment, the queue may be stored in a memory (not shown) of imaging device105.

Mobile device110may be any mobile computing device which may be, for example, a smartphone, a laptop, a tablet, a smartwatch, and the like. Mobile device110may be capable of generating and/or storing a document (not shown). Mobile device110may be utilized by a plurality of users. Each user of mobile device110may have a corresponding account or profile in messaging application115. For purposes of the present disclosure, a user of mobile device110and a user or account holder of messaging application115may be used interchangeably herein. It will be appreciated by those skilled in the art that while one mobile device110is shown inFIG. 1, multiple mobile devices may be present in example system100. A user of mobile device110may opt to connect mobile device110to imaging device105via connector application120.

Messaging application115may be any messaging application capable of transmitting messages or communicating with messaging and payments service130. In one example embodiment, messaging application115may be installed in mobile device110. In other example embodiments, messaging application115may be an application accessible through a browser in mobile device110. Messaging application115may include a set of user interface components (e.g., buttons, icons, tabs) for display on mobile device110, as is shown inFIG. 3A-3E. Messaging application115may be connected to messaging and payments service130via Internet135to exchange and receive messages from messaging and payments service130. In one example embodiment, messaging application115may be connected to Internet135via a cellular data network connection. In another example embodiment, messaging application115may be connected to Internet135via a Wi-Fi connection.

Messages sent by messaging application115may be in the form of a text message, a photo or a moving image, and the like of which is known in the field of messaging using Internet135. A user or account holder in messaging application115may have an associated profile registered in messaging and payments service130. An account holder may be a person, an organization, or a business entity. Bank account details of each user or account holder of messaging application115may be tied to his or her respective accounts in messaging and payments service130. Bank account details may refer to credit card or debit card details of the user, according to one example embodiment. Using these details, each user may be able to pay for any goods or services sold by messaging and payments service130via messaging application115.

Connector application120may be an application in mobile device110enabling mobile device110to send a document to imaging device105. The document may be an electronic document stored on or accessible through mobile device110. Connector application120may include an interface to show to a user of mobile device110information concerning use of imaging device105, such as printing features and other functional capabilities of imaging device105. Connector application120may include a function to disconnect with imaging device105and establish a connection with another imaging device which may be similar in configuration as imaging device105. Connector application120may be aware of a number of pages of a selected document in mobile device110. In one example embodiment, connector application120may indicate to a user of mobile device110a number of pages of a document selected for printing to imaging device105.

In one example embodiment and as shown inFIG. 1, connector application120may not be communicatively connected with messaging application115. Messaging application115may be used for payment while connector application120may be used for sending communications to imaging device105. When messaging application115and connector application120are both installed in mobile device110, a coordinated user experience may be provided in mobile device110to guide the user through a pay-for-print experience. In another example embodiment, messaging application115may not be executed in mobile device110as a separate application from connector application120. In such an example embodiment, a payment plugin or module of messaging application115may be integrated into connector application120. In this embodiment, messaging application115may still be connected with messaging and payments service130over Internet135.

Messaging and payments service130may be a service available over Internet135. Messaging and payments service130may include a payments module. Messaging and payments service130may be used for managing data received from messaging application115. Received data may include user accounts and/or payment details (e.g., bank account information, payment amount, etc.) of each user of messaging application115. In some example embodiments, multiple messaging applications similar to messaging application115and installed on other mobile devices may simultaneously use messaging and payments service130to exchange messages.

Chatbot140may be a software program associated with an account of an owner of imaging device105in messaging application115. While chatbot140is illustrated inFIG. 1as an element separate from mobile device110, chatbot140may operate when messaging application115is executed in mobile device110. As is typical for bots, chatbot140may be set to provide a predetermined response to any input made by a user in messaging application115. For example, chatbot140may provide a link for installing connector application120in messaging application115as a response to an initial input made by the user. Chatbot140may be used to share notifications with a user of mobile device110relating to imaging device105, such as a price per page, printing discounts and other promotions, and the like. Chatbot140may also receive from messaging and payments service130payment information. Payment information may include the number of pages purchased for printing in imaging device105. Chatbot140may include instructions to forward data from messaging and payments service130to receipt service145, as will be discussed in greater detail below.

Receipt service145may be a dedicated server for storing information from chatbot140. Receipt service145may be managed by an owner of imaging device105. Receipt service145may include instructions for creating receipt160using information provided by chatbot140. Receipt160may be an electronic file including information for releasing a stored print job in imaging device105. In other example embodiments, receipt160may be used to allow printing of documents from mobile device110at imaging device105. Information may include at least a number of pages purchased by a user of mobile device110via messaging application115. Information on receipt160may further include an identifier of the print job stored in imaging device105. In one example embodiment, receipt160may be created on demand or upon request of connector application120. In other example embodiments, receipt160may be created following receipt of information by receipt service145from chatbot140.

In the present disclosure, the document sent to imaging device105for printing may be composed of text, images, or a combination of both. The document may be comprised of one or more pages. In one example embodiment, the document may be in a format acceptable for printing at imaging device105. In some example embodiments, connector application120in mobile device110may include instructions to convert the document to a format acceptable for printing in imaging device105prior to or in the course of sending the document to imaging device105.

A number of pages for purchasing and/or their respective classifications (e.g., monochrome or colored page, single page or duplex page printing) may be referred to herein as the “payload”. The payload may consist of the number of pages for printing in imaging device105. The payload may further consist of a classification of the pages based on print type, for example, whether printed as a monochrome or colored page or in one side or both sides of the media sheet. In the present disclosure, the number of pages purchased may be associated with the document to be printed. In printing the document, a user of mobile device110may send the payment for a predetermined number of pages to messaging and payments service130via messaging application115. Messaging and payments service130may process the payment and generate the payload. Chatbot140may then forward the payload to receipt service145for receipt service145to use in creating receipt160.

In one example embodiment, connector application120may send the document to imaging device105, and imaging device105may place printing of the document on hold until receipt160is received from connector application120. In another example embodiment, connector application120may request receipt160from receipt service145and send the document to imaging device105together or along with receipt160. The document may be printed in imaging device105following verification of receipt160.

FIGS. 2A-2Eshow example screenshots in mobile device110for sending a document to imaging device105.FIG. 2Ashows an example screenshot200A of an example document displayed on mobile device110.FIG. 2Bshows an example screenshot200B including an example pop-up interface for selecting an application to be used in processing the document inFIG. 2A, such as connector application120.FIG. 2Cshows an example screenshot200C of an example page for selecting a particular imaging device105to be used in processing the example document ofFIG. 2Afollowing the selection inFIG. 2B.FIG. 2Dshows an example screenshot200D of print preferences that the user may select prior printing the document using imaging device105selected inFIG. 2C.FIG. 2Eshows an example screenshot200E indicating a successful sending of the document from mobile device110to imaging device105selected inFIG. 2C.

FIGS. 3A-3Eshow example screenshots in mobile device110of messaging application115.FIG. 3Ashows an example screenshot300A of an example welcome message associated with an account of an owner of imaging device105in messaging application115.FIG. 3Bshows an example screenshot300B of an example conversation305between the user of mobile device110and chatbot140. Example conversation305may be initiated as a result of an input made by the user of mobile device110inFIG. 3A, such as clicking Get Started link310.FIG. 3Cshows an example screenshot300C showing an example pop-up display325overlaying example conversation305shown inFIG. 3B. InFIG. 3C, pop-up display325may be generated by chatbot140for receiving a number of pages of the document for printing in imaging device105.FIG. 3Dshows an example screenshot300D of another example pop-up display330in messaging application115confirming the input of the user's payment details inFIG. 3C.FIG. 3Eshows an example screenshot300E of yet another example pop-up display335in messaging application115indicating the successful transmission of the payment details (shown inFIG. 3D) to messaging and payments service130.

While example screenshots for connector application120(FIGS. 2A-2E) are presented before the example screenshots for messaging application115(FIGS. 3A-3D), it is to be understood that the user may execute messaging application115first and enter payment for printing per page of the document prior to launching connector application120and sending the document to the selected imaging device105.

FIG. 4is an example flowchart400depicting an example method for generating an example receipt160. Receipt160may be used to release a document at imaging device105for printing.

At block405, messaging application115may be launched in mobile device110by, for example, clicking an icon corresponding to messaging application115on a display interface of mobile device110or another method known in the art. At block410, messaging application115may initiate an automated conversation with an owner of imaging device105via chatbot140. In one example embodiment, a user of mobile device110may search for an account of the owner of imaging device105in messaging application115. In this embodiment, the user of messaging application115may be directed by messaging and payments service130to chatbot140following the identification of an account of the owner of imaging device105in messaging and payments service130.FIG. 3Ashows an example account in messaging application115of the owner of imaging device105(e.g., “Company1”).FIG. 3Bshows example conversation305between a user of mobile device110and chatbot140.

At optional block415, chatbot140may send instructions to a user of mobile device110on how to install connector application120on mobile device110. The user of mobile device110may identify whether or not connector application120is installed on mobile device110. Once connector application120is installed on mobile device110, chatbot140may send information to the user of mobile device110on how to use connector application120for sending a document to imaging device105for processing or printing.

At optional block420, the user may identify a document or print job stored in mobile device110for sending to imaging device105. In one example embodiment, a document may be opened in mobile device110(seeFIG. 2A). Following identification, mobile device110may send the selected document to imaging device105via link205associated with connector application120(seeFIG. 2B). In another example embodiment, the user may execute connector application120prior to selecting the document for printing.

At block425, the user of mobile device110may purchase a number of pages for printing in imaging device105using messaging application115. The one or more pages may correspond to a number of pages of the document sent at block420. In some example aspects, the number of pages may correspond to the number of pages a user desires to print. Payment for the number of pages may be processed by messaging and payments service130connected to messaging application115via Internet135. Chatbot140may receive the number of purchased pages as well as their respective classifications (payload) from messaging and payments service130. Chatbot140may then forward the payload to receipt service145.

At block430, connector application120may send a request for receipt160from receipt service145. Connector application120may send a nonce or unique identifier to receipt service145together with the request. The unique identifier may be associated with the document sent and placed on hold for printing in imaging device105(see block420). The unique identifier may be generated by imaging device105upon receipt of the document from mobile device110. As discussed above, receipt160may include the number of pages purchased and/or their respective print classifications. In one example embodiment, receipt160may include an encryption of the payload (digital signature). In another example embodiment, receipt160may include the unique identifier of the document in imaging device105. In some example embodiments, receipt160may include an identifier of connector application120.

At block435, connector application120may send receipt160to imaging device105. Upon receipt, imaging device105may determine whether receipt160received from mobile device110is valid. In one example embodiment, determining whether receipt160is valid may include determining whether receipt160includes a unique identifier associated with a document stored in imaging device105. In some example aspects, determining whether receipt160is valid may include using the public key stored in imaging device105to verify the digital signature of receipt160.

Following a determination that receipt160is valid, imaging device105may print the document sent by mobile device110(from optional block420). In one example embodiment, imaging device105may release the held document and print the document upon a determination that receipt160is valid. In another example embodiment where block420is omitted, imaging device105may receive a document for printing together with receipt160from mobile device110and then print the document upon a determination by imaging device105that receipt160is valid such that the actions in block420and435may be performed together.

FIG. 5is a sequence diagram500including example actions performed by the different components shown inFIG. 1. Sequence diagram500includes a user501of mobile device110, imaging device105, messaging application115and messaging and payments service130, connector application120, chatbot140and receipt service145as actors in performing an example application of the example method described in flowchart400ofFIG. 4. For purposes of clarity and since messaging application115directly communicates with messaging and payments service130over Internet135, actions performed by messaging application115and by messaging and payments service130are shown under a single column.

At step505, user501may identify an account in messaging application115associated with an owner of imaging device105. In one example embodiment, identifying the account may include scanning a QR code linked to an account of the owner of imaging device105in messaging application115. Other methods for identifying the account in messaging application115associated with an owner of imaging device105to allow use of imaging device105may be apparent in the art.

At step510, following identification of the owner's account, user501(also an account holder in messaging application115) may initiate a conversation with chatbot140via messaging application115. User501may send a predetermined message to chatbot140for chatbot140to respond with information regarding usage of imaging device105. For example and as shown inFIG. 3A, user501may click Get Started link310to start a conversation with chatbot140. As a result, inFIG. 3B, chatbot140may be configured to provide to user501a link315for purchasing pages. Another link320for installing connector application120in mobile device110may also be provided to user501(seeFIG. 3B). Other information such as how to connect with imaging device105, how to send a job to imaging device105, and the like, may be configured to be provided by chatbot140in messaging application115.

At step515, chatbot140may present user501in messaging application115with link320(FIG. 3B) for installing connector application120. At step520, user501may then click link320for installing connector application120on mobile device110. While not shown, link320may lead the user to an application store (e.g., Google Play™ Store, Apple's App Store®, etc.) for downloading connector application120onto mobile device110. Where connector application120is already installed on mobile device110, user501may determine whether a version of connector application120installed on mobile device110needs updating. User501may proceed with updating connector application120when desired by user501or as necessary.

At step525, connector application120may allow mobile device110to discover and establish a connection with imaging device105. In one example embodiment, launching connector application120may allow mobile device110to send communications directly to imaging device105. With reference toFIG. 1, while connector application120is shown to be connected to one imaging device105, a plurality of other imaging devices may be located near mobile device110and may be discoverable by connector application120. Thus, an owner of imaging device105may be an owner of a plurality of other imaging devices or a fleet of imaging devices. An account holder in messaging application115who is also an owner of a plurality of imaging devices may be configured to accept payments for printing on each of the plurality of imaging devices.

At step530, connector application120may be utilized by user501to send a document from mobile device110to imaging device105. In one example embodiment, user501may execute connector application120on mobile device110, choose the desired document via connector application120, and send the document to imaging device105via connector application120. In some alternate example embodiments, user501may open the document in mobile device110and send the opened document to imaging device105via connector application120(seeFIGS. 2A-2B). Following the sending of the document to imaging device105, user501may be redirected from connector application120to messaging application115for purchasing one or more pages of document145in some example embodiments.

At step535, user501may purchase one or more pages for printing in imaging device105using messaging application115. In one example embodiment, user501may indicate a total number of pages of the document sent at step530in messaging application115. In another example embodiment, user501may indicate in messaging application115a lesser number of pages relative to the total number of pages of the document so not all pages of the document may be printed.

At step540, messaging application115may inform chatbot140of the number of pages for purchasing by user501as well as their respective classifications (payload) for printing in imaging device105. Messaging application115may send to chatbot140the number of pages indicated by the user at step535via messaging and payments service130.

At step545, chatbot140may send the payload to receipt service145. At step550, chatbot140may then send a link to messaging application115. The link may be executed in connector application120to access receipt service145and retrieve receipt160. At step555, user501may access the link received in messaging application115via connector application120. In other example embodiments and where a module of messaging application115is embedded as part of connector application120, user501may be required to log in to connector application120using his or her account in messaging application115upon receipt of the link prior to allowing connector application120to access receipt service145.

At step560, as a result of accessing the link provided by messaging application115, connector application120may be able to retrieve receipt160from receipt service145. With reference back to step530, upon receiving the document from connector application120, imaging device105may generate a unique identifier corresponding to the received document and may provide the unique identifier to connector application120. Connector application120may send this unique identifier to receipt service145, together with the request for receipt service145for use in creating receipt160.

At step565, receipt service145may create receipt160using at least the payload provided by chatbot140and/or the unique identifier from connector application120. Receipt160may also include a digital signature. The digital signature may be generated by receipt service145when a request to create receipt160is received from connector application120. In one example embodiment, the digital signature may be a hashed value of the payload (number of pages) encrypted with a private key maintained in receipt service145.

At step570, following successful receipt of receipt160from receipt service145, connector application120may send receipt160to imaging device105. Receipt160may be used by imaging device105to determine whether one or more pages has been paid for printing by user501of mobile device110. In one example embodiment, imaging device105may have a public key stored thereon for decrypting the digital signature. Imaging device105may determine whether the digital signature indicated on receipt160matches a hashed value of the payload (derived using the public key) and may determine receipt160to be valid if so. Imaging device105may also determine whether the unique identifier within receipt160matches with the unique identifier associated with the document received from mobile device110(step530) and determine that receipt160is valid upon a positive determination.

At step575, upon a determination that the information within receipt160matches with the information expected by imaging device105(i.e., correct digital signature, unique identifier present), imaging device105may determine that receipt160is valid. Where a document is placed on hold for printing in imaging device105(step535) or where a document is received together with receipt160in imaging device105, imaging device105may proceed with printing one or more pages of the document following a determination that receipt160is valid.

Receipt160may be modified to control the production of copies of a particular document. In one example embodiment, receipt160may be modified based upon a number of pages of a document that are printed by imaging device105, as tracked by connector application120. For example, user501may initially send a 5-page document to imaging device105(via connector application120) and then send payment for 3 pages of the same document to messaging and payments service130(via messaging application115). A first receipt160indicating successful payment for printing 3 pages may be created in receipt service145. Connector application120in mobile device110may request for receipt160from receipt service145and send receipt160to imaging device105. Imaging device105may then print the first 3 pages of the document. Following printing of all 3 pages of the document, connector application120may inform user501that the last 2 pages of document145were not printed by imaging device105. Connector application120may prompt user501to send payment for 2 pages of the same document to messaging and payments service130. Receipt service145may create a second receipt160which may include the same identifier of the same document but may include a different number of pages based upon the new payment made. In some example embodiments, connector application120may send instructions to receipt service145to delete receipt160following use thereof in printing a document.

FIG. 6shows an example system600for authorizing printing at an example imaging device, according to another example embodiment. Example system600includes an example mobile device605having an example print release application610, an example imaging device615and an example print release authorization service620. Print release authorization service620may include a private key630. Imaging device615may include a public key640. While not shown, mobile device605may be communicatively connected to print release authorization service620over the Internet. Mobile device605and imaging device615may be communicatively connected to each other via a predetermined network (not shown), such as the Internet.

Mobile device605may comprise the same elements as example mobile device110shown inFIG. 1. Print release application610may perform the same operations or be the same as connector application120described inFIG. 1, which allows mobile device605to send a document or a print job to a predetermined imaging device. Print release authorization service620may perform the same operations or be the same as receipt service145described inFIG. 1, which includes an instruction to create a receipt. In other example embodiments, print release authorization service620may be a server dedicated to accepting payments for printing one or more pages at imaging device615to.

FIG. 6further shows actions650-675performed by the aforementioned components to allow printing by imaging device615. Actions650-675may show another example embodiment of controlling usage of imaging device615based upon authorized payments.

At step650, mobile device605may send a request to print to imaging device615. Mobile device605may send the request via print release application610. The request may include a document for printing by imaging device615. The document may be stored in a memory of mobile device605(not shown). In other example embodiments, the document may be accessed from a remote location via print release application610and sent to imaging device615for printing.

In one example embodiment, the request may be triggered via a user interface in print release application610. For example, a user may be instructed to click a button displayed when print release application610is executed in mobile device605. The instruction may be to send the printing request to imaging device615. The printing request may also be referred to as a request for access.

At step655, imaging device615may send a nonce to mobile device605. In one example embodiment, the nonce may be an identifier of the document sent by mobile device605along with the printing request (step650). In another example embodiment, the nonce may be an identifier of mobile device605. In other example embodiments, the nonce may be a unique identifier generated by imaging device615based upon the received printing request at step650.

At step660, mobile device605may send a request for a signed payload from print release authentication service620. The request may be sent by print release application610. As discussed above, the payload may refer to a number of pages purchased by the user as well as their respective print classifications. Upon receiving the request, print release authentication service620may encrypt the payload using private key630to generate a signed payload. In one example embodiment, the request for the signed payload may include the nonce received at step655. In other example embodiments, the request for the signed payload may include an identifier of imaging device615and/or mobile device605.

At step665, print release authentication service620may send the signed payload to mobile device605following receipt of the printing request. Communications between mobile device605and print release authentication service620may be made through the Internet (not shown). At step670, mobile device605may then send the signed payload to imaging device615. Mobile device605may send the signed payload along with an instruction to print a document. In one example embodiment, and where a document is sent to imaging device615together with the printing request (see step650), mobile device605may send the signed payload together with an instruction for imaging device615to start printing the document.

At step675, imaging device615may verify a digital signature of the signed payload. As discussed above, the digital signature may refer to the encryption of the payload information using private key630in print release authentication service620. Verifying the digital signature may include processing the signed payload using public key640in imaging device615.Verifying the digital signature may also include determining whether the payload processed using public key640is the same as the signed payload received at step670. Upon a determination that the signed payload and the processed payload are the same, imaging device615may determine that the digital signature is correct. Imaging device615may then print the document sent from mobile device605.

It will be appreciated that the actions described and shown in the example flowcharts may be carried out or performed in any suitable order. It will also be appreciated that not all of the actions described inFIGS. 4-6need to be performed in accordance with the example embodiments and/or additional actions may be performed in accordance with other example embodiments of the disclosure.