A cloud computing-based data management method and system

Abstract

The embodiment of the application discloses a kind of data management method and system based on cloud computing, wherein the method comprises: front end obtains user login information, and background carries out identity verification;The background receives the identity verification information sent by the front end, verifies the identity of the user, obtains the corresponding feedback result and displays;After the front end feedback identity verification succeeds, the business data of the management system in the user authority range is collected, and the collected business data is sent to the background;The background is classified and stored to the management database by the interstellar file system to the business data collected by the front end, and the business data classification result is displayed, wherein the stored business data has traceability.The technical scheme can efficiently and safely manage data.

Description

Technical Field

[0001] This invention relates to the field of cloud computing management systems, and more specifically to a data management method and system based on cloud computing. Background Technology

[0002] With technological advancements and continuous digitalization, technologies such as the Internet of Things (IoT), big data, and cloud computing have been integrated into various industries, driving cities towards smart cities, industries towards Industry 4.0, and manufacturing towards intelligent manufacturing, thus propelling the overall upgrading of society's industries. The rapid development of big data, IoT, and cloud computing has made smart city management possible. Cloud computing based on big data is increasingly becoming an important way for internet companies to enhance computing power and optimize services, thus giving rise to big data management issues and problems related to providing services based on cloud computing.

[0003] In many fields, management systems require systematic management through meta-computing and other methods. Traditional management systems and methods cannot effectively classify and manage the various types of data within the field, and the security of stored management information is poor, resulting in low management efficiency and failing to meet management needs. Summary of the Invention

[0004] To address the aforementioned technical problems, embodiments of the present invention provide a cloud computing-based data management method and system for efficient and secure data management.

[0005] In a first aspect, embodiments of the present invention provide a data management method based on cloud computing, the method comprising:

[0006] The frontend retrieves user login information and sends it to the backend for identity verification.

[0007] The backend receives the authentication information sent by the frontend, verifies the user's identity, obtains the corresponding feedback results, and displays them.

[0008] After the front-end receives a successful authentication response from the back-end, it collects the business data of the management system within the user's permission scope and sends the collected business data to the back-end.

[0009] The backend uses the InterPlanetary File System to classify and store the business data collected from the frontend in the management database, and displays the classification results of the business data. The stored business data is traceable.

[0010] Furthermore, the management database includes a first database and a second database that are set up independently, wherein:

[0011] The first database is used to manage the first mapping relationship between business identifiers and business content, and to store the business content;

[0012] The second database is used to manage the second mapping relationship between business identifiers and business attributes, and to store the business attributes.

[0013] Furthermore, the backend categorizes and stores the business data collected from the frontend into a management database, specifically including:

[0014] Based on the business identifier of the business data, the business content collected by the front end is stored in the first database, and the business attributes collected by the front end are stored in the second database.

[0015] Furthermore, the method also includes:

[0016] The backend receives query requests from businesses, which include business attributes.

[0017] The backend queries the first and second databases based on business attributes to obtain the corresponding business content.

[0018] Furthermore, the backend categorizes and stores the business data collected from the frontend into a management database, including:

[0019] The backend determines whether the frontend user collecting business data belongs to a pre-defined important role;

[0020] If so, the backend will categorize and store the business data collected by the frontend into a management database on cloud storage;

[0021] If not, the backend determines whether the business data collected by the frontend meets either of the following two conditions: the corresponding business type belongs to a set type; or the access frequency reaches a set threshold.

[0022] If the conditions are met, the backend will categorize and store the business data collected by the frontend into a management database on cloud storage;

[0023] If the conditions are not met, the backend will categorize and store the business data collected by the frontend into a management database on local storage.

[0024] Secondly, embodiments of the present invention provide a cloud computing-based data management system, the system comprising a front-end and a back-end, wherein:

[0025] The front end includes:

[0026] The terminal interaction module is used to obtain user login information and send it to the backend for identity verification.

[0027] The management data acquisition module is used to collect business data of the management system within the user's permission scope after successful authentication, and transmit the collected business data through the wireless data transmission module;

[0028] The backend includes:

[0029] The cloud computing module is used to receive authentication information from the terminal interaction module to verify the user's identity and obtain corresponding feedback results. It is also used to receive business data transmitted through the wireless data transmission module in the management data acquisition module and to classify the business data.

[0030] The data storage management module, implemented through the InterPlanetary File System, is used to classify and store the service data transmitted by the wireless data transmission module into the management database, where the stored service data is traceable.

[0031] The data display module is used to display the business data classification results and feedback results of the cloud computing module.

[0032] Furthermore, the management database includes a first database and a second database that are set up independently, wherein:

[0033] The first database is used to manage the first mapping relationship between business identifiers and business content, and to store the business content;

[0034] The second database is used to manage the second mapping relationship between business identifiers and business attributes, and to store the business attributes.

[0035] Furthermore, the management data storage module is used to classify and store the service data transmitted by the wireless data transmission module into the management database, specifically including:

[0036] Based on the service identifier of the service data transmitted by the wireless data transmission module, the service content transmitted by the wireless data transmission module is stored in the first database, and the service attributes transmitted by the wireless data transmission module are stored in the second database.

[0037] Furthermore, the cloud computing module is also used for:

[0038] Receive business query requests, which include business attributes;

[0039] Query the first and second databases based on business attributes to obtain the corresponding business content.

[0040] Furthermore, the management data storage module is used to classify and store the business data collected from the front end into the management database, including:

[0041] Determine whether the front-end user collecting business data belongs to a pre-defined important role;

[0042] If so, the business data collected from the front end will be categorized and stored in the management database on cloud storage;

[0043] If not, determine whether the business data collected by the front end meets either of the following two conditions: the corresponding business type belongs to the set type; or the access frequency reaches the set threshold.

[0044] If the conditions are met, the business data collected from the front end will be categorized and stored in the management database on cloud storage;

[0045] If the conditions are not met, the business data collected by the front end will be categorized and stored in the management database on local storage.

[0046] The technical solution provided by this invention can classify and store data from multiple management systems within the field, enabling system management of related data, improving the efficiency of data management, and saving management time. By authenticating user permissions and issuing business collection content within the scope of permissions, the scope of business data to be collected can be well guaranteed, improving the security of data management and preventing the leakage of related data information. Attached Figure Description

[0047] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0048] Figure 1 This is a flowchart illustrating a cloud computing-based data management method provided in Embodiment 1 of the present invention;

[0049] Figure 2 This is a schematic diagram of a cloud computing-based data management system provided in Embodiment 2 of the present invention. Detailed Implementation

[0050] The embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0051] It should be understood that the described embodiments are merely some, not all, of the embodiments of the present invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.

[0052] Example 1

[0053] This embodiment provides a cloud-based data management method, applicable to cloud-based data management systems consisting of a front-end and a back-end. See also Figure 1 The method specifically includes the following steps 101-104.

[0054] Step 101: The front-end obtains the user's login information and sends it to the back-end for identity verification.

[0055] Step 102: The backend receives the authentication information sent by the frontend, verifies the user's identity, obtains the corresponding feedback result, and displays it.

[0056] Specifically, the front-end can obtain user login information (such as username and password) through form input or API calls, and then send the obtained user login information to the back-end. As a preferred implementation, after obtaining the user login information, the front-end performs authentication with the back-end based on LDAP (Lightweight Directory Access Protocol), which can improve the security of user personal information.

[0057] After receiving the login information from the frontend, the backend queries the database or uses other verification logic to verify the user's identity. The backend then returns the verification result to the frontend, typically via an HTTP response, which may include a successful authentication status code and relevant user information.

[0058] The frontend processes the verification result returned by the backend accordingly. If the verification is successful, the frontend can perform subsequent operations, such as redirecting to the login page; if the verification fails, the frontend can provide appropriate prompts, such as indicating that the username or password is incorrect.

[0059] By sending user login information to the backend for authentication, the verification process is ensured to occur in the background, thereby improving security. Simultaneously, the backend can rigorously verify user identities using databases or other authentication logic to protect system security. This approach effectively prevents the risk of frontend tampering or bypassing authentication, providing a more reliable user authentication mechanism.

[0060] Step 103: After the front-end receives a successful authentication response from the back-end, it collects the business data of the management system within the user's permission scope and sends the collected business data to the back-end.

[0061] In step 103, the backend management system maintains mapping relationships between multiple users and various business types and scopes. After verifying a user's identity, the system sends a business data collection interface corresponding to the user's business type and scope to the frontend based on this mapping relationship. Alternatively, the backend determines the business types and scopes that a user can access and operate based on their role or permission level, and sends a corresponding business data collection interface to the user. The frontend then collects business data from the management system within the user's permission scope using the business data collection interface sent by the backend and sends the collected business data back to the backend.

[0062] In this embodiment, only authorized users can obtain data collection permissions, and the content collected within the scope of permissions is restricted according to the user's identity and permissions. This ensures that only legitimate users can access and process business data within a specific scope, effectively protecting the security and privacy of business data. Furthermore, user authentication and the distribution of business collection interfaces within the user's authorized scope also prevent unnecessary data leaks and misuse, improving the accuracy and effectiveness of data collection.

[0063] Step 104: The backend uses the InterPlanetary File System to classify and store the business data collected by the frontend into the management database, and displays the classification results of the business data. The stored business data is traceable.

[0064] In specific implementation, the management database may include a first database and a second database that are set up independently, wherein: the first database is used to manage the first mapping relationship between business identifiers and business content, and to store the business content; the second database is used to manage the second mapping relationship between business identifiers and business attributes, and to store the business attributes.

[0065] Correspondingly, the backend categorizes and stores the business data collected from the frontend into a management database. Specifically, this includes storing the business content collected from the frontend in a first database and the business attributes collected from the frontend in a second database, based on the business identifiers of the business data. There is usually a relationship between business attributes and business content; business attributes are used to describe and identify the business content. Specifically, business attributes refer to the characteristics, attributes, or metadata that describe a business entity or object, including various attributes, characteristics, and identifiers of the business entity. Business content, on the other hand, refers to the specific data or information of the business entity, including the actual content, values, or text of the business entity.

[0066] Based on the above solutions, the cloud computing-based data management method provided in this embodiment also includes:

[0067] The backend receives query requests from businesses, which include business attributes.

[0068] The backend queries the first and second databases based on business attributes to obtain the corresponding business content.

[0069] In this embodiment, storing business attributes and business content separately has the following advantages:

[0070] Data structure flexibility: By storing business attributes and business content separately, data structures can be designed and managed according to business needs and data characteristics. Business attributes are usually metadata that describes the data, while business content is the actual data content. By storing them separately, it is possible to perform CRUD operations on business attributes and business content more flexibly without having to modify the entire data.

[0071] Data query and processing efficiency: Separating business attributes and business content for storage allows for optimization of different data structures, improving the efficiency of data query and processing. For example, indexes can be used to accelerate queries on business attributes without scanning the entire data content, enabling faster data location and retrieval.

[0072] Data security and privacy protection: Storing business attributes and business content separately can better protect sensitive information and private data; business attributes usually contain some metadata and key identifiers, while business content is the actual sensitive data; by storing them separately, different levels of security control can be implemented for business attributes and business content, restricting access permissions and protecting data security and privacy.

[0073] Data sharing and integration: Storing business attributes and business content separately facilitates data sharing and integration; business attributes can serve as descriptions and identifiers of data, making integration with other systems or businesses easier; at the same time, business content can be shared independently of business attributes, facilitating data interaction and sharing between different systems or businesses.

[0074] System architecture flexibility: Separating business attributes and business content for storage makes the system architecture more flexible; by decoupling business attributes and business content, they can be extended, upgraded and maintained independently without affecting the stability and functionality of the entire system.

[0075] In summary, storing business attributes and business content separately can improve the flexibility, query efficiency, security, and sharing of data management, while also helping to enhance the flexibility and scalability of the system architecture. This storage method is more in line with the structural characteristics of data and business needs, and helps to better manage and utilize data.

[0076] Furthermore, in this step, the backend can use measures such as timestamp recording, operation log recording, version management, backup and recovery, access control, and data auditing to ensure the traceability of the collected data stored in the database, enabling the tracking and recording of data changes and operations. Specifically,

[0077] Timestamp Records: Add a timestamp field to each data record in the database to record the creation time and modification time of the data. This allows you to track the data change process and time sequence, realizing a data timeline.

[0078] Operation log recording: Records all operations performed on the database, including add, modify, and delete operations. These operation logs can be stored in specific tables or recorded using a dedicated logging system. Operation logs can be traced back to specific operators and operation times for subsequent data auditing and traceability.

[0079] Version management: For data that needs to be changed frequently, a data version management approach can be adopted. A new version is generated each time the data is modified, and the relevant information of the version change is recorded. This allows you to track the historical versions of the data and to go back to a specific version when needed.

[0080] Backup and recovery: Regularly back up the database to ensure data reliability and integrity. Backup data can be used for data rollback and recovery to ensure data traceability.

[0081] Access control: Implement access control for data in the database to ensure that only authorized users can access and modify the data; by authenticating and authorizing users and recording their actions, data access and modification records can be traced.

[0082] Data auditing: Auditing database access and operations, recording each user's actions, including access time and operation content; audit logs allow tracing data access and modification records, ensuring data traceability.

[0083] As a preferred implementation, the backend categorizes and stores the business data collected from the frontend into a management database, including:

[0084] The backend determines whether the frontend user collecting business data belongs to a pre-defined important role;

[0085] If so, the backend will categorize and store the business data collected by the frontend into a management database on cloud storage;

[0086] If not, the backend will determine whether the business data collected by the frontend meets either of the following two conditions: the corresponding business type belongs to a set type; or the access frequency reaches a set threshold.

[0087] If the conditions are met, the backend will categorize and store the business data collected by the frontend into a management database on cloud storage;

[0088] If the conditions are not met, the backend will categorize and store the business data collected by the frontend into a management database on local storage.

[0089] The configuration type can be a pre-configured disaster recovery requirement higher than the first requirement, or a security requirement lower than the second requirement. The management database on cloud storage includes a separately configured first database and a second database; similarly, the management database on local storage also includes a separately configured first database and a second database.

[0090] Optionally, after receiving the business data collected from the front end, the backend verifies the collected data according to preset business logic before classifying and storing the data in the management database, ensuring the accuracy and integrity of the data. The verification operation may include at least one of the following:

[0091] Data format validation: Based on preset business rules, check whether the collected data meets the expected format requirements. For example, for the telephone number field, check whether it contains the correct number of digits and characters and whether it conforms to the standard format of telephone numbers.

[0092] Data range validation: Based on preset business rules, check whether the collected data is within the allowed range. For example, for the age field, check whether it is within a reasonable age range to avoid collecting abnormal data.

[0093] Logical relationship verification: Based on the preset business logic, check whether the relationship between the collected data is reasonable. For example, for order data, check whether the total amount of the order is equal to the sum of the amounts of each item to ensure data consistency.

[0094] Duplicate verification: Based on preset business requirements, check whether there are duplicate records in the collected data. For example, for the collection of user information, it can check whether the same username or ID number already exists in the system.

[0095] Required field validation: Based on preset business requirements, check whether the collected data has been filled in the required fields. For example, for the collection of form data, it can check whether any required fields are not filled in in order to avoid missing or incomplete data.

[0096] Data logic verification: Based on preset business rules, check whether the collected data meets specific logical conditions. For example, for the collection of data for product promotion activities, it can check whether the promotion rules are met, such as meeting certain purchase quantity or amount conditions.

[0097] In practical applications, specific verification strategies and rules can be defined and implemented according to specific business needs. By verifying the collected data, the quality and reliability of the data can be improved.

[0098] Example 2

[0099] This embodiment provides a cloud computing-based data management system. (See also...) Figure 2 The system includes a front-end 201 and a back-end 202. The front-end 201 can be a mobile terminal device with data acquisition capabilities, such as a smartphone, multimedia phone, or feature phone; the back-end 202 can be a cloud computing platform.

[0100] Specifically, the front-end 201 includes:

[0101] The terminal interaction module 2011 is used to obtain user login information and send it to the backend 202 for identity verification;

[0102] The management data acquisition module 2012 is used to collect business data of the management system within the user's permission scope after successful authentication, and to transmit the collected business data through the wireless data transmission module 2013.

[0103] Backend 202 includes:

[0104] The cloud computing module 2021 is used to receive authentication information from the terminal interaction module 2011 to verify the user's identity and obtain corresponding feedback results. It is also used to receive business data transmitted through the wireless data transmission module 2013 in the management data acquisition module 2012 and classify the business data.

[0105] The management data storage module 2022, implemented through the InterPlanetary File System, is used to classify and store the service data transmitted by the wireless data transmission module 2013 into the management database, wherein the stored service data is traceable;

[0106] The data display module 2023 is used to display the business data classification results and feedback results of the cloud computing module 2021.

[0107] Furthermore, the management database includes a first database and a second database that are set up independently, wherein:

[0108] The first database is used to manage the first mapping relationship between business identifiers and business content, and to store the business content;

[0109] The second database is used to manage the second mapping relationship between business identifiers and business attributes, and to store the business attributes.

[0110] Furthermore, the management data storage module 2022 is used to classify and store the service data transmitted by the wireless data transmission module 2013 into the management database, specifically including:

[0111] According to the service identifier of the service data transmitted by the wireless data transmission module 2013, the service content transmitted by the wireless data transmission module 2013 is stored in the first database, and the service attributes transmitted by the wireless data transmission module 2013 are stored in the second database.

[0112] Furthermore, the cloud computing module 2021 is also used for:

[0113] Receive business query requests, which include business attributes;

[0114] Query the first and second databases based on business attributes to obtain the corresponding business content.

[0115] Furthermore, the management data storage module 2022 is used to classify and store the business data collected from the front end into the management database, including:

[0116] Determine whether the front-end user collecting business data belongs to a pre-defined important role;

[0117] If so, the business data collected from the front end will be categorized and stored in the management database on cloud storage;

[0118] If not, determine whether the business data collected by the front end meets either of the following two conditions: the corresponding business type belongs to the set type; or the access frequency reaches the set threshold.

[0119] If the conditions are met, the business data collected from the front end will be categorized and stored in the management database on cloud storage;

[0120] If the conditions are not met, the business data collected by the front end will be categorized and stored in the management database on local storage.

[0121] The technical solution provided by this invention, by classifying and storing data from multiple management systems, can better organize and manage related data, thereby improving the management efficiency of the management system. Simultaneously, by performing user authorization authentication and issuing business collection content within the scope of authorized permissions, it can ensure that only users with the corresponding permissions can collect data, enhancing data management security and preventing data leakage.

[0122] Although the invention has been described above with reference to embodiments, various modifications can be made and components can be replaced with equivalents without departing from the scope of the invention. In particular, features in the embodiments disclosed herein can be combined in any way, provided there is no structural conflict. The lack of an exhaustive description of these combinations in this specification is merely for brevity and resource conservation. Therefore, the invention is not limited to the specific embodiments disclosed herein, but includes all technical solutions falling within the scope of the claims.

[0123] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the technical principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

[0124] The above-described specific embodiments are merely specific examples of the present invention. The patent protection scope of the present invention includes, but is not limited to, the above-described specific embodiments. Any appropriate changes or substitutions made by a person skilled in the art that conform to the claims of the present invention regarding a cloud computing-based management system and management method should fall within the patent protection scope of the present invention.

[0125] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature, and in the description of this invention, "a plurality of" means two or more, unless otherwise explicitly specified.

[0126] In this invention, unless otherwise explicitly specified and limited, the terms "installation," "connection," "linking," and "fixing," etc., should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances.

[0127] In this invention, unless otherwise explicitly specified and limited, "above" or "below" the second feature can include direct contact between the first and second features, or contact between the first and second features through another feature between them. Furthermore, "above," "over," and "on top" of the second feature includes the first feature being directly above or diagonally above the second feature, or simply indicates that the first feature is at a higher horizontal level than the second feature. "Below," "below," and "under" the second feature includes the first feature being directly above or diagonally above the second feature, or simply indicates that the first feature is at a lower horizontal level than the second feature.

[0128] In the description of this specification, references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0129] Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of the present invention without departing from the principles and spirit of the present invention.

[0130] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus.

[0131] The present invention and its embodiments have been described above. This description is not restrictive, and the accompanying drawings are only one embodiment of the present invention; the actual structure is not limited thereto. In conclusion, if those skilled in the art are inspired by this description and design similar structures and embodiments without departing from the spirit of the invention, such designs should fall within the protection scope of the present invention.

Claims

1. A cloud computing-based data management method, characterized in that, The method includes: The frontend retrieves user login information and sends it to the backend for identity verification. The backend receives the authentication information sent by the frontend, verifies the user's identity, obtains the corresponding feedback results, and displays them. After the front-end receives a successful authentication response from the back-end, it collects business data from the management system within the user's permission scope and sends the collected business data to the back-end. The backend uses the InterPlanetary File System to classify and store the business data collected from the frontend in the management database, and displays the classification results of the business data. The stored business data is traceable. The backend categorizes and stores the business data collected from the frontend into a management database, including: The backend determines whether the frontend user collecting business data belongs to a pre-defined important role; If so, the backend will categorize and store the business data collected by the frontend into a management database on cloud storage; If not, the backend determines whether the business data collected by the frontend meets either of the following two conditions: the corresponding business type belongs to a set type; the access frequency reaches a set threshold; the set type is a business with pre-configured disaster recovery requirements higher than the set first requirement, and a business with security requirements lower than the set second requirement. If the conditions are met, the backend will categorize and store the business data collected by the frontend into a management database on cloud storage; If the conditions are not met, the backend will categorize and store the business data collected by the frontend into a management database on local storage.

2. The data management method based on cloud computing according to claim 1, characterized in that, The management database includes a first database and a second database that are set up independently, wherein: The first database is used to manage the first mapping relationship between business identifiers and business content, and to store the business content; The second database is used to manage the second mapping relationship between business identifiers and business attributes, and to store the business attributes.

3. The data management method based on cloud computing according to claim 2, characterized in that, The backend categorizes and stores the business data collected from the frontend into a management database, specifically including: Based on the business identifier of the business data, the business content collected by the front end is stored in the first database, and the business attributes collected by the front end are stored in the second database.

4. The data management method based on cloud computing according to claim 2, characterized in that, The method further includes: The backend receives query requests from businesses, which include business attributes. The backend queries the first and second databases based on business attributes to obtain the corresponding business content.

5. A cloud computing-based data management system, characterized in that, Including front-end and back-end; The front end includes: The terminal interaction module is used to obtain user login information and send it to the backend for identity verification. The management data acquisition module is used to collect business data of the management system within the user's permission scope after successful authentication, and transmit the collected business data through the wireless data transmission module; The backend includes: The cloud computing module is used to receive authentication information from the terminal interaction module to verify the user's identity and obtain corresponding feedback results. It is also used to receive business data transmitted through the wireless data transmission module in the management data acquisition module and to classify the business data. The data storage management module, implemented through the InterPlanetary File System, is used to classify and store the service data transmitted by the wireless data transmission module into the management database, where the stored service data is traceable. The data display module is used to display the business data classification results and feedback results of the cloud computing module; The data storage management module is used to classify and store the business data collected from the front end into the management database, including: Determine whether the front-end user collecting business data belongs to a pre-defined important role; If so, the business data collected from the front end will be categorized and stored in the management database on cloud storage; If not, determine whether the business data collected by the front end meets either of the following two conditions: the corresponding business type belongs to the set type; the access frequency reaches the set threshold; the set type is a business with pre-configured disaster recovery requirements higher than the set first requirement condition, and a business with security requirements lower than the set second requirement condition. If the conditions are met, the business data collected from the front end will be categorized and stored in the management database on cloud storage; If the conditions are not met, the business data collected by the front end will be categorized and stored in the management database on local storage.

6. The cloud computing-based data management system according to claim 5, characterized in that, The management database includes a first database and a second database that are set up independently, wherein: The first database is used to manage the first mapping relationship between business identifiers and business content, and to store the business content; The second database is used to manage the second mapping relationship between business identifiers and business attributes, and to store the business attributes.

7. A cloud computing-based data management system according to claim 6, characterized in that, The management data storage module is used to classify and store the service data transmitted by the wireless data transmission module into the management database, specifically including: Based on the service identifier of the service data transmitted by the wireless data transmission module, the service content transmitted by the wireless data transmission module is stored in the first database, and the service attributes transmitted by the wireless data transmission module are stored in the second database.

8. A cloud computing-based data management system according to claim 7, characterized in that, The cloud computing module is also used for: Receive business query requests, which include business attributes; Query the first and second databases based on business attributes to obtain the corresponding business content.

Images