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

WO2017214932A1 - 一种网络切片的资源管理方法和装置 - Google Patents

一种网络切片的资源管理方法和装置 Download PDF

Info

Publication number
WO2017214932A1
WO2017214932A1 PCT/CN2016/086031 CN2016086031W WO2017214932A1 WO 2017214932 A1 WO2017214932 A1 WO 2017214932A1 CN 2016086031 W CN2016086031 W CN 2016086031W WO 2017214932 A1 WO2017214932 A1 WO 2017214932A1
Authority
WO
WIPO (PCT)
Prior art keywords
network slice
slice
network
decision result
resource
Prior art date
Application number
PCT/CN2016/086031
Other languages
English (en)
French (fr)
Inventor
唐朋成
周伟
周汉
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP16905047.3A priority Critical patent/EP3461087B1/en
Priority to PCT/CN2016/086031 priority patent/WO2017214932A1/zh
Priority to BR112018076166A priority patent/BR112018076166A2/pt
Priority to CN201680086181.1A priority patent/CN109196828A/zh
Publication of WO2017214932A1 publication Critical patent/WO2017214932A1/zh
Priority to US16/220,612 priority patent/US20190123963A1/en

Links

Images

Classifications

    • 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/64—Routing or path finding of packets in data switching networks using an overlay routing layer
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5006—Creating or negotiating SLA contracts, guarantees or penalties
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation
    • 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/83—Admission control; Resource allocation based on usage prediction
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances

Definitions

  • the present invention relates to the field of communications, and in particular, to a resource management method and apparatus for a network slice.
  • NFV Network Function Virtualization
  • ETSI European Telecommunications Standards Institute
  • NS management network services
  • VNF virtual network functions
  • the process includes NS template online, NS instantiation, NS elastic scaling, update, and instance termination.
  • NS can also be called network slice
  • network slice can be understood as the abstraction of the logical function of the network.
  • Each network slice can use the process shown in Figure 1 when deciding whether to expand or shrink.
  • the monitoring module inside the network slice periodically collects the running status indicators of the network slice.
  • operational status indicators include resource metrics and business metrics.
  • the monitoring module reports the collected running status indicators to the slice elastic scaling decision module.
  • the slice elastic scaling decision module performs elastic scaling decision according to the collected running state indicators.
  • the result of the decision may be that the number of instances of the current NS is unchanged, a certain number of NS instances are created, or a certain number of NS instances are terminated.
  • the slice elastic scalability decision module sends the decision result to the Management and Orchestration (MANO) module in the ETSI NFV architecture, and the corresponding expansion or shrinkage process is performed by the MANO.
  • MEO Management and Orchestration
  • MANO can complete a series of expansion and contraction actions with the slice elastic expansion decision module.
  • the main purpose of the capacity expansion is to meet the resource requirements of the network slice and to replenish a certain number of instances in time.
  • the purpose of the reduction is to collect resources in time when the network service is idle, so as to avoid waste of resources and reduce the cost of the sliced tenants.
  • the application provides a resource management method and apparatus for network slicing to optimize resource utilization of an infrastructure.
  • a first aspect of the present application provides a resource management method for a network slice, including:
  • the slice management module separately obtains independent decision results of multiple network slices, where the independent decision result includes expanding, shrinking, or maintaining the number of instances unchanged;
  • the slice management module determines a final decision result for each network slice according to the independent decision result of the multiple network slices;
  • the slice management module sends the final decision result to the VIM, where the final decision result is used to indicate that resources of the first network slice of the plurality of network slices are allocated to the second of the plurality of network slices Network slicing
  • the independent decision result of the first network slice is a contraction, and the independent decision result of the second network slice is to keep the number of instances unchanged or expanded; or the independent decision result of the first network slice is to keep the instance.
  • the number is unchanged, and the independent decision result of the second network slice is expansion.
  • the solution provided by the present application utilizes the characteristics of high and low interleaving between network slices to make a more rational allocation of resources, so that the independent decision result is that the expanded network slice can be reduced from the independent decision result or keep the other network slices unchanged.
  • Coordinating resources can also make the independent decision result to coordinate the resources of the network slice that keeps the number of instances from the independent decision result to other network slices, so that the network slice that needs to increase the capacity does not need to request new resources from the infrastructure, improve The utilization of infrastructure resources, while reducing the resource procurement costs of slice tenants.
  • the method before the slice management module acquires independent decision results of multiple network slices, the method further includes:
  • the slice management module receives a request for instructing to create a network slice template, where the network slice template includes a resource cooperation ratio parameter, where the resource cooperation ratio parameter is a maximum resource ratio that the network slice instance allows to be shared;
  • the slice management module creates the network slice template according to the request
  • the slice management module creates a network slice instance included in the first network slice according to the network slice template.
  • the method before the slice management module determines the final decision result for each network slice according to the independent decision result of the multiple network slices, the method further includes:
  • the slice management module acquires a total resource occupied by the first network slice and a resource cooperation ratio parameter value of the first network slice, so that resources allocated from the first network slice to the second network slice are not a product that is greater than a product of a total resource occupied by the first network slice and a resource synergy parameter value of the first network slice;
  • the resource cooperation ratio parameter value of the first network slice is a minimum value among resource parameter ratio parameter values of all network slice instances included in the first network slice.
  • the method before the slice management module determines the final decision result for each network slice according to the independent decision result of the multiple network slices, the method further includes:
  • the slice management module acquires an SLA indicator of the first network slice
  • the slice management module acquires a predicted service indicator of the first network slice after allocating resources to the second network slice;
  • the slice management module determines that the predicted service indicator of the first network slice does not violate the first A network sliced SLA indicator.
  • the network slice can be guaranteed to comply with the SLA, so as to better provide network services for users.
  • the slice management module determines a final decision result for each network slice according to the independent decision result of the multiple network slices, including:
  • the slice management module acquires a prediction independent decision result of the first network slice
  • the slice management module determines to allocate resources of the first network slice to the second network slice;
  • the slice management module determines not to allocate resources of the first network slice to the second network slice.
  • the network slice can be better complied with the SLA, and unnecessary resource allocation actions can be reduced, and the action of shrinking or expanding a certain network slice frequently can be avoided.
  • the slice management module may be deployed within the VNFM; or the slice management module may be deployed within the NFVO; or the slice management module may be deployed within the OSS/BSS.
  • the slice management module obtains independent decision results of multiple network slices, including:
  • the slice management module receives an independent decision result respectively sent by each of the plurality of network slices; or the slice management module receives, respectively, sent by each of the plurality of network slices
  • the service indicator and the resource indicator respectively determine the independent decision result of each network slice according to the service indicator and the resource indicator of each network slice.
  • the slice management module if the slice management module is deployed in the VNFM, the slice management module sends the final decision result to the VIM through an interface between the VNFM and the VIM; The slice management module sends the final decision result to the NFVO through an interface between the VNFM and the NFVO, and then forwards the final decision result by the NFVO through an interface between the NFVO and the VIM. Giving the VIM; or the slice management module transmitting the final decision result to the OSS/BSS by the OSS/BSS through the OSS/BSS and The interface between the NFVOs sends the final decision result to the NFVO, and the NFVO sends the final decision result to the VIM through an interface between the NFVO and the VIM;
  • the slice management module If the slice management module is deployed in the NFVO, the slice management module sends the final decision result to the VIM through an interface between the NFVO and the VIM; or the slice management module passes the The interface between the NFVO and the VNFM sends the final decision result to the VNFM, and the VNFM sends the final decision result to the VIM through an interface between the VNFM and the VIM;
  • the slice management module If the slice management module is deployed in the OSS/BSS, the slice management module sends the final decision result to the NFVO through an interface between the OSS/BSS and the NFVO, and then passes the NFVO An interface between the NFVO and the VIM forwards the final decision result to the VIM.
  • a second aspect of the present application provides a resource management apparatus for a network slice, where the apparatus has a function of implementing a behavior of a slice management module in the foregoing method embodiment.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules or units corresponding to the functions described above.
  • the structure of the device includes an obtaining unit, a determining unit, and a sending unit, and the units may perform corresponding functions in the foregoing method examples.
  • the units may perform corresponding functions in the foregoing method examples.
  • the detailed description in the method example which is not described herein. .
  • the apparatus includes a network interface, a processor, a bus, and a memory for communicating with other devices in the communication system, the processor being configured The corresponding functions in the above methods are performed to support the device.
  • the memory is coupled to the processor, which stores program instructions and data necessary for the device.
  • FIG. 1 is a flow chart of an elastic expansion mechanism of a network slice in the prior art
  • FIG. 2 is a schematic diagram of a deployment architecture of a network slice in the prior art
  • FIG. 3 is a curve of elastic scalability decision of two network slices according to changes in load in the prior art. Line diagram
  • FIG. 4 is a schematic diagram of an NFV system applied to a resource management method for a network slice according to an embodiment of the present disclosure
  • FIG. 5 is a schematic diagram of information interaction between a network slice and a slice management module according to an embodiment of the present disclosure
  • FIG. 6 is a flowchart of a method for resource management of a network slice according to an embodiment of the present application
  • FIG. 7 is a flowchart of operations for adding, modifying, and querying resource synergy parameters according to an embodiment of the present application
  • FIG. 8 is a flowchart of an operation for updating a resource cooperation ratio parameter in a network slice instance according to an embodiment of the present application
  • FIG. 9 is a schematic diagram of a method for sending a final decision result according to an embodiment of the present application.
  • FIG. 10 is a schematic diagram of another method for sending a final decision result according to an embodiment of the present application.
  • FIG. 11 is a schematic diagram of another transmission path of a final decision result according to an embodiment of the present application.
  • FIG. 12 is a schematic diagram of a resource allocation method between three network slices according to an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a resource management apparatus for a network slice according to an embodiment of the present disclosure
  • FIG. 14 is a schematic structural diagram of another resource management device of a network slice according to an embodiment of the present application.
  • Network Slice also known as NS
  • 3GPP 3rd Generation Partnership Project
  • a network slice consists of a set of logical network functions used to support a specific communication service. composition.
  • 3GPP 3rd Generation Partnership Project
  • Operators can provide tailored network slicing for different types of communications on the same infrastructure, as shown in Figure 2, for carriers Broadband (Mobile Broad Band, MBB) communication provides MBB network slicing, V2V slicing for Vehicle to Vehicle (V2V), and MTC network slicing for Machine Type Communication (MTC) .
  • MBB Mobile Broad Band
  • Network Slice Instance generated from a network slice template.
  • the process of creating a network slice instance from a network slice template is called instantiation.
  • a network slice instance can be implemented by software.
  • a network slice may contain multiple network slice instances, and the network slice templates used by the multiple network slice instances may be the same or different. This application uses "number of instances" to refer to the number of network slice instances that a network slice contains.
  • Resource allocation refers to allocating resources under a network slice, such as a virtual machine (VM), a central processing unit (CPU), memory, and hard disk storage, to another network.
  • the slice is used so that another network slice can be omitted from the process of requesting a new resource from the idle resource.
  • resource allocation can be implemented by revoking a part of the network slice instance under one network slice and allocating the resources occupied by the part of the network slice instance to another network slice; or modifying the attribution relationship of the network slice instance.
  • the method implements resource allocation.
  • the resource allocation can also be implemented by allocating only a part of the resources occupied by the network slice instance to other network slices without canceling the network slice instance.
  • the “independent decision result” is the result of the elastic scaling decision based on the resource indicators and business indicators of a network slice.
  • the independent decision result of each network slice is only related to the state of the network slice itself, for example, related to the resource indicator and service indicator of the network slice.
  • the “final decision result”, also known as the collaborative decision result, is the result of the elastic scaling decision obtained by integrating the independent decision results of multiple network slices.
  • the final decision result of each network slice is not only related to the independent decision result of the network slice itself, but also related to the independent decision result of other network slices.
  • the “resource indicator” may include one or more of the following: an indicator of the number of instances included in the network slice, a VM number indicator, a CPU indicator of each VM, an in-memory indicator, or a bandwidth utilization indicator.
  • the network service of the control plane may include the average processing delay of signaling, the number of attached users, and the number of activated bearers.
  • the service indicator may include a report. Forwarding bandwidth, packet processing delay, and so on.
  • Service Level Agreement refers to an agreement that describes the commitment of an operator or content provider regarding the running time, quality of operation, and connectivity of the business. For example, when a user purchases an operator's service, an SLA is signed between the operator and the user. For example, the network bandwidth provided by the operator to the user cannot be less than 50 megabytes (unit: M). If the bandwidth provided by the operator is less than 50M, Operators who violate the SLA need to compensate the user.
  • SLA Service Level Agreement
  • each network slice independently determines whether to expand or shrink capacity according to its own load.
  • FIG. 3 a curve diagram of elastic scaling decisions of two network slices according to respective load changes is performed.
  • the load variation trend of different network slices is different, and the load of the same network slice changes with time.
  • the load of the enhanced mobile bandwidth (enhanced MBB, e.g., eMBB) network slice is always at a low level, but the condition of the shrinkage has not been reached. Therefore, the number of VMs occupied by the eMBB network slice remains unchanged.
  • the load of large-scale machine-like communication (massive MTC, mMTC for short) network slices shows a trend of high and low changes.
  • MANO completes a series of expansion and contraction operations according to the load changes of mMTC network slices and MMTC network slices.
  • the present application proposes a resource management method and apparatus for network slicing, which utilizes the characteristics of high and low interleaving between network slices to make a more rational allocation of resources, so that the independent decision result is
  • the expanded network slice can coordinate resources from other network slices whose independent decision result is to shrink or keep the number of instances unchanged. It can also make the independent decision result to keep the number of instances unchanged.
  • the network slice from the independent decision result is the other network.
  • the slices coordinate resources so that the network slices that need to increase capacity do not need to request new resources from the infrastructure, which improves the utilization of infrastructure resources, and reduces the resource procurement cost of the slice tenants.
  • the resource management method for the network slice provided by the present application can be applied to the NFV system shown in FIG. 4, and the NFV system can be implemented through multiple networks, such as a data center network, a service provider network, or a local area network (Local Area Network, referred to as :LAN)etc.
  • networks such as a data center network, a service provider network, or a local area network (Local Area Network, referred to as :LAN)etc.
  • the NFV system may include an NFV-MANO 101, an NFV Infrastructure (NFV Infrastructure) 102, a plurality of VNFs 103, and a plurality of element management (EM) 104. And one or more operation support systems or business support systems (Operation Support System/Business Support System, OSS/BSS) 106.
  • NFV Infrastructure NFV Infrastructure
  • EM element management
  • operation support systems or business support systems OSS/BSS
  • NFV-MANO 101 may include a Service, VNF and Infrastructure Description system 105, Network Function Virtualization Orchestrator (NFVO) 107, one or more virtualized network functions.
  • NFVO Network Function Virtualization Orchestrator
  • the NFVI 102 may include a computing hardware 110, storage hardware 111, a hardware resource layer composed of network hardware 112, a virtualization layer, and a virtual resource layer composed of virtual computing 113 (eg, virtual machine), virtual storage 114, and virtual network 115.
  • the computing hardware 110 in the hardware resource layer can be a dedicated processor or a general purpose processor for providing processing and computing functions; the storage hardware 111 can be used to provide storage capabilities, which can be provided by the storage hardware 111 itself (eg The local memory of a server can also be provided through a network (for example, a server connects to a network storage device through a network); the network hardware 112 can be a switch, a router, and/or other network device, and the network hardware 112 is used to implement multiple devices. Communication between multiple devices via wireless or wired connection.
  • the virtualization layer in NFVI 102 is used to abstract the hardware resources of the hardware resource layer, which will be VNF 103 and hard.
  • the physical layer to which the resource belongs is decoupled to provide virtual resources to the VNF 103.
  • the virtual resource layer may include virtual computing 113, virtual storage 114, and virtual network 115.
  • the virtual computing 113, the virtual storage 114 may be provided to the VNF 103 in the form of a virtual machine or other virtual container, for example, one or more VNFs 103 may be deployed on a virtual machine.
  • the virtualization layer forms a virtual network 115 through abstract network hardware 112.
  • Virtual networks 115 such as virtual switches (Vswitches), are used to enable communication between multiple virtual machines, or between other types of virtual containers hosting VNFs.
  • Virtualization of network hardware can be through virtual LAN (Vritual LAN, VLAN for short), Virtual Private LAN Service (VPLS), Virtual eXtensible Local Area Network (VxLAN) or general purpose.
  • Technology implementation such as Nerwork Virtualization using Generic Routing Encapsulation (NVGRE).
  • OSS/BSS 106 is mainly for telecom service operators, providing comprehensive network management and service operation functions, including network management (such as fault monitoring, network information collection, etc.), billing management, and customer service management.
  • network management such as fault monitoring, network information collection, etc.
  • billing management billing management
  • customer service management customer service management.
  • the service, the VNF, and the infrastructure description system 105 are described in detail in the ETSI GS NFV 002v1.1.1 standard, and the details of the present application are not described herein again.
  • the NFV-MANO 101 can be used to implement monitoring and management of the VNF 103 and NFVI 102.
  • the NFVO 107 can communicate with one or more VNFMs 108 to implement resource related requests, send configuration information to the VNFM 108, and collect status information for the VNF 103.
  • NFVO 107 can also communicate with VIM 109 to enable resource allocation, and/or to implement reservation and exchange of configuration information and status information for virtualized hardware resources.
  • the VNFM 108 can communicate with the VNF 103 and EM 104 under the direction of the NFVO 107 to perform VNF 103 lifecycle management and implement the exchange of configuration/status information, ie, responsible for the creation, deletion, start, stop, etc. of the VNF 103.
  • the VIM 109 can be used to control and manage the interaction of the VNF 103 and computing hardware 110, storage hardware 111, network hardware 112, virtual computing 113, virtual storage 114, virtual network 115.
  • VIM 109 can be used to perform resource allocation operations to VNF 103.
  • VNFM 108 and VIM 109 can communicate with one another to exchange virtualized hardware resource configuration and status information.
  • NFVI 102 includes both hardware and software to create a virtualized environment for deployment, management, and execution.
  • Line VNF 103 the hardware resource layer and the virtual resource layer are used to provide virtual resources, such as virtual machines and/or other forms of virtual containers, to various VNFs 103.
  • the VNF 103 is a virtualization of at least one network function that was previously provided by a physical network device.
  • the VNF 103 may be a virtualized Mobility Management Entity (MME) node for providing all network functions provided by a typical non-virtualized MME device.
  • MME Mobility Management Entity
  • the VNF 103 can be used to implement the functionality of some of the components provided on the non-virtualized MME device.
  • a VNF 103 can be composed of multiple VMs.
  • the EM 104 can be used to manage one or more VNFs 103.
  • the resource management method of the network slice provided by the present application mainly involves two types of network elements, one is a network slice, and the other is a slice management module, and the slice management module is configured to slice the multiple networks according to independent decision results of multiple network slices. Coordination between resources.
  • the network slice may include one or more VNFs 103.
  • network slice 1 consists of VNF 1 and VNF 2
  • network slice 2 consists of VNF 3.
  • the independent decision result of each network slice may be determined internally by the VNF 103 included in the network slice, or may be determined by the EM 104 connected to the VNF 103 included in the network slice, or may be determined by the VNFM 108, or may be The slice management module decides.
  • the slice management module can be deployed within the VNFM 108, or it can be deployed within the NFVO 107, or it can be deployed within the OSS/BSS 106.
  • Each network slice can include at least one network slice instance 505 and a monitoring module 506.
  • the monitoring module 506 of each network slice is configured to periodically collect resource indicators and service indicators of the network slice instance 505 included in the network slice. As shown in Figure 5, Representing the resource indicator of the network slice instance 505 included in the network slice i 502 collected by the monitoring module 506 in the network slice i502 at time t, Indicates the service indicator of the network slice instance 505 included in the network slice i collected by the monitoring module 506 inside the network slice i 502 at time t.
  • each network slice may further include a slice elastic scaling decision module 507.
  • the monitoring module 506 can report the collected resource indicator and the service indicator to the slice elastic scaling decision module 507 inside the network slice.
  • the slice elastic scaling decision module 507 in each network slice is configured to obtain an independent decision result corresponding to the network slice according to the resource indicator and the service indicator of the network slice.
  • the slice elastic scaling decision module 507 can perform elastic scaling decisions based on different policies, which may be a static threshold algorithm (Static Threshold), a dynamic threshold algorithm (Dynamic Threshold) or a reinforcement learning algorithm (Reinforcement Learning), and other more advanced and more complex. Algorithm.
  • the functionality of the slice elastic scaling decision module may be implemented by the EM 104 of FIG. 4 or by the VNFM 108 of FIG.
  • the function of the slice elastic scaling decision module 507 can be implemented by the slice management module 501. That is, the monitoring module 506 can report the resource indicator and the service indicator to the slice management module 501, and the slice management module 501 obtains the independent decision result corresponding to the network slice according to the resource indicator and the service indicator of the network slice.
  • the slice management module 501 is configured to obtain independent decision results corresponding to the plurality of network slices respectively, and perform unified elastic expansion decision based on the independent decision results corresponding to the plurality of network slices respectively, for each of the plurality of network slices
  • the network slice determines the final decision result.
  • obtaining independent decision results corresponding to multiple network slices includes: directly obtaining independent decision results corresponding to multiple network slices respectively, or acquiring resource indicators and service indicators of multiple network slices, and analyzing and obtaining the based on the two indicators
  • the independent decision results corresponding to the plurality of network slices are respectively described. As shown in FIG.
  • s i,t , s j,t and s k,t respectively represent resource indicators and service indicators of network slice i 502, network slice j 503 and network slice k 504 at time t, p i,t , p j,t and p k,t represent independent decision results of network slice i 502, network slice j 503 and network slice k 504 at time t , respectively, a i,t , a j,t and a k,t respectively represent the network The final decision result of slice i502, network slice j 503 and network slice k 504 at time t.
  • the independent decision results and final decision results for each network slice may or may not be the same.
  • the slice management module 501 can perform unified elastic scaling decisions based on different policies, such as an SLA evaluation, a return on investment (ROI), and a Heuristically Search algorithm. At least one of the strategies. For example, the slice management module 501 performs a unified elastic scaling decision based on the SLA evaluation. Each network slice also needs to send the respective SLA indicator to the slice management module 501.
  • policies such as an SLA evaluation, a return on investment (ROI), and a Heuristically Search algorithm. At least one of the strategies. For example, the slice management module 501 performs a unified elastic scaling decision based on the SLA evaluation. Each network slice also needs to send the respective SLA indicator to the slice management module 501.
  • the slice management module 501 can comprehensively consider the SLA and ROI information of each network slice, and use an optimal search algorithm to find an elastic scalability policy that allows each network slice to achieve global optimization.
  • the slice management module 501 determines the final decision result for each network slice
  • the final decision result is sent to the VIM 508, and the VIM 508 adjusts the number of instances of each network slice according to the final decision result.
  • each network slice may further include an analysis engine 509.
  • the analysis engine 509 of each network slice is configured to acquire, from the monitoring module 506, the current resource indicator and the service indicator of the network slice instance 505 included in the network slice, and the historical resource indicator and the historical service indicator combined with the network slice to predict the network.
  • the trend of the sliced resource indicators and business indicators As shown in Figure 5, Representing the resource indicator of the network slice i 502 predicted by the analysis engine 509 inside the network slice i 502 at time t', Indicates the traffic indicator of the network slice i 502 predicted by the analysis engine 509 inside the network slice i 502 at time t'.
  • the analysis engine 509 can predict the change trend of the resource indicator and the service indicator by using a pattern matching method or a prediction algorithm (Prediction).
  • the slice elastic scaling decision module 507 or the slice management module 501 may further perform elastic scaling decision based on the resource indicator and the service indicator, combined with the predicted resource indicator and the predicted service indicator obtained by the analysis engine 509. , determine the uniqueness of the network slice Establish decision-making results, so that the results of independent decision-making are more accurate.
  • the slice management module 501 may perform a unified elastic scaling decision based on the independent decision result, combined with the predicted resource indicator and the predicted service indicator obtained by the analysis engine 509, for each network slice in the plurality of network slices. Determine the final decision result separately, so that the final decision result obtained is more accurate.
  • the embodiment of the present application further provides a resource management method for a network slice, as shown in FIG. 6.
  • the embodiment of the present application can achieve the purpose of dynamically adjusting the number of instances of each network slice by performing the steps in the method shown in FIG. 6 multiple times.
  • the method can include the following steps:
  • Step 601 The slice management module separately obtains independent decision results of multiple network slices, where the independent decision result includes expanding, shrinking, or maintaining the number of instances.
  • the purpose of the capacity expansion is to supplement a certain number of network slice instances in time to meet the resource requirements of the network service.
  • the purpose of the volume reduction is to recover a certain number of network slice instances in time when the network service is idle, so as to avoid waste of resources.
  • the slice management module may obtain independent decision results of multiple network slices in the following two manners.
  • the first mode the monitoring module in each of the plurality of network slices collects the service indicator and the resource indicator of the network slice, and reports it to the slice elastic scaling decision module of the network slice.
  • the slice elastic scaling decision module determines an independent decision result of the network slice according to the service indicator and the resource indicator of the network slice; and then each of the network slices separately sends a respective independent decision result to the slice management module.
  • the second mode the monitoring module in each of the plurality of network slices collects service indicators and resource indicators of the network slice; and then each of the network slices separately sends respective service indicators and resource indicators to The slice management module determines, by the slice management module, an independent decision result of each network slice according to a service indicator and a resource indicator of each network slice.
  • Step 602 If the independent decision results of the multiple network slices are not completely consistent, the slice management module separately determines a final decision result for each network slice according to the independent decision result of the multiple network slices.
  • Step 603 The slice management module sends the final decision result to the VIM, where the final decision result is used to indicate that resources of the first network slice of the multiple network slices are allocated to the multiple network slices.
  • a second network slice wherein the independent decision result of the first network slice is a contraction, and the independent decision result of the second network slice is to keep the number of instances unchanged or expanded; or, the first network slice The result of the independent decision is to keep the number of instances unchanged, and the independent decision result of the second network slice is expansion.
  • the load between multiple network slices may be interlaced with peaks and valleys.
  • the interleaving relationship is used to make a more rational allocation of resources, and the low-load network is sliced.
  • Resource allocation to high-load network slicing can increase the utilization of infrastructure resources. For example, if the CPU utilization of a network slice is less than 20%, a shrink request will be initiated. When the network slice is under normal load, such as CPU utilization is about 30%, although the threshold condition for triggering the shrinkage has not been reached, However, the network slice has a certain amount of waste of resources. With this embodiment of the present application, this part of the wasted resources can be allocated to other network slices, so that the utilization efficiency of the partially wasted resources can be improved, thereby improving the overall utilization of the infrastructure resources.
  • the analysis engine inside the network slice may adopt a pattern matching (Pattern Match) or a prediction algorithm before the slice management module or the slice elastic expansion decision module inside the network slice makes an independent decision result.
  • Pattern Match Pattern Match
  • Prediction and other methods, combined with the current resource indicators and service indicators of the network slice and the historical resource indicators and historical service indicators of the network slice, predict the change trend of the resource indicators and service indicators of the network slice, that is, predict the predicted resources of the network slice in the future. Indicators and forecasted business indicators.
  • the slice management module or the slice elastic scalability decision module in the network slice can determine the independent decision of the network slice by combining the current predicted service indicator and the predicted resource indicator of the network slice on the basis of the current service indicator and resource indicator of the network slice. result.
  • the network slice can be expanded in advance before the load of a certain network slice is abrupt, to better comply with the SLA of the network slice.
  • the first resource allocation strategy :
  • the embodiment of the present application may add a resource coordination ratio parameter attribute to the network slice, and perform resource allocation according to the resource cooperation ratio parameter of the network slice, where the resource cooperation ratio parameter is a network.
  • the slice management module needs to support operations such as adding, changing, and checking related to the resource cooperation ratio parameter.
  • the process of the related operation is as shown in FIG. 7.
  • the process of adding the resource synergy parameter in the network slice template may be referred to step 701 to Step 704:
  • Step 701 The slice management module receives a request from a user for instructing to create a network slice template, where the network slice template includes a resource collaboration ratio parameter.
  • Step 702 The slice management module creates the network slice template according to the request.
  • the resource synergy parameter included in the network slice template after the creation is completed is allowed to be viewed and modified.
  • the slice management module can authenticate the user before creating the network slice template, and check the values of the parameters carried in the request.
  • Step 703 The slice management module inserts the network slice template after the creation is completed into the template library.
  • Step 704 After completing the template creation process, the slice management module returns a template creation success confirmation message to the user.
  • step 705 For the process of modifying the resource synergy parameter in the network slice template that has been created, refer to step 705 to step 708:
  • Step 705 The slice management module receives a request from the user to indicate that the resource cooperation ratio parameter of the network slice template is updated, where the request carries the value of the new resource cooperation ratio parameter.
  • Step 706 The slice management module modifies the value of the resource synergy parameter in the network slice template according to the request.
  • the slice management module can authenticate the user and modify the network slice template to be modified before modifying the resource synergy parameter.
  • Step 707 After the slice management module completes updating the network slice template, the modified network slice template is reinserted into the template library.
  • Step 708 The slice management module returns a parameter update success confirmation message to the user.
  • Step 709 The slice management module receives a request from the user for instructing to query a network slice template attribute, where the number of the network slice template to be viewed may be specified, and if a specific network slice template is not specified in the request, the query is performed.
  • the properties of all network slice templates are not specified in the request.
  • Step 710 The slice management module extracts a corresponding network slice template from the template library according to the specified slice template number. If no number of the network slice template is specified in the request, all the network slice templates are extracted.
  • the slice management module can authenticate the user before extracting the network slice template.
  • Step 711 The slice management module returns the acquired attributes of the network slice template to the user, where the attribute includes a resource cooperation ratio parameter.
  • the foregoing process describes the action of adding, modifying, and querying the slice resource synergy parameter in the network slice template attribute, and solves the problem of configuring the resource synergy parameter.
  • the step of the embodiment can flexibly share the resource of the network slice.
  • the scale is modified to provide support for resource collaboration between network slices.
  • the slice management module can The network slice instance is created by using the network slice template, and the network slice instance included in the first network slice in step 602 is created by using the network slice template, and the network slice instance included in the first network slice after the creation is completed.
  • the resource synergy parameter values are allowed to be viewed and modified.
  • a higher resource cooperation ratio parameter may be set for the network slice instance for cost considerations, and a lower resource cooperation ratio parameter may be set for the network slice instance for performance reasons.
  • a higher resource cooperation ratio parameter may be set for the network slice instance for cost considerations
  • a lower resource cooperation ratio parameter may be set for the network slice instance for performance reasons.
  • the process of modifying the resource synergy parameter in the network slice instance is as shown in FIG. 8 and includes the following steps:
  • Step 801 The slice management module receives a request from the user to indicate that the resource cooperation ratio parameter in the network slice instance is modified, where the request carries the identifier of the network slice instance to be modified and the value of the new resource cooperation ratio parameter.
  • Step 802 The slice management module modifies the value of the resource cooperation ratio parameter in the specified network slice instance according to the request.
  • the slice management module may authenticate the user who sent the request message before modifying the resource synergy parameter.
  • Step 803 The slice management module returns a parameter update confirmation message to the user.
  • the embodiment of the present application provides a modification process for modifying a resource cooperation ratio parameter in a network slice that has been instantiated, and solves a parameter update problem of a network slice instance that has been instantiated through a network slice template, so that the user can flexibly access the network.
  • the resource synergy ratio of the slice instance is updated to support a more flexible collaborative policy configuration.
  • the resource cooperation ratio parameter value of the first network slice may be considered to be included in the first network slice.
  • a resource cooperation ratio parameter value of any one of the network slice instances; if the resource cooperation ratio parameter of the network slice instance included in the first network slice is not completely the same, the resource synergy parameter value of the first network slice may be considered as
  • the minimum value of the resource cooperation ratio parameter values of all the network slice instances included in the first network slice for example, the network slice includes two network slice instances, and the resource cooperation ratio parameter values of the two network slice instances are respectively 10%. with 20%, then the smaller value of 10% can be used as the resource synergy parameter value of the network slice.
  • the slice management module may acquire the total resource occupied by the first network slice and the resource cooperation ratio parameter value of the first network slice, so that the slice from the first network is obtained.
  • the resource allocated to the second network slice is not greater than a product of a total resource occupied by the first network slice and a resource synergy parameter value of the first network slice.
  • the resource cooperation ratio parameter value of the first network slice is a minimum value among resource parameter ratio parameter values of all network slice instances included in the first network slice.
  • the slice management module may separately acquire each of the first network slice included The total resource occupied by the network slice instance and the resource synergy parameter value of each network slice instance, so that the resource allocated from the network slice instance to the second network slice is not greater than the total resource occupied by the network slice instance.
  • the product of the network slice instance's resource synergy ratio parameter value may be separately acquired.
  • a network slice includes a network slice instance A and a network slice instance B, and the resource cooperation ratio parameter values of the network slice instance A and the network slice instance B are 10% and 20%, respectively, and the network slice instance A and the network slice instance B occupy
  • the number of VMs is 10 and 20 respectively, so the number of VMs deployed from network slice instance A cannot exceed 1 (10*10%), and the number of VMs deployed from network slice instance B cannot exceed 4 ( 20*20%).
  • the second resource allocation strategy is the second resource allocation strategy
  • the slice management module can perform resource allocation according to the SLA indicator of the network slice, and the specific implementation manner is as follows:
  • the slice management module acquires an SLA indicator of the first network slice, and acquires a predicted service indicator of the first network slice after the resource is allocated to the second network slice. If the predicted service indicator of the first network slice does not violate the SLA indicator of the first network slice, the slice management module determines to allocate resources of the first network slice to the second network slice; If the predicted service indicator of the first network slice violates the SLA indicator of the first network slice, the slice management module determines not to allocate the resource of the first network slice to the second network slice.
  • the SLA defines the maximum delay of the contract. If the slice management module predicts that a certain network slice is allocated to other network slices, the delay of the network slice at a certain moment in the future will exceed the maximum delay defined by the SLA. In this way, the predicted service indicator violates the SLA indicator of the first network slice, and the slice management module may decide not to allocate resources from the network slice.
  • the third resource allocation strategy is the third resource allocation strategy.
  • the slice management module may perform the steps in the method shown in FIG. 6 multiple times, in order to make the network slice better comply with the SLA, and in order to reduce unnecessary resource allocation actions, avoid frequently performing a certain network slice.
  • the action of shrinking or expanding for example, allocating resources of one network slice to another network slice in a certain time period, and allocating resources from other network slices to the network slice in the next adjacent time period.
  • the slice management module can perform resource allocation according to the predicted independent decision result of the network slice.
  • the prediction independent decision result is an independent decision result that may be adopted by the network slice obtained according to the predicted resource indicator and the predicted service indicator of the network slice in the next time period.
  • the slice management module acquires a prediction independent decision result of the first network slice. If the prediction independent decision result of the first network slice is not expansion, the slice management module determines to allocate resources of the first network slice to the second network slice; if the prediction of the first network slice is independent The result of the decision is expansion, and the slice management module determines not to allocate resources of the first network slice to the second network slice.
  • the slice management module may return the final decision result corresponding to the multiple network slices to each network slice, and the returned message may include a code for indicating the final decision result, such as maintaining with 0.
  • the number of the current instance is unchanged. The value of 1 indicates that the network slice needs to be passively reduced. If the result is 2, the network segment needs to be passively expanded. If the final decision result is to expand or shrink, the returned message also carries the number of instances of the expansion. The number of instances of the contraction.
  • step 603 the slice management module further needs to send the final decision result to the VIM, and the final decision result is executed by the VIM.
  • the final decision result may be sent by the slice management module to the VIM in the following ways:
  • the slice management module may send the final decision result to the VIM through an interface between the VNFM and the VIM, as shown in FIG. 9; Or the slice management module may send the final decision result to the NFVO through an interface between the VNFM and the NFVO, and then the NFVO may pass the interface between the NFVO and the VIM to the final The decision result is forwarded to the VIM, such as path 2 in FIG.
  • the slice management module may send the final decision result to the OSS/BSS through which the OSS/BSS passes the OSS/BSS and An interface between the NFVOs sends the final decision result to the NFVO, and the NFVO sends the final decision result to the VIM through an interface between the NFVO and the VIM, as shown in FIG. Route 3.
  • the slice management module may send the final decision result to the VIM through an interface between the NFVO and the VIM, as shown in path 4 in FIG. 10; Or the slice management module may send the final decision result to the VNFM through an interface between the NFVO and the VNFM, and the final is performed by the VNFM through an interface between the VNFM and the VIM The decision result is sent to the VIM, as shown in Route 5 in FIG.
  • the slice management module may send the final decision result to the NFVO through an interface between the OSS/BSS and the NFVO, and then pass the NFVO The interface between the NFVO and the VIM forwards the final decision result to the VIM, such as path 6 in FIG.
  • the present embodiment takes three network slices as an example, and illustrates the simplest of the load changes of the three network slices and the number of instances included in the three network slices. Resource allocation method between network slices. It should be noted that this embodiment is only one implementation of the present application and does not constitute a limitation of the present application.
  • the eMBB network slice and the ultra-reliable MTC (uMTC) network slice are both light.
  • Load state but because the shrinkage threshold is not reached, the shrinkage action will not be triggered; the mMTC network slice will periodically have sudden load, which are the four positions B1, B2, B4, B5 in Figure 12, uMTC network The slice will have a sudden load at the B3 position.
  • the slice management module makes the following decisions based on the state of these three network slices:
  • the independent decision result of the mMTC network slice is capacity expansion.
  • the uMTC network slice is in a light load state, and the final decision result of the slice management module is passively shrinking the uMTC network slice, and from the uMTC network slice allocation.
  • Two VMs are used for mMTC network slicing; between the positions of B1 and B2 in Figure 12, when the load of the mMTC network slice is in a downward trend, the slice management module shrinks the mMTC network slice and slices it from the mMTC network. Two VMs are allocated and returned to the uMTC network slice.
  • the slice management module has two options, one is to allocate resources from the eMBB network slice, and the other is to uMTC network slicing resources.
  • the slice management module combines the prediction algorithm to predict the load change trend of the eMBB network slice and the uMTC network slice.
  • the prediction result indicates that the load of the uMTC network slice changes at the B3 position. If the resource is allocated from the uMTC network slice, the uMTC network The slice will violate the SLA index of the uMTC network slice due to the excessive load at the B3 position. Therefore, the final decision result is to allocate 4 VMs to the mMTC network slice from the eMBB network slice.
  • the final decision results at the B4 and B5 locations in Figure 12 are similar to the final decision results at the B1 and B2 locations, and are not described here.
  • the present application further provides a resource management apparatus for network slice.
  • the resource management apparatus of the network slice includes an obtaining unit 131, a determining unit 132, and a sending. Unit 133.
  • the obtaining unit 131 is configured to separately obtain independent decision results of multiple network slices, where the independent decision result includes expanding, shrinking, or keeping the number of instances unchanged.
  • the determining unit 132 if the independent decision results of the multiple network slices are not completely consistent, determining, for each network slice, an independent decision result according to the multiple network slices Decision result.
  • the sending unit 133 is configured to send the final decision result to the VIM, where the final decision result is used to indicate that resources of the first network slice of the multiple network slices are allocated to the multiple network slices.
  • a second network slice wherein the independent decision result of the first network slice is a contraction, and the independent decision result of the second network slice is to keep the number of instances unchanged or expanded; or, the first network slice The result of the independent decision is to keep the number of instances unchanged, and the independent decision result of the second network slice is expansion.
  • the device may further include:
  • a receiving unit configured to receive a request for instructing to create a network slice template, where the network slice template includes a resource cooperation ratio parameter, and the resource cooperation ratio parameter, before the obtaining unit 131 acquires an independent decision result of the multiple network slices The maximum percentage of resources allowed to be shared for a network slice instance.
  • a template creating unit configured to create the network slice template according to the request.
  • an instance creating unit configured to create, according to the network slice template, a network slice instance included in the first network slice.
  • the acquiring unit 131 may be further configured to: acquire the first network slice.
  • the acquiring unit 131 may be further configured to: acquire the first network slice. a service level agreement SLA indicator; and obtaining a predicted service indicator of the first network slice after allocating resources to the second network slice.
  • the determining unit 132 determines the final decision result for each network slice separately.
  • the method is further configured to: determine that the predicted service indicator of the first network slice does not violate the SLA indicator of the first network slice.
  • the acquiring unit 131 may be further configured to: acquire the first network slice. The prediction of independent decision making results.
  • the determining unit 132 is specifically configured to: if the prediction independent decision result of the first network slice is not expansion, determine to allocate resources of the first network slice to the second network slice; The prediction independent decision result of the first network slice is expansion, and then determining not to allocate resources of the first network slice to the second network slice.
  • the acquiring unit 131 is configured to: receive an independent decision result sent by each of the plurality of network slices separately when acquiring the independent decision result of the multiple network slices; or, receiving the The service indicator and the resource indicator respectively sent by each of the plurality of network slices are respectively determined, and the independent decision result of each network slice is determined according to the service indicator and the resource indicator of each network slice respectively.
  • the device may be deployed within the VNFM; or the device may be deployed within the NFVO; or the device may be deployed within the OSS/BSS.
  • the sending unit 133 sends the final decision result to the VIM through an interface between the VNFM and the VIM; or the sending unit 133 passes The interface between the VNFM and the NFVO sends the final decision result to the NFVO, and the NFVO forwards the final decision result to the VIM through an interface between the NFVO and the VIM; Or the sending unit 133 sends the final decision result to the OSS/BSS, and the final decision result is sent by the OSS/BSS to the NFVO through an interface between the OSS/BSS and the NFVO, The final decision result is then sent by the NFVO to the VIM through an interface between the NFVO and the VIM.
  • the sending unit 133 sends the final decision result to the VIM through an interface between the NFVO and the VIM; or the sending unit 133 passes The interface between the NFVO and the VNFM sends the final decision result And to the VNFM, the final decision result is sent by the VNFM to the VIM through an interface between the VNFM and the VIM.
  • the sending unit 133 sends the final decision result to the NFVO through an interface between the OSS/BSS and the NFVO, and then the NFVO The final decision result is forwarded to the VIM through an interface between the NFVO and the VIM.
  • the division of the unit in the embodiment of the present application is schematic, and is only a logical function division. In actual implementation, there may be another division manner.
  • the functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the present application further provides a resource management device for a network slice.
  • the device includes a network interface 141 and a processor 142, for example, the network interface 141 and The processors 142 are connected to one another via a bus 143.
  • the processor 142 is configured to perform the following operations:
  • independent decision results of multiple network slices respectively where the independent decision result includes expanding, shrinking, or maintaining the number of instances; if the independent decision results of the multiple network slices are not completely consistent, according to the Independent decision results of the plurality of network slices respectively determine a final decision result for each network slice; the final decision result is sent to the VIM through the network interface 141, the final decision result is used to indicate that the plurality of networks are sliced
  • the resource of the first network slice is allocated to the second network slice of the plurality of network slices; wherein the independent decision result of the first network slice is a contraction, and the independent decision result of the second network slice is Keeping the number of instances unchanged or expanding; or, the independent decision result of the first network slice is to keep the number of instances unchanged, and the independent decision result of the second network slice is expansion.
  • the network interface 141 can be a wired interface, such as a fiber-optic distributed data interface. Fiber Distributed Data Interface (FDDI), Ethernet (English: Ethernet) interface. Network interface 1101 may also be a wireless interface, such as a wireless local area network interface.
  • FDDI Fiber Distributed Data Interface
  • Ethernet Edinburgh: Ethernet
  • the processor 142 may be a general-purpose processor, including a central processing unit (English: central processing unit, CPU for short), a network processor (network processor, NP for short), and the like; English: figital signal processor (referred to as: DSP), application-specific integrated circuit (English: application-specific integrated circuit, ASIC), field-programmable gate array (English: field-programmable gate array, referred to as: FPGA) or other programmable Logic devices, etc.
  • a central processing unit English: central processing unit, CPU for short
  • NP network processor
  • NP network processor
  • the device may further include: a memory for storing a program.
  • the program can include program code, the program code including computer operating instructions.
  • the memory may include random access memory (English: random access memory, RAM for short), and may also include non-volatile memory (English: non-volatile memory), such as at least one disk storage.
  • the processor 142 executes the program code stored in the memory to implement the above functions.
  • the technical solution provided by the present application utilizes the characteristics of high and low interleaving between network slices to more rationally allocate resources, so that the independent decision result is that the expanded network slice can be reduced or kept from the independent decision result.
  • the number of other network slice coordination resources that are unchanged can also make the independent decision result coordinate the resources of the network slice that keeps the number of instances from the independent decision result to other network slices, so that the network slice that needs to increase the capacity does not need to be based on the network slice.
  • the facility requests new resources, increases the utilization of infrastructure resources, and reduces the resource procurement costs of the sliced tenants.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the present invention is directed to a method, apparatus (system), and computer program according to an embodiment of the present invention.
  • the flow chart and/or block diagram of the product is described. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG.
  • These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

一种网络切片的资源管理方法和装置，该方法利用网络切片之间负载高低交错的特征对资源进行更合理的调配，使得独立决策结果为扩容的网络切片可以从独立决策结果为缩容或保持实例数不变的其它网络切片协调资源，也可以使独立决策结果为保持实例数不变的网络切片从独立决策结果为缩容的其它网络切片协调资源，从而使得需要增加容量的网络切片无需向基础设施请求新的资源，提高了基础设施资源的利用率，同时降低了切片租户的资源采购成本。

Description

一种网络切片的资源管理方法和装置 技术领域
本发明涉及通信领域，尤其涉及一种网络切片(slice)的资源管理方法和装置。
背景技术
网络功能虚拟化(Network Function Virtualization，简称：NFV)是第五代移动通信技术(5-Generation，简称：5G)网络中的关键技术之一。在欧洲电信标准化协会(European Telecommunications Standards Institute，简称：ETSI)NFV标准中定义了一系列管理网络服务(Network Service，简称：NS)和虚拟网络功能(Virtual Network Function，简称：VNF)的生命周期管理流程，包括NS模板的上线、NS实例化、NS弹性伸缩、更新以及实例终结。其中，NS又可称为网络切片，网络切片可理解为是网络的逻辑功能的抽象化。
下面介绍网络切片的弹性伸缩机制，每个网络切片在决策是否进行扩容或缩容时都可采用如图1所示的流程：
S11：网络切片内部的监控模块会周期性地采集网络切片的运行状态指标。例如，运行状态指标包括资源指标和业务指标。监控模块将采集到的运行状态指标上报给切片弹性伸缩决策模块。
S12：切片弹性伸缩决策模块根据收集到的运行状态指标做弹性伸缩决策。决策结果可以是保持当前NS的实例数不变、创建一定数目的NS实例或者终结一定数目的NS实例。
S13：切片弹性伸缩决策模块将决策结果发送给ETSI NFV架构中的管理与编排(Management and Orchestration，简称：MANO)模块，由MANO执行对应的扩容或缩容流程。
S14：MANO完成扩容或缩容流程后，给切片弹性伸缩决策模块回复确认消息。
根据上述流程，MANO可以配合切片弹性伸缩决策模块完成一系列的扩容与缩容的动作。扩容的主要目的是满足网络切片对资源的需求，及时补充一定数目的实例；缩容的目的是在网络服务空闲时及时对资源进行回收，以免造成资源浪费，降低切片租户的成本。
但现有的网络切片的弹性伸缩机制对基础设施的资源利用率仍比较低。
发明内容
本申请提供一种网络切片的资源管理方法和装置，用以优化对基础设施的资源利用率。
本申请第一方面，提供了一种网络切片的资源管理方法，包括：
切片管理模块分别获取多个网络切片的独立决策结果，其中，所述独立决策结果包括扩容、缩容或保持实例数不变；
若所述多个网络切片的独立决策结果不完全一致，则所述切片管理模块根据所述多个网络切片的独立决策结果为每个网络切片分别确定最终决策结果；
所述切片管理模块将所述最终决策结果发送给VIM，所述最终决策结果用于指示将所述多个网络切片中的第一网络切片的资源调配给所述多个网络切片中的第二网络切片；
其中，所述第一网络切片的独立决策结果为缩容，所述第二网络切片的独立决策结果为保持实例数不变或扩容；或，所述第一网络切片的独立决策结果为保持实例数不变，所述第二网络切片的独立决策结果为扩容。
本申请提供的方案利用网络切片之间负载高低交错的特征对资源进行更合理的调配，使得独立决策结果为扩容的网络切片可以从独立决策结果为缩容或保持实例数不变的其它网络切片协调资源，也可以使独立决策结果为保持实例数不变的网络切片从独立决策结果为缩容的其它网络切片协调资源，从而使得需要增加容量的网络切片无需向基础设施请求新的资源，提高了基础设施资源的利用率，同时降低了切片租户的资源采购成本。
在一个可能的设计中，在所述切片管理模块获取多个网络切片的独立决策结果之前，所述方法还包括：
所述切片管理模块接收用于指示创建网络切片模板的请求，所述网络切片模板包括资源协同比参数，所述资源协同比参数为网络切片实例允许被分享的最大资源比例；
所述切片管理模块根据所述请求创建所述网络切片模板；
所述切片管理模块根据所述网络切片模板创建所述第一网络切片包含的网络切片实例。
通过这种实现方式，描述了在网络切片模板中增加资源协同比参数这个属性的过程，以及描述了利用携带有资源协同比参数的网络切片模板创建网络切片实例的过程，解决了切片资源协同比参数的配置问题。
在一个可能的设计中，在所述切片管理模块根据所述多个网络切片的独立决策结果为每个网络切片分别确定最终决策结果之前，所述方法还包括：
所述切片管理模块获取所述第一网络切片占用的总资源和所述第一网络切片的资源协同比参数值，以使得从所述第一网络切片调配给所述第二网络切片的资源不大于所述第一网络切片占用的总资源与所述第一网络切片的资源协同比参数值的乘积；
其中，所述第一网络切片的资源协同比参数值为所述第一网络切片包含的所有网络切片实例的资源协同比参数值中的最小值。
通过这种实现方式，可以避免网络切片的资源被无限剥夺，使得网络切片之间的资源调配更加合理。
在一个可能的设计中，在所述切片管理模块根据所述多个网络切片的独立决策结果为每个网络切片分别确定最终决策结果之前，所述方法还包括：
所述切片管理模块获取所述第一网络切片的SLA指标；
所述切片管理模块获取若分配资源给所述第二网络切片之后的所述第一网络切片的预测业务指标；
所述切片管理模块确定所述第一网络切片的预测业务指标不违反所述第 一网络切片的SLA指标。
通过这种实现方式，可以保证网络切片遵守SLA，从而更好地为用户提供网络服务。
在一个可能的设计中，所述切片管理模块根据所述多个网络切片的独立决策结果为每个网络切片分别确定最终决策结果，包括：
所述切片管理模块获取所述第一网络切片的预测独立决策结果；
如果所述第一网络切片的预测独立决策结果不是扩容，则所述切片管理模块确定将所述第一网络切片的资源调配给所述第二网络切片；
如果所述第一网络切片的预测独立决策结果是扩容，则所述切片管理模块确定不将所述第一网络切片的资源调配给所述第二网络切片。
通过这种实现方式，可以令网络切片更好地遵守SLA，同时也可以减少不必要的资源调配动作，避免频繁地对某一个网络切片进行缩容或扩容的动作。
在一个可能的设计中，所述切片管理模块可以部署在VNFM内；或，所述切片管理模块可以部署在NFVO内；或，所述切片管理模块可以部署在OSS/BSS内。
在一个可能的设计中，所述切片管理模块获取多个网络切片的独立决策结果，包括：
所述切片管理模块接收所述多个网络切片中的每个网络切片分别发送的的独立决策结果；或，所述切片管理模块接收所述多个网络切片中的每个网络切片分别发送的的业务指标和资源指标，并根据每个网络切片的业务指标和资源指标分别确定每个网络切片的独立决策结果。
在一个可能的设计中，若所述切片管理模块部署在VNFM内，则所述切片管理模块通过所述VNFM与所述VIM之间的接口将所述最终决策结果发送给所述VIM；或所述切片管理模块通过所述VNFM与NFVO之间的接口将所述最终决策结果发送给所述NFVO，再由所述NFVO通过所述NFVO与所述VIM之间的接口将所述最终决策结果转发给所述VIM；或所述切片管理模块将所述最终决策结果发送给所述OSS/BSS，由所述OSS/BSS通过所述OSS/BSS与 NFVO之间的接口将所述最终决策结果发送给所述NFVO，再由所述NFVO通过所述NFVO与所述VIM之间的接口将所述最终决策结果发送给所述VIM；
若所述切片管理模块部署在NFVO内，则所述切片管理模块通过所述NFVO与所述VIM之间的接口将所述最终决策结果发送给所述VIM；或所述切片管理模块通过所述NFVO与VNFM之间的接口将所述最终决策结果发送给所述VNFM，再由所述VNFM通过所述VNFM与所述VIM之间的接口将所述最终决策结果发送给所述VIM；
若所述切片管理模块部署在OSS/BSS内，则所述切片管理模块通过所述OSS/BSS与NFVO之间的接口将所述最终决策结果发送给所述NFVO，再由所述NFVO通过所述NFVO与所述VIM之间的接口将所述最终决策结果转发给所述VIM。
本申请第二方面，提供了一种网络切片的资源管理装置，所述装置具有实现上述方法实施例中切片管理模块行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块或单元。
在一种可能的设计中，所述装置的结构中包括获取单元、确定单元和发送单元，这些单元可以执行上述方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
在一种可能的设计中，所述装置的结构中包括网络接口、处理器、总线以及存储器，所述网络接口用于与所述通信系统中的其他设备进行通信交互，所述处理器被配置为支持所述装置执行上述方法中相应的功能。所述存储器与所述处理器耦合，其保存所述装置必要的程序指令和数据。
附图说明
图1为现有技术下一种网络切片的弹性伸缩机制的流程图；
图2为现有技术下一种网络切片的部署架构的示意图；
图3为现有技术下两个网络切片根据负载的变化进行弹性伸缩决策的曲 线示意图；
图4为本申请实施例提供的一种网络切片的资源管理方法所应用的NFV系统的示意图；
图5为本申请实施例提供的一种网络切片和切片管理模块之间的信息交互示意图；
图6为本申请实施例提供的一种网络切片的资源管理方法的流程图；
图7为本申请实施例提供的一种增加、修改和查询资源协同比参数的操作流程图；
图8为本申请实施例提供的一种更新网络切片实例中的资源协同比参数的操作流程图；
图9为本申请实施例提供的一种最终决策结果的发送途径的示意图；
图10为本申请实施例提供的另一种最终决策结果的发送途径的示意图；
图11为本申请实施例提供的又一种最终决策结果的发送途径的示意图；
图12为本申请实施例提供的一种三个网络切片之间的资源调配方法的示意图；
图13为本申请实施例提供的一种网络切片的资源管理装置的结构示意图图；
图14为本申请实施例提供给的另一种网络切片的资源管理装置的结构示意图。
具体实施方式
以下，对本申请中的部分用语进行解释说明。
“网络切片”，又可称为NS，在第三代合作伙伴计划(3rd Generation Partnership Project，简称：3GPP)标准中的定义是：一个网络切片由用于支持特定通信业务的一组逻辑网络功能组成。为了多个网络切片之间不相互影响，要满足业务的多样性和网络切片的隔离性。运营商可以在同一套基础设施上为不同类型的通信提供量身定制的网络切片，如图2所示，运营商为移动 宽带(Mobile Broad Band，简称：MBB)通信提供MBB网络切片，为车辆间通信(Vehicle to Vehicle，简称：V2V)提供V2V切片，为机器类通信(Machine Type Communication，简称：MTC)提供MTC网络切片。
“网络切片实例”，通过网络切片模板生成。通过网络切片模板创建网络切片实例的过程称为实例化。例如，网络切片实例可由软件实现。一个网络切片可以包含多个网络切片实例，这多个网络切片实例所使用的网络切片模板可以相同，也可以不同。本申请使用“实例数”来指一个网络切片包含的网络切片实例的数目。
“资源调配”，是指将一个网络切片下所占用的资源，如虚拟机(简称：VM)、中央处理器(Central Processing Unit，简称：CPU)、内存和硬盘存储等，调配给另一个网络切片使用，从而可以省略另一个网络切片从空闲资源中申请新资源的过程。例如，可以通过撤销一个网络切片下的一部分网络切片实例并将撤销的这部分网络切片实例所占用的资源调配给另一个网络切片的方式实现资源调配；也可以通过修改网络切片实例的归属关系的方式实现资源调配；还可以在不撤销网络切片实例的前提下通过仅将网络切片实例所占用的一部分资源调配给其它网络切片的方式实现资源调配。
“独立决策结果”，是根据一个网络切片的资源指标和业务指标得到的弹性伸缩决策结果。每个网络切片的独立决策结果只与该网络切片自身的状态有关，例如，与该网络切片的资源指标和业务指标有关。
“最终决策结果”，也可以称为协同决策结果，是综合多个网络切片的独立决策结果得到的弹性伸缩决策结果。每个网络切片的最终决策结果不仅与该网络切片自身的独立决策结果有关，还与其它网络切片的独立决策结果有关。
“资源指标”，可以包括以下的一项或多项：网络切片包含的实例数的指标，VM个数指标，每个VM的CPU指标、内存指标、或带宽利用率指标等其他指标。
“业务指标”，取决于NS提供的服务。对于分组核心演进(Evolved Packet  Core，简称：EPC)控制面的网络服务，该业务指标可以包括信令的平均处理时延、附着的用户数、激活的承载数等；对于EPC转发面的网络服务，该业务指标可以包括报文转发带宽、报文处理时延等。
“服务水平协议(Service Level Agreement，简称：SLA)”，是指一种描述运营商或内容提供商关于业务的运行时间、运行质量、链接性等方面的承诺的协议。如，用户购买运营商的服务时，运营商和用户之间会签订SLA，比如运营商提供给用户的网络带宽不能低于50兆(单位：M)，如果运营商提供的带宽不足50M，就算运营商违反SLA，需要对用户做出赔偿。
另外，需要理解的是，在本申请的描述中，“第一”、“第二”等词汇，仅用于描述目的，而不能理解为指示或暗示相对重要性。并且，除非另有说明，“多个”的含义是两个或两个以上。
下面结合说明书附图和各实施例对本发明技术方案进行说明。
目前的弹性伸缩机制中，每个网络切片根据自身的负载独立地决定是否进行扩容或缩容，如图3所示为两个网络切片分别根据各自的负载变化进行弹性伸缩决策的曲线示意图。一般情况下，不同的网络切片的负载变化趋势不一样，并且随着时间的推移，同一网络切片的负载也会发生变化。图3中，增强型移动带宽(enhanced MBB，简称：eMBB)网络切片的负载始终处于较低水平，但还未达到缩容的条件，因此eMBB网络切片占用的VM个数始终保持不变。大规模机器类通信(massive MTC，简称：mMTC)网络切片的负载呈现出高低变化的趋势，MANO根据mMTC网络切片的负载的变化情况配合mMTC网络切片完成一系列扩容与缩容的动作。
但这种弹性伸缩机制因各个网络切片在进行弹性伸缩决策时只考虑自身负载的变化，而没有考虑部署在同一片基础设施上的其他切片的负载变化情况，采取的弹性伸缩策略只是局部最优解，而不是整个基础设施的全局最优解，因此对基础设施资源的利用率较低。
为此，本申请提出了一种网络切片的资源管理方法和装置，利用网络切片之间负载高低交错的特征对资源进行更合理的调配，使得独立决策结果为 扩容的网络切片可以从独立决策结果为缩容或保持实例数不变的其它网络切片协调资源，也可以使独立决策结果为保持实例数不变的网络切片从独立决策结果为缩容的其它网络切片协调资源，从而使得需要增加容量的网络切片无需向基础设施请求新的资源，提高了基础设施资源的利用率，同时降低了切片租户的资源采购成本。
本申请提供的网络切片的资源管理方法，可应用于图4所示的NFV系统，该NFV系统可以通过多种网络实现，例如数据中心网络、服务提供者网络、或者局域网(Local Area Network，简称：LAN)等。
如图4所示，该NFV系统可以包括NFV-MANO 101，NFV基础设施(NFV Infrastructure，简称：NFVI)102，多个VNF 103，多个网元管理器(element management，简称：EM)104，以及一个或多个运营支撑系统或业务支撑系统(Operation Support System/Business Support System，简称：OSS/BSS)106。
NFV-MANO 101可以包括服务、VNF和基础设施描述(Service VNF and Infrastructure Description)系统105，网络功能虚拟化编排器(Network Function Virtualization Orchestrator，简称：NFVO)107，一个或多个虚拟化的网络功能管理(Virtualised Network Function Manager，简称：VNFM)108，以及一个或多个虚拟化基础设施管理器(Virtualized Infrastructure Manager，简称VIM)109。NFVI 102可以包括计算硬件110、存储硬件111、网络硬件112组成的硬件资源层、虚拟化层、以及虚拟计算113(例如虚拟机)、虚拟存储114和虚拟网络115组成的虚拟资源层。
硬件资源层中的计算硬件110可以为专用的处理器或通用的用于提供处理和计算功能的处理器；存储硬件111用于提供存储能力，该存储能力可以是存储硬件111本身提供的(例如一台服务器的本地内存)，也可以通过网络提供(例如服务器通过网络连接一个网络存储设备)；网络硬件112可以是交换机、路由器和/或其他网络设备，网络硬件112用于实现多个设备之间的通信，多个设备之间通过无线或有线连接。
NFVI 102中的虚拟化层用于抽象硬件资源层的硬件资源，将VNF 103和硬 件资源所属的物理层解耦，向VNF 103提供虚拟资源。
虚拟资源层可以包括虚拟计算113、虚拟存储114和虚拟网络115。虚拟计算113、虚拟存储114可以以虚拟机或其他虚拟容器的形式提供给VNF 103，例如一个或多个VNF 103可以部署在一台虚拟机上。虚拟化层通过抽象网络硬件112形成虚拟网络115。虚拟网络115，例如虚拟交换机(Vswitches)，用于实现多个虚拟机之间，或多个承载VNF的其他类型的虚拟容器之间的通信。网络硬件的虚拟化可以通过虚拟LAN(Vritual LAN，简称：VLAN)、虚拟专用局域网业务(Virtual Private LAN Service，简称：VPLS)、虚拟可扩展局域网(Virtual eXtensible Local Area Network，简称：VxLAN)或通用路由封装网络虚拟化(Nerwork Virtualization using Generic Routing Encapsulation，简称：NVGRE)等技术实现。
OSS/BSS 106主要面向电信服务运营商，提供综合的网络管理和业务运营功能，包括网络管理(例如故障监控、网络信息收集等)、计费管理以及客户服务管理等。服务、VNF和基础设施描述系统105在ETSI GS NFV 002v1.1.1标准中有详细介绍，本申请实施例在此不再赘述。
NFV-MANO 101可以用于实现VNF 103和NFVI 102的监控和管理。NFVO 107可以与一个或多个VNFM 108进行通信以实现与资源相关的请求、发送配置信息给VNFM 108、以及收集VNF 103的状态信息。另外，NFVO 107还可以与VIM 109进行通信以实现资源分配，和/或，实现虚拟化硬件资源的配置信息和状态信息的预留和交换。VNFM 108可以在NFVO 107的指挥下与VNF 103和EM 104通信以执行VNF 103生命周期管理和实现配置/状态信息的交换，即负责VNF 103的创建、删除、启动、停止等。VIM 109可以用于控制和管理VNF 103和计算硬件110、存储硬件111、网络硬件112、虚拟计算113、虚拟存储114、虚拟网络115的交互。例如，VIM 109可以用于执行资源向VNF 103的分配操作。VNFM 108和VIM 109可以互相通信以交换虚拟化硬件资源配置和状态信息。
NFVI 102包含硬件和软件，二者共同建立虚拟化环境以部署、管理和执 行VNF 103。换句话说，硬件资源层和虚拟资源层用于向各个VNF 103提供虚拟资源，例如虚拟机和/或其他形式的虚拟容器。
VNF 103是至少一个网络功能的虚拟化，该网络功能之前是由物理网络设备提供的。在一种实现方式下，VNF 103可以是一个虚拟化的移动管理实体(Mobility Management Entity，简称：MME)节点，用于提供典型的非虚拟化的MME设备提供的所有网络功能。在另一种实现方式下，VNF 103可以用于实现非虚拟化的MME设备上提供的全部组件中的部分组件的功能。一个VNF 103可以由多个VM组成。EM 104可以用于管理一个或多个VNF 103。
本申请提供的网络切片的资源管理方法主要涉及两种网元，一种是网络切片，一种是切片管理模块，切片管理模块用于根据多个网络切片的独立决策结果对这多个网络切片之间的资源进行协调。
网络切片可以包括一个或多个VNF 103。例如，在图4中，网络切片1由VNF 1和VNF 2组成，网络切片2由VNF 3组成。每个网络切片的独立决策结果可以由与该网络切片所包含的VNF 103内部决定，也可以由该网络切片所包含的VNF 103相连的EM 104决定，也可以由VNFM 108决定，或者也可以由切片管理模块决定。
切片管理模块可以部署在VNFM 108内，也可以部署在NFVO 107内，或者也可以部署在在OSS/BSS 106内。
无论切片管理模块采取哪种部署方式，网络切片和切片管理模块之间的信息交互都如图5所示。图5中包括切片管理模块501和多个网络切片，如网络切片i 502、网络切片j 503和网络切片k 504。每个网络切片可以包括至少一个网络切片实例505和监控模块506。
每个网络切片内部的监控模块506，用于周期性地采集该网络切片包括的网络切片实例505的资源指标和业务指标。如图5中，
Figure PCTCN2016086031-appb-000001
表示网络切片i502内部的监控模块506采集到的网络切片i 502包括的网络切片实例505在t时刻的资源指标，
Figure PCTCN2016086031-appb-000002
表示网络切片i 502内部的监控模块506采集到的网络 切片i包括的网络切片实例505在t时刻的业务指标。
可选的，每个网络切片还可以包括切片弹性伸缩决策模块507。
当网络切片包括切片弹性伸缩决策模块507时，监控模块506可以将采集到的资源指标和业务指标上报给该网络切片内部的切片弹性伸缩决策模块507。
每个网络切片内部的切片弹性伸缩决策模块507，用于根据该网络切片的资源指标和业务指标，得到该网络切片对应的独立决策结果。切片弹性伸缩决策模块507可以基于不同的策略进行弹性伸缩决策，所述策略可以是静态阈值算法(Static Threshold)、动态阈值算法(Dynamic Threshold)或增强学习算法(Reinforcement Learning)以及其它更高级更复杂的算法。切片弹性伸缩决策模块的功能可以由图4中的EM 104实施，也可以由图4中的VNFM108实施。
当网络切片不包括切片弹性伸缩决策模块507时，切片弹性伸缩决策模块507的功能可以由切片管理模块501代为实施。即，监控模块506可以将资源指标和业务指标上报给切片管理模块501，由切片管理模块501根据网络切片的资源指标和业务指标得到该网络切片对应的独立决策结果。
切片管理模块501，用于获取多个网络切片分别对应的独立决策结果，基于所述多个网络切片分别对应的独立决策结果进行统一的弹性伸缩决策，为所述多个网络切片中的每个网络切片分别确定最终决策结果。例如，获取多个网络切片分别对应的独立决策结果包括：直接获取多个网络切片分别对应的独立决策结果，或是获取多个网络切片的资源指标和业务指标并基于这两个指标分析得到所述多个网络切片分别对应的独立决策结果。如图5中，si,t、sj,t和sk,t分别表示网络切片i 502、网络切片j 503和网络切片k 504在t时刻的资源指标和业务指标，pi,t、pj,t和pk,t分别表示网络切片i 502、网络切片j 503和网络切片k 504在t时刻的独立决策结果，ai,t、aj,t和ak,t分别表示网络切片i502、网络切片j 503和网络切片k 504在t时刻的最终决策结果。每个网络切片 的独立决策结果和最终决策结果可能相同，也可能不同。
切片管理模块501可以基于不同的策略进行统一的弹性伸缩决策，所述策略可以是SLA评估(Evaluation)、投资回报比(return on investment，简称：ROI)和最优解搜索算法(Heuristically Search)等策略中的至少一个。以切片管理模块501基于SLA评估进行统一的弹性伸缩决策为例，各个网络切片还需要将各自的SLA指标发送给切片管理模块501。
现有技术中，由于每个网络切片获取不到其他网络切片的SLA、ROI信息等，所以每个网络切片所做的弹性伸缩决策优化只是局部最优的弹性伸缩策略，而无法实现全局统筹。而本申请实施例中，切片管理模块501可以综合考虑各个网络切片的SLA、ROI信息等，采用最优搜索算法找到让各个网络切片达到全局最优的弹性伸缩策略。
切片管理模块501为个网络切片分别确定最终决策结果之后，将确定出的最终决策结果发送给VIM 508，由VIM 508根据最终决策结果调整每个网络切片的实例数。
可选的，每个网络切片还可以包括分析引擎509。
每个网络切片内部的分析引擎509，用于向监控模块506获取网络切片包括的网络切片实例505当前的资源指标和业务指标，以及结合该网络切片的历史资源指标和历史业务指标，预测该网络切片的资源指标和业务指标的变化趋势。如图5中，
Figure PCTCN2016086031-appb-000003
表示网络切片i 502内部的分析引擎509预测的网络切片i 502在t’时刻的资源指标，
Figure PCTCN2016086031-appb-000004
表示网络切片i 502内部的分析引擎509预测的网络切片i 502在t’时刻的业务指标。其中，分析引擎509可以采用模式识别(Pattern Match)或预测算法(Prediction)的方式预测资源指标和业务指标的变化趋势。
当网络切片还包括分析引擎509时，切片弹性伸缩决策模块507或者切片管理模块501还可以在资源指标和业务指标的基础上，结合分析引擎509得到的预测资源指标和预测业务指标进行弹性伸缩决策，确定网络切片对应的独 立决策结果，从而使得得到的独立决策结果更为准确。同理，切片管理模块501也可以在独立决策结果的基础上，结合分析引擎509得到的预测资源指标和预测业务指标进行统一的弹性伸缩决策，为所述多个网络切片中的每个网络切片分别确定最终决策结果，从而使得的得到的最终决策结果更为准确。
基于上述提供的NFV系统，本申请实施例还提供了一种网络切片的资源管理方法，如图6所示。本申请实施例可通过多次执行图6所示的方法中的步骤，达到动态调整各个网络切片的实例数的目的。例如，该方法可包括如下步骤：
步骤601：切片管理模块分别获取多个网络切片的独立决策结果，其中，所述独立决策结果包括为扩容、缩容或保持实例数不变。
其中，扩容的目的在于及时补充一定数目的网络切片实例，以满足网络服务对资源的需求，缩容的目的在于当网络服务空闲时及时回收一定数目的网络切片实例，以免造成资源浪费。
可选的，所述切片管理模块可以通过以下两种方式获取到多个网络切片的独立决策结果。
第一种方式：所述多个网络切片中的每个网络切片内部的监控模块采集该网络切片的业务指标和资源指标，并将其上报给该网络切片的切片弹性伸缩决策模块。切片弹性伸缩决策模块根据该网络切片的业务指标和资源指标确定出该网络切片的独立决策结果；然后所述每个网络切片分别将各自的独立决策结果发送给所述切片管理模块。
第二种方式：所述多个网络切片中的每个网络切片内部的监控模块采集该网络切片的业务指标和资源指标；然后所述每个网络切片分别将各自的业务指标和资源指标发送给所述切片管理模块，由所述切片管理模块根据每个网络切片的业务指标和资源指标分别确定每个网络切片的独立决策结果。
步骤602：若所述多个网络切片的独立决策结果不完全一致，则所述切片管理模块根据所述多个网络切片的独立决策结果为每个网络切片分别确定最终决策结果。
步骤603：所述切片管理模块将所述最终决策结果发送给VIM，所述最终决策结果用于指示将所述多个网络切片中的第一网络切片的资源调配给所述多个网络切片中的第二网络切片；其中，所述第一网络切片的独立决策结果为缩容，所述第二网络切片的独立决策结果为保持实例数不变或扩容；或，所述第一网络切片的独立决策结果为保持实例数不变，所述第二网络切片的独立决策结果为扩容。
在现网运行环境中，多个网络切片之间的负载可能会呈现波峰波谷交错的情况，本申请实施例正是利用此类交错关系对资源进行更合理的调配，将低负载的网络切片的资源调配给高负载的网络切片，从而可以提高基础设施资源的利用率。例如，假设某网络切片的CPU利用率低于20％时将发起缩容请求，当该网络切片在常规负载下，如CPU利用率为30％左右时，虽然尚未达到触发缩容的阈值条件，但该网络切片已经有一定程度的资源浪费。利用本申请实施例可以将这部分被浪费的资源调配给其它网络切片，从而可以提高这部分被浪费的资源的利用效率，进而提高基础设施资源整体的利用率。
可选的，为了得到更加准确的独立决策结果，在切片管理模块或网络切片内部的切片弹性伸缩决策模块作出独立决策结果之前，网络切片内部的分析引擎可以采用模式识别(Pattern Match)或预测算法(Prediction)等方式，结合网络切片当前的资源指标和业务指标以及网络切片的历史资源指标和历史业务指标，预测网络切片的资源指标和业务指标的变化趋势，即预测网络切片在未来的预测资源指标和预测业务指标。然后切片管理模块或网络切片内部的切片弹性伸缩决策模块可以在网络切片当前的业务指标和资源指标的基础上结合该网络切片未来的预测业务指标和预测资源指标，确定出该网络切片的独立决策结果。如此可以在某个网络切片的负载发生突变之前提前对该网络切片进行扩容，更好地遵守该网络切片的SLA。
以上描述了一种网络切片之间的资源调配方法，为了令网络切片之间的资源调配更加合理，本申请实施例还提出了以下三种资源调配策略。这三种资源调配策略可以单独实施，也可以联合实施。
第一种资源调配策略：
为了避免网络切片的资源被无限剥夺，本申请实施例可以为网络切片增加了一个资源协同比参数的属性，并依据网络切片的资源协同比参数进行资源调配，所述资源协同比参数为一个网络切片实例允许被分享的最大资源比例。例如，假设某网络切片实例的资源协同比参数为30％时，该网络切片实例在t1时刻占用的VM个数为10个，则该网络切片实例在t1时刻允许被调配出去的VM的个数不超过10×30％＝3个，假设该网络切片实例在t1时刻被分走3个VM，那么在下一次资源调配时该网络切片实例允许被调配出去的VM的个数不超过
Figure PCTCN2016086031-appb-000005
或不超过
Figure PCTCN2016086031-appb-000006
为了在网络切片中增加所述资源协同比参数，需要扩展实例化网络切片所用到的网络切片模板的属性，即在原有的网络切片模板参数的基础上增加资源协同比参数，并且允许在创建模板之后查看和修改所述资源协同比参数在初始创建时设置的默认值。即，切片管理模块需要支持与资源协同比参数有关的增、改、查等操作，相关操作的流程如图7所示，其中在网络切片模板中增加资源协同比参数的过程可参见步骤701至步骤704：
步骤701：切片管理模块接收来自用户的用于指示创建网络切片模板的请求，所述网络切片模板包括资源协同比参数。
步骤702：切片管理模块根据所述请求创建所述网络切片模板。
创建完成之后的所述网络切片模板包括的所述资源协同比参数允许被查看和被修改。
为了安全性和保证参数的正确性，切片管理模块可以在创建所述网络切片模板之前对该用户进行认证，以及对请求中携带的参数的取值进行校验。
步骤703：切片管理模块将创建完成之后的所述网络切片模板插入到模板库中。
步骤704：完成模板创建流程之后，切片管理模块向用户返回模板创建成功确认消息。
用户修改已经创建的网络切片模板中的资源协同比参数的过程参见步骤705至步骤708：
步骤705：切片管理模块接收来自用户的用于指示更新网络切片模板的资源协同比参数的请求，该请求中携带了新的资源协同比参数的取值。
步骤706：切片管理模块根据该请求修改网络切片模板中的资源协同比参数的取值。
为了安全性和保证参数的完整性，切片管理模块可以在修改资源协同比参数之前对用户进行认证，以及对待修改的网络切片模板进行校验。
步骤707：切片管理模块完成对网络切片模板的更新后，将修改后的网络切片模板重新插入到模板库中。
步骤708：切片管理模块向用户返回参数更新成功确认消息。
用户查看已有网络切片模板的属性的过程参见步骤709至步骤711：
步骤709：切片管理模块接收来自用户的用于指示查询网络切片模板属性的请求，该请求中可以指定待查看的网络切片模板的编号，若该请求中没有指定特定的网络切片模板，则表示查询所有网络切片模板的属性。
步骤710：切片管理模块根据指定的切片模板编号从模板库中提取对应的网络切片模板；如果该请求中中没有指定网络切片模板的编号，则提取所有的网络切片模板。
为了安全性，切片管理模块可以在提取网络切片模板之前对用户进行认证。
步骤711：切片管理模块将获取到的网络切片模板的属性返回给用户，所述属性中包括资源协同比参数。
上述过程描述了对网络切片模板属性中的切片资源协同比参数的增加、修改和查询的动作，解决了资源协同比参数的配置问题，采用本实施例的步骤可以灵活地对网络切片的资源共享比例进行修改，从而为网络切片之间的资源协同提供了支撑。
在创建完携带资源协同比参数的网络切片模板之后，切片管理模块便可 以利用该网络切片模板创建网络切片实例，如利用该网络切片模板创建步骤602中的所述第一网络切片所包含的网络切片实例，创建完成之后的所述第一网络切片包含的网络切片实例的资源协同比参数值允许被查看和被修改。
实际应用中，出于成本考虑可以为网络切片实例设置一个较高的资源协同比参数，出于性能考虑可以为网络切片实例设置一个较低的资源协同比参数。为了使得网络服务的性能更加优化，在运营期间有可能需要微调资源协同比参数，其中，修改网络切片实例中的资源协同比参数的流程如图8所示，包括以下步骤：
步骤801：切片管理模块接收来自用户的用于指示修改网络切片实例中的资源协同比参数的请求，该请求中携带了需要修改的网络切片实例的标识以及新的资源协同比参数的取值。
步骤802：切片管理模块根据该请求修改指定网络切片实例中的资源协同比参数的取值。
为了安全性，切片管理模块可以在修改资源协同比参数之前对发送该请求消息的用户进行认证。
步骤803：切片管理模块向用户返回参数更新确认消息。
本申请实施例提供了修改已经实例化了的网络切片中的资源协同比参数的修改流程，解决了已经通过网络切片模板实例化了的网络切片实例的参数更新问题，可以让用户灵活地对网络切片实例的资源协同比进行更新，从而支持更灵活的协同策略配置。
如果上述步骤603中的所述第一网络切片包含的所有网络切片实例的资源协同比参数均相同，那么所述第一网络切片的资源协同比参数值可以认为是所述第一网络切片包含的任一个网络切片实例的资源协同比参数值；如果所述第一网络切片包含的网络切片实例的资源协同比参数并不完全相同，那么所述第一网络切片的资源协同比参数值可以认为是所述第一网络切片包含的所有网络切片实例的资源协同比参数值中的最小值，如某网络切片包括两个网络切片实例，这两个网络切片实例的资源协同比参数值分别是10％和 20％，那么可以将其中的较小值10％作为该网络切片的资源协同比参数值。
相应的，在所述步骤602之前，所述切片管理模块可以获取所述第一网络切片占用的总资源和所述第一网络切片的资源协同比参数值，以使得从所述第一网络切片分配给所述第二网络切片的资源不大于所述第一网络切片占用的总资源与所述第一网络切片的资源协同比参数值的乘积。其中，所述第一网络切片的资源协同比参数值为所述第一网络切片包含的所有网络切片实例的资源协同比参数值中的最小值。
在本申请的另一个实施例中，如果所述第一网络切片包含的网络切片实例的资源协同比参数并不完全相同，所述切片管理模块还可以分别获取所述第一网络切片包含的每个网络切片实例占用的总资源和每个网络切片实例的资源协同比参数值，以使得从每个网络切片实例分配给所述第二网络切片的资源不大于该网络切片实例占用的总资源与该网络切片实例的资源协同比参数值的乘积。例如，某网络切片包括网络切片实例A和网络切片实例B，网络切片实例A和网络切片实例B的资源协同比参数值分别是10％和20％，网络切片实例A和网络切片实例B占用的VM个数分别是10个和20个，那么从网络切片实例A调配出去的VM个数不能超过1个(10*10％)，从网络切片实例B调配出去的VM个数不能超过4个(20*20％)。
第二种资源调配策略：
为了令网络切片能够更好地为用户提供网络服务，所述切片管理模块可以依据网络切片的SLA指标进行资源调配，具体实现方式如下：
在所述步骤602之前，所述切片管理模块获取所述第一网络切片的SLA指标，以及获取若分配资源给所述第二网络切片之后的所述第一网络切片的预测业务指标。如果所述第一网络切片的预测业务指标不违反所述第一网络切片的SLA指标，则所述切片管理模块确定将所述第一网络切片的资源分配给所述第二网络切片；如果所述第一网络切片的预测业务指标违反所述第一网络切片的SLA指标，则所述切片管理模块确定不将所述第一网络切片的资源分配给所述第二网络切片。
例如，SLA定义了合约的最大时延，若切片管理模块预测到某网络切片如果调配一部分资源给其它网络切片后，该网络切片在未来的某一时刻的时延将超过SLA定义的最大时延，这样，预测到的业务指标违反所述第一网络切片的SLA指标，那么切片管理模块可以决定不从该网络切片调配资源。
第三种资源调配策略：
由于所述切片管理模块可能会多次执行图6所示的方法中的步骤，为了令网络切片更好地遵守SLA，同时为了减少不必要的资源调配动作，避免频繁地对某一个网络切片进行缩容或扩容的动作，例如，在某一个时间段将某一个网络切片的资源调配给了另一个网络切片，而在相邻的下一个时间段又从其它的网络切片调配资源给该网络切片；所述切片管理模块可以依据网络切片的预测独立决策结果进行资源调配。
所述预测独立决策结果为根据网络切片的预测资源指标和预测业务指标得到的网络切片在下一个时间段内有可能采用的独立决策结果。
具体实现方式如下：
在所述步骤602之前，所述切片管理模块获取所述第一网络切片的预测独立决策结果。如果所述第一网络切片的预测独立决策结果不是扩容，则所述切片管理模块确定将所述第一网络切片的资源分配给所述第二网络切片；如果所述第一网络切片的预测独立决策结果是扩容，则所述切片管理模块确定不将所述第一网络切片的资源分配给所述第二网络切片。
在步骤602之后，所述切片管理模块可以将所述多个网络切片分别对应的最终决策结果返回给各个网络切片，返回的消息中可以包含用于指示最终决策结果的代号，如用0表示保持当前实例数不变，用1表示该网络切片需要被动缩容，用2表示该网络切片需要被动扩容，如果最终决策结果是扩容或缩容，则返回的消息中还要携带扩容的实例数以及缩容的实例数。
在步骤603中，所述切片管理模块还需要将所述最终决策结果发送给VIM，由所述VIM执行所述最终决策结果。
由于所述切片管理模块可以部署在VNFM、NFVO或OSS/BSS内，根据 所述切片管理模块不同的部署方式，所述最终决策结果可以有以下几种途径由所述切片管理模块发往所述VIM：
若所述切片管理模块部署在VNFM内，则所述切片管理模块可以通过所述VNFM与所述VIM之间的接口将所述最终决策结果发送给所述VIM，如图9中的途径1；或所述切片管理模块可以通过所述VNFM与NFVO之间的接口将所述最终决策结果发送给所述NFVO，再由所述NFVO通过所述NFVO与所述VIM之间的接口将所述最终决策结果转发给所述VIM，如图9中的途径2；或所述切片管理模块可以将所述最终决策结果发送给所述OSS/BSS，由所述OSS/BSS通过所述OSS/BSS与NFVO之间的接口将所述最终决策结果发送给所述NFVO，再由所述NFVO通过所述NFVO与所述VIM之间的接口将所述最终决策结果发送给所述VIM，如图9中的途径3。
若所述切片管理模块部署在NFVO内，则所述切片管理模块可以通过所述NFVO与所述VIM之间的接口将所述最终决策结果发送给所述VIM，如图10中的途径4；或所述切片管理模块可以通过所述NFVO与VNFM之间的接口将所述最终决策结果发送给所述VNFM，再由所述VNFM通过所述VNFM与所述VIM之间的接口将所述最终决策结果发送给所述VIM，如图10中的途径5。
若所述切片管理模块部署在OSS/BSS内，则所述切片管理模块可以通过所述OSS/BSS与NFVO之间的接口将所述最终决策结果发送给所述NFVO，再由所述NFVO通过所述NFVO与所述VIM之间的接口将所述最终决策结果转发给所述VIM，如图11中的途径6。
为了更清楚地说明本申请的技术方案，本实施例以3个网络切片为例，通过这3个网络切片的负载变化以及这3个网络切片包含的实例数的变化，说明一种最简单的网络切片之间的资源调配方法。需要说明的是，这个实施例仅仅是本申请的一种实现方式，不构成对本申请的限定。
如图12所示，初始状态时(例如，图12中的0-45秒)，eMBB网络切片和高可靠机器类通信(Ultra-reliable MTC，简称：uMTC)网络切片均处于轻 载状态，但由于未达到缩容阈值，不会触发缩容动作；mMTC网络切片会周期性地出现突发性负载，分别是图12中的B1，B2，B4，B5四个位置，uMTC网络切片在B3位置会出现一个突发性负载。
切片管理模块基于这三个网络切片的状态进行以下决策：
在图12中的B1位置，mMTC网络切片的独立决策结果是扩容，此时uMTC网络切片处于轻载状态，切片管理模块的最终决策结果是对uMTC网络切片进行被动缩容，从uMTC网络切片调配出2个VM供mMTC网络切片使用；在图12中的B1和B2的位置之间，当mMTC网络切片的负载处于下降趋势时，切片管理模块对mMTC网络切片进行缩容，并从mMTC网络切片调配出2个VM返回给uMTC网络切片。
类似的，在图12中的B2位置mMTC网络切片的负载突发程度更高，需要一次增加多个实例，此时切片管理模块有两种选择，一是从eMBB网络切片调配资源，二是从uMTC网络切片调配资源。切片管理模块结合预测算法，对eMBB网络切片和uMTC网络切片的负载变化趋势进行预测，预测结果表明uMTC网络切片的负载会在B3位置处发生变化，如果从uMTC网络切片调配资源，则该uMTC网络切片会在B3位置因负载量过大导致违反uMTC网络切片的SLA指标，因此最终决策结果是从eMBB网络切片处调配出4个VM给mMTC网络切片。
图12中的B4和B5位置处的最终决策结果与B1和B2位置处的最终决策结果类似，此处不再赘述。
基于本申请上述提供的网络切片的资源管理方法，本申请还提供一种网络切片的资源管理装置，如图13所示，所述网络切片的资源管理装置包括获取单元131、确定单元132和发送单元133。
所述获取单元131，用于分别获取多个网络切片的独立决策结果，其中，所述独立决策结果包括扩容、缩容或保持实例数不变。
所述确定单元132，若所述多个网络切片的独立决策结果不完全一致，则用于所根据所述多个网络切片的独立决策结果为每个网络切片分别确定最终 决策结果。
所述发送单元133，用于将所述最终决策结果发送给VIM，所述最终决策结果用于指示将所述多个网络切片中的第一网络切片的资源调配给所述多个网络切片中的第二网络切片；其中，所述第一网络切片的独立决策结果为缩容，所述第二网络切片的独立决策结果为保持实例数不变或扩容；或，所述第一网络切片的独立决策结果为保持实例数不变，所述第二网络切片的独立决策结果为扩容。
可选的，所述装置还可以包括：
接收单元，用于在所述获取单元131获取多个网络切片的独立决策结果之前，接收用于指示创建网络切片模板的请求，所述网络切片模板包括资源协同比参数，所述资源协同比参数为网络切片实例允许被分享的最大资源比例。
模板创建单元，用于根据所述请求创建所述网络切片模板。
实例创建单元，用于根据所述网络切片模板创建所述第一网络切片包含的网络切片实例。
可选的，在所述确定单元132根据所述多个网络切片的独立决策结果为每个网络切片分别确定最终决策结果之前，所述获取单元131还可以用于：获取所述第一网络切片占用的总资源和所述第一网络切片的资源协同比参数值，以使得所述确定单元132确定从所述第一网络切片调配给所述第二网络切片的资源不大于所述第一网络切片占用的总资源与所述第一网络切片的资源协同比参数值的乘积；其中，所述第一网络切片的资源协同比参数值为所述第一网络切片包含的所有网络切片实例的资源协同比参数值中的最小值。
可选的，在所述确定单元132根据所述多个网络切片的独立决策结果为每个网络切片分别确定最终决策结果之前，所述获取单元131还可以用于：获取所述第一网络切片的服务水平协议SLA指标；以及，获取若分配资源给所述第二网络切片之后的所述第一网络切片的预测业务指标。
相应的，所述确定单元132在为每个网络切片分别确定最终决策结果之 前，还用于：确定所述第一网络切片的预测业务指标不违反所述第一网络切片的SLA指标。
可选的，在所述确定单元132根据所述多个网络切片的独立决策结果为每个网络切片分别确定最终决策结果之前，所述获取单元131还可以用于：获取所述第一网络切片的预测独立决策结果。
相应的，所述确定单元132具体用于：如果所述第一网络切片的预测独立决策结果不是扩容，则确定将所述第一网络切片的资源调配给所述第二网络切片；如果所述第一网络切片的预测独立决策结果是扩容，则确定不将所述第一网络切片的资源调配给所述第二网络切片。
可选的，所述获取单元131在获取多个网络切片的独立决策结果时，具体用于：接收所述多个网络切片中的每个网络切片分别发送的的独立决策结果；或，接收所述多个网络切片中的每个网络切片分别发送的的业务指标和资源指标，并根据每个网络切片的业务指标和资源指标分别确定每个网络切片的独立决策结果。
可选的，所述装置可以部署在VNFM内；或，所述装置可以部署在NFVO内；或，所述装置可以部署在OSS/BSS内。
可选的，若所述装置部署在VNFM内，则所述发送单元133通过所述VNFM与所述VIM之间的接口将所述最终决策结果发送给所述VIM；或所述发送单元133通过所述VNFM与NFVO之间的接口将所述最终决策结果发送给所述NFVO，再由所述NFVO通过所述NFVO与所述VIM之间的接口将所述最终决策结果转发给所述VIM；或所述发送单元133将所述最终决策结果发送给所述OSS/BSS，由所述OSS/BSS通过所述OSS/BSS与NFVO之间的接口将所述最终决策结果发送给所述NFVO，再由所述NFVO通过所述NFVO与所述VIM之间的接口将所述最终决策结果发送给所述VIM。
可选的，若所述装置部署在NFVO内，则所述发送单元133通过所述NFVO与所述VIM之间的接口将所述最终决策结果发送给所述VIM；或所述发送单元133通过所述NFVO与VNFM之间的接口将所述最终决策结果发送 给所述VNFM，再由所述VNFM通过所述VNFM与所述VIM之间的接口将所述最终决策结果发送给所述VIM。
可选的，若所述装置部署在OSS/BSS内，则所述发送单元133通过所述OSS/BSS与NFVO之间的接口将所述最终决策结果发送给所述NFVO，再由所述NFVO通过所述NFVO与所述VIM之间的接口将所述最终决策结果转发给所述VIM。
本实施例中未尽之细节可参考上述图6所示方法中对切片管理模块的描述，在此不再赘述。
需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。在本申请的实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
基于上述提供的网络切片的资源管理方法，本申请还提供一种网络切片的资源管理装置，如图14所示，所述装置包括网络接口141和处理器142，例如，所述网络接口141和所述处理器142通过总线143相互连接。
所述处理器142用于执行以下操作：
分别获取多个网络切片的独立决策结果，其中，所述独立决策结果包括扩容、缩容或保持实例数不变；若所述多个网络切片的独立决策结果不完全一致，则所根据所述多个网络切片的独立决策结果为每个网络切片分别确定最终决策结果；通过所述网络接口141将所述最终决策结果发送给VIM，所述最终决策结果用于指示将所述多个网络切片中的第一网络切片的资源调配给所述多个网络切片中的第二网络切片；其中，所述第一网络切片的独立决策结果为缩容，所述第二网络切片的独立决策结果为保持实例数不变或扩容；或，所述第一网络切片的独立决策结果为保持实例数不变，所述第二网络切片的独立决策结果为扩容。
所述网络接口141可以是有线接口，例如光纤分布式数据接口(英文： Fiber Distributed Data Interface，简称：FDDI)、以太网(英文：Ethernet)接口。网络接口1101也可以是无线接口，例如无线局域网接口。
所述处理器142可以是通用处理器，包括中央处理器(英文：central processing unit，简称：CPU)、网络处理器(英文：network processor，简称：NP)等；还可以是数字信号处理器(英文：figital signal processor，简称：DSP)、专用集成电路(英文：application-specific integrated circuit，简称：ASIC)、现场可编程门阵列(英文：field－programmable gate array，简称：FPGA)或者其他可编程逻辑器件等。
所述处理器142为CPU时，所述装置还可以包括：存储器，用于存储程序。具体地，程序可以包括程序代码，所述程序代码包括计算机操作指令。存储器可能包含随机存取存储器(英文：random access memory，简称：RAM)，也可能还包括非易失性存储器(英文：non-volatile memory)，例如至少一个磁盘存储器。所述处理器142执行所述存储器中存储的程序代码，实现上述功能。
综上所述，本申请提供的技术方案，利用网络切片之间负载高低交错的特征对资源进行更合理的调配，使得独立决策结果为扩容的网络切片可以从独立决策结果为缩容或保持实例数不变的其它网络切片协调资源，也可以使独立决策结果为保持实例数不变的网络切片从独立决策结果为缩容的其它网络切片协调资源，从而使得需要增加容量的网络切片无需向基础设施请求新的资源，提高了基础设施资源的利用率，同时降低了切片租户的资源采购成本。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产 品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本发明的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本发明范围的所有变更和修改。
显然，本领域的技术人员可以对本发明实施例进行各种改动和变型而不脱离本发明实施例的精神和范围。这样，倘若本发明实施例的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (16)

  1. 一种网络切片的资源管理方法，其特征在于，包括：
    切片管理模块分别获取多个网络切片的独立决策结果，其中，所述独立决策结果包括扩容、缩容或保持实例数不变；
    若所述多个网络切片的独立决策结果不完全一致，则所述切片管理模块根据所述多个网络切片的独立决策结果为每个网络切片分别确定最终决策结果；
    所述切片管理模块将所述最终决策结果发送给虚拟基础设施管理器VIM，所述最终决策结果用于指示将所述多个网络切片中的第一网络切片的资源调配给所述多个网络切片中的第二网络切片；
    其中，所述第一网络切片的独立决策结果为缩容，所述第二网络切片的独立决策结果为保持实例数不变或扩容；或，所述第一网络切片的独立决策结果为保持实例数不变，所述第二网络切片的独立决策结果为扩容。
  2. 如权利要求1所述的方法，其特征在于，在所述切片管理模块获取多个网络切片的独立决策结果之前，所述方法还包括：
    所述切片管理模块接收用于指示创建网络切片模板的请求，所述网络切片模板包括资源协同比参数，所述资源协同比参数为网络切片实例允许被分享的最大资源比例；
    所述切片管理模块根据所述请求创建所述网络切片模板；
    所述切片管理模块根据所述网络切片模板创建所述第一网络切片包含的网络切片实例。
  3. 如权利要求2所述的方法，其特征在于，在所述切片管理模块根据所述多个网络切片的独立决策结果为每个网络切片分别确定最终决策结果之前，所述方法还包括：
    所述切片管理模块获取所述第一网络切片占用的总资源和所述第一网络切片的资源协同比参数值，以使得从所述第一网络切片调配给所述第二网络 切片的资源不大于所述第一网络切片占用的总资源与所述第一网络切片的资源协同比参数值的乘积；
    其中，所述第一网络切片的资源协同比参数值为所述第一网络切片包含的所有网络切片实例的资源协同比参数值中的最小值。
  4. 如权利要求1-3中任一项所述的方法，其特征在于，在所述切片管理模块根据所述多个网络切片的独立决策结果为每个网络切片分别确定最终决策结果之前，所述方法还包括：
    所述切片管理模块获取所述第一网络切片的服务水平协议SLA指标；
    所述切片管理模块获取若分配资源给所述第二网络切片之后的所述第一网络切片的预测业务指标；
    所述切片管理模块确定所述第一网络切片的预测业务指标不违反所述第一网络切片的SLA指标。
  5. 如权利要求1-4中任一项所述的方法，其特征在于，所述切片管理模块根据所述多个网络切片的独立决策结果为每个网络切片分别确定最终决策结果，包括：
    所述切片管理模块获取所述第一网络切片的预测独立决策结果；
    如果所述第一网络切片的预测独立决策结果不是扩容，则所述切片管理模块确定将所述第一网络切片的资源调配给所述第二网络切片；
    如果所述第一网络切片的预测独立决策结果是扩容，则所述切片管理模块确定不将所述第一网络切片的资源调配给所述第二网络切片。
  6. 如权利要求1-5中任一项所述的方法，其特征在于，
    所述切片管理模块部署在虚拟网络功能管理器VNFM内；或
    所述切片管理模块部署在网络功能虚拟化编排器NFVO内；或
    所述切片管理模块部署在运营支撑系统OSS/业务支撑系统BSS内。
  7. 如权利要求1-6中任一项所述的方法，其特征在于，所述切片管理模块获取多个网络切片的独立决策结果，包括：
    所述切片管理模块接收所述多个网络切片中的每个网络切片分别发送的 的独立决策结果；或
    所述切片管理模块接收所述多个网络切片中的每个网络切片分别发送的的业务指标和资源指标，并根据每个网络切片的业务指标和资源指标分别确定每个网络切片的独立决策结果。
  8. 如权利要求1-7中任一所述的方法，其特征在于，若所述切片管理模块部署在VNFM内，则所述切片管理模块通过所述VNFM与所述VIM之间的接口将所述最终决策结果发送给所述VIM；或所述切片管理模块通过所述VNFM与NFVO之间的接口将所述最终决策结果发送给所述NFVO，再由所述NFVO通过所述NFVO与所述VIM之间的接口将所述最终决策结果转发给所述VIM；或所述切片管理模块将所述最终决策结果发送给所述OSS/BSS，由所述OSS/BSS通过所述OSS/BSS与NFVO之间的接口将所述最终决策结果发送给所述NFVO，再由所述NFVO通过所述NFVO与所述VIM之间的接口将所述最终决策结果发送给所述VIM；
    若所述切片管理模块部署在NFVO内，则所述切片管理模块通过所述NFVO与所述VIM之间的接口将所述最终决策结果发送给所述VIM；或所述切片管理模块通过所述NFVO与VNFM之间的接口将所述最终决策结果发送给所述VNFM，再由所述VNFM通过所述VNFM与所述VIM之间的接口将所述最终决策结果发送给所述VIM；
    若所述切片管理模块部署在OSS/BSS内，则所述切片管理模块通过所述OSS/BSS与NFVO之间的接口将所述最终决策结果发送给所述NFVO，再由所述NFVO通过所述NFVO与所述VIM之间的接口将所述最终决策结果转发给所述VIM。
  9. 一种网络切片的资源管理装置，其特征在于，包括：
    获取单元，用于分别获取多个网络切片的独立决策结果，其中，所述独立决策结果包括扩容、缩容或保持实例数不变；
    确定单元，若所述多个网络切片的独立决策结果不完全一致，则用于所根据所述多个网络切片的独立决策结果为每个网络切片分别确定最终决策结 果；
    发送单元，用于将所述最终决策结果发送给虚拟基础设施管理器VIM，所述最终决策结果用于指示将所述多个网络切片中的第一网络切片的资源调配给所述多个网络切片中的第二网络切片；
    其中，所述第一网络切片的独立决策结果为缩容，所述第二网络切片的独立决策结果为保持实例数不变或扩容；或，所述第一网络切片的独立决策结果为保持实例数不变，所述第二网络切片的独立决策结果为扩容。
  10. 如权利要求9所述的装置，其特征在于，所述装置还包括：
    接收单元，用于在所述获取单元获取多个网络切片的独立决策结果之前，接收用于指示创建网络切片模板的请求，所述网络切片模板包括资源协同比参数，所述资源协同比参数为网络切片实例允许被分享的最大资源比例；
    模板创建单元，用于根据所述请求创建所述网络切片模板；
    实例创建单元，用于根据所述网络切片模板创建所述第一网络切片包含的网络切片实例。
  11. 如权利要求10所述的装置，其特征在于，在所述确定单元根据所述多个网络切片的独立决策结果为每个网络切片分别确定最终决策结果之前，所述获取单元还用于：
    获取所述第一网络切片占用的总资源和所述第一网络切片的资源协同比参数值，以使得所述确定单元确定从所述第一网络切片调配给所述第二网络切片的资源不大于所述第一网络切片占用的总资源与所述第一网络切片的资源协同比参数值的乘积；
    其中，所述第一网络切片的资源协同比参数值为所述第一网络切片包含的所有网络切片实例的资源协同比参数值中的最小值。
  12. 如权利要求9-11中任一项所述的装置，其特征在于，在所述确定单元根据所述多个网络切片的独立决策结果为每个网络切片分别确定最终决策结果之前，所述获取单元还用于：
    获取所述第一网络切片的服务水平协议SLA指标；
    获取若分配资源给所述第二网络切片之后的所述第一网络切片的预测业务指标；
    所述确定单元在为每个网络切片分别确定最终决策结果之前，还用于：
    确定所述第一网络切片的预测业务指标不违反所述第一网络切片的SLA指标。
  13. 如权利要求9-12中任一项所述的装置，其特征在于，在所述确定单元根据所述多个网络切片的独立决策结果为每个网络切片分别确定最终决策结果之前，所述获取单元还用于：
    获取所述第一网络切片的预测独立决策结果；
    所述确定单元具体用于：
    如果所述第一网络切片的预测独立决策结果不是扩容，则确定将所述第一网络切片的资源调配给所述第二网络切片；
    如果所述第一网络切片的预测独立决策结果是扩容，则确定不将所述第一网络切片的资源调配给所述第二网络切片。
  14. 如权利要求9-13中任一项所述的装置，其特征在于，
    所述装置部署在虚拟网络功能管理器VNFM内；或
    所述装置部署在网络功能虚拟化编排器NFVO内；或
    所述装置部署在运营支撑系统OSS/业务支撑系统BSS内。
  15. 如权利要求9-14中任一项所述的装置，其特征在于，所述获取单元在获取多个网络切片的独立决策结果时，具体用于：
    接收所述多个网络切片中的每个网络切片分别发送的的独立决策结果；或
    接收所述多个网络切片中的每个网络切片分别发送的的业务指标和资源指标，并根据每个网络切片的业务指标和资源指标分别确定每个网络切片的独立决策结果。
  16. 如权利要求9-15中任一所述的装置，其特征在于，若所述装置部署在VNFM内，则所述发送单元通过所述VNFM与所述VIM之间的接口将所 述最终决策结果发送给所述VIM；或所述发送单元通过所述VNFM与NFVO之间的接口将所述最终决策结果发送给所述NFVO，再由所述NFVO通过所述NFVO与所述VIM之间的接口将所述最终决策结果转发给所述VIM；或所述发送单元将所述最终决策结果发送给所述OSS/BSS，由所述OSS/BSS通过所述OSS/BSS与NFVO之间的接口将所述最终决策结果发送给所述NFVO，再由所述NFVO通过所述NFVO与所述VIM之间的接口将所述最终决策结果发送给所述VIM；
    若所述装置部署在NFVO内，则所述发送单元通过所述NFVO与所述VIM之间的接口将所述最终决策结果发送给所述VIM；或所述发送单元通过所述NFVO与VNFM之间的接口将所述最终决策结果发送给所述VNFM，再由所述VNFM通过所述VNFM与所述VIM之间的接口将所述最终决策结果发送给所述VIM；
    若所述装置部署在OSS/BSS内，则所述发送单元通过所述OSS/BSS与NFVO之间的接口将所述最终决策结果发送给所述NFVO，再由所述NFVO通过所述NFVO与所述VIM之间的接口将所述最终决策结果转发给所述VIM。
PCT/CN2016/086031 2016-06-16 2016-06-16 一种网络切片的资源管理方法和装置 WO2017214932A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP16905047.3A EP3461087B1 (en) 2016-06-16 2016-06-16 Network-slice resource management method and apparatus
PCT/CN2016/086031 WO2017214932A1 (zh) 2016-06-16 2016-06-16 一种网络切片的资源管理方法和装置
BR112018076166A BR112018076166A2 (pt) 2016-06-16 2016-06-16 método e aparelho de gerenciamento de recursos de fatia da rede
CN201680086181.1A CN109196828A (zh) 2016-06-16 2016-06-16 一种网络切片的资源管理方法和装置
US16/220,612 US20190123963A1 (en) 2016-06-16 2018-12-14 Method and apparatus for managing resources of network slice

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/086031 WO2017214932A1 (zh) 2016-06-16 2016-06-16 一种网络切片的资源管理方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/220,612 Continuation US20190123963A1 (en) 2016-06-16 2018-12-14 Method and apparatus for managing resources of network slice

Publications (1)

Publication Number Publication Date
WO2017214932A1 true WO2017214932A1 (zh) 2017-12-21

Family

ID=60663060

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/086031 WO2017214932A1 (zh) 2016-06-16 2016-06-16 一种网络切片的资源管理方法和装置

Country Status (5)

Country Link
US (1) US20190123963A1 (zh)
EP (1) EP3461087B1 (zh)
CN (1) CN109196828A (zh)
BR (1) BR112018076166A2 (zh)
WO (1) WO2017214932A1 (zh)

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2577525A (en) * 2018-09-27 2020-04-01 British Telecomm Network slice management
WO2020087948A1 (zh) * 2018-10-31 2020-05-07 中兴通讯股份有限公司 网络切片模板生成方法、装置、设备及存储介质
US10728954B2 (en) 2018-08-07 2020-07-28 At&T Intellectual Property I, L.P. Automated network design and traffic steering
CN112703774A (zh) * 2018-09-27 2021-04-23 英国电讯有限公司 网络切片管理
EP3729728A4 (en) * 2017-12-22 2021-07-07 Nokia Technologies Oy VIRTUAL NETWORK FUNCTION MANAGEMENT
CN113612635A (zh) * 2021-07-29 2021-11-05 西安电子科技大学 基于水平/垂直伸缩结合的网络切片实例资源分配方法
CN114079976A (zh) * 2020-08-03 2022-02-22 中国电信股份有限公司 切片资源调度方法、装置、系统和计算机可读存储介质
US20230017152A1 (en) * 2021-07-14 2023-01-19 Canon Kabushiki Kaisha Communication apparatus, communication method, and storage medium
US11811640B1 (en) * 2022-07-22 2023-11-07 Dell Products L.P. Method and system for modifying a communication network
US11882004B1 (en) 2022-07-22 2024-01-23 Dell Products L.P. Method and system for adaptive health driven network slicing based data migration
US12009975B2 (en) 2022-07-22 2024-06-11 Dell Products L.P. Method and system for generating an upgrade recommendation for a communication network
US12141571B2 (en) 2022-07-22 2024-11-12 Dell Products, L.P. Method and system for executing an application upgrade using network slicing

Families Citing this family (55)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11240660B2 (en) * 2016-09-18 2022-02-01 Alcatel Lucent Unified security architecture
EP3616468A4 (en) * 2017-04-27 2020-11-18 Intel IP Corporation IMPROVED NETWORK TRENCH MANAGEMENT FOR WIRELESS COMMUNICATIONS
US11051210B2 (en) * 2017-04-28 2021-06-29 NEC Laboratories Europe GmbH Method and system for network slice allocation
CN110679179B (zh) * 2017-06-02 2021-10-29 鸿颖创新有限公司 用于服务驱动的移动性管理的方法、装置及系统
CN109219090B (zh) * 2017-06-30 2022-11-08 中兴通讯股份有限公司 商务特性数据上报方法及装置、网络切片编排方法及装置
CN113300877B (zh) * 2017-09-27 2022-07-22 华为技术有限公司 一种网络切片管理方法及设备
CN110650029B (zh) * 2018-06-26 2021-05-18 华为技术有限公司 一种配置方法及装置
CN111126737B (zh) * 2018-11-01 2022-09-13 百度在线网络技术（北京）有限公司 跨场景的交叉分析方法、装置、电子设备及存储介质
US10834669B2 (en) 2019-02-22 2020-11-10 Vmware, Inc. Stateful network slice selection using replay of connection handshake
US10939369B2 (en) 2019-02-22 2021-03-02 Vmware, Inc. Retrieval of slice selection state for mobile device connection
US11146964B2 (en) 2019-02-22 2021-10-12 Vmware, Inc. Hierarchical network slice selection
US11246087B2 (en) 2019-02-22 2022-02-08 Vmware, Inc. Stateful network slice selection using slice selector as connection termination proxy
US11483762B2 (en) 2019-02-22 2022-10-25 Vmware, Inc. Virtual service networks
US11024144B2 (en) 2019-02-22 2021-06-01 Vmware, Inc. Redirecting traffic from mobile device to initial slice selector for connection
EP3967078A1 (en) * 2019-05-10 2022-03-16 Nokia Technologies Oy Apparatus, method, and computer program
WO2020256605A1 (en) * 2019-06-19 2020-12-24 Telefonaktiebolaget Lm Ericsson (Publ) Evaluating overall network resource congestion before scaling a network slice
JP7252854B2 (ja) 2019-07-29 2023-04-05 Kddi株式会社 制御装置、制御方法及びプログラム
KR102615191B1 (ko) * 2019-07-29 2023-12-19 케이디디아이 가부시키가이샤 제어 장치, 제어 방법 및 프로그램
US11178016B2 (en) 2019-08-26 2021-11-16 Vmware, Inc. Performing slice based operations in a data plane circuit
WO2021038335A1 (en) * 2019-08-30 2021-03-04 Telefonaktiebolaget Lm Ericsson (Publ) Method for onboarding a network function package in onap
CN114365459B (zh) * 2019-09-18 2024-05-14 三菱电机株式会社 网络控制装置、通信资源分配方法以及通信系统
EP4035451A4 (en) * 2019-09-25 2022-09-21 Telefonaktiebolaget LM Ericsson (publ) FIRST NODE, FOURTH NODE AND METHODS IMPLEMENTED USING THESE NODES FOR MANAGING THE SIZING OF A NETWORK SLICE IN A COMMUNICATIONS NETWORK
WO2021062873A1 (zh) * 2019-10-03 2021-04-08 华为技术有限公司 一种无线资源分配策略的配置方法、装置及系统
FR3102027B1 (fr) * 2019-10-10 2021-09-24 Commissariat Energie Atomique Procédé d’optimisation de la quantité de ressources réseau et du nombre de services susceptibles d’utiliser lesdites ressources
CN112751685B (zh) * 2019-10-29 2023-04-07 中国电信股份有限公司 网络切片用户面容量配置方法、装置和系统
CN110831038B (zh) * 2019-11-06 2022-07-12 中国联合网络通信集团有限公司 网络切片资源调度方法及装置
US11336538B2 (en) 2019-11-27 2022-05-17 Netsia, Inc. Slice assurance within a mobile network
US11310104B2 (en) * 2019-12-02 2022-04-19 At&T Intellectual Property I, L.P. Management of persistent network slices by a distributed learning system in a 5G or other next generation wireless network
US11510138B2 (en) * 2020-01-03 2022-11-22 Apple Inc. Network slice quota management
US11576109B2 (en) * 2020-02-28 2023-02-07 At&T Intellectual Property I, L.P. Modifying capacity assigned to support a network slice allocated to a user device in a 5G or other next generation wireless network
US11283869B2 (en) * 2020-03-25 2022-03-22 International Business Machines Corporation Data governance in a dispersed storage network using bucket templates
JP6945089B1 (ja) * 2020-03-31 2021-10-06 ノキア ソリューションズ アンド ネットワークス オサケ ユキチュアＮｏｋｉａ Ｓｏｌｕｔｉｏｎｓ ａｎｄ Ｎｅｔｗｏｒｋｓ Ｏｙ ネットワークスライス構成
US11444851B2 (en) * 2020-04-13 2022-09-13 Verizon Patent And Licensing Inc. Systems and methods of using adaptive network infrastructures
CN111555911B (zh) * 2020-04-23 2022-09-30 北京思特奇信息技术股份有限公司 一种基于产品服务模板的5g网络切片产品快速设计方法
KR20210131545A (ko) 2020-04-24 2021-11-03 삼성전자주식회사 네트워크 슬라이스 자원 할당 및 시각화 방법
CN111565120B (zh) * 2020-04-27 2022-08-16 北京思特奇信息技术股份有限公司 一种5g网络切片产品配置方法、系统及电子设备
CN113676903B (zh) * 2020-04-30 2023-03-10 华为技术有限公司 切片认证授权管理方法、装置和系统
US11696184B2 (en) * 2020-05-06 2023-07-04 Accenture Global Solutions Limited Quality of service manager for network slices of a network
US11323389B2 (en) * 2020-06-26 2022-05-03 Sap Se Logic scaling sets for cloud-like elasticity of legacy enterprise applications
CN113965475B (zh) * 2020-07-02 2023-09-05 中国移动通信集团设计院有限公司 网络切片工程验收方法及系统
CN114095382B (zh) * 2020-08-05 2023-11-10 中国移动通信集团重庆有限公司 一种网络切片虚拟资源调度方法、系统、装置及设备
FI129325B (en) * 2020-08-28 2021-11-30 Nokia Solutions & Networks Oy Control mechanism for overload
CN114430380B (zh) * 2020-10-15 2023-11-24 中国移动通信集团浙江有限公司 切片容灾池分级方法、装置和设备
CN112492621B (zh) * 2020-10-29 2022-12-23 苏州浪潮智能科技有限公司 一种基于5g核心网络动态切片的方法、系统、设备及介质
TWI740713B (zh) * 2020-11-11 2021-09-21 財團法人工業技術研究院 網路切片的資源管理方法、資源管理系統及工作負載調度裝置
US20220286914A1 (en) 2021-03-05 2022-09-08 Vmware, Inc. Ric sdk
US11836551B2 (en) 2021-03-05 2023-12-05 Vmware, Inc. Active and standby RICs
CN113556761B (zh) * 2021-06-25 2024-03-22 中国联合网络通信集团有限公司 切片资源调整方法、系统、终端设备及存储介质
US11690004B2 (en) 2021-06-29 2023-06-27 Dish Wireless L.L.C. Network slice assignment control systems and methods
US12075337B2 (en) 2021-12-17 2024-08-27 Juniper Networks, Inc. Radio access network tracking area visualization management and monitoring
CN114978277B (zh) * 2022-04-24 2023-06-27 北京邮电大学 一种基于网络切片的非地面网络中跨域资源分配方法
CN114641041B (zh) * 2022-05-18 2022-09-13 之江实验室 一种面向边缘智能的车联网切片方法及装置
US20240205068A1 (en) 2022-12-19 2024-06-20 VMware LLC Using generic key-value pairs to configure ran component attributes in a ran system
CN116528255B (zh) * 2023-06-29 2023-10-10 中国电信股份有限公司 网络切片迁移方法、装置、设备及存储介质
CN117009076B (zh) * 2023-07-04 2024-10-18 中科南京移动通信与计算创新研究院 网元的资源处理方法、装置、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104954220A (zh) * 2014-03-31 2015-09-30 华为技术有限公司 一种虚拟网络业务部署方法和设备
CN105429780A (zh) * 2015-10-30 2016-03-23 南京优速网络科技有限公司 一种虚拟化网络服务业务自动生成和动态监控的方法
WO2016048430A1 (en) * 2014-09-25 2016-03-31 Intel IP Corporation Network functions virtualization
CN105468435A (zh) * 2015-12-25 2016-04-06 赛特斯信息科技股份有限公司 Nfv动态资源分配方法

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
PL2223556T3 (pl) * 2007-12-05 2016-10-31 Przydzielanie zasobów operatorom widma współdzielonego
CN105577499B (zh) * 2014-10-10 2019-05-28 华为技术有限公司 决策协调方法、执行装置和决策协调器
US20160119166A1 (en) * 2014-10-28 2016-04-28 Electronics And Telecommunications Research Institute Method and apparatus for providing gateway function
CN104601492B (zh) * 2014-12-29 2018-11-09 上海华为技术有限公司 一种nfv架构下进行业务流控的方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104954220A (zh) * 2014-03-31 2015-09-30 华为技术有限公司 一种虚拟网络业务部署方法和设备
WO2016048430A1 (en) * 2014-09-25 2016-03-31 Intel IP Corporation Network functions virtualization
CN105429780A (zh) * 2015-10-30 2016-03-23 南京优速网络科技有限公司 一种虚拟化网络服务业务自动生成和动态监控的方法
CN105468435A (zh) * 2015-12-25 2016-04-06 赛特斯信息科技股份有限公司 Nfv动态资源分配方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3461087A4 *

Cited By (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3729728A4 (en) * 2017-12-22 2021-07-07 Nokia Technologies Oy VIRTUAL NETWORK FUNCTION MANAGEMENT
US11582049B2 (en) 2017-12-22 2023-02-14 Nokia Technologies Oy Virtual network function management
US10728954B2 (en) 2018-08-07 2020-07-28 At&T Intellectual Property I, L.P. Automated network design and traffic steering
US11076451B2 (en) 2018-08-07 2021-07-27 At&T Intellectual Property I, L.P. Automated network design and traffic steering
EP3857970A1 (en) * 2018-09-27 2021-08-04 British Telecommunications public limited company Network slice management
CN112703774A (zh) * 2018-09-27 2021-04-23 英国电讯有限公司 网络切片管理
CN112703774B (zh) * 2018-09-27 2024-02-20 英国电讯有限公司 管理电信网络中的处理资源的方法和电信网络及存储介质
GB2577525B (en) * 2018-09-27 2021-11-24 British Telecomm Network slice management
GB2577525A (en) * 2018-09-27 2020-04-01 British Telecomm Network slice management
US11665635B2 (en) 2018-09-27 2023-05-30 British Telecommunications Public Limited Company Network slice management
WO2020087948A1 (zh) * 2018-10-31 2020-05-07 中兴通讯股份有限公司 网络切片模板生成方法、装置、设备及存储介质
CN114079976B (zh) * 2020-08-03 2024-03-05 中国电信股份有限公司 切片资源调度方法、装置、系统和计算机可读存储介质
CN114079976A (zh) * 2020-08-03 2022-02-22 中国电信股份有限公司 切片资源调度方法、装置、系统和计算机可读存储介质
US20230017152A1 (en) * 2021-07-14 2023-01-19 Canon Kabushiki Kaisha Communication apparatus, communication method, and storage medium
CN113612635B (zh) * 2021-07-29 2022-08-12 西安电子科技大学 基于水平和垂直伸缩结合的网络切片实例资源分配方法
CN113612635A (zh) * 2021-07-29 2021-11-05 西安电子科技大学 基于水平/垂直伸缩结合的网络切片实例资源分配方法
US11882004B1 (en) 2022-07-22 2024-01-23 Dell Products L.P. Method and system for adaptive health driven network slicing based data migration
US11811640B1 (en) * 2022-07-22 2023-11-07 Dell Products L.P. Method and system for modifying a communication network
US12009975B2 (en) 2022-07-22 2024-06-11 Dell Products L.P. Method and system for generating an upgrade recommendation for a communication network
US12141571B2 (en) 2022-07-22 2024-11-12 Dell Products, L.P. Method and system for executing an application upgrade using network slicing

Also Published As

Publication number Publication date
EP3461087A4 (en) 2019-04-24
US20190123963A1 (en) 2019-04-25
BR112018076166A2 (pt) 2019-03-26
CN109196828A (zh) 2019-01-11
EP3461087A1 (en) 2019-03-27
EP3461087B1 (en) 2020-10-21

Similar Documents

Publication Publication Date Title
WO2017214932A1 (zh) 一种网络切片的资源管理方法和装置
CN105979007B (zh) 加速资源处理方法、装置及网络功能虚拟化系统
US10567196B2 (en) Decision coordination method, execution apparatus, and decision coordinator
CN108370328B (zh) 一种nfv mano策略描述符的管理方法及装置
US10924966B2 (en) Management method, management unit, and system
US9465641B2 (en) Selecting cloud computing resource based on fault tolerance and network efficiency
CN110311798B (zh) 一种管理虚拟资源的方法及装置
US11088924B2 (en) Network management method, device, and system
WO2019029267A1 (zh) 网络切片的管理方法和装置
CN108132827B (zh) 一种网络切片资源映射方法、相关设备及系统
WO2018082477A1 (zh) 用于管理网络切片实例的方法和装置
CN109964507A (zh) 网络功能的管理方法、管理单元及系统
CN116170314B (zh) 一种网络切片场景下ai内生的数字孪生网络平台装置
Kafle et al. Adaptive virtual network slices for diverse IoT services
CN108345490A (zh) 一种nfv中部署虚拟机的方法和系统
CN110495197A (zh) 管理网络切片的方法和装置
WO2018210075A1 (zh) 网络控制方法、装置及网络设备
Wang et al. Intelligent network slicing for B5G and 6G: Resource allocation, service provisioning, and security
CN107408058B (zh) 一种虚拟资源的部署方法、装置及系统
US20230259387A1 (en) Data flow mirroring method and apparatus
WO2018014351A1 (zh) 一种资源配置方法及装置
JP5523599B1 (ja) ネットワークシステムの資源管理システムおよび方法
CN114221948A (zh) 一种云网系统及任务处理方法
CN105847172B (zh) 业务流量控制方法及装置
CN112118579B (zh) 资源分配方法以及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16905047

Country of ref document: EP

Kind code of ref document: A1

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

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 2016905047

Country of ref document: EP

Effective date: 20181219

ENP Entry into the national phase

Ref document number: 112018076166

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20181217