Service providing method and apparatus, electronic device, and storage medium

Abstract

This application provides a service provision method, apparatus, electronic device, and storage medium. The method includes: receiving service request information sent by a client within a first region to which an edge node belongs, the service request information including payload data; decapsulating the service request information to obtain the payload data; sending the payload data to a corresponding server in a central node according to the service type requested in the service request information; and receiving service response information sent by the central node and sending the service response information to the client.

Description

Technical Field

[0001] This application relates to the field of cloud computing technology, and in particular to a service delivery method, apparatus, electronic device, and storage medium. Background Technology

[0002] In traditional cloud computing service delivery models, cloud service providers typically employ either a central node model or an edge node model to provide services to users. In the central node model, cloud service providers utilize server clusters, either by building their own data centers or partnering with data centers, to provide services to clients across the entire network. However, because some clients are physically far from the central node, network reach is compromised (i.e., longer service request latency and higher packet loss rates). In the edge node model, cloud service providers purchase data center racks and bandwidth from internet service providers (ISPs) to build edge nodes within their ISPs' Internet Data Centers (IDCs) to provide services. However, each edge node requires replicating a complete public cloud technology stack, leading to drawbacks in resource reuse, construction costs, and cache hit rates. Summary of the Invention

[0003] This application provides a service provision method, apparatus, electronic device, and storage medium to address problems existing in the related art.

[0004] In a first aspect, embodiments of this application provide a service provision method applied to an edge node, wherein the edge node is communicatively connected to a central node. The method includes: receiving service request information sent by a client within a first region to which the edge node belongs, the service request information including payload data; decapsulating the service request information to obtain the payload data; sending the payload data to a corresponding server in the central node according to the service type requested by the service request information; and receiving service response information sent by the central node and sending the service response information to the client.

[0005] Secondly, embodiments of this application provide a service providing apparatus deployed at an edge node, the edge node being communicatively connected to a central node. The apparatus includes: a request receiving unit configured to receive service request information sent by a client within a first region to which the edge node belongs, the service request information including payload data; a decapsulation unit configured to decapsulate the service request information to obtain the payload data; a request sending unit configured to send the payload data to a corresponding server in the central node according to the service type requested by the service request information; and a response sending unit configured to receive service response information sent by the central node and send the service response information to the client.

[0006] Thirdly, embodiments of this application provide an electronic device, including a memory, a processor, and a computer program stored in the memory, wherein the processor, when executing the computer program, implements the method described in any of the above-mentioned embodiments.

[0007] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the method described in any of the above-mentioned embodiments.

[0008] Compared with the prior art, this application has the following advantages:

[0009] According to the embodiments of this application, the client accesses the nearest edge node, which provides the client with service access capabilities. The central node centralizes storage and computing capabilities to provide corresponding services to the client. By utilizing the combination of edge and central nodes, the edge nodes receive and parse client service requests, allowing the central node to focus on providing cloud computing services. This improves the resource utilization rate, cache hit rate, and network reach rate of the central node, while reducing the construction cost of the edge nodes and providing users with more efficient services.

[0010] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application, it can be implemented according to the contents of the specification. In order to make the above and other objects, features and advantages of this application more obvious and understandable, specific embodiments of this application are given below. Attached Figure Description

[0011] In the accompanying drawings, unless otherwise specified, the same reference numerals throughout the various drawings denote the same or similar parts or elements. These drawings are not necessarily drawn to scale. It should be understood that these drawings depict only some embodiments according to this application and should not be construed as limiting the scope of this application.

[0012] Figure 1 This is a schematic diagram illustrating a service provision scheme according to an embodiment of this application;

[0013] Figure 2 This is a flowchart illustrating a service provision method according to an embodiment of this application;

[0014] Figure 3 This is a structural block diagram illustrating a service providing apparatus according to an embodiment of this application; and

[0015] Figure 4 This is a block diagram illustrating an electronic device according to an embodiment of this application. Detailed Implementation

[0016] In the following description, only certain exemplary embodiments are briefly described. As those skilled in the art will recognize, the described embodiments can be modified in various ways without departing from the concept or scope of this application. Therefore, the drawings and description are considered to be exemplary in nature and not restrictive.

[0017] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and all of them fall within the protection scope of the embodiments of this application.

[0018] In a related technology prior to this application, cloud computing service providers employed a central node model to provide cloud computing services to users. In this model, the service provider, either by building its own data center or partnering with another, has complete control over the infrastructure (power, network, server racks, etc.) and IDC (Internet Data Center) operations, and connects to multiple ISP lines. The node scale ranges from several thousand to hundreds of thousands of devices, utilizing server clusters to provide cloud computing services to clients across the entire network. However, because the central node is unique, some clients are physically far from it, resulting in network reach defects; that is, requests sent from clients to the central node experience longer latency and higher packet loss rates.

[0019] In another related technology prior to this application, cloud computing service providers adopted an edge node model to provide cloud computing services to users. In this model, the service provider purchases data center racks and bandwidth from an operator and builds edge nodes within that operator's data center. The node scale is typically limited to less than one thousand devices, providing cloud computing services to clients in a single region. However, each edge node requires replicating a complete public cloud technology stack; that is, each edge node repeatedly deploys a large number of computing devices, storage devices, virtualization software, caching components, etc., resulting in low resource reuse and cache hit rates, and high construction costs.

[0020] In view of this, embodiments of this application provide a solution for providing services to clients using a combination of edge nodes and central nodes, thereby solving all or part of the problems existing in the aforementioned related technologies. To more clearly illustrate the service provision solution provided in the embodiments of this application, the following is combined with... Figure 1 The service provision plan is explained. Figure 1 This is a schematic diagram illustrating a service provision scheme according to an embodiment of this application. A cloud computing service provider constructs multiple edge nodes within a region, eliminating the need to deploy a large number of computing devices, storage devices, virtualization software, caching components, etc., on these edge nodes. The edge nodes only need to provide service access and protocol offloading capabilities to clients, receive cloud computing service requests sent by clients, and parse these requests. Clients can access the nearest edge node based on physical distance. Alternatively, a cloud computing service provider constructs at least one central node within a region, deploying a large number of computing devices, storage devices, virtualization software, caching components, etc., on the central node to provide cloud computing services to clients. The edge nodes, acting as reverse proxies for the central node, can forward received cloud computing service requests from clients to the central node, which then provides the cloud computing services to the clients. Based on this service provision scheme, edge nodes can, for example, provide access to cloud computing service requests and offload network transmission protocols for clients, sending client service requests to the corresponding central node. This eliminates the need to build redundant computing and storage devices, thus saving on edge node construction costs. Central nodes utilize a centralized set of computing and storage devices to provide clients with high-performance caching, storage, and computing services, thereby improving resource reuse and cache hit rates. Clients accessing the nearest edge node also reduces service request latency and packet loss rates.

[0021] One embodiment of this application provides a service provision method 200, which is applied to an edge node that is communicatively connected to a central node. The following will refer to... Figure 2 The service provision method 200 of this application is described. Figure 2 This is a flowchart illustrating a service provision method according to an embodiment of this application. Figure 2 As shown, the service provision method 200 may include the following steps S201 to S204.

[0022] First, proceed to step S201. In step S201, receive service request information sent by a client within the first region to which the edge node belongs, the service request information including payload data.

[0023] Cloud computing service providers can deploy multiple edge nodes in each of multiple regions. In one embodiment, there can be three regions: Region 1, Region 2, and Region 3. The number of edge nodes can be determined based on the coverage area of ​​each region or the number of users in that region. For example, if the coverage area and number of users in Region 1 and Region 2 are both greater than those in Region 3, three edge nodes can be deployed in Region 1 and Region 2, and one edge node in Region 3. It should be understood by those skilled in the art that the number of regions and the number of edge nodes in each region described above are merely exemplary and are not intended to limit the scope of this application. Those skilled in the art can select the number of regions and the number of edge nodes in each region based on the technical principles of this application, as long as the technical principles of this application are implemented.

[0024] In some embodiments, an edge node is built within a first region. This edge node can receive service request information sent by clients within its first region. The client can be a mobile client, a web client, or similar. The service request information includes a header and payload data. The header contains information related to the network transport protocol used for the service request. For example, the TCP (Transmission Control Protocol) header includes source port number, destination port number, sequence number, and acknowledgment number; the HTTP (Hypertext Transfer Protocol) header includes method, URL (Uniform Resource Locator), and HTTP version information. The payload data is the data that the client needs to transmit, i.e., the specific service request content.

[0025] In one embodiment, edge nodes can receive service request information sent by clients based on their physical distance from the client. For example, there are two edge nodes in region 1, edge node A and edge node B. Edge node A is 20 km away from the client, and edge node B is 300 km away. The service request information sent by the client is received and processed by edge node A. The shorter physical distance can reduce the latency and packet loss rate of the client sending requests, providing more efficient services to the client.

[0026] Prior to step S201, the service provision method 200 further includes: opening a service interface so that the client can send the service request information based on the service interface, wherein the service interface uses an accelerated domain name and a port address as an interface identifier, and the accelerated domain name resolves to the corresponding IP address based on the client's region and the operator network used by the client.

[0027] In one embodiment, before an edge node receives service request information sent by a client within its first region, the edge node needs to open a service interface, allowing clients to send service request information to the edge node by calling this interface. This service interface uses an accelerated domain name and port address as its identifier. When a client calls this interface using the accelerated domain name, it can resolve the IP address of the edge node with the fastest access speed based on its own region and the network operator it uses, and then send the service request information to that edge node.

[0028] In one embodiment, the service interface includes at least one of the following: a cache retrieval service interface, a data storage service interface, and a computing service interface. The service interface provided by the edge node may include at least one of the following: a cache retrieval service interface, a data storage service interface, and a computing service interface. Clients can request corresponding services by calling the service interface. For example, if a client calls the cache retrieval service interface, it can request the cache retrieval service. When a client accesses a website, to retrieve content from the website more quickly, it can call the cache retrieval service interface to request the website's cached content. When a client needs to store data, it can call the data storage service interface to request the storage of this data. When a client needs to perform big data processing, machine learning model training, or other computations, it can call the computing service interface to request computation on this data or model.

[0029] In some embodiments, after step S201, the service provision method 200 further includes: verifying the identity authentication information in the service request information to verify the user identity of the client, wherein if the verification is successful, the service is provided to the client; and if the verification fails, the service is stopped from being provided to the client.

[0030] To ensure that cloud computing services are only provided to legitimate clients (i.e., clients who have already purchased cloud computing services), clients can send their authentication information along with their service request information to the edge node. In one embodiment, after purchasing cloud computing services, the client can request an access token from the edge node. Once the edge node verifies that the client has purchased cloud computing services, it issues the access token to the client. Subsequently, when the client requests cloud computing services from the edge node, it can send the access token and service request information together with the edge node. In another embodiment, after purchasing cloud computing services, the client can request a signing key from the edge node. This signing key can be an ECC-based signing key or an RSA-based signing key. Once the edge node verifies that the client has purchased cloud computing services, it issues the signing key to the client. Subsequently, when the client requests cloud computing services from the edge node, the client can digitally sign the service request information using the signing key and send the service request information and the signature value together with the edge node. Upon receiving the service request information, the edge node can verify the authentication information in the service request information to verify the client's user identity. If the verification passes, the edge node can proceed with subsequent processing to provide cloud computing services to the client; if the verification fails, the edge node refuses to provide cloud computing services to the client. Those skilled in the art should understand that the types of client authentication information described above are merely exemplary and are not intended to limit this application. Those skilled in the art can select the type of client authentication information based on the technical principles of this application, as long as the technical principles of this application are implemented.

[0031] Next, proceed to step S202. In step S202, the service request information is decapsulated to obtain the payload data.

[0032] Edge nodes can expose service interfaces for different network transport protocols, such as HTTP, TCP, and HTTPS (Hypertext Transfer Protocol Secure). Clients send service request information to the edge node by calling these different network transport protocol service interfaces. In one embodiment, the client sends the service request information to the edge node using the HTTP protocol by calling the edge node's exposed HTTP service interface. This service request includes not only payload data (i.e., the specific service request content) but also a header, which contains information related to the network transport protocol. The HTTP header includes information such as the method, URL, and HTTP version. The edge node decapsulates the service request information, i.e., strips the header, to obtain the payload data.

[0033] In one embodiment, the service request information further includes a header. Decapsulating the service request information to obtain the payload data includes: identifying the header of the service request information; and stripping the header to obtain the payload data. For example, a client sends service request information to an edge node using the HTTP protocol by calling an HTTP service interface exposed by the edge node. The TCP / IP protocol is a four-layer protocol, and the HTTP protocol belongs to the fourth layer, the application layer. Below the application layer are the transport layer, network layer, and link layer. The client needs to encapsulate the payload data layer by layer from the higher layers to the lower layers. For example, an HTTP header needs to be added at the application layer, a TCP header at the transport layer, an IP header at the network layer, and an Ethernet header at the link layer. This is because headers have fixed formats; for example, an IP header includes information such as version, header length, service type, datagram length, source IP address, and destination IP address. During the process of reading the service request information, the edge node identifies the header of the service request information according to the fixed header format of different protocols and strips the header layer by layer from the lower layers to the higher layers to obtain the payload data.

[0034] In one embodiment, the edge node not only decapsulates service request information but also offloads the network transport protocol used by the service request information. For example, the client sends service request information to the edge node using a connection-based protocol (e.g., TCP or HTTP). The edge node needs to handle establishing a connection with the client, and after the service processing is complete, the edge node also needs to handle closing the connection with the client. Therefore, the central node does not need to handle establishing and closing connections with the client according to the network transport protocol used by the client. This cumbersome processing is offloaded to the edge node, so the central node only needs to perform business-related processing, improving the service efficiency of the central node.

[0035] In one embodiment, the edge node exposes an HTTPS service interface, allowing clients to send service request information to the edge node based on the HTTPS protocol. During the use of HTTPS, the data sender and receiver need to perform two-way authentication, key exchange, and data encryption / decryption to ensure the authenticity of their identities and the confidentiality and integrity of the transmitted data. After receiving the service request information sent by the client using the HTTPS protocol, the edge node needs to negotiate a symmetric key with the client and use this symmetric key to encrypt and decrypt the transmitted data. Therefore, the central node does not need to perform key negotiation and data encryption / decryption processing with the client based on the secure transmission protocol used by the client. This cumbersome and computationally intensive processing is offloaded to the edge node, allowing the central node to focus only on business-related processing, thus improving the service efficiency of the central node.

[0036] Next, proceed to step S203. In step S203, based on the service type requested in the service request information, the payload data is sent to the corresponding server in the central node.

[0037] In some embodiments, after obtaining the payload data from the service request information, the edge node can send the payload data to the corresponding server in the central node according to the service type requested in the service request information. The edge node can obtain the service type requested by the service interface received from the service request information. For example, if the edge node receives the service request information sent by the client from the cache retrieval service interface, it can determine that the service type requested by the service request information is cache retrieval service. The central node includes servers that provide various services, such as servers that provide cache retrieval services, servers that provide data storage services, and servers that provide computing services. For example, if the service requested by the service request information is cache retrieval service, the edge node can send the payload data to the server in the central node that provides cache retrieval service, and the server in the central node that provides cache service will then provide cache retrieval service to the client.

[0038] In one embodiment, sending the payload data to the corresponding server in the central node includes: determining whether the central node of the first region is overloaded, wherein if the central node of the first region is not overloaded, the payload data is sent to the corresponding server in the central node of the first region; and if the central node of the first region is overloaded, the payload data is sent to the corresponding server in the central node of the second region.

[0039] During the process of an edge node sending payload data to the corresponding server in the central node, the edge node needs to determine whether the central node in the first region to which it belongs is overloaded. If the central node in the first region is not overloaded, it means that the central node can provide services normally, and the physical distance between the central node in the first region and the edge node is the shortest, so the payload data is sent to the corresponding server in the central node in the first region. If the central node in the first region is overloaded, it means that the central node in the first region cannot provide services normally or the service efficiency is poor, and the payload data needs to be sent to the corresponding server in the central node in the second region. The central node in the second region is not overloaded and can provide services normally.

[0040] In one embodiment, determining whether the central node of the first region is overloaded includes: determining whether the central node of the first region is overloaded based on the load parameters of the central node of the first region, wherein the load parameters include the number of connections and / or response time.

[0041] Edge nodes determine whether the central node in the first region is overloaded by obtaining its load parameters. Load parameters include the number of connections and / or response time. Each time an edge node sends data to the central node, a connection is established; therefore, the number of connections to the central node can be used as a load parameter to determine if the central node in the first region is overloaded. Response time, the total time the server spends processing incoming requests and sending responses, can also be used as a load parameter to determine if the central node in the first region is overloaded.

[0042] Edge nodes can obtain the connection count and response time of the central node in the first region and determine whether the connection count and response time are less than a predetermined threshold. If they are less than the predetermined threshold, the central node in the first region is not overloaded; otherwise, it is overloaded. In one embodiment, the central node in the first region has 30,000 connections, and the predetermined threshold for the number of connections is 20,000. Therefore, in this case, the central node in the first region is overloaded. In another embodiment, the central node in the first region has a response time of 0.5 seconds, and the predetermined threshold for the response time is 3 seconds. Therefore, in this case, the central node in the first region is not overloaded.

[0043] In one embodiment, sending the payload data to the server corresponding to the central node in the second region includes: obtaining the load parameters of multiple central nodes outside the first region and the physical distance between the multiple central nodes outside the first region and the central node in the first region; determining the central node of the second region from the multiple central nodes outside the first region, wherein the central node of the second region is the non-first region central node whose load parameter is less than a predetermined threshold and whose distance to the central node in the first region is the shortest; and sending the payload data to the server corresponding to the central node in the second region.

[0044] If the central node in the first region is determined to be overloaded, the overloaded central node will provide services slowly or stop providing services altogether, thus failing to effectively provide cloud computing services to clients. In this case, the edge node can send the payload data to the central node in the second region. When the edge node sends the payload data to the corresponding server in the central node of the second region, it needs to determine the second region from multiple regions outside the first region. The edge node needs to obtain the load parameters of multiple central nodes outside the first region and the physical distance between these multiple central nodes and the central node in the first region. Then, the edge node first needs to filter out the multiple central nodes outside the first region whose load parameters are below a predetermined threshold, and then select the central node with the shortest physical distance to the central node in the first region. This central node is determined to be the central node of the second region. The edge node then sends the payload data to the corresponding server in the central node of the second region. The central node in the second region is not overloaded and can effectively provide services to clients. Furthermore, the central node in the second region has the shortest physical distance to the edge node in the first region, which can reduce the latency and packet loss rate of client service requests, providing efficient services to clients.

[0045] Next, proceed to step S204. In step S204, the service response information sent by the central node is received and then sent to the client.

[0046] After the edge node sends the payload data to the corresponding server in the central node, the central node provides the client with the corresponding cloud computing service and sends the service response information back to the edge node. In one embodiment, if the service requested is a cache retrieval service, the corresponding service response information includes the cached data requested by the client. In another embodiment, if the service requested is a data storage service, the service response information includes information indicating whether the storage was successful or not. After receiving the service response information from the central node, the edge node sends the service response information to the client, informing the client of the result of its requested service.

[0047] Corresponding to the application scenarios and methods provided in the embodiments of this application, the embodiments of this application also provide a service providing device 300, which is deployed at an edge node, and the edge node is communicatively connected to the central node. The following figure will be referenced... Figure 3 The service providing device 300 of this application will be described. Figure 3 This is a structural block diagram illustrating a service providing apparatus according to an embodiment of this application. Figure 3 As shown, the service providing device 300 may include: a request receiving unit 301, a decapsulation unit 302, a request sending unit 303, and a response sending unit 304.

[0048] The request receiving unit 301 is configured to receive service request information sent by clients within the first region to which the edge node belongs, the service request information including payload data.

[0049] The request receiving unit 301 can be a component in an edge node, through which the edge node receives service request information sent by the client.

[0050] The decapsulation unit 302 is configured to decapsulate the service request information to obtain the payload data.

[0051] The decapsulation unit 302 can be a component in the edge node, through which the edge node decapsulates service request information.

[0052] The request sending unit 303 is configured to send the payload data to the corresponding server in the central node according to the service type requested by the service request information.

[0053] The request sending unit 303 can be a component in an edge node, through which the edge node sends payload data to the corresponding server in the central node.

[0054] The response sending unit 304 is configured to receive service response information sent by the central node and send the service response information to the client.

[0055] The response sending unit 304 can be a component in the edge node, through which the edge node sends service response information to the client.

[0056] In one embodiment, the service providing apparatus 300 further includes an interface opening unit. The interface opening unit is configured to open a service interface so that the client can send service request information based on the service interface. The service interface uses an accelerated domain name and a port address as interface identifiers. The accelerated domain name resolves to a corresponding IP address based on the client's region and the carrier network used by the client.

[0057] An interface exposure unit can be a component in an edge node, through which the edge node exposes its service interface to clients.

[0058] In one embodiment, the request sending unit 303 is further configured to determine whether the central node of the first region is overloaded. If the central node of the first region is not overloaded, the payload data is sent to the server corresponding to the central node of the first region; and if the central node of the first region is overloaded, the payload data is sent to the server corresponding to the central node of the second region.

[0059] In one embodiment, the request sending unit 303 is further configured to determine whether the central node of the first region is overloaded based on the load parameters of the central node of the first region, the load parameters including the number of connections and / or response time.

[0060] In one embodiment, the request sending unit 303 is further configured to obtain the load parameters of multiple central nodes in non-first regions and the physical distance between the multiple central nodes in non-first regions and the central node in the first region; determine the central node in the second region from the multiple central nodes in non-first regions, wherein the central node in the second region is the non-first region central node whose load parameters are less than a predetermined threshold and whose distance from the central node in the first region is the shortest; and send the payload data to the server corresponding to the central node in the second region.

[0061] In one embodiment, the service providing apparatus 300 further includes an identity authentication unit. The identity authentication unit is configured to verify the identity authentication information in the service request information to authenticate the user identity of the client, wherein if the verification is successful, the service is provided to the client; and if the verification fails, the service is stopped from being provided to the client.

[0062] The identity authentication unit can be a component in an edge node, which uses this component to verify the identity of the client user.

[0063] In one embodiment, the service interface includes at least one of the following: a cache retrieval service interface, a data storage service interface, and a computing service interface.

[0064] In one embodiment, the service request information further includes a header, and the decapsulation unit 302 is further configured to identify the header of the service request information; and strip the header to obtain the payload data.

[0065] The functions of each module in each device in the embodiments of this application can be found in the corresponding description in the above method, and they have corresponding beneficial effects, which will not be repeated here.

[0066] According to the embodiments of this application, the client accesses the nearest edge node, which provides the client with access to services. The central node centralizes storage and computing capabilities to provide corresponding services to the client. By combining edge nodes and central nodes, cloud computing services are provided to the client. This can improve the resource reuse rate and cache hit rate of the central node, as well as the network reach rate of the client, while reducing the construction cost of edge nodes, reducing the latency and packet loss rate of client service requests, and providing users with more efficient services.

[0067] According to the embodiments of this application, the central node can offload cumbersome processes related to network transmission protocols, such as connection establishment and closure, data packet decapsulation and client authentication, to the edge nodes. Furthermore, the edge nodes can send client service requests to the appropriate central node based on the load of the central node, allowing the central node to focus on providing services and offering more efficient services to the client.

[0068] Figure 4 This is a block diagram of an electronic device used to implement embodiments of this application. Figure 4 As shown, the electronic device includes a memory 401 and a processor 402. The memory 401 stores a computer program that can run on the processor 402. When the processor 402 executes the computer program, it implements the method described in the above embodiments. The number of memories 401 and processors 402 can be one or more.

[0069] The electronic device also includes:

[0070] Communication interface 403 is used to communicate with external devices and perform data exchange and transmission.

[0071] If the memory 401, processor 402, and communication interface 403 are implemented independently, they can be interconnected via a bus to communicate with each other. This bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 4The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0072] Optionally, in a specific implementation, if the memory 401, processor 402, and communication interface 403 are integrated on a single chip, then the memory 401, processor 402, and communication interface 403 can communicate with each other through an internal interface.

[0073] This application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method provided in this application.

[0074] This application also provides a chip including a processor for calling and executing instructions stored in a memory, causing a communication device with the chip installed to perform the method provided in this application.

[0075] This application also provides a chip, including: an input interface, an output interface, a processor, and a memory. The input interface, output interface, processor, and memory are connected through an internal connection path. The processor is used to execute code in the memory. When the code is executed, the processor is used to execute the method provided in the application embodiment.

[0076] It should be understood that the aforementioned processor can be a Central Processing Unit (CPU), or other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field-Programmable Gate Arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. General-purpose processors can be microprocessors or any conventional processor. It is worth noting that the processor can be a processor supporting Advanced Reduced Instruction Set Machines (ARM) architecture.

[0077] Further, optionally, the aforementioned memory may include read-only memory and random access memory. The memory may be volatile memory or non-volatile memory, or may include both. Non-volatile memory may include read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may include random access memory (RAM), which serves as an external cache. By way of example, but not limitation, many forms of RAM are available. Examples include Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0078] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions according to this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another.

[0079] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of those different embodiments or examples.

[0080] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "a plurality of" means two or more, unless otherwise explicitly specified.

[0081] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing a particular logical function or process. Furthermore, the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functionality involved.

[0082] The logic and / or steps described in the flowchart or otherwise herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus or device (such as a computer-based system, a processor-included system or other system that can fetch and execute instructions from, an instruction execution system, apparatus or device).

[0083] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. All or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware, the program being stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiments.

[0084] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. This storage medium can be a read-only memory, a disk, or an optical disk, etc.

[0085] The above description is merely an exemplary embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various variations or substitutions within the technical scope described in this application, and these should all be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A service provision method applied to an edge node, the edge node being communicatively connected to a central node, the method comprising: Receive service request information sent by a client within the first region to which the edge node belongs, the service request information including payload data; The service request information is decapsulated to obtain the payload data; Based on the service type requested in the service request information, the payload data is sent to the corresponding server in the central node; as well as Receive the service response information sent by the central node and send the service response information to the client; Sending the payload data to the corresponding server in the central node includes: Determine whether the central node of the first region is overloaded; If the central node of the first region is not overloaded, the payload data is sent to the corresponding server in the central node of the first region. If the central node of the first region is overloaded, obtain the load parameters of multiple central nodes in the non-first region and the physical distance between the multiple central nodes in the non-first region and the central node of the first region; The center node of the second region is determined from multiple center nodes outside the first region. The center node of the second region is the center node outside the first region whose load parameter is less than a predetermined threshold and whose distance to the center node of the first region is the shortest. The payload data is sent to the corresponding server in the central node of the second region.

2. The method according to claim 1, wherein, Before receiving service request information sent by clients within the first region to which the edge node belongs, the method further includes: An open service interface is provided so that the client can send the service request information based on the service interface. The service interface uses an accelerated domain name and port address as the interface identifier. When the service interface is called through the accelerated domain name, the corresponding IP address is resolved according to the client's region and the operator network used by the client.

3. The method according to claim 1 or 2, wherein, Determining whether the central node of the first region is overloaded includes: determining whether the central node of the first region is overloaded based on the load parameters of the central node of the first region, wherein the load parameters include the number of connections and / or response time.

4. The method according to claim 1 or 2, wherein, After receiving service request information sent by clients within the first region to which the edge node belongs, the method further includes: The identity verification information in the service request information is verified to authenticate the user identity of the client. If the verification passes, the service is provided to the client; and If the verification fails, services will be stopped to the client.

5. The method according to claim 2, wherein, The service interface includes at least one of the following: cache retrieval service interface, data storage service interface, and computing service interface.

6. The method according to claim 1 or 2, wherein, The service request information also includes a header, and the process of decapsulating the service request information to obtain the payload data includes: Identify the header of the service request information; Strip the header to obtain the payload data.

7. A service providing apparatus deployed at an edge node, the edge node being communicatively connected to a central node, the apparatus comprising: The request receiving unit is configured to receive service request information sent by clients within the first region to which the edge node belongs, the service request information including payload data. The decapsulation unit is configured to decapsulate the service request information to obtain the payload data; The request sending unit is configured to send the payload data to the corresponding server in the central node according to the service type requested by the service request information. as well as A response sending unit is configured to receive service response information sent by the central node and send the service response information to the client. The request sending unit is further configured to determine whether the central node of the first region is overloaded. If the central node of the first region is not overloaded, the payload data is sent to the server corresponding to the central node of the first region. If the central node of the first region is overloaded, the load parameters of multiple central nodes outside the first region and the physical distance between the multiple central nodes outside the first region and the central node of the first region are obtained. The central node of the second region is determined from the multiple central nodes outside the first region. The central node of the second region is the non-first region central node whose load parameter is less than a predetermined threshold and whose distance to the central node of the first region is the shortest. The payload data is then sent to the server corresponding to the central node of the second region.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory, wherein the processor, when executing the computer program, implements the method of any one of claims 1-6.

9. A computer-readable storage medium storing a computer program that, when executed by a processor, implements the method of any one of claims 1-6.

Images