WO2018045540A1 - Procédé de gestion du cycle de vie, et unité de gestion - Google Patents

Procédé de gestion du cycle de vie, et unité de gestion Download PDF

Info

Publication number
WO2018045540A1
WO2018045540A1 PCT/CN2016/098486 CN2016098486W WO2018045540A1 WO 2018045540 A1 WO2018045540 A1 WO 2018045540A1 CN 2016098486 W CN2016098486 W CN 2016098486W WO 2018045540 A1 WO2018045540 A1 WO 2018045540A1
Authority
WO
WIPO (PCT)
Prior art keywords
instance
management unit
target
vnfd
vnf
Prior art date
Application number
PCT/CN2016/098486
Other languages
English (en)
Chinese (zh)
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 华为技术有限公司
Priority to PCT/CN2016/098486 priority Critical patent/WO2018045540A1/fr
Publication of WO2018045540A1 publication Critical patent/WO2018045540A1/fr

Links

Images

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a lifecycle management method and a management unit.
  • NFV technology is based on massive and normalized servers and switches, and implements various network functions (such as virtual operations, virtual wide area networks, and virtual application access routers) through software to reduce costs and accelerate service deployment and resource flexibility. , build an innovative ecological chain.
  • a computer is virtualized into multiple virtual logical computers, namely virtual machines (VMs).
  • VMs virtual machines
  • a virtual machine generally uses a server physical network port, a virtual network card, and a virtual switch connected to the switch in the chassis or the top switch to perform data communication with the outside of the server.
  • NFV technology By borrowing the information technology (Information Technology, IT) virtualization technology, NFV technology enables many types of network devices to be incorporated into industry standards. For example, network devices such as services, switching, and storage can be deployed in data centers or network nodes. . NFV technology implements various network functions in software and can run these network functions on industry-standard servers. It can also migrate, instantiate, redeploy, etc. these network functions as needed, and does not need to install new ones. device of. That is, the virtualized network function (VNF) can be generated by the NFV technology. Network Service (NS) can be implemented between multiple VNFs.
  • VNFD Virtualized Network Function Descriptor
  • the Network Service Descriptor is a template for describing the deployment and maintenance of the NS, including the service topology (the various components of the VNF and the relationship between them, the virtual link, the VNF forwarding map), and the various network services.
  • the NSD includes descriptors such as VNFD, VNF forwarding map descriptors, virtual link descriptors, and physical network function descriptors.
  • NFV Orchestrator (NFVO) unit often needs to undergo a conditional filtering process with multiple parameters and an additional search process when implementing NS lifecycle management. Strategic parameter screening process, etc., to obtain suitable examples. This makes the lifecycle management process more complicated and less efficient.
  • the embodiment of the invention provides a lifecycle management method and a management unit to streamline the lifecycle management process and improve processing efficiency.
  • an embodiment of the present invention provides a lifecycle management method, where the method includes: a first management unit receives a lifecycle management request of a target NS from a second management unit, where the lifecycle management request includes a target NSD ID; The management unit searches for the target NSD according to the target NSD ID, where the target NSD includes an instance identifier, or the target NSD includes an instance identifier and a virtual network function descriptor identifier VNFD ID, and the instance identifier and/or VNFD ID is used to determine the life cycle of the target NS. The required instance is managed; the first management unit performs lifecycle management on the target NS according to the instance identifier and/or VNFD ID included in the target NSD.
  • the target NSD includes an instance identifier, or includes an instance identifier and a VNFD ID.
  • the first management unit searches for a corresponding instance according to the content included in the target NSD, thereby performing lifecycle management on the target NS, without condition filtering, additional process searching, and Processes such as strategic parameter filtering to streamline the lifecycle management process, improve the speed of finding VNF instances, and improve processing efficiency.
  • the target NSD includes a VNFD ID, and the lifecycle management of the target NS may be performed according to the VNFD ID if the lifecycle management of the target NS cannot be performed according to the instance identifier.
  • the foregoing instance identifier is one or more sets of instance identifiers, and the number of VNFD IDs may be the same as or different from the number of groups of the instance identifiers.
  • the foregoing instance identifier includes at least one of the following: a VNF instance identifier, a physical network function PNF instance identifier, a virtual network function forwarding map, a VNFFG instance identifier, a network function path NFP instance identifier, and a virtual link VL instance identifier.
  • NS instance ID or service access point SAP instance ID Each instance identifier may be used to identify a corresponding instance.
  • the VNF instance identifier is used to identify the VNF instance, and the instance identified by the instance identifier may exist in the network architecture, so that the corresponding instance is directly searched according to the instance identifier, thereby improving processing efficiency. .
  • the foregoing instance identifier includes multiplexing indication information, where the multiplexing indication information is used to indicate whether the instance identified by the instance identifier can be multiplexed by at least two NSs.
  • the multiplexing indication information may be a field, and the value of the field may indicate the real identifier identified by the instance identifier.
  • a VNFFG instance identifier includes the field, the field indicates that the VNFFG instance identifier identified by the VNFFG instance identifier can be multiplexed by at least two NSs, and the other NSs are in lifecycle management.
  • the process can directly call VNFFG instance 1, streamlining the lifecycle management process.
  • the example identified by the foregoing instance identifier includes multiplexing indication information, where the multiplexing indication information is used to indicate whether an instance can be multiplexed by at least two NSs.
  • the optional multiplexing indication information may be a certain field in the instance, which may indicate whether the instance can be multiplexed by at least two NSs. For example, if the VNF instance 1 identified by a VNF instance identifier includes the field, the other NS can directly invoke the VNF instance 1 in the lifecycle management process to streamline the lifecycle management process.
  • the VNFD identified by the VNFD ID includes multiplexing indication information, where the multiplexing indication information is used to indicate whether the VNF instance corresponding to the VNFD can be multiplexed by at least two NSs.
  • the VNF instance corresponding to the VNFD identified by the VNFD ID includes multiplexing indication information, where the multiplexing indication information is used to indicate whether the VNF instance can be multiplexed by at least two NSs.
  • the first management unit may further receive an upload request of the target NSD from the second management unit, and upload the target NSD.
  • the upload request may include content included in the target NSD.
  • the first management unit may further check whether the upload request is valid, and may verify whether the instance identified by the instance identifier included in the upload request exists in a network architecture. Checking whether the upload request is valid, if it exists in the network architecture, confirming that the upload request is valid; and verifying whether the upload request is valid by checking the multiplexing indication information included in the instance identifier included in the upload request, That is, it is detected whether the instance identified by the instance identifier is allowed to be multiplexed by at least two NSs to check whether the upload request is valid, and if it is allowed to be multiplexed by at least two NSs, it is confirmed that the upload request is valid.
  • the first management unit uploads the target NSD.
  • the first management unit may further send a confirmation upload information to the second management unit after uploading the target NSD, and notify the second management unit that the target NSD has been uploaded.
  • the first management unit may further receive a modification request for the target NSD from the second management unit, modify the target NSD, upload the modified target NSD, and update the target. NSD.
  • the first management unit may further check whether the modification request is valid, and may verify whether the instance identified by the instance identifier added or updated by the modification request exists. Checking whether the modification request is valid in the network architecture, if it exists in the network architecture, confirming that the modification request is valid; or verifying the multiplexing indication information included in the instance identifier added or updated by the modification request to verify Whether the modification request is valid, that is, whether the instance identified by the added or updated instance identifier is allowed to be checked by at least two NSs to verify whether the modification request is valid, and if it is allowed to be called by at least two NSs, the modification request is confirmed. effective.
  • the first management unit modifies the target NSD and uploads the modified target NSD.
  • the first management unit may further send confirmation modification information to the second management unit to notify the second management unit that the target NSD has been modified.
  • the foregoing lifecycle management request may be an instantiation request for requesting to instantiate the target NS; or the lifecycle management request may be an update request for requesting the update target NS.
  • the first management unit may determine whether the instance identifier includes the VNF instance identifier, so that the target NS is performed according to the VNF instance corresponding to the VNF instance identifier. Lifecycle management.
  • the first management unit acquires the VNF instance corresponding to the VNF instance identifier, and obtains the VNF instance according to the obtained VNF instance. Identify the corresponding VNF instance to perform lifecycle management on the target NS. In this manner, the lifecycle management can be performed according to the VNF instance corresponding to the VNF instance identifier, and the lifecycle management process is simplified, and the processing efficiency is improved.
  • the first management unit searches for the VNFD ID according to the VNFD ID included in the target NSD. Match the VNF instance and perform lifecycle management on the target NS according to the VNF instance matching the VNFD ID. This method can find a VNF instance that matches the VNFD ID according to the VNFD ID, and can fully utilize the VNF instance in the network architecture to improve resource utilization.
  • the first management unit is matched according to the VNFD ID. Before the VNF instance performs lifecycle management on the target NS, it may also be determined whether the number of VNF instances matching the VNFD ID is equal to a preset threshold. The number of VNF instances that match the VNFD ID may be large, but the number required for actual lifecycle management is a preset threshold, so determining whether it is equal to a preset threshold can ensure smooth lifecycle management.
  • the first management unit may perform lifecycle management on the target NS according to all instances of the VNF instance matching the VNFD ID. .
  • the first management unit may select an instance of the VNF that is equal to the preset threshold, so that lifecycle management can be smoothly performed. Increase the autonomy of the first management unit; or, the first management unit may send a selection request to the second management unit, the selection request is used to instruct the second management unit to select an equal number of VNF instances as the preset threshold, so that the first management The unit performs lifecycle management on the target NS according to the selected VNF instance.
  • the target NSD may further include a new virtual network function forwarding map VNFFG instance identifier and a new VNFD ID, and the first management unit is configured according to the instance.
  • the process of lifecycle management of the target NS by the identifier and/or VNFD ID may be: the first management unit searches for a VNF instance matching the new VNFD ID according to the new VNFD ID; and according to the VNF matching the new VNFD ID
  • the instance and the new VNFFG instance identify the corresponding VNFFG instance update target NS.
  • the target NS is updated by updating the VNF instance and the connection relationship of the VNF instance, without re-instantiation, saving operation steps and improving processing efficiency.
  • a confirmation update message may also be sent to the second management unit to notify the second management unit that the target NS has been updated.
  • the embodiment of the present invention provides a management device, which can implement the functions performed by the first management unit in the foregoing method instance, and the functions can be implemented by using hardware or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the apparatus includes a processor and a communication interface configured to support the apparatus to perform corresponding functions in the above methods.
  • the communication interface is used to support communication between the device and other network elements.
  • the device may also include a memory for processing and processing The device is coupled, which holds the necessary program instructions and data for the device.
  • the embodiment of the present invention provides another management device, which can implement the functions performed by the second management unit in the foregoing method instance, and the functions can be implemented by hardware or by executing corresponding software through hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the apparatus includes a processor and a communication interface configured to support the apparatus to perform corresponding functions in the above methods.
  • the communication interface is used to support communication between the device and other network elements.
  • the apparatus can also include a memory for coupling with the processor that retains the program instructions and data necessary for the apparatus.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions used by the first management unit, which includes a program designed to perform the above aspects.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions used by the second management unit, which includes a program designed to perform the above aspects.
  • an embodiment of the present invention provides a communication system, where the system includes the first management unit and the second management unit described in the foregoing aspects.
  • the lifecycle management request of the target NS is received by the first management unit from the second management unit, where the lifecycle management request includes the target NSD ID; the first management unit searches for the target NSD according to the target NSD ID, the target The NSD includes an instance identifier, or the target NSD includes an instance identifier and a VNFD ID, and performs lifecycle management on the target NS according to the instance identifier and/or VNFD ID included in the target NSD. Therefore, the solution of the embodiment of the present invention can implement lifecycle management according to the instance identifier and/or the VNFD ID included in the NSD, and does not require filtering, screening, and the like, thereby streamlining the lifecycle management process and improving processing efficiency.
  • FIG. 1 is a schematic diagram of a possible network architecture according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of communication of a lifecycle management method according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of communication of uploading an NSD according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of communication of updating an NSD according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of a first management unit according to an embodiment of the present disclosure.
  • FIG. 5B is a schematic structural diagram of another first management unit according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of a second management unit according to an embodiment of the present disclosure.
  • FIG. 6B is a schematic structural diagram of another second management unit according to an embodiment of the present invention.
  • the network architecture and the service scenario described in the embodiments of the present invention are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present invention, and are not limited to the technical solutions provided by the embodiments of the present invention.
  • the technical solutions provided by the embodiments of the present invention are equally applicable to similar technical problems.
  • the NFV-based network architecture mainly includes: Operation Support System (OSS)/Business Support System (BSS), Element/Network Management System (E). /NMS), Virtualized Network Function (VNF) unit, NFV Infrastructure (NFVI) unit, NFV Orchestrator (NFVO) unit, Virtualized Network Function Management (VNF Manager, VNFM) A unit and a virtualized infrastructure manager (VIM) unit, wherein the network element/network management system may also be referred to as a network management system, and the network function virtualization scheduling unit may be referred to as a network function virtualization orchestration unit.
  • the corresponding unit may be described by the abbreviation of each unit, for example, the network function virtualization infrastructure unit may be described as an NFVI or NFVI unit. The following is a brief introduction to the above units:
  • OSS/BSS is a support system for the integration and information resource sharing of telecom operators. It is mainly composed of network management, system management, billing, business, accounting and customer services, while the system passes through a unified information bus. Organically integrated. OSS/BSS can help operators determine the development direction of the system while helping them to develop their own operational support systems. It can also help users to formulate system integration standards and improve and improve users' business levels. The OSS/BSS is used in the NFV-based network architecture to make necessary modifications and adjustments to the lifecycle management (eg, instantiation, etc.) of each network element.
  • the E/NMS is a network management system of a traditional CT telecommunication network element and can manage one or more VNFs.
  • NFVI unit can be used to host and connect virtual functions, is a kind of server, virtualization management Cloud data centers for programs (such as hypervisors), operating systems, virtual machines, virtual switches, and network resources.
  • An NFVI unit can be deployed across several physical sites, such as data center operations, where the network that provides data connectivity to these physical sites is also considered part of the NFVI unit.
  • the NFVO unit can be used to manage the life cycle of the NS, coordinate the lifecycle management of the NS, coordinate the lifecycle management of the VNF (requires support from the VNFM), and coordinate the management of various resources of the NFVI unit (requires VIM support) to ensure Optimized configuration of all types of resources and connections required.
  • lifecycle management refers to the management of instantiation, update, maintenance, and termination of VNF units or NS units.
  • the VNFM unit is responsible for the lifecycle management of the VNF.
  • the VIM unit is responsible for controlling and managing the computing resources, storage resources, and network resources of the NFVI unit.
  • the VIM can be deployed to the infrastructure domain of the underlying network operator (eg, NFVI access point/service offering point).
  • vendor-configured NSDs include VNFD, Virtualized Network Function Forwarding Graph Descriptor (VNFFGD), Virtualized Link Descriptor (VLD), and Physical Network Function Descriptor (Physics Network Function Descriptor, PNFD) and other descriptors.
  • VNFFGD Virtualized Network Function Forwarding Graph Descriptor
  • VLD Virtualized Link Descriptor
  • PNFD Physical Network Function Descriptor
  • the lifecycle management of the NS can be implemented by creating a VNF instance. The specific process is: the NFVO receives an instantiation request for the target NS sent by the OSS/BSS, and the instantiation request includes the target NSD of the target NS. ID, NFVO finds the target NSD according to the target NSD ID.
  • the target NSD includes multiple sets of instance requirement information, and each set of instance requirement information in the plurality of sets of instance requirement information includes descriptors such as VNFD, VNFFGD, VLD, PNFD, etc., and NFVO according to multiple sets of instance requirements
  • the information sends an instantiation request to the VNFM, and the VNFM instantiates a plurality of VNF instances according to the plurality of sets of instance requirement information.
  • the VNF instances exist in the network architecture shown in FIG.
  • the network architecture shown in FIG. 1 includes other examples, such as virtualized link (VL) instances, etc., which can exist stably in the network architecture for a long time, and in these examples.
  • VL virtualized link
  • Each instance may be called by the lifecycle management of multiple NSs.
  • MME Mobility Management Entity
  • S-GWs Serving-GateWays
  • the lifecycle management of the NS can also be implemented by searching for the required instance of the NS instantiation.
  • the specific process is: the NFVO receives the instantiation request for the target NS sent by the OSS/BSS, and the instantiation is performed.
  • the request includes the target NSD ID of the target NS, and the NFVO searches for the target NSD according to the target NSD ID, where the target NSD includes multiple sets of instance requirement information, and each set of instance requirement information in the plurality of sets of instance requirement information includes descriptors such as VNFD, VNFFGD, VLD, and PNFD.
  • the NFVO finds the VNF instance matching the instance requirement information in the network architecture according to the multiple sets of instance requirement information, thereby realizing the instantiation of the target NS.
  • VNFD descriptors
  • conditional filtering, additional discovery processes, and strategic parameter filtering select one instance from multiple instances, resulting in a complex lifecycle management process that takes a long time and affects processing efficiency.
  • an embodiment of the present invention provides a lifecycle management method, and a first management unit, a second management unit, and a system based on the method, to streamline the lifecycle management process and improve processing efficiency.
  • the first management unit receives a lifecycle management request of the target NS from the second management unit, the lifecycle management request includes a target NSD ID; the first management unit searches for the target NSD according to the target NSD ID, the target NSD includes an instance The identifier, or the target NSD includes an identifier and a VNFD ID, the instance identifier and/or the VNFD ID is used to determine an instance required for lifecycle management of the target NS; the first management unit performs the target NS according to the instance identifier and/or the VNFD ID Lifecycle management.
  • the instance identifier and/or the VNFD ID included in the target NSD is used to determine an instance required for lifecycle management of the target NS, and the first management unit can implement the target NS according to the instance identifier and/or the VNFD ID.
  • Lifecycle management which not only makes full use of the examples in the network architecture, but also streamlines the lifecycle management process and improves processing efficiency.
  • the lifecycle management of the target NS may be to instantiate the target NS, that is, to instantiate one or more VNF instances required by the target NS; and to perform lifecycle management on the target NS may also update the target NS.
  • the first management unit is one end that receives the lifecycle management request, and may be, for example, the NFVO unit in FIG. 1;
  • the second management unit is one end that sends a lifecycle management request, and may be, for example, the one in FIG. OSS/BSS.
  • the solution of the embodiment of the present invention can be applied to the NFV-based network architecture shown in FIG. 1.
  • the solution of the embodiment of the present invention can simplify the lifecycle management process and improve processing efficiency.
  • FIG. 2 shows a lifecycle management method provided by an embodiment of the present invention.
  • the method shown in Figure 2 It can be applied to the network architecture shown in FIG. 1, wherein the first management unit can be an NFVO unit, and the second management unit can be an OSS/BSS.
  • the second management unit determines the target NS, the target NSD, and the target NSD ID.
  • the target NS is an NS to be subjected to lifecycle management, and the target NSD and the target NSD ID are respectively an NSD and an NSD ID of the target NS.
  • the second management unit may determine the target NS, the target NSD, and the target NSD ID according to actual needs.
  • the target NSD is used to describe the deployment and maintenance of the target NS.
  • the target NSD ID is the identifier of the target NSD, which is used to distinguish the target NSD from other NSDs. Each NSD uniquely corresponds to an NSD ID, and the corresponding NSD can be found according to the NSD ID.
  • the second management unit may determine the content included in the target NSD when determining the target NS.
  • the target NSD may include an instance identifier that may be used to determine an instance required for lifecycle management of the target NS.
  • the instance identifier may include at least one of the following: a VNF instance identifier, a physical network function (PNF) instance identifier, a virtualized network function forwarding graph (VNFFG) instance identifier, and a network function path (Network Function Path) , NFP) instance ID, virtual link (VL) instance ID, NS instance ID, or Service Access Point (SAP) instance ID.
  • PNF physical network function
  • VNFFG virtualized network function forwarding graph
  • NFP network function path
  • VL virtual link
  • SAP Service Access Point
  • the VNF instance identifier is used to identify the VNF instance, and each VNF instance corresponds to a different VNF instance identifier.
  • the VNF instance identifier is the VNF instance ID
  • the PNF instance identifier is the PNF instance ID
  • the VNFFG instance identifier is the VNFFG instance ID
  • the VL instance identifier is the VL instance ID
  • the NS instance identifier is the NS instance ID
  • the SAP instance identifier is the SAP instance ID.
  • the foregoing instance identifier may be one or more sets of instance identifiers, where the set of instance identifiers may include a VNF instance identifier, a PNF instance identifier, a VNFFG instance identifier, an NFP instance identifier, a VL instance identifier, an NS instance identifier, or an SAP. At least one of the instance identifiers. It can be understood that a set of instance identifiers is used to indicate a VNF instance and a link interface instance of the VNF instance, such as a forwarding map instance, a virtual link instance, an access point instance, and the like. The specific content of a certain group of instance identifiers may be selected and entered by the planning design engineer of the network service or the network administrator of the second management unit.
  • the foregoing instance identifier includes multiplexing indication information, where the multiplexing indication information is used to indicate whether the instance identified by the instance identifier can be multiplexed by at least two NSs.
  • the multiplexing indication information may be a field, and the value of the field may indicate whether the instance identified by the instance identifier can be at least two NS multiplexing.
  • a certain VNFFG instance identifier includes the field, and the field indicates that the VNFFG instance ID identified by the VNFFG instance identifier can be multiplexed by at least two NSs, and the other NS can directly invoke the VNFFG instance 1 in the lifecycle management process to simplify the life cycle. Management process.
  • the second management unit determines whether each of the instance identifiers includes a field in which the corresponding instance can be multiplexed by at least two NSs, and the field may be served by a network administrator or network service of the second management unit. The planning and design engineer enters and the second management unit identifies it.
  • the instance identified by the example identifier includes multiplexing indication information, and the multiplexing indication information is used to indicate whether an instance can be multiplexed by at least two NSs.
  • the multiplexing indication information may be a certain field in the instance, which may indicate whether the instance can be multiplexed by at least two NSs. For example, if the VNF instance 1 identified by a VNF instance identifier includes the field, the other NS can directly invoke the VNF instance 1 in the lifecycle management process to streamline the lifecycle management process.
  • the target NSD can include a VNFD ID that can be used to determine the instances required for lifecycle management of the target NS.
  • the target NSD can include the above instance identification and the VNFD ID described above.
  • the lifecycle management of the target NS may be performed according to the instance identifier. If the lifecycle management of the target NS cannot be performed according to the foregoing instance identifier, the lifecycle management of the target NS may be performed according to the VNFD ID.
  • the virtual network function descriptor VNFD identified by the VNFD ID may include multiplexing indication information indicating whether the VNF instance corresponding to the VNFD can be multiplexed by at least two NSs.
  • the VNF instance corresponding to the VNFD identified by the VNFD ID includes multiplexing indication information indicating whether the VNF instance can be multiplexed by at least two NSs. Whether the above target NS includes the VNFD ID, and whether the VNFD includes the multiplexing indication information may be set by the network administrator of the second management unit or the planning design engineer of the network service.
  • the second management unit sends a lifecycle management request of the target NS to the first management unit, the lifecycle management request including the target NSD ID.
  • the second management unit may send a lifecycle management request of the target NS to the first management unit through a communication interface between the second management unit and the first management unit, the lifecycle management request including the target NSD ID.
  • the second management unit may carry the target NSD ID only in the life management request without carrying the content included in the target NSD in the lifecycle management request.
  • the prerequisite for such implementation is that the first management unit has uploaded the target NSD, that is, the first management unit has uploaded the content included in the target NSD and the target NSD.
  • the first management unit may upload the content included in the target NSD and the target NSD to the directory, where the directory may be a VNF service directory, a VNF directory, or a network shown in FIG. 1 in the network structure shown in FIG. Other directories in the structure are not limited herein.
  • the first management unit may also receive an upload request of the target NSD from the second management unit and upload the target NSD.
  • the upload request may be determined to be valid.
  • the first management unit may determine, according to the multiplexing indication information, that the upload request is valid.
  • the process of uploading the target NSD by the first management unit may refer to the manner shown in FIG. 3. For specific implementation, refer to the description in the following FIG.
  • the first management unit may further receive a modification request of the target NSD from the second management unit, where the modification request is used to request the first management unit to modify the target NSD, and then the first management unit modifies the target NSD and uploads the modification After the target NSD.
  • the modification request may be determined to be valid.
  • the first management unit may determine, according to the multiplexing indication information, that the modification request is valid.
  • the process of modifying the target NSD by the first management unit may refer to the manner shown in FIG. 4, and the specific implementation may be referred to the description in the following FIG.
  • the first management unit looks up the target NSD according to the target NSD ID, the target NSD includes an instance identifier, or the target NSD includes an instance identifier and a VNFD ID.
  • the first management unit looks up the target NSD according to the target NSD ID included in the lifecycle management request, the target NSD includes an instance identifier, or the target NSD includes an instance identifier and a VNFD ID.
  • the number of VNFD IDs may or may not be the same as the number of groups identified by the instance.
  • the first management unit searches the directory for the target NSD and the content included in the target NSD according to the target NSD ID.
  • the first management unit performs lifecycle management on the target NS based on the instance identification and/or the VNFD ID.
  • the first management unit performs a lifecycle management on the target NS according to the instance identification lookup instance.
  • the above lifecycle management request may be an instantiation request or an update request.
  • the first management unit may determine whether the instance identifier included in the target NSD includes the VNF instance identifier.
  • the instance identifier may be one or more sets of instance identifiers. Therefore, if the instance identifier is a set of instance identifiers, the first management unit determines whether the group instance identifier includes the VNF instance identifier; The instance identifier, the first management unit determines whether each group instance identifier includes a VNF instance identifier.
  • the first management unit may find or obtain the VNF instance corresponding to the VNF instance identifier, and instantiate the target NS according to the obtained VNF instance.
  • the instance identifier may be one or more groups of instance identifiers. Therefore, if the instance identifier is a set of instance identifiers, and the group instance identifier includes the VNF instance identifier, the first management unit searches for or obtains the VNF instance identifier.
  • the VNF instance if the instance identifier is a plurality of sets of instance identifiers, and each of the plurality of sets of instance identifiers includes the VNF instance identifier, the first management unit respectively searches for or obtains the VNF instance corresponding to each VNF instance identifier, and obtains the VNF instance according to the Multiple VNF instances instantiate the target NS.
  • the first management unit may look up the VNF instance that matches the VNFD ID according to the VNFD ID included in the target NSD.
  • the first management unit may search for a VNF instance that matches the VNFD ID in the existing VNF instance set, where the existing VNF instance set is a VNF instance set existing in the network architecture.
  • the instance identifier may be one or more groups of instance identifiers. Therefore, if the instance identifier is a group instance identifier, and the group instance identifier does not include the VNF instance identifier, the first management unit is configured according to the VNFD included in the target NSD.
  • the ID searches for a VNF instance that matches the VNFD ID; if the instance identifier is a plurality of sets of instance identifiers, and the plurality of sets of instance identifiers do not include the VNF instance identifier, the first management unit is configured according to each of the plurality of VNFD IDs included in the target NSD.
  • the VNFD ID looks for a VNF instance that matches each VNFD ID, respectively.
  • the process by which the first management unit performs lifecycle management on the target NS according to the VNF instance matching the VNFD ID may be:
  • the preset threshold may be 1 or 2 or other values; optionally, the preset threshold is 1, at the preset If the threshold value is 1, determining whether the number of VNF instances matching the VNFD ID is equal to a preset threshold, that is, determining whether the VNFD ID and the matching VNF instance have a one-to-one correspondence;
  • the first management unit performs lifecycle management on the target NS according to all instances of the VNF instance matching the VNFD ID;
  • the first management unit sends the VNFM unit to the VNFM unit. And instantiating the request, the instantiation request includes a VNFD ID, the instantiation request is used to request the VNFM unit to instantiate the VNF instance according to the VNFD ID, and feed back the VNF instance to the first management unit, where the first management unit targets the target NS according to the VNF instance.
  • the first management unit sends a selection request to the second management unit, where the selection request is used to indicate that the second management unit selects the same amount as the preset threshold.
  • the VNF instance, the selection request may include a VNFD ID and a VNF instance whose number matching the VNFD ID is greater than a preset threshold, and the engineer or network administrator of the second management unit selects and pre-selects from the VNF instance whose number is greater than a preset threshold.
  • the second management unit feeds back the selected VNF instance to the first management unit; or the first management unit autonomously selects the same number of preset VNF instances from the VNF instance that is greater than the preset threshold.
  • the VNF instance, the first management unit may perform lifecycle management on the target NS according to the VNF instance selected by itself or the second management unit.
  • the VNF instance selected by the second management unit or the first management unit is an optimal VNF instance.
  • the process of lifecycle management of the target NS by the first management unit according to the VNF instance matching the VNFD ID may include the foregoing “(2)”, “(3)” or “(4)” part, It is also possible to include the above-mentioned "(1)" portion on the basis of this.
  • the instance identifier is a group of instance identifiers, and some group instance identifiers include a VNF instance identifier, and some group instance identifiers do not include the VNF instance identifier
  • the instance identifiers including the VNF instance identifiers are searched according to the VNF instance identifiers.
  • the VNF instance corresponding to the VNF instance identifier is obtained.
  • the VNF instance matching the VNFD ID is searched or obtained according to the VNFD ID, thereby performing lifecycle management on the target NS.
  • the target NSD further includes a new VNFD ID and a new VNFFG instance identifier
  • the first management unit can match the new VNFD ID according to the new VNFD ID search.
  • the VNF instance may look up a VNF instance that matches the new VNFD ID in the existing VNF instance set. If the number of VNF instances matching the new VNFD ID is greater than the preset threshold, the second management unit or the first management unit selects an instance of the VNF that is equal to the preset threshold from the VNF instances whose number is greater than the preset threshold. .
  • the first management unit may update the target NS according to the VNF FF instance corresponding to the new VNFD ID and the new VNFFG instance identifier. For example, the first management unit may identify the VNF instance and the new VNFFG instance identity pair that match the new VNFD ID. The VNFFG instance should be written to the target NS to update the target NS; the first management unit can also obtain the target NSD from the directory, and the VNF instance identifier corresponding to the VNF instance matching the new VNFD ID and the new VNFFG instance. The identifier is written to the target NSD to update the target NSD.
  • the first management unit controls the updated VNF instance and the updated VNFFG instance to be in a terminated state while updating the target NS, that is, cannot be called by other NSs.
  • the VNFFG instance is used to describe the connection relationship between the VNF instances. Therefore, the VNFFG instance of the new VNFFG instance is used to update the connection relationship between the VNF instance matching the new VNFD ID and other VNF instances.
  • the lifecycle management request of the target NS is received from the second management unit by the first management, where the lifecycle management request includes the target NSD ID; the first management unit searches for the target NSD according to the target NSD ID, the target NSD Include an instance identifier, or the target NSD includes an instance identifier and a VNFD ID, and perform lifecycle management on the target NS according to the instance identifier and/or the VNFD ID included in the target NSD, thereby implementing an instance identifier and/or a VNFD ID included according to the NSD. Carry out lifecycle management, eliminating the need for filtering, screening and other processes, streamlining the lifecycle management process and improving processing efficiency.
  • FIG. 3 is a schematic diagram of communication of uploading an NSD according to an embodiment of the present invention.
  • the second management unit sends an upload request for the target NSD to the first management unit.
  • the second management unit may send an upload request of the target NS to the first management unit through a communication interface between the second management unit and the first management unit.
  • the upload request in the existing upload process includes IDs of a plurality of descriptors included in the target NSD, and these descriptors include VNFD, VNFFGD, VLD, PNFD, and the like.
  • the upload request includes an instance identifier included in the target NSD in addition to the IDs of the plurality of descriptors, so that the content of the target NSD uploaded to the directory is richer, so that the second management unit is
  • the target NSD ID finds the target NSD
  • the instance identifier included in the target NSD can be obtained, thereby performing lifecycle management according to the instance identifier.
  • the content of the target NSD included in the upload request in the embodiment of the present invention may be selected and input by a network administrator of the second management unit or a planning and design engineer of the network service.
  • a network administrator of the second management unit or a planning and design engineer of the network service.
  • the engineer will know in advance the existing instance of the Shanghai MME region and the Pudong S-GW/Data Gateway (P-GW). Then, the engineer inputs two existing VNF instance IDs (and other link interface instances, such as VL instance ID, VNFFG instance ID, etc.) as an instance identifier into the second management unit.
  • the first management unit may receive an upload request from the second management unit, for example, receiving an upload request sent by the second management unit by using a communication interface between the second management unit and the first management unit; and acquiring the upload request includes Content.
  • the first management unit uploads the target NSD.
  • the first management unit may upload the content included in the target NSD and the target NSD to the directory, where the directory may be a VNF service directory, a VNF directory in the network structure shown in FIG. 1, or may be in FIG. Other directories in the network structure are not limited herein.
  • the directory stores the content included in the target NSD and the target NSD, that is, the content included in the target NSD is stored under the target NSD name.
  • the first management unit may also check whether the upload request is valid before uploading the target NSD.
  • the first management unit checks whether the upload request is valid by checking whether the instance identified by the instance identifier included in the upload request exists in the network architecture, for example, the upload request includes two sets of instances.
  • the first set of instance identifiers includes the VNF instance ID 1, and the VNF instance ID 1 identified by the VNF instance ID 1 exists in the network architecture;
  • the second set of instance identifiers includes the VNF instance ID 2, and the VNF instance ID 2 identifies the VNF instance 2 Exist in the network architecture, then it can be determined that the upload request is valid.
  • the first management unit checks whether the upload request is valid by checking the multiplexing indication information included in the instance identifier included in the upload request, that is, detecting whether the instance identified by the instance identifier is allowed to be At least two NS calls to verify whether the upload request is valid, specifically by verifying whether the instance identifier includes a field that can be identified by at least two NS multiplexed fields or instance identifiers, including a field that can be multiplexed by at least two NSs. To verify whether the upload request is valid, it is also possible to verify whether the upload request is valid by checking whether the VNF instance corresponding to the VNFD or VNFD included in the target NSD includes a field that can be multiplexed by at least two NSs. If it is checked that the upload request is valid, the first management unit uploads the content included in the target NSD and the target NSD to the directory.
  • the first management unit sends a confirmation upload information to the second management unit.
  • the first management unit sends a confirmation upload information to the second management unit through the communication interface between the first management unit and the second management unit, and notifies the second management unit of the target NSD and the target NSD.
  • the included content has been uploaded.
  • the second management unit does not need to send the content included in the target NSD when sending the lifecycle management request to the first management unit, thereby saving signaling overhead.
  • the above-mentioned part 303 is an optional part.
  • the second management unit may request The first management unit modifies the uploaded target NSD.
  • FIG. 4 is a schematic diagram of communication for modifying an NSD according to an embodiment of the present invention.
  • the second management unit sends a modification request of the target NSD to the first management unit, the modification request for requesting the first management unit to modify the target NSD.
  • the engineer or network administrator needs to enter the instance ID into the target NSD.
  • the engineer or network administrator needs to change an instance ID in the target NSD.
  • the first management unit may receive the modification request of the target NSD from the second management unit, for example, may receive the modification request from the second management unit by using a communication interface between the first management unit and the second management unit, and obtain the modification.
  • the added or updated instance ID included in the request may be received from the second management unit, for example, may receive the modification request from the second management unit by using a communication interface between the first management unit and the second management unit, and obtain the modification.
  • the added or updated instance ID included in the request may be received from the second management unit, for example, may receive the modification request from the second management unit by using a communication interface between the first management unit and the second management unit, and obtain the modification.
  • the added or updated instance ID included in the request may be received from the second management unit, for example, may receive the modification request from the second management unit by using a communication interface between the first management unit and the second management unit, and obtain the modification.
  • the added or updated instance ID included in the request may be received from the second management unit, for example, may receive the modification request from the
  • the second management unit modifies the target NSD.
  • the second management unit upon receiving the modification request, modifies the target NSD according to the modification request. Specifically, the second management unit may modify the target NSD according to the added or updated instance identifier included in the modification request.
  • the first management unit may also check whether the modification request is valid before modifying the update target NSD. In a possible implementation manner, the first management unit may verify whether the modification request is valid by verifying whether the identified instance of the added or updated instance identifier included in the modification request exists in the network architecture, if present, In the network architecture, it is determined that the modification request is valid.
  • the first management unit may verify whether the modification request is valid by checking the multiplexing indication information included in the added or updated instance identifier included in the modification request, that is, detecting the added or The updated instance identifies whether the identified instance is allowed to be checked by at least two NSs to verify whether the modification request is valid, specifically by verifying the added or updated instance Identifying whether the identifier includes a field that can be multiplexed by at least two NSs, or whether the instance identified by the added or updated instance identifier includes a field that can be multiplexed by at least two NSs to verify whether the modification request is valid, if included This field determines that the modification request is valid. If it is checked that the modification request is valid, the first management unit modifies the target NSD according to the added or updated instance identifier included in the modification request.
  • the first management unit uploads the modified target NSD.
  • the first management unit can upload the modified target NSD to the directory.
  • the first management unit sends confirmation modification information to the second management unit.
  • the first management unit may send the confirmation modification information to the second management unit through the communication interface between the first management unit and the second management unit to notify the second management unit that the target NSD has completed the modification.
  • the above 404 part is an optional part.
  • each network element for example, the first management unit, the second management unit, and the like, in order to implement the above functions, includes hardware structures and/or software modules corresponding to each function.
  • the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • the embodiment of the present invention may divide the function module by using the first management unit, the second management unit, and the like according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated in the function.
  • a processing module In a processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 5A shows a possible structural diagram of the first management unit involved in the above embodiment.
  • the first management unit 500 includes a processing module 502 and a communication module 503.
  • the processing module 502 is configured to perform control management on the actions of the first management unit.
  • the processing module 502 is configured to support the first management unit to perform the processes 203 and 204 in FIG. 2, the processes 302 and 303 in FIG. 3, in FIG. Processes 402, 403, and 404, and/or for the techniques described herein Other processes of surgery.
  • the communication module 503 is for supporting communication between the first management unit and the second management unit or other network entity, such as communication with the OSS/BSS unit or VNFM unit shown in FIG.
  • the first management unit may further include a storage module 501 for storing program codes and data of the first management unit.
  • the processing module 502 can be a processor or a controller, and can be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication module 503 can be a communication interface, a transceiver or a transceiver circuit, etc., wherein the communication interface is a collective name and can include one or more interfaces.
  • the storage module 501 can be a memory.
  • the first management unit involved in the embodiment of the present invention may be the first management unit shown in FIG. 5B.
  • the first management unit 510 includes a processor 512, a communication interface 513, and a memory 511.
  • the first management unit 510 may further include a bus 514.
  • the communication interface 513, the processor 512, and the memory 511 may be connected to each other through a bus 514.
  • the bus 514 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (abbreviated). EISA) bus and so on.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus 514 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 5B, but it does not mean that there is only one bus or one type of bus.
  • FIG. 6A shows a possible structural diagram of the second management unit involved in the above embodiment.
  • the second management unit 600 includes a processing module 602 and a communication module 603.
  • the processing module 602 is configured to perform control management on the actions of the second management unit.
  • the processing module 602 is configured to support the second management unit to perform the processes 201 and 202 in FIG. 2, the process 301 in FIG. 3, and the process in FIG. 401, and/or other processes for the techniques described herein.
  • the communication module 603 is configured to support communication between the second management unit and the first management unit or other network entity, such as communication with the NFVO unit shown in FIG.
  • the second management unit may further include a storage module 601 for storing program codes and data of the second management unit.
  • the processing module 602 can be a processor or a controller, for example, can be a central processing unit.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication module 603 can be a communication interface, a transceiver or a transceiver circuit, etc., wherein the communication interface is a collective name and can include one or more interfaces.
  • the storage module 601 can be a memory.
  • the second management unit involved in the embodiment of the present invention may be the second management unit shown in FIG. 6B.
  • the second management unit 610 includes a processor 612, a communication interface 613, and a memory 611.
  • the second management unit 610 may further include a bus 614.
  • the communication interface 613, the processor 612, and the memory 611 may be connected to each other through a bus 614; the bus 614 may be a peripheral component interconnection standard bus or an extended industry standard structure bus or the like.
  • the bus 614 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 6B, but it does not mean that there is only one bus or one type of bus.
  • the steps of the method or algorithm described in connection with the disclosure of the embodiments of the present invention may be implemented in a hardware manner, or may be implemented by a processor executing software instructions.
  • the software instructions may be composed of corresponding software modules, which may be stored in a random access memory (RAM), a flash memory, a read only memory (ROM), an erasable programmable read only memory ( Erasable Programmable ROM (EPROM), Electrically Erasable Programmable Read Only Memory (EEPROM), registers, hard disk, removable hard disk, read-only optical disk (CD-ROM) or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC.
  • the ASIC can be located in a core network interface device.
  • the processor and the storage medium may also exist as discrete components in the core network interface device.
  • the functions described in the embodiments of the present invention may be implemented in hardware, software, firmware, or any combination thereof.
  • the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un procédé de gestion du cycle de vie, et une unité de gestion. Le procédé comprend les étapes suivantes : une première unité de gestion reçoit, d'une seconde unité de gestion, une demande de gestion du cycle de vie d'un NS cible, la demande contenant un ID de NSD cible ; la première unité de gestion recherche un NSD cible d'après l'ID de NSD cible, le NSD cible comprenant un ID d'instance, ou un ID d'instance et un ID de VNFD, l'ID d'instance et/ou l'ID de VNFD étant utilisés pour déterminer une instance nécessaire pour la gestion du cycle de vie du NS cible ; la première unité de gestion exécute une gestion du cycle de vie sur le NS cible d'après l'ID d'instance et/ou l'ID de VNFD En option, l'ID d'instance peut contenir des informations d'indication de multiplexage pour indiquer si l'instance identifiée par l'ID d'instance peut être multiplexée par au moins deux NS. Des modes de réalisation de la présente invention peuvent simplifier le processus de gestion du cycle de vie et améliorer l'efficacité du traitement.
PCT/CN2016/098486 2016-09-08 2016-09-08 Procédé de gestion du cycle de vie, et unité de gestion WO2018045540A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/098486 WO2018045540A1 (fr) 2016-09-08 2016-09-08 Procédé de gestion du cycle de vie, et unité de gestion

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/098486 WO2018045540A1 (fr) 2016-09-08 2016-09-08 Procédé de gestion du cycle de vie, et unité de gestion

Publications (1)

Publication Number Publication Date
WO2018045540A1 true WO2018045540A1 (fr) 2018-03-15

Family

ID=61561637

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/098486 WO2018045540A1 (fr) 2016-09-08 2016-09-08 Procédé de gestion du cycle de vie, et unité de gestion

Country Status (1)

Country Link
WO (1) WO2018045540A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104219127A (zh) * 2014-08-30 2014-12-17 华为技术有限公司 一种虚拟网络实例的创建方法以及设备
CN105429780A (zh) * 2015-10-30 2016-03-23 南京优速网络科技有限公司 一种虚拟化网络服务业务自动生成和动态监控的方法
CN105656646A (zh) * 2014-11-10 2016-06-08 ***通信集团公司 一种虚拟网元的部署方法及装置
WO2016107506A1 (fr) * 2014-12-31 2016-07-07 华为技术有限公司 Appareil et procédé de chargement de réseau virtuel
WO2016114866A1 (fr) * 2015-01-13 2016-07-21 Intel IP Corporation Techniques de surveillance de fonctions de réseau virtualisées ou infrastructure de virtualisation de fonctions de réseau
CN105812171A (zh) * 2014-12-31 2016-07-27 华为技术有限公司 一种虚拟化的网络功能vnf控制方法和设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104219127A (zh) * 2014-08-30 2014-12-17 华为技术有限公司 一种虚拟网络实例的创建方法以及设备
CN105656646A (zh) * 2014-11-10 2016-06-08 ***通信集团公司 一种虚拟网元的部署方法及装置
WO2016107506A1 (fr) * 2014-12-31 2016-07-07 华为技术有限公司 Appareil et procédé de chargement de réseau virtuel
CN105812171A (zh) * 2014-12-31 2016-07-27 华为技术有限公司 一种虚拟化的网络功能vnf控制方法和设备
WO2016114866A1 (fr) * 2015-01-13 2016-07-21 Intel IP Corporation Techniques de surveillance de fonctions de réseau virtualisées ou infrastructure de virtualisation de fonctions de réseau
CN105429780A (zh) * 2015-10-30 2016-03-23 南京优速网络科技有限公司 一种虚拟化网络服务业务自动生成和动态监控的方法

Similar Documents

Publication Publication Date Title
CN109417496B (zh) 虚拟网络环境中的自动服务功能验证
US20210344692A1 (en) Providing a virtual security appliance architecture to a virtual cloud infrastructure
US20220377045A1 (en) Network virtualization of containers in computing systems
US20230104129A1 (en) Network policy generation for continuous deployment
US9485323B1 (en) Managing pooled client-premise resources via provider-defined interfaces
US9686121B2 (en) Client-premise resource control via provider-defined interfaces
CN112398676B (zh) 多租户环境中服务接入端点的基于供应商无关简档的建模
US10911331B2 (en) Service configuration method and apparatus for network service
US20220210019A1 (en) Management Method and Apparatus
WO2019127418A1 (fr) Procédé de gestion de service de réseau, dispositif et système associés
KR20180002771A (ko) 네트워크 서비스 수명 주기 관리 방법 및 디바이스
CN111865641A (zh) 在数据中心中初始化服务器配置
US20230107891A1 (en) User interface for cloud native software-defined network architectures
CN107534577B (zh) 一种网络业务实例化的方法及设备
US20230336414A1 (en) Network policy generation for continuous deployment
KR20220104241A (ko) 네트워크 작업 방법, 장치, 설비 및 저장매체
WO2017206092A1 (fr) Procédé de gestion de cycle de vie et unité de gestion
WO2018045540A1 (fr) Procédé de gestion du cycle de vie, et unité de gestion
CN114124740A (zh) 一种vnf实例化的方法和装置
WO2021244483A1 (fr) Procédé et appareil de déploiement de service de réseau virtualisé
US20230017053A1 (en) Service chaining in fabric networks
US20240129161A1 (en) Network segmentation for container orchestration platforms
CN114428620A (zh) 一种数据流镜像方法及装置
CN116962263A (zh) 一种消息的接收、发送方法及装置

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: 16915475

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16915475

Country of ref document: EP

Kind code of ref document: A1