CN113419775B - Firmware configuration method, system, equipment and medium - Google Patents
Firmware configuration method, system, equipment and medium Download PDFInfo
- Publication number
- CN113419775B CN113419775B CN202110602859.XA CN202110602859A CN113419775B CN 113419775 B CN113419775 B CN 113419775B CN 202110602859 A CN202110602859 A CN 202110602859A CN 113419775 B CN113419775 B CN 113419775B
- Authority
- CN
- China
- Prior art keywords
- firmware
- configuration file
- configuration
- aop
- model
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/76—Adapting program code to run in a different environment; Porting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a firmware configuration method, which comprises the following steps: creating an AOP (automatic optical plane) section and defining a first entry point in the AOP section; responding to the received firmware configuration request, and judging whether to trigger the first access point according to the equipment classification of the firmware to be configured; responding to the triggering of the first access point, executing a device classification process corresponding to the first access point in the AOP section to determine a configuration file corresponding to each device; and carrying out firmware configuration according to the configuration file corresponding to each device. The invention also discloses a system, a computer device and a readable storage medium. The scheme provided by the invention is based on the AOP section, the original program logic is not damaged, and all parts of the service logic can be well isolated, so that the coupling degree between all parts of the service logic is reduced, the reusability of the program is improved, and the phenomenon that the compatibility codes of the machine type are continuously increased along with the increase of the machine type when the firmware is configured and developed by research personnel is avoided.
Description
Technical Field
The present invention relates to the field of firmware configuration, and in particular, to a firmware configuration method, system, device, and storage medium.
Background
The current information technology is developed and popularized at a high speed, more and more websites, service systems and mobile phone APP appear, a large number of servers are needed to support the backsides of the websites, the service systems and the mobile phone APP, a large number of different servers are deployed in a machine room by different service providers, and a large number of hardware in-band and out-of-band management software is needed to be on-line for maintaining and updating the devices. Since servers of different manufacturers, different models and different versions are usually present in the computer room, the operation is complicated when firmware configuration is performed on the servers.
Disclosure of Invention
In view of this, in order to overcome at least one aspect of the above problems, an embodiment of the present invention provides a firmware configuration method, including the following steps:
creating an AOP (automatic optical plane) section and defining a first entry point in the AOP section;
responding to the received firmware configuration request, and judging whether to trigger the first access point according to the equipment classification of the firmware to be configured;
responding to the triggering of the first access point, executing a device classification process corresponding to the first access point in the AOP section to determine a configuration file corresponding to each device;
and carrying out firmware configuration according to the configuration file corresponding to each device.
In some embodiments, in response to receiving the firmware configuration request, determining whether to trigger the first entry point according to a device class of the firmware to be configured, further includes:
acquiring a routing file of each device;
determining the manufacturer, series and model of each device according to the routing file and further determining the corresponding type;
triggering the first entry point in response to a category of vendor, family, and/or model reaching a threshold.
In some embodiments, the method further comprises:
in response to the category of the vendor, family, and/or model not exceeding the threshold, the firmware is configured directly with the configuration file.
In some embodiments, performing a device classification procedure corresponding to the first entry point in the AOP profile to determine a profile corresponding to each device further includes:
judging whether a corresponding relation with a corresponding configuration file exists according to the model of each device;
and responding to the corresponding relation, and acquiring a corresponding configuration file according to the corresponding relation.
In some embodiments, further comprising:
and acquiring the general configuration file in response to the absence of the configuration file corresponding to the model.
In some embodiments, further comprising:
judging whether the general configuration file is compatible with equipment or not;
responding to incompatibility, modifying the general configuration file and then configuring the firmware;
and storing the modified general configuration file and adding the corresponding relation between the modified general configuration file and the model in the tangent plane.
In some embodiments, further comprising:
defining a second entry point in the AOP section;
and responding to the firmware configuration according to the configuration file corresponding to each device, and executing the log flow corresponding to the second cut-in point in the AOP section.
Based on the same inventive concept, according to another aspect of the present invention, an embodiment of the present invention further provides a firmware configuration system, including:
the system comprises a creating module, a first switching module and a second switching module, wherein the creating module is configured to create an AOP (automatic optical plane) and define a first switching point in the AOP;
the judging module is configured to respond to the received firmware configuration request and judge whether to trigger the first access point according to the equipment classification of the firmware to be configured;
a determining module, configured to execute a device classification procedure corresponding to the first entry point in the AOP slice in response to triggering the first entry point, so as to determine a configuration file corresponding to each device;
and the configuration module is configured to perform firmware configuration according to the configuration file corresponding to each device.
Based on the same inventive concept, according to another aspect of the present invention, an embodiment of the present invention further provides a computer apparatus, including:
at least one processor; and
a memory storing a computer program operable on the processor, wherein the processor executes the program to perform any of the steps of the firmware configuration method described above.
Based on the same inventive concept, according to another aspect of the present invention, an embodiment of the present invention further provides a computer-readable storage medium storing a computer program, which when executed by a processor performs the steps of any one of the firmware configuration methods described above.
The invention has one of the following beneficial technical effects: the scheme provided by the invention is based on the AOP section, the original program logic is not damaged, and all parts of the service logic can be well isolated, so that the coupling degree between all parts of the service logic is reduced, the reusability of the program is improved, the development efficiency is improved, and the phenomenon that the compatibility codes of the machine type are continuously increased along with the increase of the machine type when the firmware is configured and developed by research personnel is avoided.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the prior art descriptions will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other embodiments can be obtained according to the drawings without creative efforts.
FIG. 1 is a flowchart illustrating a firmware configuration method according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of an apparatus classification method according to an embodiment of the present invention;
FIG. 3 is a block diagram of a firmware configuration system according to an embodiment of the present invention;
FIG. 4 is a schematic structural diagram of a computer device provided in an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a computer-readable storage medium according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the following embodiments of the present invention are described in further detail with reference to the accompanying drawings.
It should be noted that all expressions using "first" and "second" in the embodiments of the present invention are used for distinguishing two entities with the same name but different names or different parameters, and it should be noted that "first" and "second" are merely for convenience of description and should not be construed as limitations of the embodiments of the present invention, and they are not described in any more detail in the following embodiments.
In an embodiment of the present invention, in Aspect-Oriented Programming (AOP), these system-level service codes are called aspects (Aspect), which contain a cut-in point (pointcut) and an announcement (address). The pointcut is used for defining which connection points (jointpoint) of the application program the notification (advice) should cut into, such as method call, exception throwing or field modification, and the precise matching is defined by a regular expression of the pointcut; the notification (advice) is to notify the application to execute the action code defined in the section when the connection point (jointpoint) arrives. The AOP technology can change the operation of the original program or add extra operation on the basis of the original program while not changing the deployed service code, and can flexibly modify the execution condition and the execution content of the action by modifying the connection point (join point) or the tangent plane (aspect). And pre-constructing a tangent plane (aspect) in the AOP module, wherein the tangent plane (aspect) comprises contents such as defining the entry point (pointcut) condition and the notification (advice) action, and when the AOP entry point condition is met, automatically executing the action in the notification, thereby achieving the technical effect of redefining the business process or adding a new business function on the premise of not changing the deployed service code.
According to an aspect of the present invention, an embodiment of the present invention provides a firmware configuration method, as shown in fig. 1, which may include the steps of:
s1, creating an AOP section and defining a first entry point in the AOP section;
s2, in response to the received firmware configuration request, judging whether the first access point is triggered according to the equipment classification of the firmware to be configured;
s3, responding to the triggering of the first access point, executing a device classification process corresponding to the first access point in the AOP section to determine a configuration file corresponding to each device;
and S4, configuring the firmware according to the configuration file corresponding to each device.
The scheme provided by the invention is based on the AOP section, the original program logic is not damaged, and all parts of the service logic can be well isolated, so that the coupling degree between all parts of the service logic is reduced, the reusability of the program is improved, the development efficiency is improved, and the phenomenon that the compatibility codes of the machine type are continuously increased along with the increase of the machine type when the firmware is configured and developed by research personnel is avoided.
In some embodiments, step S1, create an AOP slice and define a first entry point in the AOP slice, specifically, an AOP slice class may be defined with an @ Aspect annotation, and then define an entry point to be located to a package: such as @ Pointcut ("execution" (com. Instruction. Five.) Controller.) "), classes that match this rule will be plunged in. Next, define notification @ before: reading the request data before the weaving processing content is started at the cut point, namely, reading the parameter data in the HttpServletRequest before the cut point method is entered. And finally, converting into standard data according to the request content: ip, url, http method, class method, args, and storing the standard data.
In some embodiments, in response to receiving the firmware configuration request, determining whether to trigger the first entry point according to a device class of the firmware to be configured, further includes:
acquiring a routing file of each device;
determining the manufacturer, the series and the model of each device according to the routing file and further determining the corresponding type;
triggering the first entry point in response to a category of the vendor, family, and/or model reaching a threshold.
Specifically, as shown in fig. 2, a manufacturer, a family, and a model of each device may be sequentially determined according to a routing file in each device, and if there are many types of manufacturers, families, and/or models of devices that need to be configured with firmware currently, a first entry point needs to be triggered, and a process corresponding to the first entry point in a section, that is, a device classification process, is executed to determine a configuration file corresponding to each device.
In some embodiments, performing a device classification procedure corresponding to the first entry point in the AOP profile to determine a profile corresponding to each device further includes:
judging whether a corresponding relation with a corresponding configuration file exists according to the model of each device;
and responding to the corresponding relation, and acquiring a corresponding configuration file according to the corresponding relation.
Specifically, after annotating and defining a tangent plane type and a tangent point method, a user request can be intercepted through a tangent plane device, relevant parameter information of a machine type is obtained, and the relevant parameter information is converted into standard data to be stored; dividing the firmware configuration template and the url of the model according to groups, namely, the model 1 corresponds to the template 1, the model 2 corresponds to the template 2, and the model N corresponds to the template N, so that the corresponding firmware configuration template can be found according to the model; and generating a corresponding configuration page according to the model template, so that a user can conveniently execute configuration operation.
In some embodiments, the method further comprises:
in response to the category of the vendor, family, and/or model not exceeding the threshold, the firmware is configured directly with the configuration file.
Specifically, when the first entry point is not triggered, a configuration file corresponding to the device may be directly obtained, and then firmware configuration may be performed using the configuration file.
In some embodiments, further comprising:
and acquiring the general configuration file in response to the absence of the configuration file corresponding to the model.
In some embodiments, further comprising:
judging whether the general configuration file is compatible with the equipment or not;
responding to incompatibility, modifying the general configuration file and then configuring the firmware;
and storing the modified general configuration file and adding the corresponding relation between the modified general configuration file and the model in the tangent plane.
Specifically, the models can be split according to manufacturers, and classified according to manufacturers, and then classified according to series, such as M5 series, M6 series, domestic series, and the like. Defining a universal configuration file template in each series; when the new model is added, the bottom layer firstly carries out compatibility check, if the commands of firmware configuration (mainly BMC configuration and BIOS configuration) are compatible and the operations are consistent, the codes and the configuration files are not required to be modified, and if the commands are inconsistent, the new model configuration files are added under the classification of the series. And maintaining the corresponding relation between the machine type and the configuration file in the section.
In some embodiments, further comprising:
defining a second entry point in the AOP section;
and responding to the firmware configuration according to the configuration file corresponding to each device, and executing the log flow corresponding to the second cut-in point in the AOP section.
Specifically, after the method for configuring the firmware is called, a second entry point may be defined, the monitoring method may be triggered, and standard log data may be generated and output. Therefore, the annotation is utilized to generate a tangent plane device, and result data are intercepted after a tangent point method so as to be converted into standard data for storage; the log and exception processing in each original method are uniformly moved to a tangent plane class for processing, so that the code amount is greatly reduced, and the service code in the controller is clearer.
In the embodiment of the invention, a section device is defined by utilizing annotations, then the firmware configuration function and the model url are grouped in advance, so that the section device intercepts a model firmware configuration request, converts the request data into standard data for storage, analyzes the model standard data according to the function grouping, finds a corresponding firmware configuration template file, and generates a configuration interface according to the configuration file. And when the section device detects the firmware configuration operation, the log information of the firmware configuration is intercepted, and the intercepted log information is converted into standard log data and then output.
Therefore, by utilizing the characteristic that AOP section can not damage the original program logic, the machine type classification and the firmware configuration core logic are isolated, the section type and the entry point are defined by annotations, the request of the entry point is intercepted, standard machine type classification data is generated and analyzed, after the firmware configuration process is executed, log data configured and executed in the period of time is obtained, after the section is used, logs and exception processing in each original method are uniformly carried out in the section type, and the logs and exception processing are output according to a uniform data format, so that operation and maintenance personnel can check the operation result and the configuration process logs.
Based on the same inventive concept, according to another aspect of the present invention, an embodiment of the present invention further provides a firmware configuration system 400, as shown in fig. 3, including:
a creating module 401 configured to create an AOP section and define a first entry point in the AOP section;
a determining module 402, configured to determine, in response to receiving a firmware configuration request, whether to trigger the first access point according to a device class of a firmware to be configured;
a determining module 403, configured to, in response to triggering the first entry point, execute a device classification procedure corresponding to the first entry point in the AOP section to determine a configuration file corresponding to each device;
the configuration module 404 is configured to perform firmware configuration according to a configuration file corresponding to each device.
The scheme provided by the invention is based on the AOP section, the original program logic can not be damaged, and all parts of the service logic can be well isolated, so that the coupling degree between all parts of the service logic is reduced, the reusability of the program is improved, the development efficiency is improved, and the phenomenon that the types of compatible codes are continuously increased along with the increase of the types of the firmware during the configuration and development of the firmware by research and development personnel is avoided.
In some embodiments, an AOP slice is created and a first entry point is defined in the AOP slice, specifically, an AOP slice class may be defined with an @ Aspect annotation, and then an entry point is defined to be located to a package: such as @ Pointcut ("execution" (com. Instruction. Five.) Controller.) "), classes that match this rule will be plunged in. Next, define notification @ before: reading the request data before the process content is woven in before the cut-in point starts, namely, before the cut-in point method is entered, namely, reading the parameter data in the http server. And finally, converting into standard data according to the request content: ip, url, http method, class method, args, and storing the standard data.
In some embodiments, the determining module 402 is further configured to:
acquiring a routing file of each device;
determining the manufacturer, series and model of each device according to the routing file and further determining the corresponding type;
triggering the first entry point in response to a category of vendor, family, and/or model reaching a threshold.
Specifically, as shown in fig. 2, a manufacturer, a family, and a model of each device may be sequentially determined according to a routing file in each device, and if there are many types of manufacturers, families, and/or models of devices that need to be configured with firmware currently, a first entry point needs to be triggered, and a process corresponding to the first entry point in a section, that is, a device classification process, is executed to determine a configuration file corresponding to each device.
In some embodiments, the determining module 402 is further configured to:
in response to the category of the vendor, family, and/or model not exceeding the threshold, the firmware is configured directly with the configuration file.
Specifically, when the first entry point is not triggered, a configuration file corresponding to the device may be directly obtained, and then firmware configuration may be performed using the configuration file.
In some embodiments, the determination module 403 is further configured to:
judging whether a corresponding relation with a corresponding configuration file exists according to the model of each device;
and responding to the corresponding relation, and acquiring a corresponding configuration file according to the corresponding relation.
Specifically, after annotating and defining a tangent plane type and a tangent point method, a user request can be intercepted through a tangent plane device, relevant parameter information of a machine type is obtained, and the relevant parameter information is converted into standard data to be stored; dividing the firmware configuration template and the url of the machine type according to groups, namely, the machine type 1 corresponds to the template 1, the machine type 2 corresponds to the template 2, and the machine type N corresponds to the template N, so that the corresponding firmware configuration template can be found according to the machine type; and generating a corresponding configuration page according to the model template, so that a user can conveniently execute configuration operation.
In some embodiments, further comprising:
and acquiring the general configuration file in response to the absence of the configuration file corresponding to the model.
In some embodiments, further comprising:
judging whether the general configuration file is compatible with equipment or not;
responding to incompatibility, modifying the general configuration file and then configuring the firmware;
and storing the modified general configuration file and adding the corresponding relation between the modified general configuration file and the machine type in the tangent plane.
Specifically, the models can be split according to manufacturers, and classified according to manufacturers, and then classified according to series, such as M5 series, M6 series, domestic series, and the like. Defining a universal configuration file template in each series; when the new model is added, the bottom layer firstly carries out compatibility check, if the commands of firmware configuration (mainly BMC configuration and BIOS configuration) are compatible and the operations are consistent, the codes and the configuration files are not required to be modified, and if the commands are inconsistent, the new model configuration files are added under the classification of the series. And maintaining the corresponding relation between the model and the configuration file in the section.
In some embodiments, further comprising:
defining a second entry point in the AOP section;
and responding to the firmware configuration according to the configuration file corresponding to each device, and executing the log flow corresponding to the second cut-in point in the AOP section.
Specifically, after the method for configuring the firmware is called, a second entry point may be defined, the monitoring method may be triggered, and standard log data may be generated and output. The annotation is utilized to generate a tangent plane device, and result data are intercepted after a tangent point method so as to be converted into standard data for storage; the log and exception processing in each original method are uniformly moved to a tangent plane class for processing, so that the code amount is greatly reduced, and the service code in the controller is clearer.
In the embodiment of the invention, a section device is defined by utilizing annotations, then the firmware configuration function and the model url are grouped in advance, so that the section device intercepts a model firmware configuration request, converts the request data into standard data for storage, analyzes the model standard data according to the function grouping, finds a corresponding firmware configuration template file, and generates a configuration interface according to the configuration file. And when the section device detects the firmware configuration operation, the log information of the firmware configuration is intercepted, and the intercepted log information is converted into standard log data and then output.
Therefore, by utilizing the characteristic that AOP section can not damage the original program logic, the machine type classification and the firmware configuration core logic are isolated, the section type and the entry point are defined by annotations, the request of the entry point is intercepted, standard machine type classification data is generated and analyzed, after the firmware configuration process is executed, log data configured and executed in the period of time is obtained, after the section is used, logs and exception processing in each original method are uniformly carried out in the section type, and the logs and exception processing are output according to a uniform data format, so that operation and maintenance personnel can check the operation result and the configuration process logs.
Based on the same inventive concept, according to another aspect of the present invention, as shown in fig. 4, an embodiment of the present invention further provides a computer apparatus 501, comprising:
at least one processor 520; and
a memory 510, the memory 510 storing a computer program 511 executable on the processor, the processor 520 executing the program to perform the steps of:
s1, creating an AOP section and defining a first entry point in the AOP section;
s2, in response to the received firmware configuration request, judging whether to trigger the first access point according to the equipment classification of the firmware to be configured;
s3, responding to the triggering of the first access point, executing a device classification process corresponding to the first access point in the AOP section to determine a configuration file corresponding to each device;
and S4, configuring the firmware according to the configuration file corresponding to each device.
In some embodiments, in response to receiving the firmware configuration request, determining whether to trigger the first entry point according to a device class of the firmware to be configured, further includes:
acquiring a routing file of each device;
determining the manufacturer, the series and the model of each device according to the routing file and further determining the corresponding type;
triggering the first entry point in response to a category of the vendor, family, and/or model reaching a threshold.
In some embodiments, the method further comprises:
in response to the category of the vendor, family, and/or model not exceeding the threshold, the firmware is configured directly with the configuration file.
In some embodiments, executing a device classification procedure corresponding to the first entry point in the AOP profile to determine a configuration file corresponding to each device further includes:
judging whether a corresponding relation with a corresponding configuration file exists according to the model of each device;
and responding to the corresponding relation, and acquiring a corresponding configuration file according to the corresponding relation.
In some embodiments, further comprising:
and acquiring the general configuration file in response to the absence of the configuration file corresponding to the model.
In some embodiments, further comprising:
judging whether the general configuration file is compatible with equipment or not;
in response to the incompatibility, the firmware is configured after the general configuration file is modified;
and storing the modified general configuration file and adding the corresponding relation between the modified general configuration file and the model in the tangent plane.
In some embodiments, further comprising:
defining a second entry point in the AOP section;
and responding to the firmware configuration according to the configuration file corresponding to each device, and executing the log flow corresponding to the second cut-in point in the AOP section.
The scheme provided by the invention is based on the AOP section, the original program logic can not be damaged, and all parts of the service logic can be well isolated, so that the coupling degree between all parts of the service logic is reduced, the reusability of the program is improved, the development efficiency is improved, and the phenomenon that the types of compatible codes are continuously increased along with the increase of the types of the firmware during the configuration and development of the firmware by research and development personnel is avoided.
Based on the same inventive concept, according to another aspect of the present invention, as shown in fig. 5, an embodiment of the present invention further provides a computer-readable storage medium 601, where the computer-readable storage medium 601 stores computer program instructions 610, and the computer program instructions 610, when executed by a processor, perform the following steps:
s1, creating an AOP section and defining a first entry point in the AOP section;
s2, in response to the received firmware configuration request, judging whether to trigger the first access point according to the equipment classification of the firmware to be configured;
s3, responding to the triggering of the first access point, executing a device classification process corresponding to the first access point in the AOP section to determine a configuration file corresponding to each device;
and S4, configuring the firmware according to the configuration file corresponding to each device.
In some embodiments, in response to receiving the firmware configuration request, determining whether to trigger the first entry point according to a device classification of the firmware to be configured, further includes:
acquiring a routing file of each device;
determining the manufacturer, the series and the model of each device according to the routing file and further determining the corresponding type;
triggering the first entry point in response to a category of vendor, family, and/or model reaching a threshold.
In some embodiments, the method further comprises:
in response to the category of the vendor, family, and/or model not exceeding the threshold, the firmware is configured directly with the configuration file.
In some embodiments, executing a device classification procedure corresponding to the first entry point in the AOP profile to determine a configuration file corresponding to each device further includes:
judging whether a corresponding relation with a corresponding configuration file exists according to the model of each device;
and responding to the corresponding relation, and acquiring a corresponding configuration file according to the corresponding relation.
In some embodiments, further comprising:
and acquiring the general configuration file in response to the absence of the configuration file corresponding to the model.
In some embodiments, further comprising:
judging whether the general configuration file is compatible with the equipment or not;
in response to the incompatibility, the firmware is configured after the general configuration file is modified;
and storing the modified general configuration file and adding the corresponding relation between the modified general configuration file and the model in the tangent plane.
In some embodiments, further comprising:
defining a second entry point in the AOP section;
and responding to the firmware configuration according to the configuration file corresponding to each device, and executing the log flow corresponding to the second cut-in point in the AOP section.
The scheme provided by the invention is based on the AOP section, the original program logic can not be damaged, and all parts of the service logic can be well isolated, so that the coupling degree between all parts of the service logic is reduced, the reusability of the program is improved, the development efficiency is improved, and the phenomenon that the types of compatible codes are continuously increased along with the increase of the types of the firmware during the configuration and development of the firmware by research and development personnel is avoided.
Finally, it should be noted that, as understood by those skilled in the art, all or part of the processes in the methods of the embodiments described above may be implemented by instructing relevant hardware by a computer program, and the program may be stored in a computer-readable storage medium, and when executed, may include the processes of the embodiments of the methods described above.
Further, it should be appreciated that the computer-readable storage media (e.g., memory) herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory.
Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as software or hardware depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosed embodiments of the present invention.
The foregoing is an exemplary embodiment of the present disclosure, but it should be noted that various changes and modifications could be made herein without departing from the scope of the present disclosure as defined by the appended claims. The functions, steps and/or actions of the method claims in accordance with the disclosed embodiments described herein need not be performed in any particular order. Furthermore, although elements of the disclosed embodiments of the invention may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.
It should be understood that, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly supports the exception. It should also be understood that "and/or" as used herein is meant to include any and all possible combinations of one or more of the associated listed items.
The numbers of the embodiments disclosed in the embodiments of the present invention are merely for description, and do not represent the merits of the embodiments.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, and the program may be stored in a computer-readable storage medium, where the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk.
Those of ordinary skill in the art will understand that: the discussion of any embodiment above is meant only to be exemplary, and is not intended to intimate that the scope of the disclosure, including the claims, is limited to these examples; within the idea of an embodiment of the invention, also combinations between technical features in the above embodiments or in different embodiments are possible, and there are many other variations of the different aspects of the embodiments of the invention as described above, which are not provided in detail for the sake of brevity. Therefore, any omissions, modifications, substitutions, improvements, and the like that may be made without departing from the spirit and principles of the embodiments of the present invention are intended to be included within the scope of the embodiments of the present invention.
Claims (9)
1. A firmware configuration method, comprising the steps of:
creating an AOP (automatic optical plane) section and defining a first entry point in the AOP section;
responding to the received firmware configuration request, and judging whether to trigger the first access point according to the equipment classification of the firmware to be configured;
responding to the triggering of the first access point, executing a device classification process corresponding to the first access point in the AOP section to determine a configuration file corresponding to each device;
performing firmware configuration according to the configuration file corresponding to each device;
responding to the received firmware configuration request, and judging whether to trigger the first access point according to the equipment classification of the firmware to be configured, further comprising:
acquiring a routing file of each device;
determining the manufacturer, the series and the model of each device according to the routing file and further determining the corresponding type;
triggering the first entry point in response to a category of vendor, family, and/or model reaching a threshold.
2. The method of claim 1, wherein the method further comprises:
in response to the category of the vendor, family, and/or model not exceeding the threshold, the firmware is configured directly with the configuration file.
3. The method of claim 2, wherein performing a device classification procedure in the AOP facet corresponding to the first entry point to determine a profile for each device, further comprises:
judging whether a corresponding relation with a corresponding configuration file exists according to the model of each device;
and responding to the corresponding relation, and acquiring a corresponding configuration file according to the corresponding relation.
4. The method of claim 3, further comprising:
and acquiring the general configuration file in response to the absence of the configuration file corresponding to the model.
5. The method of claim 4, further comprising:
judging whether the general configuration file is compatible with the equipment or not;
in response to the incompatibility, the firmware is configured after the general configuration file is modified;
and storing the modified general configuration file and adding the corresponding relation between the modified general configuration file and the machine type in the tangent plane.
6. The method of claim 1, further comprising:
defining a second entry point in the AOP section;
and responding to the firmware configuration according to the configuration file corresponding to each device, and executing the log flow corresponding to the second cut-in point in the AOP section.
7. A firmware configuration system, comprising:
the system comprises a creating module, a first switching module and a second switching module, wherein the creating module is configured to create an AOP (automatic optical plane) and define a first switching point in the AOP;
the judging module is configured to respond to the received firmware configuration request and judge whether to trigger the first access point according to the equipment classification of the firmware to be configured;
a determining module, configured to, in response to triggering the first entry point, execute a device classification procedure corresponding to the first entry point in the AOP section to determine a configuration file corresponding to each device;
the configuration module is configured to carry out firmware configuration according to the configuration file corresponding to each device;
a determination module further configured to:
acquiring a routing file of each device;
determining the manufacturer, the series and the model of each device according to the routing file and further determining the corresponding type;
triggering the first entry point in response to a category of vendor, family, and/or model reaching a threshold.
8. A computer device, comprising:
at least one processor; and
memory storing a computer program operable on the processor, characterized in that the processor executes the program to perform the steps of the method according to any of claims 1-6.
9. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, is adapted to carry out the steps of the method according to any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110602859.XA CN113419775B (en) | 2021-05-31 | 2021-05-31 | Firmware configuration method, system, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110602859.XA CN113419775B (en) | 2021-05-31 | 2021-05-31 | Firmware configuration method, system, equipment and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113419775A CN113419775A (en) | 2021-09-21 |
| CN113419775B true CN113419775B (en) | 2022-11-04 |
Family
ID=77713378
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110602859.XA Active CN113419775B (en) | 2021-05-31 | 2021-05-31 | Firmware configuration method, system, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113419775B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102130894A (en) * | 2010-01-12 | 2011-07-20 | 大唐移动通信设备有限公司 | Authentication and certification method and system |
| CA2957041A1 (en) * | 2014-10-03 | 2016-04-07 | Benefitfocus.Com, Inc. | Systems and methods for classifying and analyzing runtime events |
| CN109240665A (en) * | 2018-08-24 | 2019-01-18 | 北京北信源信息安全技术有限公司 | Log recording method, device and electronic equipment |
| KR102059807B1 (en) * | 2018-06-27 | 2019-12-27 | 주식회사 티맥스 소프트 | Technique for memory management on service oriented architecture |
Family Cites Families (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080033972A1 (en) * | 2006-08-04 | 2008-02-07 | Jianwen Yin | Common Information Model for Web Service for Management with Aspect and Dynamic Patterns for Real-Time System Management |
| CN101035016A (en) * | 2007-02-08 | 2007-09-12 | 中兴通讯股份有限公司 | Terminal equipment configuration system and method |
| US8001519B2 (en) * | 2007-06-27 | 2011-08-16 | International Business Machines Corporation | Model driven development including aspect integration tool |
| CN101266542B (en) * | 2008-02-01 | 2011-06-29 | 中国建设银行股份有限公司 | Method and device for loading component in container |
| US10360512B2 (en) * | 2015-05-29 | 2019-07-23 | International Business Machines Corporation | Intelligent service request classification and assignment |
| CN105354671A (en) * | 2015-11-06 | 2016-02-24 | 中国南方电网有限责任公司 | Universal configuration management system and enterprise-level information system comprising same |
| CN106161157B (en) * | 2016-07-20 | 2019-01-29 | 珠海格力电器股份有限公司 | Building method, device, smart home system and the terminal of smart home system |
| US10540190B2 (en) * | 2017-03-21 | 2020-01-21 | International Business Machines Corporation | Generic connector module capable of integrating multiple applications into an integration platform |
| US20180373722A1 (en) * | 2017-06-26 | 2018-12-27 | Acronis International Gmbh | System and method for data classification using machine learning during archiving |
| US20190342296A1 (en) * | 2018-05-01 | 2019-11-07 | Microsoft Technology Licensing, Llc | Automated compliance with security, audit and network configuration policies |
| CN110780883A (en) * | 2018-07-30 | 2020-02-11 | 网宿科技股份有限公司 | Method call chain tracking method, electronic device, and computer-readable storage medium |
| CN109202898B (en) * | 2018-08-07 | 2022-03-04 | 北京云迹科技有限公司 | Parameter configuration method and device |
| CN109408376B (en) * | 2018-09-28 | 2022-04-22 | 深圳乐信软件技术有限公司 | Configuration data generation method, device, equipment and storage medium |
| JP6780724B2 (en) * | 2019-03-18 | 2020-11-04 | 株式会社オートネットワーク技術研究所 | In-vehicle update device, update processing program, and program update method |
| CN111580857B (en) * | 2020-04-27 | 2021-10-19 | 珠海格力电器股份有限公司 | Equipment firmware online configuration method, device and system |
| CN111881102A (en) * | 2020-07-29 | 2020-11-03 | 浪潮云信息技术股份公司 | Method, device and readable medium for collecting audit logs based on AOP (automatic optical plane protocol) section |
-
2021
- 2021-05-31 CN CN202110602859.XA patent/CN113419775B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102130894A (en) * | 2010-01-12 | 2011-07-20 | 大唐移动通信设备有限公司 | Authentication and certification method and system |
| CA2957041A1 (en) * | 2014-10-03 | 2016-04-07 | Benefitfocus.Com, Inc. | Systems and methods for classifying and analyzing runtime events |
| KR102059807B1 (en) * | 2018-06-27 | 2019-12-27 | 주식회사 티맥스 소프트 | Technique for memory management on service oriented architecture |
| CN109240665A (en) * | 2018-08-24 | 2019-01-18 | 北京北信源信息安全技术有限公司 | Log recording method, device and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113419775A (en) | 2021-09-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107896162B (en) | Deployment method and device of monitoring system, computer equipment and storage medium | |
| US20060265469A1 (en) | XML based scripting framework, and methods of providing automated interactions with remote systems | |
| CN107562556B (en) | Failure recovery method, recovery device and storage medium | |
| CN111949520A (en) | Automatic interface test method and equipment | |
| CN110673923A (en) | XWIKI system configuration method, system and computer equipment | |
| CN111399828B (en) | Model-driven logic device modeling method and terminal | |
| CN108920146A (en) | Page control assembly and visual Simulation operating system | |
| CN105045602A (en) | Method and device for constructing Hadoop application development framework and electronic device | |
| CN109460268B (en) | Application parameter configuration method, device and system | |
| CN101937335B (en) | Method for generating Widget icon, method for generating Widget summary document and Widget engine | |
| CN109144525A (en) | A kind of software installation method and system of network self-adapting | |
| CN113806037A (en) | Service calling method and device, storage medium and electronic equipment | |
| CN110543427A (en) | Test case storage method and device, electronic equipment and storage medium | |
| CN109840074B (en) | Service generation method, device and network equipment | |
| CN115525534A (en) | Test case generation method and platform based on swagger interface test | |
| CN113419775B (en) | Firmware configuration method, system, equipment and medium | |
| CN110442353B (en) | Installation package management method and device and electronic equipment | |
| WO2023151397A1 (en) | Application program deployment method and apparatus, device, and medium | |
| CN112596750B (en) | Application testing method and device, electronic equipment and computer readable storage medium | |
| CN113708971A (en) | Openstack cloud platform deployment method and related device | |
| CN114416305A (en) | Robot engine implementation method and system and electronic equipment | |
| CN115168175A (en) | Program error solving method, device, electronic equipment and storage medium | |
| CN111144086B (en) | Log formatting method and device, electronic equipment and storage medium | |
| CN117221373A (en) | Implementation method of rule engine of Internet of things for efficient execution | |
| CN115509837A (en) | BMC testing method, device and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |