Registration method and analysis method of edge node, cloud, equipment and medium

Abstract

The invention provides an edge node registration method, an edge node analysis method, a cloud, equipment and a medium, and relates to the technical field of computers. According to the method, at least two tunnel service instances can be deployed in the cloud, and each tunnel service instance has a corresponding instance IP address, so that the support of tunnel service level capacity expansion is realized. On this basis, the edge node can accurately establish tunnel connection with the corresponding tunnel service instance through different instance IP addresses, and register the instance IP addresses and the node identifier of the corresponding edge node in the preset database, so that the cloud can determine the corresponding tunnel service instance through different instance IP addresses to access the edge node. The load can be balanced in registration and analysis of large-scale edge nodes, and the efficiency of cloud edge tunnel establishment and node access is effectively improved.

Description

Background Art

[0002] In the cloud-edge architecture, the cloud and edge nodes are usually located in different network planes. At this time, the edge nodes can register with the Yurt-Tunnel-Server (tunnel service) on the cloud through the Yurt-Tunnel-Agent (tunnel agent) to build a cloud-edge tunnel and realize cross-network communication.

[0003] However, when edge nodes register to the cloud on a large scale from tunnel services through tunnel proxies, and when the cloud resolves to edge nodes of corresponding tunnel proxies on a large scale through tunnel proxy services, the tunnel service is burdened with heavy load, which affects the efficiency of cloud-edge tunnel establishment and node access, and further affects the quality of network services.

[0004] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0005] The purpose of the present disclosure is to provide an edge node registration method, an edge node resolution method, a cloud, an electronic device and a computer-readable storage medium, which support horizontal capacity expansion through a tunnel service instance, balance the burden in the registration and resolution of large-scale edge nodes, and improve the efficiency of cloud-edge tunnel establishment and node access.

[0006] According to the first aspect of the present disclosure, a cloud is provided, which is deployed with at least two tunnel service instances, each of which has a corresponding instance IP address; wherein, when the tunnel service instance establishes a tunnel connection with an edge node, the instance IP address and the node identifier of the edge node are registered correspondingly in a preset database.

[0007] According to the second aspect of the present disclosure, a registration method for an edge node is provided, which is applied to the cloud. The method may include: in the process of the edge node establishing a tunnel connection with a tunnel service instance through a tunnel agent component, obtaining the node identifier of the edge node and the instance IP address of the tunnel service instance; registering the node identifier and the instance IP address correspondingly in a preset database.

[0008] In an exemplary embodiment, when the edge node disconnects the tunnel connection established with the tunnel service instance through the tunnel proxy component, the node identifier of the edge node and the instance IP address of the tunnel service instance are deleted from the preset database.

[0009] According to a third aspect of the present disclosure, a method for parsing an edge node is provided, which is applied to the cloud. The method may include obtaining a node identifier of the edge node, the edge node being registered to the cloud through the method of the aforementioned second aspect; querying a corresponding instance IP address based on the node identifier in a preset database; and determining a corresponding tunnel service instance based on the instance IP address.

[0010] In an exemplary embodiment, after determining the corresponding tunnel service instance according to the instance IP address, the method further includes: accessing the edge node through a tunnel connection established between the tunnel service instance and a tunnel proxy component on the edge node.

[0011] In an exemplary embodiment, querying the corresponding instance IP address based on the node identifier in a preset database includes: if querying the corresponding service IP address based on the node identifier fails, querying the corresponding instance IP address based on the node identifier in the preset database.

[0012] According to a fourth aspect of the present disclosure, a cloud is provided, in which a proxy service update component is deployed, which is used to obtain the node identifier of the edge node and the instance IP address of the tunnel service instance during the process of the edge node establishing a tunnel connection with a tunnel service instance through the tunnel proxy component; and register the node identifier and the instance IP address in a preset database in correspondence.

[0013] In an exemplary embodiment, the proxy service update component is further used to delete the node identifier of the edge node and the instance IP address of the tunnel service instance in the preset database when the edge node disconnects the tunnel connection established with the tunnel service instance through the tunnel proxy component.

[0014] According to a fifth aspect of the present disclosure, a cloud is provided, which is deployed with a global domain name resolution component for obtaining a node identifier of an edge node, wherein the edge node is registered to the cloud by the method of the second aspect described above; a corresponding instance IP address is queried in a preset database based on the node identifier; a corresponding tunnel service instance is determined according to the instance IP address, and the edge node is accessed through a tunnel connection established between the tunnel service instance and a tunnel agent component on the edge node.

[0015] In an exemplary embodiment, the cloud also includes a native domain name resolution component, which is used to forward the node identifier to the global domain name resolution component when the query of the corresponding service IP address based on the node identifier fails.

[0016] According to a sixth aspect of the present disclosure, there is provided an electronic device, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to implement the above method by executing the executable instructions.

[0017] According to a seventh aspect of the present disclosure, there is provided a computer-readable storage medium on which a computer program is stored, and the computer program implements the above method when executed by a processor.

[0018] The edge node registration method, edge node resolution method, cloud, electronic device and computer-readable storage medium provided by the embodiments of the present disclosure. Among them, at least two tunnel service instances can be deployed in the cloud, and each tunnel service instance has a corresponding instance IP address, which supports the horizontal expansion of the tunnel service. On this basis, the edge node can accurately establish a tunnel connection with the corresponding tunnel service instance through different instance IP addresses, and register the instance IP address and the node identifier of the corresponding edge node in the preset database, and then the cloud can determine the corresponding tunnel service instance through different instance IP addresses to access the edge node, which can balance the burden in the registration and resolution of large-scale edge nodes, and effectively improve the efficiency of cloud-edge tunnel establishment and node access.

[0019] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The accompanying drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the specification are used to explain the principles of the present disclosure. Obviously, the accompanying drawings described below are only some embodiments of the present disclosure, and for ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without creative work.

[0021] Figure 1 One of the cloud edge architecture schematic diagrams according to an exemplary embodiment of the present disclosure is shown.

[0022] Figure 2 A flowchart of a registration method for an edge node according to an exemplary embodiment of the present disclosure is shown.

[0023] Figure 3 One of the flow charts of the steps of the edge node parsing method according to an exemplary embodiment of the present disclosure is shown.

[0024] Figure 4 The second flowchart of the step of the edge node parsing method according to the exemplary embodiment of the present disclosure is shown.

[0025] Figure 5 A second schematic diagram of a cloud-edge architecture according to an exemplary embodiment of the present disclosure is shown.

[0026] Figure 6 The figure shows a schematic diagram of the composition of an electronic device to which the exemplary embodiments of the present disclosure can be applied. DETAILED DESCRIPTION

[0027] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that the disclosure will be more comprehensive and complete and to fully convey the concepts of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0028] In addition, the accompanying drawings are only schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.

[0029] The disclosed embodiment is applied to the scenario where the edge node establishes a tunnel connection with the tunnel service deployed in the cloud through the tunnel proxy, and then the cloud can access the edge node through the tunnel connection. At present, ClusterIP is usually used in the relevant technology to expose the tunnel service to the outside. In essence, the cluster is a fixed virtual IP in the cluster allocated to the tunnel service. This method makes the tunnel service only discoverable or accessible by the fixed virtual IP, which is a heavy burden in the registration and resolution of large-scale edge nodes, affecting the efficiency of cloud-edge tunnel establishment and node access.

[0030] In view of the above problems, the embodiments of the present disclosure provide a cloud-based and remote-based edge node registration method and resolution method, which supports the deployment of tunnel service instances, realizes registration and resolution based on instance IP addresses and node identifiers of edge nodes, realizes horizontal expansion support for tunnel service instances, and improves the flexibility and balance of cloud-edge tunnel establishment and cloud-based access to edge nodes. The specific description is as follows in conjunction with the accompanying drawings:

[0031] Figure 1 FIG. 1 shows one of the cloud-edge architecture schematic diagrams according to an exemplary embodiment of the present disclosure. Figure 1 The cloud 110 is deployed with at least two tunnel service instances 111, each of which has a corresponding instance IP address; wherein, when the tunnel service instance establishes a tunnel connection with the edge node 120, the instance IP address and the node identifier of the edge node are registered in the preset database 112 accordingly.

[0032] like Figure 1As shown, the cloud 110 can deploy any number of tunnel service instances 111 (only two are shown), and on this basis, support horizontal expansion by increasing the number of tunnel service instances 111, and dynamically allocate instance IP addresses to each tunnel service instance 111. The edge node 120 can establish tunnel connections with different tunnel service instances 111 through different instance IP addresses. One edge node 120 can be connected to one tunnel service instance 111, or multiple edge nodes 120 can be connected to one tunnel service instance 111, thereby improving the flexibility of establishing cloud-edge tunnels and balancing the connection requirements of large-scale edge nodes.

[0033] On this basis, when the tunnel service instance 111 establishes a tunnel connection with the edge node 120, its instance IP address and the node identifier of the edge node 120 can be registered in the preset database in correspondence. The node identifier is the information that uniquely represents the edge node. The preset database can realize the registration and discovery functions of the service. By correspondingly storing the node identifier and the instance IP address, when the edge node is to be accessed in the cloud, the instance IP address can be queried according to the node identifier, thereby realizing the solution of accessing the edge node based on the instance IP address. The whole process support of multiple tunnel service instances from registration to resolution can be realized, avoiding access anomalies and the inability to schedule to other instances.

[0034] Figure 2 FIG. 1 shows a flow chart of the steps of a registration method for an edge node according to an exemplary embodiment of the present disclosure. Figure 2 , the method may include steps 201 to 202:

[0035] In step 201, in the process of establishing a tunnel connection between an edge node and a tunnel service instance through a tunnel proxy component, a node identifier of the edge node and an instance IP address of the tunnel service instance are obtained.

[0036] In the present disclosure, Figure 1 As shown, each edge node 120 may be deployed with a tunnel proxy component 121, and the edge node 120 establishes a tunnel connection with a tunnel service instance 111 through the tunnel proxy component 121. The cloud can monitor the process of establishing the tunnel connection, so as to obtain the node identifier of the corresponding edge node and the instance IP address of the tunnel service instance when a new tunnel connection is added, so as to support the subsequent registration process based on the node identifier and the instance IP address.

[0037] In step 202, the node identifier and the instance IP address are registered in a preset database in correspondence.

[0038] In the disclosed embodiment, the preset database can be a component that supports registration and discovery based on storage functions. When an edge node establishes a tunnel connection with a tunnel service instance through a tunnel proxy component, the node identifier and the instance IP address can be dynamically registered in the preset database so that address resolution can be performed based on the node identifier when accessing the edge node in the cloud. The preset database can use key-value data storage, which has higher read and write performance and improves the efficiency of information registration and call; it can also use distributed storage, which has better reliability, stability and scalability.

[0039] In an optional method embodiment of the present disclosure, the method may further include the following step 203.

[0040] In step 203, when the edge node disconnects the tunnel connection established with the tunnel service instance through the tunnel proxy component, the node identifier of the edge node and the instance IP address of the tunnel service instance are deleted from the preset database.

[0041] In the disclosed embodiment, the cloud can also monitor the edge node's disconnection of the tunnel connection established between the tunnel agent component and the tunnel service instance. It can be understood that when the tunnel connection is disconnected, the registration can be canceled, and the node identifier of the edge node and the instance IP address of the corresponding tunnel service instance can be deleted from the preset database, thereby avoiding the inability to call the tunnel connection of the corresponding tunnel agent component based on the registration information when accessing the cloud, and the address resolution exception.

[0042] Figure 3 FIG. 1 shows one of the flow charts of the step of the edge node parsing method according to an exemplary embodiment of the present disclosure. Figure 3 , the method may include steps 301 to 303:

[0043] In step 301, the node identification of the edge node is obtained, and the edge node is registered to the cloud through the aforementioned registration method.

[0044] In the embodiment of the present disclosure, when the cloud is about to access the edge node, it can first obtain the node identification of the edge node. Figure 2 The registration method of the edge node is registered to the cloud. For details, please refer to Figure 2 To avoid repetition, the related description will not be repeated here.

[0045] In step 302, the corresponding instance IP address is queried in a preset database based on the node identifier.

[0046] On this basis, based on the node identifier, the instance IP address stored corresponding to the node identifier is queried in the preset database and matched to obtain the instance IP address corresponding to the tunnel service instance that establishes a tunnel connection with the tunnel proxy component of the edge node.

[0047] In step 303, the corresponding tunnel service instance is determined according to the instance IP address.

[0048] At this point, the cloud can determine the specific tunnel service instance based on the instance IP address, and successfully implement address resolution for edge nodes based on multiple tunnel service instances.

[0049] In an optional exemplary embodiment of the present disclosure, step 304 may be further included after step 303 .

[0050] In step 304, the edge node is accessed through the tunnel connection established between the tunnel service instance and the tunnel proxy component on the edge node.

[0051] In the disclosed embodiment, the cloud can access the edge node through a tunnel connection based on this, and the tunnel connection is established between the tunnel service instance and the tunnel proxy component on the edge node. The tunnel service instance supports horizontal expansion, has better flexibility, and supports the creation, connection, registration and resolution of multiple tunnel service instances, which can balance the burden and effectively improve the efficiency of large-scale edge nodes, such as more than 100,000, when establishing cloud-edge tunnels and being accessed by the cloud.

[0052] Figure 4 FIG2 shows a second flow chart of the step of the edge node parsing method according to an exemplary embodiment of the present disclosure. Figure 4 , the method may include steps 401 to 403:

[0053] In step 401, the node identification of the edge node is obtained, and the edge node is registered to the cloud through the aforementioned registration method.

[0054] In the embodiment of the present disclosure, step 401 may correspond to the relevant description of the aforementioned step 301, and will not be described again here to avoid repetition.

[0055] In step 402, when the query of the corresponding service IP address based on the node identifier fails, the corresponding instance IP address is queried in a preset database based on the node identifier.

[0056] In the actual deployment process, it can be expanded on the basis of the existing query logic. The native domain name resolution in the cluster can query the corresponding service IP (ClusterIP) address based on the node identifier. At this time, the query fails because the instance IP address is used for the tunnel service instance. On this basis, it can be configured to query the corresponding instance IP address based on the node identifier in the preset database when the query service IP address fails. The relevant description of the specific query can refer to the aforementioned step 302. To avoid repetition, it will not be repeated here. Through this logic, the edge node resolution method provided by the present disclosure can be upgraded and deployed in the existing cluster architecture at low cost and quickly.

[0057] In step 403, the corresponding tunnel service instance is determined according to the instance IP address.

[0058] In the embodiment of the present disclosure, step 403 may correspond to the relevant description of the aforementioned step 303, and will not be described again here to avoid repetition.

[0059] The cloud and edge node registration methods and edge node resolution methods provided in the embodiments of the present disclosure. Among them, at least two tunnel service instances can be deployed in the cloud, and each tunnel service instance has a corresponding instance IP address, which supports the horizontal expansion of the tunnel service. On this basis, the edge node can accurately establish a tunnel connection with the corresponding tunnel service instance through different instance IP addresses, and register the instance IP address and the node identifier of the corresponding edge node in the preset database, and then the cloud can determine the corresponding tunnel service instance through different instance IP addresses to access the edge node, which can balance the burden in the registration and resolution of large-scale edge nodes, and effectively improve the efficiency of cloud-edge tunnel establishment and node access.

[0060] It should be noted that the above figures are only schematic illustrations of the processes included in the method according to the exemplary embodiments of the present disclosure, and are not intended to be limiting. It is easy to understand that the processes shown in the above figures do not indicate or limit the time sequence of these processes. In addition, it is also easy to understand that these processes can be performed synchronously or asynchronously, for example, in multiple modules.

[0061] Furthermore, in the embodiments of the present disclosure, the aforementioned functions can be realized by developing corresponding functional components and deploying the functional components to the cloud. Figures 1 to 4 method. Figure 5 FIG2 shows a second schematic diagram of a cloud edge architecture according to an exemplary embodiment of the present disclosure. Figure 5As shown, in an exemplary embodiment of the present disclosure, a cloud 510 is provided, in which a proxy service update component 511 is deployed, which is used to obtain the node identifier of the edge node 520 and the instance IP address of the tunnel service instance 512 during the process of the edge node 520 establishing a tunnel connection with a tunnel service instance 512 through the tunnel proxy component 521; and register the node identifier and the instance IP address correspondingly in the preset database 530.

[0062] The proxy service update component 511 can realize automatic registration of information into a preset database, and has a function of initializing the connection to the preset database. For example, the proxy service update component 511 registers the node identifier of edge node 1 and the instance IP address of tunnel service instance 1 into the preset database 530, registers the node identifier of edge node 2 and the instance IP address of tunnel service instance 1 into the preset database 530, and registers the node identifier of edge node 3 and the instance IP address of tunnel service instance 2 into the preset database 530.

[0063] In an exemplary embodiment, the proxy service update component 511 is also used to delete the node identifier of the edge node 520 and the instance IP address of the tunnel service instance 512 in the preset database 530 when the edge node 520 disconnects the tunnel connection established with the tunnel service instance 512 through the tunnel proxy component 521.

[0064] Furthermore, the proxy service update component 511 can also automatically delete the registration record in the preset database.

[0065] In the disclosed embodiment, the preset database can be implemented using etcd. etcd is a cloud-native storage component that can build a highly available distributed key-value storage database, and on this basis, as an information registration center, provide registration and resolution functions for node identifiers and instance IP addresses. The proxy service update component 511 can be extended and implemented on the basis of the apiserver-network-proxy component. By extending the NewProxyServerAdapter data registration function, it adds the function of connecting to etcd initialization, including configuring etcd's endpoints, caFile, certFile, keyFile parameters, and automatically adding and deleting etcd records. The function can write node identifiers and instance IP addresses to etcd or delete them from etcd. Among them, the endpoints parameter specifies the access address, and the caFile, certFile, and keyFile parameters specify the certificate and key files required for communication.

[0066] Relying on the extended function of the apiserver-network-proxy component, etcd is initialized and connected during the startup process, and the tunnel proxy component that monitors the edge node is called to establish a tunnel connection with the tunnel service instance. The node identifier and instance IP address are registered in etcd as an A record by calling addBandendAdapter(agentID, stream, tunnelServerPodIp, etcdClient); in the process of disconnecting the tunnel connection, the node identifier and instance IP address are deleted from etcd by calling removeBackendAdapter(agentId, stream, tunnelServerPodIp, etcdClient). The node identifier can be represented by the hostname and suffixed with edge.local.

[0067] Among them, the apiserver-network-proxy component can be deployed in the cloud-native helm chart mode. By extending and transforming the apiserver-network-proxy connection logic, it can be dynamically registered to etcd when the edge node is dynamically connected to the tunnel service instance.

[0068] refer to Figure 5 A cloud 510 is provided as shown, and a global domain name resolution component 513 is deployed on the cloud 510 for obtaining the node identifier of the edge node 520. The edge node 520 is registered to the cloud 510 through the method of the second aspect mentioned above; the corresponding instance IP address is queried in the preset database 530 based on the node identifier; the corresponding tunnel service instance 512 is determined according to the instance IP address, so that the cloud accesses the edge node 520 through the tunnel connection established between the tunnel service instance 512 and the tunnel agent component 521 on the edge node 520.

[0069] Among them, the global domain name resolution component 513 can query and read the data of the preset database on the basis of determining the node identifier to determine the instance IP address corresponding to the node identifier registered to the cloud, thereby realizing address resolution.

[0070] In the disclosed embodiment, the global domain name resolution component 513 can be implemented by extension based on the coredns component, by developing a reading plug-in for a preset database to read its data, such as extending the etcd reading plug-in to read the registration information stored in etcd.

[0071] In an exemplary embodiment, the cloud 510 further includes a native domain name resolution component 514 for forwarding the node identifier to the global domain name resolution component 513 when a query based on the node identifier for the corresponding service IP address fails.

[0072] In the disclosed embodiment, the native domain name resolution component 514 may be a coredns component that has been deployed and is running in the cluster, and is used to implement service IP address query. On this basis, corefile configuration, edge.Local configuration, and forward configuration may be performed to point to the global domain name resolution component 513 when the query fails.

[0073] Among them, the global domain name resolution component 513 can be deployed through the cloud native helm chart method.

[0074] For example, the business of cloud 510 needs to access the node identifier of edge node 520, which is https: / / node001.edge.local. In the process of establishing a tunnel connection, the edge node 520 saves an A record in / skudns / local / edge / node001 in the preset database 530 based on the proxy service update component 511 to register the instance IP address. At this time, the native domain name resolution component 514 can query the service IP address corresponding to https: / / node001.edge.local, and forward it to the global domain name resolution component 513 in the scenario where the query fails. The global domain name resolution component 513 queries the preset database 530 based on the node identifier and returns the corresponding A record data. The cloud 510 thereby obtains the instance IP address https: / / IP and accesses the edge node based on the instance IP address.

[0075] The cloud provided by the embodiment of the present disclosure can be deployed with functional components, such as a proxy service update component, a global domain name resolution component, etc. Among them, the cloud can be deployed with at least two tunnel service instances, and each tunnel service instance has a corresponding instance IP address, which supports the horizontal expansion of the tunnel service. On this basis, the edge node can accurately establish a tunnel connection with the corresponding tunnel service instance through different instance IP addresses, and register the instance IP address and the node identifier of the corresponding edge node into a preset database. Then, the cloud can determine the corresponding tunnel service instance through different instance IP addresses to access the edge node, which can balance the burden in the registration and resolution of large-scale edge nodes, and effectively improve the efficiency of cloud-edge tunnel establishment and node access.

[0076] The specific details of each component in the above-mentioned cloud have been described in detail in the implementation method of the method part. The undisclosed details can be found in the implementation method of the method part, that is, the explanation and beneficial effects of the registration method of the edge node and the parsing method of the edge node in the above-mentioned embodiment are also applicable to the cloud 510 of the embodiment of the present disclosure, and will not be elaborated here.

[0077] Those skilled in the art will appreciate that various aspects of the present disclosure may be implemented as systems, methods or program products. Therefore, various aspects of the present disclosure may be specifically implemented in the following forms, namely: complete hardware implementation, complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software, which may be collectively referred to herein as "circuits", "modules" or "systems".

[0078] Refer to the following Figure 6 hereinafter describes an electronic device 600 according to such an embodiment of the present disclosure. Figure 6 The electronic device 600 shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0079] like Figure 6 As shown, the electronic device 600 is in the form of a general computing device. The components of the electronic device 600 may include but are not limited to: at least one processing unit 610, at least one storage unit 620, a bus 630 connecting different system components (including the storage unit 620 and the processing unit 610), and a display unit 640.

[0080] The storage unit stores program codes, which can be executed by the processing unit 610, so that the processing unit 610 executes the steps according to various exemplary embodiments of the present disclosure described in the above “Exemplary Method” section of this specification.

[0081] The storage unit 620 may include a readable medium in the form of a volatile storage unit, such as a random access memory unit (RAM) 621 and / or a cache memory unit 622 , and may further include a read-only memory unit (ROM) 623 .

[0082] The storage unit 620 may also include a program / utility 624 having a set (at least one) of program modules 625, such program modules 625 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0083] Bus 630 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0084] The electronic device 600 may also communicate with one or more external devices 700 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 600, and / or communicate with any device that enables the electronic device 600 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed via an input / output (I / O) interface 650. Furthermore, the electronic device 600 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via a network adapter 660. As shown, the network adapter 660 communicates with other modules of the electronic device 600 via a bus 630. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 600, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

[0085] In addition, the exemplary embodiments of the present disclosure further provide a computer-readable storage medium on which a program product capable of implementing the above-mentioned method of the present specification is stored. In some possible implementations, various aspects of the present disclosure may also be implemented in the form of a program product, which includes a program code, and when the program product is run on a terminal device, the program code is used to enable the terminal device to execute the steps according to various exemplary embodiments of the present disclosure described in the above-mentioned "Exemplary Method" section of the present specification.

[0086] It should be noted that the computer-readable medium shown in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0087] In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, apparatus, or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in combination with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0088] In addition, program code for performing the operations of the present disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., through the Internet using an Internet service provider).

[0089] Other embodiments of the present disclosure will be readily apparent to those skilled in the art after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary technical means in the art that are not disclosed in the present disclosure. The specification and embodiments are to be considered merely as exemplary, and the true scope and spirit of the present disclosure are indicated by the claims.

Claims

1. A cloud, characterized in that: The cloud is deployed with at least two tunnel service instances, each of which has a corresponding instance IP address; wherein, when the tunnel service instance establishes a tunnel connection with an edge node, the instance IP address and the node identifier of the edge node are registered correspondingly in a preset database.

2. A registration method for an edge node, characterized in that: The method is applied to the cloud, and the method includes: In the process of establishing a tunnel connection between an edge node and a tunnel service instance through a tunnel proxy component, obtaining a node identifier of the edge node and an instance IP address of the tunnel service instance; The node identifier and the instance IP address are registered in a preset database in correspondence.

3. The method according to claim 2, characterized in that The method further comprises: In the process of the edge node disconnecting the tunnel connection established with the tunnel service instance through the tunnel proxy component, the node identifier of the edge node and the instance IP address of the tunnel service instance are deleted from the preset database.

4. A method for analyzing edge nodes, characterized in that: The method is applied to the cloud, and the method includes: Obtaining a node identifier of an edge node, the edge node being registered to the cloud by the method described in any one of claims 2 to 3; Querying the corresponding instance IP address based on the node identifier in a preset database; Determine a corresponding tunnel service instance according to the instance IP address.

5. The method according to claim 4, characterized in that After determining the corresponding tunnel service instance according to the instance IP address, the method further includes: The edge node is accessed through a tunnel connection established between the tunnel service instance and a tunnel proxy component on the edge node.

6. The method according to claim 4, characterized in that The querying the corresponding instance IP address based on the node identifier in the preset database includes: In the case that the query of the corresponding service IP address based on the node identifier fails, the corresponding instance IP address is queried based on the node identifier in the preset database.

7. A cloud, characterized in that: The cloud is deployed with a proxy service update component, which is used to obtain the node identifier of the edge node and the instance IP address of the tunnel service instance during the process of the edge node establishing a tunnel connection with a tunnel service instance through the tunnel proxy component; The node identifier and the instance IP address are registered in a preset database in correspondence.

8. The cloud according to claim 7, characterized in that: The proxy service update component is also used to delete the node identifier of the edge node and the instance IP address of the tunnel service instance in the preset database when the edge node disconnects the tunnel connection established with the tunnel service instance through the tunnel proxy component.

9. A cloud, characterized in that: The cloud is deployed with a global domain name resolution component, which is used to obtain the node identifier of the edge node. The edge node is registered to the cloud by any of the methods described in claims 2 to 3 above; the corresponding instance IP address is queried in a preset database based on the node identifier; the corresponding tunnel service instance is determined according to the instance IP address, so that the cloud can access the edge node through the tunnel connection established between the tunnel service instance and the tunnel agent component on the edge node.

10. The cloud according to claim 9, characterized in that: The cloud also includes a native domain name resolution component, and the native domain name resolution component is used to forward the node identifier to the global domain name resolution component when a query based on the node identifier for a corresponding service IP address fails.

11. An electronic device, characterized in that: include: processor; as well as A memory, configured to store executable instructions of the processor; The processor is configured to execute the edge node registration method described in any one of claims 2 to 3, or the edge node resolution method described in any one of claims 4 to 6 by executing the executable instructions.

12. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the registration method for an edge node according to any one of claims 2 to 3 or the parsing method for an edge node according to any one of claims 4 to 6 is implemented.

Images