CN111325456B - Asset data processing method and apparatus, computer system, and storage medium - Google Patents

Asset data processing method and apparatus, computer system, and storage medium Download PDF

Info

Publication number
CN111325456B
CN111325456B CN202010094896.XA CN202010094896A CN111325456B CN 111325456 B CN111325456 B CN 111325456B CN 202010094896 A CN202010094896 A CN 202010094896A CN 111325456 B CN111325456 B CN 111325456B
Authority
CN
China
Prior art keywords
asset
model
attribute
configuration
asset data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202010094896.XA
Other languages
Chinese (zh)
Other versions
CN111325456A (en
Inventor
魏世嘉
叶齐娇
陈璐璐
万里鹏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Industrial and Commercial Bank of China Ltd ICBC
Original Assignee
Industrial and Commercial Bank of China Ltd ICBC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Industrial and Commercial Bank of China Ltd ICBC filed Critical Industrial and Commercial Bank of China Ltd ICBC
Priority to CN202010094896.XA priority Critical patent/CN111325456B/en
Publication of CN111325456A publication Critical patent/CN111325456A/en
Application granted granted Critical
Publication of CN111325456B publication Critical patent/CN111325456B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
    • G06Q10/06312—Adjustment or analysis of established resource schedule, e.g. resource or task levelling, or dynamic rescheduling

Abstract

The present disclosure provides an asset data processing method, including: receiving an asset data adding request, wherein the asset data adding request comprises type information, attribute information and associated information of asset data to be added; determining whether configuration information matched with the asset data to be added is stored in the asset configuration model or not according to the type information and the attribute information; if the asset configuration model stores configuration information matched with the asset data to be added, storing the type information and the attribute information of the asset data to be added into the asset data model; and storing the association information of the asset data to be added into the asset association relation model. The present disclosure also provides an asset data processing apparatus, a computer system, and a storage medium.

Description

Asset data processing method and apparatus, computer system, and storage medium
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to an asset data processing method and apparatus, a computer system, and a storage medium.
Background
Currently, as the size of an enterprise gradually increases, the enterprise has more and more assets. Due to the wide variety of assets, it is now common to store data for each type of asset in one data model, which may be, for example, a database table.
However, as the business changes, the asset types, attributes, and associations also change, which makes storage of assets challenging. For example, each time an asset type is added, the table building operation needs to be performed again, more and more storage space is occupied as the assets are increased, and each business change needs to be performed one by one for each type of data model, which undoubtedly causes waste of time and space cost.
Disclosure of Invention
In view of the above, the present disclosure provides an asset data processing method and apparatus, a computer system, and a storage medium.
One aspect of the present disclosure provides an asset data processing method, including: receiving an asset data adding request, wherein the asset data adding request comprises type information, attribute information and associated information of asset data to be added; determining whether configuration information matched with the asset data to be added is stored in the asset configuration model or not according to the type information and the attribute information; if the asset configuration model stores configuration information matched with the asset data to be added, storing the type information and the attribute information of the asset data to be added into the asset data model, wherein the asset data model and the asset configuration model establish a mapping relation through the type identification and the attribute identification of the asset data stored respectively; and storing the association information of the asset data to be added into the asset association relation model, wherein the asset association relation model and the asset data model establish a mapping relation through the asset identification of the asset data stored respectively.
Another aspect of the present disclosure provides an asset data processing apparatus comprising: the first receiving module is used for receiving an asset data adding request, wherein the asset data adding request comprises type information, attribute information and associated information of asset data to be added; the first determining module is used for determining whether the asset configuration model stores configuration information matched with the asset data to be added or not according to the type information and the attribute information; the first adding module is used for storing the type information and the attribute information of the asset data to be added into the asset data model if the asset configuration model stores configuration information matched with the asset data to be added, wherein the asset data model and the asset configuration model establish a mapping relation through the type identification and the attribute identification of the asset data stored in the asset data model and the asset configuration model respectively; and the second adding module is used for storing the association information of the asset data to be added into the asset association relation model, wherein the asset association relation model and the asset data model establish a mapping relation through the asset identification of the asset data stored in the asset association relation model and the asset data model.
Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions for implementing the method as described above when executed.
Another aspect of the disclosure provides a computer program comprising computer executable instructions for implementing the method as described above when executed.
Another aspect of the present disclosure provides a computer system comprising: one or more processors; storage means for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method as described above.
According to the embodiment of the disclosure, under the condition that the asset configuration model is determined to store the configuration information matched with the asset data to be added, the type information and the attribute information of the asset data to be added are stored in the asset data model, and the association information of the asset data to be added is stored in the asset association relation model. The asset configuration model is used for storing asset configuration information, the asset data model is used for storing asset types and attribute information, and the asset incidence relation model is used for storing asset incidence relations, so that all types of asset data can be stored in the asset configuration model, the asset data model and the asset incidence relation model, the storage of complex and various asset data is supported, and the storage space is saved.
Drawings
The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments of the present disclosure with reference to the accompanying drawings, in which:
FIG. 1 schematically illustrates an exemplary system architecture for an asset data processing method and apparatus to which embodiments of the present disclosure may be applied;
FIG. 2 schematically illustrates a block diagram of a storage system 200 according to an embodiment of the present disclosure;
FIG. 3 schematically illustrates a flow diagram of an asset data processing method according to an embodiment of the disclosure;
FIG. 4 schematically illustrates a block diagram of an asset data model 202, in accordance with an embodiment of the present disclosure;
FIG. 5 schematically illustrates a flow diagram for storing type information and attribute information of asset data to be added to asset data model 202, in accordance with an embodiment of the present disclosure;
FIG. 6 schematically illustrates a flow diagram for storing type configuration information and attribute configuration information into an asset configuration model 201;
FIG. 7 schematically illustrates a block diagram of an asset configuration model 201 according to an embodiment of the disclosure;
FIG. 8 schematically illustrates a flow diagram for storing type configuration information and attribute configuration information into an asset configuration model 201, according to another embodiment of the disclosure;
FIG. 9 schematically illustrates a flow chart for determining whether configuration information matching to-be-added asset data is stored in the asset configuration model 201 according to an embodiment of the disclosure;
FIG. 10 schematically illustrates an internal mapping diagram of an asset configuration model 201 and an asset data model 202 of an embodiment of the disclosure;
FIG. 11 schematically illustrates a flow chart of an asset data manipulation method of an embodiment of the present disclosure;
FIG. 12 schematically illustrates a flow chart of an asset data manipulation method of an embodiment of the present disclosure;
FIG. 13 schematically illustrates a block diagram of an asset data processing device 700, according to an embodiment of the present disclosure; and
fig. 14 schematically illustrates a block diagram of a computer system 1400 suitable for implementing a robot in accordance with an embodiment of the disclosure.
Detailed Description
Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.
Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a convention analogous to "A, B or at least one of C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B or C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).
The embodiment of the disclosure provides an asset data processing method and device. The method comprises the steps of receiving an asset data adding request, wherein the asset data adding request comprises type information, attribute information and associated information of asset data to be added; determining whether configuration information matched with the asset data to be added is stored in the asset configuration model or not according to the type information and the attribute information; if the asset configuration model stores configuration information matched with the asset data to be added, storing the type information and the attribute information of the asset data to be added into the asset data model, wherein the asset data model and the asset configuration model establish a mapping relation through the type identification and the attribute identification of the asset data stored respectively; and storing the association information of the asset data to be added into the asset association relation model according to the configuration information, wherein the asset association relation model and the asset data model establish a mapping relation through the asset identification of the asset data stored in the asset association relation model and the asset data model respectively.
FIG. 1 schematically illustrates an example system architecture 100 to which the asset data processing methods and apparatus according to embodiments of the present disclosure may be applied. It should be noted that fig. 1 is only an example of a system architecture to which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, and does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.
As shown in fig. 1, the system architecture 100 according to this embodiment may include a terminal device 101, a terminal device 102, a server 103, a network 104, and a network 105. The terminal device 101 may provide an operation interface for an administrator, where the administrator may be a user with a specific operation authority, such as an asset configuration authority. The terminal device 102 may provide an operation interface for a general user.
The administrator may use the terminal device 101 to interact with the server 103 via the network 104 to receive or send messages or the like. For example, the terminal device 101 may receive an operation instruction of asset configuration operated by an administrator, transmit the operation instruction to the server 103 via the network 104, and cause the server 103 to execute the operation instruction, thereby completing asset configuration.
An ordinary user can use the terminal apparatus 102 to interact with the server 103 through the network 105 to receive or transmit a message or the like. For example, the terminal device 102 may receive an operation instruction for adding, deleting, querying and/or modifying asset data operated by a user, and send the operation instruction to the server 103 through the network 105, so that the server 103 executes the operation instruction to complete the addition, deletion, querying and/or modification of the asset. For another example, the terminal device 102 may receive an operation instruction for a user to add, delete, query and/or modify an asset association relationship, and send the operation instruction to the server 103 through the network 105, so that the server 103 executes the operation instruction to complete the addition, deletion, query and/or modification of the asset association relationship.
Terminal device 101 and terminal device 102 may be various electronic devices having display screens and supporting visual operations, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like. The server 103 may be a server that provides various services, such as a background management server (for example only) that provides support for a user with an interface operated by the terminal device 101 or the terminal device 102. The backend management server may analyze and perform other processing on the received data such as the user request, and feed back a processing result (for example, obtain information or data according to the user request) to the terminal device 101 or the terminal device 102.
It should be noted that the asset data processing method provided by the embodiment of the present disclosure may be generally executed by the server 103. The asset data processing method provided by the embodiment of the present disclosure may also be executed by a server or a server cluster that is different from the server 103 and is capable of communicating with the terminal device 101, the terminal device 102, and/or the server 103.
It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
According to the embodiment of the disclosure, the asset types are various, and the asset attributes contained in different asset types are different. For example, the asset types may include credit card business types, savings card business types, and the like. The credit card service type may include various attributes, such as destination attribute, customer attribute, and the like, and may further include other attributes, such as credit, transaction rule, and the like. The destination attribute may be "satisfying user financing" or "extending asset usage", and the client attribute may be "enterprise client", "personal client", and the like. In addition, complex association relations may exist between different asset types, for example, a credit card service type may include more sub-asset types, for example, a card transaction type, a credit service type, and the like, a card transaction type may include types of channels, products, partners, and the like, and a channel includes types of counters, self-help, and the like. Therefore, the association relationship between the assets belonging to the asset type and the asset subtype can be represented by the associated asset and the associated asset, for example, the association relationship can be that the asset of the credit card service type is the associated asset and the asset of the card transaction type is the associated asset; alternatively, the transaction type asset may be an associated asset, and the channel type asset may be an associated asset.
As business requirements change, asset types and related attributes change accordingly, and asset associations change, which makes operations of storing, modifying, deleting, and the like of assets face a serious challenge.
For example, it is now common to store in one data model for each type of asset data, where the data model may be a database table. For such a storage method, the following problems are encountered when processing asset data.
Due to the fact that the assets are various in types, one database table is used for storing each type of assets, a large number of database tables are occupied, a large amount of storage space is wasted, and therefore storage efficiency is low. And, as the business changes, the asset types and different types of attributes also need to be added, deleted, modified, etc. This makes it necessary to perform the re-table creation operation each time an asset type is added, and even if only a certain attribute of the asset is to be modified, it is necessary to query each table for modification, which will certainly cause waste of man-hour and increase the cost of maintenance time. Meanwhile, when asset information is acquired, judgment and query need to be performed table by table, which undoubtedly causes low query efficiency. In addition, the incidence relation among different types of assets is complex, and many-to-many, one-to-many and many-to-one incidence relations exist. And as business needs change, asset associations also change. The existing storage mode undoubtedly causes the problems of data redundancy, abnormal insertion, abnormal deletion and the like.
Based on the above, the embodiment of the present disclosure provides a storage system based on an asset configuration model, an asset data model and an asset incidence relation model, which respectively stores the configuration information, the type and the attribute data of the asset and the incidence relation of the asset in the asset configuration model, the asset data model and the asset incidence relation model. The asset configuration model and the asset data model establish a mapping relation through the type identification and the attribute identification, and the asset data model and the asset incidence relation model establish a mapping relation through the asset identification, so that the asset data can be flexibly configured in different service scenes, operations such as addition, deletion, modification, query and the like are performed according to configuration information, and the operation efficiency is improved. It should be noted that the asset configuration model, the asset data model, and the asset association model may be in the form of database tables, or may be in other forms.
Furthermore, the asset configuration information and the asset data are respectively stored in the asset configuration model and the asset data model, so that the asset data is configured and stored separately, the aim of flexibly configuring and storing the asset data under different service scenes is fulfilled, the asset configuration model can be updated on line, and the device can be used without restarting a server. The asset data and the asset incidence relation are respectively stored in the asset data model and the asset incidence relation model, so that the decoupling of the asset data and the incidence relation is realized, the asset relation can be flexibly associated, and the aim of adapting to the change of business requirements is fulfilled. Based on the asset configuration model, the asset data model and the asset incidence relation model, the structured design of the database is realized, the purpose of organizing and storing asset data is achieved, and data support is provided for further asset management of enterprise personnel.
FIG. 2 schematically illustrates a block diagram of a storage system 200 according to an embodiment of the disclosure.
According to the embodiment of the present disclosure, the storage system 200 may be generally disposed in the server 103, or may be disposed in a server or a server cluster different from the server 103 and capable of communicating with the terminal device 101, the terminal device 102, and/or the server 103.
As shown in FIG. 2, storage system 200 may include an asset configuration model 201, an asset data model 202, and an asset association model 203. Taking the example that the storage system 200 is disposed in the server 103, the storage system 200 provided in the embodiment of the present disclosure is described with reference to fig. 1.
The terminal device 101 may receive an operation instruction of asset configuration operated by an administrator, transmit the operation instruction to the server 103 through the network 104, and the server 103 executes the operation instruction to store asset configuration information in the asset configuration model 201. The asset configuration information may include an asset type, an asset attribute, an attribute type, a value range of an attribute value, and the like. For example, the asset type may be configured as a credit card service type, the asset attribute may be configured as a destination attribute, a customer attribute, and the like, the attribute type may be a text box, and the value range of the attribute value may be the longest length of a character string, and the like.
The terminal device 102 may receive an operation instruction for adding, deleting, querying and/or modifying the asset data, which is operated by a user, for example, the operation instruction for adding the asset data includes type information and attribute information of the asset data to be added. The terminal device 102 sends the operation instruction to the server 103 through the network 105, the server 103 executes the operation instruction, calls the asset configuration model 201 module in the storage system 200, and checks whether the asset configuration model 201 stores the configuration information of the asset requested to be operated, for example, checks whether the asset configuration model 201 stores the asset type to which the asset belongs. If the asset configuration model 201 is verified to store the configuration information of the asset requested to be operated, it is verified whether the attribute of the asset requested to be operated is stored. If the property of the asset requesting the operation is stored, it is further checked whether the property type and the property value of the asset conform to the value range of the property type and the property value configured by the asset configuration model 201. If all pass checks, the asset data model 202 in the storage system 200 is invoked, storing the asset types and/or asset attributes of the asset data in the asset data model 202.
The terminal device 102 may receive user-operated operation instructions to add, delete, query, and/or modify asset associations. Taking the operation instruction for adding the asset association relationship as an example, the operation instruction includes the asset identification of the asset associated with the asset requesting the operation. Terminal device 102 sends the operation instruction to server 103 through network 105, server 103 executes the operation instruction, and may first invoke asset configuration model 201 module in storage system 200, to check whether asset configuration information of the asset requesting the operation is stored in asset configuration model 201, and the checking step is the above example, and is not described here again. If the asset configuration model 201 is determined to store the configuration information of the asset requesting the operation, the asset data model 202 in the storage system 200 is called to obtain the asset identification of the asset requesting the operation, then the asset association relation model 203 in the storage system 200 is called to store the asset identification of the asset requesting the operation and the asset identification of the associated asset in a relationship into the asset association relation model 203.
Referring to fig. 3 to fig. 5, the asset data processing method provided by the present disclosure is further described with reference to specific embodiments.
FIG. 3 schematically shows a flow diagram of an asset data processing method according to an embodiment of the disclosure.
As shown in fig. 3, the method includes operations S301 to S304.
In operation S301, a property data addition request is received, wherein the property data addition request includes type information, attribute information, and association information of property data to be added.
According to the embodiment of the disclosure, the terminal device 102 may receive an operation instruction of adding asset data, which is operated by a user, the operation instruction is used for requesting to add an asset a, the type of the asset a may be a credit card service type, and the attribute information may include a destination attribute, a customer attribute, and the like, wherein the destination attribute may be that customer financing is satisfied, and the customer attribute may be an enterprise customer. The association information may include an asset name, an asset identification, etc. of the asset associated with asset a, for example, the association information may be asset a ', and the operation instruction may be further used to request that asset a be associated with asset a'. The terminal apparatus 102 transmits the operation instruction to the server 103.
In operation S302, it is determined whether configuration information matching the asset data to be added is stored in the asset configuration model 201 according to the type information and the attribute information.
According to the embodiment of the present disclosure, the server 103 receives an operation instruction for adding asset data, invokes the asset configuration model 201 in the storage system 200, and determines whether the asset configuration model 201 stores the configuration information of the asset a. The asset configuration model 201 is configured with information such as an asset type identifier, an asset type chinese name, an asset type english name, an asset type ranking number, an asset attribute identifier, an asset attribute chinese name, an asset attribute english name, an asset attribute type (for example, a text box, a drop-down box, a text field), a value range of an attribute value, an asset attribute ranking, and page display coordinates. Therefore, it may be verified whether the asset configuration model 201 is configured with a credit card service type by querying a chinese name or an english name of the asset type in the asset configuration model 201, and if it is verified that the asset configuration model 201 is configured with the credit card service type, it is verified whether a destination attribute is configured by querying a chinese name or an english name of the asset attribute, if the destination attribute is configured, it is verified whether the destination attribute is in accordance with the type of the asset attribute (for example, the type of the configured attribute may be a text box), and if so, it is verified whether a value "meeting customer financing" of the destination attribute exceeds a configured maximum length of a character string (for example, the maximum length of the character string of a value range of the configured attribute is 10 bytes at most).
In operation S303, if configuration information matching the asset data to be added is stored in the asset configuration model 201, the type information and the attribute information of the asset data to be added are stored in the asset data model 202, where the asset data model 202 and the asset configuration model 201 establish a mapping relationship through the type identifier and the attribute identifier of the asset data stored respectively.
According to the embodiment of the disclosure, if the type information and the attribute information of the asset a pass the verification, the type information and the attribute information of the asset a are added to the asset data model 202 according to the configuration information, and the asset identifier of the asset a is generated. The asset type identifier and the asset attribute identifier of the asset a are obtained from the asset configuration model 201, and are stored in the asset data model 202. Therefore, the asset configuration model 201 and the asset data model 202 can establish a mapping relationship through the asset type identifier and the asset attribute identifier, and the configuration information in the asset configuration model 201 can provide a basis for the entry and storage of data in the asset data model 202.
In operation S304, the association information of the asset data to be added is stored into the asset association relationship model 203, where the asset association relationship model 203 and the asset data model 202 establish a mapping relationship through the asset identifiers of the respectively stored asset data.
According to the embodiment of the present disclosure, operation S304 may be to store the asset identification of the asset data to be added and the target asset identification in the asset incidence relation model 203 in association.
According to the embodiment of the disclosure, the operation instruction may further be configured to request that the asset a is associated with the asset a ', the operation instruction may include the asset identifier of the asset a ', obtain the asset identifier of the asset a from the asset data model 202, and then combine the asset identifier of the asset a and the asset identifier of the asset a ' into an association relationship, and store the association relationship into the asset association relationship model 203. Alternatively, the operation instruction may include other information such as the name of the asset a ', the asset identifier of the asset a ' is obtained from the asset data model 202 according to the name information, and then the asset identifier of the asset a and the asset identifier of the asset a ' form an association relationship and are stored in the asset association relationship model 203. Asset data model 202 and asset association model 203 establish a mapping relationship through asset identification. Asset association model 203 may also store the asset type of asset a and the asset type of asset a'.
According to the embodiment of the disclosure, the asset configuration model 201 is used for storing asset configuration information, the asset data model 202 is used for storing asset types and attribute information, and the asset incidence relation model 203 is used for storing asset incidence relations, so that all types of asset data can be processed in the asset configuration model 201, the asset data model 202 and the asset incidence relation model 203, the storage of complex and diverse asset data is supported, and the storage space is saved. In addition, the asset configuration information, the asset type and attribute information and the asset association relationship are stored separately, so that the flexible configuration of asset data in different service scenes can be realized, the time cost of system development is reduced, convenience is provided for operations such as addition, deletion, modification and query of the asset data, and the operation efficiency is improved. And the influence of the asset type, the asset attribute and the incidence relation change on the structure of the storage system can be effectively isolated while the ever-increasing service requirements are met, so that the maintenance cost of the storage system is reduced.
FIG. 4 schematically illustrates a block diagram of an asset data model 202 of an embodiment of the disclosure.
FIG. 5 schematically illustrates a flow diagram for storing type information and attribute information of asset data to be added into asset data model 202, according to an embodiment of the disclosure.
As shown in FIG. 4, asset data model 202 includes an asset common data sub-model 202-1 and an asset attribute sub-model 202-2.
As shown in FIG. 5, storing the type information and attribute information of the asset data to be added into the asset data model 202 in operation S303 may include operations S501-S502.
In operation S501, the type information of the asset data to be added is stored into the asset common data submodel 202-1.
According to an embodiment of the present disclosure, the asset common data submodel 202-1 may be used to store some information common to all types of asset data, for example, each type of asset data may include information such as asset identification, asset name, asset type, creator, creation time, asset status, and the like. Thus, information such as asset identification, asset name (e.g., asset a), asset type (e.g., credit card type), creator, creation time, asset status, etc. of asset a may be added to the asset common data sub-model 202-1.
In operation S502, attribute information of the asset data to be added is stored into the asset attribute sub-model 202-2.
According to an embodiment of the present disclosure, the asset attribute sub-model 202-2 may be used to store attribute information specific to each type of asset data. For example, the destination attributes of the currently added asset a (e.g., meeting customer financing), customer attributes (e.g., enterprise customer), quota, etc. may be added to the asset attribute sub-model 202-2. It should be noted that the asset attribute sub-model 202-2 may also have an asset identification stored therein, so that the asset common data sub-model 202-1 and the asset attribute sub-model 202-2 may be linked through the asset identification.
According to the embodiment of the disclosure, the asset common data sub-model 202-1 stores information common to all asset types, and the asset attribute sub-model 202-2 stores attribute information specific to each asset, which can reduce data redundancy.
The method for configuring asset data provided by the present disclosure is further described with reference to fig. 6-8 in conjunction with specific embodiments.
FIG. 6 schematically shows a flow diagram for storing type configuration information and attribute configuration information into an asset configuration model 201, according to an embodiment of the disclosure.
As shown in fig. 6, the method includes operations S601 to S602.
In operation S601, an asset data configuration request is received, where the asset data configuration request includes type configuration information and attribute configuration information of asset data to be configured.
According to the embodiment of the present disclosure, the terminal device 101 may receive an operation instruction of adding asset configuration information, which is operated by an administrator, and the operation instruction is used to request type configuration information and attribute configuration information of the added asset a. The type configuration information may include an asset type chinese name, an asset type english name, an asset type ranking number, and the like, and the attribute configuration information may include an asset attribute identifier, an asset attribute chinese name, an asset attribute english name, a category of the asset attribute (for example, a text box, a drop-down box, or a text field), a value range of an attribute value, an asset attribute ranking, a page display coordinate, and the like.
For example, the type of the asset a may be a credit card service type, the attribute may include a destination attribute, a client attribute, an amount, and the like, the attribute type of the destination attribute may be a text box, that is, the value of the destination attribute is a text string, the value range of the value of the destination attribute may be a maximum length of the text string of 10 bytes, and the page display coordinate of the destination attribute may be row 1 and column 1. The attribute type of the client attribute may be a drop-down box, that is, the value of the client attribute may be one of attributes such as "enterprise client", "personal client" and the like in the drop-down box, the value range of the value of the client attribute may be an enumerated value in the drop-down box, and the page display coordinate of the client attribute may be row 2, column 1 and the like.
In operation S602, in response to the asset data configuration request, the type configuration information and the attribute configuration information of the asset data to be configured are stored in the asset configuration model 201.
According to the embodiment of the present disclosure, the configuration information is stored in the asset configuration model 201, and then the type identifier and the attribute identifier of the asset a can be generated according to the configuration information, wherein a plurality of attribute identifiers can be generated according to the attribute configuration information.
According to the embodiment of the present disclosure, the type information and the attribute information of the asset data are configured in the asset configuration model 201, and flexible configuration can be performed according to different service scenes, so as to achieve the purpose of adapting to the service requirement change.
Fig. 7 schematically illustrates a block diagram of an asset configuration model 201 of an embodiment of the present disclosure.
As shown in FIG. 7, the asset configuration model 201 includes an asset type configuration sub-model 201-1 and an asset attribute configuration sub-model 201-2.
FIG. 8 schematically illustrates a flow diagram for storing type configuration information and attribute configuration information into an asset configuration model 201, according to an embodiment of the disclosure.
As shown in fig. 8, storing the type configuration information and the attribute configuration information of the asset data to be configured in the asset configuration model 201 in operation S602 may include operations S801 to S802.
In operation S801, type configuration information of asset data to be configured is stored in the asset type configuration submodel 201-1.
According to the embodiment of the disclosure, the type configuration information of the asset a may be added to the asset type configuration submodel 201-1, wherein the type configuration information may include information such as an asset type chinese name, an asset type english name, and an asset type ranking number.
In operation S802, attribute configuration information of the asset data to be configured is stored in the asset attribute configuration submodel 201-2.
According to the embodiment of the disclosure, the attribute configuration information of the asset a may be added to the asset attribute configuration submodel 201-2, wherein the attribute configuration information may include information such as asset attribute identification, asset attribute chinese name, asset attribute english name, asset attribute sorting, page display coordinates, and the like.
According to the embodiment of the present disclosure, the attribute configuration information may further include attribute types and value ranges of attribute values. Operation S802 may specifically include storing the attribute type and the value range of the attribute value in the asset attribute configuration submodel 201-2. The attribute type may be a text box, a drop-down box, a text field, etc., and the value range of the attribute value may be a maximum length of a character string allowed to be input by the text box, an enumeration value in the drop-down box, a length of the text field, etc.
According to the embodiment of the disclosure, the asset type configuration submodel 201-1 stores type configuration information, and the asset attribute configuration submodel 201-2 stores attribute configuration information, so that the influence of the change of types or attributes on the model structure can be reduced, and the maintenance cost of the model is reduced.
Fig. 9 schematically shows a flowchart for determining whether the asset configuration model 201 stores configuration information matching the asset data to be added according to an embodiment of the present disclosure.
As shown in fig. 9, operations S901 to S903 are included.
In operation S901, it is determined whether an asset type to which the asset data to be operated belongs is stored in the asset type configuration sub model 201-1 according to the type information.
According to the embodiment of the present disclosure, after receiving the operation instruction for adding the asset a, it may be verified whether the asset configuration model 201 is configured with the type to which the asset a belongs by querying the asset type chinese name or english name in the asset configuration model 201.
In operation S902, if it is determined that the asset type to which the asset data to be operated belongs is stored in the asset type configuration sub-model 201-1, it is determined whether the attribute included in the asset data to be added is stored in the asset attribute configuration sub-model 201-2 according to the attribute information.
According to the embodiment of the present disclosure, if the asset configuration model 201 is configured with the type to which the asset a belongs, it is checked whether the attribute included in the asset a is configured by querying the chinese name or the english name of the asset attribute.
In operation S903, if it is determined that the asset attribute configuration sub-model 201-2 stores the attribute included in the asset data to be operated, it is determined whether the attribute type and the attribute value of the asset data to be operated conform to the value range of the attribute type and the asset attribute stored in the asset attribute configuration sub-model 201-2.
According to the embodiment of the present disclosure, if the asset configuration model 201 is configured with the attributes included in the asset a, it is verified whether the value of each attribute conforms to the asset attribute type, for example, whether the type of the destination attribute is a text box, and if so, it is verified whether the value of the destination attribute exceeds the configured maximum length of the character string. If all the above verifications are passed, it can be determined that the asset configuration model 201 stores the configuration information matching the asset a.
According to the embodiment of the disclosure, before the asset data is added, whether the corresponding configuration information exists in the configuration model is verified, the data can be stored after the verification is passed, and data redundancy can be reduced.
FIG. 10 schematically illustrates an internal mapping schematic of an asset configuration model 201 and an asset data model 202 of an embodiment of the disclosure.
As shown in FIG. 10, the asset configuration model 201 includes an asset type configuration sub-model 201-1 and an asset attribute configuration sub-model 201-2, a primary key of the asset type configuration sub-model 201-1 is a type identifier, and a primary key of the asset attribute configuration sub-model 201-2 is a type identifier and an attribute identifier.
The asset data model 202 includes an asset common data sub-model 202-1 and an asset attribute sub-model 202-2, the primary key of the asset common data sub-model 202-1 may be an asset identification and a type identification, and the primary key of the asset attribute sub-model 202-2 may be an asset identification and an attribute identification.
According to the embodiment of the disclosure, the asset type configuration submodel 201-1 establishes a mapping relationship with the asset attribute configuration submodel 201-2 through a type identifier; the asset type configuration submodel 201-1 establishes a mapping relation with the asset public data submodel 202-1 through a type identifier; the asset public data sub-model 202-1 establishes a mapping relation with the asset attribute sub-model 202-2 through asset identification; the asset attribute configuration sub-model 201-2 establishes a mapping relationship with the asset attribute sub-model 202-2 through attribute identification.
Based on the mapping relationship shown in fig. 10, the embodiment of the present disclosure provides an asset data operation method. Referring to fig. 11 to fig. 12, the asset data operation method provided by the embodiment of the present disclosure is further described with reference to specific embodiments.
FIG. 11 schematically illustrates a flow chart of an asset data manipulation method of an embodiment of the disclosure.
As shown in fig. 11, operations S1101 to S1105 are included.
In operation S1101, a first operation request is received, wherein the first operation request includes an asset identification of asset data to be operated.
According to the embodiment of the disclosure, the first operation request may be for requesting to acquire, delete or modify an attribute of the asset a, and the first operation request may include an asset identification of the asset a.
In operation S1102, a type identifier of the asset data to be operated is obtained from the asset common data sub-model 202-1 according to the asset identifier.
According to the mapping relationship shown in FIG. 10, the type identifier of asset a may be obtained from asset common data sub-model 202-1 according to the asset identifier of asset a.
In operation S1103, an attribute identifier of the asset data to be operated is obtained from the asset attribute configuration sub-model 201-2 according to the type identifier.
According to the mapping relationship shown in fig. 10, the attribute identifier of the asset a in the asset attribute configuration sub-model 201-2 can be obtained according to the type identifier of the asset a.
In operation S1104, attribute information of the asset data to be operated is acquired from the asset attribute sub-model 202-2 according to the asset identification and the attribute identification.
According to the mapping relationship shown in fig. 10, the attribute information of the asset a in the asset attribute sub-model 202-2 can be obtained according to the asset identification and the attribute identification of the asset a.
In operation S1105, a deletion or modification operation is performed on the attribute information of the asset data to be operated.
According to the embodiment of the disclosure, the attribute information of the asset a can be deleted or modified.
According to the embodiment of the disclosure, according to the mapping relationship between the asset configuration model 201 and the asset data model 202, dynamic addition, deletion, modification and query of asset configuration information, type information and attribute information can be supported, and the operation is convenient and fast.
FIG. 12 schematically illustrates a flow chart of an asset data manipulation method of an embodiment of the present disclosure.
As shown in fig. 12, operations S1201 to S1203 are included.
In operation S1201, a second operation request is received, wherein the second operation request includes an asset identification of asset data to be operated and an asset identification of asset data associated with the asset data to be operated.
According to the embodiment of the present disclosure, the second operation request may be a request to acquire, delete or modify the association relationship between the asset a and the asset a ', and the asset identification of the asset a' may be acquired from the asset common data sub-model 202-1.
In operation S1202, association information of the asset data to be operated is acquired from the asset association relation model 203 according to the asset identification of the asset data to be operated and the asset identification of the asset data associated with the asset data to be operated.
According to the embodiment of the disclosure, the association relationship between the asset a and the asset a 'can be obtained from the asset association relationship model 203 according to the asset identification of the asset a and the asset identification of the asset a'.
In operation S1203, a deletion or modification operation is performed on the association information of the asset data to be operated.
According to the embodiment of the disclosure, the association relationship between the asset a and the asset a' can be deleted or modified.
According to the embodiment of the disclosure, according to the mapping relationship between the asset data model 202 and the asset incidence relationship model 203, convenience can be provided for the operations of adding, deleting, modifying and querying the asset incidence relationship.
Fig. 13 schematically illustrates a block diagram of an asset data processing device 1300 according to an embodiment of the present disclosure.
As shown in fig. 13, the asset data processing apparatus 1300 includes a first receiving module 1301, a first determining module 1302, a first storing module 1303, and a second storing module 1304.
The first receiving module 1301 is configured to receive an asset data addition request, where the asset data addition request includes type information, attribute information, and association information of asset data to be added.
The first determining module 1302 is configured to determine whether configuration information matched with the asset data to be added is stored in the asset configuration model according to the type information and the attribute information.
The first storage module 1303 is configured to, if configuration information matched with the asset data to be added is stored in the asset configuration model, store the type information and the attribute information of the asset data to be added into the asset data model, where the asset data model and the asset configuration model establish a mapping relationship through the type identifier and the attribute identifier of the asset data stored in the asset data model and the asset configuration model respectively.
The second storage module 1304 is configured to store the association information of the asset data to be added into an asset association relationship model, where the asset association relationship model and the asset data model establish a mapping relationship through asset identifiers of the asset data stored in the asset association relationship model and the asset data model.
According to an embodiment of the present disclosure, an asset data model includes an asset common data sub-model and an asset attribute sub-model.
The first storage module 1303 includes a first storage unit and a second storage unit.
The first storage unit is used for storing the type information of the asset data to be added into the asset common data sub-model.
And the second storage unit is used for storing the attribute information of the asset data to be added into the asset attribute sub-model.
According to an embodiment of the present disclosure, the asset data processing device 1300 further includes a second receiving module and a third storing module.
The second receiving module is used for receiving an asset data configuration request, wherein the asset data configuration request comprises type configuration information and attribute configuration information of asset data to be configured.
And the third storage module is used for responding to the asset data configuration request and storing the type configuration information and the attribute configuration information of the asset data to be configured into the asset configuration model.
According to an embodiment of the present disclosure, an asset configuration model includes an asset type configuration sub-model and an asset attribute configuration sub-model.
The third storage module includes a third storage unit and a fourth storage unit.
And the third storage unit is used for storing the type configuration information of the asset data to be configured into the asset type configuration sub-model.
The fourth storage unit is used for storing the attribute configuration information of the asset data to be configured into the asset attribute configuration sub-model.
According to the embodiment of the present disclosure, the attribute configuration information includes attribute types and value ranges of attribute values.
The fourth storage unit is specifically configured to store the attribute type and the value range of the attribute value in the asset attribute configuration sub-model.
According to the embodiment of the present disclosure, the attribute information of the asset data to be added includes an attribute type and an attribute value.
The first determining module 1302 includes a first determining unit, a second determining unit, and a third determining unit.
The first determining unit is used for determining whether the asset type to which the asset data to be operated belong is stored in the asset type configuration sub-model according to the type information.
And the second determination unit is used for determining whether the property included in the asset attribute configuration sub-model is stored or not according to the attribute information if the asset type to which the asset data to be operated belongs is determined to be stored in the asset type configuration sub-model.
And the third determining unit is used for determining whether the attribute type and the attribute value of the asset data to be operated conform to the value range of the attribute type and the asset attribute stored in the asset attribute configuration sub-model if the attribute included in the asset data to be operated is determined to be stored in the asset attribute configuration sub-model.
According to the embodiment of the disclosure, the association information of the asset data to be added comprises a target asset identifier, and the target asset identifier is an asset identifier of the asset data associated with the asset data to be added.
The second storage module 1304 is used for storing the asset identification of the asset data to be added and the target asset identification in the asset incidence relation model in an associated manner.
According to the embodiment of the disclosure, the asset configuration model comprises an asset type configuration sub-model and an asset attribute configuration sub-model, the asset type configuration sub-model comprises a type identifier, the asset attribute configuration sub-model comprises a type identifier and an attribute identifier, the asset data model comprises an asset public data sub-model and an asset attribute sub-model, the asset public data sub-model comprises an asset identifier and a type identifier, and the asset attribute sub-model comprises an asset identifier and an attribute identifier.
According to an embodiment of the present disclosure, the asset data processing apparatus 1300 further includes a third receiving module, a first obtaining module, a second obtaining module, a third obtaining module, and a first operating module.
The third receiving module is used for receiving the first operation request, wherein the first operation request comprises the asset identification of the asset data to be operated.
The first acquisition module is used for acquiring the type identifier of the asset data to be operated from the asset public data sub-model according to the asset identifier.
And the second acquisition module is used for acquiring the attribute identifier of the asset data to be operated from the asset attribute configuration sub-model according to the type identifier.
And the third acquisition module is used for acquiring the attribute information of the asset data to be operated from the asset attribute sub-model according to the asset identification and the attribute identification.
The first operation module is used for deleting or modifying the attribute information of the asset data to be operated.
According to an embodiment of the present disclosure, the asset data processing apparatus 1300 further includes a fourth receiving module, a fourth obtaining module, and a second operating module.
The fourth receiving module is used for receiving a second operation request, wherein the second operation request comprises the asset identification of the asset data to be operated and the asset identification of the asset data associated with the asset data to be operated.
And the fourth acquisition module is used for acquiring the association information of the asset data to be operated from the asset association relation model according to the asset identification of the asset data to be operated and the asset identification of the asset data associated with the asset data to be operated.
The second operation module is used for deleting or modifying the associated information of the asset data to be operated.
Any number of modules, sub-modules, units, sub-units, or at least part of the functionality of any number thereof according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, and sub-units according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least partially as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or by any other reasonable means of hardware or firmware for integrating or packaging a circuit, or by any one of or a suitable combination of any of software, hardware, and firmware. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the disclosure may be at least partially implemented as a computer program module, which when executed may perform the corresponding functions.
For example, any plurality of the first receiving module 1301, the first determining module 1302, the first storing module 1303 and the second storing module 1304 may be combined and implemented in one module/unit/sub-unit, or any one of the modules/units/sub-units may be split into a plurality of modules/units/sub-units. Alternatively, at least part of the functionality of one or more of these modules/units/sub-units may be combined with at least part of the functionality of other modules/units/sub-units and implemented in one module/unit/sub-unit. According to an embodiment of the present disclosure, at least one of the first receiving module 1301, the first determining module 1302, the first storing module 1303 and the second storing module 1304 may be at least partially implemented as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented by hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or implemented by any one of three implementation manners of software, hardware and firmware, or an appropriate combination of any several of them. Alternatively, at least one of the first receiving module 1301, the first determining module 1302, the first storing module 1303 and the second storing module 1304 may be at least partially implemented as a computer program module, which when executed may perform a corresponding function.
It should be noted that, the asset data processing device part in the embodiment of the present disclosure corresponds to the asset data processing method part in the embodiment of the present disclosure, and the description of the asset data processing device part specifically refers to the data processing method part, which is not described herein again.
FIG. 14 schematically illustrates a block diagram of a computer system suitable for implementing the above-described method, according to an embodiment of the present disclosure. The computer system illustrated in FIG. 14 is only one example and should not impose any limitations on the scope of use or functionality of embodiments of the disclosure.
As shown in fig. 14, a computer system 1400 according to an embodiment of the present disclosure includes a processor 1401, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)1402 or a program loaded from a storage portion 1408 into a Random Access Memory (RAM) 1403. Processor 1401 may comprise, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 1401 may also include onboard memory for caching purposes. Processor 1401 may include a single processing unit or multiple processing units for performing different actions of a method flow according to embodiments of the present disclosure.
In the RAM 1403, various programs and data necessary for the operation of the system 1400 are stored. The processor 1401, the ROM 1402, and the RAM 1403 are connected to each other by a bus 1404. The processor 1401 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 1402 and/or the RAM 1403. Note that the program may also be stored in one or more memories other than the ROM 1402 and the RAM 1403. The processor 1401 may also perform various operations of the method flows according to the embodiments of the present disclosure by executing programs stored in the one or more memories.
According to an embodiment of the present disclosure, system 1400 may also include an input/output (I/O) interface 1405, which input/output (I/O) interface 1405 is also connected to bus 1404. System 1400 may also include one or more of the following components connected to I/O interface 1405: an input portion 1406 including a keyboard, a mouse, and the like; an output portion 1407 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker and the like; a storage portion 1408 including a hard disk and the like; and a communication section 1409 including a network interface card such as a LAN card, a modem, or the like. The communication section 1409 performs communication processing via a network such as the internet. The driver 1410 is also connected to the I/O interface 1405 as necessary. A removable medium 1411 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 1410 as necessary, so that a computer program read out therefrom is installed into the storage section 1408 as necessary.
According to embodiments of the present disclosure, method flows according to embodiments of the present disclosure may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication portion 1409 and/or installed from the removable medium 1411. The computer program, when executed by the processor 1401, performs the above-described functions defined in the system of the embodiment of the present disclosure. The above described systems, devices, apparatuses, modules, units, etc. may be implemented by computer program modules according to embodiments of the present disclosure.
The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist alone without being assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.
According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium. Examples may include, but are not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
For example, according to embodiments of the present disclosure, a computer-readable storage medium may include one or more memories other than ROM 1402 and/or RAM 1403 and/or ROM 1402 and RAM 1403 described above.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.
The embodiments of the present disclosure are described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used advantageously in combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.

Claims (11)

1. An asset data processing method comprising:
receiving an asset data adding request, wherein the asset data adding request comprises type information, attribute information and associated information of asset data to be added;
determining whether configuration information matched with the asset data to be added is stored in an asset configuration model according to the type information and the attribute information;
if the asset configuration model stores configuration information matched with the asset data to be added, storing the type information and the attribute information of the asset data to be added into an asset data model, wherein the asset data model and the asset configuration model establish a mapping relation through the type identification and the attribute identification of the asset data stored respectively;
storing the association information of the asset data to be added into an asset association relation model, wherein the asset association relation model and the asset data model establish a mapping relation through asset identifications of the stored asset data respectively;
wherein before receiving the asset data addition request, the method further comprises: receiving an asset data configuration request, wherein the asset data configuration request comprises type configuration information and attribute configuration information of asset data to be configured; and responding to the asset data configuration request, and storing the type configuration information and the attribute configuration information of the asset data to be configured into the asset configuration model.
2. The method of claim 1, wherein the asset data model comprises an asset common data sub-model and an asset attribute sub-model;
the storing the type information and the attribute information of the asset data to be added into the asset data model comprises:
storing the type information of the asset data to be added into the asset public data sub-model; and
and storing the attribute information of the asset data to be added into the asset attribute sub-model.
3. The method of claim 1, wherein the asset configuration model comprises an asset type configuration sub-model and an asset attribute configuration sub-model;
the storing the type configuration information and the attribute configuration information of the asset data to be configured into the asset configuration model comprises:
storing the type configuration information of the asset data to be configured into the asset type configuration sub-model;
and storing the attribute configuration information of the asset data to be configured into the asset attribute configuration sub-model.
4. The method of claim 3, wherein the attribute configuration information includes attribute types and value ranges of attribute values;
the storing the attribute configuration information of the asset data to be configured into the asset attribute configuration sub-model comprises:
and storing the attribute type and the value range of the attribute value in the asset attribute configuration sub-model.
5. The method of claim 3, wherein the attribute information of the asset data to be added comprises an attribute type and an attribute value;
the determining whether the asset configuration model stores the configuration information matched with the asset data to be added according to the type information and the attribute information comprises the following steps:
determining whether the asset type configuration submodel stores the asset type to which the asset data to be operated belongs according to the type information;
if the asset type of the to-be-operated asset data is determined to be stored in the asset type configuration sub-model, determining whether the attribute included in the to-be-added asset data is stored in the asset attribute configuration sub-model according to the attribute information;
and if the property included in the asset data to be operated is determined to be stored in the asset property configuration sub-model, determining whether the property type and the property value of the asset data to be operated conform to the value range of the property type and the asset property stored in the asset property configuration sub-model.
6. The method of claim 1, wherein the association information of the asset data to be added comprises a target asset identification, the target asset identification being an asset identification of asset data associated with the asset data to be added;
the storing the association information of the asset data to be added into the asset association relation model comprises:
and storing the asset identification of the asset data to be added and the target asset identification in the asset incidence relation model in an associated manner.
7. The method of claim 1 wherein the asset configuration model comprises an asset type configuration sub-model comprising a type identification and an asset attribute configuration sub-model comprising a type identification and an attribute identification, the asset data model comprises an asset common data sub-model comprising an asset identification and a type identification and an asset attribute sub-model comprising an asset identification and an attribute identification;
the method further comprises the following steps:
receiving a first operation request, wherein the first operation request comprises an asset identifier of asset data to be operated;
acquiring the type identifier of the asset data to be operated from the asset public data sub-model according to the asset identifier;
acquiring an attribute identifier of asset data to be operated from the asset attribute configuration sub-model according to the type identifier;
acquiring attribute information of the asset data to be operated from the asset attribute sub-model according to the asset identification and the attribute identification;
and deleting or modifying the attribute information of the asset data to be operated.
8. The method of claim 7, further comprising:
receiving a second operation request, wherein the second operation request comprises an asset identifier of asset data to be operated and an asset identifier of asset data associated with the asset data to be operated;
acquiring the association information of the asset data to be operated from the asset association relation model according to the asset identification of the asset data to be operated and the asset identification of the asset data associated with the asset data to be operated;
and deleting or modifying the associated information of the asset data to be operated.
9. An asset data processing device comprising:
the system comprises a first receiving module, a second receiving module and a sending module, wherein the first receiving module is used for receiving an asset data adding request, and the asset data adding request comprises type information, attribute information and associated information of asset data to be added;
the first determining module is used for determining whether configuration information matched with the asset data to be added is stored in the asset configuration model according to the type information and the attribute information;
the first adding module is used for storing the type information and the attribute information of the asset data to be added into an asset data model if the asset configuration model stores configuration information matched with the asset data to be added, wherein the asset data model and the asset configuration model establish a mapping relation through the type identification and the attribute identification of the asset data stored in the asset data model and the asset configuration model respectively;
the second adding module is used for storing the association information of the asset data to be added into an asset association relation model, wherein the asset association relation model and the asset data model establish a mapping relation through asset identifications of the stored asset data;
the second receiving module is used for receiving an asset data configuration request, wherein the asset data configuration request comprises type configuration information and attribute configuration information of asset data to be configured;
and the third storage module is used for responding to the asset data configuration request and storing the type configuration information and the attribute configuration information of the asset data to be configured into the asset configuration model.
10. A computer system, comprising:
one or more processors;
a memory for storing one or more programs,
wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1-8.
11. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to carry out the method of any one of claims 1 to 8.
CN202010094896.XA 2020-02-14 2020-02-14 Asset data processing method and apparatus, computer system, and storage medium Active CN111325456B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010094896.XA CN111325456B (en) 2020-02-14 2020-02-14 Asset data processing method and apparatus, computer system, and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010094896.XA CN111325456B (en) 2020-02-14 2020-02-14 Asset data processing method and apparatus, computer system, and storage medium

Publications (2)

Publication Number Publication Date
CN111325456A CN111325456A (en) 2020-06-23
CN111325456B true CN111325456B (en) 2022-08-30

Family

ID=71167117

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010094896.XA Active CN111325456B (en) 2020-02-14 2020-02-14 Asset data processing method and apparatus, computer system, and storage medium

Country Status (1)

Country Link
CN (1) CN111325456B (en)

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106202438A (en) * 2016-07-13 2016-12-07 乐视控股（北京）有限公司 The method and system of storage associated data
JP6939285B2 (en) * 2017-09-05 2021-09-22 ブラザー工業株式会社 Data processing programs and data processing equipment
CN109558404B (en) * 2018-10-19 2023-12-01 中国平安人寿保险股份有限公司 Data storage method, device, computer equipment and storage medium
CN109685899A (en) * 2018-12-25 2019-04-26 成都四方伟业软件股份有限公司 Three-dimensional visualization marks management system, method and computer storage medium
CN110399419B (en) * 2019-07-30 2023-03-24 上海金融期货信息技术有限公司 Relational template memory database system

Also Published As

Publication number Publication date
CN111325456A (en) 2020-06-23

Similar Documents

Publication Publication Date Title
CN110008045B (en) Method, device and equipment for aggregating microservices and storage medium
WO2019179026A1 (en) Electronic device, method for automatically generating cluster access domain name, and storage medium
WO2023109138A1 (en) Method and apparatus for starting android application in linux system, and electronic device
US10331669B2 (en) Fast query processing in columnar databases with GPUs
CN107133309B (en) Method and device for storing and querying process example, storage medium and electronic equipment
CN111949693B (en) Data processing device, data processing method, storage medium and electronic equipment
US20210149895A1 (en) Query conversion for querying disparate data sources
CN111427971B (en) Business modeling method, device, system and medium for computer system
WO2023082716A1 (en) Method and apparatus for operating android application in linux system, and device
CN113239377A (en) Authority control method, device, equipment and storage medium
WO2023193687A1 (en) Shared memory access method and apparatus, device, and storage medium
CN114077367A (en) Method and device for realizing shortcut of android application in Linux system
US9473561B2 (en) Data transmission for transaction processing in a networked environment
CN113568764A (en) User information acquisition method, device, equipment and medium for micro service
CN111325456B (en) Asset data processing method and apparatus, computer system, and storage medium
US11687442B2 (en) Dynamic resource provisioning for use cases
US20190258736A1 (en) Dynamic Execution of ETL Jobs Without Metadata Repository
KR20200046316A (en) Web application server, method for handling user request and method for handling intergrated request
US10628416B2 (en) Enhanced database query processing
US11178216B2 (en) Generating client applications from service model descriptions
CN110769027A (en) Service request processing method and device, computer equipment and storage medium
US20180341717A1 (en) Providing instant preview of cloud based file
US10303531B2 (en) Console application through web service
US20220405406A1 (en) Methods and Systems for Dynamic Sampling of Application Events
US10417133B2 (en) Reference cache maintenance optimizer

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant