WO2021254466A1

WO2021254466A1 - Method, apparatus and system for configuring edge side device

Info

Publication number: WO2021254466A1
Application number: PCT/CN2021/100780
Authority: WO
Inventors: 蔡志方
Original assignee: 华为技术有限公司
Priority date: 2020-06-18
Filing date: 2021-06-18
Publication date: 2021-12-23
Also published as: CN113821334A

Abstract

Disclosed are a method, apparatus and system for configuring an edge side device. The present application is used for solving the problem of improving the low configuration efficiency of the edge side device. A proxy edge side device can obtain first configuration information corresponding to a target edge side device, and sends the first configuration information to the target edge side device, and the first configuration information can be used for configuring connection establishment between the target edge side device and a cloud center. Because in the process of establishing the connection between the target edge side device and the cloud center, the proxy edge side device sends the first configuration information required for establishing the connection to the cloud center to the target edge side device, no operation and maintenance personnel need to manually configure the target edge side device item by item, thereby effectively improving the configuration efficiency of the target edge side device.

Description

Method, device and system for configuring edge side equipment

This application claims the priority of a Chinese patent application filed with the China Intellectual Property Office on June 18, 2020, the application number is 202010560994.8, and the application name is "A method and device for configuring edge-side equipment", and it is claimed on June 18, 2020. The priority of a Chinese patent application filed with the China Intellectual Property Office with application number 202010599733.7 and application name "A method, device and system for configuring edge-side equipment" on 28th, the entire content of which is incorporated into this application by reference.

Technical field

The embodiments of the present application relate to the field of edge computing technology, and in particular, to a method, device, and system for configuring edge-side devices.

Background technique

Although the cloud center has powerful data processing capabilities, it can calculate and feed back the massive data sent by edge-side devices. However, as users have higher and higher requirements for cloudification, the real-time and transmission of data processed by the cloud center Data bandwidth, etc. gradually become difficult to meet user requirements.

The emergence of edge computing can transfer the computing work of the cloud center to edge devices, which can effectively make up for the deficiencies of the cloud center. The cloud center can take the resources of the edge-side device as an extension of the cloud center resources, and use the resources of the edge-side device to provide users with corresponding data processing services, which can be called “end-side collaboration” or “side-cloud collaboration”.

At present, when deploying edge-side devices, it is mainly the operation and maintenance personnel who manually configure the edge-side devices that need to be deployed item by item, such as configuring the authentication information required for registering to the cloud center on the edge-side devices. Generally, the operation of configuring edge-side devices is complicated and error-prone, which makes the configuration efficiency of edge-side devices generally low.

Summary of the invention

The embodiments of the present application provide a method, device, and system for configuring edge-side devices, so as to solve the problem of improving the low configuration efficiency of edge-side devices.

In the first aspect, an embodiment of the present application provides a method for configuring an edge-side device. The method can be applied to a proxy edge-side device. The method includes: the proxy edge-side device obtains first configuration information corresponding to the target edge-side device, and sends The target edge-side device sends first configuration information, and the first configuration information may be used to configure the target edge-side device to establish a connection with the cloud center. Because in the process of establishing a connection between the target edge device and the cloud center, the proxy node sends the first configuration information required to establish a connection with the cloud center to the target edge device, so that the target edge device can be based on the received The first configuration information establishes a connection with the cloud center, eliminating the need for operation and maintenance personnel to manually configure the target edge-side devices to be deployed item by item, thereby improving the configuration efficiency of the target edge-side devices.

In a possible implementation manner, the method may further include: proxying the edge-side device to send a first request to the cloud center. The first request may include an identifier of the target edge-side device, and the identifier may be, for example, the target edge-side device. In order to use the first request to request the cloud center for the first configuration information corresponding to the target edge-side device; then, the proxy edge-side device can obtain the first configuration information corresponding to the target edge-side device, for example, The process may specifically include 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 to the cloud center for the first configuration information for the target edge device, so that the target edge device can The first configuration information is obtained from the agent edge side device, and a communication connection is established with the cloud center based on this.

In a possible implementation manner, the process in which the proxy edge-side device obtains the first configuration information corresponding to the target edge-side device may specifically be that the proxy edge-side device first obtains the identification of the target edge-side device, and then according to the target edge-side device The first configuration information corresponding to the target edge-side device is determined from the first configuration information corresponding to at least one edge-side device stored locally. In this embodiment, the proxy edge-side device may store the first configuration information required by the target edge-side device, so that the target edge-side device can directly obtain the first configuration information from the proxy edge-side device. In this way, the cloud center There is no need to consume a certain amount of storage space to store the first configuration information, so that the storage space of this part of the cloud center can be released, and the resources on the agent edge side device can be effectively used.

In a possible implementation manner, the method may further include: before sending the first configuration information to the target edge device, the proxy edge device may receive a second request from the target edge device. The second request can be used to request the proxy edge device to act as the proxy node of the target edge device; then, the proxy edge device can establish a proxy relationship with the target edge device according to the second request, which can specifically be directed to the target edge device first. The edge-side device sends a response message for the second request. The response message can be used to indicate that the proxy edge-side device can act as a proxy node of the target edge-side device. Then, the proxy edge-side device can receive the proxy from the target edge-side device. Confirm the message, so as to establish the agent relationship between the agent edge-side device and the target edge-side device according to the agent confirmation message. In this embodiment, the target edge-side device can apply for a proxy node (that is, a proxy edge-side device) in the network through multicast or broadcast, so as to obtain its connection with the cloud center for the target edge-side device based on the proxy node The first configuration information required.

In a possible implementation manner, before the proxy edge device establishes the agency relationship between the proxy edge device and the target edge device according to the second request, the method may further include: proxy edge device It is determined that the agent state of the agent edge-side device satisfies a preset condition. The agent state includes the agent level of the agent edge-side device and/or the number of edge-side devices that have established an agent relationship with the agent edge-side device. Accordingly, the preset For example, the condition may be that the number of agent levels on the agent edge side does not exceed the preset level, and/or the number of edge side devices that establish an agent relationship with the agent edge side device does not exceed the preset number, etc. By monitoring its own agent status, the agent edge device can avoid taking on too many agent tasks as much as possible, causing the load imbalance of the agent edge device in the network. For example, when a proxy edge device has more lower-level edge-side devices than the preset number, you can no longer add new lower-level edge-side devices for the proxy edge-side device, and you can select other edge-side devices in the network to become the proxy edge Side equipment, which can improve the network utilization between nodes.

Further, when the agent edge device becomes the agent node of the target edge device and establishes an agent relationship with the target edge device, the agent edge device can update its own agent status, for example, it can be the subordinate edge side of the agent. The number of equipment has been updated from 45 to 46 and so on.

In a possible implementation manner, the method may further include: the proxy edge-side device sends second configuration information corresponding to the target edge-side device to the target edge-side device, and the second configuration information may be used to configure the target edge-side device to correspond to Business services. The second configuration information may be, for example, the container image of the business service, the resource occupation information of different business services, etc. The resource occupation information of the business service may include, for example, the memory that each business service can occupy on the target edge device, and the processing of the The CPU occupancy rate of the target edge device allowed during the service, and the computing power of the target edge device required to process the service, etc. In this way, the automatic configuration of the business services corresponding to the target edge-side device can be realized, so that there is no need for operation and maintenance personnel to manually deploy the corresponding business services for the target edge-side device.

In a possible implementation manner, 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, it can The backup edge side device takes over the proxy edge side device to continue management, and becomes a new proxy node of the lower edge side device of the proxy edge side device.

In a possible implementation manner, after the agency relationship between the proxy edge-side device and the target edge-side device is established, the method may further include: the proxy edge-side device receives the target program from the cloud center, and Send the target program to the target edge-side device, and the target edge-side device and the proxy edge-side device are located in the same network area. In this embodiment, the agent edge device can form a hierarchical tree-type agent network after establishing an agent relationship with the target edge device. In this way, when the cloud center needs to deliver the target program to each edge device in the network, This information can be distributed to the respective edge-side devices of its agent through the corresponding agent edge-side device, which allows the cloud center to only send the target program to a small number of agent edge-side devices, and does not need to send the information to the other agent edge devices. The edge-side device sends the target program, and the other edge-side devices that are proxied can obtain the target program from the corresponding proxy edge-side device, thereby reducing the resource consumption required by the cloud center and reducing the edge-side device's dependence on the cloud center; moreover, Multiple proxy edge devices can send target programs to multiple proxy edge devices in parallel. Compared with the way that the cloud center sends target programs to edge devices one by one, the edge devices in the entire network obtain the target program. The efficiency can also 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 the second aspect, an embodiment of the present application also provides a method for configuring an edge-side device. The method can be applied to a target edge-side device. The method includes: the target edge-side device receives first configuration information corresponding to the proxy edge-side device , And establish a connection with the cloud center according to the first configuration information. Because in the process of establishing a connection between the target edge device and the cloud center, the proxy node sends the first configuration information required to establish a connection with the cloud center to the target edge device, so that the target edge device can be based on the received The first configuration information automatically establishes a connection with the cloud center, eliminating the need for operation and maintenance personnel to manually configure the target edge-side devices to be deployed item by item, thereby improving the configuration efficiency of the target edge-side devices.

In a possible implementation manner, the method further includes: the target edge-side device may send a second request to the proxy edge-side device, and the second request may be used to request the proxy edge-side device to act as a proxy node of the target edge-side device, 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 confirmation message to the proxy edge side device, where the proxy confirmation message is used to notify the proxy edge side device to establish a proxy relationship. In this embodiment, the target edge-side device can apply for a proxy node (that is, a proxy edge-side device) in the network through multicast or broadcast, so as to obtain its connection with the cloud center for the target edge-side device based on the proxy node The first configuration information required.

In a possible implementation manner, the method may further include: the target edge-side device may receive second configuration information corresponding to the target edge-side device from the proxy edge-side device or from the cloud center, and according to the second configuration information, Configure the business service corresponding to the target edge device. Exemplarily, the second configuration information may be, for example, a container image of a business service, resource occupation information of different business services, etc., where the resource occupation information of a business service may include, for example, the availability of each business service on the target edge device. The memory occupied, the CPU occupancy rate of the target edge device allowed when processing the service, and the computing power of the target edge device required to process the service, etc. The target edge device can automatically configure the business service corresponding to the target edge device according to the acquired second configuration information, thereby eliminating the need for operation and maintenance personnel to manually deploy the corresponding business service for the target edge device.

In a possible implementation manner, the method further includes: receiving a target program from a proxy edge-side device, where the target edge-side device and the proxy edge-side device are located in the same network area. In this embodiment, the cloud center can distribute the information to each edge device of its agent through the corresponding agent edge device, which makes the cloud center only need to send the target program to a small number of agent edge devices , Without sending the target program to the remaining proxied edge-side devices, the remaining proxied edge-side devices can obtain the target program from the corresponding proxy edge-side devices, thereby reducing the resource consumption required by the cloud center and reducing the edge-side devices Reliance on the cloud center; moreover, multiple agent edge devices can send target programs to multiple agent edge sides in parallel, which is compared to the way that the cloud center sends target programs to edge devices one by one, the entire network The efficiency of obtaining the target program by the edge-side device in the device can also be effectively improved.

In the third aspect, the embodiments of the present application also provide a method for configuring an edge-side device. The method can be applied to a cloud center. The method includes: the cloud center determines the first configuration information corresponding to the target edge-side device, and reports to the agent edge The side device sends the first configuration information, which can be used to configure the target edge device to establish a connection with the cloud center; then, the cloud center can verify the first configuration information from the target edge device and the cloud center to the agent Whether the first configuration information sent by the edge-side device is consistent, and if the verification is consistent, establish a connection with the target edge-side device. Because in the process of establishing a connection between the target edge side device and the cloud center, the cloud center issues the first configuration information to the proxy edge side device, and the proxy edge side device forwards the first configuration information to the target edge side device , So that the target edge-side device can automatically establish a connection with the cloud center based on the first configuration information received, without the need for operation and maintenance personnel to manually configure the target edge-side device that needs to be deployed, thereby improving the configuration of the target edge-side device efficient.

In a possible implementation manner, the method further includes: the cloud center receives a first request from the proxy edge-side device, the first request includes the identifier of the target edge-side device, and then, the cloud center may perform according to the target edge-side device To determine the first configuration information corresponding to the target edge-side device. In this embodiment, the first configuration information required for the target edge-side device to establish a communication connection with the cloud center may be located in the cloud center, and the proxy edge-side device may apply to the cloud center for the first configuration information for the target edge-side device to The target edge-side device can obtain the first configuration information from the proxy edge-side device, and establish a communication connection with the cloud center accordingly.

In a possible implementation manner, the method further includes: sending the target program to the agent edge-side device, where the target edge-side device and the agent edge-side device are located in the same network area. In this embodiment, the cloud center can distribute the information to each edge device of its agent through the corresponding agent edge device, which makes the cloud center only need to send the target program to a small number of agent edge devices , Without sending the target program to the remaining proxied edge-side devices, the remaining proxied edge-side devices can obtain the target program from the corresponding proxy edge-side devices, thereby reducing the resource consumption required by the cloud center and reducing the edge-side devices Reliance on the cloud center; moreover, multiple agent edge devices can send target programs to multiple agent edge sides in parallel, which is compared to the way that the cloud center sends target programs to edge devices one by one, the entire network The efficiency of obtaining the target program by the edge-side device in the device can also be effectively improved.

In a possible implementation manner, the method may further include: the cloud center sends second configuration information corresponding to the target edge device to the target edge device based on the established connection between the cloud center and the target edge device. The second configuration information is used to configure the business service corresponding to the target edge side device. In this embodiment, after the target edge device establishes a connection with the cloud center based on the first configuration information, the cloud center can directly issue the second configuration information to the target edge device based on the connection, so as to realize the uplink to the target edge device. Business services are automatically configured, eliminating the need for operation and maintenance personnel to manually configure, which improves the configuration efficiency of business services and reduces the operations of operation and maintenance personnel.

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

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

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

In a seventh aspect, an embodiment of the present application provides a device, including: a processor and a memory; the memory is used to store instructions, and when the device is running, the processor executes the instructions stored in the memory, so that the device executes the foregoing The method for configuring an edge-side device in the first aspect or any implementation method of the first aspect. It should be noted that the memory may be integrated in the processor or independent of the processor. The device may also include a bus. Among them, the processor is connected to the memory via a bus. Among them, the memory may include a readable memory and a random access memory.

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

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

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

In an eleventh aspect, an embodiment of the present application also provides a readable storage medium in which a program or instruction is stored. When the program or instruction is stored in the readable storage medium, when it runs on a computer, any of the above-mentioned aspects can be configured with edge-side devices. The method is executed.

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

In addition, the technical effects brought about by any one of the implementation manners of the fourth aspect to the twelfth aspect can be referred to the technical effects brought about by the different implementation manners of the first aspect to the third aspect, which will not be repeated here.

Description of the drawings

In order to more clearly describe the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings needed in the description of the embodiments. Obviously, the drawings in the following description are only some of the implementations recorded in the present application. For example, for those of ordinary skill in the art, other drawings can be obtained based on these drawings.

Figure 1 is a schematic diagram of various networking architectures;

Figure 2 is a schematic diagram of a network architecture including a public network;

Figure 3 is a schematic diagram of signaling interaction for configuring an edge-side device in an embodiment of this application;

FIG. 4 is a schematic diagram of signaling interaction for proxy edge-side devices to obtain first configuration information in an embodiment of this application;

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

FIG. 6 is a schematic structural diagram of a proxy edge-side device in an embodiment of this application;

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

FIG. 8 is a schematic structural diagram of an edge-side device in an embodiment of this application;

FIG. 9 is a schematic structural diagram of a device applied to a cloud center in an embodiment of the application;

FIG. 10 is a schematic structural diagram of a cloud center in an embodiment of this application.

detailed description

The embodiments of the present application can be applied to a network system including cloud center and edge-side devices. Among them, the cloud center can be deployed in the cloud and is responsible for managing edge-side devices. The cloud center can also be called a management platform located in the cloud. Edge-side devices can be deployed outside the cloud. In a possible implementation manner, the network system may also 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 public network networking, private network networking, and local networking based on differences in networking, as shown in Figure 1. At present, the operation and maintenance of edge-side devices relies on the cloud center, and specifically can rely on the central management node on the cloud center. The operation and maintenance personnel need to manually configure the configuration information required for the edge-side device to connect to the cloud center on the edge-side device, so that the edge-side device can establish a connection with the cloud center based on the information configured by the operation and maintenance personnel. The connection between the gateway and/or switch and the cloud center. However, the configuration operations that operation and maintenance personnel need to perform on edge-side devices are usually more complicated, not only time-consuming, but also prone to configuration errors. Operation and maintenance personnel may need to reconfigure edge-side devices manually, which leads to edge-side devices The configuration efficiency is usually low. When edge-side devices are deployed on a large scale in the network, this method of manually configuring one by one by the operation and maintenance personnel seriously reduces the deployment efficiency of the edge-side devices; and when replacing the edge-side devices that have failed in the network In the scenario, due to the low efficiency of manually configuring the newly replaced edge-side device, this makes the edge-side device unable to provide business services for a long time, and thus the edge node where the edge-side device is located cannot resume business for a long time.

Based on this, the embodiment of the present application provides a method for configuring an edge-side device to improve the configuration efficiency of the edge-side device. Specifically, the edge-side devices in the network can be divided into at least two types. One is the edge-side device that has been deployed in the network and is connected to the cloud center. It can be used as a proxy edge-side device, as shown in Figure 2. Edge-side devices A to Y, etc., and the other is a subordinate device that acts as an edge-side device as these proxy edge-side devices. When the target edge device X to be configured exists in the network area where the proxy edge device is located, one of the proxy edge devices, such as the proxy edge device Y, can become the proxy node of the target edge device X and obtain the The target edge-side device X establishes the first configuration information required for establishing a connection with the cloud center, and then sends the first configuration information to the target edge-side device X. In this way, the target edge device X can establish a connection with the cloud center according to the received first configuration information. Since in the process of establishing a connection between the target edge-side device X and the cloud center, the agent edge-side device Y sends the first configuration information required to establish a connection with the cloud center to the target edge-side device X, and there is no need for operation and maintenance personnel to check the target. The edge-side device X is manually configured item by item, which can effectively improve the configuration efficiency of the target edge-side device X. Furthermore, after the target edge-side device X is connected to the cloud center, it can also be used as other newly deployed edge-side devices Proxy edge-side equipment. At the same time, the process of establishing a communication connection between the target edge device X and the cloud center does not need to rely on the Simple Service Discovery Protocol (SSDP), so that there is a connection between the target edge device X and the cloud center as shown in Figure 2. In the case of a public network, there is no need to require the public network to support the network address translation (NAT) function, thereby reducing the requirements for the public network and improving the universality and feasibility of the implementation of the solution.

In the scenario of large-scale deployment of edge-side devices, the automatic configuration of newly deployed target edge-side devices by proxying the edge-side devices can effectively improve the deployment efficiency of edge-side devices and accelerate the progress of network delivery; and failures occur in the replacement network In the scenario of the edge-side device of, because the efficiency of automatically configuring the newly replaced target edge-side device is high, the edge node where the target edge-side device is located can resume business in a short time and continue to provide corresponding business services.

In order to make the above objectives, features, and advantages of the present application more obvious and understandable, various non-limiting implementations in the embodiments of the present application will be exemplified below in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of this application.

As shown in FIG. 3, this is a schematic diagram of signaling interaction of a method for configuring an edge-side device in an embodiment of this application. The method may specifically include:

S301: The proxy edge-side device acquires first configuration information corresponding to the target edge-side device.

In this embodiment, the edge-side device that has been deployed in the network and has a communication connection with the cloud center can be used as the proxy edge-side device, and the proxy edge-side device can be used as the edge-side device to be configured (hereinafter referred to as the target edge Side device), and assist the target edge side device to establish a connection with the cloud center.

Generally, when the target edge device is deployed, if the target edge device is not configured accordingly, it is usually difficult to directly establish a communication connection with the cloud center. Therefore, the proxy edge-side device can obtain the configuration information (hereinafter referred to as the first configuration information) required for the target edge-side device to establish a communication connection with the cloud center. Wherein, when the proxy edge device obtains the first configuration information, it can be obtained by requesting the cloud center, or it can obtain the first configuration information corresponding to the target edge device from a plurality of first configuration information stored locally. .

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

Exemplarily, as shown in FIG. 4, the proxy edge-side device may obtain the identifier of the target edge-side device, such as the serial number of the target edge-side device, and generate a first request based on the identifier; then, the proxy edge-side device may Based on the established communication connection with the cloud center, the first request is sent to the cloud center to request the cloud center to feed back the first configuration information corresponding to the target edge side device. The cloud center may parse out the identifier of the target edge-side device from the received first request, and find out the first configuration information corresponding to the target edge-side device from a plurality of locally pre-stored first configuration information 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 side device, and 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.

Generally, there may be more than one edge-side device that has been deployed in the network and established a communication connection with the cloud center. Therefore, when the target edge-side device is connected to the network, you can select one of the multiple edge-side devices that have been deployed The edge-side device serves as the proxy node of the target edge-side device. Exemplarily, as shown in FIG. 4, the target edge-side device may broadcast or multicast a second request in the network area (such as a local area network, etc.) where it is located, and the second request is used to request that the second request is received The edge-side device serves as the proxy node of the target edge-side device. After multiple edge-side devices (including proxy edge-side devices) receive the second request, they can send a response message for the second request to the target edge-side device, and the response message can be used to indicate that its own device can serve as the target. The proxy node of the edge device. After the target edge device receives response messages returned by multiple edge devices, it can select one edge device from the center of these edge devices as the proxy node, and the selected edge device is the foregoing proxy edge device.

Among them, when selecting the proxy edge-side device, the target edge-side device can select the proxy edge-side device according to the time when the response message returned by each edge-side device is received. For example, it can be the edge corresponding to the first received response message. The side device is determined to be the proxy edge side device, etc.; or the target edge side device can select the proxy edge side device according to the Media Access Control (MAC) address of the edge side device included in each response message. For example, the smallest (or The edge-side device with the largest or random MAC address value is determined to be the proxy edge-side device. Of course, the implementation of how to select the proxy edge-side device is not limited in this embodiment.

If the target edge-side device does not receive the response message returned by other edge-side devices within the first preset time period, it can re-broadcast or multicast the second request until it receives the response message returned by one or more edge-side devices . Of course, if the number of times the target edge-side device attempts to send the second request exceeds the preset threshold, or does not receive a response message returned by other edge-side devices within the second preset duration (which is greater than the first preset duration), Then the target edge device can be handed over to operation and maintenance personnel to configure basic information.

After determining the proxy edge device, the target edge device can send an agent confirmation message to the proxy edge device, and the proxy confirmation message can be used to notify the agent edge device to establish a proxy relationship and become a proxy node of the target edge device. After receiving the agent confirmation message, the agent edge device can establish and maintain an agent relationship with the target edge device (for example, a mapping table that characterizes the agent relationship, etc.), and, in the agent relationship, the agent edge device The device acts as a proxy node, and the target edge side device acts as a lower-level edge side device of the proxy node.

Further, before the edge-side device that receives the second request feeds back the response message to the target edge-side device, it may also check whether its own agent status meets a preset condition to determine whether to feed back the response message. Exemplarily, the agent status may specifically be the number of agent levels of the edge-side device (as shown in FIG. The number of levels is 2), and/or may be the number of lower-level edge-side devices that have established an agent relationship with the edge-side device, etc. When the number of proxy levels of the edge-side device does not exceed the preset number (such as level 2, etc.), and/or the number of lower-level edge-side devices that establish an agency relationship with the edge-side device does not exceed the preset number (such as 50, etc.) , Indicating that the proxy state of the edge-side device itself that receives the second request meets the preset condition, the edge-side device can send a response message for the second request to the target edge-side device; conversely, when the proxy state of the edge-side device itself When the preset condition is not met, the edge-side device may not send the response message. In this way, by checking its own agent status, the agent edge device can avoid the agent relationship network being too complicated, and avoid the agent relationship being concentrated on one agent edge device, so that the agent pressure of the agent edge device can be controlled. For example, when a proxy edge device has more lower-level edge-side devices than the preset number, you can no longer add new lower-level edge-side devices for the proxy edge-side device, and you can select other edge-side devices in the network to become the proxy edge Side equipment to improve network utilization between nodes.

Correspondingly, when the agent edge device becomes the agent node of the target edge device and establishes an agent relationship with the target edge device, the agent edge device can update its own agent status, for example, it can be the subordinate edge side of the agent. The number of equipment has been updated from 45 to 46 and so on.

In other possible implementation manners, the cloud center may also check its own agent status regularly, and after determining that its own agent status meets preset conditions, if it receives a second request from the target edge device, then the agent edge The device may return a corresponding response message, and after determining that its proxy status does not meet the preset condition, if it receives the second request, it may not respond to the second request.

Exemplarily, when the proxy edge device is a lower edge device of another edge device, when the cloud center sends the first configuration information to the proxy edge device, the first configuration information may be configured by the proxy node of the proxy edge device. The information is forwarded to the proxy edge device. Of course, the cloud center may also directly send the first configuration information to the proxy edge device. For example, as shown in Figure 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 will send the first configuration information Forward 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 foregoing embodiment, the proxy edge device obtains the first configuration information corresponding to the target edge device by applying to the cloud center. In another possible implementation manner, the proxy edge device may also store locally The first configuration information corresponding to the target edge-side device. For example, in the scenario of replacing a faulty edge-side device in the network, the first configuration information corresponding to the newly replaced target edge-side device and the faulty edge-side device can be the same, then the proxy corresponding to the faulty edge-side device The node can still become the proxy node of the newly replaced target edge-side device, and the proxy edge-side device as the proxy node can use the locally stored first configuration information corresponding to the failed edge-side device as the target edge-side device correspondence The first configuration information.

Under normal circumstances, when the proxy edge device becomes the proxy node of the target edge device, it can also be the proxy node of other edge devices. Therefore, the proxy edge device may store multiple subordinate edge devices in the local area. The first configuration information. Then, when the proxy edge-side device obtains the first configuration information corresponding to the target edge-side device, it may first obtain the identification of the target edge-side device, such as the serial number or node ID of the target edge-side device, and then, According to the identifier of the target edge-side device, the first configuration information corresponding to the target edge-side device corresponding to the identifier is determined from a plurality of first configuration information stored locally.

S302: The proxy edge-side device sends the first configuration information to the target edge-side device.

Exemplarily, the first configuration information corresponding to the target edge-side device may include device network information, registration information, or other configuration information required by the edge-side device to connect to the cloud center. Among them, the device network information, for example, may be the Internet Protocol (IP) address allocated for the edge-side device, or other information related to the device; the registration information, for example, may be the IP address of the cloud center (such as It can be the IP address of the central management node), the user name and password required for registration, etc.; other configuration information can include time configuration, disk configuration (such as configuring each partition of the disk), certificate configuration (such as configuring the docking station with the cloud center) Required certificates), security policies (such as keys for communicating with the cloud center, access permissions), etc.

S303: The target edge device sends the received first configuration information to the cloud center.

In an example, after acquiring the first configuration information, the target edge-side device may generate a registration request based on the first configuration information. The registration request includes the first configuration information. Then, the target edge-side device may The registration request is sent to the cloud center.

S304: The cloud center verifies the validity of the first configuration information received from the target edge side device.

S305: The cloud center establishes a connection with the target edge device.

Exemplarily, after receiving the registration request sent by the target edge-side device, the cloud center can parse the first configuration information corresponding to the target edge-side device from the registration request, and perform analysis on the first configuration information that is parsed Legality verification. For example, the first configuration information obtained by the target edge device may be obtained from the cloud center by the agent edge device, and the cloud center may verify the first configuration information sent by the target edge device and the previous cloud center. Whether the first configuration information corresponding to the proxy edge-side device is consistent. If the two pieces of first configuration information are consistent, the cloud center can determine that the first configuration information sent by the target edge-side device is legal, and establish a 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 notification message of connection success or connection failure to the target edge side device to notify the target edge side device of the success or failure of the connection establishment request.

After the target edge device successfully establishes a communication connection with the cloud center, when there is another edge device newly deployed in the network area, the target edge device can act as the proxy node of the newly deployed edge device, and The newly deployed edge-side device applies for corresponding first configuration information from the cloud center.

Normally, after the target edge device is deployed in the network, it can provide certain business services, such as cooperating with a third-party business platform to provide face detection services, etc. Therefore, the target edge device establishes a communication connection with the cloud center Later, the operation and maintenance personnel also need to deploy the business services provided by the target edge device.

Based on this, in a further possible implementation manner, the second configuration information required to configure the business service on the target edge-side device may be sent by other devices to the target edge-side 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 with the target edge-side device.

S307: The target edge-side device configures the business service corresponding to the target edge-side device according to the received second configuration information.

Wherein, the second configuration information may be information required for configuring the business service on the target edge device, for example, it may be a container image of the business service, resource occupation information of different business services, and so on. Wherein, the resource occupation information of a business service may include, for example, the memory that each business service can occupy on the target edge device, the CPU occupancy rate of the target edge device allowed when processing the business, and the target edge required to process the business. Any one or more of the information such as the computing capability of the side device, of course, may also include other information, which is not limited in this embodiment.

Since the target edge-side device has successfully established a connection with the cloud center, the second configuration information required to configure the business service on the target edge-side device may be that the cloud center configures the second configuration based on the established communication connection. The information is sent to the target edge-side device, so that the target edge-side device automatically deploys the business service thereon based on the received second configuration information.

Of course, in other possible implementation manners, the cloud center may also send to the target edge-side device through the proxy edge-side device. Alternatively, the second configuration information corresponding to the target edge device stored on the cloud center can be backed up to the proxy edge device in advance. In this way, the proxy edge device can send the first configuration information to the target edge device at the same time. The second configuration information stored thereon is sent to the target edge side device together. Further, when the second configuration information corresponding to the target edge device is backed up on the proxy edge device, the cloud center can periodically update (or check for updates) the second configuration information on the proxy edge device to improve the proxy edge. The completeness and reliability of the second configuration information stored on the device and the timeliness of the backup; moreover, after the second configuration information is stored on the proxy edge device, the cloud center can no longer continue to store the second configuration information, thereby not only It can improve the storage space utilization of the edge-side equipment of the agent, and it can also release part of the storage resources of the cloud center, reducing the storage pressure of the cloud center.

In some scenarios, the edge-side device after power-on may store configuration information. For example, when the proxy edge-side device deployed in the network restarts, or power-on again due to other non-fault reasons, the edge-side device may be If the first configuration information and/or the second configuration information are already stored, the edge-side device can first check whether it has stored the first configuration information and/or the second configuration information after being powered on. If so, it can be based on the Some configuration information is configured accordingly, but if not, the above process of this embodiment can be used to automatically obtain and configure corresponding configuration information. Further, if the first configuration information and/or the second configuration information is not found locally after the edge-side device is powered on again, it can be further found whether to establish a proxy relationship with other edge-side devices. If the proxy relationship exists, then The required configuration information can be obtained from the corresponding agent edge device based on the agent relationship. If the agent relationship does not exist, one agent edge device can be selected from the other edge devices, and the selected agent edge device can be selected from the selected agent edge device. Obtain the required configuration information from the side device.

In this embodiment, the agent edge device can form a hierarchical tree-type agent network after establishing an agent relationship with the target edge device. In this way, when the cloud center needs to deliver information to each edge device in the network, it can be: The information is distributed to each edge device of its agent through the corresponding agent edge device. Take the upgrade of the firmware of the edge-side device as an example. The cloud center can send the new version of the firmware to each agent edge-side device, and then each agent edge-side device sends the received new version of the firmware to its agent to obtain each edge-side device . Under normal circumstances, the number of proxy edge-side devices in the network can be much smaller than the number of proxy edge-side devices (for example, there can be 2 proxy edge-side devices in the network, and each proxy edge-side device can proxy 50 edge-side devices Etc.), which allows the cloud center to only send the new version of the firmware to a small number of proxy edge-side devices, instead of sending the new version of the firmware to the remaining proxy edge-side devices, and the remaining proxy edge-side devices can It is sent by the corresponding agent edge device, which can reduce the resource consumption required by the cloud center during the process of upgrading the firmware of the edge device, and reduce the edge device’s dependence on the cloud center; moreover, multiple agent edge devices can Sending new versions of firmware to multiple proxied edge sides in parallel, which is more efficient for upgrading the firmware of edge side devices in the entire network than the way that the cloud center sends new versions of firmware to edge side devices one by one Can also be effectively improved. Of course, in many scenarios such as software distribution, data synchronization, etc., a process similar to the above-mentioned firmware upgrade can also be used for implementation. This embodiment applies the specific application of the above-mentioned proxy edge-side device to other edge-side devices to send information from the cloud center to other edge-side devices. The scene is not limited.

When the proxy edge device fails or it cannot continue to provide proxy services for the lower edge device due to other reasons, any one or more of the following strategies can be adopted to deal with it:

As an example, each lower-level edge-side device acting as an edge-side device may resend the second request to request other edge-side devices to act as a proxy edge-side device of the lower-level edge-side device and establish a corresponding agent relationship.

In another example, each lower-level edge-side device of the agent edge-side device may elect a new agent edge-side device through competition, and the elected agent edge-side device can be established with other lower-level edge-side devices respectively. The agency relationship becomes the proxy node of the other edge-side devices.

In another example, the proxy edge device may also support a 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 its lower edge The first configuration information and/or the second configuration information corresponding to the device may be synchronized to the backup edge-side device. Of course, the backup edge-side device may be other edge-side devices in the same network area. When the proxy edge side device fails, the backup edge side device may take over the proxy edge side device for management, and become a new proxy node of the lower edge side device of the proxy edge side device. At the same time, for the slave device as a new proxy node, you can also configure a new backup edge device for it, so that when the backup edge device as the new proxy node stops providing proxy services, the new backup edge device configured The side device continues to take over management.

It should be understood that the foregoing examples are only used for illustrative description, and are not used to limit the response strategy for the proxy edge-side device to stop providing proxy services. In practical applications, other coping strategies can also be adopted.

In addition, the embodiment of the present application also provides a device that can be applied to a proxy edge-side device, and the device 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:

The obtaining module 501 is configured to obtain first configuration information corresponding to the target edge side device;

The transmission module 502 is 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 the 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 the identifier of the target edge device, and the first request uses Requesting the cloud center for the first configuration information corresponding to the target edge 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 acquiring module 501 is specifically configured to acquire the identifier of the target edge-side device, and according to the identifier of the target edge-side device, obtain information from at least one locally stored edge-side device corresponding to the The first configuration information corresponding to the target edge-side device is determined in the first configuration information.

In a possible implementation manner, the device further includes an agency relationship establishment 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 act as a proxy node of the target edge-side device;

The agent relationship establishment 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 manner, the device 500 further includes:

The determining module 504 is configured to determine that the agent state of the agent edge device meets a preset condition, the agent state includes the agent level of the agent edge device and/or an agent relationship has been established with the agent edge device The number of edge-side devices.

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

In a possible implementation manner, the device 500 further includes:

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

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

In addition, the embodiment of the present application also provides another apparatus structure applied to a proxy edge-side device. 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. Wherein, the memory 630 may be provided inside the proxy edge-side device, and may also be provided outside the proxy edge-side device. Exemplarily, the actions performed by each proxy edge-side device in the foregoing FIGS. 3 to 4 may be implemented by the processor 620. The processor 620 receives requests, sends media streams, and responses through the communication interface 610, and is used to implement any method executed by the proxy edge device described in FIGS. 3 to 4. In the implementation process, the steps of the processing flow can be implemented by the hardware integrated logic circuit in the processor 620 or the instructions in the form of software to complete the methods executed by the proxy edge-side device in FIGS. 3 to 4. For the sake of brevity, I will not repeat them here. The program code executed by the processor 620 for implementing the foregoing method may be stored in the memory 630. The memory 630 is connected to the processor 620, such as a coupling connection.

Some features of the embodiments of the present application may be implemented/supported by the processor 620 executing program instructions or software codes in the memory 630. The software components loaded on the memory 630 can be summarized in terms of function or logic, for example, the acquisition module 501, the transmission module 502, the proxy relationship establishment module 503, the determination module 504, and the synchronization module 505 shown in FIG.

Any communication interface 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 exchange. For example, the communication interface 610 in the proxy edge device 600, for example, the other device may be a device connected to the proxy edge device 600, for example, it may be a cloud center and/or an edge device.

With the same inventive concept as the above method, an embodiment of the present application also provides a device that can be applied to edge-side devices, and the device can realize the functions of the edge-side devices in the embodiments shown in FIGS. 3 to 4. As shown in FIG. 7, the device 700 includes:

The transmission module 701 is configured to receive the first configuration information corresponding to the edge side device from the agent;

The connection establishment module 702 is 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, and the second request is used to request the proxy edge side device to serve as the target edge side device. The proxy node of the device.

In a possible implementation manner, the device 700 further includes 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 the business service corresponding to the target edge side device according to the second configuration information.

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

In addition, the embodiment of the present application also provides another apparatus structure applied to an edge-side device. As shown in FIG. 8, the edge-side device 800 may include a communication interface 810 and a processor 820. Optionally, the edge-side device 800 may further include a memory 830. Wherein, the memory 830 may be disposed inside the edge-side device, or may be disposed outside the edge-side device. Exemplarily, the actions performed by each edge-side device in FIG. 3 to FIG. 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 used to implement any method executed by the edge-side device described in FIGS. 3 to 4. In the implementation process, the steps of the processing flow can be implemented by the hardware integrated logic circuit in the processor 820 or the instructions in the form of software to complete the method executed by the edge-side device in FIGS. 3 to 4. For the sake of brevity, I will not repeat them here. The program code executed by the processor 820 for implementing the foregoing method may be stored in the memory 830. The memory 830 is connected to the processor 820, such as a coupling connection. Some features of the embodiments of the present application may be implemented/supported by the processor 820 executing program instructions or software codes in the memory 830. The software components loaded on the memory 830 can be summarized in terms of function or logic, for example, the transmission module 701, the connection establishment module 702, and the configuration module 703 shown in FIG. 7.

Any communication interface 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 exchange. For example, the communication interface 810 in the edge-side device 800, for example, the other device may be a device connected to the edge-side device 800, for example, it may be a cloud center and/or a proxy edge-side device.

With the same inventive concept as the above method, an embodiment of the present application also provides a device that can be applied to a cloud center, and the device can implement the functions of the cloud center in the embodiments shown in FIGS. 3 to 4 above. As shown in FIG. 9, the device 900 includes:

The determining module 901 is configured to determine the first configuration information corresponding to the target edge side device;

The transmission module 902 is configured to send the first configuration information to the 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 903 is configured to verify 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;

The connection establishment module 904 is configured to establish a connection with the target edge-side device.

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

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

In a possible implementation manner, the transmission module 902 is further configured to send a target program to the proxy edge-side device, and the target 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 the target edge device to the target edge device based on the established connection between the cloud center and the target edge device The second configuration information corresponding to the device, where the second configuration information is used to configure the business service corresponding to the target edge-side device.

In addition, the embodiment of the present application also provides another device structure applied to the cloud center. 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. Among them, the storage 1030 may be arranged inside the cloud center or outside the cloud center. Exemplarily, the actions performed by each cloud center in the foregoing FIGS. 3 to 4 may be implemented by the processor 1020. The processor 1020 receives requests, sends media streams and responses through the communication interface 1010, and is used to implement any method executed by the cloud center described in FIGS. 3 to 4. In the implementation process, the steps of the processing flow can be implemented by the hardware integrated logic circuit in the processor 1020 or the instructions in the form of software to complete the methods executed by the edge-side device in FIGS. 3 to 4. For the sake of brevity, I will not repeat them here. The program code executed by the processor 1020 for implementing the foregoing method may be stored in the memory 1030. The memory 1030 is connected to the processor 1020, such as a coupling connection. Some features of the embodiments of the present application may be implemented/supported by the processor 1020 executing program instructions or software codes in the memory 1030. The software components loaded on the memory 1030 can be summarized in terms of function or logic, for example, the determination module 901, the transmission module 902, the verification module 903, and the connection establishment module 904 shown in FIG.

Any communication interface 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. For example, the communication interface 1010 in the cloud center 1000, for example, the other device may be a device connected to the cloud center 1000, for example, it may be an edge-side device and/or a proxy edge-side device.

The processors involved 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 gates or transistor logic devices, discrete hardware components, and may implement or Perform the methods, steps, and logical block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.

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

The processor may cooperate with the memory. The memory can be a non-volatile memory, such as a hard disk (Hard Disk Drive, HDD) or a solid-state drive (Solid-State Drive, SSD), etc., or a volatile memory (Volatile Memory), such as random access memory (Random- Access Memory, RAM). The memory is any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited to this.

The embodiment of the present application does not limit the specific connection medium between the foregoing communication interface, processor, and memory. For example, the memory, the processor, and the communication interface can be connected by a bus. The bus can be divided into an address bus, a data bus, a control bus, and so on.

Based on the above embodiments, the embodiments of the present application also provide a computer storage medium, the storage medium stores a software program, and when the software program is read and executed by one or more processors, any one or more of the above The embodiment provides a method executed by proxy edge-side device or edge-side device or cloud center. The computer storage medium may include: U disk, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk and other media that can store program codes.

Based on the above embodiments, the embodiments of the present application also provide a chip including a processor, which is used to implement the functions of the proxy edge-side device or the function of the edge-side device or the function of the cloud center involved in the above-mentioned embodiments, for example Used to implement the method performed by the proxy edge-side device in Figures 3 to 4, used to implement the method performed by the edge-side device in Figures 3 to 4, or used to implement the method performed by the cloud center in Figures 3 to 4 method. Optionally, the chip further includes a memory, and the memory is used for necessary program instructions and data to be executed by the processor. The chip can be composed of a chip, or it can include a chip and other discrete devices.

The terms "first", "second", etc. in the description and claims of the application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific sequence or sequence. It should be understood that the terms used in this way can be interchanged under appropriate circumstances, and this is only used to describe the method of distinguishing objects with the same attribute in the description of the embodiments of the present application.

Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, this application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

This application is described with reference to flowcharts and/or block diagrams of methods, devices (systems), and computer program products according to embodiments of this application. It should be understood that each process and/or block in the flowchart and/or block diagram, and the combination of processes and/or blocks in the flowchart and/or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing equipment to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing equipment are used to generate It is a device that realizes the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device. The device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment. The instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.

Obviously, those skilled in the art can make various changes and modifications to the embodiments of the present application without departing from the scope of the embodiments of the present application. In this way, if these modifications and variations of the embodiments of this application fall within the scope of the claims of this application and their equivalent technologies, this application is also intended to include these modifications and variations.

Claims

A method for configuring an edge-side device, characterized in that the method is applied to a proxy edge-side device, and the method includes:

Acquiring first configuration information corresponding to the target edge side device;

The first configuration information is sent 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 the cloud center.
The method according to claim 1, wherein the method further comprises:

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

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

Receiving a response message from the cloud center, where the response message includes the first configuration information.
The method according to claim 1, wherein the acquiring first configuration information corresponding to the target edge-side device comprises:

Acquiring the identifier of the target edge side device;

According to the identifier of the target edge-side device, the first configuration information corresponding to the target edge-side device is determined from the first configuration information corresponding to at least one edge-side device stored locally.
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 act as a proxy node of the target edge-side device;

According to the second request, a proxy relationship between the proxy edge-side device and the target edge-side device is established.
The method according to claim 4, characterized in that, before establishing a proxy relationship between the proxy edge-side device and the target edge-side device according to the second request, the method further comprises:

It is determined that the agent state of the agent edge-side device satisfies a preset condition, and the agent state includes the agent level of the agent edge-side device or the number of edge-side devices that have established an agent relationship with the agent edge-side device.
The method according to any one of claims 1 to 5, wherein the method further comprises:

Sending second configuration information corresponding to the target edge device to the target edge device, where the second configuration information is used to configure a business service corresponding to the target edge device.
The method according to claim 6, wherein the method further comprises:

The first configuration information or the second configuration information is synchronized to a backup edge-side device, where the backup edge-side device is used to act as a proxy node of the target edge-side device when the proxy edge-side device fails.
The method according to claim 4 or 5, wherein after establishing the agent relationship between the agent edge-side device and the target edge-side device, the method further comprises:

Receiving the target program from the cloud center;

Send the target program to the target edge-side device, where the target edge-side device and the proxy edge-side device are located in the same network area.
A method for configuring an edge-side device, wherein the method is applied to a target edge-side device, and the method includes:

Receiving the first configuration information corresponding to the edge side device from the agent;

According to the first configuration information, a connection is established with the cloud center.
The method according to claim 9, wherein the method further comprises:

A second request is sent to the proxy edge-side device, where the second request is used to request the proxy edge-side device to act as a proxy node of the target edge-side device, and the target edge-side device and the proxy edge-side device Located in the same network area.
The method according to claim 9 or 10, wherein the method further comprises:

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

Configure the business service corresponding to the target edge device according to the second configuration information.
A method for configuring edge-side devices, characterized in that the method is applied to a cloud center, and the method includes:

Determine the first configuration information corresponding to the target edge side device;

Sending the first configuration information to the 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;

Verifying the first configuration information from the target edge side device;

Establish a connection with the target edge-side device.
A device for configuring edge-side equipment, characterized in that the device is applied to proxy edge-side equipment, and the device includes:

An obtaining module, configured to obtain first configuration information corresponding to the target edge side device;

The transmission module is 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 the cloud center.
The apparatus according to claim 13, wherein the transmission module is further configured to send a first request to the cloud center, and the first request includes an identifier of the target edge device, and the first request A request is used to request first configuration information corresponding to the target edge device from the cloud center;

The acquiring module is specifically configured to receive a response message from the cloud center, where the response message includes the first configuration information.
The apparatus according to claim 13, wherein the acquisition module is configured to acquire the identifier of the target edge-side device, and obtain from at least one locally stored edge-side device according to the identifier of the target edge-side device The first configuration information corresponding to the target edge-side device is determined in the corresponding first configuration information.
The device according to any one of claims 13 to 15, wherein the device further comprises a proxy relationship establishment module;

The transmission module 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 act as a proxy node of the target edge-side device;

The agent relationship establishment module is configured to establish an agent relationship between the agent edge-side device and the target edge-side device according to the second request.
The device according to claim 16, wherein the device further comprises:

The determining module is configured to determine that the agent state of the agent edge device meets a preset condition, and the agent state includes the agent level of the agent edge device and/or the agent relationship has been established with the agent edge device The number of edge devices.
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-side device to the target edge-side device, and the second The configuration information is used to configure the business service corresponding to the target edge side device.
The device according to claim 18, wherein the device further comprises:

The synchronization module is configured to synchronize the first configuration information and/or the second configuration information to a backup edge-side device, and the backup edge-side device is used to serve as the target when the proxy edge-side device fails The proxy node of the edge device.
An apparatus for configuring edge-side equipment, characterized in that the apparatus is applied to a target edge-side equipment, and the apparatus includes:

The transmission module is used to receive the first configuration information corresponding to the edge side device from the agent;

The connection establishment module is configured to establish a connection with the cloud center according to the first configuration information.
A device for configuring edge-side equipment, characterized in that the device is applied to a cloud center, and the device includes:

The determining module is used to determine the first configuration information corresponding to the target edge side device;

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;

A verification module, configured to verify the first configuration information from the target edge side device;

The connection establishment module is used to establish a connection with the target edge side device.
A computing device, characterized in that the device includes a memory and a processor, the memory is used to store software instructions; the processor calls the software instructions stored in the memory to execute the above claims 1 to 8 Any of the methods described.
A computing device, characterized in that the device includes a memory and a processor, the memory is used to store software instructions; the processor calls the software instructions stored in the memory to execute the above claims 9 to 11 Any of the methods described.
A system for configuring edge-side devices, characterized in that the system includes a proxy edge-side device, a target edge-side device, and a cloud center;

The proxy edge-side device is configured to send first configuration information corresponding to the target edge-side device to the target edge-side device;

The target edge side device is used to send the first configuration information to the cloud center;

The cloud center is used to: verify the first configuration information from the target edge side device;

Establish a connection with the target edge-side device.