CN108710557B - Method and system for judging data consistency of distributed software program - Google Patents
Method and system for judging data consistency of distributed software program Download PDFInfo
- Publication number
- CN108710557B CN108710557B CN201810362576.0A CN201810362576A CN108710557B CN 108710557 B CN108710557 B CN 108710557B CN 201810362576 A CN201810362576 A CN 201810362576A CN 108710557 B CN108710557 B CN 108710557B
- Authority
- CN
- China
- Prior art keywords
- data
- program
- programs
- distributed software
- point
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 26
- 230000004048 modification Effects 0.000 description 7
- 238000012986 modification Methods 0.000 description 7
- 230000003993 interaction Effects 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Computer Hardware Design (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a method and a system for judging data consistency of a distributed software program, and relates to the field of software programs. The method comprises the following steps: numbering data acquired from the outside, associating all modified data associated with the data with the number of the data when the distributed software program processes the data, and determining a starting point program, an intermediate point program and an end point program for processing the data; and judging the relevance and integrity of the data among the distributed software programs by verifying whether the processing chain of the data related to a certain number from the starting point program, the intermediate point program to the end point program is complete. The invention can quickly determine the consistency and difference of data among programs without mutual calculation among the programs.
Description
Technical Field
The invention relates to the field of software programs, in particular to a method and a system for judging data consistency of a distributed software program.
Background
Current programs are more and more complex, and multi-thread and distributed programs are common, so that data of each part needs to be subjected to consistency judgment, that is, whether the data are the same or not is judged, because the data are lost due to some factors during transmission, for example: the network is suddenly disconnected, so that data at the two transmitting and receiving ends are inconsistent, and the data are difficult to be inconsistent, because the distributed program is assumed to be composed of N programs, N is greater than 1, N is a positive integer, if the N programs are all processing services and each program is processing different services, M programs are suddenly broken down, M is less than N, and M is a positive integer, and then the broken programs are restored to operate by means of backup data, at the moment, how to judge which service data are influenced, namely, which part of data among the N programs are still consistent, or how to judge which service data are damaged and which are complete.
When a software program is multi-threaded or distributed, it is difficult to judge the data consistency between distributed programs, and how to simply judge the damage degree of program data is an important aspect, and it is necessary to know which data are damaged before effective countermeasures can be taken.
Some software solutions at present check data among services to determine which data is lost and which data is complete, and when there are many programs, the comparison is very complicated, for example: if the N programs have business interactions with each other, the amount of data computation will be of the order of N (N-1), which is very large even if the corrupted business data is computed.
Disclosure of Invention
The present invention is directed to overcome the above-mentioned shortcomings in the prior art, and provides a method and a system for determining the consistency of distributed software program data, which can quickly determine where the consistency and difference of data between programs are located without mutual calculation between programs.
The invention provides a method for judging the consistency of distributed software program data, which comprises the following steps:
s1, numbering the data acquired from the outside, and when the distributed software program processes the data, associating all the modified data associated with the data with the number of the data, and determining a starting point program, a middle point program and an end point program for processing the data;
s2, judging the relevance and integrity of the data among the distributed software programs by checking whether the processing chain of the data related to a certain number from the starting point program, the intermediate point program to the end point program is complete or not;
step S1 specifically includes the following steps:
when the distributed software program processes data acquired from the outside, numbering the data; when all programs transmit modified data associated with the data to other services, the modified data carry the serial number of the data, and the programs are marked as starting programs of the data;
when the other programs receive the modified data which is sent by the starting program and is associated with the data, the serial numbers of the data are used; the other programs finish processing the modified data associated with the data, and if the data associated with the data is continuously transmitted to the other programs, the program is marked as a middle point program of the data; if the data associated with the data is no longer being passed to other programs, the program is marked as the end program for the data.
In addition to the above-described technical means, when the data acquired from the outside is numbered in step S1, the number is incremented without overlapping each other between the start point programs in the system.
Based on the above technical solution, in step S1, when the data obtained from the outside is numbered, the new number is used only when the external data is directly received.
On the basis of the above technical solution, step S2 specifically includes the following steps:
if the data associated with a certain number has a corresponding starting point program, all intermediate point programs and ending point programs in a processing chain in the system, the data associated with the certain number is considered to be completely processed, the data is complete, and otherwise, the data is considered to be incomplete.
The invention also provides a system for judging the data consistency of the distributed software program, which comprises an association marking unit and a data integrity judging unit, wherein:
the association flag unit is used for: numbering data acquired from the outside, associating all modified data associated with the data with the number of the data when the distributed software program processes the data, and determining a starting point program, an intermediate point program and an end point program for processing the data;
the data integrity judgment unit is used for: judging the relevance and integrity of data among distributed software programs by verifying whether a processing chain of data related to a certain number from a starting point program, an intermediate point program to a terminal point program is complete or not;
the association flag unit is specifically configured to:
when the distributed software program processes data acquired from the outside, numbering the data; when all programs transmit modified data associated with the data to other services, the modified data carry the serial number of the data, and the programs are marked as starting programs of the data;
when the other programs receive the modified data which is sent by the starting program and is associated with the data, the serial numbers of the data are used; the other programs finish processing the modified data associated with the data, and if the data associated with the data is continuously transmitted to the other programs, the program is marked as a middle point program of the data; if the data associated with the data is no longer being passed to other programs, the program is marked as the end program for the data.
In the above-described aspect, when the association flag unit numbers data acquired from the outside, the numbers are not overlapped with each other and are incremented between starting point programs in the system.
On the basis of the technical scheme, when the association marking unit numbers the data acquired from the outside, the new number is used only when the external data is directly received.
On the basis of the above technical solution, the data integrity determination unit is specifically configured to:
if the data associated with a certain number has a corresponding starting point program, all intermediate point programs and ending point programs in a processing chain in the system, the data associated with the certain number is considered to be completely processed, the data is complete, and otherwise, the data is considered to be incomplete.
Compared with the prior art, the invention has the following advantages:
the method comprises the steps of numbering data acquired from the outside, associating all modified data associated with the data with the number of the data when a distributed software program processes the data, and determining a starting point program, an intermediate point program and an end point program for processing the data; and judging the relevance and integrity of the data among the distributed software programs by verifying whether the processing chain of the data related to a certain number from the starting point program, the intermediate point program to the end point program is complete. The invention can easily judge the integrity of the data among the programs in a certain system by judging the number of the external data and the starting point program, the intermediate point program and the end point program corresponding to the number. When determining whether the data between the programs is complete, the mutual calculation between the programs is not needed, and the data difference between the programs can be quickly calculated.
Drawings
Fig. 1 is a flowchart of a method for determining data consistency of distributed software programs according to an embodiment of the present invention.
FIG. 2 is a diagram illustrating processing paths of external data in the system according to an embodiment of the present invention.
Detailed Description
The invention is described in further detail below with reference to the figures and the embodiments.
Example 1
Referring to fig. 1, embodiment 1 of the present invention provides a method for determining data consistency of a distributed software program, including the following steps:
s1, numbering the data acquired from the outside, and when the distributed software program processes the data, associating all the modified data associated with the data with the number of the data, and determining a starting point program, a middle point program and an end point program for processing the data;
and S2, judging the relevance and integrity of the data among the distributed software programs by verifying whether the processing chain of the data related to a certain number from the starting point program, the intermediate point program to the end point program is complete.
In step S1, when the data acquired from the outside is numbered, the number is incremented without overlapping each other between the start point programs in the system. Only when external data is directly received, the new number is used.
Example 2
The embodiment 2 of the invention provides a method for judging the consistency of distributed software program data, which comprises the following steps:
when the distributed software program processes data acquired from the outside, numbering the data; when all programs transmit modified data associated with the data to other services, the modified data carry the serial number of the data, and the programs are marked as starting programs of the data;
when the other programs receive the modified data which is sent by the starting program and is associated with the data, the serial numbers of the data are used; the other programs finish processing the modified data associated with the data, and if the data associated with the data is continuously transmitted to the other programs, the program is marked as a middle point program of the data; if the data associated with the data is no longer being passed to other programs, the program is marked as the end program for the data.
If the data associated with a certain number has a corresponding starting point program, all intermediate point programs and ending point programs in a processing chain in the system, the data associated with the certain number is considered to be completely processed, the data is complete, and otherwise, the data is considered to be incomplete.
Example 3
when processing first data acquired from the outside, a first program numbers the first data acquired from the outside, and the number 1001 of the first data is assumed to be 1001, and is called as a first number; all programs carry the first number 1001 when they transmit the first data to other services, and the first program is called the start program. This number does not overlap with each other and increments between starting programs in the system, and the first program is referred to as the starting program of the first number 1001.
When the second program receives the first data sent by the first program, the first serial number 1001 of the first data is used, and only when the external data is directly received, the new serial number is used; if the second program is processing the first data with the first number 1001, the second program continues to transmit the first data with the first number 1001 to other programs, and the second program is called a middle point program with the first number 1001. Since the number of the second process is the same as the number 1001 of the start process in step S1, it can be considered that the second process and the start process in step S1 are processing the same service together.
When the third program processes the first data with the first number 1001 and does not transfer the first data with the number 1001 to another program, the third program is referred to as an end point program with the first number 1001. For the first number 1001, there are both the start point procedure and the end point procedure, and as long as the related procedures have processed the first data of the number 1001, the service is considered to have been completely ended.
If the data of a number has a starting point program corresponding to the number, all intermediate point programs and a corresponding end point program in the system, the data processing of the number is considered to be completely finished, and the data is complete, for example, if the data modified by the first data of the number 1001 in the starting point program and the end point program are marked with 1001 numbers, the association and the integrity between the data can be judged only by comparing the numbers.
Example 4
Embodiment 4 of the present invention provides a system for determining data consistency of a distributed software program, including an association marking unit and a data integrity determining unit, where:
the association flag unit is used for: numbering data acquired from the outside, associating all modified data associated with the data with the number of the data when the distributed software program processes the data, and determining a starting point program, an intermediate point program and an end point program for processing the data;
the data integrity judgment unit is used for: and judging the relevance and integrity of the data among the distributed software programs by verifying whether the processing chain of the data related to a certain number from the starting point program, the intermediate point program to the end point program is complete.
When the association flag unit numbers data acquired from the outside, the numbers are not overlapped with each other and are incremented between starting point programs in the system. Only when external data is directly received, the new number is used.
Example 5
Embodiment 5 of the present invention provides a system for determining data consistency of a distributed software program, including an association marking unit and a data integrity determining unit, where:
the association flag unit is used for:
when the distributed software program processes data acquired from the outside, numbering the data; when all programs transmit modified data associated with the data to other services, the modified data carry the serial number of the data, and the programs are marked as starting programs of the data;
when the other programs receive the modified data which is sent by the starting program and is associated with the data, the serial numbers of the data are used; the other programs finish processing the modified data associated with the data, and if the data associated with the data is continuously transmitted to the other programs, the program is marked as a middle point program of the data; if the data associated with the data is no longer being passed to other programs, the program is marked as the end program for the data.
The data integrity judgment unit is used for:
if the data associated with a certain number has a corresponding starting point program, all intermediate point programs and ending point programs in a processing chain in the system, the data associated with the certain number is considered to be completely processed, the data is complete, and otherwise, the data is considered to be incomplete.
Example 6
The system is system-bound, and a distributed system is considered as a whole, and also system-bound, data entering the system from the bound can be defined, and after external data enters the system range, processing may be completed through cooperation of a plurality of programs, and fig. 2 shows solid lines 1, 2, 3 and a dotted line A, B respectively represent execution paths of two kinds of external service data.
Referring to fig. 2, program 1 receives external data numbered 100, program 1 is the starting program numbered 100, then any data modification when program 1 processes data numbered 100 is associated with number 100, including interactive data with other programs, and when program 1 processes data numbered 100, program 1 sends data numbered 100 to program 2.
Program 4 again continues to use number 100, with data modifications made that are all associated with number 100, and then program 4 does not have data interactions with other programs, i.e., program 4 is an endpoint program.
The programs 1, 2, 3, and 4 all send information that they have processed the number 100 to the MGR (Manager), i.e., the dotted lines between the programs and the MGR in fig. 2, and the Manager MGR determines whether the data processing of the number 100 has been completely finished.
program 4 sends {100, end program, from program 2 in } to hypervisor MGR;
The management program MGR determines each piece of numbering information sent by the respective program: if there is a starting point, there are intermediate points, and each intermediate point is also associated with an ending point, such as the 100 numbered data above, then the 100 numbered data is all processed in the system and the involved programs are consistent with each other at 100.
If a program is processing data of number 100 and is also processing another external service data, for example, the flow identified by the dashed line A, B in fig. 2, the processing procedure is as follows:
program 4 receives the external data and sets the external data number to 200, program 4 is the starting program number 200, and any data modification of program 4 while processing the data number 200 is associated with number 200.
Program 4 sends 200, the starting program, to program 5 to hypervisor MGR.
Program 4 also performs data interaction with program 5 when processing data numbered 200, program 5 is an intermediate point program, program 5 continues to use number 200, the data modifications it makes are all associated with number 200, program 5 also performs data interaction with program 3, program 5 sends {200, the intermediate point program, from program 4 in, to program 3 } to hypervisor MGR.
If the program 3 is damaged before the processing flow of the number 200 is started, the management program MGR may not receive the flow information identified by the program 3, and may only receive the data of the program 4 and the program 5, and then the management program MGR determines that the flow from the program 5 to the program 3 has no end program and has the exception information of the program 3, and if the program 3 is damaged and no other data is lost, the management program MGR determines that the data of the number 200 in the current system is incomplete.
By judging the number of the external data and the starting point program, the intermediate point program and the end point program corresponding to the number, the integrity of the data among the programs in a system at a certain moment can be easily judged.
Various modifications and variations of the embodiments of the present invention may be made by those skilled in the art, and they are also within the scope of the present invention, provided they are within the scope of the claims of the present invention and their equivalents.
What is not described in detail in the specification is prior art that is well known to those skilled in the art.
Claims (8)
1. A method for judging the consistency of distributed software program data is characterized by comprising the following steps:
s1, numbering the data acquired from the outside, and when the distributed software program processes the data, associating all the modified data associated with the data with the number of the data, and determining a starting point program, a middle point program and an end point program for processing the data;
s2, judging the relevance and integrity of the data among the distributed software programs by checking whether the processing chain of the data related to a certain number from the starting point program, the intermediate point program to the end point program is complete or not;
step S1 specifically includes the following steps:
when the distributed software program processes data acquired from the outside, numbering the data; when all programs transmit modified data associated with the data to other services, the modified data carry the serial number of the data, and the programs are marked as starting programs of the data;
when the current program receives the modified data which is sent by the starting program and is associated with the data, the serial number of the data is used; the current program finishes processing the modified data associated with the data, and if the data associated with the data is continuously transmitted to other programs, the current program is marked as a middle point program of the data; if the data associated with the data is no longer being passed to other programs, the current program is marked as the end program for the data.
2. The method for determining the consistency of data of a distributed software program according to claim 1, wherein: in step S1, when the data acquired from the outside is numbered, the number is incremented without overlapping each other between the start point programs in the system.
3. The method for determining the consistency of data of a distributed software program according to claim 2, wherein: in step S1, when the data acquired from the outside is numbered, the new number is used only when the external data is directly received.
4. The method for determining the consistency of data of a distributed software program according to claim 1, wherein: step S2 specifically includes the following steps:
if the data associated with a certain number has a corresponding starting point program, all intermediate point programs and ending point programs in a processing chain in the system, the data associated with the certain number is considered to be completely processed, the data is complete, and otherwise, the data is considered to be incomplete.
5. A judging system for data consistency of a distributed software program is characterized by comprising an association marking unit and a data integrity judging unit, wherein:
the association flag unit is used for: numbering data acquired from the outside, associating all modified data associated with the data with the number of the data when the distributed software program processes the data, and determining a starting point program, an intermediate point program and an end point program for processing the data;
the data integrity judgment unit is used for: judging the relevance and integrity of data among distributed software programs by verifying whether a processing chain of data related to a certain number from a starting point program, an intermediate point program to a terminal point program is complete or not;
the association flag unit is specifically configured to:
when the distributed software program processes data acquired from the outside, numbering the data; when all programs transmit modified data associated with the data to other services, the modified data carry the serial number of the data, and the programs are marked as starting programs of the data;
when the other programs receive the modified data which is sent by the starting program and is associated with the data, the serial numbers of the data are used; the other programs finish processing the modified data associated with the data, and if the data associated with the data is continuously transmitted to the other programs, the program is marked as a middle point program of the data; if the data associated with the data is no longer being passed to other programs, the program is marked as the end program for the data.
6. The system for determining the consistency of distributed software program data as recited in claim 5, wherein: when the association flag unit numbers data acquired from the outside, the numbers are not overlapped with each other and are incremented between starting point programs in the system.
7. The system for determining the consistency of distributed software program data as recited in claim 6, wherein: when the related marking unit numbers the data acquired from the outside, the new number is used only when the external data is directly received.
8. The system for determining the consistency of distributed software program data as recited in claim 5, wherein: the data integrity judgment unit is specifically configured to:
if the data associated with a certain number has a corresponding starting point program, all intermediate point programs and ending point programs in a processing chain in the system, the data associated with the certain number is considered to be completely processed, the data is complete, and otherwise, the data is considered to be incomplete.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810362576.0A CN108710557B (en) | 2018-04-20 | 2018-04-20 | Method and system for judging data consistency of distributed software program |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810362576.0A CN108710557B (en) | 2018-04-20 | 2018-04-20 | Method and system for judging data consistency of distributed software program |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108710557A CN108710557A (en) | 2018-10-26 |
| CN108710557B true CN108710557B (en) | 2021-10-19 |
Family
ID=63867387
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810362576.0A Active CN108710557B (en) | 2018-04-20 | 2018-04-20 | Method and system for judging data consistency of distributed software program |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108710557B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113650022A (en) * | 2021-07-30 | 2021-11-16 | 佛山缔乐视觉科技有限公司 | Robot programming method and device and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB2256069A (en) * | 1991-05-23 | 1992-11-25 | Digital Equipment Int | Transaction processing. |
| US9134970B2 (en) * | 2013-01-10 | 2015-09-15 | Oracle International Corporation | Software development methodology system for implementing business processes |
| CN106992884A (en) * | 2017-03-28 | 2017-07-28 | 武汉虹信技术服务有限责任公司 | A kind of multiple subsystem interlock method of intelligent building operation system |
| CN107092553A (en) * | 2017-04-20 | 2017-08-25 | 广州华多网络科技有限公司 | A kind of method, device and computer system for setting up request call chain between process |
| CN107483221A (en) * | 2016-06-08 | 2017-12-15 | 阿里巴巴集团控股有限公司 | A kind of across application problem investigation method, apparatus and system |
| CN107590072A (en) * | 2017-08-30 | 2018-01-16 | 深圳乐信软件技术有限公司 | A kind of application and development and the method and apparatus of test |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1556490A (en) * | 2004-01-08 | 2004-12-22 | 上海复旦光华信息科技股份有限公司 | Multi surce audit data business uniformity judging method based on state conversion table |
| US7949640B2 (en) * | 2008-10-31 | 2011-05-24 | Gravic, Inc. | Referential integrity, consistency, and completeness loading of databases |
| US10360095B2 (en) * | 2016-03-31 | 2019-07-23 | Change Healthcare Holdings, Llc | Methods and apparatuses for improving failure recovery in a distributed system |
-
2018
- 2018-04-20 CN CN201810362576.0A patent/CN108710557B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB2256069A (en) * | 1991-05-23 | 1992-11-25 | Digital Equipment Int | Transaction processing. |
| US9134970B2 (en) * | 2013-01-10 | 2015-09-15 | Oracle International Corporation | Software development methodology system for implementing business processes |
| CN107483221A (en) * | 2016-06-08 | 2017-12-15 | 阿里巴巴集团控股有限公司 | A kind of across application problem investigation method, apparatus and system |
| CN106992884A (en) * | 2017-03-28 | 2017-07-28 | 武汉虹信技术服务有限责任公司 | A kind of multiple subsystem interlock method of intelligent building operation system |
| CN107092553A (en) * | 2017-04-20 | 2017-08-25 | 广州华多网络科技有限公司 | A kind of method, device and computer system for setting up request call chain between process |
| CN107590072A (en) * | 2017-08-30 | 2018-01-16 | 深圳乐信软件技术有限公司 | A kind of application and development and the method and apparatus of test |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108710557A (en) | 2018-10-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109345388B (en) | Block chain intelligent contract verification method and device and storage medium | |
| CN111209343B (en) | Node data synchronization method, device, equipment and storage medium | |
| CN111290958B (en) | Method and device for debugging intelligent contract | |
| CN110570196A (en) | Transaction data processing method and device, terminal equipment and storage medium | |
| CN111679968A (en) | Interface calling abnormity detection method and device, computer equipment and storage medium | |
| US20150195124A1 (en) | Method for error diagnosis of can communication | |
| CN108710557B (en) | Method and system for judging data consistency of distributed software program | |
| CN110912805B (en) | Message reading state synchronization method, terminal, server and system | |
| CN112037062B (en) | Transaction consensus method, device, electronic equipment and readable storage medium | |
| CN113468276A (en) | Trusted data acquisition method and device of on-chain prediction machine and electronic equipment | |
| CN112817883A (en) | Method, device and system for adapting interface platform and computer readable storage medium | |
| CN114189384B (en) | Service processing method, device, equipment and storage medium | |
| CN107066347A (en) | Method and apparatus for generating output stream | |
| CN113342650B (en) | Chaotic engineering method and device for distributed system | |
| CN112995344B (en) | Block chain all-in-one machine, and chain crossing method and device and storage medium of multiple nodes in block chain all-in-one machine | |
| CN112965735B (en) | Model updating method, device, equipment and computer readable medium | |
| CN110585717B (en) | Information processing method and device | |
| CN112149696B (en) | Training method and device for graph embedding model | |
| CN106980515B (en) | Application upgrading method and device | |
| CN113065967A (en) | Multi-mode service processing method, device and equipment | |
| CN112732420A (en) | Background task execution method, distributed system and computer readable storage medium | |
| CN110580172A (en) | Configuration rule verification method and device, storage medium and electronic device | |
| CN110928713A (en) | Database service fault repairing method, related device and storage medium | |
| JPWO2020194748A5 (en) | Terminals, wireless communication methods and systems | |
| CN115080311B (en) | Informatization remote control method and device for big data |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20240703 Address after: 430000 No. 6, High-tech Fourth Road, Donghu High-tech Development Zone, Wuhan City, Hubei Province Patentee after: FIBERHOME TELECOMMUNICATION TECHNOLOGIES Co.,Ltd. Country or region after: China Patentee after: Wuhan Changjiang Computing Technology Co.,Ltd. Address before: 430000 No. 6, High-tech Fourth Road, Donghu High-tech Development Zone, Wuhan City, Hubei Province Patentee before: FIBERHOME TELECOMMUNICATION TECHNOLOGIES Co.,Ltd. Country or region before: China |