Business processing method, apparatus, device, and storage medium

Abstract

The present disclosure provides a business processing method and device, equipment and storage medium, relates to the technical field of computers, in particular to the technical field of cloud computing. The specific implementation scheme is: through the resource agent end deployed in the edge node, in the case that the resource identifier in the self and the business request matches, the instance matching information in the business request is obtained; according to the instance matching information, the target instance is selected from each service instance deployed in the cluster to which the edge node belongs and supervised by the self; if the selection is successful, the end identifier information of the self is sent to the business control end, so that the business control end feeds back the business request according to the end identifier information; the business request is issued to the target instance for processing. According to the technology of the present disclosure, the sinking of cloud computing service to the edge node is realized, and the service pressure and service cost of cloud computing resources are reduced.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and more particularly to the field of cloud computing technology. Background Technology

[0002] The public cloud big data platform provides cloud computing resources to multi-tenant distributed data sources, integrates basic application platforms for data integration, development, and analysis, and supports upper-layer data applications such as modeling, quality monitoring, lineage analysis, and circulation services. Summary of the Invention

[0003] This disclosure provides a business processing method, apparatus, device, and storage medium.

[0004] According to one aspect of this disclosure, a business processing method is provided, applied to a resource proxy deployed on an edge node, comprising:

[0005] If the instance matches the resource identifier in the business request, obtain the instance matching information in the business request.

[0006] Based on instance matching information, the target instance is selected from the service instances deployed in the clusters of the edge nodes under its own supervision;

[0007] If the selection is successful, the terminal identification information is sent to the business control terminal so that the business control terminal can respond with the business request based on the terminal identification information.

[0008] Send the business request to the target instance for processing.

[0009] According to another aspect of this disclosure, a business processing method is also provided, applied to a resource control terminal, including:

[0010] Obtain the resource identifier from the business request and determine the resource proxy deployed on the edge node that matches the resource identifier;

[0011] Send the endpoint identifier information of the resource proxy to the business control terminal so that the business control terminal can send the instance matching information in the business request to the corresponding resource proxy terminal to select the target instance of the cluster to which the edge node under the supervision of the corresponding resource proxy terminal belongs.

[0012] The target instance is used to process business requests.

[0013] According to another aspect of this disclosure, a business processing method is also provided, applied to a business control terminal, including:

[0014] A business request that retrieves instance matching information and resource identifiers;

[0015] Send a resource identifier to the resource control terminal so that the resource control terminal can identify and return the resource agent terminal that matches the resource identifier;

[0016] Send instance matching information to the matched resource agent so that the resource agent can select a target instance from the service instances deployed in the cluster of the edge node under its supervision based on the instance matching information, and return its own terminal identification information when the selection is successful.

[0017] Send a business request to the resource proxy corresponding to the endpoint identifier information, so that the corresponding resource proxy will send the business request to the target instance for processing.

[0018] According to another aspect of this disclosure, an electronic device is also provided, comprising:

[0019] At least one processor; and

[0020] A memory that is communicatively connected to at least one processor; wherein,

[0021] The memory stores instructions that can be executed by at least one processor, which enables the at least one processor to perform any of the business processing methods provided in the embodiments of this disclosure.

[0022] According to another aspect of this disclosure, a non-transitory computer-readable storage medium storing computer instructions is also provided, wherein the computer instructions are used to cause a computer to perform any of the business processing methods provided in the embodiments of this disclosure.

[0023] According to the technology disclosed herein, cloud computing services are decentralized to edge nodes, reducing the service pressure and service costs of cloud computing resources.

[0024] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0025] The accompanying drawings are provided to better understand this solution and do not constitute a limitation of this disclosure. Wherein:

[0026] Figure 1 This is a framework diagram of a cloud platform business system provided in an embodiment of this disclosure;

[0027] Figure 2A This is a flowchart of a business processing method provided in an embodiment of this disclosure;

[0028] Figure 2B This is a schematic diagram illustrating the state change of a service instance provided in an embodiment of this disclosure;

[0029] Figure 3A This is a flowchart of another business processing method provided in this embodiment of the disclosure;

[0030] Figure 3B This is a schematic diagram of the state change of a resource agent provided in an embodiment of this disclosure;

[0031] Figure 4 This is a flowchart of another business processing method provided in this embodiment of the disclosure;

[0032] Figure 5 This is a general architecture diagram of cloud data platform service sinking provided by an embodiment of this disclosure;

[0033] Figure 6 This is a structural diagram of a service processing apparatus provided in an embodiment of this disclosure;

[0034] Figure 7 This is a structural diagram of another service processing apparatus provided in an embodiment of this disclosure;

[0035] Figure 8 This is a structural diagram of another service processing device provided in the embodiments of this disclosure;

[0036] Figure 9 This is a block diagram of an electronic device used to implement the business processing method of the embodiments of this disclosure. Detailed Implementation

[0037] The exemplary embodiments of this disclosure are described below with reference to the accompanying drawings, including various details of the embodiments to aid understanding, and should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this disclosure. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0038] In order to clearly introduce the technical solution of this disclosure, the cloud platform business system involved in the embodiments of this disclosure will be briefly described first.

[0039] See Figure 1 The cloud platform business system framework diagram shown includes a business control terminal 10, a resource control terminal 20, and edge nodes 30. The business control terminal 10 is communicatively connected to both the resource control terminal 20 and the edge nodes 30.

[0040] The edge node 30 is at least one, and each edge node 30 deploys a resource proxy and service instances. The resource proxy is used to supervise at least a portion of the service instances in the cluster to which the deployed edge node 30 belongs. The at least a portion of the service instances can be service instances in the edge nodes it has deployed, or service instances in edge nodes in the cluster that it has not deployed.

[0041] The business layer of the business control terminal 10 is equipped with a business SDK (Software Development Kit) to obtain different types of business requests.

[0042] The resource control terminal 20 is used to manage the resources in the cluster to which the edge nodes 30 belong, as well as the resource proxy terminals deployed in each edge node 30. Simultaneously, based on the managed data, it determines the resource proxy terminals that can forward business requests.

[0043] Among them, the resource proxy in edge node 30 is used to select the target instance that actually processes the business request from the service instances under its supervision, and forward the business request to the corresponding target instance for business processing.

[0044] exist Figure 1 Based on the cloud platform business system shown, this disclosure provides a business processing method with different devices as the execution entities and a business processing device configured in the corresponding execution entities, for application scenarios of processing business requests in the cloud platform business system. For ease of understanding, the business processing method will first be described in detail below.

[0045] See Figure 2A The business processing method shown is applied to a resource proxy deployed on an edge node, including:

[0046] S201. If the instance matches the resource identifier in the business request, obtain the instance matching information in the business request.

[0047] Specifically, business requests can be initiated by cloud platform users when they have business needs, and then captured by the business control terminal for further processing.

[0048] For example, a business request may include a resource identifier to characterize the resource requirements for processing the business request. The resource identifier may be represented by a name or symbol, and this disclosure does not limit the specific form of the resource identifier.

[0049] The resource proxy itself matches the resource identifier in the business request. This can be understood as the service instance monitored by the resource proxy being able to provide the resource requirements that match the resource identifier for processing the business request.

[0050] For example, different available resources can be pre-set in the namespace of the party initiating the business request, and each available resource can be pre-marked with a resource proxy terminal that performs different resource supervision. Accordingly, the resource proxy terminal that matches the resource identifier in the business request can be understood as the resource proxy terminal marked in the available resources that match the resource identifier in the namespace of the party initiating the business request.

[0051] Understandably, by introducing namespaces for resource identifier matching and resource proxy markup, the initiator of the business request gains access to the matched resource proxy, thus improving the security of business request processing. Simultaneously, the resource proxy overseeing the request ensures the availability of resources matching the resource identifier, guaranteeing the effective processing of the business request.

[0052] For example, a business request may include instance matching information, which is used to characterize the business requirements in at least one dimension when processing the business request, and is used as a reference for subsequent selection of target instances.

[0053] Optionally, instance matching information may include a business identifier to represent the pending business corresponding to the business request. Alternatively, instance matching information may include an instance tag to specify the service instance handling the corresponding business request. Alternatively, instance matching information may include a service identifier to represent the service requirements of the service instance handling the corresponding business request.

[0054] For example, a resource proxy that matches the resource identifier in a business request can receive the business request and then extract the instance matching information from the business request; or it can directly receive the instance matching information from the business request.

[0055] S202. Based on the instance matching information, select the target instance from the service instances deployed in the cluster to which the edge node belongs under its own supervision.

[0056] Since the resource proxy is deployed on the edge nodes of the cluster resources, and at least one edge node of the cluster resources is deployed with service instances for providing different services, different resource proxies monitor different service instances in the cluster resources. Therefore, based on the instance matching information, the target instance for processing business requests can be selected from the service instances it monitors.

[0057] In one optional embodiment, the instance matching information may include a service identifier; accordingly, based on the historical processing status of the service corresponding to the service identifier, a target instance for processing the service request can be selected from the service instances deployed in the cluster to which the edge node belongs under its own supervision.

[0058] For example, if the service identifier belongs to an incomplete historical service, such as an interrupted, suspended, or canceled service, it indicates that a service instance has already been allocated for that historical service. Therefore, the service instance used to execute the corresponding historical service can be selected from the service instances deployed in the cluster to which the edge node belongs under its own supervision, and used as the target instance. The advantage of doing so is that by reusing the already allocated service instance as the target instance, the selection process of the target instance is simplified and the efficiency of business processing is improved, while ensuring that the selected target instance can effectively execute the business request.

[0059] In another alternative embodiment, the instance matching information may include instance tags; accordingly, service instances with matching instance tags can be selected from the service instances deployed in the cluster to which the edge node belongs under its own supervision, as the target instance.

[0060] The instance tag uniquely identifies the labeled service instance and is used to distinguish different service instances. The instance tag can be presented in the form of an instance name or identifier, and this disclosure does not limit the specific presentation method of the instance tag.

[0061] Understandably, by adding instance tags to business requests and specifying the service instance that handles the requests, the customization needs of the request initiator can be met, and the flexibility and convenience of service instance selection can be improved.

[0062] In another alternative embodiment, the instance matching information may include a service identifier; correspondingly, at least one available candidate instance may be detected from each service instance deployed in the cluster to which the edge node belongs under its own supervision; and the candidate instance that matches the service identifier may be selected as the target instance.

[0063] For example, the resource broker can perform real-time or periodic liveness checks on each service instance it monitors and use the live service instances as candidate instances; from the candidate instances, it selects the candidate instance that matches the service identifier, that is, the candidate instance that provides the service required by the service identifier, as the target instance.

[0064] For example, the resource proxy can obtain the service name from the static singleton routeMap (routing strategy), retrieve the service instance information corresponding to the service name from the local instance data cache, and obtain the service status, port number, etc.; after extracting the end identifier information of the resource proxy from the URL (Universal Resource Locator) of the obtained business request, it generates a proxy request, and encapsulates the proxy request and sends it to the selected target instance.

[0065] Understandably, by introducing a service identifier to select the target instance, it is possible to avoid the situation where the selected target instance is unable to process the business request and provide the corresponding service, thus ensuring the effectiveness of business request processing.

[0066] S203. If the selection is successful, the terminal identification information is sent to the business control terminal so that the business control terminal can respond with the business request based on the terminal identification information.

[0067] If the selection is successful, it indicates that there is a service instance among the service instances monitored by the resource proxy that can handle the business request; if the selection fails, it indicates that there is no service instance among the service instances monitored by the resource proxy that can handle the business request.

[0068] The endpoint identification information uniquely identifies the resource proxy endpoint and is used to distinguish different resource proxies. Only successful resource proxies are selected to report their endpoint identification information to the business control center, enabling the business control center to effectively identify the entity responsible for forwarding subsequent business requests and avoid mis-sending of business requests.

[0069] S204. Send the business request to the target instance for processing.

[0070] After receiving a business request from the business control center, the resource proxy can directly forward the request to the target instance for processing. Alternatively, it can perform secondary processing on the request before sending the processed request to the target instance for processing.

[0071] In an optional embodiment, the resource proxy can also obtain the business description information required to process the business request from the business control terminal or other parties; accordingly, the resource proxy can encapsulate the business description information and the business request to obtain encapsulated data, and forward the encapsulated data to the target instance so that the target instance can process the business request based on the encapsulated data.

[0072] Because different target instances have varying degrees of openness to resource proxies within the cluster to which the edge nodes belong, the available secure transmission methods differ across these openness levels. Therefore, a secure transmission method can be selected based on different openness levels, and then the selected secure transmission method can be used to send service requests to the target instance.

[0073] For example, the development mode of the target instance relative to the resource proxy is determined; wherein, the open mode is either a single-end open mode or a cluster open mode; and a secure transmission method matching the open mode is used to send business requests to the target instance.

[0074] In this context, the single-end open mode can be understood as the situation where, among the resource agents in the cluster to which the edge node belongs, the target instance is exclusively used by the current resource agent; the cluster open mode can be understood as the situation where, among the resource agents in the cluster to which the edge node belongs, the target instance can be used by any resource agent in the cluster.

[0075] Optionally, in single-end open mode, a certificate encryption mechanism based on SSL (Secure Sockets Layer) or the HTTPS (Hypertext Transfer Protocol Secure) protocol can be introduced to send data to the target instance. Since the target instance only trusts data sent by its dedicated resource proxy, the security of communication between the resource proxy and the target instance is improved. For example, a blacklist / whitelist mechanism can also be introduced on top of the above transmission protocols to further enhance communication security.

[0076] Optionally, in the cluster open mode, an RPC (Remote Procedure Call Protocol) service can be introduced, combined with a cluster blacklist / whitelist security policy, to achieve secure data access within the cluster.

[0077] In single-end open mode, each resource proxy can provide access interfaces for the initiators of different business requests. Therefore, each initiator is allowed to log in to the cluster through the corresponding resource proxy and access business data on the edge nodes deployed by the corresponding resource proxy.

[0078] Understandably, by introducing different secure transmission methods, secure data transmission to target instances can be made applicable under different open modes, thereby improving the diversity and universality of business request delivery methods, while also enhancing the security of business request delivery.

[0079] In one optional embodiment, after the target instance completes processing the business request, it generates business data corresponding to the business request. Accordingly, the target instance feeds back the business data to the resource proxy that sent the business request, and the resource proxy then forwards the business data to the business control center for output or subsequent processing. It is understood that the business request's sending path can be reused during the business data return process to ensure the security of the business data return.

[0080] This embodiment of the disclosure deploys a resource proxy in edge nodes and uses the resource proxy to select and use target instances. This enables the processing of business requests and the corresponding services to be moved from the cloud to edge nodes closer to the user. While achieving domain isolation between the cloud and the user-side edge nodes, it reduces the service pressure on the cloud, lowers the service cost of the cloud, and optimizes the service experience. Furthermore, deploying the resource proxy in the edge nodes of the cluster facilitates horizontal scaling.

[0081] Based on the above technical solutions, a management mechanism for service instances can be introduced on the resource proxy side to improve the convenience of managing service instances.

[0082] In one optional embodiment, the current service state of the monitored service instance can be determined; the corresponding service instance can be processed according to the current service state; and the current service state of the corresponding service instance can be adjusted according to the processing situation.

[0083] The current service state of a service instance represents the stage of its lifecycle and indicates the necessary subsequent processing to adjust or transform its current state. The lifecycle may include at least one of the following: service synchronization, service deployment, service operation, service activation, service upgrade, and service destruction. Different stages can be linked by changes in the current service state. Different stages can be triggered by technical personnel based on actual needs, triggered by changes in the current service state of other stages, or triggered in real-time or at set intervals using pre-defined service threads. This disclosure does not limit the specific triggering methods for different stages.

[0084] Understandably, by introducing the current state of the service and processing the service instance, the service instance is gradually adjusted to the desired state, thus realizing the automated management of the monitored service instance by the resource agent, and improving the convenience and standardization of the management process.

[0085] The current service status can be the initial service status, the service deployment status, the service stopped status, the service running status, the service awaiting upgrade status, the service disconnected status, the service offline status, the service abnormal status, or the service released status, etc.

[0086] The service initialization state indicates that during the service synchronization phase, the service instance to be added is ready and requires initialization. The service deployment state indicates that during the service deployment phase, the service instance to be deployed has been successfully initialized and requires startup; or, during the service upgrade phase, the service instance to be upgraded has been successfully rebuilt and requires restart. The service stop state indicates that during the service deployment phase, the service instance to be deployed failed to start and requires restart; or, during the service upgrade phase, the service instance to be upgraded successfully terminated and requires reloading. The service running state indicates that during the service liveness detection phase, the detected service instance is running normally and requires no intervention; or, during the service upgrade phase, the service instance to be upgraded needs to be upgraded; or, during the service synchronization phase, the service instance to be deleted needs to be set to offline. The service pending upgrade state indicates that during the service upgrade phase, the service instance to be upgraded has been successfully upgraded and requires termination. The service disconnection state indicates that during the service liveness detection phase, abnormal service instances are detected, and when the number of service disconnections exceeds the first threshold, the corresponding service instance is set to offline. The "Service Offline" status indicates that service instances slated for offline processing need to be destroyed, and the service instance's "Service Release" status is set after successful destruction. The "Service Abnormal" status indicates that service instances to be deployed during the service deployment phase failed, or service instances to be upgraded during the service upgrade phase failed, requiring abnormal intervention. The "Service Release" status indicates that service instances slated for destruction were successfully destroyed.

[0087] The following will combine Figure 2B The diagram illustrating the state changes of service instances provides a detailed explanation of the state change process for service instances under different circumstances.

[0088] In one specific implementation, during the service synchronization phase, service change detection is performed in real-time or periodically by a service update thread. If a new service is detected, preparatory operations are performed for the service instance to be added (such as generating and recording the new service instance). After preparation, the corresponding service instance is set to the initial service state for the subsequent service deployment phase. If a service deletion is detected (e.g., due to a failed service instance), the service instance to be deleted is set to the offline service state for the subsequent service destruction phase.

[0089] In another specific implementation, during the service deployment phase, service instances in the initial service state undergo initialization processing (such as creating paths, establishing secure communication connections for dependency package copying, constructing execution environments, creating and authorizing directories, and mounting containers). Successfully initialized service instances are set to the service deployment state; service instances that fail initialization are set to the service exception state, indicating the need for intervention. Further, during the service deployment phase, service instances in the service deployment state undergo startup processing (such as generating process locks for process protection and generating port files for collecting monitored service instances). Successfully started service instances are set to the service running state, while those that fail to start are set to the service stopped state. Service instances in the stopped state are restarted, with successfully restarted service instances set to the service running state and those that fail to restart set to the service exception state, indicating the need for intervention.

[0090] In another specific implementation, during the service liveness detection phase, a service protection sub-thread is used to detect whether the service instance is running normally. Normally running service instances are set to the service running state, and task load is recorded without further intervention. Service instances detected as having a version mismatch are set to the service stopped state (if the task load corresponds to an idle flag, the service stopped state is set directly; if the task load corresponds to a non-idle flag, detection continues until idle before setting the service stopped state). Service instances with abnormal detections are set to the service disconnected state. Service instances whose number of disconnections exceeds the first threshold (which can be manually set according to requirements or experience) are set to the service offline state.

[0091] In the next specific implementation, during the service upgrade phase, the service instances to be upgraded in the service running state are upgraded and updated. Successfully upgraded service instances are set to the "awaiting upgrade" state, while those that fail are set to the "running" state. Further, the service instances in the "upgrade" state are stopped. Successfully stopped service instances are set to the "stopped" state, while those that fail are set to the "abnormal" state. Further, the stopped service instances are reloaded. Successfully reloaded service instances are set to the "deployed" state, while those that fail are set to the "abnormal" state. Finally, the deployed service instances are started. Successfully started service instances are set to the "running" state, while those that fail are set to the "abnormal" state.

[0092] In another specific implementation, during the service destruction phase, service instances in the offline state are destroyed (e.g., cleaning up job data and logs, destroying deployment information, etc.). Service instances that are successfully destroyed are set to the service release state, while service instances that fail to be destroyed are set to the service offline state.

[0093] This disclosure further refines the specific status information of the current service status and the processing operations and status adjustments indicated by different status information, thereby improving the accuracy and effectiveness of the resource agent in managing the monitored service instances and effectively maintaining the autonomous ecological stability of service instances in the resource cluster.

[0094] The above describes the business processing method in detail, using the resource agent deployed on the edge node as the execution entity. The following section will describe the business processing process in detail, using the resource control terminal as the execution entity.

[0095] See Figure 3A The business processing method shown is applied to a resource control terminal and includes:

[0096] S301. Obtain the resource identifier in the business request and determine the resource proxy terminal deployed on the edge node that matches the resource identifier.

[0097] Specifically, business requests can be initiated by cloud platform users when they have business needs, and then captured by the business control terminal for further processing.

[0098] For example, a business request may include a resource identifier to characterize the resource requirements for processing the business request. The resource identifier may be represented by a name or symbol, and this disclosure does not limit the specific form of the resource identifier.

[0099] Optionally, the resource control terminal can receive business requests and extract the resource identifier from the business requests; or, alternatively, the resource control terminal can directly receive the resource identifier from the business requests for subsequent processing.

[0100] In an optional embodiment, resources under different resource identifiers and their corresponding resource proxy ends can be pre-labeled, and the resource proxy end matching the resource identifier can be determined according to the above labeling relationship.

[0101] Because cloud platform business systems provide available resources to a large number of request initiators through resource sharing, the available resources vary among different initiators due to differences in usage permissions. To facilitate management, different namespaces can be pre-defined for different initiators, and available resources can be configured within each namespace, along with the resource proxy managing those resources. Accordingly, within the namespace of the request initiator, the available resources matching the resource identifier are identified; and the resource proxy deployed on the edge nodes marked with those available resources is determined.

[0102] Namespaces are a special abstraction of scopes. By setting different namespaces for different initiators, data confusion between namespaces of different initiators is avoided. The initiator's namespace records the resource tags corresponding to the resources that the initiator has the right to use, i.e., available resources, and marks the resource agent managing the available resource under each available resource. Resource tags can include at least one of the following: reference tags, cluster application tags, and node tags. Reference tags are used to represent the reference end information of the resource, such as VPC (Virtual Private Cloud) tags or queue tags; cluster application tags are used to represent the basic information of the cluster to which the resource belongs, such as the deployed distributed components and their corresponding version numbers; node tags are used to represent the basic information of the resource node (such as an edge node) deploying the corresponding resource, such as node type, node load, and node weight. Node types can be master nodes, core nodes, task nodes, or client types, etc.

[0103] Understandably, by introducing a resource tagging system to abstractly describe heterogeneous clusters, queues, nodes, or containers, a tag library can be built using methods such as dynamic configuration, service registration, and component monitoring mechanisms. This serves as the basis for target service discovery and business request forwarding, which helps improve the efficiency and accuracy of target service discovery, thereby improving the timeliness and accuracy of business processing.

[0104] This disclosure introduces namespaces for available resources and marks resource proxies that manage available resources, facilitating the management of available resources and their resource proxies from different initiators, improving management convenience, and avoiding the occurrence of incorrect resource proxy selection, thereby improving the accuracy of resource proxy determination results.

[0105] S302. Send the endpoint identifier information of the resource proxy terminal to the business control terminal so that the business control terminal sends the instance matching information in the business request to the corresponding resource proxy terminal to select the target instance deployed in the cluster of the edge node under the supervision of the corresponding resource proxy terminal; the target instance is used to process the business request.

[0106] By sending the endpoint identifier information of the resource proxy that matches the resource identifier to the business control terminal, the business control terminal only needs to send instance matching information or business requests including instance matching information to these resource proxies. This avoids data leakage caused by rashly sending data to mismatched resource proxies and also avoids unnecessary occupation of transmission bandwidth, saving data transmission resources. In addition, mismatched resource proxies do not need to perform target instance selection operations, avoiding unnecessary waste of computing resources.

[0107] This embodiment of the disclosure deploys resource proxy terminals in edge nodes, matches and selects resource proxy terminals at the resource control terminal, and further selects and uses target instances through the selected resource proxy terminals. This realizes the sinking of the service corresponding to the processing of business requests from the cloud to the edge nodes closer to the user side. While achieving network domain isolation between the cloud and the user-side edge nodes, it reduces the service pressure on the cloud, lowers the service cost of the cloud, and optimizes the service experience.

[0108] Based on the above technical solutions, a management mechanism for the resource agent terminal can be introduced at the resource control terminal to improve the convenience of managing the resource agent terminal.

[0109] In one optional embodiment, the current proxy status of the monitored resource proxy can be determined; the corresponding resource proxy can be processed according to the current proxy status; and the current proxy status of the corresponding resource proxy can be adjusted according to the processing situation.

[0110] The current state of the resource proxy terminal represents its stage in its lifecycle and indicates the necessary subsequent processing to adjust or change its current state. The lifecycle can include proxy synchronization, deployment, operation, activation, upgrade, and destruction phases. These phases can be linked by changes in the current proxy state. Different phases can be triggered automatically by technical personnel based on actual needs, triggered by changes in the current proxy state of other phases, or triggered in real-time or at set intervals using preset proxy threads. This disclosure does not limit the specific triggering method for different phases.

[0111] Understandably, by introducing the current state of the agent and processing the resource agent, the resource agent can be gradually adjusted to the desired state, thus realizing the automated management of the monitored resource agents by the resource control terminal and improving the convenience and standardization of the management process.

[0112] The current status of the agent can be the agent initial status, agent deployment status, agent stopped status, agent running status, agent awaiting upgrade status, agent disconnected status, agent offline status, agent abnormal status, or agent released status, etc.

[0113] The proxy initial state indicates that during the proxy synchronization phase, the newly added resource proxy is ready and requires initialization. The proxy deployment state indicates that during the proxy deployment phase, the resource proxy to be deployed has successfully initialized and requires startup; or, during the proxy upgrade phase, the resource proxy to be upgraded has been successfully rebuilt and requires restart. The proxy stopped state indicates that during the proxy deployment phase, the resource proxy to be deployed failed to start and requires restart; or, during the proxy upgrade phase, the resource proxy to be upgraded successfully terminated and requires reloading. The proxy running state indicates that during the proxy detection phase, the detected resource proxy is running normally and requires no intervention; or, during the proxy upgrade phase, the resource proxy to be upgraded needs to be upgraded; or, during the proxy synchronization phase, the resource proxy to be deleted needs to be set to offline. The proxy awaiting upgrade state indicates that during the proxy upgrade phase, the resource proxy to be upgraded has been successfully upgraded and requires termination. The "Proxy Disconnection" status indicates that during the proxy activation phase, if an abnormal resource proxy is detected and the number of disconnections exceeds a second threshold, the corresponding resource proxy will be set to "Proxy Offline." The "Proxy Offline" status indicates that a resource proxy to be taken offline needs to be destroyed, and after successful destruction, the corresponding resource proxy will be set to "Proxy Release." The "Proxy Abnormality" status indicates that the deployment of a resource proxy to be deployed during the proxy deployment phase or the upgrade of a resource proxy to be upgraded during the proxy upgrade phase has failed, requiring abnormal intervention for the corresponding resource proxy. The "Proxy Release" status indicates that a resource proxy to be destroyed has been successfully destroyed.

[0114] The following will combine Figure 3B The diagram showing the state changes of the resource proxy terminal provides a detailed explanation of the state change process under different circumstances.

[0115] In one specific implementation, during the proxy synchronization phase, proxy change detection is performed in real-time or periodically via a proxy update thread. If a new proxy is detected (e.g., the addition of an edge node or cluster expansion), preparatory operations are performed for the new resource proxy (e.g., generating and recording the new resource proxy). After preparation, the corresponding resource proxy is set to its initial proxy state for subsequent proxy deployment. If a proxy deletion is detected (e.g., a resource proxy not monitoring any service instances, edge node deletion, or cluster scaling down), the resource proxy to be deleted is set to its offline proxy state for subsequent proxy destruction.

[0116] In another specific implementation, during the proxy deployment phase, the resource proxy terminals to be deployed in the initial proxy state undergo initialization processing (such as deployment directory detection, permission detection, trust establishment, certificate download, dependency package download, and installation environment preparation). Successfully initialized resource proxy terminals are set to the proxy deployment state; those failing initialization are set to the proxy exception state, indicating the need for abnormal intervention. Further, during the proxy deployment phase, the resource proxy terminals in the proxy deployment state undergo startup processing (such as daemon process creation, process lock verification, log verification, and daemon startup). Successfully started resource proxy terminals are set to the proxy running state, while those failing to start are set to the proxy stopped state. Resource proxy terminals in the proxy stopped state are restarted; successfully restarted resource proxy terminals are set to the proxy running state, while those failing to restart are set to the proxy exception state, indicating the need for abnormal intervention.

[0117] In another specific implementation, during the proxy liveness detection phase, the proxy keep-alive thread detects whether the resource proxy is running normally (obtaining information such as status, port, and active version through heartbeat requests, and persisting the data in memory, etc.); the normally running resource proxy is set to the proxy running state, and the task load is recorded, etc., without any other intervention; the resource proxy detected to be inconsistent with the version is set to the proxy stopped state (if the task load corresponds to the idle flag, the proxy is directly set to the proxy stopped state; if the task load corresponds to the non-idle flag, the detection continues until it is idle before setting the proxy stopped state); the resource proxy detected to be abnormal is set to the proxy disconnected state; the resource proxy whose number of disconnections exceeds the second threshold (which can be manually set according to needs or experience) is set to the proxy offline state.

[0118] In the next specific implementation, during the proxy upgrade phase, the proxy clients of the resources to be upgraded in the proxy running state are upgraded and updated. Proxy clients that successfully upgrade and update are set to the "pending upgrade" state, while those that fail to upgrade and update are set to the "running" state. Further, the proxy clients of the resources to be upgraded in the "upgrade" state are stopped. Proxy clients that successfully stop are set to the "stopped" state, while those that fail to stop are set to the "abnormal" state. Further, the proxy clients of the stopped state are reloaded. Proxy clients that successfully reload are set to the "deployed" state, while those that fail to reload are set to the "abnormal" state. Further, the proxy clients of the resources to be upgraded in the "deployed" state are started. Proxy clients that successfully start are set to the "running" state, while those that fail to start are set to the "abnormal" state.

[0119] In another specific implementation, during the proxy destruction phase, the proxy clients in the offline state are destroyed (e.g., forwarding or transmission is interrupted, offline service is stopped, data is cleaned up, main process exits, etc.). The proxy clients that are successfully destroyed are set to the proxy release state, and the proxy clients that are not destroyed are set to the proxy offline state.

[0120] This disclosure further refines the specific status information of the agent's current state and the processing operations and status adjustments indicated by different status information, thereby improving the accuracy and effectiveness of the resource agent's management of the supervised resource agents and effectively maintaining the autonomous ecological stability of the resource agents in the resource cluster.

[0121] The above provides a detailed explanation of the business processing methods, with the resource control center as the executing entity. The following section will detail the business processing procedure, with the business control center as the executing entity.

[0122] See Figure 4 The business processing methods shown include:

[0123] S401, Obtain a business request that includes instance matching information and resource identifier.

[0124] Specifically, business requests can be initiated by cloud platform users when they have business needs, and then captured by the business control terminal for further processing.

[0125] For example, a business request may include a resource identifier to characterize the resource requirements for processing the business request. The resource identifier may be represented by a name or symbol, and this disclosure does not limit the specific form of the resource identifier.

[0126] For example, a business request may include instance matching information, which is used to characterize the business requirements in at least one dimension when processing the business request, and is used as a reference for subsequent selection of target instances.

[0127] Optionally, instance matching information may include a business identifier to represent the pending business corresponding to the business request. Alternatively, instance matching information may include an instance tag to specify the service instance handling the corresponding business request. Alternatively, instance matching information may include a service identifier to represent the service requirements of the service instance handling the corresponding business request.

[0128] S402. Send the resource identifier to the resource control terminal so that the resource control terminal can identify and return the resource agent terminal that matches the resource identifier.

[0129] Optionally, the business control terminal can directly send a business request to the resource control terminal, and the resource control terminal can extract the resource identifier from the business request; or, alternatively, the business control terminal can directly send the resource identifier from the business request to the resource control terminal for subsequent processing.

[0130] In an optional embodiment, the resource control terminal can pre-label resources under different resource identifiers and the corresponding resource proxy terminals, and determine the resource proxy terminal that matches the resource identifier based on the above labeling relationship.

[0131] Because cloud platform business systems provide available resources to a large number of request initiators through resource sharing, the available resources vary among different initiators due to differences in usage permissions. To facilitate management, different namespaces can be pre-defined for different initiators, and available resources can be configured within each namespace, along with the resource proxy managing those resources. Accordingly, within the namespace of the request initiator, the available resources matching the resource identifier are identified; and the resource proxy deployed on the edge nodes marked with those available resources is determined.

[0132] Namespaces are a special abstraction of scopes. By setting different namespaces for different initiators, data confusion between namespaces of different initiators is avoided. The initiator's namespace records the resource tags corresponding to the resources that the initiator has the right to use, i.e., available resources, and marks the resource agent managing the available resource under each available resource. Resource tags can include at least one of the following: reference tags, cluster application tags, and node tags. Reference tags are used to represent the reference end information of the resource, such as VPC (Virtual Private Cloud) tags or queue tags; cluster application tags are used to represent the basic information of the cluster to which the resource belongs, such as the deployed distributed components and their corresponding version numbers; node tags are used to represent the basic information of the resource node (such as an edge node) deploying the corresponding resource, such as node type, node load, and node weight. Node types can be master nodes, core nodes, task nodes, or client types, etc.

[0133] S403. Send instance matching information to the matched resource agent so that the resource agent can select the target instance from the service instances deployed in the cluster of the edge node under its supervision according to the instance matching information, and return its own terminal identification information when the selection is successful.

[0134] S404. Send a business request to the resource agent corresponding to the end identifier information, so that the corresponding resource agent sends the business request to the target instance for processing.

[0135] For example, a business request can be sent to the matched resource proxy, and the resource proxy can then extract the instance matching information from the business request; or the instance matching information from the business request can be sent directly to the matched resource proxy.

[0136] In one optional embodiment, the instance matching information may include a service identifier; accordingly, the resource proxy can select a target instance for processing the service request from the service instances deployed in the cluster to which it supervises the service instance corresponding to the service identifier, based on the historical processing status of the service.

[0137] For example, if the business identifier belongs to an incomplete historical business, such as an interrupted business, a suspended business, or a canceled business, it indicates that a service instance has already been allocated for the historical business. Therefore, the service instance used to execute the corresponding historical business can be selected from the service instances deployed in the cluster to which the edge node belongs under its own supervision, and used as the target instance.

[0138] In another optional embodiment, the instance matching information may include instance tags; accordingly, the resource agent can select a service instance with matching instance tags from the service instances deployed in the cluster to which it supervises the edge nodes, as the target instance.

[0139] The instance tag uniquely identifies the labeled service instance and is used to distinguish different service instances. The instance tag can be presented in the form of an instance name or identifier, and this disclosure does not limit the specific presentation method of the instance tag.

[0140] In another alternative embodiment, the instance matching information may include a service identifier; accordingly, the resource agent can detect at least one available candidate instance from each service instance deployed in the cluster to which it supervises the edge node; and select the candidate instance that matches the service identifier as the target instance.

[0141] For example, the resource broker can perform real-time or periodic liveness checks on each service instance it monitors and use the live service instances as candidate instances; from the candidate instances, it selects the candidate instance that matches the service identifier, that is, the candidate instance that provides the service required by the service identifier, as the target instance.

[0142] This embodiment of the disclosure deploys resource proxy terminals in edge nodes, matches and selects resource proxy terminals through a resource control terminal, and further selects and uses target instances through the resource proxy terminals. This realizes the sinking of the service corresponding to the processing of business requests from the cloud to the edge nodes closer to the user side. While achieving network domain isolation between the cloud and the user-side edge nodes, it reduces the service pressure on the cloud, lowers the service cost of the cloud, and optimizes the service experience.

[0143] Based on the above technical solutions, this disclosure also provides a preferred embodiment, in which the preferred embodiment is combined with Figure 5 The overall architecture diagram of the cloud data platform service decentralization provides a detailed explanation of the business processing methods for decentralized services.

[0144] See Figure 5 The architecture diagram shown includes the resource reference presentation layer, the resource pool management layer, the service cluster management layer, the business service SDK, the resource client, and the remote service instance.

[0145] The resource reference presentation layer, resource pool management layer, and service cluster management layer are deployed on the resource control center; the business service SDK is deployed on the business control center; and the resource client and remote service instances are deployed on the resource nodes.

[0146] The business service SDK is used to capture business requests in the cloud data platform, and through service discovery, determine the remote service instance for handling business requests that can be processed in a decentralized manner, and forward the business requests to the remote service instance.

[0147] The resource client acts as an intermediary between the business service SDK and remote service instances. It receives business requests distributed by the SDK, encapsulates these requests, and forwards them to the remote service instances responsible for processing. Simultaneously, the resource client can collect real-time information from distributed computing power (i.e., remote service instances)—that is, the business data generated from processing business requests—and upload this real-time information to achieve data feedback. During the resource client's business request distribution process, a secure cross-domain control flow is established; during the resource client's business data feedback process, a secure cross-domain data flow is established, thus achieving secure communication between the resource control center and user-side resources.

[0148] For example, resource clients manage the remote service instances they oversee by introducing instance lifecycles and instance state machines. The specific oversight mechanism for remote service instances can be found in the relevant descriptions of the foregoing embodiments, and will not be repeated here.

[0149] It should be noted that user-side resources are deployed in isolation, avoiding potential risks caused by thread pool or data cache overload. Furthermore, elastic deployment enables remote service instances to maintain their own activity and perform upgrades.

[0150] During service discovery, a resource control terminal is required to manage resources and assist in resource discovery based on the results of resource management.

[0151] For example, in the service cluster management layer of the resource control terminal, resource lifecycle and resource state machine are introduced to manage the resource clients it oversees. The specific oversight mechanism for resource clients can be found in the relevant descriptions of the foregoing embodiments, and will not be repeated here.

[0152] For example, the resource pool management layer of the resource control terminal records the data storage information corresponding to different resource entities such as single-machine resources, cluster resources, or container resources, thereby realizing entity management. The stored data may include resource node records, resource tag records, and component service records. By managing the resource nodes of each resource entity, as well as the tags and components in the resource nodes, resource discovery is performed in real time or on a regular basis, and the creation or deletion of resource clients is controlled based on the discovered resources.

[0153] Optionally, the resource pool management system can also provide a unified interface for resource management and querying, enabling the categorization, management, and querying of remote resources. Simultaneously, by introducing a tagging system, it provides service registration and component monitoring capabilities, and facilitates resource information querying and filtering.

[0154] For example, in the resource reference representation layer of the resource control terminal, namespaces corresponding to different accounts are recorded. Under each namespace, resource tags and usage permissions for available resources are referenced. Simultaneously, the port information of the resource client managing that resource is recorded under each available resource. This port information allows for the location of the resource client, serving as the basis for locating remote service instances that subsequently handle business requests received by the business service SDK. Furthermore, the use of namespaces in conjunction with resource tags lays the foundation for referencing and expanding different types of resources, facilitating the management of quotas, computing power synchronization, and dynamic scaling within cloud platform services.

[0155] In one optional embodiment, during the process of managing resource entities and references, the resource control terminal carries the following intelligence:

[0156] 1) Resource Management: Interactive management of cloud platform computing resources, including registration (adding references to existing entities, etc.), creation (entities provided by resource pools, or new entities, etc.), deletion, release, update, and display of status information.

[0157] 2) Resource authentication: Verification of the identities of data platform resource users and project participants, and provides secure verification of resource user identities and authentication conversion of remote resources.

[0158] 3) Resource screening: Provides resource quotas, load, feature labeling decisions, and supports data platform applications.

[0159] 4) Resource component query: resource cluster node third-party self-check, containers, service versions, service status and routing information, etc.

[0160] 5) Remote Service Management: This includes remote service control and service discovery. Remote service control can include configuration loading, API (Application Programming Interface) registration, and activity detection; service discovery can include routing and request distribution.

[0161] For example, during resource synchronization, the cloud environment's existing backbone resource SDK or API can be called to obtain a list of various resources under the user and synchronize them with the list in the resource library; resource clusters are checked one by one to synchronize queue status, quotas, and usage, and the storage information such as queues and tags in the resource library cluster is updated; the process of deploying new resource node clients, destroying failed resource node clients, and scaling up and down existing resource nodes are handled, and the node storage information is updated to achieve resource node synchronization.

[0162] For example, by introducing a namespace, a list of all resources within the namespace (including information such as status and type), details of each resource quota and usage, etc., can be bound to a list of project tags, serving as the basis for querying resource lists, cluster queues, and project tags; node information of resource queues can be introduced to enable resource node queries; and service instance information under the namespace resource service tags can be introduced to enable service instance queries.

[0163] For example, the status monitoring of components and remote service instances can be performed on resource clusters or resource nodes, and the service tags and routing information of remote service instances can be stored in the database to achieve service management.

[0164] This disclosed embodiment achieves cloud platform service decentralization through the above technical solution, and adopts a three-layer framework of resource central control terminal - resource node - remote service instance to realize the central control service, business management service and computing tasks being pushed down to user resources, thereby isolating the business load of different users, reducing the pressure on the resource central control terminal and reducing the service cost of the cloud platform system.

[0165] As an implementation of the above-described business processing methods, this disclosure also provides an optional embodiment of an execution apparatus for implementing the above-described business processing methods.

[0166] See Figure 6 The service processing device 600 shown is configured on a resource proxy terminal deployed at an edge node, and includes: an instance matching information acquisition module 601, a target instance selection module 602, an end identifier information sending module 603, and a service request distribution module 604. Among them,

[0167] The instance matching information acquisition module 601 is used to acquire instance matching information in the business request when it matches the resource identifier in the business request.

[0168] The target instance selection module 602 is used to select a target instance from the service instances deployed in the cluster to which it is supervised, based on the instance matching information.

[0169] The terminal identification information sending module 603 is used to send its own terminal identification information to the service control terminal if the selection is successful, so that the service control terminal can respond to the service request based on the terminal identification information.

[0170] The business request distribution module 604 is used to distribute the business request to the target instance for processing.

[0171] This embodiment of the disclosure deploys a resource proxy in edge nodes and uses the resource proxy to select and use target instances. This enables the processing of business requests and the corresponding services to be moved from the cloud to edge nodes closer to the user. While achieving domain isolation between the cloud and the user-side edge nodes, it reduces the service pressure on the cloud, lowers the service cost of the cloud, and optimizes the service experience. Furthermore, deploying the resource proxy in the edge nodes of the cluster facilitates horizontal scaling.

[0172] In an optional embodiment, the instance matching information includes a service identifier; the target instance selection module 602 is specifically used for:

[0173] If the business identifier belongs to an incomplete historical business, then the service instance used to execute the corresponding historical business is selected from the service instances deployed in the cluster to which the edge node belongs under its own supervision, and this service instance is selected as the target instance.

[0174] In an optional embodiment, the instance matching information includes instance tags; the target instance selection module 602 is specifically used for:

[0175] From the service instances deployed in the cluster to which the edge node belongs under its own supervision, select the service instance whose instance tag matches as the target instance.

[0176] In an optional embodiment, the instance matching information includes a service identifier; the target instance selection module 602 is specifically used for:

[0177] From each service instance deployed on the edge node to which it is under its own supervision, detect at least one available candidate instance;

[0178] A candidate instance that matches the service identifier is selected as the target instance.

[0179] In an alternative embodiment, the resource proxy is marked among the available resources that match the resource identifier under the namespace of the initiator of the service request.

[0180] In an optional embodiment, the service request issuing module 604 includes:

[0181] An open mode determination unit is used to determine the open mode of the target instance relative to the resource proxy; wherein the open mode is a single-end open mode or a cluster open mode;

[0182] The service request sending unit is used to send the service request to the target instance using a secure transmission method that matches the open mode.

[0183] In an optional embodiment, the device 600 further includes:

[0184] The Service Current Status Determination Module is used to determine the current service status of the monitored service instances;

[0185] The service instance processing module is used to process the corresponding service instance according to the current state of the service;

[0186] The Service Current Status Adjustment Module is used to adjust the current status of the corresponding service instance based on the processing status.

[0187] In an optional embodiment, the current state of the service is a service initial state, service deployment state, service stopped state, service running state, service awaiting upgrade state, service disconnected state, service offline state, service abnormal state, or service released state.

[0188] The initial service state is used to characterize the service instance to be added during the service synchronization phase, which is ready and requires initialization.

[0189] The service deployment status is used to represent the service deployment phase, where the service instance to be deployed has been successfully initialized and needs to be started; or, in the service upgrade phase, where the service instance to be upgraded has been successfully rebuilt and needs to be restarted.

[0190] The service stop status is used to indicate that during the service deployment phase, the service instance to be deployed fails to start and needs to be restarted; or, during the service upgrade phase, the service instance to be upgraded successfully terminates the service and needs to be reloaded.

[0191] The service operation status is used to characterize whether the detected service instance is running normally and requires no intervention during the service detection phase; or whether the service instance to be upgraded needs to be upgraded during the service upgrade phase; or whether the service instance to be deleted needs to be set to offline status during the service synchronization phase.

[0192] The service pending upgrade status indicates that during the service upgrade phase, the service instance to be upgraded has been successfully upgraded and needs to be terminated.

[0193] The service disconnection status is used to characterize the abnormal service instances detected during the service activation phase, and to set the corresponding service instances to a service offline status when the number of service disconnections exceeds the first threshold.

[0194] The service offline status is used to indicate that the service instance to be offline needs to be destroyed, and the service release status is set for the corresponding service instance after successful destruction.

[0195] The service anomaly status is used to indicate that the deployment of the service instance to be deployed during the service deployment phase fails, or the upgrade of the service instance to be upgraded during the service upgrade phase fails, and the corresponding service instance needs to be handled by anomaly intervention.

[0196] The service release status indicates that the service instance to be destroyed has been successfully destroyed.

[0197] The above-described business processing apparatus can execute the business processing methods provided in any embodiment of this disclosure, and has the corresponding functional modules and beneficial effects for executing the business processing methods.

[0198] As an implementation of the above-described business processing methods, this disclosure also provides another optional embodiment of an execution apparatus for implementing the above-described business processing methods.

[0199] See Figure 7 The service processing device 700 shown is configured at the resource control terminal and includes: a resource agent terminal determination module 701 and an terminal identification information sending module 702. Among them,

[0200] The resource proxy determination module 701 is used to obtain the resource identifier in the business request and determine the resource proxy deployed on the edge node that matches the resource identifier.

[0201] The endpoint identification information sending module 702 is used to send the endpoint identification information of the resource proxy to the business control terminal, so that the business control terminal sends the instance matching information in the business request to the corresponding resource proxy to select the target instance deployed in the cluster of the edge node under the supervision of the corresponding resource proxy.

[0202] The target instance is used to process the business request.

[0203] This embodiment of the disclosure deploys resource proxy terminals in edge nodes, matches and selects resource proxy terminals at the resource control terminal, and further selects and uses target instances through the selected resource proxy terminals. This realizes the sinking of the service corresponding to the processing of business requests from the cloud to the edge nodes closer to the user side. While achieving network domain isolation between the cloud and the user-side edge nodes, it reduces the service pressure on the cloud, lowers the service cost of the cloud, and optimizes the service experience.

[0204] In an optional embodiment, the resource proxy determination module 701 includes:

[0205] The available resource determination unit is used to determine, within the namespace of the initiator of the service request, an available resource that matches the resource identifier;

[0206] The resource proxy determination unit is used to determine the resource proxy deployed on the edge node that is marked by the available resources.

[0207] In an optional embodiment, the device 700 further includes:

[0208] The proxy current status determination module is used to determine the current proxy status of the monitored resource proxy.

[0209] The resource proxy processing module is used to process the corresponding resource proxy based on the current state of the proxy.

[0210] The proxy current status adjustment module is used to adjust the current proxy status of the corresponding resource proxy based on the processing situation.

[0211] In an optional embodiment, the current state of the agent is the agent initial state, agent deployment state, agent stopped state, agent running state, agent awaiting upgrade state, agent disconnected state, agent offline state, agent abnormal state, or agent released state.

[0212] The initial state of the agent is used to represent the state during the agent synchronization phase, where the newly added resource agent is ready and needs to be initialized.

[0213] The agent deployment status is used to indicate that during the agent deployment phase, the resource agent to be deployed has been successfully initialized and needs to be started; or, during the agent upgrade phase, the resource agent to be upgraded has been successfully rebuilt and needs to be restarted.

[0214] The agent stop status is used to indicate that during the agent deployment phase, the agent for the resource to be deployed fails to start and needs to be restarted; or, during the agent upgrade phase, the agent for the resource to be upgraded successfully terminates and needs to be reloaded.

[0215] The agent running status is used to indicate that during the agent detection phase, the detected resource agent is running normally and requires no intervention; or, during the agent upgrade phase, the resource agent to be upgraded needs to be upgraded and updated; or, during the agent synchronization phase, the resource agent to be deleted needs to be set to offline status.

[0216] The agent pending upgrade status indicates that during the agent upgrade phase, the resource agent to be upgraded has been successfully upgraded and updated, and the agent needs to be terminated.

[0217] The agent disconnection status is used to characterize the abnormal service instance detected during the agent activation phase, and to set the corresponding resource agent to offline status when the number of agent disconnections exceeds the second threshold.

[0218] The offline proxy status is used to indicate that the resource proxy client to be offline needs to be destroyed, and after the destruction is successful, the corresponding resource proxy client is set to release proxy status.

[0219] The abnormal proxy status is used to indicate that the deployment of the resource proxy terminal to be deployed during the proxy deployment phase fails, or the upgrade of the resource proxy terminal to be upgraded during the proxy upgrade phase fails, and abnormal intervention processing is required for the corresponding resource proxy terminal.

[0220] The agent release status is used to indicate that the resource agent to be destroyed has been successfully destroyed.

[0221] The above-described business processing apparatus can execute the business processing methods provided in any embodiment of this disclosure, and has the corresponding functional modules and beneficial effects for executing the business processing methods.

[0222] As an implementation of the above-described business processing methods, this disclosure also provides an alternative embodiment of an execution apparatus for implementing the above-described business processing methods.

[0223] See Figure 8 The service processing device 800 shown is configured at the service control center and includes: a service request acquisition module 801, a resource identifier sending module 802, an instance matching information sending module 803, and a service request sending module 804.

[0224] The business request acquisition module 801 is used to acquire business requests, including instance matching information and resource identifiers.

[0225] The resource identifier sending module 802 is used to send the resource identifier to the resource control terminal so that the resource control terminal can determine and return the resource agent terminal that matches the resource identifier;

[0226] The instance matching information sending module 803 is used to send the instance matching information to the matched resource agent, so that the resource agent can select a target instance from the service instances deployed in the cluster to which it supervises the edge node according to the instance matching information, and return its own terminal identification information when the selection is successful.

[0227] The service request sending module 804 is used to send the service request to the resource proxy terminal corresponding to the terminal identification information, so that the corresponding resource proxy terminal sends the service request to the target instance for processing.

[0228] This embodiment of the disclosure deploys resource proxy terminals in edge nodes, matches and selects resource proxy terminals through a resource control terminal, and further selects and uses target instances through the resource proxy terminals. This realizes the sinking of the service corresponding to the processing of business requests from the cloud to the edge nodes closer to the user side. While achieving network domain isolation between the cloud and the user-side edge nodes, it reduces the service pressure on the cloud, lowers the service cost of the cloud, and optimizes the service experience.

[0229] The technical solutions disclosed herein involve the collection, storage, use, processing, transmission, provision, and disclosure of business requests, resource identifiers, instance matching information, resource proxy terminals, service instances, etc., which comply with relevant laws and regulations and do not violate public order and good morals.

[0230] According to embodiments of this disclosure, this disclosure also provides an electronic device, a readable storage medium, and a computer program product.

[0231] Figure 9 A schematic block diagram of an example electronic device 900 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0232] like Figure 9 As shown, device 900 includes a computing unit 901, which can perform various appropriate actions and processes based on a computer program stored in read-only memory (ROM) 902 or a computer program loaded from storage unit 908 into random access memory (RAM) 903. RAM 903 may also store various programs and data required for the operation of device 900. The computing unit 901, ROM 902, and RAM 903 are interconnected via bus 904. Input / output (I / O) interface 905 is also connected to bus 904.

[0233] Multiple components in device 900 are connected to I / O interface 905, including: input unit 906, such as keyboard, mouse, etc.; output unit 907, such as various types of monitors, speakers, etc.; storage unit 908, such as disk, optical disk, etc.; and communication unit 909, such as network card, modem, wireless transceiver, etc. Communication unit 909 allows device 900 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0234] The computing unit 901 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 901 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 901 performs the various methods and processes described above, such as business processing methods. For example, in some embodiments, the business processing method may be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 908. In some embodiments, part or all of the computer program may be loaded and / or installed on device 900 via ROM 902 and / or communication unit 909. When the computer program is loaded into RAM 903 and executed by the computing unit 901, one or more steps of the business processing method described above may be performed. Alternatively, in other embodiments, the computing unit 901 may be configured to perform business processing methods by any other suitable means (e.g., by means of firmware).

[0235] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0236] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0237] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0238] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0239] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with embodiments of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0240] Computer systems can include clients and servers. Clients and servers are generally geographically separated and typically interact via communication networks. The client-server relationship is established by computer programs running on the respective computers and having a client-server relationship with each other. A server can be a cloud server, also known as a cloud computing server or cloud host, a hosting product within the cloud computing service ecosystem that addresses the management difficulties and weak business scalability inherent in traditional physical hosting and VPS services. Servers can also be servers for distributed systems or servers integrated with blockchain technology.

[0241] Artificial intelligence (AI) is the study of enabling computers to simulate certain human thought processes and intelligent behaviors (such as learning, reasoning, thinking, and planning). It encompasses both hardware and software technologies. AI hardware technologies generally include sensors, dedicated AI chips, cloud computing, distributed storage, and big data processing. AI software technologies mainly include computer vision, speech recognition, natural language processing, machine learning / deep learning, big data processing, and knowledge graph technologies.

[0242] Cloud computing refers to a technology system that enables access to a shared pool of physical or virtual resources via a network. These resources can include servers, operating systems, networks, software, applications, and storage devices, and can be deployed and managed on demand and in a self-service manner. Cloud computing technology can provide efficient and powerful data processing capabilities for applications such as artificial intelligence and blockchain, as well as for model training.

[0243] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution provided in this disclosure can be achieved, and this is not limited herein.

[0244] The specific embodiments described above do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure should be included within the scope of protection of this disclosure.

Claims

1. A business processing method applied to a resource proxy deployed on an edge node, the resource proxy being used to perform service supervision on at least a portion of service instances in the cluster to which the deployed edge node belongs, the method comprising: If the instance matches the resource identifier in the business request, obtain the instance matching information in the business request. Based on the instance matching information, a target instance is selected from the service instances deployed in the cluster to which the edge node under its supervision belongs; If the selection is successful, the terminal identification information is sent to the service control terminal so that the service control terminal can respond with the service request based on the terminal identification information. The service request is sent to the target instance for processing.

2. The method according to claim 1, wherein, The instance matching information includes a service identifier; the step of selecting a target instance from the service instances deployed in the cluster to which the edge node belongs, based on the instance matching information, includes: If the business identifier belongs to an incomplete historical business, then the service instance used to execute the corresponding historical business is selected from the service instances deployed in the cluster to which the edge node belongs under its own supervision, and this service instance is selected as the target instance.

3. The method according to claim 1, wherein, The instance matching information includes instance tags; the step of selecting a target instance from the service instances deployed in the cluster to which the edge node belongs, based on the instance matching information, includes: From the service instances deployed in the cluster to which the edge node belongs under its own supervision, select the service instance whose instance tag matches as the target instance.

4. The method according to claim 1, wherein, The instance matching information includes a service identifier; the step of selecting a target instance from the service instances deployed in the cluster to which the edge node belongs, based on the instance matching information, includes: From each service instance deployed on the edge node to which it is under its own supervision, detect at least one available candidate instance; A candidate instance that matches the service identifier is selected as the target instance.

5. The method according to any one of claims 1-4, wherein, The resource proxy is marked among the available resources that match the resource identifier under the namespace of the initiator of the service request.

6. The method according to any one of claims 1-5, wherein, Sending the service request to the target instance includes: Determine the opening mode of the target instance relative to the resource proxy; wherein the opening mode is a single-end opening mode or a cluster opening mode; The service request is sent to the target instance using a secure transmission method that matches the open mode.

7. The method according to any one of claims 1-6, wherein, The method further includes: Determine the current service status of the monitored service instances; Based on the current state of the service, the corresponding service instance is processed; Adjust the current service status of the corresponding service instance based on the processing results.

8. The method according to claim 7, wherein, The current state of the service is either the initial state, the deployment state, the stopped state, the running state, the upgrade-pending state, the disconnected state, the offline state, the abnormal state, or the released state. The initial service state is used to characterize the service instance to be added during the service synchronization phase, which is ready and requires initialization. The service deployment status is used to represent the service deployment phase, where the service instance to be deployed has been successfully initialized and needs to be started; or, in the service upgrade phase, where the service instance to be upgraded has been successfully rebuilt and needs to be restarted. The service stop status is used to indicate that during the service deployment phase, the service instance to be deployed fails to start and needs to be restarted; or, during the service upgrade phase, the service instance to be upgraded successfully terminates the service and needs to be reloaded. The service operation status is used to characterize whether the detected service instance is running normally and requires no intervention during the service exploration phase; or whether the service instance to be upgraded needs to be upgraded during the service upgrade phase; or whether the service instance to be deleted needs to be set to offline status during the service synchronization phase. The service pending upgrade status indicates that during the service upgrade phase, the service instance to be upgraded has been successfully upgraded and needs to be terminated. The service disconnection status is used to characterize the abnormal service instances detected during the service activation phase, and to set the corresponding service instances to a service offline status when the number of service disconnections exceeds the first threshold. The service offline status is used to indicate that the service instance to be offline needs to be destroyed, and the service release status is set for the corresponding service instance after successful destruction. The service anomaly status is used to indicate that the deployment of the service instance to be deployed during the service deployment phase fails, or the upgrade of the service instance to be upgraded during the service upgrade phase fails, and the corresponding service instance needs to be handled by anomaly intervention. The service release status indicates that the service instance to be destroyed has been successfully destroyed.

9. A business processing method, applied to a resource control terminal, comprising: Obtain the resource identifier from the business request and determine the resource proxy deployed on the edge node that matches the resource identifier; The resource proxy is used to monitor at least some service instances in the cluster to which the deployed edge nodes belong; Send the endpoint identifier information of the resource proxy terminal to the business control terminal so that the business control terminal sends the instance matching information in the business request to the corresponding resource proxy terminal to select the target instance deployed in the cluster of the edge node under the supervision of the corresponding resource proxy terminal. The target instance is used to process the business request.

10. The method according to claim 9, wherein, The process of determining the resource proxy deployed on the edge node that matches the resource identifier includes: Under the namespace of the initiator of the service request, identify the available resource that matches the resource identifier; Identify the resource brokers deployed on the edge nodes that are marked by the available resources.

11. The method according to claim 9 or 10, wherein, The method further includes: Determine the current status of the agent on the resource agent side under supervision; Based on the current state of the agent, the corresponding resource agent is processed; Adjust the current proxy status of the corresponding resource proxy based on the processing results.

12. The method according to claim 11, wherein, The current state of the agent is either agent initial state, agent deployment state, agent stopped state, agent running state, agent awaiting upgrade state, agent disconnected state, agent offline state, agent abnormal state, or agent released state. The initial state of the agent is used to represent the state during the agent synchronization phase, where the newly added resource agent is ready and needs to be initialized. The agent deployment status is used to indicate that during the agent deployment phase, the resource agent to be deployed has been successfully initialized and needs to be started; or, during the agent upgrade phase, the resource agent to be upgraded has been successfully rebuilt and needs to be restarted. The agent stop status is used to indicate that during the agent deployment phase, the agent for the resource to be deployed fails to start and needs to be restarted; or, during the agent upgrade phase, the agent for the resource to be upgraded successfully terminates and needs to be reloaded. The agent running status is used to indicate that during the agent detection phase, the detected resource agent is running normally and requires no intervention; or, during the agent upgrade phase, the resource agent to be upgraded needs to be upgraded and updated; or, during the agent synchronization phase, the resource agent to be deleted needs to be set to offline status. The agent pending upgrade status indicates that during the agent upgrade phase, the resource agent to be upgraded has been successfully upgraded and updated, and the agent needs to be terminated. The agent disconnection status is used to characterize the abnormal service instance detected during the agent activation phase, and to set the corresponding resource agent to offline status when the number of agent disconnections exceeds the second threshold. The offline proxy status is used to indicate that the resource proxy client to be offline needs to be destroyed, and after the destruction is successful, the corresponding resource proxy client is set to release proxy status. The abnormal proxy status is used to indicate that the deployment of the resource proxy terminal to be deployed during the proxy deployment phase fails, or the upgrade of the resource proxy terminal to be upgraded during the proxy upgrade phase fails, and abnormal intervention processing is required for the corresponding resource proxy terminal. The agent release status is used to indicate that the resource agent to be destroyed has been successfully destroyed.

13. A business processing method, applied to a business control terminal, comprising: A business request that retrieves instance matching information and resource identifiers; The resource identifier is sent to the resource control terminal so that the resource control terminal can determine and return a resource proxy terminal that matches the resource identifier; the resource proxy terminal is deployed on the edge node; the resource proxy terminal is used to perform service supervision on at least some service instances in the cluster to which the deployed edge node belongs; Send the instance matching information to the matched resource agent so that the resource agent can select a target instance from the service instances deployed in the cluster to which it supervises the edge node according to the instance matching information, and return its own terminal identification information when the selection is successful. The service request is sent to the resource proxy terminal corresponding to the terminal identification information, so that the corresponding resource proxy terminal issues the service request to the target instance for processing.

14. A service processing apparatus, configured on a resource proxy terminal deployed on an edge node, the resource proxy terminal being used to perform service supervision on at least a portion of the service instances in the cluster to which the deployed edge node belongs, the apparatus comprising: The instance matching information acquisition module is used to acquire instance matching information in a business request when it matches the resource identifier in the business request. The target instance selection module is used to select a target instance from the service instances deployed in the cluster to which it is supervised, based on the instance matching information. The terminal identification information sending module is used to send its own terminal identification information to the service control terminal if the selection is successful, so that the service control terminal can respond to the service request based on the terminal identification information. The business request distribution module is used to distribute the business request to the target instance for processing.

15. The apparatus according to claim 14, wherein, The instance matching information includes a business identifier; the target instance selection module is specifically used for: If the business identifier belongs to an incomplete historical business, then the service instance used to execute the corresponding historical business is selected from the service instances deployed in the cluster to which the edge node belongs under its own supervision, and this service instance is selected as the target instance.

16. The apparatus according to claim 14, wherein, The instance matching information includes instance tags; the target instance selection module is specifically used for: From the service instances deployed in the cluster to which the edge node belongs under its own supervision, select the service instance whose instance tag matches as the target instance.

17. The apparatus according to claim 14, wherein, The instance matching information includes a service identifier; the target instance selection module is specifically used for: From each service instance deployed on the edge node to which it is under its own supervision, detect at least one available candidate instance; A candidate instance that matches the service identifier is selected as the target instance.

18. The apparatus according to any one of claims 14-17, wherein, The resource proxy is marked among the available resources that match the resource identifier under the namespace of the initiator of the service request.

19. The apparatus according to any one of claims 14-18, wherein, The service request distribution module includes: An open mode determination unit is used to determine the open mode of the target instance relative to the resource proxy; wherein the open mode is a single-end open mode or a cluster open mode; The service request sending unit is used to send the service request to the target instance using a secure transmission method that matches the open mode.

20. The apparatus according to any one of claims 14-19, wherein, The device further includes: The Service Current Status Determination Module is used to determine the current service status of the monitored service instances; The service instance processing module is used to process the corresponding service instance according to the current state of the service; The Service Current Status Adjustment Module is used to adjust the current status of the corresponding service instance based on the processing status.

21. The apparatus according to claim 20, wherein, The current state of the service is either the initial state, the deployment state, the stopped state, the running state, the upgrade-pending state, the disconnected state, the offline state, the abnormal state, or the released state. The initial service state is used to characterize the service instance to be added during the service synchronization phase, which is ready and requires initialization. The service deployment status is used to represent the service deployment phase, where the service instance to be deployed has been successfully initialized and needs to be started; or, in the service upgrade phase, where the service instance to be upgraded has been successfully rebuilt and needs to be restarted. The service stop status is used to indicate that during the service deployment phase, the service instance to be deployed fails to start and needs to be restarted; or, during the service upgrade phase, the service instance to be upgraded successfully terminates the service and needs to be reloaded. The service operation status is used to characterize whether the detected service instance is running normally and requires no intervention during the service exploration phase; or whether the service instance to be upgraded needs to be upgraded during the service upgrade phase; or whether the service instance to be deleted needs to be set to offline status during the service synchronization phase. The service pending upgrade status indicates that during the service upgrade phase, the service instance to be upgraded has been successfully upgraded and needs to be terminated. The service disconnection status is used to characterize the abnormal service instances detected during the service activation phase, and to set the corresponding service instances to a service offline status when the number of service disconnections exceeds the first threshold. The service offline status is used to indicate that the service instance to be offline needs to be destroyed, and the service release status is set for the corresponding service instance after successful destruction. The service anomaly status is used to indicate that the deployment of the service instance to be deployed during the service deployment phase fails, or the upgrade of the service instance to be upgraded during the service upgrade phase fails, and the corresponding service instance needs to be handled by anomaly intervention. The service release status indicates that the service instance to be destroyed has been successfully destroyed.

22. A business processing device, configured at a resource control terminal, comprising: The resource proxy determination module is used to obtain the resource identifier in the business request and determine the resource proxy deployed on the edge node that matches the resource identifier. The resource proxy is used to monitor at least some service instances in the cluster to which the deployed edge nodes belong; The endpoint identification information sending module is used to send the endpoint identification information of the resource proxy to the business control terminal, so that the business control terminal sends the instance matching information in the business request to the corresponding resource proxy to select the target instance deployed in the cluster of the edge node under the supervision of the corresponding resource proxy. The target instance is used to process the business request.

23. The apparatus according to claim 22, wherein, The resource proxy determination module includes: The available resource determination unit is used to determine, within the namespace of the initiator of the service request, an available resource that matches the resource identifier; The resource proxy determination unit is used to determine the resource proxy deployed on the edge node that is marked by the available resources.

24. The apparatus according to claim 22 or 23, wherein, The device further includes: The proxy current status determination module is used to determine the current proxy status of the monitored resource proxy. The resource proxy processing module is used to process the corresponding resource proxy based on the current state of the proxy. The proxy current status adjustment module is used to adjust the current proxy status of the corresponding resource proxy based on the processing situation.

25. The apparatus according to claim 24, wherein, The current state of the agent is either agent initial state, agent deployment state, agent stopped state, agent running state, agent awaiting upgrade state, agent disconnected state, agent offline state, agent abnormal state, or agent released state. The initial state of the agent is used to represent the state during the agent synchronization phase, where the newly added resource agent is ready and needs to be initialized. The agent deployment status is used to indicate that during the agent deployment phase, the resource agent to be deployed has been successfully initialized and needs to be started; or, during the agent upgrade phase, the resource agent to be upgraded has been successfully rebuilt and needs to be restarted. The agent stop status is used to indicate that during the agent deployment phase, the agent for the resource to be deployed fails to start and needs to be restarted; or, during the agent upgrade phase, the agent for the resource to be upgraded successfully terminates and needs to be reloaded. The agent running status is used to indicate that during the agent detection phase, the detected resource agent is running normally and requires no intervention; or, during the agent upgrade phase, the resource agent to be upgraded needs to be upgraded and updated; or, during the agent synchronization phase, the resource agent to be deleted needs to be set to offline status. The agent pending upgrade status indicates that during the agent upgrade phase, the resource agent to be upgraded has been successfully upgraded and updated, and the agent needs to be terminated. The agent disconnection status is used to characterize the abnormal service instance detected during the agent activation phase, and to set the corresponding resource agent to offline status when the number of agent disconnections exceeds the second threshold. The offline proxy status is used to indicate that the resource proxy client to be offline needs to be destroyed, and after the destruction is successful, the corresponding resource proxy client is set to release proxy status. The abnormal proxy status is used to indicate that the deployment of the resource proxy terminal to be deployed during the proxy deployment phase fails, or the upgrade of the resource proxy terminal to be upgraded during the proxy upgrade phase fails, and abnormal intervention processing is required for the corresponding resource proxy terminal. The agent release status is used to indicate that the resource agent to be destroyed has been successfully destroyed.

26. A business processing device, configured at a business control center, comprising: The business request acquisition module is used to acquire business requests, including instance matching information and resource identifiers; The resource identifier sending module is used to send the resource identifier to the resource control terminal, so that the resource control terminal can determine and return the resource proxy terminal that matches the resource identifier; the resource proxy terminal is deployed on the edge node; the resource proxy terminal is used to perform service supervision on at least some service instances in the cluster to which the deployed edge node belongs; The instance matching information sending module is used to send the instance matching information to the matched resource agent, so that the resource agent can select a target instance from the service instances deployed in the cluster to which it supervises the edge node according to the instance matching information, and return its own terminal identification information when the selection is successful. The service request sending module is used to send the service request to the resource proxy terminal corresponding to the terminal identification information, so that the corresponding resource proxy terminal sends the service request to the target instance for processing.

27. An electronic device comprising: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the business processing method according to any one of claims 1-13.

28. A non-transitory computer-readable storage medium storing computer instructions, wherein, The computer instructions are used to cause the computer to execute the business processing method according to any one of claims 1-13.

29. A computer program product comprising a computer program / instructions that, when executed by a processor, implement the steps of the business processing method according to any one of claims 1-13.

Images