Methods for enabling collaborative work between nodes, collaborative service engine, and collaborative system

By synchronizing group information and business data through the collaborative service engine, the problem of data transmission between branch offices and headquarters in existing collaborative work systems has been solved, enabling efficient collaborative browsing, collaborative editing and file sharing, and improving system data consistency and user experience.

CN116455897BActive Publication Date: 2026-11-10BEIJING FEIXUN DIGITAL TECH CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202310329924.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-03-30
Publication Date
2026-11-10
Estimated Expiration
2043-03-30

AI Technical Summary

Technical Problem

Existing collaborative work systems struggle to achieve efficient collaborative browsing, collaborative editing, and file sharing between branch offices and headquarters, especially when large numbers of users access the system concurrently, making it difficult to reliably transmit multimedia data and resulting in high bandwidth resource requirements.

Method used

By synchronizing group information data and business data, a collaborative service engine is used to realize collaborative operations between nodes, including group information data synchronization interface, group business data synchronization interface, management interface, query interface and heartbeat detection interface, to ensure data consistency and online status management.

Benefits of technology

It achieves data consistency and low-latency synchronization within the same collaborative task group, improving the user's collaborative task experience and system efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116455897B_ABST
    Figure CN116455897B_ABST
Patent Text Reader

Abstract

This application discloses a method, a collaborative service engine, and a collaborative system for implementing inter-node collaborative operations. The method includes: synchronizing group information data between a first node and a second node; when the synchronized group information data records that the first node and the second node belong to the same collaborative operation group, the first node and the second node synchronize group business data; and the first node displays the synchronized group business data to a user-operated client. The collaborative service engine includes: a group business data synchronization interface; a group information data synchronization interface; a management interface; a query interface; and a heartbeat detection interface. Thus, inter-node collaborative operations are realized, meeting the collaborative operation needs of multiple users for various applications.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of collaborative work technology, and in particular to a method, collaborative service engine and collaborative system for realizing collaborative work between nodes. Background Technology

[0002] Currently, most collaborative office systems set up in various branches and headquarters have functions such as video connection, point-to-point communication, and video monitoring, but have not yet reliably and efficiently realized collaborative browsing, collaborative editing, file sharing, electronic whiteboard and other collaborative work functions.

[0003] This is because collaborative browsing, collaborative editing, file sharing, electronic whiteboards and other collaborative tasks will generate a large number of concurrent user accesses, which requires the handling of real-time and reliable transmission of multimedia data such as files, audio and video, and also places higher demands on bandwidth resources.

[0004] Therefore, it is necessary to provide collaborative operation technology solutions that have application collaboration support capabilities and can provide collaborative process control and collaborative data management. Summary of the Invention

[0005] To address the above issues, this invention provides a method, a collaborative service engine, and a collaborative system for enabling collaborative operations between nodes, thereby meeting the collaborative operation needs of multiple users for various applications.

[0006] In a first aspect, the present invention provides a method for realizing collaborative work between nodes, comprising:

[0007] The first node synchronizes group information data with the second node;

[0008] When the first node and the second node belong to the same collaborative operation group after synchronization, the first node and the second node synchronize the group business data.

[0009] The first node displays the synchronized group service data to the user's client.

[0010] Furthermore, the first node synchronizes packet information data or packet service data with the second node, including:

[0011] The first node sends the packet information data version or the packet service data version to the second node;

[0012] When the first node receives a response message from the second node, it sends packet information data or packet service data to the second node so that the second node updates its stored packet information data or packet service data; wherein, the response message is a message sent by the second node when it determines that the version of the packet information data or the version of the packet service data is higher than the version stored by the second node.

[0013] Furthermore, the first node synchronizes packet information data or packet service data with the second node, including:

[0014] The first node obtains the packet information data version or the packet service data version from the second node;

[0015] When the first node determines that the version of the packet information or the version of the packet service data is higher than the version stored by the first node, it obtains the packet information data or the packet service data from the second node.

[0016] The first node updates its stored packet information data or packet service data based on the acquired packet information data or packet service data.

[0017] Furthermore, the packet information data or packet service data includes stored static data or cached real-time data;

[0018] The first node synchronizes packet information data or packet service data with the second node, including:

[0019] The first node and the second node perform synchronization of the stored static data;

[0020] The first node and the second node perform the synchronization of the cached real-time data.

[0021] Furthermore, the first node and the second node perform synchronization of the cached real-time data, including:

[0022] The cached real-time data is divided into at least two parts, which include a first part of data and a second part of data;

[0023] The synchronization of the cached real-time data includes one of the following:

[0024] When operating on the first part of the data of the first node, and when there is no record of locking the first part of the data, the first part of the data is cached;

[0025] When the first part of the data on the first node is operated on, and the second part of the data is locked by the second node, the first part of the data is cached, and the second part of the data is synchronized from the second node to the first node, wherein the second part of the data being locked by the second node indicates that the second part of the data on the second node is operated on.

[0026] When the first part of the data on the first node is operated on, and the first part of the data is locked, the first part of the data is synchronized from the second node to the first node, the first part of the data is processed and cached in response to the operation, and the locking of the first part of the data indicates that the first part of the data on the second node has been operated on.

[0027] Furthermore, before the first node synchronizes packet information data or packet service data with the second node, the process also includes:

[0028] The first node detects the online status of the second node through heartbeat information.

[0029] Secondly, the present invention provides a collaborative service engine for realizing inter-node collaborative operations, comprising:

[0030] The group business data synchronization interface is used to synchronize group business data when performing collaborative operations between nodes;

[0031] The group information data synchronization interface is used to synchronize group information data when performing collaborative operations between nodes;

[0032] The management interface is used to respond to user management operations through the client, and update the stored group information data, business priority data, and / or the online status of each node during inter-node collaborative operations;

[0033] The query interface is used to respond to user queries through the client and return the queried group business data or group information data processed during inter-node collaborative operations to the client.

[0034] The heartbeat detection interface is used to detect the online status of a target node through heartbeat information.

[0035] Thirdly, the present invention provides a collaborative system for realizing inter-node collaborative operations, comprising:

[0036] At least one collaborative service engine, which belongs to at least the same collaborative job group, is used to perform collaborative jobs between nodes;

[0037] The client consists of at least two users, including a first user's client and a second user's client; the first user's client corresponds to a collaboration service engine and runs at least one collaboration application, and the second user's client corresponds to a collaboration service engine and runs at least one collaboration application.

[0038] Each of the aforementioned collaborative service engines includes:

[0039] The group business data synchronization interface is used to synchronize group business data when performing collaborative operations between nodes;

[0040] The group information data synchronization interface is used to synchronize group information data when performing collaborative operations between nodes;

[0041] The management interface is used to respond to the management operations performed by the first user or the second user through the client, and to update the stored group information data, business priority data, and / or the online status of each node during inter-node collaborative operations.

[0042] The query interface is used to respond to the query operation of the first user or the second user through the client and return the group business data or group information data processed during the inter-node collaborative operation to the client.

[0043] The heartbeat detection interface is used to detect the online status of the target node through heartbeat information;

[0044] The client of the first user or the client of the second user is configured with an interactive interface for collaborative work, to display the group information data or the group business data processed during collaborative work between nodes, and to receive user operations for any collaborative application through the interactive interface, and to respond to the operations by accessing the corresponding collaborative service engine to process the group information data or the group business data.

[0045] Fourthly, the present invention provides a computing device, comprising: a processor and a memory, the memory storing program instructions, which, when executed by the processor, cause the processor to perform a method for implementing inter-node collaborative work as described in the first aspect, or to be configured as a collaborative service engine for implementing inter-node collaborative work as described in the second aspect.

[0046] Fifthly, the present invention provides a storage medium storing program instructions that, when executed by a processor, cause the processor to perform a method for implementing inter-node collaborative work as described in the first aspect, or to be configured as a collaborative service engine for implementing inter-node collaborative work as described in the second aspect.

[0047] These and other aspects of the invention will become more apparent from the following description of several embodiments. Attached Figure Description

[0048] Figure 1 This is a flowchart illustrating a method for implementing inter-node collaborative operations according to an embodiment of this application.

[0049] Figure 2 This is a schematic diagram illustrating the process of statically synchronizing group information for implementing the method of inter-node collaborative operation according to an embodiment of this application;

[0050] Figure 3 This is a schematic diagram illustrating the process of implementing static synchronization of grouped data in the method for realizing collaborative work between nodes according to an embodiment of this application;

[0051] Figure 4 This is a schematic diagram illustrating the process of real-time synchronization of group information in the method for implementing collaborative work between nodes according to an embodiment of this application.

[0052] Figure 5 This is a schematic diagram illustrating the process of real-time synchronization of grouped data in the method for implementing collaborative work between nodes according to an embodiment of this application.

[0053] Figure 6 This is a flowchart illustrating the method for implementing inter-node collaborative operations in this application, enabling real-time data synchronization during cross-domain collaboration.

[0054] Figure 7 A flowchart illustrating the heartbeat information detection process for the method of implementing inter-node collaborative operation according to an embodiment of this application;

[0055] Figure 8 This is a schematic diagram illustrating the composition of the collaborative service engine for implementing inter-node collaborative operations in an embodiment of this application;

[0056] Figure 9 This is a schematic diagram illustrating the composition of nodes for implementing collaborative operations between nodes in an embodiment of this application;

[0057] Figure 10 This is a schematic diagram illustrating the application of the method for implementing inter-node collaborative operations in this application during cross-domain collaboration.

[0058] Figure 11 This is a schematic diagram illustrating the application of the method for implementing inter-node collaborative operations in this application during intra-domain collaboration.

[0059] Figure 12 This is a schematic diagram of the composition of a computing device according to an embodiment of this application. Detailed Implementation

[0060] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application. In addition, the technical features of the various embodiments or individual embodiments provided in this application can be arbitrarily combined with each other to form feasible technical solutions. Such combinations are not bound by the order of steps and / or structural composition patterns, but must be based on the ability of those skilled in the art to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be considered that such combination of technical solutions does not exist and is not within the scope of protection claimed by this application.

[0061] In order to accurately describe the technical content of this application and to accurately understand this application, the following explanations or definitions of the terms used in this specification are given before describing the specific embodiments.

[0062] An engine is a core component of a developed program or software system. Using an engine, developers can quickly build and deploy the necessary functions of a program, or utilize it to assist the operation of an application. Generally speaking, an engine is a supporting part of a program or system, such as a storage engine, a search engine, or a game engine.

[0063] Collaborative browsing refers to the act of accessing and controlling web pages simultaneously with one or more other people. Unlike simply supporting multiple users to do different things at the same time without interfering with each other, it allows a group of people to engage in synchronized activities. For example, an action or behavior by one person on a web page displayed on their screen will be seen on the same web page accessed by other participants.

[0064] An electronic whiteboard typically refers to interactive electronic whiteboard software, such as an electronic whiteboard installed on a smart interactive whiteboard. Smart interactive whiteboards usually have a large screen, and in addition to being used as a display tool, they can also perform further operations on the displayed objects, such as editing word processing files (e.g., PPT, Word, PDF, TXT), editing images, and playing audio and video files.

[0065] The technical solution of this application will be described in detail below with reference to the accompanying drawings.

[0066] Example 1

[0067] like Figure 1 As shown in the figure, the method for implementing inter-node collaborative work in this application embodiment includes the following steps:

[0068] S10: The first node synchronizes group information data with the second node;

[0069] S20: When the first node and the second node belong to the same collaborative operation group in the synchronized group information data record, the first node and the second node synchronize the group business data.

[0070] S30: The first node displays the synchronized group service data to the user's client.

[0071] Thus, the first node and the second node first synchronize group information data to determine whether the synchronized group information data records that the first node and the second node belong to the same collaborative operation group. When the first node and the second node belong to the same collaborative operation group, the first node and the second node synchronize group business data so that the first node displays the synchronized group business data to the user's client, thereby realizing collaborative operation between nodes.

[0072] In some embodiments, step S10 above may include: a first node querying whether a second node is within a specified collaborative task group; if the second node is within the specified collaborative task group, the first node updating the group information data corresponding to the specified collaborative task group; if the second node is not within the specified collaborative task group, the first node adding the second node to the specified collaborative task group and updating the group information data corresponding to the specified collaborative task group.

[0073] In this way, the first node proactively manages its grouping to ensure it belongs to the same collaborative task group as the second node, enabling subsequent intra-domain or cross-domain collaborative tasks with the second node. This achieves collaborative process control and collaborative data management functions.

[0074] like Figure 2 As shown, in this embodiment, the synchronization of packet information data or packet service data between the first node and the second node includes:

[0075] The first node sends the packet information data version or the packet service data version to the second node;

[0076] When the first node receives a response message from the second node, it sends packet information data or packet service data to the second node so that the second node updates its stored packet information data or packet service data; wherein, the response message is a message sent by the second node when it determines that the version of the packet information data or the version of the packet service data is higher than the version stored by the second node.

[0077] Thus, when the first node and the second node synchronize packet information data or packet service data, the first node (e.g., node A) may send a packet information data version or packet service data version to the second node (e.g., node B); when the first node receives a response message sent by the second node, it sends packet information data or packet service data to the second node so that the second node updates its stored packet information data or packet service data; wherein, the response message is a message sent by the second node when it determines that the packet information data version or packet service data version is higher than the version stored by the second node.

[0078] In this way, the higher version of the group information data or group service data stored in the first node is synchronized to the second node that belongs to the same collaborative operation group, so that the group information data or group service data stored in the first node and the second node are consistent, and collaborative operation between nodes is realized.

[0079] In a scenario where the first node in the same collaborative work group actively synchronizes its stored group information data or group service data with the second node, the first node sends the group information data version or group service data version to the second node.

[0080] When the first node receives a response message from the second node, it sends packet information data or packet service data to the second node so that the second node updates its stored packet information data or packet service data; wherein, the response message is a message sent by the second node when it determines that the version of the packet information data or the version of the packet service data is higher than the version stored by the second node.

[0081] Specifically, the database used to store collaborative work data updates its data version number every time it saves data. For example, the current system time can be accurate to the second and used as the version number, such as 202211051603. Correspondingly, one version being higher than another could mean that the system time corresponding to that version is more recent. Alternatively, the data version number can be a combination of the user identifier who modified the data and the timestamp, which will not be elaborated further.

[0082] In other words, the first node sends a packet information data version or a packet service data version to the second node. The second node then determines whether the packet information data version or packet service data version is higher than the version stored by the second node. If it is higher than its own stored version, the first node sends a response message to the first node, requesting the first node to send packet information data or packet service data. After receiving the packet information data or packet service data sent by the first node, the first node updates its own stored packet information data or packet service data. In this way, by the first node actively synchronizing its stored packet information data or packet service data with the second node, data consistency between the first node and the second node is achieved.

[0083] In summary, through the response message mechanism and version comparison, the first node proactively synchronizes its stored group information data or group business data to the second node. This achieves a good balance between data consistency and low latency data synchronization among nodes in the same collaborative work group.

[0084] like Figure 3 As shown, in this embodiment, the synchronization of packet information data or packet service data between the first node and the second node includes:

[0085] The first node obtains the packet information data version or the packet service data version from the second node;

[0086] When the first node determines that the version of the packet information or the version of the packet service data is higher than the version stored by the first node, it obtains the packet information data or the packet service data from the second node.

[0087] The first node updates its stored packet information data or packet service data based on the acquired packet information data or packet service data.

[0088] Thus, when the first node synchronizes packet information data or packet service data with the second node, the first node (as shown in node A in the figure) may obtain the packet information data version or packet service data version from the second node (as shown in node B in the figure); when the first node determines that the packet information data version or packet service data version is higher than the version stored by the first node, it obtains the packet information data or packet service data from the second node; the first node updates its stored packet information data or packet service data according to the obtained packet information data or packet service data.

[0089] In this way, the higher version of the group information data or group service data stored in the second node is synchronized to the first node that belongs to the same collaborative operation group, so that the group information data or group service data stored in the first node and the second node are consistent, and collaborative operation between nodes is realized.

[0090] In scenarios where a first node actively requests synchronization of its stored group information data or group business data from a second node within the same collaborative task group, or where a second node actively synchronizes its stored group information data or group business data from a first node, the synchronization of group information data or group business data between the first node and the second node includes:

[0091] The first node obtains the packet information data version or the packet service data version from the second node;

[0092] When the first node determines that the version of the packet information or the version of the packet service data is higher than the version stored by the first node, it obtains the packet information data or the packet service data from the second node.

[0093] The first node updates its stored packet information data or packet service data based on the acquired packet information data or packet service data.

[0094] That is, the first node obtains the packet information data version or packet service data version from the second node; when the first node determines that the packet information version or packet service data version is higher than the version stored by the first node, it obtains the packet information data or packet service data from the second node; the first node updates its stored packet information data or packet service data according to the obtained packet information data or packet service data.

[0095] The above describes how the first node within the same collaborative task group can proactively request synchronization of its stored group information data or group business data with the second node. This achieves a good balance between data consistency and low latency data synchronization among nodes within the same collaborative task group.

[0096] like Figure 2 , Figure 3 , Figure 4 and Figure 5 As shown, in this embodiment, the packet information data or packet service data includes stored static data or cached real-time data;

[0097] The first node synchronizes packet information data or packet service data with the second node, including:

[0098] like Figure 2 or Figure 3As shown, the first node and the second node perform synchronization of the stored static data;

[0099] like Figure 4 or Figure 5 As shown, the first node and the second node perform real-time data synchronization of the cache.

[0100] Based on the time span between the data generation time and the current time during data synchronization between nodes, the group information data or group business data can be divided into static data already stored in the database or real-time data currently cached locally on the node. Specifically, in the static data synchronization scenario, the time span between the data generation time and the current time is large, and the group information data or group business data is static data already stored in the database. In the real-time data synchronization scenario, the time span between the data generation time and the current time is small, and the group information data or group business data is real-time data currently cached locally on the node.

[0101] Accordingly, the synchronization of packet information data or packet service data between the first node and the second node includes: the synchronization of the stored static data between the first node and the second node; and the synchronization of the cached real-time data between the first node and the second node.

[0102] Specifically, for static data stored in the database, the first node and the second node within the same collaborative task group synchronize the static data in the database according to the version; for real-time data cached in the database, the first node and the second node within the same collaborative task group synchronize the cached real-time data. In this way, a better balance can be achieved between data consistency among nodes within the same collaborative task group and the latency of data synchronization between nodes to meet different synchronization requirements.

[0103] Thus, in both static and real-time data synchronization scenarios, different data synchronization methods can be used to ensure consistency between the grouped information data or grouped business data stored on different nodes, depending on the data storage location. This can achieve more efficient collaborative operation between nodes and improve the user experience.

[0104] Specifically, Figure 2In this process, node A's collaborative service engine provides collaborative services to the first node, and node B's collaborative service engine provides collaborative services to the second node. When performing static synchronization of group information between the cross-domain node A and node B collaborative service engines, node A's collaborative service engine checks whether node B is its associated node upon startup. If it is, it periodically sends heartbeat detection messages to node B's collaborative service engine until it receives a valid heartbeat message from node B's collaborative service engine; it then updates the online status of the associated node. Node B's collaborative service engine replies to node A with a successful heartbeat detection message, queries node A for the group information version, and sends the version associated with both node A and node B to node B's collaborative service engine. Upon receiving the group information version, node B's collaborative service engine compares it to its own version. If it finds a version higher, it requests the corresponding group information data from node A's collaborative service engine. Node A's collaborative service engine returns the corresponding group information data. Node B's collaborative service engine then saves the group information data and its version. At this point, the static synchronization of group information data ends. Subsequently, when the collaborative application is launched, the corresponding node collaborative service engine pushes the group information data to the collaborative application.

[0105] In this way, when the first node and the second node belong to the same collaborative work group, the corresponding group information data can be statically synchronized to achieve data consistency among nodes within the same collaborative work group.

[0106] Specifically, Figure 3 In this context, the A-node collaboration service engine provides collaboration services to the first node, and the B-node collaboration service engine provides collaboration services to the second node. When the A-node and B-node collaboration service engines synchronize group information in real time across domains, when the client corresponding to the user operation on node A starts, it calls the management interface to add, delete, or modify group information. Upon receiving messages regarding added, deleted, or modified group information, the A-node collaboration service engine saves the messages locally and sends them to the associated B-node collaboration service engine. Upon receiving the group information change message from node A, the B-node collaboration service engine determines whether the version number of the group information data on node A is continuous. If not, it performs a static synchronization of the group information data with node A (refer to the previous section). Figure 2 After the group information data between node A and node B is statically synchronized, the cache information of the group information is updated, and the group information data is sent to the collaborative application of node B. The collaborative application of node B then receives the group information data from the collaborative application of node A after the group information data between node A and node B is synchronized. At this point, the real-time synchronization of group information data ends.

[0107] In this way, when the first node and the second node belong to the same collaborative work group, the corresponding group information data can be synchronized in real time, which can achieve data consistency among nodes in the same collaborative work group and shorten the delay time of data synchronization between nodes.

[0108] Specifically, Figure 4 In this architecture, the A-node collaboration service engine provides collaboration services to the first node, and the B-node collaboration service engine provides collaboration services to the second node. During cross-domain static data synchronization between the A-node and B-node collaboration service engines, the A-node collaboration service engine checks whether the B-node is its associated node upon startup. If it is, it periodically sends heartbeat messages to the B-node to determine if the heartbeat detection is successful. If the heartbeat detection fails, it updates the online status of the associated node (e.g., B-node unreachable, i.e., ISOFF) and waits for the next heartbeat detection. If the detection succeeds, it updates the online status of the associated node (e.g., B-node reachable, i.e., ISON). Node A's collaborative service engine queries Node B's collaborative service engine for group data version information. Node B receives the query message from Node A and returns version information for all group business data of users on Node A, containing this information. Node A's collaborative service engine receives the version information returned by Node B's engine and compares it with the version information queried from Node B. If it determines that the version information returned by Node B is higher than the version information on Node A, it sends a message to Node B to download the specified group business data. Node B receives the download message from Node A and returns the specified group business data to Node A. Node A receives the downloaded group business data, updates the corresponding group business data in its database and updates the group data cache, and updates the group business data version. This completes the static collaboration of group business data. The synchronized business data is stored in the database and in each node's collaborative service engine. Subsequently, when the collaborative application starts, the corresponding node's collaborative service engine pushes the group business data to the collaborative application.

[0109] In this way, when the first node and the second node belong to the same collaborative work group, the corresponding group business data can be statically synchronized to achieve data consistency among nodes within the same collaborative work group.

[0110] Specifically, Figure 5In this process, the A-node collaborative service engine provides collaborative services to the first node, and the B-node collaborative service engine provides collaborative services to the second node. When performing real-time synchronization of grouped business data between the A-node and B-node collaborative service engines across domains, after the A-node collaborative application starts, it operates the collaborative application, generates business data, and notifies the A-node collaborative job engine to synchronize business data within the same collaborative job group. Upon receiving the business data within the group, the A-node collaborative service engine saves the grouped business data locally and sends it to the associated node. If a heartbeat check is performed, the business data is sent to the associated B-node collaborative service engine within the same collaborative job group. Upon receiving the grouped business data from the A-node, the B-node collaborative service engine determines whether the version numbers of the A-node grouped business data are consecutive. If the version numbers are not consecutive, the B-node collaborative service engine first performs a static synchronization of the grouped business data with the A-node collaborative service engine (e.g., ...). Figure 3 (As shown), then update the cache of the group data and notify the B node collaborative application of the business data; the B node collaborative application receives the group business data from the A node collaborative application after the A node and B node group data are synchronized, and the real-time synchronization of the group business data ends.

[0111] In this way, the first node and the second node can synchronize the corresponding group business data in real time when they belong to the same collaborative operation group, which can achieve data consistency among nodes in the same collaborative operation group and shorten the delay time of data synchronization between nodes.

[0112] like Figure 6 As shown, in this embodiment, the first node and the second node perform synchronization of the cached real-time data, including:

[0113] The cached real-time data is divided into at least two parts, which include a first part of data and a second part of data;

[0114] The synchronization of the cached real-time data includes one of the following:

[0115] When operating on the first part of the data of the first node, and when there is no record of locking the first part of the data, the first part of the data is cached;

[0116] When the first part of the data on the first node is operated on, and the second part of the data is locked by the second node, the first part of the data is cached, and the second part of the data is synchronized from the second node to the first node, wherein the second part of the data being locked by the second node indicates that the second part of the data on the second node is operated on.

[0117] When the first part of the data on the first node is operated on, and the first part of the data is locked, the first part of the data is synchronized from the second node to the first node, the first part of the data is processed and cached in response to the operation, and the locking of the first part of the data indicates that the first part of the data on the second node has been operated on.

[0118] In real-time data synchronization scenarios, this section provides methods for handling data conflicts that occur during inter-node collaborative operations, specifically addressing whether the data to be operated on by the first node is being operated on by the second node. This ensures consistency between the grouped information data or grouped business data stored separately by each node, while also improving the efficiency of collaborative operations and enhancing the user experience.

[0119] Specifically, in order to meet the collaborative work needs of multiple users for various applications within or across domains, a large amount of collaborative data exchange is generated when two opposing nodes perform collaborative work in any collaborative work network. The grouped business data of the collaborative work between nodes can be divided into at least two parts, including a first part of data and a second part of data.

[0120] Referring to the foregoing description, when responding to user operations on the client side to perform collaborative work, the real-time data synchronization scenario between nodes can be roughly divided into the following three scenarios.

[0121] The first scenario involves a user corresponding to a first node operating any collaborative application through a user-operated client, while users corresponding to other nodes within the same collaborative task group do not initiate operations on the same collaborative application through their user-operated clients. For example, in an electronic whiteboard collaborative application, only the first node is operating (generating the first part of data) within the same work area on the electronic whiteboard, while other nodes are online but not performing any operations. In this case, the synchronization of the cached real-time data is performed, including: caching the first part of data when operating on the first node's first part of data, provided that the first part of data is not locked. Since only the first node operates on the first part of data, and other nodes within the same collaborative task group do not initiate operations on it, the database caches the first part of data and synchronizes it to other nodes within the same collaborative task group in real time.

[0122] The second scenario involves a user corresponding to the first node operating any collaborative application through a user-operated client. Simultaneously, a second node within the same collaborative task group is also initiating operations on the same collaborative application. For example, in an electronic whiteboard collaborative application, the first node operates on the first work area of ​​the electronic whiteboard (generating the first part of data), and the second node operates on the second work area of ​​the electronic whiteboard (generating the second part of data). That is, multiple online nodes within the same collaborative task group are performing different operations on the same collaborative application (e.g., accessing the same access address via the web). In this case, synchronizing the cached real-time data includes: when operating on the first part of the data of the first node, and when the second part of the data is locked by the second node, caching the first part of the data and synchronizing the second part of the data from the second node to the first node, wherein the second part of the data being locked by the second node indicates that the second part of the data on the second node has been operated on. At this time, multiple nodes within the same collaborative task group are performing different operations on the same collaborative application. The database caches the first part of the data and synchronizes the second part of the data from the second node to the first node in real time. Correspondingly, the first part of the data is synchronized from the first node to the second node in real time, and the first part of the data and the second part of the data are synchronized to other online nodes within the same collaborative task group in real time. Additionally, the first part of the data and the second part of the data are statically synchronized to other offline nodes within the same collaborative task group.

[0123] The third scenario involves a user corresponding to a first node operating any collaborative application through a user-operated client. Simultaneously, a user corresponding to a second node within the same collaborative task group is also initiating an operation on the same collaborative application through their user-operated client. For example, in an interactive whiteboard application, the first node operates on the first work area of ​​the whiteboard (generating the first part of data), and the second node also operates on the first work area of ​​the whiteboard (generating the first part of data). That is, multiple nodes within the same collaborative task group are performing operations on the same data within the same collaborative application (e.g., accessing the same access address via the web). In this case, when the first part of data on the first node is operated on and is locked, the first part of data is synchronized from the second node to the first node. The operation processes and caches the first part of data. The locking of the first part of data indicates that the first part of data on the second node has been operated on. Correspondingly, the first part of data is synchronized from the first node to the second node in real time, and the first part of data operated on by the first node and the first part of data operated on by the second node are also synchronized in real time to other online nodes within the same collaborative task group. In addition, the first part of the data operated by the first node and the first part of the data operated by the second node are statically synchronized to other offline nodes within the same collaborative task group.

[0124] Thus, methods for data synchronization are provided to address potential conflict scenarios when different nodes within the same collaborative task group operate on the same collaborative application, achieving a good balance between data consistency between nodes and low latency in data synchronization.

[0125] The three scenarios above illustrate the real-time synchronization of grouped business data between nodes. The methods for real-time synchronization of information business data between nodes can be derived similarly and will not be elaborated further.

[0126] like Figure 7 As shown, in this embodiment, before the first node synchronizes packet information data or packet service data with the second node, the following steps are also included:

[0127] The first node detects the online status of the second node through heartbeat information.

[0128] Thus, when the first node detects that the second node is online through heartbeat information, the first node and the second node begin to synchronize packet information data or packet service data. This avoids the bandwidth and computing resources consumed when synchronizing packet information data or packet service data with the second node when the second node is offline, improves the efficiency of collaborative operation, and helps to improve the user experience.

[0129] Specifically, Figure 7 In this process, node A's collaborative service engine provides collaborative services to the first node, and node B's collaborative service engine provides collaborative services to the second node. When the first node detects the online status of the second node through heartbeat information, it initiates a heartbeat detection from node A's collaborative service engine to node B's collaborative service engine. This process includes: After starting, node A's collaborative service engine first determines whether node B's collaborative service engine is an associated node, that is, whether the first node and the second node are in the same collaborative job group. If they are associated nodes, it periodically sends heartbeat detection messages (such as the string "ISON") to node B's collaborative service engine until a heartbeat message is received. After receiving the heartbeat detection message from node A's collaborative service engine, node B's collaborative service engine generates a valid heartbeat message (such as the string "ISON") and sends it to node A's collaborative service engine. When the valid heartbeat message indicates that the heartbeat information detection has passed, node A's collaborative service engine updates the online status of the associated nodes based on the received heartbeat message (e.g., maintaining an associated node online status table, which records whether node B's collaborative service engine is online (ISON) or offline (ISOFF)). The heartbeat detection process initiated by node A's collaborative service engine then ends. In this way, heartbeat feedback information from associated nodes can be obtained through heartbeat detection to provide collaborative process control.

[0130] Example 2

[0131] like Figure 8 and Figure 9 As shown in this embodiment, the collaborative service engine for implementing inter-node collaborative operations includes:

[0132] The group business data synchronization interface is used to synchronize group business data when performing collaborative operations between nodes;

[0133] The group information data synchronization interface is used to synchronize group information data when performing collaborative operations between nodes;

[0134] The management interface is used to respond to user management operations through the client, and update the stored group information data, business priority data, and / or the online status of each node during inter-node collaborative operations;

[0135] The query interface is used to respond to user queries through the client and return the queried group business data or group information data processed during inter-node collaborative operations to the client.

[0136] The heartbeat detection interface is used to detect the online status of a target node through heartbeat information.

[0137] In this way, the collaborative service engine responds to various operations initiated by the user through the client and provides various collaborative operation services to the user's client using the aforementioned method for implementing collaborative operations between nodes.

[0138] Example 3

[0139] like Figure 6 , Figure 8 , Figure 9 and Figure 10 As shown in the embodiment of this application, a collaborative system for implementing inter-node collaborative operations includes:

[0140] At least one collaborative service engine, which belongs to at least the same collaborative job group, is used to perform collaborative jobs between nodes;

[0141] The client consists of at least two users, including a first user's client and a second user's client; the first user's client corresponds to a collaboration service engine and runs at least one collaboration application, and the second user's client corresponds to a collaboration service engine and runs at least one collaboration application.

[0142] Each of the aforementioned collaborative service engines includes:

[0143] The group business data synchronization interface is used to synchronize group business data when performing collaborative operations between nodes;

[0144] The group information data synchronization interface is used to synchronize group information data when performing collaborative operations between nodes;

[0145] The management interface is used to respond to the management operations performed by the first user or the second user through the client, and to update the stored group information data, business priority data, and / or the online status of each node during inter-node collaborative operations.

[0146] The query interface is used to respond to the query operation of the first user or the second user through the client and return the group business data or group information data processed during the inter-node collaborative operation to the client.

[0147] The heartbeat detection interface is used to detect the online status of the target node through heartbeat information;

[0148] The client of the first user or the client of the second user is configured with an interactive interface for collaborative work, to display the group information data or the group business data processed during collaborative work between nodes, and to receive user operations for any collaborative application through the interactive interface, and to respond to the operations by accessing the corresponding collaborative service engine to process the group information data or the group business data.

[0149] Thus, the collaborative system that enables inter-node collaborative operations responds to various operations initiated by the user through the client to the collaborative service engine, and provides various collaborative operation services to the user's client using the aforementioned method for enabling inter-node collaborative operations.

[0150] Example 4

[0151] like Figure 9 As shown, the node used to implement collaborative work in this embodiment of the application is equipped with the aforementioned collaborative system for implementing collaborative work between nodes, including a resource layer, a service layer, and an application layer:

[0152] The resource layer includes a database for storing grouped business data of collaborative operations between this node and other nodes; wherein, this node and other nodes belong to the same collaborative operation group.

[0153] The service layer includes the aforementioned collaborative service engine, which can access at least one collaborative server. The collaborative service engine is used to transmit grouped business data for inter-node collaborative operations between the application layer and the resource layer.

[0154] The application layer includes a user-operated client that can access at least one application server. The user-operated client is used to provide users with an interactive interface for collaborative work to display grouped business data of collaborative work between nodes, and to receive user operations through the interactive interface and respond to the operations to process the grouped business data of collaborative work between nodes.

[0155] The above describes a collaborative work architecture that uses a bottom-up approach, consisting of a resource layer, a service layer, and an application layer. These layers are loosely coupled; the resource layer provides data services to the service layer above it, and the service layer provides collaborative services to the application layer above it. This overall architecture enables collaborative data exchange, collaborative work grouping management, and collaborative process control. Thus, this collaborative work architecture can meet the collaborative work needs of multiple users for various applications.

[0156] To simplify collaborative workflows and enhance user experience, the client's interface includes at least one of the following: an interface for collaborative browsing, an interface for file sharing, an interface for electronic whiteboard, an interface for collaborative editing, an interface for application sharing, and a management interface.

[0157] As shown above, the multiple interactive interface functions displayed on the client are independent of each other, so the business logic is reasonable, the business content is clear, the operation is intuitive, and the user experience is more user-friendly.

[0158] In this way, by setting up collaborative operation engines on each node, collaborative operation among various services in the network environment is realized.

[0159] The above describes how the user-operated client provides an interactive interface for collaborative work, displays grouped business data for collaborative work between nodes, and receives collaborative work operations from users. The service layer processes the grouped business data for collaborative work between nodes and accesses the database set by the resource layer to achieve collaborative data exchange.

[0160] Thus, the node used to achieve collaborative operation has a more optimized architecture, more flexible bandwidth resource adaptation capability, and more reliable data transmission capability.

[0161] The aforementioned bottom-up collaborative work architecture, consisting of resource layer, service layer, and application layer, can meet the collaborative work needs of multiple users for various applications within or across domains.

[0162] Specifically, such as Figure 11 As shown, nodes within the same fixed office location form a collaborative work network within a domain. In this network, nodes are peers, and any node can belong to multiple collaborative work groups. Within the same collaborative work group, nodes are peer nodes. In this domain-wide mode, each node can independently set up a resource layer, service layer, and application layer, or each node can set up an independent application layer while sharing the same service and application layers. When performing domain-wide collaborative work, when accessing any collaborative application (e.g., Web access application server 10) through the application layer of a node (e.g., system user 01), it needs to access the collaborative service interface set up in the service layer (e.g., Web access collaborative server 20) through the node's application layer, and then access the group business data stored in the resource layer to complete the domain-wide collaborative work. Alternatively, it may also need to access the corresponding collaborative application (e.g., Web access application server 10) through the application layer of a node (e.g., system user 02) to access the group business data stored in the resource layer to complete the domain-wide collaborative work.

[0163] Specifically, such as Figure 6As shown, nodes within the same fixed office location form a collaborative work network within a domain; nodes in multiple fixed office locations can form multiple collaborative work networks within different domains, and nodes in multiple fixed office locations can form multiple cross-domain collaborative work networks. In intra-domain or cross-domain collaborative work networks, nodes are peers, and any node can belong to multiple collaborative work groups. Within the same collaborative work group, nodes are peer nodes to each other, such as nodes within the same collaborative work group within a domain; and nodes within the same collaborative work group across domains are peer nodes to each other. In cross-domain mode, nodes within a domain typically have independent application layers, while sharing the same service and application layers. Collaborative servers across multiple domains adopt a distributed deployment architecture. Accordingly, cross-domain collaborative work can be information exchange between multiple nodes or users in different collaborative work networks but belonging to the same collaborative work group.

[0164] When performing cross-domain collaborative operations, when accessing any collaborative application through the application layer of a node (such as system user 01) (such as accessing application server 11 in the first domain 1000 via the Web), it is necessary to access the collaborative service interface set by the service layer in this domain (such as accessing collaborative server 21 in the first domain via the Web), access the collaborative service interface set by the service layer in other domains (such as accessing collaborative server 22 in the second domain via the Web), and access the corresponding collaborative application in other domains through the application layer of a node (such as system user 02) (such as accessing application server 12 in the second domain 2000 via the Web), and then access the grouped business data stored in the resource layer in the first domain or the grouped business data stored in the resource layer in the second domain to complete the cross-domain collaborative operation.

[0165] To meet the collaborative work needs of multiple users for various applications within or across domains, the database also stores at least one of the following data: the online status of each node, used to record whether each node is online; the grouping information data of each node, used to record the collaborative work group to which each node belongs; the business priority data, used to mark the priority of the group business data for collaborative work; and the routing data of each node, used to realize the data transmission when synchronizing the group business data for inter-node collaborative work between the resource layers of each node.

[0166] Thus, the database serves as a fundamental supporting resource, and is comprehensively used for collaborative data exchange, collaborative task group management, and collaborative process control.

[0167] Specifically, the database can adopt the next-generation distributed database of DM, which supports more than 100 distributed nodes and adopts a variety of security hardening measures, including link and data encryption, identity recognition, access control, digital signature, intrusion detection, system hardening, audit trail, etc., which helps to improve system security and protect user information.

[0168] like Figure 8 and Figure 9 As shown, to meet the collaborative work needs of multiple users for various applications within or across domains, the group service data synchronization interface includes a real-time group service data synchronization interface and a static group service data synchronization interface, used for real-time synchronization of group service data and static synchronization of group service data, respectively. The management interface includes a group information management interface and a service priority management interface, used to update the group information data and / or service priority data of each node stored in the database. The query interface includes a group information data query interface and a group service data query interface, wherein the group information data query interface returns the queried group information data to the client, and the group information data query interface returns the queried group service data to the client.

[0169] To better provide controllable cross-domain collaborative work support capabilities in the network environment, and to support the collaborative work needs of multiple users for various applications within or across domains, such as... Figure 8 As shown, the collaborative service engine also includes a log monitoring module, a resource management module, and a system configuration module to monitor the usage of the collaborative service engine and the relevant parameters required by it. Specifically, the log monitoring module monitors the usage of the collaborative service engine and views its logs; the resource management module monitors the group business data and group information data stored in the database and cached in each collaborative service engine; and the system configuration module configures the basic information of the collaborative service engine, including setting the heartbeat detection time interval and the static data synchronization time interval. For example, the heartbeat detection is performed every hour, and the static data is synchronized every four hours.

[0170] Specifically, the list of interfaces provided by the collaborative service engine to each node is shown in Table 1.

[0171] Table 1. List of interfaces of the collaborative service engine set in the service layer

[0172]

[0173]

[0174] This collaborative service engine may include the following functions:

[0175] 1) Associated Node Status Management Function: Manages the online status of associated nodes through heartbeat detection;

[0176] 2) Static synchronization function for group data: Ensures the consistency of group data across the entire network by statically synchronizing group data between associated nodes;

[0177] 3) Real-time synchronization of grouped data: By synchronizing the grouped business data generated by the associated nodes in real time, the business data within the group is sent to the online associated nodes;

[0178] 4) Static synchronization function for group information: Static synchronization of group information data through associated nodes ensures the consistency of group information among associated nodes;

[0179] 5) Real-time synchronization of group information: By synchronizing group information data in real time, the addition, deletion, and modification of group data will be synchronized to the associated nodes in real time;

[0180] 6) Bandwidth detection function: Real-time detection of bandwidth between associated nodes (hereinafter referred to as associated nodes), and priority transmission of high-priority service data under low bandwidth conditions;

[0181] 7) Service priority management function: Provides an interface for setting service priorities, and prioritizes the synchronization of data with high service priority under low bandwidth conditions.

[0182] Thus, the collaborative service engine is set up behind the collaborative server, serving as the basic support for collaborative nodes and the collaborative system. It can provide the ability to distribute and share media data in a single fixed office location scenario or in multiple fixed office locations that are far apart, thereby realizing the functions required for collaborative office work, such as collaborative browsing, collaborative editing, file sharing, and electronic whiteboard.

[0183] The collaborative nodes and collaborative system constructed in this way support large-scale concurrent access by users in fixed office locations and multiple fixed office location network environments. The collaborative service engine carries the processing pressure of multimedia data such as files, audio and video for collaborative services, and provides collaborative process control and collaborative data management functions, which helps to save the bandwidth resources required for collaborative services.

[0184] like Figure 11 As shown, the administrator of the collaborative system uses the management interface to initiate management or configuration requests to the application server or collaborative server. It updates the group information data of each node stored in the database through the group information management interface and updates the service priority data stored in the database through the service priority management interface. For example, by setting the priority of a certain service, high-priority group service data can be transmitted first under low bandwidth conditions.

[0185] User operating system tools can initiate management requests, such as to the application server or collaboration server, and update the packet information data of each node stored in the database through the packet information management interface; or update the service priority data stored in the database through the service priority management interface. For example, by setting the priority of a certain service, packet service data with higher service priority can be transmitted first under low bandwidth conditions.

[0186] The user's operating system tool signature initiates a collaborative work request. For example... Figure 6 or Figure 10 As shown, at least one intra-domain collaboration server responds to the collaboration request, obtains routing data for each node, and connects the node corresponding to the user to the nearest intra-domain collaboration server and application server. The intra-domain collaboration server and application server then respond to the collaboration request and synchronize grouped business data for inter-node collaboration with the extra-domain collaboration servers and application servers corresponding to other nodes.

[0187] In summary, each collaborative node utilizes a Web service model to implement the aforementioned resource layer, service layer, and application layer. For example, a collaborative service engine can be developed based on the Web service model, and a B / S (Browser / Server) collaborative server can be deployed. Users can access the collaborative server via a web browser and access the database configured in the resource layer through the collaborative service engine. Furthermore, by using a distributed architecture collaborative server in a fixed office location or multiple fixed office locations, multiple collaborative nodes for cross-domain collaborative operations can be deployed.

[0188] Specifically, the aforementioned DM database runs on a Phytium processor or Loongson processor and a Linux operating system provided by Kylin OS, or on a Phytium processor or Loongson processor and a Linux operating system provided by Kylin OS. The communication module (such as mobile communication, fixed communication, or satellite communication), as a hardware resource, uses the unique short message communication technology of the BeiDou navigation module to synchronize various types of data in the database to associated nodes according to node routing data.

[0189] like Figure 12 As shown, the computing device 900 in this embodiment includes a processor 910, a memory 920, and may also include a communication interface 930. It should be understood that... Figure 12 The communication interface 930 in the computing device 900 shown can be used for communication with other devices. The processor 910 can be connected to the memory 920. The memory 920 can be used to store program code and data. Therefore, the memory 920 can be a storage unit inside the processor 910, an external storage unit independent of the processor 910, or a component including both internal storage units and external storage units independent of the processor 910.

[0190] Optionally, the computing device 900 may also include a bus. The memory 920 and communication interface 930 can be connected to the processor 910 via the bus. The bus can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into address bus, data bus, control bus, etc.

[0191] It should be understood that in the embodiments of this application, the processor 910 may be a Central Processing Unit (CPU). The processor may also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor. Alternatively, the processor 910 may employ one or more integrated circuits to execute relevant programs to implement the technical solutions provided in the embodiments of this application.

[0192] The memory 920 may include read-only memory and random access memory, and provides instructions and data to the processor 910. A portion of the processor 910 may also include non-volatile random access memory. For example, the processor 910 may also store device type information.

[0193] When the computing device 900 is running, the processor 910 executes the computer execution instructions in the memory 920 to perform the operation steps of the aforementioned method for implementing inter-node collaborative work, or is configured as the aforementioned collaborative service engine for implementing inter-node collaborative work.

[0194] It should be understood that the computing device 900 according to the embodiments of this application can correspond to the corresponding subject in executing the methods according to the various embodiments of this application, and the above and other operations and / or functions of each module in the computing device 900 are respectively for implementing the corresponding processes of the methods of this embodiment. For the sake of brevity, they will not be described in detail here.

[0195] The functions of the above devices can be implemented by a processor executing programs (software), or by hardware such as LSI (Large Scale Integration) and ASIC (Application Specific Integrated Circuit), or by a combination of software and hardware.

[0196] The terms “first, second, third, etc.” or similar terms such as module A, module B, and module C used throughout this application are only used to distinguish similar objects and do not represent a specific ordering of objects. It is understood that a specific order or sequence can be interchanged where permitted.

[0197] Throughout this application, the reference numerals for steps, such as S10, S20, etc., do not necessarily indicate that these steps will be performed. Where permissible, the order of the steps may be interchanged or performed simultaneously.

[0198] The term "comprising" as used throughout this application should not be construed as limiting itself to the contents listed below; it does not exclude other structural elements or steps. Therefore, it should be interpreted as specifying the presence of the mentioned technical features, integrals, steps, or components, but does not exclude the presence or addition of one or more other technical features, integrals, steps, or components and groups thereof.

[0199] It is understood that those skilled in the art can combine the features mentioned in one or more embodiments throughout this application with features from other embodiments in any appropriate manner to implement this application.

[0200] Note that the foregoing are merely preferred embodiments and the technical principles employed in this application. Those skilled in the art will understand that this application is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of this application. Therefore, although this application has been described in detail through the above embodiments, this application is not limited to the above embodiments. Many other equivalent embodiments may be included without departing from the technical concept of this application, all of which fall within the scope of protection of this application.

Claims

1. A method for realizing collaborative work between nodes, characterized in that, include: The first node synchronizes group information data with the second node; When the first node and the second node belong to the same collaborative operation group after synchronization, the first node and the second node synchronize the group business data. The first node displays the synchronized group service data to the user's client. The packet information data or packet service data includes stored static data or cached real-time data; The synchronization of packet information data or packet service data between the first node and the second node includes: the first node and the second node performing synchronization of the stored static data; and the first node and the second node performing synchronization of the cached real-time data. The first node and the second node perform real-time data synchronization of the cache, including: The cached real-time data is divided into at least two parts, which include a first part of data and a second part of data; The synchronization of the real-time data in the cache includes: When operating on the first part of the data of the first node, and when there is no record of locking the first part of the data, the first part of the data is cached; When the first part of the data on the first node is operated on, and the second part of the data is locked by the second node, the first part of the data is cached, and the second part of the data is synchronized from the second node to the first node, wherein the second part of the data being locked by the second node indicates that the second part of the data on the second node is operated on. When the first part of the data on the first node is operated on, and the first part of the data is locked, the first part of the data is synchronized from the second node to the first node, the first part of the data is processed and cached in response to the operation, and the locking of the first part of the data indicates that the first part of the data on the second node has been operated on.

2. The method according to claim 1, characterized in that, The first node synchronizes packet information data or packet service data with the second node, including: The first node sends the packet information data version or the packet service data version to the second node; When the first node receives a response message from the second node, it sends packet information data or packet service data to the second node so that the second node updates its stored packet information data or packet service data; wherein, the response message is a message sent by the second node when it determines that the version of the packet information data or the version of the packet service data is higher than the version stored by the second node.

3. The method according to claim 1, characterized in that, The first node synchronizes packet information data or packet service data with the second node, including: The first node obtains the packet information data version or the packet service data version from the second node; When the first node determines that the version of the packet information or the version of the packet service data is higher than the version stored by the first node, it obtains the packet information data or the packet service data from the second node. The first node updates its stored packet information data or packet service data based on the acquired packet information data or packet service data.

4. The method according to claim 2, characterized in that, Before the first node synchronizes packet information data or packet service data with the second node, the process also includes: The first node detects the online status of the second node through heartbeat information.

5. A collaborative service engine for enabling collaborative operations between nodes, characterized in that, include: The group business data synchronization interface is used to synchronize group business data when performing collaborative operations between nodes; The group information data synchronization interface is used to synchronize group information data when performing collaborative operations between nodes; The management interface is used to respond to user management operations through the client, and update the stored group information data, business priority data, and / or the online status of each node during inter-node collaborative operations; The query interface is used to respond to user queries through the client and return the queried group business data or group information data processed during inter-node collaborative operations to the client. The heartbeat detection interface is used to detect the online status of the target node through heartbeat information; The packet information data or packet service data includes stored static data or cached real-time data; The packet information data synchronization interface and the packet service data synchronization interface are specifically used for synchronizing packet information data or packet service data between the first node and the second node, including: the first node and the second node performing synchronization of the stored static data; the first node and the second node performing synchronization of the cached real-time data; The first node and the second node perform real-time data synchronization of the cache, including: The cached real-time data is divided into at least two parts, which include a first part of data and a second part of data; The synchronization of the real-time data in the cache includes: When operating on the first part of the data of the first node, and when there is no record of locking the first part of the data, the first part of the data is cached; When the first part of the data on the first node is operated on, and the second part of the data is locked by the second node, the first part of the data is cached, and the second part of the data is synchronized from the second node to the first node, wherein the second part of the data being locked by the second node indicates that the second part of the data on the second node is operated on. When the first part of the data on the first node is operated on, and the first part of the data is locked, the first part of the data is synchronized from the second node to the first node, the first part of the data is processed and cached in response to the operation, and the locking of the first part of the data indicates that the first part of the data on the second node has been operated on.

6. A collaborative system for realizing inter-node collaborative operations, characterized in that, include: At least one collaborative service engine as described in claim 5, wherein at least one of the collaborative service engines belongs to at least the same collaborative job group and is used to perform inter-node collaborative jobs; The client consists of at least two users, including a first user's client and a second user's client; the first user's client corresponds to a collaboration service engine and runs at least one collaboration application, and the second user's client corresponds to a collaboration service engine and runs at least one collaboration application. The client of the first user or the client of the second user is configured with an interactive interface for collaborative work, to display the group information data or the group business data processed during collaborative work between nodes, and to receive user operations for any collaborative application through the interactive interface, and to respond to the operations by accessing the corresponding collaborative service engine to process the group information data or the group business data.

7. A computing device, characterized in that, include: A processor and a memory, the memory storing program instructions that, when executed by the processor, cause the processor to perform the method for implementing inter-node collaborative work as described in any one of claims 1 to 4.

8. A storage medium, characterized in that, The storage medium stores program instructions that, when executed by a processor, cause the processor to perform the method for implementing inter-node collaborative work as described in any one of claims 1 to 4.

Citation Information

Patent Citations

  • Concurrent conflict and permission processing method for cooperative grouping through multiple clients

    CN104980513A

  • Method for service object synchronization, client, and server

    CN106161629A