Communication control method of cloud edge architecture, electronic equipment and computer readable medium

Abstract

The invention provides a communication control method of a cloud edge architecture, electronic equipment and a computer readable medium, which can be applied to the technical fields of computers, cloud computing, cloud services and the like. The cloud edge architecture comprises an edge server cluster and a cloud server, the edge server cluster at least comprises a first hub and a second hub, and the communication control method based on the cloud edge architecture is applied to the second hub and comprises the following steps: based on token information of the second hub, sending the first hub and the second hub to the cloud server; establishing a second communication connection between the edge server cluster and the cloud server, so that the communication connection between the edge server cluster and the cloud server is switched from the first communication connection to the second communication connection; wherein the token information of the second hub is acquired by the second hub from the cloud server by using the first communication connection; the first communication connection is established using token information of the first hub.

Description

Technical Field

[0001] The present disclosure relates to a communication control method, an electronic device, and a computer-readable medium for a cloud-edge architecture, which can be applied to technical fields such as computers, cloud computing, and cloud services. Background Art

[0002] With the rapid development of computer technology, especially cloud computing, the cloud-edge architecture is widely applied to computer room configuration, park management, and the Internet of Things field.

[0003] The cloud-edge architecture usually includes an edge server cluster composed of multiple edge servers. However, in the current prior art, the communication configuration for multiple edge servers needs to be manually implemented by users, with complex operations and low configuration efficiency. Summary of the Invention

[0004] One aspect of the present disclosure provides a communication control method for a cloud-edge architecture. The cloud-edge architecture includes an edge server cluster and a cloud server. The edge server cluster includes at least a first hub and a second hub. The communication control method based on the cloud-edge architecture is applied to the second hub and includes: establishing a second communication connection between the edge server cluster and the cloud server based on the token information of the second hub, so that the communication connection between the edge server cluster and the cloud server is switched from a first communication connection to a second communication connection; wherein, the token information of the second hub is obtained by the second hub from the cloud server using the first communication connection; and the first communication connection is established using the token information of the first hub.

[0005] According to an embodiment of the present disclosure, the method further includes: generating a token generation request when there is a third communication connection between the first hub and the second hub; sending the token generation request to the first hub via the third communication connection, so that the first hub forwards the token generation request to the cloud server via the first communication connection and receives the token information of the second hub via the first communication connection; and receiving the token information of the second hub forwarded by the first hub via the third communication connection.

[0006] According to an embodiment of the present disclosure, generating the token generation request includes: generating the token generation request according to the first certificate information and connection identifier of the second hub.

[0007] According to an embodiment of the present disclosure, the method further includes: the first communication connection and the second communication connection have the same connection identifier, so that the cloud server sends a service request to the edge server cluster via the first communication connection or the second communication connection based on the connection identifier.

[0008] According to an embodiment of the present disclosure, the connection identifier includes the cluster identifier of the edge server cluster.

[0009] According to an embodiment of the present disclosure, the method further includes: establishing a fourth communication connection between the edge device and the second hub based on the second certificate information of the edge device corresponding to the edge server cluster; wherein the second certificate information is pre-loaded in the second hub.

[0010] According to an embodiment of the present disclosure, the method further includes: in response to detecting a failure in the first communication connection between the edge server cluster and the cloud server, establishing a second communication connection between the edge server cluster and the cloud server based on the token information of the second hub; wherein the failure of the first communication connection between the edge server cluster and the cloud server is indicated by the absence of a heartbeat signal from the first hub within a predetermined duration.

[0011] Another aspect of the present disclosure also provides a communication control method for a cloud-edge architecture. The cloud-edge architecture includes an edge server cluster and a cloud server. The edge server cluster includes at least a first hub and a second hub. The method is applied to the cloud server and includes: in response to receiving a service request from a user, determining the edge server cluster to be routed; sending the service request to the edge server cluster through the communication connection with the edge server cluster; wherein the communication connection includes a first communication connection or a second communication connection, and the second communication connection is established based on the token information of the second hub, so that the communication connection between the edge server cluster and the cloud server is switched from the first communication connection to the second communication connection; the token information of the second hub is obtained from the cloud server using the first communication connection, and the first communication connection is established using the token information of the first hub.

[0012] Another aspect of the present disclosure provides an electronic device, including: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the method as described above.

[0013] Another aspect of the present disclosure provides a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause a computer to execute the method as described above.

[0014] Another aspect of the present disclosure provides a computer program, the computer program including computer-executable instructions that are used to implement the method as described in any one of the above when executed. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] To more fully understand the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which:

[0016] Figure 1 Schematically shows a system architecture diagram of a cloud-edge architecture according to an embodiment of the present disclosure;

[0017] Figure 2 Schematically shows a flowchart of a communication control method for a cloud-edge architecture according to an embodiment of the present disclosure;

[0018] Figure 3A Schematically shows an application scenario diagram for obtaining token information of a second hub according to an embodiment of the present disclosure;

[0019] Figure 3B Schematically shows an application scenario diagram for switching a communication connection between an edge server cluster and a cloud server from a first communication connection to a second communication connection according to an embodiment of the present disclosure;

[0020] Figure 4 Schematically shows an application scenario diagram for a cloud server to forward a service request under multiple edge server clusters according to an embodiment of the present disclosure;

[0021] Figure 5 Schematically shows a flowchart of a communication control method for a cloud-edge architecture applied to a cloud server according to an embodiment of the present disclosure;

[0022] Figure 6 Schematically shows a block diagram of a communication control device for a cloud-edge architecture applied to a second hub according to an embodiment of the present disclosure;

[0023] Figure 7 Schematically shows a block diagram of a communication control device for a cloud-edge architecture applied to a cloud server according to an embodiment of the present disclosure; and

[0024] Figure 8 Schematically shows a block diagram of an electronic device for a communication control method applicable to a cloud-edge architecture according to another embodiment of the present disclosure. Detailed implementation manners

[0025] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are merely exemplary and are not intended to limit the scope of the present disclosure. In addition, in the following description, descriptions of well-known structures and technologies are omitted to avoid unnecessarily confusing the concepts of the present disclosure.

[0026] The terms used herein are merely for describing specific embodiments and are not intended to limit the present disclosure. The terms "including", "comprising", etc. used herein indicate the presence of the described features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0027] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those of ordinary skill in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification, and should not be interpreted in an idealized or overly rigid manner.

[0028] Some block diagrams and / or flowcharts are shown in the accompanying drawings. It should be understood that some of the blocks or combinations thereof in the block diagrams and / or flowcharts can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when executed by the processor, these instructions can create a device for implementing the functions / operations illustrated in these block diagrams and / or flowcharts.

[0029] Therefore, the technology of the present disclosure can be implemented in the form of hardware and / or software (including firmware, microcode, etc.). Additionally, the technology of the present disclosure can take the form of a computer program product on a computer-readable medium storing instructions, which can be used by or in conjunction with an instruction execution system. In the context of the present disclosure, a computer-readable medium can be any medium capable of containing, storing, transmitting, propagating, or transporting instructions. For example, a computer-readable medium can include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, components, or propagation media. Specific examples of computer-readable media include: magnetic storage devices, such as magnetic tapes or hard disk drives (HDDs); optical storage devices, such as compact discs (CD-ROMs); memories, such as random access memories (RAMs) or flash memories; and / or wired / wireless communication links.

[0030] Currently, the communication connection between the edge server and the cloud server in the cloud-edge architecture depends on manual settings by the user. For example, the user sends a request to the edge server through the public Internet, causing the edge server to generate a token request, which usually includes security authentication information. Then, the user manually forwards the token request to the cloud server so that the cloud server can authenticate the edge server based on the forwarded token request. After the cloud server completes the authentication of the edge server, the authenticated certificate information is forwarded back to the edge server via the user. Thus, a communication connection can be established between the edge server and the cloud server. The establishment process of the above single communication connection requires the user to perform two forwards, with complex operations and low configuration efficiency. For an edge server cluster composed of multiple edge servers, the operation complexity increases exponentially, and the operation efficiency is extremely low.

[0031] In addition, in the edge server cluster scenario, the prior art usually requires users to pre-configure the communication connections between each edge server and the cloud server in advance, so that multiple communication connections coexist between the edge server cluster and the cloud server to meet requirements such as high availability and failover. However, maintaining multiple communication connections consumes additional resources, and switching strategies for switching communication connections need to be configured on both sides of the edge server cluster and the cloud server, further increasing the complexity of communication configuration operations and resource consumption in the cloud-edge architecture. For example, both the existing cloud server and the edge server cluster need to configure switching strategies: switch to communication connection 2 when communication connection 1 fails; switch to communication connection 1 when communication connection 2 fails, and save the above switching strategies in both the cloud server and the cluster. Only based on the above switching strategies can it be determined which communication connection needs to be switched to in case of a failure.

[0032] To this end, embodiments of the present disclosure provide a communication control method based on a cloud-edge architecture, which is applied to a second hub. The method includes: establishing a second communication connection between an edge server cluster and a cloud server based on the token information of the second hub, so that the communication connection between the edge server cluster and the cloud server is switched from a first communication connection to a second communication connection; wherein, the token information of the second hub is obtained by the second hub from the cloud server using the first communication connection; the first communication connection is established using the token information of the first hub. Thus, the embodiments of the present disclosure can at least solve the technical problems of complex communication configuration operations and low configuration efficiency in the cloud-edge architecture, and achieve the technical effects of reducing communication configuration operations, improving configuration efficiency, and reducing the resource efficiency of maintaining communication connections.

[0033] To facilitate understanding of the cloud-edge architecture of the present disclosure, the following will use Figure 1 as an example for illustration. Figure 1 Schematically shows a system architecture diagram of a cloud-edge architecture according to an embodiment of the present disclosure.

[0034] As Figure 1As shown in the figure, the cloud-edge architecture at least includes an edge server cluster 110 and a cloud server 121. The edge server cluster 110 may include multiple hubs, such as a first hub 111, a second hub 112,.... The hub may be any edge server in the edge server cluster, capable of receiving requests from the cloud server and forwarding the requests to edge devices, such as forwarding to edge device 131, edge device 132,.... Alternatively, the hub may also be a special edge server in the edge server, having a management function for other edge servers in the edge server cluster. It can not only forward the requests received from the cloud server to edge devices, but also forward them to other edge servers, and the other edge servers forward the requests to edge devices. In this embodiment, the first hub and the second hub may be any edge server or a special edge server in the edge server.

[0035] The edge server cluster is used to manage multiple edge devices. For example, it can forward requests from the cloud server to edge devices and process data of edge devices, such as aggregating, deduplicating, filtering, and caching data of edge devices.

[0036] Edge devices may be computer devices (such as servers), monitoring devices, sensor devices, home devices, vehicle detection devices, etc. Based on the above cloud-edge architecture communication control method, remote management, data acquisition, and / or data processing functions for the above multiple edge devices can be realized.

[0037] The cloud server is used to remotely manage multiple applications, services, or databases. For example, the cloud server may include multiple user-side servers. In the case of realizing application isolation, service isolation, or database isolation, the remote management function can be realized. The cloud server may include a portal for receiving various requests from multiple user-side servers and forwarding the various requests to the edge server cluster.

[0038] For example, a user can initiate various requests by interacting with a terminal device or a user-side server 140. For example, the user-side server 140 may include server 141, server 142,.... Then, via the communication connection between the user-side server 140 and the portal 121, the requests are forwarded to the edge server cluster 110 through the portal 121.

[0039] It should be noted that Figure 1 the numbers of hubs, servers, edge devices, etc. are all schematic. In the actual application process, there can be any number of hubs, servers, and edge devices.

[0040] Figure 2 Schematically shows a flowchart of a communication control method for a cloud-edge architecture according to an embodiment of the present disclosure.

[0041] As shown Figure 2 in FIG. 200, the communication control method of the cloud-edge architecture includes operation S210 of establishing a second communication connection between the edge server cluster and the cloud server based on the token information of the second hub, so that the communication connection between the edge server cluster and the cloud server is switched from the first communication connection to the second communication connection; wherein, the token information of the second hub is obtained by the second hub from the cloud server using the first communication connection; the first communication connection is established using the token information of the first hub.

[0042] The cloud-edge architecture of the embodiments of the present disclosure is as shown Figure 1 in FIG. 201 and will not be described herein again.

[0043] The token information can be understood as the information obtained after being security-verified by the cloud server. The token information of the first hub and the second hub are respectively the information obtained by the cloud server after security-verifying the first hub and the second hub. It can be understood that the token information can include the information for ensuring secure communication between the verification end and the verified end. For example, taking the first hub as an example, the token information of the first hub can include the certificate issued by the cloud server (verification end), the client certificate of the first hub (verified end), and other information.

[0044] For the second hub that has passed the security verification, as long as the second hub stores the token information, a second communication connection can be established between the edge server cluster and the cloud server based on the token information. For example, a websocket channel (second communication connection) can be established between the edge server cluster and the cloud server based on the token information of the second hub and mutual Transport Layer Security (mTLS). Similarly, the first communication connection can also be a websocket channel.

[0045] Although the first communication connection and the second communication connection are established using the token information of different hubs in the edge server cluster, both the first communication connection and the communication connection are communication connections between the edge server cluster and the cloud server.

[0046] In the embodiments of the present disclosure, after the second communication connection is established between the edge server cluster and the cloud server, the first communication connection is in a disconnected state, so that there is only one communication connection between the edge server cluster and the cloud server at the same time, so as to avoid problems such as the inability to perform request transmission due to communication connection conflicts or the inability to determine whether a request is transmitted through a certain communication connection.

[0047] In one embodiment, the first communication connection can be configured based on user interaction. For example, the user sends a request to the first hub via the public Internet, causing the first hub to generate a token request, which usually includes security authentication information. Then, the user manually forwards the token request to the cloud server so that the cloud server authenticates the identity of the first hub based on the forwarded token request. After the cloud server completes the authentication of the first hub, the user forwards the authenticated certificate information back to the first hub so that the first hub establishes the first communication connection based on its own token information. Thereafter, other edge servers in the edge server cluster (such as the second hub above) can automatically obtain their respective token information through the verified and trusted first communication connection, and in the case of needing to switch the communication connection, switch the communication connection between the edge server cluster and the cloud server from the first communication connection to other communication connections (such as the second communication connection above) based on their respective token information.

[0048] Alternatively, the establishment method of the first communication connection is similar to that of the second communication connection. For example, for the first hub, a first communication connection can be established between the edge server cluster and the cloud server based on the token information of the first hub, so that the communication connection between the edge server cluster and the cloud server is switched from other communication connections to the first communication connection; wherein, the token information of the first hub is obtained by the first hub from the cloud server using other communication connections; the other communication connections are established using the token information of their corresponding hubs. The other communication connection can be the second communication connection above or other established communication connections between the edge server cluster and the cloud server.

[0049] In the embodiments of the present disclosure, since the token information of the second hub is obtained by the second hub from the cloud server using the first communication connection, the second communication connection can be established based on the token information of the second hub without manual configuration by the user. The operation of establishing the communication connection is simple and the complexity is low, improving the establishment efficiency of the communication connection. Especially in the edge server cluster scenario, multiple hubs can obtain their respective token information through an established communication connection, simplifying the operation and complexity of establishing multiple communication connections in the edge server cluster. In addition, since the edge server cluster and the cloud server communicate only through the first communication connection or the second communication connection, there is no need to consume other resources to maintain the survival of multiple communication connections, reducing the amount of consumed resources.

[0050] In a specific embodiment, the edge device may be a computer device such as a server or a gateway, and this cloud-edge architecture can be used in server management scenarios. In server management scenarios, a large number of servers and gateway devices are usually deployed to meet various requirements on the cloud server side, such as online data processing, data Q&A, data search, etc. based on artificial intelligence technology. In this scenario, to ensure that the servers can provide services in a timely and uninterrupted manner, multiple hubs are usually deployed in the edge server cluster to meet high concurrency and high availability (HA), and switching between multiple hubs or switching between multiple communication connections within the edge server cluster is also very frequent. It can be seen that in the server management scenario with a large number of edge devices and a large number of hubs, manually implementing the communication connection configuration of a large number of hubs not only has low efficiency and is prone to errors, but also easily affects the user experience on the cloud server side due to the long configuration time.

[0051] Therefore, by adopting the embodiments of the present disclosure, through an established first communication connection in the edge server cluster, the token information of the second hub in the edge server cluster can be obtained. Thus, without manual configuration by the user, the second communication connection between the edge server cluster and the cloud server can be automatically established based on the token information of the second hub, greatly improving the efficiency of establishing the communication connection between the edge server cluster and the cloud server and avoiding affecting the user experience on the cloud server side.

[0052] It should be noted that in the embodiments of the present disclosure, the first communication connection can be any established communication connection in the edge server cluster, and the second hub can be any other hub except the first hub related to the first communication connection, so as to automatically establish other communication connections through an established communication connection.

[0053] According to the embodiments of the present disclosure, the method further includes: generating a token generation request when there is a third communication connection between the first hub and the second hub; sending the token generation request to the first hub via the third communication connection, so that the first hub forwards the token generation request to the cloud server via the first communication connection and receives the token information of the second hub via the first communication connection; and receiving the token information of the second hub forwarded by the first hub via the third communication connection.

[0054] The token generation request can be a request for verifying the identity of the second hub. For example, in one embodiment, the token generation request can be a client certificate signing request (Certificate Signing Request) of the second hub, so that the cloud server can verify the identity of the second hub.

[0055] According to an embodiment of the present disclosure, communication connections may exist between multiple hubs in an edge server cluster to ensure communication between the multiple hubs. For example, the edge server cluster may include communication connections between each pair or communication connections in the form of broadcasts, etc. For ease of understanding, hereinafter, the communication connection between hubs in the edge server cluster is referred to as the third communication connection to distinguish it from the first communication connection / second communication connection between the edge server cluster and the cloud server.

[0056] The third communication connection may have other functions, such as for status synchronization. Status synchronization includes, but is not limited to: detecting whether the first hub / second hub is in an online state, performing data sharing, traffic isolation, etc.; or, the third communication connection may also be established based on multiple communication protocols. As long as there is a third communication connection between the first hub and the second hub, the above two hubs can communicate with each other.

[0057] According to an embodiment of the present disclosure, the third communication connection between the first hub and the second hub is usually established during the construction of the edge server cluster. For example, when the first hub is the master node in the edge server cluster, if a new first hub is added to the edge server cluster, to ensure the state uniformity among multiple hubs, the first hub and the second hub establish a third communication connection.

[0058] In an embodiment, if the communication between the edge server cluster and the cloud server is the first communication connection and there is a third communication connection between the first hub and the second hub, the first hub may actively call the interface of the second hub and transmit data for generating a token generation request through the third communication connection so that the second hub generates a token generation request. For example, an http message may be transmitted through the third communication connection so that the second hub generates a token generation request based on the http message. Alternatively, the second hub may also generate the above token generation request when detecting the existence of the third communication connection. The first hub may directly forward the token generation request from the second hub to the cloud server through the first communication connection for security verification by the cloud server; and forward the token information generated by the cloud server to the second hub.

[0059] In an embodiment of the present disclosure, by means of the established trusted first communication connection and the existing third communication connection between multiple hubs in the edge server cluster, indirect communication between the second hub and the cloud server can be achieved, such that the process of establishing the second communication connection does not require manual operation by the user, thereby improving the efficiency of establishing the communication connection.

[0060] In another embodiment, for the above forwarding process, the first hub may encrypt the token generation information before forwarding it. The cloud server first decrypts the encrypted token generation request based on the decryption parameters related to the first hub, and then verifies the identity of the second hub and generates the token information. Similarly, the cloud server may also encrypt the token information and transmit the encrypted token information to the first hub. The first hub decrypts it and forwards the decrypted token information to the second hub. In the above process, not only are the requests and information forwarded through the trusted first communication connection, but also the first hub performs encryption / decryption processing on the forwarded information to further improve the security of the to-be-established second communication connection.

[0061] According to an embodiment of the present disclosure, if the first hub or the second hub is in an offline state due to a failure or network reasons, etc., the third communication connection is disconnected, that is, the third communication connection does not exist. At this time, it is possible to wait again for the first hub or the second hub to resume the online state and resume the third communication connection. Alternatively, in the case where the first hub is offline, the second hub can also obtain the token information through the third communication connection with other hubs. The obtaining method is similar to the method through the first communication connection and will not be elaborated here.

[0062] According to an embodiment of the present disclosure, generating the token generation request includes: generating the token generation request according to the first certificate information and the connection identifier of the second hub.

[0063] The connection identifier is used to characterize the identifier of the communication connection between the edge server cluster and the cloud server. For example, the connection identifier may correspond to the edge server cluster.

[0064] The first certificate information may be the certificate information for verifying the identity of the second hub, such as the client certificate information (Client Certificate) of the second hub. For example, the first certificate information may include information such as the identity information of the second hub, the certificate issuing authority, the certificate serial number, and the validity period.

[0065] When generating the token generation request, the second hub may construct the first certificate information and the connection identifier as the message information in the request to generate a token generation request that can be used to verify the identity of the second hub.

[0066] In an embodiment of the present disclosure, although both the first communication connection and the second communication connection are communication connections between the edge server cluster and the cloud server, during the verification phase of establishing the second communication connection, it is still necessary to identify the established communication connection. By generating a token generation request based on the first certificate information and the connection identifier, the cloud server can identify the edge server cluster based on the connection identifier in the token generation request, so as to prevent the cloud server from confusing multiple edge server clusters and causing abnormal communication between the cloud server and the edge server cluster.

[0067] Figure 3A FIG. schematically shows an application scenario diagram for obtaining the token information of the second hub according to an embodiment of the present disclosure. Figure 3B FIG. schematically shows an application scenario diagram for switching the communication connection between the edge server cluster and the cloud server from the first communication connection to the second communication connection according to an embodiment of the present disclosure.

[0068] As Figure 3A shown, the first hub 111 invokes the interface of the second hub 112 through the third communication connection, so that the second hub 112 generates a token generation request, and the token generation request may include the first certificate information and the connection identifier of the second hub; the token generation request is forwarded to the first hub 111 through the third connection channel, and the first hub 111 then forwards the token generation request to the cloud server 121 through the first communication connection. The cloud server authenticates the second hub according to the first certificate information in the token generation request, and after the authentication passes, generates a digital certificate, binds the digital certificate with the token applied by the second hub, and jointly uses them as the token information generated by the cloud server. Subsequently, the cloud server can return the token information to the first hub 111 through the first communication connection. The first hub 111 feeds back the token information to the second hub 112 through the third communication connection again.

[0069] In the case where it is necessary to switch the communication connection between the edge server cluster and the cloud server, since the second hub 112 already includes the token information for establishing the communication connection. Therefore, the second communication connection can be directly established based on the token information of the second hub 112, and the first communication connection can be disconnected. As Figure 3B shown, the communication connection between the edge server cluster and the cloud server 121 is switched from the first communication connection established based on the token information of the first hub 111 to the second communication connection established based on the token information of the second hub 112.

[0070] In one embodiment, for multiple hubs in the same edge server cluster, the connection identifiers of the communication connections established based on their respective token information may be different, which is used to distinguish the hubs in the same edge server cluster that establish communication connections with the cloud server.

[0071] In another embodiment, for multiple hubs in the same edge server cluster, the connection identifiers of the communication connections established based on their respective token information can be the same.

[0072] Taking the first communication connection and the second communication connection as examples, the method further includes: the first communication connection and the second communication connection have the same connection identifier, so that the cloud server can send a service request to the edge server cluster through the first communication connection or the second communication connection based on the connection identifier.

[0073] In the embodiments of the present disclosure, since there is only one communication connection between the edge server cluster and the cloud server at the same time, even if the connection identifiers of multiple hubs are the same, there will be no situation of multiple communication connection conflicts.

[0074] In addition, since the first communication connection and the second communication connection have the same connection identifier, and only one of the first communication connection and the second communication connection exists at the same time, neither the cloud server nor the edge server cluster needs to configure a switching configuration for switching between the first communication connection and the second communication connection. As long as there is a certain first communication connection or the second communication connection between the edge server cluster and the cloud server, the cloud server can forward the user's service request to the edge server cluster through this communication connection.

[0075] The service request can include various requests, including requests related to data, such as data invocation, data calculation, data integration, etc.; or requests related to services, such as storage, cloud computing, virtual machines, etc.; or requests related to instant messaging, e-commerce services, search, artificial intelligence, etc.

[0076] In the embodiments of the present disclosure, by configuring the same connection identifier for the first communication connection and the second communication connection, while ensuring that there are no multiple communication connection conflicts, the cloud server does not need to configure a switching configuration for switching between the first communication connection and the second communication connection, thereby further simplifying the communication configuration operation on the cloud server side.

[0077] In a specific embodiment, the connection identifier includes the cluster identifier of the edge server cluster.

[0078] Since the cloud server can have communication connections with multiple edge server clusters, the multiple communication connections between a certain edge server cluster and the cloud server can all use the cluster identifier of the edge server cluster as the connection identifier, enabling the cloud server to quickly distinguish multiple edge server clusters based on this connection identifier.

[0079] Figure 4 Schematically shows an application scenario diagram of a cloud server forwarding a service request under multiple edge server clusters according to an embodiment of the present disclosure. AsFigure 4 As shown, the cloud server 401 can interact with edge server clusters 410, 420..., and forward the service requests corresponding to each edge server cluster to the corresponding edge server cluster.

[0080] For example, the edge server cluster 410 may include hubs 411, 412..., and the communication connection between the cloud server 401 and the edge server cluster 410 can be established based on the token information of the hubs 411, 412..., and the connection identifiers of the above multiple communication connections can all be "cluster ID: 8888-8888". For example, the first communication connection can be established based on the token information of the hub 411 (i.e., Hub-1). At this time, the connection identifier of the first communication connection is cluster ID: 8888-8888, and the encrypted transmission of the request is carried out using the portal root certificate CA and the Hub-1 client certificate.

[0081] Similarly, the edge server cluster 420 includes hubs 421, 422..., and multiple communication connections between the edge server cluster 420 and the cloud server 420 are established based on the token information of the hubs 421, 422..., and the connection identifiers can all be "cluster ID: 6666-6666"... For example, the second communication connection can be established based on the token information of the hub 422 (i.e., Hub-2). At this time, the connection identifier of the second communication connection is cluster ID: 6666-6666, and the encrypted transmission of the request is carried out using the portal root certificate CA and the Hub-1 client certificate.

[0082] For the communication connection switching scenario, taking the edge server cluster 410 including the first communication connection and the second communication connection as an example, on the edge server cluster side, the first communication connection can be switched to the second communication connection. Since the connection identifiers of the first communication connection and the second communication connection are both "cluster ID: 8888-8888", therefore, the switching between communication connections is invisible to the cloud server side, and there is no need to set the switching configuration in case of communication connection failure. After switching, the connection identifier of the second communication connection is still cluster ID: 8888-8888, and the encrypted transmission of the request is carried out using the portal root certificate CA and the client certificate of the hub 412. In addition, on the cloud server side, when receiving a service request from the user-side server for forwarding to the edge server cluster 410, it can directly determine the communication connection of the edge server cluster based on the cluster ID of the edge server cluster 410, that is, the communication connection with the connection identifier of "cluster ID: 8888-8888", thereby being able to quickly forward the service request to the edge server cluster 410.

[0083] According to an embodiment of the present disclosure, the method further includes: establishing a fourth communication connection between the edge device and the second hub based on the second certificate information of the edge device corresponding to the edge server cluster; wherein the second certificate information is pre-loaded in the second hub.

[0084] In an embodiment of the present disclosure, each hub in the edge server cluster can forward a service request to the edge device through the communication connection between the hub and the edge device. To distinguish from the first, second, and third communication connections above, the communication connection between the edge device and any hub in the edge server cluster is referred to as the fourth communication connection.

[0085] Similar to establishing the second communication connection, when establishing the fourth communication connection, the second hub needs to verify the identity of the edge device. The second certificate information can be the certificate information used to verify the identity of the edge device. For example, it can be the root certificate information of the edge device. The second certificate information may include: information such as the identity information of the edge device, the certificate issuing authority, the certificate serial number, the certificate usage, and the validity period.

[0086] Since the two cannot communicate before establishing the fourth communication connection between the second hub and the edge device, the second certificate information of the trusted edge device can be pre-loaded in the second hub, so that the establishment of the fourth communication connection can be achieved without interaction between the second hub and the edge device, further simplifying the establishment process of the communication connection.

[0087] It can be understood that if the second certificate information of a certain edge device is pre-loaded in the second hub, it indicates that the edge device is a trusted edge device, and the second hub can forward the service request of the cloud server to the edge device; if not loaded, it indicates that the second hub cannot forward the service request to the edge device.

[0088] In some embodiments, pre-loading the second certificate information is relative to establishing the fourth communication connection. For example, in the case where the second hub joins the edge server cluster, the second certificate information of each of the pre-configured multiple edge devices can be loaded into the second hub. For example, the first hub can call the corresponding configuration interface to load the second certificate information into the second hub. Or, the second hub itself can carry the second certificate information of the trusted edge device. For example, the manufacturer of the second hub can pre-load the second certificate information. Thus, when the second hub joins the edge server cluster, it can carry the second certificate information.

[0089] Similar to the second hub, any hub in the edge server cluster can pre-load the second certificate information of the edge devices it manages. The pre-loading operation is as described above and will not be elaborated here.

[0090] Based on the description of operation S210, there is only one communication connection between the edge server cluster and the cloud server at the same time, such as the first communication connection or the second communication connection; if it is necessary to switch the communication connection, the first communication connection can be switched to the second communication connection.

[0091] In some embodiments, the switch from the first communication connection to the second communication connection can be actively controlled by the edge server cluster. For example, based on a pre-configured switching strategy, the first communication connection is actively disconnected and the second communication connection is established. For example, the switching strategy can be: the first communication connection fluctuates, the bandwidth or traffic of the first communication connection is limited, the packet loss rate of the first communication connection exceeds a predetermined threshold, and / or the latency duration of the first communication connection exceeds a duration threshold. The first hub can actively disconnect the first communication connection, and the second hub can establish the second communication connection based on the token information and switch to the second communication connection to achieve the switching of the communication connection and achieve the effect of meeting the real-time and accuracy requirements of cloud-edge architecture communication.

[0092] It should be noted that when the first communication connection and the second communication connection have the same connection identifier, the above switching strategy can be configured only in the edge server cluster, and the cloud server side is unaware of the switch and does not need to configure the switching strategy, which can at least reduce the configuration operation on the cloud server side compared with the prior art.

[0093] In some other embodiments, the switch from the first communication connection to the second communication connection can be passively controlled, such as when the first communication connection fails.

[0094] In a specific embodiment, the communication control method for the cloud-edge architecture further includes: in response to detecting that the first communication connection between the edge server cluster and the cloud server fails, based on the token information of the second hub, establishing a second communication connection between the edge server cluster and the cloud server; where the failure of the first communication connection is indicated by the absence of a heartbeat signal from the first hub within a predetermined duration.

[0095] The failure of the first communication connection includes: the failure of the first hub and / or the first hub being in an offline state, and both of the above failures will cause the first communication connection to be unavailable, and communication cannot be carried out between the edge server cluster and the cloud server.

[0096] For example, status synchronization can be performed between the first hub and the second hub through a third communication connection, such as determining whether the other party is online by mutually transmitting heartbeat information. Thus, if the second hub does not receive a heartbeat signal from the first hub within a predetermined duration, it can be determined that there is a fault in the first communication connection, and the above operation S210 can be executed.

[0097] In an embodiment of the present disclosure, since there is only one communication connection between the edge server cluster and the cloud server at the same time, when the first communication connection fails, the second communication connection can be directly established based on the token information of the second hub obtained through the first communication connection, thereby realizing the switching of the communication connection in the fault scenario, without manually establishing the second communication connection and without performing fault switching configuration on the cloud server, which simplifies the operation and complexity of establishing multiple communication connections in the edge server cluster.

[0098] In addition, for the scenario of the first communication connection and the second communication connection using the same connection identifier, when switching the first communication connection to the second communication connection, the information about the communication connection on the cloud server side, such as the connection identifier, does not change, thereby realizing seamless fault switching on the cloud server side. For the scenario of using the cluster identifier of the edge server cluster as the connection identifier, the cloud server side can not only realize seamless communication connection fault switching, but also quickly locate the edge server cluster based on the cluster identifier and quickly forward the service request to the edge server cluster.

[0099] Similarly, if the current communication connection between the edge server cluster and the cloud server is the second communication connection or other communication connections, the first hub, in response to detecting a fault in the second communication connection or other communication connections between the edge server cluster and the cloud server, establishes the first communication connection based on the token information of the first hub.

[0100] Another aspect of the present disclosure also provides a cloud-edge architecture including an edge server cluster and a cloud server, and the edge server cluster at least includes a first hub and a second hub. Figure 5 Schematically shows a flowchart of a communication control method for a cloud-edge architecture applied to a cloud server according to an embodiment of the present disclosure. As Figure 5 shown, Embodiment 500 includes operations S510 - S520.

[0101] In operation S510, in response to receiving a service request from a user, determine the edge server cluster to be routed.

[0102] In operation S520, a service request is sent to the edge server cluster through a communication connection with the edge server cluster; wherein, the communication connection includes a first communication connection or a second communication connection, and the second communication connection is established based on the token information of the second hub, so that the communication connection between the edge server cluster and the cloud server is switched from the first communication connection to the second communication connection; the token information of the second hub is obtained from the cloud server using the first communication connection, and the first communication connection is established using the token information of the first hub.

[0103] The forwarding of the service request between the cloud server and the edge server cluster through the first communication connection or the second communication connection can be determined by the edge server cluster. For example, it can be actively switched as shown above, or switched in a failure scenario. Whether using the first communication connection or the second communication connection, as long as there is a communication connection between the edge server cluster and the cloud server, the cloud server can forward the service request to the edge server cluster through this communication connection, and then forward it to the corresponding edge device through the edge server cluster.

[0104] Similar to the above, the service request can include various requests, including requests related to data, requests related to services, requests related to instant messaging, e-commerce services, search, artificial intelligence, etc. The specific operations for establishing the communication connection on the cloud server side are similar to operation S210 above and will not be elaborated here.

[0105] The user can remotely log in to the systems or applications for each edge device through the cloud server, and generate service requests through the systems or applications. The systems or applications for each edge device can be implemented by the user-side server in the cloud server. The cluster identifier of the edge server cluster for managing the edge device is included in the message of the service request. Thus, the cloud server can analyze the service request to determine the edge server cluster to be routed, and forward the service request to the edge server cluster through the communication connection.

[0106] In the embodiments of the present disclosure, since there is only a first communication connection or a second communication connection between the edge server cluster and the cloud server, therefore, the cloud server side does not need to consume resources to maintain the survival of multiple communication connections, and does not need to configure a switching strategy for switching communication connections, and can convey requests through each currently unique existing communication connection, simplifying the configuration operations and complexity on the cloud server side.

[0107] Figure 6 Schematically shows a block diagram of a communication control device for a cloud-edge architecture applied to a second hub according to an embodiment of the present disclosure.

[0108] As Figure 6As shown, the communication control device 600 of the cloud-edge architecture applied to the second hub includes a communication connection establishment module 610, configured to establish a second communication connection between the edge server cluster and the cloud server based on the token information of the second hub, so that the communication connection between the edge server cluster and the cloud server is switched from the first communication connection to the second communication connection; wherein, the token information of the second hub is obtained by the second hub from the cloud server using the first communication connection; the first communication connection is established using the token information of the first hub.

[0109] According to an embodiment of the present disclosure, the communication control device 600 of the cloud-edge architecture applied to the second hub further includes: a generation module, configured to generate a token generation request when there is a third communication connection between the first hub and the second hub.

[0110] A forwarding module, configured to send the token generation request to the first hub via the third communication connection, so that the first hub forwards the token generation request to the cloud server through the first communication connection, and receives the token information of the second hub through the first communication connection

[0111] A receiving module, configured to receive the token information of the second hub forwarded by the first hub via the third communication connection.

[0112] According to an embodiment of the present disclosure, the generation module further includes a generation sub-module, configured to generate a token generation request according to the first certificate information and connection identifier of the second hub.

[0113] According to an embodiment of the present disclosure, the first communication connection and the second communication connection have the same connection identifier, so that the cloud server sends a service request to the edge server cluster through the first communication connection or the second communication connection based on the connection identifier.

[0114] According to an embodiment of the present disclosure, the connection identifier includes the cluster identifier of the edge server cluster.

[0115] According to an embodiment of the present disclosure, the communication control device 600 of the cloud-edge architecture applied to the second hub further includes: an establishment module, configured to establish a fourth communication connection between the edge device and the second hub based on the second certificate information of the edge device corresponding to the edge server cluster; wherein, the second certificate information is pre-loaded in the second hub.

[0116] According to an embodiment of the present disclosure, the communication control device 600 of the cloud-edge architecture applied to the second hub further includes a failover module, configured to establish a second communication connection between the edge server cluster and the cloud server based on the token information of the second hub in response to detecting a failure in the first communication connection between the edge server cluster and the cloud server; wherein, the absence of a heartbeat signal received from the first hub within a predetermined duration indicates a failure in the first communication connection between the edge server cluster and the cloud server.

[0117] Figure 7 Schematically shows a block diagram of a communication control device of a cloud-edge architecture applied to a cloud server according to an embodiment of the present disclosure. As Figure 7 shown, the communication control device 700 of the cloud-edge architecture applied to the cloud server includes: a determination module, configured to determine an edge server cluster to be routed in response to receiving a service request from a user; a forwarding module, configured to send the service request to the edge server cluster through a communication connection with the edge server cluster; wherein, the communication connection includes a first communication connection or a second communication connection, and the second communication connection is established based on the token information of the second hub, so that the communication connection between the edge server cluster and the cloud server is switched from the first communication connection to the second communication connection; the token information of the second hub is obtained from the cloud server using the first communication connection, and the first communication connection is established using the token information of the first hub.

[0118] According to an embodiment of the present disclosure, any plurality of modules, sub-modules, units, and sub-units, or at least part of the functions of any of them can be implemented in one module. Any one or more of the modules, sub-modules, units, and sub-units according to an embodiment of the present disclosure can be split into multiple modules for implementation. Any one or more of the modules, sub-modules, units, and sub-units according to an embodiment of the present disclosure can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on chip, a system on substrate, a system on package, an application specific integrated circuit (ASIC), or can be implemented by any other reasonable way of integrating or packaging circuits in hardware or firmware, or implemented in any one of the three implementation ways of software, hardware, and firmware, or in an appropriate combination of any several of them. Alternatively, one or more of the modules, sub-modules, units, and sub-units according to an embodiment of the present disclosure can be at least partially implemented as a computer program module, which can execute corresponding functions when the computer program module is run.

[0119] It should be noted that the device part in the embodiments of the present disclosure corresponds to the method part in the embodiments of the present disclosure. For the description of the device part, please refer to the method part specifically, and details are not described herein again.

[0120] Figure 8 A block diagram of an electronic device for a communication control method applicable to a cloud-edge architecture according to another embodiment of the present disclosure is schematically shown. Figure 8 The electronic device shown is merely an example and should not impose any limitations on the functions and usage scope of the embodiments of the present disclosure.

[0121] As Figure 8 shown, an electronic device 800 according to an embodiment of the present disclosure includes a processor 801, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 802 or a program loaded from a storage section 808 into a random access memory (RAM) 803. The processor 801 may include, for example, a general microprocessor (such as a CPU), an instruction set processor, and / or a related chipset, and / or a dedicated microprocessor (such as an application-specific integrated circuit (ASIC)), and so on. The processor 801 may also include on-board memory for caching purposes. The processor 801 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0122] In the RAM 803, various programs and data required for the operation of the electronic device 800 are stored. The processor 801, the ROM 802, and the RAM 803 are connected to each other via a bus 804. The processor 801 performs various operations of the method flow according to an embodiment of the present disclosure by executing the program in the ROM 802 and / or the RAM 803. It should be noted that the program may also be stored in one or more memories other than the ROM 802 and the RAM 803. The processor 801 may also perform various operations of the method flow according to an embodiment of the present disclosure by executing the program stored in the one or more memories.

[0123] According to an embodiment of the present disclosure, the electronic device 800 may further include an input / output (I / O) interface 805, and the input / output (I / O) interface 805 is also connected to the bus 804. The electronic device 800 may further include one or more of the following components connected to the input / output (I / O) interface 805: an input section 806 including a keyboard, a mouse, etc.; an output section 807 including, for example, a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 808 including a hard disk, etc.; and a communication section 809 including a network interface card such as a LAN card, a modem, etc. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to the input / output (I / O) interface 805 as needed. A removable medium 811, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 810 as needed so that a computer program read from it can be installed into the storage section 808 as needed.

[0124] According to an embodiment of the present disclosure, the method flow according to the embodiment of the present disclosure may be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a computer-readable storage medium, and the computer program includes program code for executing the method shown in the flowchart. In such an embodiment, the computer program may be downloaded and installed from a network through a communication part 809, and / or installed from a removable medium 811. When the computer program is executed by a processor 801, the above functions defined in the system according to the embodiment of the present disclosure are executed. According to an embodiment of the present disclosure, the above-described system, device, apparatus, module, unit, etc. may be implemented by computer program modules.

[0125] The present disclosure also provides a computer-readable storage medium, which may be included in the device / device / system described in the above embodiment; or may exist separately without being assembled into the device / device / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0126] According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium. For example, it may include but is not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above. In the present disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program, and the program may be used by or in combination with an instruction execution system, device, or device.

[0127] For example, according to an embodiment of the present disclosure, the computer-readable storage medium may include the above-described ROM 802 and / or RAM 803 and / or one or more memories other than ROM 802 and RAM 803.

[0128] An embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program includes program code for executing the method provided by the embodiment of the present disclosure. When the computer program product runs on an electronic device, the program code is used to cause the electronic device to implement the method provided by the embodiment of the present disclosure.

[0129] When the computer program is executed by the processor 801, the above functions defined in the system / apparatus of the embodiments of the present disclosure are executed. According to the embodiments of the present disclosure, the systems, apparatuses, modules, units, etc. described above can be implemented by computer program modules.

[0130] In one embodiment, the computer program can rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program can also be transmitted and distributed in the form of signals on a network medium, and be downloaded and installed through the communication part 809, and / or be installed from the removable medium 811. The program code included in the computer program can be transmitted by any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0131] According to the embodiments of the present disclosure, the program code for executing the computer program provided by the embodiments of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level procedures and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages include but are not limited to, such as Java, C++, python, the "C" language, or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device can 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 can be connected to an external computing device (for example, by using an Internet service provider to connect through the Internet).

[0132] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagram may represent a module, a segment of a program, or a portion of code that contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions noted in the blocks may occur in a different order than noted in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, or they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram or flowchart, and combinations of blocks in the block diagram or flowchart, can be implemented by a dedicated hardware-based system that performs the specified functions or operations, or by a combination of dedicated hardware and computer instructions. Those skilled in the art will appreciate that the features described in the various embodiments of the present disclosure can be combined and / or combined in various ways, even if such combinations or combinations are not explicitly described in the present disclosure. In particular, without departing from the spirit and teachings of the present disclosure, the features described in the various embodiments of the present disclosure can be combined and / or combined in various ways. All such combinations and / or combinations fall within the scope of the present disclosure.

[0133] The embodiments of the present disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments have been described separately above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. Without departing from the scope of the present disclosure, those skilled in the art can make various substitutions and modifications, and all such substitutions and modifications should fall within the scope of the present disclosure.

Claims

1. A communication control method for a cloud-edge architecture, the cloud-edge architecture including an edge server cluster and a cloud server, the edge server cluster at least including a first hub and a second hub, the method being applied to the second hub, the method comprising: Based on the token information of the second hub, establish a second communication connection between the edge server cluster and the cloud server, so that the communication connection between the edge server cluster and the cloud server is switched from a first communication connection to the second communication connection; Wherein, the token information of the second hub is obtained by the second hub from the cloud server using the first communication connection; the first communication connection is established using the token information of the first hub.

2. The method according to claim 1, further comprising: Generate a token generation request when there is a third communication connection between the first hub and the second hub; Via the third communication connection, send the token generation request to the first hub, so that the first hub forwards the token generation request to the cloud server via the first communication connection, and receives the token information of the second hub via the first communication connection; And Via the third communication connection, receive the token information of the second hub forwarded by the first hub.

3. The method according to claim 1, wherein generating the token generation request comprises: Generate the token generation request according to the first certificate information and connection identifier of the second hub.

4. The method according to claim 3, further comprising: The first communication connection and the second communication connection have the same connection identifier, so that the cloud server sends a service request to the edge server cluster via the first communication connection or the second communication connection based on the connection identifier.

5. The method according to claim 4, wherein the connection identifier includes the cluster identifier of the edge server cluster.

6. The method according to any one of claims 1 to 5, further comprising: Based on the second certificate information of the edge device corresponding to the edge server cluster, establish a fourth communication connection between the edge device and the second hub; Wherein, the second certificate information is pre-loaded in the second hub.

7. The method according to any one of claims 1 to 5, further comprising: In response to detecting that there is a fault in the first communication connection between the edge server cluster and the cloud server, based on the token information of the second hub, establish a second communication connection between the edge server cluster and the cloud server; Wherein, the fact that no heartbeat signal is received from the first hub within a predetermined time indicates that there is a fault in the first communication connection between the edge server cluster and the cloud server.

8. A communication control method for a cloud-edge architecture, the cloud-edge architecture including an edge server cluster and a cloud server, the edge server cluster at least including a first hub and a second hub, the method being applied to the cloud server, the method comprising: Upon receiving a service request from a user, determine an edge server cluster to be routed; Send the service request to the edge server cluster through a communication connection with the edge server cluster; Wherein, the communication connection includes a first communication connection or the second communication connection, and the second communication connection is established based on the token information of the second hub, so that the communication connection between the edge server cluster and the cloud server is switched from the first communication connection to the second communication connection; the token information of the second hub is obtained from the cloud server using the first communication connection, and the first communication connection is established using the token information of the first hub.

9. An electronic device, comprising: At least one processor; And A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the method according to any one of claims 1 to 8.

10. A non-transitory computer-readable storage medium storing computer instructions, wherein, The computer instructions are used to cause the computer to execute the method according to claims 1 to 8.

Images