CN118301656A - Multi-network plane work load state detection method and device and related equipment - Google Patents

Abstract

The disclosure provides a multi-network plane workload state detection method, a device and related equipment, and relates to the technical field of wireless communication networks, wherein the method comprises the following steps: responding to a creation request of a multi-network plane workload, and creating a corresponding network identification for each network plane of the multi-network plane workload, wherein the multi-network plane workload is a workload with a plurality of network planes; according to the container object identification of the multi-network plane workload and the network identification of each network plane, configuring network plane probe information for detecting the state of each network plane of the multi-network plane workload; and detecting the state information of each network plane of the multi-network plane workload according to the configured network plane probe information. The method and the device can realize probe detection on a plurality of network planes in a scene of the plurality of network planes.

Description

Multi-network plane work load state detection method and device and related equipment

Technical Field

The disclosure relates to the technical field of wireless communication networks, and in particular relates to a multi-network plane workload state detection method, a device and related equipment.

Background

Application program containerization is an important trend of modern software development and deployment, and Kubernetes is taken as an open-source container arrangement platform, so that a user can be helped to rapidly deploy and manage large-scale containerized applications, and the availability, stability and efficiency of application programs can be effectively improved. CT (Communication Technology ) applications, such as UPF (User Plane Function ), SMF (The Session Management function, session management function) and other network elements in a 5G (5 th Generation Mobile Communication Technology, fifth generation mobile communication technology) core network, require multiple network planes and network interfaces; internet technology (Internet Technology, IT) class applications, such as distributed databases, separate the data plane and the control plane in order to guarantee the bandwidth and latency of data transmission. After the application is deployed in a containerized manner, a CNI (Container Network Interface ) such as Multus (an open source CNI plug-in for Kubernetes, which can attach multiple network interfaces to Pod), cni-Genie (a component that can make Kubernetes use of multiple CNI network plug-ins) and the like can be used to meet the requirements of multiple network planes and multiple network interfaces. To ensure availability of services and network planes, probes are typically used to probe the status of services and network planes, but in a multi-network plane scenario, how to probe multiple network planes is not achieved by Kubernetes.

It should be noted that the information disclosed in the above background section is only for enhancing understanding of the background of the present disclosure and thus may include information that does not constitute prior art known to those of ordinary skill in the art.

Disclosure of Invention

The disclosure provides a method, a device and related equipment for detecting states of multiple network planes, which at least overcome the technical problem that states of multiple network planes cannot be detected in a scene of the multiple network plane workload in the related technology to a certain extent.

Other features and advantages of the present disclosure will be apparent from the following detailed description, or may be learned in part by the practice of the disclosure.

According to one aspect of the present disclosure, there is provided a multi-network plane workload state detection method, including: creating a corresponding network identification for each network plane of a multi-network plane workload in response to a creation request of the multi-network plane workload, wherein the multi-network plane workload is a workload with a plurality of network planes; according to the container object identification of the multi-network plane workload and the network identification of each network plane, configuring network plane probe information for detecting the state of each network plane of the multi-network plane workload; and detecting the state information of each network plane of the multi-network plane workload according to the configured network plane probe information.

In some exemplary embodiments of the present disclosure, based on the foregoing solution, configuring network plane probe information for performing status detection on each network plane of the multi-network plane workload according to the container object identification of the multi-network plane workload and the network identification of each network plane, includes: configuring the domain name of each network plane of the multi-network plane workload according to the container object identification of the multi-network plane workload and the network identification of each network plane; and configuring the domain name of each network plane of the multi-network plane workload as network plane probe information corresponding to each network plane of the multi-network plane workload.

In some exemplary embodiments of the present disclosure, based on the foregoing solution, configuring the domain name of each network plane of the multi-network plane workload as network plane probe information corresponding to each network plane of the multi-network plane workload includes: configuring a network plane probe domain name corresponding to each network plane of the multi-network plane workload according to the domain name of each network plane of the multi-network plane workload; and analyzing the network plane probe information corresponding to the network plane probe domain name.

In some exemplary embodiments of the present disclosure, based on the foregoing solution, before configuring the network plane probe domain name corresponding to each network plane of the multi-network plane workload according to the domain name of each network plane of the multi-network plane workload, the method further includes: storing the workload information corresponding to the multi-network plane workload to a resource database; and updating the domain name of each network plane of the multi-network-plane workload of the workload information in the resource database according to the creation request of the multi-network-plane workload.

In some exemplary embodiments of the present disclosure, based on the foregoing solution, the network plane probe information includes a null value or a non-null value, the network interface corresponding to the multi-network plane includes a default network interface or a non-default network interface, and before detecting the state information of each network plane of the multi-network plane workload according to the configured network plane probe information, the method further includes: under the condition that the network plane probe information is null, determining the network interface of the network plane as a default network interface; and under the condition that the network plane probe information is a non-null value, determining that the network interface of the network plane is a non-default network interface, creating a domain name resolution record corresponding to the non-default network interface, and storing the domain name resolution record corresponding to the non-default network interface creation in a domain name-IP data list.

In some exemplary embodiments of the present disclosure, based on the foregoing solution, detecting status information of each network plane of the multi-network plane workload according to configured network plane probe information includes: under the condition that the network plane probe information is null, detecting the state information of the network plane directly according to the detection address corresponding to the default network interface; and under the condition that the network plane probe information is a non-null value, inquiring an IP address corresponding to the non-default network interface according to the domain name-IP data list, and detecting the state information of the network plane according to the IP address corresponding to the non-default network interface.

In some exemplary embodiments of the present disclosure, based on the foregoing scheme, in response to a creation request of a multi-network plane workload, creating a respective network identification for each network plane of the multi-network plane workload, including: declaring, by way of annotation, a plurality of network interfaces, the plurality of network interfaces comprising: the container network interface plug-in of the multi-network plane and each network plane of the multi-network plane workload create a respective network identification.

According to another aspect of the present disclosure, there is also provided a multi-network plane workload state detection apparatus, including: a network identification creation module, which is applied to respond to a creation request of a multi-network-plane workload, and creates a corresponding network identification for each network plane of the multi-network-plane workload, wherein the multi-network-plane workload is a workload with a plurality of network planes; the network plane probe information configuration module is used for configuring network plane probe information for detecting the state of each network plane of the multi-network plane workload according to the container object identifier of the multi-network plane workload and the network identifier of each network plane; and the network plane state detection module is used for detecting the state information of each network plane of the multi-network plane workload according to the configured network plane probe information.

According to still another aspect of the present disclosure, there is also provided an electronic apparatus including: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform any of the multi-network plane workload state detection methods described above via execution of the executable instructions.

According to yet another aspect of the present disclosure, there is also provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements any of the above-described multi-network plane workload state detection methods.

According to another aspect of the present disclosure, there is also provided a computer program product comprising: computer program or instructions which when executed by a processor implement the multi-network plane workload state detection method of any one of the above.

According to the method, the device and the related equipment for detecting the state of the multi-network plane workload, corresponding network identifications are created for each network plane of the multi-network plane workload, network plane probe information for detecting the state of each network plane is configured according to the container object identifications of the multi-network plane workload and the network identifications of each network plane, and finally the state information of each network plane of the multi-network plane workload is detected according to the configured network plane probe information, so that the network planes needing to be detected can be flexibly configured on the premise of not changing the functional design of the existing system of Kubernetes. Compared with the problem that in the related art, for a workload with a plurality of network planes, probes cannot be specified for other network planes, the embodiment of the disclosure can detect the state information of the corresponding network plane by creating a network identifier for each network plane and only configuring the network plane probe information corresponding to the network identifier to be detected, thereby realizing the probe detection of the multiple network planes.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure. It will be apparent to those of ordinary skill in the art that the drawings in the following description are merely examples of the disclosure and that other drawings may be derived from them without undue effort.

FIG. 1 illustrates an exemplary application system architecture diagram of a multi-network plane workload state detection method in an embodiment of the present disclosure;

FIG. 2 illustrates a schematic diagram of a multi-network plane workload state detection method in an embodiment of the present disclosure;

FIG. 3 illustrates a workflow diagram for implementing a multi-network plane workload state detection method in an embodiment of the present disclosure;

FIG. 4 illustrates a schematic diagram of a multi-network plane workload state detection method in an embodiment of the present disclosure;

fig. 5 illustrates a UPF network element interface interaction diagram in an embodiment of the present disclosure;

fig. 6 illustrates a schematic diagram of UPF network element service network plane interaction in an embodiment of the present disclosure;

FIG. 7 illustrates a schematic diagram of a multi-network planar workload state detection device in an embodiment of the present disclosure;

fig. 8 is a schematic diagram of an electronic device to which a multi-network plane workload state detection method is applied in an embodiment of the present disclosure.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the disclosed aspects may be practiced without one or more of the specific details, or with other methods, components, devices, steps, etc. In other instances, well-known methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the disclosure.

The flow diagrams depicted in the figures are exemplary only, and do not necessarily include all of the elements and operations/steps, nor must they be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the order of actual execution may be changed according to actual situations.

FIG. 1 illustrates an exemplary application system architecture diagram to which the multi-network plane workload state detection method of embodiments of the present disclosure may be applied. As shown in fig. 1, the system architecture may include a terminal device 101, a network 102, and a server 103.

The medium used by the network 102 to provide a communication link between the terminal device 101 and the server 103 may be a wired network or a wireless network.

Alternatively, the wireless network or wired network described above uses standard communication techniques and/or protocols. The network is typically the Internet, but may be any network including, but not limited to, a local area network (Local Area Network, LAN), metropolitan area network (Metropolitan Area Network, MAN), wide area network (Wide Area Network, WAN), mobile, wired or wireless network, private network, or any combination of virtual private networks. In some embodiments, data exchanged over the network is represented using techniques and/or formats including HyperText Mark-up Language (HTML), extensible markup Language (Extensible MarkupLanguage, XML), and the like. All or some of the links may also be encrypted using conventional encryption techniques such as secure sockets layer (Secure Socket Layer, SSL), transport layer security (Transport Layer Security, TLS), virtual private network (Virtual Private Network, VPN), internet protocol security (Internet ProtocolSecurity, IPsec), etc. In other embodiments, custom and/or dedicated data communication techniques may also be used in place of or in addition to the data communication techniques described above.

The terminal device 101 may be a variety of electronic devices including, but not limited to, smart phones, tablet computers, laptop portable computers, desktop computers, wearable devices, augmented reality devices, virtual reality devices, and the like.

Alternatively, the clients of the applications installed in different terminal devices 101 are the same or clients of the same type of application based on different operating systems. The specific form of the application client may also be different based on the different terminal platforms, for example, the application client may be a mobile phone client, a PC client, etc.

The server 103 may be a server providing various services, such as a background management server providing support for devices operated by the user with the terminal device 301. The background management server can analyze and process the received data such as the request and the like, and feed back the processing result to the terminal equipment.

Optionally, the server may be an independent physical server, or may be a server cluster or a distributed system formed by a plurality of physical servers, or may be a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs (Content Delivery Network, content delivery networks), and basic cloud computing services such as big data and artificial intelligence platforms. The terminal may be, but is not limited to, a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart watch, etc. The terminal and the server may be directly or indirectly connected through wired or wireless communication, and the present application is not limited herein.

Those skilled in the art will appreciate that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative, and that any number of terminal devices, networks, and servers may be provided as desired. The embodiments of the present disclosure are not limited in this regard.

Under the system architecture described above, embodiments of the present disclosure provide a multi-network plane workload state detection method that may be performed by any electronic device with computing processing capabilities.

In some embodiments, the multi-network plane workload state detection method provided in the embodiments of the present disclosure may be performed by a terminal device of the above system architecture; in other embodiments, the multi-network plane workload state detection method provided in the embodiments of the present disclosure may be performed by a server in the system architecture described above; in other embodiments, the multi-network plane workload state detection method provided in the embodiments of the present disclosure may be implemented by the terminal device and the server in the system architecture in an interactive manner.

It should be noted that, in the related art Kubernetes implementation, three types of probes, that is, survival, ready and start probes, can be classified according to the purpose of use of the probe, and they can detect the state of the workload, and the Kubernetes manages the life cycle of the workload according to the state returned by the probe. In particular implementations, each probe can probe in the manner of hypertext transfer protocol (Hypertext Transfer Protocol, HTTP), transmission control protocol (Transmission Control Protocol, TCP) or gRPC (which is a modern open source high performance remote procedure call framework that can be run in any environment), where HTTP and TCP probes can configure the hostname to be probed through the Host field, default to Pod's internet protocol (Internet Protocol, IP), and for workloads with multiple network planes, the probe cannot be specified for other network planes, with the following problems and challenges:

1) Under the multi-network plane, the probe configuration limit is large. If the Host field of the HTTP and TCP probes designates the IP of other network planes, it is necessary to allocate the IP to each network plane plan in advance, which greatly limits the characteristics of flexibility, easy migration, and the like of the container, and increases the difficulty of use.

2) The single network plane state cannot represent the entire workload state. The plurality of network planes are responsible for different traffic flows, and under the condition that the cluster automatically distributes the network plane IP of the workload, the probe can only detect the default plane, when the default network plane is ready and the other network plane for processing the service is not ready, but Kubernetes considers that the workload is ready according to the detection result of the default plane, and the traffic flow is distributed to the workload, so that the service response fails.

3) The essential reason for this problem is that the Kubernetes probe does not take into account the probing requirements of multi-network plane workloads in its implementation and cannot be configured to specify the network planes that need to be probed. How to realize the probe detection of the multi-network plane workload is the key for realizing the stable and efficient operation of the multi-network plane workload.

Firstly, in view of the above-mentioned problems, an embodiment of the present disclosure provides a method for detecting a workload state of multiple network planes, which may be applied, but is not limited to, and may be specifically applied to Kubernetes, to configure a probe for detecting multiple network planes, and further detect state information of each network plane.

Fig. 2 is a schematic diagram of a multi-network plane workload state detection method according to an embodiment of the disclosure, as shown in fig. 2, where the multi-network plane workload state detection method provided in the embodiment of the disclosure includes the following steps:

s202, responding to a creation request of the multi-network plane workload, and creating a corresponding network identification for each network plane of the multi-network plane workload, wherein the multi-network plane workload is a workload with a plurality of network planes.

It should be noted that, the multi-network plane workload in the embodiments of the present disclosure is an application running on Kubernetes, where the workload in the embodiments of the present disclosure may be run in one Pod, whether the workload is made up of a single component or multiple components working together; and, the network identification in the embodiments of the present disclosure is a network account number (Identity Document, ID) of each network plane, that is, one Pod in the embodiments of the present disclosure corresponds to one workload, one Pod has a plurality of network planes, each network plane has a corresponding network ID.

In more detail, when creating a workload, the embodiments of the present disclosure need only create a corresponding one of the network identifications for each network plane that is used to distinguish between the network interfaces corresponding to each network plane that created the workload, where the IP address of each network interface is automatically assigned by the container network interface (Container Network Interface, CNI).

S204, according to the container object identification of the multi-network plane workload and the network identification of each network plane, the network plane probe information for detecting the state of each network plane of the multi-network plane workload is configured.

It should be noted that, the container object in the embodiment of the present disclosure is identified as a domain name of the multi-network plane workload, that is, one domain name corresponding to one Pod in the embodiment of the present disclosure, and the network plane probe information in the embodiment of the present disclosure should include the domain name of the Pod and the network ID corresponding to the network plane to be probed.

In more detail, in the embodiment of the present disclosure, the domain name of Pod is represented by < Pod name >, and the network identifier corresponding to the network plane is represented by < Net id >, and when the probe information of the network plane is configured, the embodiment of the present disclosure only needs to update the Host field of the probe in the Pod configuration, that is < Pod name > < Net id >, which corresponds to the domain name of Pod of the network plane to be detected and the corresponding network identifier.

S206, detecting the state information of each network plane of the multi-network plane workload according to the configured network plane probe information.

It should be noted that, the state information of each network plane of the workload in the embodiment of the present disclosure may be: pending, running, succeeded, failed, and unowns, where Pending refers to that the file of Pod has submitted Kubernetes, the application programming interface (Application Programming Interface, API) object has been created and saved Etcd (a distributed key value storage system), but without a successful dispatch, possibly because a certain container in Pod was not started successfully; running means that Pod scheduling is successful, and the containers in Pod are successfully created and at least one is Running; succeeded means that all containers of Pod run normally successfully and exit; failed means that the Pod has been exited in an abnormal state of at least one container; the Unknown refers to an abnormal state, and the Pod state cannot be detected by the cluster, which may be a problem in communication between the master node and the slave node.

The embodiment of the disclosure provides a multi-network plane workload state detection method, firstly, responding to a creation request of a multi-network plane workload, and creating a corresponding network identifier for each network plane of the multi-network plane workload; secondly, according to the container object identification of the multi-network plane workload and the network identification of each network plane, configuring network plane probe information for detecting the state of each network plane of the multi-network plane workload; then, the state information of each network plane of the multi-network plane workload is detected according to the configured network plane probe information. Compared with the problem that in the related art, for a workload with a plurality of network planes, probes cannot be specified for other network planes, the embodiment of the disclosure can detect the state information of the corresponding network plane by creating a network identifier for each network plane and only configuring the network plane probe information corresponding to the network identifier to be detected, thereby realizing the probe detection of the multiple network planes.

In some embodiments, the disclosed embodiments configure network plane probe information for status detection for each network plane of a multi-network plane workload according to a container object identification of the multi-network plane workload and a network identification of each network plane, including: configuring the domain name of each network plane of the multi-network plane workload according to the container object identification of the multi-network plane workload and the network identification of each network plane; and configuring the domain name of each network plane of the multi-network plane workload as network plane probe information corresponding to each network plane of the multi-network plane workload. Specifically, in the embodiment of the disclosure, the domain name of each network plane is configured through the container object identifier of the multi-network plane workload and the network identifier of each network plane, that is, the domain name of Pod and the network ID of each network plane are combined to obtain the domain name of each network plane, and then corresponding network plane probe information is configured for each network plane of the multi-network plane workload according to the domain name of each network plane, so that the one-to-one correspondence between the domain name of each network plane and the network plane probe information is ensured, and if a certain network plane needs to be detected, only the domain name of the network plane needs to be determined, thereby realizing probe detection on a plurality of network planes.

In some embodiments, the disclosed embodiments configure a domain name of each network plane of a multi-network plane workload as network plane probe information corresponding to each network plane of the multi-network plane workload, including: configuring a network plane probe domain name corresponding to each network plane of the multi-network plane workload according to the domain name of each network plane of the multi-network plane workload; and analyzing network plane probe information corresponding to the network plane probe domain name. Specifically, if the IP address of the probe is the same as the IP address of any network plane, it indicates that the probe and the network plane can perform network data transmission, and in the embodiment of the disclosure, the domain name of each network plane is configured as the network plane probe domain name of the network plane, and the network plane probe domain name is resolved to obtain network plane probe information, so that detection can be performed on each network plane.

In some embodiments, before configuring the network plane probe domain name corresponding to each network plane of the multi-network plane workload according to the domain name of each network plane of the multi-network plane workload, the multi-network plane workload state detection method in the embodiments of the present disclosure further includes: storing workload information corresponding to the multi-network plane workload into a resource database; and updating the domain name of each network plane of the multi-network-plane workload of the workload information in the resource database according to the creation request of the multi-network-plane workload. In more detail, as shown in fig. 3, the resource database in the embodiment of the disclosure may be Etcd, etcd internally adopts Raft protocol (a consistency algorithm based on log replication, which is implemented by selecting a leader), and the controller of Kubernetes monitors the resource change event in real time through ETCD WATCH mechanism, compares whether the actual state is consistent with the expected state, and takes a coordinated action to make it consistent, monitors the creation request of the workload of multiple network planes, that is, when the request of Pod creation is detected, the embodiment of the disclosure may modify the value of the Host field in the Pod probe in Etcd through the Api-server, and stores the domain name of each network plane after the modification.

In some embodiments, the network plane probe information includes a null value or a non-null value, the network interface corresponding to the multi-network plane includes a default network interface or a non-default network interface, and before detecting the state information of each network plane of the multi-network plane workload according to the configured network plane probe information, the multi-network plane workload state detection method in the embodiments of the present disclosure further includes: under the condition that the network plane probe information is null, determining the network interface of the network plane as a default network interface; and under the condition that the network plane probe information is a non-null value, determining the network interface of the network plane as a non-default network interface, creating a domain name resolution record corresponding to the non-default network interface, and storing the domain name resolution record corresponding to the non-default network interface creation in a domain name-IP data list. In more detail, as shown in fig. 4, in the Kubernetes related art, the probe uses the IP of the first network plane by default to probe, then the network interface used by the first network plane is the default network interface, that is, eth0 in fig. 4 is the default network interface, the network interfaces used by other network planes are non-default network interfaces, that is, net1 in fig. 4, if the probe IP is manually specified, then the IP needs to be allocated in advance, specifically, the domain name-IP data list in the embodiment of the disclosure may be characterized by Kubelet DNS, kubelet DNS providing DNS interpretation service for adding Pod DNS to the configured DNS service list of Kubelet, pod DNS in the embodiment of the disclosure provides DNS interpretation service for each non-default network interface of Pod, synchronizes state information of Pod to the Api-server through Kubelet, creates DNS records in Pod DNS records for the network interfaces of the respective network planes after monitoring that Pod creation is completed, and creates DNS interpretation service lists of Pod joining Kubelet, kubelet, and if DNS is required to search for corresponding DNS records.

In more detail, as shown in fig. 4, the DNS-controller in the embodiment of the present disclosure is configured to monitor creation and deletion of a Pod, update, by an Api-server, a host field of a probe in a Pod configuration to < Pod name > < Net id >, and create a corresponding DNS record in a Pod DNS service, where < Pod name > < Net id > corresponds to an IP address one by one, and delete, when the Pod deletes, the DNS record associated therewith.

In some embodiments, detecting status information of each network plane of a multi-network plane workload according to configured network plane probe information includes: under the condition that the network plane probe information is null, detecting the state information of the network plane directly according to the detection address corresponding to the default network interface; and under the condition that the network plane probe information is a non-null value, inquiring an IP address corresponding to the non-default network interface according to the domain name-IP data list, and detecting the state information of the network plane according to the IP address corresponding to the non-default network interface. Specifically, as shown in fig. 3, the probe in the embodiment of the present disclosure performs ready detection according to the declaration information of Pod, and uses a default network interface because the Host field is empty, if the CNI automatically configures the default network interface with an address of: 10.43.218.135, the probe address is: 10.43.218.135:80; or the probe carries out survival detection according to the declaration information of Pod, and obtains the IP address of the probe to be 10.42.2.2 through DNS query according to the value of the Host field, and the detection address is: 10.42.2.2:8080.

In some embodiments, embodiments of the present disclosure create a respective network identification for each network plane of a multi-network plane workload in response to a create request for the multi-network plane workload, comprising: declaring, by way of annotation, a plurality of network interfaces, the plurality of network interfaces comprising: the container network interface plug-in for the multi-network plane and each network plane of the multi-network plane workload create a respective network identification. In the declaration file of the workload, a plurality of network interfaces are declared in an annotation mode, each network interface comprises a CNI plug-in for creating the network plane and a network identifier, in the probe configuration, a Host field fills in the network identifier of the network interface needing to be probed, and the default network interface is used if the Host field is not filled in or has a null value.

In some embodiments, the problem addressed by the embodiments of the present disclosure is further illustrated by a 5G core network scenario, in which a user plane function (UserPlaneFunction, UPF) network element needs to interact with a session management function (SessionManagement Function, SMF), wireless networks (Radio Access Network, (R) AN) and DN (representing the network providing all target traffic services), involving the following interfaces:

n3 interface: for transferring uplink and downlink user plane data between UPF and 5G (R) AN;

n4 interface: for transmitting control plane information between the UPF and the SMF;

n6 interface: for transmitting upstream and downstream user data streams between UPF and DN;

n9 interface: for transmitting upstream and downstream user data between the UPF and other UPFs;

in the embodiment 5C core network scenario of the present disclosure, a network element may have multiple network planes, each of which is responsible for different traffic data. Taking a UPF network element as an example, as shown in fig. 6, there are 4 service network planes in total, and data interaction is performed with different network elements, all network planes need to work normally to indicate that the function of the UPF network element is normal, the network state of any network plane cannot represent the states of other network planes, in the related-technology implementation of Kubernetes, the probe defaults to use the IP of the first network plane for detection, if the detection IP of the probe is manually specified, the IP needs to be planned and allocated in advance, so that the characteristics of elasticity, flexibility, easy migration and the like of the workload on the Kubernetes are greatly limited, meanwhile, the difficulty of user use is increased, and in order to better bear the workload of multiple network planes, the Kubernetes needs to realize the detection plane of the custom probe.

Based on the same inventive concept, a multi-network plane workload state detection device is also provided in the embodiments of the present disclosure, as follows. Since the principle of solving the problem of the embodiment of the device is similar to that of the embodiment of the method, the implementation of the embodiment of the device can be referred to the implementation of the embodiment of the method, and the repetition is omitted.

Fig. 7 is a schematic diagram of a multi-network plane workload state detection device according to an embodiment of the disclosure, as shown in fig. 7, the device includes:

A network identifier creation module 701, configured to create, for each network plane of a multi-network plane workload in response to a creation request of the multi-network plane workload, where the multi-network plane workload is a workload having a plurality of network planes;

The network plane probe information configuration module 702 is configured to configure network plane probe information for performing state detection on each network plane of the multi-network plane workload according to the container object identifier of the multi-network plane workload and the network identifier of each network plane;

the network plane status detection module 703 is configured to detect status information of each network plane of the multi-network plane workload according to the configured network plane probe information.

The embodiment of the disclosure provides a multi-network plane workload state detection device, which creates a corresponding network identifier for each network plane of a multi-network plane workload through a network identifier creation module; the network plane probe information configuration module is used for configuring the network plane probe information of each network plane for state detection according to the container object identification of the multi-network plane workload and the network identification of each network plane; the network plane state detection module is used for detecting the state information of each network plane of the multi-network plane workload according to the configured network plane probe information, and the network planes needing to be detected can be flexibly configured on the premise of not changing the functional design of the Kubernetes existing system. Compared with the problem that in the related art, for a workload with a plurality of network planes, probes cannot be specified for other network planes, the embodiment of the disclosure can detect the state information of the corresponding network plane by creating a network identifier for each network plane and only configuring the network plane probe information corresponding to the network identifier to be detected, thereby realizing the probe detection of the multiple network planes.

In some embodiments, the network plane probe information configuration module in the embodiments of the present disclosure is further configured to configure a domain name of each network plane of the multi-network plane workload according to the container object identifier of the multi-network plane workload and the network identifier of each network plane; and configuring the domain name of each network plane of the multi-network plane workload as network plane probe information corresponding to each network plane of the multi-network plane workload.

In some embodiments, the network plane probe information configuration module in the embodiments of the present disclosure is further configured to configure a network plane probe domain name corresponding to each network plane of the multi-network plane workload according to the domain name of each network plane of the multi-network plane workload; and analyzing network plane probe information corresponding to the network plane probe domain name.

In some embodiments, the multi-network plane workload state detection device in the embodiments of the present disclosure further comprises: the workload information storage module is used for storing the workload information corresponding to the multi-network plane workload to the resource database before configuring the network plane probe domain name corresponding to each network plane of the multi-network plane workload according to the domain name of each network plane of the multi-network plane workload; and the updating module is used for updating the domain name of each network plane of the multi-network-plane workload of the workload information in the resource database according to the creation request of the multi-network-plane workload.

In some embodiments, the network plane probe information in the embodiments of the present disclosure includes a null value or a non-null value, the network interface corresponding to the multi-network plane includes a default network interface or a non-default network interface, and the multi-network plane workload state detecting device in the embodiments of the present disclosure further includes: the first determining module is used for determining that the network interface of the network plane is a default network interface under the condition that the network plane probe information is null before detecting the state information of each network plane of the multi-network plane workload according to the configured network plane probe information; and the second determining module is used for determining that the network interface of the network plane is a non-default network interface under the condition that the network plane probe information is a non-null value, creating a domain name resolution record corresponding to the non-default network interface, and storing the domain name resolution record corresponding to the non-default network interface creation in a domain name-IP data list.

In some embodiments, the network plane state detection module in the embodiments of the present disclosure is further configured to detect, directly according to a detection address corresponding to a default network interface, state information of a network plane when the network plane probe information is null; and under the condition that the network plane probe information is a non-null value, inquiring an IP address corresponding to the non-default network interface according to the domain name-IP data list, and detecting the state information of the network plane according to the IP address corresponding to the non-default network interface.

In some embodiments, the network identifier creation module in the embodiments of the present disclosure is further configured to declare, by way of annotation, a plurality of network interfaces, where the plurality of network interfaces includes: the container network interface plug-in for the multi-network plane and each network plane of the multi-network plane workload create a respective network identification.

Those skilled in the art will appreciate that the various aspects of the present disclosure may be implemented as a system, method, or program product. Accordingly, various aspects of the disclosure may be embodied in the following forms, namely: an entirely hardware embodiment, an entirely software embodiment (including firmware, micro-code, etc.) or an embodiment combining hardware and software aspects may be referred to herein as a "circuit," module "or" system.

Based on the same inventive concept, an embodiment of the present disclosure further provides an electronic device, including: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform the multi-network plane workload state detection method of any one of the above via execution of the executable instructions. Since the principle of solving the problem of the embodiment of the electronic device is similar to that of the embodiment of the method, the implementation of the embodiment of the electronic device can be referred to the implementation of the embodiment of the method, and the repetition is omitted.

An electronic device 800 according to such an embodiment of the present disclosure is described below with reference to fig. 8. The electronic device 800 shown in fig. 8 is merely an example and should not be construed to limit the functionality and scope of use of embodiments of the present disclosure in any way.

As shown in fig. 8, the electronic device 800 is embodied in the form of a general purpose computing device. Components of electronic device 800 may include, but are not limited to: the at least one processing unit 801, the at least one memory unit 802, and a bus 803 connecting the different system components (including the memory unit 802 and the processing unit 801).

In which a storage unit stores program code that can be executed by the processing unit 801, such that the processing unit 801 performs steps according to various exemplary embodiments of the present disclosure described in the above section of the present specification.

In some embodiments, when the electronic device is used to control a multi-network plane workload state detection method such as described above in the present disclosure, the processing unit 801 may perform the following steps of the method embodiments described above: responding to a creation request of a multi-network plane workload, and creating a corresponding network identification for each network plane of the multi-network plane workload, wherein the multi-network plane workload is a workload with a plurality of network planes; according to the container object identification of the multi-network plane workload and the network identification of each network plane, configuring network plane probe information for detecting the state of each network plane of the multi-network plane workload; and detecting the state information of each network plane of the multi-network plane workload according to the configured network plane probe information.

The storage unit 802 may include readable media in the form of volatile storage units, such as Random Access Memory (RAM) 8021 and/or cache memory 8022, and may further include Read Only Memory (ROM) 8023.

The storage unit 802 may also include a program/utility 8024 having a set (at least one) of program modules 8025, such program modules 8025 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.

Bus 803 may be one or more of several types of bus structures including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

The electronic device 800 may also communicate with one or more external devices 804 (e.g., keyboard, pointing device, bluetooth device, etc.), one or more devices that enable a user to interact with the electronic device 800, and/or any device (e.g., router, modem, etc.) that enables the electronic device 800 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 805. Also, the electronic device 800 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet, through a network adapter 806. As shown, network adapter 806 communicates with other modules of electronic device 800 over bus 803. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 800, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.

From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, including several instructions to cause a computing device (may be a personal computer, a server, a terminal device, or a network device, etc.) to perform the method according to the embodiments of the present disclosure.

Based on the same inventive concept, there is also provided in an embodiment of the present disclosure a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the multi-network plane workload state detection method of any one of the above. Since the principle of the solution of the problem of the embodiment of the computer readable storage medium is similar to that of the embodiment of the method, the implementation of the embodiment of the computer readable storage medium can be referred to the implementation of the embodiment of the method, and the repetition is omitted.

More specific examples of the computer readable storage medium in the present disclosure may include, but are not limited to: an electrical connection having 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.

In this disclosure, a computer readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Alternatively, the program code embodied on a computer readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

In particular implementations, the program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).

There is also provided, based on the same inventive concept, in an embodiment of the present disclosure, a computer program product, including: computer program or instructions which, when executed by a processor, implement the multi-network plane workload state detection method of any one of the above method embodiments. Since the principle of the solution of the problem of the embodiment of the computer program product is similar to that of the embodiment of the method, the implementation of the embodiment of the computer program product can be referred to the implementation of the embodiment of the method, and the repetition is omitted.

It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.

Furthermore, although the steps of the methods in the present disclosure are depicted in a particular order in the drawings, this does not require or imply that the steps must be performed in that particular order, or that all illustrated steps be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform, etc.

From the description of the above embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, including several instructions to cause a computing device (may be a personal computer, a server, a mobile terminal, or a network device, etc.) to perform the method according to the embodiments of the present disclosure.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

Claims (11)

1. A method for detecting a multi-network plane workload state, comprising:

Creating a corresponding network identification for each network plane of a multi-network plane workload in response to a creation request of the multi-network plane workload, wherein the multi-network plane workload is a workload with a plurality of network planes;

According to the container object identification of the multi-network plane workload and the network identification of each network plane, configuring network plane probe information for detecting the state of each network plane of the multi-network plane workload;

and detecting the state information of each network plane of the multi-network plane workload according to the configured network plane probe information.

2. The multi-network plane workload state detection method according to claim 1, wherein configuring network plane probe information for performing state detection on each network plane of the multi-network plane workload according to the container object identification of the multi-network plane workload and the network identification of each network plane comprises:

configuring the domain name of each network plane of the multi-network plane workload according to the container object identification of the multi-network plane workload and the network identification of each network plane;

And configuring the domain name of each network plane of the multi-network plane workload as network plane probe information corresponding to each network plane of the multi-network plane workload.

3. The method for detecting the workload state of multiple network planes according to claim 2, wherein configuring the domain name of each network plane of the workload of multiple network planes as the network plane probe information corresponding to each network plane of the workload of multiple network planes comprises:

configuring a network plane probe domain name corresponding to each network plane of the multi-network plane workload according to the domain name of each network plane of the multi-network plane workload;

and analyzing the network plane probe information corresponding to the network plane probe domain name.

4. The multi-network plane workload state detection method according to claim 3, wherein before configuring the network plane probe domain name corresponding to each network plane of the multi-network plane workload according to the domain name of each network plane of the multi-network plane workload, the method further comprises:

storing the workload information corresponding to the multi-network plane workload to a resource database;

And updating the domain name of each network plane of the multi-network-plane workload of the workload information in the resource database according to the creation request of the multi-network-plane workload.

5. The multi-network plane workload state detection method according to claim 1, wherein the network plane probe information comprises a null value or a non-null value, the network interface corresponding to the multi-network plane comprises a default network interface or a non-default network interface, and before detecting the state information of each network plane of the multi-network plane workload according to the configured network plane probe information, the method further comprises:

under the condition that the network plane probe information is null, determining the network interface of the network plane as a default network interface;

and under the condition that the network plane probe information is a non-null value, determining that the network interface of the network plane is a non-default network interface, creating a domain name resolution record corresponding to the non-default network interface, and storing the domain name resolution record corresponding to the non-default network interface creation in a domain name-IP data list.

6. The multi-network plane workload state detection method according to claim 5, wherein detecting the state information of each network plane of the multi-network plane workload based on the configured network plane probe information comprises:

Under the condition that the network plane probe information is null, detecting the state information of the network plane directly according to the detection address corresponding to the default network interface;

And under the condition that the network plane probe information is a non-null value, inquiring an IP address corresponding to the non-default network interface according to the domain name-IP data list, and detecting the state information of the network plane according to the IP address corresponding to the non-default network interface.

7. The multi-network plane workload state detection method according to claim 1, wherein creating a respective network identification for each network plane of the multi-network plane workload in response to a creation request of the multi-network plane workload comprises:

Declaring, by way of annotation, a plurality of network interfaces, the plurality of network interfaces comprising: the container network interface plug-in of the multi-network plane and each network plane of the multi-network plane workload create a respective network identification.

8. A multi-network plane workload state detection device, comprising:

A network identification creation module, which is applied to respond to a creation request of a multi-network-plane workload, and creates a corresponding network identification for each network plane of the multi-network-plane workload, wherein the multi-network-plane workload is a workload with a plurality of network planes;

The network plane probe information configuration module is used for configuring network plane probe information for detecting the state of each network plane of the multi-network plane workload according to the container object identifier of the multi-network plane workload and the network identifier of each network plane;

and the network plane state detection module is used for detecting the state information of each network plane of the multi-network plane workload according to the configured network plane probe information.

9. An electronic device, comprising:

a processor; and

A memory for storing executable instructions of the processor;

wherein the processor is configured to perform the multi-network plane workload state detection method of any one of claims 1 to 7 via execution of the executable instructions.

10. A computer readable storage medium having stored thereon a computer program, wherein the computer program when executed by a processor implements the multi-network plane workload state detection method according to any one of claims 1 to 7.

11. A computer program product comprising: computer program or instructions, which when executed by a processor implements the multi-network plane workload state detection method according to any one of claims 1 to 7.