WO2017096606A1 - 资源分配的方法和切片分配单元 - Google Patents
资源分配的方法和切片分配单元 Download PDFInfo
- Publication number
- WO2017096606A1 WO2017096606A1 PCT/CN2015/097102 CN2015097102W WO2017096606A1 WO 2017096606 A1 WO2017096606 A1 WO 2017096606A1 CN 2015097102 W CN2015097102 W CN 2015097102W WO 2017096606 A1 WO2017096606 A1 WO 2017096606A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- slice
- resource
- resources
- requirement
- determining
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
Definitions
- the present invention relates to the field of communications and, more particularly, to a method of resource allocation and a slice allocation unit.
- the network will be further abstracted into a Network Slice based on logical functions and built as a "custom function + general purpose hardware".
- SDN Software-defined Networking
- NFV Network Functions Virtualization
- operators can use different types of communications on the same infrastructure. Users provide tailored slices. For example, operators can provide Mobile Broadband (MBB) slicing for mobile broadband users and Massive Machine Type Communication (Massive MTC) slicing for machine-like communications. Operators need to dynamically allocate slice resources to meet new business requirements, so how to effectively allocate slice resources for different services is an important issue.
- MBB Mobile Broadband
- Massive MTC Massive Machine Type Communication
- the resource allocation scheme of the slice in the prior art is: for different services, allocating slices that are isolated from each other, that is, the resources of the slices are independently allocated. This allocation of resources that are isolated from each other for different slices results in a small resource reuse and low resource utilization.
- the embodiment of the invention provides a resource allocation method and a slice allocation unit, which can improve resource utilization.
- a method of resource allocation includes: receiving a slice request for requesting a first slice for a network service; determining, according to the slice request, a function module FB included in the first slice; acquiring a second slice, the second slice including the allocated FB of the resource; determining whether the first FB can reuse the resource of the second FB according to whether the first FB in the first slice has a reverse affinity with the second FB in the second slice, where This anti-affinity means that resources cannot be shared between two FBs.
- the slice allocation unit receives a slice request for requesting a first cut for the network service Slice, which includes service requirements and resource configuration requirements. After receiving the slice request, the slice allocation unit determines at least one function module that best matches the slice request in the slice template according to the service and resource of the slice request requirement. The slice allocation unit also acquires a second slice that includes at least one FB of allocated resources. Determining whether the first FB can multiplex the resources of the second FB according to whether the first FB in the first slice has a reverse affinity with the second FB in the second slice, thereby determining the first cut The way the resources are allocated.
- the method for resource allocation provided by the embodiment of the present invention, by receiving a slice request for requesting a first slice, determining an FB included in the first slice according to the slice request, and acquiring a second slice of the FB including the allocated resource Determining, according to whether the first FB in the first slice has a reverse affinity with the second FB in the second slice, determining whether the first FB can multiplex the resource of the second FB, thereby the slice allocation unit
- the FB in the first slice multiplexes the FB of the allocated resource as much as possible, thereby improving resource utilization.
- the slice allocation unit may first determine whether the second FB can meet the service requirement required by the first FB, and if the service requirement of the first FB can be met, determine whether the remaining resource capacity of the second FB can meet the requirement of the first FB.
- Resource requirement if the second FB can satisfy the service requirement and resource requirement of the first FB at the same time, the first FB can multiplex the second FB, so that the first FB does not need to be re-established, and accordingly The first FB allocates resources independently, improving resource utilization.
- the first Whether the first FB in the slice has a reverse affinity with the second FB in the second slice, and determining whether the first FB can multiplex the resource of the second FB including: if the first FB and the second The FB has a reverse affinity, and it is determined that the first FB cannot multiplex the resources of the second FB.
- the requirement of the first FB includes service requirements and resources demand.
- the service requirement of the first FB can be satisfied by expanding the second FB, that is, the first FB needs to be re-established, and the resources required by the first FB are allocated.
- the second FB can meet the service requirement of the first FB, but the remaining resource capacity of the second FB cannot meet the resource requirement of the first FB, the second FB can be re-created to meet the requirement of the first FB, that is, The first FB allocates the same resources as the second FB.
- each FB in the first slice cannot share resources with the FB of the allocated resource in the network list, each FB of the first slice needs to be re-established, and correspondingly, the resources need to be re-independently allocated. That is, the first slice is re-established, and resources are independently allocated for the first slice. If a part of the FBs in the first slice can multiplex the FBs that have already allocated resources, then this part of the FBs can be used without reallocating resources. If all FBs in the first slice can reuse the FB to which the resource has been allocated, the first slice does not need to be re-established. That is to say, the FB in the first slice multiplexes the FB of the allocated resource in the slice list as much as possible, thereby improving resource utilization.
- the fifth possible implementation of the first aspect includes: acquiring the second slice generated according to the mapping table of the network service and the slice.
- NFVO is not able to identify slices, so a mapping table between network services and slices is defined in NFVO. Before the NFVO is not interacting with the slice allocation unit, the NFVO can map the network service to the slice to generate a second slice. When the NFVO receives a slice request from the slice allocation unit, the slice can be mapped to a network service that the NFVO can recognize.
- the present application provides a slice allocation unit that includes means for performing the method of the first aspect.
- a slice allocation unit including: a processor and a memory;
- the memory stores a program
- the processor executes the program for executing the first Aspect or method of resource allocation as described in any of the possible implementations of the first aspect.
- the slice allocation unit receives a slice request for requesting the first slice, determines an FB included in the first slice according to the slice request, and acquires an FB including the allocated resource.
- the second slice determines whether the first FB can multiplex the resources of the second FB according to whether the first FB in the first slice has a reverse affinity with the second FB in the second slice, thereby performing slice allocation
- the unit makes the FB of the first slice reuse the FB of the allocated resource as much as possible by the comprehensive judgment of the requirement of the FB of the first slice and the FB of the allocated resource, thereby improving resource utilization.
- FIG. 1 is a schematic diagram of a network architecture according to an embodiment of the present invention.
- FIG. 2 is a schematic diagram of an application scenario of an embodiment of the present invention.
- FIG. 3 is a schematic flowchart of a method for resource allocation according to an embodiment of the present invention.
- FIG. 4 is a schematic flowchart of a method for resource allocation according to an embodiment of the present invention.
- FIG. 5 is a schematic block diagram of a slice allocation unit according to an embodiment of the present invention.
- FIG. 6 is a schematic structural diagram of a slice allocation unit according to an embodiment of the present invention.
- FIG. 1 is a schematic diagram of a 5G network architecture according to an embodiment of the present invention.
- 5G is the era of universal interconnection.
- V2V Vehicle to Vehicle
- machine communication will emerge.
- the network is further abstracted into slices based on logical functions and built in a "custom function + general purpose hardware" approach.
- Slices implemented based on custom software allow operators to provide the network as a service to users, ie operators can connect physical networks
- a slice is a connection service consisting of various custom software defined logic function blocks (FBs). For example, the classification of the logical function modules in the slices given in Table 1 consists. The end-to-end connection network consisting of the various logical function modules given in Table 1 is sliced to meet specific business needs.
- FBs software defined logic function blocks
- Table 1 consists of the classification of logical function modules in the slice
- MBB slices require basic unified control entity functions in the control plane logic function module, network management functions such as encapsulation and decapsulation in the database and forwarding plane logic function modules; small-scale machine-to-machine (M2M) slices.
- the functional requirements of the MBB slicing are basically the same, except that the functional module configuration is lower; the multimedia service slicing needs to enhance the video optimization function in the online service function relative to the MBB slicing; the public security slicing requires a fully customized functional module with high isolation.
- FIG. 2 is a schematic diagram of an application scenario of an embodiment of the present invention.
- the present invention is applied to a Network Function Virtualized (NFV)-Management and Orchestration (MANO) network management system of a European Telecommunications Standards Institute (ETSI) in which a plurality of slices are deployed.
- the system includes Operation Support System (OSS)/Business Support (System BSS), Network Functions Virtualization Orchestration (NFVO) unit, and Virtualized Network Function Management (Virtualized Network Function Management).
- VNFM virtual infrastructure management
- VIM virtualization Infrastructure
- NFVI network function Virtualization Infrastructure
- OSS/BSS has an interface with NFVO in MANO
- NFVO is a network service (NS) lifecycle management module, and is responsible for coordinating NS, virtual network function (VNF) constituting NS, and bearer Control and management of virtual resources of VNF.
- VNFM mainly controls the life cycle (instantiation, configuration, shutdown, etc.) of the VNF.
- the VIM usually runs in the corresponding infrastructure site.
- the main functions include: resource discovery, management allocation of virtual resources, and fault handling, which provide resource support for the operation of the VNF.
- Each slice corresponds to a specific type of service, providing customized services for users of such services. For example, operators offer MBB slicing for mobile broadband users and large-scale MTC slicing for machine-like communications. When the operator requests a new service, the OSS/BSS notifies the MANO to manage the orchestration, and allocates corresponding slice resources to provide the required services.
- a slice in which resources are isolated from each other is allocated, that is, the resources of the slice are independently allocated. This allocation of resources that are isolated from each other for different slices results in a small resource reuse and low resource utilization.
- FIG. 3 shows a schematic diagram of a method 100 of resource allocation in accordance with an embodiment of the present invention.
- the method 100 is performed by a slice allocation unit.
- the method 100 includes:
- S110 Receive a slice request, where the slice request is used to request a first slice for a network service.
- S130 Acquire a second slice, where the second slice includes an FB with allocated resources
- the slice allocation unit receives a slice request sent by the sending unit, where the slice request is used to request a first slice for the network service, where the slice request includes service requirement information and resource configuration requirement information.
- the slice allocating unit determines at least one function module that best matches the slice request in the slice template according to the service and resource required by the slice request.
- the slice allocation unit also acquires a second slice that includes at least one FB of allocated resources. Determining whether the first FB can multiplex the resources of the second FB according to whether the first FB in the first slice has a reverse affinity with the second FB in the second slice, thereby determining the first cut The way the resources are allocated.
- the slice allocation unit may be an independent device, may be set in the OSS/BSS in the network management system, or may be set in the NFVO in the network management system, or may also be the improved NFVO having the above functions, etc. .
- the following embodiments are described by taking a slice allocation unit as an independent device as an example, but the present invention is not limited thereto.
- the slice allocation unit receives a slice request for requesting the first slice, determines an FB included in the first slice according to the slice request, and acquires an FB including the allocated resource.
- the second slice determines whether the first FB can multiplex the resources of the second FB according to whether the first FB in the first slice has a reverse affinity with the second FB in the second slice, thereby
- the allocation unit makes the FB in the first slice reuse the FB of the allocated resource as much as possible by the comprehensive judgment of the requirement of the FB of the first slice and the FB of the allocated resource, thereby improving resource utilization.
- the sending unit sends a slice request to the slice allocating unit, the slice request is used to request the first slice for the network service.
- Service requirements and resource configuration requirements can be included in the slice request.
- the service requirement can be a mobility management requirement, a connectivity management requirement, or a quality of service indicator requirement.
- Resource configuration requirements can be affinity policies, anti-affinity policies, or high availability strategies.
- the sending unit may be the foregoing OSS/BSS or an operator, which is not limited by the present invention.
- the slice allocation unit determines a function module FB that matches the first slice according to the slice request.
- the slice allocation unit determines at least one FB that matches the first slice according to the slice request. For example, the slice allocation unit can determine whether it is a functional module required in the slice request according to the function described in the slice template.
- a second slice is acquired, the second slice including an FB of allocated resources.
- the obtaining, by the slice allocation unit, the second slice may be implemented by acquiring a slice list.
- the slice list may include only one single slice, or may include multiple slices, that is, the slice allocation.
- the unit may obtain a second slice by acquiring a slice list, or acquire a plurality of second slices.
- the acquiring the second slice includes: the slice allocation unit periodically or conditionally acquiring the slice list, and further, the function module and the resource configuration information of the second slice are obtained.
- the acquiring the second slice includes: obtaining a mapping relationship between the network service and the slice according to the network service The second slice generated by the table.
- NFVO cannot identify slices, and therefore, a mapping table between NS and slices is defined in NFVO. Before the NFVO does not interact with the slice allocation unit, the NFVO can map the NS to the slice, which in turn can generate a second slice. When the NFVO receives a slice request from the slice allocation unit, it can also map the slice to the NS that the NFVO can recognize.
- the slice allocation unit determines whether the first FB can reuse the resources of the second FB according to whether the first FB in the first slice and the second FB in the second slice have reverse affinity. This anti-affinity means that resources cannot be shared between two FBs.
- the first FB may be any one of the first slices
- the second FB may be any one of the second slices.
- the slice allocation unit acquires the second slice, and further can obtain resource configuration information of the FB of the allocated resource in the second slice, and the slice allocation unit can determine the first FB and the second FB according to the resource configuration information of the second FB. Whether there is anti-affinity, this anti-affinity means that resources cannot be shared between two FBs.
- the slice allocation unit may determine that the first FB cannot multiplex the resources of the second FB, that is, The first FB needs to be re-established and the required resources are reallocated for the first FB. That is, if at least one FB included in the first slice cannot share resources with the FB of the allocated resource in the second slice, each FB of the first slice needs to be re-established, correspondingly The ground also needs to re-allocate resources independently, that is, re-establish the first slice and allocate resources independently for the first slice.
- the first FB can share resources with the second FB, and the second FB can meet the requirement of the first FB, determining that the first slice can multiplex resources of the second FB.
- the first FB can share resources with the second FB, it is also determined whether the second FB can meet the requirement of the first FB, and if the second FB can meet the requirement of the first FB, the first FB
- the second FB can be multiplexed, that is, the first FB does not need to be re-established, and the resource is not re-allocated accordingly; if the second FB cannot meet the requirement of the first FB, the first FB cannot reuse the second FB.
- the resources of the FB that is, the first FB needs to be re-established, and resources need to be allocated independently for the first FB.
- the demand of the first FB includes service requirements and resource requirements.
- the slice allocation unit may first determine whether the second FB can meet the service requirement required by the first FB, and if the service requirement of the first FB can be met, determine whether the remaining resource capacity of the second FB can meet the requirement of the first FB. Resource requirements, if the second FB can meet the service requirements and resource requirements of the first FB at the same time, Then the first FB can multiplex the second FB, so that there is no need to re-establish the first FB, and accordingly there is no need to allocate resources independently for the first FB. Therefore, under the basic isolation requirement between slices, the remaining resources of the existing FB are reused, and the resource utilization rate is improved.
- the slice allocation unit determines whether the FB of the existing slice can be multiplexed, it can first determine whether the FB of the single slice can be multiplexed, and if the FB of the single slice can satisfy the requirement of the FB of the first slice, the priority multiplexing Single-slice FB, for example, if an existing MBB slice (that is, a resource has already been allocated for the MBB slice), if it is necessary to create a small M2M slice with less isolation requirements, the functional module of the MBB slice can satisfy the new For slicing requirements, small-scale M2M slices can directly reuse existing MBB slices.
- the FB of a single slice cannot meet the requirements of the FB of the first slice, it is determined whether the FB in the plurality of different slices can satisfy the requirement of the FB of the first slice, for example, the existing MBB slice and the small scale For M2M slicing, it is necessary to create a meter reading service slice that can be billed. Since the combination of the existing MBB slice and the FB in the small-scale M2M slice can satisfy the meter reading service slice, the meter reading is performed.
- the service slice can reuse all the FBs in the small-scale M2M slice, plus the accounting module of the MBB slice.
- the first FB does not have a reverse affinity with the second FB, and the second FB cannot meet the requirement of the first FB, determining that the first FB is unable to multiplex the second FB resource of.
- the slice allocation unit determines whether the second FB can satisfy the requirement of the first FB, including whether the service requirement and resource requirement of the first FB can be satisfied.
- the requirement of the first FB can be satisfied by expanding the second FB.
- the second FB can satisfy the service requirement of the first FB, but the remaining resource capacity of the second FB cannot meet the resource requirement of the first FB, so that a virtual machine (VM) can be added or a new one can be created.
- the second FB satisfies the requirement of the first FB, that is, the first FB can be allocated the same resource as the second FB. For example, if the existing multimedia service is sliced, when a high-level video service slice for the advanced user (VIP) needs to be created, part of the function modules of the existing multimedia service slice are expanded to meet the high-level video service. slice.
- VIP advanced user
- the second FB cannot meet the service requirements of the first FB, the first FB can be satisfied by expanding the FB.
- the service requirement of the FB that is, the need to re-establish the first FB and allocate the resources required by the first FB. For example, if an existing MBB slice needs to create a slice for carrying a video service for a VIP user, the function module of the control plane in the MBB slice is reserved, and a value added service (VAS) server that is not originally added is added to the forwarding plane. functional module.
- VAS value added service
- each FB in the first slice needs to be re-established, and correspondingly needs to be re-independent.
- Allocating resources that is, re-establishing the first slice, and independently allocating resources for the first slice. If a part of the FBs in the first slice can multiplex the FBs that have already allocated resources, then this part of the FBs can be used without reallocating resources. If all FBs in the first slice can reuse the FB to which the resource has been allocated, the first slice does not need to be re-established. That is to say, the FB in the first slice multiplexes the FB of the allocated resource in the slice list as much as possible, thereby improving resource utilization.
- the resources allocated to the FB are mainly physical resources, and may be, for example, a CPU, a storage resource, a broadband resource, and the like.
- the resource allocation manner determined by the slice allocation unit is sent to the MANO, and the MANO performs resource allocation according to the resource allocation manner, thereby completing the network connection service.
- the NFVO receives the resource allocation manner of the slice allocation unit (the method of multiplexing the existing resources or the method of reallocating the resources), so that the MANO can be triggered to allocate resources, thereby completing the network connection service. For example, reallocating resources for the first FB of the first slice or multiplexing the remaining resources of the second FB.
- the NFVO needs to verify the validity of the reallocation resource (ie, verify that it has sufficient resources to satisfy the requirement of the first FB), thereby allocating network resources for the first FB. Network connection service is guaranteed.
- the resource allocation may also be completed to the sending unit and the slice allocating unit in response to the resource allocation manner that has been determined according to the slice allocation unit.
- the slice allocation unit receives a slice request for requesting the first slice, determines an FB included in the first slice according to the slice request, and acquires an FB including the allocated resource.
- the second slice determines whether the first FB can multiplex the resources of the second FB according to whether the first FB in the first slice has a reverse affinity with the second FB in the second slice, thereby
- the allocation unit makes the FB in the first slice reuse the FB of the allocated resource as much as possible by the comprehensive judgment of the requirement of the FB of the first slice and the FB of the allocated resource, thereby improving resource utilization.
- the slice allocation unit receives a slice request for requesting a first slice for a network service, determines, according to the slice request, at least one function module that best matches the slice request in the slice template, and obtains a slice list, the slice list includes at least one FB of the allocated resource, and determining whether the first FB can be recovered according to whether the first FB in the first slice has a reverse affinity with the second FB in the slice list.
- the resource of the second FB is used to determine a resource allocation manner of the first slice.
- each FB in the first slice cannot share resources with the FB of the allocated resource in the network list, each FB of the first slice needs to be re-established, and correspondingly, the resources need to be re-independently allocated. That is, the first slice is re-established, and resources are independently allocated for the first slice. If a part of the FBs in the first slice can multiplex the FBs that have already allocated resources, then this part of the FBs can be used without reallocating resources. If all FBs in the first slice can reuse the FB to which the resource has been allocated, the first slice does not need to be re-established. That is to say, the FB in the first slice multiplexes the remaining resources of the FB of the allocated resource in the slice list as much as possible, thereby improving resource utilization.
- FIG. 4 is a schematic flowchart diagram of a method for resource allocation according to an embodiment of the present invention.
- the meanings of the various terms in the embodiments of the present invention are the same as those of the foregoing embodiments.
- a slice allocation unit receives a slice request, where the slice request is used to request a first slice for a network service, where the slice request includes a service requirement and a resource configuration requirement.
- the slice allocation unit determines, according to the slice request, a function module FB that matches the first slice.
- the slice allocation unit has an interface with the storage module, and the storage module stores a predefined slice template, which also includes a slice template that has not been online yet. After receiving the slice request sent by the sending unit, the slice allocating unit determines at least one function module that best matches the slice request in the slice template according to the service and resource required by the slice request.
- the obtaining, by the slice allocation unit, the second slice may be implemented by acquiring a slice list.
- the slice list may include only one single slice, or may include multiple slices, that is, the slice allocation unit may obtain Get a second slice from the slice list, or get Take multiple second slices.
- the slice allocation unit determines whether the first FB can multiplex resources of the second FB according to whether the FB in the first slice and the FB of the second slice have reverse affinity, and the reverse affinity indicates Resources cannot be shared between two FBs.
- the slice allocation unit acquires the second slice, and further can obtain resource configuration information of each FB in the FB of the allocated resource in the second slice, and the slice allocation unit can determine the first FB according to the resource configuration information of the second FB. Whether there is a reverse affinity with the second FB, and further determining whether the first FB can reuse the remaining resources of the second FB.
- step 305 is performed.
- step 307 is performed.
- Whether the slice allocation unit determines whether the second FB can satisfy the requirement of the first FB includes whether the service requirement of the first FB and the resource requirement of the first FB can be satisfied. That is, when the second FB is capable of satisfying the service requirement of the first FB, and the resource of the second FB can satisfy the resource requirement of the first FB, the first FB can multiplex the second FB, otherwise the first FB can only be re-allocated. Resources.
- the first FB multiplexes the remaining resources of the second FB, so that the existing slice resources of the allocated resources are reused as much as possible, and the resource utilization rate is improved.
- the slice allocation unit receives a slice request for requesting the first slice, determines an FB included in the first slice according to the slice request, and acquires an FB including the allocated resource.
- the second slice determines whether the first FB can multiplex the resources of the second FB according to whether the first FB in the first slice has a reverse affinity with the second FB in the second slice, thereby
- the allocation unit makes the FB in the first slice reuse the FB of the allocated resource as much as possible by comprehensively judging the requirement of the FB of the first slice and the FB of the allocated resource, thereby High resource utilization.
- the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be directed to the embodiments of the present invention.
- the implementation process constitutes any limitation.
- a method of resource allocation according to an embodiment of the present invention is described in detail above, and a slice allocation unit according to an embodiment of the present invention will be described below.
- FIG. 5 shows a schematic block diagram of a slice allocation unit 500 in accordance with an embodiment of the present invention.
- the slice allocation unit 500 includes:
- the receiving module 510 is configured to receive a slice request, where the slice request is used to request a first slice for a network service;
- the first determining module 520 is configured to determine, according to the slice request received by the receiving module, the function module FB included in the first slice;
- the obtaining module 530 is configured to acquire a second slice, where the second slice includes an FB of the allocated resource;
- a second determining module 540 configured to determine, according to whether the first FB in the first slice and the second FB in the second slice have reverse affinity, determine whether the first FB can multiplex the second FB A resource, wherein the anti-affinity indicates that resources cannot be shared between two FBs.
- the slice allocation unit of the resource allocation determines the FB included in the first slice according to the slice request by receiving a slice request for requesting the first slice, and acquires the FB including the allocated resource.
- the second slice determines whether the first FB can multiplex the resources of the second FB according to whether the first FB in the first slice has a reverse affinity with the second FB in the second slice, thereby
- the allocation unit makes the FB in the first slice reuse the FB of the allocated resource as much as possible by the comprehensive judgment of the requirement of the FB of the first slice and the FB of the allocated resource, thereby improving resource utilization.
- the second determining module 540 is specifically configured to:
- the first FB and the second FB do not have reverse affinity, and the second FB can meet the requirement of the first FB, it is determined that the first FB can multiplex the resources of the second FB.
- the second determining module 540 is specifically configured to:
- the first FB does not have reverse affinity with the second FB, and the second FB cannot meet the requirement of the first FB, it is determined that the first FB cannot multiplex the resources of the second FB.
- the second determining module 540 is specifically configured to:
- the first FB has a reverse affinity with the second FB, determining that the first FB is unable to multiplex the The resources of the second FB.
- the requirement of the first FB includes a service requirement and a resource requirement.
- the obtaining module 530 is specifically configured to:
- the slice allocation unit 500 may correspond to a slice allocation unit in a method of resource allocation according to an embodiment of the present invention, and the above-described and other operations and/or functions of respective modules in the slice allocation unit 500 are respectively implemented for The corresponding processes of the foregoing various methods are not described herein for the sake of brevity.
- the slice allocation unit of the resource allocation determines the FB included in the first slice according to the slice request by receiving a slice request for requesting the first slice, and acquires the FB including the allocated resource.
- the second slice determines whether the first FB can multiplex the resources of the second FB according to whether the first FB in the first slice has a reverse affinity with the second FB in the second slice, thereby
- the allocation unit makes the FB in the first slice reuse the FB of the allocated resource as much as possible by the comprehensive judgment of the requirement of the FB of the first slice and the FB of the allocated resource, thereby improving resource utilization.
- FIG. 6 shows a structure of a slice allocation unit according to still another embodiment of the present invention, including at least one processor 702 (for example, a CPU), at least one network interface 705 or other communication interface, a memory 706, and at least one communication bus 703. Used to implement connection communication between these devices.
- the processor 702 is configured to execute executable modules, such as computer programs, stored in the memory 706.
- the memory 706 may include a high speed random access memory (RAM), and may also include a non-volatile memory such as at least one disk memory.
- a communication connection with at least one other network element is achieved by at least one network interface 705 (which may be wired or wireless).
- the memory 706 stores a program 7061, and the processor 702 executes the program 7061 for performing some operations:
- processor 702 is specifically configured to:
- the first FB in the first slice does not have reverse affinity with the second FB in the second slice, and the second FB can meet the requirement of the first FB, determining that the first FB can be recovered Use the resources of the second FB.
- the processor 702 is specifically configured to:
- the resources of the second FB can be multiplexed.
- the processor 702 is specifically configured to:
- the first FB in the first slice has a reverse affinity with the second FB in the second slice, it is determined that the first FB cannot multiplex the resource of the second FB.
- the requirement of the first FB includes a service requirement and a resource requirement.
- the processor 702 is specifically configured to:
- the slice allocation unit receives a slice request for requesting the first slice, determines an FB included in the first slice according to the slice request, and acquires an included resource including the allocated resource.
- the second slice of the FB determines whether the first FB can multiplex the resources of the second FB according to whether the first FB in the first slice has a reverse affinity with the second FB in the second slice.
- the slice allocation unit makes the FB in the first slice reuse the FB of the allocated resource as much as possible by the comprehensive judgment of the requirement of the FB of the first slice and the FB of the allocated resource, thereby improving resource utilization.
- the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be directed to the embodiments of the present invention.
- the implementation process constitutes any limitation.
- the disclosed systems, devices, and methods may be implemented in other manners.
- the device embodiments described above are merely illustrative.
- the division of the unit is only a logical function division.
- there may be another division manner for example, multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed.
- the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
- the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
- each functional unit in each embodiment of the present invention 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 integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
- the technical solution of the present invention which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
- the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
- the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本发明实施例提供了一种资源分配的方法和切片分配单元。该方法包括:接收切片请求,所述切片请求用于为网络服务请求第一切片;根据所述切片请求确定所述第一切片包括的功能模块FB;获取第二切片,所述第二切片包括已分配资源的FB;根据所述第一切片中的第一FB与所述第二切片中的第二FB是否存在反亲和性,确定所述第一FB是否能够复用所述第二FB的资源,其中,所述反亲和性表示两个FB之间不能够共享资源。本发明的技术方案切片分配单元通过对第一切片的FB的需求与已分配资源的FB的综合判断,使得第一切片中的FB尽可能的复用已分配资源的FB,从而提高了资源利用率。
Description
本发明涉及通信领域,并且更具体地,涉及资源分配的方法和切片分配单元。
在未来的5G***中,网络将基于逻辑功能而被进一步抽象为切片(Network Slice),并以“定制功能+通用化硬件”的方式构建。在5G网络架构体系中,通过软件定义网络(Software-defined Networking,SDN)和(网络功能虚拟化,Network Functions Virtualization,NFV)技术相结合,运营商可以在同一套基础设施上为不同类型的通信用户提供量身定制的切片。例如,运营商可以为移动宽带用户提供移动宽带(Mobile Broad Band,MBB)切片,为机器类通信则提供大规模机器类通信(Massive Machine Type Communication,Massive MTC)切片。运营商需要动态分配切片资源来满足新业务需求,所以针对不同的业务如何有效的分配切片资源是一个重要问题。
现有技术中切片的资源分配方案是:针对不同的业务,分配资源相互隔离的切片,也就是说切片的资源独立分配。这种为不同的切片分配相互隔离的资源的分配方式会导致资源复用度小,资源利用率低。
发明内容
本发明实施例提供一种资源分配的方法和切片分配单元,能够提高资源利用率。
第一方面,提供了一种资源分配的方法。该方法包括:接收切片请求,该切片请求用于为网络服务请求第一切片;根据该切片请求确定该第一切片包括的功能模块FB;获取第二切片,该第二切片包括已分配资源的FB;根据该第一切片中的第一FB与该第二切片中的第二FB是否存在反亲和性,确定该第一FB是否能够复用该第二FB的资源,其中,该反亲和性表示两个FB之间不能够共享资源。
切片分配单元接收切片请求,该切片请求用于为网络服务请求第一切
片,该切片请求中包括服务需求和资源配置需求。切片分配单元接收到该切片请求后,根据该切片请求需求的服务和资源在切片模板中确定与该切片请求最为匹配的至少一个功能模块。切片分配单元还获取第二切片,该第二切片包括至少一个已分配资源的FB。根据该第一切片中的第一FB与该第二切片中的第二FB是否存在反亲和性,确定该第一FB是否能够复用该第二FB的资源,进而确定该第一切片的资源分配方式。
本发明实施例提供的资源分配的方法,通过接收用于请求第一切片的切片请求,根据该切片请求确定该第一切片包括的FB,并获取包括已分配资源的FB的第二切片,根据该第一切片中的第一FB与该第二切片中的第二FB是否存在反亲和性,确定该第一FB是否能够复用该第二FB的资源,由此切片分配单元通过对第一切片的FB的需求与已分配资源的FB的综合判断,使得第一切片中的FB尽可能的复用已分配资源的FB,从而提高了资源利用率。
结合第一方面,在第一方面的第一种可能的实现方式中,根据该第一切片中的第一FB与该第二切片中的第二FB是否存在反亲和性,确定该第一FB是否能够复用该第二FB的资源,包括:若该第一FB与该第二FB不存在反亲和性,且该第二FB能够满足该第一FB的需求时,确定该第一FB能够复用该第二FB的资源。
若第一FB能够与第二FB共享资源时,还需要确定第二FB是否能够满足第一FB的需求,该需求包括服务需求和资源需求。切片分配单元可以先确定第二FB是否能够满足第一FB所需的服务需求,若能够满足第一FB的服务需求时,再确定第二FB的剩余资源容量是否能够满足第一FB所需要的资源需求,若第二FB能够同时满足第一FB的服务需求和资源需求时,则该第一FB可以复用该第二FB,这样就不需要重新建立第一FB,相应地就不需要为第一FB独立地分配资源,提高了资源利用率。
结合第一方面,在第一方面的第二种可能的实现方式中,根据该第一切片中的第一FB与该第二切片中的第二FB是否存在反亲和性,确定该第一FB是否能够复用该第二FB的资源,包括:若该第一FB与该第二FB不存在反亲和性,且该第二FB不能够满足该第一FB的需求时,确定该第一FB不能够复用该第二FB的资源。
结合第一方面,在第一方面的第三种可能的实现方式中,该根据该第一
切片中的第一FB与该第二切片中的第二FB是否存在反亲和性,确定该第一FB是否能够复用该第二FB的资源,包括:若该第一FB与该第二FB存在反亲和性,确定该第一FB不能够复用该第二FB的资源。
结合第一方面的第一种可能的实现方式或第一方面的第二种可能的实现方式,在第一方面的第四种可能的实现方式中,该第一FB的需求包括服务需求和资源需求。
若第二FB不能够满足第一FB的服务需求,可以通过扩展第二FB满足第一FB的服务需求,也就是需要重新建立第一FB,并分配第一FB所需的资源。
若第二FB能够满足第一FB的服务需求,但是第二FB的剩余资源容量不能够满足第一FB的资源需求,这样可以重新创建一个第二FB来满足第一FB的需求,即可以为第一FB分配与第二FB相同的资源。
若第一切片中的每个FB都不能与网络列表中的已分配资源的FB共享资源,则该第一切片的每个FB都需要重新建立,相应地也需要重新独立的分配资源,即重新建立第一切片,并为该第一切片独立分配资源。若第一切片中的部分FB能够复用已经分配资源的FB,则这部分FB就可以不用重新分配资源。若第一切片中的全部FB都可以复用已经分配资源的FB,则第一切片不需要重新建立。也就是说,该第一切片中的FB尽可能的复用切片列表中的已经分配资源的FB,从而提高资源利用率。
结合第一方面或第一方面的第一种可能的实现方式至第一方面的第四种可能的实现方式中的任一种可能的实现方式,在第一方面的第五种可能的实现方式中,该获取第二切片,包括:获取根据网络服务与切片的映射关系表生成的该第二切片。
NFVO不能够识别切片,因此,在NFVO中定义了网络服务与切片的映射关系表。在NFVO未与切片分配单元交互之前,NFVO可以将网络服务映射到切片,进而生成第二切片。在NFVO收到切片分配单元的切片请求时,可以将切片映射到NFVO可以识别的网络服务。
第二方面,本申请提供了一种切片分配单元,该切片分配单元包括用于执行第一方面中的方法的模块。
第三方面,提供了一种切片分配单元,包括:处理器和存储器;
所述存储器存储了程序,所述处理器执行所述程序,用于执行上述第一
方面或第一方面任一种可能的实现方式所述的资源分配的方法。
基于上述技术方案,在本发明实施例中,切片分配单元接收用于请求第一切片的切片请求,根据该切片请求确定该第一切片包括的FB,并获取包括已分配资源的FB的第二切片,根据该第一切片中的第一FB与该第二切片中的第二FB是否存在反亲和性,确定第一FB是否能够复用第二FB的资源,由此切片分配单元通过对第一切片的FB的需求与已分配资源的FB的综合判断,使得第一切片中的FB尽可能的复用已分配资源的FB,从而提高了资源利用率。
为了更清楚地说明本发明实施例的技术方案,下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本发明的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1是本发明实施例的网络架构示意图。
图2是本发明实施例的应用场景的示意图。
图3是本发明实施例的资源分配的方法的示意性流程图。
图4是本发明实施例的资源分配的方法的示意性流程图。
图5是根据本发明实施例的切片分配单元的示意性框图。
图6是根据本发明实施例的切片分配单元的结构示意图。
下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例是本发明一部分实施例,而不是全部的实施例。基于本发明中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。
图1是本发明实施例的5G网络架构示意图。5G是万物互连的时代,除了移动宽带,车辆间通信(Vehicle to Vehicle,V2V)、机器类通信等更多多样化的业务将会出现。在5G***中,网络将基于逻辑功能而被进一步抽象为切片,并以“定制功能+通用化硬件”的方式构建。基于定制软件实现的切片允许运营商将网络作为一种服务提供给用户,即运营商能够将实体网络
以‘网络即服务’的形式为用户提供连接服务,并通过对速率、容量、覆盖率、延迟、可靠性、安全性和可用性等网络性能指标进行自由灵活组合,从而满足各个用例的具体要求。
切片是由各种定制化的软件定义的逻辑功能模块(Function Block,FB)组成的一种连接服务。例如,表1给出的切片中逻辑功能模块的分类组成。由表1给出的各种逻辑功能模块组成的端到端的连接网络即切片,来满足具体业务需求。
表1切片中逻辑功能模块的分类组成
例如,MBB切片需要控制面逻辑功能模块中基本的统一控制实体功能、数据库和转发面逻辑功能模块中的封装解封装等网管功能;小规模的机器间通信(Machine-to-Machine,M2M)切片与MBB切片功能需求基本相同,只是功能模块配置更低;多媒体业务切片相对MBB切片则需要增强在线服务功能中的视频优化功能;公共安全切片则需要高隔离性的完全定制的功能模块。
图2是本发明实施例的应用场景的示意图。本发明应用于部署了多个切片的欧洲电信标准化协会(European Telecommunications Standards Institute,ETSI)的网络功能虚拟化(Network Function Virtualized,NFV)-管理和编排(Management and Orchestration,MANO)网管***中,该***包括运维支撑***(Operation Support System,OSS)/业务支撑***(Business Support,System BSS)、网络功能虚拟化编排(Network Functions Virtualization Orchestration,NFVO)单元、虚拟网络功能管理(Virtualized Network Function Management,VNFM)单元、虚拟基础设施管理(Virtualized Infrastructure
Management,VIM)单元和网络功能虚拟化基础设施(Network Function Virtualized Infrastructure,NFVI)单元。其中,OSS/BSS与MANO中的NFVO有接口,NFVO是网络服务(Network Service,NS)生命周期的管理模块,同时负责协调NS、组成NS的虚拟网络功能(Virtualized Network Function,VNF)以及承载各VNF的虚拟资源的控制和管理。VNFM主要对VNF的生命周期(实例化、配置和关闭等)进行控制。VIM通常运行于对应的基础设施站点中,主要功能包括:资源的发现、虚拟资源的管理分配和故障处理等,为VNF的运行提供资源支持。
每个切片对应于一类特定的业务,为这类业务的用户提供定制化的服务。例如,运营商为移动宽带用户提供MBB切片,为机器类通信则提供大规模MTC切片。当运营商请求新的服务时,由OSS/BSS通知MANO去管理编排,分配对应的切片资源来提供所需的服务。现有技术中,针对不同的业务,分配资源相互隔离的切片,也就是说切片的资源独立分配。这种为不同的切片分配相互隔离的资源的分配方式会导致资源复用度小,资源利用率低。
图3示出了根据本发明实施例的资源分配的方法100的示意图。该方法100由切片分配单元执行。该方法100包括:
S110,接收切片请求,该切片请求用于为网络服务请求第一切片;
S120,根据该切片请求确定该第一切片包括的功能模块FB;
S130,获取第二切片,该第二切片包括已分配资源的FB;
S140,根据该第一切片中的第一FB与该第二切片中的第二FB是否存在反亲和性,确定该第一FB是否能够复用该第二FB的资源,其中,该反亲和性表示两个FB之间不能够共享资源。
具体而言,切片分配单元接收发送单元发送的切片请求,该切片请求用于为网络服务请求第一切片,该切片请求中包括服务需求信息和资源配置需求信息。切片分配单元接收到发送单元发送的切片请求后,根据该切片请求需求的服务和资源在切片模板中确定与该切片请求最为匹配的至少一个功能模块。切片分配单元还获取第二切片,该第二切片包括至少一个已分配资源的FB。根据该第一切片中的第一FB与该第二切片中的第二FB是否存在反亲和性,确定该第一FB是否能够复用该第二FB的资源,进而确定该第一切片的资源分配方式。
应理解,该切片分配单元可以是独立装置,也可以是设置在网管***中的OSS/BSS中,或者可以是设置在网管***中的NFVO中,或者还可以是改进后的NFVO具有上述功能等。为了描述方便,下述实施例以切片分配单元是独立装置为例进行说明,但本发明对此并不限定。
因此,本发明实施例提供的资源分配的方法,切片分配单元接收用于请求第一切片的切片请求,根据该切片请求确定该第一切片包括的FB,并获取包括已分配资源的FB的第二切片,根据该第一切片中的第一FB与该第二切片中的第二FB是否存在反亲和性,确定第一FB是否能够复用第二FB的资源,由此切片分配单元通过对第一切片的FB的需求与已分配资源的FB的综合判断,使得第一切片中的FB尽可能的复用已分配资源的FB,从而提高了资源利用率。
在S110中,具体而言,发送单元向切片分配单元发送切片请求,该切片请求用于为网络服务请求第一切片。该切片请求中可以包括服务需求和资源配置需求。例如,该服务需求可以是移动性管理需求、连接性管理需求或服务质量指标需求等。资源配置需求可以是亲和性策略、反亲和性策略或高可用性策略等。
应理解,该发送单元可以是前述的OSS/BSS,也可以是操作员(Operator),本发明对此不进行限定。
在S120,切片分配单元根据该切片请求确定匹配该第一切片的功能模块FB。
具体而言,切片分配单元根据该切片请求确定匹配该第一切片的至少一个FB。例如,切片分配单元可以根据切片模板中描述的功能确定是否是切片请求中需求的功能模块。
在S130,具体而言,获取第二切片,该第二切片包括已分配资源的FB。
具体而言,该切片分配单元获取第二切片可以是通过获取切片列表的形式实现,例如,切片列表中可以只包括一个单一的切片,也可以是包括多个切片,也就是说,该切片分配单元可以通过获取切片列表获取到一个第二切片,或者获取到多个第二切片。
可选地,该获取第二切片,包括:切片分配单元周期性或者条件性的获取切片列表,进而可以获知第二切片的功能模块和资源配置信息。
可选地,该获取第二切片,包括:获取根据网络服务与切片的映射关系
表生成的该第二切片。
具体而言,NFVO不能够识别切片,因此,在NFVO中定义了NS与切片的映射关系表。在NFVO未与切片分配单元交互之前,NFVO可以将NS映射到切片,进而可以生成第二切片。在NFVO收到切片分配单元的切片请求时,还可以将切片映射到NFVO可以识别的NS。
S140,切片分配单元根据该第一切片中的第一FB与该第二切片中的第二FB是否存在反亲和性,确定该第一FB是否能够复用该第二FB的资源,其中,该反亲和性表示两个FB之间不能够共享资源。
具体而言,该第一FB可以是第一切片中的任意一个FB,该第二FB也可以是第二切片中的任意一个FB。切片分配单元获取该第二切片,进而可以获知该第二切片中已分配资源的FB的资源配置信息,切片分配单元根据第二FB的资源配置信息,可以确定该第一FB与该第二FB是否存在反亲和性,该反亲和性表示两个FB之间不能够共享资源。若该第一FB与该第二FB存在反亲和性,即第一FB不能够与第二FB共享资源,该切片分配单元可以确定该第一FB不能够复用第二FB的资源,即该第一FB需要重新建立,并为该第一FB重新分配所需的资源。也就是说,若第一切片包括的至少一个FB中,每个FB都不能与第二切片中的已分配资源的FB共享资源,则第一切片的每个FB都需要重新建立,相应地也需要重新独立的分配资源,即重新建立第一切片,并为该第一切片独立分配资源。
可选地,若第一FB可以与第二FB共享资源,且该第二FB能够满足该第一FB的需求,确定该第一切片能够复用该第二FB的资源。
具体而言,若第一FB能够与第二FB共享资源时,还需要确定第二FB是否能够满足第一FB的需求,若第二FB能够满足该第一FB的需求,则该第一FB可以复用该第二FB,即该第一FB不需要重新建立,相应地也不用重新分配资源;若第二FB不能满足第一FB的需求,则该第一FB不能够复用该第二FB的资源,也就是说,该第一FB需要重新建立,并需要为该第一FB独立的分配资源。
其中,该第一FB的需求包括服务需求和资源需求。切片分配单元可以先确定第二FB是否能够满足第一FB所需的服务需求,若能够满足第一FB的服务需求时,再确定第二FB的剩余资源容量是否能够满足第一FB所需要的资源需求,若第二FB能够同时满足第一FB的服务需求和资源需求时,
则第一FB可以复用第二FB,这样就不需要重新建立第一FB,相应地就不需要为第一FB独立地分配资源。因此,在满足切片之间基本的隔离需求下,复用已有FB的剩余资源,提高了资源利用率。
应注意,第一切片中的FB在复用切片列表中的FB时,尽量使用在同一个切片中的FB,这样可以方便后续的调度。因此,在切片分配单元确定是否能够复用现有切片的FB时,可以先确定是否能够复用单一切片的FB,若单一切片的FB能够满足第一切片的FB的需求时,优先复用单一切片的FB,例如,如果现有MBB切片(即已经为该MBB切片分配了资源),若需要创建一个M2M小规模、对隔离要求不是很高的切片,由于MBB切片的功能模块能够满足新切片的需求,则小规模的M2M切片可以直接复用现有MBB切片。若单一切片的FB不能够满足第一切片的FB的需求时,再确定多个不同的切片中的FB是否能够满足第一切片的FB的需求,例如,现有MBB切片和小规模的M2M切片,需要创建一个可以计费的抄表业务切片,由于现有的MBB切片和小规模的M2M切片中FB的组合才能够满足该计费的抄表业务切片,那么该计费的抄表业务切片可以复用小规模的M2M切片中全部的FB,外加MBB切片的计费模块。
可选地,若该第一FB与该第二FB不存在反亲和性,且该第二FB不能够满足该第一FB的需求时,确定该第一FB不能够复用该第二FB的资源。
具体而言,虽然第一FB能够与第二FB共享资源,但是若第二FB不能够满足第一FB的需求时,仍然需要重新建立第一FB,且重新分配第一FB所需的资源。应注意,这里切片分配单元确定第二FB是否能够满足第一FB的需求包括是否能够满足第一FB的服务需求和资源需求。
若第二FB能够满足第一FB的服务需求,但是剩余资源容量不能满足第一FB的资源需求时,可以通过扩容第二FB满足第一FB的需求。例如,第二FB能够满足第一FB的服务需求,但是第二FB的剩余资源容量不能够满足第一FB的资源需求,这样可以新增一个虚拟机(Virtual Machine,VM)或者重新创建一个第二FB来满足第一FB的需求,即可以为第一FB分配与第二FB相同的资源。例如,若现有多媒体业务切片,在需要创建针对高级用户(Very Important Person,VIP)的高级别视频业务切片时,则对现有多媒体业务切片的部分功能模块进行扩容来满足该高级别视频业务切片。
若第二FB不能够满足第一FB的服务需求,可以通过扩展FB满足第一
FB的服务需求,也就是需要重新建立第一FB,并分配第一FB所需的资源。例如,现有MBB切片,需要创建一个针对VIP用户的承载视频业务的切片,则保留MBB切片中的控制面的功能模块、在转发面中增加原来没有的增值业务(value added service,VAS)服务器功能模块。
综上可知,若第一切片中的每个FB都不能与网络列表中的已分配资源的FB共享资源,则该第一切片的每个FB都需要重新建立,相应地也需要重新独立的分配资源,即重新建立第一切片,并为该第一切片独立分配资源。若第一切片中的部分FB能够复用已经分配资源的FB,则这部分FB就可以不用重新分配资源。若第一切片中的全部FB都可以复用已经分配资源的FB,则第一切片不需要重新建立。也就是说,第一切片中的FB尽可能的复用切片列表中的已经分配资源的FB,从而提高资源利用率。
可选地,为FB分配的资源主要为物理资源,例如,可以是CPU计算资源、存储资源以及宽带资源等,本发明对此不进行限定。
可选地,将切片分配单元确定的资源分配方式发送给MANO,MANO根据该资源分配方式,进行资源分配,进而完成网络连接服务。
具体而言,NFVO接收切片分配单元的资源分配方式(该资源分配方式即复用现有资源的方式或重新分配资源的方式),这样可以触发MANO去分配资源,进而完成网络连接服务。例如,为第一切片的第一FB重新分配资源,或者复用第二FB的剩余资源。此外,对于为第一FB重新分配资源的FB,NFVO需要验证重新分配资源的有效性(即验证自己是否有足够的资源满足该第一FB的需求),从而为该第一FB分配网络资源,保证了网络连接服务。在MANO完成网络连接服务之后,还可以向发送单元以及切片分配单元响应已经按照该切片分配单元确定的资源分配方式完成了资源分配。
因此,本发明实施例提供的资源分配的方法,切片分配单元接收用于请求第一切片的切片请求,根据该切片请求确定该第一切片包括的FB,并获取包括已分配资源的FB的第二切片,根据该第一切片中的第一FB与该第二切片中的第二FB是否存在反亲和性,确定第一FB是否能够复用第二FB的资源,由此切片分配单元通过对第一切片的FB的需求与已分配资源的FB的综合判断,使得第一切片中的FB尽可能的复用已分配资源的FB,从而提高了资源利用率。
应理解,在本发明的各种实施例中,上述各过程的序号的大小并不意味
着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本发明实施例的实施过程构成任何限定。
下面结合图4详细描述本发明实施例。应注意,这只是为了帮助本领域技术人员更好地理解本发明实施例,而非限制本发明实施例的范围。
在本发明的一个实施例中,切片分配单元接收用于为网络服务请求第一切片的切片请求,根据该切片请求在切片模板中确定与该切片请求最为匹配的至少一个功能模块,并获取切片列表,该切片列表包括至少一个已分配资源的FB,根据该第一切片中的第一FB与该切片列表中的第二FB是否存在反亲和性,确定该第一FB是否能够复用该第二FB的资源,进而确定该第一切片的资源分配方式。若第一切片中的每个FB都不能与网络列表中的已分配资源的FB共享资源,则该第一切片的每个FB都需要重新建立,相应地也需要重新独立的分配资源,即重新建立第一切片,并为该第一切片独立分配资源。若第一切片中的部分FB能够复用已经分配资源的FB,则这部分FB就可以不用重新分配资源。若第一切片中的全部FB都可以复用已经分配资源的FB,则第一切片不需要重新建立。也就是说,该第一切片中的FB尽可能的复用切片列表中的已经分配资源的FB的剩余资源,从而提高资源利用率。
图4是本发明实施例的资源分配的方法的流程示意图。本发明实施例中的各种术语的含义与前述各实施例相同。
S301,切片分配单元接收切片请求,该切片请求用于为网络服务请求第一切片,该切片请求中包括服务需求和资源配置需求。
S302,切片分配单元根据该切片请求确定匹配该第一切片的功能模块FB。
切片分配单元与存储模块有接口,该存储模块存储着预先定义的切片模板,其中也包括还没有上线的切片模板。切片分配单元接收到发送单元发送的切片请求后,根据该切片请求需求的服务和资源在切片模板中确定与该切片请求最为匹配的至少一个功能模块。
S303,获取第二切片,该第二切片包括至少一个已分配资源的FB。
该切片分配单元获取第二切片可以是通过获取切片列表的形式实现,例如,切片列表中可以只包括一个单一的切片,也可以是包括多个切片,也就是说,该切片分配单元可以通过获取切片列表获取到一个第二切片,或者获
取到多个第二切片。
S304,切片分配单元根据该第一切片中的FB与该第二切片的FB是否存在反亲和性,确定该第一FB是否能够复用该第二FB的资源,该反亲和性表示两个FB之间不能够共享资源。
切片分配单元获取该第二切片,进而可以获知该第二切片中已分配资源的FB中的每个FB的资源配置信息,切片分配单元根据第二FB的资源配置信息,可以确定该第一FB与该第二FB是否存在反亲和性,进而可以确定该第一FB是否可以复用第二FB的剩余资源。
S305,若该第一FB与该第二FB存在反亲和性,确定该第一FB不能够复用该第二FB的资源。
S306,若该第一FB与该第二FB不存在反亲和性,还需要确定该第二FB的是否能够满足第一FB的需求。若第二FB不能够满足第一FB的需求,则仍然需要重新分配该第一FB所需的资源,即执行步骤305。
若该第一FB与该第二FB不存在反亲和性,且该第二FB的能满足第一FB的需求确定该第一FB复用第二FB的剩余资源,执行步骤307。
切片分配单元确定第二FB是否能够满足第一FB的需求包括:是否能够满足第一FB的服务需求和是否能够满足第一FB的资源需求。即第二FB要能够满足第一FB的服务需求,以及第二FB的资源能够满足第一FB的资源需求时,该第一FB才能复用第二FB,否则只能重新为第一FB分配资源。
S307,确定第一FB复用第二FB的资源。
该第一FB复用该第二FB的剩余资源,这样可以使得在满足切片相互隔离的基本需求上,尽可能的复用已分配资源的现有切片资源,提高了资源利用率。
应理解,上述相应信息的具体指示方式可参考前述各实施例,为了简洁,在此不再赘述。
因此,本发明实施例提供的资源分配的方法,切片分配单元接收用于请求第一切片的切片请求,根据该切片请求确定该第一切片包括的FB,并获取包括已分配资源的FB的第二切片,根据该第一切片中的第一FB与该第二切片中的第二FB是否存在反亲和性,确定第一FB是否能够复用第二FB的资源,由此切片分配单元通过对第一切片的FB的需求与已分配资源的FB的综合判断,使得第一切片中的FB尽可能的复用已分配资源的FB,从而提
高了资源利用率。
应理解,在本发明的各种实施例中,上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本发明实施例的实施过程构成任何限定。
上文中详细描述了根据本发明实施例的资源分配的方法,下面将描述根据本发明实施例的切片分配单元。
图5示出了根据本发明实施例的切片分配单元500的示意性框图。如图5所示,该切片分配单元500包括:
接收模块510,用于接收切片请求,该切片请求用于为网络服务请求第一切片;
第一确定模块520,用于根据该接收模块接收的该切片请求确定该第一切片包括的功能模块FB;
获取模块530,用于获取第二切片,该第二切片包括已分配资源的FB;
第二确定模块540,用于根据该第一切片中的第一FB与该第二切片中的第二FB是否存在反亲和性,确定该第一FB是否能够复用该第二FB的资源,其中,该反亲和性表示两个FB之间不能够共享资源。
因此,本发明实施例提供的资源分配的切片分配单元,通过接收用于请求第一切片的切片请求,根据该切片请求确定该第一切片包括的FB,并获取包括已分配资源的FB的第二切片,根据该第一切片中的第一FB与该第二切片中的第二FB是否存在反亲和性,确定第一FB是否能够复用第二FB的资源,由此切片分配单元通过对第一切片的FB的需求与已分配资源的FB的综合判断,使得第一切片中的FB尽可能的复用已分配资源的FB,从而提高了资源利用率。
可选地,在本发明实施例中,该第二确定模块540,具体用于:
若该第一FB与该第二FB不存在反亲和性,且该第二FB能够满足该第一FB的需求时,确定该第一FB能够复用该第二FB的资源。
在本发明实施例中,可选地,该第二确定模块540,具体用于:
若该第一FB与该第二FB不存在反亲和性,且该第二FB不能够满足该第一FB的需求时,确定该第一FB不能够复用该第二FB的资源。
可选地,该第二确定模块540,具体用于:
若该第一FB与该第二FB存在反亲和性,确定该第一FB不能够复用该
第二FB的资源。
可选地,在本发明实施例中,该第一FB的需求包括服务需求和资源需求。
在本发明实施例中,可选地,该获取模块530具体用于:
获取根据网络服务与切片的映射关系表生成的该第二切片。
根据本发明实施例的切片分配单元500可对应于根据本发明实施例的资源分配的方法中的切片分配单元,并且切片分配单元500中的各个模块的上述和其它操作和/或功能分别为了实现前述各个方法的相应流程,为了简洁,在此不再赘述。
因此,本发明实施例提供的资源分配的切片分配单元,通过接收用于请求第一切片的切片请求,根据该切片请求确定该第一切片包括的FB,并获取包括已分配资源的FB的第二切片,根据该第一切片中的第一FB与该第二切片中的第二FB是否存在反亲和性,确定第一FB是否能够复用第二FB的资源,由此切片分配单元通过对第一切片的FB的需求与已分配资源的FB的综合判断,使得第一切片中的FB尽可能的复用已分配资源的FB,从而提高了资源利用率。
图6示出了本发明的又一实施例提供的切片分配单元的结构,包括至少一个处理器702(例如CPU),至少一个网络接口705或者其他通信接口,存储器706,和至少一个通信总线703,用于实现这些装置之间的连接通信。处理器702用于执行存储器706中存储的可执行模块,例如计算机程序。存储器706可能包含高速随机存取存储器(RAM:Random Access Memory),也可能还包括非不稳定的存储器(non-volatile memory),例如至少一个磁盘存储器。通过至少一个网络接口705(可以是有线或者无线)实现与至少一个其他网元之间的通信连接。
在一些实施方式中,存储器706存储了程序7061,处理器702执行程序7061,用于执行一些操作:
接收切片请求,该切片请求用于为网络服务请求第一切片;
根据该切片请求确定该第一切片包括的功能模块FB;
获取第二切片,该第二切片包括已分配资源的FB;
根据该第一切片中的第一FB与该第二切片中的第二FB是否存在反亲和性,确定该第一FB是否能够复用该第二FB的资源,其中,该反亲和性
表示两个FB之间不能够共享资源。
可选地,处理器702具体用于:
若该第一切片中的第一FB与该第二切片中的第二FB不存在反亲和性,且该第二FB能够满足该第一FB的需求时,确定该第一FB能够复用该第二FB的资源。
在本发明实施例中,可选地,处理器702具体用于:
若该第一切片中的第一FB与该第二切片中的第二FB不存在反亲和性,且该第二FB不能够满足该第一FB的需求时,确定该第一FB不能够复用该第二FB的资源。
在本发明实施例中,可选地,处理器702具体用于:
若该第一切片中的第一FB与该第二切片中的第二FB存在反亲和性,确定该第一FB不能够复用该第二FB的资源。
可选地,在本发明实施例中,该第一FB的需求包括服务需求和资源需求。
在本发明实施例中,可选地,处理器702具体用于:
获取根据网络服务与切片的映射关系表生成的该第二切片。
从本发明实施例提供的以上技术方案可以看出,切片分配单元接收用于请求第一切片的切片请求,根据该切片请求确定该第一切片包括的FB,并获取包括已分配资源的FB的第二切片,根据该第一切片中的第一FB与该第二切片中的第二FB是否存在反亲和性,确定第一FB是否能够复用第二FB的资源,由此切片分配单元通过对第一切片的FB的需求与已分配资源的FB的综合判断,使得第一切片中的FB尽可能的复用已分配资源的FB,从而提高了资源利用率。
应理解,本文中术语“和/或”,仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。另外,本文中字符“/”,一般表示前后关联对象是一种“或”的关系。
应理解,在本发明的各种实施例中,上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本发明实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到,结合本文中所公开的实施例描述的各
示例的单元及算法步骤,能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本发明的范围。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的***、装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的***、装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,该单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个***,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本发明各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(ROM,Read-Only Memory)、随机存取存储器(RAM,Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述,仅为本发明的具体实施方式,但本发明的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本发明揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本发明的保护范围之内。因此,本发明的保护范围应以该权利要求的保护范围为准。
Claims (12)
- 一种资源分配的方法,其特征在于,所述方法包括:接收切片请求,所述切片请求用于为网络服务请求第一切片;根据所述切片请求确定所述第一切片包括的功能模块FB;获取第二切片,所述第二切片包括已分配资源的FB;根据所述第一切片中的第一FB与所述第二切片中的第二FB是否存在反亲和性,确定所述第一FB是否能够复用所述第二FB的资源,其中,所述反亲和性表示两个FB之间不能够共享资源。
- 根据权利要求1所述的方法,其特征在于,所述根据所述第一切片中的第一FB与所述第二切片中的第二FB是否存在反亲和性,确定所述第一FB是否能够复用所述第二FB的资源,包括:若所述第一FB与所述第二FB不存在反亲和性,且所述第二FB能够满足所述第一FB的需求时,确定所述第一FB能够复用所述第二FB的资源。
- 根据权利要求1所述的方法,其特征在于,所述根据所述第一切片中的第一FB与所述第二切片中的第二FB是否存在反亲和性,确定所述第一FB是否能够复用所述第二FB的资源,包括:若所述第一FB与所述第二FB不存在反亲和性,且所述第二FB不能够满足所述第一FB的需求时,确定所述第一FB不能够复用所述第二FB的资源。
- 根据权利要求1所述的方法,其特征在于,所述根据所述第一切片中的第一FB与所述第二切片中的第二FB是否存在反亲和性,确定所述第一FB是否能够复用所述第二FB的资源,包括:若所述第一FB与所述第二FB存在反亲和性,确定所述第一FB不能够复用所述第二FB的资源。
- 根据权利要求2或3所述的方法,其特征在于,所述第一FB的需求包括服务需求和资源需求。
- 根据权利要求1至5中任一项所述的方法,其特征在于,所述获取第二切片,包括:获取根据网络服务与切片的映射关系表生成的所述第二切片。
- 一种切片分配单元,其特征在于,包括:接收模块,用于接收切片请求,所述切片请求用于为网络服务请求第一 切片;第一确定模块,用于根据所述接收模块接收的所述切片请求确定所述第一切片包括的功能模块FB;获取模块,用于获取第二切片,所述第二切片包括已分配资源的FB;第二确定模块,用于根据所述第一切片中的第一FB与所述第二切片中的第二FB是否存在反亲和性,确定所述第一FB是否能够复用所述第二FB的资源,其中,所述反亲和性表示两个FB之间不能够共享资源。
- 根据权利要求7所述的切片分配单元,其特征在于,所述第二确定模块,具体用于:若所述第一FB与所述第二FB不存在反亲和性,且所述第二FB能够满足所述第一FB的需求时,确定所述第一FB能够复用所述第二FB的资源。
- 根据权利要求7所述的切片分配单元,其特征在于,所述第二确定模块,具体用于:若所述第一FB与所述第二FB不存在反亲和性,且所述第二FB不能够满足所述第一FB的需求时,确定所述第一FB不能够复用所述第二FB的资源。
- 根据权利要求7所述的切片分配单元,其特征在于,所述确定模块,具体用于:若所述第一FB与所述第二FB存在反亲和性,确定所述第一FB不能够复用所述第二FB的资源。
- 根据权利要求8或9所述的切片分配单元,其特征在于,所述第一FB的需求包括服务需求和资源需求。
- 根据权利要求7至11中任一项所述的切片分配单元,其特征在于,所述获取模块具体用于:获取根据网络服务与切片的映射关系表生成的所述第二切片。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2015/097102 WO2017096606A1 (zh) | 2015-12-11 | 2015-12-11 | 资源分配的方法和切片分配单元 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2015/097102 WO2017096606A1 (zh) | 2015-12-11 | 2015-12-11 | 资源分配的方法和切片分配单元 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017096606A1 true WO2017096606A1 (zh) | 2017-06-15 |
Family
ID=59012572
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2015/097102 WO2017096606A1 (zh) | 2015-12-11 | 2015-12-11 | 资源分配的方法和切片分配单元 |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2017096606A1 (zh) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10264506B2 (en) * | 2017-05-13 | 2019-04-16 | Qualcomm Incorporated | Enable a network-trigger change of network slices |
US10820185B2 (en) | 2017-05-08 | 2020-10-27 | Qualcomm Incorporated | Mobility between areas with heterogeneous network slices |
US11303526B2 (en) | 2018-01-12 | 2022-04-12 | Huawei Technologies Co., Ltd. | Network slice deployment method and apparatus |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140098781A1 (en) * | 2012-10-05 | 2014-04-10 | Sierra Wireless, Inc. | Method, Apparatus and System for Uplink Radio Resource Allocation in an LTE Communication System |
CN104135341A (zh) * | 2014-07-31 | 2014-11-05 | 广州金山网络科技有限公司 | 一种数据通信方法、装置以及*** |
US20140342746A1 (en) * | 2011-11-02 | 2014-11-20 | Sharp Kabushiki Kaisha | Communication system, mobile station apparatus, base station apparatus, communication method, and integrated circuit |
CN104584614A (zh) * | 2012-08-22 | 2015-04-29 | 高通股份有限公司 | 用于改进多无线电共存性的时频调度 |
-
2015
- 2015-12-11 WO PCT/CN2015/097102 patent/WO2017096606A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140342746A1 (en) * | 2011-11-02 | 2014-11-20 | Sharp Kabushiki Kaisha | Communication system, mobile station apparatus, base station apparatus, communication method, and integrated circuit |
CN104584614A (zh) * | 2012-08-22 | 2015-04-29 | 高通股份有限公司 | 用于改进多无线电共存性的时频调度 |
US20140098781A1 (en) * | 2012-10-05 | 2014-04-10 | Sierra Wireless, Inc. | Method, Apparatus and System for Uplink Radio Resource Allocation in an LTE Communication System |
CN104135341A (zh) * | 2014-07-31 | 2014-11-05 | 广州金山网络科技有限公司 | 一种数据通信方法、装置以及*** |
Non-Patent Citations (1)
Title |
---|
NGMN ALLIANCE: "NGMN 5G White Paper", NEXT GENERATION MOBILE NETWORKS, vol. 30, 17 February 2015 (2015-02-17), pages 46 - 48 and 104 * |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10820185B2 (en) | 2017-05-08 | 2020-10-27 | Qualcomm Incorporated | Mobility between areas with heterogeneous network slices |
US11611865B2 (en) | 2017-05-08 | 2023-03-21 | Qualcomm Incorporated | Mobility between areas with heterogeneous network slices |
US10264506B2 (en) * | 2017-05-13 | 2019-04-16 | Qualcomm Incorporated | Enable a network-trigger change of network slices |
US20190239136A1 (en) * | 2017-05-13 | 2019-08-01 | Qualcomm Incorporated | Enable a network-trigger change of network slices |
US10880806B2 (en) | 2017-05-13 | 2020-12-29 | Qualcomm Incorporated | Enable a network-trigger change of network slices |
US11553394B2 (en) | 2017-05-13 | 2023-01-10 | Qualcomm Incorporated | Enable a network-trigger change of network slices |
US11303526B2 (en) | 2018-01-12 | 2022-04-12 | Huawei Technologies Co., Ltd. | Network slice deployment method and apparatus |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN109845303B (zh) | 网络切片的管理方法及管理单元 | |
US10838890B2 (en) | Acceleration resource processing method and apparatus, and network functions virtualization system | |
US9389903B2 (en) | Method, system and apparatus for creating virtual machine | |
JP6614340B2 (ja) | ネットワーク機能仮想化管理オーケストレーション装置と方法とプログラム | |
US11301303B2 (en) | Resource pool processing to determine to create new virtual resource pools and storage devices based on currebt pools and devices not meeting SLA requirements | |
CN113795826A (zh) | 用于分布式计算的自动化资源管理 | |
US10924966B2 (en) | Management method, management unit, and system | |
CN110221918B (zh) | 一种ns与vnf的关联方法、装置及*** | |
CN107959582B (zh) | 一种切片实例的管理方法及装置 | |
US20180018197A1 (en) | Virtual Machine Resource Allocation Method and Apparatus | |
US20120167081A1 (en) | Application Service Performance in Cloud Computing | |
US20140379928A1 (en) | Method for implementing network using distributed virtual switch, apparatus for performing the same, and network system based on distributed virtual switch | |
CN108132827B (zh) | 一种网络切片资源映射方法、相关设备及*** | |
WO2019062830A1 (zh) | 实例业务拓扑的生成方法及装置 | |
EP3531749B1 (en) | Management method, management unit and system for network function | |
CN110034944B (zh) | 网络切片部署方法及其装置 | |
CN107251486A (zh) | 一种扩展联动的方法、装置及*** | |
JP5596716B2 (ja) | リソース管理装置、リソース管理システム、リソース管理方法およびリソース管理プログラム | |
WO2017096606A1 (zh) | 资源分配的方法和切片分配单元 | |
CN108028806B (zh) | 网络功能虚拟化nfv网络中分配虚拟资源的方法和装置 | |
CN106161652A (zh) | 基于Zstack请求的私有云平台及其调度方法 | |
CN115426320A (zh) | 一种安全资源调度方法、装置、电子设备及存储介质 | |
CN114172753B (zh) | 地址预留的方法、网络设备和*** | |
CN107534678B (zh) | 建立vnfm与vim之间的连接的方法、装置及*** | |
CN115211159A (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: 15910081 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 15910081 Country of ref document: EP Kind code of ref document: A1 |