CN113014406A - Equipment deployment method, device, server and storage medium - Google Patents

Equipment deployment method, device, server and storage medium Download PDF

Info

Publication number
CN113014406A
CN113014406A CN201911315726.3A CN201911315726A CN113014406A CN 113014406 A CN113014406 A CN 113014406A CN 201911315726 A CN201911315726 A CN 201911315726A CN 113014406 A CN113014406 A CN 113014406A
Authority
CN
China
Prior art keywords
equipment
identification information
target
manufacturer
deployment
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.)
Granted
Application number
CN201911315726.3A
Other languages
Chinese (zh)
Other versions
CN113014406B (en
Inventor
李海军
李闪
张然
张曙
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba Group Holding Ltd
Original Assignee
Alibaba Group Holding Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Priority to CN201911315726.3A priority Critical patent/CN113014406B/en
Publication of CN113014406A publication Critical patent/CN113014406A/en
Application granted granted Critical
Publication of CN113014406B publication Critical patent/CN113014406B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0876Aspects of the degree of configuration automation
    • H04L41/0886Fully automatic configuration
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/50Address allocation
    • H04L61/5007Internet protocol [IP] addresses
    • H04L61/5014Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/06Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]

Abstract

The embodiment of the application provides a device deployment method, a device, a server and a storage medium. In the equipment deployment method, a target equipment manufacturer to which the equipment belongs is identified, and a field name associated with the equipment identity and contained in a host configuration request of the equipment is translated according to a field name translation template corresponding to the target equipment manufacturer to obtain the identification information of the equipment. Based on the identification information of the target device manufacturer and the device, deployment configuration data adapted to the device can be obtained and sent to the device. Based on the implementation mode, the compatibility of the dynamic host configuration process to equipment manufactured by different manufacturers can be improved, and the automatic deployment efficiency of the equipment is improved.

Description

Equipment deployment method, device, server and storage medium
Technical Field
The present application relates to the field of internet technologies, and in particular, to a device deployment method, apparatus, server, and storage medium.
Background
With the rapid development of the Internet, Infrastructure As A Service (IAAS) platforms represented by cloud computing have driven the large-scale construction of Internet Data Centers (IDCs). The automatic deployment capability of hardware devices such as network devices and servers also becomes an important index for rapid and standard delivery of various cloud platforms.
Automatic deployment of hardware devices relies on dynamic host configuration protocol implementations. In some scenarios, different device vendors perform differential customization on the dynamic host configuration protocol, and the differential customization will cause that the dynamic host configuration server cannot be well compatible with automatic deployment services of hardware devices of multiple different vendors. Therefore, a solution is yet to be proposed.
Disclosure of Invention
Various aspects of the present application provide an apparatus deployment method, apparatus, server, and storage medium, so as to improve compatibility of a dynamic host configuration process with apparatuses of various different manufacturers, and improve automatic deployment efficiency of the apparatuses.
An embodiment of the present application provides an apparatus deployment method, including: responding to a host configuration request of equipment, and identifying a target equipment manufacturer to which the equipment belongs; translating the message corresponding to the host configuration request according to a field name translation template corresponding to the target equipment manufacturer to acquire identification information of the equipment; and acquiring deployment configuration data adapted to the equipment according to the target equipment manufacturer and the identification information of the equipment, and sending the deployment configuration data to the equipment.
An apparatus for deploying a device is further provided in an embodiment of the present application, including: a translation module to: responding to a host configuration request of equipment, and identifying a target equipment manufacturer to which the equipment belongs; translating the message corresponding to the host configuration request according to a field name translation template corresponding to the target equipment manufacturer to acquire identification information of the equipment; a device deployment module to: and acquiring deployment configuration data adapted to the equipment according to the target equipment manufacturer and the identification information of the equipment, and sending the deployment configuration data to the equipment.
An embodiment of the present application further provides an apparatus deployment method, including: acquiring the corresponding relation between field names and field descriptions of different equipment manufacturers from the dynamic host configuration protocols corresponding to the different equipment manufacturers; generating field name translation templates corresponding to different equipment manufacturers according to the corresponding relation between the field names and the field descriptions of the different equipment manufacturers; responding to a host configuration request of equipment, and acquiring a field name translation template corresponding to a target equipment manufacturer to which the equipment belongs from field name translation templates corresponding to different equipment manufacturers; translating the message corresponding to the host configuration request according to a field name translation template corresponding to the target equipment manufacturer to acquire identification information of the equipment; and acquiring deployment configuration data adapted to the equipment according to the target equipment manufacturer and the identification information of the equipment, and sending the deployment configuration data to the equipment.
An apparatus for deploying a device is further provided in an embodiment of the present application, including: the preprocessing module is used for acquiring the corresponding relation between the field names and the field descriptions of different equipment manufacturers from the dynamic host configuration protocols corresponding to the different equipment manufacturers; generating field name translation templates corresponding to different equipment manufacturers according to the corresponding relation between the field names and the field descriptions of the different equipment manufacturers; a translation module to: responding to a host configuration request of equipment, and acquiring a field name translation template corresponding to a target equipment manufacturer to which the equipment belongs from field name translation templates corresponding to different equipment manufacturers; translating the message corresponding to the host configuration request according to a field name translation template corresponding to the target equipment manufacturer to acquire identification information of the equipment; a device deployment module to: and acquiring deployment configuration data adapted to the equipment according to the target equipment manufacturer and the identification information of the equipment, and sending the deployment configuration data to the equipment.
The embodiment of the application also provides a server, comprising; a memory, a processor, and a communication component; the memory is to store one or more computer instructions; the processor is configured to execute the one or more computer instructions to perform the steps in the device deployment method provided in the embodiment of the present application.
Embodiments of the present application further provide a computer-readable storage medium storing a computer program, where the computer program can execute the steps in the device deployment method provided in the embodiments of the present application when executed.
The equipment deployment method, the device, the server and the storage medium provided by the embodiment of the application can accurately identify the equipment identification information under the condition that the equipment manufacturer customizes the field names associated with the equipment identities individually, reduce the influence of differential field name customization operations of different equipment manufacturers on the equipment identity identification process, improve the compatibility of the dynamic host configuration process on equipment manufactured by various different manufacturers, and improve the automatic deployment efficiency of the equipment.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1 is a flowchart illustrating an apparatus deployment method according to an exemplary embodiment of the present application;
fig. 2 is a flowchart illustrating an apparatus deployment method according to another exemplary embodiment of the present application;
fig. 3a is a schematic flowchart of an apparatus deployment method according to another exemplary embodiment of the present application;
FIG. 3b is an interaction diagram of a device deployment process provided by an exemplary embodiment of the present application;
fig. 4a is a schematic structural diagram of an apparatus deployment device according to an exemplary embodiment of the present application;
fig. 4b is a schematic structural diagram of an apparatus deployment device according to another exemplary embodiment of the present application;
fig. 5 is a schematic structural diagram of a server according to an exemplary embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In some embodiments of the present application, a solution is provided, and the technical solutions provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings.
Fig. 1 is a flowchart illustrating an apparatus deployment method according to an exemplary embodiment of the present application, where as shown in fig. 1, the method includes:
step 101, responding to a host configuration request of the equipment, and identifying a target equipment manufacturer to which the equipment belongs.
And step 102, translating the message corresponding to the host configuration request according to the field name translation template corresponding to the target equipment manufacturer to acquire the identification information of the equipment.
Step 103, acquiring deployment configuration data adapted to the device according to the target device manufacturer and the identification information of the device, and sending the deployment configuration data to the device.
The execution subject of this embodiment may be a server, and the server may provide a dynamic host configuration service. The dynamic host configuration service refers to that a server is located in a local area network environment, and can enable a device in the network environment to dynamically obtain information such as an IP (Internet Protocol) address, a Gateway (Gateway) address, a Domain Name System (DNS) address, and the like, so as to implement automatic deployment of the device. For example, in some embodiments, the server may be implemented as a DHCP (Dynamic Host Configuration Protocol) server.
The device includes any device that can participate in an automated deployment procedure, and the device may be implemented as a pure hardware device or as a device that is a combination of hardware and software, such as a network device, a server device, and the like, which includes but is not limited to this embodiment. Among other things, network devices may include, but are not limited to: hubs, switches, bridges, routers, gateways, network interface cards, wireless access points, printers and modems, fiber optic transceivers, fiber optic cables, computers, and the like. In the process of automatic deployment of the equipment, when the equipment is started, a management port of the equipment sends a host configuration request to a server providing a dynamic host configuration service so as to request the server to distribute deployment configuration data required by automatic deployment. Furthermore, after receiving the configuration number, the device can complete an automated deployment process according to the deployment configuration data.
In general, different device vendors customize the dhcp differently, and the difference is mainly reflected in the meaning of a part of fields in the dhcp. For example, when a plurality of device manufacturers use a number as a field name, the field meanings defined by different manufacturers for the same number are different.
Based on this, the meaning of the partial field name representation is different in the host configuration request sent by the device manufactured by different device manufacturers. In order to identify a message corresponding to a configuration request sent by a device, in this embodiment, a device manufacturer to which the device belongs may be identified first.
The field name translation template is used for representing the corresponding relation between the field name and the field description in the dynamic host configuration protocol. In this embodiment, the dynamic host configuration protocol differently customized for different equipment manufacturers can be analyzed in advance to obtain the field name translation templates corresponding to different equipment manufacturers. Based on this, after the target device manufacturer to which the device belongs is determined, the field name translation template corresponding to the target device manufacturer can be obtained from the field name translation templates corresponding to different device manufacturers.
After a field name translation template corresponding to a target equipment manufacturer is obtained, translating a field name contained in a host configuration request according to the field name translation template corresponding to the target equipment manufacturer; then, the translation result of the field name associated with the equipment identity in the translation result is obtained to obtain the identification information of the equipment. Furthermore, when there is a difference between field names associated with device ids included in host configuration requests of different devices, the identification information of the different devices can be accurately obtained based on the translation operation provided in this embodiment. The field name associated with the device id refers to a field name used for recording identification information of the device.
After the identification information of the target equipment manufacturer to which the equipment belongs and the equipment is acquired, the equipment can be uniquely identified, and the corresponding deployment configuration data can be sent to the equipment.
In this embodiment, after the target device manufacturer to which the device belongs is identified, the field name associated with the device identity included in the host configuration request of the device may be translated according to the field name translation template corresponding to the target device manufacturer, so as to obtain the identification information of the device. Furthermore, the equipment identification information can be accurately identified under the condition that the field names associated with the equipment identities are individually customized by the target equipment manufacturer, the influence of differential field name customization operations of different equipment manufacturers on the equipment identity identification process is reduced, the compatibility of a dynamic host configuration process on equipment manufactured by various different manufacturers is improved, and the automatic deployment efficiency of the equipment is improved.
In the above and following embodiments of the present application, a server providing a dynamic host configuration service may provide a management port IP address assignment service to a device. After uniquely identifying the device according to the target device manufacturer to which the device belongs and the identification information of the device, the server may allocate a management port IP address to the device, and launch the management port IP address to the device as deployment configuration data.
In some alternative embodiments, the server providing the dynamic host configuration service manages the address of the deposit of the startup script, the deposit path, and the name of the startup script required for the device manufactured by each device manufacturer. After uniquely identifying the device according to the target device manufacturer to which the device belongs and the identification information of the device, the server may issue information, such as the name of the start script, the storage path of the start script, and the address of the server storing the start script, provided for the device by the target device manufacturer that manufactures the device, to the device.
After receiving the management port IP address assigned to the device, the device may communicate with other devices based on the management port IP address. For example, the server storing the startup script may be accessed based on the IP address of the management port and the address of the server storing the startup script, and the startup script may be acquired from the server storing the startup script according to the storage path of the startup script and the name of the startup script.
The starting script is set for the equipment by the equipment manufacturer to which the equipment belongs, and defines the judgment, get and run operations of the starting file and the starting version of the equipment. Based on the start script, the device can realize an automatic deployment process, which is not described any more.
It is worth noting that in the above and following embodiments of the present application, the server providing the dynamic host configuration service may provide the dynamic host configuration service for the device based on at least two data processing components: message translation plug-ins and dynamic host configuration components. The message translation plug-in is mainly used for translating a host configuration request of the equipment so as to acquire manufacturer information of the equipment and identification information of the equipment. The dynamic host configuration component is mainly used for acquiring deployment configuration data required by the equipment according to the manufacturer information and the identification information of the equipment. The device deployment method according to the embodiment of the present application will be further described below with reference to the two data processing threads.
Fig. 2 is a flowchart illustrating an apparatus deployment method according to another exemplary embodiment of the present application, where as shown in fig. 2, the method includes:
step 201, the message translation plug-in responds to a host configuration request of the device and identifies a target device manufacturer to which the device belongs.
Step 202, the message translation plug-in queries the field name translation templates corresponding to the target equipment manufacturers from the field name translation templates corresponding to different equipment manufacturers.
Step 203, the message translation plug-in translates the message corresponding to the host configuration request according to the field name translation template corresponding to the target device manufacturer.
Step 204, the message translation plug-in selects the translation result corresponding to the field name associated with the equipment identity from the translation results as the identification information of the equipment.
Step 205, the message translation plug-in provides the identification information of the target device manufacturer and the device to the dynamic host configuration component.
And step 206, the dynamic host configuration component reads the corresponding relation between the identification information of the equipment under the target equipment manufacturer and the configuration items from a preset output configuration file according to the target equipment manufacturer.
Step 207, the dynamic host configuration component determines the target configuration item corresponding to the identification information of the device according to the device identity of the target device manufacturer and the corresponding relationship between the identification information of the device and the configuration item.
And step 208, the dynamic host configuration component acquires the deployment configuration data corresponding to the target configuration item, and the deployment configuration data is used as the deployment configuration data adaptive to the equipment and is sent to the equipment.
In step 201, a host configuration request sent by a device to a server may be obtained by a message translation plug-in. Optionally, the message translation plug-in may identify, according to the message corresponding to the host configuration request, the device manufacturer to which the device belongs, and for convenience of description, mark the device manufacturer as a target device manufacturer.
Optionally, the message includes a hardware address (MAC address) of the device. The MAC address is assigned by IEEE (Institute of Electrical and Electronics Engineers), and contains the manufacturer's number of the device. Based on this, the message translation plug-in can obtain the MAC address of the device from the message corresponding to the host configuration request, and identify the target device manufacturer to which the device belongs according to the device manufacturer number included in the MAC address.
Optionally, the message includes a manufacturer name of a device manufacturer to which the device belongs, and the message translation plug-in may identify a target device manufacturer to which the device belongs based on the manufacturer name.
Optionally, in some possible cases, when the device vendor performs personalized customization on the dynamic host configuration protocol, a special vendor customization identifier is added, for example, a personalized vendor number is added. Meanwhile, the equipment manufactured by the equipment manufacturer carries the personalized and customized manufacturer number when the equipment is based on the host configuration request sent by the dynamic host configuration protocol. Based on this, the message translation plug-in can analyze whether the message corresponding to the host configuration request contains the manufacturer customized identifier when receiving the host configuration request of the device, and if the manufacturer customized identifier exists, the device manufacturer to which the device belongs can be identified according to the manufacturer customized identifier.
The above-mentioned hardware address, manufacturer name and manufacturer customized identifier of the device are reference bases for the message translation plug-in to obtain a manufacturer of the device, and the message translation plug-in may select one or more information to identify a target device manufacturer of the device, which is not limited in this embodiment.
In step 202, field name translation templates corresponding to different device manufacturers are pre-configured.
Optionally, the message translation plug-in may obtain, in advance, the dynamic host configuration protocol customized individually by different equipment manufacturers, and translate the dynamic host configuration protocol customized individually by different equipment manufacturers to obtain the field name translation templates corresponding to different equipment manufacturers.
For example, according to the dynamic host configuration protocol customized by the equipment manufacturer a, the field name translation template corresponding to the equipment manufacturer a is obtained as follows: the field of field name a is described as: the fields of the device string number and the field name b are described as follows: a physical address; according to the dynamic host configuration protocol customized by the manufacturer of the B equipment, the corresponding field name translation template of the manufacturer of the B equipment is obtained as follows: the field of field name a is described as: the field description of the product name and the field name b is as follows: the physical address, field name c, field describes the location of the profile.
Based on the above, after determining the target device manufacturer to which the device belongs, the field name translation template corresponding to the target device manufacturer may be queried from the field name translation templates corresponding to different device manufacturers, and in the next step 203, the message corresponding to the host configuration request sent by the device is translated.
In step 203, optionally, the message corresponding to the host configuration request is translated, which means that the field name contained in the message with unknown meaning is translated into text information with definite meaning, i.e. the field description. For example, if the target device manufacturer to which the device belongs is manufacturer a, the field name a in the message sent by the device may be translated into: string number, field name b translates to: the physical address. If the target manufacturer to which the device belongs is manufacturer B, the field name a in the message sent by the device may be translated into: the product name, field name b translates to: the physical address, field name c, is translated into a configuration file storage address, which is not described in detail.
In step 204, optionally, after obtaining the translation result of the message corresponding to the host configuration request, the translation result associated with the identification information of the device may be selected from the translation results according to the meaning indicated by the translation result. The translation result associated with the identification information of the device is obtained by translating the field name associated with the device identity in the message corresponding to the host configuration request, and is not repeated.
Optionally, in some embodiments, the identification information of the device may include: at least one of a Vendor ID, a hardware address, a device identity (Client ID), and a product name of the device.
In step 205, optionally, the message translation plug-in may provide the identification information of the device and the manufacturer of the target device to which the device belongs to the dynamic host configuration component.
Optionally, the message translation plug-in may generate an input configuration file (input file) for the dynamic host configuration component according to the target device manufacturer to which the device belongs and the identification information of the device, so as to be read by the dynamic host configuration component.
Optionally, in this embodiment, the input configuration file may be in a JSON (JavaScript Object Notation) format or other format with high readability, which is not limited in this embodiment.
In step 206, optionally, the output configuration file defines a correspondence between the identification information of the devices under different device manufacturers and the configuration items. Different equipment manufacturers can correspond to different output configuration files. For example, an output profile for a device vendor may define the following: the configuration items of the switch of the A1 model are as follows: PA11, PA12, PA 13; the configuration items of the switch of the A2 model are as follows: PA21, PA23 and PA 24. The output configuration file corresponding to the B device vendor may define the following: the configuration items of the computer with the B1 model are as follows: PB11, PB12, PB 13.
In some embodiments, the output configuration file is obtained by the message translation plug-in according to dynamic host configuration protocols corresponding to different device manufacturers. Optionally, the message translation plug-in may obtain the correspondence between the identification information of the device and the configuration item of different device manufacturers from the dynamic host configuration protocols corresponding to the different device manufacturers. And then, generating an output configuration file based on the corresponding relation between the identification information of the equipment under different equipment manufacturers and the configuration items, and providing the output configuration file to the dynamic host configuration component.
Optionally, the output configuration file may be in a JSON (JavaScript Object Notation) format or other format with high readability, which is not limited in this embodiment.
After the dynamic host configuration component obtains the packaged host configuration request provided by the message translation plug-in, the dynamic host configuration component can obtain the identification information of the target equipment manufacturer to which the equipment belongs and the equipment. Then, the corresponding relationship between the identification information of the device under the target device manufacturer and the configuration item can be read from the output configuration file according to the target device manufacturer to which the device belongs.
Next, in step 207 and step 208, the dynamic host configuration component may determine a target configuration item corresponding to the identification information of the device according to the device identity of the target device vendor and the correspondence between the identification information of the device and the configuration item. After the target configuration item is obtained, the dynamic host configuration component can obtain deployment configuration data adaptive to the target configuration item and send the deployment configuration data to the device.
Optionally, in some embodiments, the deployment configuration data adapted to the device may include at least one of: and managing the IP address of the port, the name of the start script, the storage path of the start script and the address of the server for storing the start script, which are not described any more. The dynamic host configuration component can generate a response message according to the deployment configuration data, and issue the response message to the device, which is not described any further.
In this embodiment, after the target device manufacturer to which the device belongs is identified, the field name associated with the device identity included in the host configuration request of the device may be translated according to the field name translation template corresponding to the target device manufacturer, so as to obtain the identification information of the device. Furthermore, the equipment identification information can be accurately identified under the condition that the field names associated with the equipment identities are individually customized by the target equipment manufacturer, the influence of differential field name customization operations of different equipment manufacturers on the equipment identity identification process is reduced, the compatibility of a dynamic host configuration process on equipment manufactured by various different manufacturers is improved, and the automatic deployment efficiency of the equipment is improved.
It should be noted that, in the above embodiment, the message translation plug-in may encode the identification information of the device and the manufacturer of the target device to which the device belongs in a specified format, and encode the generated output configuration file in the same specified format. For example, when the message translation plug-in generates the input configuration file and the output configuration file, the message translation plug-in may further perform base64 encoding on data used for generating the input configuration file and the output configuration file, so as to obtain formats of the input configuration file and the output configuration file in the same format. Furthermore, the format of the data provided for the dynamic host configuration component can be unified, and the data processing efficiency of the dynamic host configuration component is improved.
It should be noted that the execution subjects of the steps of the methods provided in the above embodiments may be the same device, or different devices may be used as the execution subjects of the methods. For example, the execution subjects of step 201 to step 204 may be device a; for another example, the execution subject of steps 201 and 202 may be device a, and the execution subject of step 203 may be device B; and so on.
In addition, in some of the flows described in the above embodiments and the drawings, a plurality of operations are included in a specific order, but it should be clearly understood that the operations may be executed out of the order presented herein or in parallel, and the sequence numbers of the operations, such as 201, 202, etc., are merely used for distinguishing different operations, and the sequence numbers do not represent any execution order per se. Additionally, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first", "second", etc. in this document are used for distinguishing different messages, devices, modules, etc., and do not represent a sequential order, nor limit the types of "first" and "second" to be different.
Fig. 3a is a schematic flowchart of a device deployment method according to another exemplary embodiment of the present application, and as shown in fig. 3a, the method includes:
step 301, obtaining the corresponding relationship between the field names and the field descriptions of different equipment manufacturers from the dynamic host configuration protocols corresponding to the different equipment manufacturers.
And step 302, generating field name translation templates corresponding to different equipment manufacturers according to the corresponding relation between the field names and the field descriptions of the different equipment manufacturers.
Step 303, responding to the host configuration request of the device, and obtaining a field name translation template corresponding to the target device manufacturer to which the device belongs from the field name translation templates corresponding to the different device manufacturers.
Step 304, translating the message corresponding to the host configuration request according to the field name translation template corresponding to the target device manufacturer, so as to obtain the identification information of the device.
And 305, acquiring deployment configuration data adapted to the equipment according to the target equipment manufacturer and the identification information of the equipment, and sending the deployment configuration data to the equipment.
For alternative implementation of steps 301 to 305, reference may be made to the descriptions of the foregoing embodiments, and details are not repeated here.
In some optional embodiments, the method further comprises the steps of: acquiring corresponding relations between identification information and configuration items of equipment under different equipment manufacturers from dynamic host configuration protocols corresponding to different equipment manufacturers; and generating an output configuration file according to the corresponding relation between the identification information of the equipment under different equipment manufacturers and the configuration items. This step can be performed simultaneously with steps 301 to 302, and this embodiment is not limited.
In some optional embodiments, a manner of obtaining deployment configuration data adapted to the device according to the target device vendor and the identification information of the device may include: acquiring the corresponding relation between the identification information of the equipment under the target equipment manufacturer and the configuration items from the output configuration file; determining a target configuration item corresponding to the identification information of the equipment according to the equipment identity of the target equipment manufacturer and the corresponding relation between the identification information and the configuration item of the equipment; and acquiring deployment configuration data corresponding to the target configuration item as deployment configuration data adaptive to the equipment.
In this embodiment, the corresponding relationship between the field names and the field descriptions of different manufacturers is obtained in advance according to the dynamic host configuration protocols corresponding to different manufacturers, and based on the corresponding relationship, the field name translation templates corresponding to different manufacturers can be generated. Therefore, in the process of dynamic configuration of the device, the field name translation template can be determined according to the target device manufacturer to which the device sending the host configuration request belongs, and the field name associated with the device identity contained in the host configuration request of the device can be translated based on the field name translation template to obtain the identification information of the device. Furthermore, the equipment identification information can be accurately identified under the condition that the field names associated with the equipment identities are individually customized by the target equipment manufacturer, the influence of differential field name customization operations of different equipment manufacturers on the equipment identity identification process is reduced, the compatibility of a dynamic host configuration process on equipment manufactured by various different manufacturers is improved, and the automatic deployment efficiency of the equipment is improved.
The following embodiment will further exemplify the technical solution provided by the embodiment of the present application in a specific application scenario with reference to fig. 3 b.
The Bootstrap server (boottrap server) realizes the automatic deployment of the equipment based on the boottrap Protocol. Boottrap server may provide services of a dynamic host configuration server (DHCP server) and services of a simple File Transfer Protocol server (TFTP server). The TFTP server manages a boot script configured for the device by the vendor of the device. The device can request the IP address and the acquisition path of the start script from the DHCP server based on DHCP and can acquire the required start script from the TFTP server.
Different equipment manufacturers usually customize the option field in the DHCP protocol to meet the standard in order to achieve the differentiation and scalability capabilities. The option field of a device is defined differently by different device vendors. In this embodiment, a middleware implemented as a plug-in is provided to shield these different device vendors from differences in the option field name definitions.
The plug-in can acquire the DHCP after the individual customization of a plurality of equipment manufacturers in advance, and acquire the corresponding relation between the field name and the field description of the individual customization of each equipment manufacturer and the name of the start script, the storage path of the start script and the address of the server for storing the start script, which are provided by different equipment manufacturers for the equipment manufactured by the equipment manufacturers, from the DHCP. According to the acquired information, the plug-in can generate a configuration template.
Based on the configuration template, the plug-in may perform base64 encoding on information such as the name of the start script, the storage path of the start script, and the address of the server storing the start script of the device corresponding to different device manufacturers, and generate an output configuration file (output file) in JSON format, as shown in fig. 3 b.
Taking a Switch (Switch) as an example, in a starting process of a default operating system of the Switch, firstly, a discovery message (such as a bootrap Protocol Discover message) needs to be sent to a DHCP server according to a DHCP. The discovery packet carries an option field defined by the device manufacturer in the DHCP.
After the plug-in obtains the discovery message, the plug-in can analyze the discovery message to obtain the equipment manufacturer to which the switch belongs. Then, the corresponding relation between the field name and the field description of the equipment manufacturer to which the switch belongs is obtained from the pre-generated configuration template, and the field name in the discovery message is translated into the field description information in the text format based on the corresponding relation. And then, acquiring the identification information of the switch according to the field description information of the text format. Base64 encoding is performed based on the identification information of the switch and the device manufacturer to which the switch belongs, and an input configuration file (input file) in JSON format is generated, as shown in fig. 3 b. And then, packaging the discovery message of the switch according to the output configuration file, and sending the packaged discovery message to a dynamic host configuration component (DHCP service).
After the dynamic host configuration component acquires the input configuration file, the identification information and the manufacturer information of the switch can be directly identified. And then, acquiring an output configuration file corresponding to the equipment manufacturer to which the switch belongs from the output configuration files corresponding to different equipment manufacturers, and acquiring a deployment configuration item required by the switch from the output configuration file. Then, the deployment configuration data corresponding to the deployment configuration item, for example, the IP address allocated to the switch, the gateway (gateway), the IP address of the TFTP server downloading the start script, the path of the start script, the name of the start script, and other information, is obtained, and a response message (offer message) is generated according to the deployment configuration data.
And after receiving the response message, the management port of the switch acquires an IP address and a gateway (gateway) which are distributed for the switch, accesses a TFTP server storing the start script through the distributed IP address according to the name of the start script, the storage path of the start script and the address of the TFTP server storing the start script, downloads the required start script, stores the start script in a memory, and executes the start script through a script executor to finish automatic deployment.
Based on the above, the DHCP server can analyze the field names in the discovery messages of the devices manufactured by different device manufacturers through the plug-in according to the preset configuration template, and automatically identify the device information and configuration requirements of the devices manufactured by a plurality of device manufacturers, without the need for the DHCP server to design a set of corresponding service code logic for the automatic deployment of each device manufacturer and knowing the respective deployment implementation mode of each device manufacturer. The middleware with the unified interface standard designed in the embodiment of the invention is used for shielding the difference of different equipment manufacturers in definition, and finally, the compatibility with equipment of multiple manufacturers can be realized, the dependency relationship between hardware equipment and a software system is decoupled, the openness of the system is improved, and the integrated ecosphere is freely expanded.
Fig. 4a is a schematic structural diagram of an apparatus deployment device provided in an exemplary embodiment of the present application, and as shown in fig. 4a, the apparatus includes:
a translation module 401a for: responding to a host configuration request of equipment, and identifying a target equipment manufacturer to which the equipment belongs; and translating the message corresponding to the host configuration request according to the field name translation template corresponding to the target equipment manufacturer to acquire the identification information of the equipment.
A device deployment module 402a to: and acquiring deployment configuration data adapted to the equipment according to the target equipment manufacturer and the identification information of the equipment, and sending the deployment configuration data to the equipment.
Further optionally, when identifying the target device manufacturer to which the device belongs, the translation module 401a is specifically configured to: and identifying at least one of a hardware address, a manufacturer name and a manufacturer customized identifier of the equipment from a message corresponding to the host configuration request so as to identify a target equipment manufacturer to which the equipment belongs.
Further optionally, the translation module 401a is specifically configured to, when translating the message corresponding to the host configuration request according to the field name translation template corresponding to the target device manufacturer to obtain the identifier information of the device: inquiring a field name translation template corresponding to the target equipment manufacturer in field name translation templates corresponding to different equipment manufacturers; translating the message corresponding to the host configuration request according to the field name translation template corresponding to the target equipment manufacturer; and selecting the translation result corresponding to the field name associated with the equipment identity from the translation result as the identification information of the equipment.
Further optionally, the translation module 401a, after obtaining the identification information of the device, is further configured to: and packaging the host configuration request according to the target device manufacturer and the identification information of the device, and providing the packaged host configuration request to the device deployment module 402 a.
Further optionally, the device deployment module 402a, when acquiring, according to the target device manufacturer and the identification information of the device, deployment configuration data adapted to the device, and sending the deployment configuration data to the device, is specifically configured to: reading the corresponding relation between the identification information of the equipment under the target equipment manufacturer and the configuration items from a preset output configuration file according to the target equipment manufacturer; determining a target configuration item corresponding to the identification information of the equipment according to the equipment identity of the target equipment manufacturer and the corresponding relation between the identification information and the configuration item of the equipment; and acquiring deployment configuration data corresponding to the target configuration item as deployment configuration data adaptive to the equipment.
Further optionally, the translation module 401a is further configured to: acquiring corresponding relations between identification information and configuration items of equipment under different equipment manufacturers from dynamic host configuration protocols corresponding to different equipment manufacturers; and generating the output configuration file according to the corresponding relationship between the identification information of the devices of different device manufacturers and the configuration items, and providing the output configuration file to the device deployment module 402 a.
Further optionally, the translation module 401a is further configured to: encoding the identification information of the target equipment manufacturer and the equipment in a specified format; and encoding the specified format for the output configuration file.
Further optionally, the translation module 401a is further configured to: acquiring the corresponding relation between field names and field descriptions of different equipment manufacturers from the dynamic host configuration protocols corresponding to the different equipment manufacturers; and generating field name translation templates corresponding to different equipment manufacturers according to the corresponding relation between the field names and the field descriptions of the different equipment manufacturers.
Further optionally, the identification information of the device includes: at least one of a vendor identification, a hardware address, an equipment identity, and a product name of the equipment.
Further optionally, the deployment configuration data comprises at least one of: the method comprises the steps of managing an IP address of a port, the name of a start script, a storage path of the start script and an address of a server for storing the start script.
In this embodiment, after the target device manufacturer to which the device belongs is identified, the field name associated with the device identity included in the host configuration request of the device may be translated according to the field name translation template corresponding to the target device manufacturer, so as to obtain the identification information of the device. Furthermore, the equipment identification information can be accurately identified under the condition that the field names associated with the equipment identities are individually customized by the target equipment manufacturer, the influence of differential field name customization operations of different equipment manufacturers on the equipment identity identification process is reduced, the compatibility of a dynamic host configuration process on equipment manufactured by various different manufacturers is improved, and the automatic deployment efficiency of the equipment is improved.
Fig. 4b is a schematic structural diagram of an apparatus deployment device according to another exemplary embodiment of the present application, and as shown in fig. 4b, the apparatus includes:
the preprocessing module 401b is configured to obtain, from dynamic host configuration protocols corresponding to different device manufacturers, a correspondence between field names and field descriptions of the different device manufacturers; and generating field name translation templates corresponding to different equipment manufacturers according to the corresponding relation between the field names and the field descriptions of the different equipment manufacturers.
A translation module 402b to: responding to a host configuration request of equipment, and acquiring a field name translation template corresponding to a target equipment manufacturer to which the equipment belongs from field name translation templates corresponding to different equipment manufacturers; translating the message corresponding to the host configuration request according to a field name translation template corresponding to the target equipment manufacturer to acquire identification information of the equipment;
a device deployment module 403b to: and acquiring deployment configuration data adapted to the equipment according to the target equipment manufacturer and the identification information of the equipment, and sending the deployment configuration data to the equipment.
Further optionally, the preprocessing module 401b is further configured to: acquiring corresponding relations between identification information and configuration items of equipment under different equipment manufacturers from dynamic host configuration protocols corresponding to different equipment manufacturers; and generating an output configuration file according to the corresponding relation between the identification information of the equipment under different equipment manufacturers and the configuration items.
Further optionally, the device deployment module 403b, when acquiring the deployment configuration data adapted to the device according to the target device manufacturer and the identification information of the device, is specifically configured to: acquiring the corresponding relation between the identification information of the equipment under the target equipment manufacturer and the configuration items from the output configuration file; determining a target configuration item corresponding to the identification information of the equipment according to the equipment identity of the target equipment manufacturer and the corresponding relation between the identification information and the configuration item of the equipment; and acquiring deployment configuration data corresponding to the target configuration item as deployment configuration data adaptive to the equipment.
In this embodiment, the corresponding relationship between the field names and the field descriptions of different manufacturers is obtained in advance according to the dynamic host configuration protocols corresponding to different manufacturers, and based on the corresponding relationship, the field name translation templates corresponding to different manufacturers can be generated. Therefore, in the process of dynamic configuration of the device, the field name translation template can be determined according to the target device manufacturer to which the device sending the host configuration request belongs, and the field name associated with the device identity contained in the host configuration request of the device can be translated based on the field name translation template to obtain the identification information of the device. Furthermore, the equipment identification information can be accurately identified under the condition that the field names associated with the equipment identities are individually customized by the target equipment manufacturer, the influence of differential field name customization operations of different equipment manufacturers on the equipment identity identification process is reduced, the compatibility of a dynamic host configuration process on equipment manufactured by various different manufacturers is improved, and the automatic deployment efficiency of the equipment is improved.
Fig. 5 is a schematic structural diagram of a server according to an exemplary embodiment of the present application, and as shown in fig. 5, the server includes: memory 501, processor 502, and communication component 503.
The memory 501 is used for storing a computer program and may be configured to store other various data to support operations on the server. Examples of such data include instructions for any application or method operating on the server, contact data, phonebook data, messages, pictures, videos, and so forth.
The memory 501 may be implemented by any type or combination of volatile or non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
A processor 502, coupled to the memory 501, for executing computer programs in the memory 501 for: receiving a host configuration request for a device through a communication component 503; responding to a host configuration request of equipment, and identifying a target equipment manufacturer to which the equipment belongs; translating the message corresponding to the host configuration request according to a field name translation template corresponding to the target equipment manufacturer to acquire identification information of the equipment; and acquiring deployment configuration data adapted to the equipment according to the target equipment manufacturer and the identification information of the equipment, and sending the deployment configuration data to the equipment.
Further optionally, when identifying the target device manufacturer to which the device belongs, the processor 502 is specifically configured to: and identifying at least one of a hardware address, a manufacturer name and a manufacturer customized identifier of the equipment from a message corresponding to the host configuration request so as to identify a target equipment manufacturer to which the equipment belongs.
Further optionally, when translating the message corresponding to the host configuration request according to the field name translation template corresponding to the target device manufacturer to obtain the identifier information of the device, the processor 502 is specifically configured to: inquiring a field name translation template corresponding to the target equipment manufacturer in field name translation templates corresponding to different equipment manufacturers through a message translation plug-in; translating the message corresponding to the host configuration request according to a field name translation template corresponding to the target equipment manufacturer through the message translation plug-in; and selecting a translation result corresponding to the field name associated with the equipment identity from the translation results through the message translation plug-in as the identification information of the equipment.
Further optionally, the processor 502, after obtaining the identification information of the device, is further configured to: and providing the identification information of the target equipment manufacturer and the equipment to a dynamic host configuration component for processing the host configuration request through a message translation plug-in.
Further optionally, when the processor 502 obtains deployment configuration data adapted to the device according to the target device manufacturer and the identification information of the device, and sends the deployment configuration data to the device, the processor is specifically configured to: reading the corresponding relation between the identification information of the equipment under the target equipment manufacturer and the configuration items from a preset output configuration file through the dynamic host configuration component according to the target equipment manufacturer; determining a target configuration item corresponding to the identification information of the equipment according to the equipment identity of the target equipment manufacturer and the corresponding relation between the identification information and the configuration item of the equipment by the dynamic host configuration component; and acquiring deployment configuration data corresponding to the target configuration item through the dynamic host configuration component, wherein the deployment configuration data is taken as deployment configuration data adaptive to the equipment.
Further optionally, the processor 502 is further configured to: acquiring the corresponding relation between the identification information and the configuration items of the equipment under different equipment manufacturers from the dynamic host configuration protocols corresponding to different equipment manufacturers through the message translation plug-in; and generating the output configuration file by the message translation plug-in according to the corresponding relation between the identification information of the equipment under different equipment manufacturers and the configuration items, and providing the output configuration file for the dynamic host configuration component.
Further optionally, the processor 502 is further configured to: coding the identification information of the target equipment manufacturer and the equipment in a specified format through the message translation plug-in; and encoding the specified format for the output configuration file.
Further optionally, the processor 502 is further configured to: acquiring the corresponding relation between the field names and the field descriptions of different equipment manufacturers from the dynamic host configuration protocols corresponding to the different equipment manufacturers through the message translation plug-in; and the message translation plug-in generates field name translation templates corresponding to different equipment manufacturers according to the corresponding relation between the field names and the field descriptions of the different equipment manufacturers.
Further optionally, the identification information of the device includes: at least one of a vendor identification, a hardware address, an equipment identity, and a product name of the equipment.
Further optionally, the deployment configuration data comprises at least one of: the method comprises the steps of managing an IP address of a port, the name of a start script, a storage path of the start script and an address of a server for storing the start script.
Further, as shown in fig. 5, the server further includes: power supply components 504, and the like. Only some of the components are schematically shown in fig. 5, and it is not meant that the server includes only the components shown in fig. 5.
Wherein the communication component 503 is configured to facilitate communication between the device in which the communication component is located and other devices in a wired or wireless manner. The device in which the communication component is located may access a wireless network based on a communication standard, such as WiFi, 2G, 3G, 4G, or 5G, or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component may be implemented based on Near Field Communication (NFC) technology, Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
The power supply 504 provides power to various components of the device in which the power supply is located. The power components may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device in which the power component is located.
In this embodiment, after the target device manufacturer to which the device belongs is identified, the field name associated with the device identity included in the host configuration request of the device may be translated according to the field name translation template corresponding to the target device manufacturer, so as to obtain the identification information of the device. Furthermore, the equipment identification information can be accurately identified under the condition that the field names associated with the equipment identities are individually customized by the target equipment manufacturer, the influence of differential field name customization operations of different equipment manufacturers on the equipment identity identification process is reduced, the compatibility of a dynamic host configuration process on equipment manufactured by various different manufacturers is improved, and the automatic deployment efficiency of the equipment is improved.
It should be noted that, in addition to the method logic described in the foregoing embodiment, the server shown in fig. 5 may also execute the following method logic:
a processor 502 for: acquiring the corresponding relation between field names and field descriptions of different equipment manufacturers from the dynamic host configuration protocols corresponding to the different equipment manufacturers; generating field name translation templates corresponding to different equipment manufacturers according to the corresponding relation between the field names and the field descriptions of the different equipment manufacturers; responding to a host configuration request of equipment, and acquiring a field name translation template corresponding to a target equipment manufacturer to which the equipment belongs from field name translation templates corresponding to different equipment manufacturers; translating the message corresponding to the host configuration request according to a field name translation template corresponding to the target equipment manufacturer to acquire identification information of the equipment; and acquiring deployment configuration data adapted to the equipment according to the target equipment manufacturer and the identification information of the equipment, and sending the deployment configuration data to the equipment.
Further optionally, the processor 502 is further configured to: acquiring corresponding relations between identification information and configuration items of equipment under different equipment manufacturers from dynamic host configuration protocols corresponding to different equipment manufacturers; and generating an output configuration file according to the corresponding relation between the identification information of the equipment under different equipment manufacturers and the configuration items.
Further optionally, when acquiring the deployment configuration data adapted to the device according to the target device manufacturer and the identification information of the device, the processor 502 is specifically configured to: acquiring the corresponding relation between the identification information of the equipment under the target equipment manufacturer and the configuration items from the output configuration file; determining a target configuration item corresponding to the identification information of the equipment according to the equipment identity of the target equipment manufacturer and the corresponding relation between the identification information and the configuration item of the equipment; and acquiring deployment configuration data corresponding to the target configuration item as deployment configuration data adaptive to the equipment.
In this embodiment, the corresponding relationship between the field names and the field descriptions of different manufacturers is obtained in advance according to the dynamic host configuration protocols corresponding to different manufacturers, and based on the corresponding relationship, the field name translation templates corresponding to different manufacturers can be generated. Therefore, in the process of dynamic configuration of the device, the field name translation template can be determined according to the target device manufacturer to which the device sending the host configuration request belongs, and the field name associated with the device identity contained in the host configuration request of the device can be translated based on the field name translation template to obtain the identification information of the device. Furthermore, the equipment identification information can be accurately identified under the condition that the field names associated with the equipment identities are individually customized by the target equipment manufacturer, the influence of differential field name customization operations of different equipment manufacturers on the equipment identity identification process is reduced, the compatibility of a dynamic host configuration process on equipment manufactured by various different manufacturers is improved, and the automatic deployment efficiency of the equipment is improved.
Accordingly, the present application further provides a computer-readable storage medium storing a computer program, where the computer program can implement the steps that can be executed by the server in the foregoing method embodiments when executed.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable server to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable server, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable server to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable server to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims (14)

1. A device deployment method, comprising:
responding to a host configuration request of equipment, and identifying a target equipment manufacturer to which the equipment belongs;
translating the message corresponding to the host configuration request according to a field name translation template corresponding to the target equipment manufacturer to acquire identification information of the equipment;
and acquiring deployment configuration data adapted to the equipment according to the target equipment manufacturer and the identification information of the equipment, and sending the deployment configuration data to the equipment.
2. The method of claim 1, wherein translating the message corresponding to the host configuration request according to a field name translation template corresponding to the target device vendor to obtain the identification information of the device comprises:
inquiring a field name translation template corresponding to the target equipment manufacturer from field name translation templates corresponding to different equipment manufacturers through a message translation plug-in;
translating the message corresponding to the host configuration request according to a field name translation template corresponding to the target equipment manufacturer through the message translation plug-in;
and selecting a translation result corresponding to the field name associated with the equipment identity from the translation results as the identification information of the equipment through the message translation plug-in.
3. The method of claim 2, wherein after obtaining the identification information of the device, further comprising:
and providing the identification information of the target equipment manufacturer and the equipment to a dynamic host configuration component for processing the host configuration request through the message translation plug-in.
4. The method according to claim 3, wherein obtaining deployment configuration data adapted to the device according to the target device vendor and the identification information of the device comprises:
reading the corresponding relation between the identification information of the equipment under the target equipment manufacturer and the configuration items from a preset output configuration file through the dynamic host configuration component according to the target equipment manufacturer;
determining a target configuration item corresponding to the identification information of the equipment according to the equipment identity of the target equipment manufacturer and the corresponding relation between the identification information and the configuration item of the equipment through the dynamic host configuration component;
and acquiring deployment configuration data corresponding to the target configuration item through the dynamic host configuration component, wherein the deployment configuration data is taken as deployment configuration data adaptive to the equipment.
5. The method of claim 4, further comprising:
acquiring the corresponding relation between the identification information and the configuration items of the equipment under different equipment manufacturers from the dynamic host configuration protocols corresponding to the different equipment manufacturers through the message translation plug-in;
and generating the output configuration file according to the corresponding relation between the identification information of the equipment under different equipment manufacturers and the configuration items through the message translation plug-in, and providing the output configuration file for the dynamic host configuration component.
6. The method of claim 3 or 5, further comprising:
coding the identification information of the target equipment manufacturer and the equipment in a specified format through the message translation plug-in; and encoding the specified format for the output configuration file.
7. The method of any one of claims 1-5, further comprising:
acquiring the corresponding relation between the field names and the field descriptions of different equipment manufacturers from the dynamic host configuration protocols corresponding to the different equipment manufacturers through the message translation plug-in;
and generating field name translation templates corresponding to different equipment manufacturers according to the corresponding relation between the field names and the field descriptions of the different equipment manufacturers through the message translation plug-in.
8. A device deployment method, comprising:
acquiring the corresponding relation between field names and field descriptions of different equipment manufacturers from the dynamic host configuration protocols corresponding to the different equipment manufacturers;
generating field name translation templates corresponding to different equipment manufacturers according to the corresponding relation between the field names and the field descriptions of the different equipment manufacturers;
responding to a host configuration request of equipment, and acquiring a field name translation template corresponding to a target equipment manufacturer to which the equipment belongs from field name translation templates corresponding to different equipment manufacturers;
translating the message corresponding to the host configuration request according to a field name translation template corresponding to the target equipment manufacturer to acquire identification information of the equipment;
and acquiring deployment configuration data adapted to the equipment according to the target equipment manufacturer and the identification information of the equipment, and sending the deployment configuration data to the equipment.
9. The method of claim 8, further comprising:
acquiring corresponding relations between identification information and configuration items of equipment under different equipment manufacturers from dynamic host configuration protocols corresponding to different equipment manufacturers;
and generating an output configuration file according to the corresponding relation between the identification information of the equipment under different equipment manufacturers and the configuration items.
10. The method according to claim 9, wherein obtaining deployment configuration data adapted to the device according to the target device vendor and the identification information of the device comprises:
acquiring the corresponding relation between the identification information of the equipment under the target equipment manufacturer and the configuration items from the output configuration file;
determining a target configuration item corresponding to the identification information of the equipment according to the equipment identity of the target equipment manufacturer and the corresponding relation between the identification information and the configuration item of the equipment;
and acquiring deployment configuration data corresponding to the target configuration item as deployment configuration data adaptive to the equipment.
11. An equipment deployment apparatus, comprising:
a translation module to: responding to a host configuration request of equipment, and identifying a target equipment manufacturer to which the equipment belongs; translating the message corresponding to the host configuration request according to a field name translation template corresponding to the target equipment manufacturer to acquire identification information of the equipment;
a device deployment module to: and acquiring deployment configuration data adapted to the equipment according to the target equipment manufacturer and the identification information of the equipment, and sending the deployment configuration data to the equipment.
12. An equipment deployment apparatus, comprising:
the preprocessing module is used for acquiring the corresponding relation between the field names and the field descriptions of different equipment manufacturers from the dynamic host configuration protocols corresponding to the different equipment manufacturers; generating field name translation templates corresponding to different equipment manufacturers according to the corresponding relation between the field names and the field descriptions of the different equipment manufacturers;
a translation module to: responding to a host configuration request of equipment, and acquiring a field name translation template corresponding to a target equipment manufacturer to which the equipment belongs from field name translation templates corresponding to different equipment manufacturers; translating the message corresponding to the host configuration request according to a field name translation template corresponding to the target equipment manufacturer to acquire identification information of the equipment;
a device deployment module to: and acquiring deployment configuration data adapted to the equipment according to the target equipment manufacturer and the identification information of the equipment, and sending the deployment configuration data to the equipment.
13. A server, comprising; a memory, a processor, and a communication component;
the memory is to store one or more computer instructions;
the processor, configured to execute the one or more computer instructions, for performing the steps in the device deployment method of any one of claims 1-10.
14. A computer-readable storage medium storing a computer program, wherein the computer program is capable of implementing the steps in the device deployment method of any one of claims 1-10 when executed.
CN201911315726.3A 2019-12-19 2019-12-19 Equipment deployment method, device, server and storage medium Active CN113014406B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911315726.3A CN113014406B (en) 2019-12-19 2019-12-19 Equipment deployment method, device, server and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911315726.3A CN113014406B (en) 2019-12-19 2019-12-19 Equipment deployment method, device, server and storage medium

Publications (2)

Publication Number Publication Date
CN113014406A true CN113014406A (en) 2021-06-22
CN113014406B CN113014406B (en) 2023-10-24

Family

ID=76381431

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911315726.3A Active CN113014406B (en) 2019-12-19 2019-12-19 Equipment deployment method, device, server and storage medium

Country Status (1)

Country Link
CN (1) CN113014406B (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113542284A (en) * 2021-07-19 2021-10-22 恩亿科(北京)数据科技有限公司 ID package translation application method, system, storage medium and electronic equipment
CN113760302A (en) * 2021-09-09 2021-12-07 四川虹美智能科技有限公司 Jenkins-based UI package deployment method and system
CN115296960A (en) * 2022-08-04 2022-11-04 上海市共进通信技术有限公司 Method for realizing remote management of home gateway based on DHCP protocol

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100180016A1 (en) * 2006-05-19 2010-07-15 Belden Inc. Automated network device configuration and network deployment
CN105009518A (en) * 2013-02-25 2015-10-28 高通股份有限公司 Methods to discover, configure, and leverage relationships in internet of things (IoT) networks
WO2017092502A1 (en) * 2015-11-30 2017-06-08 上海斐讯数据通信技术有限公司 System and method for identifying wireless terminal type in router network bridge mode
CN107294763A (en) * 2016-03-28 2017-10-24 阿里巴巴集团控股有限公司 Network equipment method and apparatus
CN107968725A (en) * 2017-11-20 2018-04-27 瑞斯康达科技发展股份有限公司 Home gateway haplotype terminal equipment configuration information returns and collocation method, equipment
WO2019076369A1 (en) * 2017-10-19 2019-04-25 北京金山云网络技术有限公司 Cloud platform deployment method, device, electronic device, and readable storage medium

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100180016A1 (en) * 2006-05-19 2010-07-15 Belden Inc. Automated network device configuration and network deployment
CN105009518A (en) * 2013-02-25 2015-10-28 高通股份有限公司 Methods to discover, configure, and leverage relationships in internet of things (IoT) networks
WO2017092502A1 (en) * 2015-11-30 2017-06-08 上海斐讯数据通信技术有限公司 System and method for identifying wireless terminal type in router network bridge mode
CN107294763A (en) * 2016-03-28 2017-10-24 阿里巴巴集团控股有限公司 Network equipment method and apparatus
WO2019076369A1 (en) * 2017-10-19 2019-04-25 北京金山云网络技术有限公司 Cloud platform deployment method, device, electronic device, and readable storage medium
CN107968725A (en) * 2017-11-20 2018-04-27 瑞斯康达科技发展股份有限公司 Home gateway haplotype terminal equipment configuration information returns and collocation method, equipment

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113542284A (en) * 2021-07-19 2021-10-22 恩亿科(北京)数据科技有限公司 ID package translation application method, system, storage medium and electronic equipment
CN113542284B (en) * 2021-07-19 2023-06-30 恩亿科(北京)数据科技有限公司 id packet translation application method, system, storage medium and electronic device
CN113760302A (en) * 2021-09-09 2021-12-07 四川虹美智能科技有限公司 Jenkins-based UI package deployment method and system
CN113760302B (en) * 2021-09-09 2023-04-07 四川虹美智能科技有限公司 Jenkins-based UI package deployment method and system
CN115296960A (en) * 2022-08-04 2022-11-04 上海市共进通信技术有限公司 Method for realizing remote management of home gateway based on DHCP protocol

Also Published As

Publication number Publication date
CN113014406B (en) 2023-10-24

Similar Documents

Publication Publication Date Title
CN112019475B (en) Resource access method, device, system and storage medium under server-free architecture
CN113014406B (en) Equipment deployment method, device, server and storage medium
JP7090603B2 (en) Service tier resource management for general purpose interworking and scalability
US11245579B1 (en) Preconfigured device representations
US20200221294A1 (en) Apparatus and method for handling esim profile for issp device
US9021005B2 (en) System and method to provide remote device management for mobile virtualized platforms
CN109213519B (en) Heterogeneous API adaptation processing method and system
US11449319B2 (en) Method and apparatus for downloading bundle to smart secure platform by using activation code
CN108322490A (en) The method, apparatus and server of virtual machine configuration and the distributed cloud service system of deployment
CN108235763B (en) Detection system, method and related device
CN108376078A (en) Upgrade method, device and the household appliance of equipment
KR102561083B1 (en) Profile-based content and services
CN111865905B (en) Ukey-based communication method, device and storage medium
US20210092073A1 (en) Resource trees by management controller
US20160212571A1 (en) Method and system for allocating device object identifier (oid) in open machine-to-machine (m2m) system and application system applying the same
CN114390044A (en) File uploading method, system, device and storage medium
US10817280B1 (en) Overriding shared service interfaces
CN116028331A (en) Configuration file generation method and framework construction method for middleware test
CN113157975A (en) Extensible markup language parsing system and method
US10469473B2 (en) Network authentication system extensions
CN107547382B (en) Neighbor relation discovery method and device
CN110881064B (en) Domain name configuration method and device
CN114338383A (en) Simplified configuration method and system for video equipment
CN111526044A (en) Method, device and medium for discovering link between switch and server
CN106921521B (en) Equipment information loading method and network equipment

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