CN117235186B - Historical information synchronization method - Google Patents
Historical information synchronization method Download PDFInfo
- Publication number
- CN117235186B CN117235186B CN202311491585.7A CN202311491585A CN117235186B CN 117235186 B CN117235186 B CN 117235186B CN 202311491585 A CN202311491585 A CN 202311491585A CN 117235186 B CN117235186 B CN 117235186B
- Authority
- CN
- China
- Prior art keywords
- information
- information base
- message database
- login user
- database
- 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 47
- 238000012217 deletion Methods 0.000 claims description 9
- 230000037430 deletion Effects 0.000 claims description 9
- 238000004590 computer program Methods 0.000 claims description 6
- 230000002596 correlated effect Effects 0.000 claims description 6
- 230000001360 synchronised effect Effects 0.000 description 8
- 238000003780 insertion Methods 0.000 description 7
- 230000037431 insertion Effects 0.000 description 7
- 230000008569 process Effects 0.000 description 4
- 238000001514 detection method Methods 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000005856 abnormality Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013524 data verification Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000007781 pre-processing Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Abstract
The application relates to a history information synchronization method, which is applied to a client and comprises the following steps: after the client jumps to the user interface from the login page, judging whether a message database of a login user exists or not; if yes, synchronizing the history information; if not, sending a creation command to a server; the creation command is used for triggering the server to create a message database of a login user; downloading the message database after receiving the creation completion notification sent by the server; opening the downloaded message database; and synchronizing historical information based on the message database.
Description
Technical Field
The application relates to the technical field of data synchronization, in particular to a history information synchronization method.
Background
The synchronous history message is information such as all operation history records or communication records of the user on the platform, and is recorded and stored by the platform, and history information is checked when the user logs in an account again or logs in on a new device.
The current way of synchronizing a large number of history messages is mainly: 1. synchronizing only the history messages of the last period of time; the synchronous mode can rapidly open the current program to enable a user to use software, and has the defect that only the latest historical information can be seen, and the early historical information cannot be seen; 2. delay synchronization history message: pulled from the server when needed. The disadvantage is that the search is not friendly, if the search is synchronous, the search speed is slow; if the searching is asynchronous, the required information cannot be searched; 3. normally all synchronous: the disadvantage is that it takes a long time, is not user friendly and requires a user to wait.
How to better synchronize the history information is a technical problem that the skilled person needs to overcome.
Disclosure of Invention
In order to at least partially solve the above technical problems, the present application provides a history information synchronization method.
In a first aspect, the present application provides a method for synchronizing history information, which adopts the following technical scheme.
After the client jumps to the user interface from the login page, judging whether a message database of a login user exists or not; if yes, synchronizing the history information; if not, sending a creation command to a server; the creation command is used for triggering the server to create a message database of a login user;
downloading the message database after receiving the creation completion notification sent by the server;
opening the downloaded message database; the method comprises the steps of,
and synchronizing historical information based on the message database.
Optionally, after downloading the message database, the method further comprises:
sending a deletion command to the server; the deletion command is used for triggering the server to delete the created message database.
Optionally, the creating command is configured to trigger the server to create a message database of the login user, including:
after receiving the creation command, the server judges whether a message database of the login user exists, if not, the server creates the message database for the login user;
checking the user authority of the login user, configuring priority authority for the login user, writing all the login user information into the created information database from a server database, and submitting database transactions; the priority rights include opening a database transaction.
Optionally, determining whether a message database of the login user exists includes:
s401, obtaining a plurality of characteristic information units based on name information, account information and history synchronization information of a login user;
s402, information of a message database of the first three pairs is called according to the characteristic information unit; the pairing degree is positively correlated with the number of paired characteristic information units; calling a characteristic information base of information of each message database; the characteristic information base comprises a first information base, a second information base and a third information base;
s403, generating an information base to be paired based on the characteristic information units and generating a blank information base;
s404, acquiring a characteristic information unit in the information base to be paired and judging whether the characteristic information unit is positioned in the first information base, the second information base and the third information base;
s405, if yes, deleting the characteristic information unit from the information base to be paired, and updating the information base to be paired;
s406, judging whether the feature information unit is unique in the feature information base; if so, go to S407; if not, go to S408;
s407, matching one of a first information base, a second information base and a third information base based on the unique characteristic information unit and judging that a message database of a login user exists;
s408, judging whether the information base to be paired is an empty set or not; if not, returning to S404; if so, go to S409;
s409, obtaining a complete information base from the blank information base;
s410, judging whether the complete information base is matched with the first information base, the second information base and the third information base; if the user is paired, the message database of the login user is judged to exist.
In a second aspect, the present application provides a method for synchronizing history information, which adopts the following technical scheme.
A history information synchronization method, comprising:
receiving a creation command sent by a client; the creation command is transmitted by the client after the client jumps to a user interface from a login page and judges that a message database of a login user does not exist;
judging whether a message database of the login user exists or not, if not, creating the message database for the login user;
checking the user authority of the login user, configuring priority authority for the login user, writing all the login user information into the created information database from a server database, and submitting database transactions; the priority authority comprises opening database transactions;
sending a creating completion notice to the client; the creation completion notification is used for triggering the client to download the message database; opening the downloaded message database; and synchronizing historical information based on the message database.
Optionally, after receiving the creation command sent by the client, the method further includes:
judging whether the login user has a message database in a creation state or not; if yes, waiting for the establishment of the message database in the establishment state to be completed;
and after the message database in the creation state is created, sending a creation completion notification to the client.
Optionally, the method further comprises:
receiving a deletion command; the deleting command is sent by the client after downloading the message database;
and clearing the file in the message database based on the deleting command.
Optionally, determining whether the message database of the login user already exists includes:
s401, obtaining a plurality of characteristic information units based on name information, account information and history synchronization information of a login user;
s402, information of a message database of the first three pairs is called according to the characteristic information unit; the pairing degree is positively correlated with the number of paired characteristic information units; calling a characteristic information base of information of each message database; the characteristic information base comprises a first information base, a second information base and a third information base;
s403, generating an information base to be paired based on the characteristic information units and generating a blank information base;
s404, acquiring a characteristic information unit in the information base to be paired and judging whether the characteristic information unit is positioned in the first information base, the second information base and the third information base;
s405, if yes, deleting the characteristic information unit from the information base to be paired, and updating the information base to be paired;
s406, judging whether the feature information unit is unique in the feature information base; if so, go to S407; if not, go to S408;
s407, matching one of a first information base, a second information base and a third information base based on the unique characteristic information unit and judging that a message database of a login user exists;
s408, judging whether the information base to be paired is an empty set or not; if not, returning to S404; if so, go to S409;
s409, obtaining a complete information base from the blank information base;
s410, judging whether the complete information base is matched with the first information base, the second information base and the third information base; if the user is paired, the message database of the login user is judged to exist.
In a third aspect, the present application discloses an electronic device comprising a memory and a processor, the memory having stored thereon a computer program loaded by the processor and performing any of the methods described above.
In a fourth aspect, the present application discloses a computer readable storage medium storing a computer program capable of being loaded by a processor and performing any of the methods described above.
Drawings
FIG. 1 is a flowchart of a history information synchronization method at a client according to an embodiment of the present application;
FIG. 2 is a flowchart of a method for synchronizing history information in a server according to an embodiment of the present application;
fig. 3 is a schematic diagram of interaction between a server and a client in a history information synchronization method according to an embodiment of the present application.
Detailed Description
The present application is further described with reference to figures 1-3 and the specific examples below:
the embodiment of the application discloses a history information synchronization method which is applied to a client. Referring to fig. 1 and 2, as an embodiment of a history information synchronization method, a history information synchronization method includes the steps of:
step 101, after a client jumps to a user interface from a login page, judging whether a message database of a login user exists or not; if yes, synchronizing the history information; if not, sending a creation command to a server; the creation command is used for triggering the server to create a message database of the login user.
Specifically, after the client jumps from the login page to the user interface, it can be understood that: after a user logs in the user terminal equipment, the client terminal comprises equipment such as a smart phone, a computer, a car machine and the like. After the client jumps to the user interface from the login page, judging whether a message database of the login user exists, and if so, processing according to a normal history information synchronization flow.
The core of the invention is to generate a database used by a client by using a server. The server creates a database of the client, the insertion capability of the database is utilized to the maximum extent, and the insertion speed of the data is improved greatly; the abnormal disconnection of the client does not affect the process of inserting the database when the data are synchronized, so that the use experience of a user is improved; the interactive steps are reduced, and the data serialization and the inverse serialization of the server and the client are omitted. Since it is a client database regenerated at the server side, the commands of the server database can be fully trusted, and thus can be inserted when data:
1. all data insertion is done in one transaction; when the client executes, a large amount of data pulled from the database in batches cannot be inserted into one transaction for the sake of safety and preventing data retransmission caused by software shutdown in the synchronization process;
2. due to the stability of the server, the synchronous writing function can be closed during database insertion, and the data insertion speed is improved; in order to prevent data loss, the client generally opens a synchronous writing function;
3. closing the external key of the database can reduce the time waste of data verification;
4. since the data is inserted from the empty database, error detection processes such as repeatability check of the normal process are omitted;
5. the same type of data may be accomplished under a pre-processing database command; if the data is the client, the data of multiple batches needs to be preprocessed by database commands for multiple times;
due to the advantages of the database insertion, compared with the client data insertion executed by a normal client, the speed of generating the client database by the server side is greatly improved.
Step 102, after receiving the creation completion notification sent by the server, downloading the message database.
Step 103, opening the downloaded message database.
Step 104, performing history information synchronization based on the message database.
As a specific embodiment of the history information synchronization method, after the message database, the method further includes:
sending a deletion command to the server; the deletion command is used for triggering the server to delete the created message database.
Specifically, the technical scheme of the invention also has the following technical advantages:
1. the serialization of data is reduced; in the normal flow, the server and the client data interact through JSON and other formats, and serialization and deserialization are needed for each interaction; when the server side executes, the data queried by the server database can be directly inserted into the client database without serialization;
2. the authority detection of the server is reduced; in the normal flow, each time of interaction, the server needs to detect data such as user rights, and the like, and by using the method, the subsequent detection is stopped once at the beginning;
3. the database file is generated by a plurality of files, so that the database can be directly downloaded in a file mode, and the network bandwidth is utilized to the maximum extent; the normal client synchronization flow cannot fully utilize the bandwidth because of short messages possibly existing in the middle of data processing, data dependence and the like;
4. the risk resistance is strong, and the user experience is better; if the history message is normally synchronized, the user cannot bear to shut down the software due to too long time, or the client is disconnected from the server due to the factors of network disconnection, power failure and the like, and the user needs to continue to synchronize after reconnection, or needs to wait for a long time; by the method, after the client command is sent for the first time, the server starts to execute the command, the client waits, the execution of the server is not affected no matter what abnormality occurs in the client, and the file can be directly downloaded until the next time the user opens the software again, so that the user experience is better.
As a specific embodiment of the history information synchronization method, the creating command is used for triggering the server to create a message database of the login user, and includes:
after receiving the creation command, the server judges whether a message database of the login user exists, if not, the server creates the message database for the login user;
checking the user authority of the login user, configuring priority authority for the login user, writing all the login user information into the created information database from a server database, and submitting database transactions; the priority rights include opening a database transaction.
As a specific embodiment of a history information synchronization method, determining whether a message database of a login user exists includes:
s401, obtaining a plurality of characteristic information units based on name information, account information and history synchronization information of a login user;
s402, information of a message database of the first three pairs is called according to the characteristic information unit; the pairing degree is positively correlated with the number of paired characteristic information units; calling a characteristic information base of information of each message database; the characteristic information base comprises a first information base, a second information base and a third information base;
s403, generating an information base to be paired based on the characteristic information units and generating a blank information base;
s404, acquiring a characteristic information unit in the information base to be paired and judging whether the characteristic information unit is positioned in the first information base, the second information base and the third information base;
s405, if yes, deleting the characteristic information unit from the information base to be paired, and updating the information base to be paired;
s406, judging whether the feature information unit is unique in the feature information base; if so, go to S407; if not, go to S408;
s407, matching one of a first information base, a second information base and a third information base based on the unique characteristic information unit and judging that a message database of a login user exists;
s408, judging whether the information base to be paired is an empty set or not; if not, returning to S404; if so, go to S409;
s409, obtaining a complete information base from the blank information base;
s410, judging whether the complete information base is matched with the first information base, the second information base and the third information base; if the user is paired, the message database of the login user is judged to exist.
Referring to fig. 2 and fig. 3, the present application further provides a history information synchronization method, which is applied to a server, and includes:
s201, receiving a creation command sent by a client; the creation command is transmitted by the client after the client jumps to a user interface from a login page and judges that a message database of a login user does not exist;
s202, judging whether a message database of the login user exists, if not, creating the message database for the login user;
s203, checking the user authority of the login user, configuring priority authority for the login user, writing all the messages of the login user into the created message database from a server database, and submitting database transactions; the priority authority comprises opening database transactions;
s204, sending a creating completion notice to the client; the creation completion notification is used for triggering the client to download the message database; opening the downloaded message database; the method comprises the steps of,
s205, carrying out history information synchronization based on the message database.
As one embodiment of the history information synchronization method, after receiving the creation command sent by the client, the method further includes:
judging whether the login user has a message database in a creation state or not; if yes, waiting for the establishment of the message database in the establishment state to be completed;
and after the message database in the creation state is created, sending a creation completion notification to the client.
As one embodiment of the history information synchronization method, the method further includes:
receiving a deletion command; the deleting command is sent by the client after downloading the message database;
and clearing the file in the message database based on the deleting command.
As one embodiment of a method for synchronizing history information, determining whether a message database of the login user already exists includes:
s401, obtaining a plurality of characteristic information units based on name information, account information and history synchronization information of a login user;
s402, information of a message database of the first three pairs is called according to the characteristic information unit; the pairing degree is positively correlated with the number of paired characteristic information units; calling a characteristic information base of information of each message database; the characteristic information base comprises a first information base, a second information base and a third information base;
s403, generating an information base to be paired based on the characteristic information units and generating a blank information base;
s404, acquiring a characteristic information unit in the information base to be paired and judging whether the characteristic information unit is positioned in the first information base, the second information base and the third information base;
s405, if yes, deleting the characteristic information unit from the information base to be paired, and updating the information base to be paired;
s406, judging whether the feature information unit is unique in the feature information base; if so, go to S407; if not, go to S408;
s407, matching one of a first information base, a second information base and a third information base based on the unique characteristic information unit and judging that a message database of a login user exists;
s408, judging whether the information base to be paired is an empty set or not; if not, returning to S404; if so, go to S409;
s409, obtaining a complete information base from the blank information base;
s410, judging whether the complete information base is matched with the first information base, the second information base and the third information base; if the user is paired, the message database of the login user is judged to exist.
The embodiment of the application also discloses electronic equipment.
Specifically, the apparatus includes a memory and a processor, and the memory stores thereon a computer program that can be loaded by the processor and execute any one of the above history information synchronization methods.
The embodiment of the application also discloses a computer readable storage medium.
Specifically, the computer-readable storage medium storing a computer program capable of being loaded by a processor and executing any one of the history information synchronization methods described above includes, for example: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
It should be noted that: the above embodiments are only for illustrating the present application and not for limiting the technical solutions described in the present application, and although the present application has been described in detail with reference to the above embodiments, it should be understood by those skilled in the art that the present application may be modified or substituted by equivalent ones, and all technical solutions and modifications thereof without departing from the spirit and scope of the present application should be covered in the scope of the claims of the present application.
Claims (4)
1. A history information synchronization method applied to a client, comprising:
after the client jumps to the user interface from the login page, judging whether a message database of a login user exists or not; if yes, synchronizing the history information; if not, sending a creation command to a server; the creation command is used for triggering the server to create a message database of a login user;
downloading the message database after receiving the creation completion notification sent by the server;
opening the downloaded message database; the method comprises the steps of,
synchronizing historical information based on the message database;
after downloading the message database, the method further comprises:
sending a deletion command to the server; the deleting command is used for triggering the server to delete the created message database;
the creation command is used for triggering the server to create a message database of a login user, and comprises the following steps:
after receiving the creation command, the server judges whether a message database of the login user exists, if not, the server creates the message database for the login user;
checking the user authority of the login user, configuring priority authority for the login user, writing all the login user information into the created information database from a server database, and submitting database transactions; the priority authority comprises opening database transactions;
judging whether a message database of a login user exists or not, comprising:
s401, obtaining a plurality of characteristic information units based on name information, account information and history synchronization information of a login user;
s402, information of a message database of the first three pairs is called according to the characteristic information unit; the pairing degree is positively correlated with the number of paired characteristic information units; calling a characteristic information base of information of each message database; the characteristic information base comprises a first information base, a second information base and a third information base;
s403, generating an information base to be paired based on the characteristic information units and generating a blank information base;
s404, acquiring a characteristic information unit in the information base to be paired and judging whether the characteristic information unit is positioned in the first information base, the second information base and the third information base;
s405, if yes, deleting the characteristic information unit from the information base to be paired, and updating the information base to be paired;
s406, judging whether the feature information unit is unique in the feature information base; if so, go to S407; if not, go to S408;
s407, matching one of a first information base, a second information base and a third information base based on the unique characteristic information unit and judging that a message database of a login user exists;
s408, judging whether the information base to be paired is an empty set or not; if not, returning to S404; if so, go to S409;
s409, obtaining a complete information base from the blank information base;
s410, judging whether the complete information base is matched with the first information base, the second information base and the third information base; if the user is paired, the message database of the login user is judged to exist.
2. A history information synchronization method applied to a server, comprising:
receiving a creation command sent by a client; the creation command is transmitted by the client after the client jumps to a user interface from a login page and judges that a message database of a login user does not exist;
judging whether a message database of the login user exists or not, if not, creating the message database for the login user;
checking the user authority of the login user, configuring priority authority for the login user, writing all the login user information into the created information database from a server database, and submitting database transactions; the priority authority comprises opening database transactions;
sending a creating completion notice to the client; the creation completion notification is used for triggering the client to download the message database; opening the downloaded message database; and, synchronizing historical information based on the message database;
after receiving the creation command sent by the client, the method further comprises the following steps:
judging whether the login user has a message database in a creation state or not; if yes, waiting for the establishment of the message database in the establishment state to be completed;
after the message database in the creation state is created, sending a creation completion notification to a client;
the method further comprises the steps of:
receiving a deletion command; the deleting command is sent by the client after downloading the message database;
based on the deletion command, clearing the files in the message database;
judging whether the message database of the login user exists or not comprises the following steps:
s401, obtaining a plurality of characteristic information units based on name information, account information and history synchronization information of a login user;
s402, information of a message database of the first three pairs is called according to the characteristic information unit; the pairing degree is positively correlated with the number of paired characteristic information units; calling a characteristic information base of information of each message database; the characteristic information base comprises a first information base, a second information base and a third information base;
s403, generating an information base to be paired based on the characteristic information units and generating a blank information base;
s404, acquiring a characteristic information unit in the information base to be paired and judging whether the characteristic information unit is positioned in the first information base, the second information base and the third information base;
s405, if yes, deleting the characteristic information unit from the information base to be paired, and updating the information base to be paired;
s406, judging whether the feature information unit is unique in the feature information base; if so, go to S407; if not, go to S408;
s407, matching one of a first information base, a second information base and a third information base based on the unique characteristic information unit and judging that a message database of a login user exists;
s408, judging whether the information base to be paired is an empty set or not; if not, returning to S404; if so, go to S409;
s409, obtaining a complete information base from the blank information base;
s410, judging whether the complete information base is matched with the first information base, the second information base and the third information base; if the user is paired, the message database of the login user is judged to exist.
3. An electronic device comprising a memory and a processor, the memory having stored thereon a computer program for loading and executing by the processor the method of any one of claims 1 or 2.
4. A computer readable storage medium, characterized in that a computer program is stored which can be loaded by a processor and which performs the method according to any of claims 1 or 2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311491585.7A CN117235186B (en) | 2023-11-10 | 2023-11-10 | Historical information synchronization method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311491585.7A CN117235186B (en) | 2023-11-10 | 2023-11-10 | Historical information synchronization method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117235186A CN117235186A (en) | 2023-12-15 |
| CN117235186B true CN117235186B (en) | 2024-02-27 |
Family
ID=89093093
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311491585.7A Active CN117235186B (en) | 2023-11-10 | 2023-11-10 | Historical information synchronization method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117235186B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20070021503A (en) * | 2005-08-18 | 2007-02-23 | 유니위스 주식회사 | A distributing method of items or contents for making mobile pages and a system thereof |
| CN103716356A (en) * | 2012-10-09 | 2014-04-09 | 三亚中兴软件有限责任公司 | Storage process operation method, device and system based on Web |
| CN105354112A (en) * | 2015-11-05 | 2016-02-24 | 网易（杭州）网络有限公司 | Stand-alone game data recovery method, apparatus and system |
| CN108229902A (en) * | 2016-12-14 | 2018-06-29 | 中山市得高行知识产权中心（有限合伙） | Financial file information input system based on intelligent cradle head service |
| WO2022001096A1 (en) * | 2020-06-30 | 2022-01-06 | 公安部第三研究所 | Facial test database management system for detection of facial recognition device, and method |
-
2023
- 2023-11-10 CN CN202311491585.7A patent/CN117235186B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20070021503A (en) * | 2005-08-18 | 2007-02-23 | 유니위스 주식회사 | A distributing method of items or contents for making mobile pages and a system thereof |
| CN103716356A (en) * | 2012-10-09 | 2014-04-09 | 三亚中兴软件有限责任公司 | Storage process operation method, device and system based on Web |
| CN105354112A (en) * | 2015-11-05 | 2016-02-24 | 网易（杭州）网络有限公司 | Stand-alone game data recovery method, apparatus and system |
| CN108229902A (en) * | 2016-12-14 | 2018-06-29 | 中山市得高行知识产权中心（有限合伙） | Financial file information input system based on intelligent cradle head service |
| WO2022001096A1 (en) * | 2020-06-30 | 2022-01-06 | 公安部第三研究所 | Facial test database management system for detection of facial recognition device, and method |
Non-Patent Citations (1)
| Title |
|---|
| 江燕良 等.Android智能手机的云服务应用研究.单片机与嵌入式系统应用.2013,(第9期),第5-7页. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117235186A (en) | 2023-12-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP1696611A1 (en) | Server data queuing system and method | |
| CN114124451A (en) | Internet of things equipment data processing method and system and computer storage medium | |
| CN109614045B (en) | Metadata dropping method and device and related equipment | |
| CN110650164B (en) | File uploading method and device, terminal and computer storage medium | |
| CN108833443B (en) | Message transmission method and system and computer equipment | |
| CN112953983A (en) | SFTP transmission method and device | |
| EP2479962A1 (en) | Method and mobile terminal for recycling short messages | |
| CN109992940B (en) | Identity verification method, device and system and identity verification server | |
| CN117235186B (en) | Historical information synchronization method | |
| CN103503388B (en) | A kind of distributed queue's message read method and equipment, system | |
| CN113254166A (en) | Method for processing IO request, storage medium and virtualization simulator | |
| CN110502574B (en) | Cross-system information synchronization method, user equipment, storage medium and device | |
| CN108881320B (en) | Authentication processing method for user login, server and client | |
| CN111930358B (en) | Operation and maintenance script generation and execution method and system | |
| CN114339637A (en) | Short message splicing method, device, equipment and storage medium | |
| CN113568398A (en) | Configuration deleting method and system for distributed control system | |
| CN112948393A (en) | Web application program service data processing method, equipment and medium | |
| CN111737129A (en) | Service control method, service control device, computer readable medium and electronic equipment | |
| CN111049877A (en) | Big data external output method and device and data open platform | |
| CN109492422A (en) | A kind of data processing method and system based on user behavior information | |
| CN111225372B (en) | Anti-off-network method, user equipment and device with storage function | |
| CN112965949B (en) | Method for remotely reading ORACLE log file | |
| CN115002135B (en) | Multi-terminal cooperation method, device, system and computer readable storage medium | |
| CN111338821B (en) | Method, system and electronic equipment for realizing data load balance | |
| CN110597778B (en) | Distributed file backup and monitoring method and device |
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 |