Service routing method and system, device, and medium

By introducing a three-layer routing service architecture into the cloud platform, clarifying the service functions of each layer, solving the problems of difficulty in implementing customization requirements of cloud platform and low routing efficiency, and achieving efficient service routing processing.

WO2024234933A1PCT designated stage expired Publication Date: 2024-11-21EBAOTECH CORP
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/088866
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-17
Filing Date
2024-04-19
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

When cloud platforms deal with customer customization needs, the routing service level in the existing technology is too simple, resulting in unclear division of responsibilities and difficulty in collaboration, which cannot meet the complex needs of customers such as custom domain names, request paths and certificate modifications, and load balancing and The pressure to apply gateways is too high, resulting in low service routing efficiency.

Method used

Adopting a three-layer routing service architecture, divided into load balancing, edge routing and application gateway. By configuring different setting functions, each layer of routing service division is clear. Load balancing is responsible for domain name and certificate configuration, edge routing processing request path and security configuration, application The gateway performs authentication and forwarding, maximizes the use of the advantages of routing services at each layer and reduces the pressure on the gateway.

Benefits of technology

It realizes flexible implementation of customer customized needs, improves the execution efficiency of cloud platform service routing, alleviates the pressure of load balancing and application gateways, simplifies responsibility collaboration, and improves the efficiency of service routing process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024088866_21112024_PF_FP_ABST
    Figure CN2024088866_21112024_PF_FP_ABST
Patent Text Reader

Abstract

The present application relates to the field of communications, and discloses a service routing method and system, a device, and a medium. By configuring layered and divided processing of three layers of routing services having different set functions, the customization requirements of clients can be realized, and the execution efficiency of the routing process of a cloud platform on services is improved. The method comprises: a load balancing service receives an access request, the access request being used for requesting a target service; the load balancing service performs first processing on the access request according to a first set function, and forwards the access request having undergone the first processing to an edge routing service; the edge routing service performs second processing on the access request according to a second set function, and forwards the access request having undergone the second processing to a gateway service; the gateway service performs third processing on the access request according to a third set function, and forwards the access request having undergone the third processing to a target server, wherein the first set function, the second set function and the third set function are all different.
Need to check novelty before this filing date? Find Prior Art

Description

A service routing method, system, device and medium

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on May 17, 2023, with application number 202310559093.0 and application name “A routing method, system, device and medium for a service”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a service routing method, system, device and medium. Background Art

[0003] For a cloud platform providing services, access requests are typically forwarded to backend services through the application's routing service. For example, access requests from the cloud platform may first pass through load balancing, then enter the application's routing service, and finally be forwarded to the corresponding backend service through the application's routing service. The application's routing service can be implemented using an application gateway or Nginx (a server).

[0004] Since cloud platforms can provide external services to businesses (to business, toB), customers will have many customized requirements, such as custom domain names, custom request paths, certificate modifications, etc. However, on the one hand, because each customized requirement is a special case, it requires all relevant staff of the cloud service provider to discuss and implement it, which makes the implementation process difficult. For example, for the demand for a custom domain name, it is often the customer themselves who needs to make the configuration, but the domain name provider actually needs to do the configuration, that is, the place where the configuration is made is the service belonging to the cloud platform, so the configuration ownership is confusing and the responsibilities cannot be sorted out, which makes it difficult to implement the customer's customized requirements. On the other hand, due to the functional limitations of the load balancing itself on some cloud platforms, such as the inability to support multiple certificates, the inability to centralize authentication, or the inability to support complex routing, some customer customization requirements may not be met.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a service routing method, system, device and medium, which easily realize the customized needs of customers and improve the routing efficiency of services in the cloud platform by configuring the layered division of labor of three-layer routing services with different set functions.

[0007] In a first aspect, an embodiment of the present application provides a service routing method, which is applied to a service routing system, wherein the service routing system includes a load balancing service, an edge routing service, and a gateway service; the method includes: the load balancing service receives an access request, and the access request is used to request a target service; the load balancing service performs a first processing on the access request according to a first setting function, and forwards the access request after the first processing to the edge routing service; the edge routing service performs a second processing on the access request according to a second setting function, and forwards the access request after the second processing to the gateway service; the gateway service performs a third processing on the access request according to a third setting function, and forwards the access request after the third processing to the target server, and the target server is used to provide the target service; wherein the first setting function, the second setting function, and the third setting function are all different.

[0008] The load balancing service can be provided by a load balancing device, the edge routing service can be implemented by an edge routing device, and the gateway service can be implemented by an application gateway. The target server can be a backend server or a frontend server. This layered division of labor between the three-tier routing services, each with its own set of functions, clearly defines the responsibilities of each routing layer. This allows customers' customized needs to be distributed among the responsible teams for different services, making it easier to meet these needs. Furthermore, by maximizing the advantages of each routing service layer, the cloud platform's routing process for services is highly efficient. Furthermore, the addition of edge routing services can alleviate pressure on gateway services to a certain extent.

[0009] In some possible implementations, the edge routing service processes the access request according to the second set function and forwards the access request to the gateway service, including: the edge routing service processes the access request according to the second set function, determines that the target service is a backend service according to the second set function, and forwards the access request to the gateway service; wherein the target service is configured to provide the backend service, such as a backend server. In this manner, the gateway service does not need to identify the classification of the target service requested by the access request, thereby reducing pressure on the gateway service.

[0010] In some possible implementations, the method further includes: the edge routing service performing a second processing on the access request according to the second set function, and if the target service is determined to be a front-end service according to the second set function processing, forwarding the access request to a target server, where the target server is configured to provide the front-end service, such as a front-end server. For example, if the access request is identified as a request for static resources such as images, the access request is forwarded without being forwarded to the application gateway service, thereby significantly alleviating pressure on the gateway service.

[0011] In some possible implementations, the first, second, and third set functions are determined based on at least one of the execution efficiency and performance of the factory-configured functions of the load balancing service, edge routing service, and gateway service. This allows each routing service layer in this application to perform only what it is responsible for and excels at, and to act as a proxy for tasks it is not good at, forwarding them to other layers for processing, thereby maximizing the advantages of each routing layer.

[0012] In some possible implementations, the first setting function includes configuring a domain name and configuring a secure socket layer (SSL) certificate. In this case, the edge service and the gateway service do not need to configure the domain name and configure the SSL certificate.

[0013] In some possible implementations, a load balancing service includes multiple sub-load balancing services; some of the multiple sub-load balancing services are used to configure custom domain names, or some of the multiple sub-load balancing services support SSL certificate modification based on customer needs. For example, the sub-load balancing service used to configure custom domain names may be a service assigned to a customer by a cloud service provider or purchased by the customer.

[0014] In some possible implementations, the second setting function includes at least one of the following: request path conversion, security configuration, header processing, and request classification; wherein the request classification is used to distinguish whether the target service is a front-end service or a back-end service.

[0015] In some possible implementations, the third setting function includes at least one of the following: authenticating the access request, forwarding the access request to the target server, and adding monitoring information to the access request.

[0016] In some possible implementations, the edge routing service can be implemented through nginx, traefik, envoy, or the service provider's custom service.

[0017] In a second aspect, the present application provides a service routing system, which includes a load balancing service, an edge routing service, and a gateway service; the load balancing service is used to receive an access request, and perform a first processing on the access request according to a first setting function, and forward the access request after the first processing to the edge routing service, and the access request is used to request a target service; the edge routing service is used to perform a second processing on the access request according to a second setting function, and forward the access request after the second processing to the gateway service; the gateway service is used to perform a third processing on the access request according to a third setting function, and forward the access request after the third processing to the target server, and the target server is used to provide the target service; wherein the first setting function, the second setting function, and the third setting function are all different.

[0018] In some possible implementations, the edge routing service processes the access request according to the second set function, and if the target service is determined to be a backend service according to the second set function, forwards the access request to the gateway service. The target service is configured to provide the backend service, such as a backend server. This eliminates the need for the gateway service to identify the target service category of the access request, thereby reducing pressure on the gateway service.

[0019] In some possible implementations, the edge routing service is used to perform a second process on the access request according to a second set function, and the target service obtained by the second set function processing is a front-end service, and the access request is forwarded to the target server, wherein the target server is used to provide the front-end service.

[0020] In some possible implementations, the first setting function, the second setting function, and the third setting function are determined based on at least one of the execution efficiency and performance of the factory configuration functions of the load balancing service, the edge routing service, and the gateway service.

[0021] In some possible implementations, the first setting function includes: configuring a domain name and configuring a secure socket layer (SSL) certificate.

[0022] In some possible implementations, the load balancing service includes multiple sub-load balancing services; wherein, some of the multiple sub-load balancing services are used to configure custom domain names, or, some of the multiple sub-load balancing services support SSL certificate modification according to customer needs.

[0023] In some possible implementations, the second setting function includes at least one of the following: request path conversion, security configuration, header processing, and request classification; wherein the request classification is used to distinguish whether the target service is a front-end service or a back-end service.

[0024] In some possible implementations, the third setting function includes at least one of the following: authenticating the access request, forwarding the access request to the target server, and adding monitoring information to the access request.

[0025] In some possible implementations, the edge routing service can be implemented through nginx, traefik, envoy, or the service provider's custom service.

[0026] In a third aspect, the present application provides a readable medium having instructions stored thereon, which, when executed on an electronic device, causes the electronic device to execute the service routing method as in the first aspect and any possible implementation thereof.

[0027] In a fourth aspect, the present application provides an electronic device comprising: a memory for storing instructions executed by one or more processors of the electronic device, and a processor, which is one of the processors of the electronic device, for executing the service routing method as in the first aspect and any possible implementation thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] FIG1A shows a schematic structural diagram of a service routing system according to some embodiments of the present application;

[0029] FIG1B shows a schematic diagram of a hierarchical structure of service routing according to some embodiments of the present application;

[0030] FIG2 is a schematic diagram showing a flow chart of a service routing method according to some embodiments of the present application;

[0031] FIG3 shows a schematic diagram of functional division of multiple load balancing services according to some embodiments of the present application;

[0032] FIG4 shows a schematic diagram of data flow of a load balancing service according to some embodiments of the present application;

[0033] FIG5 shows a data flow diagram of a load balancing service according to some embodiments of the present application;

[0034] FIG6 shows a schematic diagram of data flow of an edge routing service according to some embodiments of the present application;

[0035] FIG7 shows a schematic diagram of data flow of an edge routing service according to some embodiments of the present application;

[0036] FIG8 shows a schematic structural diagram of an electronic device according to some embodiments of the present application. DETAILED DESCRIPTION

[0037] The illustrative embodiments of the present application include, but are not limited to, a method, system, device, and medium for routing a service.

[0038] To facilitate understanding, some terms involved in this application are first explained.

[0039] Cloud platform: A computing platform built on cloud computing technology that provides resource pooling, automated deployment, elastic scaling, monitoring and management, and security features, allowing developers to quickly build applications in a cloud environment. Cloud platforms typically offer services such as cloud servers, object storage, databases, and message queues.

[0040] In some embodiments, the services provided by the cloud platform include rich functions such as user management, order management, subscription management, channel management, online customer service, and data analysis. For example, the services involved in this application can be services provided for products such as insurance products or financial products, but are not limited thereto.

[0041] As can be seen from the background, cloud platform routing services in related technologies have one or two tiers. These tiers can make it difficult to implement customer customization requirements, or even make some customization requirements impossible to meet. For example, customer customization requirements might include custom domain names, custom request paths, and certificate modifications.

[0042] In a conventional cloud platform's Tier 1 routing scenario, backend services can expose application programming interfaces (APIs) for external access. In this case, a gateway (i.e., an application gateway) typically sets the routing and then exposes the application gateway to the external network. Therefore, the network access path within the cloud platform can be: API access request -> application gateway -> backend service, meaning the cloud platform's Tier 1 routing is "application gateway." Furthermore, the aforementioned gateway can be replaced with Nginx, meaning that routing services are provided through Nginx.

[0043] In a typical cloud platform's Layer 2 routing scenario, the cloud service provider deploys a load balancer before the gateway. This load balancer merely acts as a forwarding proxy, with some functional differences still implemented by the backend gateway. Therefore, the network access path within the cloud platform can be: API access request -> load balancer -> application gateway -> backend service. In other words, the cloud platform's Layer 2 routing consists of "load balancer" and "application gateway."

[0044] Understandably, API access requests typically require a domain name, which typically points to the first layer of the API access pathway. This refers to the Internet Protocol (IP) address resolved by the Domain Name System (DNS) as the first-layer routing, and certificate configuration is also performed at this layer. Therefore, when a cloud platform has a single-layer routing scheme, API access requests are directed to the gateway, and certificate configuration is also handled by the gateway. When a cloud platform has a two-layer routing scheme, API access requests are directed to the load balancer, and certificate configuration is also handled by the load balancer. Furthermore, when a cloud platform has two-layer routing schemes, not only does the front-end load balancer need to be configured with a domain name, but the back-end gateway also needs to be configured with a domain name. Furthermore, the load balancer needs to be configured with a certificate, and the back-end gateway also needs to have related configurations, meaning that the same steps need to be performed on both layers of routing. Consequently, if a custom domain name change is required, the individuals responsible for both layers of routing will be involved and need to collaborate to resolve the issue, making it difficult to implement customized custom domain name requirements.

[0045] In this way, when there is only one layer, all functions are limited by the gateway itself. The more functions required, the greater the workload of gateway development and maintenance. When there are two layers of routing on the cloud platform, the functional division between the two layers is not so clear, and collaboration is difficult and difficult to implement.

[0046] To address the above-mentioned issues, the present application provides a service routing method that is implemented by dividing the various functions of the cloud platform's routing services into three layers: load balancing, edge routing, and application gateway. Thus, by increasing the number of routing service levels from 1 to 2 to 3, the pressure on load balancing and application gateways is alleviated. Specifically, each routing service layer in the three layers can be pre-configured with a corresponding set function to handle access requests, so that each routing service layer handles events that fall within the corresponding set function and forwards events that do not fall within the corresponding set function as a proxy to routing services in other layers for processing. For example, the present application can set corresponding set functions for the three layers of routing services, load balancing, edge routing, and application gateway, based on their respective functions and performance, so that each routing service layer achieves better performance or higher efficiency when using the corresponding set function. In this way, the present application configures different set functions for the three layers of routing services, making the functional division of the three layers of routing services clear, so that customers' customized needs can be distributed to the responsible teams of different services, making it easier to meet customers' customized needs. Furthermore, the advantages of each routing service layer are maximized, making the cloud platform's routing process for services more efficient.

[0047] The access request may be an API access request.

[0048] It can be understood that in this application, each layer of routing service only does what it is responsible for and good at, and for things it is not good at, it only acts as a proxy to forward them to other layers for processing, maximizing the advantages of routing at each layer.

[0049] For example, if setting domain names is what the load balancer excels at, then configuring the domain name setting function as the corresponding setting function of the load balancer will make the subsequent edge routing and Layer 2 functions completely independent of domain name-related functions. For another example, routing is what the gateway excels at, so the load balancer does not need to set up detailed routing.

[0050] In some embodiments, the first setting function, the second setting function, and the third setting function may be determined based on at least one of the execution efficiency and performance of the factory configuration functions of the load balancing service, the edge routing service, and the gateway service.

[0051] As you can understand, the factory-configured functions of a load balancing service primarily include load balancing, which is typically a function that load balancing services excel at, with high efficiency and performance. The factory-configured functions of an edge routing service primarily include authentication, routing, and forwarding, and these functions are typically highly efficient and performant. The factory-configured functions of a gateway service primarily include routing and forwarding, and these functions are typically highly efficient and performant.

[0052] In some embodiments, the edge routing service and the application gateway may not support the execution of the first set function, or the efficiency and performance of the edge routing service and the application gateway in executing the first set function are lower than the efficiency and performance of the load balancing service in executing the first set function.

[0053] In some embodiments, the load balancing service and the application gateway may not support the execution of the second set function, or the execution efficiency and performance of the load balancing service and the application gateway in executing the second set function are lower than the execution efficiency and performance of the edge routing service in executing the second set function.

[0054] In some embodiments, the load balancing service and edge routing service may not support the execution of the third set function, or the execution efficiency and performance of the load balancing service and edge routing service in executing the third set function are lower than the execution efficiency and performance of the application gateway in executing the third set function.

[0055] For example, this application can use the function with better execution efficiency and higher performance among the factory setting functions of the load balancing service as the first setting function, the function with better execution efficiency and higher performance among the factory setting functions of the edge routing service as the second setting function, and the function with better execution efficiency and higher performance among the factory setting functions of the application gateway as the third setting function.

[0056] 1A , a service routing scenario is provided for an embodiment of the application, which includes a client 100 , a load balancing device 200 , an edge routing service device 300 , an application gateway 400 , a backend service device 500 , and a front-end service device 600 .

[0057] It is understood that the load balancing device 200, edge routing service device 300, and application gateway 400 in this application each provide a layer of routing service. Specifically, as shown in Figure 1B, a schematic diagram of the hierarchical structure of the service routing provided in this application is provided, which includes three layers of routing services: load balancing service, edge routing service, and application gateway.

[0058] The client 100 can provide users with access to services, such as displaying a user interface for an application that provides the service. In addition, the client 100 can initiate an access request to the cloud platform, which will then pass through the load balancing device 200 deployed at the edge of the cloud platform.

[0059] In some embodiments, the access request in the present application may include at least one of the following information:

[0060] Information 1: information about the target service requested by the client 100, such as the name or identifier of the target service.

[0061] Information 2: The domain name usually points to the first layer of the API access path, that is, the IP address pointed to by the DNS resolution is the first layer of routing, such as the address pointing to the load balancing device 200.

[0062] Information 3: API address, also called API address, for example, the API address can be the address of the backend service device 500 where the target service is located or the address of the front-end service device 600. In addition, the API address can also be used to indicate the API request path.

[0063] Information 4: Header information, such as additional information including some user identity information.

[0064] It can be understood that the information included in the access request provided in this application may include but is not limited to the above examples, and may also include more or less information, which is not specifically limited here.

[0065] In some embodiments, the client 100 may be a client computer, a smart phone, a tablet computer, etc. that uses cloud services, but is not limited thereto.

[0066] The load balancing device 200 can be used to configure a secure socket layer (SSL) certificate and a domain name (Domain Name), that is, its setting function can be to configure an SSL certificate and a domain name.

[0067] As can be understood, load balancing is a computer technology used to distribute load among multiple computers (computer clusters), network connections, central processing units (CPUs), disk drives, or other resources to optimize resource usage, maximize throughput, minimize response time, and avoid overload.

[0068] A domain name, also known as a network domain, is the name of a computer or a group of computers on the Internet, consisting of a string of names separated by dots. It is used to locate the computer (sometimes also refers to the geographical location) during data transmission.

[0069] An SSL certificate is a type of digital certificate, also known as an SSL server certificate. The security protocol of an SSL certificate is primarily used to authenticate users and servers, encrypt and hide transmitted data, and ensure data integrity during transmission. For example, an SSL certificate can be used to establish encrypted and trusted transmission using the Hypertext Transfer Protocol Secure (HTTPS). Generally, applying for an SSL certificate requires a domain name, and the domain name will be identified during the application process before obtaining the latest SSL certificate.

[0070] In some embodiments, the load balancing device 200 can provide one or more load balancing services, allowing different domain names to be handled through different load balancing services. It is understood that for different domain names, if a single load balancing service does not support multiple certificates, multiple load balancing services can be used to support them. Because the resources of multiple load balancing services are naturally isolated, new load balancing services can be allocated to customers for independent processing, or customers can purchase new load balancing services themselves. In this way, regardless of the customer's customized domain name requirements, the load balancing device 200 can support them.

[0071] In some embodiments, the newly added load balancer in the load balancing device 200 of the present application can be used to configure a user-defined domain name and support certificate modification. For example, the user-defined domain name and certificate modification can be implemented by different newly added load balancers.

[0072] In some embodiments, each load balancer in this application can be configured with one or more certificates and one or more domain names, wherein each certificate supports one or more domain names.

[0073] In some embodiments, the load balancing device 200 may be an independent load balancer, or may be integrated into a switching device, but is not limited thereto.

[0074] It can be understood that in the scenario where the customer customizes the domain name, this application only needs to configure the load balancing device 200, and only the staff of the load balancing department participate in the configuration, making the customized requirements easy to implement.

[0075] Edge routing service device 300 is used to perform API path conversion, header processing, security configuration, and request classification on received access requests. Specifically, the functions of edge routing service device 300 include, but are not limited to, API path conversion, header processing, security configuration, and request classification.

[0076] It can be understood that in conventional technologies, functions such as API path conversion, header processing, security configuration, and request classification are implemented by the application gateway. However, this application implements these functions by introducing the edge routing service device 300, which can greatly alleviate the pressure on the application gateway.

[0077] In some embodiments, the edge routing service device 300 can implement the user's customized request path through the API path conversion function. In this case, the edge routing service device 300 can define a conversion rule for the user's customized request path to perform API path conversion on the API request path corresponding to the access request initiated by the user from the client 100, for example, converting the API address in the access request from the host address corresponding to the target service to the slave address corresponding to the target service.

[0078] In some embodiments, the edge routing service device 300 can filter some content in the header information of the access request through the header processing function, such as filtering out private data such as the user's bank card password or filtering out some computing rules of the cloud service provider.

[0079] In some embodiments, the edge routing service device 300 can authenticate the access request through the security configuration function. If the authentication is successful, the access request will be forwarded downstream. If the authentication is unsuccessful, the access request will be intercepted to ensure the security of the service.

[0080] In some embodiments, the edge routing service device 300 can use the request classification function to identify whether the service requested by the access request is a front-end service or a back-end service. For example, if the API address of the access request is identified as pointing to a back-end service, the access request is forwarded to the application gateway 400. If the access request is identified as requesting static resources such as images, the access request is forwarded directly to the front-end service device 600 without being forwarded to the application gateway 400, greatly alleviating the pressure on the application gateway 400.

[0081] It can be understood that edge routing service is a network service that is usually deployed at the edge of cloud computing. It is responsible for verifying, routing and forwarding requests, so that devices and clients connected to edge nodes can directly access back-end services and obtain response results. It has the advantages of close distance, flexible adaptability, high reliability and data security.

[0082] In some embodiments, edge routing services can be implemented in a variety of ways, such as nginx, traefik, envoy, etc., or services developed by cloud service providers themselves. Among them, traefik is a reverse proxy and load balancing service, and envoy is a high-performance non-blocking service proxy program developed in C++ with built-in service discovery and advanced load balancing.

[0083] Application Gateway 400: It is used to authenticate access requests and forward them to the real backend service. It can also encapsulate some common functions, such as adding some monitoring information. That is, the set functions of Application Gateway 400 are authentication and forwarding.

[0084] In some embodiments, the authentication of the application gateway 400 may include: authenticating and authorizing the user to improve the security of the network. For example, a security token may be added or verified in the user's request to ensure that the user can only access resources for which he or she has permission.

[0085] In some other embodiments, the application gateway 400 can also support conversion between multiple protocols, such as conversion between Hyper Text Transfer Protocol (HTTP) and HTTPS, conversion between WebSocket (a full-duplex communication protocol based on TCP) and Transmission Control Protocol (TCP), etc., so as to support different applications and client access.

[0086] It can be understood that the application gateway 400 in the present application has simpler functions than the application gateway in conventional technology, so the application gateway 400 has higher working efficiency and is easier to implement.

[0087] In some embodiments, the monitoring information may be used to monitor the user's identity information, such as authenticating the user's username and password, but is not limited thereto.

[0088] Backend service device 500: used to process the received access request accordingly and return the processing result to the application gateway 400, so that the application gateway 400 processes the processing result again and returns it to the edge routing service 300, and returns the processing result to the client 100 through the load balancing 200.

[0089] Front-end service device 600 is used to provide front-end services, such as web front-end services, which is the process by which users send requests to servers through browsers to obtain data, services, or resources. Among them, front-end services are mainly responsible for processing user requests, rendering pages, presenting data, and enabling interactions.

[0090] For example, in the process of accessing a web page, the front-end service device 600 provides the client with the structural style of the web page, and the back-end service device 500 provides the data of the web page. When the structural style and data of the web page are combined, the web page that the user sees becomes.

[0091] In some embodiments, the edge routing service device 300, application gateway 400, front-end service device 600 and back-end service device 500 provided in this application can all be servers, such as independent servers or cloud servers, etc., and this application does not make specific limitations on this.

[0092] In some embodiments of the present application, in the service routing scenario shown in FIG1A , the data flow path of the backend service access request process is: client 100 → load balancing device 200 → edge routing service device 300 → application gateway 400 → backend service device 500, and the reverse response data flow path is: backend service device 500 → application gateway 400 → edge routing service device 300 → load balancing device 200 → client 100. Throughout the entire process, the edge routing service device 300 and the application gateway 400 play an important bridging role, realizing the complete process from client request to backend service response.

[0093] In other embodiments of the present application, in the service routing scenario shown in FIG1A , the data flow path of the front-end service access request process is: client 100 → load balancing device 200 → edge routing service device 300 → front-end service device 600, and the reverse response data flow path is: front-end service device 600 → edge routing service device 300 → load balancing device 200 → client 100. It can be understood that because the edge routing service device 300 can classify requests, access requests for static resources used by the front-end are not forwarded to the application gateway 400 but directly forwarded to the front-end service device 600.

[0094] Next, in conjunction with FIG2 , a flow chart of a routing method for a service provided in an embodiment of the application is provided. This method can be applied to the routing scenario of the service shown in FIG1A and implemented through the hierarchical structure of the routing service shown in FIG1B . Specifically, the method can include the following steps:

[0095] S201: The client 100 sends an access request for a target service to the load balancing device 200.

[0096] It can be understood that the above target service can be a front-end service or a back-end service.

[0097] In some embodiments, the access request includes at least: a domain name and a name of a target service, but is not limited thereto.

[0098] S202: The load balancing device 200 performs a first process on the access request according to the corresponding set function.

[0099] In some embodiments, the configuration function of the load balancing device 200 may include configuring an SSL certificate and a domain name. The first processing of the access request by the load balancing device 200 may include: determining the domain name in the access request, and after determining that the domain name is the same as a preset domain name, configuring an SSL certificate associated with the domain name for the access request.

[0100] In some embodiments, as shown in FIG3 , the load balancing device 200 in the present application includes services such as load balancing service 1, load balancing service 2, and load balancing service 3. Load balancing service 1 is used to authenticate and configure SSL certificates for domain names 1 to 4 pre-set by the cloud service provider, load balancing service 2 is used to authenticate and configure SSL certificates for domain name 5 defined by the customer, and load balancing service 3 is used to authenticate and configure SSL certificates for domain names 6 to 10 pre-set by the cloud service provider.

[0101] It is understood that the load balancing service 2 can be configured with a custom domain name by the customer, so that the load balancing service 2 supports authentication of the custom domain name. For example, the load balancing service 2 can be a service purchased separately by the user.

[0102] In some embodiments, as shown in FIG4 , in response to a customer's customization requirements for a custom domain name, when a customer initiates an access request containing a user-defined domain name 5 through client 100, load balancing device 200 can authenticate the custom domain name in the access request through load balancing service 2 and, upon successful authentication, forward the access request to a downstream device, thereby fulfilling the customization requirement. Since domain name-related setting functions are implemented by load balancing device 200, the customization requirement for a custom domain name only requires the load balancing department within the cloud service provider to configure and implement the load balancing device 200, without requiring the involvement of other departments within the cloud service provider or other routing service layer devices, making the customization requirement easy to implement.

[0103] In some embodiments, some load balancing services in the load balancing device 200 of the present application may also be configured to support modification of SSL certificates, such as allowing the cloud service provider's original SSL certificate corresponding to certain domain names to be modified to a customer-configured SSL certificate. For example, load balancing service 3 in the load balancing device 200 may be configured to support modification of the original SSL certificate 1 configured for domain name 6 to SSL certificate 2.

[0104] As shown in Figure 5, in response to a customer's customized certificate modification requirements, when a customer initiates an access request containing domain name 6 via client 100, load balancing device 200 can authenticate domain name 6 in the access request through load balancing service 3. After successful authentication, it configures a new SSL certificate 2 for domain name 6 and then forwards the access request to the downstream device, thus fulfilling this customization requirement. Since the certificate modification-related configuration functions are implemented by load balancing device 200, this customization requirement only requires the load balancing department within the cloud service provider to configure load balancing device 200 and does not require the involvement of other routing service layer devices, making this customization requirement easy to implement.

[0105] S203: The load balancing device 200 forwards the first processed access request to the edge routing service device 300.

[0106] In some embodiments, the load balancing device 200 may also pre-store the address of the edge routing service device 300, and the load balancing device 200 may forward the processed access request to the edge routing service device 300 according to the address. Accordingly, the edge routing service device 300 will receive the access request.

[0107] In some embodiments, the content of the access request does not change after the first processing. For example, when the first processing is to verify the domain name, the content of the access request may not be changed.

[0108] In some other embodiments, the content in the access request may change after the first processing. For example, when the first processing is to verify the domain name and configure the SSL certificate, the first processing process may add the configured SSL certificate to the access request.

[0109] S204: The edge routing service device 300 performs a second process on the access request according to the corresponding set function.

[0110] In some embodiments, the edge routing service device 300 may be configured to perform API path conversion, header processing, security configuration, and request classification. Specifically, the second processing performed by the edge routing service device 300 on the access request may be one or more of API path conversion, header processing, security configuration, and request classification.

[0111] In some embodiments, in response to a customer's API path conversion requirements, the edge routing service device 300 pre-sets a conversion rule for API path conversion. For example, the conversion rule may include converting the address corresponding to the API path according to the user's requirements. For example, the conversion rule for API path conversion may include converting API path 1 to API path 2, i.e., converting API address 1 corresponding to API path 1 included in the access request to API address 2 corresponding to API path 2.

[0112] As shown in Figure 6, in response to the customer's API path conversion requirements, for an access request containing API address 1, the edge routing service device 300 can convert the API address 1 in the access request into API address 2, so that the access request contains API address 2, and forward the access request to the downstream device to achieve this customized requirement. Since the API path conversion-related setting functions are implemented by the edge routing service device 300, this customized requirement only requires the relevant responsible department of the edge routing service in the cloud service provider to configure the edge routing service device 300, and does not require the participation of other routing service layer devices, making this customized requirement easy to implement.

[0113] S205 : corresponding to the target service being a front-end service, the edge routing service device 300 forwards the second processed access request to the front-end service device 600 .

[0114] In some embodiments, in response to a client's request classification requirements, the edge routing service device 300 can be configured to distinguish whether the target service requested by the access request is classified as a front-end service or a back-end service, thereby enabling flexible request forwarding. For example, the edge routing service device 300 can identify the name of the target service in the access request to identify the classification of the target service. Of course, the methods by which the edge routing service device 300 identifies the classification of the target service include, but are not limited to, the above examples, and can also be other achievable methods.

[0115] As shown in Figure 7, for an access request containing the target service name 1, if the edge routing service device 300 identifies that name 1 belongs to a front-end service, it forwards the access request to the front-end service device 600. If the edge routing service device 300 identifies that name 1 belongs to a back-end service, it forwards the access request to the application gateway 400. In this case, the front-end service will not be routed to the application gateway 400, alleviating the pressure on the application gateway 400. In this case, the processing of the access request by the edge routing service device 300 can be request classification.

[0116] Similarly, for other customized requirements of customers such as security configuration and header processing, the department responsible for edge routing services in the cloud service provider only needs to configure and implement the edge routing service device 300, and there is no need for the participation of other routing service layer devices, making the customized requirements easy to implement.

[0117] In some embodiments, the content of the access request does not change after the second processing. For example, the content of the access request may not be changed when the second processing is a security configuration.

[0118] In some other embodiments, the content in the access request may change after the second processing. For example, when the second processing is API path conversion, the second processing process may include adding a converted API address to the access request.

[0119] S206: corresponding to the target service being a backend service, the edge routing service device 300 forwards the access request after the second processing to the application gateway 400. For example, the second processing may include request classification.

[0120] As shown in FIG. 7 , when the edge routing service device 300 identifies that the name 1 of the target service belongs to a backend service, it forwards the access request to the application gateway 400 .

[0121] S207: The application gateway 400 performs a third process on the received access request according to the corresponding set function.

[0122] In some embodiments, the set functions of the application gateway 400 include authentication and forwarding, that is, the third processing can be authentication and forwarding of the received request.

[0123] For example, the application gateway 400 can add or verify monitoring information such as a security token in the user's access request to ensure that the user can only access resources for which they have permission, thereby improving the security of the service. In this case, the third processing can include adding or verifying monitoring information such as a security token in the access request and forwarding it to the backend service device 500.

[0124] It can be understood that compared with the application gateway in conventional technology, the application gateway 400 in this application does not need to perform functions such as configuring domain names, SSL certificates, request classification, etc., that is, the application gateway 400 does not need to support complex functions such as load balancing. Therefore, the application gateway 400 is relatively simple and easy to implement and has higher work efficiency.

[0125] S208 : The application gateway 400 forwards the access request after the third processing to the backend service device 500 .

[0126] It is understandable that the application gateway 400 can determine the address of the backend service device 500 from the name of the target service in the access request and forward it.

[0127] In some implementations, the above S201 to S208 mainly describe the data flow after the access request is initiated from the client 100. Then the access response corresponding to the access request can be returned to the client 100 from the back-end service device 500 or the front-end service device 600 along the same path to respond to the customer's request and provide services. It can be understood that the processing process of the data flow of the access response in this application is still handled by the above-mentioned application gateway 400, edge routing service device 300 and load balancing device 200 according to their respective set functions. For example, for the security setting function, the edge routing service device 300 can perform security configuration related processing on the received access response, and this application will not go into details about this.

[0128] In some embodiments, the content of the access request does not change after the third processing. For example, when the third processing is routing forwarding, the content of the access request may not be changed.

[0129] In some other embodiments, the content in the access request may be changed after the third processing. For example, when the third processing is to add monitoring information, the third processing may include adding monitoring information to the access request.

[0130] In this way, the service routing method provided by this application can alleviate the pressure on load balancing and application gateways by dividing the various functions of the cloud platform's routing services into three levels: load balancing, edge routing, and application gateways. Thus, the service routing is layered and divided according to the set functions corresponding to each layer of routing services, making the functional division of the three-layer routing services clear, so that the customer's customized needs can be dispersed to the responsible teams of different services for implementation, making it easy to realize the customer's customized needs. In addition, the advantages of each routing service layer are maximized, making the cloud platform's routing process for services more efficient.

[0131] In some embodiments, the hardware structures of the load balancing device 200, edge routing service device 300 and application gateway 400 of the routing service provided in this application are described. For example, these devices can all be called electronic devices.

[0132] Referring now to FIG8 , a block diagram of an electronic device 1400 is shown, in accordance with one embodiment of the present application. FIG8 schematically illustrates an example electronic device 1400, in accordance with various embodiments. In one embodiment, the electronic device 1400 may include one or more processors 1404, system control logic 1408 coupled to at least one of the processors 1404, system memory 1412 coupled to the system control logic 1408, non-volatile memory (NVM) 1416 coupled to the system control logic 1408, and a network interface 1420 coupled to the system control logic 1408.

[0133] In some embodiments, the processor 1404 may include one or more single-core or multi-core processors. In some embodiments, the processor 1404 may include any combination of general-purpose processors and specialized processors (e.g., graphics processors, application processors, baseband processors, etc.). In embodiments where the electronic device 1400 employs an enhanced NodeB (eNB) or a radio access network (RAN) controller, the processor 1404 may be configured to execute various embodiments, for example, the embodiment shown in FIG2 .

[0134] In some embodiments, system control logic 1408 may include any suitable interface controller to provide any suitable interface to at least one of processors 1404 and / or any suitable device or component in communication with system control logic 1408 .

[0135] In some embodiments, the system control logic 1408 may include one or more memory controllers to provide an interface to the system memory 1412. The system memory 1412 may be used to load and store data and / or instructions. In some embodiments, the system memory 1412 of the electronic device 1400 may include any suitable volatile memory, such as a suitable dynamic random access memory (DRAM).

[0136] NVM / memory 1416 may include one or more tangible, non-transitory computer-readable media for storing data and / or instructions. In some embodiments, NVM / memory 1416 may include any suitable non-volatile memory such as flash memory and / or any suitable non-volatile storage device, such as at least one of a hard disk drive (HDD), a compact disc (CD) drive, and a digital versatile disc (DVD) drive.

[0137] NVM / storage 1416 may include a portion of storage resources on the device on which electronic device 1400 is installed, or it may be accessible to the device but not necessarily part of the device. For example, NVM / storage 1416 may be accessed over a network via network interface 1420.

[0138] In particular, system memory 1412 and NVM / storage 1416 may include, respectively, a temporary copy and a permanent copy of instructions 1424. Instructions 1424 may include instructions that, when executed by at least one of processors 1404, cause electronic device 1400 to implement the method illustrated in FIG. 2 . In some embodiments, instructions 1424, hardware, firmware, and / or software components thereof may additionally or alternatively reside in system control logic 1408, network interface 1420, and / or processor 1404.

[0139] The network interface 1420 may include a transceiver for providing a radio interface for the electronic device 1400, thereby communicating with any other suitable devices (such as a front-end module, an antenna, etc.) via one or more networks. In some embodiments, the network interface 1420 may be integrated with other components of the electronic device 1400. For example, the network interface 1420 may be integrated with at least one of the processor 1404, the system memory 1412, the NVM / storage 1416, and a firmware device (not shown) having instructions. When at least one of the processors 1404 executes the instructions, the electronic device 1400 implements the method shown in FIG. 2 .

[0140] The network interface 1420 may further include any suitable hardware and / or firmware to provide a multiple-input multiple-output radio interface. For example, the network interface 1420 may be a network adapter, a wireless network adapter, a telephone modem, and / or a wireless modem.

[0141] In one embodiment, at least one of the processors 1404 may be packaged together with logic for one or more controllers of the system control logic 1408 to form a system-in-package (SiP). In one embodiment, at least one of the processors 1404 may be integrated on the same die with logic for one or more controllers of the system control logic 1408 to form a system-on-chip (SoC).

[0142] Electronic device 1400 may further include an input / output (I / O) device 1432. I / O device 1432 may include a user interface that enables a user to interact with electronic device 1400; peripheral component interfaces may also be designed to enable peripheral components to interact with electronic device 1400. In some embodiments, electronic device 1400 may further include a sensor for determining at least one of environmental conditions and location information related to electronic device 1400.

[0143] In some embodiments, the user interface may include, but is not limited to, a display (e.g., an LCD display, a touch screen display, etc.), a speaker, a microphone, one or more cameras (e.g., a still image camera and / or a video camera), a flashlight (e.g., an LED flash), and a keyboard.

[0144] In some embodiments, the peripheral component interface may include, but is not limited to, a non-volatile memory port, an audio jack, and a power interface.

[0145] In some embodiments, the sensors may include, but are not limited to, a gyroscope sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of or interact with the network interface 1420 to communicate with components of a positioning network (e.g., Global Positioning System (GPS) satellites).

[0146] In some embodiments, the present application provides a readable medium having instructions stored thereon, which, when executed on an electronic device, causes the electronic device to execute the routing service method of the present application.

[0147] The various embodiments of the mechanisms disclosed in this application can be implemented in hardware, software, firmware, or a combination of these implementation methods. The embodiments of the present application can be implemented as a computer program or program code executed on a programmable system, which includes at least one processor, a storage system (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device.

[0148] Program code can be applied to input instructions to perform the functions described herein and generate output information. The output information can be applied to one or more output devices in a known manner. For purposes of this application, a processing system includes any system having a processor such as, for example, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), or a microprocessor.

[0149] Program code can be implemented with a high-level programming language or an object-oriented programming language to communicate with the processing system. Where necessary, program code can also be implemented in assembly language or machine language. In fact, the mechanism described in this application is not limited to the scope of any particular programming language. In either case, the language can be a compiled language or an interpreted language.

[0150] In some cases, the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented as instructions carried or stored on one or more temporary or non-temporary machine-readable (e.g., computer-readable) storage media, which may be read and executed by one or more processors. For example, the instructions may be distributed over a network or through other computer-readable media. Therefore, a machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), including but not limited to floppy disks, optical disks, optical discs, compact disc read-only memories (CD-ROMs), magneto-optical disks, read-only memories (ROMs), random access memories (RAMs), erasable programmable read-only memories (EPROMs), electrically erasable programmable read-only memories (EEPROMs), magnetic or optical cards, flash memory, or a tangible machine-readable memory for transmitting information (e.g., carrier waves, infrared signals, digital signals, etc.) using the Internet in electrical, optical, acoustic, or other forms of propagation signals. Therefore, a machine-readable medium includes any type of machine-readable medium suitable for storing or transmitting electronic instructions or information in a form readable by a machine (e.g., a computer).

[0151] In the accompanying drawings, some structural or method features may be shown in a particular arrangement and / or order. However, it should be understood that such a particular arrangement and / or order may not be required. Rather, in some embodiments, these features may be arranged in a manner and / or order different from that shown in the illustrative drawings. In addition, the inclusion of a structural or method feature in a particular figure does not imply that such feature is required in all embodiments, and in some embodiments, such features may not be included or may be combined with other features.

[0152] It should be noted that the units / modules mentioned in the various device embodiments of the present application are all logical units / modules. Physically, a logical unit / module can be a physical unit / module, or a part of a physical unit / module, or can be implemented as a combination of multiple physical units / modules. The physical implementation of these logical units / modules themselves is not the most important. The combination of functions implemented by these logical units / modules is the key to solving the technical problems raised by this application. In addition, in order to highlight the innovative part of this application, the above-mentioned device embodiments of this application do not introduce units / modules that are not closely related to solving the technical problems raised by this application. This does not mean that other units / modules do not exist in the above-mentioned device embodiments.

[0153] It should be noted that in the examples and description of this patent, relational terms such as first and second, etc. are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device that includes a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "including a" does not exclude the presence of other identical elements in the process, method, article or device that includes the element.

[0154] Although the present application has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the application.

Claims

1. A service routing method, characterized in that: Applied to a service routing system, the service routing system includes a load balancing service, an edge routing service and a gateway service; The method comprises: The load balancing service receives an access request, where the access request is used to request a target service; The load balancing service performs a first process on the access request according to a first set function, and forwards the access request after the first process to the edge routing service; The edge routing service performs a second process on the access request according to a second set function, and forwards the access request after the second process to the gateway service; The gateway service performs a third process on the access request according to a third setting function, and forwards the access request after the third process to a target service end, and the target service end is used to provide the target service; The first setting function, the second setting function and the third setting function are all different.

2. The method according to claim 1, characterized in that: The edge routing service processes the access request according to the second setting function and forwards the access request to the gateway service, including: The edge routing service performs the second processing on the access request according to the second setting function, and determines that the target service is a backend service corresponding to the second setting function, and forwards the access request to the gateway service; wherein the target service end is used to provide backend services.

3. The method according to claim 2, characterized in that The method further comprises: The edge routing service performs the second processing on the access request according to the second setting function, and determines that the target service is a front-end service corresponding to the second setting function, and forwards the access request to the target server, wherein the target server is used to provide front-end services.

4. The method according to claim 1, characterized in that: The first setting function, the second setting function and the third setting function are determined based on at least one of the execution efficiency and performance of the factory configuration functions of the load balancing service, the edge routing service and the gateway service.

5. The method according to claim 1, characterized in that The first setting function includes: configuring a domain name and configuring a secure socket layer SSL certificate.

6. The method according to claim 5, characterized in that The load balancing service includes a plurality of sub-load balancing services; Part of the multiple sub-load balancing services are used to configure a custom domain name, or part of the multiple sub-load balancing services support modification of SSL certificates according to customer requirements.

7. The method according to any one of claims 1 to 6, characterized in that The second setting function includes at least one of the following: request path conversion, security configuration, header processing, and request classification; wherein the request classification is used to distinguish whether the target service is a front-end service or a back-end service.

8. The method according to any one of claims 1 to 5, characterized in that The third setting function includes at least one of the following: authenticating the access request, forwarding the access request to the target server, and adding monitoring information to the access request.

9. The method according to claim 1, characterized in that: The edge routing service can be implemented through nginx, traefik, envoy or a custom service of the service provider.

10. A routing system for a service, characterized in that: The service routing system includes load balancing service, edge routing service and gateway service; The load balancing service is used to receive an access request, perform a first process on the access request according to a first set function, and forward the access request after the first process to the edge routing service, wherein the access request is used to request a target service; The edge routing service is used to perform a second process on the access request according to a second set function, and forward the access request after the second process to the gateway service; The gateway service is used to perform a third process on the access request according to a third setting function, and forward the access request after the third process to a target server, and the target server is used to provide the target service; The first setting function, the second setting function and the third setting function are all different.

11. A readable medium, characterized in that: The readable medium stores instructions, which, when executed on an electronic device, enable the electronic device to execute the service routing method according to any one of claims 1 to 9.

12. An electronic device, characterized in that: include: A memory for storing instructions executed by one or more processors of an electronic device, and a processor, which is one of the processors of the electronic device, for executing the service routing method described in any one of claims 1 to 9.

Citation Information

Patent Citations

  • Load balancing method and device based on application market architecture

    CN114143324A

  • Service routing method and system of cloud native platform microservice gateway

    CN115604199A

  • Service routing method, system, equipment and medium

    CN116527740A

  • Method, device and computer program product for managing network system

    US20190387051A1