Define and manage forms in a distributed ledger trust network
By introducing a metadata mechanism in DLTN, users can customize and manage forms and store records on the blockchain, solving the problem of limited functionality of form customization and management in the existing technology, and achieving more efficient form sharing and history management.
Patent Information
- Application Number
- CN201980088759.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2018-11-13
- Filing Date
- 2019-11-12
- Publication Date
- 2024-11-01
- Estimated Expiration
- 2039-11-12
AI Technical Summary
Existing blockchain technology is functionally limited in customizing and managing forms shared with other users, and cannot effectively customize and manage forms in the Distributed Ledger Trust Network (DLTN).
By introducing a metadata mechanism in DLTN, users can define and manage forms, control other users' access to forms, and store records and historical data of forms on the blockchain, realizing customization and sharing of forms.
Simplifies the definition and sharing process of forms in DLTN, provides intuitive tracking of form history and usage, and enhances user availability and security.
Smart Images

Figure CN113302645B_ABST
Abstract
Description
[0001] Related application information
[0002] This application claims the benefit of U.S. Provisional Patent Application No. 62 / 760,789, filed on November 13, 2018, the disclosure of which is incorporated herein by reference. Technical Field
[0003] Enhancements to the Distributed Ledger Trust Network ("DLTN"). Some of the enhancements relate to mechanisms for defining and managing forms in the DLTN using metadata that defines the forms. Background Art
[0004] Blockchain technology has been used in contexts such as banking, cryptocurrency exchanges, and smart contracts. In general, blockchain technology provides a distributed ledger that records transactions in a verifiable, permanent manner. The blockchain can be distributed across a network of computer systems called nodes. The nodes follow a protocol for communicating between nodes, adding new blocks to the blockchain, and approving ("validating") new blocks.
[0005] Typically, a blockchain is a list of dynamically growing records in a chain, called blocks. A given block is logically linked to a previous block in the blockchain. For example, by applying a cryptographic hash function to the data of a previous block, a hash value is calculated, and the hash value is stored in a given block. A given block also includes other fields, such as a timestamp and payload data (sometimes referred to as transaction data). The payload data typically represents one or more transactions, but more generally can be any kind of data. Typically, once a given block is added to the blockchain, the data in the given block cannot be modified later because any subsequent blocks depend on the data in the given block. (To retroactively change the data in a given block, subsequent blocks in the blockchain must also be changed, which requires a consensus level that is impossible or impractical within the blockchain network.) The integrity of the blockchain can be verified by recalculating the hash values for the corresponding blocks in the blockchain and comparing these recalculated hash values with the previously calculated hash values that logically link these blocks.
[0006] In some cases, multiple blocks may be generated simultaneously and added to the same previous block in the blockchain. This temporarily creates a fork in the blockchain. The nodes of the blockchain network follow a protocol to rank ("score") the different branches of the fork so that one of the branches (with the highest score) is followed by all nodes. In this way, the size of non-preferred branches of the blockchain is limited. Nodes supporting the blockchain share versions of the blockchain, and the version with the highest score is retained. Various incentives are implemented to reduce the likelihood that a version of the blockchain will be superseded the longer it is used.
[0007] By storing the blockchain across the nodes of the blockchain network, the risk of data loss associated with storing data in a single centralized location is mitigated. Depending on the implementation, each node in the blockchain network can store a full or partial copy of the blockchain.
[0008] In a public blockchain (also known as a permissionless blockchain), the blocks of the blockchain are accessible to participants in the blockchain network without permission. Any participant in the blockchain network can access blocks in the blockchain, verify blocks of the blockchain, add new blocks to the blockchain, and validate new blocks of the blockchain. Access control is not used in public blockchains. In contrast, in a private blockchain (also known as a permissioned blockchain), a central authority controls access to the blockchain network. That is, the central authority controls which participants can: access blocks in the blockchain, verify blocks of the blockchain, add new blocks to the blockchain, and validate new blocks of the blockchain.
[0009] In previous approaches to implementing blockchain, a given user was unable to customize and manage the forms that could be shared with other users, which limited the functionality of the blockchain network. Summary of the invention
[0010] In summary, the specific embodiments propose various innovations for the mechanism for customizing forms in a distributed ledger trust network ("DLTN"). With such innovations, a given user can define and manage customized forms shared with other users in the DLTN. For example, a given user can specify metadata that defines a form to be completed by other users, wherein the metadata defining the form is stored in the blockchain. A given user can set permissions for a form to control access to the form by other users, and a given user can assign a form to other users for completion. In this way, in some example implementations, the process of defining and sharing customized forms in the DLTN is simplified and available to users of the DLTN. As another example, after another user has submitted an instance of a form (including data entered by other users) to the blockchain, a given user can review and approve the instance of the form, or request corrections to the form by other users. In this way, in some example implementations, the process of reviewing submitted instances of a form is simplified. The blockchain can store records of forms (as specified by metadata), instances of the form including data provided by other users at different stages, and information about the status of those instances of the form (e.g., approved, correction requested, rejected), providing an intuitive way to track the history and usage of a form.
[0011] The innovations described herein include, but are not limited to, those covered by the claims. The innovations may be implemented as part of a method, as part of a computer system configured to perform the method, or as part of a non-transient computer-readable medium storing computer executable instructions, which are used to cause one or more processors in a computer system to perform the method. Various innovations may be used in combination or individually. The present disclosure is provided to introduce some concepts in a simplified form, which are further described below in the detailed description. The present disclosure is not intended to identify the key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. The foregoing and other purposes, features and advantages of the present invention will become more apparent through the following detailed description, which continues to refer to the accompanying drawings and illustrates many examples. The examples may also be used for other and different applications, and some details may be modified in various aspects without departing from the spirit and scope of the disclosed innovation. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] The following drawings illustrate some features of the disclosed innovation.
[0013] Figure 1 is a diagram illustrating an example computer system in which some of the described examples may be implemented.
[0014] Figure 2 is a diagram illustrating an example blockchain.
[0015] Figure 3 is a diagram illustrating an example architecture for managing a private blockchain in a DLTN.
[0016] Figure 4 It is shown in Figure 3 Illustration of an example architecture for authentication services and encryption / decryption services used in the architecture of .
[0017] Figure 5a and Figure 5b is a flow chart illustrating various aspects of a generalized technique for updating metadata defining a form in a DLTN.
[0018] Figure 6 is a protocol diagram illustrating an example method for updating metadata defining a form in a DLTN.
[0019] Figure 7a and Figure 7b is a flow chart illustrating various aspects of a generalized technique for providing instance data for instances of a form in a DLTN.
[0020] Figure 8 is a protocol diagram illustrating an example method for providing instance data for an instance of a form in a DLTN.
[0021] Figure 9a and Figure 9b is a flow chart illustrating various aspects of a generalized technique for reviewing and approving an example of a form in a DLTN.
[0022] Fig.10 is a protocol diagram illustrating an example method for reviewing and approving an example of a form in a DLTN.
[0023] Figures 11a to 11f is a diagram of example screen shots illustrating different features of managing metadata that defines a form in a DLTN. DETAILED DESCRIPTION
[0024] DETAILED DESCRIPTION Various innovations are proposed for a distributed ledger trust network ("DLTN"). Some of the innovations described herein relate to mechanisms for customizing forms in a DLTN.
[0025] In the examples described herein, the same reference numerals in different figures indicate the same components, modules or operations. More generally, various alternatives to the examples described herein are possible. For example, by changing the order of the described method actions, by splitting, repeating or omitting certain method actions, etc., some methods in the methods described herein can be changed. Various aspects of the disclosed technology can be used in combination or individually. Some of the innovations described herein solve one or more of the problems mentioned in the background. Generally, a given technology / tool cannot solve all such problems. It is to be understood that other examples can be utilized, and without departing from the scope of the present disclosure, structural, logical, software, hardware and electrical changes can be made. Therefore, the following description should not be considered restrictive. Specifically, the scope of the present invention is defined by the appended claims.
[0026] I. Example Computer System.
[0027] Figure 1 A generalized example of a suitable computer system (100) is illustrated in which many of the described innovations may be implemented. The innovations described herein relate to enhancements to a DLTN. Other than for use in a DLTN, the computer system (100) is not intended to suggest any limitation to the scope of use or functionality, as the innovations may be implemented in a variety of computer systems, including specialized computer systems suitable for operation in a DLTN.
[0028] Reference Figure 1, the computer system (100) includes one or more processing cores (110...11x) of a central processing unit ("CPU") and local on-chip memory (118). The processing core(s) (110...11x) execute computer executable instructions. The number of processing core(s) (110...11x) depends on the implementation and may be, for example, 4 or 8. The local memory (118) may be volatile memory (e.g., registers, cache, RAM), non-volatile memory (e.g., ROM, EEPROM, flash memory, etc.), or some combination of the two, which is accessible by the corresponding processing core(s) (110...11x).
[0029] The local memory (118) may store software (180) in the form of computer executable instructions that implement innovative tools for DLTN for operations performed by the corresponding processing core(s) (110...11x). Figure 1 In the present invention, the local memory (118) is an on-chip memory such as one or more caches, to which access operations, transfer operations, etc. by (multiple) processing cores (110...11x) are fast.
[0030] The computer system (100) may include a processing core (not shown) of a graphics processing unit (“GPU”) and local memory (not shown). Alternatively, the computer system (100) includes one or more processing cores (not shown) of a system on a chip (“SoC”), an application specific integrated circuit (“ASIC”), or other integrated circuit, and associated memory (not shown). The processing core(s) may execute computer executable instructions for one or more innovations for the DLTN.
[0031] More generally, the term "processor" may refer to any device that can process computer-executable instructions, and may include microprocessors, microcontrollers, programmable logic devices, digital signal processors, and / or other computing devices. The processor may be a CPU or other general purpose unit, however, it is also known to provide a dedicated processor using, for example, an ASIC or a field programmable gate array ("FPGA").
[0032] The term "control logic" may refer to a controller or more generally one or more processors operable to process computer-executable instructions, determine results, and generate outputs. Depending on the implementation, the control logic may be implemented by software executable on a CPU, by software controlling dedicated hardware (e.g., a GPU or other graphics hardware), or by dedicated hardware (e.g., in an ASIC).
[0033] The computer system (100) includes a shared memory (120), which may be a volatile memory (e.g., RAM), a non-volatile memory (e.g., ROM, EEPROM, flash memory, etc.), or some combination of the two, accessible by the processing core(s). The memory (120) stores software (180) in the form of computer executable instructions that implement one or more innovative tools for the DLTN for the operations performed. Figure 1 In the embodiment, the shared memory (120) is an off-chip memory, and the access operation and transfer operation of the processing core to the shared memory (120) are relatively slow.
[0034] The computer system (100) includes one or more network adapters (140). As used herein, the term network adapter refers to any network interface card ("NIC"), network interface, network interface controller, or network interface device. (Multiple) network adapters (140) support communication with another computing entity (e.g., server, other computer system) over a network. The network may be a wide area network, a local area network, a storage area network, or other network. (Multiple) network adapters (140) may support wired connections and / or wireless connections for use with wide area networks, local area networks, storage area networks, or other networks. (Multiple) network adapters (140) communicate data (such as computer executable instructions, audio or video input or output, or other data) over (multiple) network connections using modulated data signals. A modulated data signal is a signal that sets or changes one or more of its characteristics in such a way that the information in the signal is encoded. By way of example and not limitation, a network connection may use electrical, optical, RF, or other carriers.
[0035] The computer system (100) also includes one or more (plurality) input devices (150).
[0036] The input device(s) may be a touch input device (such as a keyboard, mouse, pen, or trackball), a scanning device, or another device that provides input to the computer system (100). The computer system (100) may also include video input, audio input, motion sensor / tracker input, and / or game controller input.
[0037] The computer system (100) includes one or more output devices (160). The output device(s) (160) may be a printer, a CD recorder, a video output, an audio output, or another device that provides output from the computer system (100).
[0038] The storage device (170) may be removable or non-removable and includes magnetic media (such as disks, tapes, or cassettes), optical media, and / or any other media that can be used to store information and can be accessed within the computer system (100). The storage device (170) stores instructions for software (180) that implements one or more innovations for DLTN.
[0039] An interconnection mechanism (not shown) such as a bus, controller, or network interconnects the components of the computer system (100). Typically, operating system software (not shown) provides an operating environment for other software executed in the computer system (100) and coordinates the activities of the components of the computer system (100).
[0040] Figure 1 The computer system (100) is a physical computer system. A virtual machine may include Figure 1 Components are organized as shown.
[0041] The term "application" or "program" may refer to software, such as any user mode instructions for providing functionality. The software of an application (or program) may also include instructions for an operating system and / or device driver. The software may be stored in an associated memory. The software may be, for example, firmware. Although it is contemplated that a properly programmed general-purpose computer or computing device may be used to execute such software, it is also contemplated that hard-wired circuitry or custom hardware (e.g., ASIC) may be used in place of, or in combination with, software instructions. Therefore, the examples are not limited to any particular combination of hardware and software.
[0042] The term "computer-readable medium" refers to any medium that participates in providing data (e.g., instructions) that can be read by a processor and accessed within a computing environment. Computer-readable media can take many forms, including but not limited to non-volatile media and volatile media. Non-volatile media include, for example, optical or magnetic disks and other persistent memories. Volatile media include dynamic random access memory ("DRAM"). Common forms of computer-readable media include, for example, solid-state drives, flash drives, hard disks, any other magnetic media, CD-ROMs, digital versatile disks ("DVDs"), any other optical media, RAM, programmable read-only memory ("PROM"), erasable programmable read-only memory ("EPROM"), USB memory sticks, any other memory chip or cartridge, or any other medium from which a computer can read. The term "computer-readable memory" specifically excludes transient propagation signals, carrier waves, and waveforms or other intangible or transient media, although they can be read by a computer. The term "carrier wave" may refer to an electromagnetic wave that is modulated in amplitude or frequency to convey a signal.
[0043] Innovation can be described in the general context that computer executable instructions are executed in a computer system on a target real or virtual processor. Computer executable instructions may include instructions executable on a processing core of a general-purpose processor to provide functionality described herein, instructions executable to control a GPU or dedicated hardware to provide functionality described herein, instructions executable on a processing core of a GPU to provide functionality described herein, and / or instructions executable on a processing core of a dedicated processor to provide functionality described herein. In some implementations, computer executable instructions may be organized in program modules. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of program modules may be combined or split between program modules as desired. Computer executable instructions for program modules may be executed in a local or distributed computer system.
[0044] Many examples are described in the present disclosure and are presented for illustrative purposes only. The examples described are not restrictive in any sense and are not intended to be restrictive. As is apparent from the present disclosure, the innovation currently disclosed can be widely applied to many contexts. Those of ordinary skill in the art will recognize that the disclosed innovation can be put into practice with various modifications and changes (such as structural, logical, software and electrical modifications). Although the specific features of the disclosed innovations can be described with reference to one or more specific examples, it should be understood that, unless otherwise expressly specified, such features are not limited to the usage in one or more specific examples to which they are described with reference. The present disclosure is neither a literal description of all examples nor a list of features of the present invention that must exist in all examples.
[0045] When an ordinal number (such as "first", "second", "third", etc.) is used as an adjective before a term, (unless otherwise expressly specified) the ordinal number is used only to indicate a specific feature, such as to distinguish the specific feature from another feature described by the same or similar terms. The mere use of the ordinal numbers "first", "second", "third", etc. does not indicate any physical order or position, any temporal order, or any ranking of importance, quality, etc. In addition, the mere use of an ordinal number does not define a numerical limitation on the feature identified by the ordinal number.
[0046] When introducing an element, the articles “a,” “an,” “the,” and “said” are intended to mean that there are one or more of the elements. The terms “comprising,” “including,” and “having” are intended to be inclusive and mean that there may be additional elements other than the listed elements.
[0047] When a single device, component, module or structure is described, multiple devices, components, modules or structures (whether they collaborate or not) can be used instead of a single device, component, module or structure. The functionality described as being owned by a single device can be owned by multiple devices instead, whether they collaborate or not. Similarly, where multiple devices, components, modules or structures are described in this article, whether they collaborate or not, a single device, component, module or structure can be used instead of multiple devices, components, modules or structures. The functionality described as being owned by multiple devices can be owned by a single device instead. Typically, a computer system or device can be local or distributed, and can include any combination of dedicated hardware and / or hardware with software that implements the functionality described herein.
[0048] Further, the techniques and tools described herein are not limited to the specific examples described herein. Rather, the corresponding techniques and tools can be utilized independently and separately from other techniques and tools described herein.
[0049] Devices, components, modules or structures that communicate with each other do not need to communicate with each other continuously unless otherwise explicitly specified. Instead, such devices, components, modules or structures only need to transmit to each other when necessary or desired, and can actually suppress exchanging data most of the time. For example, a device that communicates with another device via the Internet may not transmit data to the other device for weeks at a time. In addition, devices, components, modules or structures that communicate with each other can communicate directly or indirectly through one or more intermediaries.
[0050] As used herein, the term "send" means any way of conveying information from one device, component, module or structure to another device, component, module or structure. The term "receive" means any way of obtaining information from another device, component, module or structure at a device, component, module or structure. Device, component, module or structure can be part of the same computer system or different computer systems. Information can be passed by value (for example, as a parameter of a message or function call), or passed by reference (for example, in a buffer). Depending on the context, information can be directly transmitted or communicated through one or more intermediate devices, components, modules or structures. As used herein, the term "connected" means an operable communication link between a device, component, module or structure, which can be part of the same computer system or different computer systems. An operable communication link can be a wired or wireless network connection, which can be direct or through one or more intermediaries (for example, of a network).
[0051] The description of an example with multiple features does not imply that all or even any of such features are required. Instead, various optional features are described to illustrate multiple possible examples of the innovation described herein. Unless otherwise explicitly specified, no feature is necessary or required.
[0052] In addition, although process steps and phases can be described in a sequential order, such a process can be configured to work in a different order. The description of a specific sequence or order does not necessarily indicate that the step / phase is required to be performed in this order. The step or phase can be performed in any practical order. In addition, although described or implied as non-simultaneous occurrence, some steps or phases can be performed simultaneously. Describing a process as including multiple steps or phases does not imply that all or any steps or phases in the step or phase are necessary or required. Various other examples can omit some or all steps or phases in the described steps or phases. Unless otherwise clearly specified, no step or phase is necessary or required. Similarly, although a product can be described as including multiple aspects, qualities or characteristics, this does not mean that all of them are necessary or required. Various other examples can omit some or all aspects, qualities or characteristics in these aspects, qualities or characteristics.
[0053] An enumerated listing of items does not imply that any or all of those items are mutually exclusive, unless expressly specified otherwise. Likewise, an enumerated listing of items does not imply that any or all of those items are comprehensive for any category, unless expressly specified otherwise.
[0054] For purposes of illustration, the detailed description uses terms such as "determine" and "select" to describe computer operations in a computer system. These terms represent operations performed by one or more processors or other components in a computer system and should not be confused with actions performed by humans. The actual computer operations corresponding to these terms vary depending on the implementation.
[0055] II. Example blockchain.
[0056] Figure 2 An example blockchain (200) is shown, which is simplified for illustration. The blockchain (200) can be replicated between different nodes of the blockchain network. Each of the nodes can store a full or partial copy of the blockchain (200). The blockchain (200) includes a plurality of blocks, starting with a root block and growing dynamically as blocks are added to the blockchain. Each of the blocks includes a header and payload data.
[0057] The header of a block includes a plurality of fields. With the exception of the root block, the header includes a hash value that is a hash value calculated by applying a cryptographic hash function to the data of a previous block in the blockchain (200). In this manner, a given block is logically linked to a previous block in the blockchain. For example, the hash value of block 1 is calculated by applying a cryptographic hash function to the data of the root block, the hash value of block 2 is calculated by applying a cryptographic hash function to the data of block 1, and so on. The integrity of the blockchain (200) can be verified by recalculating hash values for corresponding blocks in the blockchain (200) and comparing these recalculated hash values to the previously calculated hash values (in the header) that logically link these blocks. In this manner, payload data in the blockchain (200) can be verified.
[0058] The header of the chunk also includes a timestamp and a user identifier ("ID") of the user associated with the chunk (e.g., the owner of the payload data). Other fields of the header depend on the implementation and are not shown for simplicity. For example, these fields may include a key ID that identifies the encryption key used to encrypt the payload data in the chunk and a category ID that identifies the category of the payload data in the chunk. In general, the fields of the header depend on the rules defined for the DLTN.
[0059] The blockchain (200) is used as a primary storage device for various types of data. The blockchain (200) can be shared - there is no central database that always stores data, and there is no central administrator who owns and controls the data. Payload data (sometimes called transaction data) is arbitrary data. In some blocks of the blockchain (200), the payload data is user data for a user (e.g., for one or more transactions, contact data, biographical data, identification documents), where the user data can include static data and / or dynamic data. In some other blocks of the blockchain (200), the payload data is metadata that defines a form or instance data of the form, which can be set as explained in Sections III and IV. More generally, payload data can be any kind of data.
[0060] exist Figure 2In the example of , the payload data in a given block is "owned" by the user specified by the user ID in the given block. Permission settings for the user are used to control access to the user's user data, and the permission settings can be stored in the blockchain (200) or stored outside the blockchain. The payload data in the blockchain (200) can be encrypted by user-specific (for the respective owner of the payload data) and context-specific (e.g., depending on access privileges) encryption keys. Therefore, the blockchain (200) can include different encrypted versions of the same payload data, which can be accessible to different groups of users.
[0061] Because cryptographic hash functions are applied successively to compute hash values that logically link blocks in the blockchain (200), a block depends on data (including hash values) of earlier blocks in the blockchain (200). Typically, once a block is added to the blockchain (200), the data in the block cannot be modified later. In order to retroactively change the data in a block, subsequent blocks in the blockchain must also be changed, which requires a level of consensus within the blockchain network that is impossible or impractical to achieve.
[0062] In some cases, multiple blocks may be generated simultaneously and added to the same previous block in the blockchain (200). Figure 2 In , block 2 and block 3 are generated simultaneously and added from block 1 of blockchain (200). This temporarily creates a fork in blockchain (200). A protocol is followed to rank ("score") the different branches of the fork so that all nodes follow the one branch (with the highest score). Figure 2 In the example, block 2 has a higher score than block 3, so subsequent blocks are added from block 2. Nodes in the blockchain network share versions of the blockchain (200), and the version with the highest score is retained. Various incentives are implemented to reduce the likelihood that a version of the blockchain (200) will be replaced as it is used longer.
[0063] In many of the examples described herein, the blockchain is a private permissioned blockchain. However, in some examples, the blockchain may instead be a public blockchain.
[0064] To keep it simple, Figure 2A blockchain (200) is shown in which all blocks are logically linked in a single chain (e.g., using hash values for the corresponding blocks). Alternatively, a set of separate chains of blocks may be used instead of a single blockchain, such as logically linking blocks of user data in one chain and logically linking blocks of metadata of forms in another chain. As used herein, the term "blockchain" or "the blockchain" includes blocks that are logically linked into one or more chains managed by a blockchain platform.
[0065] III. Example Architecture.
[0066] Figure 3 An example architecture (300) for managing a private blockchain in a DLTN is shown. In the example architecture (300), various entities are configured to communicate over a network (320) such as the Internet.
[0067] The one or more client systems (310) each include a DLTN client (312) for the DLTN. The user of the DLTN client (312) may be an individual, a small business, a large business, a bank, a non-profit organization, a government agency, or another entity. The client system (310) may be a personal computer, a laptop computer, a smartphone, or other type of computing device.
[0068] exist Figure 3 In the embodiment of the present invention, each of the one or more integrated partner systems (315) further includes a DLTN client (316) for the DLTN. Users of the integrated partner systems (315) potentially have enhanced privileges, permissions, or rights in the DLTN compared to users of the client system (310). However, for the purposes of the innovation described herein, the DLTN client (316) for the integrated partner system (315) is essentially the same as the DLTN client (312) for the client system (310). The integrated partner system (315) can be a personal computer, a laptop computer, a smart phone, or other type of computing device.
[0069] The DLTN client (312, 316) is configured to interoperate with a DLTN server (370) for DLTN via a secure connection (e.g., an SSL encrypted connection). Typically, the DLTN client (312, 316) provides a client-side user interface ("UI") to the DLTN. The DLTN client (312, 316) can make other client-side decisions and manage client-side communications. The DLTN client (312, 316) can be implemented as an independent executable file (e.g., a separate application). Alternatively, the DLTN client (312, 316) can be implemented using client-side script logic or other control logic in a Web browser environment that is executed on the client side. Alternatively, the DLTN client (312, 316) can be implemented as a set of functions of a Web browser to control client-oriented script logic executed by a DLTN server, wherein the script logic is executed at the DLTN server, but is a client-side controlled user input for navigation (e.g., click, data entry). Thus, the DLTN client (312, 316) may be implemented using conventional web browser functionality that provides a "front end" to the DLTN server's web application. In some example implementations, the DLTN client (312, 316) is implemented using conventional web browser functionality that uses JavaScript Object Notation ("JSON") to control client-facing scripts to interoperate with the DLTN. In conjunction with the DLTN server (370) actions, the DLTN client (312, 316) is configured to allow a user to perform various actions. For example, through the DLTN client (312, 316), a user can: log in to the DLTN; manage the network of connections to other users of the DLTN; engage in transactions with other users in the DLTN; add, edit, or remove user data; edit permission settings for a user's user data; request access to another user's user data; grant or revoke access to the user's user data in response to a request from another user; create a custom form to share with other users; provide data for a form shared by another user; or review, approve, reject, or take some other action on a submitted form. Specifically, the functionality of the DLTN client (312, 316) in various scenarios is described in Section IV.
[0070] One or more external service providers (390) are configured to provide services to the DLTN server (370). The external service providers (390) are configured to interoperate with the DLTN server (370) through a secure connection (eg, an SSL encrypted connection).
[0071] For example, the external service providers (390) may include one or more providers of communication services that are configured to provide programmatic access to the DLTN server (370) for functionality to make and receive phone calls, send and receive text messages via SMS or another set of protocols, or perform other communication functions. In some examples, the external service providers (390) include Twilio, Clickatell, and Nexmo. Specifically, the providers of communication services may allow the DLTN server (370) to communicate with the user via alternative communication channels (e.g., phone calls and voice navigation menus; SMS messages).
[0072] As another example, the external service providers (390) may include one or more providers of email services that are configured to provide programmatic access to the DLTN server (370) for functionality to send and receive emails. In some example implementations, the external service providers (390) include SendGrid. Specifically, the providers of email services may allow the DLTN server (370) to communicate with users via alternative communication channels (e.g., email).
[0073] exist Figure 3 In the example, cloud computing services (330, 350) are hosted to provide functional services for DLTN. For example, cloud computing services (330, 350) are provided by Microsoft Azure, Google Cloud or Amazon Web Services. Figure 3 Two different providers (330, 350) for cloud computing services are shown, alternatively, a single provider or more providers can be used to host services that provide functionality for the DLTN. Alternatively, privately owned computing resources or a mix of privately owned computing resources and cloud computing services can be used to provide server-side functionality for the DLTN.
[0074] The cloud computing service (330, 350) can be configured to organize services into separate partitions, groups, etc. In this way, the cloud computing service (330, 350) can support scaling and / or replication of services. The load balancer (354) can be configured to distribute traffic and workloads across partitions.
[0075] The firewall (332, 352) can be configured to monitor and control incoming network traffic and outgoing network traffic. The firewall (332, 352) can be configured to apply various security rules to establish a barrier between the network (320) and the resources of the cloud computing service (330, 350). The cloud computing service (330, 350) can be configured to include one or more public subnets and one or more isolated (private) subnets. Typically, the public subnets are accessible to the Internet. The isolated network is not accessible through the Internet, but is instead accessible through an access control list ("ACL") or other mechanism managed by the cloud computing service (330, 350).
[0076] In some example implementations, services hosted in cloud computing services (330, 350) are deployed in "containers" or executed in virtual machines. Containers or virtual machines virtualize access to resources provided by cloud computing services (330, 350). In some example implementations, services are deployed in Docker containers, which can be distributed across different locations.
[0077] DLTN includes various dedicated nodes, which are configured to perform different services according to the rules of DLTN. For redundancy, nodes can be distributed across one or more clouds provided by cloud computing services (330, 350). For example, DLTN uses Ethereum technology, which provides a distributed computing platform and operating system based on blockchain, which may support smart contract functionality. Alternatively, DLTN uses another technology (such as Eris:db, HydraChain, Hyperledger Fabric, Iroha, Sawtooth Lake, IBM blockchain platform, Multichain, Openchain, Cardano, Quorum, Stellar, Symbiont Assembly, BigChainDB, ChainCore, Corda, Credits, Domus Tower blockchain, Elements blockchain platform). As used herein, the terms "distributed ledger trust network" and "blockchain network" are interchangeable, and the term blockchain generally indicates any record (block) account book that is logically linked.
[0078] The nodes (334, 356, 360) of the DLTN provide various services. Typically, the DLTN node can be configured to store (synchronize) data of the blockchain. Alternatively, the DLTN node can be configured to verify transactions before a new block is added to the blockchain. (In some example implementations, blocks can be added to the blockchain without using cryptocurrency for payment. Like this, the speed and security of transactions are not affected by the potential volatility of the cryptocurrency used in the DLTN.) Alternatively, the DLTN node can coordinate activities in the DLTN. Typically, in order to add a block to the blockchain, the DLTN node approves (verifies) the block and adds the block.
[0079] exist Figure 3 In the embodiment of the present invention, a DLTN node (356) hosted in a public subnetwork of a cloud computing service (350) provides a node discovery service. The node discovery service is used to locate nodes in the DLTN. In some example implementations, the DLTN node (356) is an Ethereum bootstrap node that provides a lightweight service for locating nodes according to a node discovery protocol. As another example, a DLTN node (360) hosted in an isolated subnetwork of a cloud computing service (350) provides an RPC service and / or a mining service. In some example implementations, the node (360) provides an Ethereum RPC service. As another example, a DLTN node (334) hosted in a public subnetwork of a cloud computing service (330) provides a node discovery service, an RPC service, and / or a mining service. The DLTN nodes (334, 356) in the public subnetwork communicate via encrypted data transmission through the network (320). The DLTN node (360) in the isolated subnetwork communicates with the node (356) in the public subnetwork via a connection protected by a network ACL and encryption.
[0080] In some example implementations, the DLTN nodes (334, 356, 360) are Ethereum nodes implemented using Geth. Alternatively, the nodes use another implementation of Ethereum or use another DLTN technology. In some example implementations, the DLTN nodes (334, 356, 360) are deployed in a Docker container. Alternatively, the DLTN nodes (334, 356, 360) are deployed using another virtualization technology.
[0081] The architecture (300) includes one or more DLTN servers (370). The DLTN server (370) is configured to interoperate with one or more DLTN clients (312, 316) of the DLTN via a secure connection (e.g., an SSL encrypted connection). The DLTN server (370) is also configured to interoperate with one or more external service providers (390) via a secure connection (e.g., an SSL encrypted connection). The DLTN server (370) can be implemented as a standalone executable file, a Web application (also referred to as a Web-based application), or in some other way. In some example implementations, the DLTN server (370) includes a method executable to implement an application programming interface ("API"), provide Web application functionality, make other server-side decisions, and manage control logic for server-side communications. In these example implementations, the API is designed according to the principles of representation layer state transfer ("REST") The API is designed to have a predictable resource-oriented uniform resource locator ("URL") and use HTTP response codes to indicate API errors. The API uses built-in HTTP features (such as HTTP verbs) that are generally understood by off-the-shelf HTTP clients. The API uses JSON for input and output. The web application component of the DLTN server (370) can be separated from the API component of the DLTN server (370). For example, with respect to the front-end component for interoperating with the DLTN client (312, 316), the DLTN server (370) can be implemented using a library (such as React, JavaScript library) that provides functionality for building a UI and a library (such as Redux, JavaScript library) that provides functionality for managing application state. With respect to the back-end component, the DLTN server (370) can be implemented using a runtime environment (such as NodeJS) for server-side scripts and command-line tools and a web application framework (such as Express) that provides functionality for building web applications and APIs. Alternatively, the DLTN server (370) can be implemented in some other way. In some example implementations, the DLTN server (370) is deployed in a Docker container in a cloud computing environment. Alternatively, the DLTN server (370) is deployed using another virtualization technology.
[0082] In some aspects, one or more DLTN servers (370) in the architecture (300) act as a centralized authority by mediating access to the blockchain network and other platform functions (e.g., for authentication or encryption / decryption). For example, the DLTN server (370) uses a permission mechanism to control write access to the blockchain and restrict read access to the blockchain. However, in other aspects, the DLTN server (370) does not act as a central authority. There may be multiple DLTN servers (370). Moreover, transactions between users of the DLTN do not require approval or mediation of the DLTN server (370) other than mediating access to the blockchain network or other platform functions.
[0083] The DLTN server (370) is configured to allow a user to perform various actions through the DLTN client (312, 316), as described above. Specifically, the functionality of the DLTN client (370) in various scenarios is described in Section IV.
[0084] The DLTN clients (312, 316) and DLTN servers (370) may be internationalized / localized into different languages.
[0085] The architecture (300) also includes a storage device (372) configured to store photos, attachments, and other data accessible to the DLTN server (370). Such data can be used in various operations of the DLTN. The DLTN server (370) is configured to connect to the storage device (372) via a connection protected by using a network ACL and encryption.
[0086] The authentication service (380) provides authentication services to the DLTN server (370). The encryption service (382) provides encryption / decryption services to the DLTN server (370). The DLTN server (370) connects to the authentication service (380) and the encryption service (382) via a connection protected by a network ACL and encryption. In some example implementations, the authentication service (380) and the encryption service (382) are implemented using Vault. Alternatively, the authentication service (380) and the encryption service (382) can be implemented in some other way. In some example implementations, the authentication service (380) and the encryption service (382) are deployed in a Docker container in a cloud computing environment. Alternatively, the authentication service (380) and the encryption service (382) are deployed using another virtualization technology.
[0087] The authentication service (380) and the encryption service (382) are configured to manage and apply access rules (384) (such as ACL data, policy data) and encryption keys (386) in a storage device that is accessible to the authentication service (380) and the encryption service (382) through a secure connection. The access rules (384) (e.g., ACL data, policy data) and encryption keys (386) are stored in an encrypted form in a protected (isolated) subnetwork without Internet access. In a DLTN, data is typically encrypted at rest and in transit. Typically, data in a blockchain is encrypted using user-specific and context-specific encryption keys. In transit, data can be encrypted using mechanisms provided by the connection. In some example implementations, the key storage device is implemented using Consul. Alternatively, the key storage device can be implemented in some other way.
[0088] Operation and characteristics of authentication service (380) and encryption service (382) Figure 4 The architecture (400) is further explained.
[0089] The authentication service (380) performs various operations to initialize structures and data for authentication. For example, after a threshold number of master key shares (412) are acquired, the authentication service (380) can use a set of master key shares (412) to create a master key (422). The authentication service (380) can use the master key (422) to determine an encryption key (428), which can be used to decrypt access rules (384) and user encryption keys (386). The authentication service (380) can retrieve encrypted versions of the access rules (384) and user encryption keys (386) from a persistent storage device (438) and perform a decryption operation using the encryption key (428). The decrypted access rules (384) and user encryption keys (386) are buffered in a cache (430) in a memory accessible to the authentication service (380).
[0090] When a user registers, the authentication service (380) can randomly generate a set of encryption keys for the user. The authentication service (380) can use key derivation and rotation to separate encryption contexts. If necessary, the authentication service (380) can generate additional encryption keys for users (e.g., for different subsets of users whose user data is shared, or for other different contexts). Depending on the implementation, the encryption keys for users can be organized in different ways. For example, the encryption keys for users can include a first set of one or more encryption keys for encrypting / decrypting data that is not shared (i.e., private), a second set of one or more encryption keys for encrypting / decrypting the connection shared with the user in the DLTN, and a third set of one or more encryption keys for encrypting / decrypting the data shared with everyone in the DLTN (i.e., public). In this configuration, according to the access rules (ACL, policy data, etc.) and consistent with the permission settings, the (multiple) first encryption key is not shared with other users, the (multiple) second encryption key is shared with the connection of the user in the DLTN, and the (multiple) third encryption key is shared with all users in the DLTN. (An encryption key "shared" with another user can be accessed and used by the encryption service (382) on behalf of the other user, but is not actually assigned to the other user.) Or, as another example, the encryption keys for a user may include one or more encryption keys for each different subset of users in the DLTN (e.g., a first encryption key (s) not shared with the user, a second encryption key (s) shared with a first subset of users, a third encryption key (s) shared with a second subset of users, ..., an nth encryption key (s) shared with all users). Alternatively, the encryption keys for the users may be organized in some other manner.
[0091] Typically, access to sensitive data is limited to rely on authentication, authorization, and accountability provided using the authentication service (380) and encryption service (382). Before a user receives access to encryption keys, encryption / decryption requests are checked and logged according to security policies. In operation, the authentication service (380) uses ACLs and policies to specify access by users to encryption keys owned by users and shared encryption keys. In some example implementations, the authentication service (380) operates in a "whitelist" mode. Actions are not allowed unless explicitly granted via policies. The authentication service (380) receives user credentials (424) for the user from the DLTN server (370) and authenticates the user according to access rules (e.g., ACL data, policy data). If the user is authenticated and access is granted, the authentication service (380) returns a user authentication token (426) for the user. The user authentication token (426) is associated with a list of access policies and corresponding encryption keys that can be used according to the access policies, which are also provided to the encryption service (382).
[0092] For encryption / decryption, the DLTN server (370) passes the user data (442) and the user authentication token (426) to the encryption service (382). The encryption service (382) returns the user data (444). For decryption operations, the user data (442) passed to the encryption service (382) is encrypted, and the user data (444) returned by the encryption service has been decrypted using the appropriate encryption key. For encryption operations, the user data (442) passed to the encryption service (382) is decrypted, and the user data (444) returned by the encryption service has been encrypted using the appropriate encryption key. As described in Section IV, the "user data" encrypted / decrypted by the encryption service (382) can be metadata defining a form, instance data of a form, or feedback to a form. In some example implementations, the encryption service (382) uses symmetric key encryption—the same encryption key is used for encryption and decryption of data. Alternatively, the encryption service can use asymmetric key encryption (e.g., according to a public / private key protocol).
[0093] IV. Define sample metadata for a form and related operations.
[0094] This section describes various aspects of managing custom forms using metadata stored in the blockchain of the DLTN. In some example implementations, these innovations enable users to create custom forms and manage workflows using custom forms in the DLTN. The innovations described in this section can be used to support various features, including but not limited to:
[0095] The ability for users (form creators) to define custom forms through the DLTN client’s UI using metadata that is stored in the blockchain;
[0096] • The ability for a user (form creator) to set permissions to share a custom form with all other users in the DLTN or with selected other users;
[0097] • The ability for users (form creators) to assign customized forms to other users in the DLTN;
[0098] ● The ability for users (form creators) to create and manage approval workflows for custom forms;
[0099] The ability for a user (form submitter) to provide data for a custom form and submit an instance of the custom form, which is stored in the blockchain;
[0100] The ability for a user (form reviewer) to review an instance of a custom form stored in the blockchain and approve or otherwise provide feedback on the instance of the form; and
[0101] ●The ability for users to create and access immutable records of custom forms, submitted instances of custom forms, and the status of submitted instances at various stages.
[0102] A. Introduction.
[0103] In addition to storing user data, the blockchain can also store metadata that defines custom forms. The DLTN server in the DLTN can provide a UI through the DLTN client, allowing users to define custom forms. When a custom form is saved, the metadata that defines the custom form can be stored in a new block of the blockchain in association with the user ID of the user who created the custom form.
[0104] When creating a custom form, a user can start from a previous custom form, from a preset template of a form, or from an empty form. A user can add one or more fields to a custom form. A custom form can contain any number of data fields, each with defined properties. For example, a user can specify information for a field of a custom form, such as a name, a control type (e.g., text, radio button, slider), or another property. A custom form can include a single part or multiple parts. A custom form can also include embedded rules to check the consistency of data, and which fields are active depending on which data is adapted to be previously entered. This provides scalability at the data layer and the form layer.
[0105] Users can set permissions for custom forms to control which users can access custom forms in the DLTN. For example, custom forms can be made available to all connections of users in the DLTN, selected users in the DLTN, or all users in the DLTN. This provides scalability of access levels for security and permission management of custom forms in the DLTN. Permission settings for custom forms can be managed using any of a variety of mechanisms.
[0106] In order for the user to provide data for the custom form, the DLTN client can present the custom form. For example, the DLTN client draws the custom form in its UI and accepts user input in the fields of the custom form. When the user completes entering data into the custom form, the user can sign the custom form with an electronic signature. The user submits the custom form by saving the instance of the custom form in a new block of the blockchain in association with the user ID of the user who submitted the custom form. The new block may include metadata defining the form and data provided by the user. The user who submits the instance of the custom form can specify a permission so that the user and the form reviewer can access the submitted instance of the custom form. Therefore, when the user enters data for the instance of the custom form, the user can set the permission for the instance of the custom form to control which users can access and review the instance of the custom form. The permission setting for the instance data can be managed using any of a variety of mechanisms.
[0107] The reviewer can review the submitted instance of the custom form. For example, the DLTN client draws the submitted instance of the custom form in its UI and accepts feedback from the reviewer. The reviewer can check the electronic signature, approve the instance of the form, request the instance of the correction form, or provide other feedback. The new (reviewed) instance of the custom form can be stored in a new block of the blockchain in association with the user ID of the user who reviewed the custom form. The new block can include metadata defining the form, as well as data provided by the submitter and feedback from the reviewer. The reviewer can specify permission so that the original form submitter (submitter of the instance data) and the reviewer can access the new instance of the custom form. The permission settings for feedback (or new instance) from the reviewer can be managed using any of a variety of mechanisms. If requested, the submitter can make changes to the previously submitted instance of the custom form or the reviewed instance, and save another instance of the custom form in the blockchain.
[0108] Typically, each new event of the submission and review process may cause a new block to be saved in the blockchain. Together, these blocks provide a history of instances of custom forms submitted by users. For example, the blockchain includes a block for an instance of a custom form initially completed by a user, another block for a correction request, and a third block for a changed / corrected instance of the custom form. Upon approval, the blockchain includes a block for the approved instance of the custom form.
[0109] B. Examples of operations involving metadata that define a form.
[0110] Figure 5a , Figure 5b , Figure 7a , Figure 7b , Figure 9a and Figure 9b Different operations involving metadata defining a form are illustrated. Some of these operations are performed by a DLTN client, while other operations are performed by a DLTN server. Typically, a DLTN client is configured to perform various operations to interoperate with a DLTN server to access the DLTN, and a DLTN server is configured to perform various operations to provide access to the DLTN. In some example implementations, the DLTN uses Ethereum technology. Alternatively, the DLTN uses another DLTN technology.
[0111] In these examples, the metadata defining the form is (or will be) stored in the blockchain of the DLTN in association with the identity of the user who owns the form. In some example implementations, the blockchain is a private blockchain, where the DLTN server manages access to the private blockchain. Alternatively, the blockchain is a public blockchain. The blockchain includes one or more blocks. For example, a given block among the (multiple) blocks of the blockchain includes a hash value based on one or more previous blocks in the blockchain, a key identifier, a type value, a user ID of a given user, and metadata defining a form owned by a given user. The metadata is encrypted using, for example, one of a set of encryption keys that are user-specific and context-specific. Alternatively, a given block of the blockchain includes other and / or additional fields. Access to the metadata defining the form can be managed using permission settings.
[0112] In some example implementations, the DLTN client is referenced Figure 3 The DLTN client (312, 316) described herein and the DLTN server are referenced Figure 3The DLTN server (370) described herein. The DLTN server may include a web application and implement an API accessible to the DLTN client. The DLTN client may be implemented as a set of functions of a web browser to control client-oriented script logic executed by the DLTN server. The DLTN server executes in a public subnet of a cloud computing service. The DLTN server is configured to call authentication services and encryption services executed in an isolated subnet of a cloud computing service. For operations involving a blockchain of the DLTN, the DLTN server is configured to call one or more nodes of the DLTN, which are executed in an isolated subnet of a cloud computing service. Alternatively, for example, as described above with reference to Figure 3 As described, the DLTN client and / or the DLTN server are implemented in some other manner.
[0113] C. Example of defining metadata for a custom form.
[0114] Figure 5a A generalized technique for updating metadata defining a form in a DLTN is shown from the perspective of a given user's DLTN client (501). Figure 5b A generalized technique for updating metadata defining a form in a DLTN is shown from the perspective of a DLTN server (502). When a previously created form is revised, Figure 5a and 5b The update activity shown can occur. In this case, the metadata defining the form includes previously specified values that are modified according to one or more updates to the form. The updates can include, for example, the addition or change of a title of the form; the addition, removal, or change of parts of the form; the addition, removal, or change of fields of the form; the addition, removal, or change of properties of the fields; the addition, removal, or change of permission settings for the form; and / or some other addition, removal, or change. Alternatively, when the form is created, Figure 5a and 5b The update activity shown may occur. In this case, the metadata defining the form includes default initial values, which may be modified according to one or more updates to the form. The updates may include, for example, the addition of a title to the form; the addition of sections to the form; the addition of fields to the form; the addition of properties to the fields; the addition of permission settings for the form; and / or some other addition or change.
[0115] Reference Figure 5b , the DLTN server sends (510) metadata defining a given form to the DLTN client. Figure 5a, the DLTN client receives (515) metadata defining a given form from the DLTN server. The metadata defining the given form may be sent / received in an encrypted form over a secure connection. The metadata may define various properties of the given form, such as a title for the given form, one or more parts of the given form, and one or more fields of the given form. For a given field, the metadata may define one or more attributes of the field, such as the type of the field (e.g., short text, multi-line text, drop-down menu, selection list, checkbox, slider, date / time picker, formula, or attachment), the title of the field, a default value for the field, a description of the field, an indication of whether validation for the field is required, an indication of whether the value of the field is required to be unique, and / or another attribute. The metadata may also include one or more permission settings for the given form, which may allow the form to be shared with all connections of the user or with a subset of the user's connections, or not shared at all (private).
[0116] The DLTN client draws (520) a given form based on the metadata on a UI of the DLTN client. The DLTN client may include a form drawing engine (e.g., as part of a web browser) that is operable to parse the metadata defining the given form and perform drawing of the form. In addition to displaying information about the form (e.g., title, (multiple) sections, (multiple) fields, (multiple) properties of (multiple) fields, permission settings), the DLTN client also presents graphical elements operable to edit the form through the UI of the DLTN client. The graphical elements may include text boxes, drop-down menus, selection lists, check boxes, slider controls, and / or other controls for editing properties of the given form and properties of the fields.
[0117] The DLTN client receives (525) user input from a user via the UI of the DLTN client indicating one or more updates to metadata defining a given form. For example, the updates may include the addition or change of a title of a form; the addition, removal or change of portions of a form; the addition, removal or change of fields of a form; the addition, removal or change of attributes of a field; the addition, removal or change of permission settings for a form; and / or some other modification to the form. The DLTN client sends (530) the update(s) to the metadata defining the given form to the DLTN server. The update(s) may be sent / received in encrypted form over a secure connection.
[0118] Reference Figure 5b, the DLTN server receives (535) from the DLTN client an update(s) to metadata defining a given form. Based on the update(s) to the metadata defining the form, the DLTN server updates the metadata defining the form. The metadata defining the form is stored in the blockchain of the DLTN (e.g., associated with the identity of the user who owns the form). For example, the DLTN server adds the updated metadata of the form to a new block of the blockchain.
[0119] The DLTN server can manage multiple forms owned by a user. In this case, the DLTN server can retrieve a list of forms owned by the user, and information about the forms respectively, and then send the list of forms to the DLTN client, and information about the forms respectively. Such information can be sent / received via a secure connection. For a given form, the information about the form can include the title of the form, the count of the parts in the form, the count of the fields in the form, the permission status of the form, the count of the form instances created by the user, the count of the form instances requested from the user, the count of the form instances submitted by the user, and / or other information.
[0120] After receiving the list of forms and information about the forms from the DLTN server, the DLTN client may draw the list of forms, the information about the forms, and graphical controls for one or more actions for the forms, respectively, on the UI of the DLTN client. For example, the graphical controls for a given form include graphical controls for an action of viewing instance data of a given form instance, graphical controls for an action of assigning a given form, graphical controls for an action of editing a given form, and / or graphical controls for an action of archiving a given form. The DLTN client may receive user input from a user through the UI of the DLTN client, the user input indicating a selection of a given form for editing. The DLTN client may then send an indication of the selection to the DLTN server. The DLTN server may receive an indication of the selection of a form for editing from the DLTN client. In response, the DLTN server sends metadata defining the form for editing to the DLTN client, as described in reference to FIG. Figure 5a and 5b Alternatively, a user may assign a given form to another user in the DLTN for data entry. In this case, for the other user, the given form will appear in the list of forms to be completed by the other user.
[0121] Figure 6 An example method (600) for updating metadata defining a form in a DLTN is shown. The method includes referring to Figure 5a and 5b Some of the operations described in this document are as well as operations for user login, decryption, and encryption. Figure 6 In the illustrated example method (600), communications between the DLTN client and the DLTN server may use encrypted messages over a secure connection (e.g., an SSL connection) for the session. Metadata for the form may be stored in encrypted form using separate encryption keys that are specific to a given user (owner of the form) and managed by the encryption service.
[0122] To begin, in the login phase (610), the user who is the form owner initiates (611) the login process through the UI of the DLTN client. The DLTN client provides (612) the user's credentials to the DLTN server. The DLTN server authenticates (613, 614) the user using an authentication service, which, when successful, provides the DLTN server with a user authentication token. The DLTN server sends (615) a message to the DLTN client indicating that the authentication has been successful.
[0123] In the next stage (620), information about a given form is requested and presented to the user. Through the UI of the DLTN client, the user requests (621) metadata for a given form. The DLTN client sends (622) a request to the DLTN server, which retrieves (623, 624) metadata for the given form from the blockchain. The metadata may be retrieved in an encrypted form, in which case the DLTN server calls (625) a cryptographic service to decrypt the metadata. To decrypt the metadata, the cryptographic service uses one or more appropriate user-specific encryption keys for the user (form owner). The cryptographic service returns (626) the metadata in a decrypted form to the DLTN server, which sends (627) the decrypted metadata to the DLTN client. The DLTN client parses the metadata and presents (628) the given form through the UI of the DLTN client.
[0124] In the next stage (630), the user provides (631) user input through the UI of the DLTN client, which indicates one or more updates to a given form. The DLTN client sends (632) the updates to the DLTN server, and the DLTN server updates the metadata. If the updated metadata is stored in encrypted form, the DLTN server calls (633) the encryption service to encrypt the updated metadata, and the encryption service returns (634) the updated metadata in encrypted form. To encrypt the metadata, the encryption service uses one or more appropriate user-specific encryption keys for the user (form owner). The DLTN server stores (635) the updated metadata in the blockchain (e.g., in a new block of the blockchain).
[0125] D. Example of submitting form instance data.
[0126] Figure 7a A generalized technique for providing instance data for a form is shown from the perspective of a given user's DLTN client (701). Figure 7b A generalized technique for providing instance data for a form is shown from the perspective of a DLTN server (702).
[0127] Reference Figure 7b , the DLTN server retrieves (710) metadata defining the given form. The metadata defining the given form (e.g., associated with the identity of the owner of the given form) is stored in the blockchain of the DLTN. The DLTN server sends (715) the metadata defining the given form to the DLTN client. Figure 7a , the DLTN client receives (720) metadata defining a given form from the DLTN server. The metadata defining the given form may be sent / received in an encrypted form over a secure connection. The metadata may define various properties of the given form, such as a title for the given form, one or more sections of the given form, and one or more fields of the given form. For a given field, the metadata may define one or more attributes of the field, such as the type of the field (e.g., short text, multi-line text, drop-down menu, selection list, checkbox, slider, date / time picker, formula, or attachment), a title for the field, a default value for the field, a description of the field, an indication of whether validation is required for the field, an indication of whether the value of the field is required to be unique, and / or another attribute.
[0128] The DLTN client draws (725) a given form based on the metadata on the UI of the DLTN client. The DLTN client may include a form drawing engine (e.g., as part of a web browser) that is operable to parse the metadata defining the given form and perform drawing of the form. In addition to displaying information about the form (e.g., title, (multiple) sections, (multiple) fields, (multiple) attributes of (multiple) fields), the DLTN client also presents, through the UI of the DLTN client, graphical elements that are operable to complete the form fields. The graphical elements may include text boxes, drop-down menus, selection lists, check boxes, slider controls, and / or other controls to provide user input to the fields of the form.
[0129] The DLTN client receives (730) user input from a user through the UI of the DLTN client, the user input indicating instance data for an instance of a given form. For example, the user input provides values for one or more fields of a given form. The DLTN client sends (735) instance data for an instance of a given form to the DLTN server. The instance data may be sent / received in encrypted form over a secure connection.
[0130] The DLTN server receives (740) instance data for an instance of a given form from a user from a DLTN client. The DLTN server stores (745) the instance data for the instance of the given form in a blockchain together with metadata defining the given form. For example, the DLTN server stores the instance data for the instance of the given form in a blockchain together with the metadata defining the given form in association with the identity of the user providing the instance data. The DLTN server may add the instance data for the instance of the form to a new block of the blockchain. A copy of the metadata defining the form may be stored in the same block.
[0131] The DLTN server can manage multiple forms that can be completed by the user. In this case, the DLTN server can retrieve a list of forms that can be completed by the user, and information about the forms respectively, and then send the list of forms and information about the forms respectively to the DLTN client. Such information can be sent / received through a secure connection. For a given form, the information about the form can include the title of the form, the owner of the form, the submission status of the form for the user (submitter) (e.g., pending, submitted, reviewed and approved), and / or the completion status of the form for the user (submitter) (e.g., percentage completed, correction requested).
[0132] After receiving the list of forms and information about the forms from the DLTN server, the DLTN client can draw a list of forms that can be completed by the user, information about the forms respectively, and a graphic control for one or more actions of the forms respectively on the UI of the DLTN client. For example, the graphic control includes a graphic control for an action that provides instance data for an instance of the form. The DLTN client can receive user input from the user through the UI of the DLTN client, and the user input indicates the selection of a given form for data entry. The DLTN client can then send an indication of the selection to the DLTN server. The DLTN server can receive an indication of the selection of the form for data entry from the DLTN client. In response, the DLTN server sends metadata defining the form to the DLTN client for data entry.
[0133] Figure 8 An example method (800) for providing instance data for an instance of a form in a DLTN is shown. The method includes referring to Figure 7a and Figure 7b Some of the operations described in this document are as well as operations for user login, decryption, and encryption. Figure 8In the illustrated example method (800), communications between the DLTN client and the DLTN server may use encrypted messages over a secure connection (e.g., an SSL connection) for the session. Metadata for a form may be stored in encrypted form using separate encryption keys that are specific to the owner of the form and managed by an encryption service. Similarly, instance data for an instance of a form may be stored in encrypted form using separate encryption keys that are specific to the submitter of the instance data and managed by an encryption service.
[0134] To begin, in the login phase (810), the user who is the submitter of the form's instance data initiates (811) the login process through the UI of the DLTN client. The DLTN client provides (812) the user's credentials to the DLTN server. The DLTN server authenticates the user (813, 814) using an authentication service, which, when successful, provides the DLTN server with a user authentication token. The DLTN server sends (815) a message to the DLTN client indicating that the authentication has been successful.
[0135] In the next stage (820), metadata defining a given form is requested and presented to the user. Through the UI of the DLTN client, the user requests (821) metadata for a given form. The DLTN client sends (822) a request to the DLTN server, which retrieves (823, 824) metadata for the given form from the blockchain. The metadata may be retrieved in an encrypted form, in which case the DLTN server calls (825) a cryptographic service to decrypt the metadata. To decrypt the metadata, the cryptographic service uses one or more appropriate user-specific encryption keys for the form owner. The cryptographic service returns (826) the metadata in a decrypted form to the DLTN server, which sends (827) the decrypted metadata to the DLTN client. The DLTN client parses the metadata and presents (828) the given form through the UI of the DLTN client.
[0136] In the next stage (830), the user (submitter of the instance data) provides (831) user input through the UI of the DLTN client, which indicates data entry for one or more fields of a given form. The user input collectively provides instance data for the instance of the form. The DLTN client sends (832) the instance data for the instance to the DLTN server. If the instance data is stored in encrypted form, the DLTN server calls (833) an encryption service to encrypt the instance data, and the encryption service returns (834) the instance data in encrypted form. A copy of the metadata defining the form may be stored together with the instance data. To encrypt the instance data (and a copy of the metadata defining the form), the encryption service uses one or more appropriate user-specific encryption keys for the user (submitter of the instance data of the form). The DLTN server stores (835) the instance data (and a copy of the metadata defining the form) in the blockchain (e.g., in a new block of the blockchain).
[0137] E. Example of review and approval form.
[0138] Figure 9a A generalized technique for reviewing and approving a form instance in a DLTN is shown from the perspective of a given user's DLTN client as a reviewer of the form instance (901). Figure 9b A generalized technique for reviewing and approving an example of a form in a DLTN is shown from the perspective of a DLTN server (902). Figure 9a and 9b As shown, instances of a form can be reviewed and approved according to a workflow specified by the form owner.
[0139] The DLTN server retrieves (910) metadata defining a given form and instance data for an instance of the given form. The metadata and instance data for an instance of a given form (e.g., associated with the identity of the user submitting the instance data) are stored in the blockchain of the DLTN. The DLTN server sends (915) metadata and instance data for an instance of the form to the DLTN client. The metadata and instance data may be sent / received in encrypted form over a secure connection. The metadata may define various properties of a given form, such as a title of the form, one or more parts of the form, and one or more fields of the form. For a given field, the metadata may define one or more attributes of the field. The instance data may record user input for the field(s) of the form.
[0140] The DLTN client receives (920) metadata defining a form and instance data for an instance of the form from the DLTN server. Based on the metadata and the instance data for the instance of the form, the DLTN client draws (925) an instance of the form on the UI of the DLTN client. The DLTN client may include a form drawing engine (e.g., as part of a web browser) that is operable to parse the metadata and instance data defining a given form and then perform drawing of the instance of the form. In addition to displaying information about the form (e.g., title, (multiple) sections, (multiple) fields, (multiple) attributes of (multiple) fields) and instance data provided by the submitter of the form, the DLTN client presents, through the UI of the DLTN client, graphical elements that are operable to provide feedback on the instance of the form. The graphical elements may include text boxes, drop-down menus, selection lists, check boxes, slider controls, and / or other controls to provide feedback on the instance of the form.
[0141] The DLTN client receives (930) user input from a user (reviewer) through the UI of the DLTN client, which indicates feedback on an instance of a form. For example, the feedback can be an instance of approving a form or rejecting a form. Alternatively, the feedback can be a request to correct or supplement the information submitted in the instance data. The DLTN client sends (935) an indication of feedback on an instance of a given form to the DLTN server. The feedback can be sent / received in encrypted form over a secure connection.
[0142] The DLTN server receives (940) an indication of feedback on an instance of a given form from a DLTN client. Based on the indication of feedback on the instance of the given form, the DLTN server updates (945) the state of the instance of the given form. For example, the DLTN server stores the state information in a blockchain along with metadata and instance data defining the given form in association with the identity of the user (reviewer) providing the feedback. The DLTN server may add the state information to a new block of the blockchain. Copies of the metadata and instance data may be stored in the same block.
[0143] The DLTN server can manage multiple instances of forms ready for review by users (reviewers). In this case, the DLTN server can retrieve a list of form instances ready for review, and information about the instances respectively, and then send a list of form instances ready for review to the DLTN client, and information about the instances respectively. Such information can be sent / received via a secure connection. For a given instance of a form, information about the instance can include the title of the form, the user (submitter) associated with the instance of the form, the submission status of the form for the user (submitter) (e.g., pending, submitted, reviewed, and approved), the completion status of the form for the user (submitter) (e.g., percentage completed, requested correction), the history of the form instance (e.g., submission event of the form instance, correction request event of the form instance, and / or approval event of the form instance). Specifically, events in the history of the form instance can be recorded in a block in the blockchain to provide an immutable record of the form, the submitted instance of the form, and the status of the submitted instance at various stages.
[0144] After receiving a list of form instances and information about the instances from the DLTN server, the DLTN client may draw a list of instances ready for review, information about the instances, and one or more actions for the instances, respectively, on the UI of the DLTN client. For example, the graphical controls include graphical controls for actions for selecting an instance of a form for review. The DLTN client may receive user input from a user (reviewer) through the UI of the DLTN client, the user input indicating a selection of an instance of a form for review. The DLTN client may then send an indication of the selection to the DLTN server. The DLTN server may receive an indication of the selection of a form instance for review from the DLTN client. In response, the DLTN server sends metadata defining the form and instance data for the form instance, as described in reference to Figure 9a and 9b Descriptive.
[0145] Fig.10 An example method (1000) is shown for reviewing and approving an example form in a DLTN. The method includes referring to Figure 9a and 9b Some of the operations described in this document are as well as operations for user login, decryption, and encryption. Fig.10In the illustrated example method (1000), communications between a DLTN client and a DLTN server may use encrypted messages over a secure connection (e.g., an SSL connection) for the session. Metadata for a form may be stored in encrypted form using separate encryption keys that are specific to the owner of the form and managed by an encryption service. Similarly, instance data for an instance of a form may be stored in encrypted form using separate encryption keys that are specific to the submitter of the instance data and managed by an encryption service.
[0146] To begin, in the login phase (1010), a user who is a reviewer of the form instance initiates (1011) the login process through the UI of the DLTN client. The DLTN client provides (1012) the user's credentials to the DLTN server. The DLTN server authenticates the user (1013, 1014) using an authentication service, which, when successful, provides the DLTN server with a user authentication token. The DLTN server sends (1015) a message to the DLTN client indicating that the authentication has been successful.
[0147] In the next stage (1020), instance data for an instance of a given form is requested and presented to the user. Through the UI of the DLTN client, the user requests (1021) instance data for an instance of a form. The DLTN client sends (1022) a request to the DLTN server, which retrieves (1023, 1024) the instance data from the blockchain. (The DLTN server also retrieves the associated metadata of the form from the blockchain from the same block or a different block.) The instance data and metadata may be retrieved in encrypted form, in which case the DLTN server calls (1025) an encryption service to decrypt the instance data and metadata. To decrypt the instance data and metadata, the encryption service uses one or more appropriate user-specific encryption keys for the submitter of the instance data. (If the metadata is encrypted separately, it can be decrypted using one or more appropriate user-specific encryption keys for the owner of the form.) The encryption service returns (1026) the instance data (and metadata) in decrypted form to the DLTN server, which sends (1027) the instance data (and metadata) to the DLTN client. The DLTN client parses the instance data and metadata and presents (1028) an instance of the form through the UI of the DLTN client.
[0148] In the next stage (1030), the user (reviewer) provides (1031) user input through the UI of the DLTN client, which indicates feedback on the instance data of the form instance (e.g., approval, rejection, request for correction, etc.). The DLTN client sends (1032) feedback to the DLTN server, and the DLTN server determines the state information based on the feedback. If the state information is stored in an encrypted form, the DLTN server calls (1033) an encryption service to encrypt the state information, and the encryption service returns (1034) the state information in an encrypted form. A copy of the metadata defining the form and the instance data for the instance can be stored with the state information. To encrypt the state information (and the copy of the metadata / instance data), the encryption service uses one or more appropriate user-specific encryption keys for the user (reviewer of the form, and possibly submitter and / or owner). The DLTN server stores (1035) the state information (and the copy of the metadata / instance data) in the blockchain (e.g., in a new block of the blockchain).
[0149] F. Example screenshots.
[0150] Figures 11a to 11f is an illustration of example screenshots illustrating different features of managing metadata defining forms in a DLTN in some example implementations. Figures 11a to 11f , the screenshot shows a page drawn in a web browser (of a DLTN client), where the graphical elements are provided by a web application (of a DLTN server).
[0151] Fig.11a The screenshot (1100) in shows a list of forms on a page (1101) of the UI of the DLTN client after a user (Coffee Company) has logged in. The top row (1102) includes graphical controls (drop-down menus) that can be actuated to reach menus or pages that show identities associated with the user, available applications, forms (defined by the user, shared with the user, or archived by the user), the user's assets, requests from the user, and administrative settings. The top row (1102) also includes graphical indicators that indicate the language of the page (1101) and the logged in user. Below the top row (1102), the page (1101) includes a list of forms. A graphical control (a "Create Form" button) can be actuated to create a new form owned by the user. Tags can be selected to filter which forms are shown in the list—all forms, the user's own forms, forms shared with the user, or archived forms. In Fig.11a , the "All" tab is selected.
[0152] For each form shown in the list, the list entry includes the title of the form. The number of sections in the form, the number of fields in the form, the permission settings for the form (e.g., "Shared with all connections" or "Private"), status information for the form, and graphical controls that can be actuated to perform actions. The status information can indicate the number of form instances that have been created, the number of form instances that have been submitted, the number of times the form has been requested, or other information. The graphical controls can be actuated to edit the form ("Edit Form"), archive the form ("Archive"), assign the form to another user in the DLTN for data entry ("Assign Form"), view instance data for an instance of the form ("View Data Entry"), or take some other action. If the form is assigned to another user in the DLTN for data entry, then for that other user, the given form will appear in the list of forms to be completed by the other user (e.g., see Fig.11c ).
[0153] Fig.11b The screenshot (1110) in shows a particular form on a page (1111) of a UI of a DLTN client after a user (the coffee company) has actuated a graphical control to select the form for editing. The top row (1102) and Fig.11a Below the top row (1102), the page (1111) includes details about the selected form, which is titled "Family Questionnaire Form". The tabs can be selected to switch between editing the form's metadata ("Editor") and editing the form's permission settings ("Permission"). Fig.11b , the "Editor" tab is selected. Using the controls (1111) at the bottom of the page, the user can scroll the form, add or remove sections, add or remove fields, or change permission settings. For a field, the user can set properties such as a title for the field, a default value for the field, a description of the field, a JSON field name, a data type for the field (e.g., free text, short text, multi-line text, drop-down menu, country selector, check box, radio group, date / time selector, formula, or attachment), an indication of whether validation is required for the field, and an indication of whether the value of the field is required to be unique across submissions. Graphical controls are presented to save the updated metadata of the form or to cancel changes to the metadata of the form.
[0154] Fig.11cThe screenshot (1120) in shows a list of forms on a page (1121) of the UI of the DLTN client after a different user (Farmer Two) has logged in. The top row (1122) includes graphical controls (drop-down menus) that can be actuated to reach a menu or page that shows the identity associated with the user, available applications, forms, and the user's assets. The top row (1122) also includes graphical indicators that indicate the page (1121) language and the logged in user. Below the top row (1122), the page (1121) includes a list of forms. Tabs can be selected to filter which forms are shown in the list - all forms, forms to be completed by the user ("Pending"), forms previously submitted by the user ("Submitted"), forms submitted by the user that have been reviewed ("Reviewed"), or forms submitted by the user that have been approved ("Approved"). In Fig.11c , a "pending" tab is selected to show forms to be completed by the user. A search box can accept user input to search the list of forms. For each form shown in the list, the list entry includes the title, the owner of the form, when the form was created, and the completion status of the form (e.g., percentage completed or corrections requested). A form can be selected to provide data entry for the fields of the form.
[0155] Fig.11d The screenshot (1130) in shows a specific form on page (1131) of the UI of the DLTN client after the user (Farmer 2) has selected the form for data entry. Fig.11c The page (1131) is the same as the one shown. Below the top row (1122), the page includes details about the selected form, which is titled "Children's Questionnaire Form." The details include the title of the form and two sections, which are titled "Baseline Demographics Section" and "Counseling Services Section." Each section includes one or more fields for data entry. The page (1131) includes graphical controls that can be actuated to view existing data entries for the form, create new entries, or close the form. When the user provides data for the fields of the form and saves the form, an instance of the form is created.
[0156] Fig.11e The screenshot (1140) in shows a list of form instances on a page (1141) of the UI of the DLTN client after the user (coffee company) has logged in. The top row (1102) is connected to Fig.11aas shown. Below the top row (1102), the page (1141) includes a list of form instances. The forms shown are owned by the user, who is also responsible for reviewing the form instances. Tabs can be selected to filter which form instances are shown in the list - all form instances, form instances to be completed by other users ("Pending"), form instances previously submitted by other users ("Submitted"), form instances submitted by other users that have been reviewed ("Reviewed"), or form instances submitted by other users that have been approved ("Approved"). Fig.11c , the "All" tab is selected to show all instances of the form. A search box can accept user input to search a list of form instances. For each instance of a form shown in the list, the list entry includes the title of the form, the user who submitted the form instance, and when the form was assigned to or submitted by another user. The list entry also includes status information about the form instance (e.g., percentage completed or corrections requested if the form instance has not yet been submitted; approved or rejected if the form instance has been submitted and reviewed). An instance of a form can be selected to review the instance of the form.
[0157] Fig.11f The screenshot (1150) in shows a particular form instance on a page (1151) of the UI of the DLTN client after the user (the coffee company) has selected the form instance for review. Fig.11a The same as shown. Below the top row (1102), the page (1151) includes a history record for the selected form instance, which is titled "Measurement Form". The details include the title of the form, the data entry for the history record of the form, and the history record of events for the form instance. These events include when the form instance was first signed and submitted by the submitter (Farmer Two), when the reviewer (Coffee Company) requested a correction, when the submitter re-signed and resubmitted the form instance, and when the reviewer signed and approved the form instance.
[0158] The innovations described herein include, but are not limited to, the following:
[0159]
[0160]
[0161]
[0162]
[0163]
[0164]
[0165]
[0166]
[0167]
[0168]
[0169] The foregoing description discloses only examples. Modifications falling within the scope of the invention will be apparent to those of ordinary skill in the art. In view of the many possible examples to which the principles of the disclosed invention can be applied, it should be appreciated that the illustrated examples are only preferred examples of the invention and should not be considered to limit the scope of the invention. On the contrary, the scope of the invention is defined by the appended claims. Therefore, we claim all that falls within the scope and spirit of these claims as our invention.
Claims
1. A computer-readable medium having computer-executable instructions stored thereon, the computer-executable instructions being configured to cause a computer system implementing a distributed ledger trust network (DLTN) server, when programmed by the computer system, to perform operations to provide access to the DLTN, the operations comprising: sending metadata to a DLTN client, the metadata defining a given form, wherein the metadata defines one or more fields of the given form, and wherein the metadata further defines, for a given field among the one or more fields of the given form, one or more attributes of the given field of the given form, the one or more attributes including a type of the given field and a description of the given field; receiving, from the DLTN client, one or more updates to the metadata defining the given form; as well as Based on the one or more updates to the metadata defining the given form, the metadata defining the given form is updated, and the updated metadata defining the given form is stored in the blockchain of the DLTN.
2. The computer-readable medium of claim 1 , wherein the operations further comprise: Retrieve a list of forms owned by the user, and information about each of the forms, including the given form; as well as The list of forms and the information about each of the forms are sent to the DLTN client.
3. The computer-readable medium of claim 2, wherein the operations further comprise: An indication is received from the DLTN client that the given form is selected for editing, wherein the metadata defining the given form is sent in response to the selection of the given form for editing.
4. The computer-readable medium of claim 1 , wherein the metadata defining the given form includes default initial values, and wherein the one or more updates to the metadata defining the given form include: Adding a title to the given form; the addition of parts of said given form; Addition of new fields to a given form; and / or Adding new attributes to the given field of the given form, wherein the new attributes include one or more of the following: the title of the given field; a default value for the given field; an indication of whether validation is required for the given field; and An indication of whether the value of the given field is required to be unique.
5. The computer-readable medium of claim 1 , wherein the metadata defining the given form includes previously specified values, and wherein the one or more updates to the metadata defining the given form include: Adding or changing the title of said given form; the addition, modification or removal of parts of said given form; a change or removal of one of the one or more fields of the given form; A change or removal of one of the one or more attributes of the given field of the given form, wherein the one or more attributes further comprise one or more of the following: the title of the given field; a default value for the given field; an indication of whether validation is required for the given field; and An indication of whether the value of the given field is required to be unique.
6. The computer-readable medium of claim 1 , wherein the metadata defining the given form is stored in the blockchain in association with an identity of a user.
7. The computer-readable medium of claim 1 , wherein: The DLTN server includes a Web application and implements an application programming interface API accessible to the DLTN client; and The DLTN client is implemented as a separate executable application, as client-side script logic executed in a web browser environment, or as a set of functions of a web browser to control the client-oriented script logic executed by the DLTN server.
8. The computer-readable medium of claim 1 , wherein the operations further comprise: Receipt of voucher; verifying the credentials; as well as An authentication token is sent to the DLTN client.
9. The computer-readable medium of claim 1, wherein the type of the given field is selected from the group consisting of short text, multi-line text, drop-down menu, selection list, checkbox, slider, date / time picker, formula, or attachment.
10. The computer-readable medium of claim 1, wherein the operations further comprise: calling an encryption service to decrypt the metadata defining the given form, wherein the decrypted metadata is sent to the DLTN client; as well as The encryption service is called to encrypt the metadata defining an update to the given form, wherein the encrypted updated metadata is stored in the blockchain.
11. A computer system comprising a memory and one or more processing units, wherein the computer system implements a distributed ledger trust network (DLTN) server, the distributed ledger trust network server being configured to perform operations comprising: Retrieving metadata defining a given form, the metadata defining the given form being stored in a blockchain of the DLTN, wherein the metadata defines fields of the given form as a custom form; sending the metadata defining the given form to a DLTN client; receiving, from the DLTN client, instance data from a user, the instance data being for an instance of the given form, the instance data being different from the metadata defining the given form, wherein the instance data includes values for the fields of the given form provided by data entry; as well as The instance data for the instance of the given form is stored in the blockchain along with the metadata defining the given form.
12. The computer system of claim 11, wherein the operations further comprise: retrieving a list of forms available for completion by the user, and information about each of the forms, the forms including the given form; as well as The list of forms and the information about each of the forms are sent to the DLTN client.
13. The computer system of claim 12, wherein the operations further comprise: An indication of selection of the given form by the user for data entry is received from the DLTN client, wherein the metadata defining the given form is sent in response to the selection of the given form for data entry.
14. The computer system of claim 12, wherein for the given form, the information about the form comprises one or more of the following: the title of the given form; the owner of the given form; a submission status of the given form, wherein the submission status of the given form is selected from the group consisting of pending, submitted, reviewed, and approved; and A completion status of the given form, wherein the completion status of the given form is selected from the group consisting of a percentage completed and corrections requested.
15. The computer system of claim 11, wherein: The metadata defining the given form is stored in the blockchain in association with the identity of the owner of the given form; and The instance data for the instance of the given form is stored in the blockchain in association with the identity of the user, along with the metadata defining the given form.
16. The computer system of claim 11, wherein: The DLTN server includes a Web application and implements an application programming interface API accessible to the DLTN client; and The DLTN client is implemented as a separate executable application, as client-side script logic executed in a web browser environment, or as a set of functions of a web browser to control the client-oriented script logic executed by the DLTN server.
17. The computer system of claim 11 , wherein the metadata further defines properties of the given form and rules that check consistency of data in the given form and / or which of the fields in the given form are active, and wherein the metadata further defines one or more of: the title of the given form; one or more parts of the given form; and For each of the fields of the given form, one or more attributes of the field, the one or more attributes including a type of the field and a description of the field.
18. The computer system of claim 11, wherein the operations further comprise: calling an encryption service to decrypt the metadata defining the given form, wherein the decrypted metadata is sent to the DLTN client; as well as The encryption service is called to encrypt the metadata defining an update to the given form, wherein the encrypted updated metadata is stored in the blockchain.
19. The computer system of claim 11, wherein the operations further comprise: checking permissions for the given form; as well as Permissions are set for the instance of the given form, wherein the permissions for the given form are different from the permissions for the instance of the given form.
20. A method in a computer system implementing a distributed ledger trust network (DLTN) server, the distributed ledger trust network server being configured to provide access to the DLTN, the method comprising: retrieving metadata defining a given form and instance data for an instance of the given form, the metadata defining the given form and the instance data for the instance of the given form being stored in a blockchain of the DLTN, the instance data being different from the metadata defining the given form, wherein the metadata defines fields of the given form as a custom form, and wherein the instance data includes values for the fields of the given form provided by data entry; sending the metadata defining the given form and the instance data for the instance of the given form to a DLTN client; receiving an indication of feedback for said instance of said given form from said DLTN client; and Based on the indication of the feedback on the instance of the given form, a state of the instance of the given form is updated.
21. The method according to claim 20, further comprising: Retrieving a list of instances of forms prepared for review, including the given form, and information about each of the instances; as well as The list of instances of forms prepared for review and the information about the respective instances are sent to the DLTN client.
22. The method according to claim 21, further comprising: An indication of a selection of the instance of the given form for review is received from the DLTN client, wherein the metadata defining the given form and the instance data for the instance of the given form are sent in response to the selection of the instance of the given form for review.
23. The method of claim 20, wherein the feedback is selected from the group consisting of approval, rejection, and requested correction.
24. The method of claim 20, wherein: The metadata defining the given form and the instance data for the instance of the given form are stored in the blockchain in association with an identity of a user.
25. The method of claim 20, further comprising: Receipt of voucher; verifying the credentials; as well as An authentication token is sent to the DLTN client.
26. The method of claim 20, wherein the metadata further defines properties of the given form, and rules that check consistency of data in the given form and / or which of the fields in the given form are active, and wherein the metadata further defines one or more of: the title of the given form; one or more parts of the given form; and For each of the fields of the given form, one or more attributes of the field, the one or more attributes including a type of the field and a description of the field.
27. The method of claim 20, wherein the operations further comprise: calling an encryption service to decrypt the metadata defining the given form, wherein the decrypted metadata is sent to the DLTN client; calling the encryption service to decrypt the instance data for the instance of the given form, wherein the decrypted instance data is sent to the DLTN client; as well as The encryption service is called to encrypt state information, wherein the encrypted state information is stored in the blockchain.
28. The method of claim 20, wherein the operations further comprise: checking permissions for said instance of said given form; as well as Permissions are set for the state information, wherein the permissions for the instance of the given form are different from the permissions for the state information.
