WO2016118636A1 - Method and apparatus for nfv management and orchestration - Google Patents
Method and apparatus for nfv management and orchestration Download PDFInfo
- Publication number
- WO2016118636A1 WO2016118636A1 PCT/US2016/014146 US2016014146W WO2016118636A1 WO 2016118636 A1 WO2016118636 A1 WO 2016118636A1 US 2016014146 W US2016014146 W US 2016014146W WO 2016118636 A1 WO2016118636 A1 WO 2016118636A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- vnf
- vnfs
- request
- nfvi
- network
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 47
- 230000006870 function Effects 0.000 claims abstract description 48
- 238000012545 processing Methods 0.000 claims description 21
- 230000004044 response Effects 0.000 claims description 15
- 238000003860 storage Methods 0.000 claims description 7
- 238000004590 computer program Methods 0.000 claims description 6
- 238000010586 diagram Methods 0.000 description 23
- 230000011664 signaling Effects 0.000 description 6
- 230000006854 communication Effects 0.000 description 5
- 238000004891 communication Methods 0.000 description 5
- 239000000203 mixture Substances 0.000 description 3
- 230000004075 alteration Effects 0.000 description 2
- 230000010354 integration Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000003542 behavioural effect Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007175 bidirectional communication Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000012517 data analytics Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
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/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]
-
- 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
-
- 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
-
- 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
- H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/302—Route determination based on requested QoS
- H04L45/306—Route determination based on the nature of the carried application
Definitions
- the present invention relates to a method and apparatus for network virtualization, and, in particular embodiments, to a method and apparatus for network functions virtualization (NFV)-management and orchestration (MANO).
- NFV network functions virtualization
- MANO network management and orchestration
- an orchestrator typically has access to data repositories including a network services catalog, a virtualized network function (VNF) catalog, a NFV Instances repository, and a NFV infrastructure (NFVI) resources repository.
- VNF virtualized network function
- NFVI NFV infrastructure
- the network services catalog is a repository of all the on-boarded network services. It includes a network services descriptor (NSD), a virtual link descriptor (VLD) and a VNF forwarding graph descriptor (VNFFGD).
- the VLD describes resource requirements that are needed for a link between VNFs, physical network functions (PNF) and endpoints.
- the VNFFGD includes a network forwarding path (NFP) element that includes an ordered list of connection points along with rules/policies associated to the list.
- the VNF catalog is a repository of all the on-boarded VNF packages, and includes a VNF descriptor (VNFD) and software images.
- VNFD describes a VNF in terms of its deployment and operational behavior, and is used by a virtual network function manager (VNFM) to instantiate the VNF and for lifecycle management of the VNF.
- VNFM virtual network function manager
- the NFV instances repository holds information of all VNF instances and network service (NS) instances.
- Each VNF instance is represented by a VNF record, and each NS instance is represented by an NS record.
- the NFVI resources repository holds information about the available/reserved/ allocated NFVI resources as abstracted by a virtual infrastructure manager (VIM) across an operator's infrastructure domains, and is used for resource reservation, allocation and monitoring.
- VIP virtual infrastructure manager
- a method for network function virtualization (NFV)-management and orchestration (MANO) includes receiving, by a processing system, a customer request for a network service.
- the method also includes generating a virtualized network function (VNF)-forwarding graph (FG) based on the customer request.
- VNF-FG includes a plurality of VNFs.
- An apparatus for performing this method is also provided.
- a computer program product including a non-transitory computer readable storage medium.
- the non- transitory computer readable storage medium stores programming that includes instructions to generate a virtualized network function (VNF)-forwarding graph (FG) based on a customer request for a network service.
- VNF virtualized network function
- FG forwarding graph
- the VNF-FG includes a plurality of VNFs.
- FIG. 1 illustrates a block diagram of an embodiment system for performing NFV-
- FIG. 2 illustrates a block diagram of another embodiment system for performing NFV-MANO
- FIG. 3 illustrates a flowchart of an embodiment method for NFV-MANO
- FIG. 4 illustrates a block diagram of yet another embodiment system for performing NFV-MANO
- FIG. 5 illustrates a sequence diagram of another embodiment method for NFV- MANO
- FIG. 6 illustrates a block diagram of yet another embodiment system for performing NFV-MANO
- FIG. 7 illustrates a sequence diagram of yet another embodiment method for NFV-
- FIG. 8 illustrates a block diagram of yet another embodiment system for performing NFV-MANO
- FIG. 9 illustrates a sequence diagram of yet another embodiment method for NFV- MANO
- FIG. 10 illustrates a diagram of yet another embodiment system for performing NFV- MANO
- FIG. 11 illustrates a diagram of yet another embodiment system for performing NFV- MANO
- FIG. 12 illustrates a flowchart of an embodiment method for NFV-MANO
- FIG. 13 illustrates a block diagram of an embodiment processing system
- FIG. 14 illustrates a block diagram of an embodiment transceiver.
- an orchestrator receives a network service (NS) request, and determines a virtualized network function (VNF)-forwarding graph (FG) based on the NS request.
- NS network service
- VNF virtualized network function
- FG forwarding graph
- a VNF- FG is predefined for each available NS request, and NS requests and VNF-FGs may be defined manually.
- the orchestrator may select a VNF-FG that is corresponding to the NS request from a NS catalog.
- aspects of the present disclosure provide methods for generating a VNF-FG from a customer request for a network service.
- the VNF-FG is generated using network service information included in the customer request.
- the VNF-FG is not predefined but generated automatically based on the customer request.
- a NS request may also be constructed using the network service information of the customer request and the VNF-FG, and may be added to a NS repository or catalog.
- aspects of the present disclosure also provide various embodiment systems for performing NFV-MANO, in which a VNF-FG is generated based on a customer request.
- VNF-FG NFV infrastructure (NFVI)-points of presence (PoPs) for VNFs in the VNF-FG, and instantiation of the VNFs may be performed by one software entity or by different software entities.
- FIG. 1 illustrates a block diagram of an embodiment NFV-MANO system 100 which may be deployed as an ETSI NFV-MANO system.
- the system 100 includes an orchestrator 102, a virtual network function manager (VNFM) 104, and a virtual infrastructure manager (VIM) 106.
- the orchestrator 102 is in charge of the network wide orchestration and management of NFV resources, as well as realizing NFV service topologies on NFVI.
- the orchestrator 102 may be configured to manage NFVI resources across multiple VIMs and lifecycles of network services.
- a VNFM 104 is configured to provide lifecycle management of VNF instances
- a VIM 106 is configured to control and manage NFVI computing, storage and network resources within a domain.
- the orchestrator 102 receives a network request 108 such as a network service request.
- the orchestrator 102 determines a forwarding graph (FG).
- the determination of the forwarding graph is done in accordance with a NS catalog 110.
- a network service is a composition of network functions and is defined by its functional and behavioral specifications.
- a network service request may be described by a VNF-FG, and a VNF-FG is predefined for each network service.
- a VNF-FG defines a logical topology corresponding to a requested network service.
- a network function (NF) forwarding graph is a graph of logical links connecting NF nodes for the purpose of describing traffic flow between these NF nodes.
- a VNF-FG is a NF forwarding graph where at least one NF node is a VNF node.. . VNF-FGs may be developed by service providers or by their system integration partners.
- a network service (NS) catalog may be viewed as a network service database that can map a network service to a corresponding VNF-FG.
- the orchestrator 102 receiving the network request 108 may select the corresponding VNF-FG for the network request 108 from the network service database.
- NS request may include a network service with a corresponding VNF-FG, or a network service described by a VNF-FG.
- VNF-FG and FG
- NFVI-PoP and “PoP” are also used interchangeably.
- the orchestrator 102 may determine NFVI-PoPs for the VNFs included in the VNF- FG, and instantiate the VNFs at the determined NFVI-PoPs.
- a NFVI-PoP is a network point of presence where a network function is or could be deployed as a VNF.
- Instantiation of a VNF herein refers to creating an instance of the VNF on one or more physical network devices corresponding to a NFVI-PoP.
- a Software defined topology (SDT) entity may establish a virtual network topology or a virtual data-plane logical topology for a service.
- An SDT entity autonomously creates a virtual network topology in accordance with network service requirements.
- an SDT entity may determine an FG, including the number of instances of network functions in the FG.
- the SDT entity may also determine forwarding paths (e.g., for the control plane and data plane) and a point of presences (PoP) for each network function in the FG.
- an SDT entity may be implemented as a function within a topology manager, and the topology manager may generate an FG based on a customer request and perform functions of an orchestrator as well.
- SDT entities may be combined with NFV entities.
- an SDT entity is a virtual function instantiated by an NFV-MANO.
- a SDT entity provides a logical topology to an orchestrator corresponding to a NS request, and may communicate with the orchestrator via an management interface between the SDT entity and the orchestrator.
- Input to an SDT entity may include a network service request, traffic information, NFVI information, and a trigger.
- the network service request provides a service traffic description, which may include node distribution, traffic characteristics, etc.
- the network service request may also provide a service function description, which may include service function chains or a VNF-FG, and function characteristics. Examples of function chains and function characteristics include a stateless function or a state-full function, function overhead on storage, CPU, and traffic rate, and function instantiation constraints, such as a minimum or maximum number of PoPs, and preferred/un-preferred PoPs.
- Traffic quality requirements may include traffic QoS requirements and user quality of experience (QoE) requirements.
- NFVI information may include PoP locations, per-PoP function availability, and per-
- the NFVI information may include statistical load, delay, capacity between devices, base stations (BSs), routers, and NFVI-PoPs, as well as nominal remaining network resources, such as physical link capacities, and radio resources.
- a triggering event may initiate a change in a network service.
- the triggering event occurs after a timeout period or when a performance condition is satisfied, e.g., when a service, SDT, and/or a traffic engineering (TE) performance metric falls below, or rises above, a threshold.
- TE traffic engineering
- the triggering event is elicited by a human action, e.g., a service provider manually prompts the triggering event.
- FIG. 2 illustrates a block diagram of an embodiment system 200 for performing NFV-MANO.
- the system 200 includes a topology manager 202, a VNFM 204, and a VIM 206.
- the topology manager 202 may be a software module or entity that is configured to perform the functions of an orchestrator as well as generates an FG based on a customer request 208.
- the topology manager 202 may translate an incoming customer request into a VNF-FG, which, in essence, is a logical topology (or graph) including service specific VNFs (or vertices) interconnected by logical links (or edges).
- the topology manager 202 may use SDT techniques to generate an FG.
- a VNF catalog 210 may comprise a database of various VNFs that can be instantiated, and may be accessed by the Topology Manager 202 in the instantiation of VNFs in the FG.
- FIG. 3 illustrates a flowchart for an embodiment method 300 of NFV-MANO that may be used in the system 200 in FIG. 2.
- a topology manager receives a customer request for a network service (Step 302) from a customer.
- the topology manager In response to the receipt of the customer request, the topology manager generates, or determines, a VNF-FG according to the customer request (Step 304).
- a customer request may include a checklist of basic network components or service requirements that is used to build a VNF-FG.
- the customer may request a Long Term Evolution (LTE) network (e.g., from a list of templates) and additional service specific network functions.
- LTE Long Term Evolution
- the topology manager may construct a network service by use of the checklist, and generate a VNF-FG according to the constructed network service, e.g., using a network service catalog.
- the VNF-FG may include additional VNFs that are not service specific but relevant to assessing and enhancing network performance, e.g., the VNF-FG may include VNFs for traffic analytics or QoE monitor. These additional VNFs may also be accessible from a VNF catalog.
- the topology manager may then determine a NFVI-PoP for each of the VNFs in the VNF-FG (Step 306).
- a NFVI-PoP is a network point of presence where a network function is or could be deployed as a VNF.
- the topology manager may identify NFVI-PoPs corresponding to the VNFs in the VNF-FG in a physical network where the forwarding graph may be embedded.
- a NFVI-PoP associated with a VNF may be determined by checking the feasibility of a plurality of available NFVI-PoPs that can support the VNF, e.g., using the NFVI information that is accessible via a VIM, and selecting a feasible NFVI-PoP from the plurality of available NFVI-PoPs.
- the topology manager can then instantiate the VNFs at the determined NFVI- PoPs using one or more VNFMs and VIMs (Step 308).
- the topology manager may instruct one or more VNFMs and VIMs to instantiate the corresponding VNFs.
- a VIM may reserve a container, e.g., a computing resource at a network node, for each of the VNFs, and a VNFM may instantiate the VNFs on the containers.
- the topology manager may jointly, instead of sequentially, determine the VNF-FG and NFVI-PoPs.
- An event/instruction may prompt a VIM or a VNFM to instruct, or request that, the topology manager move a VNF to a new PoP.
- the topology manager may move the VNF to the new PoP by performing a sequence of steps that is similar to Steps 306-308.
- FIG. 4 illustrates a block diagram of another embodiment system 400 for performing
- the system 400 includes an SDT-FG entity 402, an SDT-PoP entity 404, a VNFM 406, and a VIM 408.
- the SDT-FG entity 402 and the SDT-PoP entity 404 are software modules or entities for generating a forwarding graph based on a customer request 410 and determining PoPs for VNFs in the forwarding graph, respectively.
- the SDT-FG entity 402 may use SDT techniques to generate a forwarding graph based on the customer request 410.
- the SDT-PoP entity 404 may also be configured to instruct instantiation of the VNFs in the forwarding graph using the one or more VNFMs 406 and one or more VIMs 408.
- service requirements corresponding to the customer request 410 may be translated by the SDT-FG entity 402 into a forwarding graph, which includes VNFs and logical links.
- the resulted forwarding graph may then be provided to the SDT-PoP entity 404 as a NS request.
- PoPs corresponding to the VNFs may be determined by the SDT-PoP entity 404, which may generate instructions to the VNFMs 406 and VIMs 408 to instantiate the VNFs at the corresponding PoPs.
- FIG. 5 illustrates a message flow diagram for an embodiment method 500 of NFV-
- An SDT-FG entity 502 receives a customer request for a network service (Step 552) from a customer 506, and generates or determines a VNF-FG according to the customer request (Step 554).
- the SDT-FG entity 502 may use or combine basic network services provided in the customer request to construct a new network service, and generate a VNF-FG using the new network service and a network service catalog.
- the SDT-FG entity 502 may construct and send a network service (NS) request to an SDT-PoP entity 504 (Step 556).
- the NS request may include the generated VNF-FG and a network service corresponding to the VNF-FG.
- the NS request may be constructed by the SDT-FG entity 502.
- the SDT-PoP entity 504 upon receipt of the NS request, may determine NFVI-PoPs for the VNFs indicated in the VNF-FG (Step 558) and instantiate the VNFs using one or more VNFMs and VIMs (Step 560).
- the FG and the NFVI-PoPs are determined sequentially by the SDT-FG entity 502 and the SDT-PoP entity 504, respectively. Further, the FG and the NFVI-PoPs are determined and provided by different entities, which may be beneficial because the SDT-FG entity 502 and the SDT-PoP entity 504 may be supported and maintained by different vendors. Each of the SDT-FG entity 502 and the SDT-PoP entity 504 may have an interface defined so that they may communicate with each other.
- a trigger message of this trigger may be forwarded to the SDT-PoP entity 504, which may repeat the steps of 558 and 560 determining new NFVI-PoPs and instantiating the VNFs at the new PoPs.
- FIG. 6 illustrates a block diagram of another embodiment system 600 for performing NFV-MANO.
- the system 600 includes an SDT-FG entity 602, an orchestrator 604, a VNFM 606, and a VIM 608.
- the SDT-FG entity 602 is configured to generate an FG based on a customer request 610. This generated FG can be used to update a NS catalogs 614 with the generated FG and network service information included in the customer request 610. For example, upon receipt of the customer request 610, the SDT-FG entity 602 may translate the service requirements of the customer request into an FG.
- the FG is provided to orchestrator 604.
- the orchestrator 604 is configured to determine PoPs for VNFs in the FG and instruct the instantiation of the VNFs using the one or more VNFMs 606 and one or more VIMs 608 at the corresponding PoPs.
- the SDT-FG entity 602 may construct a NS request using the generated FG and send the NS request to the orchestrator 604 for determination of PoPs of VNFs and instantiation.
- the system 600 may be built upon the NFV-MANO system 100 as shown in FIG. 1, where the output of the SDT-FG entity 602, i.e., the NS request, is used as the input of the NFV-MANO system 100.
- FIG. 1 the output of the SDT-FG entity 602, i.e., the NS request
- An SDT-FG entity 702 receives a customer request for a network service (Step 752) from a customer 712. In response to the receipt of customer requests 752, SDT-FG 702 determines or generates an FG corresponding to the customer request (Step 754). In one embodiment, the SDT-FG entity 702 may generate the FG using network service templates and a checklist including basic network functions. The SDT-FG entity 702 then constructs a NS request which includes the customer request information and the generated FG, and adds the NS request to a NS repository or catalog (Step 756).
- a NS request may be constructed which includes a network service and a corresponding FG, and may be reused after being archived in the NS catalog.
- the FG may be reused when a customer request for a similar network service is received.
- the SDT-FG entity 702 sends the NS request to an orchestrator 704 (Step 762).
- the orchestrator 704 acts on the request using any of a number of different methods including those illustrated in FIG. 1. For example, based on the NS request, the orchestrator 704 may determine (Step 764) NFVI-PoPs for the VNFs indicated in the FG and instruct one or more VNFMs and VIMs, such as the VNFMs 606 and VIMs 608, to instantiate the VNFs (Step 766).
- VNFMs and VIMs such as the VNFMs 606 and VIMs 608
- a trigger message may be forwarded to the orchestrator 704, and the orchestrator 704 may repeat the Steps 764 and 766 as illustrated in FIG. 7.
- the VNFM or VIM may receive an indication of the need to scale in/out and handle the trigger directly.
- FIG. 8 illustrates another embodiment system 800 for performing NFV-MANO.
- the system 800 includes an orchestrator 802, an SDT-FG entity 804, an SDT-PoP entity 806, a VNFM 808, and a VIM 810.
- the SDT-FG entity 804 generates an FG based on a customer request 812.
- the customer request 812 is received by the orchestrator 802, and can then be forwarded to the SDT-FG entity 804.
- SDT-FG 804 generates an FG in accordance with the information associated with the customer request 812 received from the orchestrator 802.
- the SDT-PoP entity 806 determines PoPs for the VNFs in the FG.
- the orchestrator 802 is configured to instruct instantiation of the VNFs in the FG at the PoPs using the one or more VNFMs 808, and one or more VIMs 810.
- FIG. 9 illustrates a sequence diagram for an embodiment method 900 of NFV- MANO, which may be used in the system 800 as illustrated in FIG. 8.
- Orchestrator 902 receives a customer request for a network service from a customer 912 (Step 952).
- the customer request, or information determined in accordance with the customer request, is transmitted to an SDT-FG entity 904 (Step 954).
- the SDT-FG entity 904 generates an FG in accordance with the received information (Step 956).
- a request for a determination of the PoPs required to instantiate the FG is sent to an SDT-PoP entity 906 (Step 958).
- the SDT-PoP entity 906 determines PoPs for the VNFs in accordance with the received request (Step 960) and sends a message, such as a PoP response message, to the SDT-FG entity 904 indicating it has finished the determination of the PoPs, in response to the request PoPs command (Step 962).
- the Request for PoPs transmitted in step 958 may include the determined FG.
- the PoP Response message of step 962 may include a listing of the selected PoPs for each VNF in the FG.
- the SDT-FG entity 904 when receiving the PoP response message, may send an acknowledgement (ACK) message (Step 964) to the orchestrator 902, indicating the generation of the FG and determination of NFVI-PoPs for the VNFs in the FG.
- ACK acknowledgement
- the orchestrator 902 can instruct the instantiation of the VNFs included in the FG based on the NFVI-PoPs (Step 966) using one or more VNFMs and VIMs.
- the orchestrator 902 may issue an instruction to instantiate the VNFs in response to receipt of the ACK message from the SDT-FG entity 904.
- the instruction to instantiate may be sent to VNFMs and VIMs associated with PoPs of the VNFs, e.g., PoPs identified by the SDT-PoP 906 in step 960.
- the instruction to instantiate the VNFs may also come directly from the SDT-PoP entity 906 after the PoPs are determined.
- the SDT-PoP entity 906 may send an instantiation command to a VNFM after the PoPs are determined.
- the trigger message may be forwarded to the SDT-PoP entity 906, and then the Steps 960-966 may be repeated.
- the SDT-PoP entity 906 determines new PoPs requested, and sends a PoP response to the SDT-FG entity 904.
- the SDT-FG entity 904 then sends an acknowledgement message to the orchestrator 902 which sends instructions to instantiate the VNFs at the new PoPs.
- the orchestrator, the SDT-FG entity, and the SDT-PoP entity in the embodiments of the present disclosure may be implemented by the same service provider or different service providers.
- the orchestrator, the SDT-FG entity, and the SDT-PoP entity may be implemented as different entities having interfaces to interact with each other. These entities may be enabled through software, and may be virtualized entities.
- FIG. 10 illustrates a diagram of an embodiment NFV-MANO system 1000 with VNFs instantiated in a single datacenter (DC).
- a topology manager or an orchestrator 1002 has a view of resource availability for an entire network through a VIM 1004.
- the topology manager 1002 determines a VNF-FG, i.e., a logical topology, of VNFs based on a customer request, and determines PoPs for the VNFs in the VNF-FG, i.e., a physical topology for the VNFs.
- the VNF-FG includes two VNFs linked together, namely VNF1 and VNF2, and the two VNFs are co-located at the same NFVI-PoP 1010 (in this example, NFVI-PoP 1010 is a single data center).
- the VIM 1004 allocates and reserves resources, such as virtualization containers and physical links for the two VNFs.
- a software defined network controller (SDN-C) 1008 determines the physical links within its NFVI-PoP, and provides forwarding rules for the data plane containing the instantiated VNFs.
- SDN-C software defined network controller
- FIG. 11 illustrates a diagram of another embodiment NFV-MANO system 1100 with VNFs instantiated across multiple DCs.
- the system 1100 includes a topology manager 1102 in charge of orchestration and management of VNFs resources in the system 1100, multiple VIMs 1104 with each configured to reserve and allocate resources within its respective domain, and multiple VNFMs 1106 with each configured to instantiate VNFs within its respective domain.
- the system 1100 also includes multiple SDN-Cs 1108 each of which is within the domain of a VIM 1104. Each of the SDN-Cs 1108 determines corresponding physical links and provides forwarding rules within its NFVI-PoP.
- the system 1100 further includes multiple wide area network infrastructure managers (WIMs) 1110, each of which is a specialized VIM and provides the topology manager 1102 with an abstract view of resources between NFVI-PoPs 1122 and 1124.
- An SDN-C 1112 within the administrative domain of a WIM 1110 determines the physical links and provides forwarding rules between the NFVI- PoPs 1122 and 1124.
- Each of the VIMs 1104 or WIMs 1110 provides connectivity services within its administrative domain and provides an abstraction of the resources to the topology manager 1102.
- Each of the VIMs 1104 or WIMs 1110 also maintains the NFVI resources repository within its domain.
- a forwarding graph may be determined to include two VNFs, namely, VNF1 and VNF2, corresponding to the NFVI-PoP 1122 and the NFVI-PoP 1124, respectively.
- the VNF1 may be instantiated at the NFVI-PoP 1122 by a VNFM 1106, and the VNF2 may be instantiated at the NFVI-PoP 1124 by another VNFM 1106.
- a second WIM 1110 and SDN-C 1112 may be available to Topology Manager 1102 so that it has visibility into (and control of) the resources used to connect EP 1114 to VNF1 inside NFVI-PoPl 1122.
- This operates much in the same manner as WIM 1110 that acts between NFVI-PoP 1 1122 and NFVI-PoP2 1124.
- the two WIMs 1110 may be combined, along with the two SDN-Cs 1112, so that there is only one set of a WIM and a corresponding SDN-C outside the data centers.
- the number of WIMs and corresponding SDN-Cs is an operational decision.
- FIG. 12 illustrates a flowchart of an embodiment method 1200 for NFV-MANO, which may be performed by a processing system.
- a customer request for a network service is received in step 1202.
- An AVNF-FG is generated in accordance with the received customer request in step 1204.
- the VNF-FG can include a plurality of VNFs.
- the VNF-FG may include a VNF that is related to network performance assessment and enhancement.
- the method 1200 may further determine a NFVI-PoP for each of the plurality of VNFs in the VNF-FG, and instantiate the plurality of VNFs using a VIM and a VNFM at the NFVI-PoPs.
- the method 1200 may construct a NS request including the generated VNF-FG, and send the NS request, based on which NFVI-PoPs for the plurality of VNFs may be determined.
- the constructed NS request may be added to a NS catalog.
- the method 1200 may send a command requesting for determination of the NFVI-PoPs for the plurality of VNFs, and receives a message in response to the command indicating determination of the NFVI-PoPs for the plurality of VNFs in the VNF-FG.
- the method 1200 may also send an acknowledgement message indicating generation of the VNF-FG and determination of the NFVI-PoPs for the plurality of VNFs in the VNF-FG, in response to the customer request.
- FIG. 13 illustrates a block diagram of an embodiment processing system 1300 for implementing the systems and methods described herein, which may be installed in a host device.
- the processing system 1300 may be used to perform the functions of any one or more of the orchestrator, SDT-FG entity and SDT-PoP entity in the embodiments of the present disclosure.
- the processing system 1300 includes a processor 1304, a memory 1306, and interfaces 1310-1314, which may (or may not) be arranged as shown in FIG. 13.
- the processor 1304 may be any component or collection of components adapted to perform computations and/or other processing related tasks
- the memory 1306 may be any component or collection of components adapted to store programming and/or instructions for execution by the processor 1304.
- the memory 1306 includes a non- transitory computer readable medium.
- the interfaces 1310, 1312, 1314 may be any component or collection of components that allow the processing system 1300 to communicate with other devices/components and/or a user.
- one or more of the interfaces 1310, 1312, 1314 may be adapted to communicate data, control, or management messages from the processor 1304 to applications installed on the host device and/or a remote device.
- one or more of the interfaces 1310, 1312, 1314 may be adapted to allow a user or user device (e.g., personal computer (PC), etc.) to interact/communicate with the processing system 1300.
- the processing system 1300 may include additional components not depicted in FIG. 13, such as long term storage (e.g., non-volatile memory, etc.).
- the processing system 1300 is included in a network device that is accessing, or part otherwise of, a telecommunications network.
- the processing system 1300 is in a network-side device in a wireless or wireline
- the processing system 1300 is in a user-side device accessing a wireless or wireline telecommunications network, such as a mobile station, a user equipment (UE), a personal computer (PC), a tablet, a wearable communications device (e.g., a smartwatch, etc.), or any other device adapted to access a telecommunications network.
- a wireless or wireline telecommunications network such as a mobile station, a user equipment (UE), a personal computer (PC), a tablet, a wearable communications device (e.g., a smartwatch, etc.), or any other device adapted to access a telecommunications network.
- FIG. 14 illustrates a block diagram of a transceiver 1400 adapted to transmit and receive signaling over a telecommunications network.
- the transceiver 1400 may be installed in a host device. As shown, the transceiver 1400 comprises a network- side interface 1402, a coupler 1404, a transmitter 1406, a receiver 1408, a signal processor 1410, and one or more device-side interfaces 1412.
- the network-side interface 1402 may include any component or collection of components adapted to transmit or receive signaling over a wireless or wireline telecommunications network.
- the coupler 1404 may include any component or collection of components adapted to facilitate bi-directional communication over the network-side interface 1402.
- the transmitter 1406 may include any component or collection of components (e.g., up-converter, power amplifier, etc.) adapted to convert a baseband signal into a modulated carrier signal suitable for transmission over the network- side interface 1402.
- the receiver 1408 may include any component or collection of components (e.g., down-converter, low noise amplifier, etc.) adapted to convert a carrier signal received over the network-side interface 1402 into a baseband signal.
- the signal processor 1410 may include any component or collection of components adapted to convert a baseband signal into a data signal suitable for communication over the device-side interface(s) 1412, or vice-versa.
- the device-side interface(s) 1412 may include any component or collection of components adapted to communicate data-signals between the signal processor 1410 and components within the host device (e.g., the processing system 1300, local area network (LAN) ports
- the transceiver 1400 may transmit and receive signaling over any type of communications medium.
- the transceiver 1400 transmits and receives signaling over a wireless medium.
- the transceiver 1400 may be a wireless transceiver adapted to communicate in accordance with a wireless telecommunications protocol, such as a cellular protocol (e.g., LTE, etc.), a wireless local area network (WLAN) protocol (e.g., Wi-Fi, etc.), or any other type of wireless protocol (e.g., Bluetooth, near field communication (NFC), etc.).
- a wireless telecommunications protocol such as a cellular protocol (e.g., LTE, etc.), a wireless local area network (WLAN) protocol (e.g., Wi-Fi, etc.), or any other type of wireless protocol (e.g., Bluetooth, near field communication (NFC), etc.
- the network-side interface 1402 comprises one or more antenna/radiating elements.
- the network-side interface 1402 may include a single antenna, multiple separate antennas, or a multi-antenna array configured for multi-layer communication, e.g., single input multiple output (SIMO), multiple input single output (MISO), multiple input multiple output (MIMO), etc.
- the transceiver 1400 transmits and receives signaling over a wireline medium, e.g., twisted-pair cable, coaxial cable, optical fiber, etc.
- Specific processing systems and/or transceivers may utilize all of the components shown, or only a subset of the components, and levels of integration may vary from device to device.
Abstract
Description
Claims
Priority Applications (9)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CA2974501A CA2974501C (en) | 2015-01-20 | 2016-01-20 | Method and apparatus for nfv management and orchestration |
SG11201705956WA SG11201705956WA (en) | 2015-01-20 | 2016-01-20 | Method and apparatus for nfv management and orchestration |
KR1020177023089A KR102178225B1 (en) | 2015-01-20 | 2016-01-20 | Method and device for NFV management and organization |
JP2017538393A JP6552130B2 (en) | 2015-01-20 | 2016-01-20 | Method and apparatus for NFV management and orchestration |
EP16740682.6A EP3241318B1 (en) | 2015-01-20 | 2016-01-20 | Method and apparatus for nfv management and orchestration |
BR112017015480A BR112017015480A2 (en) | 2015-01-20 | 2016-01-20 | method and apparatus for nfv management and orchestration |
AU2016209319A AU2016209319B2 (en) | 2015-01-20 | 2016-01-20 | Method and apparatus for NFV management and orchestration |
CN201680005628.8A CN107113232B (en) | 2015-01-20 | 2016-01-20 | NFV management arrangement method and device |
KR1020197018880A KR20190079718A (en) | 2015-01-20 | 2016-01-20 | Method and apparatus for nfv management and orchestration |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201562105486P | 2015-01-20 | 2015-01-20 | |
US62/105,486 | 2015-01-20 | ||
US201562119620P | 2015-02-23 | 2015-02-23 | |
US62/119,620 | 2015-02-23 | ||
US15/001,745 | 2016-01-20 | ||
US15/001,745 US10447547B2 (en) | 2015-01-20 | 2016-01-20 | Method and apparatus for NFV management and orchestration |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016118636A1 true WO2016118636A1 (en) | 2016-07-28 |
Family
ID=56408632
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2016/014146 WO2016118636A1 (en) | 2015-01-20 | 2016-01-20 | Method and apparatus for nfv management and orchestration |
Country Status (10)
Country | Link |
---|---|
US (1) | US10447547B2 (en) |
EP (1) | EP3241318B1 (en) |
JP (1) | JP6552130B2 (en) |
KR (2) | KR102178225B1 (en) |
CN (1) | CN107113232B (en) |
AU (1) | AU2016209319B2 (en) |
BR (1) | BR112017015480A2 (en) |
CA (1) | CA2974501C (en) |
SG (1) | SG11201705956WA (en) |
WO (1) | WO2016118636A1 (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2018121178A1 (en) * | 2016-12-26 | 2018-07-05 | 华为技术有限公司 | Resource adjustment method, device and system |
WO2018153185A1 (en) * | 2017-02-21 | 2018-08-30 | Huawei Technologies Co., Ltd. | Method for enabling automation of management and orchestration of network slices |
WO2019227483A1 (en) * | 2018-06-01 | 2019-12-05 | Huawei Technologies Co., Ltd. | Multiple server-architecture cluster for providing a virtual network function |
JP2020521387A (en) * | 2017-05-22 | 2020-07-16 | 華為技術有限公司Huawei Technologies Co.,Ltd. | Method and apparatus for creating a network slice and communication system |
JP2020145686A (en) * | 2016-08-18 | 2020-09-10 | テレフオンアクチーボラゲット エルエム エリクソン(パブル) | Network service design and deployment process for nfv system |
Families Citing this family (50)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9578664B1 (en) | 2013-02-07 | 2017-02-21 | Sprint Communications Company L.P. | Trusted signaling in 3GPP interfaces in a network function virtualization wireless communication system |
CN105210337B (en) * | 2014-03-24 | 2019-06-11 | 华为技术有限公司 | A kind of service implementation method and communication unit of NFV system |
FR3030966A1 (en) * | 2014-12-23 | 2016-06-24 | Orange | SYSTEM FOR GENERATING A VIRTUALIZED NETWORK FUNCTION |
AU2016209319B2 (en) | 2015-01-20 | 2019-01-17 | Huawei Technologies Co., Ltd. | Method and apparatus for NFV management and orchestration |
BR112017015617A2 (en) * | 2015-01-20 | 2018-04-10 | Huawei Tech Co Ltd | sdt systems and methods work interconnected with nfv and sdn. |
US9560078B2 (en) * | 2015-02-04 | 2017-01-31 | Intel Corporation | Technologies for scalable security architecture of virtualized networks |
US9686240B1 (en) | 2015-07-07 | 2017-06-20 | Sprint Communications Company L.P. | IPv6 to IPv4 data packet migration in a trusted security zone |
BR112018003775A2 (en) * | 2015-08-31 | 2018-09-25 | Huawei Tech Co Ltd | resource management method and apparatus |
US9749294B1 (en) * | 2015-09-08 | 2017-08-29 | Sprint Communications Company L.P. | System and method of establishing trusted operability between networks in a network functions virtualization environment |
EP3358790B1 (en) * | 2015-09-29 | 2020-03-18 | Huawei Technologies Co., Ltd. | Network function virtualization resource processing method and virtualized network function manager |
US10542115B1 (en) | 2015-10-01 | 2020-01-21 | Sprint Communications Company L.P. | Securing communications in a network function virtualization (NFV) core network |
US9811686B1 (en) | 2015-10-09 | 2017-11-07 | Sprint Communications Company L.P. | Support systems interactions with virtual network functions in a trusted security zone |
US9781016B1 (en) | 2015-11-02 | 2017-10-03 | Sprint Communications Company L.P. | Dynamic addition of network function services |
US10728054B2 (en) | 2015-11-04 | 2020-07-28 | Futurewei Technologies, Inc. | System and method for VNF termination management |
JP6467360B2 (en) * | 2016-02-09 | 2019-02-13 | 日本電信電話株式会社 | Network configuration recommendation device, network configuration recommendation method and program |
EP3436939A1 (en) * | 2016-03-29 | 2019-02-06 | Nokia Solutions and Networks Oy | Methods and apparatuses for moving virtualized network function instances between network service instances |
US10686651B2 (en) * | 2016-06-20 | 2020-06-16 | Apple Inc. | End-to-end techniques to create PM (performance measurement) thresholds at NFV (network function virtualization) infrastructure |
US10880176B2 (en) | 2016-09-09 | 2020-12-29 | Huawei Technologies Co., Ltd. | Method and apparatus for network slicing |
CN107819598A (en) * | 2016-09-13 | 2018-03-20 | 中兴通讯股份有限公司 | A kind of method and device for managing network function node |
US10250498B1 (en) | 2016-10-03 | 2019-04-02 | Sprint Communications Company L.P. | Session aggregator brokering of data stream communication |
US10164914B2 (en) * | 2016-11-16 | 2018-12-25 | Sprint Communications Company L.P. | Network function virtualization (NFV) software-defined network (SDN) network-to-network interfaces (NNIs) |
KR102588689B1 (en) * | 2016-11-28 | 2023-10-12 | 한국전자통신연구원 | method for scaling-out of virtualized network function, virtualized network function manager using the same, and network function virtualization system using the same |
US10764394B2 (en) | 2016-11-30 | 2020-09-01 | At&T Intellectual Property I, L.P. | Resource based framework to support service programmability for a 5G or other next generation mobile core network |
WO2018118050A1 (en) * | 2016-12-21 | 2018-06-28 | Intel Corporation | Community wifi access point (ap) virtual network function (vnf) with wifi protected access 2 (wpa2) pass-through |
US11096119B2 (en) | 2016-12-21 | 2021-08-17 | Maxlinear, Inc. | Dynamic functional partitioning for WiFi protected access 2 (WPA2) pass-through virtual network function (VNF) |
MX2019008427A (en) * | 2017-01-13 | 2019-09-19 | Ericsson Telefon Ab L M | Bulk creation of managed functions in a network that includes virtualized network function. |
TWI655877B (en) | 2017-02-06 | 2019-04-01 | 財團法人工業技術研究院 | User equipment registration method for selecting network slicing, and network controller and network communication system using the method |
US20180302343A1 (en) * | 2017-04-14 | 2018-10-18 | Argela Yazilim ve Bilisim Teknolojileri San. ve Tic. A.S. | System and method for convergence of software defined network (sdn) and network function virtualization (nfv) |
FI3616467T3 (en) * | 2017-04-25 | 2023-03-22 | Apple Inc | Network manager in a nr network |
US11051183B2 (en) | 2017-05-10 | 2021-06-29 | Huawei Technologies Co., Ltd. | Service provision steps using slices and associated definitions |
US10348638B2 (en) | 2017-05-30 | 2019-07-09 | At&T Intellectual Property I, L.P. | Creating cross-service chains of virtual network functions in a wide area network |
CN110720091B (en) | 2017-06-09 | 2023-12-08 | 瑞典爱立信有限公司 | Method for coordinating infrastructure upgrades with hosted application/Virtual Network Functions (VNFs) |
US11032135B2 (en) * | 2017-07-14 | 2021-06-08 | Telefonaktiebolaget Lm Ericsson (Publ) | Method for VNF managers placement in large-scale and distributed NFV systems |
CN109391982B (en) * | 2017-08-10 | 2022-06-07 | ***通信有限公司研究院 | Information packet generation method, arrangement management method, network element and storage medium |
CN109391499A (en) * | 2017-08-11 | 2019-02-26 | 中国电信股份有限公司 | For loading the device and method of virtual network function |
US10348488B1 (en) | 2017-08-25 | 2019-07-09 | Sprint Communications Company L.P. | Tiered distributed ledger technology (DLT) in a network function virtualization (NFV) core network |
US11128705B2 (en) * | 2017-09-15 | 2021-09-21 | Nec Corporation | Application function management using NFV MANO system framework |
FR3071948A1 (en) * | 2017-09-29 | 2019-04-05 | Orange | METHOD AND DEVICE FOR PROCESSING AN INSTALLATION REQUEST OF A NETWORK SERVICE. |
KR101976958B1 (en) * | 2017-12-15 | 2019-05-09 | 연세대학교 산학협력단 | Method of selecting graph based on response time for QoS of end-to-end network service |
CN110018877B (en) * | 2018-01-08 | 2021-09-28 | 普天信息技术有限公司 | Method and device for quickly instantiating VNF according to affinity principle |
CN108737261B (en) * | 2018-05-10 | 2020-03-17 | 电子科技大学 | Two-stage virtual network function forwarding graph design method |
WO2020026140A1 (en) * | 2018-07-30 | 2020-02-06 | Telefonaktiebolaget Lm Ericsson (Publ) | Machine learning method for adaptive virtual network functions placement and readjustment |
EP3609128A1 (en) * | 2018-08-07 | 2020-02-12 | Siemens Aktiengesellschaft | Communication system, provider node, communication node and method for providing a virtual network function to a customer node |
WO2020031158A1 (en) * | 2018-08-10 | 2020-02-13 | Nokia Technologies Oy | Method and apparatus for providing service path vectors in service based architecture of communication network |
CN113169889B (en) * | 2018-12-07 | 2024-03-12 | 诺基亚通信公司 | Method and apparatus for mapping network slices onto a network infrastructure with SLA guarantees |
CN111385114B (en) * | 2018-12-28 | 2022-04-26 | 华为技术有限公司 | VNF service instantiation method and device |
CN111082960B9 (en) * | 2019-04-15 | 2023-01-24 | 中兴通讯股份有限公司 | Data processing method and device |
EP3860048A1 (en) * | 2020-01-31 | 2021-08-04 | InterDigital CE Patent Holdings | Method for instantiating a network service and corresponding apparatus |
US11304115B2 (en) * | 2020-03-18 | 2022-04-12 | Equinix, Inc. | Network defined edge routing for an application workload |
US11847205B1 (en) | 2020-10-26 | 2023-12-19 | T-Mobile Innovations Llc | Trusted 5G network function virtualization of virtual network function elements embedded on a system-on-chip |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110196940A1 (en) * | 2001-11-21 | 2011-08-11 | Soa Software, Inc. | Web Services-Based Computing Resource Lifecycle Management |
US20140201374A1 (en) * | 2013-01-11 | 2014-07-17 | Futurewei Technologies, Inc. | Network Function Virtualization for a Network Device |
US20140310388A1 (en) * | 2013-04-10 | 2014-10-16 | Futurewei Technologies, Inc. | System and Method for Providing a Software Defined Protocol Stack |
Family Cites Families (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7843906B1 (en) * | 2004-02-13 | 2010-11-30 | Habanero Holdings, Inc. | Storage gateway initiator for fabric-backplane enterprise servers |
CA2741465C (en) | 2008-10-22 | 2013-10-15 | 6Fusion International Limited | Method and system for determining computer resource usage in utility computing |
CN104205055B (en) * | 2012-03-29 | 2019-02-01 | 瑞典爱立信有限公司 | Cloud computing system and in cloud computing system realize evolution block core (EPC) control plane method |
CN103379010B (en) * | 2012-04-20 | 2018-09-21 | 中兴通讯股份有限公司 | A kind of virtual network realization method and system |
CN103428025A (en) | 2012-05-25 | 2013-12-04 | 中兴通讯股份有限公司 | Method, apparatus and system for managing virtual network service |
US8817625B1 (en) | 2013-09-13 | 2014-08-26 | Telefonaktiebolaget L M Ericsson (Publ) | Service placement for inline services chaining with multiple instances |
US10291515B2 (en) | 2013-04-10 | 2019-05-14 | Huawei Technologies Co., Ltd. | System and method for a control plane reference model framework |
US10034222B2 (en) | 2013-06-06 | 2018-07-24 | Huawei Technologies Co., Ltd. | System and method for mapping a service-level topology to a service-specific data plane logical topology |
US9325636B2 (en) * | 2013-06-14 | 2016-04-26 | Cisco Technology, Inc. | Scaling interconnected IP fabric data centers |
US9736041B2 (en) | 2013-08-13 | 2017-08-15 | Nec Corporation | Transparent software-defined network management |
BR112016004183A8 (en) * | 2013-08-27 | 2020-02-11 | Huawei Tech Co Ltd | method for virtualization of mobile network and computer function |
US9288143B2 (en) | 2013-10-14 | 2016-03-15 | Hewlett Packard Enterprise Development Lp | Data flow path determination |
US9755901B2 (en) | 2014-01-21 | 2017-09-05 | Huawei Technologies Co., Ltd. | System and method for a software defined protocol network node |
WO2015126430A1 (en) * | 2014-02-24 | 2015-08-27 | Hewlett-Packard Development Company, L.P. | Virtual network function management with deactivated virtual machines |
EP2911347B1 (en) | 2014-02-24 | 2019-02-13 | Hewlett-Packard Enterprise Development LP | Providing policy information |
US20150288767A1 (en) * | 2014-04-03 | 2015-10-08 | Centurylink Intellectual Property Llc | Network Functions Virtualization Interconnection Hub |
US9838253B2 (en) | 2014-04-10 | 2017-12-05 | Fujitsu Limited | Object-oriented network virtualization |
US9594649B2 (en) * | 2014-10-13 | 2017-03-14 | At&T Intellectual Property I, L.P. | Network virtualization policy management system |
CN105591784A (en) * | 2014-10-24 | 2016-05-18 | 中兴通讯股份有限公司 | Warning processing method and apparatus |
WO2016086991A1 (en) * | 2014-12-04 | 2016-06-09 | Nokia Solutions And Networks Management International Gmbh | Steering of virtualized resources |
US9882815B2 (en) * | 2014-12-22 | 2018-01-30 | Telefonaktiebolaget Lm Ericsson (Publ) | Adaptive load balancing in packet processing |
AU2016209319B2 (en) | 2015-01-20 | 2019-01-17 | Huawei Technologies Co., Ltd. | Method and apparatus for NFV management and orchestration |
-
2016
- 2016-01-20 AU AU2016209319A patent/AU2016209319B2/en not_active Ceased
- 2016-01-20 CA CA2974501A patent/CA2974501C/en not_active Expired - Fee Related
- 2016-01-20 JP JP2017538393A patent/JP6552130B2/en not_active Expired - Fee Related
- 2016-01-20 BR BR112017015480A patent/BR112017015480A2/en not_active IP Right Cessation
- 2016-01-20 KR KR1020177023089A patent/KR102178225B1/en active IP Right Grant
- 2016-01-20 CN CN201680005628.8A patent/CN107113232B/en active Active
- 2016-01-20 US US15/001,745 patent/US10447547B2/en active Active
- 2016-01-20 SG SG11201705956WA patent/SG11201705956WA/en unknown
- 2016-01-20 KR KR1020197018880A patent/KR20190079718A/en not_active Application Discontinuation
- 2016-01-20 WO PCT/US2016/014146 patent/WO2016118636A1/en active Application Filing
- 2016-01-20 EP EP16740682.6A patent/EP3241318B1/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110196940A1 (en) * | 2001-11-21 | 2011-08-11 | Soa Software, Inc. | Web Services-Based Computing Resource Lifecycle Management |
US20140201374A1 (en) * | 2013-01-11 | 2014-07-17 | Futurewei Technologies, Inc. | Network Function Virtualization for a Network Device |
US20140310388A1 (en) * | 2013-04-10 | 2014-10-16 | Futurewei Technologies, Inc. | System and Method for Providing a Software Defined Protocol Stack |
Non-Patent Citations (2)
Title |
---|
See also references of EP3241318A4 * |
SEETHARAMAN, S.: "Open Flow/Software-defined Networking", DEUTSCHE TELEKOM INNOVATION CENTER, November 2011 (2011-11-01), XP055399562, Retrieved from the Internet <URL:http://www.slideshare.net/openflow/openflow-tutorial?from_action=save> [retrieved on 20160302] * |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2020145686A (en) * | 2016-08-18 | 2020-09-10 | テレフオンアクチーボラゲット エルエム エリクソン(パブル) | Network service design and deployment process for nfv system |
US11316758B2 (en) | 2016-08-18 | 2022-04-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Network service design and deployment process for NFV systems |
WO2018121178A1 (en) * | 2016-12-26 | 2018-07-05 | 华为技术有限公司 | Resource adjustment method, device and system |
US11038760B2 (en) | 2016-12-26 | 2021-06-15 | Huawei Technologies Co., Ltd. | Resource adjustment method, apparatus, and system |
WO2018153185A1 (en) * | 2017-02-21 | 2018-08-30 | Huawei Technologies Co., Ltd. | Method for enabling automation of management and orchestration of network slices |
JP2020521387A (en) * | 2017-05-22 | 2020-07-16 | 華為技術有限公司Huawei Technologies Co.,Ltd. | Method and apparatus for creating a network slice and communication system |
US11146453B2 (en) | 2017-05-22 | 2021-10-12 | Huawei Technologies Co., Ltd. | Method and apparatus for creating network slice, and communications system |
WO2019227483A1 (en) * | 2018-06-01 | 2019-12-05 | Huawei Technologies Co., Ltd. | Multiple server-architecture cluster for providing a virtual network function |
CN112166579A (en) * | 2018-06-01 | 2021-01-01 | 华为技术有限公司 | Multi-server architecture cluster providing virtualized network functionality |
CN112166579B (en) * | 2018-06-01 | 2022-02-25 | 华为技术有限公司 | Multi-server architecture cluster providing virtualized network functionality |
US11442791B2 (en) | 2018-06-01 | 2022-09-13 | Huawei Technologies Co., Ltd. | Multiple server-architecture cluster for providing a virtual network function |
Also Published As
Publication number | Publication date |
---|---|
SG11201705956WA (en) | 2017-08-30 |
EP3241318A4 (en) | 2017-11-08 |
US20160212016A1 (en) | 2016-07-21 |
CA2974501A1 (en) | 2016-07-28 |
US10447547B2 (en) | 2019-10-15 |
CA2974501C (en) | 2019-09-10 |
AU2016209319A1 (en) | 2017-08-24 |
CN107113232A (en) | 2017-08-29 |
KR20170105597A (en) | 2017-09-19 |
JP6552130B2 (en) | 2019-07-31 |
KR102178225B1 (en) | 2020-11-12 |
EP3241318B1 (en) | 2023-05-31 |
BR112017015480A2 (en) | 2018-01-30 |
EP3241318A1 (en) | 2017-11-08 |
CN107113232B (en) | 2020-09-25 |
JP2018503319A (en) | 2018-02-01 |
AU2016209319B2 (en) | 2019-01-17 |
KR20190079718A (en) | 2019-07-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10447547B2 (en) | Method and apparatus for NFV management and orchestration | |
US10298466B2 (en) | Systems and methods for SDT to interwork with NFV and SDN | |
CN109600246B (en) | Network slice management method and device | |
US11844017B2 (en) | Method and device for determining deployment information of network | |
EP3295630B1 (en) | System and methods for virtual infrastructure management between operator networks | |
EP3158686B1 (en) | System and method for virtual network function policy management | |
US11817971B2 (en) | System and method for VNF termination management | |
KR20180014097A (en) | Method and apparatus for utilizing network connectivity services or infrastructure provided by a third party | |
US11444851B2 (en) | Systems and methods of using adaptive network infrastructures | |
US20220353138A1 (en) | Apparatus and method for generating network slice in wireless communication system | |
US20220124547A1 (en) | Systems and methods to automate slice admission control | |
US20200177462A1 (en) | Service Management Method and Apparatus, and Storage Medium | |
Debbabi et al. | An overview of interslice and intraslice resource allocation in b5g telecommunication networks | |
WO2023032101A1 (en) | Performance index value calculation system and performance index value calculation method | |
WO2023032102A1 (en) | Performance index value calculation system and performance index value calculation method | |
SOUZA | Dynamic resource allocation for URLLC and eMBB services in NFV-MEC 5G networks | |
CN113875192A (en) | First entity, second entity, third entity and method performed thereby for providing a service in a communication network |
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: 16740682 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2974501 Country of ref document: CA Ref document number: 2017538393 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 11201705956W Country of ref document: SG |
|
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: 112017015480 Country of ref document: BR |
|
REEP | Request for entry into the european phase |
Ref document number: 2016740682 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 20177023089 Country of ref document: KR Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2016209319 Country of ref document: AU Date of ref document: 20160120 Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 112017015480 Country of ref document: BR Kind code of ref document: A2 Effective date: 20170719 |