WO2018130902A1 - Création massive de fonctions gérées dans un réseau comprenant une fonction de réseau virtualisée - Google Patents

Création massive de fonctions gérées dans un réseau comprenant une fonction de réseau virtualisée Download PDF

Info

Publication number
WO2018130902A1
WO2018130902A1 PCT/IB2017/058482 IB2017058482W WO2018130902A1 WO 2018130902 A1 WO2018130902 A1 WO 2018130902A1 IB 2017058482 W IB2017058482 W IB 2017058482W WO 2018130902 A1 WO2018130902 A1 WO 2018130902A1
Authority
WO
WIPO (PCT)
Prior art keywords
vnf
network
ids
information
moi
Prior art date
Application number
PCT/IB2017/058482
Other languages
English (en)
Inventor
Edwin Tse
Robert Petersen
Jan Groenendijk
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to MX2019008427A priority Critical patent/MX2019008427A/es
Priority to US16/477,755 priority patent/US20190363924A1/en
Priority to CA3050205A priority patent/CA3050205A1/fr
Priority to BR112019014501-0A priority patent/BR112019014501A2/pt
Priority to CN201780088227.8A priority patent/CN110392882A/zh
Publication of WO2018130902A1 publication Critical patent/WO2018130902A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5077—Logical partitioning of resources; Management or configuration of virtualized resources
    • 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/02—Standardisation; Integration
    • H04L41/0233—Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • 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/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • 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
    • 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances

Definitions

  • ETSI Telecommunications Standards Institute
  • NFV Network Functions Virtualization
  • IT information technology
  • the NFVO has two primary responsibilities. The first responsibility is the orchestration of NFVI resources across multiple VIMs, fulfilling the resource orchestration functions. The second responsibility is the lifecycle management of Network Services, e.g., on-boarding new Network Services and VNF Packages, management of the instantiation of VNFMs where applicable, management of the instantiation of VNFs in coordination with VNFMs, etc., and fulfilling the Network Service Orchestration functions.
  • FIG. 2 also illustrates the Operational
  • a method, in an Element Manager (EM) for deploying virtualized Managed Elements (vMEs) in a network includes receiving, from a Network Manager (NM) information that includes a set of Virtualized Network Function (VNF) identifications (IDs) each VNF ID of the set of VNF IDs representing an instantiated VNF, each instantiated VNF corresponding to a desired vME; receiving, from the NM, instructions to deploy the network in accordance with the information; creating a set of Managed Object Instances (MOIs) based on the information; receiving notification when a VNF is instantiated and begins execution, the notification including a corresponding VNF ID; and if the corresponding VNF ID matches a VNF ID from the set of VNF IDs:
  • NM Network Manager
  • VNF Virtualized Network Function
  • an Element Manager for deploying virtualized Managed Elements (vMEs) in a network.
  • the EM includes a communications interface and processing circuitry.
  • the communications interface is configured to: receive, from a Network Manager (NM) information that includes a set of Virtualized Network Function (VNF) identifications (IDs) each VNF ID of the set of VNF IDs representing an instantiated VNF, each instantiated VNF corresponding to a desired vME; and receive, from the NM, instructions to deploy the network in accordance with the information.
  • NM Network Manager
  • VNF Virtualized Network Function
  • the processing circuitry is configured to: create a set of Managed Object Instances (MOIs) based on the information; and upon the communications interface receiving notification when a VNF is instantiated and begins execution, the notification including a corresponding VNF ID, if the corresponding VNF ID matches a VNF ID from the set of VNF IDs: enable an operational state of an MOI from the set of MOIs corresponding to the matched VNF ID.
  • MOIs Managed Object Instances
  • the processing circuitry is further configured to notify the NM, via the communications interface, of the MOI whose operational state is enabled. In some embodiments, the processing circuitry is further configured to return operational control for deploying the network to the NM when all of the information has been processed. In some embodiments, each enabled MOI is linked to a corresponding VNF instance.
  • a method, in a Network Manager (NM) for deploying virtualized Managed Elements, vME, in a network includes requesting a Network Functions Virtualization Orchestrator (NFVO) to instantiate a plurality of Virtualized Network Functions, VNFs, each of the plurality of VNFs corresponding to a desired vME; receiving, from the NFVO a set of VNF identifications (IDs) each VNF ID of the set of VNF IDs corresponds to an instantiated VNF; updating a file by associating the received VNF IDs with corresponding Managed Object Instances (MOIs); and instructing an Element Manager (EM) to deploy the network based on the information in the file.
  • NFVO Network Functions Virtualization Orchestrator
  • a Network Manager for deploying virtualized Managed Elements (vMEs) in a network.
  • the NM includes a communications interface and processing circuitry.
  • the communications interface is configured to: request a Network Functions Virtualization Orchestrator (NFVO) to instantiate a plurality of Virtualized Network Functions (VNFs) each of the plurality of VNFs corresponding to a desired vME; and receive, from the NFVO, a set of VNF identifications (IDs) each VNF ID of the set of VNF IDs corresponding to an instantiated VNF.
  • NFVO Network Functions Virtualization Orchestrator
  • the communications interface is further configured to receive a notification from the EM, the notification indicating at least one MOI whose operational state is enabled.
  • each enabled MOI is linked to a corresponding VNF instance.
  • the processing circuitry is further configured to resume operational control for deploying the network when the EM has processed all of the information in the file.
  • the MOI enabling module is configured to: create a set of MOIs based on the information; and upon the communications interface module receiving notification when a VNF is instantiated and begins execution, the notification including a corresponding VNF ID, if the corresponding VNF ID matches a VNF ID from the set of VNF IDs: enable an operational state of an MOI from the set of MOIs corresponding to the matched VNF ID.
  • an Element Manager (EM) node configured to deploy virtualized Managed Elements (vMEs) in a network
  • the EM node running in a cloud computing environment and the EM node configured to: receive, from a Network Manager (NM) information that includes a set of Virtualized Network
  • NM Network Manager
  • VNF identifications each VNF ID of the set of VNF IDs representing an instantiated VNF, each instantiated VNF corresponding to a desired vME; receive, from the NM, instructions to deploy the network in accordance with the information; create a set of Managed Object Instances (MOIs) based on the information; receive notification when a VNF is instantiated and begins execution, the notification including a corresponding VNF ID; and if the corresponding VNF ID matches a VNF ID from the set of VNF IDs: enable an operational state of an MOI from the set of MOIs corresponding to the matched VNF ID.
  • VNF Visitor Call Object
  • a Network Manager (NM) node configured to deploy virtualized Managed Elements (vMEs) in a network.
  • the NM node runs in a cloud computing environment and the NM node is configured to: request a Network Functions Virtualization Orchestrator (NFVO) to instantiate a plurality of Virtualized Network Functions (VNFs) each of the plurality of VNFs corresponding to a desired vME; receive, from the NFVO, a set of VNF
  • NFVO Network Functions Virtualization Orchestrator
  • an Element Manager to deploy the network based on information in the file.
  • the NM node is further configured to receive a notification from the EM, the notification indicating at least one MOI whose operational state is enabled.
  • each enabled MOI is linked to a corresponding VNF instance.
  • the NM node is further configured to resume operational control for deploying the network when the EM has processed all of the information in the file.
  • FIG. 1 is a block diagram of a typical high-level NFV framework
  • FIG. 2 is a block diagram of an NFV-MANO architectural framework with reference points
  • non-virtualized network elements will be divided into smaller components so that the components can be individually virtualized, and assuming that there would be more virtualized MEs in a Cloud environment, such as across the
  • Processor 14 may be configured to access (e.g., write to and/or reading from) memory 16, which may include any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Readonly Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • memory 16 may be configured to store code executable by processor 14 and/or other data, e.g., data pertaining to communication, e.g., configuration and/or address data of nodes, etc.
  • Processing circuitry 12 may be configured to control any of the methods and/or processes described herein and/or to cause such methods and/or processes to be performed, e.g., by NM 10 functions described herein.
  • NM 10 includes memory 16 that is configured to store data, programmatic software code and/or other information described herein.
  • memory 16 is configured to store VNF/MOI pairing code 20.
  • VNF/MOI pairing code 20 causes processor 14 to perform some or all of the processes performed by NM 10 discussed in detail below with respect to FIG. 5 and FIG. 6 and embodiments discussed herein. It is noted that a single processing circuitry 12 can provide multiple NMs 10.
  • FIG. 4 is a block diagram of an example element manager (EM) 22, configured to perform some of the aspects of the present disclosure.
  • EM 22 may provide a package of end-user functions for management of a set of closely related types of network elements.
  • EM 22 may be responsible for the co- management of some aspects, i.e., the application aspects, of the VNFs of the network.
  • the functions provided by EM 22 may be performed by processing circuitry 24, which includes processor 26 and memory 28.
  • EM 22 may also communicate with other elements in the network via a communications interface 30.
  • EM 22 may also either include a database 31 or have access to database 31.
  • NFVO 38 may provide for the onboarding of new Network Services (NSs) and VNF packages and therefore has access to a NS catalog 44 including the different NSs and VNF catalog 46 including the set of VNF packages.
  • NFVO 38 responsible for orchestration of the NS/VNF instances, maintains an NFV instances repository 48 and NFVI Resources repository 50.
  • NFVO 38 may provide NS lifecycle management including instantiation, scale-out and scale in performance measurements, even correlation and termination.
  • the operator is aware of the number and kinds of MEs and vMEs desired.
  • the operator may know the type of PNF needed.
  • the operator may obtain this knowledge, for example, from the ME vendor who implemented the ME using one PNF.
  • the operator knows the number and the types of VNFs 34 needed.
  • the operator may obtain this knowledge, for example, from the vME vendor who implemented the vME using VNFs 34.
  • the operator instructs NM 10 to implement the network using information of the File (Step SI 00).
  • NM based on information in the File and the information described above in the pre-conditions to deployment, sends NFVO 38 an "update network service operation request" indicating that NM 10 would like a new VNF instance to be placed into an existing network service instance (Step SI 10).
  • NFVO 38 then sends VNFM 40 a "create NVF identifier operation" request (Step Si l l).
  • VNFM 40 had created the VNF instance in an instance tree, which contains multiple VNF instances, and which is stored in database 41.
  • VNFM 40 may change the state of the VNF instance from NOT INSTNTIATED to INSTANTIATED (Step SI 16). VNFM 40 may respond positively to NFVO 38, informing NFVO 38 that the VNF instance has been instantiated (Step SI 17). NFVO 38 may respond to NM 10 with an instantiated PNF ID for each ME wanted and a set of instantiated VNF IDs for each vME wanted (Step SI 18).
  • NM 10 may update the File by capturing the received PNF ID in an attribute, called, for example, assigned-ID, of the corresponding MOI and by capturing the received VNF ID(s) in an attribute, called, for example, assigned-ID, of the corresponding MOI (Step S120). NM 10 may then instruct EM 22 to deploy the network in accordance with the File information (Step SI 30). EM 22 then creates a set of MOIs in database 31 in accordance with the File information (Step S140). For an MOI representing a PNF, the MOI's assigned-ID attribute has the PNF ID. The MOI operational state may be set to Disabled. For an MOI representing a VNF 34, the MOI's assigned-ID attribute has the VNF ID. The MOI operational state may be set to Disabled.
  • EM 22 may then be notified when a VNF 34 and/or a PNF is instantiated and starts to execute (Step SI 50).
  • the PNF may notify EM 22 of its (the PNF's) presence indicating its own PNF ID and its address.
  • the VNF 34 may notify EM 22 of its (the VNF's) presence indicating its own VNF ID and its address.
  • EM 22 on reception of notification bearing the VNF ID about a VNF presence, searches database 31 for the MOI whose assigned-ID attribute value is same as the VNF ID received. When found, the MOI operational state may be changed to Enabled.
  • the method further includes notifying the NM 10 of the MOI whose operational state is enabled. In another embodiment, the method further includes returning operational control for deploying the network to the NM 10 when all of the information has been processed. In another embodiment, each enabled MOI is linked to a corresponding VNF instance.
  • Processor 14 in conjunction with VNF ID/MOI pairing code 20, updates a file by associating the received VNF IDs with their corresponding MOI (Block S240), and instructs an EM 22 to deploy the network based on the information in the file (Block S260).
  • FIG. 8 is a block diagram of an alternate NM 10 for deploying virtualized vMEs in a network.
  • NM 10 includes a communications interface module 52 configured to request NFVO 38 to instantiate a plurality of VNFs 34, where each of the plurality of VNF 34s corresponds to each desired vME, and receive, from NFVO 38, a set of VNF IDs, where each VNF ID of the set of VNF IDs corresponds to an instantiated VNF.
  • NM 10 also includes a VNF ID/MOI pairing module 54 configured to update a file associating the received VNF IDs with their corresponding MOI, and instruct, via communications interface module 52, an EM 22, to deploy the network in accordance with information in the file.
  • FIG. 9 is a block diagram of an alternate EM 22 for deploying vMEs, in a network.
  • EM 22 includes a communications interface module 56 configured to receive, from an NM 10, information that includes a set of VNF IDs, each VNF ID in the set of VNF IDs representing an instantiated VNF, each instantiated VNF corresponding to a desired vME, and receive, from NM 10, instructions to deploy the network in accordance with the information.
  • EM 22 also includes an MOI enabling module 58 configured to create a set of MOIs in accordance with the information.
  • NM 10 and EM 22 are configured to operate in a cloud-based environment such as, for example, the Internet.
  • an EM node e.g., EM 22
  • the EM node may run in a cloud computing environment providing processing circuits (e.g., processing circuitry 24 and/or processor 26) and memory (e.g., memory 28) for running the node, the memory containing instructions executable by the processing circuits.
  • the NM node is configured to request a NFVO 38 to instantiate a plurality of VNFs 34, where each of the plurality of VNFs 34 corresponds to each desired vME, receive, from the NFVO 38, a set of VNF IDs, where each VNF ID of the set of VNF IDs corresponds to an instantiated VNF 34, update a file by associating the received VNF IDs with their corresponding MOIs, and instruct, an EM 22 to deploy the network based on information in the file.
  • the NM node is further configured to receive a notification from the EM, the notification indicating at least one MOI whose operational state is enabled. In another embodiment, the NM node is further configured to resume operational control for deploying the network when the EM has processed all of the information in the file. In another embodiment, each enabled MOI is linked to a corresponding VNF instance.
  • NM 10 and EM 22 are configured to operate in a cloud computing environment 59 such as, for example, the Internet.
  • FIG. 10 is an illustration of a cloud computing environment 59, which includes NM 10 and EM 22.
  • Cloud computing environment 59 may include one or more sets of processing circuits and memory for running the NM 10 and EM 22, where the memory contains instructions executable by the processing circuits.
  • the processing circuits and memory are configured to perform any of the methods disclosed herein.
  • cloud computing environment 59 includes NM 10 and EM 22.
  • NM 10 may include, for example, processing circuit 60a and memory 62a, processing circuit 60b and memory 62b and processing circuit 60c and memory 62c.
  • the disclosure is not limited to a specific number of processing circuits and/or memory and thus the illustration in FIG. 10 of three sets of processing circuits and memory in cloud computing environment 59 is merely exemplary and the present disclosure may include any number of processing circuits and corresponding memory.
  • EM 22 may include, for example, processing circuit 60d and memory 62d, processing circuit 60e and memory 62e and processing circuit 60n and memory 62n.
  • processing circuit 60a to 60n are referred to collectively as "processing circuit 60".
  • Memory 62a to 62n are referred to collectively as "memory 62".
  • EM 22 and NM 10 may reside on the same or overlapping processing circuits 60 and memory 62, and thus the separation of EM 22 and NM 10 is FIG. 10 is purely to aid understanding.
  • the method further includes notifying the NM 10 of the MOI whose operational state is enabled. In some embodiments, the method further includes returning operational control for deploying the network to the NM 10 when all of the information has been processed. In some embodiments, each enabled MOI is linked to a corresponding VNF 34 instance.
  • an EM 22 for deploying vMEs in a network includes a communications interface 30 and processing circuitry 24.
  • the communications interface 30 is configured to: receive, from a NM 10 information that includes a set VNF IDs, each VNF ID of the set of VNF IDs representing an instantiated VNF 34, each instantiated VNF 34 corresponding to a desired vME; and receive, from the NM 10, instructions to deploy the network in accordance with the information.
  • the method further includes receiving a notification from the EM 22, the notification indicating at least one MOI whose operational state is enabled.
  • each enabled MOI is linked to a corresponding VNF 34 instance.
  • the method further includes resuming operational control for deploying the network when the EM 22 has processed all of the information in the file.
  • the communications interface 18 is further configured to receive a notification from the EM 22, the notification indicating at least one MOI whose operational state is enabled.
  • each enabled MOI is linked to a corresponding VNF 34 instance.
  • the processing circuitry 12 is further configured to resume operational control for deploying the network when the EM 22 has processed all of the information in the file.
  • an EM 22 for deploying vMEs in a network includes a communications interface module 56 and a MOI enabling module 58.
  • the communications interface module 56 is configured to: receive, from a NM 10, information that includes a set of VNF IDs, each VNF ID of the set of VNF IDs representing an instantiated VNF 34, each instantiated VNF 34 corresponding to a desired vME; and receive, from the NM 10, instructions to deploy the network in accordance with the information.
  • the MOI enabling module 58 is configured to create a set of MOIs based on the information; and upon the communications interface module 56 receiving notification when a VNF 34 is instantiated and begins execution, the notification including a corresponding VNF ID, if the corresponding VNF ID matches a VNF ID from the set of VNF IDs: enable an operational state of an MOI from the set of MOIs corresponding to the matched VNF ID.
  • a NM 10 for deploying vMEs in a network includes a communications interface module 52 and a VNF ID MOI pairing module 54.
  • the communications interface module 52 is configured to: request a NFVO 38 to instantiate a plurality of VNFs 34, each of the plurality of VNFs 34 corresponding to each desired vME; and receive, from the NFVO 38, a set of VNF IDs, each VNF ID of the set of VNF IDs corresponding to an instantiated VNF 34.
  • the VNF ID MOI pairing module 54 is configured to: update a file by associating the received VNF IDs with corresponding MOIs; and instruct, via the communications interface module 52, an EM 22 to deploy the network based on information in the file.
  • an EM node 22, configured to deploy vMEs in a network is provided.
  • the EM node 22 runs in a cloud computing environment 59 and the EM node 22 is configured to: receive, from a NM 10, information that includes a set of VNF IDs, each VNF ID of the set of VNF IDs representing an instantiated VNF 34, each instantiated VNF 34 corresponding to a desired vME; receive, from the NM 10, instructions to deploy the network in accordance with the information; create a set of MOIs based on the information; receive notification when a VNF 34 is instantiated and begins execution, the notification including a corresponding VNF ID; and if the corresponding VNF ID matches a VNF ID from the set of VNF IDs: enable an operational state of an MOI from the set of MOIs corresponding to the matched VNF ID.
  • the EM node 22 is further configured to notify the NM 10 of the MOI whose operational state is enabled. In some embodiments, the EM node 22 is further configured to return operational control for deploying the network to the NM 10 when all of the information has been processed. In some embodiments, each enabled MOI is linked to a corresponding VNF 34 instance.
  • a NM node 10 configured to deploy vMEs in a network.
  • the NM node 10 runs in a cloud computing environment 59 and the NM node 10 is configured to: request a NFVO 38 to instantiate a plurality of VNFs 34, each of the plurality of VNFs 34 corresponding to each desired vME;
  • VNFVO 38 receives, from the NFVO 38, a set of VNF IDs, each VNF ID of the set of VNF IDs corresponding to an instantiated VNF 34; update a file by associating the received VNF IDs with corresponding MOIs; and instruct, via the communications interface, an EM 22 to deploy the network based on information in the file.
  • the NM node 10 is further configured to receive a notification from the EM 22, the notification indicating at least one MOI whose operational state is enabled. In some embodiments, each enabled MOI is linked to a corresponding VNF 34 instance. In some embodiments, the NM node 10 is further configured to resume operational control for deploying the network when the EM 22 has processed all of the information in the file.
  • the concepts described herein may be embodied as a method, data processing system, and/or computer program product. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a "circuit" or "module.” Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.
  • These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other
  • Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Java® or C++.
  • the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language.
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer.
  • the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
  • LAN local area network
  • WAN wide area network
  • Internet Service Provider for example, AT&T, MCI, Sprint, EarthLink, MSN, GTE, etc.

Landscapes

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

Abstract

Selon l'invention, un procédé, un gestionnaire d'éléments (EM), un gestionnaire de réseau (NM), un nœud EM et un nœud NM sont configurés pour déployer des éléments gérés virtualisés (vMEs) dans un réseau. Le procédé consiste à : recevoir, d'un NM, des informations comprenant un ensemble d'identifiants de fonction de réseau virtualisée (VNF), chaque ID de l'ensemble d'ID de VNF représentant une VNF instanciée, chaque VNF instanciée correspondant à un vME souhaité; recevoir, du NM, des instructions visant à déployer le réseau conformément aux informations; créer un ensemble d'instances d'objets gérés (MOI) d'après les informations; recevoir une notification lorsqu'une VNF est instanciée et commence l'exécution, la notification comprenant un identifiant de VNF correspondant; et si l'ID de VNF correspondant correspond à un ID de l'ensemble d'ID de VNF, activer un état opérationnel d'un MOI de l'ensemble de MOI qui correspond à l'ID de VNF apparié.
PCT/IB2017/058482 2017-01-13 2017-12-28 Création massive de fonctions gérées dans un réseau comprenant une fonction de réseau virtualisée WO2018130902A1 (fr)

Priority Applications (5)

Application Number Priority Date Filing Date Title
MX2019008427A MX2019008427A (es) 2017-01-13 2017-12-28 Creacion masiva de funciones administradas en una red que incluye funcion de red virtualizada.
US16/477,755 US20190363924A1 (en) 2017-01-13 2017-12-28 Bulk creation of managed functions in a network that includes virtualized network function
CA3050205A CA3050205A1 (fr) 2017-01-13 2017-12-28 Creation massive de fonctions gerees dans un reseau comprenant une fonction de reseau virtualisee
BR112019014501-0A BR112019014501A2 (pt) 2017-01-13 2017-12-28 Método para implementar os elementos gerenciados virtualizados, gerenciadores de elemento e de rede, e, nós do gerenciador de elemento e do gerenciador de rede
CN201780088227.8A CN110392882A (zh) 2017-01-13 2017-12-28 在包括虚拟化网络功能的网络中批量创建被管功能

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762446105P 2017-01-13 2017-01-13
US62/446,105 2017-01-13

Publications (1)

Publication Number Publication Date
WO2018130902A1 true WO2018130902A1 (fr) 2018-07-19

Family

ID=61028100

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2017/058482 WO2018130902A1 (fr) 2017-01-13 2017-12-28 Création massive de fonctions gérées dans un réseau comprenant une fonction de réseau virtualisée

Country Status (6)

Country Link
US (1) US20190363924A1 (fr)
CN (1) CN110392882A (fr)
BR (1) BR112019014501A2 (fr)
CA (1) CA3050205A1 (fr)
MX (1) MX2019008427A (fr)
WO (1) WO2018130902A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112087818A (zh) * 2019-06-14 2020-12-15 中国移动通信有限公司研究院 一种标识分配方法、数据采集方法、设备管理方法及设备

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11327787B2 (en) * 2016-08-17 2022-05-10 Apple Inc. Using a managed object operation to control a lifecycle management operation
US11382150B2 (en) * 2018-03-26 2022-07-05 Apple Inc. System and method of managing PNF connectivity in a network slice instance
GB2573283B (en) * 2018-04-26 2020-04-29 Metaswitch Networks Ltd Improvements relating to network functions virtualization
CN112910673B (zh) * 2019-12-04 2023-05-09 中国移动通信有限公司研究院 一种确定网元部署信息的方法、装置、设备及存储介质
CN111131026B (zh) * 2019-12-26 2022-06-21 深信服科技股份有限公司 一种通信方法、装置、设备和存储介质
CN113254143B (zh) * 2020-02-11 2023-11-21 中国电信股份有限公司 虚拟化网络功能网元编排调度方法、装置和系统
JP7409504B2 (ja) * 2020-07-03 2024-01-09 日本電信電話株式会社 ネットワーク仮想化システム、仮想リソース管理装置、仮想リソース管理方法およびプログラム
CN114650224B (zh) * 2020-12-21 2023-06-30 北京金山云网络技术有限公司 节点功能的配置方法、装置、电子设备及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150381423A1 (en) * 2014-06-26 2015-12-31 Futurewei Technologies, Inc. System and Method for Virtual Network Function Policy Management
US20160212016A1 (en) * 2015-01-20 2016-07-21 Huawei Technologies Co., Ltd. Method and Apparatus for NFV Management and Orchestration
EP3068157A1 (fr) * 2015-03-13 2016-09-14 Comptel Corporation Gestion de réseau

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104410672B (zh) * 2014-11-12 2017-11-24 华为技术有限公司 网络功能虚拟化应用升级的方法、转发业务的方法及装置
EP3249860A4 (fr) * 2015-01-23 2018-01-24 Nec Corporation Procédé, dispositif et programme pour une gestion et une orchestration de virtualisation de fonction de réseau
CN106302068A (zh) * 2015-05-11 2017-01-04 中兴通讯股份有限公司 虚拟网络功能vnf的虚拟资源的管理方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150381423A1 (en) * 2014-06-26 2015-12-31 Futurewei Technologies, Inc. System and Method for Virtual Network Function Policy Management
US20160212016A1 (en) * 2015-01-20 2016-07-21 Huawei Technologies Co., Ltd. Method and Apparatus for NFV Management and Orchestration
EP3068157A1 (fr) * 2015-03-13 2016-09-14 Comptel Corporation Gestion de réseau

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication Management; Configuration Management (CM) for mobile networks that include virtualized network functions; Requirements (Release 14)", 3GPP STANDARD; 3GPP TS 28.510, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE, vol. SA WG5, no. V1.1.0, 28 November 2016 (2016-11-28), pages 1 - 18, XP051229850 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112087818A (zh) * 2019-06-14 2020-12-15 中国移动通信有限公司研究院 一种标识分配方法、数据采集方法、设备管理方法及设备
CN112087818B (zh) * 2019-06-14 2022-11-15 中国移动通信有限公司研究院 一种标识分配方法、数据采集方法、设备管理方法及设备

Also Published As

Publication number Publication date
BR112019014501A2 (pt) 2020-02-18
CN110392882A (zh) 2019-10-29
MX2019008427A (es) 2019-09-19
US20190363924A1 (en) 2019-11-28
CA3050205A1 (fr) 2018-07-19

Similar Documents

Publication Publication Date Title
US20190363924A1 (en) Bulk creation of managed functions in a network that includes virtualized network function
US11157304B2 (en) System for peering container clusters running on different container orchestration systems
US10719367B1 (en) Management of workers executing program code functions
US20190140895A1 (en) Api gateway for network policy and configuration management with public cloud
US10778798B2 (en) Remote service access in a container management system
US10452372B2 (en) Method and deployment module for managing a container to be deployed on a software platform
US10985996B2 (en) Methods, systems and apparatus for custom interface specification in a cloud management system
US11061737B2 (en) Methods, systems and apparatus for governance of virtual computing infrastructure resources
US8843914B1 (en) Distributed update service
CN107967140B (zh) 软件修改的发起方法、发布元数据的方法及装置
US20180316559A1 (en) Managing virtual network functions
WO2016119631A1 (fr) Procédé d'accès à un service en nuage et à un dispositif d'accès
CN109075986B (zh) 一种网络功能实例的管理方法及相关设备
US10140140B2 (en) Cloud virtual machine customization using extension framework
US10367696B2 (en) Automatic network management system and methods
CN106936619B (zh) 部署网络服务的方法和装置
US10324701B1 (en) Rapid deployment of computing instances
US11314545B2 (en) Predicting transaction outcome based on artifacts in a transaction processing environment
US10999150B2 (en) Methods, systems and apparatus for dynamically extending a cloud management system by adding endpoint adapter types
US20170339003A1 (en) Automatic network mangement system and methods
Aslam et al. Service provisioning for the WSN cloud
US9342291B1 (en) Distributed update service
KR102623631B1 (ko) Nfv 환경에서의 vnf 자동 설정 방법 및 이를 위한 nfv mano
CN108370329B (zh) 管理功能对象的管理方法及装置
CN116150273A (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: 17835712

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 3050205

Country of ref document: CA

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112019014501

Country of ref document: BR

122 Ep: pct application non-entry in european phase

Ref document number: 17835712

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 112019014501

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20190712