Nothing Special   »   [go: up one dir, main page]

WO2021103657A1 - 网络操作方法、装置、设备和存储介质 - Google Patents

网络操作方法、装置、设备和存储介质 Download PDF

Info

Publication number
WO2021103657A1
WO2021103657A1 PCT/CN2020/108582 CN2020108582W WO2021103657A1 WO 2021103657 A1 WO2021103657 A1 WO 2021103657A1 CN 2020108582 W CN2020108582 W CN 2020108582W WO 2021103657 A1 WO2021103657 A1 WO 2021103657A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
virtual
type
management node
virtual network
Prior art date
Application number
PCT/CN2020/108582
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 中兴通讯股份有限公司
Priority to EP20893814.2A priority Critical patent/EP4068708A4/en
Priority to US17/780,944 priority patent/US11855855B2/en
Priority to KR1020227021822A priority patent/KR102684903B1/ko
Publication of WO2021103657A1 publication Critical patent/WO2021103657A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • 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/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0866—Checking the configuration
    • H04L41/0873—Checking configuration conflicts between network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/76—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation
    • H04L47/781—Centralised allocation of resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation
    • H04L47/782—Hierarchical allocation of resources, e.g. involving a hierarchy of local and centralised entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/35—Switches specially adapted for specific applications
    • H04L49/354—Switches specially adapted for specific applications for supporting virtual local area networks [VLAN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H04L41/122—Discovery or management of network topologies of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]

Definitions

  • This application relates to the field of communications technology, for example, to a network operation method, device, device, and storage medium.
  • NFV Network Functions Virtualization
  • NFV Network Functions Virtualization
  • software and hardware decoupling and functional abstraction NFV can make network equipment functions no longer depend on dedicated hardware, so that resources can be fully and flexibly shared, realizing rapid development and deployment of new services, and automatic deployment and flexibility based on actual business needs Scaling, fault isolation and self-healing, etc.
  • the NFV system architecture defined by the European Telecommunications Standards Institute mainly includes: business operation support system and management support platform (Operation-Support System/Business Support System, OSS/BSS), virtual Network Functions (Virtualized Network Function, VNF), Network Functions Virtualization Infrastructure (NFVI), and Network Function Virtualization Management and Orchestration System (VNF-Management and Orchestration, NFV-MANO).
  • ETSI European Telecommunications Standards Institute
  • OSS/BSS Operaation-Support System/Business Support System
  • VNF Virtualized Network Function
  • NFVI Network Functions Virtualization Infrastructure
  • VNF-Management and Orchestration Network Function Virtualization Management and Orchestration
  • NFVI is mainly responsible for comprehensively virtualizing hardware resources such as computing, storage, and networking, and mapping them into virtual resources;
  • VNF runs on NFVI, uses virtual resources virtualized by NFVI, and uses software to implement various traditional NFV-MANO is responsible for managing and orchestrating the relationship between VNF and VNFI, the relationship between VNF and VNF, and the relationship between VNF and other physical network functions (Physical Network Functions, PNF).
  • PNF Physical Network Functions
  • NFV-MANO includes: Virtualized Infrastructure Manager (VIM), Virtualized Network Function Manager (VNFM), and Network Function Virtualization Orchestrator (NFVO).
  • VIM is used to control and manage virtualized resources
  • VNFM is used to manage the life cycle of VNFs
  • NFVO is used to arrange and manage virtual infrastructure, as well as the life cycle management of network services (Network Service, NS).
  • Network Service Network Service
  • switch ports can be divided into two categories: access ports and trunk ports.
  • the access port only allows packets belonging to a Virtual Local Area Network (VLAN) to pass.
  • VLAN Virtual Local Area Network
  • the two switches need to exchange packets, they need to be on the two switches.
  • the above assigns different ports for different VLAN packets to be connected separately, but the port of the switch is limited, this kind of interconnection method will waste the limited switch port; and the trunk port can allow multiple VLAN packets to pass, when using the trunk port , Each switch only needs to allocate one port for cascading to realize the transmission of different VLAN packets, thus saving switch ports.
  • NFVI's virtualized switch can already implement ports that support trunk mode.
  • trunk mode As shown in Figure 3, before the trunk mode is not supported, when a virtual machine wants to access multiple networks, multiple virtual network interface cards (vNIC) need to be configured to connect to different networks.
  • vNIC virtual network interface cards
  • add and delete The connected network can only be realized by adding or deleting virtual network cards. However, changing the virtual network card of the virtual machine will trigger the re-instancing process of the virtual machine itself and the restart of the running business software, which will cause the interruption of the VNF function. After supporting the trunk mode, you only need to configure a virtual network card for the virtual machine.
  • connection point (CP) of the virtual machine supports working in the trunk mode, that is, whether the port supports the transmission of multiple Virtual Local Area Network (VLAN) packets.
  • VLAN Virtual Local Area Network
  • the embodiment of the present application provides a network operation method, including:
  • the management node receives virtual network function information, where the virtual network function information carries at least one network dynamic change flag;
  • At least one network dynamic change flag is used to indicate whether to support dynamic network change
  • the management node operates the first type network according to the virtual network function information.
  • the embodiment of the present application also provides a network operation device, including:
  • the receiving module is configured to receive virtual network function information, where the virtual network function information carries at least one network dynamic change mark;
  • At least one network dynamic change flag is used to indicate whether to support dynamic network change
  • the operation module is used to operate the first type network according to the virtual network function information.
  • the embodiment of the present application also provides a management node device, including:
  • a memory a processor, and a computer program stored on the memory and capable of running on the processor.
  • the processor executes the above computer program, the network operation method as provided in the embodiment of the present application is realized.
  • the embodiment of the present application also provides a computer-readable storage medium that stores a computer program, and when the computer program is executed by a processor, the network operation method provided in the embodiment of the present application is implemented.
  • Figure 1 is an ETSI NFV system architecture diagram
  • Figure 2 is a comparison diagram of access port and trunk port in a non-virtualized environment
  • Figure 3 is a comparison diagram of virtual machines using trunk mode and not using trunk mode
  • FIG. 4 is a schematic flowchart of a network operation method provided by an embodiment
  • Figure 5 is a schematic diagram of the virtual network function information structure
  • FIG. 6 is a schematic flowchart of a network operation method provided by an embodiment
  • FIG. 7 is a schematic flowchart of another network operation method provided by an embodiment
  • FIG. 8 is a schematic flowchart of another network operation method provided by an embodiment
  • FIG. 9 is a schematic flowchart of another network operation method provided by an embodiment.
  • FIG. 10 is a schematic flowchart of another network operation method provided by an embodiment
  • FIG. 11 is a schematic structural diagram of a network operation device provided by an embodiment
  • Fig. 12 is a schematic structural diagram of a management node device provided by an embodiment.
  • the virtual machine provides the ability to dynamically change the access network: this ability is not equivalent to the ability to dynamically create and delete access ports provided by the virtual switch to which the virtual machine is connected. This ability means that the business software running on the virtual machine needs to deal with dynamic changes The data flow from different networks requires the business software running on the virtual machine to have data processing capabilities that match the access network. Otherwise, the realization of the function of dynamically changing the access network by using the trunk mode in a virtualized environment is incomplete.
  • FIG. 4 is a schematic flowchart of a network operation method provided by an embodiment.
  • the method can be applied to a scenario where the trunk mode is supported in a virtualization environment.
  • the method may include:
  • S401 The management node receives virtual network function information.
  • the virtual network function information may carry at least one network dynamic change flag.
  • the network dynamic change flag can be in the trunk mode to explicitly indicate whether the business software currently supports the processing of data flow changes caused by the dynamic network change.
  • the network dynamic change flag is 0 or False, it means that the service software does not support the data flow change caused by the network change, and the management node cannot initiate changes to the connected network; when the network dynamic change flag When it is 1, or True, it means that the service software supports data flow changes caused by network changes, and the management node can initiate changes to the accessed network.
  • the management node operates the first type network according to the virtual network function information.
  • the first type of network in the above steps may be a network created by MANO based on the network attributes defined in the ETSI NFV specification, where the network attributes may be descriptions and network services in the VNFD describing the network attributes supported by the VNF
  • the descriptor (Network Service Descriptor, NSD) describes the network attributes interconnected with the VNF instance and other VNF ⁇ PNF, or the relevant parameters of the network connected to the virtual network function instance added by the network management node, for example, in the network management node OSS/BSS adds relevant parameters of the network connected to the virtual network function instance during the NSD design phase.
  • the management node may perform operations on the created first type network.
  • the foregoing first type network may be one or more networks, that is, two or more networks created according to the network attributes defined in the ETSI NFV specification may be collectively referred to as the first type network.
  • the management node after receiving the virtual network function information, the management node operates the first type of network according to the virtual network function information. Since at least one network dynamic change flag carried in the virtual network function information can be used to indicate whether dynamic change is supported Therefore, the management node can correctly process the change requirements of the first type of network according to the virtual network function information.
  • the virtual network function information received in step S401 may carry at least one mode flag, and the mode flag is used to indicate whether the trunk mode is supported.
  • the virtual network function information can also carry network connection restriction characteristic parameters, where the parameters can be the number of access ports, the type of the first type of network (for example, Virtual Local Area Network, VLAN), and extensible virtual local area network (Virtual eXtensible).
  • LAN, VXLAN Generic Routing Encapsulation (GRE), the protocol stack structure of the access network (for example, Medium Access Control (MAC) ⁇ Internet Protocol (IP) ⁇ User Data Report protocol (User Datagram Protocol, UDP), MAC ⁇ IP ⁇ Transmission Control Protocol (Transmission Control Protocol, TCP)).
  • MAC Medium Access Control
  • IP Internet Protocol
  • UDP User Datagram Protocol
  • TCP Transmission Control Protocol
  • the foregoing step S402 may be that the network management node generates a virtual network function instance according to the virtual network function information, and connects the first type of network according to the virtual network function instance, and further, when the first type of network is running, the network management The node operates the connection relationship between the virtual network function instance and the first type network according to the at least one network dynamic change flag.
  • the network management node may include OSS/BSS and MANO, and the network management node may also include other units and modules, which are not limited in the embodiment of the present application.
  • the OSS/BSS can manage the virtual network function information as a part of the NSD, or independently manage the virtual network function information.
  • the OSS/BSS may carry the acquired network connection information in the NSD.
  • OSS/BSS uploads virtual network function information to MANO, so that MANO instantiates a virtual network function instance based on the virtual network function information.
  • the above OSS/BSS uploading virtual network function information to MANO may be a part of uploading NSD operation or an independent virtual network function information management operation.
  • the instantiation process can create a vSwitch for MANO, where the trunk port of the vSwitch is connected to the virtual network function instance. Furthermore, MANO connects the virtual network function instance with the first type of network, and OSS/BSS and MANO record the network dynamic change flag in the virtual network function information. If you need to add a network, MANO creates the required access port to connect to the network, and the required access port is created based on the network connection restriction characteristic parameters in the virtual network function information.
  • the network management node operates the connection relationship between the virtual network function instance and the first type of network according to the at least one network dynamic change mark, and the network management node may change the mark according to the network dynamic change mark of the at least one connection module to change the virtual network function The connection relationship between the instance and the first type of network is operated.
  • connection relationship between the virtual network function instance and the first type network may be a connection relationship between the virtual network function instance and the first type network through the connection module.
  • the connection module may include a VNF module, and/or a virtualized network function component (VNFC), and/or a CP.
  • VNF module may be composed of one or more VNFCs, one VNFC One or more CPs connected to the trunk port of the vSwitch can be connected.
  • the above-mentioned at least one network dynamic change mark can be added to the Connection Point Descriptor (CPD) in the ETSI specification. Therefore, the management node can at least dynamically change the mark through the network to pair the virtual network function instance connected through the CP with the first One type of network connection relationship is operated.
  • CPD Connection Point Descriptor
  • the network management node can operate the connection relationship between the virtual network function instance and the first type of network in accordance with the network dynamic change flag of at least one connection module in the following ways:
  • Method 1 When the network dynamic change of the connection module is marked as not supporting dynamic network change, the network management node does not change the connection relationship between the virtual network function instance and the first type of network;
  • Method 2 When the network dynamic change of the connection module is marked as supporting dynamic network change, the network management node performs a change operation on the connection relationship between the virtual network function instance and the first type of network;
  • the VNF module needs to support the connection of multiple first-type networks, and the mode carried in the virtual network function information is marked as supporting the trunk mode, that is, it can be passed through the vSwitch
  • the access port is connected to the first type of network, and the network of the virtual network function instance is dynamically marked as not supporting dynamic network changes.
  • the network management node receives the virtual network function information, it does not change the connection relationship between the virtual network function instance and the first type of network, that is, the network management node refuses to change the virtual network function instance. Modify the connection relationship with network 1, network 2, ... network n.
  • the foregoing operation of changing the connection relationship between the virtual network function instance and the first type of network may exceed the limit set in the virtual network function module by the support capability of the business software. For example, the number of access ports exceeding the limit of the virtual network function module, or changing the attributes of the access port connected to the network, etc.
  • the network management node can change the connection relationship between the virtual network function instance and the first type of network, which may include the following situations:
  • the VNF is composed of three VNFCs, namely VNFC1, VNFC2, and VNFC3.
  • the first type of network connected to VNFC1 is network e, network f, and the first type connected to VNFC2
  • the networks are network c and network d
  • the first type of network connected to VNFC3 is network a and network b.
  • the mode for VNFC1 and VNFC2 is marked as supporting trunk mode
  • the mode for VNFC3 is marked as not supporting trunk mode
  • the network dynamic change for VNFC1 is marked as supporting dynamic change mark
  • the network dynamic change for VNFC2 is marked as not supporting Dynamically change the mark. That is, VNFC1 and VNFC2 can connect to network e, network f, and network c and network d respectively through the access port of vSwitch, and VNFC3 connects to network a and network b through multiple virtual networks.
  • VNFC1 uses trunk mode and supports dynamic network change
  • VNFC2 uses trunk mode, does not support dynamic network change
  • VNFC3 does not use trunk mode
  • the network management node can learn that the network change can only be performed on the VNFC1 that supports dynamic network change according to the virtual network function information. Operation is to change the connection relationship between VNFC1 and the first type of networks e and f. For example, add network g to VNFC1, or delete network e, etc.
  • the VNF module needs to support the connection of multiple networks
  • the connected network information is variable
  • the mode carried in the virtual network function information is marked as supporting trunk Mode, that is, the first type of network can be connected through the access port of the vSwitch, and at least one network is dynamically marked as supporting dynamic change of the network.
  • the network management node performs a change operation on the connection relationship between the virtual network function instance and the first type of network.
  • the network management node can initiate a new network connection instruction through its internal OSS/BSS, and then the OSS /BSS and MANO cooperate with each other to create a new access port on the vSwitch connected to the virtual network function instance, and connect it to network m, and at the same time notify the relevant parameters of network m to the business processing software of the virtual network function instance.
  • the aforementioned network m may be a network that has already been created, or a network created specifically for virtual network instances.
  • the operation and maintenance personnel can design virtual network function instances as needed to no longer process data on network n.
  • the network management node can initiate an instruction to delete the network connection through its internal OSS/BSS, and then the OSS /BSS and MANO cooperate with each other to disconnect the connection between the virtual network function instance and network n, delete the corresponding access port on the vSwitch connected to the virtual network function module, and notify the business processing software of the virtual network function instance, network n is no longer within its processing range.
  • the VNF module needs to support the connection of multiple networks.
  • virtual network function instance 1 is connected to network 1 and network 2
  • virtual network function instance 2 is connected to network n
  • Network m is connected
  • the connected network information is variable
  • the mode carried in the virtual network function information is marked as supporting trunk mode, that is, the first type of network can be connected through the access port of vSwitch, and at least one network is dynamically marked as supporting dynamic Change the network.
  • the network management node changes the connection relationship between the virtual network function instance and the first type of network.
  • MANO in the network management node monitors that the network data flow meets the trigger condition during the orchestration management process, and virtual network function instance 1 needs to take over the data flow of network n, then OSS/BSS and MANO cooperate with each other to perform the following process: Disconnect The connection between virtual network function instance 2 and network n, delete the access port under the vSwitch of virtual network function instance 2, and notify the business processing software of virtual network function instance 2 that network n is no longer in its processing range and is in the virtual network Create a new access port on the vSwitch connected to function instance 1, connect to network n, and notify the relevant parameters of network n to the business processing software of virtual network function instance 1, so as to complete the connection between network n and virtual network function instance 2. Changes in the connection relationship.
  • the network data flow meeting the trigger condition may overload the operating overhead of virtual network function instance 2, and the data flow needs to be diverted to virtual network function instance 1 with low operating overhead, or virtual network function instance 2 If the operation fails, the data stream is diverted to the normal running virtual network function instance 1 to ensure that the business is not affected, or the virtual network function instance 1 and virtual network function instance 2 are both in low-load operation, and the dynamics in the management node
  • the expansion management module determines that the virtual network function instance 2 can be scaled down, and the data stream on the virtual network function instance 2 is shunted to the virtual network function instance 1.
  • triggering conditions are only exemplary descriptions. Under the circumstance that other triggering conditions are met, performing the change of the connection relationship between the virtual network function instance and the first type of network through the example process shown in FIG. 9 all fall within the protection scope of the present application.
  • the VNF module needs to support the connection of multiple networks.
  • virtual network function instance 1 is connected to network 1
  • network 2 is connected to network n
  • Network m is connected
  • the connected network information is variable
  • the mode carried in the virtual network function information is marked as supporting the trunk mode, that is, the first type of network can be connected through the access port of the vSwitch, and at least one network is dynamically marked as supporting dynamic change The internet.
  • network management node performs the virtual network function The connection relationship between the instance and the first type of network is not changed.
  • the virtual network function information is designed to meet the preset conditions for the information of virtual network function instance 1 (for example, virtual network function instance 1 is connected with When a high-priority type 1 network, or a high-priority user accesses a type 1 network connected to virtual network function instance 1, etc.), the network management node performs a check on the virtual network function instance 1 and network 1, network 2. The connection relationship between is not changed.
  • the OSS/BSS has determined that the connection relationship between virtual network function instance 1 and network 1 and network 2 will not be changed, but only virtual network function instance 2
  • the connection relationship between network n and network m is changed, that is, in the MANO orchestration management process, the triggered network change can only be performed on virtual network function instance 2.
  • the network can be changed by adding or deleting the access port on the vSwitch.
  • Figure 11 is a schematic structural diagram of a network operating device provided by an embodiment.
  • the device includes: a receiving module 1101, an operating module 1102; wherein the receiving module is used to receive virtual network function information, and the virtual At least one network dynamic change mark is carried in the network function information, and the at least one network dynamic change mark is used to indicate whether to support dynamic network change;
  • the operation module is used to operate the first type network according to the virtual network function information.
  • the above-mentioned operating module includes a generating unit, a connecting unit, and an operating unit; wherein the generating unit is used to generate a virtual network function instance according to the virtual network function information; the connecting unit is used to connect the first type of network according to the virtual network function instance; the operating unit, When the first type of network is running, the connection relationship between the virtual network function instance and the first type of network is operated according to at least one network dynamic change flag.
  • the above-mentioned operating unit can be specifically used to operate the connection relationship between the virtual network function instance and the first type network according to the network dynamic change mark of at least one connection module; wherein the virtual network function instance is connected to the first type network through the connection module,
  • the connection module includes a virtual network function module, and/or a virtual network function component, and/or, a connection point.
  • the operating unit When the network dynamic change of the connection module is marked as not supporting dynamic network change, the operating unit is used to not change the connection relationship between the virtual network function instance and the first type of network; or, when the network dynamic change of the connection module is marked as supporting When the network is dynamically changed, the operating unit is used to change the connection relationship between the virtual network function instance and the first type of network.
  • the operation unit used to change the connection relationship between the virtual network function instance and the first type of network may be: when the network operation device receives the network change request, the operation unit performs the operation on the virtual network function instance and the first type of network. The connection relationship of the type network is changed.
  • the operation unit used to change the connection relationship between the virtual network function instance and the first type network may be: when the network data flow meets the trigger condition, the operation unit performs the operation on the virtual network function instance and the first type network Change operation of the connection relationship.
  • the operating unit when the network dynamic change of the connection module is marked as supporting dynamic network change, and the virtual network function information meets the preset condition, the operating unit is used to check the connection relationship between the virtual network function instance and the first type of network Change operation.
  • FIG. 12 is a schematic structural diagram of a management node device provided by an embodiment.
  • the device includes a processor 1201 and a memory 1202; the number of processors 1201 in the device may be one or more, as shown in FIG.
  • the memory 1202 as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the network operation method in the embodiment of FIG.
  • the processor 1201 implements the aforementioned network operation method by running software programs, instructions, and modules stored in the memory 1202.
  • the memory 1202 may mainly include a program storage area and a data storage area.
  • the program storage area may store an operating system and an application program required by at least one function; the data storage area may store data created according to the use of the device, and the like.
  • the memory 1202 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices.
  • the embodiment of the present application also provides a storage medium containing computer-executable instructions.
  • the computer-executable instructions are used to perform a network operation method when executed by a computer processor.
  • the method includes:
  • the management node receives virtual network function information, where the virtual network function information carries at least one network dynamic change flag; at least one network dynamic change flag is used to indicate whether to support dynamic network change; One type of network to operate.
  • the various embodiments of the present application can be implemented in hardware or dedicated circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, although the present application is not limited thereto.
  • the embodiments of the present application may be implemented by executing computer program instructions by a data processor of a network operating device, for example, in a processor entity, or by hardware, or by a combination of software and hardware.
  • Computer program instructions can be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or written in any combination of one or more programming languages Source code or object code.
  • ISA Instruction Set Architecture
  • the block diagram of any logic flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions.
  • the computer program can be stored on the memory.
  • the memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as but not limited to read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), optical Memory devices and systems (Digital Versatile Disc (DVD) or Compact Disc (CD)), etc.
  • Computer-readable media may include non-transitory storage media.
  • the data processor can be any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (Digital Signal Processors, DSP), application specific integrated circuits (ASICs) ), programmable logic device (Field Programmable Gate Array, FPGA) core processor architecture processor.
  • DSP Digital Signal Processors
  • ASICs application specific integrated circuits
  • FPGA programmable logic device

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本文公开了一种网络操作方法、装置、设备和存储介质。该网络操作方法包括：管理节点接收虚拟网络功能信息，所述虚拟网络功能信息中携带有至少一个网络动态变更标记；所述至少一个网络动态变更标记用于指示是否支持动态变更网络；所述管理节点根据所述虚拟网络功能信息对第一类型网络进行操作。

Description

网络操作方法、装置、设备和存储介质
本申请要求在2019年11月29日提交中国专利局、申请号为201911205628.4的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，例如涉及一种网络操作方法、装置、设备和存储介质。
背景技术
网络功能虚拟化(Network Functions Virtualization，NFV)是一种通过使用通用硬件以及虚拟化技术来承载其他功能的软件处理技术，主要用于降低网络设备的成本。NFV通过软硬件解耦及功能抽象，可以使网络设备功能不再依赖于专用硬件，使资源可以充分、灵活地共享，实现新业务的快速开发和部署，并基于实际业务需求进行自动部署、弹性伸缩、故障隔离和自愈等。
如图1所示，欧洲电信标准协会(European Telecommunications Standards Institute，ETSI)定义的NFV系统架构主要包含：业务运营支撑系统和管理支撑平台(Operation-Support System/Business Support System，OSS/BSS)、虚拟网络功能(Virtualized Network Function，VNF)、网络功能虚拟化基础设施(Network Functions Virtualization Infrastructure，NFVI)和网络功能虚拟化管理和编排系统(VNF-Management and Orchestration，NFV-MANO)。其中，NFVI主要负责将计算、存储以及网络等硬件资源全面虚拟化、并映射成虚拟资源；VNF则是运行在NFVI上，使用经过NFVI虚拟化后的虚拟资源，并利用软件来实现各种传统的物理网络功能；NFV-MANO负责管理和编排VNF和VNFI之间的关系、VNF和VNF之间的关系，以及VNF和其他物理网络功能(Physical Network Functions，PNF)之间的关系。
NFV-MANO包含：虚拟化基础设置管理器(Virtualized Infrastructure Manager，VIM)、虚拟网络功能管理器(Virtualized Network Function Manager，VNFM)和网络虚拟化功能编排器(Network Function Virtualization Orchestrator，NFVO)。VIM用于负责控制和管理虚拟化资源，VNFM用于负责VNF的生命周期管理，NFVO用于负责对虚拟基础设施的编排和管理，以及对网络服务(Network Service，NS)的生命周期管理。
在非虚拟化应用中，交换机(switch)的端口可分为两类：接入端口(access port)和级联端口(trunk port)。如图2所示，access port只允许属于一个虚拟 局域网(Virtual Local Area Network，VLAN)的报文通过，在使用access port时，如果两个交换机之间需要交互报文，那么需要在两台交换机上为不同的VLAN报文分配不同的端口分别连接，但交换机的端口是有限的，这种互联方式会浪费有限的交换机端口；而trunk port可以允许多个VLAN报文通过，在使用trunk port时，每个交换机只需要分配一个端口用于级联，即可实现不同VLAN报文的传输，从而节省交换机的端口。
在虚拟化应用中，NFVI的虚拟化交换机(vSwitch)已经可以实现支持trunk模式的端口。如图3所示，在不支持trunk模式之前，虚拟机要接入多个网络时，需要配置多个虚拟网卡(virtual Network Interface Card，vNIC)以分别接入不同的网络，同时，增、删接入的网络也只能通过增、删虚拟网卡的方式实现。但是变更虚拟机的虚拟网卡，会触发虚拟机本身的重新实例化过程，以及运行的业务软件重启，进而导致VNF功能的中断。而支持trunk模式后，只需为虚拟机配置一个虚拟网卡，连接虚拟交换机的trunk port后，经过虚拟交换机不同的access port可以接入不同的网络，从而节省为虚拟机配置虚拟网卡的数目，以及虚拟机实例化成功后运行期间可动态变更连接网络的能力。
但是，在ETSI NFV规范中只定义了虚拟机对外连接点(connection point，CP)是否支持工作在trunk模式，即端口是否支持多个虚拟局域网(Virtual Local Area Network，VLAN)报文的传输。而对于ETSI NFV规范中的其他问题还没有讨论。
发明内容
本申请实施例提供了一种网络操作方法，包括：
管理节点接收虚拟网络功能信息，其中，虚拟网络功能信息中携带有至少一个网络动态变更标记；
至少一个网络动态变更标记用于指示是否支持动态变更网络；
管理节点根据虚拟网络功能信息对第一类型网络进行操作。
本申请实施例还提供了一种网络操作装置，包括：
接收模块，用于接收虚拟网络功能信息，其中，虚拟网络功能信息中携带有至少一个网络动态变更标记；
至少一个网络动态变更标记用于指示是否支持动态变更网络；
操作模块，用于根据虚拟网络功能信息对第一类型网络进行操作。
本申请实施例还提供了一种管理节点设备，包括：
存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，当处理器执行上述计算机程序时，实现如本申请实施例提供的网络操作方法。
本申请实施例还提供了一种计算机可读存储介质，该存储介质存储有计算机程序，当计算机程序被处理器执行时，实现本申请实施例提供的网络操作方法。
附图说明
图1为ETSI NFV系统架构图；
图2为非虚拟化环境中access port和trunk port的对比图；
图3为使用trunk模式和不使用trunk模式的虚拟机对比图；
图4为一实施例提供的一种网络操作方法的流程示意图；
图5为虚拟网络功能信息结构示意图；
图6为一实施例提供的一种网络操作方法的流程示意图；
图7为一实施例提供的另一种网络操作方法的流程示意图；
图8为一实施例提供的另一种网络操作方法的流程示意图；
图9为一实施例提供的另一种网络操作方法的流程示意图；
图10为一实施例提供的另一种网络操作方法的流程示意图；
图11为一实施例提供的一种网络操作装置结构示意图；
图12为一实施例提供的一种管理节点设备结构示意图。
具体实施方式
下文中将结合附图对本申请的实施例进行说明。
另外，在本申请实施例中，“可选地”或者“示例性地”等词用于表示作例子、例证或说明。
为了理解本申请实施例所提供的方案，在此对本申请实施例中可能涉及到的相关概念作解释和说明，例如：
虚拟机提供动态变更接入网络的能力：这一能力不等同于虚拟机所连接的虚拟交换机提供的动态创建、删除access port的能力，该能力表示在虚拟机上运行的业务软件需要处理动态变化的来自不同网络的数据流，即要求虚拟机上运行的业务软件要具备与接入网络匹配的数据处理能力。否则，虚拟化环境中利用trunk模式实现动态变更接入网络的功能实现是不完整的。
基于上述概念，图4为一实施例提供的一种网络操作方法的流程示意图，该方法可以应用于虚拟化环境中支持trunk模式的场景下，如图4所示，该方法可以包括：
S401、管理节点接收虚拟网络功能信息。
在本实施例中，虚拟网络功能信息中可以携带有至少一个网络动态变更标记。如图5所示，该网络动态变更标记可以在trunk模式下，显式表明业务软件当前是否支持处理动态变更网络导致的数据流变化。
示例性地，假设当网络动态变更标记为0，或者，假(False)时，表示业务软件不支持网络变更导致的数据流变化，管理节点不能对接入的网络发起变更；当网络动态变更标记为1，或者，真(True)时，表示业务软件支持网络变更导致的数据流变化，管理节点可以对接入的网络发起变更。
S402、管理节点根据虚拟网络功能信息对第一类型网络进行操作。
上述步骤中的第一类型网络可以为MANO根据ETSI NFV规范中定义的网络属性创建出的网络，其中，该网络属性可以为在VNFD中描述VNF所支持的网络属性的说明(description)及网络服务描述符(Network Service Descriptor，NSD)中描述与VNF实例与其他VNF\PNF互联的网络属性，或者，网络管理节点添加的与虚拟网络功能实例相连的网络的相关参数，例如，网络管理节点中的OSS/BSS在NSD设计阶段添加的与虚拟网络功能实例相连的网络的相关参数。
管理节点在获取到虚拟网络功能信息中携带的至少一个网络动态变更标记后，可以对创建出的第一类型网络进行操作。
上述第一类型网络可以为一个或多个网络，即两个或两个以上根据ETSI NFV规范中定义的网络属性创建出的网络可以统称为第一类型网络。
在本申请实施例中，管理节点接收虚拟网络功能信息后，根据虚拟网络功能信息对第一类型网络进行操作，由于虚拟网络功能信息中携带的至少一个网络动态变更标记可用于指示是否支持动态变更网络，因此，管理节点可以根据虚拟网络功能信息正确的处理第一类型网络的变更需求。
在一种示例中，步骤S401中接收到的虚拟网络功能信息可以携带有至少一个模式标记，该模式标记用于指示是否支持trunk模式。虚拟网络功能信息还可以携带网络连接限制特性参数，其中，该参数可以为access port数目、第一类型网络的类型(例如，虚拟局域网(Virtual Local Area Network，VLAN)、可拓展虚拟局域网(Virtual eXtensible LAN，VXLAN)、通用路由封装协议(Generic Routing Encapsulation，GRE))、接入网络的协议栈结构(例如，介质访问控 制(Medium Access Control，MAC)\网际协议(Internet Protocol，IP)\用户数据报协议(User Datagram Protocol，UDP)、MAC\IP\传输控制协议(Transmission Control Protocol，TCP))。
在一种示例中，上述步骤S402可以为，网络管理节点根据虚拟网络功能信息生成虚拟网络功能实例，并根据虚拟网络功能实例连接第一类型网络，进而，当第一类型网络运行时，网络管理节点根据至少一个网络动态变更标记对虚拟网络功能实例与第一类型网络的连接关系进行操作。
网络管理节点可以包括OSS/BSS和MANO，网络管理节点也可以包括其他单元、模块，本申请实施例在此不做限定。
网络管理节点接收到虚拟网络功能信息后，可以由OSS/BSS将虚拟网络功能信息作为NSD中的一部分进行管理，或者对虚拟网络功能信息独立进行管理。可选地，OSS/BSS可以把获取到的网络连接信息携带在NSD中。进而，OSS/BSS将虚拟网络功能信息上传至MANO中，使MANO根据虚拟网络功能信息实例化出虚拟网络功能实例。
上述OSS/BSS上传虚拟网络功能信息至MANO可以是上传NSD操作的一部分，或者是独立的虚拟网络功能信息管理操作。
实例化的过程可以为MANO创建vSwitch，其中，vSwitch的trunk port与虚拟网络功能实例相连。进而，MANO将虚拟网络功能实例与第一类型网络相连，并由OSS/BSS与MANO记录虚拟网络功能信息中的网络动态变更标记。如需要增加网络，则MANO创建需要的access port与网络相连，所需的access port根据虚拟网络功能信息中的网络连接限制特性参数创建。
可选地，网络管理节点根据至少一个网络动态变更标记对虚拟网络功能实例与第一类型网络的连接关系进行操作，可以为网络管理节点根据至少一个连接模块的网络动态变更标记，对虚拟网络功能实例与第一类型网络的连接关系进行操作。
虚拟网络功能实例与第一类型网络的连接关系可以为虚拟网络功能实例通过连接模块与第一类型网络连接的关系。
该连接模块可以包括VNF模块，和/或，虚拟网络功能组件(Virtualised Network Function Component，VNFC)，和/或，CP，如图5所示，VNF模块可以由一个或多个VNFC组成，一个VNFC可以连接一个或多个连接vSwitch的trunk port的CP。
上述至少一个网络动态变更标记可以添加至ETSI规范中的连接点描述符(Connection Point Descriptor，CPD)中，因此，管理节点至少可以通过该网络 动态变更标记对通过CP连接的虚拟网络功能实例与第一类型网络之间的连接关系进行操作。
在一种示例中，网络管理节点根据至少一个连接模块的网络动态变更标记，对虚拟网络功能实例与第一类型网络的连接关系进行操作可以有以下几种实现方式：
方式一、当连接模块的网络动态变更标记为不支持动态变更网络时，网络管理节点对虚拟网络功能实例与第一类型网络的连接关系不进行变更操作；
方式二、当连接模块的网络动态变更标记为支持动态变更网络时，网络管理节点对虚拟网络功能实例与第一类型网络的连接关系进行变更操作；
方式三、当连接模块的网络动态变更标记为支持动态变更网络，且虚拟网络功能信息满足预设条件时，网络管理节点对虚拟网络功能实例与第一类型网络的连接关系不进行变更操作。
如图6所示，在上述方式一中，假设在运行环境中，VNF模块需要支持连接多个第一类型网络，且虚拟网络功能信息中携带的模式标记为支持trunk模式，即可以通过vSwitch的access port连接第一类型网络，虚拟网络功能实例的网络动态标记为不支持动态变更网络。
那么在第一类型网络运行过程中，网络管理节点接收到虚拟网络功能信息后，对虚拟网络功能实例与第一类型网络的连接关系不进行变更操作，也即网络管理节点拒绝对虚拟网络功能实例与网络1、网络2、……网络n之间的连接关系进行修改。
示例性地，上述对虚拟网络功能实例与第一类型网络的连接关系的变更操作可以为超出了业务软件的支持能力在虚拟网络功能模块中设定的限制。例如，超出了虚拟网络功能模块限制的接入端口数目，或者，变更接入端口连接网络的属性等。
在上述方式二中，网络管理节点对虚拟网络功能实例与第一类型网络的连接关系进行变更操作可以包括以下几种情况：
如图7所示，在一种示例中，假设VNF由三个VNFC组成，分别为VNFC1、VNFC2、VNFC3，与VNFC1连接的第一类型网络为网络e、网络f，与VNFC2连接的第一类型网络为网络c、网络d，与VNFC3连接的第一类型网络为网络a、网络b。其中，针对VNFC1和VNFC2的模式标记为支持trunk模式，针对VNFC3的模式标记为不支持trunk模式，并且，针对VNFC1的网络动态变更标记为支持动态变更标记，针对VNFC2的网络动态变更标记为不支持动态变更标记。即VNFC1和VNFC2可以通过vSwitch的access port分别连接网络e、网络f，以 及网络c、网络d，VNFC3通过多个虚拟网络连接网络a、网络b。
那么，管理节点接收到虚拟网络功能信息后，即可获知VNFC1使用trunk模式，并且支持动态变更网络；VNFC2使用trunk模式，不支持动态变更网络，VNFC3不使用trunk模式。
进而，在上述第一类型网络a～f运行期间，若网络管理节点接收到网络变更请求时，网络管理节点根据虚拟网络功能信息，即可获知只能在支持动态变更网络的VNFC1上进行网络变更操作，即对VNFC1与第一类型网络e、f之间的连接关系进行变更操作。例如，在VNFC1上增加网络g，或者，删除网络e等等。
如图8所示，在另一种示例中，假设在运行环境中，VNF模块需要支持连接多个网络，连接的网络信息是可变的，且虚拟网络功能信息中携带的模式标记为支持trunk模式，即可以通过vSwitch的access port连接第一类型网络，至少一个网络动态标记为支持动态变更网络。
那么在第一类型网络运行期间，若网络管理节点接收到网络变更请求时，则网络管理节点对虚拟网络功能实例与第一类型网络的连接关系进行变更操作。
例如，运维人员根据需要为虚拟网络功能实例增加与网络m的连接需求，那么网络管理节点接收到该网络变更请求后，可以通过其内部的OSS/BSS发起新增网络连接指令，进而由OSS/BSS与MANO相互协作，在虚拟网络功能实例所连接的vSwitch上创建新的access port，并连接到网络m，同时将网络m的相关参数通知到虚拟网络功能实例的业务处理软件中。
上述网络m可以是已经创建好的网络，也可以是专门为虚拟网络实例创建的网络。
或者，运维人员根据需要设计虚拟网络功能实例不再处理网络n上的数据，那么网络管理节点接收到网络变更请求后，可以通过其内部的OSS/BSS发起删除网络连接的指令，进而由OSS/BSS与MANO相互协作，断开虚拟网络功能实例与网络n之间的连接，并在虚拟网络功能模块所连接的vSwitch上删除对应的access port，同时通知虚拟网络功能实例的业务处理软件，网络n已经不在其处理范围内。
如图9所示，在一种示例中，假设在运行环境中，VNF模块需要支持连接多个网络，其中，虚拟网络功能实例1与网络1、网络2连接，虚拟网络功能实例2与网络n、网络m连接，连接的网络信息是可变的，且虚拟网络功能信息中携带的模式标记为支持trunk模式，即可以通过vSwitch的access port连接第一类型网络，至少一个网络动态标记为支持动态变更网络。
那么在第一类型网络运行期间，当网络数据流满足触发条件时，网络管理节点对虚拟网络功能实例与第一类型网络的连接关系进行变更操作。
例如，网络管理节点中的MANO在编排管理过程中监测到网络数据流满足触发条件，需要由虚拟网络功能实例1接管网络n的数据流，那么OSS/BSS与MANO相互协作执行以下过程：断开虚拟网络功能实例2与网络n之间的连接，删除虚拟网络功能实例2的vSwitch下的access port，通知虚拟网络功能实例2的业务处理软件，网络n已经不在其处理范围内，并且在虚拟网络功能实例1所连接的vSwitch上创建新的access port，连接至网络n，同时将网络n的相关参数通知到虚拟网络功能实例1的业务处理软件中，从而完成网络n与虚拟网络功能实例2之间连接关系的变更。
示例性地，在上述过程中，网络数据流满足触发条件可以为虚拟网络功能实例2运行开销过载，需要将数据流分流至运行开销低的虚拟网络功能实例1上，或者，虚拟网络功能实例2运行出现故障，将数据流分流至正常运行的虚拟网络功能实例1上，以保证业务不受影响，或者，虚拟网络功能实例1和虚拟网络功能实例2都处于低负荷运行，管理节点中的动态扩容管理模块判定可以对虚拟网络功能实例2缩容，将虚拟网络功能实例2上的数据流分流至虚拟网络功能实例1上。
上述触发条件仅是示例性的说明，在满足其他触发条件的情况下，通过图9所示的示例过程执行虚拟网络功能实例与第一类型网络的连接关系的变更均属于本申请的保护范围。
如图10所示，在方式三中，假设在运行环境中，VNF模块需要支持连接多个网络，其中，虚拟网络功能实例1与网络1、网络2连接，虚拟网络功能实例2与网络n、网络m连接，连接的网络信息是可变的，且虚拟网络功能信息中携带的模式标记为支持trunk模式，即可以通过vSwitch的access port连接第一类型网络，至少一个网络动态标记为支持动态变更网络。
那么在网络1、网络2、网络n、网络m运行期间，当针对虚拟网络功能实例的网络动态标记为支持动态变更网络，且虚拟网络功能信息满足预设条件时，网络管理节点对虚拟网络功能实例与第一类型网络的连接关系不进行变更操作。
例如，虽然对于虚拟网络功能实例1的网络动态标记为支持动态变更网络，但虚拟网络功能信息被设计为针对虚拟网络功能实例1的信息满足预设条件(比如，虚拟网络功能实例1上连接有高优先级的第一类型网络，或者，高优先级的用户接入与虚拟网络功能实例1连接的第一类型网络等)时，网络管理节点对虚拟网络功能实例1与网络1、网络2之间的连接关系不进行变更操作。
这样，当运维人员发起网络变更请求时，OSS/BSS经过判断，确定对虚拟网络功能实例1与网络1、网络2之间的连接关系不进行变更操作，而只允许对虚拟网络功能实例2与网络n、网络m之间的连接关系进行变更操作，即在MANO编排管理过程中，触发的网络变更只能在虚拟网络功能实例2上进行。例如，通过增、删vSwitch上的access port实现对网络的变更。
上述预设条件仅是示例性的说明，本申请实施例对此并不作限定。
图11为一实施例提供的一种网络操作装置的结构示意图，如图11所示，该装置包括：接收模块1101、操作模块1102；其中，接收模块，用于接收虚拟网络功能信息，该虚拟网络功能信息中携带有至少一个网络动态变更标记，该至少一个网络动态变更标记用于指示是否支持动态变更网络；
操作模块，用于根据虚拟网络功能信息对第一类型网络进行操作。
上述操作模块包括生成单元、连接单元和操作单元；其中，生成单元，用于根据虚拟网络功能信息生成虚拟网络功能实例；连接单元，用于根据虚拟网络功能实例连接第一类型网络；操作单元，用于当第一类型网络运行时，根据至少一个网络动态变更标记对虚拟网络功能实例与第一类型网络的连接关系进行操作。
上述操作单元，具体可用于根据至少一个连接模块的网络动态变更标记，对虚拟网络功能实例与第一类型网络的连接关系进行操作；其中，虚拟网络功能实例通过连接模块与第一类型网络连接，连接模块包括虚拟网络功能模块，和/或，虚拟网络功能组件，和/或，连接点。
当连接模块的网络动态变更标记为不支持动态变更网络时，操作单元用于对虚拟网络功能实例与第一类型网络的连接关系不进行变更操作；或者，当连接模块的网络动态变更标记为支持动态变更网络时，操作单元用于对虚拟网络功能实例与第一类型网络的连接关系进行变更操作。
在一种示例中，操作单元用于对虚拟网络功能实例与第一类型网络的连接关系进行变更操作可以为，当网络操作装置接收到网络变更请求时，操作单元对虚拟网络功能实例与第一类型网络的连接关系进行变更操作。
在一种示例中，操作单元用于对虚拟网络功能实例与第一类型网络的连接关系进行变更操作可以为，当网络数据流满足触发条件时，操作单元对虚拟网络功能实例与第一类型网络的连接关系进行变更操作。
在一种示例中，当连接模块的网络动态变更标记为支持动态变更网络，且虚拟网络功能信息满足预设条件时，操作单元用于对虚拟网络功能实例与第一类型网络的连接关系不进行变更操作。
图12为一实施例提供的一种管理节点设备的结构示意图，如图12所示，该设备包括处理器1201和存储器1202；设备中处理器1201的数量可以是一个或多个，图12中以一个处理器1201为例；设备中的处理器1201和存储器1202可以通过总线或其他方式连接，图12中以通过总线连接为例。
存储器1202作为一种计算机可读存储介质，可用于存储软件程序、计算机可执行程序以及模块，如本申请图4实施例中的网络操作方法对应的程序指令/模块(例如，网络操作装置中的接收模块1101、操作模块1102)。处理器1201通过运行存储在存储器1202中的软件程序、指令以及模块实现上述的网络操作方法。
存储器1202可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据设备的使用所创建的数据等。此外，存储器1202可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。
本申请实施例还提供一种包含计算机可执行指令的存储介质，计算机可执行指令在由计算机处理器执行时用于执行一种网络操作方法，该方法包括：
管理节点接收虚拟网络功能信息，其中，虚拟网络功能信息中携带有至少一个网络动态变更标记；至少一个网络动态变更标记用于指示是否支持动态变更网络；管理节点根据所述虚拟网络功能信息对第一类型网络进行操作。
以上所述，仅为本申请的示例性实施例而已，并非用于限定本申请的保护范围。
一般来说，本申请的多种实施例可以在硬件或专用电路、软件、逻辑或其任何组合中实现。例如，一些方面可以被实现在硬件中，而其它方面可以被实现在可以被控制器、微处理器或其它计算装置执行的固件或软件中，尽管本申请不限于此。
本申请的实施例可以通过网络操作装置的数据处理器执行计算机程序指令来实现，例如在处理器实体中，或者通过硬件，或者通过软件和硬件的组合。计算机程序指令可以是汇编指令、指令集架构(Instruction Set Architecture，ISA)指令、机器指令、机器相关指令、微代码、固件指令、状态设置数据、或者以一种或多种编程语言的任意组合编写的源代码或目标代码。
本申请附图中的任何逻辑流程的框图可以表示程序步骤，或者可以表示相互连接的逻辑电路、模块和功能，或者可以表示程序步骤与逻辑电路、模块和功能的组合。计算机程序可以存储在存储器上。存储器可以具有任何适合于本 地技术环境的类型并且可以使用任何适合的数据存储技术实现，例如但不限于只读存储器(Read-Only Memory，ROM)、随机访问存储器(Random Access Memory，RAM)、光存储器装置和系统(数码多功能光碟(Digital Versatile Disc，DVD)或光盘(Compact Disc，CD))等。计算机可读介质可以包括非瞬时性存储介质。数据处理器可以是任何适合于本地技术环境的类型，例如但不限于通用计算机、专用计算机、微处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑器件(Field Programmable Gate Array，FPGA)核处理器架构的处理器。

Claims (10)

  1. 一种网络操作方法，包括：
    管理节点接收虚拟网络功能信息，所述虚拟网络功能信息中携带有至少一个网络动态变更标记；
    所述至少一个网络动态变更标记用于指示是否支持动态变更网络；
    所述管理节点根据所述虚拟网络功能信息对第一类型网络进行操作。
  2. 根据权利要求1所述的方法，其中，所述网络管理节点根据所述虚拟网络功能信息对第一类型网络进行操作，包括：
    所述网络管理节点根据所述虚拟网络功能信息生成虚拟网络功能实例；
    所述网络管理节点根据所述虚拟网络功能实例连接所述第一类型网络。
  3. 根据权利要求1或2所述的方法，其中，所述网络管理节点根据所述虚拟网络功能信息对第一类型网络进行操作，包括：
    在所述第一类型网络运行的情况下，所述网络管理节点根据所述至少一个网络动态变更标记对虚拟网络功能实例与所述第一类型网络的连接关系进行操作。
  4. 根据权利要求3所述的方法，其中，所述网络管理节点根据所述至少一个网络动态变更标记对虚拟网络功能实例与所述第一类型网络的连接关系进行操作，包括：
    所述网络管理节点根据至少一个连接模块的网络动态变更标记，对所述虚拟网络功能实例与所述第一类型网络的连接关系进行操作；
    其中，所述虚拟网络功能实例通过连接模块与所述第一类型网络连接；
    所述连接模块包括以下至少之一：虚拟网络功能模块，虚拟网络功能组件，连接点。
  5. 根据权利要求4所述的方法，其中，所述网络管理节点根据至少一个连接模块的网络动态变更标记，对所述虚拟网络功能实例与所述第一类型网络的连接关系进行操作，包括：
    在所述连接模块的网络动态变更标记为不支持动态变更网络的情况下，所述网络管理节点对所述虚拟网络功能实例与所述第一类型网络的连接关系不进行变更操作；
    或者，在所述连接模块的网络动态变更标记为支持动态变更网络的情况下，所述网络管理节点对所述虚拟网络功能实例与所述第一类型网络的连接关系进行变更操作。
  6. 根据权利要求5所述的方法，其中，所述网络管理节点对所述虚拟网络功能实例与所述第一类型网络的连接关系进行变更操作，包括：
    在所述网络管理节点接收到网络变更请求的情况下，对所述虚拟网络功能实例与所述第一类型网络的连接关系进行变更操作；
    或者，在所述网络数据流满足触发条件的情况下，所述网络管理节点对所述虚拟网络功能实例与所述第一类型网络的连接关系进行变更操作。
  7. 根据权利要求4所述的方法，其中，所述网络管理节点根据至少一个连接模块的网络动态变更标记，对所述虚拟网络功能实例与所述第一类型网络的连接关系进行操作，包括：
    在所述连接模块的网络动态变更标记为支持动态变更网络，且所述虚拟网络功能信息满足预设条件的情况下，所述网络管理节点对所述虚拟网络功能实例与所述第一类型网络的连接关系不进行变更操作。
  8. 一种网络操作装置，包括：
    接收模块，设置为接收虚拟网络功能信息，所述虚拟网络功能信息中携带有至少一个网络动态变更标记；
    所述至少一个网络动态变更标记用于指示是否支持动态变更网络；
    操作模块，设置为根据所述虚拟网络功能信息对第一类型网络进行操作。
  9. 一种管理节点设备，包括：
    存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，其中，所述处理器执行所述计算机程序时，实现如权利要求1-7中任一项所述的网络操作方法。
  10. 一种计算机可读存储介质，存储有计算机程序，所述计算机程序被处理器执行时实现权利要求1-7中任一项所述的网络操作方法。
PCT/CN2020/108582 2019-11-29 2020-08-12 网络操作方法、装置、设备和存储介质 WO2021103657A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP20893814.2A EP4068708A4 (en) 2019-11-29 2020-08-12 METHOD, APPARATUS AND DEVICE FOR EXECUTING OPERATION ON NETWORK, AND STORAGE MEDIUM
US17/780,944 US11855855B2 (en) 2019-11-29 2020-08-12 Network operation method based on network functions virtualization device and storage medium
KR1020227021822A KR102684903B1 (ko) 2019-11-29 2020-08-12 네트워크 작업 방법, 장치, 설비 및 저장매체

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911205628.4A CN111092828B (zh) 2019-11-29 2019-11-29 网络操作方法、装置、设备和存储介质
CN201911205628.4 2019-11-29

Publications (1)

Publication Number Publication Date
WO2021103657A1 true WO2021103657A1 (zh) 2021-06-03

Family

ID=70393790

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/108582 WO2021103657A1 (zh) 2019-11-29 2020-08-12 网络操作方法、装置、设备和存储介质

Country Status (5)

Country Link
US (1) US11855855B2 (zh)
EP (1) EP4068708A4 (zh)
KR (1) KR102684903B1 (zh)
CN (1) CN111092828B (zh)
WO (1) WO2021103657A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220231908A1 (en) * 2019-06-04 2022-07-21 Telefonaktiebolaget Lm Ericsson (Publ) Methods, Function Manager and Orchestration Node of Managing a Port Type
CN111092828B (zh) * 2019-11-29 2024-02-23 中兴通讯股份有限公司 网络操作方法、装置、设备和存储介质
CN115941486B (zh) * 2022-11-04 2024-06-07 苏州浪潮智能科技有限公司 一种集群管理方法、系统、设备以及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106921977A (zh) * 2015-12-26 2017-07-04 华为技术有限公司 一种基于业务流的服务质量规划方法、装置及系统
CN106998560A (zh) * 2016-01-25 2017-08-01 中兴通讯股份有限公司 一种虚拟化网络功能的管理方法、网络设备及系统
WO2017148326A1 (zh) * 2016-03-01 2017-09-08 中兴通讯股份有限公司 一种资源管理方法和装置
CN109995552A (zh) * 2017-12-29 2019-07-09 华为技术有限公司 Vnf服务实例化方法及装置
CN111092828A (zh) * 2019-11-29 2020-05-01 中兴通讯股份有限公司 网络操作方法、装置、设备和存储介质

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9825856B2 (en) 2014-01-06 2017-11-21 Futurewei Technologies, Inc. Service function chaining in a packet network
KR101954786B1 (ko) 2014-11-21 2019-03-06 후아웨이 테크놀러지 컴퍼니 리미티드 서비스 특정 데이터 평면 구성을 변경하기 위한 시스템 및 방법
CN104734931B (zh) * 2015-03-31 2018-06-05 华为技术有限公司 一种虚拟网络功能间链路建立方法及装置
CN106161173A (zh) * 2015-04-15 2016-11-23 中兴通讯股份有限公司 一种实现虚拟网络功能部署规格配置的方法及装置
CN106301829B (zh) * 2015-05-21 2019-08-09 华为技术有限公司 一种网络业务扩容的方法和装置
US20160373297A1 (en) * 2015-06-18 2016-12-22 At & T Intellectual Property I, L.P. Device, system, and method for managing virtual and physical components of a network via use of a registry
CN106685679A (zh) * 2015-11-09 2017-05-17 中兴通讯股份有限公司 一种网络服务部署方法和装置
CN112165424B (zh) * 2016-04-29 2021-07-13 华为技术有限公司 一种业务部署方法、装置以及网元
CN108092790B (zh) * 2016-11-21 2020-06-09 大唐移动通信设备有限公司 一种管理方法及装置
CN109728921B (zh) * 2017-10-27 2021-12-03 华为技术有限公司 虚拟网元的管理、维护和控制方法以及相关装置
US11082299B2 (en) * 2018-03-26 2021-08-03 Apple Inc. Managing virtual links in a network service instance
US20220231908A1 (en) * 2019-06-04 2022-07-21 Telefonaktiebolaget Lm Ericsson (Publ) Methods, Function Manager and Orchestration Node of Managing a Port Type

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106921977A (zh) * 2015-12-26 2017-07-04 华为技术有限公司 一种基于业务流的服务质量规划方法、装置及系统
CN106998560A (zh) * 2016-01-25 2017-08-01 中兴通讯股份有限公司 一种虚拟化网络功能的管理方法、网络设备及系统
WO2017148326A1 (zh) * 2016-03-01 2017-09-08 中兴通讯股份有限公司 一种资源管理方法和装置
CN109995552A (zh) * 2017-12-29 2019-07-09 华为技术有限公司 Vnf服务实例化方法及装置
CN111092828A (zh) * 2019-11-29 2020-05-01 中兴通讯股份有限公司 网络操作方法、装置、设备和存储介质

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
DAN WANG , TAO SUN: "Service-Based Architecture in 5G", NGMN, V1.0, 19 January 2018 (2018-01-19), XP055815779 *
See also references of EP4068708A4

Also Published As

Publication number Publication date
CN111092828B (zh) 2024-02-23
CN111092828A (zh) 2020-05-01
EP4068708A4 (en) 2023-11-29
KR102684903B1 (ko) 2024-07-15
KR20220104241A (ko) 2022-07-26
EP4068708A1 (en) 2022-10-05
US11855855B2 (en) 2023-12-26
US20220417112A1 (en) 2022-12-29

Similar Documents

Publication Publication Date Title
US11893409B2 (en) Securing a managed forwarding element that operates within a data compute node
US11743123B2 (en) Managed switch architectures: software managed switches, hardware managed switches, and heterogeneous managed switches
US20210344692A1 (en) Providing a virtual security appliance architecture to a virtual cloud infrastructure
US10063470B2 (en) Data center network system based on software-defined network and packet forwarding method, address resolution method, routing controller thereof
US9680750B2 (en) Use of tunnels to hide network addresses
WO2016107152A1 (zh) 虚拟机实例的部署方法和装置及设备
EP3482532A1 (en) Automatic service function validation in a virtual network environment
JP2019503599A (ja) クラウドコンピューティングシステムにおけるパケット処理方法、ホスト及びシステム
WO2021103657A1 (zh) 网络操作方法、装置、设备和存储介质
US9590855B2 (en) Configuration of transparent interconnection of lots of links (TRILL) protocol enabled device ports in edge virtual bridging (EVB) networks
WO2018103043A1 (zh) 云计算系统中的报文处理方法及设备
WO2018153355A1 (zh) 控制信息传递方法、服务器和系统
US10708198B1 (en) Methods and apparatus to reduce packet flooding and duplicate packets in a multi-fabric virtual network
WO2022160714A1 (zh) 一种通信方法、装置以及系统
WO2021244483A1 (zh) 一种虚拟化的网络服务的部署方法及装置
CN118972314A (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: 20893814

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20227021822

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020893814

Country of ref document: EP

Effective date: 20220629