EA044493B1 - DISTRIBUTED DATABASE SYSTEM AND METHOD OF ITS IMPLEMENTATION - Google Patents

Description

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

A method of working with a distributed database is known from the prior art, comprising the stages in which the front-end server receives a request to service the database, and the request to service the database 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 transmits the execution result to all other distributed database servers in a chain mode; and the interface server selects one distributed database server and sends the read operation to the selected distributed database server for execution (CN patent 108241641 A 07/03/2018).

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

The disadvantage of the known solution is that existing systems known from the prior art are organized in the form of a server, accessed through a web interface (website), on which all documents of all users are stored. And in accordance with the rights when users interact, access to the 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 server failure can render the entire computer network inoperable. In this case, an inoperative 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 (DDOS attack, for example), etc.

The technical problem of the invention 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 memory, a processor and an output device, wherein the memory of each computing device of the plurality of computing devices of the system stores instructions leading to the execution by the processor of functions associated with sending, through a server with a messaging system and a server with a server disk, to another computing device included in the plurality of computing devices, part of an instance of a distributed database data intended for editing and/or coordination, as well as receiving from another computing device included in a plurality of computing devices an instance of a distributed database, recording a synchronization event, recording previous synchronization events with other computing devices, the order of synchronization events, values for parameter, wherein the memory of the first computing device contains at least part of an instance of a distributed database configured to transfer to a plurality of computing devices of the system, which implement, through a network operatively connected to a plurality of computing devices of the system, a distributed database, each of the computing devices of the plurality of computing devices the systems are configured to detect the arrival of messages from other computing devices of multiple 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 the message came, and, if such permission is available , in an automated mode, selecting a link from a message through 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 a computing device includes a RAM, a memory buffer, a hard disk, a database, an EPROM, an EEPROM, and a ROM.

The values for a parameter are a database field that quantifies 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 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 designated 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 the identifier of any system that provides authorization to a third party with limited access to the user’s protected resources without transferring the login and password to the user (a third party) (for example, OAuth2; any ecosystem can provide such authentication).

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

The specified technical result is also achieved in a method for implementing a distributed database by means of a distributed database system, which includes the steps of: creating a group containing a plurality of computing devices of a distributed database system, for which part of an instance of a distributed database 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 generated portion 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 account identifiers of the group’s computing devices, as well as 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 working with part of a 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.

In this case, each of the multiple computing devices of the group is configured with the ability, if the appropriate rights are available, to add other computing devices to the group by sending an invitation to the unique account identifiers of the computing devices as part of a distributed database instance.

In this case, from the plurality of computing devices of the group, one computing device is assigned to interact with another computing device of the second set of computing devices of another group, also pre-assigned for interaction.

The claimed invention is illustrated in graphic materials, where Fig. 1 is a block diagram of a distributed database system, which illustrates

- 2 044493 distributed database system according to an embodiment using the example of one user group of four users and four computing devices;

Fig. 2 - block diagram of creating and sending an instance of a distributed database using the example of a messaging server in the form of a mail server (email);

fig. 3 - block diagram of creating a group of five people;

fig. 4 - block diagram of the organization’s internal document flow;

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

A distinctive feature of the invention is the storage of documents of each user of the system on his own computing device. When transferring 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 declared system implements client-client technology.

This allows you to avoid using huge servers with large, constantly expanding data sets, and yet ensure that all participants in the document flow receive documents. Moreover, if necessary, storing the user’s documents is possible on his personal server, or a group server, 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 for storage to the server, which is an additional function to the current work scheme.

Sending will also take an instance of a distributed database from a personal or team server, move it to a user's computing device, and then send it to another user, but the basic point of client-to-client document transfer remains the same.

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 the use of digital signatures of document flow participants. In this case, in the case of using an electronic signature, the private key is stored on a computing device or a separate storage medium of the user’s information, and the public key is transferred as part of a distributed database element using software.

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

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

The current instance of a distributed database for exchange means the extreme 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 software, even if the user is the current editor of the extreme 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 find out the identifier of the member of the first group from the message received in the invitation. Subsequently, 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 a server with a messaging system and a server with a server disk for each user of this group. This ensures that the message is received and the distributed database instance file 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 the server disk. These attempts are repeated at specified intervals until a successful result, which also guarantees the receipt of an instance of the distributed database, and hence 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, a server with a messaging system and

- 3 044493 the server with the server disk of the first must be known to the second. 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 individuals have access to the Internet. In this case, 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 disk on the Internet to send to a contact person in another group.

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

SQLite is a compact embedded DBMS. The library source code 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 computer on which the program is executed. Simplicity of implementation is achieved due to the fact that before the start of a write transaction, the entire file storing the database is locked; 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 this information is provided by the application (or operating system) itself. At the same time, the user does not need 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. After all, in this case, another application can be treated as a black box. In this case, its internal mechanism does not matter - the programmer may not even know what an API is.

Create and submit a distributed database instance.

Let's consider sending one message within a group using the example of Internet connection (creation, sending, receiving, sending confirmation). The algorithm for this function is as follows.

1. Do you have 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 a message and become a member of it?

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 identifier 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 can, but not necessarily, contain links to an unlimited number of files on a network drive, and uploads it to your network drive (Yandex Drive, Google Drive, etc.). Such a file is uploaded to the server with the server disk using the server API functions. Such API functions are standard for such servers, which is very convenient for other systems to interact with such servers.

On the network drive, after calling the next API function, a unique confidential link to download a file from this server is generated 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 sent by the first computing device in the form of a message to the unique account of the second computing device (this can be sending an email using the SMTP protocol, a message in a messenger or social network via the API functions of the messenger server, or social network).

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

In the case of email, this is a selection of letters (messages) by subject and date using the IMAP or POP3 protocol. In the case of a messenger or social network, this is checking all dialogues with other users for unread letters and selecting from them, using predefined keywords, through API functions.

- 4 044493

It is possible to implement the case with a dedicated messaging server specially created for document flow purposes; in this case, the database of such a server will be checked using keywords or identifiers.

When it detects the arrival of a specified message, the second computing device, in the absence of permission to exchange messages with the sender user, requests permission from the user of the second computing device to exchange data with another device having a unique identifier of the first user from whom the message came.

If permission is available, then the second device, using the software and knowing the format of the message, since the instance of the software 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 via the HTTPS protocol, downloads the distributed SQLite database file, and in accordance with the device group membership identifier from the message, adds a new instance to the second user’s database.

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

Next, if an existing chain of data preceding this instance is detected in a given group of devices, a new instance is added to the existing chain, otherwise a new one is created. This is implemented by indicating in each instance of a distributed document database the identifier of the parent chain and, accordingly, determining by it its membership in 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 distributed database element can be automatic thanks to software with an implemented timer, upon reaching the interval of which new mail, instant messenger or social network messages are checked, messages are processed and downloaded files in the above manner, 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 a message to the account with the unique identifier of the first user confirming the download of the file with the element of the distributed database via a link.

Such a message in a certain format will have the same download link that the first user sent, but instead of downloading from a 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 party. This will confirm that another user has downloaded the file. After the first computing device receives such confirmation using the software, the transfer of the distributed database instance is considered complete 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 distributed database elements.

If the first computing device sends an element of a distributed database to several computing devices for accounts with unique identifiers of their users, the sender's computing device deletes the file on a 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 messages sent and received using the software.

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

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

A user who has created an element of a distributed database and has not yet sent this element to another user has editing access. At the same time, only the current editor can send an instance of a distributed database.

When sending, the current sending user's computing device copies the current instance, changes the editor on the copy, and sends the new instance to the designated editor. The user who received this instance of the distributed database is the current editor of the instance and has editing access. The original of the copied copy becomes available to the sender on his computer for reading, since it is not the last one in the chain. A copy of the copy with the new editor also remains with the sender; it becomes the last element of the chain. The sender can read the last element on his computer, since he is no longer an editor. Thus, you can crawl a document using a list of users, knowing their unique message server account identifier. Such identifiers (e.g., email) are known to all group members about each member of that group. And each current recipient of the instance will be an editor, which means he will be able to send an instance of the distributed database 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 the distributed database 100 may use a set of any number of computing devices containing computing devices not shown in FIG. 1.

Also, network 105 may contain any number of mail servers and server drives. Network 105 may be any type of network (e.g., 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 through an Internet service provider (ISP) and the Internet (eg, network 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 the network 105 to send and/or receive data from one or more other computing devices. Examples of computing devices are shown in FIG. 1.

The computing device 110 includes a memory 112, a processor 111, and an output device 113. The memory 112 may be, for example, 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), and /or etc. 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 causing the processor to execute modules, processes, and/or functions associated with sending to and/or receiving from another computing device an instance of a distributed database (e.g., distributed database instance 124 on computing device 120) recording synchronization events, recording previous synchronization events with other computing devices (by exchanging distributed database instances with both the subsequent computing device and previous computing devices), the order of synchronization events, by generating a separate transaction log on each computing device distributed database (this log is stored on each computing device and is not transmitted), a value for a parameter (for example, a database field quantifying a transaction, a database field quantifying the order in which events occur, and/or any other suitable field , for which the value can be stored in the database).

The distributed database instance 114 may, for example, be configured 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 post-relational database, and/or any other suitable type of database. For example, distributed database instance 114 may store data related to any specific function and/or area. For example, distributed database instance 114 may store documents (e.g., of a user of computing device 110), including

- 6 044493 value and/or vector of values related to the ownership history of a specific 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 database instance 114.

The processor 111 of the computing device 110 may be any suitable processing device adapted to run and/or execute the 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 the 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 the value for a parameter stored in the distributed database instance 114 on computing device 110 to be sent to 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 includes another output 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 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 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, the distributed database instance 124 may be structurally and/or functionally similar to the 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, the distributed database instance 134 may be structurally and/or functionally similar to the 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, the distributed database instance 144 may be structurally and/or functionally similar to the 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, a 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 the 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 the distributed database system 100, including properties of the computing devices (eg, computing devices 110, 120, 130, 140), number of computing devices, and network 105 can be selected in any manner.

In distributed database system 100, one computing device is the leader and creates a group of users. For example, this could be the founder or director of the organization. When he creates a new member using his unique account ID, the new member is sent an invitation that contains information about the entire user group. When creating a new

- 7 044493 th participant can be assigned the rights to create new group users. For example, this could be the head of the HR department. Thus, not only the leader, but also any number of users assigned for this can add new users to the group. Each user's computing device checks the rights to create a new group member. And if there are no such rights, then the functionality for creating a new software participant is blocked or read-only. When a designated user adds a new member, information about the new member in the form of a distributed database instance is sent to all other members of the group. This way, each group member has correct information about all group members.

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

Let's consider an example when a new group of five people is created (Fig. 3). This may be a small organization. The founder or entrepreneur Pavlov creates an organization and a Pavlov user, which has a unique message server account identifier.

Pavlov has all the rights to any actions in this organization. He is marked as the creator of the group in the distributed database instance.

Using the software, he can create and edit new group employees. Pavlov creates Ivanov, who is his employee, enters his unique message server identifier, such as email, in the creation form, 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 an instance of a distributed database with a link. When accepting the invitation, Ivanov’s computing device downloads the file via the link and adds data about the new group and all its participants to its database on the computing device.

On Ivanov’s computing device there will be information about the group, user Pavlov and user Ivanov, and all this only with read access. Pavlov has everything the same, but with editing access, since he has rights to edit a 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 a copy of the 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 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 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 HR department and then he creates users of the system. He creates a new user Sinitsyna, who is an employee of Ivanov. Does not assign additional rights to her. Sinitsyna accepts the invitation. Ivanov, Petrov and Pavlov are sent a copy of the distributed database with information on Sinitsina. Everyone has information about the group, as well as users Ivanov, Petrov, Sidorov, Pavlov, Sinitsina.

For Ivanov, Petrov and Sinitsina, the information is read-only. Sidorov and Pavlov for editing. Sidorov cannot edit only Pavlova. It should be noted that when information about creating a new employee is received, the software checks whether the user of the sender of this message has rights to create a new user, and only if such rights are available 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 and the absence of confirmation from the user, the sender's computing device, using software, repeats sending the message with an instance of the distributed database. For example, a letter is lost and does not reach the recipient, a new letter is sent and this is repeated at specified intervals. Thus, the distributed database system ensures reliable data transfer between users' computing devices. The sending of such repeated messages can be canceled by the user of the sender's computing device.

-

Claims (9)

Internal document flow of the organization. Let's consider the system using the example of a group of four users who approve a document within one organization (Fig. 4). Each user knows the unique identifier of each message server account. This is achieved by creating a group and adding new members as described above. For each document, a route is set with a list of users from this group, along which this document is transferred when the current user finishes working 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 the route with other users of the group, and also sets whether any 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 his 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 for Ivanov, since Petrov is listed as the editor in this block. Only Ivanov has the first block. The second block is occupied by Ivanov and Petrov. Petrov can edit the document, since he is marked as an editor in the current second block, and transmit it further along the route. Petrov finishes his work and sends the document. A third block is created and transferred to Sidorov, as well as Ivanov. The third block, available for reading, is from Ivanov and Petrov. Sidorov can edit the third block. Sidorov, for example, included Petrov in the next stage of document bypass along the route, to Pavlov, so that Petrov could make more changes. The 4th block is created and transferred to Petrov. The fourth block, available for reading, is from 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). The 5th block, available for reading, is available from Ivanov, Petrov, Sidorov. Pavlov can edit the 5th block. Pavlov adds another user to the document - Sinitsina, and places himself on the route after Sinitsina. Block 6 is created and transmitted to Sinitsyna, as well as to other users who have already visited the document, so that they can track further actions on the document. It should be noted that all document route information is sent with the current database instance, so the new route will be available to all users. Sinitsyna can edit block 6. Ivanov, Petrov, Sidorov, Pavlov are 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 look at an example. LLC First, whose contact person is Pavlov and LLC Second, whose contact person is Pirogov (Fig. 5). LLC Second has already received and accepted an invitation from LLC First and both LLCs know the unique message server identifiers of each other's contact persons. Pavlov has information about the LLC Second group and the user-contact person LLC Second Pirogov. Pirogov has information about the LLC Pervoe group and the user-contact person LLC Pervoe Pavlov. Pavlov has a document attached, for example, an internal document flow, and sends it to the counterparty. A new block is created and sent to the counterparty’s contact person Pirogov. The status in Pavlov’s application is marked as that of an external group; in this case, copies of the new block are not sent to his 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 based on the chain identifier. Using the new chain, you can launch internal document flow in Second LLC. When it ends, you can return the document to LLC First contact person Pavlov. Pavlov identifies the new block from Pirogov as a new block to the existing chain. Then you can continue document flow within the organization. CLAIM 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 output, - 9 044493 wherein the memory of each computing device of the plurality of computing devices of the system stores instructions leading to the execution by the processor of functions associated with sending, through 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 database instance data intended for editing and/or coordination, as well as receiving from another computing device of a plurality of computing devices an instance of a distributed database, a synchronization event record, a record of previous synchronization events with other computing devices, the order of synchronization events, a value for a parameter, wherein the memory of the first the computing device contains at least part of an instance of a distributed database, configured to transmit to a plurality of computing devices of the system, which implement, through a network operatively connected to the 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 receipts messages from other computing devices of multiple 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 the message came, and, if such permission is available, in an automated allocation mode from a link message that automatically adds a new instance to the database of the second or subsequent computing devices of the plurality of computing devices of the system. 2. The system of claim 1, wherein the computing device comprises an audio output device and/or a tactile output device. 3. The system of claim 1, wherein the computing device memory is a RAM, a memory buffer, a hard disk, a database, an EPROM, an EEPROM, a ROM . 4. The system according to claim 1, characterized in that the values for the parameter are a database field that quantifies the transaction, a database field that quantifies the order in which events occur, and/or a field for which the value can be stored in database. 5. The system according to claim 1, characterized in that it 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 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 telephone number of a messenger account, a social network account identifier, an ecosystem identifier. 7. The system according to claim 1, characterized in that the computing device is a personal computing device, a desktop computer, a laptop computer, a mobile phone, a PDA. 8. A method for implementing a distributed database using a distributed database system, including the steps of: creating a group containing a plurality of computing devices of a distributed database system, for which, from the first computing device, a part of an instance of a distributed database containing a link to join the group is sent to the computing devices included in the plurality of computing devices of a distributed database system, and the formed part of the instance distributed database 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 account identifiers of the group’s computing devices, as well as 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 of work with 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 data and tracking actions on a specified document, with all parts of the distributed database instance 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 account identifiers of the computing devices as part of the instance -