Entity attribute data query and configuration method, device, and server

Abstract

The embodiments of this specification disclose a method, device, and server for querying and configuring entity attribute data. By treating only some entity units as leaf entity units, attribute data is stored and maintained. Other entity units inherit the attribute data corresponding to the leaf entity units to construct association relationships between entity units when storing entity attribute data, thereby completing the storage of attribute data for all entity units based on the association relationships and the attribute data of the leaf entity units. When querying and maintaining attribute data, only the attribute data of the leaf entity units need to be maintained. For non-leaf entity units, the attribute data of the corresponding leaf entity units can be retrieved through entity unit conversion to query the attribute data. This greatly reduces the storage scale of entity attribute data while further reducing the maintenance amount of entity attribute data and improving query efficiency.

Description

Technical Field

[0001] The present specification relates to the field of computer data processing technology, and in particular, to a method, device, and server for querying and configuring entity attribute data. Background Art

[0002] Financial institutions are usually composed of entities such as institutions, personnel, and outlets. These entities contain specific entity units such as branches, personnel, and outlets. Each entity corresponds to a large number of entity attributes. For example, institutions correspond to attributes such as business calendars, assets, and transaction authorizations, and personnel correspond to attributes such as qualifications and tags. Since each entity unit has certain differences, and there are many types of entity units and entity attributes, daily query, storage, and maintenance of the attribute values ​​corresponding to these entity units often take a lot of time and cost.

[0003] For example, a commercial bank has 500,000 branches, and each branch has a business calendar attribute. Business calendar refers to whether a branch is open on a certain day of a year in a commercial bank, and is generally accurate to the day according to the needs of the institution. A business calendar of a year contains 365 days, so all branches of the commercial bank need to maintain more than 182.5 million attribute item fields just to add a business calendar of one year. For another example, each branch of this commercial bank has a transaction authorization attribute. Transaction authorization attribute refers to whether a transaction of a branch needs authorization in a commercial bank, and is generally accurate to the transaction and position according to the needs of the institution. Assuming that the transaction authorization attribute contains 50 different authorized transactions, and each authorized transaction contains 10 authorized positions, if the transaction authorization attribute of each institution is maintained, more than 250 million attribute item fields need to be maintained. It can be seen that the query and maintenance workload of entity attribute data in actual business systems is huge, and it also requires a very large storage space. Therefore, a more efficient and simple entity attribute data configuration method is urgently needed. Summary of the invention

[0004] The purpose of the embodiments of this specification is to provide a method, device, and server for querying and configuring entity attribute data, which can significantly reduce the storage scale of entity attribute data and the maintenance amount of entity attribute data, and improve the query efficiency of entity attribute data.

[0005] This specification provides an entity attribute data query and configuration method, device, and server that are implemented in the following ways:

[0006] A method for querying entity attribute data, applied to a server, the method comprising: receiving an entity attribute data query request; the entity attribute query request comprising an entity unit to be queried and an attribute type to be queried corresponding to the entity unit to be queried; determining a leaf entity unit corresponding to the entity unit to be queried using a pre-configured entity unit association relationship; wherein the entity unit association relationship comprises an association relationship between entity units; the association relationship comprises an inheritance relationship and a co-location relationship; the inheritance relationship refers to the inheritance of the attribute data of the associated entity unit by the associated entity unit; the co-location relationship indicates that the associated entity unit and the associated entity unit are the same entity unit; the leaf entity unit refers to the entity unit corresponding to the co-location relationship; obtaining the attribute data of the leaf entity unit corresponding to the entity unit to be queried under the attribute type to be queried as the attribute data of the entity unit to be queried under the attribute type to be queried.

[0007] In some other embodiments of the method provided in this specification, the method of determining the leaf entity unit corresponding to the entity unit to be queried using the pre-configured entity unit association relationship includes: retrieving the entity unit association relationship corresponding to the attribute type to be queried; and determining the leaf entity unit corresponding to the entity unit to be queried using the entity unit association relationship corresponding to the attribute type to be queried.

[0008] In some other embodiments of the method provided in this specification, obtaining the attribute data of the leaf entity unit corresponding to the entity unit to be queried under the attribute type to be queried includes: obtaining an entity attribute data set; the entity attribute data set includes leaf entity units and attribute data of the leaf entity units under each entity attribute type; querying the attribute data of the leaf entity unit corresponding to the entity unit to be queried under the attribute type to be queried from the entity attribute data set.

[0009] On the other hand, an embodiment of the present specification also provides an entity attribute data query device, which is applied to a server, and the device includes: a query request receiving module, which is used to receive an entity attribute data query request; the entity attribute query request includes an entity unit to be queried and an attribute type to be queried corresponding to the entity unit to be queried; an entity unit conversion module, which is used to determine the leaf entity unit corresponding to the entity unit to be queried using a pre-configured entity unit association relationship; wherein the entity unit association relationship includes an association relationship between entity units; the association relationship includes an inheritance relationship and a co-location relationship; the inheritance relationship refers to the attribute data of the associated entity unit inherited by the associated entity unit; the co-location relationship indicates that the associated entity unit and the associated entity unit are the same entity unit; the leaf entity unit refers to the entity unit corresponding to the co-location relationship; an attribute data query module, which is used to obtain the attribute data of the leaf entity unit corresponding to the entity unit to be queried under the attribute type to be queried, as the attribute data of the entity unit to be queried under the attribute type to be queried.

[0010] On the other hand, an embodiment of the present specification also provides an entity attribute data configuration method, which is applied to a server, and the method includes: receiving an entity attribute data configuration request sent by a user terminal; the entity attribute configuration request includes an entity unit to be configured and a to-be-configured attribute type and to-be-configured attribute data corresponding to the entity unit to be configured; when it is determined that the entity unit to be configured belongs to a leaf entity unit by using a pre-configured entity unit association relationship, the to-be-configured attribute data is configured into an entity attribute data set based on the entity unit to be configured and the to-be-configured attribute type; wherein the entity unit association relationship includes an association relationship between entity units; the association relationship includes an inheritance relationship and a co-location relationship; the inheritance relationship refers to that the associated party entity unit inherits the attribute data of the associated party entity unit; the co-location relationship indicates that the associated party entity unit and the associated party entity unit are the same entity unit; the leaf entity unit refers to the entity unit corresponding to the co-location relationship.

[0011] In some other embodiments of the method provided in the present specification, when it is determined that the entity unit to be configured does not belong to a leaf entity unit, the association relationship between the entity unit to be configured and its corresponding associated entity unit in the pre-configured entity association relationship is deleted; and the entity unit to be configured is configured as a leaf entity unit; and the attribute data to be configured is added to the entity attribute data set based on the entity unit to be configured and the attribute type to be configured.

[0012] In some other embodiments of the method provided in this specification, before determining that the entity unit to be configured belongs to a leaf entity unit, the method also includes: verifying the attribute data to be configured using the attribute data verification rule corresponding to the attribute type to be configured; and if the verification passes, determining whether the entity unit to be configured belongs to a leaf entity unit.

[0013] In some other embodiments of the method provided in this specification, configuring the attribute data to be configured into an entity attribute data set based on the entity unit to be configured and the attribute type to be configured includes: when the attribute data of the entity unit to be configured under the attribute type to be configured does not exist in the entity attribute data set, adding the entity unit to be configured, the attribute type to be configured and the attribute data item to the entity attribute data set; filling the attribute data to be configured into the attribute data item based on the entity unit to be configured and the attribute type to be configured.

[0014] In some other embodiments of the method provided in this specification, configuring the attribute data to be configured into an entity attribute data set based on the entity unit to be configured and the attribute type to be configured includes: when attribute data of the entity unit to be configured under the attribute type to be configured exists in the entity attribute data set, updating the attribute data of the entity unit to be configured under the attribute type to be configured to the attribute data to be configured.

[0015] On the other hand, an embodiment of the present specification also provides an entity attribute data configuration device, which is applied to a server, and the device includes: a configuration request receiving module, which is used to receive an entity attribute data configuration request sent by a user terminal; the entity attribute configuration request includes an entity unit to be configured and a type of attribute to be configured and attribute data to be configured corresponding to the entity unit to be configured; an attribute data configuration module, which is used to configure the attribute data to be configured into an entity attribute data set based on the entity unit to be configured and the type of attribute to be configured, when it is determined that the entity unit to be configured belongs to a leaf entity unit using a pre-configured entity unit association relationship; wherein the entity unit association relationship includes an association relationship between entity units; the association relationship includes an inheritance relationship and a co-location relationship; the inheritance relationship refers to that the associated party entity unit inherits the attribute data of the associated party entity unit; the co-location relationship indicates that the associated party entity unit and the associated party entity unit are the same entity unit; the leaf entity unit refers to the entity unit corresponding to the co-location relationship.

[0016] In some other embodiments of the device provided in this specification, the device also includes an association relationship configuration module; wherein the association relationship configuration module is used to delete the association relationship between the entity unit to be configured and its corresponding associated party entity unit in the pre-configured entity association relationship when it is determined that the entity unit to be configured does not belong to a leaf entity unit; and configure the entity unit to be configured as a leaf entity unit; the attribute data configuration module is also used to add the attribute data to be configured to the entity attribute data set based on the entity unit to be configured and the attribute type to be configured.

[0017] In some other embodiments of the device provided in this specification, the device also includes: a verification module, used to verify the attribute data to be configured using the attribute data verification rules corresponding to the attribute type to be configured; and a judgment module, used to judge whether the entity unit to be configured belongs to a leaf entity unit if the verification passes.

[0018] On the other hand, an embodiment of the present specification further provides a server, the server comprising at least one processor and a memory for storing processor executable instructions, wherein the instructions, when executed by the processor, implement the steps of the method described in any one or more of the above embodiments.

[0019] The entity attribute data query and configuration method, device, and server provided in one or more embodiments of the present specification store and maintain attribute data by treating only certain entity units as leaf entity units, and constructing association relationships between entity units when storing entity attribute data by inheriting the attribute data corresponding to the leaf entity units, thereby completing the storage of attribute data of all entity units based on the association relationship and the attribute data of the leaf entity units. When querying and maintaining attribute data, only the attribute data of the leaf entity units need to be maintained. For non-leaf entity units, the attribute data of the corresponding leaf entity units can be retrieved through entity unit conversion to query the attribute data. This greatly reduces the storage scale of entity attribute data while further reducing the maintenance amount of entity attribute data and improving query efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the technical solutions in the embodiments of this specification or the prior art, the following briefly introduces the drawings required for use in the embodiments or the prior art description. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative labor. In the drawings:

[0021] Figure 1A schematic diagram of the association relationship between entity units in some embodiments provided in this specification;

[0022] Figure 2 A schematic diagram of the association relationship between entity units in some other embodiments provided in this specification;

[0023] Figure 3 A schematic diagram of a method for storing attribute data of a physical unit in some embodiments provided in this specification;

[0024] Figure 4 A schematic diagram of a common storage method of attribute data of a physical unit in some embodiments provided in this specification;

[0025] Figure 5 A flowchart of an embodiment of an entity attribute data query method provided in this specification;

[0026] Figure 6 A schematic diagram of the entity attribute data query process in some embodiments provided in this specification;

[0027] Figure 7 A flowchart of an embodiment of an entity attribute data configuration method provided in this specification;

[0028] Figure 8 A schematic diagram of the entity attribute data configuration process in some embodiments provided in this specification;

[0029] Fig. 9 A schematic diagram of updating attribute data of a physical unit in some embodiments provided in this specification;

[0030] Fig.10 A schematic diagram of updating attribute data of a physical unit in some other embodiments provided in this specification;

[0031] Fig.11 A schematic diagram of a common updating method of attribute data of a physical unit in some embodiments provided in this specification;

[0032] Fig.12 A schematic diagram of the module structure of an entity attribute data query device provided in this specification;

[0033] Fig.13 A schematic diagram of the module structure of an entity attribute data configuration device provided in this specification;

[0034] Fig.14 This is a schematic diagram of the functional module structure of a server provided in this specification. DETAILED DESCRIPTION

[0035] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below in conjunction with the drawings in one or more embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of the specification, not all of the embodiments. Based on one or more embodiments of the specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the embodiments of this specification.

[0036] In an example of an application scenario of this specification, a method for maintaining and querying entity attribute data is provided, and the method can be applied to a server. The server can be used to configure, store, and query entity association relationships, and can also be used to configure, store, and query entity attribute data. The server can be a single server or a server cluster consisting of multiple servers.

[0037] In the embodiments of this specification, an entity unit may refer to a specific element value corresponding to an entity. The entity may refer to a general term for a class of pre-configured elements. For example, for a bank, the bank's organization, personnel, outlets, etc. may each be an entity. Specific branches, personnel, and outlets may be entity units under the corresponding entity. For example, a person is an entity, and an employee XX under the bank is an entity unit. Specific entities and entity units under entities may be configured according to actual scenarios, and are not limited here.

[0038] Different entities can have different attribute types. For example, an organization can have business calendar, assets, transaction authorization and other entity attribute types, and a person can have qualifications, tags, and department attributes. For a branch or an employee, there can be attribute data under the corresponding attribute type. For example, the asset attribute of a branch, XX branch has asset amount, and accordingly, asset amount is the attribute data of XX branch under asset attribute.

[0039] In some embodiments, the association relationship corresponding to the entity unit when storing the attribute data can be pre-configured. The association relationship may include an inheritance relationship. The inheritance relationship may mean that the associated party entity unit inherits the attribute data of the associated party entity unit. The associated party entity unit refers to the entity unit that uses the attribute data of other entity units as its own attribute data. The associated party entity unit refers to the entity unit that the associated party entity unit refers to when storing the attribute data.

[0040] Figure 1 as well as Figure 2 A schematic diagram showing the association relationship between entity units when storing attribute data. Figure 1 As shown, e 1 With e 2 There is an inheritance relationship between them, where e 1 is the entity unit of the related party, and e 2 The inheritance relationship indicates that the associated entity unit completely inherits the attribute data of the associated entity unit and is consistent with it. The associated entity unit can only inherit the attribute data of one associated entity unit and cannot inherit multiple associated entity units. However, the associated entity unit can correspond to multiple associated entity units, that is, its attribute data can be inherited by multiple associated entity units.

[0041] like Figure 1 As shown, multiple entity units can all inherit a certain entity unit e 1 , and e 1 No longer inherits other entity units, then e 1 is a leaf entity unit. A leaf entity unit may correspond to one or more according to the actual application scenario, such as Figure 2 As shown, there is no inheritance relationship in the upper layer 1 and e 2 All of them are leaf entity units. Accordingly, entity units that no longer correspond to inherited associated entity units can be regarded as leaf entity units.

[0042] In some embodiments, the association relationship may also include a co-location relationship. The co-location relationship may indicate that the entity unit of the associating party and the entity unit of the associated party are the same entity unit. Accordingly, the entity unit corresponding to the co-location relationship may be regarded as a leaf entity unit. By further configuring the co-location relationship, the leaf entity unit may be determined more simply.

[0043] The association relationship between entity units can be sorted out in advance, and which entity unit is used as the associating entity unit and which entity unit is used as the associated entity unit can be configured according to the actual application scenario. In some embodiments, the association relationship between entity units can be stored through an entity association relationship table (Entity_Association). Table 1 shows a description table of storage fields of the entity association relationship table.

[0044] Table 1

[0045]

[0046]

[0047] As described in Table 1 above, the association relationship of each entity unit can be pre-stored in the entity association relationship table, and different entity attribute types can be represented by different Attr_Type. Different entity association relationship tables can be configured for different entities. Accordingly, if a certain association relationship is applied to all entity attribute types of a certain entity, the entity attribute type item can directly select the default default. In other embodiments, different entity association relationship tables can also be configured for different entity attribute types to facilitate storage and query.

[0048] As shown in Table 1, the association relationship can be configured as an inheritance relationship and a co-location relationship. The inheritance relationship indicates that the Related_Entity completely inherits the attribute data of the Be_Related_Entity and is consistent with it. The Related_Entity cannot inherit multiple Be_Related_Entities.

[0049] The homonymous relationship indicates that the Related_Entity and the Be_Related_Entity are the same. In this case, the entity unit corresponding to the homonymous relationship can be used as a leaf entity unit (Leaf-EU (Leaf Entity Unit)).

[0050] In some other implementations, the association relationship may also be represented by a relationship model. Figure 1 as well as Figure 2 In this way, the relationship direction identifier and / or text identifier can be used to represent the corresponding relationship between two entity units under the attribute type. In some embodiments, different relationship models can also be configured for different entity attribute types, so as to quickly determine the relationship between entity units under a certain entity attribute type, improve the simplicity of attribute data maintenance and query efficiency, etc.

[0051] After configuring the association relationship of the entity units, the storage configuration of the attribute data can be performed based on the association relationship. The attribute data corresponding to the leaf entity unit can be associated and stored with the leaf entity unit, and other entity units no longer store their corresponding attribute data. Accordingly, the attribute data of other entity units except the leaf entity unit can be determined by the association relationship of the entity units and the stored attribute data of the leaf entity unit.

[0052] The attribute data of the leaf entity unit can be stored in the attribute data set, and the leaf entity unit, the attribute type and the attribute data can be associated. In some implementations, the attribute data of the leaf entity unit can be stored in the form of a data table. Of course, other storage methods can also be used, which are not limited here. In some implementations, the attribute data set corresponding to each entity can be configured separately, or further subdivided to configure the attribute data set corresponding to each entity attribute type.

[0053] Figure 3 Indicates the storage method of the attribute data of the leaf entity unit and the storage method of other entity units except the leaf unit. Figure 3 As shown, EntityAttr(E,A) (the attribute data set of entity E under attribute type A) stores e 1 、e 2 , ...In the attribute data under attribute type A, the table under EntityAttr(E,A) is the Entity_Association (entity association) collection. Figure 3 As shown, Entity_Association stores e 3 With e 1 、e 10 With e 2 、e k With e 10 The inheritance relationship of e k 、e 10 With e 2 The corresponding attribute data under attribute type A is the same, e 3 With e 1 The corresponding attribute data under attribute type A is the same. Accordingly, there is no need to store e in EntityAttr(E,A) k 、e 10 、e 3 Attribute data of .

[0054] Currently, the commonly used Figure 4 The entity attribute storage format shown in Figure 1 is as follows.

[0055] Entity(E) represents the collection of m entity units (m specific organizations) of entity E(organization);

[0056] Entity(E)={e1,e2,…,em};

[0057] Attr(A) represents the set of n attribute items of entity attribute A;

[0058] Attr(A)={a1,a2,…,an};

[0059] EntityAttr(E,A) represents the set of attributes A of entity E;

[0060] EntityAttr(E,A)={e1a1,e1a2,…,eman};

[0061] EntityAttrData(e,A) represents the value of entity attribute A of entity element e;

[0062] EntityAttrData(e,A)=ea={ea1,ea2,…,ean};

[0063] For example, if an attribute data of an entity unit is counted as a minimum storage unit, its storage size can be quantified as Scale. Assume:

[0064] Scale(E) represents the scale of entity E;

[0065] Scale(A) indicates the scale of attribute type A;

[0066] Scale(E,A) represents the scale of attribute type A of entity E;

[0067] but:

[0068] Scale(E)=m, which is the number of entity units of entity E;

[0069] Scale(A)=n, which is the number of attribute data of attribute type A;

[0070] Scale(E,A)=m×n;

[0071] Assume that a financial institution B has x entities, each of which contains m entity units, y attribute types, and each attribute type contains n attribute data. It can be inferred that the storage scale of entity attribute data of financial institution B is:

[0072]

[0073] For financial institutions, the values ​​are generally x>=5, y>=5, m>=50000, n>=300;

[0074] Then: Scale(B)>=375 million.

[0075] It can be seen that the storage scale of attribute data of financial institutions often exceeds 2.25 billion, and usually one attribute data occupies a large space, which requires a large storage cost. At the same time, the large amount of stored data will also lead to low efficiency in reading attribute data.

[0076] Using the solution provided in the embodiments of this specification:

[0077] Scale(E,A)(NEW)=m×4+i×n (m is the number of entity units of entity E, n is the number of attribute data of entity attribute type A, 4 represents the number of fields of Entity_Association, and i represents the number of leaf entity units);

[0078] The difference D = Scale(E, A) - Scale(E, A)(NEW)

[0079] =m(n-4)–i×n

[0080] When n>>4 (generally, the number of entity attributes will be much larger than 4), then D=n(m–i).

[0081] In reality, most large financial institutions only have one leaf entity unit. In this case, i=1. Correspondingly, m>>i. That is to say, the larger the entity scale is, the larger D is, and the larger the storage scale that can be reduced by the solution of the present invention is.

[0082] It can be seen that in application scenarios with many entity units or many attribute types, such as large financial institutions, if the attribute data is stored directly, a large storage space will be consumed. Through the scheme of the above embodiment of this specification, only the attribute data of the leaf entity unit needs to be stored, and for other entity units, only the association relationship of the entity unit needs to be stored. There are relatively few leaf entity units, and the byte data occupied by the fields in the association relationship is also small, which can greatly save the storage space of the server and reduce storage costs.

[0083] Based on the solution provided in the above embodiment, this specification also provides a method for querying entity attribute data. Figure 5 As shown, the method can be applied to a server. Accordingly, the method can include the following steps:

[0084] S50: receiving an entity attribute data query request; the entity attribute query request includes an entity unit to be queried and an attribute type to be queried corresponding to the entity unit to be queried.

[0085] The server can receive entity attribute data query requests. The entity attribute data query request can be sent by a user terminal or by a server of a business system. For example, if a business person wants to query the asset amount data of a branch, he can initiate an entity attribute data query request through his user terminal. Alternatively, when a business system processes a business, it needs to call certain entity attribute data, and it can also send an entity attribute data query request to a server that performs processing such as querying the entity attribute data. Accordingly, the server that performs processing such as querying the entity attribute data can receive an entity attribute data query request sent by a user terminal or a server of a business system.

[0086] The entity attribute query request may include the entity unit to be queried and the attribute type to be queried corresponding to the entity unit to be queried. For example, if a business person wants to query the asset amount data of a branch, he can enter the name or logo of the branch and the name of the attribute type, such as asset or logo, in the query interface of the user terminal. Then, the user terminal can respond to the user's query instruction, generate a query request based on the information entered by the user, and send it to the server.

[0087] S52: Determine the leaf entity unit corresponding to the entity unit to be queried by using the pre-configured entity unit association relationship; wherein the entity unit association relationship includes the association relationship between entity units; the association relationship includes an inheritance relationship and a homonymous relationship; the inheritance relationship refers to the association party entity unit inheriting the attribute data of the association party entity unit; the homonymous relationship indicates that the association party entity unit and the association party entity unit are the same entity unit; the leaf entity unit refers to the entity unit corresponding to the homonymous relationship.

[0088] After receiving the query request, the server can use the pre-configured entity unit association relationship to determine the leaf entity unit corresponding to the entity unit to be queried. The construction and storage methods of the entity unit association relationship can refer to the above embodiment and will not be repeated here.

[0089] For example, assuming that the entity unit association relationship is stored in an entity association relationship table, the server can find the leaf entity unit corresponding to the entity unit to be queried under the attribute type to be queried from the entity association relationship table. Figure 3 As shown, assuming that the entity unit to be queried is e k , the attribute type to be queried is A, then you can use Figure 3 In the entity association table, the corresponding associated entity unit is found to be e 10 , e 10 The related party entity unit is e 2 , e 2 The related party entity unit is e2 . Then we can determine e k The corresponding leaf entity element e 2 .

[0090] If the entity element association relationship is Figure 1 or Figure 2 The association relationship model shown is stored. After finding the association relationship model corresponding to the attribute type to be queried, the entity unit to be queried can be located, and then the corresponding leaf entity unit can be found layer by layer through the association relationship description information in the model.

[0091] S54: Acquire the attribute data of the leaf entity unit corresponding to the entity unit to be queried under the attribute type to be queried, as the attribute data of the entity unit to be queried under the attribute type to be queried.

[0092] After determining the leaf entity unit, the server may obtain the attribute data of the leaf entity unit corresponding to the entity unit to be queried under the attribute type to be queried as the attribute data of the entity unit to be queried under the attribute type to be queried. Figure 3 As shown, assuming that the entity attribute data is stored in the entity attribute data table, the server can find the leaf entity unit e from the entity attribute data table. 2 Attribute data under attribute type A. You can find the e 2 The attribute data under attribute type A is as e k Attribute data under attribute type A.

[0093] The server is looking for e 2 After the attribute data under attribute type A, it can be used as e k The query result of the attribute data under attribute type A is sent to the user terminal so that the user terminal can display it. Alternatively, it can also be sent to the server of the business system so that the server can perform subsequent processing based on the attribute data.

[0094] refer to Figure 6 In a scenario example, the following methods can be used to query attribute data:

[0095] The user can input the entity unit e and the attribute type A to be queried through the user terminal, that is, the value of the attribute type A of the entity unit e is queried from EntityAttr(E,A).

[0096] The server can read the entity unit association relationship and convert the input entity unit e into the entity unit e actually stored in EntityAttr(E,A) k (e k is a leaf entity unit).

[0097] Assuming that f(e) represents the entity conversion rule, the conversion operation can be completed in the following way:

[0098]

[0099] The algorithm is expressed as:

[0100]

[0101] in,

[0102]

[0103]

[0104] The server can then retrieve e from EntityAttr(E,A) k and feeds back the attribute value to the user terminal for display.

[0105] Based on the solution provided in the above embodiment, this specification also provides a method for configuring entity attribute data. Figure 7 As shown, the method can be applied to a server. Accordingly, the method can include the following steps:

[0106] S70: receiving an entity attribute data configuration request sent by a user terminal; the entity attribute configuration request includes an entity unit to be configured and a to-be-configured attribute type and to-be-configured attribute data corresponding to the to-be-configured entity unit.

[0107] When entity attribute data needs to be updated or added, the relevant business personnel can send an entity attribute data configuration request to the server through the user terminal. For example, the user can input the entity unit to be updated or added, the attribute type of the corresponding entity unit, and the attribute data through the user terminal. For the convenience of expression, the entity unit to be updated or added input by the user can be described as the entity unit to be configured, the corresponding input attribute type can be described as the attribute type to be configured, and the input attribute data can be described as the attribute data to be configured. In response to the relevant instructions of the user, the user terminal can generate an entity attribute data configuration request based on the above information input by the user and send it to the server. Accordingly, the server can receive the entity attribute data configuration request sent by the user terminal.

[0108] S72: When it is determined that the entity unit to be configured belongs to a leaf entity unit by using a pre-built entity unit association relationship, the attribute data to be configured is configured into the entity attribute data set based on the entity unit to be configured and the attribute type to be configured; wherein the entity unit association relationship includes the association relationship between entity units; the association relationship includes an inheritance relationship and a homonymous relationship; the inheritance relationship refers to that the associated entity unit inherits the attribute data of the associated entity unit; the homonymous relationship indicates that the associated entity unit and the associated entity unit are the same entity unit; the leaf entity unit refers to the entity unit corresponding to the homonymous relationship.

[0109] After receiving the entity attribute data configuration request sent by the user terminal, the server can use the pre-configured entity unit association relationship to determine whether the configured entity unit belongs to a leaf entity unit. The construction and storage of the entity unit association relationship can be implemented with reference to the above embodiment and will not be repeated here.

[0110] In some embodiments, before using the pre-configured entity unit association relationship to determine whether the configured entity unit belongs to a leaf entity unit, the attribute data to be configured may be verified first. The attribute data verification rule corresponding to the attribute type to be configured may be used to verify the attribute data to be configured.

[0111] Entity attribute data is usually data within a certain range of rules, so its data must usually meet the relevant requirements of attribute data before it is allowed to be entered into the server to ensure the accuracy of the entered data. For example, gender must be male or female; age must be a positive integer; date must be a real and legal date and must be greater than a certain date; job number must be a real job; ID number must be 18 digits, etc. Attribute data of different attribute types usually have different corresponding requirements. You can configure the corresponding verification rules for each attribute type in advance, and then use the verification rules corresponding to each attribute type to verify the configured attribute data to determine whether it meets the preset rules. For data that does not meet the preset rules, you can refuse to maintain it. For example, the server can feedback to the user terminal a prompt message that the data meets the requirements.

[0112] When it is determined that the attribute data to be configured meets the preset verification rules, the server can use the pre-configured entity unit association relationship to determine whether the entity unit to be configured belongs to a leaf entity unit. For example, assuming that the entity unit association relationship is stored through an entity association relationship table, the server can query the entity unit to be configured from the entity association relationship table under the attribute type to be configured. The corresponding association relationship is a co-location relationship. If so, it can be determined that it belongs to a leaf entity unit; otherwise, it is determined that it does not belong to a leaf entity unit.

[0113] In the case where it is determined that the entity unit to be configured belongs to a leaf entity unit, the server may configure the entity unit to be configured into the entity attribute data set to which the entity unit to be configured belongs.

[0114] If the entity attribute data set already has corresponding attribute data, the attribute data of the entity unit to be configured under the attribute type to be configured may be updated to the attribute data to be configured, that is, the original attribute data is updated to the attribute data to be configured.

[0115] If the corresponding attribute data does not already exist in the entity attribute data set, the entity unit to be configured, the attribute type to be configured, and the attribute data item can be added to the entity attribute data set. For example, a row of entity units to be configured, attribute types to be configured, and attribute data items can be added to the entity attribute data table. Then, the attribute data to be configured can be filled into the attribute data item based on the entity unit to be configured and the attribute type to be configured. The addition of attribute data is completed.

[0116] When re-maintaining the attribute data of a non-leaf entity unit, the user can also input the attribute data of the corresponding entity unit that needs to be re-maintained through the user terminal. Accordingly, the server can determine that the received entity unit to be configured does not belong to a leaf entity unit based on the pre-configured entity unit association relationship. At this time, the server can delete the association relationship between the entity unit to be configured and its corresponding associated party entity unit in the pre-configured entity association relationship, and configure the entity unit to be configured as a leaf entity unit. Thereby, the entity unit association relationship is updated.

[0117] Then, the attribute data to be configured can be added to the entity attribute data set based on the entity unit to be configured and the attribute type to be configured. For example, a row of entity units to be configured, attribute types to be configured, and attribute data items can be added to the entity attribute data table. Then, the attribute data to be configured can be filled into the attribute data items based on the entity unit to be configured and the attribute type to be configured. The conversion of the association relationship and the addition of attribute data are completed.

[0118] If a new entity unit node is added, and the entity unit stores attribute data by inheritance, there is no need to add attribute data, and the entity unit association relationship can be directly updated. For example, you can add a row to the entity unit association relationship table and configure the attribute type, the associated entity unit, the associated entity unit and their association relationship to complete the attribute data update of the entity unit. The above method can greatly improve the simplicity and efficiency of attribute data maintenance.

[0119] In a scenario example, refer to Figure 8 , you can configure entity attribute data in the following ways:

[0120] 8.1: The user can input entity unit e and value ea of ​​attribute type A of entity unit e through the user terminal.

[0121] 8.2: Check whether ea satisfies the verification rules of A.

[0122] 8.3: If the validation rules are not met, the unsatisfied result is returned;

[0123] 8.4: If the verification rules are met, it means that ea is legal data of entity unit e;

[0124] 8.5: It can be determined whether e is a leaf entity unit;

[0125] 8.5.1: If yes, maintain ea in EntityAttr(E,A). Fig. 9 As shown, Fig. 9 Indicates that e 4 The attribute data is updated to EntityAttr(E,A).

[0126] 8.5.2: If not, adjust the entity element e to a leaf entity element, and then maintain ea in EntityAttr(E,A). Fig.10 As shown, e 3 With e 1 Delete the association relationship and set e 3 The attribute data of e is added to EntityAttr(E,A) to complete the 3 Adjustment of attribute data.

[0127] Then, the server may feed back the above configuration result to the user terminal so that the user terminal can display it.

[0128] like Fig.11 As described above, using the usual solution, if you want to modify e 3 The attribute values ​​of the entity units under its jurisdiction need to be modified separately 3 and its subordinate e 5 、e 6 etc. All the entity units under it, and if you need to modify e 1 and its subordinate entity unit attribute values, you need to modify e 1 、e 2 、e 3 、e 5 、e 6 Assume that there are m entity units under e to be modified, represented by TS(e), then TS(e) = m×(TS1(A)+TS2(A)).

[0129] The entity attribute maintenance includes at least the following two operation steps based on the above maintenance logic: entity attribute data verification S1 and entity attribute data storage S2.

[0130] set up:

[0131] TS1(A) represents the average time required for attribute type A verification;

[0132] TS2(A) represents the average time required to store attribute type A;

[0133] but:

[0134] The duration of maintaining the attribute value of attribute type A for each entity unit of entity E is:

[0135] TS(E,A)=m×(TS1(A)+TS2(A))

[0136] If the maintenance time of each attribute of each entity is the same, the maintenance time of all entity attributes is:

[0137]

[0138] Assumption: x>=5, y>=5, m>=50000, TS1(A)=TS2(A)=50ms

[0139] Then: TS(B)>=125000s.

[0140] From this we can see that using the commonly used solutions, the time cost of maintaining the entity attribute data of large financial institutions is also huge, and the maintenance efficiency is very low.

[0141] And using the scheme of the embodiment of this specification, such as Fig.11 As shown, whether it is to modify e 3 and its subordinates or e 1 And its subordinates, just need to modify e 3 The entity attribute value of .

[0142] TS(e)(NEW)=1×(TS1(A)+TS2(A))

[0143] The difference D = TS(e)-TS(e)(NEW)

[0144] =(m-1)×(TS1(A)+TS2(A))

[0145] If the entity attribute values ​​of all entities are maintained at once, the time difference D is 5000s. It can be inferred that the solution of the present invention greatly improves the maintenance efficiency.

[0146] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. For details, please refer to the description of the above-mentioned related processing related embodiments, and no further description is given here.

[0147] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0148] The distributed system testing method provided in one or more embodiments of this specification is to expand the stress testing tool of the business system, build a message producer that simulates sending messages to the message middleware, and a message consumer that retrieves messages from the message middleware for message consumption. Then, the expanded test tool can be used to produce message data to the message middleware, and retrieve message data from the message middleware for consumption, so as to simply and conveniently implement the testing of the processing performance of the message middleware. At the same time, through the above method, it is only a simple simulation of the producer and consumer processing architecture, and it is not necessary to build a test environment for all producers and consumers, which further saves the investment of test resources and reduces the overall testing cost of the distributed asynchronous message processing system. In addition, using the above method, the test of the business system can also be effectively associated with the test of the message middleware, and the production message, the consumption message and the ordinary transaction can be arranged together into the test scenario, so that the correlation of each link of the distributed asynchronous message processing is stronger, thereby improving the flexibility, comprehensiveness and effectiveness of the test, so as to accurately and effectively understand and control the system as a whole and each link, and ensure that the online system runs more stably.

[0149] Based on the entity attribute data query method described above, one or more embodiments of this specification also provide an entity attribute data query device. Fig.12 The module structure diagram of an embodiment of an entity attribute data query device provided in the specification is applied to a server, such as Fig.12 As shown, the device may include:

[0150] The query request receiving module 120 may be used to receive an entity attribute data query request; the entity attribute query request includes an entity unit to be queried and an attribute type to be queried corresponding to the entity unit to be queried;

[0151] The entity unit conversion module 122 can be used to determine the leaf entity unit corresponding to the entity unit to be queried by using the pre-configured entity unit association relationship; wherein the entity unit association relationship includes the association relationship between entity units; the association relationship includes an inheritance relationship and a co-location relationship; the inheritance relationship means that the entity unit of the associated party inherits the attribute data of the entity unit of the associated party; the co-location relationship means that the entity unit of the associated party and the entity unit of the associated party are the same entity unit; the leaf entity unit refers to the entity unit corresponding to the co-location relationship;

[0152] The attribute data query module 124 may be used to obtain the attribute data of the leaf entity unit corresponding to the entity unit to be queried under the attribute type to be queried, as the attribute data of the entity unit to be queried under the attribute type to be queried.

[0153] It should be noted that the above-mentioned device may also include other implementations according to the description of the method embodiment. The specific implementation methods can refer to the description of the relevant method embodiment, and will not be described one by one here.

[0154] Based on the above-mentioned entity attribute data configuration method, one or more embodiments of this specification also provide an entity attribute data configuration device. Fig.13 A schematic diagram of the module structure of an embodiment of an entity attribute data configuration device provided in the specification is applied to a server, such as Fig.13 As shown, the device may include:

[0155] The configuration request receiving module 130 may be used to receive an entity attribute data configuration request sent by a user terminal; the entity attribute configuration request includes an entity unit to be configured and a to-be-configured attribute type and to-be-configured attribute data corresponding to the to-be-configured entity unit;

[0156] The attribute data configuration module 132 can be used to configure the attribute data to be configured into the entity attribute data set based on the entity unit to be configured and the attribute type to be configured, when it is determined that the entity unit to be configured belongs to a leaf entity unit by using a pre-configured entity unit association relationship; wherein the entity unit association relationship includes the association relationship between entity units; the association relationship includes an inheritance relationship and a homonymous relationship; the inheritance relationship refers to the association party entity unit inheriting the attribute data of the association party entity unit; the homonymous relationship indicates that the association party entity unit and the association party entity unit are the same entity unit; the leaf entity unit refers to the entity unit corresponding to the homonymous relationship.

[0157] like Fig.13 As shown, in some other embodiments, the device may further include an association configuration module 134.

[0158] The association configuration module 134 can be used to delete the association between the entity unit to be configured and its corresponding associated entity unit in the pre-configured entity association relationship when it is determined that the entity unit to be configured does not belong to a leaf entity unit; and configure the entity unit to be configured as a leaf entity unit.

[0159] The attribute data configuration module 132 may also be used to add the attribute data to be configured into the entity attribute data set based on the entity unit to be configured and the attribute type to be configured.

[0160] like Fig.13 As shown, in some other embodiments, the device may further include:

[0161] The verification module 136 may be used to verify the attribute data to be configured using the attribute data verification rule corresponding to the attribute type to be configured.

[0162] The judgment module 138 may be used to judge whether the entity unit to be configured is a leaf entity unit when the verification is passed.

[0163] It should be noted that the above-mentioned device may also include other implementations according to the description of the method embodiment. The specific implementation methods can refer to the description of the relevant method embodiment, and will not be described one by one here.

[0164] The methods or devices described in the above embodiments provided in this specification can implement business logic through computer programs and record them on storage media, and the storage media can be read and executed by computers to achieve the effects of the solutions described in the embodiments of this specification. Therefore, this specification also provides a server, which may include a processor and a memory storing processor-executable instructions, and when the instructions are executed by the processor, the steps of the method described in any of the above embodiments are implemented.

[0165] Based on the solution of the above embodiment, in a scenario example, the server may include: Fig.14 The functional modules shown in the figure.

[0166] The entity attribute data input and output display module is mainly used to realize the display of the input and output of entity attribute data. Specifically, it can include query condition input display, maintained entity attribute data input display, query result output display, maintenance result output display, etc. The output display module can be sent by the server to the user terminal when the attribute data is queried or maintained, so that the user terminal can display the input and output interface to the user by parsing the function module. Alternatively, it can also be pre-packaged and sent to the user terminal so that the user terminal can be installed locally to realize data input and output display.

[0167] The entity attribute data checking module checks the input entity attribute data to determine whether it complies with the preset rules and refuses to maintain the data that does not comply.

[0168] The entity attribute data storage module is used for persistent data storage.

[0169] The entity conversion module is used to convert the entity e to be queried and maintained into the entity unit e physically stored in the entity attribute table EntityAttr(E,A) k The specific implementation process is detailed in the above embodiment.

[0170] The entity attribute processing module mainly implements the following functions:

[0171] Query entity attribute data:

[0172] EntityAttr queryEntityAttrData(EntityAttrType EntityAttr(E,A),Entitye);

[0173] Input: entity unit e, entity attribute type EntityAttr(E,A);

[0174] Output: attribute value ea of ​​entity element e in EntityAttr(E,A);

[0175] Function: Query the attribute value ea of ​​entity e in EntityAttr(E,A).

[0176] Maintain entity attribute data:

[0177] Int modifyEntityAttrData(EntityAttrType EntityAttr(E,A),Entity e,EntityAttr ea);

[0178] Input: entity element e, entity attribute type EntityAttr(E,A), attribute value ea of ​​entity element e in EntityAttr(E,A);

[0179] Output: maintenance result identification;

[0180] Function: Maintain the attribute value ea of ​​entity e in EntityAttr(E,A);

[0181] Key logic: If the attribute value of e already exists in EntityAttr(E,A), it will be overwritten with ea. If it does not exist, ea will be added directly in EntityAttr(E,A).

[0182] Query entity relationships:

[0183] EntityAssociation queryEntityAssociation(EntityAttrType EntityAttr(E,A),Entity e);

[0184] Input: entity unit e, entity attribute type EntityAttr(E,A);

[0185] Output: The entity relationship type of entity unit e is EntityAttr(E,A);

[0186] Function: Query the entity units whose entity relationship type of entity unit e is EntityAttr(E,A).

[0187] Maintaining entity relationships:

[0188] Int modifyEntityAssociation();

[0189] Function: Maintain entity-entity relationships.

[0190] It should be noted that the server described above may also include other implementations according to the description of the method embodiment. The specific implementation methods can refer to the description of the relevant method embodiment, which will not be described one by one here.

[0191] The embodiments of this specification are not limited to situations that must comply with standard data models / templates or the embodiments of this specification. Certain industry standards or slightly modified implementation plans based on the implementation described in the custom methods or embodiments can also achieve the same, equivalent or similar, or predictable implementation effects after deformation of the above-mentioned embodiments. The embodiments obtained by using these modified or deformed data acquisition, storage, judgment, processing methods, etc. can still fall within the scope of the optional implementation plans of this specification.

[0192] The storage medium may include a physical device for storing information, which is usually a medium that digitizes the information and then stores it in an electrical, magnetic or optical manner. The storage medium may include: a device that stores information in an electrical energy manner, such as various memories, such as RAM, ROM, etc.; a device that stores information in a magnetic energy manner, such as a hard disk, a floppy disk, a magnetic tape, a magnetic core memory, a magnetic bubble memory, a USB flash drive; a device that stores information in an optical manner, such as a CD or a DVD. Of course, there are other readable storage media, such as quantum memory, graphene memory, etc.

[0193] Each embodiment in this specification is described in a progressive manner, and the same and similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment. In the description of this specification, the description of the reference terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of this specification. In this specification, the schematic representation of the above terms does not necessarily target the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner. In addition, in the absence of contradiction, a person skilled in the art can combine and combine the different embodiments or examples described in this specification and the features of different embodiments or examples.

[0194] The above description is only an embodiment of the present specification and is not intended to limit the present specification. For those skilled in the art, the present specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification shall be included in the scope of the claims of the present specification.

Claims

1. A method for querying entity attribute data, characterized in that: Applied to a server, the method comprises: Receive an entity attribute data query request; the entity attribute data query request includes an entity unit to be queried and an attribute type to be queried corresponding to the entity unit to be queried; The leaf entity unit corresponding to the entity unit to be queried is determined by using a pre-configured entity unit association relationship; wherein the entity unit association relationship includes an association relationship between entity units; the association relationship includes an inheritance relationship and a co-location relationship; the inheritance relationship means that the entity unit of the associated party inherits the attribute data of the entity unit of the associated party; the co-location relationship means that the entity unit of the associated party and the entity unit of the associated party are the same entity unit; the leaf entity unit refers to the entity unit corresponding to the co-location relationship; the entity unit association relationship includes the entity attribute type to which the entity unit association relationship is applied; different entity attribute types correspond to different entity unit association relationships; Acquire the attribute data of the leaf entity unit corresponding to the entity unit to be queried under the attribute type to be queried as the attribute data of the entity unit to be queried under the attribute type to be queried; The method of determining the leaf entity unit corresponding to the entity unit to be queried by using the pre-configured entity unit association relationship includes: Retrieving the entity unit association relationship corresponding to the attribute type to be queried; Determine the leaf entity unit corresponding to the entity unit to be queried by using the entity unit association relationship corresponding to the attribute type to be queried; The step of obtaining the attribute data of the leaf entity unit corresponding to the entity unit to be queried under the attribute type to be queried includes: Acquire an entity attribute data set; the entity attribute data set includes a leaf entity unit and attribute data of the leaf entity unit under each entity attribute type; The attribute data of the leaf entity unit corresponding to the entity unit to be queried under the attribute type to be queried is queried from the entity attribute data set.

2. An entity attribute data query device, characterized in that: Applied to a server, the device comprises: A query request receiving module, used to receive an entity attribute data query request; the entity attribute data query request includes an entity unit to be queried and an attribute type to be queried corresponding to the entity unit to be queried; An entity unit conversion module is used to determine the leaf entity unit corresponding to the entity unit to be queried by using a pre-configured entity unit association relationship; wherein the entity unit association relationship includes an association relationship between entity units; the association relationship includes an inheritance relationship and a co-location relationship; the inheritance relationship means that the entity unit of the associated party inherits the attribute data of the entity unit of the associated party; the co-location relationship indicates that the entity unit of the associated party and the entity unit of the associated party are the same entity unit; the leaf entity unit refers to the entity unit corresponding to the co-location relationship; the entity unit association relationship includes the entity attribute type to which the entity unit association relationship is applied; different entity attribute types correspond to different entity unit association relationships; An attribute data query module, used to obtain the attribute data of the leaf entity unit corresponding to the entity unit to be queried under the attribute type to be queried, as the attribute data of the entity unit to be queried under the attribute type to be queried; The entity unit conversion module is specifically used for: Retrieving the entity unit association relationship corresponding to the attribute type to be queried; Determine the leaf entity unit corresponding to the entity unit to be queried by using the entity unit association relationship corresponding to the attribute type to be queried; The attribute data query module is specifically used for: Acquire an entity attribute data set; the entity attribute data set includes a leaf entity unit and attribute data of the leaf entity unit under each entity attribute type; The attribute data of the leaf entity unit corresponding to the entity unit to be queried under the attribute type to be queried is queried from the entity attribute data set.

3. A method for configuring entity attribute data, characterized in that: Applied to a server, the method comprises: Receiving an entity attribute data configuration request sent by a user terminal; the entity attribute data configuration request includes a to-be-configured entity unit and a to-be-configured attribute type and to-be-configured attribute data corresponding to the to-be-configured entity unit; In the case where it is determined by utilizing the pre-configured entity unit association relationship that the entity unit to be configured belongs to a leaf entity unit, the attribute data to be configured is configured into an entity attribute data set based on the entity unit to be configured and the attribute type to be configured; wherein the entity unit association relationship includes the association relationship between entity units; the association relationship includes an inheritance relationship and a co-location relationship; the inheritance relationship refers to the inheritance of the attribute data of the associated entity unit by the associated entity unit; the co-location relationship indicates that the associated entity unit and the associated entity unit are the same entity unit; the leaf entity unit refers to the entity unit corresponding to the co-location relationship; the entity unit association relationship includes the entity attribute type to which the entity unit association relationship is applied; different entity attribute types correspond to different entity unit association relationships; the entity attribute data set includes the leaf entity unit and the attribute data of the leaf entity unit under each entity attribute type; The method of using the pre-configured entity unit association relationship to determine that the entity unit to be configured belongs to a leaf entity unit includes: Retrieving the entity unit association relationship corresponding to the attribute type to be configured; The entity unit association relationship corresponding to the attribute type to be configured is used to determine that the entity unit to be configured belongs to a leaf entity unit.

4. The method according to claim 3, characterized in that In the case where it is determined that the entity unit to be configured does not belong to a leaf entity unit, deleting the association relationship between the entity unit to be configured and its corresponding associated party entity unit in the pre-configured entity association relationship; and configuring the entity unit to be configured as a leaf entity unit; The attribute data to be configured is added to the entity attribute data set based on the entity unit to be configured and the attribute type to be configured.

5. The method according to claim 3, characterized in that: Before determining that the entity unit to be configured belongs to a leaf entity unit, the method further includes: Verifying the attribute data to be configured using the attribute data verification rule corresponding to the attribute type to be configured; If the verification is passed, it is determined whether the entity unit to be configured belongs to a leaf entity unit.

6. The method according to claim 3, characterized in that The configuring the attribute data to be configured into the entity attribute data set based on the entity unit to be configured and the attribute type to be configured includes: When the attribute data of the entity unit to be configured under the attribute type to be configured does not exist in the entity attribute data set, adding the entity unit to be configured, the attribute type to be configured and the attribute data item to the entity attribute data set; The attribute data to be configured is filled into the attribute data item based on the entity unit to be configured and the attribute type to be configured.

7. The method according to claim 3, characterized in that The configuring the attribute data to be configured into the entity attribute data set based on the entity unit to be configured and the attribute type to be configured includes: When the attribute data of the entity unit to be configured under the attribute type to be configured exists in the entity attribute data set, the attribute data of the entity unit to be configured under the attribute type to be configured is updated to the attribute data to be configured.

8. An entity attribute data configuration device, characterized in that: Applied to a server, the device comprises: A configuration request receiving module, configured to receive an entity attribute data configuration request sent by a user terminal; the entity attribute data configuration request includes a to-be-configured entity unit and a to-be-configured attribute type and to-be-configured attribute data corresponding to the to-be-configured entity unit; An attribute data configuration module is used to configure the attribute data to be configured into an entity attribute data set based on the entity unit to be configured and the attribute type to be configured, when it is determined that the entity unit to be configured belongs to a leaf entity unit by using a pre-configured entity unit association relationship; wherein the entity unit association relationship includes an association relationship between entity units; the association relationship includes an inheritance relationship and a co-location relationship; the inheritance relationship means that the associated entity unit inherits the attribute data of the associated entity unit; the co-location relationship means that the associated entity unit and the associated entity unit are the same entity unit; the leaf entity unit refers to the entity unit corresponding to the co-location relationship; the entity unit association relationship includes the entity attribute type to which the entity unit association relationship is applied; different entity attribute types correspond to different entity unit association relationships; the entity attribute data set includes leaf entity units and the attribute data of leaf entity units under each entity attribute type; The method of using the pre-configured entity unit association relationship to determine that the entity unit to be configured belongs to a leaf entity unit includes: Retrieving the entity unit association relationship corresponding to the attribute type to be configured; The entity unit association relationship corresponding to the attribute type to be configured is used to determine that the entity unit to be configured belongs to a leaf entity unit.

9. The device according to claim 8, characterized in that The device also includes an association relationship configuration module; wherein, The association relationship configuration module is used to delete the association relationship between the entity unit to be configured and its corresponding associated party entity unit in the pre-configured entity association relationship when it is determined that the entity unit to be configured does not belong to the leaf entity unit; and configure the entity unit to be configured as a leaf entity unit; The attribute data configuration module is further used to add the attribute data to be configured into the entity attribute data set based on the entity unit to be configured and the attribute type to be configured.

10. The device according to claim 8, characterized in that The device also includes: A verification module, used to verify the attribute data to be configured using the attribute data verification rule corresponding to the attribute type to be configured; The judgment module is used to judge whether the entity unit to be configured is a leaf entity unit when the verification passes.

11. A server, characterized in that: The server includes at least one processor and a memory for storing processor-executable instructions, and the instructions, when executed by the processor, implement the steps of the method described in any one of claims 1 or 3-7.

Images