WO2017096606A1

WO2017096606A1 - Resource allocation method and slice allocation unit

Info

Publication number: WO2017096606A1
Application number: PCT/CN2015/097102
Authority: WO
Inventors: 宋灵燕; 唐朋成; 周伟
Original assignee: 华为技术有限公司
Priority date: 2015-12-11
Filing date: 2015-12-11
Publication date: 2017-06-15

Abstract

Embodiments of the present invention provide a resource allocation method and a slice allocation unit. The method comprises: receiving a slice request for requesting a first slice for a network service; determining, according to the slice request, a functional block (FB) comprised in the first slice; acquiring a second slice comprising an FB having an allocated resource; and determining, according to whether anti-affinity exists between a first FB in the first slice and a second FB in the second slice, whether the first FB can reuse the resource of the second FB, wherein the anti-affinity indicates that the two FBs cannot share a resource. According to the technical solution of the present invention, the slice allocation unit reuses any possible FBs having allocated resources as the FB in the first slice by taking a requirement of the FB of the first slice and the allocated resource into consideration, thereby improving a resource utilization rate.

Description

Resource allocation method and slice allocation unit

Technical field

The present invention relates to the field of communications and, more particularly, to a method of resource allocation and a slice allocation unit.

Background technique

In future 5G systems, the network will be further abstracted into a Network Slice based on logical functions and built as a "custom function + general purpose hardware". In the 5G network architecture, through the combination of Software-defined Networking (SDN) and Network Functions Virtualization (NFV) technologies, 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.

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.

Summary of the invention

The embodiment of the invention provides a resource allocation method and a slice allocation unit, which can improve resource utilization.

In a first aspect, a method of resource allocation is provided. The method 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 By comprehensively judging the requirement of the FB of the first slice and the FB of the allocated resource, the FB in the first slice multiplexes the FB of the allocated resource as much as possible, thereby improving resource utilization.

With reference to the first aspect, in a first possible implementation manner of the first aspect, determining whether the first FB in the first slice and the second FB in the second slice have a reverse affinity Whether the FB can multiplex the resources of the second FB, if: the first FB and the second FB do not have reverse affinity, and the second FB can meet the requirement of the first FB, determine the first An FB can multiplex the resources of the second FB.

If the first FB can share resources with the second FB, it is also necessary to determine whether the second FB can meet the requirements of the first FB, the requirements including 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 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.

With reference to the first aspect, in a second possible implementation manner of the first aspect, determining whether the first FB in the first slice and the second FB in the second slice have a reverse affinity Whether the FB can multiplex the resources of the second FB, if: the first FB and the second FB do not have reverse affinity, and the second FB cannot meet the requirement of the first FB, determine the The first FB cannot multiplex the resources of the second FB.

In conjunction with the first aspect, in a third possible implementation of the first aspect, 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.

In conjunction with the first possible implementation of the first aspect or the second possible implementation of the first aspect, in a fourth possible implementation of the first aspect, the requirement of the first FB includes service requirements and resources demand.

If the second FB cannot meet the service requirement of the first FB, 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.

If 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.

If 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.

In combination with the first aspect or the first possible implementation of the first aspect to any one of the possible implementations of the fourth possible implementation of the first aspect, the fifth possible implementation of the first aspect The acquiring the second slice 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.

In a second aspect, the present application provides a slice allocation unit that includes means for performing the method of the first aspect.

In a third aspect, a slice allocation unit is provided, including: a processor and a memory;

The memory stores a program, and 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.

In the embodiment of the present invention, 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.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are only some of the present invention. For the embodiments, those skilled in the art can obtain other drawings according to the drawings without any creative work.

FIG. 1 is a schematic diagram of a network architecture according to an embodiment of the present invention.

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.

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are a part of the embodiments of the present invention, but not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope 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. In addition to mobile broadband, more diverse services such as Vehicle to Vehicle (V2V) and machine communication will emerge. In a 5G system, 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 Provides connectivity services to users in the form of 'network as a service' and meets the specific requirements of each use case by freely and flexibly combining network performance metrics such as rate, capacity, coverage, latency, reliability, security, and availability.

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.

Table 1 consists of the classification of logical function modules in the slice

For example, 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.

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) unit, virtual infrastructure management (Virtualized Infrastructure) Management, VIM) unit and network function Virtualization Infrastructure (NFVI) unit. Among them, 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. In the prior art, for different 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.

S120, determining, according to the slice request, the function module FB included in the first slice;

S130: Acquire a second slice, where the second slice includes an FB with allocated resources;

S140, determining whether the first FB is capable of multiplexing 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, where the reverse Affinity means that resources cannot be shared between two FBs.

Specifically, 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. 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 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.

It should be understood that 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. . For convenience of description, 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.

Therefore, the method for resource allocation provided by the embodiment of the present invention, 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.

In S110, specifically, 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. For example, 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.

It should be understood that the sending unit may be the foregoing OSS/BSS or an operator, which is not limited by the present invention.

At S120, the slice allocation unit determines a function module FB that matches the first slice according to the slice request.

Specifically, 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.

At S130, specifically, a second slice is acquired, the second slice including an FB of allocated resources.

Specifically, the obtaining, by the slice allocation unit, the second slice may be implemented by acquiring a slice list. For example, 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.

Optionally, 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.

Optionally, 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.

Specifically, 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.

S140. 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.

Specifically, the first FB may be any one of the first slices, and 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. If the first FB has a reverse affinity with the second FB, that is, the first FB cannot share resources with the second FB, 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.

Optionally, if 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.

Specifically, if 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.

It should be noted that when the FB in the first slice multiplexes the FBs in the slice list, the FBs in the same slice are used as much as possible, which facilitates subsequent scheduling. Therefore, when 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. If 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.

Optionally, if 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.

Specifically, although the first FB can share resources with the second FB, if the second FB cannot meet the requirements of the first FB, it is still necessary to re-establish the first FB and reallocate the resources required by the first FB. It should be noted that the slice allocation unit here 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.

If the second FB can satisfy the service requirement of the first FB, but the remaining resource capacity cannot meet the resource requirement of the first FB, the requirement of the first FB can be satisfied by expanding the second FB. For example, 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.

If 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.

In summary, if 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 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.

Optionally, 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.

Optionally, 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.

Specifically, 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. In addition, for the FB that reallocates the resource for the first 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. After the MANO completes the network connection service, 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.

It should be understood that the size of the serial numbers of the above processes does not imply in various embodiments of the present invention. The order of execution, the order of execution of each process should be determined by its function and internal logic, and should not be construed as limiting the implementation of the embodiments of the present invention.

Embodiments of the present invention are described in detail below in conjunction with FIG. It should be noted that this is only to assist those skilled in the art to better understand the embodiments of the present invention and not to limit the scope of the embodiments of the present invention.

In an embodiment of the present invention, 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. If 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.

S301. 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.

S302. 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.

S303. Acquire a second slice, where the second slice includes at least one FB of the allocated resource.

The obtaining, by the slice allocation unit, the second slice may be implemented by acquiring a slice list. For example, 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.

S304. 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.

S305. If the first FB has a reverse affinity with the second FB, determine that the first FB cannot multiplex the resources of the second FB.

S306. If the first FB does not have reverse affinity with the second FB, it is further determined whether the second FB can meet the requirement of the first FB. If the second FB is unable to meet the requirements of the first FB, the resource required for the first FB needs to be re-allocated, that is, step 305 is performed.

If the first FB does not have a reverse affinity with the second FB, and the second FB can satisfy the requirement of the first FB, and the first FB multiplexes the remaining resources of the second FB, 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.

S307. Determine that the first FB multiplexes resources of the second FB.

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.

It should be understood that the foregoing specific manners of the corresponding information may refer to the foregoing embodiments, and are not described herein for brevity.

Therefore, the method for resource allocation provided by the embodiment of the present invention, 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.

It should be understood that, in various embodiments of the present invention, 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. As shown in FIG. 5, 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.

Therefore, the slice allocation unit of the resource allocation provided by the embodiment of the present invention 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.

Optionally, in the embodiment of the present invention, the second determining module 540 is specifically configured to:

If 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.

In the embodiment of the present invention, the second determining module 540 is specifically configured to:

If 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.

Optionally, the second determining module 540 is specifically configured to:

If 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.

Optionally, in the embodiment of the present invention, the requirement of the first FB includes a service requirement and a resource requirement.

In the embodiment of the present invention, the obtaining module 530 is specifically configured to:

Obtaining the second slice generated according to the mapping table of the network service and the slice.

The slice allocation unit 500 according to an embodiment of the present invention 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.

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).

In some embodiments, the memory 706 stores a program 7061, and the processor 702 executes the program 7061 for performing some operations:

Receiving a slice request for requesting a first slice for a network service;

Determining, according to the slice request, the function module FB included in the first slice;

Obtaining a second slice, the second slice including an FB of the allocated resource;

Determining whether the first FB is capable of multiplexing 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, wherein the reverse affinity Sex Indicates that resources cannot be shared between two FBs.

Optionally, the processor 702 is specifically configured to:

If 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.

In the embodiment of the present invention, the processor 702 is specifically configured to:

If the first FB in the first slice does not have reverse affinity with the second FB in the second slice, and the second FB cannot meet the requirement of the first FB, determining that the first FB is not The resources of the second FB can be multiplexed.

If 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.

As can be seen from the above technical solution provided by the embodiment of the present invention, 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.

It should be understood that the term "and/or" herein is merely an association relationship describing an associated object, indicating that there may be three relationships, for example, A and/or B, which may indicate that A exists separately, and A and B exist simultaneously. There are three cases of B alone. In addition, the character "/" in this article generally indicates that the contextual object is an "or" relationship.

One of ordinary skill in the art will recognize that each of the embodiments described herein in connection with the embodiments disclosed herein The exemplary unit and algorithm steps can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, 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. In addition, 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.

In addition, 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. Based on such understanding, 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. .

The above is only a specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the appended claims.

Claims

A method for resource allocation, characterized in that the method comprises:

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;

Obtaining a second slice, the second slice including an FB of the allocated resource;

Determining, according to whether the first FB in the first slice and the second FB in the second slice have a reverse affinity, determining whether the first FB can multiplex resources of the second FB, where The reverse affinity means that resources cannot be shared between two FBs.
The method according to claim 1, wherein the determining the first according to whether a first FB in the first slice and a second FB in the second slice have a reverse affinity Whether the FB can reuse the resources of the second FB, including:

Determining that the first FB can multiplex the second FB if the first FB and the second FB do not have reverse affinity, and the second FB can meet the requirement of the first FB resource of.
The method according to claim 1, wherein the determining the first according to whether a first FB in the first slice and a second FB in the second slice have a reverse affinity Whether the FB can reuse the resources of the second FB, including:

If the first FB and the second FB do not have reverse affinity, and the second FB cannot meet the requirement of the first FB, determining that the first FB is unable to multiplex the first FB Two FB resources.
The method according to claim 1, wherein the determining the first according to whether a first FB in the first slice and a second FB in the second slice have a reverse affinity Whether the FB can reuse the resources of the second FB, including:

If the first FB and the second FB have reverse affinity, it is determined that the first FB cannot multiplex the resources of the second FB.
The method according to claim 2 or 3, wherein the demand of the first FB comprises a service requirement and a resource requirement.
The method according to any one of claims 1 to 5, wherein the acquiring the second slice comprises:

Obtaining the second slice generated according to a mapping table of network services and slices.
A slice allocation unit, comprising:

a receiving module, configured to receive a slice request, where the slice request is used to request a first network service slice;

a first determining module, configured to determine, according to the slice request received by the receiving module, a function module FB included in the first slice;

An acquiring module, configured to acquire a second slice, where the second slice includes an FB of the allocated resource;

a second determining module, configured to determine whether the first FB is capable of multiplexing the first FB according to whether a first FB in the first slice and a second FB in the second slice have a reverse affinity A resource of two FBs, wherein the anti-affinity means that resources cannot be shared between two FBs.
The slice allocation unit according to claim 7, wherein the second determining module is specifically configured to:

Determining that the first FB can multiplex the second FB if the first FB and the second FB do not have reverse affinity, and the second FB can meet the requirement of the first FB resource of.
The slice allocation unit according to claim 7, wherein the second determining module is specifically configured to:

If the first FB and the second FB do not have reverse affinity, and the second FB cannot meet the requirement of the first FB, determining that the first FB is unable to multiplex the first FB Two FB resources.
The slice allocation unit according to claim 7, wherein the determining module is specifically configured to:

If the first FB and the second FB have reverse affinity, it is determined that the first FB cannot multiplex the resources of the second FB.
The slice allocation unit according to claim 8 or 9, wherein the demand of the first FB comprises a service requirement and a resource requirement.
The slice allocation unit according to any one of claims 7 to 11, wherein the acquisition module is specifically configured to:

Obtaining the second slice generated according to a mapping table of network services and slices.