WO2024066965A1 - 网元管理方法、装置、存储介质及电子装置 - Google Patents

网元管理方法、装置、存储介质及电子装置 Download PDF

Info

Publication number
WO2024066965A1
WO2024066965A1 PCT/CN2023/117055 CN2023117055W WO2024066965A1 WO 2024066965 A1 WO2024066965 A1 WO 2024066965A1 CN 2023117055 W CN2023117055 W CN 2023117055W WO 2024066965 A1 WO2024066965 A1 WO 2024066965A1
Authority
WO
WIPO (PCT)
Prior art keywords
cnf
operator
cnfm
catalog
cism
Prior art date
Application number
PCT/CN2023/117055
Other languages
English (en)
French (fr)
Inventor
张进
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2024066965A1 publication Critical patent/WO2024066965A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • 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/04—Network management architectures or arrangements

Definitions

  • the embodiments of the present disclosure relate to the field of communications, and in particular, to a network element management method, device, storage medium, and electronic device.
  • each application service in the network device must provide a standard Chart package format, define the container resource model according to the Kubernetes standard resource type, deploy the Chart package through the Kubernetes package tool Helm, create releases of various containers, and implement the deployment of container resources.
  • the embodiments of the present disclosure provide a network element management method, device, storage medium and electronic device to at least solve the problem that the basic capabilities of Helm and Chart packages used in related technologies for resource orchestration are not fully applicable and not flexible enough for the management of telecommunications cloud network equipment.
  • a network element management method comprising: deploying a cloud-native network function controller (Cloud-Native Network Function Operator, referred to as CNF Operator) on a master control node of a K8s system; deploying a cloud-native network function manager (Cloud-Native Network Function Manager, referred to as CNFM) and a catalog warehouse Catalog in a network management system; and managing CNF network elements through CNFM and Catalog in collaboration with CNF Operator.
  • CNF Operator Cloud-Native Network Function Operator
  • CNFM Cloud-Native Network Function Manager
  • a network element management device which includes: a first deployment module, configured to deploy CNF Operator on a master control node of a K8s system; a second deployment module, configured to deploy CNF Operator in a central node of a network management system; Deploy cloud native network function management CNFM and catalog warehouse Catalog; the management module is set to manage CNF network elements through CNFM and Catalog under the collaboration of CNF Operator.
  • a computer-readable storage medium in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.
  • an electronic device including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.
  • FIG1 is a hardware structure block diagram of a network device of a network element management method according to an embodiment of the present disclosure
  • FIG2 is a flow chart of a network element management method according to an embodiment of the present disclosure
  • FIG3 is a flow chart of a network element management method according to an exemplary embodiment of the present disclosure.
  • FIG4 is a block diagram of functional components according to the present embodiment.
  • FIG5 is a flow chart of the CNF lifecycle management phase according to this embodiment.
  • FIG6 is a block diagram of a network element management device according to an embodiment of the present disclosure.
  • FIG1 is a hardware structure block diagram of a network device of the network element management method of the embodiment of the present disclosure.
  • the network device may include one or more (only one is shown in FIG1 ) processors 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data, wherein the above-mentioned network device may also include a transmission device 106 and an input and output device 108 for communication functions.
  • FIG1 is only for illustration, and it does not limit the structure of the above-mentioned network device.
  • the network device may also include more or fewer components than those shown in FIG1 , or have a configuration different from that shown in FIG1 .
  • the memory 104 may be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the network element management method in the embodiment of the present disclosure.
  • the processor 102 executes various functional applications and network element management processing by running the computer program stored in the memory 104, that is, to implement the above method.
  • the memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory.
  • the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the network device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
  • the transmission device 106 is used to receive or send data via a network.
  • the specific example of the above network may include a wireless network provided by a communication provider of the network device.
  • the transmission device 106 includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through the network device so as to communicate with the Internet.
  • the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.
  • RF radio frequency
  • FIG. 2 is a flow chart of the network element management method according to an embodiment of the present disclosure. As shown in FIG. 2 , the process includes the following steps:
  • Step S202 deploy CNF Operator on the master node of the K8s system
  • Step S204 deploying CNFM and catalog warehouse Catalog in the network management system
  • step S204 may specifically include: deploying the CNFM and the catalog warehouse Catalog in the network function virtualization orchestrator NFVO, the virtual network function manager (Virtual Network Function Manager, referred to as VNFM) or the element management (Element Management, referred to as EM) of the network management system.
  • VNFM Virtual Network Function Manager
  • EM lement Management
  • Step S206 With the collaboration of CNF Operator, CNF network elements are managed through CNFM and Catalog.
  • CNFM and Catalog are introduced into the network management system, and CNF network elements are managed through CNFM and Catalog, thereby realizing flexible and scalable orchestration of container resources for telecom cloud network equipment.
  • FIG. 3 is a flow chart of a network element management method according to an exemplary embodiment of the present disclosure. As shown in FIG. 3 , step S206 may specifically include:
  • Step S 302 in cooperation with the CNF Operator, deploy the CNF container resources of the CNF network element through the CNFM and the Catalog.
  • the CNF package is imported through the Catalog, and the CNF package is CNF instantiated through the CNFM to deploy the CNF container resources.
  • a first creation request for creating a CNF package is sent to the CNF Operator through the CNFM to instruct the CNF Operator to download the CNF package from the Catalog;
  • a second creation request for creating a CNF instance is sent to the CNF Operator through the CNFM to instruct the CNF Operator to create the CNF instance according to the CNF package to complete the deployment of the CNF container resources.
  • the method before sending a first creation request for creating a CNF package to the CNF Operator through the CNFM, the method also includes: if the CNF Operator does not exist, sending a third creation request for creating an instance of the CNF Operator through the CNFM to the CISM, and creating the instance of the CNF Operator through the CISM.
  • Step S 304 with the cooperation of the CNF Operator, the CNF is queried through the CNFM.
  • a first query message for querying the CNF instance is sent to the CISM through the CNFM, and the first query message is sent to the CNF Operator through the CISM to instruct the CNF Operator to complete the query of the CNF instance;
  • a second query message for querying the CNF package is sent to the CISM through the CNFM, and the second query message is sent to the CNF Operator through the CISM to instruct the CNF Operator to complete the query of the CNF package.
  • Step S306 in cooperation with the CNF Operator, the CNF container resources are updated through the CNFM and the Catalog.
  • a new CNF package is imported through the Catalog; the CNF instance of the new CNF package is updated or upgraded through the CNFM to update the CNF container resources.
  • a first update message for updating the CNF package is sent to the container infrastructure service management CISM through the CNFM, and the first update message is sent to the CNF Operator through the CISM to instruct the CNF Operator to download the new CNF package from the Catalog;
  • a second update message for updating the CNF instance is sent to the CISM through the CNFM, and the second update message is sent to the CNF Operator through the CISM to instruct the CNF Operator to update the CNF instance according to the new CNF package to complete the update of the CNF container resources;
  • Step S308 in cooperation with the CNF Operator, the CNFM destroys the CNF container resources.
  • the CNFM executes CNF termination to destroy the CNF container resources.
  • the CNFM sends a first deletion message to the CISM to delete the CNF instance, and the CISM sends the first deletion message to the CISM.
  • CNF Operator to instruct the CNF Operator to delete the CNF instance to complete the release or deletion of the CNF container resources;
  • a second deletion message for deleting the CNF package is sent to the CISM through the CNFM, and the second deletion message is sent to the CNF Operator through the CISM to instruct the CNF Operator to delete the CNF package.
  • the method further includes: when CNFM is deployed in the NFVO of the network management system, the container resources of the container network function CNF network element are orchestrated by the NFVO in collaboration with the CNFM and the container infrastructure manager CISM; and/or the NFVO is connected to the operation support system OSS, and the configuration data, performance data and alarm data of the container resources of the CNF network element are reported to the OSS.
  • CNFM and Catalog can be deployed in any network management system that supports network element lifecycle orchestration, including but not limited to NFVO, VNFM, and element management (EM).
  • Custom Resources By utilizing the Custom Resources (CR) mechanism provided by Kubernetes, secondary development and extension are performed on the standard Application Programming Interface (API) of Kubernetes. All container resources or special resource types in CNF are defined through custom resources CR to form CRD.
  • API Application Programming Interface
  • the CNF Operator component is introduced for CNF container management. This component is implemented based on the Kubernetes standard custom controller (Custom Controller) framework and is deployed in the control node of CISM. Different network element types can share the same CNF Operator, or each type can provide a different CNF Operator.
  • the CNF package model specification is introduced into CNF.
  • the Chart package file in the CNF package is customized by the network element.
  • the Catalog component provides management functions such as importing and querying CNF packages.
  • CNFM uses the Kubernetes package tool Helm to create the Release of the CNF Operator, and then creates the CNF package CR and CNF instance CR in sequence, triggering the CNF Operator to download the CNF package file after listening to the CR message, and use the CNF package Chart file to deploy the CNF container resources.
  • CNFM performs lifecycle operations such as upgrading and updating CNF. CNFM creates these lifecycle operations CRs, triggering CNF Operator to listen to CR messages and perform corresponding container resource management operations.
  • CNFM deletes the CNF instance CR and CNF package CR in turn, triggering the CNF Operator to execute the corresponding CNF container resource deletion after listening to the CR message.
  • CNFM does not need to perceive the differences between different CISM platforms.
  • This embodiment introduces CNFM service in the network management system NFVO.
  • CNFM cooperates with the catalog management service Catalog to complete the Chart package management and life cycle management functions of CNF network elements.
  • catalog management service Catalog can also be deployed to manage CNF network elements, which is not limited in this embodiment.
  • FIG4 is a block diagram of the functional components according to this embodiment, as shown in FIG4, including:
  • CNFM Provides lifecycle management of CNF network elements, including instantiation, termination, update, and viewing.
  • API Server The API gateway of Kubernetes, deployed on the master node of Kubernetes, receives operation requests of custom resources CR, and writes CR data to ETCD.
  • CNF Operator Provides CR resource management for CNF network elements. It is deployed on the master node of Kubernetes, monitors changes in CR records in Kubernetes's ETCD, and performs corresponding CR resource operations, such as calling the Kubernetes interface to deploy various Pod containers of CNF.
  • FIG5 is a flow chart of the CNF lifecycle management phase according to this embodiment, as shown in FIG5 , including:
  • the deployment of CNF container resources needs to include:
  • Step 1 The user imports the CNF package in the Catalog
  • Step 2 The user performs CNF instantiation in the CNFM service
  • Step 3 CNFM queries and obtains CNF packages from Catalog
  • Step 4 CNFM creates the Release of CNF Operator through Helm (corresponding to the third creation request mentioned above), and the Kubernetes standard process is reused here;
  • Step 5 CNFM sends a CR message (corresponding to the first creation request) for creating a CNF Package to the Kubernetes API Server gateway of the Container Infrastructure Service Management (CISM), notifying the CNF Operator to download the CNF package file.
  • CISM Container Infrastructure Service Management
  • Step 6 CNFM sends a CR message (corresponding to the second creation request) to create a CNF Instance to the Kubernetes API Server gateway of CISM, notifying the CNF Operator to complete the deployment of CNF container resources.
  • Step 7 Return the instantiation result.
  • Step 8 the user performs a CNF query in the CNFM service
  • Step 9 CNFM sends a CR message (corresponding to the first query message) to query CNF Instance to the Kubernetes API Server gateway of CISM, notifying CNF Operator to complete the query of CNF instance information. This is a new process.
  • Step 10 CNFM sends a CR message (corresponding to the second query message) for querying CNF Package to the Kubernetes API Server gateway of CISM, notifying CNF Operator to complete the query of CNF package information;
  • Step 11 return the query result.
  • Step 12 The user imports a new CNF package in the Catalog, or updates an existing CNF package;
  • Step 13 the user performs CNF update or upgrade in the CNFM service
  • Step 14 CNFM queries and obtains CNF packages from Catalog
  • Step 15 CNFM sends a CR message (corresponding to the first update message) for updating CNF Package to the Kubernetes API Server gateway of CISM, notifying CNF Operator to download the new CNF package file;
  • Step 16 CNFM sends a CR message (corresponding to the second update message) for updating CNF Instance to CISM.
  • the Kubernetes API Server gateway notifies the CNF Operator to complete the update or upgrade of the CNF container resources;
  • Step 17 return the update result
  • the user executes CNF termination through CNFM and destroys the CNF container resources.
  • the CNF container resources need to be released or deleted:
  • Step 18 the user performs CNF termination in the CNFM service
  • Step 19 CNFM sends a CR message (corresponding to the first deletion message) to delete the CNF Instance to the Kubernetes API Server gateway of CISM, notifying the CNF Operator to complete the release or deletion of the CNF container resources;
  • Step 20 CNFM sends a CR message (corresponding to the second update message) to delete the CNF Package to the Kubernetes API Server gateway of CISM, informing the CNF Operator to delete the CNF package file;
  • Step 21 return the termination result.
  • This disclosure does not list or describe other lifecycle operation processes except CNF instantiation, CNF update, CNF termination, and CNF query.
  • CNF operators are introduced to manage CNF container resources, no matter which type of lifecycle operation, the following principles are followed: when resources are deployed, CNF operators are deployed first or existing public CNF operators are used, and then CNF container resources are deployed or managed through CNF operators; when resources are deleted, CNF operators are deleted or released first, and then the network element's own CNF operators are deleted or the public CNF operators are retained.
  • FIG. 6 is a block diagram of the network element management device according to an embodiment of the present disclosure. As shown in FIG. 6 , the device includes:
  • the first deployment module 62 is configured to deploy a cloud native network function operator CNF Operator on a master control node of the K8s system;
  • the second deployment module 64 is configured to deploy the cloud native network function management CNFM and the catalog warehouse Catalog in the network management system;
  • the management module 66 is configured to manage the CNF network elements through the CNFM and the Catalog in collaboration with the CNF Operator.
  • the management module 66 includes:
  • a deployment submodule configured to deploy container resources of the CNF network element through the CNFM and the Catalog in coordination with the CNF Operator;
  • a query submodule configured to query the CNF network element information through the CNFM in cooperation with the CNF Operator;
  • An update submodule configured to update the container resources of the CNF network element through the CNFM and the Catalog in coordination with the CNF Operator;
  • the destruction submodule is configured to destroy the container resources of the CNF network element through the CNFM under the cooperation of the CNF Operator.
  • the deployment submodule is further configured to send a first creation request to create a CNF package to the CNF Operator through the CNFM to instruct the CNF Operator to download the CNF package from the Catalog; send a second creation request to create a CNF instance to the CNF Operator through the CNFM to instruct the CNF Operator to download the CNF package from the Catalog; The Operator creates the CNF instance according to the CNF package to complete the deployment of the CNF container resources.
  • the device further comprises:
  • the first creation submodule is configured to send a third creation request for creating an instance of the CNF Operator to the CISM through the CNFM, and create the instance of the CNF Operator through the CISM.
  • the query submodule is further configured to send a first query message for querying a CNF instance to the CISM through the CNFM, and send the first query message to the CNF Operator through the CISM to instruct the CNF Operator to complete the query of the CNF instance; and send a second query message for querying a CNF package to the CISM through the CNFM, and send the second query message to the CNF Operator through the CISM to instruct the CNF Operator to complete the query of the CNF package.
  • the update submodule is further configured to send a first update message for updating a CNF package to a container infrastructure service management CISM through the CNFM, and send the first update message to the CNF Operator through the CISM to instruct the CNF Operator to download a new CNF package from the Catalog; and send a second update message for updating a CNF instance to the CISM through the CNFM, and send the second update message to the CNF Operator through the CISM to instruct the CNF Operator to update the CNF instance according to the new CNF package to complete the update of the CNF container resources.
  • the destruction submodule is further configured to send a first deletion message for deleting a CNF instance to the CISM through the CNFM, and send the first deletion message to the CNF Operator through the CISM to instruct the CNF Operator to delete the CNF instance; and send a second deletion message for deleting a CNF package to the CISM through the CNFM, and send the second deletion message to the CNF Operator through the CISM to instruct the CNF Operator to delete the CNF package, so as to complete the release or deletion of the CNF container resources.
  • the second deployment module 64 is further configured to deploy the CNFM and the catalog repository Catalog in the network function virtualization orchestrator NFVO, the virtual network function manager VNFM or the network element manager EM of the network management system.
  • the device further comprises:
  • an orchestration module configured to orchestrate container resources of a container network function CNF network element through the NFVO in collaboration with the CNFM and a container infrastructure manager CISM when the CNFM is deployed in the NFVO of the network management system;
  • the reporting module is configured to connect to the operation support system OSS through the NFVO, and report the configuration data, performance data and alarm data of the container resources of the CNF network element to the OSS.
  • An embodiment of the present disclosure further provides a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.
  • the above-mentioned computer-readable storage medium may include, but is not limited to: a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and other media that can store computer programs.
  • An embodiment of the present disclosure further provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.
  • the electronic device may further include a transmission device and an input/output device, wherein the transmission device is connected to the processor, and the input/output device is connected to the processor.
  • modules or steps of the present disclosure can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order than here, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation.
  • the present disclosure is not limited to any specific combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本公开实施例提供了一种网元管理方法、装置、存储介质及电子装置，该方法包括：在K8s系统的主控节点上部署云原生网络功能操控器CNF Operator；在网管系统中部署云原生网络功能管理CNFM与目录仓库Catalog；在该CNF Operator的协同下，通过该CNFM与该Catalog对CNF网元进行管理。

Description

网元管理方法、装置、存储介质及电子装置
相关申请的交叉引用
本公开基于2022年09月30日提交的发明名称为“网元管理方法、装置、存储介质及电子装置”的中国专利申请CN202211214733.6，并且要求该专利申请的优先权，通过引用将其所公开的内容全部并入本公开。
技术领域
本公开实施例涉及通信领域，具体而言，涉及一种网元管理方法、装置、存储介质及电子装置。
背景技术
按照Kubernets(K8s)的标准能力，网络设备中的每个应用服务，均需提供标准的Chart包格式，按照Kubernets标准的资源类型定义容器资源模型，通过Kubernets的包工具Helm进行Chart包部署，创建各类容器的Release，实现容器资源的部署。
目前国内运营商对于电信云中容器APP(Application)应用的管理，也是基于Chart包和Helm部署制定规范的。电信云中的CT域网络功能组网复杂，资源类型多样，采用Kubernets基础的资源类型进行定义，则Chart包非常复杂且不灵活，比如无法支持不同服务间的优先级或依赖关系。不同容器基础设施服务管理(Container Infrastructure Service Management，简称为CISM)平台的差异，无法对上层网络编排系统进行屏蔽。比如容器镜像的管理，不同CISM平台的管理方式不同，按照标准能力编排，则网络功能虚拟化编排器(Network Functions Virtualisation Orchestrator，简称为NFVO)需要针对不同CISM平台提供不同的容器镜像上传。因此，采用Helm和Chart包的基础能力进行资源编排，对于电信云网络设备的管理并非完全适用。
针对相关技术中采用Helm和Chart包的基础能力进行资源编排，对于电信云网络设备的管理并非完全适用且不够灵活的问题，尚未提出解决方案。
发明内容
本公开实施例提供了一种网元管理方法、装置、存储介质及电子装置，以至少解决相关技术中采用Helm和Chart包的基础能力进行资源编排，对于电信云网络设备的管理并非完全适用且不够灵活的问题。
根据本公开的一个实施例，提供了一种网元管理方法，该方法包括：在K8s系统的主控节点上部署云原生网络功能操控器(Cloud-Native Network Function Operator，简称为CNF Operator)；在网管系统中部署云原生网络功能管理(Cloud-Native Network Function Manager，简称为CNFM)与目录仓库Catalog；在CNF Operator的协同下，通过CNFM与Catalog对CNF网元进行管理。
根据本公开的另一个实施例，还提供了一种网元管理装置，该装置包括：第一部署模块，设置为在K8s系统的主控节点上部署CNF Operator；第二部署模块，设置为在网管系统中部 署云原生网络功能管理CNFM与目录仓库Catalog；管理模块，设置为在CNF Operator的协同下，通过CNFM与Catalog对CNF网元进行管理。
根据本公开的又一个实施例，还提供了一种计算机可读的存储介质，存储介质中存储有计算机程序，其中，计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
根据本公开的又一个实施例，还提供了一种电子装置，包括存储器和处理器，存储器中存储有计算机程序，处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
附图说明
图1是本公开实施例的网元管理方法的网络设备的硬件结构框图；
图2是根据本公开实施例的网元管理方法的流程图；
图3是根据本公开示例性实施例的网元管理方法的流程图；
图4是根据本实施例的功能组件的框图；
图5是根据本实施例的CNF生命周期管理阶段的流程图；
图6是根据本公开实施例的网元管理装置的框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本公开的实施例。
需要说明的是，本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
本公开实施例中所提供的方法实施例可以在网络设备或者类似的运算装置中执行。以运行在网络设备上为例，图1是本公开实施例的网元管理方法的网络设备的硬件结构框图，如图1所示，网络设备可以包括一个或多个(图1中仅示出一个)处理器102(处理器102可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置)和用于存储数据的存储器104，其中，上述网络设备还可以包括用于通信功能的传输设备106以及输入输出设备108。本领域普通技术人员可以理解，图1所示的结构仅为示意，其并不对上述网络设备的结构造成限定。例如，网络设备还可包括比图1中所示更多或者更少的组件，或者具有与图1所示不同的配置。
存储器104可用于存储计算机程序，例如，应用软件的软件程序以及模块，如本公开实施例中的网元管理方法对应的计算机程序，处理器102通过运行存储在存储器104内的计算机程序，从而执行各种功能应用以及网元管理处理，即实现上述的方法。存储器104可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器104可进一步包括相对于处理器102远程设置的存储器，这些远程存储器可以通过网络连接至网络设备。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输设备106用于经由一个网络接收或者发送数据。上述的网络具体实例可包括网络设备的通信供应商提供的无线网络。在一个实例中，传输设备106包括一个网络适配器(Network Interface Controller，简称为NIC)，其可通过网络设备与其他网络设备相连从而可与互联网进行通讯。在一个实例中，传输设备106可以为射频(Radio Frequency，简称为RF)模块，其用于通过无线方式与互联网进行通讯。
在本实施例中提供了一种运行于上述网络设备或网络架构的网元管理方法，图2是根据本公开实施例的网元管理方法的流程图，如图2所示，该流程包括如下步骤：
步骤S202，在K8s系统的主控节点上部署CNF Operator；
步骤S204，在网管系统中部署CNFM与目录仓库Catalog；
本实施例中，步骤S204具体可以包括：在网管系统的网络功能虚拟化编排器NFVO、虚拟网络功能管理器(Virtual Network Function Manager，简称为VNFM)或网元管理(Element Management，简称为EM)中部署所述CNFM和所述目录仓库Catalog。
步骤S206，在CNF Operator的协同下，通过CNFM与Catalog对CNF网元进行管理。
通过上述步骤S202至步骤S206，可以解决相关技术中采用Helm和Chart包的基础能力进行资源编排，对于电信云网络设备的管理并非完全适用且不够灵活的问题，在网管系统中引入CNFM和Catalog，通过CNFM和Catalog进行CNF网元管理，实现了电信云网络设备的容器资源编排灵活可扩展的编排。
图3是根据本公开示例性实施例的网元管理方法的流程图，如图3所示，步骤S206具体可以包括：
步骤S 302，在CNF Operator的协同下，通过CNFM与Catalog对CNF网元的CNF容器资源进行部署，示例性的，在CNF Operator的协同下，通过Catalog导入CNF包，通过CNFM对CNF包进行CNF实例化，以部署CNF容器资源，具体的，通过该CNFM向该CNF Operator发送创建CNF包的第一创建请求，以指示该CNF Operator从该Catalog中下载该CNF包；通过该CNFM向该CNF Operator发送创建CNF实例的第二创建请求，以指示该CNF Operator根据该CNF包创建该CNF实例，以完成该CNF容器资源的部署；
在一示例性实施例中，在通过该CNFM向该CNF Operator发送创建CNF包的第一创建请求之前，该方法还包括：如果CNF Operator不存在，则通过该CNFM向该CISM发送创建该CNF Operator的实例的第三创建请求，通过该CISM创建该CNF Operator的实例。
步骤S 304，在CNF Operator的协同下，通过该CNFM对该CNF进行查询，具体的，通过该CNFM向该CISM下发查询CNF实例的第一查询消息，通过该CISM将该第一查询消息发送给该CNF Operator，以指示该CNF Operator完成该CNF实例的查询；通过CNFM向该CISM下发查询CNF包的第二查询消息，通过该CISM将该第二查询消息发送给该CNF Operator，以指示该CNF Operator完成该CNF包的查询。
步骤S306，在CNF Operator的协同下，通过该CNFM与Catalog对该CNF容器资源进行更新，示例性的，在CNF Operator的协同下，通过Catalog导入新CNF包；通过CNFM对该新CNF包进行CNF实例更新或升级，以更新CNF容器资源，具体的，通过该CNFM向容器基础设施服务管理CISM下发更新CNF包的第一更新消息，通过该CISM将该第一更新更新消息发送给该CNF Operator，以指示该CNF Operator从该Catalog中下载新的CNF包；通过该CNFM向CISM下发更新CNF实例的第二更新消息，通过该CISM将该第二更新消息发送给该CNF Operator，以指示该CNF Operator根据该新的CNF包更新CNF实例，以完成该CNF容器资源的更新；
步骤S308，在CNF Operator的协同下，通过CNFM对CNF容器资源进行销毁，示例性的，在CNF Operator的协同下，通过CNFM执行CNF终止，以销毁CNF容器资源，具体的，通过该CNFM向CISM下发删除CNF实例的第一删除消息，通过该CISM将该第一删除消息发送给该 CNF Operator，以指示该CNF Operator删除该CNF实例，以完成该CNF容器资源的释放或删除；通过该CNFM向该CISM下发删除CNF包的第二删除消息，通过该CISM将该第二删除消息发送给该CNF Operator，以指示该CNF Operator删除该CNF包。
在一示例性实施例中，该方法还包括：在网管系统的NFVO中部署CNFM的情况下，通过NFVO协同CNFM、容器基础设施管理器CISM，对容器网络功能CNF网元的容器资源进行编排；和/或通过NFVO对接运营支撑系统OSS，并向该OSS上报CNF网元的容器资源的配置数据、性能数据及告警数据。
对于部署在Kubernets容器云平台CISM中的容器化网元或者云原生网络功能CNF，引入生命周期编排服务组件CNFM和目录管理组件Catalog，CNFM和Catalog可以部署在任一支持网元生命周期编排的网管系统中，包括但不限于NFVO、VNFM、网元管理(Element Management，简称为EM)等。
利用Kubernets提供的自定义资源(Custom Resources，简称为CR)机制，对Kubernets的标准应用编程接口(Application Programming Interface，简称为API)进行二次开发扩展，CNF中所有容器资源或者特殊的资源类型均通过自定义资源CR进行定义，并形成CRD。
对CNF的容器管理引入CNF Operator组件，该组件基于Kubernets标准的自定义控制器(Custom Controller)框架实现，部署在CISM的控制节点中，可以不同网元类型公用相同的CNF Operator，或者各自提供不同的CNF Operator。
对CNF引入CNF包模型规范，CNF包中的Chart包文件由网元自定义，Catalog组件提供CNF包的导入和查询等管理功能。
在CNF部署前的准备阶段，Catalog中需导入CNF包并保存。
在CNF的部署阶段，CNFM使用Kubernets包工具Helm创建CNF Operator的Release，然后依次创建CNF包CR和CNF实例CR，触发CNF Operator监听到CR消息后下载CNF包文件，并使用CNF包的Chart文件部署CNF容器资源。
在CNF部署后的运维阶段，CNFM对CNF的升级、更新等生命周期操作，CNFM通过创建这些生命周期操作CR，触发CNF Operator监听到CR消息后执行对应的容器资源管理操作。
在CNF部署后的销毁阶段，CNFM依次删除CNF实例CR和CNF包CR，触发CNF Operator监听到CR消息后执行对应的CNF容器资源删除。
对于虚机容器形态或裸机容器形态的CNF，其容器资源的部署和管理，均可适用上述CNFM和CNF Operator的处理方式。
以上对CNF的管理过程，CNFM无需感知不同CISM平台的差异，CNFM与CISM之间只有标准的Kubernets API接口以及基于CR的API扩展接口，这些接口与CISM平台类型无关。
本实施例在网络管理系统NFVO中引入CNFM服务。CNFM协同目录管理服务Catalog，完成CNF网元的Chart包管理和生命周期管理功能。对于其它网络管理系统比如VNFM、EM等，也可部署CNFM和Catalog服务进行CNF网元管理，本实施例不做限定。
本实施例在云原生网络功能CNF中引入CNF Operator控制器。对于通用类型的CNF，可以公用相同CNF Operator；对于特定类型的CNF，可以定义特定的CNF Operator。每个CNF Operator部署在Kubernetes的主控节点上。图4是根据本实施例的功能组件的框图，如图4所示，包括：
Catalog：提供CNF网元的Chart版本包管理，包括导入、导出、查看等。
CNFM：提供CNF网元的生命周期管理，包括实例化、终止、更新、查看等。
API Server：Kubernetes的API网关，部署在Kubernetes的主控节点上，接收自定义资源CR的操作请求，向ETCD中写入CR数据。
CNF Operator：提供CNF网元的CR资源管理，部署在Kubernetes的主控节点上，监听Kubernetes的ETCD中CR记录的变更，执行对应的CR资源操作，比如调用Kubernetes接口部署CNF的各个Pod容器。
图5是根据本实施例的CNF生命周期管理阶段的流程图，如图5所示，包括：
1、在CNF部署阶段，用户先通过Catalog导入CNF包，再通过CNFM执行CNF实例化过程，部署CNF容器资源；
在CNF部署阶段，需要实施CNF容器资源的部署包括：
步骤1，用户在Catalog中导入CNF包；
步骤2，用户在CNFM服务中执行CNF实例化；
步骤3，CNFM从Catalog查询并获取CNF包；
步骤4，CNFM通过Helm创建CNF Operator的Release(对应上述第三创建请求)，此处复用Kubernets标准流程；
步骤5，CNFM下发创建CNF Package的CR消息(对应上述第一创建请求)给容器基础设施服务管理(Container Infrastructure Service Management，简称为CISM)的Kubernets API Server网关，通知CNF Operator下载CNF包文件；
步骤6，CNFM下发创建CNF Instance的CR消息(对应上述第二创建请求)给CISM的Kubernets API Server网关，通知CNF Operator完成CNF容器资源的部署；
步骤7，返回实例化结果。
2、在CNF运维阶段，用户在CNFM服务中执行CNF查询；
在CNF运维阶段，需要实施CNF查询：
步骤8，用户在CNFM服务中执行CNF查询；
步骤9，CNFM下发查询CNF Instance的CR消息(对应上述第一查询消息)给CISM的Kubernets API Server网关，通知CNF Operator完成CNF实例信息的查询，此处为新增流程；
步骤10，CNFM下发查询CNF Package的CR消息(对应上述第二查询消息)给CISM的Kubernets API Server网关，通知CNF Operator完成CNF包信息的查询；
步骤11，返回查询结果。
3、在CNF运维阶段，用户通过Catalog导入新的CNF包，再通过CNFM执行CNF实例更新或者升级，更新CNF容器资源；
在CNF运维阶段，需要实施CNF容器资源的更新或升级：
步骤12，用户在Catalog中导入新的CNF包，或者对已有CNF包更新；
步骤13，用户在CNFM服务中执行CNF更新或者升级；
步骤14，CNFM从Catalog查询并获取CNF包；
步骤15，CNFM下发更新CNF Package的CR消息(对应上述第一更新消息)给CISM的Kubernets API Server网关，通知CNF Operator下载新的CNF包文件；
步骤16，CNFM下发更新CNF Instance的CR消息(对应上述第二更新消息)给CISM的 Kubernets API Server网关，通知CNF Operator完成CNF容器资源的更新或升级；
步骤17，返回更新结果；
4、在CNF销毁阶段，用户通过CNFM执行CNF终止，销毁CNF容器资源。
在CNF销毁阶段，需要实施CNF容器资源的释放或删除：
步骤18，用户在CNFM服务中执行CNF终止；
步骤19，CNFM下发删除CNF Instance的CR消息(对应上述第一删除消息)给CISM的Kubernets API Server网关，通知CNF Operator完成CNF容器资源的释放或删除；
步骤20，CNFM下发删除CNF Package的CR消息(对应上述第二更新消息)给CISM的Kubernets API Server网关，通知CNF Operator删除CNF包文件；
步骤21，返回终止结果。
上述的CNF实例化、CNF更新、CNF终止流程，各个子步骤的操作顺序可以根据实际场景进行裁剪、调整或者合并，在此不再逐一列举。
对于除了CNF实例化、CNF更新、CNF终止、CNF查询以外的其他生命周期操作流程，本公开没有列举描述。对于引入Operator进行CNF容器资源管理的场景，不论是哪类生命周期操作，均遵循以下原则：资源部署时，优先部署CNF Operator或者利用已存在的公用CNF Operator，再通过CNF Operator部署或者管理CNF的容器资源；资源删除时，优先通过CNF Operator删除或者释放CNF的容器资源，再删除网元自身的CNF Operator或者保留公用的CNF Operator。
根据本公开的另一个实施例，还提供了一种网元管理装置，图6是根据本公开实施例的网元管理装置的框图，如图6所示，所述装置包括：
第一部署模块62，设置为在K8s系统的主控节点上部署云原生网络功能操控器CNF Operator；
第二部署模块64，设置为在网管系统中部署云原生网络功能管理CNFM与目录仓库Catalog；
管理模块66，设置为在所述CNF Operator的协同下，通过所述CNFM与所述Catalog对CNF网元进行管理。
在一实施例中，所述管理模块66包括：
部署子模块，设置为在所述CNF Operator的协同下，通过所述CNFM与所述Catalog对所述CNF网元的容器资源进行部署；
查询子模块，设置为在所述CNF Operator的协同下，通过所述CNFM对所述CNF网元信息进行查询；
更新子模块，设置为在所述CNF Operator的协同下，通过所述CNFM与所述Catalog对所述CNF网元的容器资源进行更新；
销毁子模块，设置为在所述CNF Operator的协同下，通过所述CNFM对所述CNF网元的容器资源进行销毁。
在一实施例中，所述部署子模块，还设置为通过所述CNFM向所述CNF Operator发送创建CNF包的第一创建请求，以指示所述CNF Operator从所述Catalog中下载所述CNF包；通过所述CNFM向所述CNF Operator发送创建CNF实例的第二创建请求，以指示所述CNF  Operator根据所述CNF包创建所述CNF实例，以完成所述CNF容器资源的部署。
在一实施例中，所述装置还包括：
第一创建子模块，设置为通过所述CNFM向所述CISM发送创建所述CNF Operator的实例的第三创建请求，通过所述CISM创建所述CNF Operator的实例。
在一实施例中，所述查询子模块，还设置为通过所述CNFM向所述CISM下发查询CNF实例的第一查询消息，通过所述CISM将所述第一查询消息发送给所述CNF Operator，以指示所述CNF Operator完成所述CNF实例的查询；通过所述CNFM向所述CISM下发查询CNF包的第二查询消息，通过所述CISM将所述第二查询消息发送给所述CNF Operator，以指示所述CNF Operator完成所述CNF包的查询。
在一实施例中，所述更新子模块，还设置为通过所述CNFM向容器基础设施服务管理CISM下发更新CNF包的第一更新消息，通过所述CISM将所述第一更新更新消息发送给所述CNF Operator，以指示所述CNF Operator从所述Catalog中下载新的CNF包；通过所述CNFM向CISM下发更新CNF实例的第二更新消息，通过所述CISM将所述第二更新消息发送给所述CNF Operator，以指示所述CNF Operator根据所述新的CNF包更新CNF实例，以完成所述CNF容器资源的更新。
在一实施例中，所述销毁子模块，还设置为通过所述CNFM向CISM下发删除CNF实例的第一删除消息，通过所述CISM将所述第一删除消息发送给所述CNF Operator，以指示所述CNF Operator删除所述CNF实例；通过所述CNFM向所述CISM下发删除CNF包的第二删除消息，通过所述CISM将所述第二删除消息发送给所述CNF Operator，以指示所述CNF Operator删除所述CNF包，以完成所述CNF容器资源的释放或删除。
在一实施例中，所述第二部署模块64，还设置为在网管系统的网络功能虚拟化编排器NFVO、虚拟网络功能管理器VNFM或网元管理EM中部署所述CNFM和所述目录仓库Catalog。
在一实施例中，所述装置还包括：
编排模块，设置为在所述网管系统的NFVO中部署所述CNFM的情况下，通过所述NFVO协同所述CNFM、容器基础设施管理器CISM，对容器网络功能CNF网元的容器资源进行编排；和/或
上报模块，设置为通过所述NFVO对接运营支撑系统OSS，并向所述OSS上报所述CNF网元的容器资源的配置数据、性能数据及告警数据。
本公开的实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序，其中，该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
在一个示例性实施例中，上述计算机可读存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本公开的实施例还提供了一种电子装置，包括存储器和处理器，该存储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
在一个示例性实施例中，上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
本实施例中的具体示例可以参考上述实施例及示例性实施方式中所描述的示例，本实施 例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本公开的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开不限制于任何特定的硬件和软件结合。
以上所述仅为本公开的优选实施例而已，并不用于限制本公开，对于本领域的技术人员来说，本公开可以有各种更改和变化。凡在本公开的原则之内，所作的任何修改、等同替换、改进等，均应包含在本公开的保护范围之内。

Claims (12)

  1. 一种网元管理方法，所述方法包括：
    在K8s系统的主控节点上部署云原生网络功能操控器CNF Operator；
    在网管系统中部署云原生网络功能管理CNFM与目录仓库Catalog；
    在CNF Operator的协同下，通过所述CNFM与所述Catalog对CNF网元进行管理。
  2. 根据权利要求1所述的方法，其中，在所述CNF Operator的协同下，通过所述CNFM与所述Catalog对CNF网元进行管理包括：
    在所述CNF Operator的协同下，通过所述CNFM与所述Catalog对所述CNF网元的CNF容器资源进行部署；
    在所述CNF Operator的协同下，通过所述CNFM与所述Catalog对所述CNF容器资源进行查询；
    在所述CNF Operator的协同下，通过所述CNFM与所述Catalog对所述CNF容器资源进行更新；
    在所述CNF Operator的协同下，通过所述CNFM对所述CNF容器资源进行销毁。
  3. 根据权利要求2所述的方法，其中，在所述CNF Operator的协同下，通过所述CNFM与所述Catalog对所述CNF网元的CNF容器资源进行部署包括：
    通过所述CNFM向所述CNF Operator发送创建CNF包的第一创建请求，以指示所述CNF Operator从所述Catalog中下载所述CNF包；
    通过所述CNFM向所述CNF Operator发送创建CNF实例的第二创建请求，以指示所述CNF Operator根据所述CNF包创建所述CNF实例，以完成所述CNF容器资源的部署。
  4. 根据权利要求3所述的方法，其中，在通过所述CNFM向所述CNF Operator发送创建CNF包的第一创建请求之前，所述方法还包括：
    通过所述CNFM向容器基础设施服务管理CISM发送创建所述CNF Operator的实例的第三创建请求，通过所述CISM创建所述CNF Operator的实例。
  5. 根据权利要求2所述的方法，其中，在所述CNF Operator的协同下，通过所述CNFM对所述CNF进行查询包括：
    通过所述CNFM向容器基础设施服务管理CISM下发查询CNF实例的第一查询消息，通过所述CISM将所述第一查询消息发送给所述CNF Operator，以指示所述CNF Operator完成所述CNF实例的查询；
    通过CNFM向所述CISM下发查询CNF包的第二查询消息，通过所述CISM将所述第二查询消息发送给所述CNF Operator，以指示所述CNF Operator完成所述CNF包的查询。
  6. 根据权利要求2所述的方法，其中，在所述CNF Operator的协同下，通过所述CNFM与所述Catalog对所述CNF容器资源进行更新包括：
    通过所述CNFM向容器基础设施服务管理CISM下发更新CNF包的第一更新消息，通过所述CISM将所述第一更新更新消息发送给所述CNF Operator，以指示所述CNF Operator从所述Catalog中下载新的CNF包；
    通过所述CNFM向CISM下发更新CNF实例的第二更新消息，通过所述CISM将所述第二更新消息发送给所述CNF Operator，以指示所述CNF Operator根据所述新的CNF包更新CNF 实例，以完成所述CNF容器资源的更新。
  7. 根据权利要求2所述的方法，其中，在所述CNF Operator的协同下，通过所述CNFM对所述CNF容器资源进行销毁包括：
    通过所述CNFM向容器基础设施服务管理CISM下发删除CNF实例的第一删除消息，通过所述CISM将所述第一删除消息发送给所述CNF Operator，以指示所述CNF Operator删除所述CNF实例，以完成所述CNF容器资源的释放或删除；
    通过所述CNFM向所述CISM下发删除CNF包的第二删除消息，通过所述CISM将所述第二删除消息发送给所述CNF Operator，以指示所述CNF Operator删除所述CNF包。
  8. 根据权利要求1所述的方法，其中，在网管系统中部署云原生网络功能管理CNFM与目录仓库Catalog包括：
    在网管系统的网络功能虚拟化编排器NFVO、虚拟网络功能管理器VNFM或网元管理EM中部署所述CNFM和所述目录仓库Catalog。
  9. 根据权利要求8所述的方法，其中，所述方法还包括：
    在所述网管系统的NFVO中部署所述CNFM的情况下，通过所述NFVO协同所述CNFM、容器基础设施管理器CISM，对容器网络功能CNF网元的容器资源进行编排；和/或
    通过所述NFVO对接运营支撑系统OSS，并向所述OSS上报所述CNF网元的容器资源的配置数据、性能数据及告警数据。
  10. 一种网元管理装置，所述装置包括：
    第一部署模块，设置为在K8s系统的主控节点上部署云原生网络功能操控器CNF Operator；
    第二部署模块，设置为在网管系统中部署云原生网络功能管理CNFM与目录仓库Catalog；
    管理模块，设置为在CNF Operator的协同下，通过所述CNFM与所述Catalog对CNF网元进行管理。
  11. 一种计算机可读的存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行所述权利要求1至9任一项中所述的方法。
  12. 一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行所述权利要求1至9任一项中所述的方法。
PCT/CN2023/117055 2022-09-30 2023-09-05 网元管理方法、装置、存储介质及电子装置 WO2024066965A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211214733.6 2022-09-30
CN202211214733.6A CN117857283A (zh) 2022-09-30 2022-09-30 网元管理方法、装置、存储介质及电子装置

Publications (1)

Publication Number Publication Date
WO2024066965A1 true WO2024066965A1 (zh) 2024-04-04

Family

ID=90475996

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/117055 WO2024066965A1 (zh) 2022-09-30 2023-09-05 网元管理方法、装置、存储介质及电子装置

Country Status (2)

Country Link
CN (1) CN117857283A (zh)
WO (1) WO2024066965A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112698917A (zh) * 2020-12-31 2021-04-23 武汉达梦数据技术有限公司 一种基于容器化的PaaS平台网络架构及其实现方法
US20220021538A1 (en) * 2017-09-13 2022-01-20 Vijay Madisetti Blockchain token-based cloud orchestration architecture for discrete virtual network instances
US20220035650A1 (en) * 2020-07-30 2022-02-03 Vmware, Inc. System and method for distributed orchestration management in network function virtualization
CN114925141A (zh) * 2022-07-21 2022-08-19 南京智人云信息技术有限公司 一种基于区块链的云原生自动化部署管理系统及方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220021538A1 (en) * 2017-09-13 2022-01-20 Vijay Madisetti Blockchain token-based cloud orchestration architecture for discrete virtual network instances
US20220035650A1 (en) * 2020-07-30 2022-02-03 Vmware, Inc. System and method for distributed orchestration management in network function virtualization
CN112698917A (zh) * 2020-12-31 2021-04-23 武汉达梦数据技术有限公司 一种基于容器化的PaaS平台网络架构及其实现方法
CN114925141A (zh) * 2022-07-21 2022-08-19 南京智人云信息技术有限公司 一种基于区块链的云原生自动化部署管理系统及方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SHI TINGXIANG, XU FALU; ZHANG LU: "Evolution Solution for Container-Based 5G Telecom Cloud Network", ZTE TECHNOLOGY JOURNAL, ZTE CORPORATION, CN, vol. 27, no. 6, 31 December 2021 (2021-12-31), CN , pages 58 - 64, XP093151489, ISSN: 1009-6868, DOI: 10.12142/ZTETJ.202106011 *

Also Published As

Publication number Publication date
CN117857283A (zh) 2024-04-09

Similar Documents

Publication Publication Date Title
CN108683516A (zh) 一种应用实例的升级方法、装置和系统
US10447703B2 (en) VNF package operation method and apparatus
WO2018166398A1 (zh) 一种nfv网络中许可证的管理系统
US20140237373A1 (en) Method of provisioning a cloud-based render farm
TWI771927B (zh) 網路服務構築系統及網路服務構築方法
US20190363924A1 (en) Bulk creation of managed functions in a network that includes virtualized network function
US8650288B2 (en) Runtime usage analysis for a distributed policy enforcement system
CN109120444B (zh) 云资源管理方法、处理器以及存储介质
US20220413937A1 (en) Node management method, device and apparatus, storage medium, and system
EP3883183A1 (en) Virtualization management method and device
US11740886B2 (en) Algorithm update method and apparatus
WO2016026329A1 (zh) 终端的升级方法及装置
CN111984271A (zh) 一种区块链应用程序处理方法、装置及区块链应用系统
CN113676537A (zh) 一种异构云资源统一管理平台
CN104598525B (zh) 一种应用复制方法、设备及系统
CN112583630B (zh) 设备管理方法、装置、系统、设备及存储介质
WO2022062661A1 (zh) 操作通知方法和装置、存储介质和电子装置
JP2004535626A (ja) データおよび／またはサービスのダイナミックな配信のためのシステムおよび方法
CN111078348A (zh) 一种界面管理方法、装置、设备和存储介质
WO2024066965A1 (zh) 网元管理方法、装置、存储介质及电子装置
WO2021245447A1 (en) Stable references for network function life cycle management automation
CN116724543A (zh) 容器集群的管理方法和装置
CN103533071A (zh) 终端软件的更新方法、装置及系统
US20190028880A1 (en) Method for accessing context data by network service component, apparatus, and system
US11436377B2 (en) Secure workload image distribution and management

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23870204

Country of ref document: EP

Kind code of ref document: A1