Archival data processing method, device, server and readable storage medium

Abstract

The present invention provides a method, device, server, and readable storage medium for processing archival data, comprising: receiving an archival processing request sent by a terminal via a public cloud server; if the archival processing request carries a first private alias tag, determining a target access address corresponding to the first private alias tag based on an archival user table via the public cloud server, and establishing a communication connection between the terminal and a target private server based on the target access address; and responding to the archival processing request via the target private server to obtain an archival processing result. The present invention can achieve unified scheduling and coordination of archival data stored in the public cloud server and each private server, thereby enabling quick and accurate processing of archival data stored in the private server, and significantly reducing the operation and maintenance costs of the archival data management platform.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a method, device, server and readable storage medium for processing archival data. Background Art

[0002] At present, due to the privacy of financial accounting archives, some companies do not want to directly use the archive system of the SaaS environment. Instead, they hope to deploy a dedicated archive system in a private environment. As a result, users are distributed in different private deployment environments, and only a small part of user data is stored in the SaaS environment. At the same time, there is no archive data of the private deployment environment in the SaaS environment, resulting in the inability to uniformly schedule and coordinate the archive data stored in each environment, resulting in high maintenance costs. Summary of the Invention

[0003] In view of this, the purpose of the present invention is to provide a method, device, server and readable storage medium for processing archival data, which can realize unified scheduling and coordination of archival data stored in the public cloud server side and each private server side, so that the archival data stored in the private server side can be processed quickly and accurately, and the operation and maintenance costs of the archival data management platform can be significantly reduced.

[0004] In a first aspect, an embodiment of the present invention provides a method for processing archival data, which is applied to an archival data management platform. The archival data management platform includes a public cloud server and multiple private servers. The public cloud server stores an archival user table, which is used to represent a mapping relationship between private alias tags and access addresses of the private servers. The method includes:

[0005] Receiving, via the public cloud server, a file processing request sent by a terminal;

[0006] If the archive processing request carries a first privatization alias tag, determining, by the public cloud server, a target access address corresponding to the first privatization alias tag based on the archive user table, and establishing a communication connection between the terminal and a target privatization server based on the target access address;

[0007] The target privatized server responds to the file processing request and obtains the file processing result.

[0008] In one embodiment, the privatized server is deployed with a first message unit and a data capture unit, and the public cloud server is deployed with a second message unit. The method further includes:

[0009] When the data capture unit monitors changes to the user data stored in the profile user table, it determines the changed target user data and sends the target user data to the user push topic in the first message unit;

[0010] Push the target user data stored in the Topic to the user through the first message unit, mark the data change type tag and the second privatization alias tag, and associate the target user data, the data change type tag, and the second privatization alias tag and send them to the second message unit on the public cloud server;

[0011] The archive user table is updated based on the target user data, the data change type tag, and the second privatization alias tag through the second message unit.

[0012] In one embodiment, the target user data stored in the Topic is pushed to the user, and the data change type tag and the second privatized alias tag are marked, including:

[0013] Adding a type field and an alias field to the target user data;

[0014] Assigning the data change type of the target user data to the type field to obtain a data change type tag; and assigning a preset privatization alias to the alias field to obtain a second privatization alias tag.

[0015] In one embodiment, the public cloud server is in communication with a public cloud database, and the public cloud database is used to store user data. Updating the archive user table based on the target user data, the data change type tag, and the second privatized alias tag includes:

[0016] If the data change type tag is a new addition type, the target user data is saved in the public cloud database, an access address corresponding to the second privatized alias tag is determined, and the second privatized alias tag and the access address corresponding to the second privatized alias tag are associated and stored in the archive user table;

[0017] If the data change type is a modification type, and the second privatized alias tag is stored in the archive user table, updating the target user data to the public cloud database;

[0018] If the data change type is a deletion type, the second privatized alias tag is removed from the archive user table.

[0019] In one embodiment, the archive processing request includes a first query request, the archive processing result includes a first archive query result, the privatization server is communicatively connected to a privatization database, and the privatization database is used to store private archive data; responding to the archive processing request to obtain an archive processing result through the target privatization server, and feeding the archive processing result back to the terminal, includes:

[0020] Then, through the privatization server, searching the privatization database based on the first query request to obtain the private archive data corresponding to the first query request;

[0021] The private archive data corresponding to the first query request is used as a first archive query result.

[0022] In one embodiment, the archive processing request includes a second query request, the archive processing result includes a second archive query result, the public cloud server is communicatively connected to a public cloud database, and the public cloud database is further used to store public archive data; the method further includes:

[0023] If the second query request does not carry the first privatized alias tag, searching the public cloud database based on the second query request through the public cloud server to obtain public archive data corresponding to the second query request;

[0024] The public archive data corresponding to the second query request is used as the second archive query result.

[0025] In one embodiment, the method further comprises:

[0026] The archive processing result is fed back to the terminal through the public cloud server or the target privatized server, so that the archive processing result is displayed through the graphical user interface of the terminal.

[0027] In a second aspect, an embodiment of the present invention further provides an archival data processing device, which is applied to an archival data management platform. The archival data management platform includes a public cloud server and multiple private server ends. The public cloud server end stores an archival user table, which is used to represent a mapping relationship between private alias tags and access addresses of the private server ends. The device includes:

[0028] The public cloud server is used to receive a file processing request sent by a terminal;

[0029] The public cloud server is further configured to, if the archive processing request carries a first privatization alias tag, determine a target access address corresponding to the first privatization alias tag based on the archive user table, and establish a communication connection between the terminal and a target privatization server based on the target access address;

[0030] The target privatization server is used to respond to the archive processing request and obtain an archive processing result.

[0031] In a third aspect, an embodiment of the present invention further provides a server, comprising a processor and a memory, wherein the memory stores computer-executable instructions that can be executed by the processor, and the processor executes the computer-executable instructions to implement any one of the methods provided in the first aspect.

[0032] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions. When the computer-executable instructions are called and executed by a processor, the computer-executable instructions prompt the processor to implement any one of the methods provided in the first aspect.

[0033] An embodiment of the present invention provides a method, device, server and readable storage medium for processing archival data, which are applied to an archival data management platform. The archival data management platform includes a public cloud server and multiple private server ends. The public cloud server end stores an archival user table, which is used to represent the mapping relationship between private alias tags and access addresses of the private server ends. First, the public cloud server end receives an archival processing request sent by a terminal. When the archival processing request carries a first private alias tag, the target access address corresponding to the first private alias tag is determined based on the archival user table, and a communication connection is established between the terminal and the target private server end based on the target access address. Finally, the target private server end responds to the archival processing request to obtain an archival processing result. The above method realizes user synchronization through the archive user table stored in the public cloud server. The public cloud server receives the archive processing request sent by the terminal and establishes a communication connection between the terminal and the target privatized server according to the target access address corresponding to the first privatized alias tag, which is equivalent to forwarding the archive processing request to the target privatized server. The embodiment of the present invention adopts user synchronization and policy forwarding to realize archive retrieval under environmental isolation, realizes unified scheduling and coordination of the archive data stored in the public cloud server and each privatized server, so that the archive data stored in the privatized server can be processed quickly and accurately, and the operation and maintenance cost of the archive data management platform can be significantly reduced.

[0034] Other features and advantages of the present invention will be described in the following description, and in part will become apparent from the description, or understood by practicing the present invention. The purposes and other advantages of the present invention are realized and obtained by the structures particularly pointed out in the description, claims and drawings.

[0035] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the specific embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0037] Figure 1 A flowchart of a method for processing archival data provided by an embodiment of the present invention;

[0038] Figure 2 A functional block diagram of a method for processing archival data provided by an embodiment of the present invention;

[0039] Figure 3 A functional block diagram of another archival data processing method provided by an embodiment of the present invention;

[0040] Figure 4 A schematic structural diagram of an archival data processing device provided by an embodiment of the present invention;

[0041] Figure 5 A schematic diagram of the structure of a server provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0042] To make the objectives, technical solutions, and advantages of the embodiments of the present invention more clear, the technical solutions of the present invention will be clearly and completely described below in conjunction with the embodiments. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of them. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0043] With business development and increasing user demands, more and more users are looking to access their archive system data through public cloud mini-programs or apps (applications). However, due to the isolation of environments and the storage of data in different environments, building a mini-program in a private deployment environment will significantly increase maintenance costs, such as the need for repeated upgrades and releases, resulting in higher maintenance and iteration costs.

[0044] Based on this, the present invention implements a method, device, server and readable storage medium for processing archival data, which can realize unified scheduling and coordination of archival data stored in the public cloud server side and each private server side, so that the archival data stored in the private server side can be processed quickly and accurately, and the operation and maintenance costs of the archival data management platform can be significantly reduced.

[0045] To facilitate understanding of this embodiment, a method for processing archive data disclosed in an embodiment of the present invention is first introduced in detail. The method is applied to an archive data management platform. The archive data management platform includes a public cloud server and multiple private server ends. The public cloud server end stores an archive user table. The archive user table is used to represent the mapping relationship between the private alias label and the access address of the private server end. Figure 1 The flowchart of a method for processing archival data shown in FIG. 1 mainly includes the following steps S102 to S106:

[0046] Step S102: Receive, via the public cloud server, a file processing request sent by the terminal. This file processing request may include a query request, modification / addition / deletion management request, or other such request. In one embodiment, the terminal is installed with an app corresponding to the file data management platform. The terminal can establish a communication connection with the public cloud server via the app, allowing the public cloud server to receive the file processing request sent by the terminal via the app.

[0047] In step S104, if the archive processing request carries a first privatized alias tag, the public cloud server determines the target access address corresponding to the first privatized alias tag based on the archive user table, and establishes a communication connection between the terminal and the target privatized server based on the target access address. The first privatized alias tag can be understood as the user's unique user identifier on the archive data management platform, used to identify the user as a user on the privatized server.

[0048] In one embodiment, if the archive processing request carries a first privatization alias tag, it means that the user belongs to a user of the privatization server. At this time, the target access address corresponding to the first privatization alias tag will be searched in the archive user table, and a communication connection will be established between the terminal and the target privatization server based on the target access address. The privatization database connected to the target privatization server stores the archive data of the user.

[0049] In another embodiment, if the archive processing request does not carry the first privatized alias tag, it means that the user belongs to a user of the public cloud server. In this case, the archive processing request will be responded to directly through the public cloud server.

[0050] Step S106: The target privatized server responds to the archive processing request and obtains an archive processing result. In one embodiment, the public cloud server forwards the archive processing request to the target privatized server, which responds to the archive processing request and feeds the archive processing result back to the terminal. For example, assuming the archive processing request is a query request, the corresponding private archive data is searched in the privatized database connected to the target privatized server, and the private archive data is fed back to the terminal as the archive processing result.

[0051] The archival data processing method provided by the embodiment of the present invention realizes user synchronization through the archival user table stored in the public cloud server end. The public cloud server end receives the archival processing request sent by the terminal, and establishes a communication connection between the terminal and the target privatized server end according to the target access address corresponding to the first privatized alias tag, which is equivalent to forwarding the archival processing request to the target privatized server end. The embodiment of the present invention adopts user synchronization and policy forwarding to realize archive retrieval under environmental isolation, realizes unified scheduling and coordination of the archival data stored in the public cloud server end and each privatized server end, so that the archival data stored in the privatized server end can be processed quickly and accurately, and the operation and maintenance costs of the archival data management platform can be significantly reduced.

[0052] To reduce the operation and maintenance costs of the archive data management platform, an embodiment of the present invention provides a user-based synchronization system that synchronizes private user data to a public cloud service. Furthermore, through policy forwarding, private users are allowed to log in to the public cloud mini-program / app, forwarding user access requests from various environments to the private environment, thereby enabling archive access. To address the issue of private users being unable to log in to the mini-program / app (public cloud environment) due to environmental isolation, and thus unable to access archives on their mobile phones, an embodiment of the present invention uses a user synchronization + policy forwarding approach to enable users to access public cloud archives, more efficiently implement archive system queries, and significantly reduce subsequent maintenance costs.

[0053] To facilitate understanding of an archival data management platform, an embodiment of the present invention provides an archival data management platform comprising a public cloud server and multiple private servers. The public cloud server is communicatively connected to a terminal and each private server. The public cloud server is connected to a public cloud database for storing user data and public archival data; the private servers are connected to a private database for storing private archival data.

[0054] In actual applications, before executing the aforementioned step S102, it is necessary to maintain the archive user table stored on the public cloud server. In order to better maintain the archive user table, an embodiment of the present invention proposes that the privatized server is deployed with a first message unit and a data capture unit, and the public cloud server is deployed with a second message unit. The first message unit is also the Kafka unit deployed on the privatized server (referred to as the first Kafka unit), the data capture unit is also the Debezium unit, and the second message unit is also the Kafka unit deployed on the public cloud server (referred to as the second Kafka unit).

[0055] In practice, the private server side designs a user synchronization data synchronization model, using Kafka and Debezium to monitor data. The private server code sends data changes to a second Kafka unit on the public cloud server. The public cloud server also designs a user synchronization data reception model, which processes the private data received by the second Kafka unit (i.e., the changed target user data), synchronizes data based on additions, deletions, and modifications, and identifies the source.

[0056] For ease of understanding, an embodiment of the present invention provides an implementation method for maintaining an archive user table, as shown in steps 1 to 3 below:

[0057] Step 1: Upon detecting changes to user data stored in the archive user table, the data capture unit identifies the target user data that has changed and sends the target user data to the user push topic in the first messaging unit. In one embodiment, a user push topic is created for the first Kafka unit, and the Debezium unit monitors the archive user table in the database. When the Debezium unit detects changes to the data due to DML statements (add, modify, delete), it sends the data to the user push topic in the first Kafka unit.

[0058] In step 2, the target user data stored in the Topic is pushed to the user via the first message unit, marked with the data change type tag and the second privatized alias tag, and the target user data, data change type tag, and second privatized alias tag are associated and sent to the second message unit on the public cloud server. This embodiment of the present invention also provides an implementation for pushing target user data stored in the Topic to the user, marking the data change type tag and the second privatized alias tag, as shown in steps 2.1 to 2.2 below:

[0059] Step 2.1: Add a type field and an alias field to the target user data. The value of the type field is used to represent the data change type label, and the value of the alias field is used to represent the second privatized alias label.

[0060] Step 2.2, assign the data change type of the target user data to the type field to obtain a data change type label; and assign the preset privatized alias to the alias field to obtain a second privatized alias label. In one embodiment, the consumer code on the privatized server side listens to the user push topic. When a message arrives in the user push topic, the consumer code on the privatized server side sends the target user data to the user synchronization topic of the second Kafka unit on the public cloud server side that has been configured with the account and password. Taking the type field as an example, add a field type (that is, type field). When adding, the value of type is add, when modifying, the value of type is update, and when deleting, the value of type is Del. Taking the alias field as an example, pre-set the privatized alias, such as ICBC for ICBC, hailiangEdu for Hailiang Education, etc., and then set the value of the alias field to the privatized alias.

[0061] For example, when a user's name changes or their email address is modified, the Debezium unit will monitor the changes in the data and the changed data, and send it to the first Kafka unit on the private server side. The code on the private server side will then consume the message, tag the target user data with the data change type label and the private alias label, and then send the target user data, the data change type label, and the private alias label to the second Kafka unit on the public cloud server side.

[0062] Step 3: Update the archive user table based on the target user data, the data change type tag, and the second privatized alias tag via the second message unit. This embodiment of the present invention also provides an implementation for updating the archive user table, as shown in steps 3.1 to 3.3 below:

[0063] Step 3.1, if the data change type label is a new type, the target user data is saved to the public cloud database, and the access address corresponding to the second private alias label is determined, so that the second private alias label and the access address corresponding to the second private alias label are associated and stored in the archive user table. The second Kafka unit is provided with a user synchronization topic. In one embodiment, the public and server sides will monitor the user synchronization topic. When a message comes in, the consumer of the second Kafka unit code will immediately consume the message and determine the data change type. If the data is new, the target user data is inserted into the public cloud database to ensure that the ID (Identity document) in the target user data remains unchanged, wherein the ID can be ensured to be unique using a snowflake algorithm, and the private alias label is also inserted into the archive user table.

[0064] In step 3.2, if the data change type is modification and the second privatized alias tag is stored in the profile user table, the target user data is updated to the public cloud database. In one embodiment, when the data is modified, a query is performed using the target user data ID. To compensate for message loss, this embodiment further determines whether the user exists. If not, step 3.1 is executed. If so, the user is modified.

[0065] Step 3.3: If the data change type is a deletion type, the second privatized alias tag is removed from the archive user table. In one embodiment, when the data is deleted, the archive user table in the public cloud database is directly deleted using the ID of the target user data.

[0066] To facilitate understanding of the above embodiments, the embodiments of the present invention provide the following Figure 2The functional block diagram of a method for processing archival data shown in the figure, on the privatized server side, the Debezium unit monitors the user changes (including additions, deletions, and modifications) of the electronic archival data in MySQL (i.e., the above-mentioned privatized database) on the privatized server side through the Debezium unit. If the user data is monitored to have changed, the changed target user data is sent to the user push Topic of the first Kafka unit, the privatized service monitors the user push Topic, and tags the target user data stored in the user push Topic, and sends the tagged target user data to the user synchronization Topic of the second Kafka unit of SaaS (i.e., the public cloud server side), monitors the user synchronization Topic, and synchronizes the target user data to the MySQL of SaaS (i.e., the above-mentioned public cloud database) through the service agent.

[0067] The data synchronization provided by this embodiment of the present invention involves monitoring changes in the private archive user table, tagging and sending the data to the public cloud, and then synchronizing the data received by the public cloud to the public cloud SaaS archive user table. This is the core technology of this embodiment of the present invention. In its implementation, the data transmission process from private archive users to public cloud archive users avoids the drawbacks of traditional archive user transmission methods, such as data loss, insufficient data, and delayed data transmission. By leveraging streaming computing, it significantly improves the user experience and enhances the accuracy and real-time nature of data.

[0068] On the basis of the foregoing embodiment, the embodiment of the present invention explains step S102 to step S106. In actual application, the terminal (i.e., mobile terminal) program or APP can achieve quasi-real-time processing of data based on the foregoing embodiment. The user logs in to verify the account password, determines the identifier, forwards the domain name data for different identifiers, and forwards the requests of users from different sources to the corresponding privatized server. Specifically, when the user logs in to the mini program or app, the login interface at this time requests the public cloud server. Since the user has been synchronized to the public cloud database, the password is verified at this time. If it does not exist, the user will be prompted that it does not exist. If it exists, the privatized alias tag field will be judged.

[0069] The embodiment of the present invention provides the following two implementations for determining whether the second query request carries the first privatized alias tag:

[0070] (1) The archive processing request includes a first query request, and the archive processing result includes a first archive query result. When the second query request carries a first private alias tag, the public cloud server determines the target access address corresponding to the first private alias tag based on the archive user table, and establishes a communication connection between the terminal and the target private server based on the target access address; the private server then searches the private database based on the first query request to obtain the private archive data corresponding to the first query request, and uses the private archive data corresponding to the first query request as the first archive query result.

[0071] In actual applications, if the private alias tag is not empty, it means that the data is private user data. Since the public cloud server does not have private data, the interface request address configured by the private alias tag is queried through the interface, such as wwww.baidu.com, and all subsequent requests are forwarded to this domain name for access.

[0072] (2) The archive processing request includes a second query request, and the archive processing result includes a second archive query result. When the second query request does not carry the first privatized alias tag, a search is performed in the public cloud database based on the second query request via the public cloud server to obtain public archive data corresponding to the second query request, and the public archive data corresponding to the second query request is used as the second archive query result.

[0073] In actual applications, if the privatization alias tag is empty, it means that the data is from the public cloud itself. The mini program will remain unchanged, and all subsequent requests will be processed by the public cloud server by default.

[0074] After the corresponding archival data is obtained through the query, the archival processing results can be fed back to the terminal through the public cloud server or the target privatized server, so that the archival processing results can be displayed through the terminal's graphical user interface. In the specific implementation, if the privatized alias tag is not empty, the archival processing results are queried and fed back through the target privatized server. If the target privatized server is empty, the archival processing results are queried and fed back through the public cloud server, and finally the archival processing results are displayed through the terminal's applet or APP. In actual applications, when the user side queries, users of different data platforms will obtain requests from different servers. Due to the synchronization of user data, privatized users can log in to the public cloud platform, and because the code forwards the traffic strategy, all data requests after login actually access the corresponding privatized server, ensuring the consistency and accuracy of the data.

[0075] To facilitate understanding of the above embodiments, the embodiments of the present invention provide the following Figure 3The functional block diagram of another archival data processing method shown is that the user accesses and logs in to the SaaS applet or APP, and verifies the account filled in by the user. If it fails, the user exits. If it passes, it determines whether it carries the first privatized alias tag. If there is no tag, the user continues to request SaaS to try to access it. If there is a tag, the user queries the target access address corresponding to the first privatized alias tag, and accesses the corresponding privatized server end based on the target access address to try to access it.

[0076] When logging in to query the archive app, the data is accurately forwarded to the corresponding database based on the private tag label strategy management, avoiding the disadvantage of the public cloud without private data. At the same time, the data is accurate, greatly improving the usability of the code. The embodiment of the present invention applies a strategy of forwarding traffic from different domain names based on tags, so that the mobile terminal can access private data. The data seen by different enterprise users is inconsistent. The data comes from multiple different private servers. The isolated data can be displayed on a single platform. This is also one of the innovations of the embodiment of the present invention.

[0077] The embodiment of the present invention can solve the problem that privatized users cannot log in to the public cloud applet while ensuring the accuracy and completeness of the query results, avoiding problems that may exist in other query solutions.

[0078] In summary, the archival data processing method provided by the embodiment of the present invention has at least the following characteristics:

[0079] (1) Reduce operation and maintenance costs. Due to environmental isolation and data asynchrony, if this solution is not adopted, it is inevitable that each privatization will have to be deployed separately with an independent mini-program or APP. The cost of subsequent upgrades will increase significantly. The increasing number of code deployments and releases will increase the operation and maintenance costs. Through user synchronization and traffic strategy forwarding, the operation and maintenance costs are greatly reduced, and code maintenance is made more convenient, as only one set of code needs to be maintained.

[0080] (2) Improve user experience: Through the implementation scheme of the embodiment of the present invention, users can query the data of the private environment more quickly and accurately, and access it on their mobile phones, thereby improving the user experience.

[0081] (3) Ensure data consistency and accuracy: Because the embodiment of the present invention implements a data user synchronization mechanism and traffic forwarding strategy, it ensures that the SaaS platform user data is updated synchronously, ensuring data consistency. Traffic is forwarded to the corresponding server, ensuring data accuracy.

[0082] (4) Real-time performance: The implementation scheme of the embodiment of the present invention is based on using Debezium to monitor changes in the database's archive user table and respond promptly to data changes. When user data changes, the data can be immediately transmitted to the public cloud for modification, ensuring the real-time performance of the data.

[0083] Therefore, the embodiments of the present invention have high practicality and market value.

[0084] Regarding the archival data processing method provided in the aforementioned embodiment, an embodiment of the present invention provides an archival data processing device, which is applied to an archival data management platform. The archival data management platform includes a public cloud server and multiple private server ends. The public cloud server end stores an archival user table, which is used to represent the mapping relationship between the private alias label and the access address of the private server end. Figure 4 The schematic diagram of the structure of a device for processing archival data is shown, and the device mainly includes the following parts:

[0085] The public cloud server 402 is used to receive the file processing request sent by the terminal;

[0086] The public cloud server 402 is further configured to, if the archive processing request carries the first privatization alias tag, determine a target access address corresponding to the first privatization alias tag based on the archive user table, and establish a communication connection between the terminal and the target privatization server based on the target access address;

[0087] The target privatization server 404 is used to respond to the file processing request and obtain the file processing result.

[0088] The archival data processing device provided by the embodiment of the present invention realizes user synchronization through the archival user table stored in the public cloud server end. The public cloud server end receives the archival processing request sent by the terminal, and establishes a communication connection between the terminal and the target privatized server end according to the target access address corresponding to the first privatized alias tag, which is equivalent to forwarding the archival processing request to the target privatized server end. The embodiment of the present invention adopts user synchronization and policy forwarding to realize archive retrieval under environmental isolation, realizes unified scheduling and coordination of the archival data stored in the public cloud server end and each privatized server end, so that the archival data stored in the privatized server end can be processed quickly and accurately, and the operation and maintenance costs of the archival data management platform can be significantly reduced.

[0089] In one embodiment, the privatized server side 404 is deployed with a first messaging unit and a data capture unit, and the public cloud server side 402 is deployed with a second messaging unit. The method further includes:

[0090] The data capture unit is used to, when monitoring changes to the user data stored in the archive user table, determine the changed target user data and send the target user data to the user push topic in the first message unit;

[0091] The first message unit is used to push the target user data stored in the Topic to the user, mark the data change type tag and the second privatization alias tag, and associate the target user data, the data change type tag and the second privatization alias tag to the second message unit on the public cloud server;

[0092] The second message unit is used to update the archive user table based on the target user data, the data change type tag and the second privatization alias tag.

[0093] In one embodiment, the first message unit is further configured to:

[0094] Add type field and alias field to target user data;

[0095] The data change type of the target user data is assigned to the type field to obtain a data change type label; and the preset privatization alias is assigned to the alias field to obtain a second privatization alias label.

[0096] In one embodiment, the public cloud server 402 is in communication with a public cloud database, which is used to store user data; and the second message unit is further used to:

[0097] If the data change type tag is a new type, the target user data is saved in the public cloud database, and the access address corresponding to the second privatized alias tag is determined, so that the second privatized alias tag and the access address corresponding to the second privatized alias tag are associated and stored in the archive user table;

[0098] If the data change type is modification type and the second privatized alias tag is stored in the archive user table, the target user data is updated to the public cloud database;

[0099] If the data change type is deletion type, the second privatized alias tag is removed from the archive user table.

[0100] In one embodiment, the archive processing request includes a first query request, the archive processing result includes a first archive query result, the privatization server is in communication with a privatization database, and the privatization database is used to store private archive data; the target privatization server is further configured to:

[0101] Searching the privatized database based on the first query request to obtain private archive data corresponding to the first query request;

[0102] The private archive data corresponding to the first query request is used as the first archive query result.

[0103] In one embodiment, the archive processing request includes a second query request, the archive processing result includes a second archive query result, the public cloud server is in communication with a public cloud database, and the public cloud database is further configured to store public archive data; the public cloud server 402 is further configured to:

[0104] If the second query request does not carry the first privatized alias tag, searching the public cloud database based on the second query request to obtain public archive data corresponding to the second query request;

[0105] The public archive data corresponding to the second query request is used as the second archive query result.

[0106] In one embodiment, the public cloud server 402 or the target privatized server 404 is further configured to feed back the archive processing result to the terminal so as to display the archive processing result through a graphical user interface of the terminal.

[0107] The device provided in the embodiment of the present invention has the same implementation principle and technical effects as those in the aforementioned method embodiment. For the sake of brief description, for matters not mentioned in the device embodiment, reference can be made to the corresponding content in the aforementioned method embodiment.

[0108] An embodiment of the present invention provides a server. Specifically, the server includes a processor and a storage device. The storage device stores a computer program, and when the computer program is executed by the processor, it executes the method described in any one of the above-mentioned embodiments.

[0109] Figure 5 A structural diagram of a server provided in an embodiment of the present invention, wherein the server 100 includes: a processor 50, a memory 51, a bus 52 and a communication interface 53, wherein the processor 50, the communication interface 53 and the memory 51 are connected via the bus 52; the processor 50 is used to execute an executable module stored in the memory 51, such as a computer program.

[0110] The memory 51 may include high-speed random access memory (RAM) and may also include non-volatile memory, such as at least one disk storage. The system network element communicates with at least one other network element via at least one communication interface 53 (which may be wired or wireless), and may utilize the Internet, a wide area network, a local area network, a metropolitan area network, or the like.

[0111] The bus 52 may be an ISA bus, a PCI bus, or an EISA bus. The bus may be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, Figure 5 Only one bidirectional arrow is used in the diagram, but this does not mean that there is only one bus or one type of bus.

[0112] Among them, the memory 51 is used to store programs, and the processor 50 executes the program after receiving the execution instruction. The method executed by the device for flow process definition disclosed in any embodiment of the above-mentioned embodiment of the present invention can be applied to the processor 50 or implemented by the processor 50.

[0113] The processor 50 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method may be completed by hardware integrated logic circuits or software instructions in the processor 50. The processor 50 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It may implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present invention. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in conjunction with the embodiments of the present invention may be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or the like. The storage medium is located in the memory 51 , and the processor 50 reads the information in the memory 51 and completes the steps of the above method in combination with its hardware.

[0114] The computer program product of the readable storage medium provided in the embodiment of the present invention includes a computer-readable storage medium storing program code. The instructions included in the program code can be used to execute the method described in the previous method embodiment. The specific implementation can be referred to the previous method embodiment and will not be repeated here.

[0115] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0116] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present invention, which are used to illustrate the technical solutions of the present invention, rather than to limit them. The scope of protection of the present invention is not limited thereto. Although the present invention has been described in detail with reference to the above-described embodiments, those skilled in the art should understand that any person skilled in the art can modify or easily conceive of changes to the technical solutions described in the above-described embodiments within the technical scope disclosed by the present invention, or replace some of the technical features therein with equivalents. Such modifications, changes, or replacements do not deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should be included in the scope of protection of the present invention. Therefore, the scope of protection of the present invention shall be subject to the scope of protection of the claims.

Claims

1. A method for processing archival data, characterized in that: The method is applied to an archive data management platform, the archive data management platform including a public cloud server and multiple private server ends, the public cloud server end storing an archive user table, the archive user table being used to represent a mapping relationship between private alias labels and access addresses of the private server ends, and comprising: Receiving, via the public cloud server, a file processing request sent by a terminal; If the archive processing request carries a first privatization alias tag, determining, by the public cloud server, a target access address corresponding to the first privatization alias tag based on the archive user table, and establishing a communication connection between the terminal and the target privatization server based on the target access address; Responding to the file processing request to obtain a file processing result through the target privatized server; The privatized server is deployed with a first message unit and a data capture unit, and the public cloud server is deployed with a second message unit. The method further includes: determining, by the data capture unit, upon monitoring a change in user data stored in the archive user table, the changed target user data, and sending the target user data to a user push topic in the first message unit; marking, by the first message unit, the target user data stored in the user push topic with a data change type tag and a second privatized alias tag, and associating the target user data, the data change type tag, and the second privatized alias tag and sending them to the second message unit on the public cloud server; and updating, by the second message unit, the archive user table based on the target user data, the data change type tag, and the second privatized alias tag. The public cloud server is communicatively connected to a public cloud database, which is used to store user data. The archive user table is updated based on the target user data, the data change type tag, and the second privatization alias tag, including: if the data change type tag is a new type, the target user data is saved to the public cloud database, and the access address corresponding to the second privatization alias tag is determined, so as to associate the second privatization alias tag with the access address corresponding to the second privatization alias tag and store them in the archive user table; if the data change type is a modification type and the second privatization alias tag is stored in the archive user table, the target user data is updated to the public cloud database; if the data change type is a deletion type, the second privatization alias tag is removed from the archive user table.

2. The method for processing archival data according to claim 1, characterized in that: Pushing the target user data stored in the Topic to the user, marking the data change type tag and the second privatized alias tag, includes: Adding a type field and an alias field to the target user data; Assigning the data change type of the target user data to the type field to obtain a data change type tag; and assigning a preset privatization alias to the alias field to obtain a second privatization alias tag.

3. The method for processing archival data according to claim 1, characterized in that: The archive processing request includes a first query request, the archive processing result includes a first archive query result, the privatization server is in communication with a privatization database, and the privatization database is used to store private archive data; The target privatized server responds to the file processing request to obtain a file processing result, and feeds back the file processing result to the terminal, including: Then, through the privatization server, searching the privatization database based on the first query request to obtain the private archive data corresponding to the first query request; The private archive data corresponding to the first query request is used as a first archive query result.

4. The method for processing archival data according to claim 1, wherein: The archive processing request includes a second query request, the archive processing result includes a second archive query result, the public cloud server is in communication with a public cloud database, and the public cloud database is further used to store public archive data; the method further includes: If the second query request does not carry the first privatized alias tag, searching the public cloud database based on the second query request through the public cloud server to obtain public archive data corresponding to the second query request; The public archive data corresponding to the second query request is used as the second archive query result.

5. The method for processing archival data according to any one of claims 1 to 4, characterized in that: The method further comprises: The archive processing result is fed back to the terminal through the public cloud server or the target privatized server, so that the archive processing result is displayed through the graphical user interface of the terminal.

6. A device for processing archival data, characterized in that: The device is applied to an archive data management platform, the archive data management platform including a public cloud server and multiple private server ends, the public cloud server end storing an archive user table, the archive user table being used to represent the mapping relationship between private alias tags and access addresses of the private server ends, and the device including: The public cloud server is used to receive a file processing request sent by a terminal; The public cloud server is further configured to, if the archive processing request carries a first privatization alias tag, determine a target access address corresponding to the first privatization alias tag based on the archive user table, and establish a communication connection between the terminal and a target privatization server based on the target access address; The target privatized server is used to respond to the file processing request and obtain the file processing result; The privatized server side is deployed with a first message unit and a data capture unit, and the public cloud server side is deployed with a second message unit, further comprising: the data capture unit is used to, when monitoring a change in the user data stored in the archive user table, determine the changed target user data and send the target user data to the user push topic in the first message unit; the first message unit is used to mark the target user data stored in the user push topic with a data change type tag and a second privatized alias tag, and associate the target user data, the data change type tag and the second privatized alias tag and send them to the second message unit on the public cloud server side; the second message unit is used to update the archive user table based on the target user data, the data change type tag and the second privatized alias tag; The public cloud server is communicatively connected to a public cloud database, which is used to store user data. The second message unit is further used to: if the data change type tag is a new addition type, save the target user data to the public cloud database, determine the access address corresponding to the second private alias tag, and associate the second private alias tag and the access address corresponding to the second private alias tag and store them in the archive user table; if the data change type is a modification type and the second private alias tag is stored in the archive user table, update the target user data to the public cloud database; if the data change type is a deletion type, remove the second private alias tag from the archive user table.

7. A server, characterized in that: The method comprises a processor and a memory, wherein the memory stores computer-executable instructions that can be executed by the processor, and the processor executes the computer-executable instructions to implement the method according to any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions. When the computer-executable instructions are called and executed by a processor, the computer-executable instructions prompt the processor to implement the method according to any one of claims 1 to 5.

Images