102. The URL code can be, for example, an address on the Web that is a reference that specifies a location on a computer network and a mechanism for retrieving the document 134.

In addition, in the embodiment shown in FIG. 2, the printed document 136 may be retrieved from the multifunction printer 110 by a second user (User B) 104. The printed document 136 can be one or more documents and wherein each of the one or more documents is comprises of one or more printed pages. For example, the printed document 136 can be a portfolio of documents that can include one or more document such as contracts, proposals, reports, financial documents, certificates, and the like.

In accordance with an exemplary embodiment, as disclosed herein, for each request, for printing or scanning of a document (or document file) 134, a new block can be added to the blockchain 124 using techniques such as proof of work, proof of stake or other appropriate means that a request for the printing or scanning of the document (or document file) 134 has been made with an identifier as to the requesting party or user, for example, the first user (User A) 102 as shown in FIG. 2. As set forth, each new block can include a verification data field that is calculated based on data from the prior block, thereby “chaining” them and preventing modifications to the blockchain so that each and every request received by the one or more centralized identity (DID) servers 122 for printing or scanning of the document (or document file) 134 can be added to the blockchain 124.

FIG. 3 is an illustration of a method 300 for document ownership using decentralized identity for blocking a print job in accordance with an exemplary embodiment. As shown in FIG. 3, the first user (User A) 102 can send data 132, for example, via an email to a third user (User C) 106. In accordance with an embodiment, the information associating the first user (User A) 102 as the owner of the document (or document file) 134 and the embedded authentication into the document (or document file) 134 can include limitations relating to viewing, editing, printing, and scanning of the document (or document file) 134. For example, the embedded authentication may preclude, for example, the third user (User C) 106 from printing the document (or document file) 134. Rather, for example, the third user (User C) 106 may only have permission to view the document (or document file) 134 rather than printing of the document (or document file) 134.

As shown in FIG. 3, the third user (User C) 106 sends a request to the multifunction printer 110 for printing of the document (or document file) 134. Upon receipt of the request to print the document (or document file) 134 from the third user (User C) 106, the multifunction printer 110 sends a request to the one or more decentralized identity (DID) servers 122 for permissions associated with the document (or document file) 134. The request to the one or more decentralized identity (DID) servers 122 will also include an identity of the user, for example, a unique user ID associated with the third user (User C) 106 that is requesting the printing of the document (or document file) 134. For example, in this particular case, the third user (User C) 106.

Upon receipt of the request from the multifunction printer 110, the one or more decentralized identity (DID) servers 122 can check the blockchain 124 for permissions associated with the document (or document file) 134 requested for printing by obtaining the decentralized identity code stored on the blockchain 124. The one or more decentralized identity (DID) servers 122 checks the decentralized identity code on the blockchain and determines that the third user (User C) 106 does not have permission to print the document (or document file) 134. The one or more decentralized identity (DID) servers 122 responds to the request from the multifunction printer 110 by notifying the multifunction printer 110 that the print request is denied, i.e., the third user (User C) does not have permission to print th the document (or document file) 134.

FIG. 4 is an illustration of a method 400 for document ownership using decentralized identity for print tracking in accordance with an exemplary embodiment. As shown in FIG. 4, the first user (User A) 102 can create a document (or document file) 134 on the computer system 130. The document file can include data 132 in the form of the document file 134, for example. Once the document (or document file) 134 has been created, the first user (User A) 102 can set the first user (User A) 102 as the owner of the document (or document file) 134, and the information associating the first user (User A) 102 as the owner of the document (or document file) 134 can be sent to the one or more decentralized identity (DID) servers 122 of the cloud computing system 120 for recordation, for example, on the blockchain 124.

In accordance with an embodiment, the information associating the first user (User A) 102 as the owner of the document (or document file) 134 can include embedded authentication into the document (or document file) 134 in the form of a decentralized identity (DID) code. As set forth above, the user 102 can set permissions, for example, who can print a copy of the document (or document file) 134, how many copies of the document (or document file) 134 can be printed, and other permissions associated with retrieval and/or printing of the document (or document file) 134. For example, the permissions can also include limitations relating to view, edit, print, and scan.

As shown in FIG. 4, the first user (User A) can send a print request to the multifunction printer 110. The multifunction printer 110 receives the print request to print the document (or document file) 134 from the user 102 and sends a request to the one or more decentralized identity (DID) servers 122 for the decentralized identity (DID) code associated with the document (or document file) 134 from the blockchain 124 to determine if the user who requested the printing of the document (or document file) 134, i.e., the first user (User A) 102 has permission to print the document (or document file) 134. The request from the multifunction printer 110 to the one or more decentralized identity (DID) servers 122 will also include an identity of the user, for example, the first user (User A) 102 that is requesting the printing of the document (or document file) 134. For example, in this particular case, the first user (User A) 102 can have a unique user identifier (or user ID) that identifies the first user (User A) 102 from other users, for example, the second user (User B) 104.

For example, as shown in FIG. 4, since the first user (User A) 102 is authorized to print the document (or document file) 134, the multifunction printer 110 executes the printing of the document (or document file) 134 in the form of printed document 136. In accordance with an embodiment, the printed document 136 can include the decentralized identity (DID) code 138 on the printed document itself.

In addition, the one or more decentralized identity (DID) servers 122 can add a new block can be added to the blockchain 124 regarding the print history of the document (or document file) 134. For example, the print history can include which document (or document file) 134 was printed or scanned, when the document (or document file) 134 was printed or scanned, and by whom the document (or document file 134) was printed or scanned. As set forth, each new block can include a verification data field that is calculated based on data from the prior block, thereby “chaining” them and preventing modifications to the blockchain so that each and every request received by the one or more centralized identity (DID) servers 122 for printing or scanning of the document (or document file) 134 can be added to the blockchain 124. In this particular, for example, if the permissions associated with the document (or document file) 134 includes, for example, an expiration date, a number of copies, or other limitations on the printing of the document (or document file) 134, the one or more decentralized identity (DID) servers 122 can send a notice to the first user (User A) 102, or the second user (User B) 104 that the number of printings of the document (or document file) 134 or availability of the document (or document file) 134 has been reached or expired and the permissions for the document (or document file) 134 will preclude future printing of the document (or document file) 134. As shown in FIG. 4, the first user (User A) 102 and the second user (User B) 104 receive a notification that the document (or document file) 134 will no longer be available after a certain number of printing or certain date, or alternatively, that the document (or document file) 134 is no longer available as the permissions set for the document (or document) 134 has expired or the number of printings has been reached.

FIG. 5 is an illustration of a method 500 for document ownership using decentralized identity for print tracking in accordance with another exemplary embodiment. As shown in FIG. 5, the printed document 136 can include the decentralized identity (DID) code 138 on the printed document 136 itself. For example, the decentralized identity (DID) code 138 can be in the form of a uniform resource locator (URL) or a quick response (QR) code that is placed on the contents, for example, diagonally across the printed document 136 to prevent the decentralized identity (DID) code 138 from being removed. For example, if the decentralized identity (DID) code 138 is printed on the top or bottom of the printer document 136, the decentralized identity (DID) code 138 can be easily removed or cut off, or covered.

FIG. 6 is an illustration of a method 600 for document ownership using decentralized identity for scan tracking denial in accordance with an exemplary embodiment. As shown in FIG. 6, a second user (User B) 104, may want to scan a printed document 136 that include the decentralized identity (DID) code 138 printed on the printed document 136 itself. The second user (User B) 104 places the printed document 136 on the multifunction printer 110 and request that the printed document be scanned into, for example, a digital format.

The multifunction printer 110 reads the URL (or QR) code 138 printed on the printed document 136 and sends a request to the one or more decentralized identity (DID) servers 122 for permission to scan the printed document 136. The one or more decentralized identity (DID) servers 122 retrieves from the blockchain 124, the permissions associated with decentralized identity (DID) code 138 and can determine that the second user (User B) 104 does not have permission to scan the printed document 136. For example, the second user (User B) 104 may not have permission to scan the printed document, or alternatively, for example, the permissions associated with the printed document 136 may not allow scanning of the printed document 136, i.e., no scan. The one or more decentralized (DID) servers 122 sends a response to the multifunction printer 110 that the request to scan the printed document has been denied.

In addition, the one or more decentralized identity (DID) servers 122 can notify the owner of the printed document 136, for example, in this case, the first user (User A) 102 that the second user (User B) 104, or in general, that a request to scan the printed document 136 has been made.

FIG. 7 is an illustration of a method 700 for document ownership using decentralized identity for scan tracking approval in accordance with an exemplary embodiment. As shown in FIG. 7, a second user (User B) 104, may want to scan a printed document 136 that include the decentralized identity (DID) code 138 printed on the printed document 136 itself. The second user (User B) 104 places the printed document 136 on the multifunction printer 110 and request that the printed document be scanned into, for example, a digital format.

The multifunction printer 110 reads the URL (or QR) code 138 printed on the printed document 136 and sends a request to the one or more decentralized identity (DID) servers 122 for permission to scan the printed document 136. The one or more decentralized identity (DID) servers 122 retrieves from the blockchain 124, the permissions associated with decentralized identity (DID) code 138 and can determine that the second user (User B) 104 is permitted to scan the printed document 136. The one or more decentralized identity (DID) servers 122 sends a response to the multifunction printer 110 that the printed document 136 can be scanned, and the scanning of the printed document 136 by the multifunction printer 110 is executed.

FIG. 8 is an illustration of a flowchart 800 for document ownership for one or more users of a multifunction printer 110 in accordance with an exemplary embodiment. As shown in FIG. 8, the method for document ownership for one or more users of a multifunction printer 110 includes receiving, by the multifunction printer 110, a request to execute one or more of a print job and a scan job (810); forwarding, by the multifunction printer 110, a request to a decentralized identity server 122 for authorization to execute one or more of the print job and the scan job received by the multifunction printer 110 (820); receiving, by the multifunction printer 110, a response from the decentralized identity server 122 for the authorization to execute the one or more of the print job and the scan job received by the multifunction printer 110 (830); and executing, by the multifunction printer 110, the one or more of the print job and the scan job when the response from the decentralized identity server 122 authorizes the execution of the one or more of the print job and the scan job (840).

In accordance with an embodiment, the method further includes sending, by the multifunction printer 110, a user identity associated with the request to execute the one or more of the print job and the scan job to the decentralized identity server 122; and receiving, by the multifunction printer 110, the response from the decentralized identity server 122 for the authorization to execute the one or more of the print job and the scan job received based on the user identity with the request to execute the one or more of the print job and the scan job.

In accordance with an embodiment, when the one or more of the print job and the scan job is the print job, the method further includes: printing, by the multifunction printer 110, the print job with a decentralized identity code on contents of the printed print job, and wherein the decentralized identity code is one or more of a uniform resource locator, a quick response code, and a user identifier. The method also includes receiving, by the multifunction printer 110, a request to execute scanning of the printed print job with the decentralized identity code on the contents of the printed print job; sending, by the multifunction printer 110, the decentralized identity code from the printed print job to the decentralized identity server 122 for authorization to execute the scanning of the printed print job; and receiving, by the multifunction printer 110, the response from the decentralized identity server 122 for the authorization to execute the scan job based on the decentralized identify code.

In accordance with an embodiment, the method further includes reading, by the multifunction printer 110, the decentralized identity code on the contents of the printed print job; and sending, by the multifunction printer 110, the read decentralized identity code on the contents of the printed print job to the decentralized identity server 122.

In accordance with an embodiment, the method further includes authenticating, by the multifunction printer 110, a user of the multifunction printer 110 associated with the one or more of the print job and the scan job based on a biometric identifier for the user, and the biometric identifier is from a biometric authenticator device associated with one of the multifunction printer 110 and a client device, the biometric authenticator device including one or more of a sensor, a scanning device, or an electronic reader, and wherein the biometric identifier of the user being at least one physiological characteristic of the user, and wherein the at least one physiological characteristic is selected from one or more of fingerprints, palm veins, face recognition, DNA (deoxyribonucleic acid), palm print, hand geometry, iris recognition, retina, and/or odor/scent. For example, the client device can be a mobile device, a smart phone, or a wearable device, and wherein the method further includes communicating, by the multifunction printer 110, to the client device of the user via a wireless communication protocol, the wireless protocol being a near-field communication (NFC) or a Bluetooth technology standard.

FIG. 9 is an illustration of a flowchart 900 for a method for document ownership associated with a multifunction printer 110 in accordance with an exemplary embodiment. As shown in FIG. 9, the method for document ownership for the multifunction printer 110 includes: receiving, by a decentralized identity server 122, a request for authorization to execute one or more of a print job and a scan job from the multifunction printer 110 (910); retrieving, by the decentralized identity server 122 from a distributed ledger, one or more permissions for the one or more of the print job and the scan job (920); determining, by the decentralized identity server 122, if the multifunction printer 110 is authorized to execute the one or more of the print job and the scan job based on the retrieved one or more permissions for the one or more of the print job and the scan job (930); and sending, by the decentralized identity server 122, a response to the request for authorization to execute the one or more of the print job and the scan job to the multifunction printer 110 with approval or denial of the request for authorization to execute the one or more of the print job or the scan job based on the determination of the retrieved one or more permissions for the one or more of the print job and the scan job (940).

In accordance with an exemplary embodiment, the method further includes receiving, by the decentralized identity server 122, a user identifier associated with the request for authorization to execute the one or more of the print job and the scan job from the multifunction printer 110; and determining, by the decentralized identity server 122, if the multifunction printer 110 is authorized to execute the one or more of the print job and the scan job based on the received user identifier and the retrieved one or more permissions for the one or more of the print job and the scan job from the distributed ledger. The method further includes receiving, by decentralized identity server, the one or more permissions for the one or more of the print job and the scan job; and recording, by the decentralized identity server 122, the one or more permissions for the one or more of the print job and the scan job on the distributed ledger.

In accordance with an exemplary embodiment, the method further includes sending, by the decentralized identity server 122, a notification to one or more users associated with the request for authorization received from the multifunction printer 110 to execute the one or more of the print job and the scan job.

In accordance with an embodiment, the distributed ledger is a blockchain.

In accordance with an exemplary embodiment, the one or more of the print job and the scan job is a scan job, and the method further comprises: receiving, by the decentralized identity server 122, a decentralized identity code from the multifunction printer 110, the decentralized identity code being on contents of a scanned document; determining, by the decentralized identity server 122, if the multifunction printer 110 is authorized to execute the scan job based on the decentralized identity code and permissions associated with the decentralized identity code; and sending, by the decentralized identity server 122, the response to the request for authorization to execute the scan job to the multifunction printer 110 with approval or denial of the request for authorization to execute the scan job.

In accordance with an exemplary embodiment, the method further comprises recording, by the decentralized identity server 122 on the distributed ledger, a history for the one or more of the print job and the scan job that have been printed or scanned including when printed or scanned and an identifier associated with the history for the one or more of the print job and the scan job that have been printed or scanned. The method can also include sending, by the decentralized identity server