CN114374702A - Disaster tolerance data analysis and presentation method - Google Patents
Disaster tolerance data analysis and presentation method Download PDFInfo
- Publication number
- CN114374702A CN114374702A CN202111609126.5A CN202111609126A CN114374702A CN 114374702 A CN114374702 A CN 114374702A CN 202111609126 A CN202111609126 A CN 202111609126A CN 114374702 A CN114374702 A CN 114374702A
- Authority
- CN
- China
- Prior art keywords
- data
- client
- disaster recovery
- application server
- backup
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 28
- 238000007405 data analysis Methods 0.000 title description 4
- 238000011084 recovery Methods 0.000 claims abstract description 75
- 230000005540 biological transmission Effects 0.000 claims abstract description 15
- 230000000007 visual effect Effects 0.000 claims abstract description 10
- 238000012545 processing Methods 0.000 claims abstract description 6
- 230000007547 defect Effects 0.000 abstract description 2
- 238000004458 analytical method Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 238000012544 monitoring process Methods 0.000 description 3
- 238000013523 data management Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000003860 storage Methods 0.000 description 2
- 238000012800 visualization Methods 0.000 description 2
- 241000220317 Rosa Species 0.000 description 1
- 230000002159 abnormal effect Effects 0.000 description 1
- 235000014510 cooky Nutrition 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000009545 invasion Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
- H04L63/0442—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
- H04L69/162—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields involving adaptations of sockets based mechanisms
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to a method for analyzing and presenting disaster tolerant data, which solves the defects that different disaster tolerant backup products are difficult to present on the same platform and data transmission adopts plaintext compared with the prior art. The invention comprises the following steps: backup processing of the base node; connecting a client; carrying out encryption and decryption transmission on disaster tolerance data; and analyzing and presenting the disaster tolerance data. The invention can select to access different disaster recovery backup products according to different disaster recovery backup scenes, and the client and the application server adopt a WebSocket mode and an asymmetric encryption mode for data transmission, thereby ensuring the safety of data and realizing the visual presentation of disaster recovery data.
Description
Technical Field
The invention relates to the technical field of disaster recovery data analysis, in particular to an analysis presentation method of disaster recovery data.
Background
With the development of informatization, data loss can be caused no matter natural disasters occur, or man-made misoperation or invasion occurs, so that unpredictable loss is brought, generally, the faults are divided into system faults, object faults and medium faults, however, data disaster recovery backup is the last measure for ensuring data safety, and if data backup disaster recovery is not adopted, data can be generally lost and damaged.
Although there are many backup disaster recovery products in the market at present, there are some problems, such as no visual display system, for operators to know the disaster recovery backup situation. Most of the methods adopt mail, short messages and the like, and only when a problem occurs, the problem is known. This results in either no ability to predict problems in advance for the system, or part of the manufacturer has a visualization system but cannot fuse multiple products. When a plurality of products are used during disaster recovery backup, different visual interfaces are required to be opened simultaneously to view problems.
Most of visual presentation systems are used for large-screen presentation and data presentation, and data are regularly requested to an application server in a polling mode, so that the expenses of hardware such as bandwidth and memory are greatly increased. There is often a case that when data is in problem, the visualization system has a delay prompt. Since the backend data is acquired only by a prescribed time, this leads to a situation in which the operator delays the operation.
The method also has a problem that data transmission is mostly carried out between most backup disaster recovery system clients and application servers and between the backup disaster recovery servers and the application servers in the market at present in a plaintext mode, so that the system is easy to attack, and an attacker can easily acquire related data.
Therefore, how to develop an analysis presentation method for disaster recovery data has become a technical problem to be solved urgently.
Disclosure of Invention
The invention aims to solve the defects that different disaster recovery backup products are difficult to present on the same platform and data transmission adopts plaintext in the prior art, and provides an analysis presenting method of disaster recovery data to solve the problems.
In order to achieve the purpose, the technical scheme of the invention is as follows:
a method for analyzing and presenting disaster tolerant data comprises a disaster recovery end, an application server, an infrastructure node and a client, wherein the disaster recovery end is used for backing up data related to disaster recovery, the application server is used for recording records of the disaster recovery end and the backup end and configuring and alarming information of the backup end and the disaster recovery end, the client is used for displaying a disaster recovery large screen, the records of the disaster recovery and visual operation, the disaster recovery end is connected with the client through the application server, the infrastructure node is connected with the disaster recovery end and the application server through the backup end,
the method for analyzing and presenting the disaster tolerance data comprises the following steps:
backup processing of the base node;
connecting a client;
carrying out encryption and decryption transmission on disaster tolerance data;
and (3) analyzing and presenting disaster tolerance data: data transmission is carried out in a mode of Websocket plus asymmetric encryption, decryption is carried out when the presentation segment is displayed, and corresponding data is stored in a localForage in a symmetric encryption mode; when the access is present, data is obtained from localforage.
The backup processing of the base node comprises the following steps:
the infrastructure node performs backup operation in a local machine room;
the infrastructure node performs local backup on the node data and stores the node data into a backup end through a disaster recovery backup tool;
if the backup end needs disaster recovery, the data of the backup end is backed up to the disaster recovery backup end in different places through the disaster recovery backup tool, and meanwhile, the information is recorded into the application server.
The connection of the client comprises the following steps:
the client login system sends a login request and transmits a user name, a password, an ip address of the client and a public key publicity of the client to the application server;
the application server inquires account passwords and ip information in the system, stores the publickey of the client if the account passwords and the ip information exist in the system, and simultaneously transmits the publickey of the application server and the secret key symmetrically encrypted by the client to the client in a websocket mode;
after the two parties exchange the public key, the client and the application server respectively store the encryption secret key of the other party.
The encryption and decryption transmission of the disaster tolerance data comprises the following steps:
the client requests the application server to encrypt the data through the public key of the application server, and then pushes the data to the application server;
the application server decrypts the data according to the private key of the application server, inquires the data of the application server, encrypts the data through the public key of the client, and pushes the data to the client after encryption is completed;
the client side decrypts the data through a private key of the client side after obtaining the data, after decryption is completed, the data are classified, data encryption is carried out according to a symmetric encryption key transmitted by the server side, and then the data are stored in a localForage.
Advantageous effects
Compared with the prior art, the method for analyzing and presenting the disaster recovery data can select and access different disaster recovery backup products according to different disaster recovery backup scenes, and the client and the application server transmit data by adopting a WebSocket mode and an asymmetric encryption mode, so that the safety of the data is ensured, and the visual presentation of the disaster recovery data is realized.
The disaster recovery data-based analysis presentation system can be compatible with different disaster recovery backup products, such as nbu, tripod heads, rose and other current mainstream disaster recovery backup products, and meanwhile, the system adopts a WebSocket mode to carry out data interaction between the client and the application server, so that a long link can be established between the client and the application server, the client can actively request data of the server, and the server can also actively push the data to the client, so that the application server can actively push different clients once acquiring abnormal data of disaster recovery.
Meanwhile, data is transmitted between the client and the application server in an asymmetric encryption mode to ensure the safety of the data, the data is classified and encrypted as backup data or disaster recovery data for the first time and is stored in the localForage of the client, when the server has new data, the data is pushed to the client through the WebSocket server, the client decrypts the data of the server again and then encrypts the data according to the encryption mode of the client, and therefore the double encryption effect is achieved, the safety of the data is ensured, and meanwhile the data delay condition of the client and the application server is solved.
The disaster recovery backup presentation method has different presentation ends, and disaster recovery backup operators can more intuitively watch and know problems, so that prejudgment can be quickly made and problems can be timely handled; because the system adopts a localForage front-end storage mode to carry out data encryption storage, when the visual system is disconnected, the system is large in screen and the visual data cannot be viewed.
Drawings
FIG. 1 is a sequence diagram of the method of the present invention;
FIG. 2 is a block diagram of the method of the present invention;
fig. 3 is a diagram illustrating an example of a disaster tolerance data management platform formed by the method of the present invention.
Detailed Description
So that the manner in which the above recited features of the present invention can be understood and readily understood, a more particular description of the invention, briefly summarized above, may be had by reference to embodiments, some of which are illustrated in the appended drawings, wherein:
as shown in fig. 2, the disaster recovery data analysis and presentation method according to the present invention includes a disaster recovery end, an application server, an infrastructure node, and a client, where the disaster recovery end is used to backup data related to disaster recovery, the application server is used to record records of the disaster recovery end and the backup end, and configure and alarm information of the backup end and the disaster recovery end, the client is used to display a large disaster recovery screen, the records of the disaster recovery and part of visual operations, the disaster recovery end is connected to the client through the application server, and the infrastructure node is connected to the disaster recovery end and the application server through the backup end.
As shown in fig. 1, the method for analyzing and presenting disaster tolerance data includes the following steps:
the first step, backup processing of the base node. By adopting the mode, the backup and disaster recovery operations can be ensured to be completed under the condition of not influencing codes and running environments of a production environment. The method comprises the following specific steps:
(1) the infrastructure node performs backup operation in a local machine room;
(2) the infrastructure node performs local backup on the node data and stores the node data into a backup end through a disaster recovery backup tool;
(3) if the backup end needs disaster recovery, the data of the backup end is backed up to the disaster recovery backup end in different places through the disaster recovery backup tool, and meanwhile, the information is recorded into the application server.
And step two, connecting the clients. By adopting the method, the safety of the data can be ensured firstly, and meanwhile, the application server can record the currently accessed account and the ip for tracing the related information in the later period. The method comprises the following specific steps:
(1) the client login system sends a login request and transmits a user name, a password, an ip address of the client and a public key publicity of the client to the application server;
(2) the application server inquires account passwords and ip information in the system, stores the publickey of the client if the account passwords and the ip information exist in the system, and simultaneously transmits the publickey of the application server and the secret key symmetrically encrypted by the client to the client in a websocket mode;
(3) after the two parties exchange the public key, the client and the application server respectively store the encryption secret key of the other party.
And thirdly, encrypting and decrypting the disaster recovery data for transmission. By adopting the method, the data security is well ensured, meanwhile, the major browser in the localForage market supports the function, and the data storage amount of the localForage is much larger than that of the cookie. The method comprises the following specific steps:
(1) the client requests the application server to encrypt the data through the public key of the application server, and then pushes the data to the application server;
(2) the application server decrypts the data according to the private key of the application server, inquires the data of the application server, encrypts the data through the public key of the client, and pushes the data to the client after encryption is completed;
(3) the client side decrypts the data through a private key of the client side after obtaining the data, after decryption is completed, the data are classified, data encryption is carried out according to a symmetric encryption key transmitted by the server side, and then the data are stored in a localForage.
Fourthly, analyzing and presenting the disaster tolerance data: data transmission is carried out in a mode of Websocket plus asymmetric encryption, decryption is carried out when the presentation segment is displayed, and corresponding data is stored in a localForage in a symmetric encryption mode; when the access is present, data is obtained from localforage.
The presentation mode of the computer end is a browser, and the development and use technology is mainly developed in the mode of vue + echarts + websock + localForage. The mobile phone end is mainly divided into two modes for presentation, wherein the mode is that the small program is mainly researched and developed in a mode of copy + echarts + websock + localForage, and the mode is that the android app is adopted for displaying, and the acoustic android is adopted for developing. The two presentation modes are encrypted by adopting an encryption mode corresponding to websocket, decryption is carried out when the used presentation sections are displayed, and meanwhile, the corresponding data are stored in localForage in a symmetric encryption mode. When the data are changed, the server side pushes the data to the client side through the websocket for display, and meanwhile, the data in the localForage are updated so as to be directly obtained from the localForage next time and then directly displayed.
As shown in fig. 3, the disaster recovery data management platform formed by the method of the present invention mainly includes a disaster recovery cloud service management platform large screen, a service access, a monitoring management, a work order center, and a report center. The main contents displayed on the large screen are the number of enterprises, the number of backup clients, the number of disaster recovery clients, a trend graph of disaster recovery backup conditions, a node distribution condition of each disaster recovery backup stack point displayed on the map, and relevant information of each stack point displayed when each stack point is clicked. Service access is mainly responsible for accessing relevant stack point information. The monitoring management mainly displays the monitoring information of each stack point, and the work order center is mainly responsible for displaying and recording the condition that the related problems are processed. The report center is mainly responsible for displaying different polling conditions of each stack point. The disaster recovery platform displays relevant information, mutually exchanges keys after a first request, transmits the keys of the data storing localFoage to a client, acquires the relevant data and stores the data locally, the data needs to be encrypted and decrypted in the data transmission process, the client classifies the decrypted data and stores the data in localFoage, the data is directly acquired from localFoage at the later stage, and the data is symmetrically decrypted and then displayed before being displayed from localFoage each time. And at the later stage, if the application server pushes new data through the webscolet, the new data is displayed, and meanwhile, the localFoage data is updated. By adopting the mode, the safety in the data transmission process is well ensured, the frequency of continuously requesting data from the server is reduced, and hardware resources such as bandwidth and memory are well reduced.
The foregoing shows and describes the general principles, essential features, and advantages of the invention. It will be understood by those skilled in the art that the present invention is not limited to the embodiments described above, which are merely illustrative of the principles of the invention, but that various changes and modifications may be made without departing from the spirit and scope of the invention, which fall within the scope of the invention as claimed. The scope of the invention is defined by the appended claims and equivalents thereof.
Claims (4)
1. A method for analyzing and presenting disaster tolerant data comprises a disaster recovery end, an application server, an infrastructure node and a client, wherein the disaster recovery end is used for backing up data related to disaster recovery, the application server is used for recording the records of the disaster recovery end and the backup end and configuring and alarming the information of the backup end and the disaster recovery end, the client is used for displaying a disaster recovery large screen, the records of the disaster recovery and visual operation, the disaster recovery end is connected with the client through the application server, the infrastructure node is connected with the disaster recovery end and the application server through the backup end,
the method is characterized by comprising the following steps:
11) backup processing of the base node;
12) connecting a client;
13) carrying out encryption and decryption transmission on disaster tolerance data;
14) and (3) analyzing and presenting disaster tolerance data: data transmission is carried out in a mode of Websocket plus asymmetric encryption, decryption is carried out when the presentation segment is displayed, and corresponding data is stored in a localForage in a symmetric encryption mode; when the access is present, data is obtained from localforage.
2. The method according to claim 1, wherein the backup processing of the base node includes the following steps:
21) the infrastructure node performs backup operation in a local machine room;
22) the infrastructure node performs local backup on the node data and stores the node data into a backup end through a disaster recovery backup tool;
23) if the backup end needs disaster recovery, the data of the backup end is backed up to the disaster recovery backup end in different places through the disaster recovery backup tool, and meanwhile, the information is recorded into the application server.
3. The method according to claim 1, wherein the connection between the clients comprises the following steps:
31) the client login system sends a login request and transmits a user name, a password, an ip address of the client and a public key publicity of the client to the application server;
32) the application server inquires account passwords and ip information in the system, stores the publickey of the client if the account passwords and the ip information exist in the system, and simultaneously transmits the publickey of the application server and the secret key symmetrically encrypted by the client to the client in a websocket mode;
33) after the two parties exchange the public key, the client and the application server respectively store the encryption secret key of the other party.
4. The method according to claim 1, wherein the encryption and decryption transmission of the disaster recovery data includes the following steps:
41) the client requests the application server to encrypt the data through the public key of the application server, and then pushes the data to the application server;
42) the application server decrypts the data according to the private key of the application server, inquires the data of the application server, encrypts the data through the public key of the client, and pushes the data to the client after encryption is completed;
43) the client side decrypts the data through a private key of the client side after obtaining the data, after decryption is completed, the data are classified, data encryption is carried out according to a symmetric encryption key transmitted by the server side, and then the data are stored in a localForage.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111609126.5A CN114374702B (en) | 2021-12-27 | 2021-12-27 | Analysis and presentation method for disaster recovery data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111609126.5A CN114374702B (en) | 2021-12-27 | 2021-12-27 | Analysis and presentation method for disaster recovery data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114374702A true CN114374702A (en) | 2022-04-19 |
| CN114374702B CN114374702B (en) | 2024-01-30 |
Family
ID=81142291
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111609126.5A Active CN114374702B (en) | 2021-12-27 | 2021-12-27 | Analysis and presentation method for disaster recovery data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114374702B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101918927A (en) * | 2008-01-18 | 2010-12-15 | Tivo有限公司 | Distributed backup and retrieval system |
| CN102148822A (en) * | 2011-01-24 | 2011-08-10 | 辽宁国兴科技有限公司 | Remote online data disaster-tolerant system |
| CN104243195A (en) * | 2013-06-19 | 2014-12-24 | 国家电网公司 | Remote disaster recovery processing method and device |
| CN108255641A (en) * | 2017-12-25 | 2018-07-06 | 南京壹进制信息技术股份有限公司 | A kind of CDP disaster recovery methods based on cloud platform |
| CN111147420A (en) * | 2018-11-02 | 2020-05-12 | 深信服科技股份有限公司 | Data disaster tolerance method, device, system, equipment and computer readable storage medium |
| CN113268378A (en) * | 2021-05-18 | 2021-08-17 | Oppo广东移动通信有限公司 | Data disaster tolerance method and device, storage medium and electronic equipment |
-
2021
- 2021-12-27 CN CN202111609126.5A patent/CN114374702B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101918927A (en) * | 2008-01-18 | 2010-12-15 | Tivo有限公司 | Distributed backup and retrieval system |
| CN102148822A (en) * | 2011-01-24 | 2011-08-10 | 辽宁国兴科技有限公司 | Remote online data disaster-tolerant system |
| CN104243195A (en) * | 2013-06-19 | 2014-12-24 | 国家电网公司 | Remote disaster recovery processing method and device |
| CN108255641A (en) * | 2017-12-25 | 2018-07-06 | 南京壹进制信息技术股份有限公司 | A kind of CDP disaster recovery methods based on cloud platform |
| CN111147420A (en) * | 2018-11-02 | 2020-05-12 | 深信服科技股份有限公司 | Data disaster tolerance method, device, system, equipment and computer readable storage medium |
| CN113268378A (en) * | 2021-05-18 | 2021-08-17 | Oppo广东移动通信有限公司 | Data disaster tolerance method and device, storage medium and electronic equipment |
Non-Patent Citations (2)
| Title |
|---|
| KARIM USMAN: "Securing Remote Backup Files From Man in the Middle Attacks by using Encryption and Compression Mechanisms", 《 INTERNATIONAL JOURNAL OF ADVANCED STUDIES IN COMPUTER SCIENCE AND ENGINEERING》, pages 9 - 15 * |
| 刘坤灿: "基于区块链的数据灾备网络设计", 《电子世界》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114374702B (en) | 2024-01-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11057359B2 (en) | Key encryption key rotation | |
| US11271726B2 (en) | Key encryption methods, apparatuses, and systems | |
| US10868801B2 (en) | Method and system for establishing connection | |
| CN110401677B (en) | Method and device for acquiring digital copyright key, storage medium and electronic equipment | |
| US11582266B2 (en) | Method and system for protecting privacy of users in session recordings | |
| CN108964893B (en) | Key processing method, device, equipment and medium | |
| CN104601325A (en) | Data encryption method, device, equipment and system and data decryption method, device, equipment and system | |
| CN109063011B (en) | Log processing method, electronic device and computer readable storage medium | |
| CN113301431A (en) | Video data encryption and decryption method and device, electronic equipment and system | |
| CN115002203B (en) | Data packet grabbing method, device, equipment and computer readable medium | |
| CN104092672A (en) | Method for encrypting and decrypting information by means of ciphertext storage gateway | |
| CN113609147B (en) | Data sharing method and device and electronic equipment | |
| CN114221927A (en) | Mail encryption service system and method based on national encryption algorithm | |
| CN112671876B (en) | Method and equipment for page operation and maintenance | |
| CN117874143A (en) | Cloud edge database middleware synchronization method in distributed environment | |
| CN109286604B (en) | Method and device for realizing container service and electronic equipment | |
| CN111585998B (en) | Audit data secure transmission method and system | |
| CN114374702B (en) | Analysis and presentation method for disaster recovery data | |
| US20170293987A1 (en) | License verification method executed via mobile device and associated computer program product | |
| CN115208630A (en) | Block chain based data acquisition method and system and block chain system | |
| CN208227203U (en) | A kind of security video monitor supervision platform automatic test software service | |
| CN108390917B (en) | Intelligent message sending method and device | |
| CN114339630B (en) | Method and device for protecting short message | |
| US20240070037A1 (en) | Multi-Computer System for Maintaining Application Programming Interface Stability with Shared Computing Infrastructure | |
| CN110022247B (en) | APP data encryption transmission test method |
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 |