Cloud edge cooperation system and server

Abstract

The invention relates to the technical field of cloud computing, and provides a cloud edge cooperation system and a server, which can request to a server without modifying a request path or parameter of a client, and realize non-intrusive synchronous routing. The method comprises the following steps: a central cloud side client sends a synchronous routing request to an application service; the application service generates a unique identifier associated with the synchronous routing request, and deploys a central cloud side forwarding service; the central cloud side gateway is configured to a first-class route of the target edge cloud side gateway and is associated with the unique identifier; the central cloud side client sends access information to the central cloud side forwarding service; the center cloud side forwarding service adds a unique identifier on the access information and then sends the access information to a center cloud side gateway; and the central cloud side gateway sends the access information to a target edge cloud side gateway according to the determined one-class route associated with the unique identifier added in the access information, so that the target edge cloud side gateway sends the access information to a target edge cloud side server.

Description

Technical Field

[0001] The present application relates to the field of cloud computing technology, and in particular to a cloud-edge collaboration system, a central cloud-side server, and an edge cloud-side server. Background Art

[0002] Cloud-edge collaboration refers to the collaborative work between the central cloud and the edge cloud, achieving optimal utilization of system resources through data sharing and task allocation. In the application interaction of the cloud-edge collaboration system, a synchronous route can be opened between the central cloud and the edge cloud. In this way, clients on the central cloud and edge cloud sides can access the server on the edge cloud or central cloud side through the opened synchronous route (in a production environment, the network between the central cloud and the edge cloud is restricted, and generally only the gateway on the central cloud or edge cloud side can be accessed). Current gateways generally locate different target services or target clusters through the access request path or access request parameters. If the access request path or access request parameters cannot locate different target services or target clusters, the client needs to modify the original access request path or access request parameters. However, for some clients with fixed access request paths or access request parameters, modifying the access request path or access request parameters is difficult to achieve. Summary of the Invention

[0003] Based on this, it is necessary to provide a cloud-edge collaboration system, a central cloud-side server and an edge cloud-side server to address the above technical problems.

[0004] The present application provides a cloud-edge collaboration system, which includes:

[0005] The central cloud client sends a synchronous routing request to the application service, pointing to the target edge cloud and the target edge cloud server.

[0006] The application service generates a unique identifier associated with the synchronization routing request and deploys a central cloud side forwarding service on the central cloud side;

[0007] The central cloud-side gateway configures a type of route to the target edge cloud-side gateway and associates it with the unique identifier;

[0008] The central cloud side client sends access information to the central cloud side forwarding service;

[0009] The central cloud side forwarding service adds the unique identifier to the access information and sends it to the central cloud side gateway;

[0010] The central cloud-side gateway determines a type of routing associated with the unique identifier added to the access information, and sends the access information to the target edge cloud-side gateway based on the type of routing, so that the target edge cloud-side gateway sends the access information to the target edge cloud-side service end.

[0011] In one embodiment, the target edge cloud side gateway is configured with a second type of routing to the target edge cloud side server;

[0012] The target edge cloud side gateway sends the access information to the target edge cloud side server according to the second type of routing to the target edge cloud side server.

[0013] In one embodiment, the target edge cloud-side gateway associates the second type of route with the unique identifier;

[0014] The target edge cloud side gateway determines a second type of routing associated with the unique identifier added to the access information, and sends the access information to the target edge cloud side server according to the second type of routing.

[0015] In one embodiment, the unique identifier is obtained by performing a hash operation based on relevant information about the target edge cloud side and the target edge cloud side service end.

[0016] The present application provides a cloud-edge collaboration system, which includes:

[0017] The edge cloud client sends a synchronous routing request to the target central cloud and the target central cloud server to the application service;

[0018] The application service generates a unique identifier associated with the synchronization routing request and deploys an edge cloud side forwarding service on the edge cloud side;

[0019] The edge cloud side gateway configures a class of routing to the target central edge cloud side gateway and associates it with the unique identifier;

[0020] The edge cloud side client sends access information to the edge cloud side forwarding service;

[0021] The edge cloud side forwarding service adds the unique identifier to the access information and sends it to the edge cloud side gateway;

[0022] The edge cloud side gateway determines a type of routing associated with the unique identifier added to the access information, and sends the access information to the target center cloud side gateway based on the type of routing, so that the target center cloud side gateway sends the access information to the target center cloud side service end.

[0023] In one embodiment,

[0024] The target center cloud side gateway configures a second type of routing to the target center cloud side server;

[0025] The target center cloud side gateway sends the access information to the target center cloud side server according to the second type of routing to the target center cloud side server.

[0026] In one embodiment,

[0027] The target center cloud-side gateway associates the second type of route with the unique identifier;

[0028] The target center cloud-side gateway determines a second type of routing associated with the unique identifier added to the access information, and sends the access information to the target center cloud-side service end according to the second type of routing.

[0029] In one embodiment, the unique identifier is obtained by performing a hash operation based on relevant information about the target central cloud side and the target central cloud side service end.

[0030] The present application provides a central cloud-side server, which includes a central cloud-side gateway of the cloud-edge collaboration system as described in any of the above embodiments; the central cloud-side server includes a central cloud-side client of the cloud-edge collaboration system as described in any of the above embodiments, or a central cloud-side service end of the cloud-edge collaboration system as described in any of the above embodiments.

[0031] The present application provides an edge cloud-side server, which includes an edge cloud-side gateway of the cloud-edge collaboration system as described in any of the above embodiments; the edge cloud-side server includes an edge cloud-side client of the cloud-edge collaboration system as described in any of the above embodiments, or an edge cloud-side service end of the cloud-edge collaboration system as described in any of the above embodiments.

[0032] In the solution provided by this application, the central cloud client sends a synchronous routing request directed to the target edge cloud and the target edge cloud server to the application service; the application service generates a unique identifier associated with the synchronous routing request and deploys a central cloud forwarding service on the central cloud; the central cloud gateway configures a class of routing to the target edge cloud gateway and associates it with the unique identifier; the central cloud client sends access information to the central cloud forwarding service; the central cloud forwarding service adds a unique identifier to the access information and sends it to the central cloud gateway; the central cloud gateway determines the class of routing associated with the unique identifier added to the access information and sends the access information to the target edge cloud gateway based on the class of routing, so that the target edge cloud gateway sends the access information to the target edge cloud server. With the solution provided by this application, it is possible to request to the server without modifying the client's request path or request parameters (the request path and request parameters belong to the access information), thereby reducing the intrusion to the client and achieving non-intrusive synchronous routing. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the following briefly introduces the drawings required for use in the embodiments or related technical descriptions. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0034] Figure 1 This is a schematic diagram of the architecture of a cloud-edge collaboration system in one embodiment;

[0035] Figure 2 A schematic diagram of the process involved in the cloud-edge collaboration system in one embodiment;

[0036] FIG3( a ) is a flowchart of configuration related to synchronous routing requests from the central cloud side to the edge cloud side in one embodiment;

[0037] FIG3( b ) is a schematic diagram of an architecture in which a central cloud-side application requests a service from an edge cloud-side application in one embodiment;

[0038] Figure 4 This is a schematic diagram of an architecture in which a central cloud-side application requests a service from an edge cloud-side application in another embodiment;

[0039] Figure 5 A flowchart of configuration related to synchronous routing requests from the edge cloud side to the central cloud side in one embodiment;

[0040] Figure 6 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0041] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0042] The solution provided in this application can achieve synchronous routing from the central cloud side to the edge cloud side without modifying the client's request path or request parameters (that is, it is a non-invasive solution for the client).

[0043] The present application provides a cloud-edge collaborative system. In this embodiment, the central cloud-side application requests services from the edge cloud-side application. Accordingly, the central cloud-side application can be called the central cloud-side client, the requested edge cloud-side application can be called the target edge cloud-side server, and the edge cloud side where the requested edge cloud-side application is located is called the target edge cloud side.

[0044] Reference Figure 1 The cloud-edge collaborative system includes a central cloud server and an edge cloud server. The central cloud server includes a central cloud client, a central cloud forwarding service, and a central cloud gateway. In scenarios where a central cloud application requests a service from an edge cloud application, the central cloud server also includes an application service. The target edge cloud server includes a target edge cloud gateway and a target edge cloud server.

[0045] The process involved in this embodiment includes: Figure 2 Steps S201 to S206 are shown, specifically:

[0046] In step S201, the central cloud client sends a synchronous routing request to the application service, which is directed to the target edge cloud and the target edge cloud server.

[0047] For example, the central cloud side client can send an http / https synchronization routing request to the application service, and the request carries the service address information of the target edge cloud side and the target edge cloud side server.

[0048] Step S202: The application service generates a unique identifier associated with the synchronization routing request, and deploys a central cloud-side forwarding service on the central cloud side.

[0049] After the application service receives the synchronous routing request, it can generate a unique identifier (unique id) associated with the synchronous routing request and deploy a forwarding service on the central cloud side. This forwarding service can be called the central cloud side forwarding service. The central cloud side forwarding service is a service that can modify access information (such as access request path, access request parameters) according to configuration parameters (such as the unique identifier associated with the synchronous routing request, gateway address). The central cloud side forwarding service can forward the access information to the central cloud side gateway, and add the unique identifier associated with the synchronous routing request to the front of the access information, and then configure a route to the target edge cloud side gateway on the central cloud side gateway (for distinction, the route between gateways is called a first-class route), and can also configure a route to the target edge cloud side server on the target edge cloud side gateway (for distinction, the route between the gateway and the application is called a second-class route).

[0050] Taking HTTP / HTTPS as an example, after receiving an HTTP / HTTPS synchronization routing request, the application service can generate a unique identifier (unique ID) associated with the HTTP / HTTPS synchronization routing request and deploy an HTTP / HTTPS forwarding service on the central cloud side. This HTTP / HTTPS forwarding service can be referred to as the central cloud-side HTTP / HTTPS forwarding service. The central cloud-side HTTP / HTTPS forwarding service can modify HTTP / HTTPS access information (such as the HTTP / HTTPS access request path and HTTP / HTTPS access request parameters) based on configuration parameters (such as the unique identifier associated with the HTTP / HTTPS synchronization routing request and the gateway address). The central cloud-side HTTP / HTTPS forwarding service forwards the HTTP / HTTPS access information to the central cloud-side gateway, prepending the unique identifier associated with the HTTP / HTTPS synchronization routing request to the HTTP / HTTPS access information. The central cloud-side HTTP / HTTPS forwarding service then configures an HTTP / HTTPS route to the target edge cloud-side gateway (for differentiation, gateway-to-gateway routing is called a first-class route). It can also configure an HTTP / HTTPS route to the target edge cloud-side server on the target edge cloud-side gateway (for differentiation, gateway-to-application routing is called a second-class route). The central cloud-side client is an HTTP / HTTPS client.

[0051] In step S203, the central cloud-side gateway configures a type of route to the target edge cloud-side gateway and associates it with the unique identifier.

[0052] To distinguish, the route between gateways is called a first-class route. The central cloud-side gateway can configure a first-class route from itself to the target edge cloud-side gateway and associate the first-class route with the aforementioned unique identifier.

[0053] Step S204: The central cloud-side client sends access information to the central cloud-side forwarding service.

[0054] The access information may include an access request, and the access information may also include an access request path or access request parameters.

[0055] In this step, the central cloud side client accesses the target edge cloud side server through the central cloud side forwarding service. Therefore, the central cloud side client sends access information to the central cloud side forwarding service.

[0056] Exemplarily, the central cloud side client sends access information to the central cloud side http / https forwarding service, where the access information includes an http / https access request, and the access information may include an http / https access request path or an http / https access request parameter.

[0057] Step S205: The central cloud side forwarding service adds a unique identifier to the access information and sends it to the central cloud side gateway.

[0058] After receiving the access information from the central cloud client, the central cloud forwarding service can add a unique identifier to the access request path or access request parameters of the access information. Specifically, the unique identifier can be added to the front end of the access request path or access request parameters, and then sent to the central cloud gateway.

[0059] For example, after receiving the access information from the central cloud side client, the central cloud side http / https forwarding service can add a unique identifier to the front end of the http / https access request path of the access information, and then send it to the central cloud side gateway.

[0060] In step S206, the central cloud side gateway determines a type of routing associated with the unique identifier added to the access information, and sends the access information to the target edge cloud side gateway according to the type of routing, so that the target edge cloud side gateway sends the access information to the target edge cloud side server.

[0061] Since the central cloud-side gateway is pre-configured with a class of routes associated with a unique identifier, after receiving the access information sent by the central cloud-side forwarding service, the central cloud-side gateway can parse the access request path of the access information or the unique identifier carried by the access request parameters, thereby obtaining a class of routes associated with the unique identifier. According to this class of routes, the access information is sent to the target edge cloud-side gateway, so that the target edge cloud-side gateway sends the access information to the target edge cloud-side server.

[0062] For example, after the central cloud-side gateway receives the access information sent by the central cloud-side http / https forwarding service, it can parse out the unique identifier carried by the http / https access request path in the access information, thereby obtaining a type of route associated with the unique identifier. According to this type of route, the access information is sent to the target edge cloud-side gateway, so that the target edge cloud-side gateway sends the access information to the target edge cloud-side server.

[0063] In the above-mentioned cloud-edge collaborative system, the central cloud-side client sends a synchronous routing request directed to the target edge cloud side and the target edge cloud side server to the application service; the application service generates a unique identifier associated with the synchronous routing request and deploys the central cloud-side forwarding service on the central cloud side; the central cloud-side gateway configures a class of routing to the target edge cloud side gateway and associates it with the unique identifier; the central cloud-side client sends access information to the central cloud-side forwarding service; the central cloud-side forwarding service adds a unique identifier to the access information and sends it to the central cloud-side gateway; the central cloud-side gateway determines the class of routing associated with the unique identifier added to the access information, and sends the access information to the target edge cloud side gateway based on the class of routing, so that the target edge cloud side gateway sends the access information to the target edge cloud side server. With the solution provided by this application, it is possible to request the server in the relevant edge cloud side without modifying the client's request path or request parameters (the request path and request parameters belong to the access information), thereby reducing the intrusion to the client and achieving non-intrusive synchronous routing.

[0064] In one embodiment, the target edge cloud side gateway configures a second type of routing to the target edge cloud side server; the target edge cloud side gateway sends the access information to the target edge cloud side server according to the second type of routing to the target edge cloud side server.

[0065] To distinguish them, the routing between the gateway and the application is called Class II routing. The target edge cloud gateway configures a Class II route to the target edge cloud server. After receiving access information from the central cloud gateway, the target edge cloud gateway can send the access request for the access information to the target edge cloud server based on the Class II route. After receiving the access request, the target edge cloud server provides the corresponding service to the central cloud client. The central cloud client can obtain the services of the target edge cloud server without modifying the access request path or access request parameters, reducing the intrusion to the central cloud client.

[0066] In one embodiment, the target edge cloud side gateway associates the second type of route with the unique identifier; the target edge cloud side gateway determines the second type of route associated with the unique identifier added to the access information, and sends the access information to the target edge cloud side server based on the second type of route.

[0067] After the application service generates a unique identifier, it can send the unique identifier and a synchronization routing request to the central cloud-side forwarding service. Based on the information contained in the synchronization routing request, the central cloud-side forwarding service sends the unique identifier to the target edge cloud-side gateway. The target edge cloud-side gateway configures a second-class route to the target edge cloud-side server and binds the second-class route to the unique identifier.

[0068] After the target edge cloud side gateway receives the access information sent by the central cloud side gateway, it can parse the access request path of the access information or the unique identifier carried by the access request parameter, thereby obtaining the second-class routing associated with the unique identifier, and according to the second-class routing, send the access request of the access information to the target edge cloud side server.

[0069] In this embodiment, the target edge cloud side gateway associates the second-class route with the unique identifier, and can subsequently quickly find the corresponding second-class route, thereby sending the access request in the access information to the target edge cloud side server.

[0070] In one embodiment, the unique identifier is obtained by performing a hash operation based on relevant information about the target edge cloud side and the target edge cloud side service end.

[0071] The central cloud client can send a synchronization routing request to the application service, which carries the service address information of the target edge cloud and the target edge cloud server. After receiving the synchronization routing request, the application service performs a hash operation based on the timestamp and the service address information of the target edge cloud and the target edge cloud server carried in the synchronization routing request to obtain a unique identifier. This ensures that the unique identifier is unique and avoids duplication with other unique identifiers that would affect the processing flow.

[0072] Referring to Figure 3(a), Figure 3(a) shows the relevant configuration process of http / https synchronous routing requests from the central cloud side to the edge cloud side.

[0073] When triggered by the user, the client on the central cloud side can send an http / https synchronization routing request to the application service. The request carries the service address information of the target edge cloud side and the target edge cloud side server. After receiving the http / https synchronization routing request, the application service can generate a unique identifier (unique id) associated with the http / https synchronization routing request and deploy an http / https forwarding service on the central cloud side. This http / https forwarding service can be called the central cloud side http / https forwarding service. The central cloud side http / https forwarding service is a service that can modify http / https access information (such as the http / https access request path and http / https access request parameters) according to configuration parameters (such as the unique identifier associated with the http / https synchronization routing request and the gateway address). The central cloud-side http / https forwarding service can forward http / https access information to the central cloud-side gateway, and add a unique identifier associated with the http / https synchronization routing request in front of the http / https access information. Then, the central cloud-side gateway configures an http / https route to the target edge cloud-side gateway (for distinction, the routing between gateways is called a first-class routing). The target edge cloud-side gateway can also configure an http / https route to the target edge cloud-side server (for distinction, the routing between gateways and applications is called a second-class routing). After the central cloud-side gateway is successfully configured, the successful configuration information can be fed back to the application service; after the target edge cloud-side gateway is successfully configured, the successful configuration information can be fed back to the application service. After receiving the successful configuration information, the application service can feedback to the central cloud-side client and display it to the user.

[0074] 3( b ), FIG3( b ) shows a schematic diagram of an architecture in which a central cloud-side application requests a service from an edge cloud-side application.

[0075] The first client on the central cloud side sends access information to the http / https forwarding service ① on the central cloud side. The access information includes an http / https access request. The access information may include an http / https access request path or an http / https access request parameter. After receiving the access information from the first client on the central cloud side, the http / https forwarding service ① on the central cloud side may add a unique identifier a to the front end of the http / https access request path in the access information, and then send it to the central cloud side gateway. After receiving the access information sent by the http / https forwarding service ① on the central cloud side, the central cloud side gateway may parse out the unique identifier a carried in the http / https access request path in the access information, thereby obtaining a type of route associated with the unique identifier a, and according to the type of route, send the access information to the first edge cloud side gateway.

[0076] After the first edge cloud side gateway receives the access information sent by the central cloud side gateway, it can parse the access request path of the access information or the unique identifier a carried by the access request parameter, thereby obtaining the second-class routing associated with the unique identifier a, and according to the second-class routing, send the access request of the access information to the first edge cloud side server.

[0077] The second client on the central cloud side sends access information to the http / https forwarding service ② on the central cloud side. The access information includes an http / https access request. The access information may include an http / https access request path or an http / https access request parameter. After receiving the access information from the second client on the central cloud side, the http / https forwarding service 2 on the central cloud side may add a unique identifier b to the front end of the http / https access request path in the access information, and then send it to the central cloud side gateway. After receiving the access information sent by the http / https forwarding service ② on the central cloud side, the central cloud side gateway may parse out the unique identifier b carried in the http / https access request path in the access information, thereby obtaining a type of route associated with the unique identifier b, and send the access information to the second edge cloud side gateway based on the type of route.

[0078] After the second edge cloud side gateway receives the access information sent by the central cloud side gateway, it can parse the access request path of the access information or the unique identifier b carried by the access request parameter, thereby obtaining the second-class routing associated with the unique identifier b, and according to the second-class routing, send the access request of the access information to the second edge cloud side server.

[0079] The present application provides a cloud-edge collaboration system. In this embodiment, an edge cloud application requests a service from a central cloud application. Accordingly, the edge cloud application can be referred to as an edge cloud client, the requested central cloud application can be referred to as a target central cloud server, and the central cloud where the requested central cloud application resides is referred to as the target central cloud. In scenarios where an edge cloud application requests a service from a central cloud application, the edge cloud server also includes an application service.

[0080] The interaction process involved in this embodiment includes: Figure 4 Steps S401 to S406 are shown, specifically:

[0081] In step S401, the edge cloud client sends a synchronous routing request to the target central cloud and the target central cloud server to the application service.

[0082] For example, the edge cloud client can send an http / https synchronization routing request to the application service, which carries the service address information of the target central cloud side and the target central cloud side server.

[0083] In step S402 , the application service generates a unique identifier associated with the synchronization routing request and deploys an edge cloud-side forwarding service on the edge cloud side.

[0084] After the application service receives the synchronous routing request, it can generate a unique identifier (unique ID) associated with the synchronous routing request and deploy a forwarding service on the edge cloud side. This forwarding service can be called an edge cloud side forwarding service. The edge cloud side forwarding service is a service that can modify access information (such as access request path, access request parameters) according to configuration parameters (such as the unique identifier associated with the synchronous routing request, gateway address). The edge cloud side forwarding service can forward the access information to the edge cloud side gateway, and add the unique identifier associated with the synchronous routing request to the front of the access information, and then configure a route to the target central cloud side gateway on the edge cloud side gateway (for distinction, the route between gateways is called a first-class route), and can also configure a route to the target central cloud side server on the target central cloud side gateway (for distinction, the route between the gateway and the application is called a second-class route).

[0085] Taking HTTP / HTTPS as an example, after receiving an HTTP / HTTPS synchronization routing request, the application service can generate a unique identifier (unique ID) associated with the HTTP / HTTPS synchronization routing request and deploy an HTTP / HTTPS forwarding service on the edge cloud side. This HTTP / HTTPS forwarding service can be referred to as the edge cloud-side HTTP / HTTPS forwarding service. The edge cloud-side HTTP / HTTPS forwarding service modifies HTTP / HTTPS access information (such as the HTTP / HTTPS access request path and HTTP / HTTPS access request parameters) based on configuration parameters (such as the unique identifier associated with the HTTP / HTTPS synchronization routing request and the gateway address). The edge cloud-side HTTP / HTTPS forwarding service forwards the HTTP / HTTPS access information to the edge cloud-side gateway, prepending the unique identifier associated with the HTTP / HTTPS synchronization routing request to the HTTP / HTTPS access information. The edge cloud-side HTTP / HTTPS forwarding service then configures an HTTP / HTTPS route to the target central cloud-side gateway (for differentiation, gateway-to-gateway routing is called a first-class route). The target central cloud-side gateway can also configure an HTTP / HTTPS route to the target central cloud-side server (for differentiation, gateway-to-application routing is called a second-class route). The edge cloud-side client is an HTTP / HTTPS client.

[0086] In step S403, the edge cloud gateway configures a type of route to the target central edge cloud gateway and associates it with a unique identifier.

[0087] To distinguish, the route between gateways is called a first-class route. The edge cloud gateway can configure a first-class route from itself to the target central cloud gateway and associate the first-class route with the unique identifier mentioned above.

[0088] Step S404: The edge cloud client sends access information to the edge cloud forwarding service.

[0089] The access information may include an access request, and the access information may also include an access request path or access request parameters.

[0090] In this step, the edge cloud side client accesses the target central cloud side server through the edge cloud side forwarding service. Therefore, the edge cloud side client sends access information to the edge cloud side forwarding service.

[0091] Exemplarily, the edge cloud side client sends access information to the edge cloud side http / https forwarding service, where the access information includes an http / https access request, and the access information may include an http / https access request path or an http / https access request parameter.

[0092] In step S405 , the edge cloud side forwarding service adds a unique identifier to the access information and sends it to the edge cloud side gateway.

[0093] After receiving the access information from the edge cloud client, the edge cloud forwarding service can add a unique identifier to the access request path or access request parameters of the access information. Specifically, the unique identifier can be added to the front end of the access request path or access request parameters, and then sent to the edge cloud gateway.

[0094] For example, after receiving the access information from the edge cloud client, the edge cloud side http / https forwarding service can add a unique identifier to the front end of the http / https access request path of the access information, and then send it to the edge cloud side gateway.

[0095] In step S406, the edge cloud side gateway determines a type of routing associated with the unique identifier added to the access information, and sends the access information to the target center cloud side gateway according to the type of routing, so that the target center cloud side gateway sends the access information to the target center cloud side server.

[0096] Since the edge cloud side gateway is pre-configured with a class of routes associated with a unique identifier, after receiving the access information sent by the edge cloud side forwarding service, the edge cloud side gateway can parse the access request path of the access information or the unique identifier carried by the access request parameters, thereby obtaining a class of routes associated with the unique identifier. According to the class of routes, the access information is sent to the target central cloud side server, so that the target central cloud side gateway sends the access information to the target central cloud side server.

[0097] For example, after the edge cloud side gateway receives the access information sent by the edge cloud side http / https forwarding service, it can parse out the unique identifier carried by the http / https access request path in the access information, thereby obtaining a type of route associated with the unique identifier. According to this type of route, the access information is sent to the target center cloud side gateway, so that the target center cloud side gateway sends the access information to the target center cloud side server.

[0098] In the above-mentioned cloud-edge collaborative system, the edge cloud client sends a synchronous routing request directed to the target central cloud side and the target central cloud side server to the application service; the application service generates a unique identifier associated with the synchronous routing request and deploys the edge cloud side forwarding service on the edge cloud side; the edge cloud side gateway configures a type of routing to the target central cloud side gateway and associates it with the unique identifier; the edge cloud side client sends access information to the edge cloud side forwarding service; the edge cloud side forwarding service adds a unique identifier to the access information and sends it to the edge cloud side gateway; the edge cloud side gateway determines the type of routing associated with the unique identifier added to the access information, and sends the access information to the target central cloud side gateway based on the type of routing, so that the target central cloud side gateway sends the access information to the target central cloud side server. With the solution provided by this application, it is possible to request the server in the relevant central cloud side without modifying the client's request path or request parameters (the request path and request parameters belong to the access information), thereby reducing the intrusion to the client and achieving non-intrusive synchronous routing.

[0099] In one embodiment, the target center cloud side gateway configures a second type of routing to the target center cloud side server; the target center cloud side gateway sends access information to the target center cloud side server according to the second type of routing to the target center cloud side server.

[0100] To distinguish them, the routing between the gateway and the application is called Class II routing. The target center cloud-side gateway configures a Class II route to the target center cloud-side server. After receiving access information from the edge cloud-side gateway, the target center cloud-side gateway can send the access request for the access information to the target center cloud-side server based on the Class II route. After receiving the access request, the target center cloud-side server provides the corresponding service to the edge cloud-side client. The edge cloud-side client can obtain the services of the target center cloud-side gateway without modifying the access request path or access request parameters, reducing the intrusion to the edge cloud-side client.

[0101] In one embodiment, the target center cloud side gateway associates the second type of routing with the unique identifier; the target center cloud side gateway determines the second type of routing associated with the unique identifier added to the access information, and sends the access information to the target center cloud side service end according to the second type of routing.

[0102] After the application service generates a unique identifier, it can send the unique identifier and a synchronization routing request to the edge cloud forwarding service. Based on the information in the synchronization routing request, the edge cloud forwarding service sends the unique identifier to the target central cloud gateway. The target central cloud gateway configures a second-class route to the target central cloud server and binds the second-class route to the unique identifier.

[0103] After the target center cloud side gateway receives the access information sent by the edge cloud side gateway, it can parse the access request path of the access information or the unique identifier carried by the access request parameter, thereby obtaining the second-class routing associated with the unique identifier, and according to the second-class routing, send the access request of the access information to the target center cloud side gateway.

[0104] In this embodiment, the target center cloud-side gateway associates the second-class route with the unique identifier, and can subsequently quickly find the corresponding second-class route, thereby sending the access request in the access information to the target center cloud-side gateway.

[0105] In one embodiment, the unique identifier is obtained by performing a hash operation based on relevant information about the target central cloud side and the target central cloud side service end.

[0106] The edge cloud client can send a synchronization routing request to the application service. This request carries the service address information of the target central cloud and the target central cloud server. After receiving the synchronization routing request, the application service performs a hash operation based on the timestamp and the service address information of the target central cloud and the target central cloud server carried in the synchronization routing request to obtain a unique identifier. This ensures that the unique identifier is unique and avoids duplication with other unique identifiers that could affect the processing flow.

[0107] Reference Figure 5 , Figure 5 It shows the configuration process of http / https synchronous routing request from edge cloud side to central cloud side.

[0108] When triggered by the user, the edge cloud client can send an http / https synchronization routing request to the application service. The request carries the service address information of the target central cloud side and the target central cloud side server. After receiving the http / https synchronization routing request, the application service can generate a unique identifier (unique id) associated with the http / https synchronization routing request and deploy an http / https forwarding service on the edge cloud side. This http / https forwarding service can be called an edge cloud side http / https forwarding service. The edge cloud side http / https forwarding service is a service that can modify http / https access information (such as http / https access request path, http / https access request parameters) according to configuration parameters (such as the unique identifier associated with the http / https synchronization routing request and the gateway address). The edge cloud-side http / https forwarding service can forward http / https access information to the edge cloud-side gateway, and add a unique identifier associated with the http / https synchronization routing request to the front of the http / https access information. Then, the edge cloud-side gateway configures an http / https route to the target center cloud-side gateway (for distinction, the routing between gateways is called a first-class routing). The target center cloud-side gateway can also configure an http / https route to the target center cloud-side server (for distinction, the routing between gateways and applications is called a second-class routing). After the edge cloud-side gateway is successfully configured, the configuration success information can be fed back to the application service; after the target center cloud-side gateway is successfully configured, the configuration success information can be fed back to the application service. After receiving the configuration success information, the application service can feedback it to the edge cloud-side client and display it to the user.

[0109] It should be understood that, although the various steps in the flowcharts involved in the various embodiments described above are displayed in sequence according to the instructions of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowcharts involved in the various embodiments described above can include multiple steps or multiple stages, and these steps or stages are not necessarily executed and completed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0110] The present application provides a central cloud-side server, which includes a central cloud-side gateway of the cloud-edge collaboration system as described in any of the above embodiments; the central cloud-side server includes a central cloud-side client of the cloud-edge collaboration system as described in any of the above embodiments, or a central cloud-side service end of the cloud-edge collaboration system as described in any of the above embodiments.

[0111] The present application provides an edge cloud-side server, which includes an edge cloud-side gateway of the cloud-edge collaboration system as described in any of the above embodiments; the edge cloud-side server includes an edge cloud-side client of the cloud-edge collaboration system as described in any of the above embodiments, or an edge cloud-side service end of the cloud-edge collaboration system as described in any of the above embodiments.

[0112] The central cloud side server and the edge cloud side server can be implemented by computer equipment. The internal structure diagram of the computer equipment can be as follows Figure 6 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, abbreviated as I / O) and a communication interface. The processor, memory and input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the computer device is used to store data involved in the above embodiment. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, it implements the steps introduced in one of the above embodiments.

[0113] Those skilled in the art will understand that Figure 6 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0114] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above embodiments are implemented.

[0115] In one embodiment, a computer program product is provided, on which a computer program is stored. The computer program is used by a processor to execute the steps in the above embodiments.

[0116] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0117] Those skilled in the art will appreciate that all or part of the processes in the above embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the above embodiments. In particular, any reference to memory, database, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The databases involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the various embodiments provided herein may be, but are not limited to, general-purpose processors, central processing units (CPUs), graphics processing units (GPUs), digital signal processors (DSPs), programmable logic devices (PLDs), quantum computing-based data processing logic devices, artificial intelligence (AI) processors, and the like.

[0118] The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0119] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. A cloud-edge collaborative system, characterized in that: The system comprises: The central cloud client sends a synchronous routing request to the application service, pointing to the target edge cloud and the target edge cloud server. The application service generates a unique identifier associated with the synchronization routing request and deploys a central cloud side forwarding service on the central cloud side; The central cloud-side gateway configures a type of route to the target edge cloud-side gateway and associates it with the unique identifier; The central cloud side client sends access information to the central cloud side forwarding service; The central cloud side forwarding service adds the unique identifier to the access information and sends it to the central cloud side gateway; The central cloud-side gateway determines a type of routing associated with the unique identifier added to the access information, and sends the access information to the target edge cloud-side gateway based on the type of routing, so that the target edge cloud-side gateway sends the access information to the target edge cloud-side service end.

2. The system according to claim 1, wherein: The target edge cloud side gateway configures a second type of routing to the target edge cloud side server; The target edge cloud side gateway sends the access information to the target edge cloud side server according to the second type of routing to the target edge cloud side server.

3. The system according to claim 2, characterized in that The target edge cloud-side gateway associates the second type of route with the unique identifier; The target edge cloud side gateway determines a second type of routing associated with the unique identifier added to the access information, and sends the access information to the target edge cloud side server according to the second type of routing.

4. The system according to claim 1, wherein: The unique identifier is obtained by performing a hash operation based on relevant information about the target edge cloud side and the target edge cloud side service end.

5. A cloud-edge collaborative system, characterized in that: The system comprises: The edge cloud client sends a synchronous routing request to the target central cloud and the target central cloud server to the application service; The application service generates a unique identifier associated with the synchronization routing request and deploys an edge cloud side forwarding service on the edge cloud side; The edge cloud side gateway configures a class of routing to the target central edge cloud side gateway and associates it with the unique identifier; The edge cloud side client sends access information to the edge cloud side forwarding service; The edge cloud side forwarding service adds the unique identifier to the access information and sends it to the edge cloud side gateway; The edge cloud side gateway determines a type of routing associated with the unique identifier added to the access information, and sends the access information to the target center cloud side gateway based on the type of routing, so that the target center cloud side gateway sends the access information to the target center cloud side service end.

6. The system according to claim 5, characterized in that The target center cloud side gateway configures a second type of routing to the target center cloud side server; The target center cloud side gateway sends the access information to the target center cloud side server according to the second type of routing to the target center cloud side server.

7. The system according to claim 6, characterized in that The target center cloud-side gateway associates the second type of route with the unique identifier; The target center cloud-side gateway determines a second type of routing associated with the unique identifier added to the access information, and sends the access information to the target center cloud-side service end according to the second type of routing.

8. The system according to claim 5, wherein: The unique identifier is obtained by performing a hash operation based on relevant information about the target center cloud side and the target center cloud side service end.

9. A central cloud-side server, characterized in that: The central cloud-side server includes the central cloud-side gateway of the cloud-edge collaboration system as described in any one of claims 1 to 8; the central cloud-side server includes the central cloud-side client of the cloud-edge collaboration system as described in any one of claims 1 to 4, or the central cloud-side service end of the cloud-edge collaboration system as described in any one of claims 5 to 8.

10. An edge cloud server, characterized in that: The edge cloud side server includes the edge cloud side gateway of the cloud-edge collaboration system as described in any one of claims 1 to 8; the edge cloud side server includes the edge cloud side client of the cloud-edge collaboration system as described in any one of claims 1 to 4, or the edge cloud side service end of the cloud-edge collaboration system as described in any one of claims 5 to 8.

Images