CN115550187B - Network element topology change method, device, system, electronic device and storage medium - Google Patents
Network element topology change method, device, system, electronic device and storage medium Download PDFInfo
- Publication number
- CN115550187B CN115550187B CN202211056891.3A CN202211056891A CN115550187B CN 115550187 B CN115550187 B CN 115550187B CN 202211056891 A CN202211056891 A CN 202211056891A CN 115550187 B CN115550187 B CN 115550187B
- Authority
- CN
- China
- Prior art keywords
- network element
- topology
- pod
- component
- service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides a network element topology change method, a device, a system, electronic equipment and a storage medium, belonging to the technical field of cloud computing and communication, comprising the steps of obtaining a Pod change event by using a topology gateway component; analyzing the Pod change event by using a topology gateway component to obtain a network element micro-service Pod of the target network element, writing the network element micro-service Pod into the Kafka topic, and calling the network element micro-service Pod from the Kafka topic by using the topology component to update a network element topology hierarchy chart of the target network element. According to the network element topology changing method, device, system, electronic equipment and storage medium, the Pod changing event is analyzed and checked, and the Pod related to the network element is dynamically identified to update the topology structure of the network element, so that the dynamic configuration update of the network element is realized under the condition of ensuring continuous and uninterrupted service.
Description
Technical Field
The present invention relates to the field of cloud computing and communication technologies, and in particular, to a network element topology changing method, device, system, electronic device, and storage medium.
Background
Currently, cloud technology has penetrated into various scenarios of internet technology (Internet Technology, IT), communication technology (Communication Technology, CT) technology.
In the CT scene, great benefits are brought to operations such as operation and maintenance, upgrading and changing of the base station and the core network.
However, the configuration change of the network element of the core network is realized in a reestablishing manner, and this manner may cause service interruption of the core network.
Disclosure of Invention
The network element topology changing method, the device, the system, the electronic equipment and the storage medium are used for solving the defect that the service of the core network is interrupted due to the network element configuration change in the prior art, and realizing the automatic configuration change of the network element under the condition of ensuring the continuous and uninterrupted service.
The invention provides a network element topology changing method, which comprises the following steps:
acquiring a Pod change event by using a topology gateway component;
analyzing the Pod change event by utilizing the topology gateway component to acquire a network element micro-service Pod of a target network element;
Writing the network element micro-service Pod into a Kafka topic, wherein the Kafka topic is created based on the network element micro-service Pod;
And calling the network element microservice Pod from the Kafka topic by using a topology component so as to update the network element topology hierarchy chart of the target network element.
According to the method for changing the network element topology provided by the invention, the method for obtaining the Pod change event by using the topology gateway component comprises the following steps:
Monitoring API SERVER components by using the topology gateway components;
and under the condition that the API SERVER component is changed, acquiring the Pod change event by utilizing the topology gateway component.
According to the network element topology changing method provided by the invention, the analyzing the Pod changing event by using the topology gateway component to obtain the network element micro-service Pod of the target network element comprises the following steps:
analyzing the Pod change event by utilizing the topology gateway component to acquire a network element Pod of a target network element;
verifying the content of the annotation field of the network element Pod by utilizing the topology gateway component to obtain a first verification result;
And under the condition that the annotation field is determined to be a preset field and the first check result is qualified, determining the network element Pod as the network element micro-service Pod.
According to the method for changing the network element topology provided by the invention, the writing of the network element microservice Pod into the Kafka topic comprises the following steps:
Under the condition that the content of the annotation field is consistent with the hierarchical structure of the target network element according to the first check result, calling the topology gateway component to create the Kafka topic according to the network element micro-service Pod;
And writing the network element micro-service Pod into the Kafka topic.
According to the method for changing the network element topology provided by the invention, the network element microservice Pod is called from the Kafka topic by using a topology component so as to update the network element topology hierarchy chart of the target network element, and the method comprises the following steps:
Calling the network element microservice Pod from the Kafka topic by utilizing the topology component;
Checking the network element micro-service Pod by utilizing the topology component to acquire a second checking result;
Under the condition that the me field of the network element micro service Pod is consistent with the initial field of the target network element according to the second checking result, a network element topology hierarchy chart is created by utilizing the topology component;
the network element topology hierarchy chart is used for carrying out topology structure updating on the target network element.
According to the method for changing the network element topology provided by the invention, after the network element topology hierarchical graph is created by utilizing the topology component, the method further comprises the following steps:
querying the network element topology hierarchy map through the topology component;
and generating the topology state of the target network element according to the network element topology hierarchy chart.
The invention also provides a network element topology changing device, which comprises:
The acquisition module is used for acquiring the Pod change event by using the topology gateway component;
the analyzing module is used for analyzing the Pod change event by utilizing the topology gateway component so as to acquire a network element micro-service Pod of the target network element;
The writing module is used for writing the network element micro-service Pod into the Kafka topic, wherein the Kafka topic is created based on the network element micro-service Pod;
And the calling module is used for calling the network element microservice Pod from the Kafka topic by using a topology component so as to update the network element topology hierarchy chart of the target network element.
The invention also provides a K8s system for executing the network element topology changing method.
The invention also provides an electronic device comprising a memory, a processor and a computer program stored on the memory and running on the processor, wherein the processor implements any one of the network element topology changing methods when executing the program.
The invention also provides a non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements a network element topology change method as described in any of the above.
The invention also provides a computer program product comprising a computer program which when executed by a processor implements a network element topology change method as described in any of the above.
According to the network element topology changing method, device, system, electronic equipment and storage medium, the Pod changing event is analyzed and checked, and the Pod related to the network element is dynamically identified to update the topology structure of the network element, so that the dynamic configuration update of the network element is realized under the condition of ensuring continuous and uninterrupted service.
Drawings
In order to more clearly illustrate the invention or the technical solutions of the prior art, the following description will briefly explain the drawings used in the embodiments or the description of the prior art, and it is obvious that the drawings in the following description are some embodiments of the invention, and other drawings can be obtained according to the drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic flow chart of a network element topology changing method provided by the present invention;
Fig. 2 is a second flow chart of a network element topology changing method provided by the present invention;
Fig. 3 is a schematic structural diagram of a network element topology changing device provided by the present invention;
Fig. 4 is a schematic structural diagram of an electronic device provided by the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present invention more apparent, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings, and it is apparent that the described embodiments are some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The Kubernetes (hereinafter referred to as K8 s) system is used for managing containerized applications on a plurality of hosts in the cloud platform, is an open-source platform, and can realize functions of automatic deployment, automatic capacity expansion and maintenance and the like of a container cluster.
The K8s can realize quick deployment application, quick expansion application and seamless connection of new application functions, can save resources and can optimize the use of hardware resources.
The K8s also has multiple functions, and specifically can comprise a plurality of application loads (Pod) for cooperative work, storage system mounting, application health detection, replication of application instances, pod automatic expansion/contraction, registration and discovery, load balancing, rolling update, resource monitoring, log access, application program debugging, authentication and authorization providing and the like.
The following describes a network element topology changing method, device, system, electronic equipment and storage medium provided by the embodiments of the present invention with reference to fig. 1 to 4.
The execution main body of the network element topology changing method provided by the embodiment of the invention can be the electronic equipment or the software or the functional module or the functional entity which can realize the network element topology changing method in the electronic equipment, and the electronic equipment in the embodiment of the invention comprises but is not limited to a K8s system. The execution body is not limited to the present invention.
Fig. 1 is a flow chart of a network element topology changing method provided by the present invention, as shown in fig. 1, including but not limited to the following steps:
first, in step S1, a Pod change event is acquired by the topology gateway component.
The Pod change event may be event information generated by information change such as generation of Pod in the K8s system.
Specifically, a topology gateway component (topo-gw) component is configured to monitor API SERVER components in the K8s system, determine that an information change about a Pod occurs in the K8s system when the API SERVER component changes, and the K8s system acquires a Pod change event corresponding to the information change by using the topo-gw component.
An open-source cloud computing management platform project (OpenStack) environment is built on a physical machine, a plurality of virtual machine nodes are created in the OpenStack environment through a container cluster management (Cloud Controller Manager, CCM) component, and domain names, networks and the like are configured for each virtual machine node.
Based on a plurality of virtual machine nodes, a K8s cluster of multiple nodes is deployed to construct a K8s system, and the 3 roles of a master node, an etcd and a worker are set on the same node, so that the role unification of the master node and the worker node is realized. Wherein, the number of virtual machine nodes can be set to 3, and indexes such as central processing unit (Central Processing Unit, CPU), memory, disk and the like are consistent with kubernetesK s system.
The target network element may be a cloud primary network element of a core network of a fifth generation mobile communication technology, such as a user plane function (the User Plane Function, UPF) network element, an access and mobility management function (ACCESS AND Mobility Management Function, AMF) network element, etc., and in the subsequent embodiments of the present invention, the UPF network element is taken as an example to update a topology map, which is not considered as limiting the protection scope of the present invention.
The K8s system is provided with a UPF network element, an elastic load balancing service (Elastic Load Balance, ELB) cluster for main/standby switching, a Redis cluster, an operation and maintenance component and a public component, wherein the target network element is deployed in the K8s cluster in a Pod mode, the operation and maintenance component comprises a topology component (topo component) and a topo-gw component, and the public component comprises an etcd cluster and a Kafka cluster.
The Pod of the UPF network element internally runs a sidecar container cim configured UPF network element according to sidecar mode to connect with ELB cluster, redis cluster, etcd cluster and Kafka cluster.
The components on which the UPF network element depends include a highly reliable Redis cluster, an ELB cluster, and the like.
Further, in step S2, the topology gateway component is utilized to parse the Pod change event, so as to obtain a network element micro service Pod of the target network element.
The K8s system analyzes the acquired Pod change event by utilizing the topo-gw component, analyzes the network element Pod of the UPF network element in the Pod change event, checks the content of the annotation field by utilizing the topo-gw component under the condition that the network element Pod is determined to have the canonical animation annotation field, and can judge that the analyzed network element Pod is the network element micro-service Pod of the UPF network element under the condition that the annotation field is determined to be me, nfc, nfs or nfsi and other fields.
Further, in step S3, the network element micro-service Pod is written into a Kafka topic, which is created based on the network element micro-service Pod.
Kafka topic is created by the topo-gw component for the storage of network element microservices.
And under the condition that the content of the annotation field is checked and the network element Pod is the network element micro-service Pod of the UPF network element, if the content of the annotation field is consistent with the hierarchical structure of the target network element, the K8s system calls a topo-gw component to create a Kafka topic according to the network element micro-service Pod, and writes the network element micro-service Pod into the Kafka topic.
The network element hierarchical structure comprises four levels of network elements, network functions, network function services and network function service instances.
Further, in step S4, the network element microservice Pod is invoked from the Kafka topic by using a topology component, so as to update the network element topology hierarchy chart of the target network element.
The K8s system utilizes the topo component to call the written network element micro-service Pod from the Kafka topoic, and utilizes the topo component to check the me field of the fetched network element micro-service Pod, and when the me field of the network element micro-service Pod is consistent with vender fields of initial configuration information, the topo component is utilized to create a network element topology hierarchy chart so as to maintain a network element topology tree of the UPF network element, thereby realizing topology structure update of the target network element, and the topo component also needs to fill in an analysis related field according to the topo requirement, wherein the analysis related field can comprise the network element and various service information. The initial configuration information is configured by default when the UPF network element is deployed, and the vender field is a default field of the initial configuration information.
The network element topology layer diagram can dynamically display topology information, detect the health state of the network element, and is convenient to operate and maintain.
The K8s container management platform can also query json files of a network element topology tree of the UPF network element through an API interface exposed by the topo component, and generate a topology state of the UPF network element according to a network element topology hierarchy chart and display the topology state on a page of the K8s container management platform.
The topology state comprises a network element micro-service hierarchical relationship, a dynamic monitoring state of the network element Pod, a link state between micro-services and the like.
When the network element micro-service Pod is subjected to addition and deletion change, the network element topology tree is updated by the page of the K8s container management platform, and an alarm can be reported if an abnormality is detected, so that operation and maintenance personnel can process in time.
According to the network element topology changing method provided by the invention, the Pod changing event is analyzed and checked, and the Pod related to the network element is dynamically identified to update the topology structure of the network element, so that the dynamic configuration update of the network element is realized under the condition of ensuring continuous and uninterrupted service.
Optionally, the acquiring, by the topology gateway component, the Pod change event includes:
Monitoring API SERVER components by using the topology gateway components;
and under the condition that the API SERVER component is changed, acquiring the Pod change event by utilizing the topology gateway component.
Specifically, the K8s system monitors API SERVER the component by using the topo-gw component, and determines that information change about Pod occurs in the K8s system under the condition that API SERVER the component is changed, and the K8s system acquires a Pod change event corresponding to the information change by using the topo-gw component.
According to the network element topology changing method provided by the invention, the API SERVER components are monitored, so that the Pod changing event is obtained, and a foundation is provided for updating the network element topology structure.
Optionally, the analyzing the Pod change event by using the topology gateway component to obtain a network element micro service Pod of the target network element includes:
analyzing the Pod change event by utilizing the topology gateway component to acquire a network element Pod of a target network element;
verifying the content of the annotation field of the network element Pod by utilizing the topology gateway component to obtain a first verification result;
And under the condition that the annotation field is determined to be a preset field and the first check result is qualified, determining the network element Pod as the network element micro-service Pod.
The annotation field may be an animation annotation field of a specification, and the preset field may be fields such as me, nfc, nfs, nfsi, etc. And when the annotation field does not belong to the preset field, the first check result comprises that the network element Pod is not the network element micro-service Pod.
The K8s system analyzes the acquired Pod change event by utilizing the topo-gw component, analyzes the network element Pod of the UPF network element in the Pod change event, checks the content of the annotation field by utilizing the topo-gw component under the condition that the network element Pod is determined to have the canonical animation annotation field, and can judge the analyzed network element Pod to be the network element micro-service Pod under the condition that the annotation field is determined to be me, nfc, nfs or nfsi and other fields.
According to the network element topology changing method provided by the invention, the network element Pod is checked to determine the network element micro-service Pod, so that a foundation is provided for updating the network element topology structure.
Optionally, the writing the network element microservice Pod to Kafka topic includes:
Under the condition that the content of the annotation field is consistent with the hierarchical structure of the target network element according to the first check result, calling the topology gateway component to create the Kafka topic according to the network element micro-service Pod;
And writing the network element micro-service Pod into the Kafka topic.
The network element hierarchical structure comprises four levels of network elements, network functions, network function services and network function service instances.
If the first verification result includes that the network element Pod is the network element micro-service Pod, and if the first verification result may further include that the annotation field is consistent with the hierarchical structure of the target network element, calling a topo-gw component to create a Kafka topic according to the network element micro-service Pod, and writing the network element micro-service Pod into the Kafka topic.
According to the network element topology changing method provided by the invention, the network element microservice Pod is written into the Kafka topic by checking the post-node of the network element microservice Pod, so as to provide a foundation for updating the network element topology structure.
Optionally, the calling the network element microservice Pod from the Kafka topic by using a topology component to update a network element topology hierarchy chart of the target network element includes:
Calling the network element microservice Pod from the Kafka topic by utilizing the topology component;
Checking the network element micro-service Pod by utilizing the topology component to acquire a second checking result;
Under the condition that the me field of the network element micro service Pod is consistent with the initial field of the target network element according to the second checking result, a network element topology hierarchy chart is created by utilizing the topology component;
the network element topology hierarchy chart is used for carrying out topology structure updating on the target network element.
If the me field is consistent with vender fields of the initial configuration information, the second check result is passed, and if the me field is inconsistent with vender fields of the initial configuration information, the second check result is not passed.
The K8s system utilizes the topo component to call the written network element micro-service Pod from the Kafka topoic, and utilizes the topo component to check the me field of the fetched network element micro-service Pod, and when the me field of the network element micro-service Pod is consistent with vender fields of initial configuration information, the topo component is utilized to create a network element topology hierarchy chart so as to maintain a network element topology tree of the UPF network element and realize topology structure update of the target network element, and the topo component also needs to fill in an analysis related field according to the topo requirement, wherein the analysis related field comprises the network element and various service information. The initial configuration information is configured by default when the UPF network element is deployed, and the vender field is a default field of the initial configuration information.
The network element topology layer diagram can dynamically display topology information, detect the health state of the network element, and is convenient to operate and maintain.
According to the network element topology changing method provided by the invention, a network element topology hierarchy chart is formed aiming at the network element microservice, and the data flow direction, the data link health condition and the like between the network element microservices are tracked in a topology chart mode.
Optionally, after the creating a network element topology level graph by using the topology component, the method further includes:
querying the network element topology hierarchy map through the topology component;
and generating the topology state of the target network element according to the network element topology hierarchy chart.
The topology state comprises a network element micro-service hierarchical relationship, a dynamic monitoring state of the network element Pod, a link state between micro-services and the like.
The K8s container management platform can also query json files of a network element topology tree of the UPF network element through an API interface exposed by the topo component, and generates network element microservice hierarchical relations of the UPF network element, dynamic monitoring states of the network element Pod, link states among microservices and the like according to the network element topology hierarchical diagram and displays the network element microservices hierarchical relations, the dynamic monitoring states of the network element Pod, the link states among microservices and the like on a page of the K8s container management platform.
When the network element micro-service Pod is subjected to addition and deletion change, the network element topology tree is updated by the page of the K8s container management platform, and an alarm can be reported if an abnormality is detected, so that operation and maintenance personnel can process in time.
According to the network element topology changing method provided by the invention, the running state of the network element can be perceived dynamically through the topology state, and whether the network element is on-line or off-line is checked. And the topology relation of other components on which the network element itself depends, and the data flow direction. And observing whether the operation logic of the network element is normal or not through the whole topological relation, and judging whether the data flow direction is normal or not according to the data flow direction relation of each component of the network element, and whether the request response among each component is normal or not.
Fig. 2 is a second flow chart of a network element topology changing method provided by the present invention, as shown in fig. 2, including:
Step1, preparing a physical machine environment, and deploying a multi-node high-availability OpenStack environment;
step 2, creating 3 virtual machine nodes based on an OpenStack environment, configuring domain names, networks and the like for each virtual machine node, and deploying K8s clusters on the 3 virtual machine nodes;
step 3, deploying components such as UPF network elements, ELB, redis, topo, topo-gw, etcd, kafka and the like by a K8s system
Step 4, operating a cim side car container in the UPF network element;
step 5, the topo-gw component monitors API SERVER to obtain a Pod change event;
Step 6, analyzing whether the Pod change event has an animation field of the UPF network element to obtain a network element Pod of the UPF network element;
step 7, checking Pod, checking up to be qualified, and serving Pod for network element micro-service;
step 8, creating Kafka topic, and putting the network element micro-service Pod into the Kafka topic;
Step 9, inquiring the network element micro service Pod and checking the me field;
step 10, creating a network element topology hierarchical graph and maintaining a network element topology tree;
step 11, filling in the relevant field of the section, including network elements and various service information;
And step 12, inquiring the network element topology tree by the K8s system, dynamically displaying the addition and deletion changes of the network element service, and displaying the health state of the network element service in real time.
The network element topology changing device provided by the invention is described below, and the network element topology changing device described below and the network element topology changing method described above can be referred to correspondingly.
Fig. 3 is a schematic structural diagram of a network element topology changing device provided by the present invention, as shown in fig. 3, including:
An obtaining module 301, configured to obtain a Pod change event by using a topology gateway component;
The parsing module 302 is configured to parse the Pod change event by using the topology gateway component, so as to obtain a network element microservice Pod of the target network element;
A writing module 303, configured to write the network element micro service Pod into a Kafka topic, where the Kafka topic is created based on the network element micro service Pod;
and a retrieving module 304, configured to retrieve the network element microservice Pod from the Kafka topic by using a topology component, so as to update a network element topology hierarchy chart of the target network element.
First, the acquisition module 301 acquires the Pod change event using the topology gateway component.
The Pod change event may be event information generated by information change such as generation of Pod in the K8s system.
Specifically, a topology gateway component (topo-gw) component is configured to monitor API SERVER components in the K8s system, determine that an information change about a Pod occurs in the K8s system when the API SERVER component changes, and the K8s system acquires a Pod change event corresponding to the information change by using the topo-gw component.
An open-source cloud computing management platform project (OpenStack) environment is built on a physical machine, a plurality of virtual machine nodes are created in the OpenStack environment through a container cluster management (Cloud Controller Manager, CCM) component, and domain names, networks and the like are configured for each virtual machine node.
Based on a plurality of virtual machine nodes, a K8s cluster of multiple nodes is deployed to construct a K8s system, and the 3 roles of a master node, an etcd and a worker are set on the same node, so that the role unification of the master node and the worker node is realized. The number of virtual machine nodes can be 3, and the indexes of CPU, memory, disk and the like are consistent with those of kubernetesK s.
The target network element may be a cloud primary network element of a core network of a fifth generation mobile communication technology, such as a user plane function (the User Plane Function, UPF) network element, an access and mobility management function (ACCESS AND Mobility Management Function, AMF) network element, etc., and in the subsequent embodiments of the present invention, the UPF network element is taken as an example to update a topology map, which is not considered as limiting the protection scope of the present invention.
The K8s system is provided with a UPF network element, an elastic load balancing service (Elastic Load Balance, ELB) cluster for main/standby switching, a Redis cluster, an operation and maintenance component and a public component, wherein the target network element is deployed in the K8s cluster in a Pod mode, the operation and maintenance component comprises a topology component (topo component) and a topo-gw component, and the public component comprises an etcd cluster and a Kafka cluster.
The Pod of the UPF network element internally runs a sidecar container cim configured UPF network element according to sidecar mode to connect with ELB cluster, redis cluster, etcd cluster and Kafka cluster.
The components on which the UPF network element depends include a highly reliable Redis cluster, an ELB cluster, and the like.
Further, the parsing module 302 parses the Pod change event by using the topology gateway component to obtain a network element micro service Pod of the target network element.
The K8s system analyzes the acquired Pod change event by utilizing the topo-gw component, analyzes the network element Pod of the UPF network element in the Pod change event, checks the content of the annotation field by utilizing the topo-gw component under the condition that the network element Pod is determined to have the canonical animation annotation field, and can judge that the analyzed network element Pod is the network element micro-service Pod of the UPF network element under the condition that the annotation field is determined to be me, nfc, nfs or nfsi and other fields.
Further, the writing module 303 writes the network element micro service Pod into a Kafka topic, which is created based on the network element micro service Pod.
Kafka topic is created by the topo-gw component for the storage of network element microservices.
And under the condition that the content of the annotation field is checked and the network element Pod is the network element micro-service Pod of the UPF network element, if the content of the annotation field is consistent with the hierarchical structure of the target network element, the K8s system calls a topo-gw component to create a Kafka topic according to the network element micro-service Pod, and writes the network element micro-service Pod into the Kafka topic.
The network element hierarchical structure comprises four levels of network elements, network functions, network function services and network function service instances.
Further, the retrieving module 304 retrieves the network element microservice Pod from the Kafka topic by using a topology component to update the network element topology hierarchy chart of the target network element.
The K8s system utilizes the topo component to call the written network element micro-service Pod from the Kafka topoic, and utilizes the topo component to check the me field of the fetched network element micro-service Pod, and when the me field of the network element micro-service Pod is consistent with vender fields of initial configuration information, the topo component is utilized to create a network element topology hierarchy chart so as to maintain a network element topology tree of the UPF network element, thereby realizing topology structure update of the target network element, and the topo component also needs to fill in an analysis related field according to the topo requirement, wherein the analysis related field can comprise the network element and various service information. The initial configuration information is configured by default when the UPF network element is deployed, and the vender field is a default field of the initial configuration information.
The network element topology layer diagram can dynamically display topology information, detect the health state of the network element, and is convenient to operate and maintain.
The K8s container management platform can also query json files of a network element topology tree of the UPF network element through an API interface exposed by the topo component, and generate a topology state of the UPF network element according to a network element topology hierarchy chart and display the topology state on a page of the K8s container management platform.
The topology state comprises a network element micro-service hierarchical relationship, a dynamic monitoring state of the network element Pod, a link state between micro-services and the like.
When the network element micro-service Pod is subjected to addition and deletion change, the network element topology tree is updated by the page of the K8s container management platform, and an alarm can be reported if an abnormality is detected, so that operation and maintenance personnel can process in time.
The network element topology changing device provided by the invention dynamically identifies the relevant Pod of the network element by analyzing and checking the Pod changing event so as to update the topology structure of the network element, thereby realizing the dynamic configuration update of the network element under the condition of ensuring continuous and uninterrupted service.
The invention also provides a K8s system which can execute the network element topology changing method provided by the methods, and the method specifically comprises the following steps:
First, the K8s system obtains the Pod change event using the topology gateway component.
The Pod change event may be event information generated by information change such as generation of Pod in the K8s system.
Specifically, a topology gateway component (topo-gw) component is configured to monitor API SERVER components in the K8s system, determine that an information change about a Pod occurs in the K8s system when the API SERVER component changes, and the K8s system acquires a Pod change event corresponding to the information change by using the topo-gw component.
An open-source cloud computing management platform project (OpenStack) environment is built on a physical machine, a plurality of virtual machine nodes are created in the OpenStack environment through a container cluster management (Cloud Controller Manager, CCM) component, and domain names, networks and the like are configured for each virtual machine node.
Based on a plurality of virtual machine nodes, a K8s cluster of multiple nodes is deployed to construct a K8s system, and the 3 roles of a master node, an etcd and a worker are set on the same node, so that the role unification of the master node and the worker node is realized. The number of virtual machine nodes can be 3, and the indexes of CPU, memory, disk and the like are consistent with those of kubernetesK s.
The target network element may be a cloud primary network element of a core network of a fifth generation mobile communication technology, such as a user plane function (the User Plane Function, UPF) network element, an access and mobility management function (ACCESS AND Mobility Management Function, AMF) network element, etc., and in the subsequent embodiments of the present invention, the UPF network element is taken as an example to update a topology map, which is not considered as limiting the protection scope of the present invention.
The K8s system is provided with a UPF network element, an elastic load balancing service (Elastic Load Balance, ELB) cluster for main/standby switching, a Redis cluster, an operation and maintenance component and a public component, wherein the target network element is deployed in the K8s cluster in a Pod mode, the operation and maintenance component comprises a topology component (topo component) and a topo-gw component, and the public component comprises an etcd cluster and a Kafka cluster.
The Pod of the UPF network element internally runs a sidecar container cim configured UPF network element according to sidecar mode to connect with ELB cluster, redis cluster, etcd cluster and Kafka cluster.
The components on which the UPF network element depends include a highly reliable Redis cluster, an ELB cluster, and the like.
Further, the K8s system analyzes the Pod change event by utilizing the topology gateway component to obtain the network element micro-service Pod of the target network element.
The K8s system analyzes the acquired Pod change event by utilizing the topo-gw component, analyzes the network element Pod of the UPF network element in the Pod change event, checks the content of the annotation field by utilizing the topo-gw component under the condition that the network element Pod is determined to have the canonical animation annotation field, and can judge that the analyzed network element Pod is the network element micro-service Pod of the UPF network element under the condition that the annotation field is determined to be me, nfc, nfs or nfsi and other fields.
Further, the K8s system writes the network element micro-service Pod into a Kafka topic, wherein the Kafka topic is created based on the network element micro-service Pod.
Kafka topic is created by the topo-gw component for the storage of network element microservices.
And under the condition that the content of the annotation field is checked and the network element Pod is the network element micro-service Pod of the UPF network element, if the content of the annotation field is consistent with the hierarchical structure of the target network element, the K8s system calls a topo-gw component to create a Kafka topic according to the network element micro-service Pod, and writes the network element micro-service Pod into the Kafka topic.
The network element hierarchical structure comprises four levels of network elements, network functions, network function services and network function service instances.
Further, the K8s system utilizes a topology component to call the network element microservice Pod from the Kafka topic so as to update the network element topology hierarchy chart of the target network element.
The K8s system utilizes the topo component to call the written network element micro-service Pod from the Kafka topoic, and utilizes the topo component to check the me field of the fetched network element micro-service Pod, and when the me field of the network element micro-service Pod is consistent with vender fields of initial configuration information, the topo component is utilized to create a network element topology hierarchy chart so as to maintain a network element topology tree of the UPF network element, thereby realizing topology structure update of the target network element, and the topo component also needs to fill in an analysis related field according to the topo requirement, wherein the analysis related field can comprise the network element and various service information. The initial configuration information is configured by default when the UPF network element is deployed, and the vender field is a default field of the initial configuration information.
The network element topology layer diagram can dynamically display topology information, detect the health state of the network element, and is convenient to operate and maintain.
The K8s container management platform can also query json files of a network element topology tree of the UPF network element through an API interface exposed by the topo component, and generate a topology state of the UPF network element according to a network element topology hierarchy chart and display the topology state on a page of the K8s container management platform.
The topology state comprises a network element micro-service hierarchical relationship, a dynamic monitoring state of the network element Pod, a link state between micro-services and the like.
When the network element micro-service Pod is subjected to addition and deletion change, the network element topology tree is updated by the page of the K8s container management platform, and an alarm can be reported if an abnormality is detected, so that operation and maintenance personnel can process in time.
The K8s system provided by the invention dynamically identifies the relevant Pod of the network element by analyzing and checking the Pod change event so as to update the topology structure of the network element, thereby realizing the dynamic configuration update of the network element under the condition of ensuring continuous and uninterrupted service.
Fig. 4 is a schematic structural diagram of an electronic device according to the present invention, as shown in fig. 4, the electronic device may include a processor (processor) 410, a communication interface (Communications Interface) 420, a memory (memory) 430, and a communication bus 440, where the processor 410, the communication interface 420, and the memory 430 perform communication with each other through the communication bus 440. The processor 410 may invoke logic instructions in the memory 430 to perform a network element topology change method including obtaining a Pod change event with a topology gateway component, parsing the Pod change event with the topology gateway component to obtain a network element micro service Pod of a target network element, writing the network element micro service Pod into a Kafka topic created based on the network element micro service Pod, and invoking the network element micro service Pod from the Kafka topic with a topology component to update a network element topology hierarchy map of the target network element.
Further, the logic instructions in the memory 430 described above may be implemented in the form of software functional units and may be stored in a computer-readable storage medium when sold or used as a stand-alone product. Based on this understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention. The storage medium includes a U disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, an optical disk, or other various media capable of storing program codes.
In another aspect, the invention further provides a computer program product, the computer program product comprises a computer program, the computer program can be stored on a non-transitory computer readable storage medium, when the computer program is executed by a processor, the computer program can execute the network element topology changing method provided by the method, the method comprises the steps of acquiring a Pod changing event by using a topology gateway component, analyzing the Pod changing event by using the topology gateway component to acquire a network element micro-service Pod of a target network element, writing the network element micro-service Pod into a Kafka topic, wherein the Kafka topic is created based on the network element micro-service Pod, and calling the network element micro-service Pod from the Kafka topic by using a topology component to update a network element topology hierarchy chart of the target network element.
In yet another aspect, the present invention further provides a non-transitory computer readable storage medium, on which a computer program is stored, which when executed by a processor, is implemented to perform the network element topology changing method provided by the above methods, where the method includes obtaining a Pod change event with a topology gateway component, parsing the Pod change event with the topology gateway component to obtain a network element micro service Pod of a target network element, writing the network element micro service Pod into a Kafka topic, where the Kafka topic is created based on the network element micro service Pod, and retrieving the network element micro service Pod from the Kafka topic with a topology component to update a network element topology hierarchy map of the target network element.
The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
From the above description of the embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by means of software plus necessary general hardware platforms, or of course may be implemented by means of hardware. Based on this understanding, the foregoing technical solution may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a computer readable storage medium, such as ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in the respective embodiments or some parts of the embodiments.
It should be noted that the above-mentioned embodiments are merely for illustrating the technical solution of the present invention, and not for limiting the same, and although the present invention has been described in detail with reference to the above-mentioned embodiments, it should be understood by those skilled in the art that the technical solution described in the above-mentioned embodiments may be modified or some technical features may be equivalently replaced, and these modifications or substitutions do not make the essence of the corresponding technical solution deviate from the spirit and scope of the technical solution of the embodiments of the present invention.
Claims (9)
1. A method for changing a topology of a network element, comprising:
acquiring a Pod change event by using a topology gateway component;
analyzing the Pod change event by utilizing the topology gateway component to acquire a network element micro-service Pod of a target network element;
Writing the network element micro-service Pod into a Kafka topic, wherein the Kafka topic is created based on the network element micro-service Pod;
the network element microservice Pod is called from the Kafka topic by utilizing a topology component so as to update a network element topology hierarchy chart of the target network element;
The analyzing the Pod change event by using the topology gateway component to obtain the network element micro service Pod of the target network element includes:
analyzing the Pod change event by utilizing the topology gateway component to acquire a network element Pod of a target network element;
verifying the content of the annotation field of the network element Pod by utilizing the topology gateway component to obtain a first verification result;
And under the condition that the annotation field is determined to be a preset field and the first check result is qualified, determining the network element Pod as the network element micro-service Pod.
2. The network element topology altering method of claim 1, wherein said obtaining a Pod altering event with a topology gateway component comprises:
Monitoring API SERVER components by using the topology gateway components;
and under the condition that the API SERVER component is changed, acquiring the Pod change event by utilizing the topology gateway component.
3. The network element topology changing method of claim 1, wherein said writing the network element microservice Pod to Kafka topic comprises:
Under the condition that the content of the annotation field is consistent with the hierarchical structure of the target network element according to the first check result, calling the topology gateway component to create the Kafka topic according to the network element micro-service Pod;
And writing the network element micro-service Pod into the Kafka topic.
4. A method of changing a network element topology according to any of claims 1-3, wherein said invoking the network element microservice Pod from the Kafka topic by means of a topology component to update a network element topology hierarchy map of the target network element comprises:
Calling the network element microservice Pod from the Kafka topic by utilizing the topology component;
Checking the network element micro-service Pod by utilizing the topology component to acquire a second checking result;
Under the condition that the me field of the network element micro service Pod is consistent with the initial field of the target network element according to the second checking result, a network element topology hierarchy chart is created by utilizing the topology component;
the network element topology hierarchy chart is used for carrying out topology structure updating on the target network element.
5. The network element topology altering method of claim 4, further comprising, after said creating a network element topology hierarchy map with said topology component:
querying the network element topology hierarchy map through the topology component;
and generating the topology state of the target network element according to the network element topology hierarchy chart.
6. A network element topology changing apparatus, comprising:
The acquisition module is used for acquiring the Pod change event by using the topology gateway component;
the analyzing module is used for analyzing the Pod change event by utilizing the topology gateway component so as to acquire a network element micro-service Pod of the target network element;
The writing module is used for writing the network element micro-service Pod into the Kafka topic, wherein the Kafka topic is created based on the network element micro-service Pod;
a calling module, configured to call the network element microservice Pod from the Kafka topic by using a topology component, so as to update a network element topology hierarchy chart of the target network element;
The analyzing module is further configured to analyze the Pod change event by using the topology gateway component to obtain a network element Pod of the target network element, check the content of an annotation field of the network element Pod by using the topology gateway component to obtain a first check result, and determine that the network element Pod is the network element microservice Pod when the annotation field is determined to be a preset field and the first check result is determined to be qualified.
7. The K8s system is characterized by comprising a UPF network element, a main-standby switched elastic load balancing service cluster, a Redis cluster, an operation and maintenance component and a public component, wherein the operation and maintenance component comprises a topology component and a topology gateway component, the public component comprises an etcd cluster and a Kafka cluster, and the K8s system is used for executing the network element topology changing method according to any one of claims 1-5 based on the UPF network element, the main-standby switched elastic load balancing service cluster, the Redis cluster, the operation and maintenance component and the public component.
8. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the network element topology change method according to any of the claims 1-5 when executing the program.
9. A non-transitory computer readable storage medium having stored thereon a computer program, which when executed by a processor implements the network element topology change method of any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211056891.3A CN115550187B (en) | 2022-08-31 | 2022-08-31 | Network element topology change method, device, system, electronic device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211056891.3A CN115550187B (en) | 2022-08-31 | 2022-08-31 | Network element topology change method, device, system, electronic device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115550187A CN115550187A (en) | 2022-12-30 |
| CN115550187B true CN115550187B (en) | 2025-06-27 |
Family
ID=84726413
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211056891.3A Active CN115550187B (en) | 2022-08-31 | 2022-08-31 | Network element topology change method, device, system, electronic device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115550187B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117278401A (en) * | 2023-08-03 | 2023-12-22 | 中国电信股份有限公司技术创新中心 | Configuration updating method and device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111258609A (en) * | 2020-01-19 | 2020-06-09 | 北京百度网讯科技有限公司 | Upgrading method and device of Kubernetes cluster, electronic equipment and medium |
| CN113010385A (en) * | 2021-03-18 | 2021-06-22 | 山东英信计算机技术有限公司 | Task state updating method, device, equipment and medium |
| CN114143203A (en) * | 2021-11-05 | 2022-03-04 | 华东师范大学 | Kubernetes container network data packet index acquisition method and system based on dynamic service topological mapping |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110198231B (en) * | 2018-05-08 | 2022-02-25 | 腾讯科技（深圳）有限公司 | Container network management method and system for multiple tenants and middleware |
| CN113821268B (en) * | 2020-06-18 | 2024-06-04 | 复旦大学 | A Kubernetes network plugin method integrated with OpenStack Neutron |
| CN112866333B (en) * | 2020-12-28 | 2023-03-24 | 上海领健信息技术有限公司 | Cloud-native-based micro-service scene optimization method, system, device and medium |
-
2022
- 2022-08-31 CN CN202211056891.3A patent/CN115550187B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111258609A (en) * | 2020-01-19 | 2020-06-09 | 北京百度网讯科技有限公司 | Upgrading method and device of Kubernetes cluster, electronic equipment and medium |
| CN113010385A (en) * | 2021-03-18 | 2021-06-22 | 山东英信计算机技术有限公司 | Task state updating method, device, equipment and medium |
| CN114143203A (en) * | 2021-11-05 | 2022-03-04 | 华东师范大学 | Kubernetes container network data packet index acquisition method and system based on dynamic service topological mapping |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115550187A (en) | 2022-12-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10680896B2 (en) | Virtualized network function monitoring | |
| CN108173911B (en) | Microservice fault detection and processing method and device | |
| US10419553B2 (en) | Dynamic docker pool recycling | |
| Brandón et al. | Fmone: A flexible monitoring solution at the edge | |
| CN105556499A (en) | Intelligent auto-scaling | |
| CN111901421B (en) | A data processing method and related equipment | |
| WO2016150153A1 (en) | Software release method and device | |
| CN106936659B (en) | Public cloud dial testing method and device | |
| Dadashi Gavaber et al. | BADEP: bandwidth and delay efficient application placement in fog‐based IoT systems | |
| CN114938396A (en) | Routing method of service call request, method and device for creating service | |
| CN113419818B (en) | Basic component deployment method, device, server and storage medium | |
| CN116781564B (en) | Network detection method, system, medium and electronic equipment of container cloud platform | |
| CN114679380A (en) | Method and related device for creating edge cluster | |
| CN115103007A (en) | Distributed cloud-based service discovery method, device and readable storage medium | |
| CN115550187B (en) | Network element topology change method, device, system, electronic device and storage medium | |
| CN116192885A (en) | High-availability cluster architecture artificial intelligence experiment cloud platform data processing method and system | |
| CN106060048A (en) | Network resource access method and network resource access device | |
| CN108089968A (en) | Method for monitoring state of database of virtual machine by host machine | |
| CN118747147A (en) | Application system high availability evaluation method, device, equipment and medium | |
| CN109274533B (en) | Web service fault positioning device and method based on rule engine | |
| US12423297B2 (en) | Monitoring metadata synchronization and aggregation | |
| CN116860654A (en) | Operation and maintenance configuration data modeling method, device, equipment and storage medium | |
| CN115550170A (en) | Network element configuration changing method, device, system, electronic equipment and storage medium | |
| US9137121B1 (en) | Managing networks utilizing network simulation | |
| CN115221059A (en) | System fault tolerance test method, electronic device, storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |