Cloud service network detection method and device, equipment and medium

Abstract

The invention provides a cloud service network detection method and device, equipment and a medium, and relates to the technical field of cloud computing services, the method comprises the steps that a service object set in a to-be-detected cloud service scene is acquired, and the service object set is composed of a kernel mode object, a user mode object and a link object; obtaining a non-interference program of each service object in the service object set, and performing data capture point configuration on each service object through the non-interference program to capture a network state data set of each service object; obtaining a candidate topological graph of the cloud service scene, and labeling the candidate topological graph based on the network state data set to obtain a labeled target topological graph; and carrying out network state detection on the cloud service scene according to the target topological graph.

Description

Technical Field

[0001] The present disclosure relates to the field of cloud services, and in particular to a cloud service network detection method, device, equipment and medium. Background Art

[0002] With the development of technology, load balancing has realized on-demand distribution of multi-tenant network traffic in cloud computing virtualization network scenarios. In load balancing scenarios, the network status of each node, such as the client, load forwarding node, and server, as well as the links between nodes, has a certain degree of impact on the service efficiency and stability of cloud computing services. Summary of the invention

[0003] The present disclosure proposes a cloud service network detection method, device, equipment and medium.

[0004] According to the first aspect of the present disclosure, a cloud service network detection method is proposed, comprising: obtaining a service object set in a cloud service scenario to be detected, wherein the service object set is composed of kernel state objects, user state objects and link objects; obtaining a non-interference program for each service object in the service object set, and configuring a data capture point for each service object through the non-interference program to capture a network status data set of each service object; obtaining a candidate topology map of the cloud service scenario, and annotating the candidate topology map based on the network status data set to obtain a labeled target topology map; and performing network status detection on the cloud service scenario according to the target topology map.

[0005] According to a second aspect of the present disclosure, a cloud service network detection device is proposed, comprising: an acquisition module, used to acquire a service object set in a cloud service scenario to be detected, wherein the service object set is composed of kernel-state objects and user-state objects; a capture module, used to acquire a non-interference program for each service object in the service object set, and configure a data capture point for each service object through the non-interference program to capture a network status data set of each service object; a labeling module, used to acquire a candidate topology map of the cloud service scenario, and label the candidate topology map based on the network status data set to obtain a labeled target topology map; and a detection module, used to perform network status detection on the cloud service scenario according to the target topology map.

[0006] According to a third aspect of the present disclosure, an electronic device is proposed, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the cloud service network detection method proposed in the first aspect above.

[0007] According to a fourth aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer instructions is proposed, wherein the computer instructions are used to enable the computer to execute the cloud service network detection method proposed in the first aspect above.

[0008] According to a fifth aspect of the present disclosure, a computer program product is proposed, including a computer program, wherein when the computer program is executed by a processor, the cloud service network detection method proposed in the first aspect is implemented.

[0009] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The accompanying drawings are used to better understand the present solution and do not constitute a limitation of the present disclosure.

[0011] Figure 1 A schematic diagram of a cloud service network detection method according to an embodiment of the present disclosure;

[0012] Figure 2 A schematic diagram of a flow chart of a cloud service network detection method according to another embodiment of the present disclosure;

[0013] Figure 3 A schematic diagram of a load balancing scenario according to an embodiment of the present disclosure;

[0014] Figure 4 A schematic diagram of a flow chart of a cloud service network detection method according to another embodiment of the present disclosure;

[0015] Figure 5 A schematic diagram of a flow chart of a cloud service network detection method according to another embodiment of the present disclosure;

[0016] Figure 6 A schematic diagram of a flow chart of a cloud service network detection method according to another embodiment of the present disclosure;

[0017] Figure 7 A schematic diagram of a flow chart of a cloud service network detection method according to another embodiment of the present disclosure;

[0018] Figure 8 This is a schematic diagram of the structure of a cloud service network detection device according to an embodiment of the present disclosure;

[0019] Fig. 9 A schematic block diagram of an electronic device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0020] The following is a description of exemplary embodiments of the present disclosure in conjunction with the accompanying drawings, including various details of the embodiments of the present disclosure to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present disclosure. Similarly, for the sake of clarity and conciseness, descriptions of well-known functions and structures are omitted in the following description.

[0021] Data processing is a basic part of system engineering and automatic control. Data is a form of expression of facts, concepts or instructions, which can be processed by manual or automatic devices. After data is interpreted and given a certain meaning, it becomes information. Data processing is the collection, storage, retrieval, processing, transformation and transmission of data. The basic purpose of data processing is to extract and derive valuable and meaningful data for certain specific people from a large amount of data that may be disorganized and difficult to understand.

[0022] Cloud services are the addition, use and interaction of Internet-based services, usually involving the provision of dynamic, scalable and often virtualized resources through the Internet. Cloud is a metaphor for the network and the Internet. Cloud services refer to the on-demand and scalable access to required services through the network. Such services can be IT and software, Internet-related, or other services.

[0023] Figure 1 FIG. 1 is a flow chart of a cloud service network detection method according to an embodiment of the present disclosure. Figure 1 As shown, the method includes:

[0024] S101, obtaining a service object set in a cloud service scenario to be detected, wherein the service object set is composed of kernel state objects, user state objects and link objects.

[0025] In the disclosed embodiments, a variety of services may be provided to the user end through cloud computing services, wherein scenarios requiring network status and network quality detection may be marked as cloud service scenarios to be detected.

[0026] Among them, cloud service scenarios may include load balancing scenarios, and may also include other service scenarios that can be provided by cloud computing, which are not specifically limited here.

[0027] Optionally, the cloud service scenario includes multiple objects, among which the objects corresponding to the kernel state can be marked as kernel state objects in the cloud service scenario, and the objects corresponding to the user state can be marked as user state objects in the cloud service scenario, and the network links between nodes can be determined as link objects, thereby obtaining an object set consisting of kernel state objects, user state objects and link objects, and the object set is determined as the service object set in the cloud service scenario.

[0028] As an example, taking the load balancing scenario included in the cloud service scenario as an example, the load balancing scenario includes a client, a load forwarding node and a back-end server, wherein, for the objects corresponding to the kernel state included in the client, the part of objects can be determined as the kernel state objects in the load balancing scenario, and for the objects corresponding to the user state included in the client, the part of objects can be determined as the user state objects in the load balancing scenario, and for the network link between the client and the load forwarding node, the part of the link can be determined as the link object in the load balancing scenario.

[0029] It should be noted that the service object set in the cloud service scenario may include kernel state objects, user state objects, and network link objects between network nodes. In this scenario, through the service object set in the cloud service scenario, the network status data of the kernel state objects in the cloud service scenario can be captured and detected, the network status data of the user state objects in the cloud service scenario can be captured and detected, and the network status data transmitted on each link object in the cloud service scenario can be captured and detected, thereby realizing full-scenario network status detection in the cloud service scenario.

[0030] S102, obtaining a non-interference program for each service object in the service object set, and configuring a data capture point for each service object through the non-interference program to capture a network status data set of each service object.

[0031] In the embodiment of the present disclosure, each service object in the service object set can provide the cloud computing services required by the user terminal through the network. In this scenario, the relevant status data of the network of each service object can be obtained, and the set composed of the obtained data can be determined as the network status data set of each service object.

[0032] For any service object, its network status data set may include network status description data of the service object, such as packet loss rate, delay rate, jitter, throughput, error rate, and retransmission rate.

[0033] Optionally, a data capture program that is used to capture data and does not affect the operation of the service object can be obtained as a non-interference program corresponding to the service object, and the non-interference program can be configured on the service object based on the program configuration method in the relevant technology to capture multiple network status data on the service object, thereby obtaining a network status data set of the service object.

[0034] Among them, the non-interference program can be constructed based on the extended Berkeley Packet Filter (eBPF) in the relevant technology, or it can be constructed based on other types of data capture programs that will not affect the operation of the service object, and no specific limitation is made here.

[0035] S103, obtaining a candidate topology map of the cloud service scenario, and annotating the candidate topology map based on the network status data set to obtain a labeled target topology map.

[0036] In the embodiment of the present disclosure, the service object set includes each network node in the cloud service scenario, and the links between each network node. In this scenario, a topology map can be drawn based on each service object using a topology map drawing method in related technologies, and the drawn topology map can be determined as a candidate topology map for the cloud service scenario.

[0037] In this scenario, the network status data set of each service object can be annotated in the candidate topology map, wherein the network status data set of each service object can be placed in the candidate topology map based on the topology map annotation method in the relevant technology to achieve the annotation of the network status data set to the candidate topology map, and the annotated topology map is determined as the target topology map of the cloud service scenario.

[0038] S104: Perform network status detection on the cloud service scenario according to the target topology map.

[0039] In the embodiment of the present disclosure, the network status data of each service object in the service object set included in the cloud service scenario can be obtained according to the target topology map. In this scenario, the network status of each service object in the cloud service scenario can be detected through the target topology map.

[0040] Optionally, the target topology map may be visualized based on a preset visualization strategy, and network status data in the target topology map may be obtained through a display area provided by the visualization, and the network status data in the display area may be compared with preset reference network status data.

[0041] Among them, for any service object, when there is a mismatch between each network status data in the network status data set corresponding to the service object and the reference network status data corresponding to each network status data, the mismatched data is obtained from each network status data, and network anomaly processing is performed on the corresponding service object in the cloud service scenario based on the data.

[0042] The cloud service network detection method proposed in the present invention obtains a service object set in a cloud service scenario and a non-interference program for each service object, and captures a network status data set of each service object through the non-interference program, and annotates a candidate topology map of the cloud service scenario based on the network status data set of each service object to obtain a labeled target topology map, and performs network status detection on the cloud service scenario through the target topology map. In the present disclosure, the network status data set of each service object is captured by a non-interference program, which reduces the impact of the acquisition of the network status data set on the operation of the service object, improves the stability of the service object operation when the network status data set is captured, and compared with the acquisition of network status data by packet capture in the related art, the probability of abnormal data acquisition caused by packet capture positioning failure is avoided, the real-time and accuracy of the acquisition of the network status data set is improved, and the resource consumption of the acquisition of the network status data set is reduced. The target topology map of the cloud service scenario is obtained based on the network status data set and the candidate topology map, and the network status of the cloud service scenario is detected by the target topology map. Compared with the manual data integration in the related art, the dependence of the network status detection on manual labor is reduced, the detection efficiency and detection accuracy of the network status detection of the cloud service scenario are improved, thereby improving the stability of the network operation of the cloud service scenario and the stability of the cloud computing service provided by the cloud service scenario, and optimizing the user's service experience.

[0043] In the above embodiment, the acquisition of the target topology map can be combined with Figure 2 Further understanding, Figure 2 FIG. 1 is a flow chart of a cloud service network detection method in another embodiment of the present disclosure. Figure 2 As shown, the method includes:

[0044] S201, obtaining a service object set in a cloud service scenario to be detected, wherein the service object set is composed of kernel state objects, user state objects and link objects.

[0045] Optionally, a service request initiation object set, a load forwarding object set, a service provision object set and a link object set in the cloud service scenario are obtained, and based on the service request initiation object set and the service provision object set, a kernel state object set in the cloud service scenario is obtained; and, based on the service request initiation object set, the service provision object set and the load forwarding object set, a user state object set in the cloud service scenario is obtained.

[0046] As an example, Figure 3 As shown, the cloud service scenario is set as Figure 3 The load balancing scenario shown is Figure 3 Taking the load balancing scenario corresponding to tenant 1 shown as an example, client 1, client 2,..., client K are service request initiating objects in the load balancing scenario corresponding to tenant 1, server 1, server 2,..., server N are service providing objects in the load balancing scenario corresponding to tenant 1, and each load balancing forwarding node included in the load balancing instance 1 (not shown in the figure) is the load forwarding object in the load balancing scenario corresponding to tenant 1.

[0047] In this example, the set consisting of client 1, client 2, ..., client K is Figure 3 The service request initiation object set in the load balancing scenario corresponding to tenant 1 shown in the figure is composed of server 1, server 2, ..., server N. Figure 3 The service provision object set in the load balancing scenario corresponding to tenant 1 shown, and the set consisting of the load balancing forwarding nodes (not shown in the figure) included in load balancing instance 1 are the load forwarding object set in the load balancing scenario corresponding to tenant 1.

[0048] like Figure 3 As shown, Figure 3 The cloud service scenario shown also includes load balancing scenarios corresponding to other tenants, where: Figure 3 The service request initiation object set, load forwarding object set and service provision object set in the load balancing scenario corresponding to tenant L shown can be understood in conjunction with the relevant content of the load balancing scenario corresponding to tenant 1, and will not be repeated here.

[0049] In the embodiment of the present disclosure, there are some objects in the service request initiation object set and the service provision object set in the cloud service scenario that can implement the operation of functions based on the kernel state. In this scenario, some objects that implement the operation of functions based on the kernel state can be screened out from the service request initiation object set and the service provision object set, and these some objects can be determined as the kernel state objects in the cloud service scenario, and then the kernel state object set in the cloud service scenario can be formed based on each kernel state object.

[0050] Optionally, there are some objects in the service request initiation object set, service provision object set and load forwarding object set in the cloud service scenario that can implement functional operations based on user-state processes. In this scenario, corresponding screening can be performed on the service request initiation object set, service provision object set and load object forwarding set to filter out some objects that implement functional operations based on user-state processes, and determine these some objects as user-state objects in the cloud service scenario, and determine the set of user-state objects as the user-state object set in the cloud service scenario.

[0051] Optionally, there are network links between network nodes in the cloud service scenario. In this scenario, each network link included in the cloud service scenario can be obtained as a link object in the cloud service scenario, thereby obtaining a link object set composed of each link object.

[0052] As an example, Figure 3 As shown, in Figure 3 In the load balancing scenario shown, kernel objects can be filtered from each client and each server to obtain Figure 3 The kernel state object set in the load balancing scenario shown in the figure, and the user state objects are screened from the load forwarding nodes (not shown in the figure) included in each client, each server and each load balancing instance, so as to obtain Figure 3 The user state object set in the load balancing scenario shown in FIG. Figure 3 The network links between the clients, load balancing instances, and servers shown are determined as link objects, thereby obtaining Figure 3 The set of link objects in the load balancing scenario is shown.

[0053] Optionally, based on the kernel state object set and the user state object set, a service object set of the cloud service scenario is obtained.

[0054] In the disclosed embodiment, after obtaining the kernel state object set and the user state object set in the cloud service scenario, the set consisting of the kernel object set and the user state object set can be determined as the service object set in the cloud service scenario.

[0055] S202: Acquire a service sub-object set of each service object and a hook point of each service sub-object in the service sub-object set.

[0056] In the embodiment of the present disclosure, a service object includes a plurality of service sub-objects, and a set of the plurality of service sub-objects may be determined as a service sub-object set in the service object.

[0057] As an example, Figure 4 As shown, for Figure 4The service object host 1 shown can determine the physical components and virtual components constituting the host 1 as the service sub-objects included in the host 1, and determine the set of the physical components and virtual components as the service sub-object set in the host 1.

[0058] In the disclosed embodiment, for any service object, a corresponding data capture program can be configured on each service sub-object in the service sub-object set included in the service object, and then the network status data of each service sub-object can be obtained by running the data capture program, thereby obtaining the network status data set of the service object.

[0059] Optionally, for any service sub-object, the hook point of the service sub-object can be determined based on the hook point setting method in the relevant technology, and then the data crawler program can be configured based on the hook point on the service sub-object.

[0060] S203: Perform program configuration on the hook points of each service sub-object based on the non-interference program to obtain the configured data capture points of each service sub-object.

[0061] In the embodiment of the present disclosure, a data capture program that meets set conditions can be configured for each service sub-object, wherein the set conditions can be that the normal operation of the configured service sub-object is not affected while performing data capture. In this scenario, the data capture program that meets the condition can be determined as a non-interference program.

[0062] Among them, the non-interference program can be constructed based on the eBPF technology in the relevant technology, or it can be obtained based on other technologies that can realize non-interference data capture programs, which is not specifically limited here.

[0063] Optionally, for any service sub-object, a non-interference program adapted to the service sub-object may be obtained, and the non-interference program may be configured at a hook point of the service sub-object to implement program configuration of the data capture program of the service sub-object.

[0064] Furthermore, for any service sub-object, a hook point on the service sub-object configured with a non-interference program is determined as a data capture point on the service sub-object.

[0065] As an example, Figure 4 As shown, in Figure 4In the load balancing scenario shown, the hook points 1 to hook points N of the service sub-objects 1 to the service sub-objects N inside the host machine 1 can be obtained, and based on the preset ebpf program, the program configuration of the non-interference program can be performed on the hook points to the hook points N inside the host machine 1 respectively, so as to obtain the data capture points configured on the service sub-objects 1 to the service sub-objects N inside the host machine 1.

[0066] exist Figure 4 In the scenario shown, it is also possible to obtain hook points 1 to hook point N of service sub-objects 1 to service sub-object N inside the virtual machine corresponding to client 1, and perform non-interference program configuration on hook points to hook point N inside the virtual machine corresponding to client 1 based on the preset ebpf program, thereby obtaining the data capture points configured on service sub-objects 1 to service sub-object N inside the virtual machine corresponding to client 1.

[0067] exist Figure 4 In the scenario shown, network card driver 1 is Figure 4 The link objects in the scene are shown. In this example, the hook points on each service sub-object included in the network card driver 1 can be obtained, and the hook points on the network card driver 1 are configured based on the preset ebpf program as a non-interference program, so as to obtain the data capture points configured on each service sub-object corresponding to the network card driver 1.

[0068] like Figure 4 As shown, Figure 4 The scene is also provided with Figure 4 The forwarding node 1 and forwarding node 2 are shown, wherein the forwarding node 1 user obtains the network status data captured by the data capture points respectively configured on the service sub-object 1 to the service sub-object N inside the host machine 1, and the forwarding node 2 is used to obtain the network status data captured by the data capture points respectively configured on the service sub-object 1 to the service sub-object N inside the virtual machine corresponding to the client 1.

[0069] Further, through Figure 4 The data aggregation module shown is based on Figure 4 The network status data of each service sub-object included in the host machine 1, the client 1 and the network card driver 1 are shown to obtain the network status data set of each related service object.

[0070] like Figure 4 As shown, in Figure 4 The load balancing scenario shown also includes Figure 4 The load balancing forwarding node (Load Balancer Forwarding Node, LB forwarding node) shown in Figure 4As shown, the load balancing forwarding nodes include Figure 4 The network card driver 2 is shown as a link object, and the DPDK (Data Plane Development Kit) receiving queue, DPDK working core and DPDK sending queue are shown as user state objects.

[0071] In this example, the hook points on each service sub-object included in the DPDK receive queue, the DPDK working core and the DPDK send queue can be obtained respectively, and based on the preset ebpf program as a non-interference program, the hook points on each service sub-object included in the DPDK receive queue, the DPDK working core and the DPDK send queue can be configured with a non-interference program respectively, thereby obtaining the data capture points configured on each service sub-object included in the DPDK receive queue, the DPDK working core and the DPDK send queue.

[0072] Also, the hook points of each service sub-object included in the network card driver 2 are obtained, and the program of the non-interference program is configured for each hook point based on the preset ebpf program as a non-interference program, so as to obtain the configured data capture points on each service sub-object included in the network card driver 2.

[0073] It should be noted that Figure 4 The configuration of the data capture points on each service sub-object included in the other service objects shown can be understood in conjunction with the relevant content in the above examples, and will not be repeated here.

[0074] As another example, you can also combine Figure 5 ,like Figure 5 As shown, you can get Figure 5 The hook points on each service sub-object included in the DPDK receive queue, DPDK working core and DPDK send queue are shown, and based on the preset ebpf program, the hook points on each service sub-object included in the DPDK receive queue, DPDK working core and DPDK send queue are respectively configured with non-interference programs, thereby obtaining the data capture points configured on each service sub-object included in the DPDK receive queue, DPDK working core and DPDK send queue.

[0075] In this example, after configuring the data capture points of the DPDK receive queue, DPDK working core, and DPDK send queue, the network status data on each service sub-object included in the DPDK receive queue, DPDK working core, and DPDK send queue can be obtained based on each data capture point.

[0076] S204: Capture data of each service sub-object based on the data capture point to obtain network status data of each service sub-object.

[0077] In the disclosed embodiment, the network status data of each service sub-object can be captured by configuring a non-interference program on a data capture point on each service sub-object.

[0078] Optionally, for any data capture point, in response to identifying that a non-interference program configured on the data capture is triggered, the target state space of the service sub-object to which the data capture point belongs is obtained, and the network status data of the service sub-object is obtained from the target state space through the non-interference program, wherein the target state space is one of the kernel space and the user space.

[0079] In the embodiment of the present disclosure, for any service sub-object, the non-interference program configured on the service sub-object has its own corresponding triggering condition. In this scenario, when the triggering condition of the non-interference program is met, it can be determined that the non-interference program is triggered. In this scenario, the non-interference program can be started, and data capture is performed on the service sub-object configured by the non-interference program based on the startup of the non-interference program.

[0080] In the scenario where the service object to which the service sub-object belongs is a kernel state object, when the non-interference program configured on the service sub-object is triggered and started, the kernel space corresponding to the service sub-object can be determined as the target state space for capturing relevant data of the service sub-object.

[0081] In this scenario, the network status data corresponding to the service sub-object can be captured from the kernel space of the service sub-object as the target state space, thereby obtaining the network status data of the service sub-object.

[0082] As an example, for any service sub-object included in the service object corresponding to the kernel state, the kernel space of the service sub-object can be used as the target state space to capture the corresponding network state data from the kernel space through the running of the program without interference.

[0083] For any service sub-object included in the service object corresponding to the user state, when the non-interference program configured on the service sub-object is triggered and started, the user space corresponding to the service sub-object can be determined as the target state space from which the relevant data of the service sub-object can be captured. In this scenario, the network state data corresponding to the service sub-object can be captured from the user space of the service sub-object as the target state space, thereby obtaining the network state data of the service sub-object.

[0084] As an example, for Figure 4The service sub-objects corresponding to the kernel state in the virtual machine corresponding to the client 1 shown can be configured based on the non-interference program configured on each service sub-object. Figure 4 The kernel space 1 shown captures the network status data of each service sub-object in this example.

[0085] And, for Figure 4 The service sub-objects corresponding to the user state in the virtual machine corresponding to the client 1 shown can be configured based on the non-interference program from Figure 4 The network status data of each service sub-object in this example is captured in the user space 1 shown.

[0086] against Figure 4 In the load balancing forwarding node shown, the service sub-objects included in the DPDK receiving queue, DPDK working core and DPDK sending queue corresponding to the user state can be based on the method of capturing DPDK data through the ebpf program in the relevant technology, based on the ebpf program configured as a non-interference program on the data capture point of each service sub-object included in the DPDK receiving queue, DPDK working core and DPDK sending queue, directly capture the network status data of each service sub-object included in the DPDK receiving queue, DPDK working core and DPDK sending queue, thereby obtaining the network status data of each service sub-object included in the DPDK receiving queue, DPDK working core and DPDK sending queue.

[0087] S205: Obtain a network status data set of each service object based on the network status data of each service sub-object.

[0088] In the disclosed embodiment, for any service object, the network status data of each service sub-object included in the service object can be obtained, and a set of the network status data of each service sub-object can be determined as the network status data set of the service object.

[0089] As an example, in Figure 4 In the scenario shown, a forwarding node 1 is provided inside the host machine 1, and a forwarding node 2 is provided inside the virtual machine corresponding to the client 1. In this example, the network status data captured by each data capture point inside the host machine can be transmitted to the forwarding node 1 through the forwarding node 2. Figure 4 The data aggregation module 1 shown in the figure and the network status data captured by each data capture point inside the virtual machine can be transmitted to the forwarding node 2 through the forwarding node 2. Figure 4 The data aggregation module 1 shown further obtains the network status data set of each service object related to the host 1 and the client 1.

[0090] It should be noted that Figure 4Other forwarding nodes in the illustrated scenario can be understood in conjunction with the above example related content and will not be described in detail here.

[0091] As another example, Figure 6 As shown, each process in the user space and functions 1 to N included in each process can be connected with Figure 6 The transmission protocol module shown interacts with each other, wherein the transmission protocol module may include Figure 6 Hypertext Transfer Protocol / Secure Hypertext Transfer Protocol / Secure Sockets Layer Protocol / Transport Layer Security Protocol, etc., and through the transmission protocol module Figure 6 The interaction between the system call modules shown implements data interaction between the user space and the kernel space.

[0092] exist Figure 6 In the kernel space shown, data interaction between the kernel space and the network card driver is achieved through the system call module, the socket module and the transmission control protocol / international protocol module.

[0093] In this example, when the service sub-object is a user-mode object, it can be accessed from the Figure 6 The user space shown captures the corresponding network status data, and when the service sub-object is a kernel state object, the corresponding network status data can be captured from the kernel space based on the non-interference program, and when the service sub-object is a link object, the non-interference program can be used to capture the corresponding network status data from the kernel space. Figure 6 The network card driver shown captures the corresponding network status data, and then obtains the network status data set of each service object.

[0094] The cloud service network detection method proposed in the present invention configures the hook points of each service sub-object based on a non-interference program to obtain the data capture points of each service sub-object, so as to obtain the network status data of each service sub-object, and then obtains the network status data set of each service object based on the network status data of each service sub-object, thereby reducing the influence of the acquisition of the network status data set on the operation of the service object, improving the stability of the operation of the service object when the network status data set is captured, and compared with the acquisition of network status data by packet capture in the related art, the probability of abnormal data acquisition caused by packet capture positioning failure is avoided, the real-time and accuracy of the acquisition of the network status data set is improved, and the resource consumption of the acquisition of the network status data set is reduced.

[0095] In the above embodiment, the acquisition of the target topology map can be combined with Figure 7 Further understanding, Figure 7 FIG. 1 is a flow chart of a cloud service network detection method according to another embodiment of the present disclosure. Figure 7 As shown, the method includes:

[0096] S701, drawing a topology map based on a service object set to obtain a candidate topology map.

[0097] In the embodiments of the present disclosure, a topology map may be drawn based on a topology map drawing method in related technologies and a service object set in a cloud service scenario, and the drawn topology map may be determined as a candidate topology map of the cloud service scenario.

[0098] S702: Obtain the location identifier of each service sub-object in the service sub-object set of each service object.

[0099] In the disclosed embodiment, each service sub-object has its own identification information, wherein for any service sub-object, the node identification of the network data forwarding node of the service sub-object and the capture point identification of the data capture point configured by the service sub-object are obtained.

[0100] As an example, Figure 4 As shown, for Figure 4 Any service sub-object within the host 1 shown, Figure 4 The forwarding node 1 shown is the network data forwarding node of the service sub-object, and the identification information of the forwarding node 1 can be determined as the node identification of the service sub-object.

[0101] Furthermore, identification information of a hook point configured with a non-interference program on the service sub-object may be obtained as a grabbing point identification of a data grabbing point of the service sub-object.

[0102] Optionally, based on the node identifier and the grab point identifier, a location identifier of the service sub-object is obtained.

[0103] In the disclosed embodiment, after obtaining the node identifier and the grab point identifier of each service sub-object, for any service sub-object, the set consisting of the node identifier and the grab point identifier can be determined as the identification information of the service sub-object, wherein the specific location of the service sub-object in the cloud service scenario can be determined through the node identifier and the grab point identifier carried in the identification information, and the identification information can be determined as the positioning identifier of the service sub-object.

[0104] S703: For any service sub-object, obtain a first topology object corresponding to the service sub-object from the candidate topology map, and mark the location identifier and network status data of the service sub-object on the first topology object to obtain a marked second topology object.

[0105] In the disclosed embodiment, the network status data and location identifier of each service sub-object may be annotated in the candidate topology map, thereby obtaining a labeled topology map.

[0106] For any service sub-object, a corresponding portion of the service sub-object in the candidate topology map may be obtained, and the partial image may be determined as the first topology object corresponding to the service sub-object in the candidate topology map.

[0107] In this scenario, the node identifier carried in the positioning identifier of the service sub-object can be used as the horizontal coordinate, and the grab point representation carried in the positioning identifier can be used as the vertical coordinate, and then the horizontal coordinate and the vertical coordinate can be marked on the first topological object based on the information marking method in the relevant technology, and, based on the information marking method in the relevant technology, the network status data of the service sub-object can be marked on the first topological object corresponding to the service sub-object, and then the topological object after the positioning identifier and the network status data are marked is obtained, and it is determined as the second topological object corresponding to the service sub-object.

[0108] S704: Based on the second topology object of each service sub-object, the candidate topology map is annotated and updated to obtain a target topology map of the cloud service scenario.

[0109] In the disclosed embodiment, after obtaining the second topology object after marking each service sub-object, the first topology objects corresponding to each second topology object in the candidate topology map can be updated, and the updated topology map can be determined as the target topology map of the cloud service scenario.

[0110] Among them, based on the topology map update algorithm in the relevant technology, each first topology object in the candidate topology can be updated based on each second topology object. Among them, each first topology object can be overwritten and updated, or each first topology object can be deleted and then the second topology object can be filled in the blank position after deletion, thereby realizing the annotation update of the candidate topology map. No specific limitation is made here.

[0111] S705: Perform network status detection on the cloud service scenario according to the target topology map.

[0112] Optionally, the marked network status data on each third topology object in the target topology map is obtained.

[0113] In an embodiment of the present disclosure, each topological object in the target topological map can be marked as a third topological object. In this scenario, the network status data marked on each third topological object can be obtained from the target topological map based on the topological map data acquisition method in the related technology, as the marked network status data of each third topological object.

[0114] Optionally, in response to identifying that abnormal network data exists in the annotated network status data on each third topology object, an abnormal fourth topology object in the target topology map is obtained, and an abnormal location identifier is obtained from the object annotation information of the fourth topology object.

[0115] In the disclosed embodiment, for any third topology object, the annotated network status data on the third topology object may be obtained, and compared with the reference network status data corresponding to the third topology object to obtain a corresponding comparison result.

[0116] When the comparison result indicates that the annotated network status data does not match the reference network status data, it can be determined that the annotated network status data is abnormal, and the data can be marked as abnormal network data, and the third topology object corresponding to the abnormal network data can be determined as the fourth topology object with an abnormality.

[0117] Furthermore, the labeling information of the fourth topology object in the target topology map is obtained, and the information is determined as the object labeling information of the fourth topology object, and a positioning identifier is extracted therefrom and marked as an abnormal positioning identifier.

[0118] Optionally, based on the abnormal location identifier, the abnormal service sub-object is centrally located from the service object, and the abnormal service sub-object is fault processed based on the abnormal network data.

[0119] In the disclosed embodiment, based on the abnormal location identifier, the network data forwarding node and data capture point corresponding to the service sub-object corresponding to the fourth topology object can be determined, thereby realizing the location of the service sub-object of the fourth topology object in the cloud service scenario, and determining the located service sub-object as the abnormal service sub-object in the cloud service scenario.

[0120] Furthermore, based on the data item to which the abnormal network data belongs, a preset network abnormality processing strategy is obtained, and based on the strategy, fault processing is performed on the abnormal service sub-object.

[0121] The cloud service network detection method proposed in the present invention annotates candidate topology maps based on network status data sets and positioning identifiers to obtain a target topology map of a cloud service scenario, and performs network status detection of the cloud service scenario through the target topology map. Compared with the manual data integration in the related art, the degree of dependence of network status detection on manual work is reduced, the detection efficiency and detection accuracy of network status detection of the cloud service scenario are improved, thereby improving the stability of network operation of the cloud service scenario and the stability of cloud computing services provided by the cloud service scenario, and optimizing the user's service experience.

[0122] An embodiment of the present disclosure further proposes a cloud service network detection device. Since the cloud service network detection device proposed in the embodiment of the present disclosure corresponds to the cloud service network detection methods proposed in the above-mentioned embodiments, the implementation methods of the above-mentioned cloud service network detection methods are also applicable to the cloud service network detection device proposed in the embodiment of the present disclosure, and will not be described in detail in the following embodiments.

[0123] Figure 8 FIG. 1 is a schematic diagram of the structure of a cloud service network detection device according to an embodiment of the present disclosure. Figure 8 As shown, the cloud service network detection device 800 includes an acquisition module 81, a capture module 82, a labeling module 83 and a detection module 84, wherein:

[0124] An acquisition module 81 is used to acquire a service object set in a cloud service scenario to be detected, wherein the service object set is composed of kernel state objects, user state objects and link objects;

[0125] The capture module 82 is used to obtain the non-interference program of each service object in the service object set, and configure the data capture point for each service object through the non-interference program to capture the network status data set of each service object;

[0126] The annotation module 83 is used to obtain a candidate topology map of the cloud service scenario, and annotate the candidate topology map based on the network status data set to obtain an annotated target topology map;

[0127] The detection module 84 is used to perform network status detection on the cloud service scenario according to the target topology map.

[0128] In the disclosed embodiment, the capture module 82 is also used to: obtain a service sub-object set of each service object, and a hook point of each service sub-object in the service sub-object set; configure the hook point of each service sub-object based on a non-interference program to obtain a data capture point after the configuration of each service sub-object; capture data of each service sub-object based on the data capture point to obtain network status data of each service sub-object; and obtain a network status data set of each service object based on the network status data of each service sub-object.

[0129] In the disclosed embodiment, the capture module 82 is also used to: for any data capture point, in response to identifying that the non-interference program configured on the data capture is triggered, obtain the target state space of the service sub-object to which the data capture point belongs, and obtain the network status data of the service sub-object from the target state space through the non-interference program, wherein the target state space is one of the kernel space and the user space.

[0130] In the disclosed embodiment, the annotation module 83 is also used to: draw a topology map based on the service object set to obtain a candidate topology map; obtain the location identifier of each service sub-object in the service sub-object set of each service object; for any service sub-object, obtain the first topology object corresponding to the service sub-object from the candidate topology map, and annotate the location identifier and network status data of the service sub-object on the first topology object to obtain a marked second topology object; based on the second topology object of each service sub-object, annotate and update the candidate topology map to obtain a target topology map of the cloud service scenario.

[0131] In the disclosed embodiment, the labeling module 83 is also used to: for any service sub-object, obtain the node identifier of the network data forwarding node of the service sub-object and the grab point identifier of the data grab point configured for the service sub-object; and obtain the positioning identifier of the service sub-object based on the node identifier and the grab point identifier.

[0132] In the disclosed embodiment, the detection module 84 is also used to: obtain the annotated network status data on each third topological object in the target topological map; in response to identifying the presence of abnormal network data in the annotated network status data on each third topological object, obtain the abnormal fourth topological object in the target topological map, and obtain the abnormal location identifier from the object annotation information of the fourth topological object; based on the abnormal location identifier, locate the abnormal service sub-object from the service object set, and perform fault processing on the abnormal service sub-object based on the abnormal network data.

[0133] In the disclosed embodiment, the acquisition module 81 is also used to: acquire the service request initiation object set, load forwarding object set, service provision object set and link object set in the cloud service scenario; obtain the kernel state object set in the cloud service scenario based on the service request initiation object set and the service provision object set; obtain the user state object set in the cloud service scenario based on the service request initiation object set, the service provision object set and the load forwarding object set; obtain the service object set of the cloud service scenario based on the kernel state object set, the user state object set and the link object set.

[0134] The cloud service network detection device proposed in the present invention obtains a set of service objects in a cloud service scenario and a non-interference program for each service object, and captures a network status data set of each service object through the non-interference program, and annotates a candidate topology map of the cloud service scenario based on the network status data set of each service object, obtains a labeled target topology map, and performs network status detection on the cloud service scenario through the target topology map. In the present disclosure, the network status data set of each service object is captured by a non-interference program, which reduces the impact of the acquisition of the network status data set on the operation of the service object, improves the stability of the service object operation when the network status data set is captured, and compared with the acquisition of network status data by packet capture in the related art, the probability of abnormal data acquisition caused by packet capture positioning failure is avoided, the real-time and accuracy of the acquisition of the network status data set is improved, and the resource consumption of the acquisition of the network status data set is reduced. The target topology map of the cloud service scenario is obtained based on the network status data set and the candidate topology map, and the network status of the cloud service scenario is detected by the target topology map. Compared with the manual data integration in the related art, the dependence of the network status detection on manual labor is reduced, the detection efficiency and detection accuracy of the network status detection of the cloud service scenario are improved, thereby improving the stability of the network operation of the cloud service scenario and the stability of the cloud computing service provided by the cloud service scenario, and optimizing the user's service experience.

[0135] According to an embodiment of the present disclosure, the present disclosure also proposes an electronic device, a readable storage medium, and a computer program product.

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

[0137] like Fig. 9As shown, the device 900 includes a computing unit 901, which 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 909 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 via a bus 904. An input / output (I / O) interface 905 is also connected to the bus 904.

[0138] A number of components in the device 900 are connected to the I / O interface 905, including: an input unit 906, such as a keyboard, a mouse, etc.; an output unit 906, such as various types of displays, speakers, etc.; a storage unit 909, such as a disk, an optical disk, etc.; and a communication unit 909, such as a network card, a modem, a wireless communication transceiver, etc. 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 telecommunication networks.

[0139] The computing unit 901 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 901 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 901 performs the various methods and processes described above, such as a cloud service network detection method. For example, in some embodiments, the cloud service network detection method may be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as a storage unit 909. In some embodiments, part or all of the computer program may be loaded and / or installed on 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 cloud service network detection method described above may be performed. Alternatively, in other embodiments, the computing unit 901 may be configured to perform the cloud service network detection method in any other appropriate manner (e.g., by means of firmware).

[0140] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0141] The program code for implementing the method of the present disclosure may be written in any combination of one or more programming languages. These program codes may be presented to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, implements the functions / operations specified in the flow chart and / or block diagram. The program code may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0142] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0143] To propose interactions with a user account, the systems and techniques described herein may 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 the user account; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user account can propose input to the computer. Other types of devices may also be used to propose interactions with the user account; for example, feedback proposed to the user account may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user account may be received in any form (including acoustic input, voice input, or tactile input).

[0144] The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user account computer with a graphical user account interface or a web browser through which a user account can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), and the Internet.

[0145] A computer system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship of client and server is generated by computer programs running on respective computers and having a client-server relationship with each other. The server may be a cloud server, a server of a distributed system, or a server combined with a blockchain.

[0146] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this disclosure can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solutions disclosed in this disclosure can be achieved, and this document does not limit this.

[0147] The above specific implementations do not constitute a limitation on the protection scope of the present disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present disclosure shall be included in the protection scope of the present disclosure.

Claims

1. A cloud service network detection method, wherein: The method comprises: Acquire a service object set in a cloud service scenario to be detected, wherein the service object set is composed of kernel state objects, user state objects and link objects; Acquire a non-interference program for each service object in the service object set, and configure a data capture point for each service object through the non-interference program to capture a network status data set of each service object; Obtaining a candidate topology map of the cloud service scenario, and annotating the candidate topology map based on the network status data set to obtain an annotated target topology map; According to the target topology map, a network status detection is performed on the cloud service scenario.

2. The method according to claim 1, wherein: The step of obtaining the non-interference program of each service object in the service object set and configuring a data capture point for each service object through the non-interference program to capture a network status data set of each service object includes: Obtaining a service sub-object set of each service object and a hook point of each service sub-object in the service sub-object set; Based on the non-interference program, program configuration is performed on the hook points of each service sub-object to obtain the configured data capture points of each service sub-object; Capture data of each service sub-object based on the data capture point to obtain network status data of each service sub-object; Based on the network status data of each service sub-object, a network status data set of each service object is obtained.

3. The method according to claim 2, wherein: The method of capturing data of each service sub-object based on the data capture point to obtain network status data of each service sub-object includes: For any data capture point, in response to identifying that a non-interference program configured on the data capture is triggered, the target state space of the service sub-object to which the data capture point belongs is obtained, and the network status data of the service sub-object is obtained from the target state space through the non-interference program, wherein the target state space is one of the kernel space and the user space.

4. The method according to claim 1, wherein: The obtaining of the candidate topology map of the cloud service scenario and annotating the candidate topology map based on the network status data set to obtain the annotated target topology map includes: Draw a topology map based on the service object set to obtain the candidate topology map; Obtain the location identifier of each service sub-object in the service sub-object set of each service object; For any service sub-object, obtain a first topology object corresponding to the service sub-object from the candidate topology map, and mark the location identifier and network status data of the service sub-object on the first topology object to obtain a marked second topology object; Based on the second topology object of each service sub-object, the candidate topology map is annotated and updated to obtain the target topology map of the cloud service scenario.

5. The method according to claim 4, wherein: The obtaining of the location identifier of each service sub-object in the service sub-object set of each service object includes: For any service sub-object, obtain the node identifier of the network data forwarding node of the service sub-object and the grabbing point identifier of the data grabbing point configured by the service sub-object; Based on the node identifier and the grab point identifier, a location identifier of the service sub-object is obtained.

6. The method according to claim 1, wherein: The performing network status detection on the cloud service scenario according to the target topology map includes: Obtaining the annotated network status data on each third topology object in the target topology map; In response to identifying that abnormal network data exists in the annotated network status data on each third topology object, obtaining an abnormal fourth topology object in the target topology map, and obtaining an abnormal location identifier from the object annotation information of the fourth topology object; Based on the abnormal location identifier, the abnormal service sub-object is centrally located from the service object, and the abnormal service sub-object is fault processed based on the abnormal network data.

7. The method according to claim 1, wherein: The obtaining of a service object set in a cloud service scenario to be detected, wherein the service object set is composed of kernel state objects, user state objects and link objects, and includes: Obtaining a service request initiation object set, a load forwarding object set, a service provision object set, and a link object set in the cloud service scenario; Based on the service request initiating object set and the service providing object set, obtaining a kernel state object set in the cloud service scenario; Based on the service request initiation object set, the service provision object set and the load forwarding object set, a user state object set in the cloud service scenario is obtained; Based on the kernel state object set, the user state object set and the link object set, the service object set of the cloud service scenario is obtained.

8. A cloud service network detection device, wherein: The device comprises: An acquisition module, used to acquire a service object set in a cloud service scenario to be detected, wherein the service object set is composed of kernel state objects, user state objects and link objects; A capture module, used for acquiring a non-interference program of each service object in the service object set, and configuring a data capture point for each service object through the non-interference program to capture a network status data set of each service object; A labeling module, used to obtain a candidate topology map of the cloud service scenario, and label the candidate topology map based on the network status data set to obtain a labeled target topology map; A detection module is used to perform network status detection on the cloud service scenario according to the target topology map.

9. The device according to claim 7, wherein: The crawling module is also used for: Obtaining a service sub-object set of each service object and a hook point of each service sub-object in the service sub-object set; Based on the non-interference program, program configuration is performed on the hook points of each service sub-object to obtain the configured data capture points of each service sub-object; Capture data of each service sub-object based on the data capture point to obtain network status data of each service sub-object; Based on the network status data of each service sub-object, a network status data set of each service object is obtained.

10. The device according to claim 9, wherein: The crawling module is also used for: For any data capture point, in response to identifying that a non-interference program configured on the data capture is triggered, the target state space of the service sub-object to which the data capture point belongs is obtained, and the network status data of the service sub-object is obtained from the target state space through the non-interference program, wherein the target state space is one of the kernel space and the user space.

11. The device according to claim 8, wherein: The annotation module is also used for: Draw a topology map based on the service object set to obtain the candidate topology map; Obtain the location identifier of each service sub-object in the service sub-object set of each service object; For any service sub-object, obtain a first topology object corresponding to the service sub-object from the candidate topology map, and mark the location identifier and network status data of the service sub-object on the first topology object to obtain a marked second topology object; Based on the second topology object of each service sub-object, the candidate topology map is annotated and updated to obtain the target topology map of the cloud service scenario.

12. The device according to claim 11, wherein The annotation module is also used for: For any service sub-object, obtain the node identifier of the network data forwarding node of the service sub-object and the grabbing point identifier of the data grabbing point configured by the service sub-object; Based on the node identifier and the grab point identifier, a location identifier of the service sub-object is obtained.

13. The device according to claim 8, wherein: The detection module is further used for: Obtaining the annotated network status data on each third topology object in the target topology map; In response to identifying that abnormal network data exists in the annotated network status data on each third topology object, obtaining an abnormal fourth topology object in the target topology map, and obtaining an abnormal location identifier from the object annotation information of the fourth topology object; Based on the abnormal location identifier, the abnormal service sub-object is centrally located from the service object, and the abnormal service sub-object is fault processed based on the abnormal network data.

14. The device according to claim 8, wherein: The acquisition module is further used for: Obtaining a service request initiation object set, a load forwarding object set, a service provision object set, and a link object set in the cloud service scenario; Based on the service request initiating object set and the service providing object set, obtaining a kernel state object set in the cloud service scenario; Based on the service request initiation object set, the service provision object set and the load forwarding object set, a user state object set in the cloud service scenario is obtained; Based on the kernel state object set, the user state object set and the link object set, the service object set of the cloud service scenario is obtained.

15. An electronic device, comprising: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 7.

16. A non-transitory computer-readable storage medium storing computer instructions, wherein: The computer instructions are used to cause the computer to execute the method according to any one of claims 1-7.

17. A computer program product, comprising a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 7.

Images