Product configuration management and generation method and related device
Patent Information
- Application Number
- CN202311706587.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-12-12
- Publication Date
- 2025-06-13
Smart Images
Figure CN120144169A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the technical field of network products, and particularly to a product configuration management and generation method and related devices. Background Art
[0002] There are a large number of scenario constraints in the configuration parameters and feature activation of network services or products. For example, in a configuration scenario of a wireless network device, there is a mutually exclusive constraint relationship between Parameter 1 and Parameter 2. These constraint relationships are compiled into rule codes in different languages during the product development process for subsequent verification of configuration scenarios. Currently, the formulation, review, and distribution of product configurations are basically completed manually. For example, the configuration files of devices such as network elements and base stations need to be field-researched by business experts and then designed through expert discussions and other work. After the design is completed, the configuration files also need to go through multiple verifications and reviews. The entire process not only requires a high degree of business knowledge but also takes a long time and is difficult. Thus, how to improve the generation efficiency of product configuration files is one of the problems that need to be solved urgently. Summary of the Invention
[0003] Embodiments of this application provide a product configuration management and generation method and related devices, which can extract information such as the management objects and object attributes of a product based on the intention information input by a user, and generate the configuration information of the product based on this information, thereby facilitating the improvement of the generation efficiency of product configurations.
[0004] In a first aspect, embodiments of this application provide a product configuration management and generation method, which includes:
[0005] Obtain first intention information; the first intention information is used to indicate the configuration management of a product;
[0006] Determine a first management object of the product, the attributes of the first management object, and the values of the attributes of the first management object based on the first intention information;
[0007] Generate the configuration information of the product based on the first management object, the attributes of the first management object, and the values of the attributes of the first management object.
[0008] It can be seen that in the embodiments of this application, an electronic device can, in the case of the user inputting the first intention information for configuring and managing a product, determine the first management object to be configured by the user, the attributes of the first management object, and the values of the attributes of the first management object through semantic recognition, so as to be able to generate the configuration information of the product based on the parsed first management object, the attributes of the first management object, and the values of the attributes of the first management object, without the need for manual mastery of high-difficulty domain knowledge and formulating the configuration information of the product through research, discussion, etc., thereby facilitating the improvement of the generation efficiency of the configuration information.
[0009] In a possible implementation, after generating the configuration information of the product based on the first management object, the attributes of the first management object, and the values of the attributes of the first management object, the method further includes:
[0010] Obtain the constraint rules associated with the first management object and the attributes of the first management object;
[0011] Detect whether the configuration information of the product satisfies the constraint rules associated with the first management object and the attributes of the first management object;
[0012] If the configuration information of the product satisfies the constraint rules associated with the first management object and the attributes of the first management object, load the configuration information of the product onto the product.
[0013] In this implementation, since the configuration information of the product and all the constraint rules associated with the attributes of the first management object are uniformly compiled, there is no need to repeatedly compile the configuration information according to the compilation syntax of each constraint rule during the satisfiability check, which is beneficial to improving the efficiency of the satisfiability check of the configuration information and further beneficial to improving the efficiency of configuration distribution.
[0014] In a possible implementation, the first intent information includes the first named entity of the first management object and the second named entity of the attributes of the first management object; generating the configuration information of the product based on the first management object, the attributes of the first management object, and the values of the attributes of the first management object includes:
[0015] Obtain the first canonical code of the first management object and the second canonical code of the attributes of the first management object;
[0016] Replace the first named entity in the first intent information with the first canonical code, and replace the second named entity in the first intent information with the second canonical code to obtain the second intent information;
[0017] Generate the configuration information of the product based on the second intent information.
[0018] In this implementation, the electronic device replaces the first named entity and the second named entity in the first intent information with the first canonical code of the first management object and the second canonical code of the attributes of the first management object respectively, and can obtain the second intent information that is easier for the machine to understand, so that the configuration information of the product can be generated based on the second intent information.
[0019] In a possible implementation, the method further includes:
[0020] If there are constraint rules in the constraint rules associated with the first management object and the attributes of the first management object that the configuration information of the product cannot satisfy, output the constraint rules that the configuration information of the product cannot satisfy.
[0021] In this implementation, when there are constraint rules in the database that cannot be satisfied by the generated configuration information, the electronic device can output these constraint rules so that the user can modify the first intent information to generate configuration information that satisfies the constraint rules associated with the attributes of the first management object.
[0022] In a possible implementation, before obtaining the first intent information, the method further includes:
[0023] Obtaining third intent information; the third intent information is used to indicate the generation of constraint rules for a product;
[0024] Determining a second management object of the product, the attributes of the second management object, and the attribute constraints of the attributes of the second management object based on the third intent information;
[0025] Generating constraint rules for the product based on the second management object of the product, the attributes of the second management object, and the attribute constraints of the attributes of the second management object.
[0026] In this implementation, when the user inputs third intent information for generating rules for a product, the electronic device can determine, through semantic recognition, the second management object for which the user needs to generate constraint rules, the attributes of the second management object, and the attribute constraints of the attributes of the second management object, so that it can generate constraint rules for the product based on the parsed second management object, the attributes of the second management object, and the attribute constraints, without the need for manual mastery of difficult domain knowledge and a large amount of coding knowledge to design the constraint rules for the product, which is conducive to improving the generation efficiency of the constraint rules.
[0027] In a possible implementation, the method further includes:
[0028] Performing conflict detection and redundancy detection on the generated constraint rules and the existing rules of the product;
[0029] Outputting the detection result.
[0030] In this implementation, the electronic device can use formal techniques to perform conflict detection and redundancy detection on the generated constraint rules and the existing rules of the product to ensure the accuracy of formulating the constraint rules and is conducive to improving the efficiency of the constraint rule formulation process.
[0031] In a possible implementation, if the generated constraint rules have a conflict relationship with one or more first existing rules, the detection result includes one or more first existing rules; or if the generated constraint rules have a redundancy relationship with one or more second existing rules, the detection result includes one or more second existing rules.
[0032] In this implementation, the electronic device can output existing rules that conflict with or have a redundant relationship with the generated constraint rules, so as to facilitate designers to modify or delete these rules, or modify the constraint rules according to these rules to optimize the product's constraint rules.
[0033] In a possible implementation, this method further includes:
[0034] Compiling the generated constraint rules using unified compilation to obtain the rules to be stored in the library expressed in a unified programming language;
[0035] Storing the rules to be stored in the library.
[0036] In this implementation, the generated constraint rules are all compiled uniformly before being stored in the library. When generating configuration information subsequently, only one unified compilation is required to perform satisfiability verification with the existing rules in the database. When both the rules and the configuration are uniformly compiled, it is beneficial to improve the efficiency and accuracy of subsequent satisfiability verification.
[0037] In a possible implementation, the third intent information includes the third named entity of the second management object and the fourth named entity of the attributes of the second management object; generating the constraint rules of the product based on the second management object of the product, the attributes of the second management object, and the attribute constraints of the attributes of the second management object includes:
[0038] Obtaining the third canonical code of the second management object and the fourth canonical code of the attributes of the second management object;
[0039] Replacing the third named entity in the third intent information with the third canonical code, and replacing the fourth named entity in the third intent information with the fourth canonical code to obtain the fourth intent information;
[0040] Generating the constraint rules of the product based on the fourth intent information.
[0041] In this implementation, the electronic device replaces the third named entity and the fourth named entity in the third intent information with the third canonical code of the second management object and the fourth canonical code of the attributes of the second management object respectively, and can obtain the fourth intent information that is easier for the machine to understand, so as to generate the constraint rules of the product based on the fourth intent information.
[0042] In a second aspect, an embodiment of the present application provides a product configuration management and generation device, which includes an acquisition unit and a processing unit;
[0043] The acquisition unit is used to acquire first intent information; the first intent information is used to indicate the configuration management of the product;
[0044] A processing unit, configured to determine a first management object of the product, attributes of the first management object, and values of the attributes of the first management object based on first intent information; and generate configuration information of the product based on the first management object, the attributes of the first management object, and the values of the attributes of the first management object.
[0045] In a possible implementation, the obtaining unit is further configured to obtain a constraint rule associated with the first management object and the attributes of the first management object;
[0046] The processing unit is further configured to detect whether the configuration information of the product satisfies the constraint rule associated with the first management object and the attributes of the first management object; if the configuration information of the product satisfies the constraint rule associated with the first management object and the attributes of the first management object, load the configuration information of the product onto the product.
[0047] In a possible implementation, the first intent information includes a first named entity of the first management object and a second named entity of the attributes of the first management object; in terms of generating the configuration information of the product based on the first management object, the attributes of the first management object, and the values of the attributes of the first management object, the processing unit is specifically configured to:
[0048] Obtain a first canonical code of the first management object and a second canonical code of the attributes of the first management object;
[0049] Replace the first named entity in the first intent information with the first canonical code, and replace the second named entity in the first intent information with the second canonical code to obtain second intent information;
[0050] Generate the configuration information of the product based on the second intent information.
[0051] In a possible implementation, the processing unit is further configured to:
[0052] If there is a constraint rule in the constraint rule associated with the first management object and the attributes of the first management object that the configuration information of the product cannot satisfy, output the constraint rule that the configuration information of the product cannot satisfy.
[0053] In a possible implementation, the obtaining unit is further configured to obtain third intent information; the third intent information is used to indicate the generation of the constraint rule of the product;
[0054] The processing unit is further configured to determine a second management object of the product, attributes of the second management object, and attribute constraints of the attributes of the second management object based on the third intent information; and generate the constraint rule of the product based on the second management object of the product, the attributes of the second management object, and the attribute constraints of the attributes of the second management object.
[0055] In a possible implementation, the processing unit is further configured to:
[0056] Perform conflict detection and redundancy detection on the generated constraint rules and the existing rules of the product;
[0057] Output the detection result.
[0058] In a possible implementation, if the generated constraint rules have a conflict relationship with one or more first existing rules, the detection result includes one or more first existing rules; or if the generated constraint rules have a redundancy relationship with one or more second existing rules, the detection result includes one or more second existing rules.
[0059] In a possible implementation, the processing unit is further configured to:
[0060] Compile the generated constraint rules using unified compilation to obtain the rules to be stored in the library expressed in a unified programming language;
[0061] Store the rules to be stored in the library.
[0062] In a possible implementation, the third intent information includes the third named entity of the second management object and the fourth named entity of the attributes of the second management object; in terms of generating the constraint rules of the product based on the second management object of the product, the attributes of the second management object, and the attribute constraints of the attributes of the second management object, the processing unit is specifically configured to:
[0063] Obtain the third canonical code of the second management object and the fourth canonical code of the attributes of the second management object;
[0064] Replace the third named entity in the third intent information with the third canonical code, and replace the fourth named entity in the third intent information with the fourth canonical code to obtain the fourth intent information;
[0065] Generate the constraint rules of the product based on the fourth intent information.
[0066] It should be understood that since the method embodiment and the device embodiment are different presentation forms of the same technical concept, the content of the first aspect of the embodiments of the present application should be synchronously adapted to the second aspect of the embodiments of the present application, and can achieve the same or similar beneficial effects, which will not be elaborated here.
[0067] In a third aspect, the embodiments of the present application provide an electronic device, including a processor, a memory, a communication interface, and one or more programs, where the one or more programs are stored in the memory and are configured to cooperate with the communication interface to implement the method in any one of the embodiments of the first aspect when executed by the processor.
[0068] Fourthly, an embodiment of the present application provides a chip, including: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method in any one of the embodiments of the first aspect above.
[0069] Fifthly, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program for a device to execute, and when the computer program is executed, it implements the method in any one of the embodiments of the first aspect above.
[0070] Sixthly, an embodiment of the present application provides a computer program product, when the computer program product is run on a device, so that the device executes the method in any one of the embodiments of the first aspect above. Description of the Drawings
[0071] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the background art, the following will describe the drawings required to be used in the embodiments of the present application or the background art.
[0072] Figure 1 It is a schematic diagram of the formulation, verification, and storage of constraint rules in a related art;
[0073] Figure 2 It is a schematic diagram of the formulation, verification, and distribution of configurations in a related art;
[0074] Figure 3 It is a schematic diagram of a system architecture provided by an embodiment of the present application;
[0075] Figure 4 It is a schematic flowchart of a product configuration management and generation method provided by an embodiment of the present application;
[0076] Figure 5 It is a schematic diagram of generating and managing configuration information based on a software system architecture provided by an embodiment of the present application;
[0077] Figure 6 It is a schematic overall flowchart of generating, verifying, and distributing configuration information provided by an embodiment of the present application;
[0078] Figure 7 It is a schematic flowchart of another product configuration management and generation method provided by an embodiment of the present application;
[0079] Figure 8 It is a schematic diagram of generating and managing constraint rules based on a software system architecture provided by an embodiment of the present application;
[0080] Figure 9 It is a schematic overall flowchart of generating, verifying, and storing constraint rules provided by an embodiment of the present application;
[0081] Figure 10 This is a schematic structural diagram of a product configuration management and generation device provided by an embodiment of the present application;
[0082] Figure 11 This is a schematic structural diagram of an electronic device provided by an embodiment of the present application. Detailed implementation manners
[0083] Terms such as "first", "second", "third", and "fourth" in the specification, claims, and drawings of the present application are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but optionally further includes steps or units not listed, or optionally further includes other steps or units inherent to these processes, methods, products, or devices.
[0084] Referring to "embodiment" herein means that a specific feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the present application. The phrase appears in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment mutually exclusive with other embodiments. Those skilled in the art will explicitly and implicitly understand that the embodiments described herein can be combined with other embodiments.
[0085] The terms "component", "module", "system", etc. used in this specification are used to represent computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. By way of illustration, an application running on a terminal device and the terminal device can both be components. One or more components can reside in a process and / or an execution thread, and the components can be located on one computer and / or distributed between two or more computers. In addition, these components can execute from various computer-readable media storing various data structures. The components can communicate, for example, through local and / or remote processes according to a signal having one or more data packets (such as data from two components interacting with each other in a local system, a distributed system, and / or a network, such as the Internet interacting with other systems through a signal).
[0086] First, relevant terms and relevant technical backgrounds in the present application are briefly introduced to facilitate understanding by those skilled in the art.
[0087] Object Configuration;
[0088] Configuration Constraints Rules;
[0089] Managed Object Class, MOC; The type of object to be managed, such as the wireless configuration management object type;
[0090] Managed Object Instance, MOI; The instance of the object to be managed, such as the wireless configuration management object instance;
[0091] aim / goal; Specifically refers to the goal to be achieved, which may not include the detailed steps required to achieve the goal;
[0092] description; Refers to a detailed description of a process, including the steps or operations in the process.
[0093] In the scenario of wireless network device configuration, with the rapid development and application of the 5th Generation Mobile Communication Technology (5G), new wireless network devices are constantly being introduced. Coupled with the existing wireless network devices, it has led to a complex situation of various types, systems, and combinations of new and old hardware in the configuration operation and maintenance of wireless network devices. This has brought huge challenges to the formulation, verification, and distribution of configuration data, seriously affecting the site operation and maintenance efficiency.
[0094] With the introduction of some large language models, related research has proposed the idea of using such models to formulate the configuration constraints rules and configuration information of wireless network devices. Although large language models have strong language perception and logical reasoning abilities, they are basically trained with general language materials and lack knowledge in the field of wireless network device configuration, making it difficult to efficiently complete tasks such as formulating and verifying configuration constraints rules and configuration information. In addition, they have certain requirements for time and computing power, and the usage cost is relatively high. Existing large language model tools are mostly generative models, which are greatly limited in the number of inferences and inference speed, and it is difficult to meet the efficiency requirements of the business.
[0095] The formulation and verification of the existing device configuration constraints rules and other tasks are basically completed manually. Since different device configurations involve different domain knowledge, and the constraints rules may be described using different program grammars in different scenarios, relevant personnel need to master a relatively high level of domain knowledge and coding knowledge. As Figure 1 shown, the process of formulating, verifying, and storing the constraints rules may include the following steps:
[0096] (1) Designers first need to design rules based on experience and collect test case data for testing and validating the rules.
[0097] (2) Developers write rule scripts according to the rule syntax and test and validate the correctness of the rule scripts based on the case data.
[0098] (3) After passing the test and validation, it is necessary to use software parameters and hardware constraint cases to validate the rule scripts.
[0099] (4) After passing the instance validation, it is necessary to conduct rule reviews and summary reports. After the reviews are passed, the generated rules will be stored in the database.
[0100] Constraint rules are usually stored in the form of compiled scripts. The description grammars of the scripts used for compiling rules in different regions and different systems are inconsistent, including various description grammars such as natural language, Extensible Markup Language (XML) files, Lua scripts, Object Constraint Language (OCL), etc. There is no unified rule syntax expression for constraint rules. Different regional network points use different grammars for rule formulation and need to adapt to different compilers. There may be a situation of repeated compilation of rules in different languages during rule calculation, and the calculation efficiency is relatively low. A large number of constraint rules are reviewed manually during the formulation process, and it is difficult to accurately evaluate the legality and effectiveness of the rules. Moreover, in the presence of a large number of existing rules, it is very time-consuming to conduct redundancy detection and conflict detection manually, and it is difficult to efficiently and accurately detect redundant or conflicting rules and clean or modify them.
[0101] The formulation, verification, and distribution of existing device configuration files are mainly completed manually. As Figure 2 shown, the process of formulating, verifying, and distributing device configurations can include the following steps:
[0102] a. Relevant personnel write configuration scripts based on experience and the syntax specifications of device configurations.
[0103] b. Multilingual compilation is performed on the generated configuration information based on multiple compilation languages adopted by the constraint rules (such as: Rule Script Compilation Language A, Rule Script Compilation Language B... Rule Script Compilation Language N), and the satisfiability verification is performed on the compiled configuration information and the constraint
[0104] rules in the database.
[0105] c. After passing the verification, the configuration design plan is approved, and after the approval is passed, the configuration is distributed to the device to take effect.
[0106] Since the configuration of wireless network devices requires relatively high domain expertise, the design of configuration files requires on-site research and discussion by designers, resulting in high design difficulty. On the other hand, existing rules are compiled and stored in script files of different specifications, and the rule language contains different grammars. In order to perform matching verification between a configuration file and related constraint rules, the configuration file needs to be adapted to different grammar rules for compilation and verification, resulting in low verification efficiency. After multiple verifications, the configuration plan still needs to be manually reviewed to finally confirm whether to issue it, and the efficiency of approval and issuance is not high either.
[0107] To overcome the deficiencies and defects of the prior art, the present application proposes a product configuration management and generation method, which can be implemented based on Figure 3 the system architecture shown. As Figure 3 shown, the system architecture mainly includes a rule design module, an operation and maintenance module, and an operator network module. Among them, the rule design module provides a rule designer, which includes a rule design description module, an intention recognition and extraction module, and a constraint rule generation module. The rule design description module is used for rule design user input management object description, object attribute description, and attribute constraint description. The intention recognition and extraction module is used to extract key information of rule management objects, management object attributes, and attribute constraint descriptions based on the input of rule design users, and then transfer them to the model transfer engine for verification of management objects and object attributes through the model transfer engine. After successful verification, it is returned to the constraint rule generation module to generate constraint rules. The model transfer engine will perform conflict and redundancy detection and simulation testing on the constraint rules generated by module C again. Users can modify or re-design the rules through the rule design module according to the detection and test results, and the model transfer engine will publish the verified constraint rules into the database. The operation and maintenance party inputs configuration change / configuration generation information in the operation and maintenance module. The configuration generation unit extracts the key information in the configuration change / configuration generation and generates the configuration information of the device based on this key information. The unified rule verification unit queries the rules from the database and performs satisfiability verification on the generated configuration information and the constraint rules returned by the query. The configuration management unit can modify the generated configuration information or configuration change / configuration generation information based on the results of the satisfiability verification. Exemplarily, the operation and maintenance module can run in the cloud or locally. The operator network module provides networking services, and the configuration distribution unit loads the verified configuration information onto the device to take effect.
[0108] The technical solution provided by the present application will be introduced in detail below in combination with specific embodiments.
[0109] Please refer to Figure 4 , Figure 4 which is a schematic flowchart of a product configuration management and generation method provided by an embodiment of the present application, and this method can be based on Figure 3The system architecture implementation shown can be specifically executed by an electronic device. For example, Figure 4 as shown, the method includes steps 401 - 403:
[0110] 401: Obtain first intent information; the first intent information is used to indicate configuration management of a product.
[0111] In the embodiments of the present application, the product can be a hardware product (such as a wireless network device) or a software product. The first intent information may include a first named entity of the first management object of the product, a second named entity of the attribute of the first management object, and the value of the attribute of the first management object. The first intent information can be for configuration change, configuration optimization, configuration generation, etc. of the first management object of the product. For example: the user inputs "Set the positioning function of module X to 1". Among them, the first management object refers to the management object that the user currently wants to configure. Exemplarily, the first intent information can be a natural language description input by the user, such as: it can be text or voice, etc. Exemplarily, the user can input the first intent information through the electronic device in the operation and maintenance module of the configuration unified verification technology system.
[0112] 402: Determine the first management object of the product, the attribute of the first management object, and the value of the attribute of the first management object based on the first intent information.
[0113] In the embodiments of the present application, the electronic device can perform semantic recognition on the first intent information through a language model, and parse out the first management object, the attribute of the first management object, and the value of the attribute of the first management object included in the first intent information. Exemplarily, as Figure 5 shown, the configuration generation unit in the operation and maintenance module of the configuration unified verification technology system performs semantic recognition by calling the language model, and parses out three parts: the first management object, the attribute of the first management object, and the value of the attribute of the first management object based on the semantic recognition result.
[0114] 403: Generate configuration information of the product based on the first management object, the attribute of the first management object, and the value of the attribute of the first management object.
[0115] In the embodiments of the present application, as Figure 5 shown, based on the parsed first management object, the attribute of the first management object, and the value of the attribute of the first management object, the electronic device can generate corresponding configuration information through the configuration generation unit. Exemplarily, the configuration information exists in the form of a configuration script or a configuration file. Exemplarily, the configuration information can be obtained through unified compilation. For example: it is compiled using a unified compilation language or a unified syntax specification, and the compilation language or syntax specification is the same as that of the constraint rules in the database, that is, the configuration information of the product and the existing rules in the database are both obtained through unified compilation.
[0116] Exemplarily, after the electronic device parses out the first management object, the attributes of the first management object, and the values of the attributes of the first management object, it will also obtain the first canonical code of the first management object and the second canonical code of the attributes of the first management object. Specifically, based on product knowledge, all associated management objects associated with the product and the attributes of all associated management objects are queried from the database first, and then it is verified whether the first management object exists among these associated management objects and whether the attributes of the first management object exist among the attributes of the associated management objects, and the verification result is returned. If the first management object and the attributes of the first management object exist, all associated first canonical codes of the first management object and all associated second canonical codes of the attributes of the first management object are returned. If the first management object does not exist, verification failure is returned, and the configuration information creation is invalid. In the case of obtaining the first canonical code and the second canonical code, the electronic device replaces the first named entity in the first intent information with the first canonical code, and replaces the second named entity in the first intent information with the second canonical code to obtain the second intent information, where the second intent information refers to the replaced intent information. For example: the first canonical code of the X module is "MOC1Cell", and the second canonical code of the positioning function is "location_func", then the electronic device can replace the named entities in the first intent information with these canonical codes, and generate configuration information based on the first canonical code, the second canonical code, and the value content of the attributes in the second intent information.
[0117] In this implementation manner, the electronic device replaces the first named entity and the second named entity in the first intent information with the first canonical code of the first management object and the second canonical code of the attributes of the first management object respectively, and can obtain the second intent information that is easier for the machine to understand, so that the configuration information of the product can be generated based on the second intent information.
[0118] Exemplarily, after generating the configuration information of the product based on the first management object, the attributes of the first management object, and the values of the attributes of the first management object, the method further includes:
[0119] Obtain the constraint rules associated with the first management object and the attributes of the first management object;
[0120] Detect whether the configuration information of the product satisfies the constraint rules associated with the first management object and the attributes of the first management object;
[0121] If the configuration information of the product satisfies the constraint rules associated with the first management object and the attributes of the first management object, load the configuration information of the product onto the product.
[0122] In the embodiments of the present application, as Figure 5As shown in the figure, the electronic device can use the parsed first management object and the attributes of the first management object to retrieve in the database through the unified rule verification unit to obtain all the constraint rules associated with the first management object and the attributes of the first management object, and then detect whether the generated configuration information meets these constraint rules, that is, perform satisfiability verification. If the satisfiability verification passes, that is, the configuration information of the product meets all the constraint rules associated with the first management object and the attributes of the first management object, the electronic device performs configuration distribution through the configuration distribution unit, that is, loads the configuration information of the product onto the product.
[0123] In this implementation, since the configuration information of the product and all the constraint rules associated with the first management object and the attributes of the first management object are compiled uniformly, there is no need to recompile the configuration information according to the compilation syntax of each constraint rule during the satisfiability verification, which is beneficial to improving the efficiency of the satisfiability verification of the configuration information, and thus beneficial to improving the efficiency of configuration distribution.
[0124] Exemplarily, if there are constraint rules that the configuration information of the product cannot meet among the constraint rules associated with the first management object and the attributes of the first management object, it returns that the verification fails and outputs the constraint rules that the configuration information of the product cannot meet, so that the user can modify the first intent information based on this constraint rule and regenerate the configuration information of the product based on the modified intent information, or directly modify the generated configuration information. Optionally, the script identifier corresponding to the constraint rule that the configuration information of the product cannot meet can also be output, so that the user can quickly find the script corresponding to this constraint rule based on this script identifier.
[0125] In this implementation, when there are constraint rules in the database that the generated configuration information cannot meet, the electronic device can output this constraint rule, so that the user can modify the first intent information to generate configuration information that meets the constraint rules associated with the attributes of the first management object.
[0126] It can be seen that in the embodiment of the present application, when the electronic device receives the first intent information for configuring and managing the product input by the user, it can determine the first management object to be configured by the user, the attributes of the first management object, and the values of the attributes of the first management object through semantic recognition, so as to be able to generate the configuration information of the product based on the parsed first management object, the attributes of the first management object, and the values of the attributes of the first management object, without the need for manual mastery of difficult domain knowledge and formulating the configuration information of the product through research, discussion, etc., which is beneficial to improving the generation efficiency of the configuration information.
[0127] To better understand this solution, the overall process of generating, verifying, and distributing the configuration information of the product is briefly described below, as Figure 6As shown, it includes the following steps:
[0128] A0. The user enters the configuration design page;
[0129] A1. The user inputs the intention of device configuration change or addition based on natural language. This intention includes the management object of the device, the attributes of the management object, and the attribute values;
[0130] A2. The configuration generation unit performs semantic perception according to the user intention, and parses out the three parts of the management object, the attributes of the management object, and the attribute values in the intention;
[0131] A3. The configuration generation unit obtains all associated objects and attributes according to the above parsing results and device knowledge;
[0132] A4. The configuration generation unit sends a request to the database engine through the rule generation engine to verify the management object and the attributes of the management object;
[0133] A5. The database engine returns the verification result. If the verification passes, it returns the standard encoding of the management object and the attributes of the management object; otherwise, it returns verification failure and the configuration information creation is invalid;
[0134] A6. The configuration generation unit uses the standard encoding to replace the management object and the attributes of the management object in the natural language according to the verification result, and generates the specific configuration of the device according to the description of the attribute values;
[0135] B1. After the user confirms the generated configuration, the unified rule verification unit sends a request to the database engine according to the attributes of the management object to query the relevant constraint rules involved, and performs the satisfiability verification between the configuration and the constraint rules;
[0136] B2. The unified rule verification unit returns the verification result and the generated specific configuration. If the verification fails, it returns the specific unsatisfied rules and the script identifier of the unsatisfied rules; the user modifies the configuration and iterates steps A1 - B1 according to the feedback; if the verification passes, it executes C1.
[0137] C1. After the user confirms the configuration generation result, the configuration is sent down through the configuration sending unit, and the configuration takes effect on the device.
[0138] Please refer to Figure 7 , Figure 7 which is the flow schematic diagram of a product configuration management and generation method provided by an embodiment of the present application. As Figure 7 shown, the method includes steps 701 - 709:
[0139] 701: Obtain the third intention information; the third intention information is used to indicate the constraint rules for generating the product.
[0140] In the embodiments of the present application, the third intention information may include the third named entity of the second management object of the product, the fourth named entity of the attributes of the second management object, and the attribute constraints of the attributes of the second management object. For example, a rule designer inputs "When the positioning function starts in the xx module of the community, the scheduling function must be turned off". Here, the second management object refers to the management object involved in the configuration information of the constraints for which the product needs to generate constraint rules. For example, the second management object may be the first management object or a management object other than the first management object. Exemplarily, the third intention information may be a natural language description input by the designer, such as text or voice, etc. Exemplarily, the designer can input the third intention information through an electronic device in the rule design module of the configuration unified verification technology system.
[0141] 702: Determine the second management object of the product, the attributes of the second management object, and the attribute constraints of the attributes of the second management object based on the third intention information.
[0142] In the embodiments of the present application, the electronic device can perform semantic recognition on the third intention information through a language model and parse out the second management object, the attributes of the second management object, and the attribute constraints of the attributes of the second management object included in the third intention information. For example:
[0143] Second management object: xx module;
[0144] Attributes of the second management object: positioning function, scheduling function;
[0145] Attribute constraint: When the positioning function starts, the scheduling function must be turned off.
[0146] Exemplarily, as Figure 8 shown, the rule designer in the rule design module of the configuration unified verification technology system calls the language model for semantic recognition and parses out three parts: the second management object, the attributes of the second management object, and the attribute constraints of the attributes of the second management object based on the semantic recognition result.
[0147] 703: Generate the constraint rules of the product based on the second management object of the product, the attributes of the second management object, and the attribute constraints of the attributes of the second management object.
[0148] In the embodiments of the present application, as Figure 8 shown, based on the parsed second management object, the attributes of the second management object, and the attribute constraints of the attributes of the second management object, the electronic device can generate corresponding constraint rules through the rule designer. Exemplarily, the constraint rules exist in the form of rule scripts. Based on certain compilation grammars and using certain compilation rules, the constraint rule script of the product is compiled.
[0149] In this implementation, when the electronic device receives the third intention information input by the user for rule generation of the product, it can determine, through semantic recognition, the second management object for which the user needs to generate constraint rules, the attributes of the second management object, and the attribute constraints of the attributes of the second management object, so as to be able to generate the constraint rules of the product based on the parsed second management object, the attributes of the second management object, and the attribute constraints, without the need for manual mastery of difficult domain knowledge and a large amount of coding knowledge to design the constraint rules of the product, which is conducive to improving the generation efficiency of the constraint rules.
[0150] Exemplarily, after parsing out the second management object, the attributes of the second management object, and the attribute constraints of the attributes of the second management object, the electronic device also obtains the third standard code of the second management object and the fourth standard code of the attributes of the second management object through a rule designer. Specifically, based on the second management object and the attributes of the second management object, a fuzzy match is performed in the database to determine whether the second management object and the attributes of the second management object exist in the database, and the verification result is returned. If the second management object and the attributes of the second management object exist, the third standard code of the second management object and the fourth standard code of the attributes of the second management object are returned. For example:
[0151] Standard code of xx module: MOC2Cell;
[0152] Standard code of the positioning function of xx module: location_func;
[0153] Standard code of the scheduling function of xx module: schedule_func.
[0154] When the third standard code and the fourth standard code are obtained, the electronic device replaces the third named entity in the third intention information with the third standard code, and replaces the fourth named entity in the third intention information with the fourth standard code, to obtain the fourth intention information, where the fourth intention information refers to the replaced intention information. The electronic device generates the constraint rules of the product based on the third standard code, the fourth standard code, and the attribute constraints in the fourth intention information.
[0155] In this implementation, by using the third standard code of the second management object and the fourth standard code of the attributes of the second management object to replace the third named entity and the fourth named entity in the third intention information respectively, the electronic device can obtain the fourth intention information that is easier for the machine to understand, so as to be able to generate the constraint rules of the product based on the fourth intention information.
[0156] Exemplarily, the method further includes:
[0157] Performing conflict detection and redundancy detection on the generated constraint rules and the existing rules of the product;
[0158] Output the detection result.
[0159] Exemplarily, as Figure 8 shown, the electronic device can perform conflict detection and redundancy detection on the generated constraint rules and the existing rules of the product through the rule verification unit, and output the detection result through the rule verification unit.
[0160] In this implementation manner, the electronic device can use formal techniques to perform conflict detection and redundancy detection on the generated constraint rules and the existing rules of the product, so as to ensure the accuracy of formulating the constraint rules and is beneficial to improving the efficiency of the constraint rule formulation process.
[0161] Exemplarily, if the generated constraint rule has a conflict relationship with one or more first existing rules, the detection result includes one or more first existing rules; or if the generated constraint rule has a redundancy relationship with one or more second existing rules, the detection result includes one or more second existing rules.
[0162] In the embodiments of the present application, the electronic device outputs one or more first existing rules that conflict with the generated constraint rules and one or more second existing rules that have a redundancy relationship with the generated constraint rules through the rule verification unit. For one or more first existing rules, the rule designer can modify them, or based on one or more first existing rules and the corresponding redundancy or conflict relationship, the rule designer can modify the third intent information or directly modify the generated constraint rules. As Figure 8 shown, for one or more second existing rules, the rule verification unit provides a one-key cleaning and selective deletion function to sort and summarize the constraint rules of the product. Based on the rule designer's trigger of the one-key cleaning function, the electronic device can delete one or more second existing rules; based on the rule designer's selection of some or all of the one or more second existing rules, the electronic device can delete the selected part or all of the second existing rules.
[0163] In this implementation manner, the electronic device can output the existing rules that conflict with or have a redundancy relationship with the generated constraint rules, so as to facilitate the designer to modify or delete these rules, or modify the constraint rules according to these rules to optimize the constraint rules of the product.
[0164] Exemplarily, as Figure 8 shown, the electronic device can also perform simulation detection on the generated constraint rules through the rule verification unit, that is, detect whether the generated constraint rules have an impact on the existing rules of the product through simulation technology.
[0165] Exemplarily, as Figure 8As shown, based on the results of conflict detection, redundancy detection, and simulation detection, the electronic device can display all the constraint rules of the product and the relationships between the constraint rules in the form of a topology diagram, that is, visualize all the constraint rules and the relationships between the constraint rules. The nodes in the topology diagram can represent the corresponding constraint rules, and the edges between the nodes can represent the relationships between the corresponding constraint rules.
[0166] Exemplarily, as Figure 8 shown, after the rule designer modifies the conflict rules and clears the redundant rules, the electronic device will compile the generated constraint rules using unified compilation to obtain the rules to be stored in the database with a unified syntax representation, and store the rules to be stored in the database. Among them, unified compilation means expressing the generated constraint rules using a unified rule syntax. Exemplarily, if there are no one or more first existing rules with conflicts and no one or more second existing rules with redundant relationships in the generated constraint rules, the electronic device directly compiles the generated constraint rules using unified compilation to obtain the rules to be stored in the database with a unified programming language representation, and stores the rules to be stored in the database.
[0167] In this implementation method, the generated constraint rules are all compiled uniformly before being stored in the database. When generating configuration information later, only one unified compilation is required to perform satisfiability verification with the existing rules in the database. In the case where both the rules and the configuration are uniformly compiled, it is beneficial to improve the efficiency and accuracy of subsequent satisfiability verification.
[0168] To better understand this solution, the overall process of generating, verifying, and storing the constraint rules of the product is briefly described below, as Figure 9 shown, including the following steps:
[0169] 0. The designer enters the rule formulation page;
[0170] 1. The rule designer prompts to input the intention information for generating the constraint rules of the product;
[0171] 2. The designer inputs the intention of formulating the constraint rules based on natural language, and this intention includes the management object of the device, the attributes of the management object, and the language description of the attribute constraints;
[0172] 3. The rule designer parses the management object, the attributes of the management object, and the three parts of the attribute constraints in the rule description through a language large model according to the user's natural language rule description;
[0173] 4. The rule designer sends a request to the database engine to verify the management object of the device and the attributes of the management object to verify whether there are standard management objects and attributes that match this attribute in the database;
[0174] 5. The database engine returns the verification result. If the verification passes, it returns the management object and the standard code of the attributes of the management object; otherwise, it returns verification failure and the constraint rule creation is invalid.
[0175] 6. Based on the verification result, the rule designer replaces the management object and the attributes of the management object in the natural language with the standard code, and generates the constraint rules for the device according to the attribute constraints of the attributes.
[0176] 7. The rule verification unit detects relationships such as conflicts and redundancies between the newly added rules and the existing rules, and conducts simulation detection, and outputs the detection result in the form of a topology graph.
[0177] 8. The rule verification unit returns the detection result and the generated constraint rules. If there are rules in the existing rules that conflict with the generated constraint rules or have a redundant relationship with the generated constraint rules, the detection result includes the conflicting rule or the redundant rule.
[0178] 9. According to the detection result, the designer can selectively delete the redundant rules or modify the conflicting rules; the designer can also select the one-key clearing function, and the rule verification unit automatically deletes all redundant rules according to the redundancy result.
[0179] 10. The designer confirms to add this rule.
[0180] 11. The rule designer uniformly compiles the rules through the storage function and stores them in the rule database.
[0181] 704: Obtain the first intent information; the first intent information is used to indicate the configuration management of the product.
[0182] 705: Determine the first management object of the product, the attributes of the first management object, and the value of the attributes of the first management object based on the first intent information.
[0183] 706: Generate the configuration information of the product based on the first management object, the attributes of the first management object, and the value of the attributes of the first management object.
[0184] 707: Obtain the constraint rules associated with the first management object and the attributes of the first management object.
[0185] 708: Detect whether the configuration information of the product meets the constraint rules associated with the first management object and the attributes of the first management object.
[0186] 709: If the configuration information of the product meets the constraint rules associated with the first management object and the attributes of the first management object, load the configuration information of the product onto the product.
[0187] Among them, the specific implementation methods of steps 704 - 709 are inFigure 4 As described in the embodiments shown, and the same or similar beneficial effects can be achieved, so details are not repeated here. It should be noted that the generation and management of constraint rules and the generation and management of configuration information can be executed by the same electronic device or by different electronic devices.
[0188] Please refer to Figure 10 , Figure 10 which is a schematic structural diagram of a product configuration management and generation device provided by an embodiment of the present application. As Figure 10 shown, the device may include an acquisition unit 1001 and a processing unit 1002; where:
[0189] The acquisition unit 1001 is configured to acquire first intention information; the first intention information is used to indicate the configuration management of a product.
[0190] The processing unit 1002 is configured to determine a first management object of the product, an attribute of the first management object, and a value of the attribute of the first management object based on the first intention information; generate configuration information of the product based on the first management object, the attribute of the first management object, and the value of the attribute of the first management object.
[0191] It can be seen that in the Figure 10 shown device, when the user inputs the first intention information for configuring and managing the product, the first management object to be configured by the user, the attribute of the first management object, and the value of the attribute of the first management object can be determined through semantic recognition, so that the configuration information of the product can be generated based on the parsed first management object, the attribute of the first management object, and the value of the attribute of the first management object, without the need for manual mastery of difficult domain knowledge and formulating the configuration information of the product through research, discussion, etc., which is conducive to improving the generation efficiency of the configuration information.
[0192] In a possible implementation manner, the acquisition unit 1001 is further configured to acquire a constraint rule associated with the first management object and the attribute of the first management object;
[0193] The processing unit 1002 is further configured to detect whether the configuration information of the product satisfies the constraint rule associated with the first management object and the attribute of the first management object; if the configuration information of the product satisfies the constraint rule associated with the first management object and the attribute of the first management object, load the configuration information of the product onto the product.
[0194] In a possible implementation manner, the first intention information includes a first named entity of the first management object and a second named entity of the attribute of the first management object; in terms of generating the configuration information of the product based on the first management object, the attribute of the first management object, and the value of the attribute of the first management object, the processing unit 1002 is specifically configured to:
[0195] Obtain the first canonical code of the first management object and the second canonical code of the attributes of the first management object;
[0196] Replace the first named entity in the first intent information with the first canonical code, and replace the second named entity in the first intent information with the second canonical code to obtain the second intent information;
[0197] Generate the configuration information of the product based on the second intent information.
[0198] In a possible implementation manner, the processing unit 1002 is further configured to:
[0199] If there is a constraint rule that the configuration information of the product cannot satisfy among the constraint rules associated with the first management object and the attributes of the first management object, output the constraint rule that the configuration information of the product cannot satisfy.
[0200] In a possible implementation manner, the obtaining unit 1001 is further configured to obtain the third intent information; the third intent information is used to indicate generating the constraint rules of the product;
[0201] The processing unit 1002 is further configured to determine the second management object of the product, the attributes of the second management object, and the attribute constraints of the attributes of the second management object based on the third intent information; generate the constraint rules of the product based on the second management object of the product, the attributes of the second management object, and the attribute constraints of the attributes of the second management object.
[0202] In a possible implementation manner, the processing unit 1002 is further configured to:
[0203] Perform conflict detection and redundancy detection on the generated constraint rules and the existing rules of the product;
[0204] Output the detection result.
[0205] In a possible implementation manner, if the generated constraint rules have a conflict relationship with one or more first existing rules, the detection result includes one or more first existing rules; or if the generated constraint rules have a redundancy relationship with one or more second existing rules, the detection result includes one or more second existing rules.
[0206] In a possible implementation manner, the processing unit 1002 is further configured to:
[0207] Compile the generated constraint rules using unified compilation to obtain the rules to be stored in the unified programming language representation;
[0208] Store the rules to be stored.
[0209] In a possible implementation, the third intent information includes a third named entity of the second management object and a fourth named entity of the attributes of the second management object; in terms of generating a constraint rule for the product based on the second management object of the product, the attributes of the second management object, and the attribute constraints of the attributes of the second management object, the processing unit 1002 is specifically configured to:
[0210] Obtain a third specification code of the second management object and a fourth specification code of the attributes of the second management object;
[0211] Replace the third named entity in the third intent information with the third specification code, and replace the fourth named entity in the third intent information with the fourth specification code to obtain fourth intent information;
[0212] Generate a constraint rule for the product based on the fourth intent information.
[0213] It should be noted that Figure 10 The implementation of each described unit can also be correspondingly referred to Figures 4 to 9 The corresponding description of the illustrated embodiment. And Figure 10 The beneficial effects brought by the described communication device can be referred to Figures 4 to 9 The corresponding description of the illustrated embodiment, and will not be repeated here.
[0214] Based on the descriptions of the above method embodiments and device embodiments, an embodiment of the present application further provides an electronic device. Please refer to Figure 11 , Figure 11 FIG. is a schematic structural diagram of an electronic device provided by an embodiment of the present application. The electronic device at least includes a processor 1101, a memory 1102, and a communication interface 1103. The processor 1101, the memory 1102, and the communication interface 1103 are interconnected through a bus 1104. The electronic device can be used to execute the relevant steps of the product configuration management and generation method. The electronic device can be a device running a configuration unified verification technology system or a chip in the device. The processor 1101 in the electronic device is used to read the computer program code stored in the above memory 1102 and execute Figures 4 to 9 The method of any one of the illustrated embodiments.
[0215] The memory 1102 includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read only memory (EPROM), or a compact disc read-only memory (CD-ROM). The memory 1102 is used to store relevant computer programs and data.
[0216] The processor 1101 can be one or more central processing units (CPUs). When the processor 1101 is a single CPU, it can be a single-core CPU or a multi-core CPU.
[0217] Exemplarily, the processor 1101 in the electronic device can be used to read one or more programs stored in the above-mentioned memory 1102 and perform the following operations:
[0218] Obtain first intent information; the first intent information is used to indicate configuration management of a product;
[0219] Determine a first management object of the product, attributes of the first management object, and values of the attributes of the first management object based on the first intent information;
[0220] Generate configuration information of the product based on the first management object, attributes of the first management object, and values of the attributes of the first management object.
[0221] In a possible implementation, after generating the configuration information of the product based on the first management object, attributes of the first management object, and values of the attributes of the first management object, the processor 1101 is further used to:
[0222] Obtain constraint rules associated with the first management object and attributes of the first management object;
[0223] Detect whether the configuration information of the product meets the constraint rules associated with the first management object and attributes of the first management object;
[0224] If the configuration information of the product meets the constraint rules associated with the first management object and attributes of the first management object, load the configuration information of the product onto the product.
[0225] In a possible implementation, the first intent information includes a first named entity of a first management object and a second named entity of an attribute of the first management object; the processor 1101 executes to generate configuration information of a product based on the first management object, the attribute of the first management object, and the value of the attribute of the first management object, including:
[0226] Obtain a first specification code of the first management object and a second specification code of the attribute of the first management object;
[0227] Replace the first named entity in the first intent information with the first specification code, and replace the second named entity in the first intent information with the second specification code to obtain second intent information;
[0228] Generate configuration information of the product based on the second intent information.
[0229] In a possible implementation, the processor 1101 is further configured to:
[0230] If there is a constraint rule that the configuration information of the product cannot satisfy among the constraint rules associated with the first management object and the attribute of the first management object, output the constraint rule that the configuration information of the product cannot satisfy.
[0231] In a possible implementation, before obtaining the first intent information, the processor 1101 is further configured to:
[0232] Obtain third intent information; the third intent information is used to indicate the generation of constraint rules of the product;
[0233] Determine a second management object of the product, an attribute of the second management object, and an attribute constraint of the attribute of the second management object based on the third intent information;
[0234] Generate constraint rules of the product based on the second management object of the product, the attribute of the second management object, and the attribute constraint of the attribute of the second management object.
[0235] In a possible implementation, the processor 1101 is further configured to:
[0236] Perform conflict detection and redundancy detection on the generated constraint rules and the existing rules of the product;
[0237] Output the detection result.
[0238] In a possible implementation, if the generated constraint rules have a conflict relationship with one or more first existing rules, the detection result includes one or more first existing rules; or if the generated constraint rules have a redundancy relationship with one or more second existing rules, the detection result includes one or more second existing rules.
[0239] In a possible implementation, the processor 1101 is further configured to:
[0240] Compile the generated constraint rules through unified compilation to obtain the rules to be stored in a unified programming language representation;
[0241] Store the rules to be stored.
[0242] In a possible implementation, the third intent information includes a third named entity of the second management object and a fourth named entity of the attribute of the second management object; the processor 1101 executes to generate constraint rules of the product based on the second management object of the product, the attribute of the second management object, and the attribute constraint of the attribute of the second management object, including:
[0243] Obtain a third canonical code of the second management object and a fourth canonical code of the attribute of the second management object;
[0244] Replace the third named entity in the third intent information with the third canonical code, and replace the fourth named entity in the third intent information with the fourth canonical code to obtain fourth intent information;
[0245] Generate constraint rules of the product based on the fourth intent information.
[0246] It should be noted that the implementation of each operation can also be correspondingly referred to Figures 4 to 9 the corresponding description of the method in any one of the embodiments shown.
[0247] It should be noted that although Figure 11 the electronic device shown only shows the processor 1101, the memory 1102, the communication interface 1103, and the bus 1104, in the specific implementation process, those skilled in the art should understand that the electronic device also includes other devices necessary for normal operation. At the same time, according to specific needs, those skilled in the art should understand that the electronic device may also include hardware devices for implementing other additional functions. In addition, those skilled in the art should understand that the electronic device may also only include the devices necessary for implementing the embodiments of the present application, and does not necessarily include Figure 11 all the devices shown in
[0248] An embodiment of the present application also provides a chip, including: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method described in any one of the above Figures 4 to 9 embodiments. The chip can be a chip in an electronic device.
[0249] An embodiment of the present application also provides a computer-readable storage medium (Memory), and the computer-readable storage medium stores a computer program, and when the computer program is run, it implements the method as described in any one of the above Figures 4 to 9The method described in any one of the embodiments. It can be understood that the computer-readable storage medium here can include both the built-in storage medium in the device and, of course, the extended storage medium supported by the device. The computer-readable storage medium provides storage space, which stores the operating system of the device. And, one or more computer programs suitable for being loaded and executed by the processor of the device are also stored in this storage space. It should be noted that the computer-readable storage medium here can be high-speed RAM or non-volatile memory, such as at least one disk memory; optionally, it can also be at least one computer-readable storage medium located far from the aforementioned processor.
[0250] The embodiments of the present application also provide a computer program product, which includes: computer program code. When the computer program code is run by an electronic device, Figures 4 to 9 the method flow described in any one of the embodiments can be realized.
[0251] In the above embodiments, the descriptions of the various embodiments have their own emphases. For the parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.
[0252] It should be understood that the processor mentioned in the embodiments of the present application can be a CPU, or other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc.
[0253] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a ROM, a programmable read-only memory (PROM), an EPROM, an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a RAM, which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchlink dynamic random access memory (SLDRAM), and direct rambus random access memory (DRRAM).
[0254] It should be noted that when the processor is a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, the memory (storage module) is integrated in the processor.
[0255] It should be noted that the memory described herein is intended to include but not be limited to these and any other suitable types of memory.
[0256] It should be understood that in various embodiments of the present application, the magnitudes of the sequence numbers of the above processes do not mean the order of execution. The order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
[0257] In several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the device embodiments described above are merely exemplary. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection between each other may be through some interfaces. The indirect coupling or communication connection of the devices or units may be in an electrical, mechanical, or other form.
[0258] The unit described as a separation component may or may not be physically separated. The component shown as a unit may or may not be a physical unit, that is, it may be located in one place, or may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0259] In addition, each functional unit in various embodiments of the present application may be integrated in a processing unit, may exist separately as individual physical units, or two or more units may be integrated in one unit. If the above integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium.
[0260] In the present application, "at least one" means one or more, and "a plurality" means two or more. "And / or" describes the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. In the written description of the present application, the character " / " generally represents an "or" relationship between the associated objects before and after.
[0261] The steps in the method of the embodiment of the present application can be adjusted, combined, and deleted according to actual needs.
[0262] The modules in the device of the embodiment of the present application can be combined, divided, and deleted according to actual needs.
[0263] As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements on some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.
Claims
1. A product configuration management and generation method, characterized in that, the method includes: Obtain first intent information; the first intent information is used to indicate the configuration management of the product; Based on the first intent information, determine the first management object of the product, the attributes of the first management object, and the values of the attributes of the first management object; Generate the configuration information of the product based on the first management object, the attributes of the first management object, and the values of the attributes of the first management object.
2. The method according to claim 1, characterized in that, After generating the configuration information of the product based on the first management object, the attributes of the first management object, and the values of the attributes of the first management object, the method further includes: Obtain the constraint rules associated with the first management object and the attributes of the first management object; Detect whether the configuration information of the product satisfies the constraint rules associated with the first management object and the attributes of the first management object; If the configuration information of the product satisfies the constraint rules associated with the first management object and the attributes of the first management object, load the configuration information of the product onto the product.
3. The method according to claim 1 or 2, characterized in that, The first intent information includes the first named entity of the first management object and the second named entity of the attributes of the first management object; generating the configuration information of the product based on the first management object, the attributes of the first management object, and the values of the attributes of the first management object includes: Obtain the first canonical code of the first management object and the second canonical code of the attributes of the first management object; Replace the first named entity in the first intent information with the first canonical code, and replace the second named entity in the first intent information with the second canonical code to obtain second intent information; Generate the configuration information of the product based on the second intent information.
4. The method according to claim 2, characterized in that, The method further includes: If there are constraint rules that the configuration information of the product cannot satisfy among the constraint rules associated with the first management object and the attributes of the first management object, output the constraint rules that the configuration information of the product cannot satisfy.
5. The method according to any one of claims 1-4, characterized in that, Before obtaining the first intent information, the method further includes: Obtain third intent information; the third intent information is used to indicate the generation of the constraint rules of the product; Based on the third intent information, determine the second management object of the product, the attributes of the second management object, and the attribute constraints of the attributes of the second management object; Generate the constraint rules of the product based on the second management object of the product, the attributes of the second management object, and the attribute constraints of the attributes of the second management object.
6. The method according to claim 5, characterized in that, The method further includes: Perform conflict detection and redundancy detection on the generated constraint rules and the existing rules of the product; Output the detection result.
7. The method according to claim 6, wherein, if the generated constraint rule has a conflict relationship with one or more first existing rules, the detection result includes the one or more first existing rules; or if the generated constraint rule has a redundancy relationship with one or more second existing rules, the detection result includes the one or more second existing rules.
8. The method according to claim 6, wherein, the method further includes: compiling the generated constraint rule by unified compilation to obtain a rule to be stored in a unified programming language expression; storing the rule to be stored.
9. The method according to any one of claims 5-8, wherein, the third intention information includes a third named entity of the second management object and a fourth named entity of the attribute of the second management object; generating the constraint rule of the product based on the second management object of the product, the attribute of the second management object, and the attribute constraint of the attribute of the second management object includes: obtaining a third specification code of the second management object and a fourth specification code of the attribute of the second management object; replacing the third named entity in the third intention information with the third specification code, and replacing the fourth named entity in the third intention information with the fourth specification code to obtain fourth intention information; generating the constraint rule of the product based on the fourth intention information.
10. A product configuration management and generation device, wherein, the device includes an acquisition unit and a processing unit; the acquisition unit is configured to acquire first intention information; the first intention information is used to indicate configuration management of a product; the processing unit is configured to determine a first management object of the product, an attribute of the first management object, and a value of the attribute of the first management object based on the first intention information; generate configuration information of the product based on the first management object, the attribute of the first management object, and the value of the attribute of the first management object.
11. The method according to claim 10, wherein, the acquisition unit is further configured to acquire a constraint rule associated with the first management object and the attribute of the first management object; the processing unit is further configured to detect whether the configuration information of the product satisfies the constraint rule associated with the first management object and the attribute of the first management object; if the configuration information of the product satisfies the constraint rule associated with the first management object and the attribute of the first management object, load the configuration information of the product onto the product.
12. The device according to claim 10 or 11, wherein, the first intention information includes a first named entity of the first management object and a second named entity of the attribute of the first management object; in terms of generating the configuration information of the product based on the first management object, the attribute of the first management object, and the value of the attribute of the first management object, the processing unit is specifically configured to: Obtain the first standard code of the first management object and the second standard code of the attributes of the first management object; Replace the first named entity in the first intent information with the first standard code, and replace the second named entity in the first intent information with the second standard code to obtain second intent information; Generate the configuration information of the product based on the second intent information.
13. The apparatus according to claim 11, wherein, the processing unit is further configured to: If there is a constraint rule that cannot be satisfied by the configuration information of the product among the constraint rules associated with the first management object and the attributes of the first management object, output the constraint rule that cannot be satisfied by the configuration information of the product.
14. The apparatus according to any one of claims 10-13, wherein, the obtaining unit is further configured to obtain third intent information; the third intent information is used to indicate the generation of the constraint rules of the product; the processing unit is further configured to determine the second management object of the product, the attributes of the second management object, and the attribute constraints of the attributes of the second management object based on the third intent information; generate the constraint rules of the product based on the second management object of the product, the attributes of the second management object, and the attribute constraints of the attributes of the second management object.
15. The apparatus according to claim 14, wherein, the processing unit is further configured to: Perform conflict detection and redundancy detection on the generated constraint rules and the existing rules of the product; Output the detection result.
16. The apparatus according to claim 15, wherein, If the generated constraint rules have a conflict relationship with one or more first existing rules, the detection result includes the one or more first existing rules; or if the generated constraint rules have a redundancy relationship with one or more second existing rules, the detection result includes the one or more second existing rules.
17. The apparatus according to claim 15, wherein, the processing unit is further configured to: Compile the generated constraint rules using unified compilation to obtain the rules to be stored in a unified programming language representation; Store the rules to be stored.
18. The apparatus according to any one of claims 14-17, wherein, The third intent information includes the third named entity of the second management object and the fourth named entity of the attributes of the second management object; in terms of generating the constraint rules of the product based on the second management object of the product, the attributes of the second management object, and the attribute constraints of the attributes of the second management object, the processing unit is specifically configured to: Obtain the third standard code of the second management object and the fourth standard code of the attributes of the second management object; Replace the third named entity in the third intent information with the third standard code, and replace the fourth named entity in the third intent information with the fourth standard code to obtain fourth intent information; Generate the constraint rules of the product based on the fourth intent information.
19. An electronic device, wherein, Comprising a processor, a memory, a communication interface, and one or more programs, the one or more programs being stored in the memory and configured to, when executed by the processor, cooperate with the communication interface to implement the method according to any one of claims 1-9.
20. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program for execution by a device, and when the computer program is executed, the method according to any one of claims 1-9 is implemented.
21. A computer program product, characterized in that when the computer program product is run by a device, the device executes the method according to any one of claims 1-9.
Citation Information
Cited By
Product configuration management and generation method and related device
EP4811122A1
Product configuration management and generation method and related device
WO2025124056A1