CN111159141A - Decentralized distributed data synchronization method, distributed node and system - Google Patents
Decentralized distributed data synchronization method, distributed node and system Download PDFInfo
- Publication number
- CN111159141A CN111159141A CN202010001878.2A CN202010001878A CN111159141A CN 111159141 A CN111159141 A CN 111159141A CN 202010001878 A CN202010001878 A CN 202010001878A CN 111159141 A CN111159141 A CN 111159141A
- Authority
- CN
- China
- Prior art keywords
- request
- data
- distributed
- node
- synchronous
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2308—Concurrency control
- G06F16/2336—Pessimistic concurrency control approaches, e.g. locking or multiple versions without time stamps
- G06F16/2343—Locking methods, e.g. distributed locking or locking implementation details
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5083—Techniques for rebalancing the load in a distributed system
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Software Systems (AREA)
- Computer Security & Cryptography (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention belongs to the field of distributed storage, and discloses a decentralized distributed data synchronization method, distributed nodes and a decentralized distributed data synchronization system. The method comprises the following steps: by monitoring the load of the distributed nodes, the relatively idle nodes are automatically selected as the initiating end of the synchronous request, the effectiveness judgment and the preprocessing of data writing and the distribution of synchronous information are carried out, the data processing capacity of the whole system is improved, and the usability and the flexibility are enhanced; the design adopts a synchronous mode based on a request/response structure, and the whole process of request sending, data writing and result feedback between a synchronous initiating terminal and a response terminal can be realized only by once interaction. The method can efficiently and reliably finish the distribution, processing and feedback of the synchronous information among the distributed nodes, and achieves the aim of real-time synchronization of system data.
Description
Technical Field
The invention belongs to the field of distributed storage, and relates to a distributed data synchronization method, distributed nodes and a distributed data synchronization system.
Background
With the rapid development of network and information technology, the distributed technology is mature day by day, and the application of the distributed system is wider and wider. In a distributed system, how to realize real-time sharing of information among distributed nodes and guarantee data consistency of the system are always a hotspot problem in the field.
Nowadays, most distributed systems still adopt a centralized design concept, that is, the operation of the whole system is coordinated and controlled through a central node, the biggest problem of the distributed systems lies in the safety and the bottleneck problem of the central node, and if the central node has a problem, the normal operation of the whole system is directly influenced.
Therefore, the probability of failure of the distributed system is high at present. Therefore, how to improve the performance and fault tolerance of the system on the premise of ensuring the consistency of the system data is a difficult problem which is always expected to be solved in the field.
Disclosure of Invention
The invention aims to improve the performance and fault tolerance of the distributed system on the premise of ensuring the data consistency of the distributed system. Therefore, the decentralized distributed data synchronization method provided by the invention can efficiently and reliably complete the distribution, processing and feedback of synchronization information among distributed nodes, and achieves the purpose of real-time synchronization of system data.
The technical scheme of the invention is as follows:
in the decentralized distributed data synchronization method, all nodes of a distributed system are peer-to-peer (namely, the distributed system can be used as a synchronization initiating end and a synchronization responding end); the data synchronization method comprises the following steps:
receiving a request for writing data by an external application call interface;
selecting a relatively idle node as an initiating end of a synchronous request, and acquiring a distributed lock corresponding to the data; the other nodes of the distributed system are all used as receiving ends of the synchronous requests;
the initiating end extracts and codes information, encapsulates the information into synchronous request information, distributes the synchronous request information to all receiving ends, and completes the synchronous task of the data based on the synchronous mode of a request/response structure;
and releasing the lock after the synchronization task of the data is finished.
Based on the above scheme, the invention further optimizes as follows:
optionally, the relatively idle node is selected by a load balancing policy.
Optionally, before information extraction and encoding, the initiating end verifies the validity of the external request, including whether the request is legal or not and whether node data is affected or not; only if the external request for the piece of data is confirmed to be valid, the subsequent data synchronization process is performed.
Optionally, the synchronization pattern based on the "request/response" structure is:
(1) the initiating terminal sends the encapsulated synchronous request message to the receiving terminal and waits for result feedback;
(2) the receiving end keeps message monitoring and sets corresponding event processing, analyzes and decodes the request to realize corresponding data operation, generates feedback information according to the operation result, encapsulates the feedback information in the response message and returns the response message to the initiating end;
(3) and after receiving the result feedback of all the nodes, the initiating end analyzes and returns the synchronous result.
Correspondingly, the invention also provides a node of the decentralized distributed system, which comprises a processor and a computer readable storage medium, wherein the computer readable storage medium stores a computer program for realizing distributed data synchronization; the computer program is loaded by a processor to perform the steps of:
step a, when a request for writing data by an external application call interface is received, responding to the request for writing data; or directly from step b (corresponding to the case where other nodes of the distributed system receive requests to write data);
b, confirming the node as an initiating end or a receiving end of the synchronous request; if the request is confirmed to be the initiating end of the synchronous request; the following step c 1-step c6 are performed; if the synchronous request is confirmed to be the receiving end of the synchronous request, the following steps d1-d3 are executed;
step c1, analyzing the data writing request from outside, and obtaining the distributed lock corresponding to the data from the lock center according to the request;
c2, if the lock is successfully obtained, writing the data into the node database; if the lock acquisition fails, waiting;
step c3, the node recodes the data writing request, packages the data writing request into a synchronous request message and distributes the synchronous request message to other distributed nodes in the system;
step c4, setting monitoring and waiting for response messages of other distributed nodes;
step c5, receiving response messages which indicate that the synchronization is successful and are returned by all other distributed nodes; if any node does not respond or the response message shows a synchronization error, reporting error information of the corresponding node to an upper layer;
step c6, releasing the lock;
d1, monitoring the synchronous request, if there is a data synchronous request, reading the data and triggering the corresponding event;
d2, decoding the data synchronization request, and writing the data into the local node database according to the requirement;
and d3, generating local synchronous feedback information, encapsulating the local synchronous feedback information into a response message and returning the response message to the synchronous initiating terminal.
Optionally, step b determines that the node is used as an initiating end or a receiving end of the synchronization request, specifically, the load of all distributed nodes is monitored by the load balancing server, a relatively idle node is selected as the initiating end of the synchronization request, and the other nodes of the distributed system are all used as the receiving ends of the synchronization request.
Optionally, step c1, after parsing the data write request from outside, verifies the validity of the request, including whether the request is legal or not, and whether the node data is affected or not; the distributed lock corresponding to the piece of data is acquired to the lock center only if the external request for the piece of data is validated.
Optionally, the response message in step d3 includes the identification information of the node and the synchronization result.
Optionally, step c6 also records data change information in the local log after releasing the lock; step d2 also records data synchronization information in local log after writing data into the local node database.
Correspondingly, the invention also provides a decentralized distributed system, which comprises:
a plurality of distributed nodes having links established for communication with each other; each distributed node is a node of the decentralized distributed system;
the load balancing server is used for monitoring the load of all the distributed nodes, selecting relatively idle nodes as an initiating end of a synchronous request when receiving a request for writing data by an external application calling interface, and taking the other nodes of the distributed system as receiving ends of the synchronous request;
and the lock center is used for responding to the request of the distributed node, granting the requested distributed lock to the distributed node, and releasing the lock after the distributed node completes the task.
Compared with the prior art, the invention has the following advantages:
the invention adopts decentralized design, the whole distributed system has no central node, all nodes are equal, therefore, the failure of any node in the distributed system only affects the function in a very small range, the problems of performance bottleneck and single point failure do not exist, and the invention has better usability.
The invention realizes the automatic selection of the synchronous initiating terminal, not only can improve the data processing capacity of the whole system, but also can adapt to the dynamic change of the whole environment and enhance the availability and the flexibility of the system; in addition, the invention also designs a synchronization mode based on a 'request/response' structure, can realize the distribution, processing and feedback of the synchronization information among the nodes only by one-time interaction, and provides high-efficiency and reliable data real-time synchronization.
Drawings
FIG. 1 is a schematic decentralized distributed data synchronization process of an embodiment.
FIG. 2 is a flow diagram illustrating a synchronization pattern based on a "request/response" structure, according to an embodiment.
FIG. 3 is a decentralized, distributed system infrastructure of one embodiment.
Detailed Description
The present invention will be described in detail below by way of examples with reference to the accompanying drawings.
The decentralized distributed data synchronization method provided by this embodiment mainly includes two parts, namely, an automatic selection at a synchronization initiator and a synchronization mode based on a "request/response" structure, and the overall flow is as shown in fig. 1.
When the external application calls the interface to write data into the distributed nodes, the appropriate distributed nodes are selected through a load balancing strategy to carry out data preprocessing and initiate a synchronization request, and the other nodes respond to the synchronization request, so that corresponding data operation is realized, and data synchronization is completed. In particular, it relates to
1. Decentralization: in this embodiment, there is no central node, and each valid node is peer-to-peer, that is, it may be used as a synchronization initiating end or a synchronization responding end.
2. Automatic selection of the synchronization initiator: by monitoring the load of the distributed nodes, the nodes which are relatively idle are automatically selected as the initiating end of the synchronous request, the effectiveness judgment and the preprocessing of data writing are carried out, the data processing capacity of the whole system is improved, and the availability and the flexibility of the system are enhanced. Since the primary purpose of distributed data synchronization is to achieve data consistency of the whole system, no matter which node in the system initiates a synchronization request, data consistency can be achieved as long as the rest nodes can complete synchronization operation within a specified time as required. When an external request is received, the data is preprocessed by a relatively idle distributed node according to the load balancing strategy evaluation set by the system: and judging the validity of the external request (whether the request is legal or not, whether node data is influenced or not and the like), then extracting and coding information, packaging the information into a synchronous request and distributing the synchronous request to other nodes. Here, the selection of the load balancing policy may be implemented by setting a special load balancing server to select a relatively idle node as an initiator of the synchronization request, or by a plurality of nodes to determine the initiator of the synchronization request according to the load balancing policy operation.
3. Synchronization patterns based on the "request/response" structure: the main structure is as shown in fig. 2, (1) the synchronization initiating end encodes the synchronization information, encapsulates the synchronization information into a 'request message' and sends the 'request message' to the other distributed nodes to be synchronized in the network, and waits for the result to be fed back; (2) the synchronous receiving end keeps message monitoring and sets corresponding event processing, analyzes and decodes the request to realize corresponding data operation, generates feedback information according to the operation result, encapsulates the feedback information in a response message and returns the response message to the request initiating end; (3) and after receiving the result feedback of all the nodes, the synchronous initiating end analyzes and returns the synchronous result. Through the mode, the synchronous request initiating node can receive synchronous processing results of all other distributed nodes only by one-time request distribution operation, and positions the nodes with synchronous failure and error information, namely, the whole process of request sending, data writing and result feedback between the synchronous initiating terminal and the response terminal can be realized only by one-time interaction.
Accordingly, the present embodiment establishes a decentralized distributed system, as shown in fig. 3.
The operation of the "synchronization initiator" and the "synchronization receiver" is described in further detail below. The 'synchronization initiating end' can be any one node in the distributed system, and the rest nodes are all used as 'synchronization receiving ends'.
At the synchronization initiation end:
step 1, analyzing a data writing request from the outside;
step 2, the node verifies the validity of the request; for example, sometimes parsing data requires modifying or deleting a piece of data that does not already exist, the distributed system does not need to respond to the write request; of course, if there is already a corresponding interpretation mechanism outside the distributed system, this step can be omitted;
step 3, if the request is valid, acquiring a distributed lock corresponding to the data from the lock center according to the write request; if the request is invalid, returning immediately;
step 4, the lock is successfully acquired (that is, only the node has the authority to execute the synchronization of the data at present, if other nodes receive the write-in request of the same data from the outside at the moment, the node must wait for the current synchronization task to be executed), and the data is written into the node database; if the lock acquisition fails, waiting;
step 5, the node recodes the data writing request (mainly because the external request may be in a different data format from the internal communication of the distributed system), encapsulates the data writing request into a request message (containing the synchronous request and corresponding data) and distributes the request message to the rest distributed nodes in the system;
step 6, setting monitoring and waiting for response messages of other distributed nodes;
step 7, all other distributed nodes return response messages indicating successful synchronization; if any node does not respond (waiting for overtime) or the response message shows a synchronization error, reporting error information of the corresponding node to an upper layer;
step 8, releasing the lock;
and 9, recording data change information by the local log.
At the synchronous responding end:
step 1, monitoring a synchronous request, and if a data synchronous request exists, reading data and triggering a corresponding event;
step 2, decoding the data synchronization request, and writing the data into a node database according to the request;
step 3, recording data synchronization information by a local log;
and 4, generating local synchronous feedback information, encapsulating the local synchronous feedback information into a response message and returning the response message to the synchronous initiating terminal. The response message here includes at least the information of the own node (node IP) and the synchronization result (success or failure).
Claims (10)
1. A decentralized distributed data synchronization method is characterized in that all nodes of a distributed system are peer-to-peer; the data synchronization method comprises the following steps:
receiving a request for writing data by an external application call interface;
selecting a relatively idle node as an initiating end of a synchronous request, and acquiring a distributed lock corresponding to the data; the other nodes of the distributed system are all used as receiving ends of the synchronous requests;
the initiating end extracts and codes information, encapsulates the information into synchronous request information, distributes the synchronous request information to all receiving ends, and completes the synchronous task of the data based on the synchronous mode of a request/response structure;
and releasing the lock after the synchronization task of the data is finished.
2. The decentralized distributed data synchronization method according to claim 1, wherein: and selecting the relatively idle node through a load balancing strategy.
3. The decentralized distributed data synchronization method according to claim 1, wherein: before information extraction and coding, an initiating terminal verifies the validity of an external request, including whether the request is legal or not and whether node data is influenced or not; only if the external request for the piece of data is confirmed to be valid, the subsequent data synchronization process is performed.
4. The decentralized distributed data synchronization method according to claim 1, wherein: the synchronization pattern based on the "request/response" structure is:
(1) the initiating terminal sends the encapsulated synchronous request message to the receiving terminal and waits for result feedback;
(2) the receiving end keeps message monitoring and sets corresponding event processing, analyzes and decodes the request to realize corresponding data operation, generates feedback information according to the operation result, encapsulates the feedback information in the response message and returns the response message to the initiating end;
(3) and after receiving the result feedback of all the nodes, the initiating end analyzes and returns the synchronous result.
5. A node of a decentralized distributed system, comprising a processor and a computer readable storage medium storing a computer program for implementing distributed data synchronization; wherein the computer program is loaded by a processor to perform the steps of:
step a, when a request for writing data by an external application call interface is received, responding to the request for writing data; or directly from step b;
b, confirming the node as an initiating end or a receiving end of the synchronous request; if the request is confirmed to be the initiating end of the synchronous request; the following step c 1-step c6 are performed; if the synchronous request is confirmed to be the receiving end of the synchronous request, the following steps d1-d3 are executed;
step c1, analyzing the data writing request from outside, and obtaining the distributed lock corresponding to the data from the lock center according to the request;
c2, if the lock is successfully obtained, writing the data into the node database; if the lock acquisition fails, waiting;
step c3, the node recodes the data writing request, packages the data writing request into a synchronous request message and distributes the synchronous request message to other distributed nodes in the system;
step c4, setting monitoring and waiting for response messages of other distributed nodes;
step c5, receiving response messages which indicate that the synchronization is successful and are returned by all other distributed nodes; if any node does not respond or the response message shows a synchronization error, reporting error information of the corresponding node to an upper layer;
step c6, releasing the lock;
d1, monitoring the synchronous request, if there is a data synchronous request, reading the data and triggering the corresponding event;
d2, decoding the data synchronization request, and writing the data into the local node database according to the requirement;
and d3, generating local synchronous feedback information, encapsulating the local synchronous feedback information into a response message and returning the response message to the synchronous initiating terminal.
6. The node of the decentralized distributed system according to claim 5, wherein:
and b, confirming that the node is used as an initiating end or a receiving end of the synchronous request, specifically, monitoring the load of all distributed nodes through a load balancing server, selecting relatively idle nodes as the initiating end of the synchronous request, and using the rest nodes of the distributed system as the receiving ends of the synchronous request.
7. The node of the decentralized distributed system according to claim 5, wherein:
step c1, after analyzing the data write request from outside, verifying the validity of the request, including whether the request is legal or not and whether the node data is affected or not; the distributed lock corresponding to the piece of data is acquired to the lock center only if the external request for the piece of data is validated.
8. The node of the decentralized distributed system according to claim 5, wherein: the response message in step d3 includes the identification information of the own node and the synchronization result.
9. The node of the decentralized distributed system according to claim 5, wherein:
step c6 also records data change information in the local log after releasing the lock;
step d2 also records data synchronization information in local log after writing data into the local node database.
10. A decentralized, distributed system, comprising:
a plurality of distributed nodes having links established for communication with each other; each distributed node is a node of the decentralized distributed system according to claim 5;
the load balancing server is used for monitoring the load of all the distributed nodes, selecting relatively idle nodes as an initiating end of a synchronous request when receiving a request for writing data by an external application calling interface, and taking the other nodes of the distributed system as receiving ends of the synchronous request;
and the lock center is used for responding to the request of the distributed node, granting the requested distributed lock to the distributed node, and releasing the lock after the distributed node completes the task.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010001878.2A CN111159141A (en) | 2020-01-02 | 2020-01-02 | Decentralized distributed data synchronization method, distributed node and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010001878.2A CN111159141A (en) | 2020-01-02 | 2020-01-02 | Decentralized distributed data synchronization method, distributed node and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111159141A true CN111159141A (en) | 2020-05-15 |
Family
ID=70561125
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010001878.2A Pending CN111159141A (en) | 2020-01-02 | 2020-01-02 | Decentralized distributed data synchronization method, distributed node and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111159141A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112035164A (en) * | 2020-09-03 | 2020-12-04 | 中国银行股份有限公司 | Method for updating node configuration of distributed system, application node and control node |
| CN114390007A (en) * | 2021-12-23 | 2022-04-22 | 西安诺瓦星云科技股份有限公司 | Data processing method, device, storage medium and processor |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120284229A1 (en) * | 2011-04-13 | 2012-11-08 | Kim Mi-Jeom | Selecting data nodes in distributed storage system |
| CN104486319A (en) * | 2014-12-09 | 2015-04-01 | 上海爱数软件有限公司 | Real-time synchronization method and real-time synchronization system for configuration file applied to high-availability system |
| CN107295080A (en) * | 2017-06-19 | 2017-10-24 | 北京百度网讯科技有限公司 | Date storage method and server applied to distributed server cluster |
| CN108763339A (en) * | 2018-05-14 | 2018-11-06 | 北京辰森世纪科技股份有限公司 | Synchronous method, device and the equipment of database data |
| CN110225087A (en) * | 2019-05-08 | 2019-09-10 | 平安科技（深圳）有限公司 | Cloud access method, device and storage medium based on global load balancing |
| CN110515733A (en) * | 2019-08-26 | 2019-11-29 | 江苏华库数据技术有限公司 | A method of reducing large scale database cluster DML resource consumption |
| CN110633046A (en) * | 2018-06-22 | 2019-12-31 | 北京东土科技股份有限公司 | Storage method and device of distributed system, storage equipment and storage medium |
-
2020
- 2020-01-02 CN CN202010001878.2A patent/CN111159141A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120284229A1 (en) * | 2011-04-13 | 2012-11-08 | Kim Mi-Jeom | Selecting data nodes in distributed storage system |
| CN104486319A (en) * | 2014-12-09 | 2015-04-01 | 上海爱数软件有限公司 | Real-time synchronization method and real-time synchronization system for configuration file applied to high-availability system |
| CN107295080A (en) * | 2017-06-19 | 2017-10-24 | 北京百度网讯科技有限公司 | Date storage method and server applied to distributed server cluster |
| CN108763339A (en) * | 2018-05-14 | 2018-11-06 | 北京辰森世纪科技股份有限公司 | Synchronous method, device and the equipment of database data |
| CN110633046A (en) * | 2018-06-22 | 2019-12-31 | 北京东土科技股份有限公司 | Storage method and device of distributed system, storage equipment and storage medium |
| CN110225087A (en) * | 2019-05-08 | 2019-09-10 | 平安科技（深圳）有限公司 | Cloud access method, device and storage medium based on global load balancing |
| CN110515733A (en) * | 2019-08-26 | 2019-11-29 | 江苏华库数据技术有限公司 | A method of reducing large scale database cluster DML resource consumption |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112035164A (en) * | 2020-09-03 | 2020-12-04 | 中国银行股份有限公司 | Method for updating node configuration of distributed system, application node and control node |
| CN114390007A (en) * | 2021-12-23 | 2022-04-22 | 西安诺瓦星云科技股份有限公司 | Data processing method, device, storage medium and processor |
| CN114390007B (en) * | 2021-12-23 | 2024-03-15 | 西安诺瓦星云科技股份有限公司 | Data processing method, device, storage medium and processor |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2016184175A1 (en) | Database processing method and apparatus | |
| TWI678909B (en) | Safety authentication method, device and system | |
| CN111010305A (en) | Configuration management system and method based on NETCONF protocol | |
| CN102420805B (en) | Method, system and device for communication by virtue of socket connection | |
| CN111159141A (en) | Decentralized distributed data synchronization method, distributed node and system | |
| CN110210845B (en) | Method, apparatus, medium, and computing device for blockchain data migration | |
| CN111552568B (en) | Cloud service calling method and device | |
| CN106027534A (en) | System for implementing financial message processing based on Netty | |
| CN111917737A (en) | Cross-network RPC calling system and method | |
| CN101953188B (en) | Method and apparatus for processing multi-channel request subscription under service management platform | |
| CN113221093A (en) | Single sign-on system, method, equipment and product based on block chain | |
| CN102137102B (en) | Realizing method of service supporting platform for supporting multiclass information publishing modes | |
| CN114301988A (en) | Distributed calling method and device, storage medium and electronic equipment | |
| CN1972276A (en) | A management method and system for protocol access | |
| CN115098528B (en) | Service processing method, device, electronic equipment and computer readable storage medium | |
| CN112636959B (en) | Network slice privacy number service guarantee system and method for distinguishing service types | |
| CN105245579B (en) | A kind of distribution network system mass data Communication processing method and system | |
| CN113949728A (en) | Method for synchronizing different platform devices, first platform and second platform | |
| CN114422558A (en) | Data message conversion self-description protocol MQTT method based on container edge proxy | |
| CN102137083B (en) | Method, device and system for registering application system | |
| CN107528797B (en) | Data processing method, device and system | |
| CN110572430A (en) | identity data synchronization system and method based on timing task | |
| CN1332531C (en) | A method for dynamically adjusting system service performance on service management point | |
| CN112383886B (en) | Subscription data synchronization method and device of LTE B-Trunc system | |
| CN117478504B (en) | Information transmission method, device, terminal equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |