CN117390034A - Data updating method, device, electronic equipment and computer readable storage medium - Google Patents
Data updating method, device, electronic equipment and computer readable storage medium Download PDFInfo
- Publication number
- CN117390034A CN117390034A CN202310955950.9A CN202310955950A CN117390034A CN 117390034 A CN117390034 A CN 117390034A CN 202310955950 A CN202310955950 A CN 202310955950A CN 117390034 A CN117390034 A CN 117390034A
- Authority
- CN
- China
- Prior art keywords
- attribute
- target
- entity
- value
- processed
- 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 50
- 238000012545 processing Methods 0.000 claims abstract description 54
- 230000008569 process Effects 0.000 claims description 8
- 238000004590 computer program Methods 0.000 claims description 5
- 238000012790 confirmation Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 4
- 230000014509 gene expression Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000012512 characterization method Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000010606 normalization Methods 0.000 description 2
- 230000009467 reduction Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
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/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2308—Concurrency control
- G06F16/2336—Pessimistic concurrency control approaches, e.g. locking or multiple versions without time stamps
- G06F16/2343—Locking methods, e.g. distributed locking or locking implementation details
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24564—Applying rules; Deductive queries
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)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a data updating method, a data updating device, electronic equipment and a computer readable storage medium, and relates to the technical field of data processing. A data updating method, comprising: acquiring a new attribute value of a target attribute of at least one dimension of an entity to be processed; the new attribute values of the target attributes of each dimension are respectively provided with priorities; judging the priority of the original attribute value of each target attribute in the entity to be processed and the priority of the new attribute value of the target attribute according to each target attribute in the entity to be processed; if the priority of the original attribute value of the target attribute in the entity to be processed is lower than the priority of the new attribute value of the target attribute, updating the value of the target attribute in the entity to be processed into the new attribute value of the target attribute; if the priority of the original attribute value of the target attribute in the entity to be processed is higher than the priority of the new attribute value of the target attribute, the value of the target attribute in the entity to be processed is kept to be the original attribute value of the target attribute.
Description
Technical Field
The present invention relates to the technical field of data processing, and in particular, to a data updating method, a data updating device, an electronic device, and a computer readable storage medium.
Background
Currently, when merging multi-source entity attributes, the old attributes of the entity are typically overridden with the newly obtained entity attributes. The data sources of the attributes of the same entity can be multiple, at present, the same credibility is adopted for all the attributes in the same data source, and the entity attributes with higher credibility are directly used for integrally covering the old attributes of the entity. The existing data updating mode is not accurate enough.
Disclosure of Invention
The application provides a data updating method, a device, electronic equipment and a computer readable storage medium, which are used for solving the problem that the existing data updating mode is inaccurate because the entity attribute with higher credibility is directly and integrally used for covering the old attribute of the entity in the prior art.
In a first aspect, the present application provides a data updating method, including: acquiring an original attribute value and a corresponding new attribute value of a target attribute of at least one dimension of an entity to be processed; the original attribute value and the new attribute value of the target attribute of each dimension are respectively provided with priority; if the priority of the original attribute value of the target attribute in the entity to be processed is lower than the priority of the new attribute value of the target attribute, updating the value of the target attribute in the entity to be processed into the new attribute value of the target attribute; and if the priority of the original attribute value of the target attribute in the entity to be processed is higher than the priority of the new attribute value of the target attribute, keeping the value of the target attribute in the entity to be processed as the original attribute value of the target attribute.
In this embodiment of the present invention, since the obtained new attribute value of each target attribute is set with a priority, and the original attribute value of each target attribute in the entity to be processed is also set with a priority, when data update is performed, the old attribute of the entity is not directly covered by the newly obtained entity attribute, but the original attribute value of the target attribute needs to be repaired or not can be determined by using the obtained priority of the new attribute value and the priority of the original attribute value for each target attribute. Compared with the prior art, the scheme can fully consider the credibility of each new attribute value obtained, and further can solve the problem that in the prior art, the old attribute of the entity is directly covered by the new entity attribute, so that the data updating mode is inaccurate.
With reference to the foregoing technical solution provided in the first aspect, in some possible implementation manners, the method further includes: and aiming at each target attribute in the entity to be processed, if the priority of the original attribute value of the target attribute in the entity to be processed is equal to the priority of the new attribute value of the target attribute, carrying out conflict processing according to a preset conflict processing strategy.
In the embodiment of the application, when the priorities of the new attribute value and the original attribute value of the target attribute are the same, conflict processing is performed according to a preset conflict processing strategy, so that the problem that the system cannot process due to the fact that the priorities of the new attribute value and the original attribute value of the target attribute are the same is solved.
With reference to the foregoing technical solution of the first aspect, in some possible implementation manners, the performing conflict processing according to a preset conflict processing policy includes: judging whether the original attribute value of the target attribute in the entity to be processed is the same as the new attribute value of the target attribute; if the original attribute value of the target attribute in the entity to be processed is the same as the new attribute value of the target attribute, keeping the value of the target attribute in the entity to be processed as the original attribute value of the target attribute, and setting the attribute state of the target attribute as effective representation; if the original attribute value of the target attribute in the entity to be processed is different from the new attribute value of the target attribute, keeping the value of the target attribute in the entity to be processed as the original attribute value of the target attribute, setting the attribute state of the target attribute as a representation conflict, and recording the new attribute value of the target attribute into a preset conflict list.
In the embodiment of the application, the attribute state is set for the target attribute, so that when the priority of the original attribute value of the target attribute is the same as the priority of the new attribute value of the target attribute and the original attribute value of the target attribute is different from the new attribute value of the target attribute, the attribute state can be set as conflict, and further, a worker can conveniently determine the target attribute needing manual intervention according to the attribute state. And the staff can also quickly acquire the new attribute value of the target attribute according to the preset conflict list, so that the processing efficiency of the staff can be improved.
With reference to the foregoing technical solution provided in the first aspect, in some possible implementation manners, the method further includes: and setting the attribute state of the target attribute in the entity to be processed as effective representation if the priority of the original attribute value of the target attribute in the entity to be processed is lower than the priority of the new attribute value of the target attribute aiming at each target attribute in the entity to be processed.
In the embodiment of the present invention, when the priority of the original attribute value of the target attribute in the entity to be processed is lower than the priority of the new attribute value of the target attribute, the value of the target attribute in the entity to be processed is updated to the new attribute value of the target attribute, so that the updated value of the target attribute will not necessarily collide, and therefore, the attribute state of the target attribute in the entity to be processed is set to be effective for characterization, so that the entity to be processed needs to be used can be accurately known about the attribute that can be directly used in the entity to be processed.
With reference to the foregoing technical solution provided in the first aspect, in some possible implementation manners, the method further includes: under the condition that the value of the target attribute in the entity to be processed is updated to be a new attribute value of the target attribute, recording the updating time of the target attribute; and if the update time of the target attribute and the duration of the current time interval exceed the preset duration threshold, reducing the priority of the new attribute value of the target attribute.
In this embodiment of the present application, if the priority of the original attribute value of the target attribute of the entity to be processed is higher, the value of the target attribute may be unchanged all the time in a longer time. The longer the time kept unchanged, the lower the reliability of the value of the target attribute, so that the time for setting the target attribute to be updated as the original attribute value exceeds the preset time threshold, the priority of the original attribute value of the target attribute is reduced, and the problem of reliability reduction caused by the fact that the original attribute value of the target attribute cannot be updated for a long time can be effectively prevented.
With reference to the foregoing technical solution provided in the first aspect, in some possible implementation manners, the method further includes: acquiring a missing attribute of the entity to be processed and a new attribute value corresponding to the missing attribute, wherein the missing attribute is an attribute which does not exist in the entity to be processed; wherein the missing attribute is an attribute that does not exist in the entity to be processed; and adding the missing attribute in the entity to be processed, and setting a new attribute value of the missing attribute as an original attribute value of the missing attribute.
According to the embodiment of the application, the entity to be processed can be perfected according to the acquired missing attribute and the new attribute value corresponding to the missing attribute, so that the data of the entity to be processed can be more comprehensive.
With reference to the foregoing technical solution provided by the first aspect, in some possible implementation manners, a process for obtaining a new attribute value of a target attribute of at least one dimension of the entity to be processed includes: acquiring initial attributes of at least one dimension of the entity to be processed and initial attribute values of each initial attribute from a target data source; carrying out standardized processing on the obtained attribute names of all the initial attributes to obtain the attribute names of the target attributes of at least one dimension of the entity to be processed; and carrying out standardization processing on the initial attribute value of each initial attribute to obtain a new attribute value of the target attribute of at least one dimension of the entity to be processed.
In the embodiment of the application, the obtained attribute names of the initial attribute information are standardized, and the obtained initial attribute values are standardized, so that the new attribute value of the target attribute of at least one dimension of the entity to be processed, which is obtained after the processing, is ensured to be the same as the attribute name of the target attribute of each dimension in the entity to be processed, and the range of the new attribute value is the same, and further the subsequent updating process can be normally performed.
With reference to the foregoing technical solution provided by the first aspect, in some possible implementation manners, the target data source includes N, where N is a positive integer greater than or equal to 2, and the obtaining, from the target data source, an initial attribute of at least one dimension of the entity to be processed and an initial attribute value of each initial attribute includes:
for each dimension initial attribute in the initial attributes of the at least one dimension, acquiring M candidate initial attribute values and priorities of the initial attribute from the N target data sources; wherein M is a positive integer less than or equal to N;
and determining the candidate initial attribute value with the highest priority from the M candidate initial attribute values as the initial attribute value corresponding to the corresponding initial attribute.
In a second aspect, the present application provides a data updating apparatus, including: the system comprises an acquisition module, a judging module and a processing module, wherein the acquisition module is used for acquiring an original attribute value and a corresponding new attribute value of a target attribute of at least one dimension of an entity to be processed; the original attribute value and the new attribute value of the target attribute of each dimension are respectively provided with priority; the processing module is used for updating the value of the target attribute in the entity to be processed into the new attribute value of the target attribute if the priority of the original attribute value of the target attribute in the entity to be processed is lower than the priority of the new attribute value of the target attribute; the processing module is further configured to keep the value of the target attribute in the entity to be processed as the original attribute value of the target attribute if the priority of the original attribute value of the target attribute in the entity to be processed is higher than the priority of the new attribute value of the target attribute.
In a third aspect, the present application provides an electronic device, comprising: the device comprises a memory and a processor, wherein the memory is connected with the processor; the memory is used for storing programs; the processor is configured to invoke a program stored in the memory, so as to execute the data updating method provided in the first aspect and/or in combination with any possible implementation manner of the first aspect.
In a fourth aspect, the present application provides a computer readable storage medium having stored thereon a computer program which, when executed by a computer, performs the data updating method of the first aspect and/or provided in connection with any possible implementation manner of the first aspect.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments will be briefly described below, it being understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered limiting the scope, and that other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flow chart of a data updating method according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a process for updating a to-be-processed entity with a new attribute value of a target attribute of at least one dimension of the to-be-processed entity according to an embodiment of the present application;
FIG. 3 is a block diagram illustrating a data updating apparatus according to an embodiment of the present application;
fig. 4 is a block diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures. Also, relational terms such as "first," "second," and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
The technical solutions of the present application will be described in detail below with reference to the accompanying drawings.
In the prior art, if the attribute of the target entity includes "phone number" and "age", the attribute values of "phone number" and "age" are derived from the telecommunication system. At this time, if the new attribute value of "age" and the new attribute value of "telephone number" of the target entity are acquired from the home registration system. Since the reliability of the "telephone number" obtained from the telecommunication system is higher than that of the "telephone number" obtained from the home registration system. Therefore, if the new attribute value of the "age" and the new attribute value of the "phone number" of the newly acquired target entity are directly used to cover the old attribute of the entity to be updated, the reliability of the "phone number" of the target entity may be reduced, so that the existing data updating mode is not accurate enough.
The application provides a data updating method for improving the accuracy of data updating.
Referring to fig. 1, fig. 1 is a schematic diagram illustrating a data updating method according to an embodiment of the present application, and the steps included in the method will be described with reference to fig. 1.
S100: and acquiring an original attribute value and a corresponding new attribute value of the target attribute of at least one dimension of the entity to be processed.
Where an entity generally refers to what can exist independently, as the basis for all attributes and everything primitive. The essence of an entity is that one independent individual, the core of which is the identification of an entity is to distinguish between individuals, and two different individuals cannot be considered as one, nor one individual as two different individuals. The entity may be physically present person, object, device, virtual software, account, etc., or a together event, a show.
The new attribute values of the target attributes for each dimension are respectively set with priorities.
Attributes of different dimensions refer to different types of attributes, e.g., attribute "name" and attribute "age" are attributes of different dimensions.
The attribute of the entity to be processed is information for describing the entity to be processed, for example, the attribute of the entity to be processed includes a "name" and an "age", and the attribute value of the "name" is the name of the entity to be processed, and the attribute value of the "age" is the age of the entity to be processed.
The original attribute value is the current attribute value of the target attribute of the entity to be processed, and the original attribute value can be obtained in advance and stored in a local storage medium; or may be obtained from other electronic devices when needed.
The new attribute value is the acquired attribute value of the target attribute of the entity to be processed. The new attribute values may be collected from a network or other electronic device.
The number of specific levels of the priorities may be set according to practical situations, and the total level of the priorities is a positive integer greater than or equal to 2. The specific level of priority may be represented by numerals or letters, for example, the priority is 1, 2, 3, 4, 5 in order from high to low, which is illustrated herein for ease of understanding only and should not be construed as limiting the present application.
Alternatively, the specific level of priority may be expressed in a text language or the like. For example, the priorities are "normal source, trusted source, manual confirmation" in order from low to high, that is, the priority of "manual confirmation" is the highest, and the priority of "normal source" is the lowest. The examples herein are for ease of understanding only and should not be construed as limiting the present application.
Alternatively, the priority of the new attribute value for the target attribute for each dimension may be determined based on the data source of the new attribute value. For example, the priority is "normal source, trusted source, manual confirmation" in order from low to high, and if the target attribute is a telephone number, the reliability of the telephone number acquired from the telecommunication system is high, so the priority of the telephone number acquired from the telecommunication system may be "trusted source", but the reliability of the user address acquired from the telecommunication system is low, so the priority of the user address acquired from the telecommunication system may be "normal source". The examples herein are for ease of understanding only and should not be construed as limiting the present application.
The attribute names representing the same attribute, the manner in which attribute values of the same attribute are expressed may be different due to different data sources. For example, in data source 1, the attribute name representing the attribute of the user name may be a "name", and the birth year of the user is represented in data source 1 by a full name of the province (e.g., sichuan, chongqing, etc.); in the data source 2, the attribute name representing the attribute of the user name may be "name", and the birth of the user is represented by a province abbreviation (e.g., chuan, choster, etc.) in the data source 2. It will be understood that "name" and "name" actually refer to the same attribute, and that the provincial holonomy scale and provincial acronym are used to represent the birth place of the user, except that the expressions of the two are different.
Thus, in order to facilitate the subsequent data update flow, in one embodiment, the specific step of obtaining a new attribute value of the target attribute of at least one dimension of the entity to be processed may be: acquiring initial attributes of at least one dimension of an entity to be processed and initial attribute values of each initial attribute from a target data source; carrying out standardized processing on the obtained attribute names of all the initial attributes to obtain the attribute names of the target attributes of at least one dimension of the entity to be processed; and carrying out standardization processing on the initial attribute value of each initial attribute to obtain a new attribute value of the target attribute of at least one dimension of the entity to be processed.
And carrying out standardization processing on the attribute names of all the acquired initial attributes, namely modifying the acquired attribute names of the initial attributes of at least one dimension into the same attribute names as the attribute names of the corresponding attributes in the entity to be processed. For example, if the attribute name of the initial attribute is "name" and the attribute name of the corresponding attribute in the entity to be processed is "name", the attribute name of the initial attribute is modified to "name". The examples herein are for ease of understanding only and should not be construed as limiting the present application.
The initial attribute is an unprocessed attribute directly acquired from the data source.
And carrying out standardization processing on the obtained initial attribute values (namely the attribute values of the initial attributes) of all the initial attributes, namely modifying the obtained expression mode of the initial attribute values of the initial attributes of at least one dimension into the same expression mode as the attribute values of the corresponding attributes in the entity to be processed. For example, if the initial attribute is the place of birth and the initial attribute value of the initial attribute is "Sichuan" and the expression of the corresponding attribute in the entity to be processed is provincial full scale, the initial attribute value of the initial attribute is modified to be "Sichuan". The examples herein are for ease of understanding only and should not be construed as limiting the present application.
Optionally, one implementation manner of performing standardization processing on the initial attribute value of each initial attribute may be to unify the data dictionaries corresponding to the acquired initial attribute value of the initial attribute and the original attribute value of the corresponding attribute in the entity to be processed, that is, map different enumeration values onto the consistent data dictionaries.
The specific implementation and working principle of the data dictionary are well known to those skilled in the art, and are not described herein for brevity.
Because the data types in different data sources may be different, in one embodiment, after the initial attribute of at least one dimension of the entity to be processed and the initial attribute value of each initial attribute are obtained from the target data source, the obtained initial attribute of at least one dimension and the initial attribute value of each initial attribute may be further converted into a specified data type.
In one embodiment, since the attributes acquired from the same data source may include attributes of a plurality of different entities, after performing normalization processing on attribute names of all acquired initial attributes and performing normalization processing on initial attribute values of each initial attribute, mapping the processed initial attribute of each dimension and the initial attribute value of each initial attribute into a preset standard template respectively to obtain a standard entity template including new attribute values of target attribute information of at least one dimension. Steps S200-S400 are then performed based on the new attribute values of the target attribute information for at least one dimension included in the standard entity template corresponding to the entity to be processed.
The standard entity template corresponding to the entity to be processed refers to a standard entity template of the same entity as the entity to be processed.
In one embodiment, if the target data source includes N, where N is a positive integer greater than or equal to 2, the specific process of obtaining the initial attribute of at least one dimension of the entity to be processed and the initial attribute value of each initial attribute from the target data source may be: firstly, for the initial attribute of each dimension in the initial attributes of at least one dimension, M candidate initial attribute values and priorities of the initial attribute are obtained from N target data sources; wherein M is a positive integer less than or equal to N; and then, determining the candidate initial attribute value with the highest priority from the M candidate initial attribute values as the initial attribute value corresponding to the corresponding initial attribute. For ease of understanding, the description will be given by taking as an example a target data source 1, a target data source 2, and a target data source 3.
If the initial attribute value of the attribute 1 and the initial attribute value of the attribute 2 are obtained from the target data source 1, the priority corresponding to the attribute 1 is a "trusted source", and the priority corresponding to the attribute 2 is a "normal source". The initial attribute value of the attribute 1 is obtained from the target data source 2, and the priority corresponding to the attribute 1 is "common source". The initial attribute value of the attribute 1 and the initial attribute value of the attribute 2 are obtained from the target data source 3, and the priority corresponding to the attribute 1 is "common source", and the priority corresponding to the attribute 2 is "trusted source".
Then for attribute 1, attribute 1 in target data source 1 is taken as the initial attribute of attribute 1 because attribute 1 in target data source 1 corresponds to the highest priority.
Correspondingly, carrying out standardized processing on the attribute names of the attribute 1 in the target data source 1 to obtain the attribute names of the target attribute 1 corresponding to the attribute 1 in the entity to be processed; and carrying out standardization processing on the initial attribute value of the attribute 1 in the target data source 1 to obtain a new attribute value of the target attribute 1 corresponding to the attribute 1 in the entity to be processed.
Similarly, for attribute 2, attribute 2 in target data source 2 is the initial attribute of attribute 2, since attribute 2 in target data source 3 corresponds to the highest priority.
Correspondingly, carrying out standardized processing on the attribute names of the attributes 2 in the target data source 3 to obtain the attribute names of the target attributes 2 corresponding to the attributes 2 in the entity to be processed; and carrying out standardization processing on the initial attribute value of the attribute 2 in the target data source 3 to obtain a new attribute value of the target attribute 2 corresponding to the attribute 2 in the entity to be processed.
The examples herein are for ease of understanding only and should not be construed as limiting the present application.
S200: if the priority of the original attribute value of the target attribute in the entity to be processed is lower than the priority of the new attribute value of the target attribute, updating the value of the target attribute in the entity to be processed into the new attribute value of the target attribute.
For example, when the priority level is "normal source, trusted source, and manual confirmation" in order from low to high, if the priority of the original attribute value of the target attribute is "normal source" and the priority of the new attribute value of the target attribute is "trusted source", the value of the target attribute in the entity to be processed is updated to the new attribute value of the target attribute. The examples herein are for ease of understanding only and should not be construed as limiting the present application.
In one embodiment, the data updating method further includes: in case of updating the value of the target attribute in the entity to be processed to a new attribute value of the target attribute, the update time of the target attribute is recorded. And if the update time of the target attribute and the duration of the current time interval exceed the preset duration threshold, reducing the priority of the new attribute value of the target attribute.
The preset duration threshold may be set according to practical situations, and specific values of the preset duration are not limited here.
Optionally, the preset duration threshold may include a plurality of preset duration thresholds, and the corresponding preset duration threshold may be determined according to the priority of the original attribute value.
For example, when the priority level is "normal source, trusted source, and manual confirmation" in order from low to high, the priority level may be set to be "normal source" corresponding to the first preset duration threshold, the priority level is "trusted source" corresponding to the second preset duration threshold, and the priority level is "manual confirmation" corresponding to the third preset duration threshold.
In this case, if the priority of the original attribute value of the target attribute is "manual confirmation", if the duration in which the target attribute is updated to the original attribute value exceeds the third preset duration threshold, the priority of the original attribute value of the target attribute is reduced. The examples herein are for ease of understanding only and should not be construed as limiting the present application.
Alternatively, the manner of each priority reduction may be set according to actual requirements, for example, the priority may be reduced one level at a time, or the priority may be reduced multiple levels at a time, where the specific manner of reducing the priority is not limited.
S300: if the priority of the original attribute value of the target attribute in the entity to be processed is higher than the priority of the new attribute value of the target attribute, the value of the target attribute in the entity to be processed is kept to be the original attribute value of the target attribute.
For example, when the priority level is "normal source, trusted source, and manual confirmation" in order from low to high, if the priority of the original attribute value of the target attribute is "trusted source" and the priority of the new attribute value of the target attribute is "normal source", the value of the target attribute in the entity to be processed is kept as the original attribute value of the target attribute. The examples herein are for ease of understanding only and should not be construed as limiting the present application.
In addition to both cases S300, S400, the priority of the original attribute value of the target attribute in the processing entity may also be equal to the priority of the new attribute value of the target attribute.
In this case, since the priorities are the same, the following embodiments are possible.
In a first embodiment, a value may be randomly selected from the original attribute value and the new attribute value of the target attribute as the value of the target attribute.
In a second embodiment, for each target attribute in the entity to be processed, if the priority of the original attribute value of the target attribute in the entity to be processed is equal to the priority of the new attribute value of the target attribute, performing conflict processing according to a preset conflict processing policy.
The specific manner of performing the conflict processing according to the preset conflict processing strategy may be: firstly, judging whether the original attribute value of the target attribute in the entity to be processed is the same as the new attribute value of the target attribute.
If the original attribute value of the target attribute in the entity to be processed is the same as the new attribute value of the target attribute, the value of the target attribute in the entity to be processed is kept to be the original attribute value of the target attribute, and the attribute state of the target attribute is set to be effective in characterization.
Optionally, if the target attribute has information such as data update time or a time length when the target attribute is updated to the original attribute value, the data update time of the target attribute is updated to the current time, or the time length when the target attribute is updated to the original attribute value is reset to 0.
If the original attribute value of the target attribute in the entity to be processed is different from the new attribute value of the target attribute, keeping the value of the target attribute in the entity to be processed as the original attribute value of the target attribute, setting the attribute state of the target attribute as a characterization conflict, and recording the new attribute value of the target attribute into a preset conflict list.
Optionally, if the original attribute value of the target attribute in the entity to be processed is different from the new attribute value of the target attribute, the value of the target attribute in the entity to be processed may be updated to be the new attribute value of the target attribute. And setting the attribute state of the target attribute as a characteristic conflict, and recording the original attribute value of the target attribute before being updated into a preset conflict list.
The specific implementation manner of updating the value of the target attribute to the new attribute value of the target attribute in the entity to be processed is the same as the foregoing manner, and is not described herein for brevity.
Or if the original attribute value of the target attribute in the entity to be processed is different from the new attribute value of the target attribute, the value of the target attribute in the entity to be processed can be updated to be a designated value (such as a null setting, etc.), the attribute state of the target attribute is set to be a representation conflict, and the original attribute value and the new attribute value of the target attribute are recorded in a preset conflict list.
In the case that the target attribute has an attribute state, in one embodiment, the data updating method further includes: and setting the attribute state of each target attribute in the entity to be processed as effective representation if the priority of the original attribute value of the target attribute in the entity to be processed is lower than the priority of the new attribute value of the target attribute aiming at each target attribute in the entity to be processed.
Under the condition that the priority of the original attribute value of the target attribute in the entity to be processed is lower than the priority of the new attribute value of the target attribute, the value of the target attribute in the entity to be processed is updated to be the new attribute value of the target attribute, so that the updated value of the target attribute is not necessarily conflicted, the attribute state of the target attribute in the entity to be processed is set to be effective in representation, and the entity to be processed is convenient to use, and the attribute which can be directly used in the entity to be processed can be accurately known.
Optionally, the data updating method further includes: for each target attribute in the entity to be processed, if the priority of the original attribute value of the target attribute in the entity to be processed is higher than the priority of the new attribute value of the target attribute, the attribute state of the target attribute in the entity to be processed is kept unchanged.
Optionally, in the case that the attribute value of the target attribute in the entity to be processed is null, the attribute state of the target attribute may be set to represent the missing.
Wherein, when the entity to be processed is just created, each attribute in the entity to be processed is empty, so that the attribute state of each attribute can be set to represent the missing.
In one embodiment, the data updating method further includes: and acquiring the new attribute value corresponding to the missing attribute of the entity to be processed. Adding the missing attribute in the entity to be processed, and setting the new attribute value of the missing attribute as the original attribute value of the missing attribute.
Wherein the missing attribute is an attribute that does not exist in the entity to be processed.
And perfecting the entity to be processed according to the acquired new attribute value of the target attribute of at least one dimension, so that the data of the entity to be processed can be more comprehensive.
For ease of understanding, the description will be given by taking the example that the entity to be processed includes attribute 1, attribute 2, and attribute 3. When the acquired new attribute value of the target attribute of at least one dimension of the entity to be processed includes the attribute 4 and the new attribute value 4 corresponding to the attribute 4, the attribute 4 is added to the entity to be processed because the entity to be processed does not include the attribute 4, and the value of the attribute 4 in the entity to be processed is set as the new attribute value 4. The examples herein are for ease of understanding only and should not be construed as limiting the present application.
To facilitate understanding of the foregoing data updating method, the description will be given by taking "normal, trusted, and manual" as an example, where the priority is from low to high, as shown in fig. 2.
And acquiring new attribute values of the attributes of the plurality of dimensions of the entity to be processed from the data source Agent1 on 1 month and 1 day to obtain the table 1.
And then establishing a to-be-processed entity to obtain all the attributes of the to-be-processed entity, and updating the to-be-processed entity by utilizing all the attributes and new attribute values corresponding to each attribute in the table 1 to obtain the table 2. Wherein the new attribute value of each attribute in table 1 is employed and the time of update and the priority of each new attribute value are recorded, as is the entity originally created.
New attribute values of attributes of multiple dimensions of the entity to be processed are obtained from the scanner on 1 month and 2 days, and table 3 is obtained.
As can be seen from the IP of table 3, the entity corresponding to the table 3 should be the entity corresponding to 10.25.21.102, and thus, table 2 is updated with each attribute and the new attribute value corresponding to each attribute included in table 3.
The original attribute value of the attribute service name in the entity to be updated (table 2) is Web, the state is effective, the priority is common, the priority of the newly arrived attribute service name in table 3 is common, and the new attribute value is HTTP. That is, the priority of the original attribute value and the new attribute value corresponding to the "service name" is the same, but the original attribute value and the new attribute value are different. Therefore, the attribute state of the "service name" is set as a conflict, the value of the "service name" in the entity to be updated is updated to "HTTP", and "HTTP", "Web" is recorded into the conflict value list, and the update recording time is 1 month and 2 days.
The original attribute value of the attribute operating system in the entity to be updated (table 2) is RedHat, the state is effective, and the priority is credible. The attribute "operating system" priority in the newly arrived table 3 is normal, and the new attribute value is Linux. Thus, the value of "operating system" in the entity to be processed is kept as the original attribute value of "operating system", and the attribute status, priority and update time are unchanged.
The original attribute value of the attribute "software name" in the entity to be updated (table 2) is nginnx, the state is effective, and the priority is common. The attribute "software name" priority in the newly arrived table 3 is normal, and the new attribute value is nginnx. Therefore, the value of the 'software name' in the entity to be processed is kept as the original attribute value of the 'software name', the attribute state and the priority are unchanged, and the update time is updated to be 1 month and 2 days.
The original attribute value of the attribute "software version" in the entity to be updated (table 2) is 1.21, the state is effective, and the priority is common. The attribute "software version" priority in the newly arrived table 3 is normal, and the new attribute value is 1.19. Therefore, the attribute status of "software version" is set as conflict, the value of "software version" in the entity to be updated is updated to "1.21", and "1.21", "1.19" is recorded into the conflict value list, and the update recording time is 1 month and 2 days.
The newly arrived attribute "open port" in table 3 has a trusted priority and a new attribute value of 443. Since the attribute does not exist in the entity to be updated (table 2), an attribute "open port" is newly added in the entity to be updated, the attribute value of the open port is set to 443, the attribute state is set to be effective, the update time is set to 1 month and 2 days, and the priority is set to be trusted.
To sum up, the updated entity to be updated, i.e. table 4, is obtained.
And acquiring new attribute values of the attributes of the plurality of dimensions of the entity to be processed from the Agent2 on 1 month and 3 days to obtain the table 5.
As can be seen from the IP of table 5, the entity corresponding to the table 5 should be the entity corresponding to 10.25.21.102, and thus the entity to be processed (table 4) is updated with each attribute and the new attribute value corresponding to each attribute included in table 5.
The original attribute value of the attribute service name in the entity to be updated (table 4) is HTTP, the state is effective, and the priority is common. The attribute "service name" priority in the newly arrived table 5 is trusted, and the new attribute value is OA. Therefore, the attribute value of the "service name" in the entity to be processed is set to OA, the attribute status is set to be effective, the update time is set to 1 month and 3 days, and the priority is set to be trusted.
The original attribute value of the attribute operating system in the entity to be updated (table 4) is RedHat, the state is effective, and the priority is credible. The newly arrived attribute "operating system" in table 5 has a trusted priority and the new attribute value is CentOS. Therefore, the attribute state of "operating system" is set as a conflict, the value of "software version" in the entity to be updated is updated to CentOS, centOS, redHat is recorded into the conflict value list, and the update recording time is 1 month and 3 days.
The original attribute value of the attribute "software name" in the entity to be updated (table 4) is nginnx, the state is effective, and the priority is common. The original attribute value of the attribute "software name" in the newly arrived table 5 is nginnx, and the priority is trusted. Therefore, the value of the software name in the entity to be processed is kept as the original attribute value of the software name, the attribute state is unchanged, the priority is updated to be credible, and the update time is updated to be 1 month and 2 days.
The original attribute value of the attribute "software version" in the entity to be updated (table 4) is 1.21, the state is conflict, and the priority is common. The attribute "software version" priority in the newly arrived table 5 is normal, and the new attribute value is 1.23. Therefore, the attribute status of "software version" is set to be conflicting, the value of "software version" in the entity to be updated is kept unchanged, and "1.23" is recorded into the conflicting value list, and the update recording time is 1 month and 3 days.
The newly arrived attribute "open port" in table 5 has a normal priority and a new attribute value of 80. Since the priority of the "open port" in the entity to be updated (table 4) is higher than the priority of the "open port" in table 5, the attribute value and attribute state of the "open port" in the entity to be updated, the update data and the priority are kept unchanged.
To sum up, the updated entity to be updated, i.e. table 6, is obtained.
And acquiring new attribute values of the attributes of the plurality of dimensions of the manually processed entity to be processed on 1 month and 4 days to obtain the table 7. And resolving the attribute with conflict in the entity to be processed through the manually processed data.
The original attribute value of the attribute "operating system" in the entity to be updated (table 6) is CentOS, the state is conflict, and the priority is credible. The original attribute value of the attribute "operating system" newly arrived at table 7 is CentOS, and the priority is manual. Thus, the "operating system" in the entity to be updated is kept unchanged, the attribute status is set to be effective, the update time is set to be 1 month and 4 days, and the priority is set to be manual.
The original attribute value of the attribute "software name" in the entity to be updated (table 6) is nginnx, the state is conflict, and the priority is credible. The original attribute value of the attribute "software name" in the new arrival table 7 is nginnx, and the priority is manual. Thus, the "software name" in the entity to be updated is kept unchanged, the attribute state is set to be effective, the update time is set to be 1 month and 4 days, and the priority is set to be manual.
The original attribute value of the attribute "software version" in the entity to be updated (table 6) is 1.21, the state is conflict, and the priority is common. The original attribute value of the attribute "software version" newly arrived at in table 7 is 1.23, and the priority is manual. Therefore, the attribute value of the "software name" in the entity to be updated is updated to 1.23, the attribute state is set to be effective, the update time is set to 1 month and 4 days, and the priority is set to be manual.
To sum up, the updated entity to be updated, i.e. table 8, is obtained.
The foregoing examples are provided merely for the purpose of understanding and are not to be construed as limiting the present application.
Based on the same technical concept, the present application further provides a data updating apparatus, as shown in fig. 3, where the data updating apparatus 100 includes an acquisition module 110 and a processing module 120.
An obtaining module 110, configured to obtain an original attribute value and a corresponding new attribute value of a target attribute of at least one dimension of an entity to be processed; the original attribute value and the new attribute value of the target attribute of each dimension are respectively provided with priority.
And the processing module 120 is configured to update the value of the target attribute in the entity to be processed to a new attribute value of the target attribute if the priority of the original attribute value of the target attribute in the entity to be processed is lower than the priority of the new attribute value of the target attribute.
The processing module 120 is further configured to keep the value of the target attribute in the entity to be processed as the original attribute value of the target attribute if the priority of the original attribute value of the target attribute in the entity to be processed is higher than the priority of the new attribute value of the target attribute.
The processing module 120 is further configured to, for each of the target attributes in the entity to be processed, perform conflict processing according to a preset conflict processing policy if the priority of the original attribute value of the target attribute in the entity to be processed is equal to the priority of the new attribute value of the target attribute.
The processing module 120 is specifically configured to determine whether the original attribute value of the target attribute in the entity to be processed is the same as the new attribute value of the target attribute; if the original attribute value of the target attribute in the entity to be processed is the same as the new attribute value of the target attribute, keeping the value of the target attribute in the entity to be processed as the original attribute value of the target attribute, and setting the attribute state of the target attribute as effective representation; if the original attribute value of the target attribute in the entity to be processed is different from the new attribute value of the target attribute, keeping the value of the target attribute in the entity to be processed as the original attribute value of the target attribute, setting the attribute state of the target attribute as a representation conflict, and recording the new attribute value of the target attribute into a preset conflict list.
The processing module 120 is further configured to, for each of the target attributes in the entity to be processed, set an attribute status of the target attribute in the entity to be processed to be characterized as valid if a priority of an original attribute value of the target attribute in the entity to be processed is lower than a priority of a new attribute value of the target attribute.
The processing module 120 is further configured to record an update time of the target attribute in a case where the value of the target attribute in the entity to be processed is updated to a new attribute value of the target attribute; and if the update time of the target attribute and the duration of the current time interval exceed the preset duration threshold, reducing the priority of the new attribute value of the target attribute.
The processing module 120 is further configured to obtain a missing attribute of the entity to be processed and a new attribute value corresponding to the missing attribute, where the missing attribute is an attribute that does not exist in the entity to be processed; and adding the missing attribute in the entity to be processed, and setting a new attribute value of the missing attribute as an original attribute value of the missing attribute.
The acquiring module 110 is specifically configured to acquire, from a target data source, an initial attribute of at least one dimension of the entity to be processed and an initial attribute value of each initial attribute; carrying out standardized processing on the obtained attribute names of all the initial attributes to obtain the attribute names of the target attributes of at least one dimension of the entity to be processed; and carrying out standardization processing on the initial attribute value of each initial attribute to obtain a new attribute value of the target attribute of at least one dimension of the entity to be processed.
If the target data sources include N, where N is a positive integer greater than or equal to 2, the obtaining module 110 is specifically configured to obtain, for an initial attribute of each dimension in the initial attributes of the at least one dimension, M candidate initial attribute values and priorities of the initial attributes from the N target data sources; wherein M is a positive integer less than or equal to N; and determining the candidate initial attribute with the highest priority from M candidate initial attribute values corresponding to the acquired initial attributes as the initial attribute corresponding to the corresponding initial attribute.
The data updating apparatus 100 provided in the embodiments of the present application has the same implementation principle and technical effects as those of the embodiments of the data updating method, and for brevity, reference may be made to corresponding contents in the embodiments of the data updating method.
Please refer to fig. 4, which illustrates an electronic device 200 according to an embodiment of the present application. The electronic device 200 includes: a processor 210, a memory 220.
The memory 220 and the processor 210 are electrically connected directly or indirectly to each other to realize data transmission or interaction. For example, the components may be electrically connected to each other via one or more communication buses or signal lines. The memory 220 is used for storing a computer program, for example, the software functional module shown in fig. 3, that is, the data updating apparatus 100. The data updating apparatus 100 includes at least one software function module that may be stored in the memory 220 in the form of software or firmware (firmware) or cured in an Operating System (OS) of the electronic device 200. The processor 240 is configured to execute executable modules stored in the memory 220, such as software functional modules or computer programs included in the data updating apparatus 100. At this time, the processor 240 is configured to obtain an original attribute value and a corresponding new attribute value of a target attribute of at least one dimension of the entity to be processed; the original attribute value and the new attribute value of the target attribute of each dimension are respectively provided with priority; if the priority of the original attribute value of the target attribute in the entity to be processed is lower than the priority of the new attribute value of the target attribute, updating the value of the target attribute in the entity to be processed into the new attribute value of the target attribute; and if the priority of the original attribute value of the target attribute in the entity to be processed is higher than the priority of the new attribute value of the target attribute, keeping the value of the target attribute in the entity to be processed as the original attribute value of the target attribute.
The Memory 220 may be, but is not limited to, a random access Memory (Random Access Memory, RAM), a Read Only Memory (ROM), a programmable Read Only Memory (Programmable Read-Only Memory, PROM), an erasable Read Only Memory (Erasable Programmable Read-Only Memory, EPROM), an electrically erasable Read Only Memory (Electric Erasable Programmable Read-Only Memory, EEPROM), etc.
The processor 240 may be an integrated circuit chip with signal processing capabilities. The processor may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; but also digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor 240 may be any conventional processor or the like.
The electronic device 200 includes, but is not limited to, a personal computer, a server, and the like.
The embodiments of the present application also provide a computer-readable storage medium (hereinafter referred to as a storage medium) on which a computer program is stored, which when executed by a computer such as the above-described electronic device 200, performs the above-described data updating method. The computer-readable storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing description is only of the preferred embodiments of the present application and is not intended to limit the same, but rather, various modifications and variations may be made by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.
Claims (11)
1. A method of updating data, comprising:
acquiring an original attribute value and a corresponding new attribute value of a target attribute of at least one dimension of an entity to be processed; the original attribute value and the new attribute value of the target attribute of each dimension are respectively provided with priority;
If the priority of the original attribute value of the target attribute in the entity to be processed is lower than the priority of the new attribute value of the target attribute, updating the value of the target attribute in the entity to be processed into the new attribute value of the target attribute;
and if the priority of the original attribute value of the target attribute in the entity to be processed is higher than the priority of the new attribute value of the target attribute, keeping the value of the target attribute in the entity to be processed as the original attribute value of the target attribute.
2. The method according to claim 1, wherein the method further comprises:
and aiming at each target attribute in the entity to be processed, if the priority of the original attribute value of the target attribute in the entity to be processed is equal to the priority of the new attribute value of the target attribute, carrying out conflict processing according to a preset conflict processing strategy.
3. The method of claim 2, wherein said performing conflict processing according to a preset conflict processing policy comprises:
judging whether the original attribute value of the target attribute in the entity to be processed is the same as the new attribute value of the target attribute;
if the original attribute value of the target attribute in the entity to be processed is the same as the new attribute value of the target attribute, keeping the value of the target attribute in the entity to be processed as the original attribute value of the target attribute, and setting the attribute state of the target attribute as effective representation;
If the original attribute value of the target attribute in the entity to be processed is different from the new attribute value of the target attribute, keeping the value of the target attribute in the entity to be processed as the original attribute value of the target attribute, setting the attribute state of the target attribute as a representation conflict, and recording the new attribute value of the target attribute into a preset conflict list.
4. A method according to claim 3, characterized in that the method further comprises:
and setting the attribute state of the target attribute in the entity to be processed as effective representation if the priority of the original attribute value of the target attribute in the entity to be processed is lower than the priority of the new attribute value of the target attribute aiming at each target attribute in the entity to be processed.
5. The method according to claim 1, wherein the method further comprises:
under the condition that the value of the target attribute in the entity to be processed is updated to be a new attribute value of the target attribute, recording the updating time of the target attribute;
and if the update time of the target attribute and the duration of the current time interval exceed the preset duration threshold, reducing the priority of the new attribute value of the target attribute.
6. The method according to claim 1, wherein the method further comprises:
acquiring a missing attribute of the entity to be processed and a new attribute value corresponding to the missing attribute, wherein the missing attribute is an attribute which does not exist in the entity to be processed;
and adding the missing attribute in the entity to be processed, and setting a new attribute value of the missing attribute as an original attribute value of the missing attribute.
7. The method according to any of claims 1-6, wherein the process of obtaining new attribute values for target attributes of at least one dimension of the entity to be processed comprises:
acquiring initial attributes of at least one dimension of the entity to be processed and initial attribute values of each initial attribute from a target data source;
carrying out standardized processing on the obtained attribute names of all the initial attributes to obtain the attribute names of the target attributes of at least one dimension of the entity to be processed; and carrying out standardization processing on the initial attribute value of each initial attribute to obtain a new attribute value of the target attribute of at least one dimension of the entity to be processed.
8. The method of claim 7, wherein the target data source comprises N, N being a positive integer greater than or equal to 2, the obtaining initial attributes of the at least one dimension of the entity to be processed from the target data source and initial attribute values for each initial attribute comprising:
For each dimension initial attribute in the initial attributes of the at least one dimension, acquiring M candidate initial attribute values and priorities of the initial attribute from the N target data sources; wherein M is a positive integer less than or equal to N;
and determining the candidate initial attribute value with the highest priority from the M candidate initial attribute values as the initial attribute value corresponding to the corresponding initial attribute.
9. A data updating apparatus, comprising:
the acquisition module is used for acquiring an original attribute value and a corresponding new attribute value of a target attribute of at least one dimension of the entity to be processed; the original attribute value and the new attribute value of the target attribute of each dimension are respectively provided with priority;
the processing module is used for updating the value of the target attribute in the entity to be processed into the new attribute value of the target attribute if the priority of the original attribute value of the target attribute in the entity to be processed is lower than the priority of the new attribute value of the target attribute;
the processing module is further configured to keep the value of the target attribute in the entity to be processed as the original attribute value of the target attribute if the priority of the original attribute value of the target attribute in the entity to be processed is higher than the priority of the new attribute value of the target attribute.
10. An electronic device, comprising: the device comprises a memory and a processor, wherein the memory is connected with the processor;
the memory is used for storing programs;
the processor is configured to invoke a program stored in the memory to perform the method of any of claims 1-8.
11. A computer-readable storage medium, on which a computer program is stored, which, when being run by a computer, performs the method according to any one of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310955950.9A CN117390034A (en) | 2023-07-31 | 2023-07-31 | Data updating method, device, electronic equipment and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310955950.9A CN117390034A (en) | 2023-07-31 | 2023-07-31 | Data updating method, device, electronic equipment and computer readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117390034A true CN117390034A (en) | 2024-01-12 |
Family
ID=89461943
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310955950.9A Pending CN117390034A (en) | 2023-07-31 | 2023-07-31 | Data updating method, device, electronic equipment and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117390034A (en) |
-
2023
- 2023-07-31 CN CN202310955950.9A patent/CN117390034A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109617646B (en) | Message conversion method and device, computer equipment and computer readable storage medium | |
| JP4983795B2 (en) | System management program, system management apparatus, and system management method | |
| CN107911397B (en) | Threat assessment method and device | |
| CN111782652B (en) | Data calling method, device, computer equipment and storage medium | |
| EP3671512B1 (en) | Automated software vulnerability determination | |
| CN110471912B (en) | Employee attribute information verification method and device and terminal equipment | |
| CN108805725B (en) | Risk event confirmation method, server, and computer-readable storage medium | |
| CN110442466B (en) | Method, device, computer equipment and storage medium for preventing repeated access request | |
| CN117390034A (en) | Data updating method, device, electronic equipment and computer readable storage medium | |
| CN110489416B (en) | Information storage method based on data processing and related equipment | |
| CN116932072A (en) | Service configuration method, device, computer readable storage medium and terminal equipment | |
| US11113706B2 (en) | Scoring information matching method and device, storage medium and server | |
| CN112783909B (en) | Data updating method, device, terminal equipment and storage medium | |
| CN114115933A (en) | Method, system, device, electronic equipment and medium for software upgrading | |
| CN113626436A (en) | Data processing method and device | |
| CN108415814B (en) | Method for automatically recording field change, application server and computer readable storage medium | |
| CN112711584A (en) | Data checking method, checking device, terminal equipment and readable storage medium | |
| CN113220762A (en) | Method, device, processor and storage medium for realizing general record processing of key service field change in big data application | |
| CN112115175B (en) | Cloud service product processing method and device, electronic equipment and storage medium | |
| CN111125232A (en) | Method and device for accessing public cloud asset information | |
| CN114118014B (en) | Distributed document control method and device, readable storage medium and electronic equipment | |
| US11768819B2 (en) | Data unblocking in application platforms | |
| CN115099922B (en) | Financial data query method, system, readable storage medium and computer equipment | |
| CN115994089A (en) | Test script generation method, device, computer equipment, storage medium and product | |
| CN116881081A (en) | Acquisition configuration updating method, device and system of monitoring system 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 |