Resource management method, device, storage medium and electronic device

By acquiring and computing the target model relationship between resource data, the problem of high complexity in resource management in the existing technology is solved, and the relationship between resource data is quickly determined and managed, reducing the complexity of resource data management in multi-department collaboration Spend.

CN112988752BActive Publication Date: 2024-11-22BEIJING DA MI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202110337337.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-03-29
Publication Date
2024-11-22
Estimated Expiration
2041-03-29

AI Technical Summary

Technical Problem

In the collaboration between multiple departments, the existing resource management solutions are complex and difficult to automatically generate resource relationships due to the complexity of resource data and the lack of association relationships.

Method used

By obtaining target resource data, determining its corresponding target model, and calculating the target model relationship with other models, and automatically computing and storing the target data relationship between resource data, the complexity of resource data management in multiple departments is reduced.

Benefits of technology

It realizes rapid determination and management of relationships between resource data, reduces development workload, supports dynamic modification of user needs, and reduces the complexity of resource data management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112988752B_ABST
    Figure CN112988752B_ABST
Patent Text Reader

Abstract

The present application discloses a resource management method, device, storage medium and electronic device, which belongs to the field of computer technology. The resource management method includes: obtaining target resource data, and determining the corresponding target model based on the target resource data, obtaining the target model relationship between the target model and other models, and calculating and storing the target data relationship between the target resource data and the corresponding resource data in other models according to the target model relationship. Therefore, the present application can reduce the complexity of multi-department and large-scale related resource data management.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a resource management method, device, storage medium and electronic device. Background Art

[0002] As software applications increase, the amount of resource data required also increases. In the management scenario of R&D-related resources within the same company, there are various types of resources. Each type of resource data is maintained by a dedicated department, and there are many relationships between resources. A system is needed to integrate these resources, connect the relationship data between resources, and flexibly provide data to the outside world.

[0003] However, the existing resource management solution requires finding the maintenance departments of different resources, using the internal system to export the required resource data, standardizing the resource data, and then manually sorting out the resource relationships, which makes the management of resource data more complicated. Summary of the invention

[0004] The embodiments of the present application provide a resource management method, device, storage medium and electronic device to solve the technical problem of complex association management between resource data in the prior art. The technical solution is as follows:

[0005] In a first aspect, an embodiment of the present application provides a resource management method, including:

[0006] Acquiring target resource data, and determining a corresponding target model based on the target resource data;

[0007] Acquire a target model relationship between the target model and other models;

[0008] The target data relationship between the target resource data and corresponding resource data in other models is calculated and stored according to the target model relationship.

[0009] In a second aspect, an embodiment of the present application provides a resource management device, the device comprising:

[0010] A first acquisition module, used to acquire target resource data and determine a corresponding target model based on the target resource data;

[0011] A second acquisition module is used to acquire the target model relationship between the target model and other models;

[0012] The storage module is used to calculate and store the target data relationship between the target resource data and the corresponding resource data in other models according to the target model relationship.

[0013] In a third aspect, an embodiment of the present application provides a computer storage medium, wherein the computer storage medium stores a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing the above-mentioned method steps.

[0014] In a fourth aspect, an embodiment of the present application provides an electronic device, comprising: a memory and a processor; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the above-mentioned method steps.

[0015] The beneficial effects brought about by the technical solutions provided by some embodiments of the present application include at least:

[0016] When the resource management method, device, storage medium and electronic device are working, the target resource data is obtained, and the corresponding target model is determined based on the target resource data, the target model relationship between the target model and other models is obtained, and the target data relationship between the target resource data and the corresponding resource data in other models is calculated and stored according to the target model relationship. By defining different models corresponding to different resource types and determining the relationship between different models, the electronic device can quickly and conveniently determine the relationship between each resource data according to the model corresponding to each type of resource data and the corresponding model relationship, without introducing additional complex secondary development. At the same time, the target model and the relationship between models can be modified at any time according to user needs, so as to realize the modification of the relationship between different types of resource data, thereby reducing the complexity of multi-department resource data management. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0018] Figure 1 It is a schematic diagram of a network architecture of a management system provided by an embodiment of the present application;

[0019] Figure 2 It is a flowchart of a resource management method provided in an embodiment of the present application;

[0020] Figure 3 is another flow chart of a resource management method provided by an embodiment of the present application;

[0021] Figure 4 is a schematic diagram of a receiving resource provided in an embodiment of the present application;

[0022] Figure 5is a schematic diagram of a query resource provided in an embodiment of the present application;

[0023] Figure 6 is a schematic diagram of a modification model provided in an embodiment of the present application;

[0024] Figure 7 This is a schematic diagram of coding generation provided by an embodiment of the present application;

[0025] Figure 8 is a schematic diagram of a resource relationship provided in an embodiment of the present application;

[0026] Fig. 9 is a schematic diagram of a database update provided in an embodiment of the present application;

[0027] Fig.10 is a schematic diagram of a query resource provided in an embodiment of the present application;

[0028] Fig.11 is a schematic diagram of a query resource provided in an embodiment of the present application;

[0029] Fig.12 is a schematic diagram of defining a data interface provided in an embodiment of the present application;

[0030] Fig.13 is a schematic diagram of a query resource provided in an embodiment of the present application;

[0031] Fig.14 is a structural diagram of a resource management device provided in an embodiment of the present application;

[0032] Fig.15 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0033] In order to make the objectives, technical solutions and advantages of the present application more clear, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

[0034] When the following description is designed with drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Instead, they are only examples of devices and methods consistent with some aspects of the present application as detailed in the attached claims.

[0035] In the description of this application, it should be understood that the terms "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. For those of ordinary skill in the art, the specific meanings of the above terms in this application can be understood according to specific circumstances. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the previously associated objects are in an "or" relationship.

[0036] The present application is described in detail below with reference to specific embodiments.

[0037] Figure 1 An exemplary system architecture 100 is shown that can be applied to the resource management method of the present application.

[0038] like Figure 1 As shown, the system architecture 100 may include a user 101, an electronic device 102, and a network 103. The network 103 is used to provide a medium for a communication link between the user 101 and the electronic device 102. The system architecture 100 can be applied to various practical application scenarios. For example, when the system architecture 100 is applied to online live broadcasting, the user 101 may be a teacher or student in an online live broadcasting course, as well as personnel such as R&D background, the user 101 may be used to trigger various instructions on the electronic device 102, the electronic device 102 may be a teacher client, a student client, a background management server, and other devices, and the electronic device 102 may be responsible for, but not limited to, reading various instructions triggered by the user 101, decoding the instructions, and executing the instructions. For example, during an online live course, user 101 (for example, but not limited to Teacher A) needs to upload a piece of audio and video data in order to explain a certain concept more intuitively. User 101 (for example, but not limited to Teacher A) can click the load button with the mouse to trigger the loading of the uploaded audio and video data 1 service, and then the electronic device (for example, but not limited to the teacher client) obtains the target resource data of the audio and video data 1, determines the corresponding target data relationship based on the corresponding target model, and then stores the target resource data and the target data relationship. Other users (for example, but not limited to Student A) can download the target resource data (i.e., audio and video data 1) according to the unique code, and obtain related operations such as the corresponding relationship between each resource data piece.

[0039] The electronic device 102 may be hardware or software. When the electronic device 102 is hardware, it may be various electronic devices having a relationship between a coding generation rule and a sample model, including but not limited to a smart phone, a tablet computer, a laptop computer, and a desktop computer. When the electronic device 102 is software, it may be implemented as multiple software or software modules (for example, to provide distributed storage services), or it may be implemented as a single software or software module, which is not specifically limited here.

[0040] The network 103 may include various types of wired communication links or wireless communication links, and the user 101 and the electronic device 102 may exchange data through the network 103. For example, the wired communication link may include optical fiber, twisted pair or coaxial cable, and the wireless communication link may include Bluetooth communication link, Wireless-Fidelity (Wi-Fi) communication link or microwave communication link.

[0041] It should be understood that Figure 1 The number of users 101, electronic devices 102 and networks 103 in FIG. 1 is only illustrative. Depending on the implementation requirements, there may be any number of users 101, electronic devices 102 and networks 103.

[0042] In the following method embodiments, for the sake of convenience, only the electronic device is used as the execution subject of each step for introduction and description.

[0043] The following will be combined with the attached Figures 2 to 3 , the resource management method provided in the embodiment of the present application is introduced in detail.

[0044] See also Figure 2 , provides an interactive schematic diagram of a resource management method according to an embodiment of the present application. The method may include the following steps:

[0045] S201: Acquire target resource data, and determine a corresponding target model based on the target resource data.

[0046] Generally, resource data can refer to resources in a computer network system, which can be divided into three categories: data resources, software resources, and hardware resources. For example, data resources can include image data, audio and video data, file data, domain name data, etc., software resources can include system software (such as but not limited to operating software, protocol software, etc.) and user software (such as but not limited to live course software, resource management software, and middleware clusters, etc.), and hardware resources can include hardware such as hosts, storage hard disks, and displays. The resource data can coordinate with each other to jointly complete the various business needs of users on electronic devices.

[0047] The target resource data may be any type of resource data in a computer network system. The target resource data here does not specifically refer to a certain type or a class of specific resource data, and is not specifically limited. It may be resource data obtained for the user's current operation in order to distinguish it from other resource data being called for other purposes.

[0048] The target resource data may carry type information and attribute information. The type information may be information used to characterize the type of the target resource data, and may include multiple types such as application class, host class, service class, middleware class, domain name class, and interface class. Electronic devices may be divided into different types according to specific application scenarios, which are not specifically limited here. Attribute information may refer to information about the characteristics, properties, or status of target resource data. Different types of resource data may include different attribute information. For example, the target resource data of the application class may include attribute information such as summary, department, message queue (MQ) cluster, relational database management system MySql cluster, business end ID card number (ID), business end name, project group, business end, application name, target path, application person in charge, programming language, distributed version control system Git warehouse address, application template, application description, upload date, download update record, etc. The target resource data of the host class may include attribute information such as summary, department, host name, host type, service provider, product line, operating system, host environment, etc. The attribute information may be inherent in the resource data itself, or customized by a user or technician, which helps to increase the applicability of the present application and facilitates technicians to set it according to actual needs. No specific limitation is made here.

[0049] The electronic device can determine the type information and attribute information of the target resource data by reading the header file of the target resource data and then parsing the header file. For example, the electronic device can determine that the type of the resource data is a data type by determining that the format of a certain resource data is a bmp format or a jpg format, and then by reading the header file of the bmp format or jpg format resource data, it can determine that the attribute information includes information such as file type, opening method, location, size, occupied space, and creation time. The electronic device can also pre-set the correspondence between the type information and attribute information and the information identifier, and then the electronic device can determine the information identifier of the target resource data, and then query the specific type information and attribute information of the target resource data from the correspondence between the type information and attribute information and the information identifier on the network server, and receive the query result sent from the network server, which helps the electronic device to quickly and accurately determine the information of the target resource data.

[0050] There are many ways for electronic devices to obtain target resource data, which are not specifically limited here. Electronic devices can receive target resource data reported by other related devices. For example, electronic devices can receive stress testing solutions uploaded by technician A in the live stress testing department using host a. Electronic devices can also crawl target resource data that meets certain conditions on the Internet through crawler technology. For example, the live template material research department can crawl relevant resource data about explaining Dream of the Red Chamber on the Internet. Electronic devices can also receive target resource data uploaded by users. For example, in an online live broadcast system, student A shares small videos of his life with other classmates and teachers, or the resource management platform server can receive the teaching template of the first semester English class for the sixth grade uploaded by teacher B, which helps electronic devices to obtain target resource data more conveniently and diversely.

[0051] After acquiring the target resource data, the electronic device can then determine the target model corresponding to the target resource data. The target model can be an abstract data structure used to describe the same type of resource data, which can be understood as a table structure in a database, etc., and can include encoding, display name, data type, description, name attribute, default value, and relationship information (such as but not limited to relationship metadata number, relationship type, source model, source attribute encoding, source end display name, target model, target model encoding, target end display name, version) and other parameters or attributes, which are used here to distinguish other types of models. Relationship information can be information used to describe the relationship between each model. The electronic device can determine the relationship between different models through relationship information, and then determine the relationship between each resource data. The relationship can be various custom relationships such as affiliation, same project relationship, same responsibility, etc.

[0052] The electronic device can customize various attributes of the target model, including operations such as adding, modifying and deleting, and the target model can be used to determine the unique code of the target resource data. There are various ways for the electronic device to determine the target resource data, which are not specifically limited here. For example, the electronic device can determine the target model corresponding to the target resource data through the type information carried by the target resource data. The electronic device determines that the target resource data is a host type, and then determines that the target model is a host-type target model through the correspondence between the type information and the target model. The correspondence between the type information and the target model can be stored locally or in the cloud (for example, but not limited to a storage server), which helps to reduce the storage space of the electronic device and improve operating efficiency.

[0053] The target model may include a corresponding target code generation rule, which may refer to a rule, method or function for obtaining a corresponding code according to the attribute information of the resource data, and the target model and the code generation rule may have a one-to-one correspondence. The correspondence relationship is not specifically limited here, and may be in the form of a relationship correspondence table, etc. The code generation rule may also be one of the parameters of the target model, and the logical relationship between the code generation rule and the target model is not specifically limited here, and may be determined according to actual usage, which helps electronic devices to quickly, conveniently and accurately determine the target code generation rule.

[0054] The target model may include a corresponding target model relationship, and the target model relationship may refer to a relationship, association, etc. between different models obtained according to the attribute information of the resource data. The target model and the target model relationship may be a one-to-one correspondence. The corresponding relationship method is not specifically limited here, and may be in the form of a relationship correspondence table, etc. The target model relationship may also be one of the parameters of the target model. The logical relationship between the target model relationship and the target model is also not specifically limited here, and can be determined according to actual usage, which helps electronic devices to quickly, conveniently and accurately determine the target model relationship.

[0055] In the existing resource relationship acquisition scheme, since resources are distributed and maintained by different development departments, the standards are not unified, and the relationships between different resources are missing, users need to find the maintenance departments of different resources, use the internal system to export the required resource data, standardize the resource data, and manually organize the resource relationships. Resource relationships cannot be automatically generated, and the quality of resource relationship data cannot be guaranteed. A large amount of development and maintenance code is required, resulting in complex management of resource data. In this application, the resource relationship between resource data is determined by defining corresponding models for different types of resource data. After defining the model, the data standard for each type of resource data can be manually set, and there is no need to determine which attributes and other information need to be entered, and to create new columns, tables, etc. to change the storage structure. Through the model relationship definition, resource relationship data is automatically calculated, which is convenient for maintenance and modification, and management attributes (addition, deletion, modification) are defined, which facilitates technical personnel to meet user needs and reduce development workload.

[0056] S202: Obtain a target model relationship between the target model and other models.

[0057] Generally, the target model relationship can be a description of the association relationship between models or tables, which can be understood as a foreign key in the database. For example, an application can be associated with an application process, an application process and a host can be a master-subordinate relationship, an application can be associated with an application domain name, and an application domain name can be associated with a domain name, etc. Relationships can be divided into model relationships and resource relationships. Model relationships are at the model level, and can specify that there is a certain relationship between two models, which can be described by relationship metadata. Resource relationships can refer to two specific resource data, and according to the rules defined by the model relationship, an actual relationship is generated. Relation metadata can include metadata number, relationship type, source model, source attribute model, target model, target attribute code, target end display name, version and other information. Electronic devices can determine the relationship between resource data through relationship metadata. There are many ways for electronic devices to obtain the target model relationship between the target model and other models. For example, the electronic device determines that the target model is numbered A and the other model is numbered B. The electronic device can query in the pre-set model relationship table to determine that model A and model B are in a master-subordinate relationship. In a possible embodiment, the electronic device can also determine the relationship between the target model through the type information and attribute information of the target model and other models. For example: the electronic device determines that the target model C is an application type, and the attribute information includes the live broadcast software 1 function document. The other model D is also an application type, and the attribute information also includes the live broadcast software 1 function document. Then the electronic device can determine that the model relationship between the target model C and the other model D is a relationship of the same type and order. This helps the electronic device to quickly determine the target model relationship, thereby improving the processing efficiency of subsequent steps.

[0058] S203: Calculate and store the target data relationship between the target resource data and corresponding resource data in other models according to the target model relationship.

[0059] Generally, the target data relationship can refer to the specific actual relationship between two resource data, which can include master-child relationship, association relationship, belonging relationship and the same application process loading relationship, etc. Various relationships can be customized, and no specific limitation is made here, in order to correspond to the target resource data and other resource data. After the electronic device obtains the target model relationship between the target model and other models, it can then determine the target data relationship between the target resource data and other specific resource data. For example: the electronic device determines that the target model relationship is an inclusion relationship, and then the resource relationship data can be automatically calculated through the attribute information of the two models. It is determined that the attribute information of the target model and the other models includes creator A and product line 5, then the electronic device can calculate the target resource data-the other resource data is the same layer node relationship associated with the same cluster. The method of calculating the target data relationship in this application is not specifically limited, and can be customized according to the actual use of the user. The user can also enter a modification instruction to modify the calculation method at any time. In a possible embodiment, the other model and the target model can be of the same type or different types, and there is no specific limitation, which helps to improve the adaptability of resource management.

[0060] In a possible embodiment, after the electronic device obtains the target data relationship corresponding to the target resource data, the target data relationship and other attribute information of the target resource data (such as but not limited to storage address, etc.) can be set as a corresponding relationship, and the corresponding relationship is set in a manner including uploading to a database in a storage server, etc. Then, the electronic device can perform processing such as calling on multiple departments and platforms through the unique coding information, which is helpful for multi-department business processing and facilitates maintenance and management.

[0061] It can be seen from the above content that the target resource data is obtained, and the corresponding target model is determined based on the target resource data, the target model relationship between the target model and other models is obtained, and the target data relationship between the target resource data and the corresponding resource data in other models is calculated and stored according to the target model relationship. By defining different models corresponding to different resource types and determining the relationship between different models, the electronic device can quickly and conveniently determine the relationship between each resource data according to the model corresponding to each type of resource data and the corresponding model relationship, without introducing additional complex secondary development. At the same time, the target model and the relationship between models can be modified at any time according to user needs, so as to realize the modification of the relationship between different types of resource data and reduce the complexity of multi-department resource data management.

[0062] See also Figure 3 , another interactive schematic diagram of a resource management method is provided in an embodiment of the present application. The resource management method may include the following steps:

[0063] S301. Obtain sample type information of at least one type and sample common attribute information corresponding to each sample type information.

[0064] Generally, sample type information may refer to type information used to define the corresponding model, and sample common attribute information may refer to attribute information commonly owned by resource data of the same type. For example, an electronic device may obtain two sample type information, data type and software type. The data type may include two resource data, picture a and audio and video b, wherein picture a may include attribute information such as file type, opening method, location, and occupied space, and video b may include attribute information such as file type, location, frame rate, and format. Then, the electronic device may use the file type and location as the sample common attributes corresponding to the data type. In a possible embodiment, the electronic device may receive sample type information reported by the user and sample common attribute information corresponding to each sample type information. The electronic device may also search all local resources to obtain sample type information and sample common attribute information corresponding to each sample type information, which helps the electronic device to quickly and conveniently obtain resource data.

[0065] S302: Determine corresponding sample models according to each sample type information, and determine sample encoding generation rules and sample model relationships corresponding to each sample model according to common attributes of each sample.

[0066] Generally, after the electronic device obtains at least one type of sample type information and the sample common attribute information corresponding to each sample type information, it can determine the corresponding sample models according to each sample type information, and determine the sample code generation rules and sample model relationships corresponding to each sample model according to the common attributes of each sample. For example: the electronic device can define the sample template of the data type as obtaining the sample common attributes file type, location and opening method, etc., and the corresponding sample code generation rule can be set to add the first item and the second item, that is, add the file type and location, which is helpful to generate a unique code based on the existing attribute information and reduce the development workload. The electronic device can define the sample template of the application type as obtaining the sample common attributes application name type, development company and version number, etc., and the corresponding sample code generation rule can be set to add the first item and the third item, that is, add the name type and version number. For example: the electronic device can set the sample model relationship to be an association relationship with other sample models A, an inclusion relationship with other sample templates B, no relationship with other sample templates C, and the same application dynamic library relationship with other sample templates D. The sample model relationship corresponds to the corresponding template model, which can be one of the attribute information in the corresponding sample model, or can be stored in a relationship data table. The electronic device obtains it through query, which helps the electronic device to quickly and efficiently determine the sample coding generation rules and sample model relationships corresponding to each sample model.

[0067] S303: receiving newly added resource data uploaded by the user, querying whether the newly added resource data has a corresponding unique code, and if the newly added resource data does not have a corresponding unique code, taking the newly added resource data as target resource data.

[0068] Generally, the newly added resource data may refer to the resource data uploaded by the current user, which is not specifically limited to a certain resource or a certain type of resource, and is used to distinguish other resources in the electronic device. After the electronic device determines the sample encoding generation rules corresponding to each sample model according to the common attributes of each sample, it can receive the newly added resource data uploaded by the user, such as Figure 4 As shown, the user can first select the resource data to be uploaded (for example, but not limited to file 1), and then upload file 1 to the electronic device by clicking the "Confirm Upload" button on the electronic device display. The electronic device can then query whether the newly added resource data has a corresponding unique code. The query method is not limited. For example, the electronic device can mark the resource data that has generated a unique code as 1, and the resource data that has not generated a unique code as 0. Then the electronic device can quickly traverse all resource data to determine whether the newly added resource data has generated a unique code, so as to prevent repeated coding due to various reasons such as repeated uploading, which wastes computer resources.

[0069] After the electronic device inquires whether there is a corresponding unique code for the newly added resource data, if there is a corresponding unique code for the newly added resource data, there is no need to regenerate the unique code corresponding to the newly added resource data; if there is no corresponding unique code for the newly added resource data, the newly added resource data is used as the target resource data, that is, the unique code corresponding to the newly added resource data needs to be generated subsequently.

[0070] In a possible embodiment, the electronic device can also query all local resource information at a preset time (for example, but not limited to a time period of 2 hours) to query whether all resource data has a corresponding unique code. If there is uncoded resource data in all resource data, the uncoded resource data is used as the target resource data. Figure 5 As shown, assuming that the preset time is 12:00, at non-preset times (for example but not limited to 11:49), the electronic device does not execute the resource query task. Starting at 12:00, the query duration can be customized (for example but not limited to 20 minutes), and the electronic device executes the query of all local resource information services. The progress can also be queried on the electronic device now, and the execution of the query service can also be performed in the background so as not to interfere with the electronic device's execution of the current service, which helps the electronic device to reasonably allocate services and avoid resource waste or insufficient resources.

[0071] S304: Determine the target metadata corresponding to the target resource data based on the type information thereof, and determine the target model corresponding to the target resource data according to the target metadata.

[0072] Generally, the target resource data carries type information and attribute information. The target metadata can be data describing the data, mainly information used to describe the data attributes, which can be used to support functions such as indicating storage location, historical data, resource search, file records, etc. The target metadata is not limited to a certain type or category of metadata, but is to distinguish it from metadata corresponding to other types. For example, the target metadata may include metadata ID, name, resource type, description, version and other information. After the electronic device obtains the target resource data, it can determine the corresponding target metadata based on the type information. For example, the electronic device determines that the target resource data is an application (such as but not limited to online live broadcast software) type, and then determines that the target metadata corresponding to the application type may include host type, Media Access Control Address (Mac) address, host person in charge, operating system kernel release version and product line and other information.

[0073] Then the electronic device can determine the application target model corresponding to the type of application (such as but not limited to online live broadcast software) based on the target metadata, and all specific parameters of the target metadata of the target model corresponding to the target resource data can be obtained through the application target model. That is, after the electronic device receives the reported resource data, it can load the corresponding target model according to the type information carried by the resource data, and then determine the specific parameters of the metadata of the target model (such as but not limited to the attribute information of the resource data and the corresponding encoding generation rules and model relationships). Finally, the electronic device can input the specific parameters of the metadata of the target model (that is, the attribute set data of the resource data) according to the encoding generation rules, calculate the encoding generation rules, generate a unique code, and then calculate the actual data relationship between the target resource data and other resource data according to the model relationship, which helps the electronic device to accurately and quickly determine the target model.

[0074] S305: Receive a model modification instruction, modify the target metadata of the target model based on the model modification instruction, the target metadata corresponds to the target model relationship, and use the modified target model as the target model corresponding to the target resource data.

[0075] Generally, a model modification instruction may refer to an instruction used to modify the metadata of a model corresponding to a certain type of resource data (such as but not limited to instructions such as adding, deleting, and modifying). After the electronic device determines the target model corresponding to the target resource data, it may also receive a model modification instruction, and modify the target metadata of the target model based on the model modification instruction. For example, the electronic device first determines through the target model that the first item of the target model metadata (i.e., the specific attribute information of the target resource data) is the business line: business line 3, the second item is the region to which the machine belongs: region B, and the third item is the number of processor cores: 4 cores. The corresponding relationship of the target model is an association relationship with model A and a master-subordinate relationship with model B.

[0076] Then, the electronic device determines, based on the model modification instruction, that the first item of the modified target model metadata (i.e., the specific attribute information of the target resource data) is the business line: Business Line 3, the second item is the region of the machine: Region B, and the third item is the number of processor cores: 6 cores. The corresponding target model relationship is a master-sub relationship with model A and an association relationship with model B. The correspondence between the target metadata and the target model relationship can be understood as the target model relationship being one of the metadata in the target model. For example, the fourth item is the target model relationship: it is an association relationship with model C and a master-sub relationship with model D. It can also be understood as the target model relationship having a corresponding relationship with the target model. The logical relationship and the specific correspondence method are not specifically limited. Figure 6 As shown, the user can first modify the metadata of the target model on the model modification interface, such as starting with business line No. 3 and target model relationship as an association relationship with model 1, and change the current business line to No. 2 and target model relationship to a master-subordinate relationship with model 1, and modify by clicking the "Confirm Modification" button on the electronic device. Finally, the current information of the model can be viewed in the current model metadata interface, which helps the electronic device to process batch calculation resource relationships for similar resource data. Finally, the electronic device uses the modified target model as the target model corresponding to the target resource data.

[0077] S306: Acquire target metadata of the target model, and determine metadata relationships between the target model and other models based on the target metadata.

[0078] Generally, metadata relationship can refer to the relationship information between the target model and other models, and can be part of the data in the target metadata. After the electronic device uses the modified target model as the target model corresponding to the target resource data, the target data relationship can be determined through the target model. For example, the target metadata determined by the electronic device includes metadata number, name, resource type, description, version, encoding generation rule, model attribute metadata and metadata relationship, etc., wherein the metadata relationship can include metadata relationship number: 123456, relationship type: master-child relationship, source model: host type, source attribute code: abc, source end display name host number 1, target model: model 1 and target model code: 456789. The metadata relationship can include the relationship information of one or more other models. The number of data and specific information here are not limited and can be customized according to user needs.

[0079] S307: Determine a target model relationship between the target model and other models in the sample model relationship according to the metadata relationship between the target model and other models.

[0080] Generally, after determining the metadata relationship between the target model and the other models, the electronic device can determine the target model relationship between the target model and the other models. For example, the electronic device determines that the metadata relationship between the target model and the other models includes the corresponding model: model 1 and the corresponding model code: 456789. The sample model relationship previously determined by the electronic device in the target model includes an association relationship with model 1, a master-sub relationship with model 2, a same-order relationship with model 3, and a same-business relationship with model 4, etc. The electronic device can quickly and accurately determine that the target model relationship between the target model and other models is an association relationship by querying the corresponding model or random model code.

[0081] S308. Generate a unique code corresponding to the target resource data according to the target code generation rule and the attribute information, determine the target data relationship between the target resource data and the corresponding resource data in other models based on the target model relationship and the unique code, and store the target data relationship.

[0082] Generally, after determining the target model relationship between the target model and other models, the electronic device can determine the target data relationship between the target resource data and the corresponding resource data in other models. For example, the electronic device determines that the first item of the modified target model metadata (i.e., the specific attribute information of the target resource data) is the business line: business line 3, the second item is the machine area: area B, and the third item is the number of processor cores: 6 cores. The corresponding target code generation rule is to use the first item and the third item of the target metadata to add b3631c65241c991c979bfddaad4ef1e1, and the electronic device uses this value as the unique code corresponding to the target resource data. Then the electronic device can determine that the target data relationship with the corresponding resource data a in other models is a same-order library file relationship for loading the same business, etc. through the target model relationship (such as but not limited to the association relationship) and the attribute information of other resource data a (such as but not limited to the service provider, usage description, cluster name, etc.).

[0083] After the electronic device determines the target data relationship between the target resource data and the corresponding resource data in other models, the unique codes corresponding to the target resource data and other resource data can also be corresponding. The user can determine the data relationship between different resource data according to the different unique codes corresponding to different resource data, which is helpful for resource management and maintenance. Figure 7 As shown, the electronic device can customize the code generation rules (such as but not limited to rule 1 and rule 2), and then customize the attribute information on the code generation interface on the electronic device, and then click the "OK" button to generate a unique code corresponding to the target resource data. Figure 8 As shown, the data relationship can be represented by a model topology diagram with the application as the center. The application domain name is associated with the application, the application domain name is associated with a specific domain name, MQ applications are associated with each other, the MQ cluster and the MQ application are the master-child relationship, the MQ cluster and the MQ node are the master-child relationship, etc.

[0084] S309: Store the original data corresponding to the target resource data and the target data relationship in a relational database, and update the index database and the graph database based on the target data relationship.

[0085] Generally, a relational database can be a database used to store resource data raw data and data relationships (such as but not limited to MySql database), which can include model metadata, relationship metadata, resource data, resource relationship data, raw data, etc. An index database can refer to a database used to search and query resource data (such as but not limited to ES database), and its functions can include indexing (automatically created for each main model, supporting sub-models, etc.), drawing mapping (automatically created according to model attribute definitions, etc.) and word segmentation (IK word segmentation, full-text indexing, etc.), real-time update of resource data, and consistency with the original data, etc. A graph database can be a database used to represent resource data relationships (such as but not limited to NEO4J database), which can include nodes (which can correspond to resource data) and edges (which can represent relationship data between resource data), real-time update of resource data, and consistency with the original data, etc.

[0086] For example: after the electronic device determines the target data relationship between the target resource data and the corresponding resource data in other models, the original data (such as 30M data size) corresponding to the target resource data (such as but not limited to live courseware 1) and the target data relationship (such as association relationship with live courseware 2, inclusion relationship with picture 1, etc.) are stored in the relational database, and the index database and graph database are updated based on the target data relationship. Fig. 9 As shown, the electronic device obtains a message corresponding to the MQ data type, and then determines the corresponding target data relationship, and then adds MQ node 2 in the graph database.

[0087] S310: Generate a corresponding data interface based on the metadata of each model, receive a query instruction based on the data interface, and obtain a data relationship of resource data corresponding to the query code according to the query code.

[0088] Generally, the data interface can refer to obtaining resource data in the electronic device through the Hypertext Transfer Protocol (HTTP) protocol. Generally, the electronic device can call the data interface in the external program code, pass in parameters, and obtain the specified resource data. The data interface can include: a general interface and a custom interface. The general interface can be automatically generated after each model definition is completed, such as: adding, deleting, querying, and modifying the resource data in the specified "model". The calling method, format and parameters of the general interface can be fixed. If the third party has personalized needs, for example: do not want the interface to return all resource attributes, only want to return part of the attributes, etc., these needs cannot be met by the general interface, and a custom interface is needed to support it. The query instruction can refer to an instruction used to query the data relationship between different resource data. The query instruction can carry a first query code and a second query code. The first query code can correspond to the first resource data, and the second query code can correspond to the second resource data. For example, the electronic device analyzes the query instruction and determines that the first query code is 123456789 and the second query code is 987654321. Then, the two query codes can be input into the resource management platform of the electronic device to obtain relationship information such as resources belonging to the same category, developed by the same department and applied to the same project. Fig.10 As shown, the electronic device determines two unique codes (for example but not limited to 123456 and 456789), and then the data relationship between the two corresponding resource data can be queried by clicking the "Relationship Query" button in the code relationship query interface on the electronic device.

[0089] like Fig.11 As shown, the electronic device can customize the query resource data. For example, the electronic device can determine that the current model is an application type, and then click the "OK" button on the query interface of the electronic device to determine that the total amount of valid application type data is 1815, of which 999 are not associated with other resource data (partially represented by available fan-shaped area 2), and 816 are associated with other resource data (partially represented by available fan-shaped area 1). The total amount of relationship data of the application type is determined to be 19906, of which 11663 are resource data of the ES cluster (partially represented by available fan-shaped area 1), 3469 are resource data of the MySql cluster (partially represented by available fan-shaped area 2), 678 are resource data of the MQ cluster (partially represented by available fan-shaped area 3), 468 are resource data of the service (partially represented by available fan-shaped area 4), and so on.

[0090] like Fig.12As shown, the electronic device can generate the interface path of the custom API through the custom API basic information (such as but not limited to name, target model, description, filter conditions, grouping, status, maximum number of returns per page, parameters, model attributes, operators, attributes, value main model attributes and sub-model attributes - application process list, etc.), and then the electronic device can generate the required information through the interface path. Fig.13 As shown, the electronic device can also customize the input settings, display the resource list, and then display specific information by clicking buttons such as "Details", "Modify Records", "Relationship Calculation", and "Relationship Topology". It can also search for resource data that meets user needs based on filtering conditions.

[0091] When the scheme of the embodiment of the present application is executed, the target resource data is obtained, and the corresponding target model is determined based on the target resource data, the target model relationship between the target model and other models is obtained, and the target data relationship between the target resource data and the corresponding resource data in other models is calculated and stored according to the target model relationship. By defining different models corresponding to different resource types and determining the relationship between different models, the electronic device can quickly and conveniently determine the relationship between each resource data according to the model corresponding to each type of resource data and the corresponding model relationship, without introducing additional complex secondary development. At the same time, the target model and the relationship between models can be modified at any time according to user needs, so as to realize the modification of the relationship between different types of resource data, thereby reducing the complexity of multi-department resource data management.

[0092] The following is an embodiment of the device of the present application, which can be used to execute the embodiment of the method of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the method of the present application.

[0093] See also Fig.14 , which shows a schematic diagram of the structure of a resource management device provided by an exemplary embodiment of the present application, hereinafter referred to as management device 14. Management device 14 can be implemented as all or part of the terminal through software, hardware or a combination of both. It includes:

[0094] A first acquisition module 1401 is used to acquire target resource data and determine a corresponding target model based on the target resource data;

[0095] The second acquisition module 1402 is used to acquire the target model relationship between the target model and other models;

[0096] The storage module 1403 is used to calculate and store the target data relationship between the target resource data and the corresponding resource data in other models according to the target model relationship.

[0097] In a possible embodiment, the management device 14 further includes:

[0098] A third acquisition module is used to acquire at least one type of sample type information and sample common attribute information corresponding to each sample type information;

[0099] The first determination module is used to determine the corresponding sample models according to the sample type information, and to determine the sample coding generation rules and sample model relationships corresponding to the sample models according to the common attributes of the samples.

[0100] In a possible embodiment, the first acquisition module 1401 includes:

[0101] A first receiving unit, configured to receive newly added resource data uploaded by a user, and query whether the newly added resource data has a corresponding unique code;

[0102] The first determining unit is configured to use the newly added resource data as target resource data if there is no corresponding unique code for the newly added resource data.

[0103] In a possible embodiment, the first acquisition module 1401 includes:

[0104] A second determining unit, configured to determine the corresponding target metadata based on the type information of the target resource data;

[0105] The third determining unit is used to determine the target model corresponding to the target resource data according to the target metadata.

[0106] In a possible embodiment, the management device 14 further includes:

[0107] A first receiving module, configured to receive a model modification instruction, and modify target metadata of the target model based on the model modification instruction, wherein the target metadata corresponds to the target model relationship;

[0108] The second determining module is used to use the modified target model as the target model corresponding to the target resource data.

[0109] In a possible embodiment, the second obtaining module 1402 includes:

[0110] A first acquisition unit, configured to acquire target metadata of the target model, and determine a metadata relationship between the target model and the other models based on the target metadata;

[0111] The fourth determining unit is used to determine the target model relationship between the target model and other models in the sample model relationship according to the metadata relationship between the target model and the other models.

[0112] In a possible embodiment, the storage module 1403 includes:

[0113] A generating unit, configured to generate a unique code corresponding to the target resource data according to the target code generating rule and the attribute information;

[0114] A fifth determining unit is used to determine the target data relationship between the target resource data and corresponding resource data in other models based on the target model relationship and the unique code, and store the target data relationship.

[0115] In a possible embodiment, the storage module 1403 further includes:

[0116] A storage unit, used to store the original data corresponding to the target resource data and the target data relationship in a relational database;

[0117] An updating unit is used to update the index database and the graph database based on the target data relationship.

[0118] In a possible embodiment, the management device 14 further includes:

[0119] A generation module is used to generate corresponding data interfaces based on the metadata of each model;

[0120] A second receiving module, configured to receive a query instruction based on the data interface; wherein the query instruction carries a query code;

[0121] The query module is used to obtain the data relationship of the resource data corresponding to the query code according to the query code.

[0122] The embodiments of this application and Figures 2 to 3 The method embodiments are based on the same concept, and the technical effects they bring are also the same. The specific process can be referred to Figures 2 to 3 The description of the method embodiment will not be repeated here.

[0123] The device 14 can be a field-programmable gate array (FPGA), a dedicated integrated chip, a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processing circuit, a microcontroller unit (MCU), and a programmable logic device (PLD) or other integrated chips.

[0124] When the scheme of the embodiment of the present application is executed, the target resource data is obtained, and the corresponding target model is determined based on the target resource data, the target model relationship between the target model and other models is obtained, and the target data relationship between the target resource data and the corresponding resource data in other models is calculated and stored according to the target model relationship. By defining different models corresponding to different resource types and determining the relationship between different models, the electronic device can quickly and conveniently determine the relationship between each resource data according to the model corresponding to each type of resource data and the corresponding model relationship, without introducing additional complex secondary development. At the same time, the target model and the relationship between models can be modified at any time according to user needs, so as to realize the modification of the relationship between different types of resource data, thereby reducing the complexity of multi-department resource data management.

[0125] The present application also provides a computer storage medium, which can store multiple instructions, which are suitable for being loaded by a processor and executing the above method steps. The specific execution process can be seen in Figure 2 or Figure 3 The specific description of the illustrated embodiment will not be repeated here.

[0126] The present application also provides a computer program product, which stores at least one instruction, and the at least one instruction is loaded and executed by the processor to implement the template control method described in the above embodiments.

[0127] See also Fig.15 , is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Fig.15 As shown, the electronic device 15 may include: at least one processor 1501 , at least one network interface 1504 , a user interface 1503 , a memory 1505 , and at least one communication bus 1502 .

[0128] The communication bus 1502 is used to realize the connection and communication between these components.

[0129] The user interface 1503 may include a display screen (Display) and a camera (Camera), and the optional user interface 1503 may also include a standard wired interface and a wireless interface.

[0130] The network interface 1504 may optionally include a standard wired interface or a wireless interface (such as a WI-FI interface).

[0131] Among them, the processor 1501 may include one or more processing cores. The processor 1501 uses various interfaces and lines to connect various parts in the entire terminal 1500, and executes various functions and processes data of the terminal 1500 by running or executing instructions, programs, code sets or instruction sets stored in the memory 1505, and calling data stored in the memory 1505. Optionally, the processor 1501 can be implemented in at least one hardware form of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), and programmable logic array (Programmable Logic Array, PLA). The processor 1501 can integrate one or a combination of a central processing unit (Central Processing Unit, CPU), a graphics processing unit (Graphics Processing Unit, GPU) and a modem. Among them, the CPU mainly processes the operating system, user interface and application programs; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 1501, and it can be implemented separately through a chip.

[0132] Among them, the memory 1505 may include a random access memory (Random Access Memory, RAM) and may also include a read-only memory (Read-Only Memory). Optionally, the memory 1505 includes a non-transitory computer-readable storage medium. The memory 1505 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 1505 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned method embodiments, etc.; the data storage area may store data involved in the above-mentioned method embodiments, etc. The memory 1505 may optionally be at least one storage device located away from the aforementioned processor 1501. As Fig.15 As shown, the memory 1505 as a computer storage medium may include an operating system, a network communication module, a user interface module, and a resource management application.

[0133] exist Fig.15In the electronic device 1500 shown, the user interface 1503 is mainly used to provide an input interface for the user and obtain data input by the user; and the processor 1501 can be used to call the resource management application stored in the memory 1505 and specifically perform the following operations:

[0134] Acquiring target resource data, and determining a corresponding target model based on the target resource data;

[0135] Acquire a target model relationship between the target model and other models;

[0136] The target data relationship between the target resource data and corresponding resource data in other models is calculated and stored according to the target model relationship.

[0137] In one embodiment, before executing the acquisition of target resource data, the processor 1501 is further configured to execute:

[0138] Obtaining at least one type of sample type information and sample common attribute information corresponding to each sample type information;

[0139] The corresponding sample models are determined according to the sample type information, and the sample encoding generation rules and sample model relationships corresponding to the sample models are determined according to the common attributes of the samples.

[0140] In one embodiment, when the processor 1501 executes the method of obtaining target resource data, it specifically executes:

[0141] Receive new resource data uploaded by the user, and query whether the new resource data has a corresponding unique code;

[0142] If the newly added resource data does not have a corresponding unique code, the newly added resource data is used as the target resource data.

[0143] In one embodiment, when the processor 1501 determines the corresponding target model based on the target resource data, it specifically performs:

[0144] Determine the corresponding target metadata based on the type information of the target resource data;

[0145] A target model corresponding to the target resource data is determined according to the target metadata.

[0146] In one embodiment, after the processor 1501 executes the step of determining the corresponding target model based on the target resource data, the processor 1501 is further configured to execute:

[0147] receiving a model modification instruction, and modifying target metadata of the target model based on the model modification instruction, wherein the target metadata corresponds to the target model relationship;

[0148] The modified target model is used as the target model corresponding to the target resource data.

[0149] In one embodiment, when the processor 1501 executes the step of obtaining the target model relationship between the target model and other models, the processor 1501 specifically executes:

[0150] Acquire target metadata of the target model, and determine metadata relationships between the target model and other models based on the target metadata;

[0151] According to the metadata relationships between the target model and the other models, the target model relationships between the target model and the other models are determined in the sample model relationships.

[0152] In one embodiment, when the processor 1501 calculates and stores the target data relationship between the target resource data and the corresponding resource data in other models according to the target model relationship, it specifically executes:

[0153] Generate a unique code corresponding to the target resource data according to the target code generation rule and the attribute information;

[0154] A target data relationship between the target resource data and corresponding resource data in other models is determined based on the target model relationship and the unique code, and the target data relationship is stored.

[0155] In one embodiment, when the processor 1501 calculates and stores the target data relationship between the target resource data and the corresponding resource data in other models according to the target model relationship, it specifically executes:

[0156] The original data corresponding to the target resource data and the target data relationship are stored in a relational database;

[0157] The index database and the graph database are updated based on the target data relationship.

[0158] In one embodiment, after the processor 1501 calculates and stores the target data relationship between the target resource data and the corresponding resource data in other models according to the target model relationship, it is further configured to execute:

[0159] Generate corresponding data interfaces based on the metadata of each model;

[0160] Receiving a query instruction based on the data interface; wherein the query instruction carries a query code;

[0161] The data relationship of the resource data corresponding to the query code is obtained according to the query code.

[0162] The technical concept and Figure 2 or Figure 3 The technical concept is the same as that of Figure 2 or Figure 3 The method embodiments are not described in detail here.

[0163] In an embodiment of the present application, target resource data is obtained, and a corresponding target model is determined based on the target resource data, a target model relationship between the target model and other models is obtained, and a target data relationship between the target resource data and corresponding resource data in other models is calculated and stored according to the target model relationship. By defining different models corresponding to different resource types and determining the relationship between different models, the electronic device can quickly and conveniently determine the relationship between each resource data according to the model corresponding to each type of resource data and the corresponding model relationship, without introducing additional complex secondary development. At the same time, the target model and the relationship between models can be modified at any time according to user needs, so as to realize the modification of the relationship between different types of resource data, thereby reducing the complexity of multi-department resource data management.

[0164] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing related hardware through a computer program, and the program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The storage medium can be a disk, an optical disk, a read-only storage memory, or a random access memory, etc.

[0165] The above disclosure is only the preferred embodiment of the present application, which certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the present application.

Claims

1. A resource management method, characterized in that: The method comprises: Obtaining at least one type of sample type information and sample common attribute information corresponding to each sample type information; Determine the corresponding sample models according to the sample type information, and determine the sample encoding generation rules and sample model relationships corresponding to the sample models according to the common attributes of the samples; Acquire target resource data, and determine a corresponding target model based on the target resource data, wherein the target model includes a corresponding target code generation rule; Acquire a target model relationship between the target model and other models; The acquiring the target model relationship between the target model and other models includes: Acquire target metadata of the target model, and determine metadata relationships between the target model and other models based on the target metadata; According to the metadata relationship between the target model and the other models, determining the target model relationship between the target model and other models in the sample model relationship; Calculate and store the target data relationship between the target resource data and the corresponding resource data in other models according to the target model relationship; The step of calculating and storing the target data relationship between the target resource data and corresponding resource data in other models according to the target model relationship includes: Generate a unique code corresponding to the target resource data according to the target code generation rule and the attribute information; Determine a target data relationship between the target resource data and corresponding resource data in other models based on the target model relationship and the unique code, and store the target data relationship; After calculating and storing the target data relationship between the target resource data and the corresponding resource data in other models according to the target model relationship, the method further includes: Generate corresponding data interfaces based on the metadata of each model; Receiving a query instruction based on the data interface; wherein the query instruction carries a query code; The data relationship of the resource data corresponding to the query code is obtained according to the query code.

2. The method according to claim 1, characterized in that: The obtaining of target resource data includes: Receive new resource data uploaded by the user, and query whether the new resource data has a corresponding unique code; If the newly added resource data does not have a corresponding unique code, the newly added resource data is used as the target resource data.

3. The method according to claim 1, characterized in that: The determining the corresponding target model based on the target resource data includes: Determine the corresponding target metadata based on the type information of the target resource data; A target model corresponding to the target resource data is determined according to the target metadata.

4. The method according to claim 1, characterized in that: After determining the corresponding target model based on the target resource data, the method further includes: receiving a model modification instruction, and modifying target metadata of the target model based on the model modification instruction, wherein the target metadata corresponds to the target model relationship; The modified target model is used as the target model corresponding to the target resource data.

5. The method according to claim 1, characterized in that: The target data relationship between the target resource data and the corresponding resource data in other models is calculated and stored according to the target model relationship, and further includes: The original data corresponding to the target resource data and the target data relationship are stored in a relational database; The index database and the graph database are updated based on the target data relationship.

6. A resource management device, characterized in that: include: A first acquisition module, used to acquire at least one type of sample type information and sample common attribute information corresponding to each sample type information; Determine the corresponding sample models according to the sample type information, and determine the sample encoding generation rules and sample model relationships corresponding to the sample models according to the common attributes of the samples; Acquire target resource data, and determine a corresponding target model based on the target resource data, wherein the target model includes a corresponding target code generation rule; A second acquisition module is used to acquire the target model relationship between the target model and other models; The acquiring the target model relationship between the target model and other models includes: Acquire target metadata of the target model, and determine metadata relationships between the target model and other models based on the target metadata; According to the metadata relationship between the target model and the other models, determining the target model relationship between the target model and other models in the sample model relationship; A storage module, used for calculating and storing the target data relationship between the target resource data and the corresponding resource data in other models according to the target model relationship; Calculating and storing the target data relationship between the target resource data and corresponding resource data in other models according to the target model relationship includes: Generate a unique code corresponding to the target resource data according to the target code generation rule and the attribute information; Determine a target data relationship between the target resource data and corresponding resource data in other models based on the target model relationship and the unique code, and store the target data relationship; After calculating and storing the target data relationship between the target resource data and the corresponding resource data in other models according to the target model relationship, the method further includes: Generate corresponding data interfaces based on the metadata of each model; Receiving a query instruction based on the data interface; wherein the query instruction carries a query code; The data relationship of the resource data corresponding to the query code is obtained according to the query code.

7. A computer storage medium, characterized in that: The computer storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor and executing the method steps according to any one of claims 1 to 5.

8. An electronic device, characterized in that: include: A memory and a processor; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the method steps as claimed in any one of claims 1 to 5.