WO2018000239A1 - Assurance de qualité de service de bout en bout sur des réseaux qui mettent en œuvre une virtualisation de fonction de réseau - Google Patents

Assurance de qualité de service de bout en bout sur des réseaux qui mettent en œuvre une virtualisation de fonction de réseau Download PDF

Info

Publication number
WO2018000239A1
WO2018000239A1 PCT/CN2016/087657 CN2016087657W WO2018000239A1 WO 2018000239 A1 WO2018000239 A1 WO 2018000239A1 CN 2016087657 W CN2016087657 W CN 2016087657W WO 2018000239 A1 WO2018000239 A1 WO 2018000239A1
Authority
WO
WIPO (PCT)
Prior art keywords
nfv
service
network
qos
infrastructure
Prior art date
Application number
PCT/CN2016/087657
Other languages
English (en)
Inventor
Tao Zheng
Xiaoyu Wang
Original Assignee
Orange
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 Orange filed Critical Orange
Priority to PCT/CN2016/087657 priority Critical patent/WO2018000239A1/fr
Publication of WO2018000239A1 publication Critical patent/WO2018000239A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H04L47/805—QOS or priority aware
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS

Definitions

  • the present invention relates to the implementation of communications network functionality and, in particular, to functionality for implementing network services that operate over networks that implement Network Function Virtualization (NFV) . More especially, the invention provides a method and system to assure end-to-end quality of service over network infrastructure in which implement network function virtualization is implemented.
  • NFV Network Function Virtualization
  • networking In communications networks, networking has traditionally been implemented using specialised hardware to provide the required functionality. To improve the pace of improvement in networking technology, and in the light of increasing convergence between telecommunications networks and data communications networks, software implementations of networking equipment have been developed.
  • NFV network function virtualization
  • the expression ′′communications network′′ refers in general to networks of different kinds including, inter alia, telecommunications networks and data-communications networks (and converged networks) , whether providing fixed or mobile services.
  • the expression ′′computer network′′ as used herein may also refer to the same networks in view of the fact that the present document discusses networks in which network functions are virtualized.
  • the present invention may be applied in relation to network services that operate over network infrastructure in which NFV is implemented at least to some extent; in other words, the invention may be applied even in the case where the network infrastructure still employs one or more dedicated hardware elements (physical network functions, PNFs) .
  • a given end-to-end service that operates over communications networks can be defined in terms of a forwarding graph of network functions and end points/terminals.
  • the expression ′′network service′′ used herein refers to some service that is implemented with the aid of network infrastructure and which involves performance of technical functions by components in the network (e.g. communications functions, networking functions, firewall functionality, domain name resolution functionality, and so on) .
  • the service model of a given network service may be implemented by network service chaining, as illustrated in figure 1.
  • Some or all of the network functions needed to operate the network service may be implemented using virtual network functions (VNFs) .
  • VNFs virtual network functions
  • the VNFs may be considered to be middleboxes and elements of network services that are to be deployed in a cloud platform.
  • the network service is implemented on a service platform which may belong to a network operator or other service provider.
  • VNFs may be instantiated on network infrastructure so that the network has the capability of supporting different network services.
  • resources computing power, storage, networking resources
  • specific hardware component will be allocated for implementing the associated virtual machine/run the associated application software.
  • Figure 1 illustrates a simple generalised example of a network service implemented using VNFs 102, 104, and 106.
  • VNFs may be used to provide various functions including, but not limited to: deep packet inspection, virtual firewalls, load balancing, evolved packet core features, base station functionality, intrusion prevention, virtual routing, and so on.
  • figure 1 does not represent all elements of the service platform on which the network service is implemented.
  • the VNFs 102, 104, 106 are in communication with one another via network infrastructure.
  • End points 100 and 108 of the architecture represent the service end points, such as for example a user terminal connected to a base station 1 and/or a processing device in a house 27 (see figure 3 discussed below) .
  • the end point 100 is in communication with the VNF 102 via a first infrastructure network 110
  • the end point 108 is in communication with the VNF 106 via a third infrastructure network 116
  • VNF 102 is in communication with VNF 104 via infrastructure network 114.
  • the infrastructure hardware used in implementing the network service illustrated in figure 1 may depend on the nature of the service: typically it may include servers, storage, communications links, routing devices, control and management units, and so on.
  • the communications links used in implementing the network service illustrated in figure 1 may be wired and/or wireless.
  • NFV MANO Framework for the management and orchestration of NFV resources in networking infrastructure (including management of computing, networking, storage and virtual machine (VM) resources) .
  • VM virtual machine
  • Implementation of NFV MANO involves use of three main functional modules -NFV Orchestrator, VNF Manager and Virtualized Infrastructure Manager (VIM) –interacting with application program interfaces (APIs) that are provided on components in the network infrastructure.
  • VIP Virtualized Infrastructure Manager
  • APIs application program interfaces
  • ETSI NFV MANO framework the manner in which individual VNFs are managed on a commodity hardware platform is described using an Elemental Management System (EMS) .
  • EMS Elemental Management System
  • FIG. 2 illustrates schematically an example of network infrastructure architecture provided with NFV MANO components that interact with one another, with EMSs and other network infrastructure elements in order to manage and orchestrate NFV resources.
  • the network infrastructure includes NFV infrastructure (NFVI) 120 including hardware resources 121 with an associated virtualization layer 122 for instantiating VNFs 124 which are managed according to EMSs 125.
  • the network infrastructure includes business support systems (BSS) and/or operations support systems (OSS) 128 provided by network service providers for managing their networks (e.g., telephone networks) .
  • BSS/OSS 128 provides functionality to support functions such as service provisioning and network configuration and fault management.
  • NFV MANO infrastructure 130 is interconnected to the network infrastructure and it comprises the three functions mentioned above: an NFV orchestrator (NFVO) 132, a set of VNF Managers 134 and a virtualized Infrastructure manager (VIM) 136.
  • the N FV Orchestrator (NFVO) 132 is configured to be in communication with the OSS/BSS 128, the set of VNF managers 134 and the virtualized infrastructure manager (VIM) 136.
  • the set of VNF managers 134 are configured to be in communication with the VNFs 124 and their associated EMSs 125, as well as with the NFVO 132 and the VIM 136.
  • the VIM 136 is configured to be in communication with the NFV infrastructure 120 as well as with the set of VNF mangers 134 and the NFVO 132.
  • NFV MANO can be installed according to its own capacity, network size, network types and network location. Generally, one set of NFV MANO components is connected to one single operator′s NFV network, unless the size of a single NFV network exceeds the capacity of a NFV MANO (in which case, the NFV network can be divided into several parts connecting to different MANOs, for example according to geographic location) or the single network may have been divided into different parts in advance because of its very large-scale coverage (for example, in China a nationwide network is divided up, generally by different provinces) . .
  • FIG. 2 The example of figure 2 is simplified.
  • communications networks tend to be interconnected in complex webs that include, for example, network infrastructure operated by different telecommunications companies, networks implementing different technology standards, and so on.
  • network services may be implemented using VNFs that are located in plural, different infrastructure networks.
  • one end-to-end service usually relates to different networks, or network parts, belonging to different MANOs.
  • the VNFs of the service chain are located in three different infrastructure networks 110, 114, 116. Accordingly, there may be a large physical distance between two successive VNFs in a service chain. This issue is illustrated by figure 3.
  • Figure 3 illustrates an example of network architecture implementing, inter alia, mobile telecommunications, in which NFV is employed to virtualize the dependency between network functions and the associated hardware.
  • NFV network function
  • substantially all of the network functions are illustrated as VNFs but the skilled person will recognize that physical network functions (PNFs) may also be present in network infrastructure.
  • PNFs physical network functions
  • the cloud shapes shown in figure 3 represent hardware resource pools.
  • base stations (BS) 1 can provide communications capabilities via software implementations of functions such as the functions of LTE virtual bases stations (vBS LTE) 5, 3G virtual base stations (vBS 3G) 7, 2G virtual base stations (vBS 2G) 9 and WiMax virtual base stations (vBS WiMax) 11 that run on hardware devices 13.
  • LTE virtual bases stations vBS LTE
  • vBS 3G 3G virtual base stations
  • vBS 2G 2G virtual base stations
  • WiMax WiMax virtual base stations
  • CDN content delivery network
  • the network infrastructure illustrated in figure 3 also includes virtualized home and enterprise networks 21, virtualized fixed access networks 23 (for communication with homes 27 and offices 25) , virtualized mobile core networks/IMS 19 and virtualized mobile IP networking systems 29. Each of these virtualized systems 21, 23, 29, 19 is provided via software implementations running on hardware 13.
  • figure 3 illustrates the provision of virtualized control plane functionality of Asymmetric digital subscriber lines ASDL 31, of Very-high-bit-rate digital subscriber lines (VDSL) 33 and virtualized control plane functionality conforming to ITU-T or G standards (ITU-T/G) 35.
  • figure 3 illustrates virtualized residential gateways (RGW) 37, virtualized Network address translation (NAT) 39 and virtualized set-top box functionality 41 provided via software implementations running on hardware 13.
  • RGW virtualized residential gateways
  • NAT virtualized Network address translation
  • set-top box functionality 41 provided via software implementations running on hardware 13.
  • FIG 3 illustrates virtualization of functions and entities such as Call Session Control Function (CSCF) 43, signalling gateway (SGW) 45, mobility management entity (MME) 47, domain name server (DNS) 49, Dynamic Host Configuration Protocol (DHCP) 51 and firewalls 53, with the functions provided via software implementations running on hardware 13.
  • CSCF Call Session Control Function
  • SGW signalling gateway
  • MME mobility management entity
  • DNS domain name server
  • DHCP Dynamic Host Configuration Protocol
  • firewalls 53 with the functions provided via software implementations running on hardware 13.
  • FIG 3 illustrates a case where CSCF 43, MME 47, DHCP 51 are also provided in virtualized form, as well as virtualized packet data network gateways (PGW) 55, virtualized App servers 57 and virtualized load balancing 59.
  • PGW packet data network gateways
  • Figure 3 represents an example in which several different cloud infrastructures 3, 15, 19, 21, 23 and 29 are interconnected. These may well correspond to networks operated and managed by different operating companies.
  • NFV is implemented in all of the illustrated cloud infrastructures and each one is liable to have its own set of NFV MANO components.
  • VNF forwarding graph 61 As an example of a network service that may be provided using a networking architecture such as that of figure 3, consider a cloud application which a user can access using his mobile device via networking capability provided using LTE. This is illustrated using the VNF forwarding graph 61 at the top of figure 3. The skilled person will recognise that this is merely one example of a VNF forwarding graph selected for one service provided using one particular type networking architecture. Other forwarding graphs representing other services can also be generated, and such graphs need not be merely linear as depicted in figure 3, for example they may contain branches.
  • the example network service represented by forwarding graph 61 is considered to start at an LTE vBS 5 (represented in the forwarding graph as 63) .
  • the end point of the service is actually an end-user whose user equipment communicates with the LTE base station via a wireless interface, but from the point of view of the network infrastructure the service chain may be considered to begin at the base station.
  • the LTE virtualized base station 5 communicates with an MME 47 in the core mobile network 19 (represented in the forwarding graph as 65) and then an SGW 45 in the core mobile network 19 (represented in the forwarding graph as 67) .
  • the service communicates with a PGW 55 in the mobile IP networking system 29 (represented in the forwarding graph as 69) and an App server in the mobile IP networking system 29 (represented in the forwarding graph as 71) which hosts the cloud application the user wishes to access.
  • the VNFs are deployed in several different cloud infrastructures.
  • the connections from the first VNF 63 in the service chain (i.e. LTE virtualized base station 5) to the second VNF 65 (i.e. virtualized mobile management entity 47) and from the third VNF 67 (i.e. virtualized signaling gateway 45) to the fourth VNF 69 (i.e. virtualized packet data network gateway 55) are long distance connections.
  • these two connections are likely to have a huge impact on the end-to-end quality of service (QoS) that is attained by the network service which is implemented using a service chain that embodies this VNF forwarding graph 61.
  • QoS quality of service
  • Ensuring that end-to-end QoS requirements are satisfied in network service chains is particularly important, especially to telecommunications operators.
  • Various techniques are known for monitoring performance in networking infrastructure and for managing the implementation of network function virtualization. However, the known techniques do not provide methods or systems that assure end-to-end QoS for network services that operate over real-world network infrastructure in which NFV is implemented.
  • the present invention provides a method of assuring end-to-end quality of service for a network service implemented on networking infrastructure comprising network function virtualization (NFV) , the method comprising:
  • QoS quality of service
  • the present invention provides a system to assure end-to-end quality of service for a network service implemented on networking infrastructure comprising network function virtualization (NFV) , the system comprising:
  • NFV network function virtualization
  • an NFV end-to-end QoS manager configured to determine a target profile for end-to-end quality of service (QoS) for the network service
  • an NFV-platform information monitoring module configured to monitor network function virtualization platform information as it changes
  • end-to-end QoS manager is configured to determine a service chain deployment, comprising virtualised network functions, satisfying said target QoS profile, and to output information indicative of the determined service chain deployment to NFV management infrastructure for set-up of the VNFs of said service chain.
  • a computer program product comprising computer readable instructions which, when executed by a processor perform all of the steps of the method of the first aspect, and a computer readable medium comprising such a computer program.
  • the method, system and computer program product according to the invention provide a technique for assuring end-to-end QoS for a network service implemented in networking infrastructure wherein NFV is implemented.
  • the provided method, system and computer program product provide simplified handling of scenarios such as those which may be involved when implementing network services ′′across-MANOs′′ , for example roaming, inter-communications between network operators and multiple MANOs deployment (one operator having several independent networks) .
  • the same unified modules and algorithm are which are used when generating service chains that assure desired end-to-end QoS are also used when handling failures of VNFs; this reduces system complexity.
  • Figure 1 illustrates a simplified example of a network forwarding graph
  • Figure 2 illustrates schematically the provision of NFV-MANO components to manage NFV in an example network infrastructure
  • Figure 3 illustrates a known example of a network architecture implementing mobile telecommunications in which NFV is employed to virtualise the relationship between network functions and the associated hardware;
  • Figure 4 illustrates an example of a system according to an embodiment of the invention to assure a service chain′s end-to-end QoS in communications network infrastructure where NFV is implemented.
  • Figure 5 illustrates an embodiment in which the QoS assurance system of figure 4 is deployed externally to NFV-MANO;
  • Figure 6 illustrates an embodiment in which the QoS assurance system of figure 4 is deployed internally to NFV-MANO;
  • Figure 7 illustrates an example of a method according to an embodiment of the invention to assure a service chain′s end-to-end QoS in communications network infrastructure where NFV is implemented.
  • Figure 8 illustrates an example of interactions that may take place between components of the QoS assurance system of figure 4 and components of network infrastructure at a time when a new service chain is generated;
  • Figure 9 illustrates an example of interactions that may take place between components of the QoS assurance system of figure 4 and components of network infrastructure when QoS is unsatisfied and/or a QoS profile is changed.
  • any service chain can be implemented using different VNFs in different configurations, and there is no particular limitation on the number or type of VNFs employed or in the manner in which such VNFs are connected to one another.
  • the principles discussed below may be applied in respect of assuring end-to-end QoS for service chains implemented in the network architecture of figure 3 and, indeed, for service chains implemented over substantially any communications network infrastructure in which NFV is implemented.
  • the examples below will be described in a context where the management and orchestration of NFV in a networking infrastructure are handled according to the ETSI NFV-MANO framework, but it is to be understood that the present invention is not limited to application in that context, the invention may be applied in the context of other frameworks.
  • certain embodiments of the present invention provide a system to assure a service chain′s end-to-end QoS in communications network infrastructure where NFV is implemented.
  • the system comprises two new functional modules to handle the end-to-end QoS of NFV′s service chain to the network infrastructure.
  • Figure 4 illustrates an example of a system 200, according to an embodiment of the invention, to assure a service chain′s end-to-end (E2E) QoS in communications network infrastructure where NFV is implemented.
  • E2E end-to-end
  • the system 200 to assure E2E QoS comprises an NFV-platform information center 210 which operates to collect NFV platform information that impacts on the end-to-end QoS of a service chain that is (or is to be) implemented using VNFs.
  • the NFV-platform information center 210 may be configured to collect the following items of information:
  • VNFs VNF types, the platform where each VNF is located
  • the specific items of information, regarding the NFV platform, which are monitored by the NFV-platform information center 210 may vary depending on the use case; for example in the case of mobile services it may be appropriate to monitor a greater number of special NFV-platform information items than in the case of fixed-line services. In many use cases it is advantageous to monitor the four information items a) to d) of the above list in order to ensure that a judicious choice is made of deployment solution (see below) . Monitoring the transmission delay and network location can increase the likelihood of choosing, for deployment, VNFs which are instantiated in locations which have a relatively greater positive impact on QoS.
  • Monitoring the current state of deployment of VNFs promotes reuse of VNFs after they have finished other tasks, or during the runtime, and this can reduce costs.
  • Monitoring the NFV platform′s load rate can help to deploy VNFs more balanced among the whole NFV platform on the premise that the service chain′s E2E QoS is assured.
  • the NFV-platform information center 210 may be configured:
  • NFV management and organization (MANO) infrastructure provided in the networking architecture in which the network service is being (or will be) implemented
  • the NFV-platform information center 210 may be configured to establish a preliminary record of the NFV-platform information of the NFV-MANOs in the networking infrastructure, as a kind of image of the current state of the NFV platform with which the system 200 may interact.
  • the NFV-platform information center 210 may establish the preliminary record in a variety of ways.
  • the preliminary record is recorded in the NFV-platform information center by explicit programming (manual or automated) .
  • a kind of ′′NFV-MANO discovery′′ process may be implemented involving communication between the NFV-platform information center 210 and the NFV-MANOs in the networking infrastructure, whereby the NFV-platform information center 210 discovers the NFV-MANOs that are operating in the networking infrastructure and obtains their NFV-platform information.
  • the NFV-MANO infrastructure which communicates with the system 200 may be configured so that, during the operational phase of system 200, the NFV-MANOs respond to changes they are aware of in NFV-platform parameters that impact on end-to-end performance (e.g. parameters mentioned under a) to d) above) by reporting the changes to the NFV-platform information center 210, thereby keeping the NFV-platform information center 210 updated.
  • Each NFV-MANO reports NFV-platform changes in the NFV infrastructure which it is managing.
  • the NFV-MANOs may be configured to report current values of relevant NFV-platform parameters to the NFV-platform information center 210 even at times when no change occurs (e.g. periodically or intermittently; spontaneously or triggered by receipt of a request from the NFV-platform information center 210) .
  • NFV-MANO components already determine some of the NFV-platform information items that are of use to the NFV-platform information center 210.
  • New functions and physical/software interfaces may be added to existing NFVMANO components as needed so that the NFV-MANO components determine other NFV-platform information items required by the NFV-platform information center 210 and communicate the determined information items to the NFV-platform information center 210.
  • new NFV-MANO components may be built which already include all the required functions and interfaces.
  • the system 200 to assure E2E QoS further comprises an NFV end-to-end QoS manager 220 which operates to assure satisfaction of end-to-end QoS by generating a deployment solution of VNFs to implement a service chain satisfying the QoS profile. More specifically, the NFV end-to-end QoS manager 220 may be configured:
  • the NFV end-to-end QoS manager 220 may be configured to communicate with a QoS function of the service platform which implements the relevant network service, in order to obtain details of an end-to-end QoS profile associated with the network service.
  • the physical (or virtualized) element from which the NFV end-to-end QoS manager 220 retrieves the QoS profile may vary dependent on the implementation of the external service platform.
  • the QoS profile may include the following information:
  • the specific parameters or indicators that form part of the QoS profile may vary depending on the network service in question; for example in the case of certain mobile services the QoS profile may include parameters as defined in table 1 of the ETSI and GPP standard TS22.105 version 13.0.0 (currently accessible at http: //www. 3gpp. org/DynaReport/22105. htm) .
  • the NFV end-to-end QoS manager 220 may be configured to use any convenient technique to generate an NFV-deployment configuration to implement a service chain satisfying the desired/required QoS.
  • the NFV end-to-end QoS manager 220 may implement techniques described in the applicant′s co-pending PCT patent application filed on the same day as the present application and entitled ′′Method and system for the optimisation of deployment of virtual network functions in a communications network that uses software defined networking′′ , the entire contents of which are incorporated herein by reference.
  • each of the NFV-platform information center 210 and the NFV end-to-end QoS manager 220 may be implemented using a processing apparatus (for example, computer apparatus comprising a processor) configured to execute instructions of a computer program to implement the above-described functionality.
  • the processing apparatus may form part of the network, for example it may constituted by a server in the network, but this is not essential.
  • Each of the NFV-platform information center 210 and the NFV end-to-end QoS manager 220 may be implemented as one or more physical network functions, as one or more virtualized network functions, or a combination of the two.
  • FIG. 6 illustrates a first deployment scenario for the system 200 to assure E2E QoS.
  • This first deployment scenario corresponds to an independent deployment mode.
  • the NFV-platform information center 210 and the NFV end-to-end QoS manager 220 are separate from NFV MANO infrastructure and communicate with the NFV MANO infrastructure through external interfaces, for example via the Se-Ma interface defined in the ETSI NFV framework.
  • This first deployment scenario applies to distributed and integrated NFV MANO models.
  • FIG. 7 illustrates a second deployment scenario for the system 200 to assure E2E QoS.
  • This second deployment scenario corresponds to a dependent deployment mode.
  • the NFV-platform information center 210 and the NFV end-to-end QoS manager 220 are integrated with NFV MANO as two internal functions and communicate with NFV MANO through internal interfaces.
  • This second deployment scenario only applies to an integrated NFV MANO model.
  • certain embodiments of the present invention provide a method to assure a service chain′s end-to-end QoS in communications network infrastructure where NFV is implemented.
  • Figure 7 illustrates an example of the method.
  • the method comprises determining a target profile of end-to-end QoS for a network service (S10) .
  • the target QoS profile may be obtained in various ways. For example, when a network service is being commissioned the service provider may specify requirements for end-to-end QoS. One or more of these requirements may form the target QoS profile. As another example, the service provider may update or otherwise modify the requirements for end-to-end QoS and the target QoS profile determined in step S10 may be based on the changed QoS profile.
  • the method further comprises ongoing monitoring (S20) of information regarding the NFV-platform.
  • This monitoring may be performed by the NFV platform information center 210 as described above.
  • a deployment of VNFs that would satisfy the target profile for end-to-end QoS may be generated (S30) and details of the VNF deployment may be outputted (S40) .
  • the details of the generated VNF deployment solution may be outputted to the relevant NFV-MANO components in a request for set-up the VNFs, of the generated deployment solution, for which they are responsible.
  • the method may include special process flows when a service chain is generated and/or special process flows when there is a change such that a QoS requirement is unsatisfied.
  • Figure 8 illustrates interactions that may take place between the NFV-platform information center 210, NFV end-to-end QoS manager 220, a QoS function 300 of a service platform and a plurality of NFV-MANO installations 130a-130c in a case where the service platform intends to implement a network service so a new service chain is being generated and the service chain which ends up being generated involves VNFs to be managed by the plurality of different NFV-MANO installations 130a-130c.
  • the various NFV MANO installations managing VNFs in the service chain of the network service report the NFV platform information to the NFV platform information center/function 210 when the related information changes.
  • the NFV QoS manager/function 220 sends a request to the QoS function 300 of the service platform to obtain the target QoS profile from 3 rd party service/QoS function 300.
  • the QoS function 300 of the service platform returns QoS profile information to the NFV QoS manager/function 220.
  • NFV QoS manager/function220 sends a request to the NFV platform information center/function 210 to obtain NFV platform information relevant to implementation of the target network service.
  • the NFV platform information center/function 210 responds to the request of step 4 by sending the relevant NFV platform information to the NFV QoS manager/function220.
  • the NFV QoS manager/function 220 generates a candidate deployment solution of a service chain according to related information it retrieved.
  • step 5 If a satisfactory new deployment solution cannot be found in step 5, then the processing flow ends and there is no deployment solution to satisfy the service′s QoS. A report of the failure may be generated and may, for example, be transmitted to the service provider. The process flow then ends.
  • the NFV QoS manager/function 220 sends information indicative of the solution to each related NFV MANO to request to set up related VNFs under management by that NFV MANO.
  • Each NFV-MANO receives the information it requires to set-up the VNFs under its management which form part of the service chain in the candidate solution.
  • Figure 9 illustrates interactions that may take place between the NFV-platform information center 210, NFV end-to-end QoS manager 220, a network function relevant to QoS of the network service and a plurality of NFV-MANO installations 130a-130c in a case where, as a result of a change, a new deployment solution of VNFs may be needed in order to assure desired end-to-end QoS for a network service.
  • a change may be, for example, the occurrence of some failure condition or degradation of system performance which results in the achieved QoS being less than desired (e.g. a QoS alarm may trigger the interactions illustrated in figure 9) .
  • the change may derive from an updating of the QoS profile associated with the network service.
  • the related network function may be, for example, the QoS function 300 of the service platform, a network function which detects a failure condition, and so on.
  • the various NFV MANO installations managing VNFs in the service chain of the network service report the NFV platform information to the NFV platform information center/function 210 when the related information changes.
  • the related function transmits to the NFV QoS manager/function 220 information indicative of the changed condition (s) .
  • the NFV QoS manager/function 220 sends a request to the NFV platform information center/function 210 asking for the NFV platform information that is relevant to the network service in question.
  • the NFV-platform information center 210 returns the relevant NFV-platform information to the NFV QoS manager/function 220.
  • the NFV QoS manager/function 220 generates a new service-chain deployment solution with the aim of finding a new solution which will satisfy the desired end-to-end QoS profile, taking into account any applicable retrieved related information.
  • the new service-chain deployment solution may be expressed as an adjustment of a current service-chain deployment solution
  • step 5 a) If a satisfactory new deployment solution cannot be found in step 5, then the processing flow ends and there is no deployment solution to satisfy the service′s QoS. A report of the failure may be generated.
  • step 5 If a satisfactory new deployment solution is found in step 5, the NFV QoS manager/function 220 sends information indicative of the solution to each related NFV MANO to request modification of related VNFs under management by that NFV MANO.
  • Each involved NFV MANO reports back to the NFV QoS manager/function 220 regarding the result of adjusting (or attempting to adjust) the relevant VNFs.
  • Embodiments can be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which -when loaded in an information processing system -is able to carry out these methods.
  • Computer program means or computer program in the present context mean any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after conversion to another language.
  • Such a computer program can be stored on a computer-or machine-readable medium allowing data, instructions, messages or message packets, and other machine-readable information to be read from the medium.
  • the computer-or machine-readable medium may include non-volatile memory, such as ROM, Flash memory, Disk drive memory, CD-ROM, and other permanent storage.
  • a computer-or machine-readable medium may include, for example, volatile storage such as RAM, buffers, cache memory, and network circuits.
  • the computer-or machine readable-medium may comprise computer-or machine-readable information in a transitory state medium such as a network link and/or a network interface, including a wired network or a wireless network, that allow a device to read such computer-or machine-readable information.

Abstract

La présente invention concerne un procédé d'assurance de qualité de service de bout en bout pour un service de réseau mis en œuvre sur une infrastructure de réseautage comprenant une virtualisation de fonction de réseau (NFV) consistant : à déterminer un profil cible pour une qualité de service de bout en bout (QoS) pour le service de réseau, à surveiller les informations de la plateforme de virtualisation de la fonction de réseau lorsqu'elle change, à déterminer un déploiement de chaîne de service, comprenant des fonctions de réseau virtualisées, à satisfaire ledit profil QoS cible et à délivrer des informations indicatives du déploiement de chaîne de service déterminé à l'infrastructure de gestion de NFV pour la configuration des VNF de ladite chaîne de service.
PCT/CN2016/087657 2016-06-29 2016-06-29 Assurance de qualité de service de bout en bout sur des réseaux qui mettent en œuvre une virtualisation de fonction de réseau WO2018000239A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/087657 WO2018000239A1 (fr) 2016-06-29 2016-06-29 Assurance de qualité de service de bout en bout sur des réseaux qui mettent en œuvre une virtualisation de fonction de réseau

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/087657 WO2018000239A1 (fr) 2016-06-29 2016-06-29 Assurance de qualité de service de bout en bout sur des réseaux qui mettent en œuvre une virtualisation de fonction de réseau

Publications (1)

Publication Number Publication Date
WO2018000239A1 true WO2018000239A1 (fr) 2018-01-04

Family

ID=60785796

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/087657 WO2018000239A1 (fr) 2016-06-29 2016-06-29 Assurance de qualité de service de bout en bout sur des réseaux qui mettent en œuvre une virtualisation de fonction de réseau

Country Status (1)

Country Link
WO (1) WO2018000239A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109639460A (zh) * 2018-11-19 2019-04-16 中国联合网络通信集团有限公司 Nfv资源管理的方法和装置
FR3096529A1 (fr) * 2019-06-28 2020-11-27 Orange Procédé de gestion d’une communication dans un environnement de chainage de service
CN112383447A (zh) * 2020-11-02 2021-02-19 中移系统集成有限公司 业务质量测量方法、装置、设备及存储介质
CN113328871A (zh) * 2020-02-28 2021-08-31 中国移动通信有限公司研究院 信令采集的配置方法、装置及存储介质
CN114788241A (zh) * 2019-12-04 2022-07-22 皇家Kpn公司 提供网络管理与切片管理之间的接口

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104137482A (zh) * 2014-04-14 2014-11-05 华为技术有限公司 一种云计算架构下的容灾数据中心配置方法及装置
WO2015091964A1 (fr) * 2013-12-19 2015-06-25 Amdocs Software Systems Limited Système, procédé et programme informatique permettant une communication inter-modules dans un réseau sur la base d'une virtualisation de fonction réseau (nfv)
WO2016026129A1 (fr) * 2014-08-22 2016-02-25 Nokia Technologies Oy Infrastructure de sécurité et de confiance pour réseaux virtualisés
US20160127975A1 (en) * 2014-10-31 2016-05-05 At&T Intellectual Property I, L.P. Mobile network with software defined networking architecture
US20160150421A1 (en) * 2014-11-21 2016-05-26 Huawei Technologies Co., Ltd. System and Method for Modifying a Service-Specific Data Plane Configuration
CN105681216A (zh) * 2016-04-27 2016-06-15 赛特斯信息科技股份有限公司 Nfv架构下网络业务接入控制和负载均衡的系统及方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015091964A1 (fr) * 2013-12-19 2015-06-25 Amdocs Software Systems Limited Système, procédé et programme informatique permettant une communication inter-modules dans un réseau sur la base d'une virtualisation de fonction réseau (nfv)
CN104137482A (zh) * 2014-04-14 2014-11-05 华为技术有限公司 一种云计算架构下的容灾数据中心配置方法及装置
WO2016026129A1 (fr) * 2014-08-22 2016-02-25 Nokia Technologies Oy Infrastructure de sécurité et de confiance pour réseaux virtualisés
US20160127975A1 (en) * 2014-10-31 2016-05-05 At&T Intellectual Property I, L.P. Mobile network with software defined networking architecture
US20160150421A1 (en) * 2014-11-21 2016-05-26 Huawei Technologies Co., Ltd. System and Method for Modifying a Service-Specific Data Plane Configuration
CN105681216A (zh) * 2016-04-27 2016-06-15 赛特斯信息科技股份有限公司 Nfv架构下网络业务接入控制和负载均衡的系统及方法

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109639460A (zh) * 2018-11-19 2019-04-16 中国联合网络通信集团有限公司 Nfv资源管理的方法和装置
CN109639460B (zh) * 2018-11-19 2021-12-07 中国联合网络通信集团有限公司 Nfv资源管理的方法和装置
FR3096529A1 (fr) * 2019-06-28 2020-11-27 Orange Procédé de gestion d’une communication dans un environnement de chainage de service
CN114788241A (zh) * 2019-12-04 2022-07-22 皇家Kpn公司 提供网络管理与切片管理之间的接口
CN114788241B (zh) * 2019-12-04 2024-05-03 皇家Kpn公司 提供网络管理与切片管理之间的接口
CN113328871A (zh) * 2020-02-28 2021-08-31 中国移动通信有限公司研究院 信令采集的配置方法、装置及存储介质
CN113328871B (zh) * 2020-02-28 2022-08-12 中国移动通信有限公司研究院 信令采集的配置方法、装置及存储介质
CN112383447A (zh) * 2020-11-02 2021-02-19 中移系统集成有限公司 业务质量测量方法、装置、设备及存储介质

Similar Documents

Publication Publication Date Title
US11212181B2 (en) Cloud zone network analytics platform
US11134410B2 (en) Quality of service (QoS) control in mobile edge computing (MEC)
WO2018000239A1 (fr) Assurance de qualité de service de bout en bout sur des réseaux qui mettent en œuvre une virtualisation de fonction de réseau
US9588815B1 (en) Architecture for data collection and event management supporting automation in service provider cloud environments
US9847915B2 (en) Network function virtualization for a network device
US9973375B2 (en) App store portal providing point-and-click deployment of third-party virtualized network functions
JP2021534692A (ja) モバイル装置接続を提供するための方法、システムおよびコンピュータ可読媒体
EP2404405B1 (fr) Gestion d'éléments de réseau
CN114788333A (zh) 用于使用反馈机制提供网络切片管理的方法、系统和计算机可读介质
EP3525399B1 (fr) Orchestration de gestion multi-vbng auto-entraînée et adaptable
US10999121B2 (en) Service OAM virtualization
US20200351717A1 (en) Employing self organizing network (son) techniques to manage data over cable service interface specification (docsis) backhaul for small cells
EP3697039A1 (fr) Sélection de points d'extrémité à équilibre de charge pour des dispositifs clients accédant aux points d'extrémité par l'intermédiaire d'un réseau
US10397791B2 (en) Method for auto-discovery in networks implementing network slicing
US20210273890A1 (en) Devices and methods for time sensitive communication in a communication network
US10511544B2 (en) Path computation element protocol response and simple network management protocol confirmation for tunnel configuration
WO2021185452A1 (fr) Surveillance d'un réseau de communication
KR20200105499A (ko) 가상화된 네트워크 기능들
US10320621B1 (en) Network loading management system and method
US11552839B2 (en) Residential gateway with traffic scheduling
CN109845329B (zh) 一种通信方法、网络设备及应用管理单元
Derakhshan et al. Enabling cloud connectivity using SDN and NFV technologies
US10749699B1 (en) Predictive indicator based on network performance
US11943101B2 (en) Joint orchestration for private mobile network
Meneses et al. Virtualization of customer equipment: Challenges and opportunities

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16906640

Country of ref document: EP

Kind code of ref document: A1