CN113821334A

CN113821334A - Method, device and system for configuring edge side equipment

Info

Publication number: CN113821334A
Application number: CN202010599733.7A
Authority: CN
Inventors: 蔡志方
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-06-18
Filing date: 2020-06-28
Publication date: 2021-12-21
Also published as: WO2021254466A1

Abstract

The application discloses a method, a device and a system for configuring edge side equipment, which are used for solving the problem of low configuration efficiency of the edge side equipment. The proxy edge device may obtain first configuration information corresponding to the target edge device, and send the first configuration information to the target edge device, where the first configuration information may be used to configure the target edge device to establish a connection with the cloud center. In the process of establishing the connection between the target edge side equipment and the cloud center, the agent edge side equipment sends the first configuration information required for establishing the connection between the agent edge side equipment and the cloud center to the target edge side equipment, and operation and maintenance personnel do not need to manually configure the target edge side equipment item by item, so that the configuration efficiency of the target edge side equipment can be effectively improved.

Description

Method, device and system for configuring edge side equipment

The present application claims priority from the chinese patent application filed on 18/6/2020 of china intellectual property office under the name "a method and apparatus for configuring edge side devices" under the application number 202010560994.8, the entire contents of which are incorporated herein by reference.

Technical Field

The embodiment of the application relates to the technical field of edge computing, in particular to a method, a device and a system for configuring edge side equipment.

Background

Although the cloud center has a strong data processing capability and can calculate and feed back mass data sent by the edge side device, as the requirement of a user on clouding becomes higher and higher, the real-time performance of the cloud center for processing data, the bandwidth for transmitting data, and the like are gradually difficult to meet the requirement of the user.

And the edge computing can transfer the computing work of the cloud center part to the edge side equipment, so that the defect of the cloud center can be effectively made up. The cloud center may use the resources of the edge-side device as an extension of the cloud center resources, and provide corresponding data processing services for the user by using the resources of the edge-side device, which may be referred to as "edge-side cooperation" or "edge-cloud cooperation".

At present, when edge-side equipment is deployed, operation and maintenance personnel mainly perform manual configuration item by item on the edge-side equipment to be deployed, for example, authentication information required by registering the edge-side equipment to a cloud center is configured on the edge-side equipment. Generally, the operation of configuring the edge side device is complicated and error-prone, which makes the configuration of the edge side device generally inefficient.

Disclosure of Invention

The embodiment of the application provides a method, a device and a system for configuring edge side equipment, which are used for solving the problem of low configuration efficiency of the edge side equipment.

In a first aspect, an embodiment of the present application provides a method for configuring an edge side device, where the method may be applied to a proxy edge side device, and the method includes: the proxy edge side device obtains first configuration information corresponding to a target edge side device, and sends the first configuration information to the target edge side device, where the first configuration information may be used to configure the target edge side device to establish a connection with a cloud center. In the process of establishing connection between the target edge side equipment and the cloud center, the agent node sends the first configuration information required for establishing connection between the target edge side equipment and the cloud center to the target edge side equipment, so that the target edge side equipment can be connected with the cloud center based on the received first configuration information, operation and maintenance personnel do not need to manually configure the target edge side equipment to be deployed item by item, and the configuration efficiency of the target edge side equipment can be improved.

In one possible embodiment, the method may further include: the proxy edge side device sends a first request to the cloud center, where the first request may include an identifier of a target edge side device, where the identifier may be, for example, a serial number of the target edge side device, so as to request, by using the first request, first configuration information corresponding to the target edge side device from the cloud center; then, the proxy edge device may obtain first configuration information corresponding to the target edge device, and the process may specifically be, for example, receiving a response message from the cloud center, where the response message includes the first configuration information. In this embodiment, the first configuration information required by the target edge device may be located in the cloud center, and the proxy edge device may apply the first configuration information to the cloud center for the target edge device, so that the target edge device may obtain the first configuration information from the proxy edge device, and thus establish a communication connection with the cloud center.

In a possible implementation manner, the process of acquiring, by the proxy edge device, the first configuration information corresponding to the target edge device may specifically be that the proxy edge device first acquires an identifier of the target edge device, and then determines, according to the identifier of the target edge device, the first configuration information corresponding to the target edge device from the locally stored first configuration information corresponding to at least one edge device. In this embodiment, the proxy edge device may store first configuration information required by the target edge device, so that the target edge device may directly obtain the first configuration information from the proxy edge device, and thus, the cloud center may not consume a certain storage space to store the first configuration information, so that the storage space of the part on the cloud center may be released, and resources on the proxy edge device may be effectively utilized.

In one possible embodiment, the method may further include: before sending the first configuration information to the target edge side device, the proxy edge side device may receive a second request from the target edge side device, where the second request may be used to request the proxy edge side device to serve as a proxy node of the target edge side device; then, the proxy edge device may establish a proxy relationship with the target edge device according to the second request, specifically, a response message for the second request may be first sent to the target edge device, where the response message may be used to indicate that the proxy edge device is capable of serving as a proxy node of the target edge device, and then the proxy edge device may receive a proxy confirmation message from the target edge device, so as to establish the proxy relationship between the proxy edge device and the target edge device according to the proxy confirmation message. In this embodiment, the target edge device may apply for a proxy node (i.e., a proxy edge device) in the network in a multicast or broadcast manner, so as to obtain, for the target edge device, first configuration information required for connection with the cloud center based on the proxy node.

In a possible implementation manner, before the proxy edge side device establishes the proxy relationship between the proxy edge side device and the target edge side device according to the second request, the method may further include: the proxy edge side device determines that a proxy state of the proxy edge side device satisfies a preset condition, where the proxy state includes a proxy number of the proxy edge side device and/or a number of edge side devices that have established a proxy relationship with the proxy edge side device, and correspondingly, the preset condition may be that, for example, the proxy number of the proxy edge side does not exceed the preset number, and/or the number of edge side devices that have established a proxy relationship with the proxy edge side device does not exceed the preset number. The agent edge side equipment can avoid the excessive agent tasks born by the agent edge side equipment as much as possible by monitoring the agent state of the agent edge side equipment, so that the load of the agent edge side equipment in the network is unbalanced. For example, when the lower edge devices of a certain proxy edge device are more than the preset number, new lower edge devices may not be added to the proxy edge device, and other edge devices in the network may be selected to become proxy edge devices, so that the network utilization rate between nodes may be improved.

Further, after the proxy edge device becomes a proxy node of the target edge device and establishes a proxy relationship with the target edge device, the proxy edge device may update its own proxy state, for example, the number of subordinate edge devices that the proxy edge device proxies may be updated from 45 to 46.

In one possible embodiment, the method may further include: and the proxy edge side equipment sends second configuration information corresponding to the target edge side equipment, wherein the second configuration information can be used for configuring business services corresponding to the target edge side equipment. The second configuration information may be, for example, a container mirror of a service, resource occupation information of different service, and the like, and the resource occupation information of the service may include, for example, a memory that can be occupied by each service on a target edge device, a CPU occupation rate of the target edge device allowed when the service is processed, and a computing capability of the target edge device required for processing the service. Therefore, the automatic configuration of the business service corresponding to the target edge side equipment can be realized, and the corresponding business service does not need to be manually deployed for the target edge side equipment by operation and maintenance personnel.

In one possible embodiment, the method may further include: the proxy edge side device synchronizes the first configuration information and/or the second configuration information to the backup edge side device, so that when the proxy edge side device fails, the backup edge side device can take over the proxy edge side device to continue management, and becomes a new proxy node of a lower-level edge side device of the proxy edge side device.

In a possible implementation, after establishing the proxy relationship between the proxy edge-side device and the target edge-side device, the method may further include: and the agent edge side equipment receives the target program from the cloud center and sends the target program to the target edge side equipment, and the target edge side equipment and the agent edge side equipment are positioned in the same network area. In this embodiment, after the agent edge device establishes an agent relationship with the target edge device, a hierarchical tree-type agent network may be formed, so that, when the cloud center needs to issue the target program to each edge device in the network, the information may be distributed to each edge device of its agent by the corresponding agent edge device, so that the cloud center may only send the target program to a small number of agent edge devices without sending the target program to the remaining agent edge devices, and the remaining agent edge devices may obtain the target program from the corresponding agent edge devices, thereby reducing resource consumption required by the cloud center and reducing dependency of the edge devices on the cloud center; moreover, the plurality of agent edge side devices can send the target program to the plurality of agent edge sides in parallel, and compared with a mode that the target program is sent to the edge side devices one by the cloud center, the efficiency of obtaining the target program by the edge side devices in the whole network can be effectively improved. As an example, the target program may be, for example, a new version of firmware, or may be software to be distributed or data to be synchronized.

In a second aspect, an embodiment of the present application further provides a method for configuring an edge-side device, where the method may be applied to a target edge-side device, and the method includes: the target edge side equipment receives first configuration information corresponding to the agent edge side equipment, and establishes connection with the cloud center according to the first configuration information. In the process of establishing connection between the target edge side equipment and the cloud center, the agent node sends the first configuration information required for establishing connection between the target edge side equipment and the cloud center to the target edge side equipment, so that the target edge side equipment can automatically establish connection with the cloud center based on the received first configuration information, operation and maintenance personnel do not need to manually configure the target edge side equipment to be deployed item by item, and the configuration efficiency of the target edge side equipment can be improved.

In one possible embodiment, the method further comprises: the target edge side device may send a second request to the proxy edge side device, where the second request may be used to request the proxy edge side device to serve as a proxy node of the target edge side device, and then the target edge side device may receive a response message from the proxy edge side device for the second request, and send a proxy acknowledgement message to the proxy edge side device, where the proxy acknowledgement message is used to notify the proxy edge side device to establish a proxy relationship. In this embodiment, the target edge device may apply for a proxy node (i.e., a proxy edge device) in the network in a multicast or broadcast manner, so as to obtain, for the target edge device, first configuration information required for connection with the cloud center based on the proxy node.

In one possible embodiment, the method may further include: the target edge device may receive second configuration information corresponding to the target edge device from the proxy edge device or from the cloud center, and configure a service corresponding to the target edge device according to the second configuration information. For example, the second configuration information may be, for example, a container mirror of a service, resource occupation information of different services, and the like, where the resource occupation information of a service may include, for example, a memory that can be occupied by each service on a target edge device, a CPU occupancy of the target edge device allowed when the service is processed, and a computing capability of the target edge device required for processing the service. The target edge side device can automatically configure the business service corresponding to the target edge side device according to the acquired second configuration information, so that operation and maintenance personnel do not need to manually deploy the corresponding business service for the target edge side device.

In one possible embodiment, the method further comprises: and receiving the target program from the agent edge side equipment, wherein the target edge side equipment and the agent edge side equipment are positioned in the same network area. In this embodiment, the cloud center may be each edge side device that distributes the information to its agent through the corresponding agent edge side device, so that the cloud center may only need to send the target program to a smaller number of agent edge side devices, and need not send the target program to the remaining proxied edge side devices, and the remaining proxied edge side devices may obtain the target program from the corresponding agent edge side devices, thereby reducing resource consumption required by the cloud center and reducing dependence of the edge side devices on the cloud center; moreover, the plurality of agent edge side devices can send the target program to the plurality of agent edge sides in parallel, and compared with a mode that the target program is sent to the edge side devices one by the cloud center, the efficiency of obtaining the target program by the edge side devices in the whole network can be effectively improved.

In a third aspect, an embodiment of the present application further provides a method for configuring an edge device, where the method may be applied to a cloud center, and the method includes: the cloud center determines first configuration information corresponding to the target edge side device, and sends the first configuration information to the agent edge side device, wherein the first configuration information can be used for configuring the target edge side device to establish connection with the cloud center; then, the cloud center may check whether the first configuration information from the target edge-side device is consistent with the first configuration information sent by the cloud center to the proxy edge-side device, and establish a connection with the target edge-side device if the first configuration information is consistent with the first configuration information. In the process of establishing connection between the target edge side equipment and the cloud center, the cloud center issues the first configuration information to the agent edge side equipment, and the agent edge side equipment forwards the first configuration information to the target edge side equipment, so that the target edge side equipment can automatically establish connection with the cloud center based on the received first configuration information, operation and maintenance personnel do not need to manually configure the target edge side equipment to be deployed item by item, and the configuration efficiency of the target edge side equipment can be improved.

In one possible embodiment, the method further comprises: the cloud center receives a first request from the agent edge side device, where the first request includes an identifier of the target edge side device, and then the cloud center may determine first configuration information corresponding to the target edge side device according to the identifier of the target edge side device. In this embodiment, the first configuration information required by the target edge device to establish the communication connection with the cloud center may be located in the cloud center, and the proxy edge device may apply for the first configuration information from the target edge device to the cloud center, so that the target edge device can obtain the first configuration information from the proxy edge device and establish the communication connection with the cloud center.

In one possible embodiment, the method further comprises: and sending the target program to the agent edge side equipment, wherein the target edge side equipment and the agent edge side equipment are positioned in the same network area. In this embodiment, the cloud center may be each edge side device that distributes the information to its agent through the corresponding agent edge side device, so that the cloud center may only need to send the target program to a smaller number of agent edge side devices, and need not send the target program to the remaining proxied edge side devices, and the remaining proxied edge side devices may obtain the target program from the corresponding agent edge side devices, thereby reducing resource consumption required by the cloud center and reducing dependence of the edge side devices on the cloud center; moreover, the plurality of agent edge side devices can send the target program to the plurality of agent edge sides in parallel, and compared with a mode that the target program is sent to the edge side devices one by the cloud center, the efficiency of obtaining the target program by the edge side devices in the whole network can be effectively improved.

In one possible embodiment, the method may further include: and the cloud center sends second configuration information corresponding to the target edge side equipment based on the established connection between the cloud center and the target edge side equipment, wherein the second configuration information is used for configuring business services corresponding to the target edge side equipment. In this embodiment, after the target edge device establishes a connection with the cloud center based on the first configuration information, the cloud center may directly issue the second configuration information to the target edge device based on the connection, so as to implement automatic configuration of the business service uplinked to the target edge device, thereby avoiding manual configuration by operation and maintenance personnel, improving configuration efficiency of the business service, and reducing operations of the operation and maintenance personnel.

In a fourth aspect, based on the same inventive concept as the method embodiment of the first aspect, an embodiment of the present application provides an apparatus, where the apparatus is applied to the proxy edge-side device described in the first aspect, that is, the apparatus may be a proxy edge-side device, and may also be a chip or a processor that can be applied to the proxy edge-side device. The apparatus has the function of implementing the embodiments of the first aspect described above. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a fifth aspect, based on the same inventive concept as the method embodiment of the second aspect, an embodiment of the present application provides an apparatus, which is applied to the target edge-side device described in the second aspect, that is, the apparatus may be the target edge-side device, or may be a chip or a processor that can be applied to the target edge-side device. The apparatus has the function of implementing the embodiments of the second aspect described above. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a sixth aspect, based on the same inventive concept as the method embodiment of the third aspect, an embodiment of the present application provides an apparatus, where the apparatus is applied to the cloud center described in the third aspect, that is, the apparatus may be a cloud center, or may be a chip or a processor that can be applied to the cloud center. The apparatus has a function of realizing the embodiments of the third aspect described above. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a seventh aspect, an embodiment of the present application provides an apparatus, including: a processor and a memory; the memory is configured to store instructions, and when the apparatus is executed, the processor executes the instructions stored in the memory, so as to cause the apparatus to perform the method for configuring an edge device in the first aspect or any implementation method of the first aspect. It should be noted that the memory may be integrated into the processor or may be independent from the processor. The apparatus may also include a bus. Wherein, the processor is connected with the memory through a bus. The memory may include a readable memory and a random access memory, among others.

In an eighth aspect, an embodiment of the present application provides an apparatus, including: a processor and a memory; the memory is configured to store instructions, and when the apparatus is running, the processor executes the instructions stored in the memory, so as to cause the apparatus to perform the method for configuring an edge device in the second aspect or any implementation method of the second aspect. It should be noted that the memory may be integrated into the processor or may be independent from the processor. The apparatus may also include a bus.

In a ninth aspect, an embodiment of the present application provides an apparatus, including: a processor and a memory; the memory is configured to store instructions, and when the apparatus is running, the processor executes the instructions stored in the memory, so as to cause the apparatus to perform the method for configuring an edge device in any implementation method of the third aspect or the third aspect. It should be noted that the memory may be integrated into the processor or may be independent from the processor. The apparatus may also include a bus.

In a tenth aspect, an embodiment of the present application further provides a system, including the proxy edge-side device in the fourth aspect or the seventh aspect, the target edge-side device in the fifth aspect or the eighth aspect, and the cloud center in the sixth aspect or the ninth aspect. For example, the proxy edge device may send first configuration information corresponding to the target edge device; the target edge side equipment sends the first configuration information to the cloud center; and after the cloud center verifies the first configuration information from the target edge side equipment, establishing connection with the target edge side equipment.

In an eleventh aspect, embodiments of the present application further provide a readable storage medium, which stores a program or instructions, and when the readable storage medium is run on a computer, the method for configuring an edge side device according to any of the above aspects is executed.

In a twelfth aspect, embodiments of the present application further provide a computer program product containing instructions, which when run on a computer, cause the computer to execute any of the methods for configuring an edge device in the above aspects.

In addition, for technical effects brought by any implementation manner of the fourth aspect to the twelfth aspect, reference may be made to technical effects brought by different implementation manners of the first aspect to the third aspect, and details are not described here again.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art according to the drawings.

FIG. 1 is a schematic diagram of various networking architectures;

FIG. 2 is a schematic diagram of a networking architecture including a public network;

fig. 3 is a schematic signaling interaction diagram of an edge device configured in an embodiment of the present application;

fig. 4 is a schematic signaling interaction diagram illustrating that a proxy edge side device obtains first configuration information in an embodiment of the present application;

fig. 5 is a schematic structural diagram of an apparatus applied to a proxy edge-side device in an embodiment of the present application;

fig. 6 is a schematic structural diagram of a proxy edge device in an embodiment of the present application;

fig. 7 is a schematic structural diagram of an apparatus applied to an edge-side device in an embodiment of the present application;

fig. 8 is a schematic structural diagram of an edge-side device in an embodiment of the present application;

fig. 9 is a schematic structural diagram of an apparatus applied to a cloud center in an embodiment of the present application;

fig. 10 is a schematic structural diagram of a cloud center in an embodiment of the present application.

Detailed Description

The embodiment of the application can be applied to a network system comprising a cloud center and edge side equipment. The cloud center may be deployed in a cloud and is responsible for managing edge-side devices, and the cloud center may also be referred to as a management platform located in the cloud. The edge side device may be deployed outside the cloud. In a possible implementation manner, the network system may further include a third-party service platform, and the third-party service platform may cooperate with the service running on the edge side device to complete corresponding service processing.

The network system can be divided into a public network, a private network and a local network according to the networking difference, as shown in fig. 1. At present, operation and maintenance of the edge side device depend on the cloud center, and may specifically depend on a central management node on the cloud center. The operation and maintenance personnel need to manually configure configuration information required by the edge side device to be docked to the cloud center on the edge side device, so that the edge side device establishes connection with the cloud center based on the information configured by the operation and maintenance personnel, specifically, the connection between the edge side device and the cloud center through a gateway and/or a switch. However, the configuration operation that the operation and maintenance personnel need to perform on the edge-side device is generally complex, not only takes a long time, but also is prone to configuration errors, and the operation and maintenance personnel may need to manually reconfigure the edge-side device again, which results in that the configuration efficiency of the edge-side device is generally low. When the edge side equipment is deployed in a large scale in the network, the deployment efficiency of the edge side equipment is seriously reduced by the way that operation and maintenance personnel manually configure the edge side equipment item by item; in a scenario of replacing an edge device with a failure in a network, since the efficiency of manually configuring a newly replaced edge device is low, the edge device cannot provide a service for a long time, and thus an edge node where the edge device is located cannot recover the service for a long time.

Based on this, the embodiment of the present application provides a method for configuring an edge side device, so as to improve the configuration efficiency of the edge side device. Specifically, the edge devices in the network may be divided into at least two types, one type is an edge device that has been deployed in the network and establishes a connection with the cloud center, and may be used as proxy edge devices, such as proxy edge devices a to Y shown in fig. 2, and the other type is used as an edge device that is a lower device of these proxy edge devices. When a target edge device X to be configured exists in a network area where the proxy edge device is located, one of the proxy edge devices, such as the proxy edge device Y, may become a proxy node of the target edge device X, acquire first configuration information required for establishing a connection between the target edge device X and a cloud center, and then send the first configuration information to the target edge device X. In this way, the target edge device X may establish a connection with the cloud center according to the received first configuration information. In the process of establishing connection between the target edge side device X and the cloud center, the proxy edge side device Y sends the first configuration information required for establishing connection with the cloud center to the target edge side device X, and operation and maintenance personnel do not need to manually configure the target edge side device X item by item, so that the configuration efficiency of the target edge side device X can be effectively improved. Meanwhile, the process of establishing the communication connection between the target edge side device X and the cloud center is not implemented by means of a Simple Service Discovery Protocol (SSDP), so that when a public network as shown in fig. 2 exists between the target edge side device X and the cloud center, the public network does not need to be required to support a Network Address Translation (NAT) function, and thus, the requirement on the public network can be reduced, and the universality and feasibility of implementation of the scheme are improved.

In a scene of large-scale deployment of the edge side equipment, the newly deployed target edge side equipment is automatically configured by the proxy edge side equipment, so that the deployment efficiency of the edge side equipment can be effectively improved, and the network delivery progress is accelerated; in the scene of replacing the edge side equipment with failure in the network, because the efficiency of automatically configuring the newly replaced target edge side equipment is higher, the edge node where the target edge side equipment is located can recover the service in a short time and continue to provide the corresponding service.

In order to make the aforementioned objects, features and advantages of the present application more comprehensible, various non-limiting embodiments accompanying the present application examples are described below with reference to the accompanying drawings. It is to be understood that the embodiments described are only a few embodiments of the present application and not all 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.

As shown in fig. 3, a signaling interaction diagram of a method for configuring an edge device in an embodiment of the present application is specifically shown, where the method may specifically include:

s301: the proxy edge side equipment acquires first configuration information corresponding to the target edge side equipment.

In this embodiment, the edge device that has been deployed in the network and has a communication connection with the cloud center may serve as a proxy edge device, and the proxy edge device may serve as a proxy node of an edge device to be configured (hereinafter referred to as a target edge device) and assist the target edge device in establishing a connection with the cloud center.

In general, when deploying a target edge-side device, it is often difficult to establish a communication connection directly with a cloud center if the target edge-side device is not configured accordingly. Therefore, the proxy edge side device may acquire configuration information (hereinafter, referred to as first configuration information) required for the target edge side device to establish a communication connection with the cloud center. When acquiring the first configuration information, the proxy edge-side device may obtain the first configuration information by requesting the cloud center, or obtain the first configuration information corresponding to the target edge-side device from a plurality of locally stored first configuration information.

In a possible implementation manner, the proxy edge device located in the same network area as the target edge device to be configured may serve as a proxy node of the target edge device to apply for the first configuration information required for establishing the connection between the target edge device and the cloud center from the cloud center.

For example, as shown in fig. 4, the proxy edge device may obtain an identifier of the target edge device, such as a serial number of the target edge device, and generate a first request based on the identifier; then, the proxy edge-side device may send the first request to the cloud center based on the communication connection that the proxy edge-side device has established with the cloud center, so as to request the cloud center to feed back the first configuration information corresponding to the target edge-side device. The cloud center can analyze the identifier of the target edge side device from the received first request, and find out first configuration information corresponding to the target edge side device from a plurality of first configuration information stored locally in advance according to the identifier; then, the cloud center may generate a response message based on the found first configuration information, and send the response message to the proxy edge device, where the response message includes the first configuration information found by the cloud center. The proxy edge side device may parse the received response message to obtain the first configuration information, so as to subsequently forward the first configuration information to the target edge side device.

In general, there may be more than one edge device that has been deployed in the network and that establishes a communication connection with the cloud center, and therefore, when a target edge device accesses the network, one of the edge devices may be selected from the multiple edge devices that have been deployed as a proxy node of the target edge device. For example, as shown in fig. 4, the target edge-side device may broadcast or multicast a second request in a network area (e.g., a local area network, etc.) where the target edge-side device is located, where the second request is used to request the edge-side device that receives the second request to serve as a proxy node of the target edge-side device. After receiving the second request, the plurality of edge side devices (including the proxy edge side device) may send a response message for the second request to the target edge side device, where the response message may be used to indicate that the own device is capable of serving as a proxy node of the target edge side device. After receiving the response messages returned by the plurality of edge devices, the target edge device may select one of the edge devices from the edge device centers as a proxy node, where the selected edge device is the proxy edge device.

When selecting the proxy edge device, the target edge device may select the proxy edge device according to the time of receiving the response message returned by each edge device, for example, the edge device corresponding to the response message received first may be determined as the proxy edge device; alternatively, the target edge device may select the proxy edge device according to a Media Access Control (MAC) address of the edge device included in each response message, for example, the edge device with the minimum (or maximum, or random) MAC address value may be determined as the proxy edge device, and of course, the implementation of how to select the proxy edge device in this embodiment is not limited.

If the target edge side device does not receive the response messages returned by other edge side devices within the first preset time length, the second request can be broadcasted or multicasted again until the response messages returned by one or more edge side devices are received. Of course, if the number of times that the target edge device attempts to send the second request exceeds the preset threshold, or no response message returned by other edge devices is received within the second preset time length (which is greater than the first preset time length), the target edge device may submit the operation and maintenance personnel to configure the basic information.

After determining the proxy edge device, the target edge device may send a proxy confirmation message to the proxy edge device, where the proxy confirmation message may be used to notify the proxy edge device to establish a proxy relationship, so as to become a proxy node of the target edge device. After receiving the proxy confirmation message, the proxy edge device may establish and maintain a proxy relationship (e.g., may be a mapping table representing the proxy relationship) with the target edge device, and in the proxy relationship, the proxy edge device serves as a proxy node, and the target edge device serves as a lower-level edge device of the proxy node.

Further, before the edge device receiving the second request feeds back the response message to the target edge device, it may also check whether the proxy status of the edge device itself meets a preset condition to determine whether to feed back the response message. For example, the proxy status may specifically be a proxy number of the edge device (as shown in fig. 2, the proxy number of the proxy edge device a is 1, and the proxy number of the proxy edge device Y as its lower edge device is 2), and/or may be the number of lower edge devices that have established a proxy relationship with the edge device, and the like. When the agent level number of the edge device does not exceed a preset level number (e.g., level 2, etc.), and/or the number of lower-level edge devices establishing an agent relationship with the edge device does not exceed a preset number (e.g., level 50, etc.), indicating that the agent status of the edge device receiving the second request satisfies a preset condition, the edge device may send a response message for the second request to the target edge device; on the contrary, when the agent status of the edge device itself does not satisfy the preset condition, the edge device may not send the response message. Therefore, the proxy edge side device can avoid the excessively complex proxy relationship network and the concentration of the proxy relationship on one proxy edge side device by checking the proxy state of the proxy edge side device, thereby controlling the proxy pressure of the proxy edge side device. For example, when the lower edge devices of a certain proxy edge device are more than the preset number, new lower edge devices may not be added to the proxy edge device, and other edge devices in the network may be selected to become proxy edge devices, thereby improving the network utilization rate between nodes.

Accordingly, when the proxy edge device becomes a proxy node of the target edge device and establishes a proxy relationship with the target edge device, the proxy edge device may update its own proxy state, for example, the number of subordinate edge devices that the proxy edge device proxies may be updated from 45 to 46.

In other possible embodiments, the cloud center may also periodically check its own proxy state, and after determining that its own proxy state satisfies the preset condition, if receiving a second request from the target edge-side device, the proxy edge-side device may return a corresponding response message, and after determining that its own proxy state does not satisfy the preset condition, if receiving the second request, the cloud center may not respond to the second request.

For example, when the proxy edge device is a lower-level edge device of another edge device, and the cloud center sends the first configuration information to the proxy edge device, the first configuration information may be forwarded to the proxy edge device by the proxy node of the proxy edge device, or the cloud center may directly send the first configuration information to the proxy edge device. For example, as shown in fig. 2, regarding the first configuration information corresponding to the target edge-side device X, the cloud center may send the first configuration information to the proxy edge-side device a, and then the proxy edge-side device a forwards the first configuration information to the proxy edge-side device Y; or, the cloud center may also directly send the first configuration information corresponding to the target edge-side device X to the proxy edge-side device Y.

In the above embodiment, the proxy edge device obtains the first configuration information corresponding to the target edge device by applying for the first configuration information from the cloud center, but in another possible embodiment, the proxy edge device may also locally store the first configuration information corresponding to the target edge device. For example, in a scenario of replacing a failed edge device in a network, the first configuration information corresponding to the newly replaced target edge device and the failed edge device may be the same, so that the proxy node corresponding to the failed edge device may still become a proxy node of the newly replaced target edge device, and the proxy edge device serving as the proxy node may use the locally stored first configuration information corresponding to the failed edge device as the first configuration information corresponding to the target edge device.

In general, the proxy edge device may become a proxy node of the target edge device and may also be a proxy node of another edge device, and therefore, the local of the proxy edge device may store the first configuration information corresponding to a plurality of lower-level edge devices. Then, when acquiring the first configuration information corresponding to the target edge device, the proxy edge device may first acquire an identifier of the target edge device, for example, a serial number or a Node (Node) ID of the target edge device, and then determine, according to the identifier of the target edge device, the first configuration information corresponding to the target edge device corresponding to the identifier from the plurality of locally stored first configuration information.

S302: and the agent edge side equipment sends the first configuration information to the target edge side equipment.

For example, the first configuration information corresponding to the target edge device may include device network information, registration information, or other configuration information required by the edge device to interface with the cloud center. The device network information may be, for example, an Internet Protocol (IP) address allocated to the edge device, or other information related to the device; the registration information may be, for example, an IP address of the cloud center (for example, an IP address of the central management node), a user name and a password required for registration, and the like; other configuration information may include time configuration, disk configuration (e.g., configuring each partition of the disk), certificate configuration (e.g., configuring a certificate required for interfacing with the cloud center), security policy (e.g., a key for communicating with the cloud center, access rights), and the like.

S303: and the target edge side equipment sends the received first configuration information to the cloud center.

In one example, after acquiring the first configuration information, the target edge-side device may generate a registration request based on the first configuration information, where the registration request includes the first configuration information, and then the target edge-side device may send the registration request to the cloud center.

S304: and the cloud center verifies the legality of the received first configuration information from the target edge side equipment.

S305: and the cloud center is connected with the target edge side equipment.

For example, after receiving a registration request sent by a target edge device, the cloud center may analyze first configuration information corresponding to the target edge device from the registration request, and perform validity check on the analyzed first configuration information. For example, the first configuration information acquired by the target edge device may be obtained by the proxy edge device applying from the cloud center, and then the cloud center may check whether the first configuration information sent by the target edge device is consistent with the first configuration information corresponding to the proxy edge device sent by the cloud center before. If the two pieces of first configuration information are consistent, the cloud center may determine that the first configuration information sent by the target edge side device is legal, and establish communication connection with the target edge side device. If the two pieces of first configuration information are inconsistent, the cloud center may determine that the first configuration information sent by the target edge side device is illegal, and refuse to establish a communication connection with the target edge side device. Further, the cloud center may also send a connection success or connection failure notification message to the target edge device to notify the target edge device that the connection establishment is successful or failed.

After the target edge device successfully establishes communication connection with the cloud center, when there is another edge device newly deployed in the network area, the target edge device may serve as a proxy node of the newly deployed edge device, and apply for the newly deployed edge device for corresponding first configuration information from the cloud center.

In general, after the target edge device is deployed in the network, a certain service may be provided, for example, a face detection service is provided in cooperation with a third-party service platform, and therefore, after the target edge device establishes a communication connection with the cloud center, the operation and maintenance personnel also need to deploy the service provided by the target edge device for the target edge device.

Based on this, in a further possible implementation manner, the second configuration information required for configuring the service on the target edge device may be sent to the target edge device by another device, for example, this embodiment may further include:

s306: the cloud center may also send the second configuration information to the target edge-side device based on the communication connection established between the cloud center and the target edge-side device.

S307: and the target edge side equipment configures the business service corresponding to the target edge side equipment according to the received second configuration information.

The second configuration information may be information required for configuring the service on the target edge device, and may be, for example, a container mirror image of the service, resource occupation information of different services, and the like. The resource occupation information of the service may include, for example, any one or more of the memory that can be occupied by each service on the target edge device, the CPU occupancy of the target edge device allowed when processing the service, and the computing capability of the target edge device required for processing the service, and of course, may also include other information, which is not limited in this embodiment.

Since the target edge device and the cloud center have successfully established the connection, for the second configuration information required for configuring the service on the target edge device, the cloud center may send the second configuration information to the target edge device based on the established communication connection, so that the target edge device automatically deploys the service on the target edge device based on the received second configuration information.

Of course, in other possible embodiments, the cloud center may send the target edge device to the proxy edge device through the proxy edge device. Or, the second configuration information corresponding to the target edge device stored in the cloud center may be backed up to the proxy edge device in advance, so that the proxy edge device may send the second configuration information stored in the proxy edge device to the target edge device while sending the first configuration information to the target edge device. Further, when the second configuration information corresponding to the target edge side device is backed up on the proxy edge side device, the cloud center may periodically and synchronously update (or check and update) the second configuration information on the proxy edge side device, so as to improve the integrity and reliability of the second configuration information stored on the proxy edge side device and the timeliness of backup; moreover, after the agent edge side device stores the second configuration information, the cloud center does not need to store the second configuration information any more, so that the utilization rate of the storage space of the agent edge side device can be improved, part of storage resources of the cloud center can be released, and the storage pressure of the cloud center is reduced.

In some scenarios, the edge device after being powered on may store configuration information, for example, when the proxy edge device deployed in the network is restarted or is powered on again due to other non-failure reasons, the edge device may already store the first configuration information and/or the second configuration information, and after being powered on, the edge device may first check whether the edge device itself stores the first configuration information and/or the second configuration information, if so, the edge device may perform corresponding configuration based on the existing configuration information, and if not, the above-described process of this embodiment may be adopted to automatically obtain the corresponding configuration information and perform configuration. Further, if the edge device is powered on again and the first configuration information and/or the second configuration information is not found locally, it may further find whether to establish an agent relationship with other edge devices, if the agent relationship exists, the required configuration information may be obtained from the corresponding agent edge device based on the agent relationship, and if the agent relationship does not exist, one agent edge device may be selected from the other edge devices, and the required configuration information may be obtained from the selected agent edge device.

In this embodiment, after the agent edge device establishes an agent relationship with the target edge device, a hierarchical tree-type agent network may be formed, so that when the cloud center needs to issue information to each edge device in the network, the information may be distributed to each edge device of its agent by the corresponding agent edge device. Taking the example of upgrading the firmware of the edge side device, the cloud center may send the firmware of the new version to each agent edge side device, and then each agent edge side device sends the received firmware of the new version to its agent to obtain each edge side device. In general, the number of edge devices acting on the agent in the network may be much smaller than the number of edge devices being acted on (for example, there may be 2 edge devices acting on the agent in the network, and each edge device acting on the agent may act on 50 edge devices, etc.), so that the cloud center may only need to send the new version of firmware to the fewer edge devices acting on the agent, and does not need to send the new version of firmware to the remaining edge devices acting on the agent, and the remaining edge devices acting on the agent may be sent by the corresponding edge devices acting on the agent, thereby reducing resource consumption required by the cloud center in the process of upgrading the edge device firmware, and reducing the dependence of the edge devices on the cloud center; moreover, the plurality of agent edge side devices can send the new versions of firmware to the plurality of agent edge sides in parallel, which can effectively improve the efficiency of upgrading the firmware of the edge side devices in the whole network compared with the mode that the cloud center sends the new versions of firmware to the edge side devices one by one. Of course, in many scenarios such as software distribution, data synchronization, and the like, a process similar to the firmware upgrade may also be used for implementation, and this embodiment does not limit a specific application scenario in which the proxy edge device sends information issued by the cloud center to other edge devices.

When the proxy edge side device fails or cannot continue to provide proxy service for the subordinate edge side device for other reasons, any one or more of the following policies may be adopted for coping with the failure:

as an example, each subordinate edge device of the proxy edge device may resend the second request to request other edge devices to serve as proxy edge devices of the subordinate edge device, and establish corresponding proxy relationships.

In another example, each lower-level edge device of the proxy edge devices may elect a new proxy edge device in a contention manner, and the elected proxy edge device may establish a proxy relationship with its remaining-level edge devices, respectively, to become a proxy node of the remaining edge devices.

In yet another example, the proxy edge device may also be a support hot-standby mechanism, for example, each proxy edge device may have at least one slave device, and the proxy relationship on the proxy edge device and the first configuration information and/or the second configuration information corresponding to the subordinate edge device thereof may be synchronized into a backup edge device, which may of course be other edge devices in the same network area. When the proxy edge device fails, the backup edge device may take over the management of the proxy edge device and become a new proxy node of the lower-level edge device of the proxy edge device. Meanwhile, for the slave device serving as a new proxy node, a new backup edge device may be configured for the slave device, so that when the backup edge device serving as the new proxy node stops providing the proxy service, the configured new backup edge device continues to take over management.

It should be understood that the above examples are only used for illustration, and are not used to limit the policy for the proxy edge side device to stop providing the proxy service. In practical application, other coping strategies may be adopted.

In addition, an apparatus that can be applied to a proxy edge-side device is also provided in the embodiments of the present application, and the apparatus can implement the functions performed by the proxy edge-side device shown in fig. 3 or fig. 4. Referring to fig. 5, the apparatus 500 may include:

an obtaining module 501, configured to obtain first configuration information corresponding to a target edge device;

a transmission module 502, configured to send the first configuration information to the target edge-side device, where the first configuration information is used to configure the target edge-side device to establish a connection with a cloud center.

In a possible implementation manner, the transmission module 502 is further configured to send a first request to the cloud center, where the first request includes an identifier of the target edge-side device, and the first request is used to request the cloud center for first configuration information corresponding to the target edge-side device;

the obtaining module 501 is specifically configured to receive a response message from the cloud center, where the response message includes the first configuration information.

In a possible implementation manner, the obtaining module 501 is specifically configured to obtain an identifier of the target edge device, and determine, according to the identifier of the target edge device, first configuration information corresponding to the target edge device from first configuration information corresponding to at least one locally stored edge device.

In a possible implementation, the apparatus further includes an agent relationship establishing module 503;

the transmission module 502 is further configured to receive a second request from the target edge-side device, where the second request is used to request the proxy edge-side device to serve as a proxy node of the target edge-side device;

the agent relationship establishing module 503 is configured to establish an agent relationship between the agent edge side device and the target edge side device according to the second request.

In a possible implementation, the apparatus 500 further includes:

a determining module 504, configured to determine that the proxy state of the proxy edge side device satisfies a preset condition, where the proxy state includes a proxy number of the proxy edge side device and/or a number of edge side devices that have established a proxy relationship with the proxy edge side device.

In a possible implementation manner, the transmission module 502 is further configured to send second configuration information corresponding to the target edge device, where the second configuration information is used to configure a service corresponding to the target edge device.

In a possible implementation, the apparatus 500 further includes:

a synchronization module 505, configured to synchronize the first configuration information and/or the second configuration information to a backup edge side device, where the backup edge side device is configured to serve as a proxy node of the target edge side device when the proxy edge side device fails.

In a possible implementation manner, the transmission module 502 is further configured to receive an object program from the cloud center, and send the object program to a target edge side device, where the target edge side device and the proxy edge side device are located in the same network area.

In addition, another apparatus structure applied to the proxy edge-side device is provided in the embodiments of the present application, as shown in fig. 6, the proxy edge-side device 600 may include a communication interface 610 and a processor 620. Optionally, the proxy edge side device 600 may further include a memory 630. The memory 630 may be disposed inside the proxy edge device, or may be disposed outside the proxy edge device. The actions performed by each proxy edge device in fig. 3-4 may be implemented by the processor 620, for example. The processor 620 receives requests, sends media streams and responses through the communication interface 610 and is configured to implement any of the methods performed by the proxy edge side device described in fig. 3-4. In implementation, the steps of the processing flow may implement the method executed by the proxy edge side device in fig. 3 to 4 through instructions in the form of hardware integrated logic circuit or software in the processor 620. For brevity, no further description is provided herein. Program code executed by processor 620 to implement the above-described methods may be stored in memory 630. The memory 630 is coupled to the processor 620, such as coupled to the processor.

Some of the features of the embodiments of the present application may be performed/supported by processor 620 executing program instructions or software code in memory 630. The software components loaded on the memory 630 may be summarized functionally or logically, for example, the obtaining module 501, the transmitting module 502, the proxy relationship establishing module 503, the determining module 504, and the synchronizing module 505 shown in fig. 5.

Any of the communication interfaces involved in the embodiments of the present application may be a circuit, a bus, a transceiver, or any other device that can be used for information interaction. Such as the communication interface 610 in the proxy edge side device 600, and the other apparatuses may be devices connected to the proxy edge side device 600, such as a cloud center and/or an edge side device.

The same inventive concept as the above method, the embodiment of the present application further provides an apparatus that can be applied to an edge side device, and the apparatus can implement the functions of the edge side device in the embodiments shown in fig. 3 to fig. 4. Referring to fig. 7, the apparatus 700 includes:

a transmission module 701, configured to receive first configuration information corresponding to a device on an agent edge side;

a connection establishing module 702, configured to establish a connection with the cloud center according to the first configuration information.

In a possible implementation manner, the transmission module 701 is further configured to send a second request to the proxy edge side device, where the second request is used to request the proxy edge side device to serve as a proxy node of the target edge side device.

In a possible embodiment, the apparatus 700 further comprises a configuration module 703;

the transmission module 701 is further configured to receive second configuration information corresponding to the target edge-side device from the proxy edge-side device or from the cloud center;

the configuration module 703 is configured to configure, according to the second configuration information, a service corresponding to the target edge device.

In a possible implementation manner, the transmission module 701 is configured to receive an object program from the proxy edge-side device, where the object edge-side device and the proxy edge-side device are located in the same network area.

In addition, another apparatus structure applied to an edge-side device is provided in an embodiment of the present application, as shown in fig. 8, the edge-side device 800 may include a communication interface 810 and a processor 820. Optionally, the edge device 800 may further include a memory 830. The memory 830 may be disposed inside the edge device, or may be disposed outside the edge device. The actions performed by each of the edge devices in fig. 3-4 may be implemented by the processor 820. The processor 820 receives requests, sends media streams and responses through the communication interface 810 and is configured to implement any of the methods performed by the edge side devices described in fig. 3-4. In implementation, the steps of the processing flow may implement the method performed by the edge side device in fig. 3 to 4 through instructions in the form of hardware integrated logic circuit or software in the processor 820. For brevity, no further description is provided herein. Program code executed by processor 820 to implement the above-described methods may be stored in memory 830. The memory 830 is coupled to the processor 820, such as coupled to the processor. Some of the features of the embodiments of the present application may be performed/supported by the processor 820 executing program instructions or software code in the memory 830. The software components loaded on the memory 830 may be summarized functionally or logically, for example, the transmission module 701, the connection establishment module 702, and the configuration module 703 shown in fig. 7.

Any of the communication interfaces involved in the embodiments of the present application may be a circuit, a bus, a transceiver, or any other device that can be used for information interaction. Such as the communication interface 810 in the edge side device 800, for example, the other apparatus may be a device connected to the edge side device 800, such as a cloud center and/or a proxy edge side device.

The same inventive concept as the method described above, the embodiment of the present application further provides an apparatus that can be applied to a cloud center, and the apparatus can implement the functions of the cloud center in the embodiments shown in fig. 3 to fig. 4 described above. Referring to fig. 9, apparatus 900 comprises:

a determining module 901, configured to determine first configuration information corresponding to a target edge-side device;

a transmission module 902, configured to send the first configuration information to a proxy edge-side device, where the first configuration information is used to configure the target edge-side device to establish a connection with the cloud center;

a checking module 903, configured to check that the first configuration information from the target edge side device is consistent with the first configuration information sent by the cloud center to the proxy edge side device;

a connection establishing module 904, configured to establish a connection with the target edge-side device.

In a possible implementation manner, the transmitting module 902 is further configured to receive a first request from the proxy edge-side device, where the first request includes an identifier of the target edge-side device;

the determining module 901 is specifically configured to determine, according to the identifier of the target edge-side device, first configuration information corresponding to the target edge-side device.

In a possible implementation manner, the transmission module 902 is further configured to send an object program to the proxy edge-side device, where the object edge-side device and the proxy edge-side device are located in the same network area.

In a possible implementation manner, the transmission module 902 is further configured to send, to the target edge device, second configuration information corresponding to the target edge device based on the connection established between the cloud center and the target edge device, where the second configuration information is used to configure a service corresponding to the target edge device.

In addition, another device structure applied to a cloud center is provided in the embodiments of the present application, as shown in fig. 10, the cloud center 1000 may include a communication interface 1010 and a processor 1020. Optionally, the cloud center 1000 may further include a memory 1030. The memory 1030 may be disposed inside the cloud center, or may be disposed outside the cloud center. The actions performed by the cloud centers of fig. 3-4 may be implemented by processor 1020. The processor 1020 receives requests, sends media streams, and responses through the communication interface 1010 and is configured to implement any of the methods performed by the cloud center described in fig. 3-4. In implementation, the steps of the processing flow may implement the method performed by the edge side device in fig. 3 to 4 through instructions in the form of hardware integrated logic circuit or software in the processor 1020. For brevity, no further description is provided herein. Program code executed by processor 1020 to implement the above-described methods may be stored in memory 1030. The memory 1030 is coupled to the processor 1020, such as coupled to the processor. Some of the features of the embodiments of the present application may be performed/supported by processor 1020 executing program instructions or software code in memory 1030. The software components loaded on the memory 1030 may be generalized functionally or logically, such as the determination module 901, the transmission module 902, the verification module 903, and the connection establishment module 904 shown in fig. 9.

Any of the communication interfaces involved in the embodiments of the present application may be a circuit, a bus, a transceiver, or any other device that can be used for information interaction. Such as the communication interface 1010 in the cloud center 1000, and the other apparatuses may be devices connected to the cloud center 1000, such as edge side devices and/or proxy edge side devices.

The processors referred to in the embodiments of the present application may be general purpose processors, digital signal processors, application specific integrated circuits, field programmable gate arrays or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like that implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present application. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a processor.

The coupling in the embodiments of the present application is an indirect coupling or a communication connection between devices, modules or modules, and may be an electrical, mechanical or other form for information interaction between the devices, modules or modules.

The processor may cooperate with the memory. The Memory may be a nonvolatile Memory, such as a Hard Disk Drive (HDD) or a Solid-State Drive (SSD), and may also be a Volatile Memory (RAM), for example, a Random-Access Memory (RAM). The memory is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such.

The embodiment of the present application does not limit the specific connection medium among the communication interface, the processor, and the memory. Such as memory, processor, and communication interfaces may be connected by a bus. The bus may be divided into an address bus, a data bus, a control bus, etc.

Based on the foregoing embodiments, the present application further provides a computer storage medium, where a software program is stored, and when the software program is read and executed by one or more processors, the software program may implement the method provided by any one or more of the above embodiments for acting on an edge-side device or a cloud center. The computer storage medium may include: u disk, removable hard disk, read only memory, random access memory, magnetic or optical disk, etc. for storing program codes.

Based on the foregoing embodiments, an embodiment of the present application further provides a chip, where the chip includes a processor, configured to implement the function of the proxy edge-side device or the function of the cloud center according to the foregoing embodiments, for example, to implement the method executed by the proxy edge-side device in fig. 3 to 4, to implement the method executed by the edge-side device in fig. 3 to 4, or to implement the method executed by the cloud center in fig. 3 to 4. Optionally, the chip further comprises a memory for the processor to execute the necessary program instructions and data. The chip may be constituted by a chip, or may include a chip and other discrete devices.

The terms "first," "second," and the like in the description and in the claims of the present application and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances and are merely descriptive of the various embodiments of the application and how objects of the same nature can be distinguished.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application 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 application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. 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 data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, 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 data processing apparatus 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 data processing apparatus 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.

It will be apparent to those skilled in the art that various changes and modifications may be made in the embodiments of the present application without departing from the scope of the embodiments of the present application. Thus, if such modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to encompass such modifications and variations.

Claims

1. A method for configuring an edge side device, the method being applied to a proxy edge side device, the method comprising:

acquiring first configuration information corresponding to target edge side equipment;

and sending the first configuration information to the target edge side equipment, wherein the first configuration information is used for configuring the target edge side equipment to establish connection with a cloud center.

2. The method of claim 1, further comprising:

sending a first request to the cloud center, where the first request includes an identifier of the target edge-side device, and the first request is used to request the cloud center for first configuration information corresponding to the target edge-side device;

the acquiring of the first configuration information corresponding to the target edge side device includes:

receiving a response message from the cloud center, wherein the response message comprises the first configuration information.

3. The method according to claim 1, wherein the obtaining first configuration information corresponding to the target edge-side device includes:

acquiring an identifier of the target edge side device;

and determining first configuration information corresponding to the target edge side device from locally stored first configuration information corresponding to at least one edge side device according to the identifier of the target edge side device.

4. The method according to any one of claims 1 to 3, wherein before sending the first configuration information to the target edge-side device, the method further comprises:

receiving a second request from the target edge side device, where the second request is used to request the proxy edge side device to serve as a proxy node of the target edge side device;

and establishing an agent relationship between the agent edge side equipment and the target edge side equipment according to the second request.

5. The method of claim 4, wherein before establishing the proxy relationship between the proxy edge-side device and the target edge-side device according to the second request, the method further comprises:

determining that the agent state of the agent edge side device meets a preset condition, wherein the agent state comprises the agent grade number of the agent edge side device or the number of the edge side devices establishing an agent relationship with the agent edge side device.

6. The method according to any one of claims 1 to 5, further comprising:

and sending second configuration information corresponding to the target edge side device, where the second configuration information is used to configure a service corresponding to the target edge side device.

7. The method of claim 6, further comprising:

synchronizing the first configuration information or the second configuration information to a backup edge side device, where the backup edge side device is used as a proxy node of the target edge side device when the proxy edge side device fails.

8. The method according to claim 4 or 5, wherein after establishing the proxy relationship between the proxy edge side device and the target edge side device, the method further comprises:

receiving a target program from the cloud center;

and sending the target program to the target edge side equipment, wherein the target edge side equipment and the proxy edge side equipment are positioned in the same network area.

9. A method for configuring an edge side device, the method being applied to a target edge side device, the method comprising:

receiving first configuration information corresponding to the proxy edge side equipment;

and establishing connection with the cloud center according to the first configuration information.

10. The method of claim 9, further comprising:

and sending a second request to the proxy edge side device, where the second request is used to request the proxy edge side device to serve as a proxy node of the target edge side device, and the target edge side device and the proxy edge side device are located in the same network area.

11. The method according to claim 9 or 10, characterized in that the method further comprises:

receiving second configuration information corresponding to the target edge side device from the proxy edge side device;

and configuring the business service corresponding to the target edge side equipment according to the second configuration information.

12. A method for configuring edge side equipment, wherein the method is applied to a cloud center, and the method comprises the following steps:

determining first configuration information corresponding to target edge side equipment;

sending the first configuration information to proxy edge side equipment, wherein the first configuration information is used for configuring the target edge side equipment to establish connection with the cloud center;

checking first configuration information from the target edge side equipment;

and establishing connection with the target edge side equipment.

13. An apparatus for configuring an edge side device, the apparatus being applied to a proxy edge side device, the apparatus comprising:

the acquisition module is used for acquiring first configuration information corresponding to the target edge side equipment;

and the transmission module is used for sending the first configuration information to the target edge side equipment, wherein the first configuration information is used for configuring the target edge side equipment to establish connection with a cloud center.

14. The apparatus according to claim 13, wherein the transmission module is further configured to send a first request to the cloud center, where the first request includes an identifier of the target edge-side device, and the first request is used to request, from the cloud center, first configuration information corresponding to the target edge-side device;

the obtaining module is specifically configured to receive a response message from the cloud center, where the response message includes the first configuration information.

15. The apparatus of claim 13, wherein the obtaining module is configured to obtain an identifier of the target edge device, and determine, according to the identifier of the target edge device, first configuration information corresponding to the target edge device from first configuration information corresponding to at least one locally stored edge device.

16. The apparatus according to any one of claims 13 to 15, wherein the apparatus further comprises a proxy relationship establishing module;

the transmission module is further configured to receive a second request from the target edge device, where the second request is used to request the proxy edge device to serve as a proxy node of the target edge device;

and the proxy relationship establishing module is configured to establish a proxy relationship between the proxy edge side device and the target edge side device according to the second request.

17. The apparatus of claim 16, further comprising:

a determining module, configured to determine that an agent status of the agent edge side device meets a preset condition, where the agent status includes an agent level number of the agent edge side device and/or a number of edge side devices that have established an agent relationship with the agent edge side device.

18. The apparatus according to any one of claims 13 to 17, wherein the transmission module is further configured to send second configuration information corresponding to the target edge device, where the second configuration information is used to configure a service corresponding to the target edge device.

19. The apparatus of claim 18, further comprising:

a synchronization module, configured to synchronize the first configuration information and/or the second configuration information to a backup edge side device, where the backup edge side device is configured to serve as a proxy node of the target edge side device when the proxy edge side device fails.

20. An apparatus for configuring an edge side device, the apparatus being applied to a target edge side device, the apparatus comprising:

the transmission module is used for receiving first configuration information corresponding to the agent edge side equipment;

and the connection establishing module is used for establishing connection with the cloud center according to the first configuration information.

21. An apparatus for configuring an edge-side device, the apparatus being applied to a cloud center, the apparatus comprising:

the determining module is used for determining first configuration information corresponding to the target edge side equipment;

a transmission module, configured to send the first configuration information to a proxy edge-side device, where the first configuration information is used to configure the target edge-side device to establish a connection with the cloud center;

the verification module is used for verifying first configuration information from the target edge side equipment;

and the connection establishing module is used for establishing connection with the target edge side equipment.

22. A computing device, the device comprising a memory and a processor, the memory to store software instructions; the processor invokes the memory-stored software instructions to perform the method of any of claims 1 to 8.

23. A computing device, the device comprising a memory and a processor, the memory to store software instructions; the processor invokes the memory-stored software instructions to perform the method of any of the preceding claims 9 to 11.

24. A system for configuring edge side equipment is characterized in that the system comprises proxy edge side equipment, target edge side equipment and a cloud center;

the proxy edge side device is used for sending first configuration information corresponding to the target edge side device;

the target edge side device is used for sending the first configuration information to the cloud center;

the cloud center is configured to: checking first configuration information from the target edge side equipment;

and establishing connection with the target edge side equipment.