CN116545955A

CN116545955A - Service processing method, device, equipment and storage medium

Info

Publication number: CN116545955A
Application number: CN202310263842.5A
Authority: CN
Inventors: 叶青; 李莅
Original assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Current assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Priority date: 2023-03-17
Filing date: 2023-03-17
Publication date: 2023-08-04

Abstract

The disclosure provides a service processing method, a device, equipment and a storage medium, relates to the technical field of computers, and particularly relates to the technical field of cloud computing. The specific implementation scheme is as follows: acquiring instance matching information in a service request under the condition that the resource agent end deployed at an edge node is matched with a resource identifier in the service request; selecting a target instance from service instances which are supervised by the user and are deployed in a cluster to which the edge node belongs according to the instance matching information; if the selection is successful, the terminal identification information of the terminal is sent to a service central control terminal, so that the service central control terminal feeds back the service request according to the terminal identification information; and issuing the service request to the target instance for processing. According to the technology disclosed by the invention, the sinking of the cloud computing service to the edge node is realized, and the service pressure and the service cost of the cloud computing resource are reduced.

Description

Service processing method, device, equipment and storage medium

Technical Field

The disclosure relates to the field of computer technology, and in particular to the field of cloud computing technology.

Background

The public cloud big data platform provides cloud computing resources for multi-tenant distributed data sources, integrates basic application platforms for data integration, development and analysis, and supports upper data applications such as modeling, quality monitoring, blood margin analysis, circulation service and the like.

Disclosure of Invention

The present disclosure provides a service processing method, apparatus, device and storage medium.

According to an aspect of the present disclosure, there is provided a service processing method applied to a resource proxy deployed at an edge node, including:

under the condition that the self is matched with the resource identification in the service request, acquiring instance matching information in the service request;

selecting a target instance from service instances which are supervised by the user and are deployed in a cluster to which the edge node belongs according to the instance matching information;

if the selection is successful, the terminal identification information of the terminal is sent to the service center control terminal, so that the service center control terminal feeds back a service request according to the terminal identification information;

and issuing a service request to the target instance for processing.

According to another aspect of the present disclosure, there is further provided a service processing method, applied to a resource central control end, including:

acquiring a resource identifier in a service request, and determining a resource agent end which is matched with the resource identifier and is deployed at an edge node;

the method comprises the steps of sending terminal identification information of a resource agent terminal to a service central control terminal, so that the service central control terminal sends instance matching information in a service request to a corresponding resource agent terminal, and selecting a target instance which is supervised by the corresponding resource agent terminal and deployed in a cluster to which an edge node belongs;

The target instance is used to process the service request.

According to another aspect of the present disclosure, there is further provided a service processing method, applied to a service central control end, including:

acquiring a service request comprising instance matching information and a resource identifier;

the resource identification is sent to the resource central control end, so that the resource central control end determines and feeds back a resource agent end matched with the resource identification;

the method comprises the steps of sending instance matching information to a matched resource agent end, enabling the resource agent end to select a target instance from service instances which are supervised by the resource agent end and deployed in a cluster to which an edge node belongs according to the instance matching information, and feeding back end identification information of the resource agent end when selection is successful;

and sending the service request to the resource agent end corresponding to the end identification information, so that the corresponding resource agent end sends the service request to the target instance for processing.

According to another aspect of the present disclosure, there is also provided an electronic device including:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform any one of the service processing methods provided by the embodiments of the present disclosure.

According to another aspect of the present disclosure, there is also provided a non-transitory computer-readable storage medium storing computer instructions for causing a computer to execute any one of the service processing methods provided by the embodiments of the present disclosure.

According to the technology disclosed by the invention, the sinking of the cloud computing service to the edge node is realized, and the service pressure and the service cost of the cloud computing resource are reduced.

It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following specification.

Drawings

The drawings are for a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:

fig. 1 is a frame diagram of a cloud platform service system provided in an embodiment of the present disclosure;

fig. 2A is a flowchart of a service processing method provided in an embodiment of the present disclosure;

FIG. 2B is a schematic diagram of a change of state of a service instance provided by an embodiment of the present disclosure;

FIG. 3A is a flow chart of another business processing method provided by an embodiment of the present disclosure;

FIG. 3B is a schematic diagram illustrating a state change of a resource agent according to an embodiment of the present disclosure;

FIG. 4 is a flowchart of another business processing method provided by an embodiment of the present disclosure;

FIG. 5 is a diagram of a cloud data platform service sinking aggregate architecture provided by an embodiment of the present disclosure;

fig. 6 is a block diagram of a service processing apparatus according to an embodiment of the present disclosure;

fig. 7 is a block diagram of another service processing apparatus according to an embodiment of the present disclosure;

fig. 8 is a block diagram of yet another service processing apparatus provided in an embodiment of the present disclosure;

fig. 9 is a block diagram of an electronic device for implementing a business processing method of an embodiment of the present disclosure.

Detailed Description

Exemplary embodiments of the present disclosure are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present disclosure to facilitate understanding, and should be considered as merely exemplary. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

In order to clearly introduce the technical scheme of the present disclosure, first, a cloud platform service system according to an embodiment of the present disclosure is briefly described.

Referring to a framework diagram of the cloud platform service system shown in fig. 1, the framework diagram includes a service central control end 10, a resource central control end 20 and an edge node 30. Wherein, the service central control end 10 is respectively in communication connection with the resource central control end 20 and the edge node 30.

Wherein, the number of the edge nodes 30 is at least one, and each edge node 30 is provided with a resource agent end and a service instance; the resource agent is configured to perform service supervision on at least some service instances in the cluster to which the deployed edge node 30 belongs. Wherein, at least part of the service instances can be the service instances in the edge nodes deployed by the service instances per se, and can also comprise the service instances in the edge nodes deployed by the service instances not per se in the cluster.

The service layer of the service central control terminal 10 is provided with a service SDK (Software Development Kit ) for acquiring service requests of different categories.

The resource central control end 20 is configured to manage resources in the cluster resources to which the edge nodes 30 belong and resource agent ends deployed in the edge nodes 30. And meanwhile, determining a resource agent end capable of forwarding the service request according to the managed data.

The resource proxy in the edge node 30 is configured to select a target instance for actually processing the service request from the managed service instances, and forward the service request to the corresponding target instance for service processing.

On the basis of the cloud platform service system shown in fig. 1, the disclosure provides a service processing method using different devices as execution bodies and a service processing device configured in the corresponding execution bodies, which are used for processing service requests in the cloud platform service system. For ease of understanding, the service processing method will be described in detail first.

Referring to fig. 2A, the service processing method applied to a resource agent deployed at an edge node includes:

s201, under the condition that the self is matched with the resource identification in the service request, obtaining the instance matching information in the service request.

When the cloud platform user has service requirements, the service request is initiated to the cloud platform service system and is captured by the service central control end, and then subsequent processing is carried out.

Illustratively, a resource identifier may be included in the service request to characterize the resource demand situation for processing the service request. The resource identifier may be embodied in a name or identifier, and the specific presentation form of the resource identifier is not limited in this disclosure.

The resource agent end is matched with the resource identifier in the service request, which can be understood as the resource requirement matched with the resource identifier can be provided for the processing of the service request in the service instance supervised by the resource agent end.

For example, different available resources may be preset under the namespace of the initiator of the service request, where the different available resources are pre-marked with resource agent ends for performing different resource supervision. Correspondingly, a resource proxy end matched with a resource identifier in a service request can be understood as the resource proxy end marked in available resources matched with the resource identifier under the name space of the initiator of the service request.

It can be understood that the namespaces are introduced to perform resource identification matching and resource agent end marking, so that the initiator of the service request has the use authority of the matched resource agent end, and the safety of service request processing is improved. Meanwhile, the resources monitored by the resource agent end have available resources matched with the resource identification, so that the effective processing of the service request is ensured.

For example, the service request may include instance matching information, which is used to characterize the service requirement situation in at least one dimension when the service request is processed, and is used as a reference basis for selecting a subsequent target instance.

Optionally, the instance matching information may include a service identifier, which is used to characterize a service to be processed corresponding to the service request. Or alternatively, the instance matching information may include an instance tag for specifying a service instance for processing the corresponding service request. Or alternatively, the instance matching information may include a service identifier for characterizing a service requirement situation of a service instance handling the corresponding service request.

For example, the resource agent end matched with the resource identifier in the service request can receive the service request and then extract the instance matching information in the service request; or directly receives instance matching information in the service request.

S202, selecting a target instance from service instances which are supervised by the user and are deployed in a cluster to which the edge node belongs according to instance matching information.

Because the resource agent end is deployed on the edge nodes in the cluster resource, at least one edge node of the cluster resource is deployed with service examples for providing different services, and the different resource agent ends monitor the different service examples in the cluster resource, the target examples for processing the service requests can be selected from all the service examples monitored by the resource agent end according to the example matching information.

In an alternative embodiment, the instance matching information may include a service identification; correspondingly, a target instance for processing the service request can be selected from service instances which are supervised by the user and are deployed in the cluster to which the edge node belongs according to the historical processing condition of the service corresponding to the service identifier.

For example, if the service identifier belongs to an incomplete history service, such as an interrupt service, a pause service, or a cancel service, it indicates that a service instance has been previously allocated to the history service, so that a service instance adopted for executing the corresponding history service may be selected from service instances that are self-supervised and deployed in a cluster to which the edge node belongs, and be used as a target instance. The method has the advantages that the distributed service instance is multiplexed to serve as the target instance, the selection process of the target instance is simplified on the basis that the selected target instance can effectively execute the service request, and the service processing efficiency is improved.

In another alternative embodiment, the instance matching information may include an instance tag; correspondingly, the service instance with the matched instance label can be selected from the service instances which are supervised by the user and are deployed in the cluster to which the edge node belongs, and the service instance is taken as a target instance.

Wherein the instance tag can uniquely characterize the marked service instance for distinguishing between different service instances. The instance tag may be presented by way of instance name or identifier, and the specific presentation manner of the instance tag is not limited in this disclosure.

It can be understood that by adding an instance tag to the service request and designating the service instance for processing the service request, the customized requirement of the initiator of the service request can be satisfied, and the flexibility and convenience of selecting the service instance are improved.

In yet another alternative embodiment, the instance matching information may include a service identification; correspondingly, at least one available candidate instance can be detected from each service instance which is self-supervised and is deployed in the cluster to which the edge node belongs; and selecting the candidate instance matched with the service identification as a target instance.

The resource agent terminal can detect and activate each service instance supervised by the resource agent terminal in real time or at fixed time, and takes each surviving service instance as a candidate instance; and selecting a candidate instance matched with the service identifier from the candidate instances, namely, a candidate instance for providing the service required by the service identifier as a target instance.

For example, the resource agent may obtain a service name from a static single-instance routeMap (routing policy), and obtain service instance information corresponding to the service name from a local instance data cache, to obtain a service state, a port number, and the like; and intercepting the end identification information of the resource proxy end from the URL (Universal Resource Locator, uniform resource locator) of the acquired service request, generating a proxy request, packaging the proxy request and then issuing the proxy request to the selected target instance.

It can be understood that the service identifier is introduced to select the target instance, so that the situation that the selected target instance cannot process the service request and provide corresponding service can be avoided, and the effectiveness of service request processing is ensured.

And S203, if the selection is successful, the terminal identification information of the terminal is sent to the service center control terminal, so that the service center control terminal feeds back a service request according to the terminal identification information.

If the selection is successful, the fact that the service instance capable of processing the service request exists in the service instances supervised by the resource agent end is indicated; if the selection fails, the fact that the service instance capable of processing the service request does not exist in the service instances supervised by the resource agent end is indicated.

The terminal identification information can uniquely characterize the resource agent terminal and is used for distinguishing different resource agent terminals. Only the successful resource agent end is selected to feed back the end identification information of the resource agent end to the service central control end, so that the service central control end can effectively acquire the operation main body for forwarding the service request, and the situation of the error sending of the service request is avoided.

S204, service requests are issued to the target instance for processing.

After the resource agent receives the service request sent by the service central control end, the service request can be directly forwarded to the target instance for the target instance to process the service request. Or, alternatively, after the service request is processed for the second time, the processed target request is sent to the target instance, so that the target instance can process the service request.

In an alternative embodiment, the resource agent end can also obtain the service description information required for processing the service request from the service central control end or other parties; correspondingly, the resource agent can encapsulate the service description information and the service request to obtain encapsulation data, and forward the encapsulation data to the target instance for the target instance to process the service request based on the encapsulation data.

Because different target examples have different opening scales on resource agent ends in clusters to which the edge nodes belong, certain differences exist in the available safe transmission modes of different opening scales. Therefore, the selection of the secure transmission mode can be performed according to different open scales, and further the service request is issued to the target instance through the selected secure transmission mode.

Illustratively, determining a development mode of the target instance relative to the resource agent end; wherein the open mode is a single-ended open mode or a cluster open mode; and adopting a safe transmission mode matched with the open mode to issue a service request to the target instance.

The single-ended open mode can be understood as a condition that in each resource agent end of the cluster to which the edge node belongs, the target instance is only used exclusively by the current resource agent end; the cluster open mode may be understood as a condition that, in each resource agent in the cluster to which the edge node belongs, the target instance is available for any resource agent in the cluster.

Optionally, in the single-ended open mode, a certificate encryption mechanism based on SSL (Secure Sockets Layer, secure socket layer) or HTTPS (Hypertext Transfer Protocol Secure, hypertext transfer security) protocol may be introduced to issue data to the target instance, so that the security of communication between the resource agent and the target instance is improved because the target instance only trusts the data sent by the dedicated resource agent. For example, a black-and-white list mechanism can be introduced on the basis of the transmission protocol, so that the communication security is further improved.

Optionally, in a cluster open mode, an RPC (Remote Procedure Call Protocol ) service may be introduced, and in combination with a cluster blacklist security policy, secure access of data in the cluster is achieved.

In the single-ended open mode, each resource agent can provide access interfaces for the originators of different service requests, so that each initiator is allowed to log in the cluster through the corresponding resource agent, and service data access and the like are performed on the edge nodes deployed by the corresponding resource agent.

It can be understood that by introducing different security transmission modes, the method is suitable for the security data transmission to the target instance in different open modes, thereby improving the diversity and universality of the service request issuing mode and simultaneously improving the security of service request issuing.

In an alternative embodiment, after the target instance processes the service request, service data corresponding to the service request is generated; correspondingly, the target instance feeds back service data to the resource agent end sending the service request, and the resource agent end transfers the service data to the service central control end for output or subsequent processing. It can be understood that the service request issuing path can be multiplexed in the service data returning process, so that the service data returning safety can be ensured.

According to the embodiment of the disclosure, the resource agent end is deployed in the edge node, and the target instance is selected and used through the resource agent end, so that the service corresponding to the processing service request is realized, the cloud end sinks towards the edge node close to the user side, the cloud end service pressure is reduced while the network domain isolation of the cloud end and the edge node of the user side is realized, the cloud end service cost is reduced, and the service experience is optimized. Meanwhile, resource agent end deployment is carried out in the edge nodes of the cluster, so that transverse expansion is facilitated.

Based on the technical schemes, a management mechanism for the service instance can be introduced at the resource agent end so as to improve the convenience of service instance management.

In an alternative embodiment, the current state of service of the managed service instance may be determined; processing the corresponding service instance according to the current state of the service; and adjusting the current service state of the corresponding service instance according to the processing condition.

The service current state of the service instance is used for representing the stage of the corresponding service instance in the life cycle and indicating what kind of processing is needed to be carried out on the service instance subsequently, so that adjustment or conversion of the service current state is realized. Wherein, the life cycle can comprise at least one of a service synchronization stage, a service establishment stage, a service operation stage, a service detection stage, a service upgrading stage, a service destruction stage and the like. Wherein, the different phases can be related by changing the current state of the service. The different stages can be automatically triggered to switch in by a technician according to actual demands, switch in through service current state conversion of other stages, switch in real time or at a fixed time by setting a preset service thread, and the like.

It can be understood that by introducing the current state of the service, the service instance is processed, the service instance is gradually adjusted to the expected state, the automatic management of the resource agent end on the supervised service instance is realized, and the convenience and standardization of the management process are improved.

The service current state may be a service initial state, a service setup state, a service stop state, a service running state, a service to-be-upgraded state, a service disconnection state, a service offline state, a service abnormal state, or a service release state.

The service initial state is used for representing that the newly added service instance is ready to be completed in the service synchronization stage, and initialization processing is needed. The service provisioning state is used for representing a service provisioning stage, and a service instance to be built is successfully initialized and needs to be started; or, the characterization is successful in reconstructing the service instance to be upgraded in the service upgrading stage, and the restarting treatment is needed. The service stop state is used for representing that in a service establishment stage, a service instance to be established fails to be started and needs to be restarted; or in the service upgrading stage, the service of the service instance to be upgraded is terminated successfully, and reloading processing is needed. The service running state is used for representing that the detected service instance normally runs in the service detection and activation stage without intervention; or in the service upgrading stage, the service instance to be upgraded needs to be upgraded and updated; or in the service synchronization stage, service downloading state setting needs to be carried out on the service instance to be deleted. The service to-be-upgraded state is used for representing that the service instance to be upgraded is successfully upgraded and updated in the service upgrading stage, and service termination processing is needed. The service disconnection state is used for representing the abnormal service instance detected in the service activation detection stage, and when the service disconnection times exceed a first time threshold value, service disconnection state setting is carried out on the corresponding service instance. The service down state is used for representing the service instance needing to be subjected to the destruction treatment, and setting the service release state of the corresponding service instance after the destruction is successful. The service abnormal state is used for representing the failure of service instance construction to be constructed in the service construction stage or the failure of service instance upgrading to be upgraded in the service upgrading stage, and abnormal intervention processing is required for the corresponding service instance. The service release state is used for representing success in destroying the service instance to be destroyed.

The following describes the state change procedure of the service instance in different situations in detail with reference to the schematic state change diagram of the service instance shown in fig. 2B.

In a specific implementation manner, in a service synchronization stage, service change detection is performed in real time or at fixed time through a service update thread; and if the new service is detected to be added, performing a preliminary preparation operation (such as generating and recording the new service instance) of the service instance to be added, and setting the corresponding service instance to be in a service initial state after the preparation is completed so as to enter a service configuration stage subsequently. If the service deletion is detected to be needed (if the service instance is invalid), the service instance to be deleted is set to be in a service offline state so as to enter a service destruction stage subsequently.

In another specific implementation manner, in a service provisioning stage, initializing a service instance to be provisioned in a service initial state (such as creating a path, establishing a secure communication connection to perform dependent package copying, executing environment construction, directory creation and authorization, and container mounting), and setting the service instance successfully initialized as a service provisioning state; and setting the service instance with failed initialization as a service abnormal state for indicating abnormal intervention on the corresponding service instance. Further, in the service provisioning stage, a service instance in a service provisioning state is started (such as generating a process lock for realizing process daemon, generating a port file for collecting a monitored service instance, etc.), a service instance which is successfully started is set to a service running state, and a service instance which is failed to start is set to a service stopping state; and restarting the service instance in the service stop state, setting the service instance which is successfully restarted as a service running state, and setting the service instance which is failed to restart as a service abnormal state, wherein the service abnormal state is used for indicating abnormal intervention on the corresponding service instance.

In a further specific implementation manner, in a service probing stage, detecting whether a service instance runs normally or not through a service protection sub-thread; setting a normally running service instance as a service running state, recording task loads and the like, and needing no other intervention; setting the detected service instance which is not in accordance with the version as a service stop state (if the task load corresponds to the idle mark, the service stop state is set directly; if the task load corresponds to the non-idle mark, the service stop state is set after the detection is continued until the idle state is detected); setting the abnormal service instance as a service disconnection state; and setting the service instance of which the service disconnection times exceed the first time number threshold (which can be set manually according to requirements or experience) as a service offline state.

In the next concrete implementation mode, in a service upgrading stage, upgrading and updating are carried out on the service instance to be upgraded in the service running state, the service instance to be upgraded which is successfully upgraded and updated is set to be in the service upgrading state, and the service instance to be upgraded which is failed to be upgraded and updated is set to be in the service running state. Further, service stopping processing is performed on the service instance to be upgraded in the state to be upgraded, the service instance to be upgraded which is successfully stopped is set to be in a service stopping state, and the service instance to be upgraded which is failed to stop is set to be in a service abnormal state. Further, the service instance to be upgraded in the service stop state is reloaded, the service instance to be upgraded which is reloaded successfully is set to be in a service setup state, and the service instance to be upgraded which is not reloaded successfully is set to be in a service abnormal state. Further, the service instance to be upgraded in the service configuration state is started, the service instance to be upgraded which is successfully started is set to be in a service running state, and the service instance to be upgraded which is failed to start is set to be in a service abnormal state.

In still another specific implementation manner, in a service destruction stage, destruction processing (such as cleaning job data and logs, destroying deployment information, etc.) is performed on the service instance to be offline in the service offline state, the service instance to be offline that is destroyed successfully is set to a service release state, and the service instance to be offline that is destroyed failed is set to a service offline state.

According to the embodiment of the disclosure, the processing operation and state adjustment conditions indicated by the specific state information of the current state of the service and the different state information are further refined, so that the accuracy and effectiveness of the resource agent end in managing the supervised service instance are improved, and the autonomous ecological stability of the service instance in the resource cluster is effectively maintained.

The service processing method is described in detail by taking the resource agent end deployed at the edge node as the execution main body. The business processing procedure will be described in detail below with the resource central control end as the execution subject.

Referring to fig. 3A, a service processing method is applied to a resource central control end, and includes:

s301, acquiring a resource identifier in the service request, and determining a resource agent end which is matched with the resource identifier and is deployed at the edge node.

Optionally, the resource central control end may receive the service request and extract the resource identifier in the service request; or alternatively, the resource central control terminal directly receives the resource identifier in the service request for subsequent processing.

In an alternative embodiment, the resources under different resource identifiers may be labeled in advance, and the corresponding resource agent end determines the resource agent end matched with the resource identifier according to the labeling relationship.

The cloud platform service system provides available resources for a large number of requested sponsors in a resource sharing mode, and the available resources corresponding to different sponsors have certain difference due to different use authorities. For convenience in management, different namespaces can be preset for different originators, available resources are set under the corresponding namespaces, and resource agent ends for managing the corresponding available resources are marked. Correspondingly, under the name space of the initiator of the service request, determining available resources matched with the resource identification; and determining a resource agent end which is marked by the available resources and is deployed at the edge node.

The naming space is a special abstraction of the scope, and by setting different naming spaces for different sponsors, the occurrence of data confusion among the naming spaces of different sponsors is avoided. The name space of the initiator records a resource label corresponding to the resource with the use authority of the initiator, namely the available resource, and a resource agent end for managing the available resource is marked under the available resource. The resource tag may include at least one of a reference class tag, a cluster application class tag, a node tag, and the like. The reference class label is used for representing the reference end information of the resource, and can comprise a VPC (Virtual Private Cloud ) mark or a queue mark and the like; the cluster application class label is used for representing basic information of a cluster to which the resource belongs, and can comprise a distributed component deployed, a corresponding version number and the like; the node tag is used to represent basic information of resource nodes (such as edge nodes) for deploying corresponding resources, and may include, for example, node types, node loads, node weights, and the like. The node type may be a master node (master), a core node (core), a task node (task), a client (client) type, or the like.

It can be understood that by introducing a resource tag system, abstract description heterogeneous clusters, queues, nodes or containers and the like, a tag library can be constructed in a mode based on dynamic configuration, service registration, component monitoring mechanism and the like, and the tag library is used as a basis for target service discovery and service request forwarding, so that the efficiency and accuracy of target service discovery are improved, and the timeliness and accuracy of service processing are improved.

The embodiment of the disclosure carries out available resources by introducing the namespaces and marks the resource agent ends for managing the available resources, is convenient for managing the available resources of different originators and the resource agent ends thereof, improves the management convenience, simultaneously avoids the occurrence of wrong selection of the resource agent ends, and improves the accuracy of the determination result of the resource agent ends.

S302, sending terminal identification information of a resource agent terminal to a service central control terminal, so that the service central control terminal sends instance matching information in a service request to a corresponding resource agent terminal, and selecting a target instance which is supervised by the corresponding resource agent terminal and deployed in a cluster to which an edge node belongs; the target instance is used to process the service request.

The terminal identification information of the resource agent terminal matched with the resource identification is sent to the service central control terminal, so that the service central control terminal only needs to send the instance matching information or the service request comprising the instance matching information to the part of resource agent terminals in the follow-up, the situation that data leakage occurs when data is sent to the unmatched resource agent terminals in a trade way is avoided, meanwhile, the endless occupation of transmission bandwidth is avoided, and the data transmission resources are saved. In addition, the unmatched resource agent end does not need to execute the selection operation of the target instance, so that the endless waste of computing resources is avoided.

According to the embodiment of the disclosure, the resource agent end is deployed in the edge node, the resource central control end performs matching selection of the resource agent end, and further the selected resource agent end performs selection and use of the target instance, so that the service corresponding to the processing service request is realized, the cloud end sinks towards the edge node close to the user side, the cloud end and the network domain of the edge node at the user side are isolated, the service pressure of the cloud end is reduced, the service cost of the cloud end is reduced, and the service experience is optimized.

Based on the technical schemes, a management mechanism for the resource agent end can be introduced into the resource central control end so as to improve the convenience of the resource agent end management.

In an alternative embodiment, the proxy current state of the supervised resource proxy may be determined; processing the corresponding resource agent end according to the current state of the agent; and adjusting the current state of the proxy of the corresponding resource proxy end according to the processing condition.

The proxy current state of the resource proxy end is used for representing the stage of the corresponding resource proxy end in the life cycle and indicating what kind of processing is needed to be carried out on the resource proxy end subsequently, so that adjustment or conversion of the current state is realized. The lifecycle may include, among other things, a proxy synchronization phase, a proxy setup phase, a proxy run phase, a proxy probe phase, a proxy upgrade phase, and a proxy destruction phase. Wherein, the different phases can be related by changing the current state of the agent. The different stages may be automatically triggered to switch in by a technician according to actual needs, switch in by changing the current state of agents in other stages, switch in real time or in a fixed time by setting a preset agent thread, etc., and the specific switch-in modes of the different stages are not limited in the disclosure.

It can be understood that the current state of the agent is introduced to process the resource agent end, so that the resource agent end is gradually adjusted to the expected state, the automatic management of the resource center control end on the supervised resource agent end is realized, and the convenience and standardization of the management process are improved.

The current state of the agent can be an initial state of the agent, an agent setup state, an agent stop state, an agent running state, an agent to-be-upgraded state, an agent disconnection state, an agent abnormal state, an agent release state or the like.

The agent initial state is used for representing that in an agent synchronization stage, a resource agent end to be newly added is ready to be completed and needs to be initialized. The agent provisioning state is used for representing the agent provisioning stage, the resource agent end to be built is successfully initialized, and the starting processing is needed; or, the representation is successfully rebuilt at the resource agent end to be upgraded in the agent upgrading stage, and restarting treatment is needed. The agent stop state is used for representing that in the agent establishment stage, the resource agent end to be established fails to start and needs to be restarted; or in the proxy upgrading stage, the proxy is successfully terminated at the resource proxy end to be upgraded, and reloading processing is needed. The agent running state is used for representing that the detected resource agent end normally runs in the agent probing stage without intervention; or in the agent upgrading stage, the resource agent end to be upgraded needs to be upgraded and updated; or in the proxy synchronization stage, proxy downlink state setting needs to be carried out on the resource proxy end to be deleted. The agent to-be-upgraded state is used for representing that the resource agent end to be upgraded is successfully upgraded and is required to be subjected to termination agent processing in the agent upgrading stage. The proxy disconnection state is used for representing the abnormal resource proxy end in the proxy detection and activation stage, and when the proxy disconnection times exceed a second time threshold, proxy downlink state setting is carried out on the corresponding resource proxy end. The proxy down-line state is used for representing that the resource proxy end to be offline needs to be destroyed, and setting the proxy release state of the corresponding resource proxy end after the destruction is successful. The agent abnormal state is used for representing the resource agent end to be built in the agent building stage to be built failure or the resource agent end to be upgraded in the agent upgrading stage to be upgraded failure, and abnormal intervention processing is needed for the corresponding resource agent end. The agent release state is used for representing successful end destruction of the resource agent to be destroyed.

The following will describe the state change process of the resource agent in different situations in detail with reference to the state change schematic diagram of the resource agent shown in fig. 3B.

In a specific implementation manner, in a proxy synchronization stage, proxy change detection is performed in real time or at a fixed time through a proxy update thread; if it is detected that the agent needs to be newly added (such as edge node newly added or cluster expansion, etc.), performing a preliminary preparation operation (such as generating and recording a newly added resource agent) of the resource agent to be newly added, and setting the corresponding resource agent to be in an agent initial state after preparation is completed, so as to enter an agent configuration stage subsequently. If it is detected that proxy deletion is required (such as a resource proxy end without any service instance supervision, a deletion of an edge node, or cluster capacity reduction, etc.), the resource proxy end to be deleted is set to be in a proxy offline state, so that a proxy destruction stage is entered subsequently.

In another specific implementation manner, in the agent provisioning stage, initializing a resource agent end to be built in an agent initial state (such as deployment catalog detection, authority detection, trust establishment, certificate downloading, dependence package downloading, installation environment preparation and the like), and setting the resource agent end which is successfully initialized as an agent provisioning state; and setting the resource agent end with failed initialization as an agent abnormal state, and indicating abnormal intervention on the corresponding resource agent end. Further, in the proxy setup stage, starting processing (such as daemon process creation, process lock verification, log verification, daemon starting and the like) is performed on the resource proxy end in the proxy setup state, the resource proxy end which is successfully started is set to be in a proxy running state, and the resource proxy end which is failed to start is set to be in a proxy stopping state; and restarting the resource agent terminal in the agent stop state, setting the resource agent terminal which is successfully restarted as an agent running state, setting the resource agent terminal which is failed to restart as an agent abnormal state, and indicating to perform abnormal intervention on the corresponding resource agent terminal.

In a further specific implementation manner, in the proxy probe activity stage, detecting whether the resource proxy end operates normally or not through a proxy keep-alive thread (acquiring information such as a state, a port, an active version and the like through a heartbeat request, and performing memory data persistence and the like); setting a normally operated resource agent end as an agent operation state, recording task loads and the like without other intervention; setting the resource agent end which is detected to be inconsistent with the version as an agent stop state (if the task load corresponds to the idle mark, the agent stop state is set directly; if the task load corresponds to the non-idle mark, the agent stop state is set after the detection is continued until the idle state is detected); setting the resource agent end for detecting the abnormality as an agent disconnection state; and setting the resource proxy end of which the proxy disconnection times exceed a second time threshold (which can be set manually according to requirements or experience) as a proxy offline state.

In the next concrete implementation mode, in the proxy upgrading stage, upgrading and updating are carried out on the resource proxy end to be upgraded in the proxy running state, the resource proxy end to be upgraded which is successfully upgraded and updated is set to be in the state to be upgraded, and the resource proxy end to be upgraded which is failed to be upgraded and updated is set to be in the proxy running state. Further, the agent stopping process is carried out on the resource agent end to be upgraded in the state to be upgraded, the resource agent end to be upgraded which is successfully stopped is set to be in the agent stopping state, and the resource agent end to be upgraded which is failed to be stopped is set to be in the agent abnormal state. Further, the resource agent end to be upgraded in the agent stop state is subjected to reloading processing, the resource agent end to be upgraded which is successfully reloaded is set to be in an agent setup state, and the resource agent end to be upgraded which is failed to be reloaded is set to be in an agent abnormal state. Further, the resource agent end to be upgraded in the agent setup state is started, the resource agent end to be upgraded which is successfully started is set to be in an agent running state, and the resource agent end to be upgraded which is failed to start is set to be in an agent abnormal state.

In still another specific implementation manner, in the agent destruction stage, destruction processing (such as forwarding or transmission interruption, stopping offline service, data cleaning, main process exit, etc.) is performed on the to-be-offline resource agent end of the agent offline state, the to-be-offline resource agent end which is destroyed successfully is set to an agent release state, and the to-be-offline resource agent end which is destroyed failed is set to an agent offline state.

According to the embodiment of the disclosure, the processing operation and state adjustment conditions indicated by the specific state information and the different state information of the current state of the proxy are further refined, so that the accuracy and effectiveness of the resource proxy for managing the supervised resource proxy are improved, and the autonomous ecological stability of the resource proxy in the resource cluster is effectively maintained.

The service processing method is described in detail above by taking the resource central control terminal as an execution subject. The service processing procedure will be described in detail below with the service central control end as the execution subject.

Referring to fig. 4, the service processing method includes:

s401, acquiring a service request comprising instance matching information and a resource identifier.

S402, the resource identification is sent to the resource central control end, so that the resource central control end determines and feeds back a resource agent end matched with the resource identification.

Optionally, the service central control end may directly send the service request to the resource central control end, and the resource central control end extracts the resource identifier in the service request; or alternatively, the service central control end directly sends the resource identifier in the service request to the resource central control end for subsequent processing.

In an alternative embodiment, the resource central control end may annotate the resources under different resource identifiers in advance, and determine the resource proxy end matched with the resource identifier according to the annotation relationship.

S403, sending instance matching information to the matched resource agent end, so that the resource agent end selects a target instance from service instances which are managed by the resource agent end and deployed in the cluster to which the edge node belongs according to the instance matching information, and feeds back the end identification information of the resource agent end when the selection is successful.

S404, sending a service request to the resource agent corresponding to the end identification information, so that the corresponding resource agent sends the service request to the target instance for processing.

For example, a service request may be sent to the matched resource proxy, and then the resource proxy extracts the instance matching information in the service request; or directly sending the instance matching information in the service request to the matched resource agent end.

In an alternative embodiment, the instance matching information may include a service identification; correspondingly, the resource agent end can select a target instance for processing the service request from service instances which are supervised by the resource agent end and are deployed in the cluster to which the edge node belongs according to the historical processing condition of the service corresponding to the service identifier.

For example, if the service identifier belongs to an incomplete history service, such as an interrupt service, a pause service, or a cancel service, it indicates that a service instance has been previously allocated to the history service, so that a service instance adopted for executing the corresponding history service may be selected from service instances that are self-supervised and deployed in a cluster to which the edge node belongs, and be used as a target instance.

In another alternative embodiment, the instance matching information may include an instance tag; correspondingly, the resource agent end can select a service instance with the instance label matched from all service instances which are managed by the resource agent end and deployed in the cluster to which the edge node belongs as a target instance.

In yet another alternative embodiment, the instance matching information may include a service identification; correspondingly, the resource agent can detect at least one available candidate instance from each service instance which is self-supervised and deployed in the cluster to which the edge node belongs; and selecting the candidate instance matched with the service identification as a target instance.

According to the embodiment of the disclosure, the resource agent end is deployed in the edge node, the resource agent end is matched and selected through the resource central control end, and the target instance is selected and used through the resource agent end, so that the service corresponding to the processing service request is realized, the cloud end sinks towards the edge node close to the user side, the cloud end and the network domain of the edge node of the user side are isolated, the service pressure of the cloud end is reduced, the service cost of the cloud end is reduced, and the service experience is optimized.

Based on the above technical solutions, the present disclosure further provides a preferred embodiment, in which a service processing method of a sinking service is described in detail with reference to a cloud data platform service sinking total architecture diagram of fig. 5.

Referring to the architecture diagram shown in fig. 5, the architecture diagram includes a resource reference representation layer, a resource pool management layer, a service cluster management layer, a business service SDK, a resource client, and a remote service instance.

The resource reference representation layer, the resource pool management layer and the service cluster management layer are deployed at the resource central control end; the service SDK is deployed at the service central control end; both the resource client and the remote service instance are deployed in a resource node.

The service SDK is used for capturing service requests in the cloud data platform, determining remote service examples for processing the service requests which can be processed in a sinking mode through service discovery, and forwarding the service requests to the remote service examples.

The resource client is used as an intermediate hub between the business service SDK and the remote service instance, receives the business request distributed by the business service SDK, packages the business request for the second time, and forwards the business request to the remote service instance for processing the corresponding business request for processing. Meanwhile, the resource client can also collect real-time information (namely business data generated by processing business requests) of distributed computing power (namely remote service instance), and realize data reflow through uploading the real-time information. And establishing a safe cross-domain control flow in the service request issuing process of the resource client, and establishing a safe cross-domain data flow in the service data returning process of the resource client, so that the safe communication between the resource central control end and the user side resource is realized.

Illustratively, the resource client manages the remote service instance supervised by itself by introducing an instance lifecycle and an instance state machine. The specific supervision mechanism of the remote service instance can be referred to the relevant description of the foregoing embodiments, and will not be repeated here.

It should be noted that, the hidden trouble caused by overload of the thread pool or the data cache is avoided by the way of isolating and disposing the user side resources. Meanwhile, keep-alive, upgrading and the like of the remote service instance are realized through an elastic deployment mode.

In the service discovery process, the resource central control terminal is required to perform resource management, and assist in resource discovery according to the resource management result.

In an exemplary service cluster management layer of the resource central control end, the management of the resource client end supervised by the resource central control end is realized by introducing a resource life cycle and a resource state machine. The specific supervision mechanism of the resource client can be referred to the relevant description of the foregoing embodiments, and will not be repeated here.

In an exemplary embodiment, in a resource pool management layer of the resource central control end, data storage conditions corresponding to different resource entities such as stand-alone resources, cluster resources or container resources are recorded, so as to implement entity management. The stored data may include resource node records, resource tag records, component service records, etc., and by managing the resource nodes of each resource entity, and tags and components in the resource nodes, etc., resource discovery is performed in real time or at regular time, and creation or deletion of resource clients, etc., is controlled according to the discovered resources.

Optionally, in the resource pool management, a uniform resource nano-tube and a query interface can be further provided for realizing classified nano-tube and query service for remote resources. Meanwhile, by introducing a label system, service registration and component monitoring capability are provided, and convenience is provided for resource information inquiry and screening.

The resource reference representation layer of the resource central control end records namespaces corresponding to different accounts, references resource labels and use permission conditions of available resources under the namespaces, and records port information of resource clients for managing the resources under the available resources, so that positioning of the resource clients is realized through the port information, and the resource client is used as a positioning basis for a remote service instance for processing service requests received by a service SDK. Meanwhile, by matching the namespaces with the use of resource labels and the like, a foundation is laid for the quotation and expansion of different types of resources, and management such as packaging quota, calculation synchronization, dynamic expansion and contraction in cloud platform service can be conveniently realized.

In an alternative embodiment, in the process of performing resource entity and reference nanotube, the resource central control end carries the following intelligence:

1) Resource nano-tube: the cloud platform calculates the interactive management such as the registration (adding references to the existing entities and the like), creation (providing entities in a resource pool or adding entities and the like), deletion, release, update, state information presentation and the like of the resources.

2) And (3) resource authentication: data platform resource user, project participant identity verification, etc., and provides secure resource user identity verification and authentication conversion of remote resources.

3) And (3) resource screening: providing resource quota, load, feature tag decisions, supporting data platform applications, and the like.

4) Querying a resource component: resource cluster node third party self-checking, container, service version, service status, routing information, etc.

5) Remote service management: remote service control, service discovery, and the like. Wherein the remote service control may include configuration loading, API (Application Programming Interface ) registration, probe activity, etc.; service discovery may include routing, request distribution, and the like.

For example, in the process of resource synchronization, a cloud environment present backbone resource SDK or API and the like can be called to acquire various resource lists under a user, and the resource lists are synchronized with the lists in a resource library; detecting resource clusters one by one, synchronizing the state of a queue, quota, consumption and the like, and updating storage information such as a resource library cluster queue, a label and the like; and processing the newly added resource node client side establishment flow, the invalid resource node client side reconstruction flow and the expansion and contraction flow of the existing resource nodes, and updating the node storage information so as to realize the synchronization of the resource nodes.

By introducing a naming space, binding an item tag list as a query basis of the resource list, a cluster queue, item tags and the like, wherein all resource lists (including state, type and other information), each resource quota, usage details and the like in the naming space are processed; introducing node information of a resource queue to realize resource node inquiry; and introducing service instance information under the name space resource service label to realize service instance inquiry.

The method includes the steps of monitoring the states of components and remote service instances on a resource cluster or a resource node, and warehousing the service labels and the route information of the remote service instances to realize service management.

According to the technical scheme, cloud platform service sinking is achieved, the three-layer framework of resource central control end-resource node-remote service instance is adopted, total control service, service control service and calculation tasks are pushed down to user resources, service loads of different users are prevented, pressure of the resource central control end is reduced, and service cost of a cloud platform system is reduced.

As an implementation of the above-mentioned service processing methods, the present disclosure further provides an optional embodiment of an execution apparatus that implements the above-mentioned service processing methods.

Referring to fig. 6, a service processing apparatus 600, configured at a resource agent end deployed at an edge node, includes: an instance matching information acquisition module 601, a target instance selection module 602, an end identification information sending module 603 and a service request issuing module 604. Wherein,,

an instance matching information obtaining module 601, configured to obtain instance matching information in a service request when the instance matching information obtaining module matches a resource identifier in the service request;

the target instance selecting module 602 is configured to select a target instance from service instances that are self-supervised and deployed in a cluster to which the edge node belongs according to the instance matching information;

the terminal identification information sending module 603 is configured to send terminal identification information of itself to a service central control terminal if the selection is successful, so that the service central control terminal feeds back the service request according to the terminal identification information;

and a service request issuing module 604, configured to issue the service request to the target instance for processing.

In an alternative embodiment, the instance matching information includes a service identification; the target instance selection module 602 is specifically configured to:

and if the service identifier belongs to the incomplete history service, selecting a service instance adopted for executing the corresponding history service from service instances which are supervised by the service identifier and are deployed in a cluster to which the edge node belongs as the target instance.

In an alternative embodiment, the instance matching information includes an instance tag; the target instance selection module 602 is specifically configured to:

and selecting the service instance matched with the instance label from the service instances which are supervised by the self and are deployed in the cluster to which the edge node belongs as the target instance.

detecting at least one available candidate instance from each service instance which is self-supervised and is deployed in a cluster to which an edge node belongs;

and selecting a candidate instance matched with the service identification as the target instance.

In an alternative embodiment, the resource agent is marked in the available resources that match the resource identity under the namespace of the originator of the service request.

In an alternative embodiment, the service request issuing module 604 includes:

an open mode determining unit, configured to determine an open mode of the target instance with respect to the resource agent end; wherein the open mode is a single-ended open mode or a cluster open mode;

and the service request issuing unit is used for issuing the service request to the target instance by adopting a safe transmission mode matched with the open mode.

In an alternative embodiment, the apparatus 600 further comprises:

the service current state determining module is used for determining the service current state of the supervised service instance;

the service instance processing module is used for processing the corresponding service instance according to the current state of the service;

and the service current state adjusting module is used for adjusting the service current state of the corresponding service instance according to the processing condition.

In an optional embodiment, the service current state is a service initial state, a service setup state, a service stop state, a service running state, a service to-be-upgraded state, a service disconnection state, a service offline state, a service abnormal state, or a service release state;

the service initial state is used for representing that in a service synchronization stage, a newly added service instance is ready to be completed and needs to be initialized;

The service provisioning state is used for representing a service provisioning stage, and a service instance to be built is successfully initialized and needs to be started; or, representing that the service instance to be upgraded is successfully rebuilt in the service upgrading stage and needs to be restarted;

the service stopping state is used for representing that in a service establishment stage, a service instance to be established fails to be started and needs to be restarted; or in the service upgrading stage, the service of the service instance to be upgraded is terminated successfully, and reloading treatment is needed;

the service running state is used for representing that the detected service instance normally runs in the service detection and activation stage without intervention; or in the service upgrading stage, the service instance to be upgraded needs to be upgraded and updated; or in the service synchronization stage, service downloading state setting is required to be carried out on the service instance to be deleted;

the service to-be-upgraded state is used for representing that the service instance to be upgraded is successfully upgraded and is required to be subjected to service termination treatment in the service upgrading stage;

the service disconnection state is used for representing abnormal service examples in a service detection and activation stage, and when the service disconnection times exceed a first time number threshold value, service downlink state setting is carried out on the corresponding service examples;

The service down-line state is used for representing the service instance to be subjected to the destruction treatment, and setting the service release state of the corresponding service instance after the destruction is successful;

the service abnormal state is used for representing failure of service instance construction to be constructed in a service construction stage or failure of service instance upgrading to be upgraded in a service upgrading stage, and abnormal intervention processing is required to be carried out on the corresponding service instance;

the service release state is used for representing that the service instance to be destroyed is destroyed successfully.

The service processing device can execute the service processing method provided by any embodiment of the disclosure, and has the corresponding functional modules and beneficial effects of executing the service processing method.

As an implementation of the above-mentioned service processing methods, the present disclosure further provides another alternative embodiment of an execution apparatus for implementing the above-mentioned service processing methods.

Referring to fig. 7, a service processing apparatus 700, configured at a resource central control end, includes: a resource agent end determination module 701 and an end identification information sending module 702. Wherein,,

a resource agent end determining module 701, configured to obtain a resource identifier in a service request, and determine a resource agent end deployed at an edge node and matched with the resource identifier;

The terminal identification information sending module 702 is configured to send terminal identification information of the resource proxy to a service central control terminal, so that the service central control terminal sends instance matching information in a service request to a corresponding resource proxy terminal, and selects a target instance which is supervised by the corresponding resource proxy terminal and deployed in a cluster to which an edge node belongs;

the target instance is used for processing the service request.

In an alternative embodiment, the resource agent end determining module 701 includes:

an available resource determining unit, configured to determine, under a namespace of an initiator of the service request, an available resource that matches the resource identifier;

And the resource agent end determining unit is used for determining the resource agent end marked by the available resources and deployed at the edge node.

In an alternative embodiment, the apparatus 700 further comprises:

the proxy current state determining module is used for determining the proxy current state of the supervised resource proxy end;

the resource agent end processing module is used for processing the corresponding resource agent end according to the current state of the agent;

and the proxy current state adjusting module is used for adjusting the proxy current state of the corresponding resource proxy end according to the processing condition.

In an optional embodiment, the current state of the agent is an agent initial state, an agent setup state, an agent stop state, an agent running state, an agent to-be-upgraded state, an agent disconnection state, an agent offline state, an agent abnormal state, or an agent release state;

the agent initial state is used for representing that in an agent synchronization stage, a resource agent end to be newly added is ready to be completed and needs to be initialized;

the agent configuration state is used for representing an agent configuration stage, and the resource agent end to be configured is successfully initialized and needs to be started; or, representing that the resource agent end to be upgraded is successfully rebuilt in the agent upgrading stage and needs to be restarted;

The agent stop state is used for representing that in the agent establishment stage, the resource agent end to be established fails to start and needs to be restarted; or in the agent upgrading stage, the agent is successfully terminated at the resource agent end to be upgraded, and reloading treatment is needed;

the agent running state is used for representing that the detected resource agent end normally runs in the agent probing stage without intervention; or in the agent upgrading stage, the resource agent end to be upgraded needs to be upgraded and updated; or in the proxy synchronization stage, proxy downlink state setting is required to be carried out on the resource proxy end to be deleted;

the agent to-be-upgraded state is used for representing that the resource agent end to be upgraded is successfully upgraded and is required to be subjected to termination agent processing in an agent upgrading stage;

the proxy disconnection state is used for representing the abnormal service instance detected in the proxy detection and activation stage, and proxy downlink state setting is carried out on the corresponding resource proxy terminal when the proxy disconnection times exceed a second time threshold;

the proxy downlink state is used for representing that the resource proxy end to be offline is required to be destroyed, and proxy release state setting is carried out on the corresponding resource proxy end after the destruction is successful;

The agent abnormal state is used for representing the failure of the resource agent end to be built in the agent building stage or the failure of the resource agent end to be upgraded in the agent upgrading stage, and abnormal intervention processing is required to be carried out on the corresponding resource agent end;

the agent release state is used for representing successful end destruction of the resource agent to be destroyed.

As an implementation of the above-mentioned service processing methods, the present disclosure further provides an alternative embodiment of an execution apparatus for implementing the above-mentioned service processing methods.

Referring to fig. 8, a service processing apparatus 800, configured at a service central control end, includes: a service request acquisition module 801, a resource identification transmission module 802, an instance matching information transmission module 803 and a service request transmission module 804. Wherein,,

a service request acquisition module 801, configured to acquire a service request including instance matching information and a resource identifier;

a resource identifier sending module 802, configured to send the resource identifier to a resource central control end, so that the resource central control end determines and feeds back a resource proxy end that is matched with the resource identifier;

An instance matching information sending module 803, configured to send the instance matching information to the matched resource agent, so that the resource agent selects a target instance from service instances that are self-supervised and deployed in a cluster to which the edge node belongs according to the instance matching information, and feeds back self-end identification information when the selection is successful;

and a service request sending module 804, configured to send the service request to a resource proxy corresponding to the terminal identification information, so that the corresponding resource proxy sends the service request to the target instance for processing.

In the technical scheme of the disclosure, the related processes of collection, storage, use, processing, transmission, provision, disclosure and the like of service requests, resource identifiers, instance matching information, resource agent ends, service instances and the like all conform to the regulations of related laws and regulations and do not violate the popular regulations of the public order.

According to embodiments of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium and a computer program product.

Fig. 9 shows a schematic block diagram of an example electronic device 900 that may be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the disclosure described and/or claimed herein.

As shown in fig. 9, the apparatus 900 includes a computing unit 901 that can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM) 902 or a computer program loaded from a storage unit 908 into a Random Access Memory (RAM) 903. In the RAM 903, various programs and data required for the operation of the device 900 can also be stored. The computing unit 901, the ROM 902, and the RAM 903 are connected to each other by a bus 904. An input/output (I/O) interface 905 is also connected to the bus 904.

Various components in device 900 are connected to I/O interface 905, including: an input unit 906 such as a keyboard, a mouse, or the like; an output unit 907 such as various types of displays, speakers, and the like; a storage unit 908 such as a magnetic disk, an optical disk, or the like; and a communication unit 909 such as a network card, modem, wireless communication transceiver, or the like. The communication unit 909 allows the device 900 to exchange information/data with other devices through a computer network such as the internet and/or various telecommunications networks.

The computing unit 901 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of computing unit 901 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized 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 respective methods and processes described above, such as a business processing method. For example, in some embodiments, the business processing method may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as the storage unit 908. In some embodiments, part or all of the computer program may be loaded and/or installed onto the device 900 via the ROM 902 and/or the communication unit 909. When the computer program is loaded into the RAM 903 and executed by the computing unit 901, one or more steps of the above-described service processing method may be performed. Alternatively, in other embodiments, the computing unit 901 may be configured to perform the business processing method by any other suitable means (e.g., by means of firmware).

Various implementations of the systems and techniques described here above can be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), complex Programmable Logic Devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.

Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These 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 the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

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

The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the internet.

The computer system may include a client and a server. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service are overcome. The server may also be a server of a distributed system or a server that incorporates a blockchain.

Artificial intelligence is the discipline of studying the process of making a computer mimic certain mental processes and intelligent behaviors (e.g., learning, reasoning, thinking, planning, etc.) of a person, both hardware-level and software-level techniques. Artificial intelligence hardware technologies generally include technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing, and the like; the artificial intelligent software technology mainly comprises a computer vision technology, a voice recognition technology, a natural language processing technology, a machine learning/deep learning technology, a big data processing technology, a knowledge graph technology and the like.

Cloud computing (cloud computing) refers to a technical system that a shared physical or virtual resource pool which is elastically extensible is accessed through a network, resources can comprise servers, operating systems, networks, software, applications, storage devices and the like, and resources can be deployed and managed in an on-demand and self-service mode. Through cloud computing technology, high-efficiency and powerful data processing capability can be provided for technical application such as artificial intelligence and blockchain, and model training.

It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps recited in the present disclosure may be performed in parallel, sequentially, or in a different order, provided that the desired results of the technical solutions provided by the present disclosure are achieved, and are not limited herein.

The above detailed description should not be taken as limiting the scope of the present disclosure. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present disclosure are intended to be included within the scope of the present disclosure.

Claims

1. A service processing method is applied to a resource agent end deployed at an edge node, and comprises the following steps:

if the selection is successful, the terminal identification information of the terminal is sent to a service central control terminal, so that the service central control terminal feeds back the service request according to the terminal identification information;

and issuing the service request to the target instance for processing.

2. The method of claim 1, wherein the instance matching information comprises a service identification; according to the instance matching information, selecting a target instance from service instances which are self-supervised and deployed in a cluster to which an edge node belongs, wherein the method comprises the following steps:

3. The method of claim 1, wherein the instance matching information comprises an instance tag; according to the instance matching information, selecting a target instance from service instances which are self-supervised and deployed in a cluster to which an edge node belongs, wherein the method comprises the following steps:

4. The method of claim 1, wherein the instance matching information comprises a service identification; according to the instance matching information, selecting a target instance from service instances which are self-supervised and deployed in a cluster to which an edge node belongs, wherein the method comprises the following steps:

5. The method according to any of claims 1-4, wherein the resource broker is marked in available resources matching the resource identity under a namespace of an originator of the service request.

6. The method of any of claims 1-5, wherein the issuing the service request to the target instance comprises:

determining an open mode of the target instance relative to the resource agent end; wherein the open mode is a single-ended open mode or a cluster open mode;

and transmitting the service request to the target instance by adopting a safe transmission mode matched with the open mode.

7. The method of any of claims 1-6, wherein the method further comprises:

determining a service current state of the supervised service instance;

processing the corresponding service instance according to the current state of the service;

and adjusting the current service state of the corresponding service instance according to the processing condition.

8. The method of claim 7, wherein the service current state is a service initial state, a service setup state, a service stop state, a service run state, a service to-be-upgraded state, a service disconnection state, a service down state, a service exception state, or a service release state;

9. A business processing method is applied to a resource central control terminal and comprises the following steps:

the terminal identification information of the resource agent terminal is sent to the service central control terminal, so that the service central control terminal sends the instance matching information in the service request to the corresponding resource agent terminal, and the selection of the target instance which is supervised by the corresponding resource agent terminal and deployed in the cluster to which the edge node belongs is carried out;

The target instance is used for processing the service request.

10. The method of claim 9, wherein the determining a resource agent deployed at an edge node that matches the resource identification comprises:

under the name space of the initiator of the service request, determining available resources matched with the resource identification;

and determining a resource agent end marked by the available resources and deployed at the edge node.

11. The method according to claim 9 or 10, wherein the method further comprises:

determining the current state of the agent of the supervised resource agent end;

processing the corresponding resource agent end according to the current state of the agent;

and adjusting the current state of the proxy of the corresponding resource proxy end according to the processing condition.

12. The method of claim 11, wherein the agent current state is an agent initial state, an agent setup state, an agent stopped state, an agent running state, an agent to-be-upgraded state, an agent out-of-connection state, an agent offline state, an agent abnormal state, or an agent released state;

13. A service processing method is applied to a service center control terminal and comprises the following steps:

the resource identification is sent to a resource central control end, so that the resource central control end determines and feeds back a resource agent end matched with the resource identification;

the instance matching information is sent to the matched resource agent end, so that the resource agent end selects a target instance from service instances which are supervised by the resource agent end and deployed in the cluster to which the edge node belongs according to the instance matching information, and feeds back the end identification information of the resource agent end when the selection is successful;

14. A service processing apparatus configured at a resource proxy deployed at an edge node, comprising:

the instance matching information acquisition module is used for acquiring instance matching information in the service request under the condition that the instance matching information is matched with the resource identification in the service request;

the target instance selecting module is used for selecting a target instance from service instances which are supervised by the target instance selecting module and are deployed in a cluster to which the edge node belongs according to the instance matching information;

the terminal identification information sending module is used for sending terminal identification information of the terminal to the service central control terminal if the selection is successful, so that the service central control terminal feeds back the service request according to the terminal identification information;

and the service request issuing module is used for issuing the service request to the target instance for processing.

15. The apparatus of claim 14, wherein the instance matching information comprises a service identification; the target instance selection module is specifically configured to:

16. The apparatus of claim 14, wherein the instance matching information comprises an instance tag; the target instance selection module is specifically configured to:

17. The apparatus of claim 14, wherein the instance matching information comprises a service identification; the target instance selection module is specifically configured to:

18. The apparatus according to any of claims 14-17, wherein the resource broker is marked in an available resource that matches the resource identity under a namespace of an originator of the service request.

19. The apparatus of any of claims 14-18, wherein the service request issuing module comprises:

20. The apparatus of any of claims 14-19, wherein the apparatus further comprises:

21. The apparatus of claim 20, wherein the service current state is a service initial state, a service setup state, a service stop state, a service run state, a service to-be-upgraded state, a service disconnection state, a service down state, a service exception state, or a service release state;

22. A service processing device, configured at a resource central control end, comprising:

the resource agent end determining module is used for acquiring the resource identification in the service request and determining the resource agent end which is matched with the resource identification and is deployed at the edge node;

the terminal identification information sending module is used for sending terminal identification information of the resource agent terminal to the service central control terminal so that the service central control terminal sends instance matching information in a service request to the corresponding resource agent terminal, and the selection of target instances which are supervised by the corresponding resource agent terminal and are deployed in clusters to which the edge nodes belong is carried out;

the target instance is used for processing the service request.

23. The apparatus of claim 22, wherein the resource agent end determination module comprises:

24. The apparatus of claim 22 or 23, wherein the apparatus further comprises:

25. The apparatus of claim 24, wherein the agent current state is an agent initial state, an agent setup state, an agent stopped state, an agent running state, an agent to-be-upgraded state, an agent out-of-connection state, an agent offline state, an agent abnormal state, or an agent released state;

26. A service processing device, configured at a service central control end, comprising:

the service request acquisition module is used for acquiring a service request comprising instance matching information and a resource identifier;

the resource identification sending module is used for sending the resource identification to the resource central control terminal so that the resource central control terminal determines and feeds back a resource agent terminal matched with the resource identification;

the instance matching information sending module is used for sending the instance matching information to the matched resource agent end so that the resource agent end can select a target instance from service instances which are supervised by the resource agent end and deployed in the cluster to which the edge node belongs according to the instance matching information, and feeds back the end identification information of the resource agent end when the selection is successful;

and the service request sending module is used for sending the service request to the resource agent end corresponding to the end identification information so that the corresponding resource agent end can send the service request to the target instance for processing.

27. An electronic device, comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the traffic processing method of any one of claims 1-13.

28. A non-transitory computer readable storage medium storing computer instructions for causing a computer to perform the business processing method of any one of claims 1-13.

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