RU2784208C1 - Distributed database system and implementation method - Google Patents

Abstract

FIELD: computer technology.

SUBSTANCE: present invention relates to the field of computer technology. The effect is achieved due to the fact that the computing device (CD) sends by means of a server with a messaging system and a server with a server disk to another CD a part of an instance of a distributed database (DB) intended for editing and/or coordination, and also receives from another CD instance of a distributed (DB), record of a synchronization event, record of previous synchronization events with other CDs, order of synchronization events, value for a parameter, while the first CD contains a part of a distributed instance (DB) configured to be transferred to a plurality of CDs of the system, which are implemented by distributed networks (DB). Each of the CDs is configured to detect the receipt of a message from other CDs and, in the absence of permission to exchange messages, request permission to exchange data with the CD having a unique ID of the CD account from which the message came, and if such permission is available, to automatically extract from a link message that automatically adds a new instance to the (DB) of the second or subsequent CDs.

EFFECT: increasing the stability of a hardware failure in a distributed database (DB).

10 cl, 5 dwg

Description

The invention relates to the field of computer technology and is intended to implement data transfer within a networked group of computing devices, as well as data exchange between different such groups of computing devices.

In the prior art, a method for working with a distributed database is known, comprising the steps in which the front-end server receives a database service request, and the database service request is divided into a write operation and a read operation; the interface server sends the write operation to the pre-designated global database server for execution, and the global database server sends the execution result to all other distributed database servers in chain mode; and the interface server selects one distributed database server and sends a read operation to the selected distributed database server for execution (patent CN108241641 A 07/03/2018).

A device for implementing a distributed database is also known from the prior art, comprising: a memory of the first computing device containing a part of the distributed database instance on the first computing device adapted for inclusion in a plurality of computing devices that are implemented via a network operatively connected to a plurality of computing devices, a distributed database that contains a first entry in logical association with a first public key associated with the first computing device; and a processor of the first computing device operatively connected to the memory, wherein the processor is adapted to: receive from the second computing device of the plurality of computing devices the first public key associated with the second computing device and encrypted with the first public key associated with the first computing device, and being in a logical connection with the second record of the distributed database; decrypting, on the first computing device, the first public key associated with the second computing device with the private key paired with the first public key associated with the first computing device; sending to the second computing device a second public key associated with the first computing device, in logical connection with the third distributed database entry and encrypted with the second public key, associated with the second computing device and in logical connection with the fourth distributed database entry; determining a transmission command by performing a lexicographic comparison between the second public key associated with the first computing device and the first public key associated with the second computing device; and sending a signal to insert into the distributed database a transfer command adapted to transfer a value from each source entry of the plurality of source entries, including the first entry and the fourth entry, to another target entry of the plurality of target entries, including the second entry and the third entry, wherein the transmission command is signed with a private key and adapted to be executed in such a way as to hide the identifier of the computing device associated with each target record from the set of target records among the set of computing devices containing the first computing device and the second computing device (patent RU 2746446 C2 14.04. 2021).

The disadvantage of the known solution is that the existing systems known from the prior art are organized as a server, which is accessed through a web interface (website), which stores all documents of all users. And in accordance with the rights, when users interact, access to files of other users is given. That is, existing systems use conventional client-server technology. This type of system is unreliable due to the fact that the inoperability of the server can make the entire computer network inoperable. At the same time, an inoperable server should be considered a server whose performance is not enough to serve all clients, as well as a server that is under repair, maintenance, under attack (for example, a DDos attack), etc.

The technical problem of the claimed group of inventions is to solve the problem of creating a distributed database system that implements client-client technology.

The technical result consists in providing the possibility of implementing a distributed database system and a method for transferring elements of this database from one participant in such a system to another.

The specified technical result is achieved in a distributed database system containing a plurality of computing devices interconnected via a network, as well as a server with a messaging system and a server with a server disk, functionally connected to each computing device of a plurality of computing devices, each of which contains a memory, a processor and an output device, wherein the memory of each computing device of a plurality of computing devices of the system stores instructions that lead to the execution by the processor of functions associated with sending, via a server with a messaging system and a server with a server disk, to another computing device included in the plurality of computing devices of a part of a distributed base instance data intended for editing and/or reconciliation, as well as receiving from another computing device an instance of a distributed database included in a plurality of computing devices, recording an event synchronization, a record of previous synchronization events with other computing devices, an order of synchronization events, a value for a parameter, wherein the memory of the first computing device contains at least a part of a distributed database instance configured to be transferred to a plurality of computing devices of the system, which are implemented via a network operatively connected with a plurality of computing devices of the system, a distributed database, each of the computing devices of the plurality of computing devices of the system is configured to detect the receipt of a message from other computing devices of the plurality of computing devices of the system, and, in the absence of permission to exchange messages, request permission to exchange data with the computing device, having a unique identifier of the account of the computing device from which the message was received, and, if such permission is available, in the automated mode of separation from the message communication of a link by which a new instance is automatically added to the database of the second or subsequent computing devices of a plurality of computing devices of the system.

The computing device includes an audio output device and/or a tactile output device.

The memory of the computing device is a random access memory RAM, a memory buffer, a hard disk, a database, an erasable programmable read-only memory EPROM, an electrically erasable programmable read-only memory EEPROM, a read-only memory ROM.

Values for a parameter are database fields that quantify the transaction, database fields that quantify the order in which events occur, and/or a field for which a value can be stored in the database.

Additionally contains a second set of computing devices, which is configured to interact with the first set of computing devices by receiving and transmitting distributed database instances through the assigned computing devices of the first and second sets of computing devices of the system.

The unique identifier of a computing device account is an email address, a phone number of a messenger account, a social network account identifier, an ecosystem identifier (for example, Sber ID, Yandex Passport, etc.), as well as an identifier of any system that provides authorization to a third party with limited access to protected user resources without passing her (third party) login and password (an example of OAuth2 is just any ecosystem can provide such authentication).

The computing device is a personal computing device, desktop computer, laptop computer, mobile phone, personal digital assistant PDA.

The specified technical result is also achieved in a method for implementing a distributed database by means of a distributed database system, including the steps at which: a group is created containing a plurality of computing devices of the distributed database system, for which a part of a distributed database instance containing a link is sent from the first computing device for joining a group of computing devices included in a plurality of computing devices of the distributed database system, wherein the formed part of the distributed database instance is stored on the first computing device; for each document that is part of a distributed database instance on the first computing device, a route is specified with a list of unique identifiers of the group's computing device account, as well as the rights to edit and/or approve the sent part of the distributed database instance for each of the specified computing devices of the group, upon completion work with a part of the distributed database instance on the current computing device, the specified part of the instance is sent to the next computing device specified in the route, and also simultaneously sent to previous computing devices, to form a complete instance of the distributed database and track actions on the specified document, while all parts of the distributed database instance are stored in the memory of each computing device specified in the route.

In this case, each of the plurality of computing devices in the group is configured to add other computing devices to the group, if they have the appropriate rights, by sending an invitation to the unique identifiers of the computing device account as part of a distributed database instance.

At the same time, one computing device is assigned from the set of computing devices of the group, interacting with another computing device of the second set of computing devices of another group, also previously assigned for interaction.

The claimed group of inventions is illustrated on graphic materials, where

1 is a block diagram of a distributed database system illustrating a distributed database system according to an embodiment with one user group of four users and four computing devices as an example.

Fig.2 - structural scheme for creating and sending an instance of a distributed database on the example of a messaging server in the form of a mail server (e-mail)

Fig.3 - block diagram of the creation of a group of five people

Fig.4 - block diagram of the organization's internal workflow

Fig.5 - block diagram of sending a document to a counterparty

A distinctive feature of the claimed group of inventions is the storage of documents of each user of the system on his own computing device. When transmitting data, a message transmission server and a temporary data storage server with a personal or corporate user account are used, and a document received from another user is also stored on the recipient's user's computing device. That is, the claimed system implements client-client technology.

This makes it possible not to use huge servers with large constantly replenished data arrays, and nevertheless ensure that documents are received by all participants in the workflow. In this case, if necessary, the storage of the user's documents is possible on his personal server, or the server of the group, and not on the user's computing device, but this will be ensured after receiving a database instance on the user's computing device and subsequent redirection to storage on the server, which is an additional function to the current scheme of work.

When sending, an instance of a distributed database will also be taken from a personal server or a group server, moved to the user's computing device and then sent to another user, but the main point of sending client-client documents is preserved.

It should also be noted that the number of devices in one or different groups of a distributed database system can be unlimited, the number of such groups can be unlimited.

This distributed database system and the method of transferring its elements can be convenient, in particular, for electronic document management, including using a digital signature of document management participants. In this case, in the case of using an electronic signature, the private key is stored on the computing device or a separate storage medium of the user, and the public key is transmitted as part of a distributed database element using software.

In some embodiments, the device comprises at least a portion of a first distributed database instance on a first computing device adapted to be included in a group of computing devices that implement a distributed database via a network operably connected to the group of computing devices.

The processor is configured to receive a database instance from any network device. The transfer of data from one computing device to the second is carried out due to the fact that the user of the first device knows the unique identifier of the account of the messaging system of the user of the other device. The unique identifier of a messaging account can be, for example, an email address, a phone number of a messenger account, an identifier of a social network account, etc. Thus, using the software, on the basis of each other's known identifier, users can form user groups for data exchange and distributed database storage.

The current instance of a distributed database for exchange is the last instance of the chain, for example, one document that is available to the user for editing. All previous instances in such chains are readable by the software, even if the user is the current editor of the last instance of the chain. Different groups of users can share current distributed database instances with other groups. To do this, it is enough to know the unique identifier of the messaging system account of at least one user from another group and send him an invitation. Thus, the user of the second group using the software will be able to accept the invitation and learn from the message received in the invitation the ID of the member of the first group. In the future, the user of the second group can send instances of the distributed database to the user of the first group.

It should be noted that each device of one group must have access to the server with the messaging system and the server with the server disk of each user of this group. This ensures that a message is received and a file with a distributed database instance is downloaded for each user in the group.

It should be noted that the software can handle failed attempts to send messages and upload an instance to a server drive. These attempts are repeated at a specified interval until a successful result, which also guarantees the receipt of a distributed database instance, which means the stability of the entire system.

Devices from different groups can be on different networks. But the server with the messaging system and the server with the server disk of the contact user from another group must be accessible to the contact user of the first group. Conversely, the server with the messaging system and the server with the server disk of the former must be known to the latter. For example, one group may be on the local network of an organization, the second on the local network of another organization, but the contact persons of both persons have Internet access. At the same time, contact persons have two messaging system accounts and a server with a server disk, one messaging system account and one account with a server disk for internal transfer of a distributed database instance located in the local network of the current organization, a second messaging system account and a second account with a server drive on the Internet to send to a contact in another group.

The database can be stored on the user's local computer, for example, using a compact embedded SQLite DBMS.

SQLite is a compact, embedded DBMS. The source code of the library has been released into the public domain. The word "embedded" means that SQLite does not use the client-server paradigm, that is, the SQLite engine is not a separate running process with which the program interacts, but is a library with which the program is linked, and the engine becomes an integral part of the program. Thus, function calls (API) of the SQLite library are used as the exchange protocol. This approach reduces overhead, response time and simplifies the program. SQLite stores the entire database (including definitions, tables, indexes, and data) in a single standard file on the machine where the program is running. Ease of implementation is achieved due to the fact that before the start of the execution of the write transaction, the entire file that stores the database is blocked; ACID functions are achieved, among other things, by creating a log file.

API (application programming interface) is a set of ready-made classes, functions, procedures, structures and constants. All of this information is provided by the application itself (or the operating system). At the same time, the user does not have to understand that this API technology ensures the interaction of modules. The purpose of the information provided is to use this data when interacting with external programs. The APIs of various products are used by programmers to create applications that will interact with each other. In general, this mechanism is used to combine the work of various applications into a single system. This is quite convenient for performers. Indeed, in this case, another application can be treated as a “black box”. At the same time, its internal mechanism does not matter - a programmer may not know at all what an API is.

Creating and Sending a Distributed Database Instance

Let's consider sending a single message within a group using the Internet connection as an example (creating, sending, receiving, sending confirmation). The algorithm for this function looks like this:

1 - Is there permission to receive data from this sender?

2 - Create permission to receive data from this sender?

3 - Is the user of this (second) computing device included in the group specified in the received message?

4 - Create a group received in the message and become a member?

5 - Is there a chain according to the chain identifier in the received element of the distributed database?

6 - The element is added to the chain and becomes the last one in it.

7 - A new chain is created with the first element received from the sender.

Knowing the user ID of the second computing device, the first computing device using software creates a new element of the distributed database, which is formed as a separate SQLite file on the user's computing device, the file, in turn, may, but not necessarily, contain links to an unlimited number of files on network drive, and uploads to your network drive (Yandex Drive, Google Drive, etc.). Such a file is uploaded to the server with a server disk using the server functions API. Such API functions are standard for such servers, which is very convenient for other systems to interact with such servers.

After calling the following API function, a unique confidential link to download a file from this server is generated on the network drive and returned to the first computing device in response to this API function call.

This link, as well as user and group data in a certain format, is transmitted by the first computing device as a message to a unique account of the second computing device (this can be sending an e-mail using the SMTP protocol, a message to a messenger or social network through the API functions of the messenger server, or social network).

The second computing device, upon pressing a button or upon reaching a certain time interval on the timer (automatic mode), checks on its account with a unique identifier for the presence of received messages in a certain format.

In the case of e-mail, this is a selection of letters (messages) by subject and date using the IMAP or POP3 protocol. In the case of a messenger or a social network, this is a check of all dialogues with other users for unread letters and a selection of them, according to predefined keywords, through API functions. It is possible to implement a case with a dedicated messaging server specially created for the purpose of document flow, in which case the database of such a server will be checked by keywords or identifiers.

Upon detecting the receipt of a given message, the second computing device, in the absence of permission to exchange messages with the sender user, requests the permission of the user of the second computing device to exchange data with another device having a unique identifier of the first user from which the message came.

If permission is available, then the second device, using the software and knowing the message format, since the software instance that sends and receives messages in this way is identical on all computing devices of all user groups, pulls out a link from the message and using the link received from the message using The software downloads the distributed SQLite database file over HTTPS and, according to the device group ID from the message, adds a new instance to the second user's database.

If there is no information about the device group from the message, the user is prompted to join the group.

Further, if an existing data chain is found that precedes this instance in this group of devices, a new instance is added to the existing chain, otherwise a new one is created. This is implemented by specifying in each instance of the distributed database of the document the identifier of the parent chain and, accordingly, determining whether it belongs to this chain, or the novelty of the database instance.

If the distributed database instance received via the link contained other links to a network drive, then these files are also downloaded via the HTTPS protocol using the software as attachments to this distributed database instance. Thus, a database element is transferred from one device to another, and the acceptance of a new element of a distributed database can be automatic thanks to software with an implemented timer, upon reaching the interval of which new mail, messenger or social network messages are checked, messages are processed and files are downloaded above, and the creation, editing and sending of an instance is carried out either by the user of the computing device by filling out or editing data forms and pressing control buttons, or by software under specified conditions.

After accepting a new element of the distributed database, the second computing device sends to the account with the unique identifier of the first user a message confirming the download from the link of the file with the element of the distributed database.

Such a message in a certain format will have the same download link that the first user sent, but instead of downloading from the link on the first computing device, the link is identified in the log of sent and received messages.

When identified, the message is marked as received by the other side. This will confirm the download of the file by another user. After the first computing device receives such confirmation with the help of the software, the transfer of the distributed database instance is considered completed and the first computing device deletes the file with the link from the network drive via the API function to free up resources for temporary storage of other transferred elements of the distributed database.

If the first computing device sends an element of a distributed database to several computing devices on accounts with unique identifiers of their users, the sender's computing device deletes the file on the network drive after receiving confirmation from all computing devices to which the first device sent a link to this instance. This is tracked through a log of sent and received messages using the software.

Each recipient computing device, after adding to existing or creating a new chain of a distributed database, with the help of software gives the user of the computing device access to a database instance. This takes into account the fact that each element of the distributed database contains a unique identifier of the user account to which it currently belongs - the editor.

Thus, using the software, an element of a distributed database is accessed in the read format, if the element belongs to another participant, or in the editing format, if the element belongs to this participant.

A user who has created a distributed database item and has not yet sent that item to another user has edit access. At the same time, only the current editor can send a distributed database instance.

On submission, the current sender's computing device copies the current instance, changes the editor on the copy, and sends the new instance to the assigned editor. The user who received this distributed database instance is the current editor of the instance and has edit access. The original of the copied instance becomes available to the sender on his computer for reading, since it is not the last one in the chain. A copy of the instance with the new editor also remains with the sender, it becomes the last element of the chain. The end element is readable by the sender on his computer, since he is no longer an editor. Thus, it is possible to bypass the document through the list of users knowing their unique identifier of the message server account. Such identifiers (for example, e-mail) are known to all members of the group about each member of this group. And each current recipient of the instance will be an editor, which means it will be able to send a distributed database instance further.

In FIG. 1 illustrates a distributed database 100 implemented on four computing devices (computing device 110, computing device 120, computing device 130, and computing device 140), but it should be understood that distributed database 100 may use a set of any number of computing devices containing computing devices not shown in Fig. one.

Also, the Network 105 may contain any number of mail servers and server drives. Network 105 may be any type of network (eg, local area network (LAN), wide area network (WAN), virtual network, telecommunications network) implemented as a wired network and/or wireless network and used to functionally interconnect computing devices 110 , 120, 130, 140. As described in more detail herein, in some embodiments, for example, the computing devices are personal computers connected to each other via an Internet Service Provider (ISP) and the Internet (eg, networks 105).

In some embodiments, a connection may be established via network 105 between any two computing devices 110, 120, 130, 140. As shown in FIG. 1, for example, a connection may be established between computing device 110 and any of computing device 120, computing device 130, or computing device 140.

In some embodiments, computing devices 110, 120, 130, 140 may communicate with each other (e.g., send data to and/or receive data) and with the network via intermediate networks and/or alternate networks (not shown in FIG. 1) .

Such intermediate networks and/or alternative networks may be of the same type and/or a different type of network compared to network 105.

Each computing device 110, 120, 130, 140 may be any type of device adapted to send data over network 105 to send and/or receive data from one or more other computing devices. Examples of computing devices are shown in FIG. one.

The computing device 110 includes a memory 112, a processor 111, and an output device 113. The memory 112 may be, for example, random access memory (RAM), memory buffer, hard drive, database, erasable programmable read only memory (EPROM), electrically erasable program read only memory (EEPROM), read only memory (ROM), and /or so on. In some embodiments, memory 112 of computing device 110 contains data associated with a distributed database instance (eg, distributed database instance 114). In some embodiments, memory 112 stores instructions that cause the processor to execute modules, processes, and/or functions associated with sending and/or receiving from another computing device an instance of a distributed database (e.g., distributed database instance 124 on computing device 120) recording a synchronization event, recording previous synchronization events with other computing devices (by exchanging instances of a distributed database with both subsequent computing device and previous computing devices), the order of synchronization events, by forming a separate transaction log on each computing device distributed database (this log is stored on each computing device and is not transmitted), values for the parameter (for example, database fields that quantify the transaction, database fields that quantify o characterizing the order in which events occur and/or any other suitable field for which a value can be stored in the database).

The distributed database instance 114 may, for example, be adapted to perform data operations, including storing, modifying, and/or deleting data. In some embodiments, distributed database instance 114 may be a relational database, an object database, a per-relational database, and/or any other suitable type of database. For example, distributed database instance 114 may store data related to any particular function and/or area. For example, distributed database instance 114 may store documents (eg, of a user of computing device 110), including a value and/or vector of values related to the ownership history of a particular document.

In general, a vector can be any set of values for a parameter, and a parameter can be any data object and/or database field that can take on different values. Thus, distributed database instance 114 may have a number of parameters and/or fields, each of which is associated with a vector of values. The value vector is used to determine the actual value for the parameter and/or field in this instance 114 of the database.

Processor 111 of computing device 110 may be any suitable processing device adapted to start and/or execute distributed database instance 114.

For example, processor 111 may be adapted to update distributed database instance 114 in response to receiving a signal from computing device 120 and/or causing a signal to be sent to computing device 120.

In embodiments, processor 111 may be adapted to execute modules, functions, and/or processes to update distributed database instance 114 in response to receiving a value for a parameter stored in another distributed database instance (e.g., distributed database instance 124 on a computing device). 120) and/or causing a value for a parameter stored in the distributed database instance 114 on the computing device 110 to be sent to the computing device 120.

In some embodiments, processor 111 may be a general purpose processor, an application specific integrated circuit (ASIC), a digital signal processor (DSP), and/or the like. The display 113 may be any suitable display such as, for example, a liquid crystal display (LCD), a cathode ray tube (CRT) display, or the like.

In other embodiments, any of the computing devices 110, 120, 130, 140 comprise another output device in place of or in addition to the displays 113, 123, 133, 143.

For example, any of the computing devices 110, 120, 130, 140 may include an audio output device (eg, a speaker), a tactile output device, and/or the like. In still other embodiments, any of the computing devices 110, 120, 130, 140 includes an input device instead of or in addition to the displays 113, 123, 133, 143. For example, any of the computing devices 110, 120, 130, 140 may include a keyboard, mouse, and/or the like.

Computing device 120 has a processor 121, memory 122, and display 123, which may be structurally and/or functionally similar to processor 111, memory 112, and display 113, respectively. Also, distributed database instance 124 may be structurally and/or functionally similar to distributed database instance 114. Computing device 130 has a processor 131, memory 132, and display 133, which may be structurally and/or functionally similar to processor 111, memory 112, and display 113, respectively.

Also, distributed database instance 134 may be structurally and/or functionally similar to distributed database instance 114. Computing device 140 has a processor 141, memory 142, and display 143, which may be structurally and/or functionally similar to processor 111, memory 112, and display 113, respectively.

Also, distributed database instance 144 may be structurally and/or functionally similar to distributed database instance 114. Although the computing devices 110, 120, 130, 140 are shown as similar to each other, each computing device of the distributed database system 100 may be different from other computing devices. Each computing device 110, 120, 130, 140 of the distributed database system 100 may be any of, for example, a computing element (e.g., a personal computing device such as a desktop computer, laptop computer, etc.), a mobile phone, a handheld personal computer (PDA), etc.

For example, computing device 110 may be a desktop computer, computing device 120 may be a smartphone, and computing device 130 may be a server. In some embodiments, one or more portions of computing devices 110, 120, 130, 140 may include a hardware module (e.g., a digital signal processor (DSP)), and/or a software module (e.g., a computer code module stored in memory and/or executed by the processor).

In some embodiments, one or more functions associated with computing devices 110, 120, 130, 140 (eg, functions associated with processors 111, 121, 131, 141) may be included in one or more modules. Properties of distributed database system 100, including properties of computing devices (eg, computing devices 110, 120, 130, 140), number of computing devices, and network 105 may be selected in any manner.

In distributed database system 100, one computing device is the leader and it creates a group of users. For example, it can be the founder or director of the organization. When he creates a new member by specifying his unique account ID, an invitation is sent to the new member, which contains data about the entire user group. When a new member is created, he can be assigned the rights to create new group users. For example, it could be the head of the human resources department. Thus, not only the leader can add new users to the group, but also any number of users assigned to this. The computing device of each user checks the rights to create a new member of the group. And if there are no such rights, then the functionality of creating a new software participant is blocked or read-only. When a designated user adds a new member, the new member's information is sent as a distributed database instance to all other members of the group. Thus, each member of the group has correct information about all members of the group.

When a new group member is created, they can be assigned rights to create documents. If there are no such rights in this group, then you can only send documents received from other users, the user himself cannot create a new one. This distribution of rights is achieved by software.

Consider an example when a new group of five people is created (figure 3). It may be a small organization. Founder or Entrepreneur Pavlov creates an organization and user Pavlov, who has a unique messaging server account ID.

Pavlov has every right to any action in this organization. It is marked as the creator of the group in the distributed database instance.

Using the software, he can create and edit new team members. Pavlov creates Ivanov, who is his employee, enters in the creation form his unique message server identifier, such as email, and does not give him additional rights in the group.

Ivanov is sent an invitation from Pavlov's computing device to join the group, it is sent as a distributed database instance with a link. When accepting the invitation, Ivanov's computing device downloads the file from the link and adds data about the new group and all its members to its database on the computing device.

Ivanov's computing device will have information about the group, user Pavlov and user Ivanov, and all this with read access only. Pavlov has everything the same, but with edit access, since he has the rights to edit the group and create and edit users in this group.

Pavlov creates the user Petrov, who is also his employee, also without additional rights in the group. Petrov accepts the invitation and read-only information about the group and users Pavlov, Ivanov, Petrov appears on his computing device. Pavlov's computing device sends to Ivanov's computing device an instance of a distributed database with data about the new user Petrov, as this is done for all members of the group.

Thus, Ivanov's computing device also has data about the group and users Ivanov, Petrov, Pavlov and, using software, provides read-only access to Ivanov. Pavlov, on the other hand, has access to the group and users Pavlov, Ivanov, Petrov for editing. Pavlov creates the user Sidorov, who is also his employee. But he gives Sidorov the rights in the group to create and edit new users in the group. Sidorov accepts the invitation. Ivanov and Petrov are sent data on Sidorov, including his rights in the group. Ivanov and Petrov have data on the group and users Ivanov, Petrov, Sidorov and Pavlov, and read-only.

Sidorov and Pavlov have access to data on the group and users Ivanov, Petrov, Sidorov for editing and data about the user Pavlov for reading, since he is the creator of the group.

Sidorov, for example, is the head of the personnel department and then he creates users of the system. He creates a new user, Sinitsyna, who is Ivanov's employee. It does not assign additional rights. Sinitsyna accepts the invitation. Ivanov, Petrov and Pavlov are sent a copy of the distributed database with information on Sinitsyna. Everyone has information about the group, as well as users Ivanov, Petrov, Sidorov, Pavlov, Sinitsyn.

Ivanov, Petrov and Sinitsyna have read-only information. Sidorov and Pavlov for editing. Sidorov cannot edit only Pavlov. It should be noted that when information about the creation of a new employee is received, the software checks whether the user of the sender of this message has the rights to create a new user, and only if such rights exist in the group, a new user is added to the recipient's computing device.

It should be noted that after the time specified in the settings has elapsed and there is no confirmation from the user, the sender's computing device, using software, repeats sending the message with a distributed database instance. For example, the letter was lost and did not reach the recipient, a new letter is sent and this is repeated at specified intervals. Thus, the distributed database system ensures the reliability of data transfer between users' computing devices. The sending of such repeated messages can be canceled by the user of the sender's computing device.

Internal document flow of the organization

Consider the system using the example of a group of four users who coordinate a document within one organization (Fig. 4).

Each user knows the unique ID of each message server account. This is achieved by creating a group and adding new members to it as described above. Each document is assigned a route with a list of users from this group, through which this document is transmitted when the current user completes work with it by reassigning the current editor and sending it in the manner described above. Consider a list of four users: Ivanov, Petrov, Sidorov, Pavlov. Ivanov creates a document and fills in the route with other users of the group, and also sets whether one of the users can replace one with another in the list of users to bypass the document.

Any user can add a new user to the bypass list, the new user will be from the same group. When Ivanov finishes work and sends the document, a second copy of the chain of this document (block) is created, which is transferred to Petrov.

Petrov becomes the current editor of the document, the second block becomes the last block in the chain, the previous block becomes read-only for Ivanov. The second block is also read-only by Ivanov, since Petrov is listed as the editor in this block. The first block has only Ivanov. The second block has Ivanov and Petrov. Petrov can edit the document, since he is marked as an editor in the current second block, and pass it on along the route. Petrov finishes work and sends the document. The third block is created and transferred to Sidorov, as well as to Ivanov. The third block available for reading is in Ivanov and Petrov.

Sidorov can edit the third block. Sidorov, for example, introduced Petrov to the next line of document bypass along the route, to Pavlov, so that Petrov would make more changes.

The 4th block is created and transferred to Petrov. The fourth block available for reading belongs to Ivanov and Sidorov. Petrov can edit the 4th block.

Petrov made changes and sent the document further. The 5th block is created and transferred to Pavlov (for example, he is the boss and agrees on the final version of the document). Ivanov, Petrov, Sidorov have the 5th block available for reading.

Pavlov can edit the 5th block. Pavlov introduces another User into the document - Sinitsyna, puts himself on the route after Sinitsyna. Block 6 is created and transferred to Sinitsyna, as well as to other users who have already visited the document, so that they can track further actions on the document.

Note that all document route information is sent with the current database instance, so all users will have the new route. Sinitsyna can edit block 6. Ivanov, Petrov, Sidorov, Pavlov read-only. Sinitsyna passes on.

The 7th block is created and transferred to Pavlov. Pavlov can edit. Ivanov, Petrov, Sidorov, Sinitsyna have the 7th block with read-only access.

Sending a document to a counterparty

Let's consider an example. LLC "First", the contact person of which is Pavlov and LLC "Second", the contact person of which is Pirogov (figure 5).

LLC Vtoroe has already received and accepted an invitation from LLC Pervoe and both LLCs know the unique identifiers of the message server of each other's contact persons.

Pavlov has data on the group Vtoroe LLC and the user-contact person Vtoroe LLC Pirogov. Pirogov has data on the Pervoe LLC group and the user-contact person of Pervoe LLC Pavlov.

Pavlov has a document in the application, for example, an ongoing internal document flow, and sends it to the counterparty. A new block is created and sent to the contact person of the counterparty, Pirogov.

The status in the Pavlov application is marked as that of an external group; in this case, copies of the new block are not sent to their employees Ivanov, Petrov, and Sidorov. Pirogov's application accepts a new block from Ivanov and creates a new chain, since there were no such ones by the chain ID. Using the new chain, you can start the internal document flow in Vtoroe LLC.

When it ends, it will be possible to return the document to Pervoe LLC to the contact person Pavlov. For Pavlov, a new block from Pirogov is identified as a new block to an existing chain. Then you can continue the workflow within the organization.

Claims (18)

1. A distributed database system containing a plurality of computing devices interconnected via a network, as well as a server with a messaging system and a server with a server disk, functionally connected to each computing device of a plurality of computing devices, each of which contains a memory, a processor and a device conclusion, while the memory of each computing device of a plurality of computing devices of the system stores instructions that lead to the execution by the processor of functions associated with sending, via a server with a messaging system and a server with a server disk, to another computing device included in the plurality of computing devices, parts of a distributed database instance intended for editing and/or negotiation, as well as receiving from another computing device a plurality of computing devices of a distributed database instance, a synchronization event record, a record of previous synchronization events with other computing devices, an order of synchronization events, a value for a parameter, wherein the memory of the first computing device contains at least a part of a distributed database instance, configured to transfer to a plurality of computing devices of the system, which implement a distributed database via a network functionally connected to a plurality of computing devices of the system, each of the computing devices of the plurality of computing devices of the system is configured to detect the receipt of a message from other computing devices of the plurality of computing devices of the system, and, in the absence of permission to exchange messages, request permission to exchange data with a computing device that has a unique account identifier of the computing device from which it came message, and, with such permission, in the automated mode of extracting a link from the message, by which a new instance is automatically added to the database of the second or subsequent computing devices of a plurality of computing devices of the system. 2. The system of claim. 1, characterized in that the computing device contains an audio output device and/or a tactile output device. 3. The system according to claim 1, characterized in that the memory of the computing device is a random access memory RAM, a memory buffer, a hard disk, a database, an erasable programmable read-only memory device EPROM, an electrically erasable programmable read-only memory device EEPROM, a read-only memory device ROM . 4. The system of claim. 1, characterized in that the values for the parameter are database fields that quantify the transaction, a database field that quantifies the order in which events occur, and/or a field for which a value can be stored in database. 5. The system according to claim 1, characterized in that it further comprises a second set of computing devices, which is configured to interact with the first set of computing devices by receiving and transmitting distributed database instances through the assigned computing devices of the first and second sets of computing devices of the system. 6. The system according to claim 1, characterized in that the unique identifier of the computing device account is an email address, a phone number of a messenger account, a social network account identifier, an ecosystem identifier. 7. The system of claim. 1, characterized in that the computing device is a personal computing device, a desktop computer, a laptop computer, a mobile phone, a personal digital assistant PDA. 8. A method for implementing a distributed database by means of a distributed database system, comprising the steps of: create a group containing a plurality of computing devices of a distributed database system, for which from the first computing device, a part of the distributed database instance containing a link to join the group is sent to the computing devices included in the plurality of computing devices of the distributed database system, while the formed part of the distributed database instance is stored on the first computing device, for each document that is part of the distributed database instance on the first computing device, a route is specified with a list of unique identifiers of the group's computing device account, as well as rights to edit and/or approve the sent part of the distributed database instance for each of the specified group computing devices, upon completion of work with a part of the distributed database instance on the current computing device, the specified part of the instance is sent to the next computing device specified in the route, and is also simultaneously sent to previous computing devices, to form a complete instance of the distributed database and track actions on the specified document, while all parts of the distributed database instance are stored in the memory of each computing device specified in the route. 9. The method according to claim 8, characterized in that each of the plurality of computing devices in the group is configured to add other computing devices to the group by sending an invitation to the unique identifiers of the computing device account as part of a distributed database instance. 10. The method according to claim 8, characterized in that one computing device is assigned from the plurality of computing devices of the group, interacting with another computing device of the second plurality of computing devices of another group, also pre-assigned for interaction.

Images