Attribute configuration method and device, computer device, storage medium and program product

Abstract

The application relates to an attribute configuration method and device, computer equipment, a storage medium and a computer program product. The method comprises the following steps: obtaining a first type of configuration object and a second type of configuration object; the first type of configuration object contains identification information, and the second type of configuration object does not contain identification information; determining attribute information of the first type of configuration object according to the identification information of the first type of configuration object; the attribute information comprises a compulsory attribute and a non-compulsory attribute; taking the configuration object with non-compulsory attribute information in the first type of configuration object and the second type of configuration object as a target configuration object, and determining attribute information of the target configuration object based on an attribute index of the target configuration object. According to the method, attribute information of the configuration object can be conveniently determined, and the efficiency of configuring the attribute of the configuration object is improved.

Description

Technical Field

[0001] This application relates to the field of big data technology, and in particular to an attribute configuration method, apparatus, computer equipment, storage medium, and computer program product. Background Technology

[0002] As data centers in the financial industry continue to expand, the number of hardware and software infrastructures deployed within them is also increasing. This has led to the emergence of configuration management systems (MMS), which are management systems that manage infrastructure or configuration objects within a data center. MMS can generate configuration information by recording basic information about configuration objects and their associated relationships. Therefore, efficiently acquiring the basic information of configuration objects is particularly important for MMS.

[0003] In general, the basic information of a configuration object can be described through its properties. Traditionally, this involves manually configuring these properties to obtain the object's basic information. However, this traditional method of configuring object properties is inefficient. Summary of the Invention

[0004] Therefore, it is necessary to provide an attribute configuration method, apparatus, computer device, computer-readable storage medium, and computer program product that can improve the efficiency of attribute configuration in order to address the above-mentioned technical problems.

[0005] Firstly, this application provides an attribute configuration method. The method includes:

[0006] Obtain a first type of configuration object and a second type of configuration object; the first type of configuration object contains identification information, while the second type of configuration object does not contain identification information;

[0007] Based on the identification information of the first type of configuration object, the attribute information of the first type of configuration object is determined; the attribute information includes required attributes and optional attributes;

[0008] The configuration objects with non-mandatory attribute information in the first type of configuration objects and the second type of configuration objects are taken as target configuration objects. The attribute information of the target configuration objects is determined based on the attribute indicators of the target configuration objects.

[0009] In one embodiment, the step of taking the configuration objects with non-mandatory attribute information in the first type of configuration objects and the second type of configuration objects as target configuration objects, and determining the attribute information of the target configuration objects based on the attribute indicators of the target configuration objects, includes:

[0010] Retrieve configuration objects from the first type of configuration objects whose attribute information is not required;

[0011] The configuration object of the non-mandatory attributes and the second type of configuration object are used as the target configuration object;

[0012] Calculate the attribute metrics of the target configuration object, and determine the attribute information of the target configuration object based on the attribute metrics of the target configuration object; the attribute metrics include call frequency and query frequency.

[0013] In one embodiment, calculating the attribute metrics of the target configuration object includes:

[0014] The invocation frequency of the target configuration object is calculated based on the total number of first applications corresponding to the target configuration object and the total number of second applications corresponding to the target configuration object; the second application is used to transmit the attribute information with the target configuration object, and the first application is the application in the second application used to call the target configuration object;

[0015] The query frequency of the target configuration object is calculated based on the number of queries to the target configuration object within a preset time period and the total number of the target configuration objects.

[0016] In one embodiment, the method further includes:

[0017] Based on the attribute information of the first type of configuration object, configure the required tags for the configuration objects in the first type of configuration object whose attribute information is required;

[0018] The step of retrieving configuration objects from the first type of configuration objects whose attribute information is a non-mandatory attribute includes:

[0019] Based on the required field tag, obtain configuration objects from the first type of configuration objects whose attribute information is not required.

[0020] In one embodiment, determining the attribute information of the first type of configuration object based on the identification information of the first type of configuration object includes:

[0021] Obtain the mapping relationship between the identification information of the first type of configuration object and the attribute information of the first type of configuration object;

[0022] Based on the identification information of the first type of configuration object and the mapping relationship, the attribute information of the first type of configuration object is determined.

[0023] In one embodiment, the method further includes:

[0024] Determine whether the configuration object includes identification information;

[0025] If the configuration object includes identification information, then the configuration object is classified as a first type of configuration object;

[0026] If the configuration object does not include identification information, then the configuration object is classified as a second type of configuration object.

[0027] In one embodiment, the method further includes:

[0028] The target configuration object in the target configuration object whose attribute information is required, and the configuration object in the first type of configuration object whose attribute information is required, are taken as the configuration objects to be verified;

[0029] Perform a non-empty check on the values ​​corresponding to the attribute information of the configuration object to be checked, and generate a non-empty check result;

[0030] A prompt interface is generated based on the configuration object to be verified, whose non-empty verification result is empty.

[0031] Secondly, this application also provides an attribute configuration device. The device includes:

[0032] The configuration object acquisition module is used to acquire a first type of configuration object and a second type of configuration object; the first type of configuration object contains identification information, while the second type of configuration object does not contain identification information.

[0033] The first determining module is used to determine the attribute information of the first type of configuration object based on the identification information of the first type of configuration object; the attribute information includes required attributes and optional attributes;

[0034] The second determining module is used to take the configuration objects with non-mandatory attribute information in the first type of configuration objects and the second type of configuration objects as target configuration objects, and determine the attribute information of the target configuration objects based on the attribute indicators of the target configuration objects.

[0035] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the steps of the method in any of the embodiments of the first aspect described above.

[0036] Fourthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, implements the steps of the method in any of the embodiments of the first aspect described above.

[0037] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the steps of the method in any of the embodiments of the first aspect described above.

[0038] The aforementioned attribute configuration method, apparatus, computer device, storage medium, and computer program product acquire a first type of configuration object and a second type of configuration object. The first type of configuration object contains identification information, while the second type of configuration object does not. Based on the identification information of the first type of configuration object, attribute information of the first type of configuration object is determined. Attribute information includes mandatory attributes and optional attributes. Configuration objects with optional attributes in the first type of configuration object and the second type of configuration object are used as target configuration objects, and attribute information of the target configuration objects is determined based on the attribute indicators of the target configuration objects. Since this application can pre-acquire the first type of configuration object containing identification information and the second type of configuration object not containing identification information, for the first type of configuration object, the attribute information of the first type of configuration object can be directly determined based on its identification information. Using configuration objects with optional attributes in the first type of configuration object and the second type of configuration object as target configuration objects, the attribute information of the target configuration object can be conveniently determined based on its attribute indicators, thereby improving the efficiency of configuring the attributes of configuration objects. Attached Figure Description

[0039] Figure 1 This is an application environment diagram of the attribute configuration method in one embodiment;

[0040] Figure 2 This is a flowchart illustrating an attribute configuration method in one embodiment;

[0041] Figure 3 A flowchart illustrating the steps for determining the attribute information of a target configuration object in one embodiment;

[0042] Figure 4 This is a flowchart illustrating the attribute index calculation steps in one embodiment;

[0043] Figure 5 This is a flowchart illustrating the required label configuration steps in another embodiment;

[0044] Figure 6 This is a flowchart illustrating the steps for determining the attribute information of a first type of configuration object in one embodiment.

[0045] Figure 7 A flowchart illustrating the configuration of the object classification step in another embodiment;

[0046] Figure 8 This is a flowchart illustrating the non-empty verification step in another embodiment;

[0047] Figure 9 This is a schematic diagram of the overall process of the verification steps in one embodiment;

[0048] Figure 10 This is a flowchart illustrating the attribute configuration method in one optional embodiment;

[0049] Figure 11 This is a schematic diagram of the overall process of the attribute configuration method in one embodiment;

[0050] Figure 12 This is a structural block diagram of an attribute configuration device in one embodiment;

[0051] Figure 13 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0052] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0053] As data centers in the financial industry continue to expand, the number of hardware and software infrastructures deployed within them is also increasing. This has led to the emergence of configuration management systems (MMS), which are management systems that manage configuration objects within the data center. These configuration objects refer to the data center's hardware and software infrastructure. Hardware infrastructure includes equipment such as server room environment devices, servers, storage devices, and network equipment, while software infrastructure includes software information and application information. MMS can generate configuration information by recording basic information about configuration objects and their associated relationships, enabling management application systems to accurately deploy information in the actual production environment. Furthermore, MMS can send configuration information to downstream systems such as monitoring systems, operations and maintenance systems, and resource provisioning systems, thus providing foundational data for actual application processes. Therefore, the efficient acquisition of basic information about configuration objects is particularly important for MMS and related systems.

[0054] Generally, the basic information of a configuration object can be described through its attributes. These attributes include required attributes (also called mandatory field attributes) and optional attributes (also called optional field attributes). Required attributes are typically used to describe the key information contained within the configuration object, while optional attributes are used to describe the less critical information. Traditionally, the attribute information of a configuration object is determined through interviews and consultations with relevant stakeholders (such as configuration entry personnel, configuration users, and configuration supervisors) during the configuration object definition or modification phase. In other words, the traditional method generally involves manually configuring the attributes of the configuration object to obtain its basic information. The basic information of a configuration object includes its attribute information.

[0055] However, traditional methods of configuring object attributes are time-consuming and labor-intensive, requiring extensive consultation and repeated coordination among stakeholders when there are many involved. Furthermore, since the personnel who input the configuration information are often different from the users, changes in usage or scenario are frequently not detected in a timely manner, hindering timely updates. Additionally, adjusting attribute information necessitates application releases, a cumbersome process. In summary, traditional attribute configuration methods suffer from low efficiency.

[0056] The attribute configuration method provided in this application embodiment can be applied to, for example, Figure 1In the application environment shown, terminal 102 communicates with server 104 via a network. A data storage system can store the data that server 104 needs to process. The data storage system can be integrated onto server 104 or placed on the cloud or other network servers. Server 104 obtains a first type of configuration object and a second type of configuration object; the first type of configuration object contains identification information, while the second type of configuration object does not contain identification information; server 104 determines the attribute information of the first type of configuration object based on its identification information; the attribute information includes required attributes and optional attributes; server 104 uses the configuration objects with optional attributes in the first type of configuration object and the second type of configuration object as target configuration objects, and determines the attribute information of the target configuration objects based on their attribute indicators. Terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can be smart speakers, smart TVs, smart air conditioners, smart vehicle devices, etc. Portable wearable devices can be smartwatches, smart bracelets, head-mounted devices, etc. Server 104 can be implemented using a standalone server or a server cluster composed of multiple servers.

[0057] In one embodiment, such as Figure 2 As shown, a property configuration method is provided, which can be applied to Figure 1 Taking server 104 as an example, the following steps are included:

[0058] Step 220: Obtain the first type of configuration object and the second type of configuration object; the first type of configuration object contains identification information, while the second type of configuration object does not contain identification information.

[0059] In this context, "configuration objects" refers to the hardware and software infrastructure of the data center. Hardware infrastructure includes equipment such as data center environment devices, servers, storage devices, and network equipment, while software infrastructure includes software information and application information. In this embodiment, configuration objects can be pre-classified into a first type and a second type. The first type of configuration object contains identification information, while the second type does not. Identification information refers to the identifier corresponding to the configuration object. Therefore, server 104 can obtain both the first and second type of configuration objects from the configuration objects.

[0060] Step 240: Determine the attribute information of the first type of configuration object based on the identification information of the first type of configuration object; the attribute information includes required attributes and optional attributes.

[0061] For example, the server's identification information can be "server," and the application node's identification information can be "appnode." Therefore, server 104 can determine the attribute information of each configuration object in the first type of configuration object based on the identification information of the first type of configuration object. The attribute information includes required attributes and optional attributes; that is, the attribute information of the first type of configuration object can be either required or optional. If the attribute information of the first type of configuration object is a required attribute, it indicates that the first type of configuration object is a required item; if the attribute information of the first type of configuration object is an optional attribute, it indicates that the first type of configuration object is an optional item. Required attributes are also called mandatory input attributes, and generally, required attributes are used to describe the information contained in the configuration object as key information; optional attributes are also called optional input attributes, and generally, optional attributes are used to describe the information contained in the configuration object as non-key information. Generally, the attribute information of the first type of configuration object is usually required, but this embodiment does not limit this.

[0062] Step 260: Take the configuration objects with non-mandatory attribute information in the first type of configuration objects and the second type of configuration objects as target configuration objects, and determine the attribute information of the target configuration objects based on the attribute indicators of the target configuration objects.

[0063] Optionally, based on the determined attribute information of the first type of configuration objects, server 104 can select configuration objects with non-mandatory attribute information from the first type of configuration objects, and use the configuration objects with non-mandatory attribute information in the first type of configuration objects and the second type of configuration objects as target configuration objects. Then, based on the attribute metrics of the target configuration objects, server 104 can determine the attribute information of the target configuration objects. Here, attribute metrics are index values ​​used to characterize the attribute information of the configuration objects.

[0064] In the above attribute configuration method, a first type of configuration object and a second type of configuration object are obtained. The first type of configuration object contains identification information, while the second type of configuration object does not contain identification information. Based on the identification information of the first type of configuration object, the attribute information of the first type of configuration object is determined. The attribute information includes required attributes and optional attributes. Configuration objects with optional attributes in the first type of configuration object and the second type of configuration object are used as target configuration objects. Based on the attribute indicators of the target configuration objects, the attribute information of the target configuration objects is determined. Since this application can pre-obtain the first type of configuration object containing identification information and the second type of configuration object not containing identification information, for the first type of configuration object, the attribute information of the first type of configuration object can be directly determined based on its identification information. Using configuration objects with optional attributes in the first type of configuration object and the second type of configuration object as target configuration objects, the attribute information of the target configuration object can be conveniently determined based on its attribute indicators. This improves the efficiency of configuring the attributes of configuration objects.

[0065] In one embodiment, such as Figure 3 As shown, configuration objects with non-mandatory attributes in the first type of configuration objects and the second type of configuration objects are taken as target configuration objects. Based on the attribute indicators of the target configuration objects, the attribute information of the target configuration objects is determined, including:

[0066] Step 320: Obtain configuration objects with non-mandatory attribute information from the first type of configuration objects.

[0067] Optionally, based on the attribute information of the first type of configuration objects, server 104 can determine whether the attribute information of the first type of configuration objects is a required attribute or a non-required attribute, and thus select configuration objects from the first type of configuration objects whose attribute information is non-required. The attribute information of the configuration objects includes required attributes (also called mandatory input attributes) and non-required attributes (also called optional input attributes). Non-required attributes are generally used to describe non-critical information contained in the configuration object.

[0068] Step 340: Use the configuration objects with non-required attributes and the second type of configuration objects as the target configuration objects.

[0069] Optionally, server 104 may use configuration objects with non-mandatory attribute information in the first type of configuration objects and second type of configuration objects as target configuration objects. The target configuration object is used to represent configuration objects whose attribute information cannot be accurately determined based on the configuration object's identifier information.

[0070] Step 360: Calculate the attribute metrics of the target configuration object, and determine the attribute information of the target configuration object based on the attribute metrics of the target configuration object; the attribute metrics include call frequency and query frequency.

[0071] Optionally, for each target configuration object, server 104 can calculate the attribute metrics of the target configuration object based on its actual usage. Then, based on the attribute metrics, server 104 can determine the attribute information of the target configuration object. The attribute information includes required and optional attributes, and the attribute metrics are indicator values ​​used to characterize the attribute information of the configuration object, including call frequency and query frequency.

[0072] In this embodiment, configuration objects with non-mandatory attributes are obtained from the first type of configuration objects; these non-mandatory attribute configuration objects and the second type of configuration objects are used as target configuration objects. For each target configuration object, this embodiment can calculate the attribute indicators of the target configuration object and, based on these indicators, conveniently determine the attribute information of the target configuration object, thereby improving the efficiency of configuring the attributes of the target configuration object.

[0073] In one embodiment, such as Figure 4 As shown, the attribute metrics of the target configuration object are calculated, including:

[0074] Step 420: Calculate the call frequency of the target configuration object based on the total number of first applications corresponding to the target configuration object and the total number of second applications corresponding to the target configuration object; the second application is used to transmit attribute information with the target configuration object, and the first application is the application in the second application used to call the target configuration object.

[0075] Optionally, since configuration information can be generated by recording the basic information of the configuration object and the associated relationships, and the server 104 can send the generated configuration information to downstream systems such as monitoring systems, operation and maintenance systems, and resource supply systems, thereby providing basic data for the actual application process. Therefore, for each target configuration object, the server 104 can calculate the call frequency of the target configuration object based on the total number of first applications corresponding to the target configuration object and the total number of second applications corresponding to the target configuration object. The second application is used to transmit attribute information with the target configuration object, and the first application is the application used to call the target configuration object within the second application. For example, the call frequency of the target configuration object is equal to the total number of first applications corresponding to the target configuration object divided by the total number of second applications corresponding to the target configuration object.

[0076] Step 440: Calculate the query frequency of the target configuration object based on the number of queries of the target configuration object within a preset time period and the total number of target configuration objects.

[0077] Optionally, for each target configuration object, the server 104 can calculate the query frequency of the target configuration object based on the number of queries performed on the target configuration object within a preset time period and the total number of target configuration objects. The query frequency of a target configuration object represents the number of times the target configuration object is queried within the preset time period. For example, the query frequency of a target configuration object is equal to the number of queries performed on the target configuration object within the preset time period divided by the total number of configuration objects.

[0078] In this embodiment, the call frequency of the target configuration object can be calculated based on the total number of applications used to call the target configuration object in the second application and the total number of second applications used to transmit attribute information with the target configuration object; the query frequency of the target configuration object can be calculated based on the number of queries to the target configuration object within a preset time period and the total number of target configuration objects. Since the attribute indicators include call frequency and query frequency, the attribute indicators of the target configuration object can be conveniently determined based on the call frequency and query frequency.

[0079] In one embodiment, such as Figure 5 As shown, the attribute configuration method also includes:

[0080] Step 520: Based on the attribute information of the first type of configuration object, configure the required tags for the configuration objects in the first type of configuration object whose attribute information is required.

[0081] Optionally, based on the attribute information of the first type of configuration objects, the server 104 can determine whether the attribute information of the first type of configuration objects is a required attribute or a non-required attribute, and thus select configuration objects from the first type of configuration objects whose attribute information is required. Then, the server 104 can configure required field tags for each configuration object in the first type of configuration objects whose attribute information is required. Required attributes, also known as mandatory input attributes, are generally used to describe key information contained in the configuration object. Required field tags are used to indicate that the attribute information of the configuration object is required. Required field tags can be in the form of asterisks, checkmarks, etc., and can be configured through manual input or automatic annotation. Of course, this embodiment does not limit the marking form or configuration method of required field tags.

[0082] Configuration objects from the first type of configuration objects that have non-required attribute information include:

[0083] Step 540: Based on the required tags, obtain the configuration objects with non-required attributes from the first type of configuration objects.

[0084] Optionally, based on the required tags in the first type of configuration objects, the server 104 can determine that the configuration objects in the first type of configuration objects that do not have required tags configured are configuration objects with non-required attributes. Thus, the server 104 can obtain configuration objects with non-required attributes from the first type of configuration objects.

[0085] In this embodiment, based on the attribute information of the first type of configuration objects, mandatory tags are configured for configuration objects whose attribute information is mandatory. Then, based on the mandatory tags, configuration objects whose attribute information is not mandatory can be obtained from the first type of configuration objects, thus allowing for convenient determination of the target configuration object.

[0086] In one embodiment, such as Figure 6 As shown, based on the identifier information of the first type of configuration object, the attribute information of the first type of configuration object is determined, including:

[0087] Step 620: Obtain the mapping relationship between the identification information of the first type of configuration object and the attribute information of the first type of configuration object.

[0088] Optionally, for the first type of configuration object, server 104 can obtain the mapping relationship between the identification information and attribute information of the first type of configuration object. For example, for a server with the identification information "server", the identification information of each server includes a serial number, resource code, and management ID corresponding to each server, wherein the serial number, resource code, and management ID each correspond one-to-one with a server. Based on historical production and operation data, the identification information such as the serial number, resource code, and management ID corresponding to each server can be used to determine whether the information contained in each server is critical information. If the information contained in a server is critical information, then the attribute information of that server is determined to be a required attribute, thereby obtaining the mapping relationship between the identification information and the attribute information of that server, and thus obtaining the mapping relationship between the identification information and the attribute information of each server.

[0089] Step 640: Determine the attribute information of the first type of configuration object based on the identification information and mapping relationship of the first type of configuration object.

[0090] Optionally, based on the identification information of the first type of configuration object and the mapping relationship between the identification information of the first type of configuration object and the attribute information of the first type of configuration object, the server 104 can find the attribute information of the first type of configuration object corresponding to the identification information of the first type of configuration object from the mapping relationship between the identification information of the first type of configuration object and the attribute information of the first type of configuration object, thereby determining the attribute information of each configuration object in the first type of configuration object.

[0091] In this embodiment, for the first type of configuration object, the mapping relationship between the identification information of the first type of configuration object and the attribute information of the first type of configuration object is obtained; then, based on the identification information of the first type of configuration object and the pre-obtained mapping relationship, the attribute information of the first type of configuration object can be easily determined.

[0092] In one embodiment, such as Figure 7 As shown, the attribute configuration method also includes:

[0093] Step 720: Determine whether the configuration object includes identification information.

[0094] Step 740: If the configuration object includes identification information, then the configuration object is classified as a first-class configuration object.

[0095] Step 760: If the configuration object does not include identification information, then the configuration object is classified as a second type of configuration object.

[0096] Optionally, for each configuration object, server 104 can determine whether the configuration object includes identification information. If it is determined that the configuration object includes identification information, the configuration object is classified into a first type of configuration object; if it is determined that the configuration object does not include identification information, the configuration object is classified into a second type of configuration object. Here, identification information refers to the identifier corresponding to the configuration object. The first type of configuration object is a collection of configuration objects containing identification information, and the second type of configuration object is a collection of configuration objects not containing identification information. For example, the second type of configuration object may include upper-level regulatory configuration objects and production operation and maintenance configuration objects, and both upper-level regulatory configuration objects and production operation and maintenance configuration objects are configuration objects that do not contain identification information.

[0097] In this embodiment, it is determined whether the configuration object includes identification information. If the configuration object includes identification information, it is classified as a first type of configuration object; if the configuration object does not include identification information, it is classified as a second type of configuration object. This embodiment can classify configuration objects into first-type and second-type configuration objects by determining whether the configuration object includes identification information.

[0098] In one embodiment, such as Figure 8 As shown, the attribute configuration method also includes:

[0099] Step 820: The target configuration object in the target configuration object with required attribute information and the configuration object in the first type of configuration object with required attribute information are taken as the configuration objects to be verified.

[0100] Optionally, such as Figure 9 As shown, Figure 9This is a schematic diagram of the overall flow of the verification steps in one embodiment. First, server 104 can obtain the attribute information of the first type of configuration object and the attribute information of the target configuration object, thereby obtaining the attribute information of each configuration object. Second, server 104 can load the attribute information of each configuration object on the front-end interface and mark the configuration objects with required attributes on the front-end interface. Then, the target configuration object with required attributes and the configuration objects with required attributes in the first type of configuration object are used as the configuration objects to be verified. The configuration objects to be verified are those with required attributes.

[0101] Step 840: Perform non-empty validation on the values ​​corresponding to the attribute information of the configuration object to be validated, and generate a non-empty validation result.

[0102] Optionally, combined Figure 9 As shown, for each configuration object to be validated where the attribute information is mandatory, a non-empty validation is performed on the values ​​corresponding to the attribute information of the configuration object to be validated, generating a non-empty validation result. The non-empty validation refers to the process of determining whether the value corresponding to the attribute information of the configuration object to be validated is empty using a conditional statement. Since all the attribute information of the configuration object to be validated is mandatory, the non-empty validation result of the configuration object to be validated cannot be empty.

[0103] Step 860: Generate a prompt interface based on the configuration object to be verified whose non-empty verification result is empty.

[0104] Optionally, if the non-empty verification result of the configuration object to be verified is empty, it means that the value corresponding to the attribute information of the configuration object to be verified is empty, that is, the user has not filled in the value corresponding to the attribute information of the configuration object to be verified. Therefore, the server 104 can generate a prompt interface based on the configuration object to be verified with an empty non-empty verification result, to prompt the user to fill in the value corresponding to the attribute information of the configuration object to be verified with an empty non-empty verification result.

[0105] In this embodiment, the target configuration object with required attribute information and the configuration objects with required attribute information in the first type of configuration objects are used as the configuration objects to be verified. The values ​​corresponding to the attribute information of the configuration objects to be verified are subjected to non-empty validation, generating a non-empty validation result. Based on the configuration objects to be verified whose non-empty validation result is empty, a prompt interface is generated. This allows for non-empty validation of the values ​​corresponding to the attribute information of the configuration objects to be verified that have required attribute information, thus avoiding errors in the attribute information of the configuration objects due to omissions in the missing attribute information.

[0106] In an optional embodiment, such as Figure 10 As shown, a property configuration method is provided, which can be applied to Figure 1 Taking server 104 as an example, the following steps are included:

[0107] Step 1002: Determine whether the configuration object includes identification information;

[0108] Step 1004: If the configuration object includes identification information, then the configuration object is classified as a first type of configuration object;

[0109] Step 1006: If the configuration object does not include identification information, then the configuration object is classified as a second type of configuration object;

[0110] Step 1008: Obtain the first type of configuration object and the second type of configuration object; the first type of configuration object contains identification information, while the second type of configuration object does not contain identification information;

[0111] Step 1010: Obtain the mapping relationship between the identification information of the first type of configuration object and the attribute information of the first type of configuration object;

[0112] Step 1012: Determine the attribute information of the first type of configuration object based on the identification information and mapping relationship of the first type of configuration object; the attribute information includes required attributes and optional attributes;

[0113] Step 1014: Based on the attribute information of the first type of configuration object, configure the required tags for the configuration objects in the first type of configuration object whose attribute information is required.

[0114] Step 1016: Based on the required tags, obtain the configuration objects with non-required attributes from the first type of configuration objects;

[0115] Step 1018: Use the configuration objects with non-mandatory attributes and the second type of configuration objects as the target configuration objects;

[0116] Step 1020: Calculate the call frequency of the target configuration object based on the total number of first applications corresponding to the target configuration object and the total number of second applications corresponding to the target configuration object; the second application is used to transmit attribute information with the target configuration object, and the first application is the application in the second application used to call the target configuration object;

[0117] Step 1022: Calculate the query frequency of the target configuration object based on the number of queries of the target configuration object within a preset time period and the total number of target configuration objects;

[0118] Step 1024: Determine the attribute information of the target configuration object based on its attribute metrics; the attribute metrics include call frequency and query frequency.

[0119] Step 1026: Take the target configuration object in the target configuration object whose attribute information is required and the configuration object in the first type of configuration object whose attribute information is required as the configuration objects to be verified.

[0120] Step 1028: Perform non-empty validation on the values ​​corresponding to the attribute information of the configuration object to be validated, and generate a non-empty validation result.

[0121] Step 1030: Generate a prompt interface based on the configuration object to be verified whose non-empty verification result is empty.

[0122] Optional, such as Figure 11 As shown, Figure 11 This is a schematic diagram of the overall flow of the attribute configuration method in one embodiment. First, for each configuration object, it is determined whether a required label is configured for each configuration object according to the name of the configuration object. If a required label is configured for the configuration object, the attribute information of the configuration object is determined to be a required attribute; if no required label is configured for the configuration object, the attribute index of the configuration object is calculated, and it is determined whether the attribute index of the configuration object meets a preset threshold. If the attribute index of the configuration object meets the preset threshold, the attribute information of the configuration object is determined to be a required attribute; if the attribute index of the configuration object does not meet the preset threshold, the attribute information of the configuration object is determined to be a non-required attribute. Then, the determined attribute information of each configuration object is stored in a list of required attributes or in a cache. Since the attribute index includes the call frequency and the query frequency, the call frequency and the query frequency need to be considered together when determining whether the attribute index of each configuration object meets the preset threshold. For example, the condition for the attribute index of a configuration object to meet the preset threshold can be: the call frequency meets a preset call frequency threshold, and the query frequency meets a preset query frequency threshold. Of course, this embodiment does not limit the preset threshold, the preset call frequency threshold, and the preset query frequency threshold.

[0123] In the above attribute configuration method, a first type of configuration object and a second type of configuration object are obtained. The first type of configuration object contains identification information, while the second type of configuration object does not contain identification information. Based on the identification information of the first type of configuration object, the attribute information of the first type of configuration object is determined. The attribute information includes required attributes and optional attributes. Configuration objects with optional attributes in the first type of configuration object and the second type of configuration object are used as target configuration objects. Based on the attribute indicators of the target configuration objects, the attribute information of the target configuration objects is determined. Since this application can pre-obtain the first type of configuration object containing identification information and the second type of configuration object not containing identification information, for the first type of configuration object, the attribute information of the first type of configuration object can be directly determined based on its identification information. Using configuration objects with optional attributes in the first type of configuration object and the second type of configuration object as target configuration objects, the attribute information of the target configuration object can be conveniently determined based on its attribute indicators. This improves the efficiency of configuring the attributes of configuration objects.

[0124] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0125] Based on the same inventive concept, this application also provides an attribute configuration apparatus for implementing the attribute configuration method described above. The solution provided by this apparatus is similar to the implementation described in the above method; therefore, the specific limitations in one or more attribute configuration apparatus embodiments provided below can be found in the limitations of the attribute configuration method described above, and will not be repeated here.

[0126] In one embodiment, such as Figure 12 As shown, an attribute configuration device 1200 is provided, including: a configuration object acquisition module 1220, a first determination module 1240, and a second determination module 1260, wherein:

[0127] The configuration object acquisition module 1220 is used to acquire a first type of configuration object and a second type of configuration object; the first type of configuration object contains identification information, while the second type of configuration object does not contain identification information.

[0128] The first determining module 1240 is used to determine the attribute information of the first type of configuration object based on the identification information of the first type of configuration object; the attribute information includes required attributes and optional attributes.

[0129] The second determining module 1260 is used to take the configuration objects with non-mandatory attribute information in the first type of configuration objects and the second type of configuration objects as target configuration objects, and determine the attribute information of the target configuration objects based on the attribute indicators of the target configuration objects.

[0130] In one embodiment, the second determining module 1260 includes:

[0131] The configuration object determination unit is used to obtain configuration objects from the first type of configuration objects whose attribute information is a non-mandatory attribute.

[0132] The target configuration object determination unit is used to identify configuration objects with non-mandatory attributes and second-type configuration objects as target configuration objects.

[0133] The attribute information determination unit is used to calculate the attribute indicators of the target configuration object and determine the attribute information of the target configuration object based on the attribute indicators; the attribute indicators include call frequency and query frequency.

[0134] In one embodiment, the attribute information determination unit includes:

[0135] The call frequency calculation unit is used to calculate the call frequency of the target configuration object based on the total number of the first application corresponding to the target configuration object and the total number of the second application corresponding to the target configuration object; the second application is used to transmit attribute information with the target configuration object, and the first application is the application in the second application used to call the target configuration object;

[0136] The query frequency calculation unit is used to calculate the query frequency of the target configuration object based on the number of queries to the target configuration object within a preset time period and the total number of target configuration objects.

[0137] In one embodiment, the attribute configuration device 1200 further includes:

[0138] The required tag configuration module is used to configure required tags for configuration objects whose attribute information is required, based on the attribute information of the first type of configuration objects.

[0139] The configuration object determination unit includes:

[0140] The configuration object determination sub-unit is used to obtain configuration objects with non-mandatory attributes from the first type of configuration objects based on the required tags.

[0141] In one embodiment, the first determining module 1240 includes:

[0142] The mapping relationship acquisition unit is used to acquire the mapping relationship between the identification information of the first type of configuration object and the attribute information of the first type of configuration object;

[0143] The first determining unit is used to determine the attribute information of the first type of configuration object based on the identification information and mapping relationship of the first type of configuration object.

[0144] In one embodiment, the attribute configuration device 1200 further includes:

[0145] The judgment module is used to determine whether the configuration object includes identification information;

[0146] The first type of configuration object determination module is used to classify the configuration object into the first type of configuration object if the configuration object includes identification information;

[0147] The second-class configuration object determination module is used to classify configuration objects into the second-class configuration objects if the configuration object does not include identification information.

[0148] In one embodiment, the attribute configuration device 1200 further includes:

[0149] The module for determining configuration objects to be verified is used to identify target configuration objects whose attribute information is required and configuration objects whose attribute information is required in the first type of configuration objects as configuration objects to be verified.

[0150] The non-empty verification module is used to perform non-empty verification on the values ​​corresponding to the attribute information of the configuration object to be verified, and generate non-empty verification results.

[0151] The prompt interface generation module is used to generate a prompt interface based on the configuration object to be verified, where the non-empty verification result is empty.

[0152] Each module in the aforementioned attribute configuration device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0153] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 13As shown, this computer device includes a processor, memory, input / output interfaces (I / O), and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operating system and computer programs stored in the non-volatile storage media. The database stores attribute configuration data. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When executed by the processor, the computer program implements an attribute configuration method.

[0154] Those skilled in the art will understand that Figure 13 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0155] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0156] Retrieve the first type of configuration object and the second type of configuration object; the first type of configuration object contains identification information, while the second type of configuration object does not contain identification information;

[0157] Based on the identification information of the first type of configuration object, determine the attribute information of the first type of configuration object; the attribute information includes required attributes and optional attributes;

[0158] The configuration objects with non-mandatory attributes in the first type of configuration objects and the second type of configuration objects are taken as target configuration objects. The attribute information of the target configuration objects is determined based on the attribute indicators of the target configuration objects.

[0159] In one embodiment, configuration objects with non-mandatory attribute information in the first type of configuration objects and the second type of configuration objects are taken as target configuration objects. Based on the attribute indicators of the target configuration objects, the attribute information of the target configuration objects is determined. When the processor executes the computer program, it also performs the following steps:

[0160] Retrieve configuration objects from the first type of configuration objects whose attribute information is not required;

[0161] Use the configuration objects with non-mandatory attributes and the second type of configuration objects as the target configuration objects;

[0162] Calculate the attribute metrics of the target configuration object, and determine the attribute information of the target configuration object based on the attribute metrics; the attribute metrics include call frequency and query frequency.

[0163] In one embodiment, when calculating the attribute metrics of the target configuration object, the processor also performs the following steps when executing the computer program:

[0164] The call frequency of the target configuration object is calculated based on the total number of first applications corresponding to the target configuration object and the total number of second applications corresponding to the target configuration object; the second application is used to transmit attribute information with the target configuration object, and the first application is the application in the second application used to call the target configuration object;

[0165] The query frequency of the target configuration object is calculated based on the number of queries to the target configuration object within a preset time period and the total number of target configuration objects.

[0166] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0167] Based on the attribute information of the first type of configuration objects, configure the required tags for the configuration objects in the first type of configuration objects whose attribute information is required;

[0168] When the processor executes a computer program, it also performs the following steps after retrieving configuration objects from the first type of configuration objects whose attribute information is not required:

[0169] Based on the required tags, retrieve the configuration objects whose attribute information is not required from the first type of configuration objects.

[0170] In one embodiment, the characteristic is that, based on the identification information of the first type of configuration object, the attribute information of the first type of configuration object is determined, and the processor further implements the following steps when executing the computer program:

[0171] Obtain the mapping relationship between the identification information and attribute information of the first type of configuration object;

[0172] Based on the identification information and mapping relationship of the first type of configuration object, determine the attribute information of the first type of configuration object.

[0173] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0174] Determine whether the configuration object includes identification information;

[0175] If the configuration object includes identification information, then the configuration object is classified as a first-class configuration object;

[0176] If the configuration object does not include identification information, then the configuration object is classified as a second type of configuration object.

[0177] In one embodiment, the processor, when executing the computer program, further performs the following steps:

[0178] The target configuration object with required attributes in the target configuration object and the configuration object with required attributes in the first type of configuration object are used as the configuration objects to be verified.

[0179] Perform non-empty validation on the values ​​corresponding to the attribute information of the configuration object to be validated, and generate a non-empty validation result.

[0180] A prompt interface is generated based on the configuration object to be verified, whose non-empty verification result is empty.

[0181] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0182] Retrieve the first type of configuration object and the second type of configuration object; the first type of configuration object contains identification information, while the second type of configuration object does not contain identification information;

[0183] Based on the identification information of the first type of configuration object, determine the attribute information of the first type of configuration object; the attribute information includes required attributes and optional attributes;

[0184] The configuration objects with non-mandatory attributes in the first type of configuration objects and the second type of configuration objects are taken as target configuration objects. The attribute information of the target configuration objects is determined based on the attribute indicators of the target configuration objects.

[0185] In one embodiment, configuration objects with non-mandatory attribute information in the first type of configuration objects and the second type of configuration objects are used as target configuration objects. Based on the attribute indicators of the target configuration objects, the attribute information of the target configuration objects is determined. When the computer program is executed by the processor, the following steps are also implemented:

[0186] Retrieve configuration objects from the first type of configuration objects whose attribute information is not required;

[0187] Use the configuration objects with non-mandatory attributes and the second type of configuration objects as the target configuration objects;

[0188] Calculate the attribute metrics of the target configuration object, and determine the attribute information of the target configuration object based on the attribute metrics; the attribute metrics include call frequency and query frequency.

[0189] In one embodiment, when calculating attribute metrics of a target configuration object, the computer program, when executed by a processor, also performs the following steps:

[0190] The call frequency of the target configuration object is calculated based on the total number of first applications corresponding to the target configuration object and the total number of second applications corresponding to the target configuration object; the second application is used to transmit attribute information with the target configuration object, and the first application is the application in the second application used to call the target configuration object;

[0191] The query frequency of the target configuration object is calculated based on the number of queries to the target configuration object within a preset time period and the total number of target configuration objects.

[0192] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0193] Based on the attribute information of the first type of configuration objects, configure the required tags for the configuration objects in the first type of configuration objects whose attribute information is required;

[0194] When a computer program is executed by a processor, it also performs the following steps after retrieving configuration objects from the first type of configuration objects where the attribute information is not required:

[0195] Based on the required tags, retrieve the configuration objects whose attribute information is not required from the first type of configuration objects.

[0196] In one embodiment, based on the identification information of the first type of configuration object, the attribute information of the first type of configuration object is determined, and when the computer program is executed by the processor, the following steps are further implemented:

[0197] Obtain the mapping relationship between the identification information and attribute information of the first type of configuration object;

[0198] Based on the identification information and mapping relationship of the first type of configuration object, determine the attribute information of the first type of configuration object.

[0199] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0200] Determine whether the configuration object includes identification information;

[0201] If the configuration object includes identification information, then the configuration object is classified as a first-class configuration object;

[0202] If the configuration object does not include identification information, then the configuration object is classified as a second type of configuration object.

[0203] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0204] The target configuration object with required attributes in the target configuration object and the configuration object with required attributes in the first type of configuration object are used as the configuration objects to be verified.

[0205] Perform non-empty validation on the values ​​corresponding to the attribute information of the configuration object to be validated, and generate a non-empty validation result.

[0206] A prompt interface is generated based on the configuration object to be verified, whose non-empty verification result is empty.

[0207] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps:

[0208] Retrieve the first type of configuration object and the second type of configuration object; the first type of configuration object contains identification information, while the second type of configuration object does not contain identification information;

[0209] Based on the identification information of the first type of configuration object, determine the attribute information of the first type of configuration object; the attribute information includes required attributes and optional attributes;

[0210] The configuration objects with non-mandatory attributes in the first type of configuration objects and the second type of configuration objects are taken as target configuration objects. The attribute information of the target configuration objects is determined based on the attribute indicators of the target configuration objects.

[0211] In one embodiment, configuration objects with non-mandatory attribute information in the first type of configuration objects and the second type of configuration objects are used as target configuration objects. Based on the attribute indicators of the target configuration objects, the attribute information of the target configuration objects is determined. When the computer program is executed by the processor, the following steps are also implemented:

[0212] Retrieve configuration objects from the first type of configuration objects whose attribute information is not required;

[0213] Use the configuration objects with non-mandatory attributes and the second type of configuration objects as the target configuration objects;

[0214] Calculate the attribute metrics of the target configuration object, and determine the attribute information of the target configuration object based on the attribute metrics; the attribute metrics include call frequency and query frequency.

[0215] In one embodiment, when calculating attribute metrics of a target configuration object, the computer program, when executed by a processor, also performs the following steps:

[0216] The call frequency of the target configuration object is calculated based on the total number of first applications corresponding to the target configuration object and the total number of second applications corresponding to the target configuration object; the second application is used to transmit attribute information with the target configuration object, and the first application is the application in the second application used to call the target configuration object;

[0217] The query frequency of the target configuration object is calculated based on the number of queries to the target configuration object within a preset time period and the total number of target configuration objects.

[0218] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0219] Based on the attribute information of the first type of configuration objects, configure the required tags for the configuration objects in the first type of configuration objects whose attribute information is required;

[0220] When a computer program is executed by a processor, it also performs the following steps after retrieving configuration objects from the first type of configuration objects where the attribute information is not required:

[0221] Based on the required tags, retrieve the configuration objects whose attribute information is not required from the first type of configuration objects.

[0222] In one embodiment, based on the identification information of the first type of configuration object, the attribute information of the first type of configuration object is determined, and when the computer program is executed by the processor, the following steps are further implemented:

[0223] Obtain the mapping relationship between the identification information and attribute information of the first type of configuration object;

[0224] Based on the identification information and mapping relationship of the first type of configuration object, determine the attribute information of the first type of configuration object.

[0225] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0226] Determine whether the configuration object includes identification information;

[0227] If the configuration object includes identification information, then the configuration object is classified as a first-class configuration object;

[0228] If the configuration object does not include identification information, then the configuration object is classified as a second type of configuration object.

[0229] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0230] The target configuration object with required attributes in the target configuration object and the configuration object with required attributes in the first type of configuration object are used as the configuration objects to be verified.

[0231] Perform non-empty validation on the values ​​corresponding to the attribute information of the configuration object to be validated, and generate a non-empty validation result.

[0232] A prompt interface is generated based on the configuration object to be verified, whose non-empty verification result is empty.

[0233] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data shall comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0234] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0235] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0236] The above embodiments are merely illustrative of several implementation methods of this application, and their descriptions are relatively specific and detailed. However, they should not be construed as limiting the scope of this application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for configuring attributes, characterized in that, The method includes: Obtain a first type of configuration object and a second type of configuration object; the first type of configuration object contains identification information, while the second type of configuration object does not contain identification information; Based on the identification information of the first type of configuration object, the attribute information of the first type of configuration object is determined; the attribute information includes required attributes and optional attributes; The configuration objects with non-mandatory attributes in the first type of configuration objects and the second type of configuration objects are taken as target configuration objects. Based on the attribute indicators of the target configuration objects, the attribute information of the target configuration objects is determined. The step of taking the configuration objects with non-mandatory attribute information in the first type of configuration objects and the second type of configuration objects as target configuration objects, and determining the attribute information of the target configuration objects based on the attribute indicators of the target configuration objects, includes: Retrieve configuration objects from the first type of configuration objects whose attribute information is not required; The configuration object of the non-mandatory attributes and the second type of configuration object are used as the target configuration object; Calculate the attribute metrics of the target configuration object, and determine the attribute information of the target configuration object based on the attribute metrics of the target configuration object; the attribute metrics include call frequency and query frequency.

2. The method according to claim 1, characterized in that, The calculation of the attribute metrics of the target configuration object includes: The invocation frequency of the target configuration object is calculated based on the total number of first applications corresponding to the target configuration object and the total number of second applications corresponding to the target configuration object; the second application is used to transmit the attribute information with the target configuration object, and the first application is the application in the second application used to call the target configuration object; The query frequency of the target configuration object is calculated based on the number of queries to the target configuration object within a preset time period and the total number of the target configuration objects.

3. The method according to claim 1, characterized in that, The method further includes: Based on the attribute information of the first type of configuration object, configure the required tags for the configuration objects in the first type of configuration object whose attribute information is required; The step of retrieving configuration objects from the first type of configuration objects whose attribute information is a non-mandatory attribute includes: Based on the required field tag, obtain configuration objects from the first type of configuration objects whose attribute information is not required.

4. The method according to any one of claims 1-3, characterized in that, The step of determining the attribute information of the first type of configuration object based on the identification information of the first type of configuration object includes: Obtain the mapping relationship between the identification information of the first type of configuration object and the attribute information of the first type of configuration object; Based on the identification information of the first type of configuration object and the mapping relationship, the attribute information of the first type of configuration object is determined.

5. The method according to any one of claims 1-3, characterized in that, The method further includes: Determine whether the configuration object includes identification information; If the configuration object includes identification information, then the configuration object is classified as a first type of configuration object; If the configuration object does not include identification information, then the configuration object is classified as a second type of configuration object.

6. The method according to any one of claims 1-3, characterized in that, The method further includes: The target configuration object in the target configuration object whose attribute information is required, and the configuration object in the first type of configuration object whose attribute information is required, are taken as the configuration objects to be verified; Perform a non-empty check on the values ​​corresponding to the attribute information of the configuration object to be checked, and generate a non-empty check result; A prompt interface is generated based on the configuration object to be verified, whose non-empty verification result is empty.

7. An attribute configuration device, characterized in that, The device includes: The configuration object acquisition module is used to acquire a first type of configuration object and a second type of configuration object; the first type of configuration object contains identification information, while the second type of configuration object does not contain identification information. The first determining module is used to determine the attribute information of the first type of configuration object based on the identification information of the first type of configuration object; the attribute information includes required attributes and optional attributes; The second determining module is used to take the configuration objects in the first type of configuration objects whose attribute information is non-mandatory and the second type of configuration objects as target configuration objects, and determine the attribute information of the target configuration objects based on the attribute indicators of the target configuration objects; The second determining module includes: The configuration object determination unit is used to obtain configuration objects whose attribute information is a non-mandatory attribute from the first type of configuration objects; The target configuration object determination unit is used to determine the configuration object of the non-mandatory attribute and the second type of configuration object as the target configuration object; An attribute information determination unit is used to calculate the attribute indicators of the target configuration object and determine the attribute information of the target configuration object based on the attribute indicators of the target configuration object; the attribute indicators include call frequency and query frequency.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images