A method, apparatus, device, system and storage medium for deploying network devices

Abstract

The application provides a method, device, equipment, system and storage medium for deploying a network device. The method comprises: a terminal device acquiring a server identifier and an enterprise identifier; the server identifier indicating a server to which the network device needs to be connected, and the enterprise identifier indicating an enterprise to which the network device belongs; acquiring an identifier of the network device; associating the identifier of the network device with the enterprise identifier to generate association information; and sending the association information to the server indicated by the server identifier. According to the embodiment, the network device can be started without the network administrator of the enterprise going to the installation site of the network device, and the method is convenient and fast.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method, apparatus, device, system, and storage medium for deploying network equipment. Background Technology

[0002] With the development of cloud computing technology, the concept of the cloud has been widely accepted by enterprises. Many companies are connecting their internal network devices to the cloud and adopting a cloud management model for these devices. This means that the company's network administrators can remotely manage the network accessed in the cloud via the Internet, including adding, deleting, and maintaining network devices.

[0003] However, the connection of network devices requires the company's network administrators to operate them at the installation site, which brings inconvenience to the network administrators. Summary of the Invention

[0004] This application discloses a method, apparatus, device, system, and storage medium for deploying network devices. The method can complete the commissioning of network devices without requiring the enterprise's network administrators to go to the installation site, and is characterized by convenient and quick operation.

[0005] In a first aspect, this application provides a method for deploying network devices, comprising: a terminal device obtaining a server identifier and an enterprise identifier; the server identifier indicating a server managing the network device, and the enterprise identifier indicating an enterprise to which the network device belongs; obtaining the identifier of the network device; associating the identifier of the network device and the enterprise identifier to generate association information; and sending the association information to the server indicated by the server identifier.

[0006] As can be seen, the terminal device obtains the server identifier and the enterprise identifier, then obtains the network device identifier, generates association information between the network device identifier and the enterprise identifier, and sends the association information to the server indicated by the server identifier. The terminal device can be any temporary operator at the network device installation site. This application eliminates the need for the company's network administrators to operate the network device at the installation site; it allows for direct operation by on-site personnel, resulting in rapid deployment and high efficiency.

[0007] Based on the first aspect, in possible implementations, obtaining the server identifier and the enterprise identifier includes: obtaining encrypted information; decrypting the encrypted information to obtain the server identifier and the enterprise identifier.

[0008] It is understandable that, to ensure information security, the server identifier and enterprise identifier obtained by the terminal device may exist in the form of encrypted information. After obtaining the encrypted information, the terminal device decrypts it to obtain the server identifier and enterprise identifier.

[0009] Based on the first aspect, in possible implementations, the encrypted information may take the form of a QR code; correspondingly, decrypting the encrypted information to obtain the server identifier and the enterprise identifier includes: scanning and parsing the QR code to obtain the server identifier and the enterprise identifier.

[0010] As can be seen, to facilitate operation by temporary personnel, the encrypted information can be presented in the form of a QR code. Temporary personnel can directly obtain the server and company identifiers by scanning the QR code with their terminal devices, without having to manually enter them. This avoids the drawbacks of potential input errors due to manual input, and features ease of operation and accurate information.

[0011] Based on the first aspect, in a possible implementation, scanning and parsing the QR code to obtain the server identifier and the enterprise identifier includes: scanning and parsing the QR code to obtain a first Uniform Resource Locator (URL) link; and obtaining the server identifier and the enterprise identifier based on the first URL link.

[0012] As can be seen, to further ensure information security and facilitate operation by temporary personnel, another way to obtain the server and enterprise identifiers is for the terminal device to scan the QR code after receiving it, obtain a first URL link, and then obtain the server and enterprise identifiers based on the first URL link. This implementation method ensures information security and is simple to operate.

[0013] Based on the first aspect, in a possible implementation, scanning and parsing the QR code to obtain the server identifier and the enterprise identifier includes: scanning and parsing the QR code to obtain a second Uniform Resource Locator (URL) link; wherein the second URL link includes the server identifier and the enterprise identifier.

[0014] It is understandable that the server identifier and enterprise identifier can also be obtained by having the terminal device scan a QR code to obtain a second URL link, where the second URL link includes the server identifier and enterprise identifier.

[0015] Based on the first aspect, in a possible implementation, the encrypted information may take the form of a third Uniform Resource Locator (URL) link; the third URL link indicates the acquisition of the server identifier and the enterprise identifier; correspondingly, the decryption of the encrypted information to obtain the server identifier and the enterprise identifier includes: obtaining the server identifier and the enterprise identifier according to the third URL link.

[0016] As can be seen, encrypted information can also exist directly in the form of a third-party URL link. The terminal device obtains the server identifier and enterprise identifier based on the third-party URL link.

[0017] Based on the first aspect, in possible implementations, the encrypted information may take the form of a fourth Uniform Resource Locator (URL) link; the fourth URL link may include the server identifier and the enterprise identifier.

[0018] It is understandable that encrypted information can also exist directly in the form of a fourth URL link, which includes server identifier and enterprise identifier.

[0019] Based on the first aspect, in possible implementations, the encrypted information further includes account permission information; the account permission information indicates the permissions possessed by the terminal device, including associating the identifier of the network device with the enterprise identifier to generate the association information, and / or sending the association information to the server indicated by the server identifier.

[0020] As can be seen, the encrypted information may also include account permission information. This account permission information represents the permissions possessed by the terminal device, including the permission to associate the network device's identifier with the enterprise identifier and the permission to send the associated information to the server. This account permission information can further guarantee the operating permissions of temporary operators, preventing accidental or unauthorized operations by other personnel from affecting the initial setup of the network device.

[0021] Based on the first aspect, in a possible implementation, obtaining the server identifier and the enterprise identifier includes: obtaining voice information; recognizing the voice information to obtain the server identifier and the enterprise identifier.

[0022] It's understandable that server identifiers and enterprise identifiers can also be obtained through voice information. After receiving the voice information, the terminal device can obtain the server identifier and enterprise identifier by recognizing the voice information. In this method, the terminal device can automatically obtain the server identifier and enterprise identifier through voice recognition, eliminating the need for manual input and avoiding situations where errors in manual input may lead to the failure of associating the network device's identifier and enterprise identifier.

[0023] Secondly, this application provides an apparatus for deploying network devices, comprising: an acquisition unit for acquiring a server identifier and an enterprise identifier; the server identifier indicating a server managing the network device, and the enterprise identifier indicating an enterprise to which the network device belongs; the acquisition unit is further configured to acquire an identifier of the network device; an association unit for associating the identifier of the network device and the enterprise identifier to generate association information; and a communication unit for sending the association information to the server indicated by the server identifier.

[0024] Based on the second aspect, in a possible implementation, the acquisition unit is used to: acquire encrypted information; decrypt the encrypted information to obtain the server identifier and the enterprise identifier.

[0025] Based on the second aspect, in possible implementations, the encrypted information may take the form of a QR code; the acquisition unit is used to: scan and parse the QR code to obtain the server identifier and the enterprise identifier.

[0026] Based on the second aspect, in a possible implementation, the acquisition unit is used to: scan and parse the QR code to obtain a first Uniform Resource Locator (URL) link; and obtain the server identifier and enterprise identifier based on the first URL link.

[0027] Based on the second aspect, in a possible implementation, the acquisition unit is used to: scan and parse the QR code to obtain a second Uniform Resource Locator (URL) link; wherein the second URL link includes the server identifier and the enterprise identifier.

[0028] Based on the second aspect, in a possible implementation, the encrypted information may take the form of a third Uniform Resource Locator (URL) link; the third URL link indicates the acquisition of the server identifier and the enterprise identifier; the acquisition unit is configured to: obtain the server identifier and the enterprise identifier based on the third URL link.

[0029] Based on the second aspect, in a possible implementation, the encrypted information may take the form of a fourth Uniform Resource Locator (URL) link; the fourth URL link may include the server identifier and the enterprise identifier.

[0030] Based on the second aspect, in possible implementations, the encrypted information also includes account permission information; the account permission information indicates the permissions possessed by the terminal device, including associating the identifier of the network device with the enterprise identifier to generate the association information, and / or sending the association information to the server indicated by the server identifier.

[0031] Based on the second aspect, in a possible implementation, the acquisition unit is used to: acquire voice information; recognize the voice information to obtain the server identifier and the enterprise identifier.

[0032] Each functional unit in the second aspect apparatus described above is used to implement the method described in the first aspect and any implementation thereof.

[0033] Thirdly, this application provides a terminal device, including a memory and a processor, wherein the memory is used to store instructions, and the processor is used to invoke the instructions stored in the memory to execute the method described in the first aspect or any implementation thereof.

[0034] Fourthly, this application provides a computer storage medium including program instructions that, when executed on a computer, cause the computer to perform the method described in the first aspect or any implementation thereof.

[0035] Fifthly, this application provides a computer program product including program instructions. When the computer program product is executed by a terminal device, the terminal device performs the method described in the first aspect. The computer program product can be a software installation package. When it is necessary to use the method provided by any possible design of the first aspect, the computer program product can be downloaded and executed on the terminal device to implement the method described in the first aspect or any possible implementation of the first aspect.

[0036] Sixthly, this application provides a system including a terminal device and a server, wherein the terminal device is used to implement the method described in the first aspect or any implementation thereof.

[0037] As can be seen, in the commissioning of network devices, to overcome the drawback that enterprise network administrators need to go to the installation site of the network devices to complete the process, this application provides a method for deploying network devices. In this method, a terminal device obtains a server identifier and an enterprise identifier. The terminal device can be any temporary operator at the network device installation site. The server identifier and enterprise identifier can exist in the form of encrypted information; for ease of operation, the encrypted information can be in the form of a QR code or a URL link. Then, the network device identifier is obtained. The network device identifier and the enterprise identifier are linked together to generate association information, which is then sent to the server indicated by the server identifier. After receiving the association information, the server saves the association information, i.e., it saves the association relationship between the network device identifier and the enterprise identifier. The server receives a commissioning application for the network device, which carries the network device identifier, and sends configuration information to the network device so that the network device can complete the commissioning configuration according to the configuration information. Implementing this application allows for network device commissioning without requiring enterprise network administrators to go to the installation site. This method is characterized by fast commissioning speed and simple operation. Attached Figure Description

[0038] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0039] Figure 1 A schematic diagram of a system architecture is provided for this application;

[0040] Figure 2 A flowchart illustrating a method for deploying network devices provided in this application;

[0041] Figure 3 A schematic diagram of an apparatus for deploying network devices provided in this application;

[0042] Figure 4 A schematic diagram of the structure of a terminal device provided in this application;

[0043] Figure 5 A schematic diagram of the structure of a server provided in this application;

[0044] Figure 6 A schematic diagram of a system structure provided for this application. Detailed Implementation

[0045] The solutions in the embodiments provided in this application will now be described in detail with reference to the accompanying drawings.

[0046] See Figure 1 , Figure 1 This application provides a schematic diagram of a system architecture. The system includes at least one network device (such as network device 110A, network device 110B, and network device 110C) and a cloud 120, wherein the cloud 120 includes at least one server, such as server 121A, server 121B, and server 121C.

[0047] Cloud 120 refers to a cluster of computing devices provided by a third-party provider to users or enterprises for providing computing, storage, and communication resources. In this application, Cloud 120 is used to provide free or low-cost resource services to one or more enterprises. Cloud 120 can be provided by any provider; for example, it could be provided by provider A, provider B, or provider C.

[0048] Network devices refer to routers, switches, firewalls, etc. Network devices 110A, 110B, and 110C can connect to the cloud 120 via the network.

[0049] Servers 121A, 121B, and 121C can be physical servers or virtual machines; this application does not impose any specific restrictions.

[0050] For a company, there are multiple network devices. These devices can connect to a single provider's cloud service simultaneously, or they can connect to multiple providers' cloud services simultaneously. For example, all network devices in company A can connect to provider A's cloud service, or some network devices in company A can connect to provider A's cloud service, while others connect to provider B's cloud service. In other words, all network devices in a company can connect to one or more providers' cloud services.

[0051] A provider's cloud 120 can connect to one or more network devices from one enterprise. For example, provider A's cloud can connect only some or all of enterprise A's network devices, or provider A's cloud can connect some or all of enterprise A's network devices as well as some or all of enterprise B's network devices.

[0052] The server is equipped with a network management system, which is used to allocate and manage resources for at least one enterprise connected to the server and for each network device within that enterprise. Network administrators within each enterprise can log in to the network management system using an account and password to view the network devices within their enterprise and their operational status, and to operate and maintain those devices.

[0053] In the aforementioned system, enterprise network administrators can log into the network management system to view a specific network device within the enterprise and its operational status. They can then operate and maintain the device, provided it has been successfully connected to the server, successfully associated with or bound to the enterprise to which it belongs, and configured accordingly. In other words, the network device has been successfully commissioned. The following describes how to perform network device commissioning.

[0054] 1) The company's network administrators arrive at the location where the network devices are installed, carrying terminal equipment. They obtain the network device identifiers through these devices, which are used to distinguish each network device. These identifiers can be electronic serial numbers (ESNs), Media Access Control (MAC) addresses, etc. The terminal equipment can be any of a mobile phone, computer, iPad, or wearable electronic device.

[0055] 2) The terminal device associates the network device's identifier with the enterprise identifier of the company to which the network device belongs, obtains the association information, and sends the association information to the target server. The target server refers to the server that manages the network device, and the target server does not belong to the company to which the network device belongs. For example, the target server can be a server provided by provider A. The enterprise identifier is the basis for distinguishing different companies. Different companies have different enterprise identifiers. The enterprise identifier can be the company name or company address, or it can be a name, number, etc. that can be manually set to identify the company.

[0056] Optionally, the terminal device can also send the associated information and the target server information (the name, identifier, or address of the target server, etc.) to the network device so that the network device can query the enterprise to which it belongs and the server to which it belongs.

[0057] 3) The target server receives the association information sent by the terminal device and saves the association relationship, that is, it saves the association relationship between the network device's identifier and the enterprise identifier. If the enterprise's information does not exist on the server, that is, if the enterprise is connecting to the network device on the server for the first time, the server will create a new enterprise identifier for the enterprise and associate the network device's identifier with the enterprise identifier; if the enterprise's information exists on the server, that is, if the enterprise is not connecting to the network device on the server for the first time, the server will directly associate the network device's identifier with the enterprise identifier.

[0058] Optionally, the target server can send the association information to the registration service center, which is used to store and manage the registration information of various network devices and enterprises on the server.

[0059] 4) When the network device powers on, it obtains the address of its affiliated server, i.e., the address of the target server, and initiates a service activation request to the target server. The service activation request carries the identifier of the network device. The network device can determine which server it belongs to by obtaining the name, identifier, or address of the target server from the registration service center (after knowing which server it belongs to, the network device can determine the address of the target server based on its internally stored information), or by obtaining the address of the target server based on the association information sent by the terminal device and the target server information.

[0060] 5) Upon receiving the commissioning request from the network device, the target server, based on the network device's identifier and its affiliated enterprise identifier, sends configuration information to the network device, such as packet forwarding priority, access control list (ACL) policies, and quality of service (QoS) policies. Correspondingly, after receiving the configuration information from the target server, the network device configures itself so that it can process packets according to the configuration information in subsequent applications. This completes the commissioning of the network device.

[0061] In the aforementioned network device commissioning methods, such as obtaining the network device's identifier, uploading the network device's identifier to the target server, and assigning the target server to the network device, these operations require the enterprise's network administrators to go to the network device installation site to complete them. However, when the enterprise's network administrators are far away from the network device installation site or even in different locations, it is not very convenient for the enterprise's network administrators to reach the installation site, and the network device commissioning work cannot be completed quickly and efficiently.

[0062] This application provides a method for deploying network devices; see [link to relevant documentation] Figure 2 , Figure 2 This application provides a flowchart illustrating a method for deploying network devices, including but not limited to the following description.

[0063] S101. The terminal device obtains the server identifier and the enterprise identifier.

[0064] Terminal equipment refers to the equipment used by temporary operators at the location of the network equipment. The temporary operator can be anyone at the location of the network equipment, and the terminal equipment can be any electronic device with communication functions such as mobile phone, computer, tablet, iPad, laptop, watch, etc.

[0065] The server identifier indicates the server that manages the network devices. The server identifier can be a manually configured server name; for example, if the server managing the network devices is provided by provider A, the server identifier can be "Provider A Server"; if the server managing the network devices is provided by provider B, the server identifier can be "Provider B Server". The server identifier can also be the server's login address. For example, if the server managing the network devices is provided by provider A, the server identifier can be the login address of the server provided by provider A; if the server managing the network devices is provided by provider B, the server identifier can be the login address of the server provided by provider B. This application does not impose specific limitations on the server identifier, as long as the server identifier can represent the server managing the network devices.

[0066] The enterprise identifier indicates the enterprise to which the network device belongs. For example, if the network device belongs to enterprise A, the enterprise identifier can be A, where A can be the enterprise name or address, etc. When an enterprise has multiple chain enterprises, branches, subsidiaries, or affiliated enterprises, the enterprise identifier can include the address or name of a specific branch, subsidiary, or affiliated enterprise. In other words, the enterprise identifier should be able to identify which specific branch, branch, or affiliated enterprise the network device belongs to. For example, if enterprise A has three branches located in Beijing, Nanjing, and Shenzhen, and the network device belongs to an enterprise in Nanjing, then the enterprise identifier could be the name of enterprise A – Nanjing. Or, if enterprise A has three branches, namely Enterprise A Store 1, Enterprise A Store 2, and Enterprise A Store 3, and the network device belongs to Enterprise A Store 1, then the enterprise identifier could be Enterprise A Store 1; and so on. This application does not specifically limit the enterprise identifier, as long as the enterprise identifier can represent the enterprise to which the network device belongs.

[0067] The terminal device may obtain the server identifier and the enterprise identifier from the server, from other terminal devices, or from other channels. This application does not specify the method by which the terminal device obtains the server identifier and the enterprise identifier.

[0068] Once the terminal device obtains the server identifier and the enterprise identifier, it will know which server manages the network device and which enterprise the network device belongs to.

[0069] Optionally, to ensure information security, the server identifier and enterprise identifier can exist in the form of encrypted information. The terminal device receives the encrypted information, decrypts it, and obtains the server identifier and enterprise identifier. To facilitate operation by temporary personnel, the encrypted information can be in the form of a QR code. After receiving the QR code, the terminal device scans and parses it to obtain the server identifier and enterprise identifier. Alternatively, the encrypted information can also be in the form of a third-party URL link. This third-party URL link indicates how to obtain the server identifier and enterprise identifier. Temporary personnel can remotely obtain the server identifier and enterprise identifier by clicking on the third-party URL link. For example, the third-party URL link could be http: / / xxxxxx. Temporary personnel can click on the third-party URL link to invoke other local applications and obtain the server identifier and enterprise identifier from those applications; or, without manual clicking, the terminal device can automatically redirect to a page based on the third-party URL link to obtain the server identifier and enterprise identifier. For example, the encrypted information can also be in the form of a fourth URL link, where the fourth URL link includes a server identifier and a company identifier. For instance, the fourth URL link could be 123456ab: / Provider A Server / Company A's Name / , where "Provider A Server" is the server identifier and "Company A's Name" is the company identifier. These examples of third and fourth URL links are for illustrative purposes only, and this application does not impose specific limitations on their forms.

[0070] Optionally, the terminal device scanning and parsing the QR code to obtain the server identifier and enterprise identifier may further include: the terminal device scanning and parsing the QR code to obtain a first Uniform Resource Locator (URL) link, and then obtaining the server identifier and enterprise identifier based on the first URL link. One implementation of obtaining the server identifier and enterprise identifier based on the first URL link is that a temporary operator remotely obtains the server identifier and enterprise identifier by clicking on the first URL link; another implementation is that after the terminal device obtains the first URL link by scanning the QR code, it automatically redirects to a page based on the first URL link without requiring a click from a temporary operator, and remotely obtains the server identifier and enterprise identifier; yet another implementation is that a temporary operator clicks on the first URL link to invoke other local applications and obtains the server identifier and enterprise identifier from those applications; still another implementation is that after the terminal device obtains the first URL link by scanning the QR code, it automatically invokes other local applications based on the first URL link without requiring a click from a temporary operator, and obtains the server identifier and enterprise identifier from those applications. Optionally, the terminal device scans and parses the QR code to obtain the server identifier and the enterprise identifier. It may also include: the terminal device scans and parses the QR code to obtain a second URL link, wherein the second URL link includes the server identifier and the enterprise identifier.

[0071] In this application, the server identifier and enterprise identifier are in the form of a QR code or a URL link. This is to ensure information security and prevent tampering or accidental modification, and also to facilitate operation by temporary personnel. This application eliminates the need for temporary personnel to manually input the server identifier and enterprise identifier, avoiding the drawbacks of input errors caused by manual input, and has the advantages of convenient operation and improved efficiency.

[0072] Optionally, the encrypted information may also include account permission information, which indicates the permissions possessed by the terminal device. For example, this includes the permission to associate the network device's identifier with the enterprise identifier, generate associated information, and send the generated associated information to the server indicated by the server identifier. For instance, the account permission information may include a temporary account used to log in to a specified application on the terminal device. In this example, after a temporary operator logs in to the specified application using the temporary account, they perform subsequent steps S102 and S103 through that application. See the description of steps S102 and S103 for details. Steps S102 and S103 must be completed through the specified application; other methods are not feasible. This is to prevent unauthorized or accidental operations and ensure information security. To further ensure information security, the account permission information may also include operational permissions related to the temporary account, such as the validity period or validity time limit of the temporary account, the number of times or the number of terminals allowed to log in using the temporary account, etc.

[0073] Optionally, to facilitate operation by temporary personnel, the server identifier, enterprise identifier, and account permission information can be in the form of a QR code. That is, after receiving the QR code, the terminal device can directly obtain the server identifier and enterprise identifier by scanning and parsing, and at the same time automatically log in to the designated application using the temporary account, and perform the following steps S102 and S103 through the designated application on the terminal device.

[0074] Optionally, if the network device is a gateway device, the terminal device can also obtain a Point-to-Point Protocol over Ethernet (PPPoE) account and password, which are used for network device configuration. The PPPoE account and password can also be obtained in the form of a QR code along with server identifiers, enterprise identifiers, and other information.

[0075] Optionally, the QR code can also be an encrypted QR code. The terminal device scans and decrypts the received encrypted QR code to obtain the server identifier and enterprise identifier, and at the same time automatically logs into the specified application using a temporary account.

[0076] The information carried in a QR code can be determined according to specific circumstances. To facilitate understanding, the following two examples illustrate this.

[0077] Example 1: Server Identifier = Provider A Server\Enterprise Identifier = Enterprise A's Name - Nanjing\Temporary Account = abc\Temporary Account Validity Period = March 11, 10:00-12:00\Temporary Account Allowed Login Times = 1

[0078] Example 2: Server Identifier = Provider A Server\Enterprise Identifier = Enterprise A's Name - Nanjing\Temporary Account = abcdef\PPPOE Account = def\PPPOE Password = 123

[0079] In Example 1, the QR code carries information such as server identifier, enterprise identifier, temporary account, validity period of the temporary account, and allowed login count. In Example 2, the QR code carries information such as server identifier, enterprise identifier, temporary account, PPPoE account, and PPPoE password. These two examples are merely illustrations of the content and format carried in QR codes and are not intended to limit this application. The encrypted information in QR code form is just one example of this application; encrypted information can also exist in other forms, such as barcodes, etc., and this application does not make any specific limitations.

[0080] Optionally, the process of the terminal device obtaining the server identifier and enterprise identifier may further include: the terminal device obtaining voice information, then recognizing the voice information to obtain the server identifier and enterprise identifier. The voice information may be obtained from a server or from other terminal devices. The terminal device automatically obtains the server identifier and enterprise identifier by recognizing the voice information, without the need for manual input. Optionally, the voice information may also include account permission information, etc.

[0081] S102. The terminal device obtains the identifier of the network device.

[0082] Identification of network devices can include, for example, the network device's electronic serial number, MAC address, or a name that is manually set for the network device.

[0083] Terminal devices can obtain the identifier of network devices by scanning the network device's barcode or QR code, or by manually entering it.

[0084] Optionally, after logging into the designated application, the terminal device can scan the network device's barcode or QR code through the application to obtain the network device's identifier.

[0085] S103. The terminal device associates the network device identifier with the enterprise identifier to obtain the association information.

[0086] The terminal device associates the network device's identifier with the corporate identifier of the company to which the network device belongs, thereby obtaining association information. Optionally, the network device's identifier can be associated with the corporate identifier of the company to which it belongs through a specified application.

[0087] For example, Table 1 is an example table of association information provided in this application, in which "electronic serial number" represents the identifier of a router, "name of enterprise A - Nanjing" represents the identifier of enterprise A, and this association information indicates that the enterprise to which the router belongs is enterprise A.

[0088] Table 1

[0089] Electronic serial number Company A's Name - Nanjing

[0090] S104. The terminal device sends the association information to the server indicated by the server identifier, and the server receives the association information sent by the terminal device accordingly.

[0091] The terminal device sends the association information to the server indicated by the server identifier. Accordingly, the server receives the association information sent by the terminal device and knows the identifier of the network device and which enterprise the network device belongs to.

[0092] Optionally, if the network device is a gateway device, the terminal device can also send the PPPoE account and PPPoE password to the network device.

[0093] S105. The server stores the association between the identifiers of network devices and the enterprise identifiers.

[0094] S106. The server receives the commissioning request sent by the network device.

[0095] After the network device powers on, it sends a commissioning request to the server. The commissioning request includes the network device's identifier, and the server receives the commissioning request accordingly. The method by which the network device determines which server to send its commissioning request to has been described above and will not be repeated here.

[0096] Optionally, if the network device is a gateway device, after the network device is powered on, it will receive and configure its own PPPoE account and PPPoE password, and then send an activation request to the server.

[0097] S107. The server sends configuration information to the network devices.

[0098] The server sends configuration information to the network devices so that the network devices can complete the initial configuration.

[0099] As can be seen, the terminal device obtains the server identifier and enterprise identifier, then obtains the network device identifier, and then associates the network device identifier and enterprise identifier to generate association information, which is then sent to the server indicated by the server identifier. The server receives the association information and saves the association relationship between the network device identifier and the enterprise identifier. When it receives a network device commissioning application, the application carries the network device identifier, and the server sends commissioning configuration information to the network device, completing the commissioning of the network device. In this application, the server identifier and enterprise identifier can exist in the form of a QR code, a URL link, or even voice information, ensuring information security and facilitating operation by temporary personnel. This method is characterized by fast commissioning speed and simple operation.

[0100] See Figure 3 , Figure 3 This is a schematic diagram of a network device deployment apparatus 300 provided in an embodiment of this application. The apparatus 300 includes: an acquisition unit 301, used to acquire a server identifier and an enterprise identifier, and also used to acquire the identifier of the network device, specifically for performing... Figure 2 Steps S101 and S102; the association unit 302 is used to associate the network device identifier and the enterprise identifier to generate association information, which can be used to execute Figure 2 Step S103; Communication unit 303, used to send the associated information to the server indicated by the server identifier, specifically communication unit 303 can be used to perform Figure 2 Step S104 in the process.

[0101] The network device deployment apparatus 300 corresponds to the terminal device in the above method embodiment. Each unit in the network device deployment apparatus 300 is used to implement various steps and methods implemented by the terminal device in the method embodiment. For specific details, please refer to the description of the above method. For the sake of brevity, it will not be repeated here.

[0102] The division of the above-mentioned functional units in the network device deployment apparatus 300 is only for illustrative purposes. In actual applications, the above functions can be assigned to different functional units as needed. That is, the internal structure of the network device deployment apparatus 300 can be divided into different functional units to realize all or part of the functions described in the method embodiment.

[0103] See Figure 4 , Figure 4 This is a schematic diagram of a terminal device 400 provided in an embodiment of this application, which includes at least: a processor 410, a transceiver 420, and a memory 430, wherein the processor 410, transceiver 420, and memory 430 are coupled through a bus 440.

[0104] Processor 410 executes program code stored in memory 430. Figure 3 The processor 410 comprises an acquisition unit 301, an association unit 302, and a communication unit 303. In practical applications, the processor 410 may include one or more general-purpose processors. These general-purpose processors can be any type of device capable of processing electronic instructions, including a central processing unit (CPU), microprocessor, microcontroller, main processor, controller, and ASIC (Application Specific Integrated Circuit), etc. The processor 410 reads the program code stored in the memory 430 and, in cooperation with the transceiver 420, executes some or all of the steps of the method performed by the interface data playback device 40 in the above embodiments of this application.

[0105] Transceiver 420 can be a wired interface (e.g., an Ethernet interface) for communicating with other computing nodes or devices. When transceiver 420 is a wired interface, it can employ a protocol family above TCP / IP, such as RAAS, Remote Function Call (RFC), Simple Object Access Protocol (SOAP), Simple Network Management Protocol (SNMP), Common Object Request Broker Architecture (CORBA), and distributed protocols, etc. Transceiver 420 can also be a specific device used to receive or send data information.

[0106] The memory 430 can store program code and program data. The program code includes the code for the acquisition unit 301, the code for the association unit 302, and the code for the communication unit 303. The program data includes: server identifier, enterprise identifier, network device identifier, association information, etc. In practical applications, the memory 430 can include volatile memory, such as random access memory (RAM); the memory can also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid-state drive (SSD); the memory can also include combinations of the above types of memory.

[0107] Optionally, the terminal device 400 may also include a user interface for receiving user operations, such as clicking on a first URL link or a second URL link.

[0108] In the device 300 for deploying network equipment, the acquisition unit 301 and the association unit 302 may be located in the processor 410 of the terminal device 400; the communication unit 303 may be located in the transceiver of the terminal device 400.

[0109] See Figure 5 , Figure 5 This application provides a schematic diagram of the structure of a server 500, which can be implemented in the cloud and includes at least one computing node 510 and at least one storage node 520.

[0110] The computing node 510 includes one or more processors 511, transceivers 512 and memory 513, which can be connected via a bus 514.

[0111] Processor 511 includes one or more general-purpose processors that execute program code stored in memory 513. Figure 2The method described above. The general-purpose processor can be any type of device capable of processing electronic instructions, including a central processing unit (CPU), microprocessor, microcontroller, main processor, controller, and ASIC (Application Specific Integrated Circuit), etc. It can be a dedicated processor used only for computing node 510 or can be shared with other computing nodes 510. Processor 511 reads the program code stored in memory 513 and, in cooperation with transceiver 512, executes some or all of the steps in the method for deploying a network device according to the above embodiments of this application.

[0112] Transceiver 512 can be a wired interface (e.g., an Ethernet interface) for communicating with other computing nodes or users. When transceiver 512 is a wired interface, it can use a protocol family above TCP / IP, such as RAAS, Remote Function Call (RFC), Simple Object Access Protocol (SOAP), Simple Network Management Protocol (SNMP), Common Object Request Broker Architecture (CORBA), and distributed protocols, etc.

[0113] The memory 513 may include volatile memory, such as random access memory (RAM); the memory may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid-state drive (SSD); the memory may also include combinations of the above types of memory.

[0114] Storage node 520 includes one or more storage controllers 521 and storage arrays 522. The storage controllers 521 and storage arrays 522 can be connected via bus 523.

[0115] The storage controller 521 includes one or more general-purpose processors, wherein the general-purpose processor can be any type of device capable of processing electronic instructions, including CPUs, microprocessors, microcontrollers, main processors, controllers, and ASICs, etc. It can be a dedicated processor for a single storage node 520 or can be shared with compute node 500 or other storage nodes 520. It is understood that in this embodiment, each storage node includes one storage controller; in other embodiments, multiple storage nodes may share a single storage controller, and this is not specifically limited here.

[0116] Memory array 522 may include multiple memories. These memories may be non-volatile memories, such as ROM, flash memory, HDDs, or SSDs, and may also include combinations of these types of memories. For example, a memory array may consist of multiple HDDs or multiple SSDs, or it may consist of both HDDs and SSDs. Multiple memories, with the assistance of memory controller 521, are combined in different ways to form memory groups, thereby providing higher storage performance and data backup technology than a single memory. Optionally, memory array 522 may include one or more data centers. Multiple data centers may be located in the same location or in different locations; no specific limitation is made here. Memory array 522 may store program code and program data.

[0117] Server 500 is possible Figure 1 Any server in the cloud provided by a certain provider. The transceiver 512 in the server 500 can be used to receive association information sent by terminal devices, or to receive opening requests sent by network devices, or to send configuration information to network devices; the memory 513 or memory array 522 can be used to store the received association information, etc.

[0118] In some possible embodiments, the server described above can be implemented as a virtualized device.

[0119] For example, a virtualization device can be a virtual machine (VM) running a program for sending messages, deployed on hardware devices (e.g., a physical server). A virtual machine refers to a complete computer system simulated by software, possessing full hardware system functionality and running in a completely isolated environment; a virtual machine can be configured as a server. For example, a virtual server can be implemented based on a general-purpose physical server combined with Network Functions Virtualization (NFV) technology. Those skilled in the art can readily visualize a virtual server with the aforementioned functions on a general-purpose physical server by combining NFV technology after reading this application; further details are omitted here.

[0120] Virtualization devices can be containers, which are entities used to provide isolated virtualized environments. For example, a container can be a Docker container, and it can be configured as a server. For instance, a server can be created using a corresponding image; for example, a container instance of `proxy-container`, which provides proxy services, can be created and provided as a server. When implemented using container technology, servers can run on the kernel of a physical machine, and multiple servers can share the operating system of the physical machine. Container technology can isolate different servers. Containerized servers can run in virtualized environments, such as virtual machines, or directly on physical machines.

[0121] For example, a virtualization device can be a Pod. A Pod is the basic unit used by Kubernetes (Kubernetes is an open-source container orchestration engine from Google, often shortened to K8s) for deploying, managing, and orchestrating containerized applications. A Pod can include one or more containers. Each container in the same Pod is typically deployed on the same host, so each container in the same Pod can communicate through that host and share its storage and network resources. A Pod can be configured as a server. Specifically, a Pod can be created by instructing Container as a Service (CaaS, a container-based PaaS service) to provide the Pod as a server.

[0122] Of course, servers can also be other virtualization devices, which will not be listed here.

[0123] In some possible embodiments, the server described above can also be implemented by a general-purpose processor. For example, the general-purpose processor can be a chip. Specifically, the general-purpose processor implementing the server includes processing circuitry and input and output interfaces internally connected and communicating with the processing circuitry. The processing circuitry is used to execute the message generation step in the various method embodiments above through the input interface, the receiving step in the various method embodiments above through the input interface, and the sending step in the various method embodiments above through the output interface. Optionally, the general-purpose processor may also include a storage medium, and the processing circuitry is used to execute the storage step in the various method embodiments above through the storage medium. The storage medium may store instructions executed by the processing circuitry, and the processing circuitry is used to execute the instructions stored in the storage medium to execute the various method embodiments above.

[0124] See Figure 6This application provides a system 600, which includes a terminal device 601 and a server 602. Optionally, the terminal device 601 may be a device 300 or a terminal device 400 that deploys network equipment, and the server 602 may be a server 500 or a virtual server.

[0125] Optionally, system 600 may also include a network device connected to server 602. The network device can be any of a router, switch, firewall, etc.

[0126] This application provides a computer program product that, when run on a terminal device, causes the terminal device to perform the above-described actions. Figure 2 Examples of the methods described.

[0127] Those skilled in the art will recognize that the method steps and units described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the steps and components of each embodiment have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0128] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be found in the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0129] In the several embodiments provided in this application, the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, or it may be an electrical, mechanical, or other form of connection.

[0130] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiments of this application, depending on actual needs.

[0131] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0132] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0133] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. This computer program product includes one or more computer program instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., digital video disc (DVD), or a semiconductor medium (e.g., solid-state drive), etc.

[0134] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for deploying network devices, characterized in that, include: The terminal device obtains a server identifier and an enterprise identifier. The terminal device is a device used by a temporary operator at the location of the network device. The server identifier indicates the server that manages the network device, and the enterprise identifier indicates the enterprise to which the network device belongs. The server does not belong to the enterprise. Obtain the identifier of the network device; The identifier of the network device and the enterprise identifier are associated to generate association information; The associated information is sent to the server indicated by the server identifier.

2. The method according to claim 1, characterized in that, The acquisition of the server identifier and enterprise identifier includes: Obtain encrypted information; The encrypted information is decrypted to obtain the server identifier and the enterprise identifier.

3. The method according to claim 2, characterized in that, The encrypted information may take the form of a QR code; Accordingly, the step of decrypting the encrypted information to obtain the server identifier and the enterprise identifier includes: The QR code is scanned and parsed to obtain the server identifier and the enterprise identifier.

4. The method according to claim 3, characterized in that, The step of scanning and parsing the QR code to obtain the server identifier and the enterprise identifier includes: The QR code is scanned and parsed to obtain the URL link of the first Uniform Resource Locator; Based on the first URL link, obtain the server identifier and enterprise identifier.

5. The method according to claim 3, characterized in that, The step of scanning and parsing the QR code to obtain the server identifier and the enterprise identifier includes: The QR code is scanned and parsed to obtain a second Uniform Resource Locator (URL) link; wherein the second URL link includes the server identifier and the enterprise identifier.

6. The method according to claim 2, characterized in that, The encrypted information includes a third Uniform Resource Locator (URL) link; the third URL link indicates the acquisition of the server identifier and the enterprise identifier. Accordingly, the step of decrypting the encrypted information to obtain the server identifier and the enterprise identifier includes: The server identifier and the enterprise identifier are obtained based on the third URL link.

7. The method according to claim 2, characterized in that, The encrypted information is in the form of a fourth Uniform Resource Locator (URL) link; the fourth URL link includes the server identifier and the enterprise identifier.

8. The method according to any one of claims 2-7, characterized in that, The encrypted information also includes account permission information; The account permission information indicates the permissions possessed by the terminal device, including associating the identifier of the network device with the enterprise identifier to generate the association information, and / or sending the association information to the server indicated by the server identifier.

9. The method according to claim 1, characterized in that, The acquisition of the server identifier and enterprise identifier includes: Obtain voice information; The voice information is recognized to obtain the server identifier and the enterprise identifier.

10. An apparatus for deploying network equipment, said apparatus being a terminal device used by temporary operators at the location of the network equipment, characterized in that, include: The acquisition unit is used to acquire a server identifier and an enterprise identifier; the server identifier indicates the server that manages the network device, and the enterprise identifier indicates the enterprise to which the network device belongs; The acquisition unit is further configured to acquire the identifier of the network device; The association unit is used to associate the identifier of the network device with the enterprise identifier to generate association information; A communication unit is used to send the associated information to the server indicated by the server identifier.

11. The apparatus according to claim 10, characterized in that, The acquisition unit is used for: Obtain encrypted information; The encrypted information is decrypted to obtain the server identifier and the enterprise identifier.

12. The apparatus according to claim 11, characterized in that, The encrypted information may take the form of a QR code; The acquisition unit is used to: scan and parse the QR code to obtain the server identifier and the enterprise identifier.

13. The apparatus according to claim 12, characterized in that, The acquisition unit is used for: The QR code is scanned and parsed to obtain the URL link of the first Uniform Resource Locator; Based on the first URL link, obtain the server identifier and enterprise identifier.

14. The apparatus according to claim 12, characterized in that, The acquisition unit is used for: The QR code is scanned and parsed to obtain a second Uniform Resource Locator (URL) link; wherein the second URL link includes the server identifier and the enterprise identifier.

15. The apparatus according to claim 11, characterized in that, The encrypted information includes a third Uniform Resource Locator (URL) link; the third URL link indicates the acquisition of the server identifier and the enterprise identifier. The acquisition unit is used to: obtain the server identifier and the enterprise identifier based on the third URL link.

16. The apparatus according to claim 11, characterized in that, The encrypted information is in the form of a fourth Uniform Resource Locator (URL) link; the fourth URL link includes the server identifier and the enterprise identifier.

17. The apparatus according to any one of claims 11-16, characterized in that, The encrypted information also includes account permission information; The account permission information indicates the permissions possessed by the terminal device, including associating the identifier of the network device with the enterprise identifier to generate the association information, and / or sending the association information to the server indicated by the server identifier.

18. The apparatus according to claim 10, characterized in that, The acquisition unit is used for: Obtain voice information; The voice information is recognized to obtain the server identifier and the enterprise identifier.

19. A terminal device, characterized in that, The method includes a memory and a processor, wherein the memory is used to store instructions, and the processor is used to invoke the instructions stored in the memory to execute the method as described in any one of claims 1-9.

20. A computer storage medium, characterized in that, Includes program instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-9.

21. A system, characterized in that, It includes a terminal device and a server, wherein the terminal device is used to perform the method according to any one of claims 1-9.

Images