Network element automatic deployment method, private network system, device, equipment and storage medium

Abstract

The embodiment of the invention discloses a network element automatic deployment method, a private network system, a device, equipment and a storage medium, and the method is applied to an MEC server, and comprises the steps: determining a to-be-deployed target network element through detecting container instances of a plurality of network elements in a core network; wherein the container instances of the plurality of network elements are deployed in the MEC server based on a containerization technology; determining a target available IP address of the target network element; configuring an interface address parameter of the target network element based on the dependency relationship among the plurality of network elements and the target available IP address; and creating a container instance of the target network element based on the interface address parameter.

Description

Technical Field

[0001] The present application relates to but is not limited to the field of network system deployment, and in particular to a network element automatic deployment method, a private network system, a device, equipment and a storage medium. Background Art

[0002] At present, the existing core network systems in the industry built based on containerization technology use container technologies such as Docker to implement network element resource scheduling. There is no solution for automatic deployment of core network elements of the fifth generation mobile communication technology (5th Generation Mobile Communication Technology, 5G) using containerization technology. Summary of the invention

[0003] In view of this, the embodiments of the present application provide at least a network element automatic deployment method, a private network system, a device, a equipment and a storage medium.

[0004] The technical solution of the embodiment of the present application is implemented as follows:

[0005] In a first aspect, an embodiment of the present application provides a method for automatic deployment of network elements, which is applied to an MEC server, and the method includes:

[0006] By detecting container instances of multiple network elements in the core network, the target network element to be deployed is determined; wherein the container instances of the multiple network elements are deployed in the MEC server based on containerization technology; the target available IP address of the target network element is determined; based on the dependency relationship between the multiple network elements and the target available IP address, the interface address parameters of the target network element are configured; based on the interface address parameters, the container instance of the target network element is created.

[0007] In a second aspect, an embodiment of the present application provides a private network system, including: a base station and a MEC server, wherein:

[0008] The base station is used to establish a network connection with the MEC server;

[0009] The MEC server is used to determine the target network element to be deployed by detecting container instances of multiple network elements in the core network; wherein the container instances of the multiple network elements are deployed in the MEC server based on containerization technology; determine the target available IP address of the target network element; configure the interface address parameters of the target network element based on the dependency relationship between the multiple network elements and the target available IP address; and create the container instance of the target network element based on the interface address parameters.

[0010] In a third aspect, an embodiment of the present application provides a network element automatic deployment device, which is applied to a MEC server, including:

[0011] A system monitoring module, used to determine the target network element to be deployed by detecting the container instances of multiple network elements in the core network; wherein the container instances of the multiple network elements are deployed in the MEC server based on containerization technology;

[0012] An address analysis module, used to determine a target available IP address of the target network element;

[0013] A parameter configuration module, configured to configure the interface address parameters of the target network element based on the dependency relationship between the multiple network elements and the target available IP address;

[0014] The container creation module is used to create a container instance of the target network element based on the interface address parameter.

[0015] In a fourth aspect, an embodiment of the present application provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program executable on the processor, and when the processor executes the program, the steps in the method of the first aspect are implemented.

[0016] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps in the method of the first aspect described above.

[0017] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory, and are not intended to limit the technical solutions of the present disclosure.

[0018] The embodiments of the present application have at least the following technical effects:

[0019] In an embodiment of the present application, first, by detecting container instances of multiple network elements in the core network, the target network element to be deployed is determined; then the target available IP address of the target network element is determined; then, based on the dependency relationship between the multiple network elements and the target available IP address, the interface address parameters of the target network element are configured; finally, based on the interface address parameters, a container instance of the target network element is created; in this way, through the analysis and calculation of IP addresses, unified planning and dynamic setting of interface address parameters of 5G core network network elements can be achieved, so that automatic deployment of network elements can be achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The drawings herein are incorporated into the specification and constitute a part of the specification. These drawings illustrate embodiments consistent with the present application and are used together with the specification to illustrate the technical solution of the present application.

[0021] Figure 1 An optional flow chart of the network element automatic deployment method provided in the embodiment of the present application;

[0022] Figure 2 An optional flow chart of the network element automatic deployment method provided in the embodiment of the present application;

[0023] Figure 3 An optional flow chart of the network element automatic deployment method provided in the embodiment of the present application;

[0024] Figure 4 An optional flow chart of the network element automatic deployment method provided in the embodiment of the present application;

[0025] Figure 5 A schematic diagram of the system framework of the private network system provided in the embodiment of the present application;

[0026] Figure 6 A schematic diagram of deployment components in a MEC server provided in an embodiment of the present application;

[0027] Figure 7 A schematic diagram of the relationship between components in the MEC server provided in an embodiment of the present application;

[0028] Figure 8 A schematic diagram of the deployment distribution of containerized core network elements in K8s components provided in an embodiment of the present application;

[0029] Fig. 9 A logical flow chart of the network element automatic deployment method provided in the embodiment of the present application;

[0030] Fig.10 A schematic diagram of an abnormality diagnosis process provided in an embodiment of the present application;

[0031] Fig.11 A schematic diagram of the intelligent expansion and contraction process provided in an embodiment of the present application;

[0032] Fig.12 A schematic diagram of the structure of a network element automatic deployment device provided in an embodiment of the present application;

[0033] Fig.13 A hardware entity diagram of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0034] In order to make the purpose, technical solutions and advantages of the present application clearer, the technical solutions of the present application are further elaborated in detail below in conjunction with the drawings and embodiments. The described embodiments should not be regarded as limiting the present application. All other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application.

[0035] In the following description, reference is made to “some embodiments”, which describe a subset of all possible embodiments, but it will be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0036] The terms "first / second / third" involved are merely used to distinguish similar objects and do not represent a specific ordering of the objects. It is understandable that "first / second / third" can be interchanged with a specific order or sequence where permitted so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein.

[0037] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing this application and are not intended to limit this application.

[0038] Before further describing the embodiments of the present application in detail, the nouns and terms involved in the embodiments of the present application are described first. The nouns and terms involved in the embodiments of the present application are subject to the following interpretations.

[0039] Core network: Its main function is to provide user connection, user management and service bearing, and to provide an interface to the external network as a bearer network.

[0040] Base station: also known as a shared mobile communication base station, is an interface device for mobile devices to access the Internet. It is also a form of radio station. It refers to a radio transceiver station that transmits information between mobile devices through a mobile communication exchange center within a certain radio coverage area.

[0041] Network element: It is composed of one or more disks or frames and can independently complete certain transmission functions. 5GC (5G Core Network) is mainly composed of the following network elements: AMF (Access and Mobility Management Function), AUSF (Authentication Server Function), SMF (Session Management Function), UPF (User Plane Function), UDM (Unified Data Management), PCF (Policy Control Function), etc., but not limited to these.

[0042] Kubernetes container orchestration tool: abbreviated as K8s, is an open source container orchestration system used to manage containerized applications on multiple hosts in a cloud platform.

[0043] Docker is an open source application container engine. Developers can package their applications and dependencies in a portable container and publish them to popular Linux machines. They can also achieve virtualization. Dockers is a containerization technology. K8S is a set of automated deployment tools that can manage Dockers containers throughout their life cycle.

[0044] MEC, short for Mobile Edge Computing, is a product of ICT integration and a key technology to support operators in their 5G network transformation to meet the development needs of high-definition video, virtual reality / augmented reality (VR / AR), industrial Internet, and Internet of Vehicles.

[0045] A physical server refers to an independent server, that is, a physically separate server. The structure of a physical server includes a processor, hard disk, memory, system bus, etc., which is similar to the general computer architecture. However, due to the need to provide highly reliable services, it has higher requirements in terms of processing power, stability, reliability, security, scalability, manageability, etc.

[0046] The embodiment of the present application provides a method for automatic deployment of network elements, which is applied to an MEC server, wherein the MEC server may include but is not limited to a processor, a hard disk, a memory, a system bus, etc. Figure 1 An optional flow chart of the network element automatic deployment method provided in the embodiment of the present application, such as Figure 1 As shown, the method includes the following steps S110 to S140:

[0047] Step S110 , determining a target network element to be deployed by detecting container instances of multiple network elements in the core network.

[0048] Here, the container instances of the multiple network elements are deployed in the MEC server based on containerization technology, where the container instance refers to a program running based on the container image of the network element. In implementation, the containerization deployment technology can be used to build a container cluster. For example, multiple network elements of the core network can be deployed in the same Kubernetes cluster, and different network elements can be deployed on different nodes, but it is not limited to this.

[0049] Among them, multiple network elements can be devices in the core network that provide network services to the outside. In this application, the 5G core network is used as an example for explanation. Multiple network elements can be AMF, SMF, UPF and UDM, but it is not limited to this. It can also be other network elements of the 5G core network. The above multiple network elements need to cooperate with each other to provide users with complete 5G core network services. Therefore, the embodiment of the present application first detects whether each network element container instance exists, and takes at least one network element with a missing container instance as the target network element to be deployed. In some embodiments, it is detected that only one network element in the core network does not have a container instance, and the network element is directly deployed as the target network element; in some embodiments, it is detected that there are multiple network elements in the core network that lack container instances, then these multiple network elements are all used as target network elements to be deployed, and multiple target network elements can be deployed simultaneously, or one of the multiple target network elements can be randomly selected in sequence for deployment until all target network elements have created container instances. The embodiment of the present application does not limit the deployment order of different target network elements.

[0050] It is worth noting that after the container instances of each network element of the core network are automatically deployed for the first time, the dependencies between the network elements have been stored and the interface address parameters of each network element have been determined. In the subsequent detection process, if at least one target network element is missing from the container instance, the stored interface address parameters of each target network element can be directly obtained for configuration without being restricted by the dependency relationship. Therefore, the target network element can be randomly selected to be deployed first.

[0051] Step S120: determining a target available IP address of the target network element.

[0052] Here, the target available IP address is at least one idle available IP address. In implementation, the available IP segments in the current network environment can be first obtained, and then the occupied or allocated IP addresses are removed to obtain at least one idle IP address, and then one or more addresses are randomly selected from the at least one IP address as the target available IP address of the target network element. It should be noted that each creation of a container instance requires an IP address, and the number of target available IP addresses is selected according to the number of container instances to be created.

[0053] In some embodiments, the target available IP address of the target network element can be determined by the following steps: obtaining an IP address segment of a target environment; wherein the target environment is a container operating environment of the multiple network elements; determining a used IP address in the target environment; wherein the used IP address includes an address where a started container instance is running; determining an allocated IP address configured for a container instance to be started of other network elements; wherein the other network elements are network elements other than the target network element in the target environment; the allocated IP address includes a predefined address that is allocated but not running in response to a container startup request of the other network element; and determining the target available IP address of the target network element based on the IP address segment, the used IP address, and the allocated IP address.

[0054] Here, the target environment is understood to be the environment in which the container instances of each network element actually run, such as the nodes in the K8S component. Correspondingly, the IP address segment of the target environment, that is, the IP segment that can be used by the current network, is determined by extracting the service-cidr and pod-network-cidr parameter values ​​of the K8s components.

[0055] It should be noted that the allocated IP address is generally stored locally through a software program. Before other network elements apply for IP addresses but do not start container instances, the allocated IP address needs to be temporarily stored. The network IP parameter information configured when creating the corresponding container instance is the allocated IP address. When deploying the target network element, there may be predefined addresses for other network elements other than the target network element that have applied for IP addresses but have not started container instances. Therefore, in order to determine the target available IP address of the target network element, it is necessary to remove the IP addresses occupied by existing container instances and the predefined addresses that have been allocated but not yet occupied from the target environment. In this way, it can be ensured that the target network element is allocated with an available IP address without causing abnormal operation of other network element container instances.

[0056] Step S130: configuring the interface address parameters of the target network element based on the dependency relationship between the multiple network elements and the target available IP address.

[0057] Here, the dependency relationships among multiple network elements are determined through the system architecture of the core network. For example, the AMF network element mainly depends on the AUSF, UDM, and SMF network elements; the UDM mainly depends on the AUSF, AMF, and SMF network elements, etc.

[0058] The interface address parameter is the network IP parameter information of the target network element, including the IP address of the target network element itself and the IP address of the external interface. In implementation, based on the dependency relationship, the IP address of the container instance of the dependent network element connected to the target network element is detected and obtained, and combined with the target available IP address calculated in the previous step, the parameter configuration of the target network element is completed.

[0059] Step S140: Create a container instance of the target network element based on the interface address parameters.

[0060] Here, the interface address parameters set in the previous step are used to generate corresponding control instructions, initiate a container instance creation request, and start the container instance of the target network element in the MEC server, thereby completing the automatic deployment of the target network element.

[0061] In an embodiment of the present application, first, by detecting container instances of multiple network elements in the core network, the target network element to be deployed is determined; then the target available IP address of the target network element is determined; then, based on the dependency relationship between the multiple network elements and the target available IP address, the interface address parameters of the target network element are configured; finally, based on the interface address parameters, a container instance of the target network element is created; in this way, through the analysis and calculation of IP addresses, unified planning and dynamic setting of interface address parameters of 5G core network network elements can be achieved, so that automatic deployment of network elements can be achieved.

[0062] In some implementations, the interface address parameter includes the IP address of the target network element and the IP address of the external interface. Figure 1 , Figure 2 An optional flow chart of the network element automatic deployment method provided in the embodiment of the present application, such as Figure 2 As shown, the above step S130 "configuring the interface address parameters of the target network element based on the dependency relationship between the multiple network elements and the target available IP address" includes the following steps S210 to S240:

[0063] Step S210: determining a dependent network element connected to an external interface of the target network element based on the dependency relationship between the multiple network elements.

[0064] Here, the dependency relationship between the multiple network elements can be determined through the system architecture of the 5G core network. For example, the UPF network element mainly depends on the SMF network element; the AUSF network element mainly depends on the AMF and UDM network elements; the PCF network element mainly depends on the SMF and AMF network elements.

[0065] Step S220: When a container instance of the dependent network element exists or an allocated IP address of the dependent network element exists, determine the IP address of the external interface based on the container instance IP address of the dependent network element or the allocated IP address of the dependent network element.

[0066] Here, the container instance IP address represents the IP address of the container instance actually running after the dependent network element has completed the creation of the container instance, and the allocated IP address represents the IP address to be allocated to the network element container before the container instance is started.

[0067] In some implementations, when a container instance of a dependent network element exists, the IP address of the container instance is directly used as the IP address of the external interface of the target network element; in some implementations, when an allocated IP address of the dependent network element exists, the allocated IP address is used as the IP address of the external interface of the target network element.

[0068] Step S230: configuring the interface address parameters of the target network element based on the target available IP address and the IP address of the external interface.

[0069] Here, the target available IP address and the IP address of the external interface are set as the IP parameters of the target network element to complete the configuration of the interface address parameters.

[0070] Step S240: When the container instance of the dependent network element does not exist and the allocated IP address of the dependent network element does not exist, the dependent network element is used as a new target network element, and a container instance of the new target network element is preferentially created.

[0071] Here, when the container instance of the dependent network element does not exist and the allocated IP address of the dependent network element does not exist, the calculation of the IP address of the dependent network element and the subsequent creation of the container instance are initiated.

[0072] It should be noted that the container instance of the target network element can only be started when the container instance of the dependent network element is started first. If the container instance of the dependent network element does not exist and the allocated IP address of the dependent network element does not exist, it is necessary to create a container instance with the dependent network element as the new target network element. After the container instance of the dependent network element is started, the original target network element continues to perform subsequent operations.

[0073] In the embodiment of the present application, by analyzing and calculating the IP address, combined with the dependency relationship between multiple network elements, unified planning and dynamic setting of the interface address parameters of the target network element to be deployed in the 5G core network can realize the automatic deployment of the target network element. In this way, the core network network element deployment can realize the automatic calculation and setting of parameter configuration information without the need for prior planning and preset.

[0074] In some implementations, after the core network elements are deployed, it is necessary to monitor the network element IP and service port in real time to identify abnormal network elements and quickly restart the container instance. Figure 3 An optional flow chart of the network element automatic deployment method provided in the embodiment of the present application, such as Figure 3 As shown, the method further includes the following steps S310 to S330:

[0075] Step S310: monitor the status of the interactive service interfaces between the multiple network elements in real time.

[0076] Here, the interactive service interfaces of the multiple network elements are uniformly defined based on the 5G core network architecture, including the IP address and service port of each network element. For example, for the AMF network element, the interactive service interface includes N1, N2, N8, N11, N12, N14, and N22, and for the UDM network element, the interactive service interface includes N8, N10, and N13.

[0077] The status of the interactive service interface is understood as whether the IP address of the network element is used normally and whether the service corresponding to the service port of the network element is reachable. In implementation, you can periodically ping each network element IP address and telnet each network element service port to check whether the service corresponding to each service port is reachable.

[0078] Step S320: When it is detected that the service corresponding to the first service port is unreachable, determine that the network element corresponding to the first service port is an abnormal network element.

[0079] Here, unreachable services are determined through detection, and then abnormal network elements are determined based on a uniformly defined interactive service interface.

[0080] Step S330: restart the container instance of the abnormal network element.

[0081] Here, based on the abnormal network elements calculated in the previous step, a K8S component control instruction is generated to initiate a container instance restart request.

[0082] In the embodiment of the present application, the IP address and service port of each network element are monitored and analyzed in real time, the status of its service interface is determined, and the abnormal network element is triggered to restart quickly, thereby minimizing the service interruption time and improving user perception.

[0083] In some implementations, after the core network elements are deployed, dynamic expansion and contraction may be performed to improve resource utilization. Figure 4 An optional flow chart of the network element automatic deployment method provided in the embodiment of the present application, such as Figure 4 As shown, the method further includes the following steps S410 to S430:

[0084] Step S410: Determine the load score of each network element under at least two target indicators within a preset detection period.

[0085] Here, the preset detection period can be set according to the actual business, for example, 5 minutes or 10 minutes, and the embodiment of the present application does not limit this. At least two target indicators are multi-source analysis indicators set for the load condition of the network element, including but not limited to at least two of the number of signaling items, memory occupancy, and CPU occupancy. Different target indicators correspond to different load score calculation methods.

[0086] Step S420: performing weighted summation on the load scores of the at least two target indicators based on a preset weight coefficient to determine a comprehensive score.

[0087] Here, the load scores of multiple indicators are used to weight and determine the comprehensive score to avoid distortion of judgment due to occasional fluctuations or errors in a single indicator.

[0088] Step S430: adjusting the container instance corresponding to the network element based on the comprehensive score and a preset resource deployment threshold.

[0089] Here, the resource deployment threshold includes a positive threshold and a negative threshold. When the comprehensive score is greater than the positive threshold, it indicates that the load of the network element is too much, and the container instance of the network element needs to be expanded; when the comprehensive score is less than the negative threshold, it indicates that the load of the network element is too little, and the container instance of the network element needs to be reduced.

[0090] In some implementations, when the comprehensive score is greater than the positive threshold, a new container instance is created for the network element; when the comprehensive score is less than the negative threshold and the number of container instances of the corresponding network element is greater than 1, one container instance is deleted. In this way, the conditions and algorithms for triggering the expansion and contraction of network elements are proposed, and the composite weighted score is automatically output to trigger the operation and maintenance instructions, thereby realizing the elastic expansion and contraction of 5G core network resources.

[0091] In some embodiments, when the comprehensive score is greater than the positive threshold, creating a new container instance for the network element includes: determining the current available resources of the server; and creating a new network element container instance for the network element when the available resources meet the minimum deployment resource requirements of the network element.

[0092] Here, the current available resources of the server can be determined based on the current CPU and memory usage of the server. If the available resources are sufficient, a new network element container instance is created; if capacity expansion is required but the available resources are insufficient, a resource alarm can be issued. In this way, container instances can be quickly created for network elements with too little load while ensuring the security of the corresponding services.

[0093] In the embodiment of the present application, conditions and algorithms for triggering the need for expansion or reduction of network elements are proposed, and a weighted composite of multiple indicators is used to avoid judgment distortion caused by occasional fluctuations or errors in a single indicator, thereby achieving elastic expansion or reduction of 5G core network resources.

[0094] Figure 5 The system architecture diagram of the private network system provided in the embodiment of the present application is as follows: Figure 5 As shown, the private network system includes a base station 51 and a MEC server 52, wherein:

[0095] The base station 51 is used to establish a network connection with the MEC server 52;

[0096] The MEC server 52 is used to determine the target network element to be deployed by detecting the container instances of multiple network elements in the core network; wherein the container instances of the multiple network elements are deployed in the MEC server based on containerization technology; determine the target available IP address of the target network element; configure the interface address parameters of the target network element based on the dependency relationship between the multiple network elements and the target available IP address; and create the container instance of the target network element based on the interface address parameters.

[0097] It should be noted that the base station 51 can be a commonly used base station, an evolved node base station (eNB), or a network side device in a 5G system, such as a next generation node base station (gNB) or a transmission and reception point (TRP) or a cell.

[0098] The base station 51 can provide the MEC server 52 with relevant information and user identity information of all mobile terminals in the cell, and the MEC server 52 can calculate the location of each mobile terminal. The connection between the base station 51, the MEC server 52 and the core network can be a wireless connection.

[0099] In the embodiment of the present application, the base station and the MEC server physical equipment are used to establish a network connection, realize the overall sinking of the 5G core network, and build an ultra-low latency private network system. In the MEC server, through the analysis and calculation of the IP address, the interface address parameters of the 5G core network network elements are uniformly planned and dynamically set, so as to realize the automatic deployment of the network elements.

[0100] In some embodiments, the MEC server includes an application, a container orchestration tool, and a container image repository; the container image repository is used to store the container images of each of the multiple network elements; the container orchestration tool is used to deploy the corresponding container instances for the multiple network elements respectively; the application is used to control the container orchestration tool to obtain each of the container images from the container image repository and create the container instance of the corresponding network element, and execute the steps of the network element automatic deployment method.

[0101] Here, the container orchestration tool can be a K8s component. In implementation, multiple nodes are created in the container orchestration tool to provide a container operating environment for containerized core network elements. There can be multiple container instances on a node, and different network elements can be deployed on different nodes, but this is not limited to this.

[0102] The above-mentioned network element automatic deployment method is described below in conjunction with a specific embodiment. However, it is worth noting that this specific embodiment is only for better illustrating the present application and does not constitute an improper limitation on the present application.

[0103] In the related technologies, for network element deployment, only for containerized IMS applications (including: I / S-CSCF, P-CSCF, TAS network elements), it is necessary to estimate and manually configure all network element configuration information in the database in advance. This is a "semi-automatic" mode, which is single-environment targeted and does not have the universality of transplantation, that is, it does not achieve automatic adaptation of the deployment environment and real-time calculation and allocation of parameter configuration information. For the location of network element faults and fault locations, the prerequisite for implementation is that the interface transmission data needs to be collected, that is, it is assumed that the interface access between each network element is normal, and whether the service of the network element interface is accessible is not considered, that is, the transmission data cannot be collected. For dynamic expansion and contraction of resources, the conditions that trigger the need for expansion and contraction and the specific calculation method are not given in a targeted manner, that is, why expansion and contraction are needed.

[0104] The embodiment of the present application uses a base station and an MEC server, deploys K8s components, a container image repository and applications in the server, and deploys 5GC network element images in the container image repository, so that an independent communication private network system is formed within the coverage of the base station, and the application provides automatic deployment strategies, abnormal diagnosis strategies and expansion and contraction strategies, generates K8s control instructions, and realizes 5GC intelligent operation and maintenance.

[0105] In the implementation, first prepare the physical equipment of the base station and MEC server and establish a network connection. Then deploy K8s components, container image warehouse components and application components in the MEC server. All components are deployed on the MEC server to achieve the overall sinking of the 5G core network and build an ultra-low latency private network system.

[0106] Figure 6 A schematic diagram of deployment components in a MEC server provided in an embodiment of the present application is shown in FIG. Figure 6 As shown, K8s component 61, container image repository 62 and application 63 are deployed in MEC server 52. The relationship between the components is as follows: Figure 7As shown, the K8s component 61 includes multiple nodes, namely the master node (Master Node), node 1 (Node 1), node 2 (Node 2), ..., node N (Node N), which are used to provide a container operating environment for the containerized 5GC network element. After the container image warehouse 62 component is deployed, the container image files of each network element are imported, such as AMF container image 71, UDM container image 72, UPF container image 73, AUSF container image 74, PCF container image 75, SMF container image 76, etc. The application 63 component can be set with functional modules such as a system monitoring module, a policy analysis module, a parameter setting module, and a control instruction module. Among them, the system monitoring module is used to monitor and analyze the status of the network element container instance in real time, the policy analysis module can determine the target network element to be deployed, diagnose abnormal network elements, and realize the dynamic expansion and contraction of network element resources, the parameter setting module is used to configure the interface address parameters of the network element, and the control instruction module is used to initiate container instance creation, restart, deletion and other instructions.

[0107] During implementation, after the application 63 component is deployed, the network element automatic deployment method is triggered to generate K8s component control instructions, which controls the K8s component 61 to pull the container image of the target network element from the container image repository 62 and start the container, completing the deployment of the private network system based on the containerized core network.

[0108] Figure 8 A schematic diagram of the deployment distribution of containerized core network elements in K8s components provided in an embodiment of the present application is shown in FIG. Figure 8 As shown, the K8s component pulls the container image of each network element and starts the container, and finally generates AMF service, UDM service, AUSF service, PCF service, SMF service, and UPF service. The AMF service includes two container instances, amf pod1 and amfpod2, which run on node 1 and node 2 respectively; the UDM service includes two container instances, udm pod1 and udm pod2, which run on the master node and node 1 respectively; the UPF service includes two container instances, upf pod1 and upf pod2, which run on node 2 and node 3 respectively; the AUSF service includes one container instance, ausf pod1, which runs on node 3; the PCF service and SMF service include one container instance, pcf pod1 and smf pod1, respectively, which run on node N.

[0109] Based on the private network system provided in the embodiment of the present application, Fig. 9 A logical flow chart of the network element automatic deployment method provided in the embodiment of the present application, such as Fig. 9 As shown, the steps S01 to S08 are included:

[0110] Step S01, determine the target network element 1.

[0111] Here, in the embodiment of the present application, an application is used to automatically check the K8s component network element container instance, determine the missing network elements in AMF, UDM, UPF, AUSF, PCF, and SMF, and set them as the target network elements to be deployed.

[0112] Step S02, collecting the target environment IP address segments.

[0113] Here, in the embodiment of the present application, the parameter values ​​of the K8s components service-cidr and pod-network-cidr are extracted to determine the IP segments that can be used by the network.

[0114] Step S03, calculating the target available IP address of the target network element 1.

[0115] Here, in the embodiment of the present application, the target environment IP address segment provided in step S02 is used to subtract the used IP address and the allocated IP address of the network element container in the target environment to obtain at least one idle IP address, and then one or more addresses are randomly selected from the at least one IP address as the target available IP address of the target network element. When each container instance is created, an IP address is randomly selected from the target available IP addresses for configuration. The embodiment of the present application does not limit how to select a specific IP address from the target available IP addresses.

[0116] Step S04, temporarily storing the target available IP address.

[0117] Here, in the embodiment of the present application, a database is used to save the target network element IP address calculated in step S03.

[0118] Step S05, analyzing the dependent network elements required by the target network element 1.

[0119] Here, the AMF network element in the 5G core network mainly depends on AUSF, UDM, and SMF network elements; UDM mainly depends on AUSF, AMF, and SMF network elements; UPF mainly depends on SMF network elements; AUSF mainly depends on AMF and UDM network elements; PCF mainly depends on SMF and AMF network elements; SMF mainly depends on UPF, AMF, UDM, and PCF network elements.

[0120] Step S06, determining whether a container instance of the dependent network element exists or whether an allocated IP address of the dependent network element exists.

[0121] Here, in the embodiment of the present application, according to the dependency result analyzed in step S05, the K8s component checks whether the dependent network element container instance exists, or checks whether the allocated IP address of the dependent network element exists. If not, the IP address calculation of the dependent network element and subsequent container creation are initiated.

[0122] like Fig. 9 As shown, if the judgment result of step S06 is yes, continue to execute step S07; if the judgment result of step S06 is no, take the above-mentioned dependent network element as the target network element 2 (i.e., the new target network element), and execute steps S03' to S06' for the target network element 2 (the implementation process is the same as steps S03 to S06). Among them, if the judgment result of step S06' is no, take the dependent network element of the target network element 2 as the target network element 3, and execute steps S03" to S06" for the target network element 3 (the implementation process is the same as steps S03 to S06).

[0123] Step S07, setting the interface address parameters of the target network element 1.

[0124] Here, in the embodiment of the present application, the network IP parameter configuration of the aforementioned determined target network element 1 includes: the IP address of the target network element itself, the IP address of the external interface (i.e., the IP address of the dependent network element). According to the aforementioned steps, the parameter setting is completed based on the determined available IP address of the target network element, the allocated IP address of the dependent network element, or the IP address of the dependent network element container.

[0125] Step S08: Create a container instance of the target network element 1.

[0126] Here, in the implementation of the embodiment of the present application, the parameters set in step S07 are used to generate K8s component control instructions and initiate a container instance creation request.

[0127] The embodiment of the present application can realize automatic deployment of network elements by analyzing and calculating IP addresses, uniformly planning and dynamically setting interface address parameters of 5G core network elements. The core network element deployment can realize automatic calculation and setting of parameter configuration information without the need for prior planning and preset.

[0128] In some implementations, after the 5G core network system is deployed, the embodiment of the present application also provides an abnormal diagnosis process, such as Fig.10 As shown, the method includes the following steps S101 to S103:

[0129] Step S101: define the interactive service interface between network elements.

[0130] Here, in the embodiment of the present application, the interactive service interface (including N1~N16 and N22 interfaces) between each network element is defined according to the 5GC architecture in 3GPP, involving AMF network element IP and service port, UDM network element IP and service port, UPF network element IP and service port, AUSF network element IP and service port, PCF network element IP and service port and SMF network element IP and service port. The specific correspondence is shown in Table 1 below:

[0131] Table 1 Interactive service interfaces corresponding to the IP and service ports of each network element

[0132] Network element Interactive Service Interface AMF network element IP and service port N1, N2, N8, N11, N12, N14, N22 UDM network element IP and service port N8, N10, N13 UPF network element IP and service port N3, N4, N6, N9 AUSF network element IP and service port N12, N13 PCF network element IP and service port N5, N7, N15 SMF network element IP and service port N4, N7, N10, N11, N16

[0133] Step S102: Analyze whether the service port of the network element is abnormal, and determine whether the network element is abnormal.

[0134] Here, the service port reachability detection method includes but is not limited to the following methods: "ping IP address", "telnet IP address service port".

[0135] The application periodically pings each network element IP address and telnets each network element service port every minute to detect whether the service corresponding to each service port is reachable; unreachable services are removed and abnormal network elements are calculated according to the interactive service interface defined in step S101.

[0136] Step S103: restart the container instance of the abnormal network element.

[0137] Here, based on the abnormal network elements calculated in the previous step, a K8s component control instruction is generated to initiate a container instance restart request.

[0138] The embodiment of the present application provides real-time monitoring and analysis of network element IP and service ports, determines the status of its service ports, and quickly restarts its abnormal network elements, thereby minimizing service interruption time and improving user perception.

[0139] In some implementations, after the 5G core network system is deployed, the embodiment of the present application also provides a dynamic expansion and contraction process.

[0140] like Fig.11 As shown, the method includes the following steps S111 to S113:

[0141] Step S111, setting at least two target indicators and corresponding weights.

[0142] Here, the embodiment of the present application sets three target indicators for each network element, namely the number of signaling bars (xl_value, unit: pieces), CPU occupancy (cpu_value, unit: %) and memory occupancy (mem_value, unit: %), and sets the weight of each target indicator: the weight of the number of signaling bars is Q xl , the weight of CPU usage is Q cpu , the weight of memory usage is Q mem , and 1=Q xl +Q cpu +Q mem .

[0143] In implementation, the K8s component is controlled by the application to collect the specific values ​​of each target indicator, where the value of the number of signaling items is the total number within the detection period T, and the values ​​of CPU and memory are the average values ​​within the detection period T.

[0144] Step S112: setting indicator thresholds for at least two target indicators.

[0145] Here, the indicator threshold of each target indicator is set, which is divided into a maximum value and a minimum value. The maximum value represents the upper limit of the ideal business volume, and the minimum value represents the lower limit of the ideal business volume.

[0146] For example, the maximum number of signaling items F xl.max (such as 10000), minimum value F xl.min (e.g. 100);

[0147] The maximum value of CPU usage F cpu.max (such as 80), minimum value F cpu.min (Example 20)

[0148] The maximum value of memory usage F mem.max (such as 80), minimum value F mem.min (eg. 40)

[0149] Step S113, setting the system detection cycle and score threshold.

[0150] Here, the detection period T is set (such as 5 minutes); the score threshold is divided into a positive threshold P max (e.g. 30) and a negative threshold P min (e.g. -30), a value greater than the positive threshold indicates excessive load, and a value less than the negative threshold indicates insufficient load.

[0151] Step S114, calculating whether the comprehensive score meets the conditions.

[0152] Here, firstly, the comprehensive score of each network element under multiple target indicators is determined, and then based on the comprehensive score and the score threshold, it is determined whether the capacity needs to be expanded or reduced.

[0153] Load score P of the number of signaling messages xl Calculated by the following formulas (1) and (2), if P xl >100, then P xl =100, otherwise P xl =0:

[0154]

[0155]

[0156] Where xl_value is the number of signaling lines, F xl.maxand F xl.min are the maximum and minimum number of signaling messages respectively. The load score P of CPU usage cpu Calculated by the following formulas (3) and (4):

[0157]

[0158]

[0159] Where cpu_value is the CPU usage, F cpu.max and F cpu.min are the maximum and minimum CPU usage respectively, and P cpu =0.

[0160] The load score P of memory usage mem Calculated by the following formulas (5) and (6):

[0161]

[0162]

[0163] Among them, mem_value is the memory usage, F mem.max and F mem.min are the maximum and minimum values ​​of memory usage respectively, and P mem =0.

[0164] Finally, the comprehensive score P0 is calculated by formula (7):

[0165] P0=P xl ×Q xl +P cpu ×Q cpu +P mem ×Q mem Formula (7);

[0166] In P0>P max (positive threshold), expansion processing is required, and step S115 is continued; at P0 <P min (negative threshold), it is necessary to perform capacity reduction processing and continue to execute step S118.

[0167] Step S115, determining whether the available resources of the server are sufficient.

[0168] Here, in the embodiment of the present application, the current CPU and memory usage of the hardware server are extracted to determine the available resources of the server. If the available resources meet the minimum resource deployment requirements of a single network element, step S116 is executed; if not, step S117 is executed.

[0169] Step S116: create a new container instance.

[0170] Step S117, hardware server resource alarm.

[0171] Step S118, determining whether there are multiple container instances.

[0172] Here, in the embodiment of the present application, the number of container instances of the corresponding network element in the K8s component is extracted. If the number of container instances is less than or equal to 1, the detection of this cycle ends; if the number is greater than 1, step S119 is executed to delete 1 container instance. A container instance deletion request is initiated by generating a K8s component control instruction.

[0173] Step S119: delete the container instance of the network element.

[0174] Here, the comprehensive score continues to be calculated each time a container instance is deleted.

[0175] The embodiment of the present application adopts a multi-indicator weight calculation rule. According to the number of signal lives, CPU occupancy and memory occupancy data within the detection period, different indicator types use different score calculation methods, and automatically output a composite weighted score to trigger operation and maintenance instructions, thereby realizing elastic expansion and contraction of 5G core network resources.

[0176] The embodiment of the present application proposes a network element automatic deployment method and a private network system for a 5G core network system based on containerization technology, deploys K8s components and applications on a physical server, and controls the network element automatic deployment process, abnormal diagnosis process, and expansion and contraction process through the application to achieve intelligent operation and maintenance of the 5G core network.

[0177] Compared with the related technology, the embodiments of the present application have at least the following technical effects: the core network network element deployment can realize the automatic calculation and setting of parameter configuration information without the need for prior planning and preset; real-time monitoring and detection of network element IP and service port, judgment of its service interface status, triggering abnormal network element for rapid restart, minimizing service interruption time to improve user perception; proposing conditions and algorithms for triggering network element expansion and contraction, using weighted compound of multiple indicators to solve the judgment distortion caused by occasional fluctuations or errors of a single indicator, thereby realizing elastic expansion and contraction of 5G core network resources.

[0178] Based on the foregoing embodiments, an embodiment of the present application provides a network element automatic deployment device, which includes the modules included, and the sub-modules and units included in each module, which can be implemented by a processor in a computer device; of course, it can also be implemented by a specific logic circuit; in the implementation process, the processor can be a central processing unit (CPU), a microprocessor (MPU), a digital signal processor (DSP) or a field programmable gate array (FPGA), etc.

[0179] Fig.12 A schematic diagram of a network element automatic deployment device provided in an embodiment of the present application, such as Fig.12 As shown, the device 1200 includes: a system monitoring module 1210, an address analysis module 1220, a parameter configuration module 1230 and a container creation module 1240, wherein:

[0180] The system monitoring module 1210 is used to determine the target network element to be deployed by detecting the container instances of multiple network elements in the core network; wherein the container instances of the multiple network elements are deployed in the MEC server based on containerization technology;

[0181] The address analysis module 1220 is used to determine the target available IP address of the target network element;

[0182] The parameter configuration module 1230 is used to configure the interface address parameters of the target network element based on the dependency relationship between the multiple network elements and the target available IP address;

[0183] The container creation module 1240 is used to create a container instance of the target network element based on the interface address parameter.

[0184] In some embodiments, the address analysis module 1220 includes: an acquisition submodule, used to acquire the IP address segment of the target environment; wherein the target environment is the container operating environment of the multiple network elements; a first determination submodule, used to determine the used IP addresses in the target environment; wherein the used IP addresses include the addresses where the started container instances are running; a second determination submodule, used to determine the allocated IP addresses set in the container instances to be started of other network elements in the target environment; wherein the allocated IP addresses include predefined addresses that are allocated but not running in response to container startup requests of other network elements; a third determination submodule, used to determine the target available IP address of the target network element based on the IP address segment, the used IP addresses and the allocated IP addresses.

[0185] In some embodiments, the interface address parameters include the IP address of the target network element and the IP address of the external interface; the parameter configuration module 1230 includes: a third determination submodule, used to determine the dependent network element connected to the external interface of the target network element based on the dependency relationship between the multiple network elements; a fourth determination submodule, used to determine the IP address of the external interface based on the container instance IP address of the dependent network element or the allocated IP address of the dependent network element when a container instance of the dependent network element exists or the allocated IP address of the dependent network element exists; a configuration submodule, used to configure the interface address parameters of the target network element based on the target available IP address and the IP address of the external interface.

[0186] In some embodiments, the parameter configuration module 1230 also includes: a target update submodule, which is used to take the dependent network element as a new target network element and preferentially create a container instance of the new target network element when the container instance of the dependent network element does not exist and the allocated IP address of the dependent network element does not exist.

[0187] In some embodiments, the device also includes: a status monitoring module, used to monitor the status of the interactive service interface between the multiple network elements in real time; wherein the interactive service interface of the multiple network elements includes the IP address and service port of each of the network elements; an abnormality judgment module, used to determine that the network element corresponding to the first service port is an abnormal network element when it is detected that the service corresponding to the first service port is unreachable; and a container restart module, used to restart the container instance of the abnormal network element.

[0188] In some embodiments, the device also includes: a first scoring module, used to determine the load score of each of the network elements under at least two target indicators within a preset detection period; a second scoring module, used to weighted sum the load scores of the at least two target indicators based on a preset weight coefficient to determine a comprehensive score; and a dynamic adjustment module, used to adjust the container instance of the corresponding network element based on the comprehensive score and a preset resource deployment threshold.

[0189] In some embodiments, the resource deployment threshold includes a positive threshold and a negative threshold; the dynamic adjustment module includes: an expansion submodule, used to create a new container instance for the network element when the comprehensive score is greater than the positive threshold; a reduction submodule, used to delete one of the container instances when the comprehensive score is less than the negative threshold and the number of the container instances of the corresponding network element is greater than 1.

[0190] In some embodiments, the target indicator includes at least two of the number of signaling messages, memory occupancy, and CPU occupancy; the capacity expansion submodule includes: a resource evaluation unit, used to determine the current available resources of the server; a creation unit, used to create a new network element container instance for the network element when the available resources meet the minimum deployment resource requirements of the network element.

[0191] The description of the above device embodiment is similar to the description of the above method embodiment, and has similar beneficial effects as the method embodiment. In some embodiments, the functions or modules included in the device provided by the embodiments of the present disclosure can be used to execute the method described in the above method embodiment. For technical details not disclosed in the device embodiment of the present application, please refer to the description of the method embodiment of the present application for understanding.

[0192] It should be noted that in the embodiments of the present application, if the above-mentioned network element automatic deployment method is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application can be essentially or partly reflected in the form of a software product that contributes to the relevant technology. The software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a U disk, a mobile hard disk, a read-only memory (ROM), a disk or an optical disk. In this way, the embodiments of the present application are not limited to any specific hardware, software or firmware, or any combination of hardware, software, and firmware.

[0193] An embodiment of the present application provides a computer device, including a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and when the processor executes the program, some or all of the steps in the above method are implemented.

[0194] The embodiment of the present application provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, some or all of the steps in the above method are implemented. The computer-readable storage medium can be transient or non-transient.

[0195] An embodiment of the present application provides a computer program, including a computer-readable code. When the computer-readable code is run in a computer device, a processor in the computer device executes some or all of the steps for implementing the above method.

[0196] The embodiment of the present application provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program, and when the computer program is read and executed by a computer, some or all of the steps in the above method are implemented. The computer program product can be implemented specifically by hardware, software or a combination thereof. In some embodiments, the computer program product is specifically embodied as a computer storage medium, and in other embodiments, the computer program product is specifically embodied as a software product, such as a software development kit (SDK) and the like.

[0197] It should be noted here that the description of the various embodiments above tends to emphasize the differences between the various embodiments, and the same or similar aspects can be referenced to each other. The description of the above device, storage medium, computer program and computer program product embodiments is similar to the description of the above method embodiment, and has similar beneficial effects as the method embodiment. For technical details not disclosed in the embodiments of the device, storage medium, computer program and computer program product of this application, please refer to the description of the method embodiment of this application for understanding.

[0198] It should be noted that Fig.13 A schematic diagram of a hardware entity of a computer device in an embodiment of the present application is shown in FIG. Fig.13 As shown, the hardware entity of the computer device 1300 includes: a processor 1301, a communication interface 1302 and a memory 1303, wherein:

[0199] Processor 1301 generally controls the overall operation of computer device 1300 .

[0200] The communication interface 1302 enables the computer device to communicate with other terminals or servers through a network.

[0201] The memory 1303 is configured to store instructions and applications executable by the processor 1301, and can also cache data to be processed or processed by the processor 1301 and each module in the computer device 1300 (for example, image data, audio data, voice communication data, and video communication data), which can be implemented by flash memory (FLASH) or random access memory (Random Access Memory, RAM). Data transmission can be performed between the processor 1301, the communication interface 1302, and the memory 1303 through the bus 1304.

[0202] It should be understood that "one embodiment" or "an embodiment" mentioned throughout the specification means that specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in various embodiments of the present application, the size of the serial number of each step / process mentioned above does not mean the order of execution, and the execution order of each step / process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. The serial numbers of the embodiments of the present application mentioned above are for description only and do not represent the advantages and disadvantages of the embodiments.

[0203] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0204] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.

[0205] The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units; they may be located in one place or distributed on multiple network units; some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0206] In addition, all functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may be a separate unit, or two or more units may be integrated into one unit; the above-mentioned integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0207] A person skilled in the art can understand that all or part of the steps of implementing the above method embodiment can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above method embodiment; and the aforementioned storage medium includes: mobile storage devices, read-only memories (ROM), magnetic disks or optical disks, etc., various media that can store program codes.

[0208] Alternatively, if the above-mentioned integrated unit of the present application is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can essentially or in other words, the part that contributes to the relevant technology can be embodied in the form of a software product, which is stored in a storage medium and includes a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROMs, magnetic disks, or optical disks.

[0209] The above is only an implementation method of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application.

Claims

1. A method for automatic deployment of network elements, characterized in that: Applied to a MEC server, the method includes: Determine the target network element to be deployed by detecting container instances of multiple network elements in the core network; wherein the container instances of the multiple network elements are deployed in the MEC server based on containerization technology; Determine a target available IP address of the target network element; Based on the dependency relationship between the multiple network elements and the target available IP address, configure the interface address parameters of the target network element; Based on the interface address parameters, a container instance of the target network element is created.

2. The method according to claim 1, characterized in that The determining the target available IP address of the target network element includes: Obtaining an IP address segment of a target environment; wherein the target environment is a container operating environment of the multiple network elements; Determine the used IP addresses in the target environment; wherein the used IP addresses include the addresses where the started container instances are running; Determine an allocated IP address configured for a container instance to be started of another network element; wherein the other network element is a network element other than the target network element in the target environment; the allocated IP address includes a predefined address allocated but not running in response to a container start request of the other network element; Based on the IP address segment, the used IP address and the allocated IP address, a target available IP address of the target network element is determined.

3. The method according to claim 1, characterized in that The interface address parameters include the IP address of the target network element and the IP address of the external interface; and configuring the interface address parameters of the target network element based on the dependency relationship between the multiple network elements and the target available IP address includes: Based on the dependency relationship between the multiple network elements, determining a dependent network element connected to an external interface of the target network element; In a case where the container instance of the dependent network element exists or the allocated IP address of the dependent network element exists, determining the IP address of the external interface based on the container instance IP address of the dependent network element or the allocated IP address of the dependent network element; Based on the target available IP address and the IP address of the external interface, the interface address parameters of the target network element are configured.

4. The method according to claim 3, characterized in that: The method further comprises: In the case that the container instance of the dependent network element does not exist and the allocated IP address of the dependent network element does not exist, the dependent network element is used as a new target network element, and a container instance of the new target network element is preferentially created.

5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: Monitoring the status of the interactive service interfaces between the multiple network elements in real time; wherein the interactive service interfaces of the multiple network elements include the IP address and service port of each of the network elements; In a case where it is detected that a service corresponding to the first service port is unreachable, determining that the network element corresponding to the first service port is an abnormal network element; Restart the container instance of the abnormal network element.

6. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: Determining a load score of each network element under at least two target indicators within a preset detection period; Performing a weighted summation of the load scores of the at least two target indicators based on a preset weight coefficient to determine a comprehensive score; Based on the comprehensive score and a preset resource deployment threshold, the container instance of the corresponding network element is adjusted.

7. The method according to claim 6, characterized in that The resource deployment threshold includes a positive threshold and a negative threshold; and adjusting the container instance of the corresponding network element based on the comprehensive score and the preset resource deployment threshold includes: When the comprehensive score is greater than the positive threshold, creating a new container instance for the network element; When the comprehensive score is less than the negative threshold and the number of the container instances of the corresponding network element is greater than 1, one of the container instances is deleted.

8. The method according to claim 7, characterized in that The target indicators include at least two of the number of signaling items, memory usage and CPU usage; The creating a new container instance for the network element when the comprehensive score is greater than the positive threshold includes: Determining currently available resources of the server; In a case where the available resources meet the minimum deployment resource requirement of the network element, a new network element container instance is created for the network element.

9. A private network system, characterized in that: The private network system includes a base station and a MEC server, wherein: The base station is used to establish a network connection with the MEC server; The MEC server is used to determine the target network element to be deployed by detecting the container instances of multiple network elements in the core network; wherein the container instances of the multiple network elements are deployed in the MEC server based on containerization technology; determine the target available IP address of the target network element; configure the interface address parameters of the target network element based on the dependency relationship between the multiple network elements and the target available IP address; and create the container instance of the target network element based on the interface address parameters.

10. The private network system according to claim 9, characterized in that: The MEC server includes an application, a container orchestration tool, and a container image repository; The container image repository is used to store the container images of the multiple network elements; The container orchestration tool is used to deploy corresponding container instances for the multiple network elements respectively; The application is used to control the container orchestration tool to obtain each of the container images from the container image repository and create the container instance of the corresponding network element, and execute the steps of the network element automatic deployment method.

11. A network element automatic deployment device, characterized in that: Applied to MEC servers, including: A system monitoring module, used to determine the target network element to be deployed by detecting the container instances of multiple network elements in the core network; wherein the container instances of the multiple network elements are deployed in the MEC server based on containerization technology; An address analysis module, used to determine a target available IP address of the target network element; A parameter configuration module, configured to configure the interface address parameters of the target network element based on the dependency relationship between the multiple network elements and the target available IP address; The container creation module is used to create a container instance of the target network element based on the interface address parameter.

12. A computer device comprising a memory and a processor, wherein the memory stores a computer program executable on the processor, wherein: When the processor executes the program, the steps in the method according to any one of claims 1 to 8 are implemented.

13. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps in the method according to any one of claims 1 to 8 are implemented.

Images