CN112115235A - Entity attribute data query and configuration method, device and server - Google Patents
Entity attribute data query and configuration method, device and server Download PDFInfo
- Publication number
- CN112115235A CN112115235A CN202011044663.5A CN202011044663A CN112115235A CN 112115235 A CN112115235 A CN 112115235A CN 202011044663 A CN202011044663 A CN 202011044663A CN 112115235 A CN112115235 A CN 112115235A
- Authority
- CN
- China
- Prior art keywords
- entity
- entity unit
- attribute data
- attribute
- unit
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 55
- 238000006243 chemical reaction Methods 0.000 claims abstract description 9
- 238000012795 verification Methods 0.000 claims description 9
- 230000015654 memory Effects 0.000 claims description 8
- 238000013524 data verification Methods 0.000 claims description 4
- 238000012423 maintenance Methods 0.000 abstract description 14
- 238000013500 data storage Methods 0.000 abstract description 7
- 238000012545 processing Methods 0.000 description 13
- 238000010586 diagram Methods 0.000 description 12
- 238000012360 testing method Methods 0.000 description 10
- 238000013475 authorization Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 6
- 230000008520 organization Effects 0.000 description 4
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 238000010276 construction Methods 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000000750 progressive effect Effects 0.000 description 2
- 238000012797 qualification Methods 0.000 description 2
- OKTJSMMVPCPJKN-UHFFFAOYSA-N Carbon Chemical compound [C] OKTJSMMVPCPJKN-UHFFFAOYSA-N 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000013499 data model Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 229910021389 graphene Inorganic materials 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 238000009662 stress testing Methods 0.000 description 1
- 230000026676 system process Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/33—Querying
- G06F16/3331—Query processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/31—Indexing; Data structures therefor; Storage structures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/33—Querying
- G06F16/338—Presentation of query results
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- Software Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the specification discloses an entity attribute data query and configuration method, an entity attribute data query and configuration device and a server, wherein attribute data are stored and maintained by taking only some entity units as leaf entity units, and other entity units establish the association relationship of the entity units during entity attribute data storage in a mode of inheriting the attribute data corresponding to the leaf entity units, so that the attribute data of all the entity units are stored based on the association relationship and the attribute data of the leaf entity units. When the attribute data is inquired and maintained, only the attribute data of the leaf entity unit is required to be maintained, and for the non-leaf entity unit, the attribute data of the corresponding leaf entity unit can be called in an entity unit conversion mode to inquire the attribute data. Therefore, the storage scale of the entity attribute data is greatly reduced, the maintenance amount of the entity attribute data is further reduced, and the query efficiency is improved.
Description
Technical Field
The present disclosure relates to the field of computer data processing technologies, and in particular, to a method, an apparatus, and a server for querying and configuring entity attribute data.
Background
Generally, a financial institution is composed of entities such as institutions, personnel and websites, and these entities include specific entity units such as branches, personnel and websites. Each entity corresponds to a number of entity attributes. For example, the organization corresponds to attributes such as a business calendar, assets, and transaction authorization, and the person corresponds to attributes such as qualification and tags. Because each entity unit has a certain difference, and there are many entity units and entity attribute types, it usually takes a relatively large time and cost to query, store, and maintain the attribute values corresponding to these entity units on a daily basis.
For example, a commercial bank contains 50 million branches, each branch containing business calendar attributes. The business calendar indicates whether a certain day of a certain branch office in a certain year is in business or not in a commercial bank, and the business calendar is generally accurate to the day according to the needs of the branch office. Then the business calendar for one year would contain 365 days, and the business bank would need to maintain more than 1.825 billion attribute entry fields with only one new business calendar for all branches of the business bank. As another example, each branch of the commercial bank may contain transaction authorization attributes. The transaction authorization attribute refers to whether a certain transaction of a certain branch mechanism needs authorization in a commercial bank, and generally the transaction and the post are accurate according to the mechanism requirement. Assuming that the transaction authorization attribute contains 50 different authorization transactions, each of which in turn contains 10 authorization positions, if the transaction authorization attribute for each institution is maintained, more than 2.5 billion attribute entry fields need to be maintained. Therefore, the workload of inquiring and maintaining the entity attribute data in the actual service system is huge, and a huge storage space is occupied. Therefore, a more efficient and simple method for configuring entity attribute data is needed.
Disclosure of Invention
Embodiments of the present disclosure provide a method, an apparatus, and a server for querying and configuring entity attribute data, which can greatly reduce storage scale of the entity attribute data and maintenance amount of the entity attribute data, and improve query efficiency of the entity attribute data.
The specification provides a method, a device and a server for querying and configuring entity attribute data, which are realized by the following modes:
an entity attribute data query method is applied to a server, and comprises the following steps: receiving an entity attribute data query request; the entity attribute query request comprises 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 inquired by utilizing a preset entity unit incidence relation; wherein the entity unit incidence relation comprises an incidence relation between entity units; the incidence relation comprises an inheritance relation and a parity relation; the inheritance relationship refers to that the entity unit of the associated party inherits the attribute data of the entity unit of the associated party; the same-position relation represents that the entity unit of the related party and the entity unit of the related party are the same entity unit; the leaf entity unit refers to the entity unit corresponding to the same position relation; and acquiring 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.
In other embodiments of the method provided in this specification, the determining, by using a preconfigured entity unit association relationship, a leaf entity unit corresponding to the entity unit to be queried includes: calling an entity unit incidence relation corresponding to the attribute type to be inquired; and determining the leaf entity unit corresponding to the entity unit to be inquired by using the entity unit incidence relation corresponding to the attribute type to be inquired.
In other embodiments of the method provided in this specification, the obtaining attribute data of the leaf entity unit corresponding to the entity unit to be queried in the attribute type to be queried includes: acquiring an entity attribute data set; the entity attribute data set comprises leaf entity units and attribute data of the leaf entity units under each entity attribute type; and inquiring attribute data of the leaf entity unit corresponding to the entity unit to be inquired under the attribute type to be inquired from the entity attribute data set.
On the other hand, an embodiment of the present specification further provides an entity attribute data query apparatus, which is applied to a server, and the apparatus includes: the query request receiving module is used for receiving an entity attribute data query request; the entity attribute query request comprises an entity unit to be queried and an attribute type to be queried corresponding to the entity unit to be queried; the entity unit conversion module is used for determining a leaf entity unit corresponding to the entity unit to be inquired by utilizing a preset entity unit incidence relation; wherein the entity unit incidence relation comprises an incidence relation between entity units; the incidence relation comprises an inheritance relation and a parity relation; the inheritance relationship refers to that the entity unit of the associated party inherits the attribute data of the entity unit of the associated party; the same-position relation represents that the entity unit of the related party and the entity unit of the related party are the same entity unit; the leaf entity unit refers to the entity unit corresponding to the same position relation; and the attribute data query module is used for acquiring the attribute data of the leaf entity unit corresponding to the entity unit to be queried under the attribute type to be queried, and taking the attribute data as the attribute data of the entity unit to be queried under the attribute type to be queried.
On the other hand, an embodiment of the present specification further 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 comprises an entity unit to be configured, and an attribute type to be configured and attribute data to be configured which correspond to the entity unit to be configured; under the condition that the entity unit to be configured belongs to a leaf entity unit is determined by utilizing a pre-configured entity unit incidence relation, 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; wherein the entity unit incidence relation comprises an incidence relation between entity units; the incidence relation comprises an inheritance relation and a parity relation; the inheritance relationship refers to that the entity unit of the associated party inherits the attribute data of the entity unit of the associated party; the same-position relation represents that the entity unit of the related party and the entity unit of the related party are the same entity unit; the leaf entity unit refers to the entity unit corresponding to the same position relationship.
In other embodiments of the method provided in this specification, in a case that it is determined that the entity unit to be configured does not belong to a leaf entity unit, deleting an association relationship between the entity unit to be configured and an associated entity unit corresponding to the entity unit to be configured in a preconfigured entity association relationship; configuring the entity unit to be configured into a leaf entity unit; and adding 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.
In 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 further includes: verifying the attribute data to be configured by using an attribute data verification rule corresponding to the attribute type to be configured; and under the condition that the verification is passed, judging whether the entity unit to be configured belongs to a leaf entity unit.
In other embodiments of the method provided in this specification, the 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 does not exist in the entity attribute data set, adding the entity unit to be configured, the attribute type to be configured and an attribute data item in the entity attribute data set; and 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.
In other embodiments of the method provided in this specification, the 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: and 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, updating the attribute data of the entity unit to be configured under the attribute type to be configured into the attribute data to be configured.
On the other hand, an embodiment of the present specification further provides an entity attribute data configuration apparatus, which is applied to a server, and the apparatus includes: a configuration request receiving module, configured to receive an entity attribute data configuration request sent by a user terminal; the entity attribute configuration request comprises an entity unit to be configured, and an attribute type to be configured and attribute data to be configured which correspond to the entity unit to be configured; the attribute data configuration module is used for 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 under the condition that the entity unit to be configured belongs to the leaf entity unit by utilizing the preset entity unit incidence relation; wherein the entity unit incidence relation comprises an incidence relation between entity units; the incidence relation comprises an inheritance relation and a parity relation; the inheritance relationship refers to that the entity unit of the associated party inherits the attribute data of the entity unit of the associated party; the same-position relation represents that the entity unit of the related party and the entity unit of the related party are the same entity unit; the leaf entity unit refers to the entity unit corresponding to the same position relationship.
In other embodiments of the apparatus provided in this specification, the apparatus further includes an association configuration module; the incidence relation configuration module is used for deleting the incidence relation between the entity unit to be configured and the corresponding associated entity unit in the entity incidence relation configured in advance under the condition that the entity unit to be configured does not belong to the leaf entity unit; configuring the entity unit to be configured into a leaf entity unit; the attribute data configuration module is further configured to add the attribute data to be configured to an entity attribute data set based on the entity unit to be configured and the attribute type to be configured.
In other embodiments of the apparatus provided herein, the apparatus further comprises: the verification module is used for verifying the attribute data to be configured by using an attribute data verification rule corresponding to the attribute type to be configured; and the judging module is used for judging whether the entity unit to be configured belongs to the leaf entity unit or not under the condition that the verification is passed.
In another aspect, this specification further provides a server including at least one processor and a memory for storing processor-executable instructions, where the instructions, when executed by the processor, implement the steps of the method according to any one or more of the foregoing embodiments.
According to the entity attribute data query and configuration method, the entity attribute data query and configuration device and the server provided by one or more embodiments of the present specification, only some entity units are used as leaf entity units to store and maintain attribute data, and other entity units establish an association relationship of the entity units when storing the entity attribute data in a manner of inheriting the attribute data corresponding to the leaf entity units, so that the attribute data of all entity units can be stored based on the association relationship and the attribute data of the leaf entity units. When the attribute data is inquired and maintained, only the attribute data of the leaf entity unit is required to be maintained, and for the non-leaf entity unit, the attribute data of the corresponding leaf entity unit can be called in an entity unit conversion mode to inquire the attribute data. Therefore, the storage scale of the entity attribute data is greatly reduced, the maintenance amount of the entity attribute data is further reduced, and the query efficiency is improved.
Drawings
In order to more clearly illustrate the embodiments of the present specification or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present specification, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort. In the drawings:
FIG. 1 is a schematic diagram of associations between entity units in some embodiments provided herein;
FIG. 2 is a schematic diagram illustrating associations between entity units in further embodiments provided herein;
FIG. 3 is a schematic diagram of an attribute data storage manner of an entity unit in some embodiments provided herein;
FIG. 4 is a schematic diagram illustrating a general storage manner of attribute data of entity units in some embodiments provided herein;
FIG. 5 is a flowchart illustrating an embodiment of a method for querying entity attribute data provided in the present specification;
FIG. 6 is a schematic representation of an entity attribute data query flow in some embodiments provided herein;
FIG. 7 is a flowchart illustrating an embodiment of a method for configuring entity attribute data provided in the present specification;
FIG. 8 is a schematic illustration of entity attribute data configuration flow in some embodiments provided herein;
FIG. 9 is a schematic diagram of attribute data update of entity units in some embodiments provided herein;
FIG. 10 is a schematic representation of attribute data updates for entity units in further embodiments provided herein;
FIG. 11 is a schematic diagram illustrating a general update of attribute data of entity units in some embodiments provided herein;
fig. 12 is a schematic block diagram of an entity attribute data query device provided in this specification;
FIG. 13 is a block diagram of an entity attribute data configuration apparatus provided in the present specification;
fig. 14 is a schematic structural diagram of functional modules of a server provided in this specification.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in the present specification, the technical solutions in one or more embodiments of the present specification will be clearly and completely described below with reference to the drawings in one or more embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the specification, and not all embodiments. All other embodiments obtained by a person skilled in the art based on one or more embodiments of the present specification without making any creative effort shall fall within the protection scope of the embodiments of the present specification.
An example of an application scenario in the present specification provides an entity attribute data maintenance and query method, which may be applied to a server. The server can be used for executing configuration, storage and query of entity association relation, and also can be used for executing configuration, storage and query of entity attribute data. The server may be one server or a server cluster composed of a plurality of servers.
In the embodiments of the present specification, an entity unit may refer to a specific element value corresponding to an entity. The entity may refer to a generic name of a class of elements that are pre-configured. For example, for a bank, the organization, personnel, network points, etc. of the bank may each be one entity. And specific branches, persons and network points can be used as entity units under corresponding entities. For example, a person is an entity, and an employee XX under the bank is an entity unit. The specific entities and entity units under the entities may be configured according to an actual scene, which is not limited herein.
Different attribute types may correspond to different entities. For example, an organization may correspond to entity attribute types such as a business calendar, assets, and transaction authorization, and a person may correspond to entity attribute types such as a qualification, a tag, and a department to which the person belongs. And the attribute data under the corresponding attribute type can be corresponded to a certain branch office and a certain staff. For example, the asset attribute of the branch office, XX branch office corresponds to the asset amount, and accordingly, the asset amount is the attribute data of XX branch office under the asset attribute.
In some embodiments, the association relationship corresponding to the entity unit when storing the attribute data may be configured in advance. The association relationship may comprise an inheritance relationship. The inheritance relationship can mean that the associated entity unit inherits the attribute data of the associated entity unit. The related entity unit represents an entity unit which takes attribute data of other entity units as attribute data of the entity unit. The associated entity unit represents an entity unit referred to by the associated entity unit at the time of attribute data storage.
Fig. 1 and fig. 2 are schematic diagrams illustrating association relationships corresponding to entity units when storing attribute data. As shown in FIG. 1, e1And e2Are in inheritance relationship, wherein e1Is an associated entity unit, e2Is an entity unit of an association party. The inheritance relationship indicates that the association entity unit completely inherits the attribute data of the associated entity unit and keeps consistent with the association entity unit. The related entity unit can only continue the attribute data of one related entity unit and can not inherit a plurality of related entity units. And the associated entity unit may correspond to a plurality of associated entity units, i.e. the attribute data thereof may be inherited by the plurality of associated entity units.
As shown in FIG. 1, a plurality of entity units can all inherit a certain entity unit e1And e is1No further entity elements are inherited, then e can be assigned1Are leaf entity units. The leaf entity unit can be based on the realityOne or more application scenes correspond to, as shown in FIG. 2, the upper layer has no inheritance relationship e1And e2Are all leaf entity units. Accordingly, the entity unit having the inherited associated entity unit may no longer correspond as a leaf entity unit.
In some embodiments, the association relationship may further include a co-location relationship. The co-located relationship may indicate that the associated entity unit and the associated entity unit are the same entity unit. Accordingly, the entity units corresponding to the same-position relationship can be used as leaf entity units. By further configuring the homothetic relationship, the leaf sub-entity units can be determined more simply.
The association relationship between the entity units can be combed in advance, which entity unit is used as an association entity unit, and which entity unit is used as an associated entity unit can be configured according to an actual application scene. In some embodiments, the Association between Entity units may be stored by an Entity Association table (Entity _ Association). Table 1 shows an entity association table storage field description table.
TABLE 1
As described in table 1 above, the association relationship of each entity unit may be stored in the entity association relationship table in advance, and may be represented by different Attr _ types for different entity attribute types. For different entities, different entity association relation tables can be correspondingly configured. Correspondingly, if a certain incidence relation is applied to all entity attribute types of a certain entity, the entity attribute type item can directly select default. In other embodiments, different entity association tables may be configured for different entity attribute types, so as to facilitate storage and query.
As shown in Table 1, the association relationship can be configured as an inheritance relationship and a co-location relationship. Wherein the inheritance relationship indicates that the Related _ Entity completely inherits the attribute data of the Be _ Related _ Entity and keeps consistent with the attribute data. The Related _ Entity cannot inherit a plurality of Be _ Related _ entities.
The parity indicates that the Related _ Entity is the same as Be _ Related _ Entity. At this time, the Entity unit corresponding to the parity relationship can be used as a Leaf Entity unit (Leaf-eu (Leaf Entity unit)).
In other embodiments, the association relationship may also be characterized by a relationship model. As shown in fig. 1 and fig. 2, a relationship direction identifier and/or a text identifier may be used to represent what kind of association relationship two entity units correspond to under what kind of attribute. In some embodiments, different relationship models may be configured for different entity attribute types, so as to quickly determine an association relationship between entity units in a certain entity attribute type, and improve the convenience of attribute data maintenance and query efficiency.
After the association relationship of the entity unit is configured, the storage configuration of the attribute data can be performed based on the association relationship. The attribute data corresponding to the leaf entity unit and the leaf entity unit may be stored in an associated manner, and the attribute data corresponding to the other entity units are no longer stored in the other entity units. Accordingly, the attribute data of other entity units than the leaf entity units can be determined by the association relationship of the entity units and the stored attribute data of the leaf entity units.
The attribute data of the leaf entity unit may be stored into an attribute data set, and the leaf entity unit, the attribute type, and the attribute data may be associated. In some embodiments, the attribute data of the leaf entity unit may be stored in the form of a data table. Of course, other storage manners may be used, and are not limited herein. In some embodiments, the attribute data set corresponding to each entity may be configured separately, or further subdivided, and the attribute data set corresponding to each entity attribute type may be configured.
FIG. 3 shows attribute data for leaf entity elementsStorage modes and storage modes of other entity units except leaf units. As shown in FIG. 3, EntityAttr (E, A) (the attribute data set for entity E under attribute type A) has E stored therein1、e2… … Attribute data under Attribute type A, Table under EntityAttr (E, A) is an Entity _ Association collection. As shown in FIG. 3, the Entity _ Association stores e3And e1、e10And e2、ekAnd e10The inheritance relationship of (2) then represents ek、e10And e2Corresponding attribute data under attribute type A are the same, e3And e1The corresponding attribute data under the attribute type A are the same. Accordingly, there is no need to store E in EntityAttr (E, A)k、e10、e3The attribute data of (1).
It is now common to employ the form of entity attribute storage as shown in figure 4. Wherein,
entity (E) represents a collection of m entity units (m specific organizations) of entity E (organization);
Entity(E)＝{e1,e2,…，em}；
attr (A) represents the collection of n attribute entries for entity attribute A;
Attr(A)＝{a1,a2,…，an}；
EntityAttr (E, A) represents the collection of A attributes for entity E;
EntityAttr(E,A)＝{e1a1,e1a2,…，eman}；
EntityAtttrData (e, A) represents the value of entity attribute A for entity element e;
EntityAttrData(e,A)＝ea＝{ea1,ea2,…,ean}；
for example, if an attribute data of an entity unit is calculated as a minimum storage unit, the storage size thereof may be quantized to Scale. Suppose that:
scale (E) represents the size of entity E;
scale (A) represents the size of the attribute type A;
scale (E, A) represents the Scale of the attribute type A of the entity E;
then:
scale (E) ═ m, which is the number of entity units of entity E;
scale (a) ═ n, which is the number of attribute data of the attribute type a;
Scale(E,A)＝m×n；
assuming that a financial institution B has x entities, each entity has m entity units and y attribute types, and each attribute type has n attribute data, it can be inferred that the entity attribute data storage size of the financial institution B is:
for the financial institution, the value is generally x > -5, y > -5, m > -50000, n > -300;
then: scale (b) > 3.75 billion.
It can be seen that the storage scale of the attribute data of the financial institution is often over 22.5 hundred million, and the space occupied by one attribute data is also large, thereby consuming a large storage cost. Meanwhile, the large amount of stored data also results in low efficiency of reading attribute data.
By using the scheme provided by the embodiment of the specification:
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 indicates the number of fields of Entity _ Association, and i indicates the number of leaf Entity units);
the difference D is Scale (E, A) -Scale (E, A) (NEW)
＝m(n-4)–i×n
When n > >4 (generally, the number of entity attributes is much larger than 4), D ═ n (m-i).
In practical terms, in a large financial institution, the institution entity of the large financial institution only includes one leaf entity unit, and in this case, i is 1. Corresponding to, m>>i，
That is to say an entityThe larger the scale, the larger D, the larger the storage scale that the inventive solution can reduce.
Therefore, in an application scenario with more entity units or attribute types, such as a large financial institution, if the attribute data is directly stored, a larger storage space is consumed. Through the scheme of the embodiment of the present specification, only the attribute data of the leaf entity unit needs to be stored, and only the association relationship of the entity unit needs to be stored for other entity units. The leaf entity units are relatively few, and the byte data occupied by the fields in the association relationship are also small, so that the storage space of the server can be greatly saved, and the storage cost is reduced.
Based on the scheme provided by the above embodiment, an embodiment of the present specification further provides an entity attribute data query method. In one embodiment, as shown in fig. 5, the method may be applied to a server. Accordingly, the method may comprise the steps of:
s50: receiving an entity attribute data query request; the entity attribute query request comprises an entity unit to be queried and an attribute type to be queried corresponding to the entity unit to be queried.
The server may receive an entity attribute data query request. The entity attribute data query request may be sent by a user terminal, or may be sent by a server of a service system. For example, if a service person wants to query the asset data of a branch office, an entity attribute data query request can be initiated through the user terminal of the service person. Or, when a certain service system processes a service, it needs to call certain entity attribute data, and it may also send an entity attribute data query request to a server that performs processing such as query of entity attribute data. Accordingly, a server that performs processing such as query of entity attribute data may receive an entity attribute data query request sent by a user terminal or a server of a service system.
The entity attribute query request may include an entity unit to be queried and a type of an attribute to be queried corresponding to the entity unit to be queried. For example, if a service person wants to query the asset quota data of a branch office, information such as the name or identifier of the branch office and information such as the name asset or identifier of the attribute type may be input in the query interface of the user terminal. Then, the user terminal can respond to the query instruction of the user, generate a query request based on the information input by the user, and send the query request to the server.
S52: determining a leaf entity unit corresponding to the entity unit to be inquired by utilizing a preset entity unit incidence relation; wherein the entity unit incidence relation comprises an incidence relation between entity units; the incidence relation comprises an inheritance relation and a parity relation; the inheritance relationship refers to that the entity unit of the associated party inherits the attribute data of the entity unit of the associated party; the same-position relation represents that the entity unit of the related party and the entity unit of the related party are the same entity unit; the leaf entity unit refers to the entity unit corresponding to the same position relationship.
After receiving the query request, the server may determine the leaf entity unit corresponding to the entity unit to be queried by using a pre-configured entity unit association relationship. The construction method and the storage method of the entity unit association relationship may refer to the above embodiments, which are not described herein again.
For example, assume that entity unit associations are stored by an entity association table. The leaf entity unit corresponding to the entity unit to be queried under the attribute type to be queried can be found from the entity association relation table in the server. As shown in FIG. 3, assume that the entity unit to be queried is ekIf the attribute type to be queried is a, the entity association relationship table in fig. 3 can be utilized to find out that the associated entity unit corresponding to the attribute type to be queried is e10，e10Associated entity unit of e2，e2Associated entity unit of e2. Then e can be determinedkCorresponding leaf entity unit e2。
If the entity unit association relationship is stored through the association relationship model shown in fig. 1 or fig. 2, the entity unit to be queried may also be located after finding the association relationship model corresponding to the attribute type to be queried, and then the leaf entity unit corresponding to the entity unit is found layer by layer through the association relationship description information in the model.
S54: and acquiring 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.
After determining the leaf entity unit, the server may obtain attribute data of the leaf entity unit corresponding to the entity unit to be queried in the attribute type to be queried, as the attribute data of the entity unit to be queried in the attribute type to be queried. As shown in fig. 3, assuming that the entity attribute data is stored through the entity attribute data table, the server may find the leaf entity unit e from the entity attribute data table2Attribute data under attribute type a. Can find e2Attribute data under Attribute type A as ekAttribute data under attribute type a.
The server finds e2After attribute data under attribute type A, it can be regarded as ekAnd sending the attribute data query result under the attribute type A to the user terminal so as to display the user terminal. Or, the attribute data may be sent to a server of the service system, so that the server performs subsequent processing based on the attribute data.
Referring to FIG. 6, in one example scenario, the query for attribute data may be performed in the following manner:
the user can input the entity unit E and the attribute type A of the required query through the user terminal, namely, the value of the attribute type A is queried for the entity unit E from EntityAttr (E, A).
The server can read the entity unit incidence relation and convert the input entity unit E into the entity unit E actually stored in Entityattr (E, A)k(ekAs a leaf entity unit).
Assuming that the entity conversion rule is represented by f (e), the conversion operation can be accomplished by:
the algorithm is used to represent:
wherein,
the server may then fetch E from EntityAttr (E, A)kAnd feeding back the attribute value to the user terminal for display.
Based on the scheme provided by the above embodiment, an embodiment of the present specification further provides an entity attribute data configuration method. In one embodiment, as shown in fig. 7, the method may be applied to a server. Accordingly, the method may comprise the steps of:
s70: receiving an entity attribute data configuration request sent by a user terminal; the entity attribute configuration request comprises an entity unit to be configured, and an attribute type to be configured and attribute data to be configured which correspond to the entity unit to be configured.
When the entity attribute data needs to be updated or added, related service personnel can send an entity attribute data configuration request to the server through the user terminal. For example, the user may input an entity unit to be updated or newly added, an attribute type of the corresponding entity unit, and attribute data through the user terminal. For convenience of description, the entity unit to be configured may be described by an entity unit to be updated or newly added, which is input by a user, the attribute type corresponding to the input may be described as the attribute type to be configured, and the input attribute data may be described as the attribute data to be configured. The user terminal responds to the relevant instruction of the user, and can generate an entity attribute data configuration request based on the information input by the user and send the entity attribute data configuration request to the server. Correspondingly, the server may receive the entity attribute data configuration request sent by the user terminal.
S72: under the condition that the entity unit to be configured belongs to a leaf entity unit is determined by using a pre-constructed entity unit incidence relation, 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; wherein the entity unit incidence relation comprises an incidence relation between entity units; the incidence relation comprises an inheritance relation and a parity relation; the inheritance relationship refers to that the entity unit of the associated party inherits the attribute data of the entity unit of the associated party; the same-position relation represents that the entity unit of the related party and the entity unit of the related party are the same entity unit; the leaf entity unit refers to the entity unit corresponding to the same position relationship.
After receiving the entity attribute data configuration request sent by the user terminal, the server may determine whether the configuration entity unit belongs to the leaf entity unit by using a pre-configured entity unit association relationship. The construction and storage manner of the entity unit association relationship may be implemented with reference to the above embodiments, and details are not repeated here.
In some embodiments, before determining whether the configuration entity unit belongs to a leaf entity unit by using a preconfigured entity unit association relationship, the attribute data to be configured may be checked. The attribute data to be configured may be checked by using an attribute data check rule corresponding to the attribute type to be configured.
Entity attribute data generally has a certain rule range, so the data generally needs to meet the relevant requirements of the attribute data and is allowed to be recorded into a server so as to ensure the accuracy of the recorded data. For example, the gender must be male, female; age must be a positive integer; the date must be the actual legal date, must be greater than a certain date; the post number must be a true post; the identification number must be an 18 digit number, and so on. The attribute data of different attribute types usually have different corresponding related requirements, and the corresponding check rule can be configured for each attribute type in advance, and then the attribute data to be configured can be checked by using the check rule corresponding to each attribute type to judge whether the attribute data meets the preset rule or not, and the data which does not meet the preset rule can be refused to be maintained. For example, the server may feed back prompt information that the data meets the requirements to the user terminal.
Under the condition that the attribute data to be configured meet the preset verification rule, the server can determine whether the entity unit to be configured belongs to the leaf entity unit or not by using the entity unit incidence relation configured in advance. For example, if the entity unit association relationship is stored through the entity association relationship table, the server may query, from the entity association relationship table, that the entity unit to be configured has a corresponding association relationship of a same-position relationship under the attribute type to be configured, and if so, may determine that the entity unit to be configured belongs to the leaf entity unit; otherwise, it is determined that it does not belong to a leaf entity unit.
In a case that 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 an entity attribute data set to which the entity unit to be configured belongs.
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 can be updated to the attribute data to be configured, that is, the original attribute data is updated to the attribute data to be configured.
If the entity attribute data set does not already have corresponding attribute data, the entity unit to be configured, the attribute type to be configured and the attribute data item can be added in the entity attribute data set. For example, a row of entity units to be configured, attribute types to be configured, and attribute data items are added to the entity attribute data table. Then, the attribute data to be configured may be populated into the attribute data item based on the entity unit to be configured and the attribute type to be configured. And completing the addition of the attribute data.
When the attribute data of a certain non-leaf entity unit is maintained again, the user can also input the attribute data of the entity unit which needs to be maintained again through the user terminal. Accordingly, the server may determine that the received entity unit to be configured does not belong to the leaf entity unit based on the pre-configured entity unit association relationship. At this time, the server may delete the association relationship between the entity unit to be configured and the associated entity unit corresponding thereto in the pre-configured entity association relationship, and configure the entity unit to be configured as the leaf entity unit. Therefore, the updating of the entity unit incidence relation is realized.
Then, the attribute data to be configured may 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 may be added to the entity attribute data table. Then, the attribute data to be configured may be populated into the attribute data item based on the entity unit to be configured and the attribute type to be configured. And completing the conversion of the association relation and the addition of the attribute data.
If the entity unit is a newly added entity unit node and the entity unit stores the attribute data in an inheritance way, the newly added attribute data is not needed, and the association relationship of the entity unit can be directly updated. If a row is added to the entity unit association relationship table and the attribute type, the association entity unit, the associated entity unit and the association relationship thereof are configured, the updating of the attribute data of the entity unit can be completed. By the method, the simplicity and the efficiency of attribute data maintenance can be greatly improved.
In one example scenario, referring to FIG. 8, entity attribute data may be configured in the following manner:
8.1: the user can input the entity unit e and the value ea of the attribute type A of the entity unit e through the user terminal.
8.2: and checking whether the ea meets the checking rule of A.
8.3: if the verification rule is not satisfied, returning a result which is not satisfied;
8.4: if the verification rule is satisfied, it indicates that ea is the legal data of the entity unit e;
8.5: whether e is a leaf entity unit can be judged;
8.5.1: if so, ea is maintained into EntityAttr (E, A). As shown in FIG. 9, FIG. 9 shows4The attribute data of (2) is updated into EntityAttr (E, A).
8.5.2: if not, entity element E is adjusted to be a leaf entity element, and then ea is maintained into EntityAttr (E, A). As shown in FIG. 10, e3And e1Deleting e3Adding the attribute data of (a) to EntityAttr (E, A), completing the pair E3Adjustment of the attribute data of (1).
Then, the server can feed back the configuration result to the user terminal so as to display the user terminal.
As shown in FIG. 11, the general scheme is adopted if e is to be modified3And the attribute values of the units of the entities under the jurisdiction thereof need to be respectively and independently modified3And its subordinate e5、e6Waiting for all jurisdictional entity units and modifying e if necessary1And the attribute value of the unit of the entity under jurisdiction needs to be modified1、e2、e3、e5、e6The entity attribute value of (1). Assuming that m entity units are to be modified, denoted by TS (e), then TS (e) m × (TS1(a) + TS2 (a)).
For entity attribute maintenance, at least the following 2 operation steps are included based on the above maintenance logic, entity attribute data checking S1, and entity attribute data storage S2.
Setting:
TS1(A) represents the average length of time required for attribute type A checking;
TS2(a) indicates the average length of time required for attribute type a storage;
then:
the duration of maintaining the attribute value of the attribute type A once for each entity unit of the entity E is as follows:
TS(E,A)＝m×(TS1(A)+TS2(A))
if the maintenance duration of each attribute of each entity is the same, the maintenance duration of the attributes of the whole entity is as follows:
suppose that: x > 5, y > 5, m > 50000, TS1(a) TS2(a) 50ms
Then: ts (b) > < 125000 s.
Therefore, by adopting the common scheme, the time cost for maintaining the entity attribute data of the large financial institution is huge, and the maintenance efficiency is very low.
However, the solution using the embodiments of the present specification, as shown in FIG. 11, is not limited to the modification e3And whether it governs e1And its subordinate, only need to modify e3The entity attribute value of (2) is sufficient.
TS(e)(NEW)＝1×(TS1(A)+TS2(A))
The difference D ═ TS (e) -TS (e) (NEW)
＝(m-1)×(TS1(A)+TS2(A))
If the entity attribute values of all entities are maintained at once, the time difference D is 5000 s. Therefore, the maintenance efficiency is greatly improved by the scheme of the invention.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. For details, reference may be made to the description of the related embodiments of the related processing, and details are not repeated herein.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
One or more embodiments of the present specification provide a testing method for a distributed system, which constructs a message producer simulating sending a message to a message middleware and a message consumer calling a message from the message middleware for message consumption by extending a stress testing tool of a business system. Then, the expanded testing tool can be used for producing message data to the message middleware and calling the message data from the message middleware for consumption, so that the testing of the processing performance of the message middleware is realized simply and conveniently. Meanwhile, by the mode, only the processing framework of the producer and the consumer is simulated simply, and the test environment of all the producers and the consumers is not required to be established, so that the investment of test resources is further saved, and the overall test cost of the distributed asynchronous message processing system is reduced. In addition, by utilizing the mode, the test of the service system and the test of the message middleware can be effectively associated, and the production message, the consumption message and the common transaction are arranged into a test scene together, so that the association of each link of the distributed asynchronous message processing is stronger, the flexibility, the comprehensiveness and the effectiveness of the test are further improved, the whole system and each link can be accurately and effectively known and mastered, and the operation of an online system is more stable.
Based on the entity attribute data query method, one or more embodiments of the present specification further provide an entity attribute data query device. Fig. 12 is a schematic block diagram illustrating an embodiment of an entity attribute data query apparatus provided in the specification, applied to a server, where as shown in fig. 12, the apparatus may include:
a query request receiving module 120, which may be configured to receive an entity attribute data query request; the entity attribute query request comprises an entity unit to be queried and an attribute type to be queried corresponding to the entity unit to be queried;
the entity unit conversion module 122 may be configured to determine, by using a pre-configured entity unit association relationship, a leaf entity unit corresponding to the entity unit to be queried; wherein the entity unit incidence relation comprises an incidence relation between entity units; the incidence relation comprises an inheritance relation and a parity relation; the inheritance relationship refers to that the entity unit of the associated party inherits the attribute data of the entity unit of the associated party; the same-position relation represents that the entity unit of the related party and the entity unit of the related party are the same entity unit; the leaf entity unit refers to the entity unit corresponding to the same position relation;
the attribute data query module 124 may be configured to obtain attribute data of the leaf entity unit corresponding to the entity unit to be queried in the attribute type to be queried, as the attribute data of the entity unit to be queried in the attribute type to be queried.
It should be noted that the above-described apparatus may also include other embodiments according to the description of the method embodiment. The specific implementation manner may refer to the description of the related method embodiment, and is not described in detail herein.
Based on the above entity attribute data configuration method, one or more embodiments of the present specification further provide an entity attribute data configuration device. Fig. 13 is a schematic block diagram illustrating an embodiment of an entity attribute data configuration apparatus provided in the specification, applied to a server, where as shown in fig. 13, the apparatus may include:
a configuration request receiving module 130, configured to receive an entity attribute data configuration request sent by a user terminal; the entity attribute configuration request comprises an entity unit to be configured, and an attribute type to be configured and attribute data to be configured which correspond to the entity unit to be configured;
the attribute data configuration module 132 may be configured to configure, when it is determined that the entity unit to be configured belongs to the leaf entity unit by using a preconfigured entity unit association relationship, 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; wherein the entity unit incidence relation comprises an incidence relation between entity units; the incidence relation comprises an inheritance relation and a parity relation; the inheritance relationship refers to that the entity unit of the associated party inherits the attribute data of the entity unit of the associated party; the same-position relation represents that the entity unit of the related party and the entity unit of the related party are the same entity unit; the leaf entity unit refers to the entity unit corresponding to the same position relationship.
In other embodiments, as shown in fig. 13, the apparatus may further include an association configuration module 134. Wherein,
the association relationship configuration module 134 may be configured to delete an association relationship between the entity unit to be configured and the associated entity unit corresponding to the entity unit to be configured in the pre-configured entity association relationship, if it is determined that the entity unit to be configured does not belong to the leaf entity unit; and configuring the entity unit to be configured into a leaf entity unit.
The attribute data configuration module 132 may be further configured to add the attribute data to be configured to an entity attribute data set based on the entity unit to be configured and the attribute type to be configured.
As shown in fig. 13, in other embodiments, the apparatus may further include:
the checking module 136 may be configured to perform checking processing on the attribute data to be configured by using an attribute data checking rule corresponding to the attribute type to be configured.
The determining module 138 may be configured to determine whether the entity unit to be configured belongs to a leaf entity unit if the check passes.
It should be noted that the above-described apparatus may also include other embodiments according to the description of the method embodiment. The specific implementation manner may refer to the description of the related method embodiment, and is not described in detail herein.
The method or apparatus provided by the present specification and described in the foregoing embodiments may implement service logic through a computer program and record the service logic on a storage medium, where the storage medium may be read and executed by a computer, so as to implement the effect of the solution described in the embodiments of the present specification. Accordingly, the present specification also provides a server which may comprise a processor and a memory storing processor-executable instructions which, when executed by the processor, implement steps comprising the method of any one of the above embodiments.
Based on the solution of the above embodiment, in one scenario example, the server may include the functional module shown in fig. 14. Wherein,
the entity attribute data input and output display module is mainly used for realizing the display of the input and output of the entity attribute data. The method specifically comprises query condition input display, maintained entity attribute data input display, query result output display, maintenance result output display and the like. The output display module can be sent to the user terminal by the server when the attribute data is inquired or maintained, so that the user terminal can display the input and output interface to the user by analyzing the function module. Or, the data can be packaged and sent to the user terminal in advance, so that the user terminal can carry out local installation to realize input and output display of the data.
And the entity attribute data checking module checks the input entity attribute data, judges whether the input entity attribute data accords with a preset rule or not, and refuses to maintain the data which does not accord with the preset rule.
The entity attribute data storage module is used for persistent data storage.
The entity conversion module is used for converting an entity E to be inquired and maintained into an entity unit E physically stored in an entity attribute table Entityattr (E, A)k. The specific implementation process is described in the above embodiments.
The entity attribute processing module mainly realizes the following functions:
and inquiring entity attribute data:
EntityAttr queryEntityAttrData(EntityAttrType EntityAttr(E,A),Entity e)；
inputting an entity unit E and an entity attribute type EntityAttr (E, A);
outputting the attribute value ea of the entity unit E in EntityAttr (E, A);
the functions are as follows: the attribute value ea of entity E is queried in EntityAttr (E, A).
Maintaining entity attribute data:
Int modifyEntityAttrData(EntityAttrType EntityAttr(E,A),Entity e,EntityAttr ea)；
inputting an entity unit E, an entity attribute type EntityAttr (E, A) and an attribute value ea of the entity unit E in the EntityAttr (E, A);
outputting a maintenance result identifier;
the functions are as follows: the attribute value ea of entity E is maintained in EntityAttr (E, A);
the key logic is as follows: if E already has an attribute value in the entityAttr (E, A), then the ea is used for overwriting, and if not, the ea is directly added in the entityAttr (E, A).
Querying entity relationships:
EntityAssociation queryEntityAssociation(EntityAttrType EntityAttr(E,A),Entity e)；
inputting an entity unit E and an entity attribute type EntityAttr (E, A);
outputting the entity relationship type of the entity unit E is the entity relationship of EntityAttr (E, A);
the functions are as follows: and querying the entity unit of which the entity relationship type of the entity unit E is EntityAttr (E, A).
Maintaining entity relationships:
Int modifyEntityAssociation()；
the functions are as follows: entity relationships are maintained.
It should be noted that the above description of the server according to the method embodiment may also include other embodiments. The specific implementation manner may refer to the description of the related method embodiment, and is not described in detail herein.
The embodiments of the present description are not limited to what must be consistent with a standard data model/template or described in the embodiments of the present description. Certain industry standards, or implementations modified slightly from those described using custom modes or examples, may also achieve the same, equivalent, or similar, or other, contemplated implementations of the above-described examples. The embodiments using these modified or transformed data acquisition, storage, judgment, processing, etc. may still fall within the scope of the alternative embodiments of the present description.
The storage medium may include a physical device for storing information, and typically, the information is digitized and then stored using an electrical, magnetic, or optical media. The storage medium may include: devices that store information using electrical energy, such as various types of memory, e.g., RAM, ROM, etc.; devices that store information using magnetic energy, such as hard disks, floppy disks, tapes, core memories, bubble memories, and usb disks; devices that store information optically, such as CDs or DVDs. Of course, there are other ways of storing media that can be read, such as quantum memory, graphene memory, and so forth.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment. In the description of the specification, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the specification. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
The above description is only an example of the present specification, and is not intended to limit the present specification. Various modifications and alterations to this description will become apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification should be included in the scope of the claims of the present specification.
Claims (13)
1. An entity attribute data query method is applied to a server, and comprises the following steps:
receiving an entity attribute data query request; the entity attribute query request comprises 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 inquired by utilizing a preset entity unit incidence relation; wherein the entity unit incidence relation comprises an incidence relation between entity units; the incidence relation comprises an inheritance relation and a parity relation; the inheritance relationship refers to that the entity unit of the associated party inherits the attribute data of the entity unit of the associated party; the same-position relation represents that the entity unit of the related party and the entity unit of the related party are the same entity unit; the leaf entity unit refers to the entity unit corresponding to the same position relation;
and acquiring 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.
2. The method according to claim 1, wherein the determining the leaf entity unit corresponding to the entity unit to be queried by using a pre-configured entity unit association relationship comprises:
calling an entity unit incidence relation corresponding to the attribute type to be inquired;
and determining the leaf entity unit corresponding to the entity unit to be inquired by using the entity unit incidence relation corresponding to the attribute type to be inquired.
3. The method according to claim 1, wherein the obtaining attribute data of the leaf entity unit corresponding to the entity unit to be queried under the attribute type to be queried includes:
acquiring an entity attribute data set; the entity attribute data set comprises leaf entity units and attribute data of the leaf entity units under each entity attribute type;
and inquiring attribute data of the leaf entity unit corresponding to the entity unit to be inquired under the attribute type to be inquired from the entity attribute data set.
4. An entity attribute data query device, applied to a server, the device comprising:
the query request receiving module is used for receiving an entity attribute data query request; the entity attribute query request comprises an entity unit to be queried and an attribute type to be queried corresponding to the entity unit to be queried;
the entity unit conversion module is used for determining a leaf entity unit corresponding to the entity unit to be inquired by utilizing a preset entity unit incidence relation; wherein the entity unit incidence relation comprises an incidence relation between entity units; the incidence relation comprises an inheritance relation and a parity relation; the inheritance relationship refers to that the entity unit of the associated party inherits the attribute data of the entity unit of the associated party; the same-position relation represents that the entity unit of the related party and the entity unit of the related party are the same entity unit; the leaf entity unit refers to the entity unit corresponding to the same position relation;
and the attribute data query module is used for acquiring the attribute data of the leaf entity unit corresponding to the entity unit to be queried under the attribute type to be queried, and taking the attribute data as the attribute data of the entity unit to be queried under the attribute type to be queried.
5. An entity attribute data configuration method is applied to a server, and comprises the following steps:
receiving an entity attribute data configuration request sent by a user terminal; the entity attribute configuration request comprises an entity unit to be configured, and an attribute type to be configured and attribute data to be configured which correspond to the entity unit to be configured;
under the condition that the entity unit to be configured belongs to a leaf entity unit is determined by utilizing a pre-configured entity unit incidence relation, 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; wherein the entity unit incidence relation comprises an incidence relation between entity units; the incidence relation comprises an inheritance relation and a parity relation; the inheritance relationship refers to that the entity unit of the associated party inherits the attribute data of the entity unit of the associated party; the same-position relation represents that the entity unit of the related party and the entity unit of the related party are the same entity unit; the leaf entity unit refers to the entity unit corresponding to the same position relationship.
6. The method according to claim 5, wherein in case that 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 the associated entity unit corresponding thereto in the pre-configured entity association relationship; configuring the entity unit to be configured into a leaf entity unit;
and adding 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.
7. The method of claim 5, wherein before determining that the entity unit to be configured belongs to a leaf entity unit, the method further comprises:
verifying the attribute data to be configured by using an attribute data verification rule corresponding to the attribute type to be configured;
and under the condition that the verification is passed, judging whether the entity unit to be configured belongs to a leaf entity unit.
8. The method according to claim 5, wherein the 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 comprises:
when 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 an attribute data item in the entity attribute data set;
and 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.
9. The method according to claim 5, wherein the 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 comprises:
and 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, updating the attribute data of the entity unit to be configured under the attribute type to be configured into the attribute data to be configured.
10. An entity attribute data configuration device, applied to a server, the device comprising:
a configuration request receiving module, configured to receive an entity attribute data configuration request sent by a user terminal; the entity attribute configuration request comprises an entity unit to be configured, and an attribute type to be configured and attribute data to be configured which correspond to the entity unit to be configured;
the attribute data configuration module is used for 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 under the condition that the entity unit to be configured belongs to the leaf entity unit by utilizing the preset entity unit incidence relation; wherein the entity unit incidence relation comprises an incidence relation between entity units; the incidence relation comprises an inheritance relation and a parity relation; the inheritance relationship refers to that the entity unit of the associated party inherits the attribute data of the entity unit of the associated party; the same-position relation represents that the entity unit of the related party and the entity unit of the related party are the same entity unit; the leaf entity unit refers to the entity unit corresponding to the same position relationship.
11. The apparatus of claim 10, further comprising an association configuration module; wherein,
the incidence relation configuration module is used for deleting the incidence relation between the entity unit to be configured and the corresponding associated entity unit in the entity incidence relation configured in advance under the condition that the entity unit to be configured does not belong to the leaf entity unit; configuring the entity unit to be configured into a leaf entity unit;
the attribute data configuration module is further configured to add the attribute data to be configured to an entity attribute data set based on the entity unit to be configured and the attribute type to be configured.
12. The apparatus of claim 10, further comprising:
the verification module is used for verifying the attribute data to be configured by using an attribute data verification rule corresponding to the attribute type to be configured;
and the judging module is used for judging whether the entity unit to be configured belongs to the leaf entity unit or not under the condition that the verification is passed.
13. A server, characterized in that the server comprises at least one processor and a memory for storing processor-executable instructions, which when executed by the processor implement the steps of the method of any one of claims 1-3 or 5-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011044663.5A CN112115235A (en) | 2020-09-28 | 2020-09-28 | Entity attribute data query and configuration method, device and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011044663.5A CN112115235A (en) | 2020-09-28 | 2020-09-28 | Entity attribute data query and configuration method, device and server |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112115235A true CN112115235A (en) | 2020-12-22 |
Family
ID=73798614
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011044663.5A Pending CN112115235A (en) | 2020-09-28 | 2020-09-28 | Entity attribute data query and configuration method, device and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112115235A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114328937A (en) * | 2022-03-10 | 2022-04-12 | 中国医学科学院医学信息研究所 | Scientific research institution information processing method and device |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101350033A (en) * | 2008-09-05 | 2009-01-21 | 北京邮电大学 | Method and apparatus for switching OWL information into relation data base |
| US20120158757A1 (en) * | 2010-12-15 | 2012-06-21 | Microsoft Corporation | Inherited Entity Storage Model |
| CN102567932A (en) * | 2010-12-30 | 2012-07-11 | 北京亿阳信通软件研究院有限公司 | Method, device and system for managing comprehensive resources |
| CN105468605A (en) * | 2014-08-25 | 2016-04-06 | 济南中林信息科技有限公司 | Entity information map generation method and device |
| CN107766545A (en) * | 2017-10-31 | 2018-03-06 | 浪潮软件集团有限公司 | Scientific and technological data management method and device |
| CN110147421A (en) * | 2019-05-10 | 2019-08-20 | 腾讯科技（深圳）有限公司 | A kind of target entity link method, device, equipment and storage medium |
| CN110362551A (en) * | 2018-04-02 | 2019-10-22 | 阿里巴巴集团控股有限公司 | Building Method of Data Warehouse, device, equipment and storage medium |
-
2020
- 2020-09-28 CN CN202011044663.5A patent/CN112115235A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101350033A (en) * | 2008-09-05 | 2009-01-21 | 北京邮电大学 | Method and apparatus for switching OWL information into relation data base |
| US20120158757A1 (en) * | 2010-12-15 | 2012-06-21 | Microsoft Corporation | Inherited Entity Storage Model |
| CN102567932A (en) * | 2010-12-30 | 2012-07-11 | 北京亿阳信通软件研究院有限公司 | Method, device and system for managing comprehensive resources |
| CN105468605A (en) * | 2014-08-25 | 2016-04-06 | 济南中林信息科技有限公司 | Entity information map generation method and device |
| CN107766545A (en) * | 2017-10-31 | 2018-03-06 | 浪潮软件集团有限公司 | Scientific and technological data management method and device |
| CN110362551A (en) * | 2018-04-02 | 2019-10-22 | 阿里巴巴集团控股有限公司 | Building Method of Data Warehouse, device, equipment and storage medium |
| CN110147421A (en) * | 2019-05-10 | 2019-08-20 | 腾讯科技（深圳）有限公司 | A kind of target entity link method, device, equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114328937A (en) * | 2022-03-10 | 2022-04-12 | 中国医学科学院医学信息研究所 | Scientific research institution information processing method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10977629B2 (en) | Computerized messaging module for blockchain networks | |
| CN111247550B (en) | Computerized transaction management module for blockchain networks | |
| CN110472207A (en) | List generation method and device | |
| US8291433B2 (en) | Unified, configurable services stack for integration of enterprise applications | |
| US10599985B2 (en) | Systems and methods for expediting rule-based data processing | |
| CN109034988A (en) | A kind of accounting entry generation method and device | |
| CN112651826B (en) | Credit line management and control system, method and readable storage medium | |
| Lytvyn et al. | Development of the system to integrate and generate content considering the cryptocurrent needs of users | |
| CN112464633A (en) | Template generation method and device, electronic equipment and storage medium | |
| US20180374047A1 (en) | Computing framework for compliance report generation | |
| CN109271564A (en) | Declaration form querying method and equipment | |
| CN105302556A (en) | Calculation realization method and system and server apparatus | |
| CN112115235A (en) | Entity attribute data query and configuration method, device and server | |
| CN114565443B (en) | Data processing method, data processing device, computer equipment and storage medium | |
| CN113779132B (en) | Data importing method, device, computer equipment and storage medium | |
| CN114331729A (en) | Data processing method and device of double-block chain architecture in data bank scene | |
| CN114693283A (en) | Cross-system business process approval processing method and device and computer equipment | |
| CN114298741A (en) | Quotation scheme determination method and device, electronic equipment and storage medium | |
| CN115017185A (en) | Data processing method, device and storage medium | |
| CN110096653A (en) | Construction method, device, equipment and the storage medium of space time information service architecture | |
| CN115952174B (en) | Data table connection method, system, terminal and storage medium | |
| CN116738960B (en) | Document data processing method, system, computer equipment and storage medium | |
| CN115408396B (en) | Method, device, computer equipment and storage medium for storing business data | |
| CN117114727A (en) | Method, device, computer equipment and storage medium for generating product model | |
| CN117493371A (en) | Service data processing method, device, computer equipment and storage medium |
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 |