FIELD OF THE INVENTION
[001] Embodiments of the present invention, generally relate to generating a digital document, and in particular relate to generating a secure digital document using distributed ledger technology.
BACKGROUND
[002] The recent increase in incidents of document forgery gives rise to third parties that collect and validate documents. There are many ways to verify the authenticity of paper documents, including watermarks, signatures, and embossed seals. However, digital documents present a problem of authenticity, as documents in digital form can be easily modified or altered, which makes them difficult to trust.
[003] Conventionally, there are many products and services that provide secure and verified document management, but they are quite expensive, and often require the involvement of a third party as well. However, personal documents cannot be trusted in the hands of third-parties, as they are susceptible to attacks and misuse by the third parties often without user's permission or knowledge.
[004] Further, conventional solutions require a tremendous amount of resources to audit and verify documents to create trust in today's digital document verification, validation and sharing process. This leads to reduction in efficiency and accuracy. Further, conventional document verification and validation processes are also terribly inaccurate and prone to failure. Therefore, it is quite challenging to protect the documents, and impossible to truly verify the existence and ownership of the document, because of the manual efforts required for the same. Some software programs have helped to automate some of these tasks, but they are even harder to protect, synchronize, and verify because computer records are easy to change and have single point of failure, if not managed properly and protected securely.
[005] Therefore, there is a need for an improved system and method for creating secure

digital document which solves the above disadvantages associated with the conventional methods.
SUMMARY
[006] According to an aspect of the present disclosure, a distributed ledger file system (102) for creating secure bdoc document (which is block chain document or secure digital document) is provided herein. The distributed ledger file system (102) includes an input module (204) configured to enable the user to provide predetermined information related to the document and the document itself for creating the bdoc document. The distributed ledger file system (102) further includes a process module (206) configured to process the user supplied information to create a metadata file (for example, metadata.txt file). The distributed ledger file system (102) further includes a bdoc creator module (208) configured to bundle the document and metadata file together and to create the bdoc document. The distributed ledger file system (102) further includes a verification module (210) that is configured to verify the authenticity and integrity of bdoc document. The distributed ledger file system (102) further includes an update module (212) that is configured to enable the user to update the bdoc document.
[007] According to another aspect of the present disclosure, a computer-implemented method for enabling users to create a secure bdoc document is provided herein. The computer-implemented method includes enabling the user to provide predetermined information related to the document and the document itself for creating the bdoc document. The computer-implemented method further includes processing the user supplied information to create a metadata file. The computer-implemented method further includes bundling the document and metadata file together and creating the bdoc document. The computer-implemented method further includes verifying the bdoc document. The computer-implemented method further includes enabling the user to update the bdoc document.
[008] The preceding is a simplified summary to provide an understanding of some aspects of

embodiments of the present invention. This summary is neither an extensive nor exhaustive overview of the present invention and its various embodiments. The summary presents selected concepts of the embodiments of the present invention in a simplified form as an introduction to the more detailed description presented below. As will be appreciated, other embodiments of the present invention are possible utilizing, alone or in combination, one or more of the features set forth above or described in detail below.
BRIEF DESCRIPTION OF THE DRAWINGS
[009] The above and still further features and advantages of embodiments of the present invention will become apparent upon consideration of the following detailed description of embodiments thereof, especially when taken in conjunction with the accompanying drawings, and wherein:
[0010] FIG. 1 is a block diagram depicting a network environment for facilitating creation, updating, verification, and deletion of bdoc document according to an embodiment of the present invention;
[0011] FIG. 2 is a block diagram of modules stored in memory, according to an embodiment of the present invention;
[0012] FIG. 3 is a schematic diagram of enabling a user to provide predetermined information related to the document and the document, according to an embodiment of the present invention;
[0013] FIG. 4 is a schematic diagram of meta data and constituents of the meta data, according to an embodiment of the present invention;
[0014] FIG. 5 is a schematic diagram of creation of bdoc document having metadata, according to an embodiment of the present invention;
[0015] FIG. 6 depicts an exemplary flowchart illustrating a method of creating a bdoc

document, according to an embodiment of the present invention;
[0016] FIG. 7 depicts an exemplary flowchart illustrating a method of verification of the bdoc document, according to an embodiment of the present invention; and
[0017] FIG. 8 depicts an exemplary flowchart illustrating a method of updating the bdoc document, according to an embodiment of the present invention.
[0018] To facilitate understanding, like reference numerals have been used, where possible, to designate like elements common to the figures.
DETAILED DESCRIPTION
[0019] As used throughout this application, the word "may" is used in a permissive sense (i.e., meaning having the potential to), rather than the mandatory sense (i.e., meaning must). Similarly, the words "include", "including", and "includes" mean including but not limited to.
[0020] The phrases "at least one", "one or more", and "and/or" are open-ended expressions that are both conjunctive and disjunctive in operation. For example, each of the expressions "at least one of A, B and C", "at least one of A, B, or C", "one or more of A, B, and C", "one or more of A, B, or C" and "A, B, and/or C" means A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, B and C together.
[0021] The term "a" or "an" entity refers to one or more of that entity. As such, the terms "a" (or "an"), "one or more" and "at least one" can be used interchangeably herein. It is also to be noted that the terms "comprising", "including", and "having" can be used interchangeably.
[0022] The term "automatic" and variations thereof, as used herein, refers to any process or operation done without material human input when the process or operation is performed. However, a process or operation can be automatic, even though performance of the process or operation uses material or immaterial human input, if the input is received before performance of the process or operation. Human input is deemed to be material if such input influences how

the process or operation will be performed. Human input that consents to the performance of the process or operation is not deemed to be "material".
[0023] FIG. 1 illustrates an exemplary network environment (100) where various embodiments of the present invention may be implemented. The network environment (100) includes a distributed ledger file system (102) connected to an electronic device 104 (for example, laptop, desktop computer or any other computing device), and a distributed ledger (108) via a network (106). The Network (106) may include, but is not restricted to, a communication network such as Internet, PSTN, Local Area Network (LAN), Wide Area Network (WAN), Metropolitan Area Network (MAN), and so forth. In an embodiment, the network (106) can be a data network such as the Internet. Further, the distributed ledger (108) may be a block chain technology based distributed ledger. Further, the messages exchanged between the distributed ledger file system (102) and the electronic devices (104) can comprise any suitable message format and protocol capable of communicating the information necessary for the distributed ledger file system (102) to provide secure digital documents (for example, block chain documents, hereinafter known as, bdoc documents) to the user. The electronic devices (104) may utilize the distributed ledger file system (102) to create secure and auditable digital documents or bdoc documents of different types (for example, word file, pdf file, image file, video file or any other file), verify the bdoc documents, and update the bdoc documents.
[0024] In an embodiment of the present invention, the distributed ledger file system (102) may be a computing device. In operation, a user of the electronic device (104) may access the distributed ledger file system (102) to provide information related to a document and the document itself, and create the secure and auditable bdoc document. The distributed ledger file system (102) includes a processor (110) and a memory (112). In one embodiment, the processor (110) includes a single processor and resides at the distributed ledger file system (102). In another embodiment, the processor (110) may include multiple sub-processors.
[0025] Further, the memory (112) includes one or more instructions that may be executed by the processor (110) to enable the user to provide predetermined information related to the

document and the document itself, to process the user supplied predetermined information and the document itself to create a metadata file, and to bundle the document and metadata file together and to create the bdoc document. In one embodiment, the memory (112) includes the modules (114) and a database (not shown in figure). The database may include various data generated during processing information received from users and computing hash values of metadata files. Furthermore, the memory (112) of the distributed ledger file system (102) is coupled to the processor (110).
[0026] Referring to FIG. 2, the modules (114) includes a login module (202), an input module (204), a process module (206), a bdoc creator module (208), a verification module (210), and an update module (212). The modules (114) are instructions stored in the memory and may process user supplied information and the document itself to create bdoc document, verify the bdoc document, and update the bdoc document.
[0027] The login module (202) is configured to enable a user to create an account with the distributed ledger file system. In an embodiment, the user may provide his/her name, login ID, email ID, age, organization name, mobile number, country name etc. Based on details received from the user, the login module (202) is configured to assign a unique ID to the user. According to an embodiment of the present invention, the user may use the unique ID in subsequent login to the system to uniquely identifying himself/herself In another embodiment, the login module (202) is configured to enable the user to login into the system (102) without creating account. For example, the user may login via his/her email account (for example, Gmail) or any social media account (for example, Facebook, Linkedln etc.). Those skilled in art will appreciate that such login facility allows user convenience, and the identity of the user may come based on his/her email account or social media account.
[0028] The input module (204) is configured to enable the user to provide predetermined basic information related to the document and the document itself for creating the bdoc document. The predetermined basic information may be information related to identity associated with the document. In another embodiment, the input module (204) is configured to enable the user

to upload a document, as shown in FIG. 3. In an embodiment, the user may either upload or use the document editors to provide the document pages along with user information. Those skilled in the art will appreciate that the document editors may be utilized by the users to edit the documents. Further, in an embodiment, the input module (204) is configured to encrypt the document (that was provided by the user) using a key. In an embodiment, keys used for encryption may be generated by the input module (204). In another embodiment, keys used for encryption may be generated by the user or organization using the input module (204). Further, the input module (204) is configured to store respective private key for each document in the distributed ledger (108). Those skilled in art will appreciate that such encryption provides additional security layer in generation of the bdoc document. Further, the input module (204) is configured to store respective private key for each document in distributed ledger (108). In a preferred embodiment, the input module is configured to store respective private key for each document in distributed ledger (108) or database or any other storage.
[0029] Further, according to an embodiment of the present invention, the process module (206) is configured to process the user supplied inputs to create a metadata (metadata.txt). In an embodiment, as shown in FIG. 4, metadata may contain information about the 'block chain ID' (i.e., identifier), 'block chain type', 'document ID', 'basic information', 'pages', 'user information', 'user permissions', 'public information', 'history of bdoc', 'workflow', and 'previous version information'. Further, the process module (206) is configured to send a request to distributed ledger (108) to assign a unique ID to the document.
[0030] In an embodiment, 'block chain ID' may provide information related to the context of the block chain in the network. Further, the 'block chain type' may provide the information related to the type of block chain used for bdoc creation public, private or permissioned. Further, the 'document ID' is a unique id assigned to bdoc. The 'basic information' includes the information about the document name, document type and last version of the document. Further, the 'pages' provide the information related to the various pages of document, for example, name of pages, sequence of pages, type, and actual name of the pages, as shown in

FIG. 4. The 'user information' provides the information related to user of the document, for example, user ID, user type, and their relation with the document. The 'user permissions' may provide the information related to permissions of different users associated with the bdoc document. Further, the 'public information' may provide the information about the name of the document, created date, name of the user who created the document, type of the document, name of the user who has done the last modification in the bdoc document and date on which this modification is done. The 'history' may provide the information about the various events along with their respective time in the bdoc document life cycle. The 'workflow' may provide the information related to the application in which bdoc document can be used by users. The 'previous versions' may provide the information about the previous versions of the bdoc document.
[0031] Further, according to an embodiment of the present invention, the process module (206) is configured to compute a hash of the basic information, pages, user information, user permissions, public information, and history of bdoc, workflow and previous version information. In an embodiment, the process module (206) is configured to create a metadata.txt file containing basic information hash, page final hash, pages hashes, user information hash, user permissions hash, public information hash, history hash, work flow hash, previous versions hash, previous version final hash, and metadata.txt hash. Further, the process module (206) is configured to store the created hash values in the distributed ledger (108). Further, the process module (206) is configured to decrypt the document provided by the user using the key stored in the distributed ledger (108).
[0032] The bdoc creator module (208) is configured to create the bdoc document. According to an embodiment of the present invention, the bdoc creator module (208) is configured to bundle the document (that was provided by the user) and metadata together to create the bdoc document, as shown in FIG. 5. In an embodiment, documents may have all the pages provided by user as an input to the distributed ledger file system, and the metadata may include information about the block chain ID, block chain type, document ID, basic information,

pages, user information, user permissions, public information, and history of bdoc, workflow and previous version information, as shown in FIG. 5.
[0033] The verification module (210) is configured to verify the bdoc document. In an embodiment, the verification module (210) is configured to enable the user to provide the bdoc document. The verification module (210) is further configured to unbundle the bdoc document to get document pages and metadata file (metadata.txt). Further, the verification module (210) is configured to parse the metadata file to get the information about the block chain id, block chain type, document id, basic info, pages, user info, user permissions, public info, history, workflow, previous versions details.
[0034] Further, the verification module (210) is configured to compute hash of the metadata file. Further, the verification module (210) is configured to send a request to distributed ledger (108) using API (application programming interface) to match the computed metadata hash with the metadata hash stored on the distributed ledger (108) with respect to the document id. According to an embodiment of the present invention, in case, the computed metadata hash matches with the stored metadata hash, the verification module (210) is configured to certify that the document is valid. In case, the computed metadata hash does not match with the stored metadata hash, the verification module (210) is configured to certify that the document is not valid. Further, in another embodiment, the verification module (210) is configured to enable the owner to divide all available information into public and private information. The verification module (210) may compute individual metadata hash values for private information (for example, ownership information) and public information. The verification module (210) is configured to further match computed individual metadata hash values for private and public information, with the private and public metadata hash stored on the distributed ledger (108), and certify the document as valid or invalid based on matching. Those skilled in the art will appreciate that the verification module allows dividing information into private and public information, and thus provides additional utility for the users.
[0035] The update module (212) is configured to enable the user to update the bdoc document.

In an embodiment, the user may provide the bdoc document to the update module or a bdoc viewer. The update module (212) is configured to unbundle the bdoc document to get metadata file (metadata.txt) and document pages. Further, update module (212) is configured to parse the metadata to get the information about the block chain id, block chain type, document id, basic info, pages, user info, user permissions, public info, history, workflow, and previous versions details. Further, the update module (212) is configured to check user permission using 'metadata.txt' for bdoc document update.
[0036] In an embodiment, in case the owner of the document (for example, user A) gives the permission to another user (for example, user B) to update the document, the user B is allowed to make the changes in the document by the update module (212). Further, the update module (212) is configured to update metadata as per the changes done by user in the document. Further, the update module (212) is configured to compute new hashes for the basic information hash, page final hash, pages hashes, user information hash, user permissions hash, public information hash, history hash, workflow hash, previous versions hash, previous version final hash, and metadata file hash. Further, the update module (212) is configured to send a request to store the created hashes in the distributed ledger using APIs. Further, the update module (212) is configured to bundle the metadata file and documents pages together to create the updated bdoc document.
[0037] FIG. 6 illustrates an exemplary flowchart of a method of creating a secure and auditable bdoc document, according to an embodiment of the present invention. Initially, at step 602, a user is enabled to login and provide predetermined basic information related to document and the document(s) itself to be created. In an embodiment, the user may use a unique ID (assigned to user when she/he set up account with the system) in login to the system. After successful login, the user is enabled to provide predetermined information related to the document and the document itself for creating a bdoc document. The predetermined information may be information related to identity associated with the document. Alternatively, the user may also upload a document.

[0038] At step 604, a metadata file are created or updated based on user supplied inputs like basic information and/or document uploaded. In an embodiment, the metadata may contain information about the block chain ID, block chain type, document ID, basic information, pages, user information, user permissions, public information, and history of bdoc, workflow and previous version information. Further, a unique ID may be assigned to the document.
[0039] At step 606, hash values of the metadata file is created. In an embodiment, the hash file may contain basic information hash, page final hash, pages hashes, user information hash, user permissions hash, public information hash, history hash, work flow hash, previous versions hash, previous version final hash, and metadata.txt hash.
[0040] At step 608, computed hash values of the metadata file are stored in a distributed ledger (108). In an embodiment, the distributed ledger (108) may be used to store the computed hash values of the metadata file. At step 610, the metadata file and document (provided by the user) are bundled to create a bdoc document. In an embodiment, documents may have all the pages provided by user as an input to the distributed ledger file system. Further, in an embodiment, the metadata may include information about the block chain ID, block chain type, document ID, basic information, pages, user information, user permissions, public information, and history of bdoc, workflow and previous version information.
[0041] FIG. 7 illustrates an exemplary flowchart of a method of verification of the bdoc document, according to an embodiment of the present invention. Initially, at step 702, the user is enabled to provide a bdoc document that is required to be verified. At step 704, the bdoc document is unbundled to retrieve pages of documents and metadata file. Further, the metadata file is parsed and hash is computed for metadata file. At step 706, the computed hash value of metadata file is compared/matched with stored hash value of the metadata file in the distributed ledger. In an embodiment, the computing and verification of the metadata hash is performed for proving the authenticity of the bdoc document. Further, the hash of constituents of the metadata file is also computed in order to identify the details of tampering, in case the document has been tampered with.

[0042] At step 708, it is determined if the match of computed hash value and stored hash value is successful. In case, the match is successful, at step 710, the document is certified as valid document. In another case, if the match is not successful, at step, the document is certified as invalid document.
[0043] FIG. 8 illustrates an exemplary flowchart of a method of updating the bdoc document, according to an embodiment of the present invention. The user may provide the bdoc document that is required to be updated. At step 802, the metadata file of the document is parsed to check permission of the user trying to interact with the document.
[0044] In an embodiment, in case the user has permission from the owner of the document, at step 804, the user is enabled to update the document. Further, metadata file may be updated as per changes done by the user in the document. In case, the user does not have permission, the user is denied to update the document and the method concludes.
[0045] At step 806, new hash values of the metadata file is computed. In an embodiment, new hash values for example, basic information hash, page final hash, pages hashes, user information hash, user permissions hash, public information hash, history hash, workflow hash, previous versions hash, previous version final hash, and metadata file hash may be computed.
[0046] At step 808, the updated hash values of the metadata file are stored in the distributed ledger. In an embodiment, updated hash values may be stored in the distributed ledger (108). At step 810, the metadata file and documents are bundled together to create the updated bdoc document. In an embodiment, step 810 is executed after step 810. In another embodiment, steps 808 and 810 may be executed in parallel.
[0047] The distributed ledger file system (102) and the methods performed by the distributed ledger file system (102) advantageously provide generation of a secure digital document (bdoc document) using distributed ledger technology. Those skilled in the art will appreciate that the block chain provide a mechanism to store the data in a peer-to-peer decentralized distributed

ledger and makes it independently auditable, as each participating node in the block chain network maintains a copy of the ledger. In an embodiment, the distributed nature of the ledger prevents tampering and revision, which makes it easy to confirm the authenticity and security of every transaction recorded on the chain. Further, the distributed ledger, provided by the distributed ledger file system, facilitates creation of a document format "bdoc" that makes it faster, cheaper for document creation and validation.
[0048] Further, in an embodiment, the document format, provided by the distributed ledger file system, may be used to certify the existence, integrity, and ownership of a document or file. Those skilled in the art will appreciate that proving the authenticity of a document at a certain point in time may be very useful for educators, entrepreneurs, and attorneys. For example, timestamping data in an unalterable state while maintaining confidentiality is useful for legal applications. Further, users may use the format to prove the ownership and authenticity of any documents including wills, deeds, powers of attorney, health care directives, promissory notes, satisfaction of a promissory notes, without even disclosing the contents of the document.
[0049] Further, in an embodiment, the distributed ledger file system (102) advantageously solves the problem of verifying the validity of digital assets, such as a picture of birth certificate, a pdf document stating will or a signed legal document that specify a business deal very efficiently. Further, the distributed ledger file system advantageously can be utilized at a very low implementation cost. Further, the distributed ledger file system advantageously facilitates addressing the authenticity, integrity, security and transparency of the documents. In an embodiment, the distributed ledger file system can advantageously embed authentication, ownership information into the document itself and can protect against tampering or modification.
[0050] Further, the distributed ledger file system (102) advantageously enables any user (having the permission/ownership of the document) to access the bdoc documents. In another embodiment, the user may be verified based on login details, such as login ID and password.

In yet another embodiment, the user may be verified based on their online identities, such as email accounts or social media accounts. Further, the use of digital signatures encoded into documents, as opposed to physical signatures printed with physical ink, provides assurance that the document was not modified after the signing. The distributed ledger file system advantageously enables users to own and control their documents without compromising security. Further, the distributed ledger file system advantageously makes collecting, storing and sharing of documents simpler, as all operations can be easily tracked on distributed ledger. Further, in an embodiment, the encrypted data may be advantageously decrypted based on user (or owner of the document) permission only, thus providing privacy to the sensitive information over the internet. In an embodiment, permission may be requested from owner of the document every time another user wants to view it. Further, any correction/update within the document may be stored in metadata hash values stored on the distributed ledger (108). Hence, authentic correction/update in the document may be easily verified. Further, the distributed ledger file system (102) can advantageously provide dividing information into private and public, matching of individual metadata hash values for private and public information with the private and public metadata hash stored on the distributed ledger (108), and certify the document as valid or invalid based on matching.
[0051] The foregoing discussion of the present invention has been presented for purposes of illustration and description. It is not intended to limit the present invention to the form or forms disclosed herein. In the foregoing Detailed Description, for example, various features of the present invention are grouped together in one or more embodiments, configurations, or aspects for the purpose of streamlining the disclosure. The features of the embodiments, configurations, or aspects may be combined in alternate embodiments, configurations, or aspects other than those discussed above. This method of disclosure is not to be interpreted as reflecting an intention the present invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment, configuration, or aspect. Thus, the following claims are hereby incorporated into this Detailed Description, with each claim

standing on its own as a separate embodiment of the present invention.
[0052] Moreover, though the description of the present invention has included description of one or more embodiments, configurations, or aspects and certain variations and modifications, other variations, combinations, and modifications are within the scope of the present invention, e.g., as may be within the skill and knowledge of those in the art, after understanding the present disclosure. It is intended to obtain rights which include alternative embodiments, configurations, or aspects to the extent permitted, including alternate, interchangeable and/or equivalent structures, functions, ranges or steps to those claimed, whether or not such alternate, interchangeable and/or equivalent structures, functions, ranges or steps are disclosed herein, and without intending to publicly dedicate any patentable subject matter.

CLAIMS

1.A distributed ledger file system (102) for enabling a user to create a secure bdoc
document, the distributed ledger file system (102) comprising a processor (110) and a
memory (112), the memory (112) storing:
an input module (204) configured to enable the user to provide predetermined information related to the bdoc document and a document;
a process module (206) configured to process the user supplied predetermined information to create a metadata file; and
a bdoc creator module (208) configured to bundle the document and metadata file together and to create the bdoc document.
2. The distributed ledger file system (102) as claimed in claim 1, wherein the predetermined information is information related to identity associated with the bdoc document.
3. The distributed ledger file system (102) as claimed in claim 1, wherein the input module (204) is further configured to enable the user to upload or create a document.
4. The distributed ledger file system (102) as claimed in claim 1, wherein the metadata file comprising information about a block chain ID, block chain type, document ID, basic information, pages, user information, user permissions, public information, history of bdoc, workflow, and previous version information.
5. The distributed ledger file system (102) as claimed in claim 1, wherein the process module (206) is configured to compute a hash of the basic information, pages, user information, user permissions, public information, history of bdoc, workflow, and previous version information.

6. The distributed ledger file system (102) as claimed in claim 1, wherein the process module (206) is configured to store the created hash values in the distributed ledger (108).
7. The distributed ledger file system (102) as claimed in claim 1, wherein the process module (206) is further configured to send a request to distributed ledger to assign a unique ID to the document.
8. The distributed ledger file system (102) as claimed in claim 1, further comprising a login module (202) configured to enable a user to create an account with the distributed ledger file system.
9. The distributed ledger file system (102) as claimed in claim 8, wherein the login module (202) is further configured to assign a unique ID to the user.
10. The distributed ledger file system (102) as claimed in claim 1, further comprising a verification module (210) configured to verify the bdoc document by computing a hash of the metadata file, and matching the computed hash value with the stored hash value in the distributed ledger (108).
11. The distributed ledger file system (102) as claimed in claim 1, further comprising an update module (212) configured to enable the user to update the bdoc document, based on permission of the owner of the document.
12. A computer-implemented method for enabling users to create a secure and auditable bdoc document, the computer-implemented method comprising:

enabling the user to provide predetermined information related to the bdoc document and a document;
processing the user supplied information to create a metadata file; and
bundling the document and metadata file together, and creating the bdoc document.
13. The computer-implemented method as claimed in claim 12, wherein the metadata file comprising information about a block chain ID, block chain type, document ID, basic information, pages, user information, user permissions, public information, history of bdoc, workflow, and previous version information.
14. The computer-implemented as claimed in claim 12, further comprising verifying the bdoc document by computing a hash of the metadata file, and matching the hash value with the stored hash value.
15. The computer-implemented method as claimed in claim 12, further comprising enabling the user to update the bdoc document.